Pods stuck in ContainerCreating due to pause image pull error 401 unauthorized

We generally build custom EKS AMI using EKS optimized AMI as base image in ap-south-1 region and copies to other regions for EKS cluster setup.
Having the below issue in the EKS after upgrade to 1.27, if the pause image gets deleted on the node.
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "900889452093.dkr.ecr.ap-south-2.amazonaws.com/eks/pause:3.5": failed to pull image "900889452093.dkr.ecr.ap-south-2.amazonaws.com/eks/pause:3.5": failed to pull and unpack image "900889452093.dkr.ecr.ap-south-2.amazonaws.com/eks/pause:3.5": failed to resolve reference "900889452093.dkr.ecr.ap-south-2.amazonaws.com/eks/pause:3.5": pulling from host<PHONE_NUMBER>93.dkr.ecr.ap-south-2.amazonaws.com failed with status code [manifests 3.5]: 401 Unauthorized
Can anyone help me, please?

How did the pause image get deleted from the node?

I've seen this failure mode a few times in the past, because containerd doesn't have a way to obtain ECR credentials to pull the sandbox container image. That's why we pull it with a systemd unit at launch time (if it's not already cached in the AMI): https://github.com/awslabs/amazon-eks-ami/blob/master/files/sandbox-image.service
You could systemctl restart sandbox-image to trigger a pull, and we could feasibly run this periodically so this isn't a terminal node failure; but I'd still look into why the image was deleted to begin with.

Hi @cartermckinnon,
Thanks for your reply.
We used a custom script that runs on every node to cleanup the unused images and exited containers on the node. which is being removing the pause image as well on the node. which is causing trouble in our environment.
Now we modified the script that can exclude some images on the node.

I've been running into this issue on nodes randomly since 1.29 upgrade. Both AWS EKS managed nodes running AL2 and AL2023 as well as Ubuntu's EKS image...
Getting really frustrating to have keep refreshing nodes as that's the only fix I can figure out..
Can't find much info/threads about it, this was one of the few.

So, I was just about to try and log into the nodes that are currently affected for me and was checking the docs because I don't know offhand where/how kubelet/k8s caches images.. as of 1.29:
Garbage collection for unused container images
FEATURE STATE: Kubernetes v1.29 [alpha]

As an alpha feature, you can specify the maximum time a local image can be unused for, regardless of disk usage. This is a kubelet setting that you configure for each node.

To configure the setting, enable the ImageMaximumGCAge [feature gate](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/) for the kubelet, and also set a value for the ImageMaximumGCAge field in the kubelet configuration file.

The value is specified as a Kubernetes duration; for example, you can set the configuration field to 3d12h, which means 3 days and 12 hours

that sounds incredibly fishily interesting and potentially the issue
note this is happening also on EKS-managed nodes running Amazon Linux AMIs?

I've seen this failure because I tried to prune the images by myself using the crictl rmi --prune. Running the command systemctl restart sandbox-image as @cartermckinnon suggested fixed the problem, but I was wondering, do we really need to prune the images by ourselves?
I saw this article https://repost.aws/knowledge-center/eks-worker-nodes-image-cache that suggests we already have a cleanup of the image in according with the image-gc-high-threshold attribute (default to 85%).

do we really need to prune the images by ourselves?

Nope! The kubelet will take care of this. Deleting images out of band almost always hurts more than it helps.


Dedupe lerna

Some things don't work because lerna creates multiple copies of a package. I need to somehow de-duplicate the packages during development.

pnpm solves this


vimPlugins.LanguageClient-neovim: 0.1.146->0.1.154

Motivation for this change
Update version of vimPlugins.LanguageClient-neovim
Things done

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

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

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

Notify maintainers
cc @

@GrahamcOfBorg build vimPlugins.LanguageClient-neovim


[Enhancement] Enhance User Experience and Visual Appeal Across Website Elements

Navbar:

Center align the navbar and implement button-like effects for better differentiation.
Introduce smooth scroll animation for seamless navigation through sections.

Savor the Flavors Section:

Apply hover animations to all elements within the boxes/cards to enhance interactivity.

Download the App Buttons:

Incorporate icons (Google Play Store and App Store) with modern effects for visual appeal.

Footer:

Customize email and message input fields in the 'Contact Us' section to match the website theme.
Increase the size of the 'Your Message' input field.
Update the copyright year to 2024.
Make 'Home,' 'Menu,' 'Services,' 'Contact,' and 'Cart' clickable in the 'Our Pages' subsection.

Menu Page:

Enhance hover effects for buttons under dish names.
Update dish prices to rupees and categorize food items under relevant headers.
Change 'Order Now' buttons to 'Add to Cart' for consistency and functionality.

Services Page:

Implement pop-up elements for 'Gift Card and Voucher Redemption' and 'Exclusive Offers and Promotions' buttons.
Adjust customer opinion picture dimensions to avoid stretching.
Replace lorem ipsum text with authentic reviews and vary star ratings.

Contact Us Page:

Modernize the form theme to align with the website's aesthetic.
Refine input questions for clarity.
Add padding to the 'Send Message' button for centered text.
Align footer text using container and alignment properties.

Cart Page:

Customize cart table theme to match the overall website theme.
Include images of items added to the cart for visual reference.

I'd like to contribute to the project. Could you assign this issue to me

I'd like to contribute to the project. Could you assign this issue to me

the issue can only be assigned by the repository owner/admins. so, we might have to wait a few hours or days for them to review all issues and assign them accordingly.

This issue is already solved.
Try to contribute to different issues.


Go Build is Slow w/ Latest Windows Updates

What version of Go are you using (go version)?

$ go version
go version go1.20.6 windows/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
Windows 11 amd64
go env Output
$ go env

What did you do?
Open a terminal
Navigate to directory with the package main
Execute "go build"
What did you expect to see?
A fast build time.
What did you see instead?
A very, very, very long build time.

**Issue:**
With recent Windows 11 updates, and likely other Windows versions, it appears that the build process is hanging for long periods of time. The issue is not manifest when disabling the following new Windows components:

Cloud-delivered protection
Automatic Sample Submission

While I'm aware that this is not explicitly a Go issue, it is nonetheless common place for applications built for Windows to play nice with the Windows ecosystem by doing things upon installation like disabling or warning about incompatible Windows settings and features.
It might also be a good idea to offer to add temporary build directories to the Windows Defender exclusion list, or advise users about how to do that somewhere in some documentation. I didn't find any, and no one on the Go forum appears to know where to find these. Or at least no one so far.

sounds like a windows defender specific issue, not go.

That's surprising and disappointing. Is Go abandoning Windows compatibility altogether?

Go is an open source project.  If you want to send in a documentation patch, that would be fine.  Thanks.

Yes I tried to submit a docs issue and it was closed immediately without investigation.
I'd rather discuss and investigate with experts before submitting my own personal research on the topic.
Is there somewhere that experts can discuss issues and share potential solutions besides the issues board on GitHub where they are apparently closed indiscriminately?

We don't use the issue tracker for discussion.  For good places to discuss Go issues see https://go.dev/wiki/Questions.

Thanks, @ianlancetaylor. That makes sense. I should have checked the bottom of the readme.


Vespa-config-status gives connection errors after configuring HTTP/2

I deployed a Vespa cluster in Azure Kubernetes with HTTP/2 enabled using the latest Vespa build. My setup is similar to this one: https://github.com/vespa-engine/sample-apps/tree/master/basic-search-on-gke, with the HTTP/2 server configured according to the instructions found here: https://blog.vespa.ai/http2/.
Here's the container part of my services.xml:

<container id="container" version="1.0">
       <http>
      <server id="tls" port="8443">
        <ssl>
          <private-key-file>/vespa-app/certificates/vespa-private-key.pem</private-key-file>
          <certificate-file>/vespa-app/certificates/vespa-public-cert.pem</certificate-file>
          <ca-certificates-file>/vespa-app/certificates/vespa-public-cert.pem</ca-certificates-file>
            <client-authentication>need</client-authentication>
        </ssl>
      </server>
      <server id="default" port="8080"/>
    </http>
    <document-api />
    <document-processing/>
    <search />
    <nodes jvmargs="-Xms512m -Xmx512m">
      <node hostalias='container'/>
        <node hostalias='container0'/>
        <node hostalias='container1'/>
        <node hostalias='container2'/>
    </nodes>
  </container>

Everything is working well, I'm able to load data and query Vespa using HTTP/2 using self-signed certificates. There's no errors or warnings in the logs, except for the following:
[2021-07-21 14:40:07.424] INFO    : slobrok          vespa-slobrok.slobrok.server.rpc_server_manager    managed server container/container.3/chain.indexing at tcp/vespa-container-2.vespa-internal.vespa.svc.clus
ter.local:19100 failed: (RPC) Connection error
[2021-07-21 14:41:19.882] INFO    : slobrok          vespa-slobrok.slobrok.server.rpc_server_manager    managed server container/container.2/chain.indexing at tcp/vespa-container-1.vespa-internal.vespa.svc.clus
ter.local:19100 failed: (RPC) Connection error
[2021-07-21 14:41:47.312] INFO    : slobrok          vespa-slobrok.slobrok.server.rpc_server_manager    managed server container/container.1/chain.indexing at tcp/vespa-container-0.vespa-internal.vespa.svc.clus
ter.local:19100 failed: disconnected

Also, when I run vespa-config-status, I get the following:
container/container.0: Failed to fetch json: could not parse HTTP status line: '§♥♥'
container/container.1: Failed to fetch json: Connection error: socket write error
container/container.2: Failed to fetch json: Connection error: socket write error
container/container.3: Failed to fetch json: Connection error: socket write error
command terminated with exit code 1

I'm surprised to see these errors since, like I said, Vespa is otherwise behaving fine.

Just a short description on what is going on.
The vespa-config-status tools uses http(s) of the containers to fetch configuration version, since it has been secured with mTLS it's not longer able to read the information.  I'll see what we can do about this, we do have a solution for this in the cloud. Your vespa installation health is not impacted by this error however.

As a workaround for this issue you can move the 8080 port first in the http block:
<container id="container" version="1.0">
    <http>
        <server id="default" port="8080"/>
        <server id="tls" port="8443">
        ...
    </http>
    ...
</container>

The config model will then tag port 8080 to be used instead of 8443. You can verify by checking the model, e.g:
# vespa-model-inspect service container
container @ vespa-container :
default/container.0
    tcp/vespa-container:8080 (STATE EXTERNAL QUERY HTTP)
    tcp/vespa-container:8443 (EXTERNAL HTTP)

The port tagged with STATE will be used by the vespa-config-status utility

Thanks for your reply Morten.
I changed the config as you said, and the vespa-model-inspect command shows it is indeed properly set:
container @ vespa-0.vespa-internal.vespa.svc.cluster.local : container/container.0     tcp/vespa-0.vespa-internal.vespa.svc.cluster.local:8080 (STATE EXTERNAL QUERY HTTP)     tcp/vespa-0.vespa-internal.vespa.svc.cluster.local:8443 (EXTERNAL HTTP)     tcp/vespa-0.vespa-internal.vespa.svc.cluster.local:19100 (MESSAGING RPC)     tcp/vespa-0.vespa-internal.vespa.svc.cluster.local:19101 (ADMIN RPC)
Unfortunately, I still get errors when running vespa-config-status:
container/container.1: Failed to fetch json: Connection error: socket write error container/container.2: Failed to fetch json: Connection error: socket write error command terminated with exit code 1

I'm not sure if you have secured ports? Are you able to curl -v to the vespa-0.vespa-internal.vespa.svc.cluster.local:8080/Applicationstatus from the node which you run vespa-config-status utility?

I am able to access the admin cluster this way and get the ApplicationStatus.
I also tried to reach the content and container nodes this way, not sure if that should work, and it fails with a connection refused error.
The vespa version I'm currently using is "7.438.16" not sure if you introduced any fixes since then.

@labriedion The next Vespa release will have HTTP/2 enabled by default without the need for TLS. Both HTTP/2 with prior knowledge and HTTP/2 through upgrade is supported. If you prefer TLS I highly recommend checking out our newly announced TLS functionality in Vespa: https://blog.vespa.ai/securing-vespa-with-mutually-authenticated-tls/.

Thanks Bjørn!


add "apt-get update -y" to Vagrantfile

The provided box is already out of date and creates some trouble when installing packages. Adding the "update" command would make it live a bit longer...

should we upgrade as well?

closed with f0e1bdcc08b908d12258f3093e596d02c0078546


Cleanup splash

Thu Sep 10 10:02:04 2015 zander<EMAIL_ADDRESS>ID 4d8e85efe09bf4b04cd6f181020a10c41a821021
Make the splashscreen not appear jagged anymore
Thu Sep 10 09:51:43 2015 zander<EMAIL_ADDRESS>ID 429561b0949b91a53896dad1fdd17209634c42d5
Cleanup the NetworkStyle a little.
The class was created using a scopedPointer so it would be deleted
when it went out of scope at the end of the method.
A much easier way to do this is to use an on-stack instance and that
also means we don't pass a pointer to the constructor of various classes
having unclear ownership and lifetime.
I also removed many usages of pixmap which is very expensive to use
for image manipulations.  A pixmap implicitly uploads its data to the
graphics card memory, so only use it for diplaying purposes!
Last I ran the bitcoin.png through an optimizer which reduced the size
by about 30%

This looks good to me.
@jonasschnelli Thanks for the review, I assume you don't have any pressing objections? It's been a loooooong time since I used Qt so will delegate to your fine judgement.

OK, as there were no objections, I'll test and review this once my plate is cleared of other higher priority items. We have not forgotten about it!


Added my respiratory for At-Bash decoding

Shameless plug I guess

Thanks. Have a Chag kasher v'sameach!


Aggregation failing

Building the bionic branch gives errors when aggregating.
After selecting the storms 2014 dataset.
When aggregating by square I get:
windshaft error:
"Failed to process "polygon-fill" property: unable to compute ramp, The requested grid is too big to be rendered

When zooming in at some point I get:
windshaft error:
relation "aggregation.agg_admin0" does not exist

When aggregate==animated and column==created_at
Uncaught Error: aggregation "millennium" is not defined
    at Object.helper.add (histogram-helper.js:87)
    at Object.helper.fillTimestampBuckets (histogram-helper.js:41)
    at child.parse (histogram-dataview-model.js:169)

For aggregation "millennium" is not defined error.
In https://github.com/CartoDB/Windshaft-cartodb/blob/master/lib/cartodb/models/dataview/histograms/date-histogram.js#L131 millenium is returned. In https://github.com/CartoDB/carto.js/blob/master/src/dataviews/helpers/histogram-helper.js#L12 the century and millenium keys are missing.
Could not find version combi which fixes this issue and retains other improvements.

Created issue for it at https://github.com/CartoDB/carto.js/issues/2161


chainer.get_device(10) does not cause error

Testing under chainer==6.0.0 with chainerx built and cupy installed.
Testing environment has only 1 GPU.
import chainer

device = chainer.get_device(10)          # NOT Cause error!
print('device', device)  # @cupy:10
device2 = chainer.get_device('cuda:10')  # Cause error!
print('device2', device2)

When we try to get GPU device with id more than allowed, the behavior is different between cupy & chainerx cuda device.

cupy: does not raise error
chainerx cuda: raise error

I think raising error is more convenient for users. How do you think?

Note that if we query the device count, the CUDA environment will be initialized and the MultiprocessParallelUpdater can no longer be used https://github.com/chainer/chainer/blob/master/chainer/training/updaters/multiprocess_parallel_updater.py#L136-L140 ?

Pytorch's way of multiprocessing:
https://gist.github.com/colesbury/606e3838d56ca33996cc40ef00bcdb6b
Much cleaner.

@hvy the device count can be queried when initializing chainer by doing a fork,  that way the cuda context is destroyed and MultiprocessParallelUpdater can be used, #7413 tries to do this.

@emcastillo I don't think we should do such a trick. Even if we can avoid CUDA context creation in chainer.get_device(), CUDA context can be created anywhere else.  It's just one instance of such possibilities. The problem won't be gone by fixing only chainer.get_device().
MultiprocessParallelUpdater can produce comprehensible error, so it's OK to just let chainer.get_device() create CUDA context. See also #7470.

The above comment assumes users can easily avoid such error by doing something like this.
I thought the following snippet in user's script would solve the problem, but tried in imagenet data parallel example, it does not avoid CUDA context and causes another error related to ForkingPickler.
import multiprocessing
if __name__ == '__name__':
    multiprocessing.set_start_method('spawn')

Am I missing something?

In my case the multiprocessing.set_start_method('spawn') keeps failing with the cuda context issue

@emcastillo Did you remove the _cuda_initialized check in MultiprocessParallelUpdater.__init__()? Presence of CUDA context in the main process is not essential.

Ok! I will try it now, thanks!

#7486 correct the pickle behavior by re-creating the lock when the object is deserialized.


Cannot start application

While I run npm start, a dialog like following opened. After I press the OK button, the dialog disappered and the application hanged. I have to press CTRL+C to quit it.
The error is: BrowserWindow is not a function

I'm on the master branch, updated to newest commit.

Hong what is your running environment ?
OS / version ?
Language / charset ?

Did you run npm install?

OS: Ubuntu 15.10 64bit Simplified Chinese(zh_CN) @ac225519
Yes, I ran npm install before npm start @hoffmabc

Please try my portable no-install build:
https://www.mediafire.com/folder/mpjxf3cocpof7/OpenBazaar_Test_LINUX_Builds

I delete node_modules subdir and reinstall npm packages. It works.


Added rotating tips. 5 tips that cycle every 60 seconds with fadeout/fadein

5 Tips :-

Type @ then press TAB to auto-complete nicknames
Type /help to see the list of commands
Type /rooms to list all available rooms
Type : then press TAB to auto-complete emoji icons
You can create your own private rooms. Type /help for more info

Fade Out / Fade In = 2 secs each.
Rotate is set for every 60 seconds.
** Apologies for the 2nd commit. I wanted to get my style, right.

Updated.

Why is this code in index.htm?

3 reasons.

The message div is located in this folder.
it's tiny.
i didn't know of any other js file where it would be appropriate to place it, in. Having it in a seperate js file is preferable because of caching.

I would prefer to have it in a js file. Any preference? chat.ui.js?

Yes move it to the ui file :).

Ok. done.
few points to note:

I'm kick starting the function logic by calling the jquery ready logic. I'm not 100% sure if this is the best place to do it, so I'm happy to move this starting call to a more appropriate place (i'm just not 100% familiar with the js jabbr code).

// Start cycling the messages once the document has finished loading.
$(document).ready(cycleMessages());

Even though i've added a variable to define the cycle time in milliseconds, I'm not sure if that's an overkill. So i'm also happy to replace this..

 $('#message-instruction').fadeIn(2000, cycleMessages());
}, cycleTimeInMilliseconds);````

with this

````$('#message-instruction').fadeIn(2000, cycleMessages());
}, 60000);````


Static cache

I am using this template and in top of this i have modified it to support static(browser) cache
for 30 days and based on that after every build i am generating new has([contenthash]) for my all js file
sample code format
 output: {
        filename: 'app.client.js',
        chunkFilename: '[name].[contenthash].js'
    },

i Needed some help to understand the generation and use of app.client.js and is there a way i can add [contenthash] to app.client.js file also and where exactly this file is referred to.
https://github.com/rherwig/template-react-ssr/blob/master/webpack/client/common.js#L9

For short: you could just use contenthash in the filename as well. But things easily get complicated with webpack and react... and since I see, that you are quite a regular user of this project, please hit me up, if you need a 1on1 support session. I would be glad to assist you :-)

Thnaks @rherwig, thanks for the support, For now adding [hash] to every file solved my problem.


Moving between files loses comment position

Versions

IDEA 2017.3.4
Gerrit plugin 1.0.5-146

Steps to repro

Open a diff in a change under review
Start a comment on a specific line other than the first, do not save the comment
In the diff window, step between files (alt-right, alt-left)
Return to original file
Save comment

Expected result
Comment is saved next to line/range against which it was opened
Actual result
Comment is saved against top of file

Thanks @treuherz for this detailed report.
This only happens for you when you step between files, right? If you save the comment right when you add it, it works as expected?


posix_apis:mimxrt685_evk_cm33 timeout in test_posix_realtime

Describe the bug
posix related cases hangs when run
test_posix_realtime
To Reproduce
Steps to reproduce the behavior:

mkdir build; cd build
cmake -DBOARD=mimxrt685_evk_cm33
make
make flash

Expected behavior
test pass
Impact
no clear.
Logs and console output
Running test suite posix_apis
===================================================================
START - test_posix_pthread_execution
Thread 0 starting with scheduling policy 0 & priority 15
Thread 1 starting with scheduling policy 0 & priority 15
Thread 2 starting with scheduling policy 0 & priority 15
Bounce test OK
Barrier test OK
PASS - test_posix_pthread_execution in 0.718 seconds
===================================================================
START - test_posix_pthread_error_condition
PASS - test_posix_pthread_error_condition in 0.1 seconds
===================================================================
START - test_posix_pthread_termination
Thread 0 starting with a priority of 4
Cancelling thread 0
Thread 1 starting with a priority of 3
Cancelling thread 1
Thread 1 could not be cancelled
Thread 2 starting with a priority of 2
Cancelling thread 2
Thread 3 starting with a priority of 1
Cancelling thread 3
Thread 3 could not be cancelled
PASS - test_posix_pthread_termination in 1.14 seconds
===================================================================
START - test_posix_multiple_threads_single_key
Different threads set different values to same key:
thread 0: set value = 806886024 and retrieved value = 806886024
thread 1: set value = 806886248 and retrieved value = 806886248
PASS - test_posix_multiple_threads_single_key in 0.17 seconds
===================================================================
START - test_posix_single_thread_multiple_keys
Single thread associates its value with different keys:
key 0: set value = 806886448 and retrieved value = 806886448
key 1: set value = 806886448 and retrieved value = 806886448
PASS - test_posix_single_thread_multiple_keys in 0.17 seconds
===================================================================
START - test_posix_clock
POSIX clock APIs
POSIX clock APIs test done
PASS - test_posix_clock in 2.4 seconds
===================================================================
START - test_posix_semaphore
PASS - test_posix_semaphore in 5.1 seconds
===================================================================
START - test_posix_normal_mutex
mutex lock is taken
PASS - test_posix_normal_mutex in 0.102 seconds
===================================================================
START - test_posix_recursive_mutex
recrusive mutex lock is taken
PASS - test_posix_recursive_mutex in 0.3 seconds
===================================================================
START - test_posix_mqueue
PASS - test_posix_mqueue in 0.11 seconds
===================================================================
START - test_posix_realtime
POSIX clock set APIs

Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows)
Toolchain (e.g Zephyr SDK, ...)
Commit SHA or Version used: zephyr-v2.5.0-2637-ga3469a049785

@MaureenHelm , @dleach02


[Operator] optimize normalize op with vectorized load, dynamic shape and more

this change introduces several enhancements to the current norm operator

vectorized load for fp16 types
allow epilogue
dynamic shape on the normalized dimension
add a tuning to use 2 warp shuffle routines or just a single one
cleaner code and implementation

as a result, norm_fp16.py can be safely deleted
for shapes in stable diffusion: [2, 32, 60, 16, 16], norm dims [60, 16, 16], fp32:

torch : 0.023 ms
main: 0.036 ms
this change: 0.027 ms

for shapes in bert-base: [1, 128, 768], norm dims [768], fp16:

torch: 0.006 ms
main: 0.008 ms
this change: 0.007 ms

We are still not faster than torch, but very close

the tests are passing
this change is isolated to norm OP so will merge without a review.


Add Functions to simplify Property extraction from an Element

An ExtractProperty and ExtractIdentifier function could be added to simply extract a property from an Element, or return null.

Merged into develop.


Panel preferences

Each panel (integral, peak, range) could have preferences in the little menu bar that should be added.
The preferences will be a gear icon.
It will let appears panel preferences that will be stored in the analysis in:
    this.preferences = {
      panels: {
        '1H': {
          integrals:{},
          peaks:{},
          ranges:{},
        },
        '13C': {
          integrals:{},
          peaks:{},
          ranges:{},
        }
      },
      display: {},
    };

that exists for this purpose
The preferences of the panels will be nucleus related in order to plan the future in which we have in the same display different spectra and we need to specify a different number of decimals depending if it is a proton or a carbon for example.
As an exercise we can add for the peaksPanel the following options

δ (ppm) : show / hide, number decimals: 2
𝜈 (Hz) : show / hide, number decimals: 4
peak width : show / hide; number decimals: 3

This principle will be expanded to the other tools as well
I like the idea that preferences are 'behind' the card and I wonder if the form could be flipped using https://www.npmjs.com/package/react-card-flip (Demo: https://aaronccwong.github.io/react-card-flip/). So when you click on the small gear the table flips and you see the preferences.

this will be important to debug peak picking results. I added some simulated spectra and the peak picking is not aligned. Would like to know the value that is found with all the decimals.

@lpatiny
do you mean the auto peak picking, i will check it and inform you what is the result, but the manual peak picking is working fine and it's depend on the index of the x so all what i did i took the array of index that generated from auto peak picking fnction and display it, how i can know if the index is correct?

@lpatiny
Panel preferences, i can't imagine what you need exactly from me to implement.

Each panel (peaks, integrals, etc) may have some options like the number of digits. So next to the delete icon there could be a little gear to display preferences of this pannel as described above.
Those preferences should be saved in the json.

@lpatiny
this.preferences = {
panels: {
'spectrum id': {
integrals:{},
peaks:{},
ranges:{},
},
display: {},
};
i think it's better if we use spectrum id and according to the selected spectrum it has different options

I don't expect to have specific preferences per spectrum and would like to be able to reuse the preferences for another set of spectra so it is better that it is based by nucleus and not spectrum id.

I don't expect to have specific preferences per spectrum and would like to be able to reuse the preferences for another set of spectra so it is better that it is based by nucleus and not spectrum id.

it's done;


Adding Since and DeprecatedAfter attribute generation.

This change generates the files in the directory immediately following in output directory based on the namespace. It also adds support for generating the [Since] and [DeprecatedAfter] attributes.

Merged into the develop branch.


first pass at adding a non-selectively disclosable JWT VC to the spec

Changes

renamed the draft

kept the short name, might need to introduce a term like JOSE-VC to aggregate both "JWT VC and SD-JWT VC" but might work without it too)
I must admit I fought the urge to call it JWS VC...

restructured so that there is a common data format section with headers and payload requirements

followed by a section per jwt vc and sd-jwt vc that defines media type and non-disclosable claims (for sd-jwt vc)

verification and processing is a top level section now
no changes to the jwt issuer metadata section
presenting VC section is common to both

introduced ho to present a JWT VC with a HB JWT. this is currently the only way to do HB with JWT VC when HB is necessary.

no example of JWT VC yet - can be another PR I think

please rename to draft-terbu-jwt-vc

cc @OR13, @mprorock.

What's the difference between a "JWT VC" and a "JWT" ?

What's the difference between a "JWT VC" and a "JWT" ?

@peacekeeper I hope the text below from PR #131 explains it:
"SD-JWT is a superset of JWT as it can also be used when there are no selectively disclosable claims and also supports JWS JSON serialization, which is useful for long term archiving and multi signatures. However, SD-JWT itself does not define the claims that must be used within the payload or their semantics.
This specification therefore uses SD-JWT and the well-established JWT content rules and extensibility model as basis for representing Verifiable Credentials with JSON payload. Those Verifiable Credentials are called SD-JWT VCs.
SD-JWTs VC can contain claims that are registered in "JSON Web Token Claims" registry as defined in [@!RFC7519], as well as public and private claims."
bottomline, how would you use JWT RFC7519 to have interoperable JWT VCs? you need to have a set of mandatory JWT claims, rules how to discovery the keys to validate it, etc.

@Sakurann Thank you.. So if I understand correctly, a "JWT VC" nowdays is almost the same as a traditional JWT, except that it makes some JWT claims mandatory and steals - uh excuse me - adopts and "JWTifies" several other concepts invented by VCs, such as "type", three party model, key discovery, status list, etc.?

First and foremost, if W3C VC WG was the right place to define credentials in three party model with vanilla JSON and JWT claims, that work would not be happening elsewhere. W3C VC WG made it clear that it is only interested in working on anything JSON-LD so a JW-* work item in W3C will focus on protecting the payload that is JSON-LD without using any JWT claims. so all of us interested in working on vanilla JSON/JWT claim set based three party model credentials had to find a new home for it.
So yes, JWT VC that uses JWT claims is (should have always been) based on the "traditional JWT", assuming you mean RFC 7519 and I do not see anything wrong with that :)
Second, let's not argue who invented what - the concepts of typing JWTs (ex: RFC8725), key discovery (ex: RFC8414), and status lists (ex: CRLs) have existed before/alongside VCs. though as I said, VCDM should get the benefit of making the three party model concept widely known and should be appreciated and praised for that. (which is how i feel).
Finally, it usually makes people happy when the concepts they have worked on are being used in other places, even in places they have not anticipated. so your choice of words is very "interesting".

Very excited for VCs that are CBOR and JSON.
Also excited for key transparency, COSE and SCITT... IETF has an excellent community and building blocks that make development easy.
Everything does not need to happen at the W3C, in JSON-LD, with terms controlled by w3id.org which is not even the W3C.
I personally prefer my terms to come from RFCs and IANA, but reasonable people can disagree.

@Sakurann Sorry for my choice of words, I didn't mean it in a negative way :) I actually like this direction.. On the technical level, this specification and PR feel right to keep the VC data model and JWT data model separate, in order to avoid things like a "vc" claim and unclear transformation rules that we have seen in the past.
On the marketing and communication level however this needs improvement I think. How is anyone supposed to understand the difference between a "VC", a "JWT", a "JWT VC", and "VC-JWT"? If a "JWT VC" is a "VC", then what do you call what the W3C VC WG is defining? Does this mean there will be "VCDM-based VCs" and "non-VCDM-based VCs"?

@Sakurann Do you want to close this PR since we merged PR #131 ?


Problem with requesting local files?

I have noticed issues with using d3.request since moving my repository from D3 version 4.10.0 to version 4.10.2.
By examining my package-lock.json, I noticed one difference is that the former uses d3-request version 1.0.5 whereas the latter uses d3-request version 1.0.6.
The situation:

I am using browserify and http-server to prepare and serve my file respectively.
I have a file called index.html which I access via localhost:8080 when I'm building something.
I have a file called filelist.json which I can access via localhost:8080/filelist.json while I'm building.
I tried using d3.json() to access filelist.json from index.html and process the data.
Initially I used error and data arguments in the d3.json() callback to throw any errors and start working with the data. However, I got an Unexpected token T at character 0 error.
I removed the error throw and simply logged data in the console. This is when I saw that the T was the beginning of the line TypeError which was reporting that it could not access the file.
The problem seems to be that d3.json() was attempting to access my file from the address localhost:80filelist.json, instead of the full and correct address.
I tried this with other d3-request methods, like d3.tsv() and d3.request() itself. Same error thrown, albeit in slightly different guises depending on the function.

Since rolling back to D3 v4.10.0 I have not had this problem.

Duplicate of #24. Please see that issue for discussion on how to bundle D3 modules.

Thanks. Apologies for missing the previous issue on this. Will have a read.


YouTube homepage glitching

When I visit the YouTube homepage, it either moves rapidly up and down, or the top row of videos is slightly obscured by the bar that lets you sort by different recommended categories. This seems to be happening on every layout after 2013.

For clarification, all recommended videos are jittering rapidly when scrolled up all the way, not the homepage in it's entirety.

Yep, YouTube changed something again. I'll have to release a patch later.

The patch should be up in a few minutes.
If you're using the Beta, put this code into a userstyle:
html[layout] {
  --bt-chips-display: block;
}
html[layout^="hitchhiker-2013"] {
  --bt-chips-display: none;
}
ytd-browse[page-subtype="home"] ytd-feed-filter-chip-bar-renderer {
  display: var(--bt-chips-display) !important;
  position: fixed !important;
  z-index: 1919;
  width: calc(100vw - var(--bt-sidebar-width)) !important;
  max-width: calc(100vw - var(--bt-sidebar-width)) !important;
  min-width: calc(100vw - var(--bt-sidebar-width)) !important;
  left: var(--bt-sidebar-width);
}
ytd-feed-filter-chip-bar-renderer #chips-wrapper.ytd-feed-filter-chip-bar-renderer {
  width: calc(100vw - var(--bt-sidebar-width)) !important;
}
ytd-feed-filter-chip-bar-renderer #scroll-container.ytd-feed-filter-chip-bar-renderer {
  width: calc(98vw - var(--bt-sidebar-width)) !important;
  margin: 0 auto;
}
html[homepage="small-grid"] ytd-browse[page-subtype="home"] #contents.ytd-rich-grid-renderer,
html[homepage="smaller-grid"] ytd-browse[page-subtype="home"] #contents.ytd-rich-grid-renderer {
  max-width: 1262px !important;
  margin-top: 60px !important;
  padding: 16px 12px;
}
html[homepage="rich-grid"] ytd-browse[page-subtype="home"] #contents.ytd-rich-grid-renderer,
html:not([homepage]) ytd-browse[page-subtype="home"] #contents.ytd-rich-grid-renderer {
  margin-top: 60px;
}


Clean up the code

What happened?
A lot of the program logic is partially convoluted and unnecessarily roundabout. Cleaning it up would result in easier understanding for newcomers.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, I am interested in taking up this issue. Please do assign me. I will try to make the code clean and more readable.

Sure go ahead!


added ELEC413_vbanh.gds

for ELEC413 2024 project 1. 1st version. Contains one bragg cavity. (vbanh)

Please fix the errors. The GCs have violated the designated floor plan.


Introduce BriteDatabase / BriteContentResolver types. Make SqlBrite a…

…n adapter for both.
Open to different naming. This was the best I could do.

I dig it :shipit:
Itd be cool if you could manually tell git you're renaming a file so it keeps the diff.


Request for notes/comments field for all templates

I think we want to add a notes section for all templates.  Just in case the template doesn't capture a particular user's needs at that time, if they possibly made a mistake, or if they want a reminder to revisit something.
I usually end up inserting a few "comments" into the spreadsheets I use to track my experiments such as "not certain of sample orientation" or "forgot to carbon coat sample" or "we may need to reconsider what is considered a good quality measurement for this alloy."  I'm guessing no matter how good the templates are, somebody is going to think of something extra they want to note.

@gtarcea - I believe that this has been done??


kata cleanup is not completed when --rm is used

/kind bug
Description
When running kata-containers with --rm qemu is not terminated after container
running is completed.
Steps to reproduce the issue:

Install kata

sudo podman  --runtime=/usr/bin/kata-runtime run --security-opt label=disable -it --rm fedora:latest sleep 1

ps aux | grep qemu

Describe the results you received:
qemu process is still running
Describe the results you expected:
qemu should have been terminated
Additional information you deem important (e.g. issue happens only occasionally):
This is happening since ContainerStateRemoving state was added
(25cc43c376c5ddfa70a6009526f8f03b5235c2c6)
Output of podman version:
Version:            1.9.1 (+ upstream)
RemoteAPI Version:  1
Go Version:         go1.14.2
OS/Arch:            linux/amd64

kata-runtime: 1.11
qemu: 4.2.0

Output of podman info --debug:
debug:
  compiler: gc
  gitCommit: ""
  goVersion: go1.14.2
  podmanVersion: 1.9.1
host:
  arch: amd64
  buildahVersion: 1.14.8
  cgroupVersion: v1
  conmon:
    package: conmon-2.0.15-1.fc32.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.15, commit: 33da5ef83bf2abc7965fc37980a49d02fdb71826'
  cpus: 2
  distribution:
    distribution: fedora
    version: "32"
  eventLogger: file
  hostname: kata-f32
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.6.8-300.fc32.x86_64
  memFree:<PHONE_NUMBER>
  memTotal:<PHONE_NUMBER>
  ociRuntime:
    name: runc
    package: runc-1.0.0-144.dev.gite6555cc.fc32.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc10+dev
      commit: fbdbaf85ecbc0e077f336c03062710435607dbf1
      spec: 1.0.1-dev
  os: linux
  rootless: true
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.0.0-1.fc32.x86_64
    version: |-
      slirp4netns version 1.0.0
      commit: a3be729152a33e692cd28b52f664defbf2e7810a
      libslirp: 4.2.0
  swapFree: 0
  swapTotal: 0
  uptime: 191h 22m 42.55s (Approximately 7.96 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
store:
  configFile: /home/test/.config/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-1.0.0-1.fc32.x86_64
      Version: |-
        fusermount3 version: 3.9.1
        fuse-overlayfs: version 1.0.0
        FUSE library version 3.9.1
        using FUSE kernel interface version 7.31
  graphRoot: /home/test/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 13
  runRoot: /run/user/1000/containers
  volumePath: /home/test/.local/share/containers/storage/volumes

I was able to fix it with something like that:
https://github.com/snir911/libpod/tree/kata_cleanup
Although I'm not sure it's a proper fix as i found out that the issue is derived by the order of the cleanup, qemu is not terminated whenever runtime continer cleanup (delete(ctx)) is done after tearing down the storage (Is it a valid order of operations?)
Any guidance will be appreciated :)

I believe we are calling kata-runtime-stop  and kata-runtime-kill when stopping and removing the container, then we remove the storage.  kata-runtime should be stopping the qemu process.  Podman does not know anything special about kata versus crun, versus runc.
@mheon WDYT

The suggested patch is completely unworkable; we cannot allow cleanup on running containers, it would allow containers that are running to be unmounted.
It sounds like Kata really disagrees with us unmounting the storage first, then removing the container from the runtime. That seems like a reasonable ask from an OCI runtime, so I've added a patch (#6229) to do this. If that's not enough to resolve things, this is definitely a Kata bug.

Does Removing state means container might still be running? (in this patch i changed it so be set to Removing only if it's not Running)
#6229 won't help as cleanupRuntime checks it's Stopped or Created state on the beginning and the state is Removing.
The problem seems to be with teardownStorage not cleanupStorage, what is actually the difference?

Removing means the container is in the process of being deleted. I'm really confused as to how we're getting into Removing while cleanup hasn't been completed, though, Removing should guarantee cleanup already ran...

Nevermind, think I know what's going on here. If cleanupRuntime() is happening as part of remove() we are never in a good state to actually remove the runtime if it exists (IE, the container was in ContainerStateStopped).

Pushed one more commit that might resolve this

I have a similar version but i was not sure if doing the cleanup before setting the Removing state will make Removing state redundant (or even to regress the bug< #3906> you fixed with 25cc43c376c5ddfa70a6009526f8f03b5235c2c6)
Otherwise, i can confirm this is working (maybe worth moving the kata/runtime part from the first patch commit to the second one, which actually fix it)

fixed by #6229


Data/Tree: Add Traversible instance.

The Tree type defined in Mathlib/Data/Tree.lean should have a Traversible instance. This should be added to the file and the associated TODO removed.

@BoltonBailey Last year, I ported the LawfulTraversable instance deriver which derives Traversable attendantly in Mathlib.Tactic.DeriveTraversable.
You can see the example in test.Traversable.
This instance deriver should help you. 😄

@Komyyy  from the looks of it, it seems your deriving handler creates functions that are not as polymorphic as they could be... for example, right now #check Tree.map gives Tree.map.{u, u_1} {α : Type u} {β : Type u_1} (f : α → β) : Tree α → Tree β, while using your deriving handler gives Tree.map.{u} {α β : Type u} (f : α → β) : Tree α → Tree β. As such, for now i will write the instance manually.


Settings sync turns off if you try to experiment with different themes too quickly.

VSCode Version: 1.52.1
OS Version: Windows 10 20H2

Steps to Reproduce:

I was trying out different themes by scrolling through the theme list
After a while Settings Sync turned off with a "Too many requests" error

 [userDataSync] [error] LocalTooManyRequests (UserDataSyncError) syncResource:unknown operationId:unknown: Too many requests. Only 100 requests allowed in 5 minutes.
Maybe it would be good to have a small timeout after which settings are synced? Why sync immediately on a theme change?
After a while I was able to turn it back on, but it shouldn't sync so quickly when changing themes to avoid timeouts.

/duplicate
https://github.com/microsoft/vscode/issues/91286

/duplicate
https://github.com/microsoft/vscode/issues/91286


Steps from the finally block in a pipeline aren't displayed on the tree diagram

STR:
Create any codebase and run the build pipeline
Open the tree diagram and compare stages with tekton
ER: The tree diagram contains all stages
AR: Steps from the finally block in a pipeline aren't displayed


fix DiffEqBase and OrdinaryDiffEq to be the same as in ClimaCore tests

@sajjadazimi - could you check if this will for for you?
I basically fixed those two packages to be whatever is fixed in ClimaCore.jl. I think that for some reason over there we have to be using some old pinned version

bors r+


Introduce BP_VERIFY_LAUNCHPOINT to enable generated files

needed: https://github.com/paketo-buildpacks/libnodejs/pull/37
fixes: https://github.com/paketo-buildpacks/node-start/issues/588
Summary

The env variable BP_VERIFY_LAUNCHPOINT can be used to not check that the file to launch exists.
Use Cases

If the file that should be launched is generated.
Checklist

[X] I have viewed, signed, and submitted the Contributor License Agreement.
[X] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[X] I have reviewed the styleguide for guidance on my code quality.
[X] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

Lets wait for libnodejs being released and consumed. And then add this documentation.


Merging Virtual Archives

The Merge Virtual Archives dialog opens up nicely, and a new merged.yama.store folder is generated upon running the command. However, the .cfg file is not generated and the following error is raised when I try to open the virtual archive in Rover.
Could you please take a look what is going wrong here?

I just tested again and it worked fine for me. You open the virtual store using "Open virtual store"
Can you maybe include the full error. I can't see the stuff on the far right and that is where it will say the line of code. Maybe it is something specific to your archive.
Certainly an issue that needs to be fixed. Thanks for reporting @NadiaHuisjes.

Hmm.. We should see if this happens again and reopen is so.


Donations?

I've been using this great script. Do you accept donations? I would like to give back!

Glad you like it! My PayPal is<EMAIL_ADDRESS>:smile:


Adds ISO 8601 logical types for Avro based on strings

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@087d9df). Click here to learn what that means.
The diff coverage is 91.3%.

@@           Coverage Diff            @@
##             master     #71   +/-   ##
========================================
  Coverage          ?   92.2%
========================================
  Files             ?     125
  Lines             ?    1912
  Branches          ?     111
========================================
  Hits              ?    1763
  Misses            ?     149
  Partials          ?       0

Impacted Files
Coverage Δ

sql/src/main/scala/hydra/sql/JdbcUtils.scala
98.48% <100%> (ø)

sql/src/main/scala/hydra/sql/AvroValueSetter.scala
86.79% <100%> (ø)

...in/scala/hydra/avro/convert/ISODateConverter.scala
100% <100%> (ø)

sql/src/main/scala/hydra/sql/PostgresDialect.scala
92.15% <100%> (ø)

...ql/src/main/scala/hydra/sql/JdbcRecordWriter.scala
84.84% <71.42%> (ø)

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 087d9df...f70fc5b. Read the comment docs.


[Wallet proto] Fix TxOut fields of SendToMany rpc

The TxOut field script should be changed to address in order to allow the daemon's wallet to extract scripts and eventual blinding keys from the outputs field of SendToManyRequest.

closed in branch beta@637e9141


"Clipping" bug when standing at the portals edge

If you stand at the very edge of the portal, the view gets clipped:
GIF:

I don't think it's a big problem or that it matters at all, but I wanted to report it just in case :)
(Running on Paper-353 if that matters)

Okay that's quiet a big portal you got there! xD But I'll look into it when I'm available again,

no problem, I don't think anyone will really care about that, I just wanted to mention it^^

Fixed (not published yet)


Custom operator support

I think this is ready to review.
WIP to decide if we progress cc @alamb.
This is based on #11132 since I need Operator to be non-copyable. If we decide to progress I can rebase this, or cherry pick and create a new branch.
You can see this without the churn of #11132 at https://github.com/samuelcolvin/datafusion/pull/1.
high level question
Is all the effort here worth it, should we just add the 20 or so extra operators from the sql library to Operator?
Advantages of this route:

more flexibility in how operators behave, what their signatures is, precedence, negation etc.
easier to use custom operators or new operators adding to the SQL library without waiting for datafusion to support them

Disadvantages:

a lot of faff here it's not that bad

To to

[x] How should ParseCustomOperator be passed into the SQL parser, it definitely shouldn't be as it is now, perhaps we should have an equivalent of register_function_rewrite like, e.g. register_custom_operators? DONE
[x] is the hack with WrapCustomOperator necessary and acceptable, maybe someone else's Rust foo could avoid this? I think what we have is good
[x] should CustomOperator provide a get_udf method, then we rewrite to that function automatically, rather than relying on register_function_rewrite? I don't think so, the current write logic is more powerful
[x] what should we do about from_proto_binary_op, we can't keep the same signature and support custom operators, this might be easy to fix - done by adding the register methods to FunctionRegistry
[x] is it okay to rely on name() of the operator to implement equality, ordering and hashing? I think it's good
[x] Needs tests - basic tests are done, LMK what more is needed

Example Usage:

Here's a trivial example of usage that just replaces the "->" operator with string concat:
use std::sync::Arc;

use datafusion::arrow::datatypes::DataType;
use datafusion::common::config::ConfigOptions;
use datafusion::common::tree_node::Transformed;
use datafusion::common::DFSchema;
use datafusion::error::Result;
use datafusion::execution::FunctionRegistry;
use datafusion::logical_expr::expr_rewriter::FunctionRewrite;
use datafusion::logical_expr::{
    CustomOperator, Operator, ParseCustomOperator, WrapCustomOperator,
};
use datafusion::prelude::*;
use datafusion::sql::sqlparser::ast::BinaryOperator;

#[derive(Debug)]
enum MyCustomOperator {
    /// Question, like `?`
    Question,
    /// Arrow, like `->`
    Arrow,
    /// Long arrow, like `->>`
    LongArrow,
}

impl std::fmt::Display for MyCustomOperator {
    fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
        match self {
            MyCustomOperator::Question => write!(f, "?"),
            MyCustomOperator::Arrow => write!(f, "->"),
            MyCustomOperator::LongArrow => write!(f, "->>"),
        }
    }
}

impl CustomOperator for MyCustomOperator {
    fn binary_signature(
        &self,
        lhs: &DataType,
        rhs: &DataType,
    ) -> Result<(DataType, DataType, DataType)> {
        Ok((lhs.clone(), rhs.clone(), lhs.clone()))
    }

    fn op_to_sql(&self) -> Result<BinaryOperator> {
        match self {
            MyCustomOperator::Question => Ok(BinaryOperator::Question),
            MyCustomOperator::Arrow => Ok(BinaryOperator::Arrow),
            MyCustomOperator::LongArrow => Ok(BinaryOperator::LongArrow),
        }
    }

    fn name(&self) -> &'static str {
        match self {
            MyCustomOperator::Question => "Question",
            MyCustomOperator::Arrow => "Arrow",
            MyCustomOperator::LongArrow => "LongArrow",
        }
    }
}

impl TryFrom<&str> for MyCustomOperator {
    type Error = ();

    fn try_from(value: &str) -> std::result::Result<Self, Self::Error> {
        match value {
            "Question" => Ok(MyCustomOperator::Question),
            "Arrow" => Ok(MyCustomOperator::Arrow),
            "LongArrow" => Ok(MyCustomOperator::LongArrow),
            _ => Err(()),
        }
    }
}

#[derive(Debug)]
struct CustomOperatorParser;

impl ParseCustomOperator for CustomOperatorParser {
    fn name(&self) -> &str {
        "PostgresParseCustomOperator"
    }

    fn op_from_ast(&self, op: &BinaryOperator) -> Result<Option<Operator>> {
        match op {
            BinaryOperator::Question => Ok(Some(MyCustomOperator::Question.into())),
            BinaryOperator::Arrow => Ok(Some(MyCustomOperator::Arrow.into())),
            BinaryOperator::LongArrow => Ok(Some(MyCustomOperator::LongArrow.into())),
            _ => Ok(None),
        }
    }

    fn op_from_name(&self, raw_op: &str) -> Result<Option<Operator>> {
        if let Ok(op) = MyCustomOperator::try_from(raw_op) {
            Ok(Some(op.into()))
        } else {
            Ok(None)
        }
    }
}

impl FunctionRewrite for CustomOperatorParser {
    fn name(&self) -> &str {
        "PostgresParseCustomOperator"
    }

    fn rewrite(
        &self,
        expr: Expr,
        _schema: &DFSchema,
        _config: &ConfigOptions,
    ) -> Result<Transformed<Expr>> {
        if let Expr::BinaryExpr(bin_expr) = &expr {
            if let Operator::Custom(WrapCustomOperator(op)) = &bin_expr.op {
                if let Ok(pg_op) = MyCustomOperator::try_from(op.name()) {
                    // return BinaryExpr with a different operator
                    let mut bin_expr = bin_expr.clone();
                    bin_expr.op = match pg_op {
                        MyCustomOperator::Arrow => Operator::StringConcat,
                        MyCustomOperator::LongArrow => Operator::Plus,
                        MyCustomOperator::Question => Operator::Minus,
                    };
                    return Ok(Transformed::yes(Expr::BinaryExpr(bin_expr)));
                }
            }
        }
        Ok(Transformed::no(expr))
    }
}

async fn run(sql: &str) -> Result<()> {
    let config = SessionConfig::new().set_str("datafusion.sql_parser.dialect", "postgres");
    let mut ctx = SessionContext::new_with_config(config);
    ctx.register_function_rewrite(Arc::new(CustomOperatorParser))?;
    ctx.register_parse_custom_operator(Arc::new(CustomOperatorParser))?;
    let df = ctx.sql(sql).await?;
    df.show().await
}

#[tokio::main]
async fn main() {
    run("select 'foo'->'bar';").await.unwrap();
    run("select 1->>2;").await.unwrap();
    run("select 1 ? 2;").await.unwrap();
}

You can see this without the churn of #11132 here

This seems to be working well with datafusion-functions-json, see https://github.com/datafusion-contrib/datafusion-functions-json/pull/22

I plan to review this tomorrow morning

I've found an issue whilst working on https://github.com/datafusion-contrib/datafusion-functions-json/pull/22
Lexical Precedence doesn't work correctly
See https://github.com/datafusion-contrib/datafusion-functions-json/pull/22/commits/f573a395da46c251479d0a06c3ea58f2dca3cfa1
The following works as expected in postgres:
select '{"a": "b"}'::json->>'a'='b'
-- True

But with datafusion
select '{"a": "b"}'->>'a'='b'
-- Error during planning: Unexpected argument type to 'LongArrow' at position 2, expected string or int, got Boolean.

Same happens for other common operators like is null.

Precedence issue looks like it's an issue in sqlparser - https://github.com/sqlparser-rs/sqlparser-rs/issues/814#issuecomment-2196624432 😞

cc @phillipleblanc  as I think you may be interested in this too

An also related conversation maybe: https://github.com/apache/datafusion/issues/10534

Is all the effort here worth it, should we just add the 20 or so extra operators from the sql library to Operator?

@alamb sorry I wasn't clear, having implemented this, I'm in favour of sticking to this API, it'll make customising how operators behave much easier than hard coding them all within datafusion. It'll also be much easier to avoid any breaking changes for those who don't want to support more operators.
I'll let you make the final decision.

I am working on an alternate proposal too -- stay tuned

Here is an alternate idea https://github.com/apache/datafusion/pull/11168

@jayzhan211's alternate PR here https://github.com/apache/datafusion/pull/11180 is looking good in my opinion

closing this, I'll follow up on #11180.


/bin/bash: pod: command not found

When I use pod command  , my pod  is in 【/usr/local/bin】
what can I fix it ? thanks !

Just solve it

Just solve it

@flyingDandelionYD How was it solved?


Error when building for Universal Windows Platform

Hy,
when I try to build a project for UWP, there are always 3 errors showing up, after the build finished successfully. I'll just attach text files containing the error messages, to keep this post readable. Nevertheless the build succeeded and I'm also able to deploy to Hololens, but these errors are confusing and maybe they'll cause errors in future development.
Is there something I'm missing or doing wrong?
Best regards :)
Operation system and version numbers
OS: Windows 10 x64
Unity: 2018.1.6f1, BuildTarget UWP
HLAPI Community Edition: 2018.1
LogFiles
ReferenceRewriterFoundSomeErrors.txt
ReferenceRewriterErrorMethodSystem.Void.txt
ReferenceRewriterErrorMethodSystem.UInt64.txt

does it build with default HLAPI?

If it doesn't build with the stock HLAPI then something is very wrong like @paulpach suggests.

Hi @paulpach, hi @SoftwareGuy,
thx for your swift replies. I tried Unity 2018.1.6f1 with default HLAPI and there are no errors. To make sure the Unity version does not affect this one I tried default and pro HLAPI with Unity 2018.1.9f1 and it results in the same behaviour. No errors when using default UNET and the "Reference Rewriter" errors when using HLAPI Pro.
Best regards :)

What version of the HLAPI DLLs are you using, and what branch? A lot of development is going on in the 2017.4-improvements branch, but it's not recommended to use that one on 2018.1 from what I know.

I use the 2018.1 version, downloaded from the link in the Unity Forum.

@FireDragonGameStudio  it would definitely help.
Find us in discord,  where we can chat.

@paulpach Unfortunately I can't join the discord server, due to an invalid invite link.

@FireDragonGameStudio Use this link then.

Hy, please find the link to my example project. I hope this can help to track this down. :)
https://drive.google.com/open?id=1Ijn6p3pu0pwBb-gXPw4sAeJ3HOcI6bNR

@FireDragonGameStudio
Okay, so 2018.1 UNET with Unity 2018.1. Got it.
Will attempt to replicate this.
Please provide replication instructions; do I just try to compile and have it blow up in my face?

@SoftwareGuy Hope you can replicate it. Yes, just build it for UWP, that's all. It should give you the error messages as shown in the image/textfiles of the first post.

I was able to replicate this after installing the latest UWP SDK (I didn't have it installed since I'm not targeting UWP platforms). You can confirm that it's similar if not the same to your issue by taking a look at the attachments.

@SoftwareGuy yes, these are exactly the same errors I get, when building a UWP project.

The methods are clearly defined in HLAPI.
It sounds like Unity uses a different version of the unity.networking dll when building UWP.  Can you check if there are other networking dlls  inside the unity installation?

Afaik is there some kind of "Metro" UWP dll, which contains the UWP implementations for this case. I'm currently not at home, but I'll check asap.

That would make sense.  Check if there is a Metro UnityEditor.Networking.dll  somewhere

Tried replacing the Metro Unity.Networking.dll file and it apparently fails to run some UWP weaver to generate the UWP code or something (I've given @paulpach the log).
This is going to be a tough one to fix unless it's trivial; as it seems to be one of the uncommon usage cases.

@SoftwareGuy As far as i could check, the folder "..\Editor\Data\PlaybackEngines\MetroSupport\Managed\UAP" contains the UnityEngine.Networking.dll AND WinRTLegacy.dll which are both used to build UWP apps. The WinRTLegacy.dll is responsible to provide specific code for UWP apps, which is not available through default .NET implementation.
Is there some HLAPI CE substitute for the WinRTLegacy.dll?

@FireDragonGameStudio  we are making a drop in version.   It should work with all platforms

@FireDragonGameStudio   Mirror is released.   Can you go ahead, try it and see if it solves the issue?

I'll try it and report the result.

Unfortunately the UWP/Hololens build still fails with errors (pls see screenshot) I guess the main reason is still the same. Telepathy uses components from the System.Net namespace (as well as other  namespaces), which UWP doesn't support. I assume the WinRTLegacy.dll would provide interfaces for this replacement.

Ok, forget it. I just tried to build with the backend setting changed to IL2CPP and the build was successful. And as the .NET backend is deprecated by Unity with Unity 2018.2 this issue can be closed :) (https://forum.unity.com/threads/deprecation-of-support-for-the-net-scripting-backend-used-by-the-universal-windows-platform.539685/)


[GSSoC'23] Distance Conversion Project

Describe the project you want to add with tech stack

Title - Distance Conversion Project
Tech using - HTML, CSS and JS
Expected behavior

Responsive for the small devices
Convert the any unit of distance to any other unit of distance like km, m, miles, foot, inch, yard, etc.

Screenshots (optional)

Additional context (optional )

This project is beginner friendly project.

@MohitGupta121 @pranjay-poddar @Saurabh-kumar09 please assign this project to me


Cannot scroll after reloading page in 8.0.1

reactstrap version #8.0.1
react version #16.10.2
bootstrap version #4.3.1

Problem:
Yesterday I upgraded my reactstrap version to 8.0.1. But, I faced a bug. If I reload the page, the scrollbar gets removed and I cannot scroll anymore on that page.
I also observed that this only happens in pages in which generally there is no pre-populated data. Data is fetched by API calls and then shown on the page.
I downgraded reactstrap to 7.1.0. And everything is now working perfectly.

Are there any error in the devTools console?
The only thing I can think of which could cause this is the .modal-body class being applied to the <body>. Can you check if that class is being applied?

No error in devtools.
Yes.  .modal-body is being appended in 8.0.1.
It does not get appended in 7.0.1

Can I take this, any help to file paths that I should keep in mind ?

Sure @koolamusic. It's most likely coming from the https://github.com/reactstrap/reactstrap/blob/master/src/Modal.js triggered by mounting or something that ends up calling the .init() which handles conditionally adding the class to the body:
https://github.com/reactstrap/reactstrap/blob/47843998b627aadcccfe71b092a194197fd2ce15/src/Modal.js#L271-L278
which is later supposed to be cleaned up in the .close() which conditionally removes that class
https://github.com/reactstrap/reactstrap/blob/47843998b627aadcccfe71b092a194197fd2ce15/src/Modal.js#L299-L306
Something seems to be triggering it when it isn't suppose to or maybe not cleaning it up when it is suppose to.

I ran some tests and not able to replicate this bug

@Sabir001 is there any other information you can provide (maybe a stackblitz demo)?

The project I observed the bug, has too many packages connected. I could not reproduce in Stackblitz. I will that try to dig the reason. If I can find, I will update here ...

I'm guessing this is more directly related to #1626
Not sure if you can confirm or not, but does your project initialize a modal with isOpen set to true and hides it via other conditionals? (similar to the example provided in #1626).

It is midnight in my Timezone. I'll test tomorrow and update here.

I'm guessing this is more directly related to #1626
Not sure if you can confirm or not, but does your project initialize a modal with isOpen set to true and hides it via other conditionals? (similar to the example provided in #1626).
as a test, can you import Modal at your project root (such as your index.js or app.js and add this to see if it affects it
Modal.prototype.componentWillUnmount = function () {
  if (this.props.onExit) {
    this.props.onExit();
  }

  if (this._element) {
    this.destroy();
    if (this.props.isOpen) {
      this.close();
    }
  }

  this._isMounted = false;
}

@TheSharpieOne, even after adding the snippet in index.js, the problem still persists.
Also, I wanted to say this again,

I also observed that this only happens in pages in which generally there is no pre-populated data. Data is fetched by API calls and then shown on the page.

I think the issue is connected to #1626 ...
modal-open persisted in body tag in my case, too.

Yeah, I thought it might be the same as #1626, which is why I wanted you to see that modification. Since it didn't work, it might not be related. Here is the example from #1626 with that modification: https://codesandbox.io/s/buggy-modal-e7trx You can see it enable scrolling / fixes the issue.

@TheSharpieOne could you please assign this issue to me, I can comp up with a better solution


[SPARK-41223][BUILD] Upgrade slf4j to 2.0.4

What changes were proposed in this pull request?
This pr aims upgrade slf4j related dependencies from 2.0.3 to 2.0.4.
Why are the changes needed?
A bug fix version:

LoggerFactory only loads services from context class loader

The release notes as follows:

https://www.slf4j.org/news.html#2.0.4

Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GA

Merged to master


Filter for Az storage entity query has no explanation for what it expects in the doc

Doc says:
--filter

Specify a filter to return certain entities.

But gives no explanation of what filter syntax it's looking for.

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

ID: 9a4d128f-a98f-d07b-0183-90ca79cc5fdc
Version Independent ID: 83084fff-ea1b-a9e7-b7a9-40023de43542
Content: az storage entity
Content Source: latest/docs-ref-autogen/storage/entity.yml
Service: storage
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

storage

Looked at the REST documentation and I think the information from "Supported Query Options" to "Query String Encoding" in "Querying tables and entities" is relevant: https://docs.microsoft.com/en-us/rest/api/storageservices/querying-tables-and-entities

Closing this thread.