Hyundai Tucson Hybrid 2022 CAN error when going onroad

Describe the bug
Bought and installed a C3X for my girlfriend's mom in her Hyundai Tucson Hybrid 2022, but we are getting "CAN Error: Check Connections" error when starting the car and openpilot going from offroad to onroad. See route 4c55c9ec1741c686|2024-01-06--13-31-21--0 for an example. Currently on devel branch for stock openpilot 0.9.5.
I was able to walk her through the process of setting up her Connect account and sharing her device with me. I was able to SSH into the device via Connect and tmux a while she started the car. It looks like there might be some issue with the ACCELERATOR_BRAKE_ALT CAN message as the following errors started popping up constantly:
opendbc/can/parser.cc: 0x100 'ACCELERATOR_BRAKE_ALT' NOT SEEN

Screenshots of logs below (note there is some overlap between the screenshots to make sure I captured it all):

Which car does this affect?
Hyundai Tucson Hybrid 2022
Provide a route where the issue occurs
4c55c9ec1741c686|2024-01-06--13-31-21
openpilot version
0.9.5
Additional info
No response

I switched her to master-ci and tried again, but getting the same issue.
This appears to be a potential fingerprinting issue where the car is being detected as the ICE variant rather than the hybrid (e.g. seems to fingerprint as TUCSON_4TH_GEN rather than TUCSON_HYBRID_4TH_GEN). By reading the logs in Connect Admin, I was able to get these firmwares:
'carFw': [{'address': 1975,
                          'brand': 'hyundai',
                          'bus': 0,
                          'ecu': 'cornerRadar',
                          'fwVersion': b'\xf1\x003D',
                          'logging': True,
                          'obdMultiplexing': True,
                          'request': [b'"\xf1\x00'],
                          'responseAddress': 1983,
                          'subAddress': 0},
                         {'address': 1971,
                          'brand': 'hyundai',
                          'bus': 0,
                          'ecu': 'hvac',
                          'fwVersion': b"\xf1\x00NX4   97255-P0030CONTROL ASS'Y-DATC  1.04 NX4HEV ATC 0.7 V1.00",
                          'logging': True,
                          'obdMultiplexing': True,
                          'request': [b'"\xf1\x00'],
                          'responseAddress': 1979,
                          'subAddress': 0},
                         {'address': 2000,
                          'brand': 'hyundai',
                          'bus': 0,
                          'ecu': 'fwdRadar',
                          'fwVersion': b'\xf1\x00NX4__               1.00 1.00 99110-N9100         ',
                          'logging': False,
                          'obdMultiplexing': True,
                          'request': [b'"\xf1\x00'],
                          'responseAddress': 2008,
                          'subAddress': 0},
                         {'address': 1988,
                          'brand': 'hyundai',
                          'bus': 0,
                          'ecu': 'fwdCamera',
                          'fwVersion': b'\xf1\x00NX4 FR_CMR AT USA LHD 1.00 1.00 99211-N9210 14G',
                          'logging': False,
                          'obdMultiplexing': True,
                          'request': [b'"\xf1\x00'],
                          'responseAddress': 1996,
                          'subAddress': 0},
                         {'address': 1969,
                          'brand': 'hyundai',
                          'bus': 0,
                          'ecu': 'parkingAdas',
                          'fwVersion': b'\xf1\x10NX4H ADAS_PRK ANL 1.00 1.01 99910-P0800',
                          'logging': True,
                          'obdMultiplexing': True,
                          'request': [b'"\xf1\x10'],
                          'responseAddress': 1977,
                          'subAddress': 0}],

Based on the current selfdrive/car/hyundai/values.py, the Ecu.fwdRadar value of b'\xf1\x00NX4__               1.00 1.00 99110-N9100         ' already exists, but I did need to add the value of b'\xf1\x00NX4 FR_CMR AT USA LHD 1.00 1.00 99211-N9210 14G' to Ecu.fwdCamera.
However, now the same Ecu.fwdCamera and Ecu.fwdRadar values appear in both CAR.TUCSON_4TH_GEN and CAR.TUCSON_HYBRID_4TH_GEN. I'm guessing it's defaulting to CAR.TUCSON_4TH_GEN since it appears first in the list and already has the matching firmwares:

For now, I will look into how to force the TUCSON_HYBRID_4TH_GEN fingerprint, but what's the best way to fix this going forward? Do we need to add additional ECU firmware types such as cornerRadar, hvac, or parkingAdas so that there is more information available to differentiate between the ICE and hybrid versions?

After hard-coding to TUCSON_HYBRID_4TH_GEN, we were able to get everything working! (is this the best way to hard-code?) Still looking for guidance on how to upstream her fwdCamera firmware version into master so that there's not a collision with TUCSON_4TH_GEN though.

Hey! We just merged a PR to detect if the car is hybrid or not, so your car will be supported on master after https://github.com/commaai/openpilot/pull/31238


【建议】[Suggestion] Remove generic methods and open up the getMacInstalledApps search parameter.

1.开放了MacOS的getMacInstalledApps方法的搜索App的目录，兼容系统的/System/Applications里面的App.
2.因为不同平台返回的数据不同，就删除了公共方法，交给用户自行判断。

Opened the getMacInstalledApps method of MacOS to search the App directory, which is compatible with the Apps in /System/Applications of the system.
Because the data returned by different platforms are different, the public method is deleted and left to the user's own judgment.

可以暴露，我有预留的口子，但是没有暴露出来


touch: Add ioctl to enable/disable gesture

Summary
Impact
New IOCTL code
Testing
factory test

Please update Documentation/components/drivers/character/touchscreen.rst

Please update Documentation/components/drivers/character/touchscreen.rst

But touchscreen.rst doesn't describe any IOCTL at all.:(.


Sorting: Implement Bucket sort in C++

https://en.wikipedia.org/wiki/Bucket_sort

Hey, @akgmage assign this to me.


"Source for this Page" links broken on the manual site

Links to "Source for this page" in the Laika manual are somewhat malformed. For example, I get the following from this page:
https://github.com/planet42/Laika/tree/master/docs/03-preparing-content/03-theme-settings.md
Which returns github's custom 404. Walking the source tree, the correct URL seems to be :
https://github.com/planet42/Laika/blob/master/docs/src/03-preparing-content/03-theme-settings.md

Thank you for raising this. The src sub-directory had been introduced at some later point, and the manual had not been updated for this.

Yes, that link is broken for other reasons, thanks again.
And yes, as long as this ticket is open you can add them to the list, but most likely I'll push fixes over the weekend that will auto-close this ticket. After that it's then better to open new tickets.


Feature request: synchronization primitives for async functions

Problem: when an asynchronous function is called and accesses shared or global state, race conditions arise.
Solution: provide some mechanism to prevent reentrance into asynchronous function (or section of function), so that only one invocation may run at a time.  This can be done by waiting for the previous function to finish, or by aborting the previous invocation with a Promise rejection.  I see this working similarly to the C# lock keyword.
Problem:
function wait() {
	return new Promise( resolve => { setTimeout( resolve, Math.random() * 10 ); } );
}

let shared: number;
async function foo() {
	shared = 0;
	for( let i = 0; i < 100; i++ ) {
		shared += 5;
		await wait();
	}
	return shared;
}
foo().then( c => { console.log( c ); } ); // unpredictable output
foo().then( c => { console.log( c ); } ); // race condition

Strawman:
symbol foolock = Symbol();
@lock( foolock, /* block */ false )
async function foo() {
	// ...
}
foo().then( c => { console.log( c ); } ); // rejects, doesn't output
foo().then( c => { console.log( c ); } ); // predictable output, pre-empts last invocation

This could be at the function level, or at the block level:
async function foo() {
	lock( foolock ) { // statement causes rejection in other functions currently holding foolock
	}
	await lock( barlock ) { // statement blocks until barlock becomes available
	}
}

Challenge:
I see three possible behaviors for a lock block:

Block
Reject others
Reject self

I'm not sure how to express which one is desirable.  1 and 3 might be possible to implement from an external library, but 2 would require integration into __awaiter.

For real-world scenarios running into this problem, consider:

a function executing a sequence of animation steps (reentrance causes irratic interleaved animation)
a function loading the components of a scene through AJAX (reentrance causes mix of SceneA and SceneB elements being loaded)

This is an area of possible conflict with the future of JavaScript. I would say this should go as a proposal for TC39 (https://github.com/tc39/ecma262#ecmascript). We have avoided areas of possible conflict with the committee to ensure that TypeScript is a super set of JavaScript. This issue is thus out of scope for the typescript project at the time being.
I would recommend @rbuckton's prex library for some of these concepts (see https://github.com/rbuckton/prex),

@errorx666 to expand on @mhegazy's comment above, I wrote prex for just this purpose. Using Semaphore, your example above would read something like this:
import { Semaphore } from "prex";
const foolock = new Semaphore(1);
async function foo() {
    await foolock.wait(); // statement suspends until foolock becomes available
    try {
      // code inside of block goes here...
    }
    finally {
      foolock.release();
    }
}

1. Block

This is feasible using the Semaphore example I provided, above.

2. Reject others

This is likely difficult to accomplish or does not do what you would expect, as you cannot implicitly stop execution of another function without some mechanism for that other function to check whether it should reject. One option for that scenario is to use a CancellationToken and have the other callees invoke token.throwIfCancellationRequested().

3. Reject self

This is somewhat possible by pairing a Semaphore with a CancellationToken, and having the token reject after a short delay:
import { Semaphore, CancellationTokenSource } from "prex";
const foolock = new Semaphore(1);

async function foo () {
  const cts = new CancellationTokenSource();
  setTimeout(() => cts.cancel(), 0); // cancel the source immediately

  await foolock.wait(cts.token); // throws if foolock is not available immediately
  try {
  }
  finally {
    foolock.release();
  }
}


Improve 2FA autofill

This improves the autofill suggestion on mobile devices and some password managers.
I got the ideas of those changes from this article from Twilio
It seems to improve autofilling in both mobile devices and desktop password managers as tested in Issue #15403

Codecov Report

Merging #16473 (3056d91) into main (ec35783) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #16473      +/-   ##
==========================================
- Coverage   45.43%   45.42%   -0.02%
==========================================
  Files         717      717
  Lines       84184    84184
==========================================
- Hits        38252    38243       -9
- Misses      39780    39790      +10
+ Partials     6152     6151       -1

Impacted Files
Coverage Δ

services/mailer/mail_comment.go
77.77% <0.00%> (-7.41%)
:arrow_down:

modules/process/manager.go
72.83% <0.00%> (-2.47%)
:arrow_down:

modules/notification/mail/mail.go
36.27% <0.00%> (-1.97%)
:arrow_down:

modules/git/blame.go
65.71% <0.00%> (-1.43%)
:arrow_down:

services/pull/pull.go
41.93% <0.00%> (-0.44%)
:arrow_down:

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 ec35783...3056d91. Read the comment docs.


Better DX for healthcheck

I think the test field in healthcheck should be abstracted into a new cmd field and the time intervals could also be humanized.
Currently the test field is a single list where the first element has special meaning:
#HealthCheck: {
	test?: [...string]
	interval?:    int
	timeout?:     int
	startperiod?: int
	retries?:     int
}

The options are:

[]: inherit healthcheck
["NONE"] : disable healthcheck
["CMD", args...] : exec arguments directly
["CMD-SHELL", command] : run command with system's default shell

Here's what some dockerfile instructions produce:
CMD-SHELL
HEALTHCHECK --interval=5m --timeout=3s CMD curl -f http://localhost/ || exit 1

healthcheck: {
    test: [
        "CMD-SHELL",
        "curl -f http://localhost/ || exit 1",
    ]
    interval:<PHONE_NUMBER>00
    timeout:<PHONE_NUMBER>
}

CMD
HEALTHCHECK --interval=5m --timeout=3s CMD ["curl", "-f", "http://localhost/"]

healthcheck: {
    test: [
        "CMD",
        "curl",
        "-f",
        "http://localhost/",
    ]
    interval:<PHONE_NUMBER>00
    timeout:<PHONE_NUMBER>
}

NONE
HEALTHCHECK NONE

healthcheck: {
    test: ["NONE"]
}

Proposal
Change to:
#HealthCheck: {
	{
		disable: true
	} | {
		cmd: string | [...string]
		interval?: int | #Duration
		timeout?: int | #Duration
		start_period?: int | #Duration
		retries?: int
	}
}

#Duration: string // regex here

Then, the previous calls would become:
config: {
    healthcheck: {
        cmd: "curl -f http://localhost/ || exit 1"
        interval: "3s"
        timeout: "3s"
    }
}

config: {
    healthcheck: {
        cmd: ["curl", "-f", "http://localhost/"]
        interval: "3s"
        timeout: "3s"
    }
}

config: {
    healthcheck: disable: true
}

I'm closing this since the 0.2 CUE API is frozen, in favor of the GraphQL API.


[Feature]: Button card

Requirements

[X] I have updated Mushroom to the latest available version
[X] I did a search to see if there is a similar issue or if a pull request is open.

Is your feature request related to a problem?
I'd like to be able to use <mushroom-button> separately. It would be useful for various actions on my dashboard. In my scenario, I use components to navigate to the dashboard of each component. Currently I can't use a single button style

square: true
type: grid
columns: 4
cards:
  - type: custom:vertical-stack-in-card
    cards:
      - type: custom:mushroom-light-card
        entity: light.103_office_biodynamic_light
        layout: vertical
        name: Světla
        fill_container: true
        secondary_info: none
        tap_action:
          action: navigate
          navigation_path: /lovelace-lights/dashboard
      - type: custom:mushroom-entity-card
        icon: mdi:lightbulb-group-off-outline
        entity: button.press_104_sitting_room_switch_light
        layout: vertical
        secondary_info: none
        tap_action:
          action: call-service
          service: light.turn_off
          target:
            entity_id: light.103_office_biodynamic_light
        primary_info: none
        icon_color: black
  - type: custom:mushroom-cover-card
    entity: cover.all
    fill_container: true
    layout: vertical
    secondary_info: none
    name: Stínění
    show_buttons_control: true
    tap_action:
      action: navigate
      navigation_path: /lovelace-shades/dashboard
  - type: custom:vertical-stack-in-card
    cards:
      - type: custom:mushroom-fan-card
        entity: fan.pichler
        fill_container: true
        layout: vertical
        secondary_info: none
        icon_animation: true
        name: Větrání
        tap_action:
          action: navigate
          navigation_path: /lovelace-ventilation/dashboard
      - type: custom:mushroom-entity-card
        entity: select.pichler_mode
        icon_color: black
        secondary_info: none
        primary_info: none
        layout: horizontal
  - type: custom:mushroom-lock-card
    fill_container: true
    secondary_info: none
    layout: vertical
    name: Zámky
    hold_action:
      action: navigate
      navigation_path: /lovelace-security/dashboard
    entity: lock.locks

Describe the solution you'd like
Custom card
      - type: custom:mushroom-button
        icon: mdi:lightbulb-group-off-outline
        tap_action:
          action: call-service
          service: light.turn_off
          target:
            entity_id: light.all
        icon_color: black

Describe alternatives you've considered
No response
Additional context
No response

Seems related to:

https://github.com/piitaya/lovelace-mushroom/issues/1286
https://github.com/piitaya/lovelace-mushroom/issues/887


shadow: fix crash when shadow cluster does not exist

This can happen when shadowing is used with RDS and CDS.
Fixes https://github.com/envoyproxy/envoy/issues/4504
Risk Level: Low
Testing: New UT
Docs Changes: N/A
Release Notes: N/A

@junr03 @ggreenway I added a debug log. PTAL.


The dev server is not running on port 3000.

Hello.
I did all steps but when I try to run npm start I get error:
PS C:\NodeJS\My Office Add-in> npm start
><EMAIL_ADDRESS>start C:\NodeJS\My Office Add-in
> office-addin-debugging start manifest.xml
Debugging is being started...
App type: desktop
Enabled debugging for add-in 05c2e1c9-3e1d-406e-9a91-e9ac64854143. Debug method: 0
Starting the dev server... (webpack-dev-server --mode development)
Unable to start the dev server. Error: The dev server is not running on port 3000.
Debugging started.
OS: Windows 8.1

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

ID: 15be7148-d1e8-b58b-b026-9f072efb638a
Version Independent ID: 53a5d00c-d82b-6536-2e80-3e2a3452879a
Content: Build your first Outlook add-in - Outlook Developer
Content Source: docs/add-ins/quick-start.md
Product: outlook
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

I've deleted old project and created a new without spaces in its name and now it works.


Improving signal examples

Documentation on signals needs improvements

https://docs.wagtail.io/en/latest/reference/signals.html#page-published
Details

I would like to see clear example about how to do test. The current example have multiple issues:

Example is using an external service that it requires API access from an external provider account and setup to work
It doesn't specify where code should be inserted

This is a reference section. It is about technical details, not a tutorial or how-to. The introduction to signals and the example should go into a separate how-to listen to signals page.
Signals are a Django concept. We could add a link to the Django documentation to learn about the basics.


[nrf noup] Make sdk-connectedhomeip green again

Fetch cbor2 in bootstrap.sh
Edit nRF examples to be compatible with NCS main
Cherry-pick a change to fix cirque CI
Update Python modules on nRF Connect update to harden things in the future.
Signed-off-by: Damian Krolik<EMAIL_ADDRESS>

Please cherry-pick also this one: https://github.com/project-chip/connectedhomeip/commit/3ef748cf8ac11031becee1550536a43e1331de63, as in NCS update commit I introduced a bug that was fixed later on.

Please cherry-pick also this one: project-chip/connectedhomeip@3ef748c, as in NCS update commit I introduced a bug that was fixed later on.

Ok, I did and squashed with the previous commit.


Fix hostname resolution for proxied connections

Proxied connections resolve the hostname to an IP address while tunneling even when noResolveHostname option is set.
This behavior is unwanted in some scenarios, especially when a proxy does whitelisting based on hostnames.
This pr should fix this.

@bartosz822 I'm inclined to approve this, but first...

Should we differentiate between proxied and isNoResolveHostnames.
Can you provide a small code snippet / output that shows the difference from different input?
How does this work with discovered servers, which usually come in the form of an ip address? Probably no effect, but I just want to think about it.

@bartosz822 Just waiting for another pair of eyes on this.

@bartosz822 I'm closing this, it's redundant.
NatsConnection line 194 calls resolveHost (NatsConnection, line 1759)
NatsConnection, line 1762 checks for an ip address
NatsConnection, line 1763 is serverPool.resolveHostToIps (NatsServerPool, line 188)
NatsServerPool resolveHostToIps checks the flag isNoResolveHostnames

@scottf I've seen the code you've mentioned and this pull request is not redundant, could you please reopen it? I've observed in proxy logs using this library that the  connection was made using the IP address even though isNoResolveHostnames flag was set. The NatsConnection that is passed to the connect method is indeed unresolved, but the constructor of InetSocketAddress does the resolution under the hood, look at the code from java.net:
public InetSocketAddress(String hostname, int port) {
        checkHost(hostname);
        InetAddress addr = null;
        String host = null;
        try {
            addr = InetAddress.getByName(hostname);
        } catch(UnknownHostException e) {
            host = hostname;
        }
        holder = new InetSocketAddressHolder(host, addr, checkPort(port));
    }```

Take also a look at the implementation of `java.net.Socket#connect(java.net.SocketAddress, int)`, it checks if the `SocketAddress` is resolved or not.

What was the input, meaning the servers specified in the options? You saw the stack trace. Also, if there is any resolving or checking to be done, it needs to be done before SocketDataPort.connect. I suppose it's possible that the SocketDataPort may need to be changed to never resolve as it should take exactly what it was given

@scottf I haven't received any new feedback on this PR since quite a while. Is it ok? Is there something else that needs to be done?

Hi, I was curious how we're doing on this MR? The reason that I'm asking is that we currently have to maintain some firewall rules using IP addresses over domain names which the colleagues from security don't like much.

Hi, I was curious how we're doing on this MR? The reason that I'm asking is that we currently have to maintain some firewall rules using IP addresses over domain names which the colleagues from security don't like much.

It's been quite a while since I reviewed this but I remember it was incomplete. Resolve hostnames is on by default, but you can turn it off in options via the options builder by calling noResolveHostnames()

Looking at the description it seems that the noResolveHostnames doesn't work for proxied connections. We observe the same still or was this fixed in another MR and I just missed it?

@GrafBlutwurst I think the problem is legitimate, just not the fix in this PR. Also, why are you proxying connections?

@GrafBlutwurst I really wanted to close this but the user insisted I was not understanding the problem. Which may be true. Is it possible that you can open a fresh defect issue in the repo and we can try to start this process over? I'm certain, I was not happy with the proposed code change, but frankly it's been a while and I can't remember why.

@scottf Here's the defect issue. https://github.com/nats-io/nats.java/issues/967
Let me know if I can help in any way. Looking at the code it's also how I would have solved the issue I think :/ , but maybe you have a better idea.

@scottf Here's the defect issue. #967
Let me know if I can help in any way. Looking at the code it's also how I would have solved the issue I think :/ , but maybe you have a better idea.

If I remember correctly, by the time it got to that point, it should have already been resolved. So it needs to be traced back and determined where it should happen.

I think the point here is that in a proxied case with firewalls we never want the hostname to be resolved to an IP on the client. Connections should always be established by hostname so that we don't need 2 firewall rules.
In particular the constructor call new InetSocketAddress(host, port) does resolution underneath thus on the firewall this connection attempt is by IP. Thus necessitating the use of InetSocketAddress.createUnresolved(host, port).
At least that was my understanding when looking at the code and would address our issue with hostname resolution.

@GrafBlutwurst Is this still an issue? Recent versions of the client support proxies much better, addressing the fact that the client to proxy is secure, but commonly proxy to server is insecure. Also there is the Options.noResolveHostnames option.
To setup the client for proxy, see this: https://github.com/nats-io/nats.java?tab=readme-ov-file#reverse-proxy


Update README.md

I update README.MD file, whenever you marge anyone's pull request it will automatically update.

Hello @Darkrider0007
Thanks for your contribution.
Let's connect ->
GitHub -> @Suryansh1720001 (Follow)
LinkedIn -> https://www.linkedin.com/in/suryanshprajapati17


Unexpectedly long results for search

Upon searching 'opamp', I get the following results, with a lot of warnings from unrelated parts.
What is this due to?
Can someone replicate this issue?
Also, it takes a lot of time to execute the search.

python
Python 2.7.12 (default, Nov 12 2018, 14:36:49)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import skidl
from skidl import *
search('opamp')
WARNING: Could not open directory ''
WARNING: Non-identical pins with the same number (6) in symbol drawing BAT54ADW
WARNING: Non-identical pins with the same number (3) in symbol drawing BAT54ADW
WARNING: Non-identical pins with the same number (3) in symbol drawing BAV99
WARNING: Non-identical pins with the same number (6) in symbol drawing Rohm_UMP11N
WARNING: Non-identical pins with the same number (3) in symbol drawing Rohm_UMP11N
WARNING: Non-identical pins with the same number (2) in symbol drawing Rohm_UMN1N
WARNING: Non-identical pins with the same number (2) in symbol drawing Rohm_UMN1N
WARNING: Non-identical pins with the same number (2) in symbol drawing Rohm_UMN1N
WARNING: Non-identical pins with the same number (4) in symbol drawing MC3486N
WARNING: Non-identical pins with the same number (8) in symbol drawing MC3486N
WARNING: Non-identical pins with the same number (16) in symbol drawing MC3486N
WARNING: Non-identical pins with the same number (8) in symbol drawing MC3486N
WARNING: Non-identical pins with the same number (16) in symbol drawing MC3486N
WARNING: Non-identical pins with the same number (8) in symbol drawing MC3486N
WARNING: Non-identical pins with the same number (12) in symbol drawing MC3486N
WARNING: Non-identical pins with the same number (16) in symbol drawing MC3486N
WARNING: Non-identical pins with the same number (4) in symbol drawing MC3487DX
WARNING: Non-identical pins with the same number (8) in symbol drawing MC3487DX
WARNING: Non-identical pins with the same number (16) in symbol drawing MC3487DX
WARNING: Non-identical pins with the same number (8) in symbol drawing MC3487DX
WARNING: Non-identical pins with the same number (16) in symbol drawing MC3487DX
WARNING: Non-identical pins with the same number (8) in symbol drawing MC3487DX
WARNING: Non-identical pins with the same number (12) in symbol drawing MC3487DX
WARNING: Non-identical pins with the same number (16) in symbol drawing MC3487DX
WARNING: Non-identical pins with the same number (4) in symbol drawing MC3487N
WARNING: Non-identical pins with the same number (8) in symbol drawing MC3487N
WARNING: Non-identical pins with the same number (16) in symbol drawing MC3487N
WARNING: Non-identical pins with the same number (8) in symbol drawing MC3487N
WARNING: Non-identical pins with the same number (16) in symbol drawing MC3487N
WARNING: Non-identical pins with the same number (8) in symbol drawing MC3487N
WARNING: Non-identical pins with the same number (12) in symbol drawing MC3487N
WARNING: Non-identical pins with the same number (16) in symbol drawing MC3487N
WARNING: Non-identical pins with the same number (1) in symbol drawing UA9637
WARNING: Non-identical pins with the same number (4) in symbol drawing UA9637
WARNING: Non-identical pins with the same number (1) in symbol drawing UA9638CD
WARNING: Non-identical pins with the same number (4) in symbol drawing UA9638CD
WARNING: Non-identical pins with the same number (1) in symbol drawing UA9638CP
WARNING: Non-identical pins with the same number (4) in symbol drawing UA9638CP
WARNING: Non-identical pins with the same number (AG19) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AH23) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AJ20) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AJ22) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AJ34) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AK13) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AK14) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AK23) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AK35) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AL22) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AM14) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AM22) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AN23) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AP20) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AP22) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AR23) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AM33) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AM34) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AM36) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AN31) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AN32) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AN34) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AN35) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AN36) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AP30) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AP32) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AP33) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AP35) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AP36) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AR30) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AR31) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AR33) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AR34) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AR36) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AT30) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AT31) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AT32) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AT33) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AT34) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AT35) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (AK34) in symbol drawing P4080-BGA1295
WARNING: Non-identical pins with the same number (29) in symbol drawing PIC16F871-IPT
WARNING: Non-identical pins with the same number (1) in symbol drawing 74LVC2G53
WARNING: Non-identical pins with the same number (2) in symbol drawing 74LVC2G53
WARNING: Non-identical pins with the same number (5) in symbol drawing 74LVC2G53
WARNING: Non-identical pins with the same number (6) in symbol drawing 74LVC2G53
WARNING: Non-identical pins with the same number (7) in symbol drawing 74LVC2G53
WARNING: Non-identical pins with the same number (1) in symbol drawing 74LVC1G3157
WARNING: Non-identical pins with the same number (2) in symbol drawing 74LVC1G3157
WARNING: Non-identical pins with the same number (5) in symbol drawing 74LVC1G3157
WARNING: Non-identical pins with the same number (6) in symbol drawing 74LVC1G3157
Searching Analog_Switch.lib ..WARNING: Non-identical pins with the same number (1) in symbol drawing IRF6802SD
WARNING: Non-identical pins with the same number (1) in symbol drawing 74LS78
WARNING: Non-identical pins with the same number (5) in symbol drawing 74LS78
WARNING: Non-identical pins with the same number (7) in symbol drawing EABC80
Amplifier_Audio.lib: OPA1622 (High-Fidelity, Bipolar-Input, Audio Operational Amplifier, VSON-10)
Amplifier_Audio.lib: LM386 (Low Voltage Audio Power Amplifier, DIP-8/SOIC-8/SSOP-8)
Amplifier_Difference.lib: LM733CH (Single Differential Amplifier, TO-5-10)
Amplifier_Difference.lib: LM733CN (Single Differential Amplifier, DIP-14)
Amplifier_Instrumentation.lib: INA327 (Precision, Rail-to-Rail I/O Instrumentation Amplifier, MSOP-10 package)
Amplifier_Instrumentation.lib: INA128 (Precision, Low Power Instrumentation Amplifier G = 1 + 49.4kOhm/Rg, DIP-8/SOIC-8)
Amplifier_Instrumentation.lib: INA326 (Precision, Rail-to-Rail I/O Instrumentation Amplifier, MSOP-8 package)
Amplifier_Operational.lib: AD8603 (Zero-Drift, Precision, Low-Noise, Rail-to-Rail Output, 36-V Operational Amplifier, TSOT-23-5)
Amplifier_Operational.lib: NE5534 (Single Low-Noise Operational Amplifiers, DIP-8/SOIC-8)
Amplifier_Operational.lib: OP179GS (Single Rail-to-Rail High Output Current Operational Amplifiers, SOIC-8)
Amplifier_Operational.lib: CA3130 (4.5MHz, BiMOS Operational Amplifier with MOSFET Input/Bipolar Output, DIP-8/SOIC-8)
Amplifier_Operational.lib: THS4631DDA (Single High-voltage, High Slew Rate, Wideband, FET-input Operational Amplifier, MSOP-8)
Amplifier_Operational.lib: LMV321 (Single Low-Noise, Low Quiescent Current, Precision Operational Amplifier e-trim Series, SC-70-5)
Amplifier_Operational.lib: ADA4530-1 (Femtoampere Input Bias Current Electrometer Amplifier, SOIC-8)
Amplifier_Operational.lib: MCP603-xCH (Single 2.7V to 6.0V Single Supply CMOS Op Amps, with Chip Select, SOT-23-6)
Amplifier_Operational.lib: MCP601-xP (Rail-to-Rail Input/Output Operational Amplifier, PDIP-8)
Amplifier_Operational.lib: LTC6082xDHC (Precision Quad CMOS Rail-to-Rail Input/Output Amplifiers, DFN-16)
Amplifier_Operational.lib: LTC6362xMS8 (Precision, Low Power, Rail-to-Rail Input/Output, Differential Op Amp/SAR ADC Driver, DFN-8)
Amplifier_Operational.lib: L272M (Dual Power Operation Amplifier, DIP-8)
Amplifier_Operational.lib: MAX4238AUT (Ultra-Low Offset/Drift, Low-Noise, Precision Amplifiers, SOT-23-6)
Amplifier_Operational.lib: LM321 (Low Power Single Operational Amplifier, SOT-23-5)
Amplifier_Operational.lib: LTC6082xGN (Quad Single-Supply, Rail-to-Rail Operational Amplifier, MicroAmplifier Series, SSOP-16)
Amplifier_Operational.lib: NCS325 (Single operational amplifier, 50uV Offset, 0.25uV/C, 35uA Zero-Drift, SOT-23-5)
Amplifier_Operational.lib: LTC6081xDD (Precision Dual CMOS Rail-to-Rail Input/Output Amplifiers, DFN-10)
Amplifier_Operational.lib: LM4250 (Programmable Operational Amplifier, DIP-8/SOIC-8)
Amplifier_Operational.lib: LMH6551MM (Differential, High-Speed, Op Amp, VSSOP-8)
Amplifier_Operational.lib: OPA2333xxDRB (Dual 1.8V, microPower, CMOS Operational Amplifiers, Zero-Drift Series, SON-8)
Amplifier_Operational.lib: TSV912IQ2T (Dual rail-to-rail input/output 8 MHz operational amplifiers, DFN-8)
Amplifier_Operational.lib: LM318M (Operational Amplifier, DIP-8)
Amplifier_Operational.lib: OPA2695xD (Dual, Ultra-Wideband, Current-Feedback Operational Amplifier with Disable, SOIC-8)
Amplifier_Operational.lib: THS3491xDDA (900-MHz, 500-mA High-Power Output Current Feedback Operational Amplifier, SOIC-8)
Amplifier_Operational.lib: LMV601 (1MHz, Low-Power, General-Purpose, 2.7V Operational Amplifiers, SC-70-6)
Amplifier_Operational.lib: LTC1152 (Rail-to-Rail Input, Rail-to-Rail Output, Zero-Drift Op Amp, DIP-8, SOIC-8)
Amplifier_Operational.lib: OP279 (Dual Rail-to-Rail High Output Current Operational Amplifiers, SOIC-8/TSSOP-8)
Amplifier_Operational.lib: NCS2325D (Dual operational amplifier, 50uV Offset, 0.25uV/C, 35uA Zero-Drift, SOIC-8)
Amplifier_Operational.lib: OPA890xD (Single Low-Power, Wideband, Voltage-Feedback Operational Amplifier with Disable, SO-8)
Amplifier_Operational.lib: LTC1151CN8 (Dual Â±15V, Zero-Drift, Operational Amplifier, DIP-8)
Amplifier_Operational.lib: OPA2691-14 (Dual Wideband, Current-Feedback Operational Amplifier With Disable, SOIC-14)
Amplifier_Operational.lib: TSV524xIQ4T (Quad CMOS Rail-to-Rail Input/Output Amplifier, 1.15MHz GBP, QFN-16)
Amplifier_Operational.lib: ADA4898-2 (Dual High Voltage, Low Noise, Low Distortion, Unity-Gain Stable, High Speed Op Amp, SOIC-8-1EP)
Amplifier_Operational.lib: LMH6551MA (Differential, High-Speed, Op Amp, SOIC-8)
Amplifier_Operational.lib: OPA330xxYFF (50Î¼V V OS, 0.25Î¼V/Â°C, 35Î¼A CMOS OPERATIONAL AMPLIFIERS, ZerÃ¸-Drift Series, DSBGA)
Amplifier_Operational.lib: LM318J (Operational Amplifier, DIP-14)
Amplifier_Operational.lib: LTC1151CSW (Dual Â±15V, Zero-Drift, Operational Amplifier, SOIC-16W)
Amplifier_Operational.lib: ADA4898-1YRDZ (High Voltage, Low Noise, Low Distortion, Unity-Gain Stable, High Speed Op Amp, SOIC-8)
Amplifier_Operational.lib: MCP6L91RT-EMS (10 MHz, 850 ÂµA Op Amps, MSOP-8)
Amplifier_Operational.lib: MCP6002-xMC (1MHz, Low-Power Op Amp, DFN-8)
Amplifier_Operational.lib: LM741 (Single JFET-Input Operational Amplifiers, DIP-8/SOIC-8)
Amplifier_Operational.lib: OP179GRT (Single Rail-to-Rail High Output Current Operational Amplifiers, SOT-23-5)
Amplifier_Operational.lib: OPA355NA (200MHz, CMOS, Operational amplifier, with shutdown, SOT-23-6)
Amplifier_Operational.lib: OP249GS (Precision JFET, High Speed, Dual Operational Amplifier, SOIC-8)
Amplifier_Operational.lib: L272 (Dual Power Operation Amplifier, DIP-16)
Amplifier_Operational.lib: OPA2376xxYZD (Dual Low-Noise, Low Quiescent Current, Precision Operational Amplifier e-trim Series, DSBGA-8)
Amplifier_Operational.lib: LMH6611 (Single Supply, 345 MHz, Rail-to-Rail Output, Amplifier, TSOT-23-6)
Amplifier_Operational.lib: MCP6L91RT-EOT (Single rail-to-rail input/output 8 MHz operational amplifiers, SOT-23-5)
Amplifier_Operational.lib: NCS4325 (Quad operational amplifier, 50uV Offset, 0.25uV/C, 35uA Zero-Drift, SOIC-14)
Amplifier_Operational.lib: LM2904 (Dual rail-to-rail input/output 8 MHz operational amplifiers, MiniSO-8)
Amplifier_Operational.lib: OPA1641 (JFET input, ultralow distortion, low-noise operational amplifier, SOIC-8/VSSOP-8)
Amplifier_Operational.lib: OP07 (Single SoundPlus High Performance Audio Operational Amplifiers, DIP-8/SOIC-8)
Amplifier_Operational.lib: ADA4841-1YRJ (Low Power, Low Noise and Distorsion, Rail-to-Rail Output Amplifier, SOT-23-6)
Amplifier_Operational.lib: OPA890xDBV (Single Low-Power, Wideband, Voltage-Feedback Operational Amplifier with Disable, SOT-23-6)
Amplifier_Operational.lib: LM675 (Power Operational Amplifier, TO-220-5)
Amplifier_Operational.lib: NCS2325DM (Dual operational amplifier, 50uV Offset, 0.25uV/C, 35uA Zero-Drift, MSOP-8)
Amplifier_Operational.lib: OPA2325 (Precision, 10-MHz, Low-Noise, Low-Power, RRIO, CMOS Operational Amplifier, SOIC-8)
Amplifier_Operational.lib: MAX4238ASA (Ultra-Low Offset/Drift, Low-Noise, Precision Amplifiers, SOIC-8)
Amplifier_Operational.lib: OPA2695xRGT (Dual, Ultra-Wideband, Current-Feedback Operational Amplifier with Disable, QFN-16)
Amplifier_Operational.lib: ADA4807-2ACP (Dual Rail-to-Rail Input/Output Amplifiers, with disable, SC-70-6/SOT-23-6)
Amplifier_Operational.lib: ADA4870ARRZ (High Speed, High Voltage, 1A Output Drive Amplifier, PSOP-20)
Amplifier_Operational.lib: LM6361 (Single High Speed Operational Amplifier, DIP-8/SOIC-8)
Amplifier_Operational.lib: MCP601-xST (Single 2.7V to 6.0V Single Supply CMOS Op Amps, TSSOP-8)
Amplifier_Operational.lib: LM2902 (Quad Rail-to-rail, 20 MHz GBP, operational amplifiers, SOIC-14/TSSOP-14)
Amplifier_Operational.lib: MCP6L91T-EOT (Single rail-to-rail input/output 8 MHz operational amplifiers, SOT-23-5)
Amplifier_Operational.lib: ADA4807-1 (Single Rail-to-Rail Input/Output Amplifiers, with disable, SC-70-6/SOT-23-6)
Amplifier_Operational.lib: MCP603-xP (Single 2.7V to 6.0V Single Supply CMOS Op Amps, with Chip Select, TSSOP-8)
Amplifier_Operational.lib: OPA333xxD (Single rail-to-rail input/output 8 MHz operational amplifiers, SOIC-8)
Amplifier_Operational.lib: L272D (Dual Power Operation Amplifier, SOIC-16)
Amplifier_Operational.lib: LTC6362xDD (Precision, Low Power, Rail-to-Rail Input/Output, Differential Op Amp/SAR ADC Driver, DFN-8)
Amplifier_Video.lib: AD813 (Single Supply, Low Power, Triple Video Amplifier, DIP-14/SOIC-14)
Device.lib: Opamp_Dual_Generic (Dual operational amplifier)
Device.lib: Opamp_Quad_Generic (Quad operational amplifier)
Power_Management.lib: TSM103W (Dual Operational Amplifier and 2.5V 0.4% Voltage Reference, SOIC-8)
Power_Management.lib: TSM102 (Dual Operational Amplifier and Dual Comparator and 0.4% Voltage Reference, SOIC-16)
Simulation_SPICE.lib: OPAMP (Operational amplifier, single, node sequence=1:+ 2:- 3:OUT 4:V+ 5:V-)
pspice.lib: OPAMP (OPAmp symbol for simulation only)

The warnings are about library symbols that have more than one pin with the same pin number. I'm not sure why some symbols are designed that way, but it seems like a mistake.
The initial invocation of search() is slow (takes over a minute on my PC) because it's scanning in all the libraries (mostly these large FPGA libs) looking for a match with your search string. Once that's done, any other searches are fast (and the warning messages no longer appear). The initial search might be made faster (it's on my to-do list).

I pushed a change that reduced my search() time from 108s to 21s. You can try it to see if it helps you.

OK, guess we're done here.


Detected package downgrade of System.Configuration.ConfigurationManager with version 6.7.0

After update to version 6.7.0 I'm having this problem:
error NU1605:
      Warning As Error: Detected package downgrade: System.Configuration.ConfigurationManager from 8.0.0 to 6.0.1. Reference the package directly from the project to select a different version.
       My.Project -> Serilog.Sinks.MSSqlServer 6.7.0 -> Microsoft.Data.SqlClient 5.2.1 -> System.Configuration.ConfigurationManager (>= 8.0.0)
       My.Project -> Serilog.Sinks.MSSqlServer 6.7.0 -> System.Configuration.ConfigurationManager (>= 6.0.1)

This is caused by the fact that version 5.2.1 of Microsoft.Data.SqlClient uses at least version 8.0.0 of System.Configuration.ConfigurationManager when compiled with the .NET 8 target framework while the Serilog.Sinks.MSSqlServer package continues to use an older mejor version.
Serilog packages used in the project:

Serilog.AspNetCore: 8.0.2
Serilog.Settings.Configuration: 8.0.2
Serilog.Sinks.MSSqlServer: 6.7.0

Target framework and operating system:

.NET 8
OS: Microsoft Windows 11 Pro - Version 10.0.22631 Build 22631

Same problem here.
To solve it, i installed the package Microsoft.Data.SqlClient 5.2.1 Explicitly from nuget, then installed Serilog.Sinks.MSSqlServer package.

me too

me too

Downgraded SqlClient to 5.1.6 and created a dev release with the changes. This should fix the described package downgrade issue.
https://www.nuget.org/packages/Serilog.Sinks.MSSqlServer/6.7.1-dev-00084
Please try it out and give us some feedback. Thanks a lot! :)

I'm having a similar problem with the latest update. Some of my packages use the System.Configuration.ConfigurationManager 7.0.0 transitive package and when I upgrade to version 6.7.0 the configuration loading stops because it requires System.Configuration.ConfigurationManager from 8.0.0. So for now I'm going to downgrade Sink and wait, maybe I'll be stuck with this version of Sink (6.6.1) for a while until all my dependencies update the ConfigurationManager. I don't feel comfortable manually updating Transitive packages, there are always risks.

@lucasNewSharp so you still see the package downgrade issue with the dev release 6.7.1-dev-00084 of the SQL sink, is that correct?

I tested today with a .NET 8 project and the sink code of 6.7.1-dev-00084 and the downgrade warning was gone. Will create a stable sink version 6.7.1 and close this issue.

Thank you! ☺


Converting rasm file to netCDF3 using xarray

This would help new users like https://github.com/pydata/xarray/issues/1113 and simplify the RTD build process (https://github.com/pydata/xarray/issues/1106).
The problem is that it is not as trivial as expected. On the latest master:
import xarray as xr
ds = xr.tutorial.load_dataset('rasm')
ds.to_netcdf('rasm.nc', format='NETCDF3_CLASSIC', engine='scipy')

Throws an error:
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
/home/mowglie/Documents/git/xarray/xarray/backends/api.py in to_netcdf(dataset, path, mode, format, group, engine, writer, encoding)
    516     try:
--> 517         dataset.dump_to_store(store, sync=sync, encoding=encoding)
    518         if isinstance(path, BytesIO):

/home/mowglie/Documents/git/xarray/xarray/core/dataset.py in dump_to_store(self, store, encoder, sync, encoding)
    754         if sync:
--> 755             store.sync()
    756

/home/mowglie/Documents/git/xarray/xarray/backends/scipy_.py in sync(self)
    149         super(ScipyDataStore, self).sync()
--> 150         self.ds.flush()
    151

/home/mowglie/.pyvirtualenvs/py3/lib/python3.4/site-packages/scipy/io/netcdf.py in flush(self)
    388         if hasattr(self, 'mode') and self.mode in 'wa':
--> 389             self._write()
    390     sync = flush

/home/mowglie/.pyvirtualenvs/py3/lib/python3.4/site-packages/scipy/io/netcdf.py in _write(self)
    400         self._write_gatt_array()
--> 401         self._write_var_array()
    402

/home/mowglie/.pyvirtualenvs/py3/lib/python3.4/site-packages/scipy/io/netcdf.py in _write_var_array(self)
    448             for name in variables:
--> 449                 self._write_var_metadata(name)
    450             # Now that we have the metadata, we know the vsize of

/home/mowglie/.pyvirtualenvs/py3/lib/python3.4/site-packages/scipy/io/netcdf.py in _write_var_metadata(self, name)
    466         for dimname in var.dimensions:
--> 467             dimid = self._dims.index(dimname)
    468             self._pack_int(dimid)

ValueError: '2' is not in list

Should we try to get to the source of this, or should I simply use ncks to do the conversion?

Can you write it as netcdf3 using engine="netcdf4"? This might be a scipy bug.

Yes, it works. But opening it with scipy throws a new error (to xarray's defense, the file I created with ncks also can't be opened with scipy- but it can with ncview).
I think all this gets way to complicated for a Sunday evening and a simple demo file ;-)

I also think this is a scipy bug. After converting the file to netCDF3 CLASSIC mode, I get an error in the scipy backend...
$ ncks -3 rasm.nc rasm.nc

$ ncdump -k rasm.nc
classic
$ ncdump -h rasm.nc
netcdf rasm {
dimensions:
	time = 36 ;
	y = 205 ;
	x = 275 ;
variables:
	double Tair(time, y, x) ;
		Tair:_FillValue = 9.96920996838687e+36 ;
		Tair:units = "C" ;
		Tair:long_name = "Surface air temperature" ;
		Tair:dimensions = "2" ;
		Tair:type_preferred = "double" ;
		Tair:time_rep = "instantaneous" ;
		Tair:coordinates = "yc xc" ;
	double time(time) ;
		time:dimensions = "1" ;
		time:long_name = "time" ;
		time:type_preferred = "int" ;
		time:units = "days since 0001-01-01" ;
		time:calendar = "noleap" ;
	double xc(y, x) ;
		xc:long_name = "longitude of grid cell center" ;
		xc:units = "degrees_east" ;
		xc:bounds = "xv" ;
	double yc(y, x) ;
		yc:long_name = "latitude of grid cell center" ;
		yc:units = "degrees_north" ;
		yc:bounds = "yv" ;

// global attributes:
		:title = "/workspace/jhamman/processed/R1002RBRxaaa01a/lnd/temp/R1002RBRxaaa01a.vic.ha.1979-09-01.nc" ;
		:institution = "U.W." ;
		:source = "RACM R1002RBRxaaa01a" ;
		:output_frequency = "daily" ;
		:output_mode = "averaged" ;
		:convention = "CF-1.4" ;
		:references = "Based on the initial model of Liang et al., 1994, JGR, 99, 14,415- 14,429." ;
		:comment = "Output from the Variable Infiltration Capacity (VIC) model." ;
		:nco_openmp_thread_number = 1 ;
		:NCO = "\"4.6.0\"" ;
		:history = "Tue Dec 27 13:38:40 2016: ncks -3 rasm.nc rasm.nc\n",
			"history deleted for brevity" ;
}```

```Python

In [1]: from scipy.io import netcdf
   ...: f = netcdf.netcdf_file('rasm.nc', 'r')
   ...: for k, v in f.variables.items():
   ...:     print(k, v.dimensions)
   ...:
yc ('y', 'x')
xc ('y', 'x')
time b'1'
Tair b'2'

In [2]: import xarray as xr
   ...: xr.open_dataset('rasm.nc', engine='netcdf4')
<xarray.Dataset>
Dimensions:  (time: 36, x: 275, y: 205)
Coordinates:
  * time     (time) datetime64[ns] 1980-09-16T12:00:00 1980-10-17 ...
    xc       (y, x) float64 189.2 189.4 189.6 189.7 189.9 190.1 190.2 190.4 ...
    yc       (y, x) float64 16.53 16.78 17.02 17.27 17.51 17.76 18.0 18.25 ...
  * y        (y) int64 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ...
  * x        (x) int64 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ...

I don't know where scipy is getting the b'1' and b'2' dimensions. I can push the converted dataset to xarray-data but that doesn't really solve the problem of using scipy.

It looks like scipy gets confused between the the dimensions = '1' netCDF attribute and the variable's actual dimensions, so this is another scipy bug. When it sets the dimensions netCDF attribute, it overwrites the Python attribute of the same name:  https://github.com/scipy/scipy/blob/c48dfa43eae3474f06353ed3664caed945e9aee1/scipy/io/netcdf.py#L837-L849
The simple work around is to remove the dimensions attribute from each of these variables.

I see. I should have looked at the attributes.  https://github.com/pydata/xarray-data/issues/7 fixes these issue and the dataset can now be read with scipy.


Fix follow company logic when there is no button available for it in …

…the popup
The program was crashing when the element was not found in the page.
followCompany = self.driver.find_element(By.CSS_SELECTOR,"label[for='follow-company-checkbox']")
Just created a try/except using the already imported NoSuchElementException.

@tudopropaganda use self.exists(...) instead of try/catch.
And the Follow button does exist on the form. So to accept a change, I would need to see the exception (just copy/paste it) and you should find if the follow checkbox is updated on the last page of submitting the easyapply form.


 I've confirmed that the build succeeds with the following command:
$ git show -q
commit 67f8b5c379844a5862c198f611e18f6496225475 (HEAD -> go1.18, origin/go1.18)
Author: Kazuki Suda<EMAIL_ADDRESS>Date:   Thu Apr 7 23:33:55 2022 +0900

    Use Go 1.18

$ go build -o bin/alertmanager-to-github .
$ bin/alertmanager-to-github -h
NAME:
   bin/alertmanager-to-github - Webhook receiver Alertmanager to create GitHub issues

USAGE:
   alertmanager-to-github [global options] command [command options] [arguments...]

COMMANDS:
   start          Start webhook HTTP server
   test-template  Test rendering a template
   help, h        Shows a list of commands or help for one command

GLOBAL OPTIONS:
   --help, -h  show help (default: false)

I've fixed it at https://github.com/pfnet-research/alertmanager-to-github/pull/4/commits/de37846632f627e4b5b4406b42afe68545e58f52.


Add new example

A new example solved using SAT solver

just to be sure you replace OptimizationExpert by your "name?" is it ok for you ?


merge from arlac77/template-arlac77-github,arlac77/template-esm-only

package.json

merge from template package.json

README.md

docs(README): update from template

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add minnsing prefetech on products webhooks in 3.0

I want to merge this change because coping changes from #8811 to 3.0.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-5135 Missing prefetch in products webhooks.


Antialiasing stopped working on Insiders

VSCode Version: 1.32.0-insider
OS Version: macOS 10.13.6

Steps to Reproduce:

Open up VS Code and the font is not antialiased.
Flip through the options in the settings and it never changes the aliasing.

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

https://github.com/Microsoft/vscode/commit/1b908ce4ece05277191900bf567bcfb357d08064#diff-d3e0527fc1661d3ca1a624b2e58f62f2L44
The anti-aliasing classes are added to the same element as the monaco-workbench class and not nested underneath. I reckon the selectors should be along the lines of .monaco-workbench.monaco-font-aliasing-###.

We are building exploration builds that use a much newer version of our UI framework (Electron version 6.0.x). I wonder if this issue reproduces with one of these builds, could you try? Download:

macOS: Download
Linux (DEB): Download
Linux (RPM): Download
Windows: Download

Tried the exploration build and the issue did not reproduce for me on macOS 10.14.6.

Version: 1.37.0-exploration
Commit: 960208fdf9aa06e6892aa14c9c84ddd607fbeb2f
Date: 2019-07-31T06:56:38.567Z
Electron: 6.0.0
Chrome: 76.0.3809.88
Node.js: 12.4.0
V8: 7.6.303.27-electron.0
OS: Darwin x64 18.7.0


Introduce Pulse IR skeleton

Summary
This PR continues the work on the new Pulse Compiler and IR (RFC) by introducing a skeleton for the IR representation.
Details and comments
The implementation follows the form first presented in #11234. Only basic functionalities were introduced at this point, because #11726 is still pending, and the work on the compiler (following #11743) will better reveal what functionality is missing.

Thanks @nkanazawa1989 for the quick review.
As we discussed offline, we both think it's reasonable to continue with the list representation of the elements for now. Conversion to DAG is not trivial, and might require an extra conversion step (ScheduleBlock->IR1->IR2?).
With the exception of shift_initial_time, I removed all methods which are arguably a pass. I think shift_initial_time is something we'll need to do often, and should live in the IR level.
About initial_time, I don't think O(N) is terrible here. But if we don't go in the DAG direction, we can later optimize this - Tracking initial time instead of calculating it? (will require initial_time setting to go through the block). Using the list structure to only examine some of the elements?


Package request: paperlib

Project description
An open-source academic paper management tool.
Metadata

homepage URL: https://paperlib.app/en/
source URL: https://github.com/Future-Scholars/paperlib
license: GPL-3.0 license
platforms: unix, linux, darwin

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

I created a PR https://github.com/NixOS/nixpkgs/pull/323958 based on this packaging request.


GH-38865 [C++][Parquet] support passing a RowRange to RecordBatchReader

!!! this PR is based on arrow-13 for early review
Rationale for this change
see https://github.com/apache/arrow/issues/38865
What changes are included in this PR?
add a parameter in GetRecordBatchReader to accept row_ranges.
The row ranges can be used to:

skip decompressing and decoding unnecessary pages. This part is done by leveraging an existing hook called DataPageFilter
Now only necessary pages are remaining. In Parquet, row number is not aligned across different columns' pages, so the remaining rows for different columns are different. We introduced a new class called RecordSkipper to i. coordinate all Column Readers' progress so that they can still resemble row records correctly ii. skip unnecessary rows in necessary pages

Are these changes tested?
a new test file callled range_reader_test.cc is added
Are there any user-facing changes?
a new GetRecordBatchReader API overload is added. NO existing API is broken

Closes: #38865

!!! this PR is based on arrow-13 for early review

Generally there isn't much benefit to targeting a PR at a maintenance branch,  could you retarget to main/master

hi @emkornfield , thanks for your thorough review. Looks like I should have provided some background to reviewers:

We're working on native parquet reading in Clickhouse, which maintains a arrow-13 fork. That's why this PR draft is based on arrow-13.
It's my first time to contribute to Arrow, so I'm consulting  @wgtmac and @mapleFU offline to check whether this PR is needed by Arrow community and how to revise the PR to meet community standard.
@wgtmac has quickly summarized a detailed design doc at https://docs.google.com/document/d/1SeVcYudu6uD9rb9zRAnlLGgdauutaNZlAaS0gVzjkgM. When the design doc has reached consensus, I'll come back to this PR and address all the review comments.

Looking forward to contributing.
Thanks!

I think it might be worth having more discussion on the issue with representation of RowRanges and on the newly exposed API on the issue to make sure we come to a consensus

The latest version follows the design in https://docs.google.com/document/d/1SeVcYudu6uD9rb9zRAnlLGgdauutaNZlAaS0gVzjkgM/edit

hi @emkornfield , I've just pushed my refinements to this PR and will go through a review with @wgtmac . It may save you your time if you wait until @wgtmac has approved it


filter by value analysis: show boolean fields in dropdown menu

re: #11546 (pointing to previous work by @nobuti)

boolean columns now appear in the column selector
added the missing tests for filter-form-model

I intentionally left out of the scope some issues I detected during the development of the feature, that will be tackled as part of the milestone https://github.com/CartoDB/cartodb/milestone/142

Tests are failing @matallo, any clue?

thanks for jumping in @nobuti tests seem to pass now 😘

spotted the root of the problem here, rather than making the test more relaxed
CDB.SQL.prototype.execute was being overdriven by some other test (that one in the commit) thus that instance was being triggered rather the original one
this was happening passing all the tests, but not filtering the specs
whenever you see an strange trace with sql query executed as part of tests failing this would probably be the culprit, in my case it was the use of CDB.SQL in https://github.com/CartoDB/cartodb/blob/master/lib/assets/core/javascripts/cartodb3/editor/layers/layer-content-views/analyses/column-data.js#L13
moreover this was only happening in the terminal, but not in the browser, lovely
thanks @ivanmalagon for your 🕵 skills
/cc @nobuti @xavijam

thanks for the review @xavijam applied the suggested changes 👍

What about merging this one into @nobuti's one (https://github.com/CartoDB/cartodb/pull/12158) and keep going from there?

Oh @matallo, there is a problem with the travis tests. Could you check it please?

@xavijam merging, changes made and fixed the tests


How to enable Server Side includes in Azure WebApp?

Have a static website and using Server Side Includes. Deployed to webapp and did not work.
In one of the blogs mentioned that i should add a web.config with below values
<?xml version="1.0" encoding="UTF-8"?> <configuration> 	<system.webServer> 		<handlers> 			<add name="SSINC-htm" path="*.htm" verb="*" modules="ServerSideIncludeModule" resourceType="File" /> 		</handlers> 	</system.webServer> </configuration>
But didnt work.
Am i missing anything.

@jeevaeastpoint Hi, can you please share more details about the issue you have, and which document you are referring to? Thanks a lot!

@YutongTie-MSFT  I was referring to this https://azure.microsoft.com/en-gb/blog/server-side-includes-ssi-in-windows-azure-web-sites-waws/  but the website doesnt load at all. Not sure what is wrong. There is no other documentation about the server side includes available.

@YutongTie-MSFT We have a static website which uses some npm packages and gulp tasks. There no web.config defined for this project. The pages uses Server Side includes and I have tried deploying to Azure WebApp but no luck. During local development we have enabled SSI in the IIS webserver and i guess the Azure webapp uses IIS under the hood. My question is

Is SSI module is enabled by default?
If not how to enable it.
If it is already enabled, how to instruct the webserver to pick my index.shtml file. [Note that i have already set the default document to index.shtml]

@jeevaeastpoint Thanks for your clarification. @BryanTrach-MSFT will help you to solve it.

@BryanTrach-MSFT Any updates on this.

@jeevaeastpoint We would like to work closer with you on this matter. I was able to get SSI working in a sample app. Can you please reach out to us at<EMAIL_ADDRESS>with your subscription ID and the URL of this post? We look forward to your reply.
Since we will work with you offline, we will close out this thread.

If you end up on this closed GitHub issue like me due to your Server Side Includes not working in an Azure App service, make sure that your App Service is running in 64bit process mode. The module won't be running otherwise.

Followed the instructions on the provided blog source. Not working AT ALL. I'm unable to turn SSI on for a WebApp.


Invalid hex color: #NaNNaNNaN

Description
Hi. after entering my user id for the cloud assisted setup, the qr does not appear on my screen.
Please help!
Thank you!

Steps to reproduce
No response
Expected behaviour
No response
Additional context
No response
Confirmation

[X] I am sure this is a bug or improvement, that is well enough described that it can be implemented.

[ ] If this is for a specific device, the device config is mentioned above, or diagnostics are included.

[ ] Log messages or diagnostics relevant to the issue are included.

[X] This is not requesting addition of a new device.

I just confirmed that the QR code is still working in HA 2024.11.0, so it is not a change made in HA that this integration needs to adapt to.
Perhaps it is something else in your local installation causing this, such as a custom theme, in which case it needs to be reported there (or to HA if the theme author determines the problem to be in HA)


KAFKA-9034 Tolerate spaces in $JAVA_HOME

This allows kafka tools to work on Cygwin where $JAVA_HOME typically contains a space (e.g. "C:\Program Files\Java\jdkXXX")

```shell
JAVA_MAJOR_VERSION=$($JAVA -version 2>&1 | sed -E -n 's/.* version "([0-9]*).*$/\1/p')

There is another similar code in the kafka-run-class.sh. Should it be fixed also?

Good spot. Yes, it should be. I've updated, and tested it on Cygwin to confirm.
What is the process for getting this PR merged now?


Privatelink host in provider's block

Provider Version
0.66.1
Terraform Version
1.3.9
Describe the bug
Unable to authenticate using privatelink host "....privatelink.snowflakecomputing.com"
Expected behavior
Authenticate properly
Code
provider "snowflake" {
  account  = "${var.SNOWFLAKE_ORG}-${var.SNOWFLAKE_ACCOUNT}" # the Snowflake account identifier
  username = var.SNOWFLAKE_USERNAME                          # the Snowflake user name
  # Password defined with env variable SNOWFLAKE_PASSWORD
  role = "ACCOUNTADMIN"
  host = "app-${var.SNOWFLAKE_ORG}-${var.SNOWFLAKE_ACCOUNT}.privatelink.snowflakecomputing.com" # here
}

Additional context
I set up the Azure private link following the documentation: https://docs.snowflake.com/en/user-guide/privatelink-azure, everything is working properly since I'm able to access the UI with the privatelink host from a VM that is within the virtual network.
The problem is that I'd like to create a "network policy" on Snowflake using Terraform to restrict access to only the private IPs coming from the virtual network. But if I do then I can't use Terraform anymore since it is using the "public" host. Also, I'm using a pipeline running on VMSS instances hence the IPs are constantly changing so I can't whitelist my CI.
So I tried to use the privatelink host in the provider's block so the network policy won't block Terraform. But it's not working with the following error message. Is it even possible to use the privatelink host with the provider?
Thanks :)
Error message:
Error: could not retrieve session id err = 261004 (08004): failed to auth for unknown reason. HTTP: 405

@PLsergent I am wondering where Terraform is running, and if it is part of the virtual network that you have configured. I personally have not used the Azure privatelink before, but we do use a private Snowflake that I can only connect to when I am on the VPN, wondering if that is all similar. it looks like you have done the right thing by setting host. Perhaps the best next thing to do would be to schedule a call with you to investigate further. If you could please reach out to your Snowflake account representative and have them send a message to me that would be great.

Hey @PLsergent. Was this issue resolved?


config.staticUrl

Default to /static/
If can be useful to change it to / when hosting robots.txt or sitemap.xml
Also move the serveStatic logic for the folder inside lib/nuxt.js, so the middleware will have the same logic.

Finally, map /static/ to /


nz-tab support each tab has a router

I'm submitting a...

[ ] Bug report
[ x ] Feature request
[ x ] Documentation issue or request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Support request => Please do not submit support request here

Current behavior

Does nz-tab support each tab has a  router similar like
I checked material docoment found this:

While  is used to switch between views within a single route,  provides a tab-like UI for navigating between routes.The tab-nav-bar is not tied to any particular router; it works with normal  elements and uses the active property to determine which tab is currently active. The corresponding  can be placed anywhere in the view.

    {{tabLink.label}}

<router-outlet></router-outlet>

Expected behavior
Each tab has  a individual router

    <nz-tabset>
        <nz-tab>
            <ng-template #nzTabHeading>
                登录
            </ng-template>
            <router-outlet></router-outlet>

        </nz-tab>

        <nz-tab>
            <ng-template #nzTabHeading>
                注册
            </ng-template>
            <router-outlet ></router-outlet>
        </nz-tab>

    </nz-tabset>

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

ng-zorro-antd version: X.Y.Z

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX

For Tooling issues:
- Node version: XX
- Platform:

Others:

    <nz-tabset>
        <nz-tab>
            <ng-template #nzTabHeading>
                登录
            </ng-template>
        </nz-tab>
        <nz-tab>
            <ng-template #nzTabHeading>
                注册
            </ng-template>
        </nz-tab>
    </nz-tabset>
    <router-outlet ></router-outlet>

@vthinkxie Unfortunately, your solution does not work well because the user can change the tab without clicking the routerLink. Is there a workaround for that?


builtins.json: we should generate it on build

The builtins.json file was being generated only on install target,
we must generate it while building.
Signed-off-by: Leandro Dorileo<EMAIL_ADDRESS>

ACK

applied.


Creating custom buttons using emojis

I am looking for a way to create a custom "button" using an emoji in my app. Some emojis, such as 👍, 👎, ✅, ❌, imply feedback that might be shared on a given message block (for example, ❌ might be used to dismiss a block). In order to create a UI that is as simple and uncluttered as possible, I am hoping to use an arbitrary emoji effectively as a button, without adding a larger button accessory.
Ostensibly, this would involve adding a link to the emoji <(url)|👍>, such that clicking the emoji would send a signal to my app and delete the block. However, I am not sure how/if this can be implemented:

as I am not sure what that link should look like, and where it should post

would selecting this emoji always open the link in a new window?

Any recommendations would be much appreciated.
The slack_bolt version
slack-bolt==1.5.0
slack-sdk==3.5.0
Python runtime version
3.9.2
OS info
ProductName:    macOS
ProductVersion: 11.2.3
BuildVersion:   20D91
Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64

Hi @rkoniuta, thanks for asking the question!
Unfortunately, there is no way to make links or text functioning like a button.
The only way is to use button components in Block Kit. Our recommendation for your use case is to use an "actions" block. With the block, you can have multiple buttons in a single block. Here is the Block Kit Builder URL demonstrating how it works.

{
  "blocks": [
    {
      "type": "section",
      "text": {
        "type": "plain_text",
        "text": "If everything looks good, click the :check_green: button. Otherwise, click the :x: button and let us know what else you need  by submitting the modal :bow:"
      }
    },
    {
      "type": "actions",
      "elements": [
        {
          "type": "button",
          "text": {
            "type": "plain_text",
            "text": ":x:"
          },
          "value": "ng",
          "action_id": "ng"
        },
        {
          "type": "button",
          "text": {
            "type": "plain_text",
            "text": ":check_green:"
          },
          "value": "ok",
          "action_id": "ok"
        }
      ]
    }
  ]
}

If you would like to navigate your end users to an external URL, you can set the URL to a button element. Of course, you can include this as one of the elements in an "actions" block.
{
  "type": "button",
  "text": {
    "type": "plain_text",
    "text": "Update your settings"
  },
  "value": "1",
  "url": "https://www.example.com/your-own-url",
  "action_id": "link-button"
}

I hope this was helpful to you. This may not be a solution for your use case but if there is nothing else to ask here, may I ask you to close this issue?

👋 Hey @rkoniuta, let us know if you have something further to ask/discuss here. Let me close this issue after waiting for your response for a few more days.

Let me close this issue but please feel free to write in if you have something further to discuss here.

can we add buttons to our message with slack-bolt in python


PlacesSearch/SearchNearby:: PlacePhoto - [bug]: Documentation error

Thanks for stopping by to let us know something could be better!

PLEASE READ
If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.
Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.
If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.
Check for answers on StackOverflow with the google-maps tag.

Please be sure to include as much information as possible:
Environment details

Specify the API at the beginning of the title (for example, "Places: ...")

Done

OS type and version

NA

Library version and other environment information

"Last updated 2021-09-29 UTC."

Steps to reproduce

https://developers.google.com/maps/documentation/places/web-service/search-nearby
Under PlacePhoto
See how example API call contradicts the required parameters for the call

Code example
https://maps.googleapis.com/maps/api/place/photo?maxwidth=400&photo_reference=photo_reference&key=YOUR_API_KEY

Field
Required
Type
Description

height
required
number
The height of the photo.

html_attributions
required
Array
The HTML attributions for the photo.

photo_reference
required
string
A string used to identify the photo when you perform a Photo request.

width
required
number
The width of the photo.

Following these steps will guarantee the quickest resolution possible.
Thanks!

I don't quite follow with what is the issue here.

width is the dimension within the photo schema returned in an API request such as place details.
maxwidth is a parameter for a place photo API request

I apologize for the lack of clarification.
In the docs, it says that height, html_attributions, photo_reference, and width are required parameters for the API call. Maybe, I have misinterpreted the documentation as saying those are the required return values from the API.

Yeah, those properties are part of the response schema for the other place apis.

I apologize for misinterpreting the docs. Ill go ahead and close out the issue.


Leader Icon getting question mark when hovering in late game

Leader Icon getting question mark when hovering in late game

Not a bug


Annotate parse tree for diphthongs

The notes for a column should include whether the column contains a diphthong.

Done.


Provide documentation on how to set up Skygear and Skygear cloud

Now there is no explicit guide on how to set up Skygear Server and cloud dev

It should be on skygeario/skygear-doc/#421


Add splitter function source_target_split

We need a function available from root of skadawith the following use case

X_s, y_s, X_t, y_t = source_target_split(X,y,sample_domain)

X_s, y_s, domain_s, Xt, yt, domain_t = source_target_split(X,y,sample_domain, return_domains = True)

# it just uses the sign of sample_domain (or of y if sample domain is not provided) but can still return the domains when asked (when multiple/source are available)

For many visulationsation we need an easy way to split teh data that avoid using logical sleection EVERYWHERE when needed to split the data.

In the code it's done with check_X_domain helpers, though I agree there should be a friendlier options for the API users (checkers are for those who works on their own estimators).
Should the ordering be (Xs, Xt, ys, yt) the same way split_train_test does it in sklearn?

i have a fisrt implementation in PR #31 this is a good point it will better allow the splitting of wiegts and domains


How to loop through custom fields content

Hi
Am making a theme for in camaleon 2.4 and i have some slider content

and i would like to display these content in the front end, how do i go about it

Sample here:
https://gist.github.com/owen2345/fdec8eb47db6db91a76c05827bc64c5b

Please close issues if they are resolved


HTTP Perf tests failing for days

Description:
$subject

It seems like even though the load-tests are passing, results have not been updated to load-test-result branch was not properly deleted when updating a previous load-test results.
Will be fixed with #1164

Results have successfully updated. https://github.com/ballerina-platform/module-ballerina-http/actions/runs/2795950476

Even though the workflow was successful, the error rate for load-tests are 100%. Hence, re-opening the issue.

Even though the workflow was successful, the error rate for load-tests are 100%. Hence, re-opening the issue.

Ack

This was verified as fixed with following PR #1183
There was an issue with snowpeak load test and it will be captured in issue #3070


Cycle Markers for Cubase and ADR Cue Sheets

Steffan, from your experience with DAWs, does MarkersExtractor able to fit into the workflow for creating Cycle Markers and ADR Cue Sheets.
ADR Cue Sheets
https://www.soundsinsync.com/products/edicue
https://www.production-expert.com/home-page/adr-cueing-made-easy-with-the-free-pg-pt-session-software
Now that we can export caption as markers, I wonder is it helpful (or make sense) for the users if we can create ADR Cue Sheets file? And users can import the ADR Cue Sheets into their DAW for ADR recordings?
Cycle Markers
Does Cubase have the ability to import Cycle Markers?
https://steinberg.help/wavelab_pro/v10/en/wavelab/topics/markers/markers_from_xml_files_importing_t.html

Does Cubase have the ability to import Cycle Markers?

Yes. DAWFileKit can import/export Cubase XML files.


fix: fix WEBUI_BANNERS environment variable not working

Pull Request Checklist
Fixes the environment variable documented here: https://docs.openwebui.com/getting-started/env-configuration#webui_banners
Note: to make this work, you have to escape the quote in your .env file. Example:
WEBUI_BANNERS="[{\"id\": \"1\", \"type\": \"warning\", \"title\": \"Your messages are stored.\", \"content\": \"Your messages are stored and may be reviewed by human people. LLM's are prone to hallucinations, check sources.\", \"dismissible\": true, \"timestamp\": 1000}]"

Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[x] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[x] Testing: Have you written and run sufficient tests for validating the changes?
[x] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description

Remove unused dependencies in config.py.
Parse banners config from environment if set.

Fixed

Fix WEBUI_BANNERS environment variable

LGTM, Thanks!


🌊 [Feature] Add tools built with python

TODO:

Add any tools built with Python under the tools folder

Make sure to add README using the template provided

You can add an already existing tool as long as it has different features

hello @AseanK i would like to work on this, can i work on it pls?

Sure! Have fun! 😀

hello @AseanK i have created a PR for this issue on https://github.com/AseanK/python-tools-and-games/pull/35
pls review

I have added a PR on https://github.com/AseanK/python-tools-and-games/pull/36
can i work on the readme.md, i think it needs improvement (If you don't mind)
@AseanK

@marameref
Sure! Any improvements are welcome!

@AseanK I want to work on this issue as a part of the semester project! Could you please assign this to me?

@ruchit-t sure! Have fun!

@ruchit-t sure! Have fun!

@AseanK, I added a Python tool to track the internet connectivity of the WiFi network on Windows OS. Please have a look at the logic and the Readme file to get better insight!
If you feel it is correct, please accept my PR #38
Thanks again!


Support tagging pages

Per #71
Current commit is just the data model change, I'll add UI in a subsequent commit to this PR.

This seems ready to review. It allows admins to tag pages. Those tags don't get displayed on the page, and the pages aren't displayed on the tag's page, because I'm not sure what the UI y'all want for that is.
In terms of deprecated categories and themes, it seems totally reasonable to just migrate categories to tags, since they have the same representation. I'm not sure if all the categories that exist want to still exist as tags, though; the ones that are seeded are the old categories from the earlier site, which aren't really topical.
Themes could also be migrated, though they seem to have a constraint that an article only has one theme; I don't know if this is something we want to keep.

Hi @withoutboats! Looks pretty good so far at quick glance.
But if I'm understanding it correctly, it's not quite ready to merge as is. Unless I'm missing something.
Is there a way to discern that one tag is a tag and another is a category?

There is no difference between the two in structure, but how we use Category is like sections in a newspaper.
Tag is topical. There can be an Arts Article tagged with "foo" and a History Article tagged with "foo".
An Article can have many tags. Way more than we (currently) want to show in the header image area.
An Article can have many categories, but we keep it between 1 and 3. So we can show them in the header image area.
Categories are used as a top level item in the site nav (footer). Tags are not.

Am I missing how this is done?
If I'm not and it doesn't currently work that way, can you add that to your PR please?
(Sorry this Issue didn't have better specs.)
PS. Themes have a similar requirement. Structurally, they're very similar to Tags (even if we removed the one theme per Article restriction, which I'd be fine with.)

Is there a way to discern that one tag is a tag and another is a category?

This doesn't actually change anything about either categories or themes - this PR only allows tags to be applied to page (so articles still have both categories and tags).
The questions in my previous comments were to suss out the requirements you've enumerated, thanks :-)
If you want we can land these changes incrementally or I can keep iterating on the other changes in #71 on this branch, it doesn't make a difference to me.

Oh great! I misunderstood.
Incremental is better than all at once. I'll ask @bookis to review this PR too.


Bug-04092022-1 - error when using "schedule is.expired" filter

Describe the bug
The output ends with the following error

processing ruleset 'PanoramaConf: / RuleStore:Security' that holds 96 rules

** ERROR ** * Died on user notice or warning!! Error: Undefined variable: d on /tools/pan-os-php/lib/object-classes/Schedule.php:371

*** Backtrace ***
Provided via Slack

Expected behavior
script should export expired rules into Excel
Steps to reproduce
run command
pan-os-php type=rule in=config.xml location=any 'actions=exporttoexcel:expired-rules.xls' 'filter=(schedule is.expired)'
Screenshots
additional information provided via Slack
Your Environment

Version used: 2.0.56
Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3): Docker
Operating System and version (desktop or mobile): Windows 10 Pro

fixed with PR: #646


The results of context.param are URL-encoded

Current behavior
URL: http://localhost:8000/çawa yî%3F
Code:
app.get("/:text", () => {
  console.log(context.param("text"));
})

Output:
%C3%A7awa%20y%C3%AE%3F

Expected behavior
URL: http://localhost:8000/çawa yî%3F
Code:
app.get("/:text", () => {
  console.log(context.param("text"));
})

Output:
çawa yî?

Version: 2.4.0

@yusukebe
Due to RFC 2718, URL may also include multilingual characters using utf-8 encoding.
For a certain period of time, browser didn't decode it and show encoded string in url field. But nowadays, they properly decode it. (mostly, I think)
So I think it makes sense to decode it by default when we call param().
What do you think?

Yes, you should decode it. That's what I want.

You're currently not decoding it.

@yujong-lee

But nowadays, they properly decode it. (mostly, I think)

Yes, I think so. And I've also tried it with other Node.js frameworks: Express.js and Fastify; the characters are decoded. So, let's make it decode the values when calling param().

I am not familiar with the codebase so I leave that to you.


ARK: SA Not Updating Metrics (Possibly Child Process Monitoring)

Operating System
Ubuntu 24.04
AMP Version and Build Date
<IP_ADDRESS>
AMP Release Stream
Mainline
I confirm that

[X] I have searched for an existing bug report for this issue.
[X] I am using the latest available version of AMP.
[X] my operating system is up-to-date.

Intended Action
N/A
Expected Behaviour
N/A
Actual Behaviour
N/A
Reproduction
A fix was put in to address metrics not updating, but they are still not updating for ARK: SA.

Resolved in tomorrow's update.


Delta-RS Saved Delta Table not properly ingested into Databricks

Environment
Delta-rs version:
0.18.2
Binding:
Not sure
Environment:

Cloud provider:
Azure Data Lake Gen2

OS:
Windows 11

Other:

Bug
What happened:
Ingesting the delta table stored on the azure data lake, made by the deltalake pakage on azure databricks leads to databricks not picking up the delta tables properly; it loads up all of the parquet files instead of reading it as delta table.
What you expected to happen:
Only the latest version of the delta table is ingested
How to reproduce it:
Created a pandas dataframe, write to azure multiple times using overwrrite,
More details:
Creating a ticket with databricks as well to resolve the issue.

We need more info because this sounds like you are not reading the table correctly with spark

Heya, reading the table via databricks sql, loading it via deltatable package locally with pandas

Loading it in databricks sql

Loading it in databricks sql with distinct

The databricks sql also keeps the older version of the file which different rows

Nevermind, me being a knobhead. I saved to azure data lake with .parquet in the blobname
Fixing it gives me this for ingestion (I am quite new to databricks)

Closing this now thanks!


sfdx force:source:delete does not work on production orgs

force:source:delete fails and wouldn't run on production orgs.
Steps to Reproduce:

Connect to any production org and attempt to delete any metadata (in this case attempting to delete a custom field)

sfdx force:source:delete -m "CustomField:testobject__c.Admin_Badges__c"
throws error:
{
"status": 1,
"name": "sf:INVALID_OPERATION",
"message": "INVALID_OPERATION: testLevel of NoTestRun cannot be used in production organizations",
"exitCode": 1,
"commandName": "SourceDeleteCommand"
}

As above command failed with testLevel missing error, try providing testlevel and attempt the delete

sfdx force:source:delete -m "CustomField:trailheadapp__Trailhead_User_Data__c.Admin_Badges__c" -l RunLocalTests
throws error:
{
"status": 1,
"name": "Error",
"message": "Unexpected arguments: -l, RunLocalTests\nSee more help with --help",
"exitCode": 1,
"commandName": "SourceDeleteCommand",
"stack": "Error: Unexpected arguments: -l, RunLocalTests
}
tried other possibilities with --checkonly flag etc.. but none help.
tried with latest and greatest cli & plugin version.
Couple other notes:

The documentation from Salesforce is very Vague around this and needs correction as well. It doesn't clearly state whether this is designed to work for production orgs or not.
This command should also take manifest file (package.xml/destructivechanges.xml) to have scalable way to list components to delete. currently it seem like designed to accept only comma separated metadata components which is not viable.

@salesforce Any update here? We don't have visibility on work items.

@fransf-wtax - We first want to promote the source plugin to the production CLI core plugins.  Once that work is complete the next scheduled work will be to add the source delete command to it, but also to support destructive changes as part of a source:deploy.  My guess is it will be delivered in late July or early August.

This was fixed in latest v7.120.0, release notes:
https://github.com/forcedotcom/cli/tree/main/releasenotes#71200-sept-30-2021

This was fixed in latest v7.120.0, release notes: https://github.com/forcedotcom/cli/tree/main/releasenotes#71200-sept-30-2021

Sorry but this still seems to be happening even in the latest release.
Here's my output running  sfdx -v
sfdx-cli/7.132.0 wsl-x64 node-v16.13.0

This was fixed in latest v7.120.0, release notes: https://github.com/forcedotcom/cli/tree/main/releasenotes#71200-sept-30-2021

The error remain unresolved in the latest release:
sfdx-cli/7.201.6 win32-x64 node-v18.15.0
Error:
sfdx force:source:delete --sourcepath c:\Users\mario\Desktop\Workspace\SF Albira PRO\force-app\main\default\lwc\gtagManagerScript --noprompt (node:9344) Warning: Deprecated environment variable: SFDX_JSON_TO_STDOUT. Please use SF_JSON_TO_STDOUT instead. (Use node --trace-warnings ... to show where the warning was created) Warning: The "force source delete" command has been deprecated. Use "project delete source" instead. Warning: The "--sourcepath" flag has been deprecated. Use "--source-dir | -p" instead. Warning: The "--noprompt" flag has been deprecated. Use "--no-prompt | -r" instead. *** Deleting with SOAP API *** Error (1): INVALID_OPERATION: testLevel of NoTestRun cannot be used in production organizations


[SPARK-24777][SQL] Add write benchmark for AVRO

What changes were proposed in this pull request?
Refactor DataSourceWriteBenchmark and add write benchmark for AVRO.
How was this patch tested?
Build and run the benchmark.

Test build #96182 has finished for PR 22451 at commit d410a36.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait DataSourceWriteBenchmark

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96182/
Test FAILed.

HI, @gengliangwang . Since this aims to refactor, could you check #22443 to be consistent?

Refactor DataSourceWriteBenchmark and add write benchmark for AVRO.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3197/
Test PASSed.

Test build #96191 has started for PR 22451 at commit 34af59d.

Test build #96191 has finished for PR 22451 at commit 34af59d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96191/
Test FAILed.

Merged build finished. Test FAILed.

retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3212/
Test PASSed.

Test build #96217 has started for PR 22451 at commit 34af59d.

Test build #96217 has finished for PR 22451 at commit 34af59d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96217/
Test PASSed.

btw, why this pr automatically links to the corresponding jira...?: https://issues.apache.org/jira/browse/SPARK-24777

@maropu When I create this PR, I type to "[[" at the beginning of title, thus it fails to link to the JIRA.

oh, I see. can you put it in the jira manually?

Oh I was creating a PR for refactoring BenchmarkBase, I planned to merge this one after that one.
Since this is merged, I will create one to refactor both.


WIP: frontend: Improve pod persistent volume detail

Improve information for volumes under pod details page
Fixes issue #1329
Description
Current feature request to enable names as a dynamic link to the corresponding PVC within the pod details page.
Changes

[x] Created a source field for navigation to the Volumes PVC and Config map

I was supposed to clarify here how we are supposed to update this view. Sorry for the delay and here it is:
Let's have a Volumes section where each volume will use a NameValueTable whose first row is the name of the volume (similar to ContainerInfo).
Each of these tables, besides the 1st row with the name of the volume should have:

Type: The typeof this volume (ConfigMap, hostPath, projected, ...), see https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#volume-v1-core
Others: Rows depending on the kind

For the "Others" mentioned above, they will be different depending on the type, so we should have likely a table renderer per kind, like: VolumeConfigMapRenderer, VolumeHostPathRenderer, etc.
Since it's nearly impossible to cover all cases, we can show the plain YAML for the keys within the type value. If these keys are a string, boolean, or a number, just render their value as is. If it's an object/array, then just convert (YAML) to a string (indented/pretty) and display it.
Hope this makes it clearer.

WIP NOTE: still deciding if to keep the rendering table to its own component or to use current logic / something similar to render detail data

currently working on a fix for better YAML prints (ref: VolumeDetailRender component)

rendering the details through their own component render table could allow easier changes to an Innertable (already experimented with) but shows problems with rendering as either inner table squished or all others data squished to the right

WIP NOTE: (continued...)
Added working YAML print that I forgot, still needs polish

commit note:
fixes bug where detail would print as empty with a label when string is set to ""

It's coming up nice!
I think we should change Type to Kind, to avoid the clash with the other "type". WDYT?

commit note:
- data and yaml render working

removed old component file
changed default label to keyword "Kind"

Note: will remove the console logs during the next review

Could you please add a story for the VolumeSection component?
(probably this one will need the signoff as well)

Commit

Created a story for volume section

commit note

issue fixed where the volume for rendering and volume used for links shared no fields

this bit is still broken and needs to be fixed

refactored the code and implemented fixes from comments

I ran the npm i18n to try to fix the error for the new word "volumes" being added but it seems not to want to take it?

found a bug where clicking on a secret source link may not work
it also undone the fix for optional field somehow?

removed the console logs and edit spacing

I have tried to rebase onto the current main and met a few issues.
There seems to be an issue originating from the cronjob details file (unrelated to the changes in this branch) which this branch does not update for some reason, the commits were made a few days ago but it does not update on rebase?

Somehow the issue from the volumes keyword has returned, could be a similar issue?

I was able to fix the first error where it wouldnt update the changes made to another file, but the volumes keyword error still remains


Ensure users know to set METEOR_PACKAGE_DIRS in their ${HOME}/.profile

This adds some scripting to append the METEOR_PACKAGE_DIRS export to ${HOME}/.profile if it's not there and update it if there is one there already.

That's great but for the standard install export METEOR_PACKAGE_DIRS=${ YOUR VULCAN HOME }/packages; isn't really necessary? I think it's better to keep things simple imo.

Are you sure?  I was getting an error when I tried to run without that reference.

I'll have to double-check but you're not supposed to get an error.

I noticed the error after rebooting.
When I added the METEOR_PACKAGE_DIRS link to my ~/.profile I could reboot without the error appearing.

What was the error?

Sorry not to have shown the error initially, I was explaining why I added the PACKAGE_DIRS linking, not reporting a bug.  I thought the error was an expected consequence of not having the link, and saw no reason to look any deeper.  Anyway, this is what I am seeing :
/home/you/.meteor/packages/meteor-tool/.1.2_2.fkst7p++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:280
					    throw(ex);
					    ^
Error: Fragment "UsersCurrent" registered, but not initialized.
    at getFragment (packages/vulcan:lib/lib/modules/fragments.js:161:11)
    at withCurrentUser (packages/vulcan:core/lib/modules/containers/withCurrentUser.js:15:9)
    at meteorInstall.node_modules.meteor.vulcan:forms.lib.FormWrapper.jsx (packages/vulcan:forms/lib/FormWrapper.jsx:223:16)
    at fileEvaluate (packages/modules-runtime.js:333:9)
    at require (packages/modules-runtime.js:228:16)
    at meteorInstall.node_modules.meteor.vulcan:forms.lib.export.js (packages/vulcan:forms/lib/export.js:1:228)
    at fileEvaluate (packages/modules-runtime.js:333:9)
    at require (packages/modules-runtime.js:228:16)
    at /home/you/projects/Vulcan-Starter/.meteor/local/build/programs/server/packages/vulcan_forms.js:2121:15
    at /home/you/projects/Vulcan-Starter/.meteor/local/build/programs/server/packages/vulcan_forms.js:2127:3
=> Exited with code: 1

I think that's an unrelated issue, let me look into it.

Closing as we try to minimize the code surface. We expect users to learn advanced Meteor feature for packages alongside Vulcan, and to directly ask questions on the Slack if they feel blocked or support such help script as 3rd party repos.