Not parsing datetimeInput from timestamp, always using UTC

I have dates stored as timestamp in database (i.e: "1617706041927"), so I need to manage them as it but this plugin always uses UTC(i.e: "2021-04-06T19:45:00.000Z") even I configure the plugin through provider to work with timestamps setting datetimeInput to x given it means timestamp. I've also tested with other values but it seems it haven't effect always giving UTC values.

There is a stackblitz with the issue:
stackblitz

hi @jmelich, thanks very much for the bugreport. unfortunately I don't have any time to "maintain" this repository in regards of bugs. all I'm doing is updating dependencies and accepting pull-requests. feel free to open one - I'l gladly look it through! br, timon


boltzcli: autoswap setup unexpected "invalid swap type" error

Not sure how I managed to get into this state, I tested a couple of configurations without ever activating autoswap before I got here.

My autoswap.toml:
acceptZeroConf = false
budget = "100000"
budgetInterval = "604800"
channelPollInterval = "30"
currency = "LBTC"
enabled = false
failureBackoff = "86400"
maxBalance = "0"
maxBalancePercent = 75.0
maxFeePercent = 1.0
maxSwapAmount = "0"
minBalance = "0"
minBalancePercent = 25.0
perChannel = false
staticAddress = ""
swapType = ""
wallet = ""


some prompts can't be identified in several prompts together

When I input three prompts but animation only identifies two of them through img to video. For example, I input below prompts:
"The girl's hair is blown by the wind, blinks and turns her head slowly. Golden sparks exploded in the background and foreground“
The animation shows hair is blowing and sparks moving, but girl's eye and head is motionless. I tried several times and different pictures but result is same. I find only two of three could be identified. I don't know why it happens. Seed change is same.

This is my workflow via picture which could load into comfyUI.

Not really something I can do anything about, it's about the model itself.


chore: Documentation de l'infrasturcture

Recreate https://github.com/mission-apprentissage/bal/pull/194  due to https://github.com/mission-apprentissage/bal/pull/219

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

v1.43.2
GitHub release

Your semantic-release bot :package::rocket:


Add missing credential types to Azure Identity README

Related to https://github.com/Azure/azure-sdk-for-net/pull/29096
Summary of changes

Add missing OnBehalfOfCredential and ClientAssertionCredential types to the README's "Credential Classes" section.
Alphabetize the credential types in the tables, for easier scanning.
Link credential types to their respective API ref pages.

API change check
API changes are not detected in this pull request.


No way to filter repositories in wizard?

I am part of several large organizations.
First off (this isn't really on your end), I have no ability to limit access to just some organizations. So, when I get to step one of the wizard, where it loads in my repositories from all these organizations I don't care about.
On top of that, I don't see a way to filter down the results. Only the first 10-15 results seem to have been returned. I see no way to retrieve additional repositories.
What I would like to see is either an infinite scroller, that continued to load in repositories as you scroll down, or (even better), a filtering system that allows the user to filter by certain criteria (like organization, visibility, etc.). Extra points for text match search!

In addition of that, I think it'll be good to filter by organization

@renatomarinho  I will check this if You`re


API for Users returns wrong data

Note: as a shorthand, all URLs in this post are relative to http://codewars.com/api/v1/users/ .
Today the bug that was displaying the :username/code-challenges/completed results in place of :username seemed to have been fixed.
I went to MindWanderer/code-challenges/completed.  Yay!  That worked.  Then I went back to MindWanderer.  Huh, that now also shows my completed challenges as well.
I played around with different usernames, as well as :username/code-challenges/authored and it looks like some sort of caching issue.  After an API call for a user, for several minutes, all calls for any data regarding that user return the same thing.  It's server-side caching; if I make a call on one machine at one IP address, a different machine at a different IP address returns the same data.  It seems to clear after several minutes of inactivity.

Caching issue has been deployed. Thanks.


Wrong defaults in pinout diagram?

In the pinout diagram (PocketBeagle_pinout.png), do the dotted lines indicate the default mode? If so, the PRU defaults are wrong (P1_29/31/33/35 and P2_28/30/32/34).
I checked the latest Stretch IoT build (Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l GNU/Linux) and these pins come up in GPIO mode, not PRU.

@RobertCNelson can you make sure the default modes match the silkscreen in all of the images? The device tree I provided made "default" be the mode that is documented as the default. This will help with many newb issues.

@shirriff and @jadonk correct pinmux's should now be avaialbe in:
4.4.91-ti-r138 (building)
4.9.67-ti-r82 (building)
4.14.4-ti-r15 (building)
4.14.4-bone7 (building)
&
4.15.0-rc3 (sunday)

and the matching config-pin will be:
bb-cape-overlays_4.4.20171207.0-0rcnee1

https://github.com/beagleboard/bb.org-overlays/commit/0013331fd0fe49b90af5a57944ef854283ab1d70
Regards,


Update Posts “test-post”

Automatically generated by Netlify CMS

👷 Deploy Preview for shimmering-marigold-4f5b4a processing.

Name
Link

🔨 Latest commit
45f436badbea953bbbf9aa1b67055bbb059f7030

🔍 Latest deploy log
https://app.netlify.com/sites/shimmering-marigold-4f5b4a/deploys/633d90d31c3e210008d6231a


utc_datetime Error

 %Inspect.Error{message: "got UndefinedFunctionError with message \"function Inspect.DateTime.inspect/2 is undefined (module Inspect.DateTime is not available)\" while inspecting %{__struct__: DateTime, calendar: Calendar.ISO, day: 27, hour: 4, microsecond: {152960, 6}, minute: 50, month: 5, second: 36, std_offset: 0, time_zone: \"Etc/UTC\", utc_offset: 0, year: 2017, zone_abbr: \"UTC\"}"

when i use dev environment i am getting date with utc_datetime perfectly, but when i am generating release and running , i am getting above error while getting utc_datetime in ecto .

Use of utc_datetime requires Elixir 1.3. What's the version you use in the release?
Please fill in the issue template. It saves us both time going back and forth on basic questions like this.

Yes, please open up a new issue where the issue template is correctly filled. Thank you.


Clangd 16.0.6 and newer fail to autocomplete method arguments

Suppose you have this header (fun-args.hpp):
class Test
{
public:
    void fun(int a, int b, int c);
};

And this implementation file where I'm trying to implement fun:
#include "fun-args.hpp"

void Test::

When I finish writing that, I get a suggestion for the function to be completed with arguments, and I would expect that selecting it I would get the arguments autocompleted like:
#include "fun-args.hpp"

void Test::fun(int a, int b, int c)

But since Clangd 16.0.6 this doesn't work anymore and it stops at writing void Test::fun (Clangd 15.0.7 was working).
Logs
clang-16.0.6-logs.txt
System information
Output of clangd --version:
clangd version 16.0.6
Features: linux
Platform: x86_64-pc-linux-gnu

Editor/LSP plugin: Vscode with the clangd extension
Operating system: Arch Linux

The change that regressed this is https://reviews.llvm.org/D137040, though note that the previous behaviour was accidental (clangd mistakenly thought you're writing a call, and the current behaviour when completing a call is to provide placeholders for the arguments that include the parameter type and parameter name; https://github.com/clangd/clangd/issues/1252 is on file to revise this to drop the type since it just gets in the way for calls).
The proper fix here is to have clangd detect when you're writing a definition/declaration rather than a call, and have a dedicated behaviour there that is appropriate for definitions/declarations (which would probably include inserting the signature without making each argument a placeholder); see also https://github.com/clangd/clangd/issues/753.


Fix DeregisterCriticalServiceAfter configuration on ttl healthchecks - Consul

DeregisterCriticalServiceAfter property doesn't set properly if ttl healthcheck enabled.
I think it is not correct, because DeregisterCriticalServiceAfter feature work pretty well with ttl healthchecks too.
Note: this pr modify default behaviour and can broke backward compatibility a bit. I don't know if it is critical or not =)

/azp run

We need to fix this in a way to fix #319. I'll add these changes.


Change .json() to .text

Change .json() to .text because not all API's and website's return as json

yeah this is a totally fair criticism. I was planning on making this a CLI arg in the future, but I can't think of a good name for it.

I don't think it should just be outright changed to .text though, as most places where you would expect to use autorequests would be in an api where json data is returned, so the option of having both sounds like the best of both worlds to me.

done!


appears to be only scanning half the inventory?

The scanning appears to be only happening to part of the display or something else is wrong? i have the resolution set to 1080 with text at medium, i tried in windowed and windowed fullscreen, it  will show the overlay for all the items equipped in the slots-helm,armor,gloves,pants,boots,weapon.
then the inventory slots only the first row slots get scanned (minus last 2 all the way to right). if i put an item in the first upper left slot it shows the overlay, then i move that item to the next slot over, it shows the overlay still. but move it to the last slot  and the overlay no longer will show.
same happens if i move the item to the middle row or bottom in the inventory.
any idea what could be happening?
EDIT: oh i also tried messing with resolution scaling and messing with windows scalling even though windows scalling should have no affect on games.

heres a short video showing whats happening.
https://www.youtube.com/shorts/dk_CSgygdh0

Ignore the bad paint skills but it works like this:

The capture area used to look for tooltips is based on your current mouse position and the tooltip width.
The tooltip width for 1080p should be set to 380. You can set the tooltip width here:

oh i also tried messing with resolution scaling and messing with windows scalling even though windows scalling should have no affect on games.

Maybe not on the game but it will mess up the mouse coordinates and capture area of this app.
And one last question. Do you use one or two monitors? If you have two it makes it easier for you to find the problem.

Heck yea, i lowered the width to 380 and restarted the app, it captures the whole inventory now. did i miss this part in the instructions/wiki? i searched to see if this was mentioned anywhere but only thing i seen was the main readme says the width for 1440 is 500 but didnt say anything about other resolutions.
and no no second monitor so couldnt have used it to help me troubleshoot that :(

Glad that is working now!
The recommended settings are mentioned when you download a system preset:

But I'll update the readme to make it more obvious.


Why use DataMagic as the YML loader?

Hey @cheezy,
Would you be open to a PR which switches page_navigation to use FigNewton, or YMLReader directly. By using DataMagic we take on Faker as a dependency which adds unnecessary weight.
Best,
Justin

If we can merge the symbol support PR to FigNewton, this would all come together nicely.

While this topic is somewhat on people's mind, is there any example at all that shows how to use a YAML file with this page navigation functionality? I see a unit test for it but it makes little sense in terms of the usage. And most things I try seem not to work.


Make the Readme file beautiful and clean

@Anu27n Sir please assign this issue to me , i would love to work on this .

@PRAteek-singHWY  Assigned.

@PRAteek-singHWY Assigned.

can u please tell me all these issues are also under the Hactoberfest right .
they will count towards my PRs in hacktoberfest right Sir

Hi @Anu27n Can you Please assign this to me under Hacktoberfest tag.

@harshitkumargupta  Assigned

@PRAteek-singHWY  yes it does.

@Anu27n can you assign me this under hacktoberfest tag as well?

@anant-jain01 assigned please star the repo jai jinendra 😅

thank you bhai
jai jinendra
😂😂


sampler.sample cannot be used to resume chains

General information:

emcee version: 3.0.rc2
platform: Linux 5.2.8, Python 3.7.4
installation method (pip/conda/source/other?): add path to local repo

Problem description:
I'm integrating emcee into one of my packages. It is important that chains can be resumed. This works well if using sampler.run_mcmc(None, n), but fails with iterating over sampler.sample(None, n).
Actual behavior:
ValueError: incompatible input dimensions
Minimal example:

import emcee
import numpy as np

def log_prob(theta):
    log_prior = -0.5 *  np.sum((theta-1.0)**2 / 100.0)
    log_prob = -0.5 * np.sum(theta**2) + log_prior
    return log_prob, log_prior

coords = np.random.randn(32, 5)
nwalkers, ndim = coords.shape

filename = "tutorial.h5"
backend = emcee.backends.HDFBackend(filename)

sampler = emcee.EnsembleSampler(nwalkers, ndim, log_prob, backend=backend)

max_n = 1000

sampler.run_mcmc(coords, max_n, progress=True)

new_sampler = emcee.EnsembleSampler(nwalkers, ndim, log_prob, backend=backend)

new_sampler.run_mcmc(None, max_n, progress=True)    # works :)

for _ in new_sampler.sample(None, iterations=max_n, progress=True):  # does not work :(
    continue

Many thanks for this great package!

Turns out, the iterations= keyword is necessary... closing.

Thanks for this! There are some (perhaps weak) reasons why that doesn't work in the current implementation, but there is an easy workaround that could be integrated more seamlessly:
new_sampler = emcee.EnsembleSampler(nwalkers, ndim, log_prob, backend=backend)

state = new_sampler.get_last_sample()

for _ in new_sampler.sample(state, iterations=max_n, progress=True):  # should work now!
    continue

Hope that helps!

It does, thanks a lot! I'm keeping this open, but feel free to close it.


Add an Android Device (x86 first, then ARM)

API 28+ needs to be used.

x86 in the works https://github.com/Devsh-Graphics-Programming/Nabla/pull/28

Done in Nabla


add Step Functions examples

Description of changes:
I added two examples for AWS Step Functions:

startExecution
stopExecution

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution under the terms of your choice.

Hey, thanks for submitting this example. We currently have our examples in three separate GitHub repositories and are working on consolidating them. I'm going to leave this open until that consolidation is complete and then I might need you to re-submit it to a different repo. I'll reply with an update when we get there.

Thank you for your patience while we consolidated our examples. They are now mastered in the awsdocs/aws-doc-sdk-examples repository. If you want to, you can open a pull request there for this change, or let me know if you like me to do it. Thank you!

Thank you for your patience while we consolidated our examples. They are now mastered in the awsdocs/aws-doc-sdk-examples repository. If you want to, you can open a pull request there for this change, or let me know if you like me to do it. Thank you!

I will do it at least I can say that I have a contributed

@jdisanti I did it
https://github.com/awsdocs/aws-doc-sdk-examples/pull/2762


Just question by my interest.

Did your formatter built in JS by Mozilla?
The function name are absolutely same. I surprised.

Interesting... I have no idea.
Could you show us where exactly?


dll mode for image loader library especially tiff?

First, thanks for making vliv opensource. Previously I've been using libvips-based viewer to view tiled/pyramid tiff.
Please consider to have libtiff as dll instead of statically linked to main plugin.
nowadays libtiff been adding compressor every few years, who knows whats next. It would be easier for end user to just replace libtiff with updated one. At the moment I'm really interested in tiled webp inside tiff and vliv don't support it although it does support webp.

this is the example of tiff that I made with vips
https://archive.org/download/megamap/megamap-rbga-1px1km-lq.tiff

nevermind, I have compiled vliv with vs2008 on windows xp with updated tiff.
but if you did I'd be very grateful
thankyou

I did not know libtiff was updated for webp support, hopefully you have been able to recompile the internal plugin with webp in  tiff support...
My work version in is 4.0.3.

Vliv 2.5.8 is built with webp in tiff support, so your image is opening correclty. Still using libtiff 4.3.0 though...

Works on XP! I just need to convert some lines to c89 but it compiled with vs2008. Thanks for your update, I love small and neat software like yours!
Although I dissapointed that webp isn't quite good for GIS... so many detail crushed compared to jpeg at the same size. But its lossless mode is by far the best that Tiff currently has.

hey maybe you could merge webp plugin into internal plugin to make it linked all libraries efficiently? currently 2.5.8 missing webp (standalone) plugin.
and just a little nitpick, since vliv released as 32-bit you might want to enable bigram mode "/LARGEADDRESSAWARE" to linker flag, so it could open huge non-tiled jpeg file?
I tested it but vliv seems struggling when panning the image, maybe it's by design? considering vliv do things on the fly, unlike vips that cache non-tled file to %TEMP% first.

Yes webp and non internal plugins are proof of concept and might not be delivered (but should be compilable from vlivplugins repo).
It should be quite simple to share libraries (libwebp) in this case.
What is important to me is specific TIFF support (tiles/strips/pyramid) and I have never really worked on making it load standard TIFFs. In this case it will effectively try to load whole image as other viewers.
I have sample TIFF that go far beyond memory loadable, at 120 gigabytes and 720 gigapixels so /LARGEADDESSAWARE would not help. Only tiling and pyramid allows display of this kind of image.
I would consider any large TIFF not tiled (such as Nasa's Webb images) bad practice (why don't they tile them ?) ;-)

I see, good point then :)

When I started writing Vliv more than 20 years ago it was an exercise in C and core win32 so I am not that surprised it still runs on XP !
Nice projection image you have, I also used Visible Earth images (Blue Marble) quite some time ago...

I released 2.5.9 with Webp support in internal plugin and /LARGEADDRESSAWARE

I am curious about the projection you used, I guess some kind of equal-area one, but I am clueless.

I've uploaded the pyramid tiff here https://archive.org/details/megamap
sadly can't upload the lossless version (480mb), seems too big for my isp


Perf: Remove runtime injection from runtime

What changed / motivation ?
The inject function has been removed from the main export of @stylex/stylex. Now the inject function can only be used by manually importing @stylex/stylex/lib/stylex-inject.
The Babel plugin has similarly been updated to import the inject function from the new location when runtimeInjection is turned on.
Also, runtimeInjection now accepts a string or {from: string, as: string} object to be able to override the inject function module location.
Additional Context

Tests have been updated to reflect the changes. The updated snapshots will show what has changed.
NOTE: The Webpack plugin is currently inlining the stylex-inject module in the generated code in the snapshot test. Trying to configure Webpack to not do that is causing strange errors.
Pre-flight checklist

[x] Performed a self-review of my code

We should probably be checking the size of the bundled runtime in the CI task. It hasn't been showing the contribution of inject or styleq, so the size savings aren't showing up in the results

We should probably be checking the size of the bundled runtime in the CI task

I am looking into that. The numbers above are by using browserify, terser and gzip. I expect using rollup might squeeze this down a bit more.

oh actually it looks like styleq is inlined in lib/stylex.js, so we're good. the CI workflow already minifies and gzips.

2.29 kB

This is in the ballpark of the size I got in local testing, but the comparison is still wrong since this PR cut the size in half.
Will figure this out later.

It's just because we don't inline ./stylex/lib/StyleXSheet.js into the main export of the package - the size of that file is listed separately in the "unchanged" files table. If we had size-diffed a production rollup bundle, we'd have seen the 3K reduction from inject not being imported anymore.


Can I use this library with freeRTOS?

Can I use this library with freeRTOS?

Yes you can simply just include FreeRTOS and just call the ThingsBoard library in a seperate task. Just ensure that you call loop() and therefore the task relatively often, because that will process incoming messages over MQTT.

Thanks, I'd been doing that and works fine!


_1password-gui: 8.9.8 -> 8.9.10, 8.9.10-1.BETA -> 8.9.12-4.BETA

Description of changes
Update 1password-gui
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

_1password-gui
_1password-gui-beta


Messages in controlling channel should not be processed by moderation modules

I have the message length module on for pajbot (RoboWeest) and found that when running a command on streamelements in the controlling channel that is too long, streamelements will still get timed out despite the violation not happening in the bot's connected channel perse: https://i.nuuls.com/UPvED.gif

Honestly this is such a low priority issue that it's not worth investing work into this, especially given that pajbot has been moved into maintenance mode. I'll close the issue for now. If somebody wants, they can of course send a PR to implement this regardless.


merge from main into obcloud 24v5

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Additional documentation e.g., usage docs, etc.:

lgtm


Apiservices fail to initialize on Minikube

I am trying to get KubeDB running on Minikube without a VM, on WSL 2. During the installation, I get the following output:
checking kubeconfig context
minikube

checking whether extended apiserver feature is enabled

KUBEDB_DOCKER_REGISTRY=kubedb
KUBEDB_ENABLE_ANALYTICS=true
KUBEDB_ENABLE_APISERVER=true
KUBEDB_ENABLE_MUTATING_WEBHOOK=true
KUBEDB_ENABLE_RBAC=true
KUBEDB_ENABLE_VALIDATING_WEBHOOK=true
KUBEDB_IMAGE_PULL_POLICY=IfNotPresent
KUBEDB_IMAGE_PULL_SECRET=
KUBEDB_NAMESPACE=kube-system
KUBEDB_OPERATOR_NAME=operator
KUBEDB_OPERATOR_TAG=0.8.0
KUBEDB_PURGE=0
KUBEDB_RUN_ON_MASTER=0
KUBEDB_SERVICE_ACCOUNT=kubedb-operator
KUBEDB_UNINSTALL=0

Wrote ca certificates in  /home/borre/cubonacci
Wrote server certificates in  /home/borre/cubonacci
deployment.apps/kubedb-operator configured
secret/kubedb-server-cert configured
service/kubedb-operator unchanged
apiservice.apiregistration.k8s.io/v1alpha1.validators.kubedb.com configured
apiservice.apiregistration.k8s.io/v1alpha1.mutators.kubedb.com configured
serviceaccount/kubedb-operator unchanged
clusterrole.rbac.authorization.k8s.io/kubedb-operator reconciled
clusterrolebinding.rbac.authorization.k8s.io/kubedb-operator reconciled
rolebinding.rbac.authorization.k8s.io/kubedb-server-extension-server-authentication-reader reconciled
clusterrolebinding.rbac.authorization.k8s.io/kubedb-server-auth-delegator reconciled
clusterrole.rbac.authorization.k8s.io/kubedb:core:admin reconciled
clusterrole.rbac.authorization.k8s.io/kubedb:core:edit reconciled
clusterrole.rbac.authorization.k8s.io/kubedb:core:view reconciled
validatingwebhookconfiguration.admissionregistration.k8s.io/validators.kubedb.com unchanged
mutatingwebhookconfiguration.admissionregistration.k8s.io/mutators.kubedb.com unchanged

waiting until kubedb operator deployment is ready
waiting until kubedb apiservice is available
timed out waiting for the condition
KubeDB apiservice v1alpha1.validators failed to be ready

When I check the status of the apiservices using kubectl get apiservices, I see:
NAME                                   SERVICE                       AVAILABLE                      AGE
[...]
v1alpha1.mutators.kubedb.com           kube-system/kubedb-operator   False (FailedDiscoveryCheck)   1m
v1alpha1.validators.kubedb.com         kube-system/kubedb-operator   False (FailedDiscoveryCheck)   1m
[...]

The output of kubectl describe apiservice v1alpha1.validators.kubedb.com is:
Name:         v1alpha1.validators.kubedb.com
Namespace:
Labels:       app=kubedb
Annotations:  kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"apiregistration.k8s.io/v1beta1","kind":"APIService","metadata":{"annotations":{},"labels":{"app":"kubedb"},"name":"v1alpha1...
API Version:  apiregistration.k8s.io/v1
Kind:         APIService
Metadata:
  Creation Timestamp:  2019-06-26T14:46:44Z
  Resource Version:    5988
  Self Link:           /apis/apiregistration.k8s.io/v1/apiservices/v1alpha1.validators.kubedb.com
  UID:                 37ac1de2-9821-11e9-83c7-6226b2628906
Spec:
  Ca Bundle:               LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUN1RENDQWFDZ0F3SUJBZ0lCQURBTkJna3Foa2lHOXcwQkFRc0ZBREFOTVFzd0NRWURWUVFERXdKallUQWUKRncweE9UQTJNall4TlRNNU5ERmFGdzB5T1RBMk1qTXhOVE01TkRGYU1BMHhDekFKQmdOVkJBTVRBbU5oTUlJQgpJakFOQmdrcWhraUc5dzBCQVFFRkFBT0NBUThBTUlJQkNnS0NBUUVBd0NBRzROb1pkalRiTUxPczBOeUV0L3RkCm4ydUViVkNncXUzRkI3SGdmRTM2NGl2Vk5vK3cweDU3aEIzWDk0dlYvWkRSVmVEUVovc1hIT09mUmc3NE8weloKT3JIU0ZtYXREZzg1cmlHMlYxd2xPdi9GdXNVNHVKSTRRMU03emRmQ0ZzNmdoVWV3eDM3SThyRFo5L1NERFM0SgppWHduZlc3M2Q5aXhURFJ3eHdPUkdGNjBDTTdRd1ljdG1IaUdFZU5HczdPSUNOTHdzY3YyYklGQVJjMk9GNzh6CnNHMmRrOUEwUlVTM3dPZTNlVkpFSDhWbGl5WmdoeVJkdy9GZHNvT2hWT1gvbzBsK0pRcWc1T1ZCbjdpUEhoY0UKdUtMc0E0eGdrcGp5YVkzdG5iRFVUeG0yZGY2RUxpS3ZYcjlZMzhyZmhkRHNBeWYvSVp4ZWJzd1NsZ0tUbXdJRApBUUFCb3lNd0lUQU9CZ05WSFE4QkFmOEVCQU1DQXFRd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBTkJna3Foa2lHCjl3MEJBUXNGQUFPQ0FRRUFCb2pSQW9FMVFFdHlkdUtJZWtOZ2dsRkM1S1E5VlpuYnJlWCtvbkRWZVpaNlFpYzkKQW9rMTd2NlVxQVdsYzR0aDZpOElZM3REZitJeXFyY1o5WVBkOC9nQ1lBc0FDTzBidEpjVnZwU3JSazBoT0o5egpETVIyTm1wRHBNNFZiRlNhdWtpR2lxaTY1cFlBTUpjZXJYK0duQ29rU0dxc0YxQmxnTjQ4bkZBbk9SWlJsVFB6CjdkMVQ4Tmt6QXYyODNramNNVHlYbDlETUp1OWV0WldhakN2ZVpLdEVJMy83WEMvYnVxekIvQnRWZlpNZTJ3MlgKTG95YlRxQnBudUZKYkdHTlNNcEZRMWQvYjZ2OVhDM09vNWZ6b3hpMnVJT1NYNWRPWjdUalduRmFTWlEwK1Qzbwp4b2RZMGx3WmN4VHJqT3J1UXhhZ3FDMkd1OUJlY3ZqMC9FUXFHZz09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
  Group:                   validators.kubedb.com
  Group Priority Minimum:  1000
  Service:
    Name:            kubedb-operator
    Namespace:       kube-system
  Version:           v1alpha1
  Version Priority:  15
Status:
  Conditions:
    Last Transition Time:  2019-06-26T14:46:44Z
    Message:               no response from https://<IP_ADDRESS>:443: Get https://<IP_ADDRESS>:443: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
    Reason:                FailedDiscoveryCheck
    Status:                False
    Type:                  Available
Events:                    <none>

Any help would be greatly appreciated

To pull the salient detail over from ^

I can't speak for OP, but for my part this seems to be downstream of #504 #655

This is to say it seems to be a TLS issue and adding --set apiserver.healthcheck.enabled=false to helm chart install seems to at least unblock the install.
You know... if I had to guess this might be as simple as a race in TLS generation vs the rest of the initialization rolling
Doing:
$ kubectl port-forward -n kube-system kubedb-operator-d8756579b-xmk9q 8443
# then
$ openssl s_client -connect <IP_ADDRESS>:8443 | openssl x509 -noout -text

I see a Not Before: Nov  7 21:51:54 2019 GMT where my install was done LAST DEPLOYED: Thu Nov  7 14:55:55 2019 – so like that implies the cert is backdated a few minutes ... but is minikube coming up with a correct clock immediately?
idk just a theory

(It appears I started the minikube cluster in question, rapidly iterating to test this, about 14:49 (21:49 UTC) )

I have met similar issue on a cluster deployed with Kubespray

I'm running into this issue with a cluster deployed with kops, kubernetes v1.15.10 and kubeDB 0.12.

Same here on GKE clusters 1.15.11+ and latest kubedb version 0.12 and 0.13.0-rc-0 installed with helm or installer script.

I am also running with same issue GKE version 1.14.10-gke.36 and kubedb latest version 0.13.0-rc-0 tried installing with both helm and installer script.

My issue was with firewall rule of kube master node, I added port 8443 on firewall then mutator and validator apiservices worked.

Same issue here, GKE 1.14.10-gke.36 and kubedb version v0.13.0-rc.0. The issue occurs if GKE is configured as a private cluster

Same issue here, GKE 1.14.10-gke.36 and kubedb version v0.13.0-rc.0. The issue occurs if GKE is configured as a private cluster

Did you find any workaround other than not using a private cluster (which is not an option for our security requirements)? Why would a private cluster prevent communication to pods within the cluster?

This appears to be a VPC firewall issue because the port is not 443: https://github.com/kubernetes/kubernetes/issues/79739


listMyDidsWithMeta API specification is different from implementation

As I pointed out in #2238 , listMyDidsWithMeta API returns json which includes tempVerkey field but  https://github.com/hyperledger/indy-sdk/blob/master/wrappers/nodejs/README.md does not say so.

Link to description: https://github.com/hyperledger/indy-sdk/blob/master/wrappers/nodejs/README.md#listmydidswithmeta--wh----dids


CRDs in git release differ from CRDs rendered by karpenter-crd helm chart

Description
Observed Behavior:
Rendering the CRDs via kustomize results in a different manifest than rendering with helm.
The CRDs installed via the helm chart remove the post-install webhook (cf. #6837).
The CRDs in the Karpenter release still contain the webhook.
Expected Behavior:
CRDs should be the same for both within the same release.
Reproduction Steps (Please include YAML):
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
  - https://raw.githubusercontent.com/aws/karpenter-provider-aws/v0.37.2/pkg/apis/crds/karpenter.sh_nodepools.yaml
  - https://raw.githubusercontent.com/aws/karpenter-provider-aws/v0.37.2/pkg/apis/crds/karpenter.sh_nodeclaims.yaml
  - https://raw.githubusercontent.com/aws/karpenter-provider-aws/v0.37.2/pkg/apis/crds/karpenter.k8s.aws_ec2nodeclasses.yaml

helm template karpenter-crd oci://public.ecr.aws/karpenter/karpenter-crd --version 0.37.2

Versions:

Chart Version: 0.37.2
Kubernetes Version (kubectl version): v1.30.2-eks-db838b0

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

@raidlman - you may wish to follow the thread @ #6847

The CRDs from the karpenter-crd chart are able to be templatized as karpenter helm chart cannot. You should use the karpenter-crd as the mechanism to manage your CRDs.


[FEATURE REQUEST] Add transparency to Icons

Feature Request
Describe the solution / feature you'd like
Add transparency to Icons.
At higher brightness, the black background in the icons starts to appear as a gray background (screenshot below).
Is it possible to make the black background transparent (always black).
Then the icons will look more harmoniously on the matrix at any brightness.
Judging by the documentation and source code ESPHome supports icons with transparency, even in the RGB565 icon type used.
https://github.com/esphome/esphome/blob/dev/esphome/components/image/__init__.py#L321-L325
0x0020 as I understand it is RGB - [0,0,32], i.e. by enabling transparency we should get completely black color for all colors below [0,0,32].
Additional context

Or maybe you can do like the good old days, add a transparency property to the icon, and use the top left pixel as the transparent color.

I eee the problem but as you stated  it's a "problem" of the ESPHOME components, a work around is editing the icons in gimp and change all transparent part to black.

Actually, it may not be an ESPHome problem.  ESPHome relies on Pillow to transform the images, doesn't it?

it's a "problem" of the ESPHOME components

As far as I understood the source code, ESPHome when loading a picture, if the transparency property is specified, processes it and discards everything below a certain level, makes rgb = 0, and as a result it is black on the address LEDs, i.e. the diode is not lit. We load the picture as a stream using PIL and directly publish the picture to ESPHome and without specifying the property - has transparency.

Oh and if you want that in a .cmd or .bat file, be sure to change all % to %% yeah?

How's this for a solution? Use ImageMagick to transform all transparencies to black...

Does this solve the problem of the matrix displaying gray instead of black at hight brightness?

I use everywhere LaMetric icons from the site, it would not be bad if during the build they would be downloaded and cached in some directory (interesting idea in my opinion). :)
In principle it is not difficult to download them all and process them with ImageMagick, but it seems to me that this should be solved by ESPHome settings, especially since it supports transparency and we can always convert them before packing them into an ESPHome resource.

Maybe this is where you should add code like ESPHome does?
https://github.com/lubeda/EspHoMaTriXv2/blob/main/components/ehmtxv2/__init__.py#L364
rgb = (R << 11) | (G << 5) | B
if rgb == 0x0020:
  gb = 0

Then the code of loading a picture, will take into account the transparency, as it is done in ESPHome, well, or to each icon to add a sign of transparency, and then change the code to such a code:
rgb = (R << 11) | (G << 5) | B
if transparent:
  if rgb == 0x0020:
    gb = 0

Please check the 2023.8.0 version

That's great! I hope this solves this problem. I'll have to upgrade to 2023.8 and check it out. Thanks a lot!
PS: When can we expect the 2023.8 release? :)

I was just digging into Pillow and found that RGBA is the key.  Thanks, lubeda!
Sidenote that although we can still use LaMetric as a source, some of my research found that the style of conversion I show above (converting all transparent pixels to a uniform color) help compress the image since apparently some pictures may contain different color values for transparent pixels... Although this might not seem like much of a difference, it can add up - especially in compression - and this could help @andrewjswan in his quest for >100 icons.
I have 28 8x8 GIFs (all animated):
Before ImageMagick: 10268 bytes
After ImageMagick: 10222 bytes
I tested by putting them in a normal compression ZIP file (with WinRAR):
Before ImageMagick: 9065 bytes
After ImageMagick: 8749 bytes
So, maybe only a 3% savings overall, but still... something.  I imagine that due to the way compression works, the more pictures you have, the more significant the savings.

in his quest for >100 icons.

I'm still on an older version, so I have 90 of them, but I don't want to increase them much, for example duplicate weather icons, for weather forecast icons, so I want to use them on different screens. But I can't do that yet.

in version 2023.08, the highlighted transparent background on some icons has disappeared, it's super! But for example there is also a background on this icon https://pixelit .bastelbunker.de/images/543.gif is it possible to fix it in the same way?

https://github.com/lubeda/EspHoMaTriXv2/assets/34610364/d99a8a0b-43cb-4d5c-884f-22df39d01a53

Changed the threshold, so this shows more black, but all scaled images may cause problems, e.g. inside the "D" there are some pixels not black but dark blue.


GridModel option to show cell focus

Fixes #946
Tweak to also avoid (existing) shifting on right-aligned focused cells
Lighten up grid row borders in general if shown

Note there is a corresponding branch in Toolbox to add a new switch to our sample grids and DRY that up a bit.  They should be merged together if looking good.

I admit that renaming showHover does not make much sense in the light of then choosing showCellFocus as this new prop.  I dunno - something about showHover seemed like it was not quite clear/right at the time, but I'm having a hard time justifying the rename now and would be happy to keep as it was - but still move to the gridModel vs. a grid prop.


Add file permission and ownership tests for install script

We should verify that all the files created by the install script have the right ownership and permissions. The lack of these has already caused bugs via unrelated changes. For example: #816

[x] System config file (#819)
[ ] User config file
[ ] File storage
[ ] Extension credentials directory

Closing in favor of https://github.com/SumoLogic/sumologic-otel-collector-packaging/issues/90


Question regarding coordinates of SceneGlyphItemBlock

I am trying to export pdfs with highlighted text from my remarkable in a way that allows me to have the highlights show up as  annotations in a reference manager i.e. Jabref. I already managed to extract the highlights with rmscene (Thank you very much for your work on this by the way!) But I am struggling to understand how to interpret the coordinates  I get from:
with open(
    "result/fe28f8d6-82d7-4ee2-a1df-0c6cbf1a1785/73efd3f4-f6b9-43c8-9507-db728a545848.rm",
    "rb",
) as f:
    result = [
        block for block in read_blocks(f) if isinstance(block, SceneGlyphItemBlock)
    ]

x = result[0].item.value.rectangles[0].x
y = result[0].item.value.rectangles[0].y
w = result[0].item.value.rectangles[0].w
h = result[0].item.value.rectangles[0].h

The resulting values I got where the following:
x=-777.0586776928369,
y=154.8036158772884,
w=518.3922791561563,
h=113.49999618530273
And I don't quite get how I can translate that into the coordinates I need for generating the annotations via pdf-annotate.
I would assume that the x and y value represent the coordinate of the top left(?) corner of the highlighted area, while w is representing the width and h the height. What I don't understand is why the x value is negative or how the coordinate system works in the remarkable files. Where is it centered, how do I find out the total size, etc.
Maybe you could give me some pointers?

from this, it looks like the origin is the center point of the page
https://github.com/ricklupton/rmc/blob/main/src/rmc/exporters/svg.py#L52
so a negative x value represents the left side of the page... but I'm not totally certain this is right, since the remarkable templates are 1404×1872px and -777 would be off the x=-702 margin... maybe this is excluding the menubar width?

I can confirm that x=-702 is the top-left of the ReMarkable screen. You can go lower than -702 (and higher than 701) if you expand the page by swiping to the left/right. Though I don't think that's the case for your notebook, @Joogle?
There are still some unknowns about the coordinates. Although I do think @ricklupton knows more about this than I do. For instance, if you have written text to the page with the text tool, all coordinates of everything on the page gets shifted.
I also recall there being a block having x coordinate offsets that might affect the position of other blocks on the page, although I genuinely have no idea how that one works. I also don't see it in the rmc rendering logic. After some searching, it's the TreeNodeBlock: https://github.com/ricklupton/rmscene/blob/10e5e4e896c1c5ead47c34998967a3951e06a735/src/rmscene/scene_stream.py#L148
I don't recall the menubar affecting x-coordinates.

So, first of all, thanks for the input everyone!
I finally got around to testing stuff for a bit.
The document I am using is a simple .odt file in A4 format, that I converted to .pdf.
I tried what @ricklupton suggested and the lines seem to use the same coordinate system as the highlight rectangle.
However the size of the coordinate system seems to be bigger than the standard remarkable one and also seems to have a different center than described.
On the X-Axis I have coordinates from approximately  -990 to 990 while the coordinates on the y axis seem to range from somewhere around 10 to 2630. (I tried to approximate those with dots I made with the ballpoint pen, just in case that's relevant) So I would assume that the center point in the pdf would be in the middle of the top of the page.
That's not what I expected, but maybe I misunderstood what you were saying.
In any case in order to work with the coordinates it would be very helpful to get the actual dimensions of the page, is there any way to do that?

The dimensions of the page are calculated based on the minmax positions of all items in the scene. It's not available as a pre-computed number anywhere as far as I have seen.
I think ReMarkable does something to fit the PDF onto the screen.
A4 = 210x297mm = aspect ratio of 70/99
RM = 1404x1872px = aspect ratio of 3/4
The result is 1990x2630px ~ish
So the RM was scaled
1990 / 1404 = 995/702 ≃ 99/70
2630 / 1872 = 131.5/93.6 ≃ 99/70
These values make sense given the aspect ratio of A4.
So to fit a PDF onto the RM, we need to compute
pdf_width = 210
pdf_height = 297
aspect_in = pdf_width / pdf_height
RM_WIDTH = 1404
RM_HEIGHT = 1872

notebook_width = RM_WIDTH / aspect_in
notebook_height = RM_HEIGHT / aspect_in

print(notebook_width, notebook_height) # 1985, 2647

This is similar to what you measured.
So the coordinates stored in the annotations are probably not scaled by the inverse aspect ratio (or, I guess the portrait aspect ratio)

I managed to get it working with the approach you described @Azeirah - Thank you!
The following produces the input PDF with a rectangle around the highlighted text. I didn't yet manage to have the annotation show up in Jabref, but that's a different problem.
pdf_width = 210
pdf_height = 297
aspect_in = pdf_width / pdf_height
RM_WIDTH = 1404
RM_HEIGHT = 1872
notebook_width = RM_WIDTH / aspect_in
notebook_height = RM_HEIGHT / aspect_in

# With x,y,w,h coming from the SceneGlyphItemBlock
x1= x + (notebook_width/2)
y2 = notebook_height - y
x2 = x1+w
y2 = y1-h

from pdf_annotate import PdfAnnotator, Location, Appearance
a = PdfAnnotator("input.pdf")
a.set_page_dimensions((notebook_width, notebook_height), 0)

a.add_annotation(
    "square",
    Location(x1=x1, y1=y1, x2=x2, y2=y2, page=0),
    Appearance(stroke_color=(1, 0, 0), stroke_width=5),
)
a.write("result.pdf")


kernel: userspace: aligned memory allocation for dynamic objects

This allows allocating dynamic kernel objects with memory alignment
requirements. The first candidate is for thread objects for x86
and x86_64 where saving/restoring SSE/FPU registers require strict
alignment.
Fixes #29589
Fixes #29629

Looks like there is some potential conflict with #30363 which has been open for a while in preparation for dynamic pthtread stacks (#29029, which has been there for quite a long time too).
@dcpleung - I wonder if this ticket could focus more on dynamic kobject creation while #30363 could focus more on allocation.
Please let me know if you can think of a better alternative.

Looks like there is some potential conflict with #30363 which has been open for a while in preparation for dynamic pthtread stacks (#29029, which has been there for quite a long time too).
@dcpleung - I wonder if this ticket could focus more on dynamic kobject creation while #30363 could focus more on allocation.
Please let me know if you can think of a better alternative.

Once your PR is merged, I can rebase this on top of your changes.

On Tue, 12 Jan 2021, Christopher Friedt wrote:

return z_dynamic_object_aligned_create(1, size);

I think elsewhere that sizeof(void*) is used in place of an unspecified alignment because it's a reasonable safe default alignment.

Personally, I'd prefer using 0 when no particular alignment is
necessary. The code will already take care to return memory with the
minimum alignment for all basic types for a given platform in that case.

On Tue, 12 Jan 2021, Christopher Friedt wrote:

return z_dynamic_object_aligned_create(1, size);

I think elsewhere that sizeof(void*) is used in place of an unspecified alignment because it's a reasonable safe default alignment.

Personally, I'd prefer using 0 when no particular alignment is
necessary. The code will already take care to return memory with the
minimum alignment for all basic types for a given platform in that case.

On Tue, 12 Jan 2021, Christopher Friedt wrote: + return z_dynamic_object_aligned_create(1, size); I think elsewhere that sizeof(void*) is used in place of an unspecified alignment because it's a reasonable safe default alignment.
Personally, I'd prefer using 0 when no particular alignment is necessary. The code will already take care to return memory with the minimum alignment for all basic types for a given platform in that case.

Hm... sys_heap_aligned_alloc() with alignment 0 simply calls sys_heap_alloc() which has no minimal alignment (AFAIK). So probably better to pass a value over.

On Tue, 12 Jan 2021, Christopher Friedt wrote: + return z_dynamic_object_aligned_create(1, size); I think elsewhere that sizeof(void*) is used in place of an unspecified alignment because it's a reasonable safe default alignment.
Personally, I'd prefer using 0 when no particular alignment is necessary. The code will already take care to return memory with the minimum alignment for all basic types for a given platform in that case.

Hm... sys_heap_aligned_alloc() with alignment 0 simply calls sys_heap_alloc() which has no minimal alignment (AFAIK). So probably better to pass a value over.

Looks good - just a slight change request to have consistent naming. Are any additional tests required?

Updated the naming and alignment value.

Looks good - just a slight change request to have consistent naming. Are any additional tests required?

Updated the naming and alignment value.

On Tue, 12 Jan 2021, Daniel Leung wrote:

Hm... sys_heap_aligned_alloc() with alignment 0 simply calls sys_heap_alloc() which has no minimal alignment (AFAIK). So probably better to pass a value over.

It sure does. sys_heap_alloc() must have minimal alignment for the
platform no matter what. And I know it does.

On Tue, 12 Jan 2021, Daniel Leung wrote:

Hm... sys_heap_aligned_alloc() with alignment 0 simply calls sys_heap_alloc() which has no minimal alignment (AFAIK). So probably better to pass a value over.

It sure does. sys_heap_alloc() must have minimal alignment for the
platform no matter what. And I know it does.

On Tue, 12 Jan 2021, Daniel Leung wrote: Hm... sys_heap_aligned_alloc() with alignment 0 simply calls sys_heap_alloc() which has no minimal alignment (AFAIK). So probably better to pass a value over.
It sure does. sys_heap_alloc() must have minimal alignment for the platform no matter what. And I know it does.

Changed the value to 0. There is another issue where they reported the minimal alignment was 4, but I recalled it as 1, hence the confusion.

On Tue, 12 Jan 2021, Daniel Leung wrote: Hm... sys_heap_aligned_alloc() with alignment 0 simply calls sys_heap_alloc() which has no minimal alignment (AFAIK). So probably better to pass a value over.
It sure does. sys_heap_alloc() must have minimal alignment for the platform no matter what. And I know it does.

Changed the value to 0. There is another issue where they reported the minimal alignment was 4, but I recalled it as 1, hence the confusion.

On Tue, 12 Jan 2021, Daniel Leung wrote:

Changed the value to 0. There is another issue where they reported the minimal alignment was 4, but I recalled it as 1, hence the confusion.

Thanks. There is a 1 in z_thread_malloc() that could be turned into a 0 as well for consistency.

On Tue, 12 Jan 2021, Daniel Leung wrote:

Changed the value to 0. There is another issue where they reported the minimal alignment was 4, but I recalled it as 1, hence the confusion.

Thanks. There is a 1 in z_thread_malloc() that could be turned into a 0 as well for consistency.

On Tue, 12 Jan 2021, Daniel Leung wrote: Changed the value to 0. There is another issue where they reported the minimal alignment was 4, but I recalled it as 1, hence the confusion.
Thanks. There is a 1 in z_thread_malloc() that could be turned into a 0 as well for consistency.

Changed that too.

On Tue, 12 Jan 2021, Daniel Leung wrote: Changed the value to 0. There is another issue where they reported the minimal alignment was 4, but I recalled it as 1, hence the confusion.
Thanks. There is a 1 in z_thread_malloc() that could be turned into a 0 as well for consistency.

Changed that too.


The existence of md-sidenav-layout prevents scrolling events from being fired

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
If an app contains a md-sidenav-layout component, scrolling events are not fired.

If the current behavior is a bug,
please provide steps to reproduce and if possible a minimal demo of the problem

Here is a plunker with a md-sidenav-layout and a link to open the side nav. It also has a host listener and logs the pageYOffset to console. Be sure and scroll the page and see if you get anything in the console. I did not.
http://plnkr.co/edit/MG0JT6s04ooclNZ4Deun?p=preview
Edit the plnkr and remove or comment out the md-sidenav-layout element. Be sure to remove the closing tag as well. Clear the console. Now scroll the window, and you will see pageYOffset being logged to the console.

What is the expected behavior?
md-sidenav-layout component should not prevent scrolling events from being fired

What is the motivation / use case for changing the behavior?
Often scrolling events are needed to trigger the display of a fixed header. This is not currently possible if the md-sidenav-layout is used.

Which version of Angular and Material, and which browser and OS does this issue affect?
@angular2.0.0 RC.1
@angular2-material2.0.0-alpha.4

Did this work in previous versions of Angular / Material?
Please also test with the latest stable and snapshot versions.

Other information
(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix)

This is expected behaviour. Please note your page isn't scrolling because your content isn't actually large enough to make it scroll. What you're scrolling is the content of the sidenav. If you add content outside of the sidenav itself your body will scroll.
Cheers!

I don't believe this issue should be closed.
I've edited the plnkr to hopefully make this clearer.
http://plnkr.co/edit/MG0JT6s04ooclNZ4Deun?p=preview
First, with the app on the right side, scroll the page up and down. You will see the large 0 change. This is logging the pageYOffset value.
Now edit the app.component.html and Uncomment the stuff that is commented out:

and at the bottom uncomment:

Now, scroll the page up and down again. Notice the big 0 never changes. It is no longer logging the pageYOffset value.

That's because what you're scrolling is the content of the sidenav <md-content>, not the page. If you open the console and run $('md-sidenav-layout').scrollTop you'll see the proper scrolling position.
This is expected behaviour when you have an overflow: scroll on the content. The page isn't scrolling because the layout is taking the whole page, but isn't taller than 100%. Makes sense?


Cannot build with CUDA support on Windows.

Click to expand!
Issue Type
Support
Source
source
Tensorflow Version
TF 2.11
Custom Code
No
OS Platform and Distribution
Windows 11
Mobile device
No response
Python version
3.10
Bazel version
5.3.2
GCC/Compiler version
MSVC 14.34.31933
CUDA/cuDNN version
11.8/8.6
GPU model and memory
RTX3090 24GB
Current Behaviour?
When I'm trying to build the latest stable version TensorFlow-GPU (2.11.0) with CUDA on windows as same as we used to do, I find the following Errors

`WARNING: Cannot build with CUDA support on Windows. Starting in TF 2.11, CUDA build is not supported for Windows. To use TensorFlow GPU on Windows, you will need to build/install TensorFlow in WSL2.`

This error prevents me to set further CUDA and GPU info, as the consequence, I cannot build GPU version but only CPU version.

Standalone code to reproduce the issue
As a normal compiling procedure:

python .\configure.py

Relevant log output
You have bazel 5.3.2- (@non-git) installed.
Please specify the location of python. [Default is C:\Users\<username>\miniconda3\envs\compile\python.exe]:

Found possible Python library paths:
  C:\Users\<username>\miniconda3\envs\compile\Lib\site-packages
Please input the desired Python library path to use.  Default is [C:\Users\<username>\miniconda3\envs\compile\Lib\site-packages]

Do you wish to build TensorFlow with ROCm support? [y/N]:
No ROCm support will be enabled for TensorFlow.

WARNING: Cannot build with CUDA support on Windows.
Starting in TF 2.11, CUDA build is not supported for Windows. For using TensorFlow GPU on Windows, you will need to build/install TensorFlow in WSL2.

Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is /arch:AVX]:

Hi @Zhaopudark !
It is correct from 2.11 onwards , You have to rely on Windows Subsystem linux for GPU usage.
Alternatively, you can use Tensorflow-ml plugin through pip .
Attached relevant thread for reference.
Thank you!

@mohantym  Thanks a lot.
I have been compiling and using the latest version of TensorFlow GPU on Windows for several years, which can always have all features supported on Linux, such as AVX2, XLA .etc., and can work well with other components, such as PowerShell, MySQL, Python, Conda .etc. It can even benefit from automatic GPU overclocking on Windows.
It may a little bit disappointing that since TF 2.11 onwards, the original Windows Platform will not be supported by TensorFlow GPU.  Anyway, thanks a lot for contributing to TF and making it better and better.
Nowadays, I have totally changed to WSL2, compiling and using TF2.11 GPU successfully. In my practice, there may be approximately a 4-5% performance loss if compared to the one on the original Window. But the cost is still acceptable.
WSL2 may always be a less-than-correct and desirable choice. Because users may well choose WSL2 because some of the codes or components they need are not supported on Windows but are supported on Linux, and these users do not necessarily have two separate platforms. But from my point of view,  for most users, the code and components they want are actually supported on Windows, it just requires them to invest some of their time to learn extra Windows operation and maintenance, such as the running mechanisms, the syntax of PowerShell or CMD, and the command line mode of other tools on Windows, and then, they can find a good way to realize their desired codes or components on Windows well.
That is, the reason for not choosing the Window platform may be to save time, but if the Windows community is also active, users don't need to spend much time.
For a long time, if a user of a machine learning framework uses the Window platform, he/she will be seen as a unicorn. This is unfair because there is always someone who does not have that much money to support two separate platforms, or even three, and as a researcher, the Windows platform is naturally the most economical choice in order to cope with clerical work simultaneously. These people are even willing to spend more time learning Windows operation and maintenance for better usage of the machine learning frameworks but are often discriminated against for "why don't use Mac and Linux servers?".
Users' choices should not be discriminated against, but unfortunately, this no-longer-supporting for original Windows will make Windows users feel more discriminated, even if it is not the official intent. Even though maintaining one more platform will cost more manpower, I still hope the original Windows support will come back.
Thanks again and best wishes.

Hi @Zhaopudark !
We are not dropping windows support .
It will be just maintained by third party colloborators (Intel) considering the effort to maintain the integrity and  diversity  . Ref
You can use Tensorflow-Direct ML plugin in same windows machine as suggested in previous thread.
(Note: A Windows user myself).
Thank you!

@mohantym, thank you.
I have also tried Tensorflow-Direct ML plugin. Even though it is convenient for its simple configuration, it is still in the development phase with less than complete functionality, such as does not support  XLA, mixed precision .etc.
So, now the situation may be that it is not available in a short term to use the latest version of Tensorflow-GPU or its equivalent replacement on Windows native platform as same as the original and without performance loss.
Hope this 'painful' period will end soon.
Thank you again, and thanks to all TensorFlow contributors/maintainers for your efforts.

@Zhaopudark !
Thanks for the update and sharing your concern.
@SuryanarayanaY !
Could you look at this issue.
Thank you!

@Zhaopudark,
Your concerns regarding dropping the TF_GPU support on windows native is well noted and will be escalated to the concern team.But at present it is official from the documentation that:
TensorFlow 2.10 was the last TensorFlow release that supported GPU on native-Windows. Starting with TensorFlow 2.11, you will need to install [TensorFlow in WSL2](https://tensorflow.org/install/pip#windows-wsl2) and there is little we can do here for now at least.
I am not sure whether Windows native support can be extended in Future versions or not but also can't deny it. It's all based on requirements from community and Tensorflow Team is keenly watching the observations,concerns,inputs from community and may act accordingly. For time being as there is little we can do now shall we close this issue ?
Thankyou!

@SuryanarayanaY
Thanks for your detailed information, I will always look forward to a better and widely supported TensorFlow.
And, this issue can be closed.
Thank you.


fixed mysql syntax for multiple FROM and a JOIN

fixes #6545

PostgreSQLQueryTest::testFromWithJoin fails.

I know, will fix it later

Still fails after the fix: https://travis-ci.org/yiisoft/yii2/jobs/60672219#L194

was not a real fix, just rebased on master.

what about this one?

buildFrom() has no idea whether there is a join or not. If we want to add a check for that, this has
to be done in build() but I do not see a good way for overriding that one.

https://github.com/yiisoft/yii2/pull/6545#issuecomment-263095898


auto rename of computer objects when the hostname was changed

Checklist

[X] I have verified this is the correct repository for opening this issue.
[X] I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.
Currently the computer object name on central management is not changing when the hostname was changed. The computer is not clearly to identified.
Describe The Solution. Why is it needed?
When the chocolatey agent is polling it could send and compare / update the computer object name.
Additional Context
No response
Related Issues
No response

This is not the correct repository for this. Moving this to chocolatey-licensed-issues.


Disable OpenAPI CLI service generated tests

Description:
Disable the openAPI service generated below tests until new service changes support

testInlineRequestBodyServiceGen()
testAllOfSchemaGen()
testOneOfSchemaGen()

Suggested Labels:

Suggested Assignees:

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

Close this issue since the fix already merged with the repo.


Allow syndicators to syndicate posts by default (and ignore client setting)?

Not all Micropub clients let you choose which syndication targets to publish to (cough - Micro.blog - cough).
Should it be possible to set a syndicator plugin to always syndicate posts regardless?
What happens if a user then wants to override this default and skip syndication – not sure there’s a way to declare that syndication shouldn’t happen via the mp-syndicate-to property, only that it should.

It's tempting to deviate from the spec - I have felt that too with Celestial. It would be better in the long run for everyone to either open a request with the spec maintainers or get this fixed in the infringing Micropub clients themselves.


Update Carousel.md: Fix broken table format

Fix 2 broken tables format.

Q
A

Bug fix?
✔

New feature?
❌

New sample?
❌

What's in this Pull Request?
Fix broken table on the Carousel documentation.

Thank you @AriGunawan for the fix!


SelectMenu navigation

Currently, if a user opens the select menu using their mouse, we allow them to navigate using tabs. But if they open the select menu using their keyboard, they can navigate using the up/down arrows as per the wcag spec. Should the behaviour be the same regardless of whether they opened using a mouse or a keyboard?
Creating this issue because I honestly don't remember the decision making process behind this when I built this 😂cc @muan if you have any thoughts! I believe the keyboard nav we implemented here was based off of the WS work in details-menu here: https://github.com/github/details-menu-element/blob/master/index.js#L217

As a data point (not guaranteeing this is correct, but it did go through an accessibility audit), the Azure Dev Ops <Dropdown /> used only arrow keys once you opened the dropdown.
https://developer.microsoft.com/en-ca/azure-devops/components/dropdown#advanced-dropdown
So, when expanding by activating the button, the filter <input /> gets focus. Then the user can down arrow to move to the tabs (right and left arrow to move between the tabs) and down arrow again to get to the items. Tabbing at any point will close the menu and return focus to the button.
At the very least it seems like maybe left/right arrow should be able to move focus between the tabs?
https://www.w3.org/TR/wai-aria-practices/examples/tabs/tabs-2/tabs.html

<details-menu>'s arrow key navigation works regardless how the menu is opened.  We follow https://www.w3.org/TR/wai-aria-practices-1.2/#menu. The cases with input is slightly different.

I'll hijack this to suggest supporting navigating by typing as well, as available on macOS (and presumably on other OSes as well). Example when pressing g:

I'll hijack this to suggest supporting navigating by typing as well, as available on macOS (and presumably on other OSes as well). Example when pressing g:

I believe this has been addressed!

I believe this has been addressed!


Added Send Icon

I have added the Send Icon with the hover effect. Here are the screenshots:
Before:

After:

Kindly accept my pull request under Hacktoberfest 2024

Thanks


Web - Expense request avatar is broken in LHN

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

Action Performed:

Login account A with policyExpenseChat beta permission
Create workspace if not exist
Invite user B to workspace
Login user B on another device
On B, Go to invited A's workspace chat
Request money
click ReportPreview to go to expense report
click IOUPreview to go to expense request
Observe highlighted row in LHN

Expected Result:
Avatar is not broken
Actual Result:
Avatar is broken
Workaround:
Unknown
Platforms:

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

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

Version Number: 1.3.47-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/8086ed37-55a7-4d0b-995c-a8d6ee3ea441
https://github.com/Expensify/App/assets/93399543/4a252a3c-cba3-4243-bf24-6a0413089d74
Expensify/Expensify Issue URL:
Issue reported by: @situchan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690545428804849
View all open jobs on GitHub

@situchan How can I get account with policyExpenseChat beta permission?
I was overriding the Permissions.canUseAllBetas function to return true in my local, but when opening any workspace chat it return 304.
Do I need to have this permission in backend also?
cc @bernhardoj

@bernhardoj
Thanks for help.
But how can I get this permission in backend?

@ahmedGaber93 please request permission in slack. You need to provide emails to be added to beta.

Thanks for help @situchan.
I have request permission in slack.

@stephanieelliott can I C+ review this if possible? As I found the root cause and solution while reporting this bug.

Hey @situchan do you think this issue will be fixed with the root cause you found? https://github.com/Expensify/App/issues/23847

This issue seems similar to #23847 - it looks like it's going to be fixed with #23815 - I asked the engineers in 23815 if they agree

@Christinadobrzyn No, it's different issue. #23815 was deployed to staging 6 hrs ago but broken avatar issue is still reproducible.

This issue seems similar to #23847 - it looks like it's going to be fixed with #23815 - I asked the engineers in 23815 if they agree

FYI: https://github.com/Expensify/App/pull/23815#issuecomment-1660110273

thanks for confirming @rezkiy37! Closing this as it's confirmed to be fixed with  https://github.com/Expensify/App/pull/23815#issuecomment-1660110273
@situchan feel free to reach out in the Expensify-Bugs room if you find any regressions

Hey @rezkiy37, can you double-check this issue will be fixed? @situchan believes to think the issue still exists after the merge.
Sorry for all the confusion @stephanieelliott - tried to save you some time!

Hi, @situchan! Could you please take a look at this comment where I attached examples. The second video associated with this issue. Do I still have the bug there?
https://github.com/Expensify/App/pull/23815#issuecomment-1660110273

@rezkiy37 you can test on staging right now

@rezkiy37 I checked your video. It's IOU request (in DM). The issue is in expense request (in workspace chat).
Is it clear now?

Appreciate you, thanks @Christinadobrzyn! 💕

@situchan, I've tried to reproduce it one more time on the staging. Everything looks good. Avatars are circles.
https://github.com/Expensify/App/assets/57314631/bbd06521-99d4-475b-9137-a5d506236718

Ah it's merged 12 hrs ago. So @rezkiy37 it's not your PR but Georgia's PR which fixed this issue.


Fix native-image with Netty >= 4.1.83.Final

Add a reflection configuration entry in WebServer to for io.netty.channel.DefaultChannelPipeline$TailContext
Fixes #6869

Nice work. Good grief.


Simplify implementation of swift_unreachable

I'll move this file to include/Swift/Runtime, and rename to swift_runtime_unreachable in the next PR once this is merged

@swift-c please smoke test

@swift-c please smoke test

@swift-ci please smoke test

I think historically we haven't trusted LLVM headers to not pull in more dependencies for the runtime. Additionally, the runtime should be built with the just-built Clang rather than the host compiler, so we need to be careful not to include anything like llvm/Config/Config.h.

That's why I initially added my own implementation of LLVM_ATTRIBUTE_NORETURN.
However, I took a look in the runtime: it's incredibly popular, and the runtime imports LLVM in most places: https://github.com/apple/swift/search?utf8=✓&q=LLVM_ATTRIBUTE_NORETURN

All right, withdrawn. (Should still be double-checked by someone who knows the runtime.)

@jrose-apple  @gparker42 maybe? I know he has experience in this area with I think SmallVector.

Yes, we already pull in llvm headers in lots of places. We have similar portability goals so we don't want to reinvent LLVM's OS and tools compatibility.
The threat of mismatched llvm-config.h is news to me. Elsewhere we ought to make sure that the build system keeps everything straight.

I think the conflicting config files problem would only occur if the host compiler is a) built from source and b) has its sources in the INCLUDE environment variable or passed via cmake
Seems unlikely?

An OS build system is one likely way to get that. I see llvm-config.h distributed in /usr/local/include in the SDKs generated for macOS internal builds, at least.


Spaces are cut in folders names (prompt, chat, attachments)

EPAM AI DIAL chat version
0.7.0
What happened?
It's a part if #973

Rename folder with spaces in the middle

Click on confirm button -> spaces are cut in the name -> bug

Expected result: spaces should be left if they are in the middle of the name. Spaces should be cut only before or after text
Confidential information

[X] I confirm that do not share any confidential information

Verified on staging successfully

Verified on sales env 0.9.2 successfully


Code completion doesn't recognize attributes

Describe the bug
After typing @, typing a letter or pressing Ctrl+Space shows completions for all identifiers and keywords, not just attribute names.
To Reproduce
Steps to reproduce the behavior:

Open a Q# file in Visual Studio Code.

Type @r in a namespace:
namespace Example {
    @r
}

Code completion shows identifiers that aren't valid as attributes, like the repeat keyword.

Expected behavior
Code completion should only valid attribute names. It is probably easier to show all user-defined types instead of only user-defined types with the @Attribute() attribute, since I don't think code completion is capable of filtering by attributes right now.
Screenshots

System information

QDK extension v0.12.20092803
Windows 10, .NET Core 3.1.401
Visual Studio Code version 1.49.2

Additional context
CodeCompletion\FragmentParsing.fs is probably a good place to start. The modifiers parser can parse things that appear before a declaration, like the internal keyword. It should be possible to also parse the @ symbol here followed by a user-defined type name.
https://github.com/microsoft/qsharp-compiler/blob/edc3d1557d62dc3cf1175caf6386e78aee91eb03/src/QsCompiler/TextProcessor/CodeCompletion/FragmentParsing.fs#L25-L27

Hi @samarsha, is it okay if I attempt to fix this?

Hi @ashwinpilgaonkar, yes, feel free to start working on this! Let me know if you have any questions.

@samarsha sure will do, thanks.

Hi @samarsha, I seem to be having some trouble with installing the development VSIX extension.
I took the following steps to setup my development environment as per the docs:

Installed vsce globally using npm
Cloned the project and ran bootstrap.ps1
Followed the steps to build a self-contained version of the language server using dotnet publish
Ran vsce package to produce an installable VSIX
Attempted to install the generated VSIX file into VS Code using Local Extension Installer by Edgar Geier

The module activation fails and gives the following error:
[2020-10-05 17:22:09.679] [exthost] [info] ExtensionService#_doActivateExtension quantum.quantum-devkit-vscode {"startup":false,"extensionId":{"value":"quantum.quantum-devkit-vscode","_lower":"quantum.quantum-devkit-vscode"},"activationEvent":"onLanguage:qsharp"}
[2020-10-05 17:22:09.679] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/ashpi/.vscode/extensions/quantum.quantum-devkit-vscode-0.9999.20102010/out/extension
[2020-10-05 17:22:09.701] [exthost] [error] Activating extension quantum.quantum-devkit-vscode failed due to an error:
[2020-10-05 17:22:09.703] [exthost] [error] Error: Cannot find module 'vscode-extension-telemetry'
Require stack:
- c:\Users\ashpi\.vscode\extensions\quantum.quantum-devkit-vscode-0.9999.20102010\out\telemetry.js
- c:\Users\ashpi\.vscode\extensions\quantum.quantum-devkit-vscode-0.9999.20102010\out\extension.js
- c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js
- c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-amd.js
- c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork.js
	at Function.Module._resolveFilename (internal/modules/cjs/loader.js:844:17)
	at Module._load (internal/modules/cjs/loader.js:737:27)
	at Function.Module._load (electron/js2c/asar.js:769:28)
	at Function.t._load (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1046:268)
	at Function.i._load (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1015:981)
	at Function.n._load (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1012:303)
	at Module.require (internal/modules/cjs/loader.js:899:19)
	at n (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js:16:135)
	at Object.<anonymous> (c:\Users\ashpi\.vscode\extensions\quantum.quantum-devkit-vscode-0.9999.20102010\out\telemetry.js:7:38)
	at Module.o._compile (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js:16:360)
	at Object.Module._extensions..js (internal/modules/cjs/loader.js:1051:10)
	at Module.load (internal/modules/cjs/loader.js:862:32)
	at Module._load (internal/modules/cjs/loader.js:774:14)
	at Function.Module._load (electron/js2c/asar.js:769:28)
	at Function.t._load (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1046:268)
	at Function.i._load (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1015:981)
	at Function.n._load (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1012:303)
	at Module.require (internal/modules/cjs/loader.js:899:19)
	at n (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js:16:135)
	at Object.<anonymous> (c:\Users\ashpi\.vscode\extensions\quantum.quantum-devkit-vscode-0.9999.20102010\out\extension.js:16:21)
	at Module.o._compile (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js:16:360)
	at Object.Module._extensions..js (internal/modules/cjs/loader.js:1051:10)
	at Module.load (internal/modules/cjs/loader.js:862:32)
	at Module._load (internal/modules/cjs/loader.js:774:14)
	at Function.Module._load (electron/js2c/asar.js:769:28)
	at Function.t._load (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1046:268)
	at Function.i._load (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1015:981)
	at Function.n._load (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1012:303)
	at Module.require (internal/modules/cjs/loader.js:899:19)
	at require (internal/modules/cjs/helpers.js:74:18)
	at Function.s [as __$__nodeRequire] (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js:33:604)
	at p._loadCommonJSModule (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1017:241)
	at p._doActivateExtension (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:915:625)
	at p._activateExtension (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:914:708)
	at Object.actualActivateExtension (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:912:453)
	at h._activateExtension (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:644:731)
	at c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:644:409
	at Array.map (<anonymous>)
	at h._activateExtensions (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:644:397)
	at h.activateById (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:642:207)
	at p._activateById (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:913:363)
	at p.$activate (c:\Users\ashpi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:922:391)
	at processTicksAndRejections (internal/process/task_queues.js:94:5)

I even tried to globally install vscode-extension-telemetry using npm but it doesn't seem to solve the problem.
I haven't received any errors at any of the other steps.
I'm running the latest version Windows 10 (64-bit), VS Code and .NET Core.
I'm unable to figure out why this is happening. Is there something I'm missing?

It looks like the same error is affecting the latest release of the QDK extension for VS Code, actually, so it seems like it is a separate issue that we will hopefully have a fix for soon. However, for some reason it doesn't affect me when I build the VSIX using vsce package - the extension seems to work when I install it.
Can you double-check that there is a node_modules folder in the repository's src/VSCodeExtension folder? If not, running npm install should create it.
Also, instead of using vsce package, you could try running the extension in an experimental VS Code instance. The instructions in the "Debugging" section should help: https://github.com/microsoft/qsharp-compiler/blob/main/src/VSCodeExtension/BUILDING.md#debugging

The "Cannot find module 'vscode-extension-telemetry'" problem looks like it was caused by a recent update to vsce, but I think that a new update has fixed it - @ashwinpilgaonkar can you try running npm install -g vsce to update vsce and then building the VSIX again?

Hi @samarsha, thanks for all the info!
You can find my replies stated below -

The "Cannot find module 'vscode-extension-telemetry'" problem looks like it was caused by a recent update to vsce, but I think that a new update has fixed it - @ashwinpilgaonkar can you try running npm install -g vsce to update vsce and then building the VSIX again?

I just tried it. The same error still shows up.

It looks like the same error is affecting the latest release of the QDK extension for VS Code, actually, so it seems like it is a separate issue that we will hopefully have a fix for soon. However, for some reason it doesn't affect me when I build the VSIX using vsce package - the extension seems to work when I install it.

Oh, I see.

Can you double-check that there is a node_modules folder in the repository's src/VSCodeExtension folder? If not, running npm install should create it.

You're right, the node_modules folder was indeed missing. I ran npm install, but it doesn't seem to change anything. FYI, regardless of whether the node_modules is present or not, VSCode does detect the installation of the extension (I get the option to uninstall/disable it). But the autocomplete doesn't work and VSCode throws the following error Could not download Q# language server.
When I build a self-contained version of the language server and set the quantumDevKit.languageServerPath path in settings.json, it throws up another error - The Q# Language Server has encountered an error. Diagnostics will be reloaded upon saving the file. Details on the encountered error have been logged to the output window.
[Info  - 5:11:24 pm] workspace folder: c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension
[Error - 5:11:27 pm] Error on loading project 'c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\templates\library\Library.csproj': The SDK 'Microsoft.Quantum.Sdk/0.9999.2010.2010-alpha' specified could not be found.  c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\templates\library\Library.csproj.
Ignoring non-Q# project 'c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\templates\library\Library.csproj'.
[Error - 5:11:28 pm] Error on loading project 'c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\templates\unittest\Test.csproj': The SDK 'Microsoft.Quantum.Sdk/0.9999.2010.2010-alpha' specified could not be found.  c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\templates\unittest\Test.csproj.
Ignoring non-Q# project 'c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\templates\unittest\Test.csproj'.
[Error - 5:11:28 pm] Error on loading project 'c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\templates\application\Application.csproj': The SDK 'Microsoft.Quantum.Sdk/0.9999.2010.2010-alpha' specified could not be found.  c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\templates\application\Application.csproj.
Ignoring non-Q# project 'c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\templates\application\Application.csproj'.
[Error - 5:11:28 pm] Error on loading project 'C:\Users\ashpi\AppData\Local\Temp\qsharp\c_x2f__x2f_Users_x2f_ashpi_x2f_OneDrive_x2f_Documents_x2f_Work_x2f_Open Source_x2f_qsharp-compiler_x2f_src_x2f_VSCodeExtension\generated.csproj': The SDK 'Microsoft.Quantum.Sdk/0.9999.2010.2010-alpha' specified could not be found.  C:\Users\ashpi\AppData\Local\Temp\qsharp\c_x2f__x2f_Users_x2f_ashpi_x2f_OneDrive_x2f_Documents_x2f_Work_x2f_Open Source_x2f_qsharp-compiler_x2f_src_x2f_VSCodeExtension\generated.csproj.
Ignoring non-Q# project 'C:\Users\ashpi\AppData\Local\Temp\qsharp\c_x2f__x2f_Users_x2f_ashpi_x2f_OneDrive_x2f_Documents_x2f_Work_x2f_Open Source_x2f_qsharp-compiler_x2f_src_x2f_VSCodeExtension\generated.csproj'.
[Info  - 5:11:28 pm] Failed to load temporary .csproj for c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\Program.qs.
[Info  - 5:11:29 pm] The file c:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\VSCodeExtension\Program.qs is not associated with a compilation unit. Only syntactic diagnostics are generated.
[Error - 5:11:36 pm]
=============================
System.ArgumentException: no namespace with the given name exists
   at Microsoft.Quantum.QsCompiler.SymbolManagement.NamespaceManager.TryResolveQualifier(NonNullable`1 qualifier, NonNullable`1 nsName, NonNullable`1 source) in C:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\QsCompiler\Core\SymbolTable.fs:line 805
   at Microsoft.Quantum.QsCompiler.SymbolManagement.NamespaceManager.TryGetCallableHeader(QsQualifiedName callableName, FSharpOption`1 declSource, NonNullable`1 nsName, NonNullable`1 source) in C:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\QsCompiler\Core\SymbolTable.fs:line 1586
   at Microsoft.Quantum.QsCompiler.SymbolManagement.NamespaceManager.TryGetCallable(QsQualifiedName callableName, NonNullable`1 nsName, NonNullable`1 source) in C:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\QsCompiler\Core\SymbolTable.fs:line 1600
   at Microsoft.Quantum.QsCompiler.CompilationBuilder.SuggestedEdits.SuggestionsForIndexRange(FileContentManager file, CompilationUnit compilation, Range range) in C:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\QsCompiler\CompilationManager\EditorSupport\CodeActions.cs:line 396
   at Microsoft.Quantum.QsCompiler.CompilationBuilder.EditorCommands.CodeActions(FileContentManager file, CompilationUnit compilation, Range range, CodeActionContext context) in C:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\QsCompiler\CompilationManager\EditorSupport\EditorCommands.cs:line 146
   at Microsoft.Quantum.QsCompiler.CompilationBuilder.ProjectManager.<>c__DisplayClass25_0.<CodeActions>b__0(FileContentManager file, CompilationUnit c) in C:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\QsCompiler\CompilationManager\ProjectManager.cs:line 1032
   at Microsoft.Quantum.QsCompiler.CompilationBuilder.CompilationUnitManager.<FileQuery>g__TryQueryFile|31_0[T](FileContentManager f, <>c__DisplayClass31_0`1& ) in C:\Users\ashpi\OneDrive\Documents\Work\Open Source\qsharp-compiler\src\QsCompiler\CompilationManager\CompilationUnitManager.cs:line 717
=============================

Also, instead of using vsce package, you could try running the extension in an experimental VS Code instance. The instructions in the "Debugging" section should help: https://github.com/microsoft/qsharp-compiler/blob/main/src/VSCodeExtension/BUILDING.md#debugging

Could you help me out with this?
I went through the docs but I was unable to locate the Debug tab in VSCode.
From the Debug tab in VS Code, ensure that "Extension" is selected in the Debug target menu and press the green ‣.

But the autocomplete doesn't work and VSCode throws the following error Could not download Q# language server.

I think this is normal. The extension tries to download a language server with the same version as the extension, but since you built the extension manually, a language server with a matching version number doesn't exist on the download server. So I think setting quantumDevKit.languageServerPath is necessary here.

When I build a self-contained version of the language server and set the quantumDevKit.languageServerPath path in settings.json, it throws up another error - The Q# Language Server has encountered an error. Diagnostics will be reloaded upon saving the file. Details on the encountered error have been logged to the output window.

This is also probably normal, unfortunately - since the language server is asynchronous, sometimes it receives commands that are no longer valid for the current state. These cause exceptions which are ignored in the release build but are shown in debug builds. I think it would be good if the language server handled this more nicely - generally if something is expected to happen often it shouldn't throw an exception, but for now I think it's probably safe to ignore them.

Could you help me out with this?
I went through the docs but I was unable to locate the Debug tab in VSCode.

When you have the VSCodeExtension folder open in VS Code, there should be a button on the right that has a triangle and a bug. If you click that, then click the green triangle at the top, it should run the extension:

I think this is normal. The extension tries to download a language server with the same version as the extension, but since you built the extension manually, a language server with a matching version number doesn't exist on the download server. So I think setting quantumDevKit.languageServerPath is necessary here.

Yes.

This is also probably normal, unfortunately - since the language server is asynchronous, sometimes it receives commands that are no longer valid for the current state. These cause exceptions which are ignored in the release build but are shown in debug builds. I think it would be good if the language server handled this more nicely - generally if something is expected to happen often it shouldn't throw an exception, but for now I think it's probably safe to ignore them.

Oh, I see. Okay.

When you have the VSCodeExtension folder open in VS Code, there should be a button on the right that has a triangle and a bug. If you click that, then click the green triangle at the top, it should run the extension:

Thanks, I was able to get the experimental mode running now!
However, there is still a difference in output between the official latest build and the development version, regardless of whether it is installed as a VSIX extension, or being run in debug mode in an experimental instance of VSCode.

Dev build

Official latest build

Are you editing a Q# file that is not part of a Q# project? Can you try creating a new Q# project and opening a file inside the project folder? One way to do this is press Ctrl+Shift+P and then type "q# create" in the command palette.
The extra completion items RangeEnd, RangeReverse, etc. come from library functions, which means that a project file needs to exist that has a reference to the library package. If you open a Q# file outside of a project folder, the language server tries to automatically create a project file to use, but the project file it creates has a reference to a package with the same version as the language server itself. Since that version number was created locally and doesn't exist on the package server, the autogenerated project file won't work on non-release versions of the language server. #614 is the issue relating to this.
Also, thanks for your patience through all of these confusing issues. :) I think that I will add these to the README/BUILDING.md files so that getting started with developing the language server is more clear in the future.

Are you editing a Q# file that is not part of a Q# project? Can you try creating a new Q# project and opening a file inside the project folder? One way to do this is press Ctrl+Shift+P and then type "q# create" in the command palette.

Yes, all along I was using a sample .qs file that wasn't part of a Q# project. Both the screenshots I provided in my previous reply were obtained after testing on that file.
I did as you said and created a new Q# project. Now the outputs are matching in both cases. That's one problem solved!

The extra completion items RangeEnd, RangeReverse, etc. come from library functions, which means that a project file needs to exist that has a reference to the library package. If you open a Q# file outside of a project folder, the language server tries to automatically create a project file to use, but the project file it creates has a reference to a package with the same version as the language server itself. Since that version number was created locally and doesn't exist on the package server, the autogenerated project file won't work on non-release versions of the language server. #614 is the issue relating to this.

Okay, it makes a lot of sense now.

Also, thanks for your patience through all of these confusing issues. :) I think that I will add these to the README/BUILDING.md files so that getting started with developing the language server is more clear in the future.

It's no problem at all!
In fact its things like these that add to the learning experience. :)

Also, just to confirm - this fix should filter out and display only RangeEnd, RangeReverse, RangeStart and RangeStep in the case of "@r,,," correct?

I think this screenshot might be a better example:

I think the only things that should be shown are:

EntryPoint
Example (which is a namespace, because the namespace could contain attributes)
ExampleType

Although ExampleType is technically not an attribute, code completion only supports filtering based on categories like "callable" and "user-defined type" currently. So I think it's OK if we show all user-defined types, even if they aren't necessarily attributes - it would still be a big improvement over the current behavior, and we can possibly add more specific filtering later.
There are also two of each for EntryPoint and ExampleType because one of them is the type itself and the other is the type constructor (which is a callable). If code completion shows only user-defined types, then only the ones with the gray rectangle and two squares should be shown, not the purple cube ones.

@samarsha I was going through the FragmentParsing.fs file. Suppose I want to print the output of this statement -
let private modifiers =
    expectedKeyword qsInternal

How can I do that? Where can I view the output?

modifiers has type Parser<'a, 'b>, which is basically like a function that takes in a string input and returns a parser result. I think the easiest way to run the parser directly is using F# Interactive:

Temporarily remove private from let private modifers so we can access it from a script.
Open a terminal in the qsharp-compiler\src\QsCompiler\TextProcessor folder.
Run these commands:

dotnet publish
dotnet fsi -I bin\Debug\netstandard2.1\publish -r Microsoft.Quantum.QsTextProcessor.dll

This should open F# Interactive where you can type in F# code now.
open FParsec;;
open Microsoft.Quantum.QsCompiler.TextProcessing.CodeCompletion.FragmentParsing;;
"" + "\u0004" |> runParserOnString modifiers [] "";;

That should output:
val it :
  ParserResult<Quantum.QsCompiler.TextProcessing.CodeCompletion.CompletionKind list,
               Quantum.QsCompiler.DataTypes.QsCompilerDiagnostic list> =
  Success: [Keyword "internal"]

This means that modifiers successfully parsed the empty string "" and said that the internal keyword can appear here. You can try replacing "" with "int", "foo", etc. and it should give the same output. However, if you try to parse "@", it says:
"@" + "\u0004" |> runParserOnString modifiers [] "";;
val it :
  ParserResult<Quantum.QsCompiler.TextProcessing.CodeCompletion.CompletionKind list,
               Quantum.QsCompiler.DataTypes.QsCompilerDiagnostic list> =
  Failure:
Error in Ln: 1 Col: 1
@♦
^
Expecting: identifier, '\u0004' or 'internal'

This part is what we want to change - we want it to recognize @ and say that a user-defined type can follow it.


Create dataset loader for Thai Depression Dataset

Dataloader name: thai_depression/thai_depression.py
DataCatalogue: http://seacrowd.github.io/seacrowd-catalogue/card.html?thai_depression

Dataset
thai_depression

Description
The corpus is a compilation of 944 expert-verified cases of depression in several online blogs (Storylog, bloggang, and lblogspot) written in Thai. The blog posts are further split into sentences in the data to fine-tune Thai BERT models.

Subsets
-

Languages
tha

Tasks
Text Classification

License
Creative Commons Attribution Non Commercial No Derivatives 4.0 (cc-by-nc-nd-4.0)

Homepage
https://zenodo.org/records/4734552

HF URL
-

Paper URL
https://aclanthology.org/2021.wnut-1.3/

#self-assign

#self-assign

#self-assign

still working on it :)

@ilhamfp Thanks for letting us know!! Just let us know if you need any help. 🙏


Add ref to Select to allow closing of dropdown

Feature request 🚀

[ ] I will create Pull Request
[x] It's just a suggestion

Expected

Select component should have a ref to enable programmatically closing the dropdown.

Examples

const ref = useRef(null)
const handler = val => {
  console.log(val)
  if(val === "3") ref.current.blur()
}
return (
  <Select ref={ref} placeholder="Choose one" onChange={handler} multiple>
     <Select.Option value="1">Option 1</Select.Option>
     <Select.Option value="2">Option 2</Select.Option>
     <Select.Option value="3">Option 3 should close select</Select.Option>
  </Select>
)

I'm looking for this as well, I want to use the Select with  react-hook-form but I can't at this moment, are you working at this? I saw the code and seems like you need a well understanding of the code to add the ref prop

In fact, blur is not controlled by ref, because it is not a native input, but a component that mimics the behavior of select. For this type of component, exporting ref is not helpful.
I think you probably don't know how to use Select in combination with react-hook-form, the ref you mentioned is how the uncontrolled components are combined with react-hook-form, Geist Select is typically a controlled component, however. It may be helpful to read the documentation at the link.
(If anyone would like to create an online example to illustrate this point it would be very useful)

I have the same issue at the moment. It might be a bug a well with useClickAway.
My issue is that useClickAway() works well, except when you click on a different select dropdown. In that case, both dropdowns are open, while I want the first to close and the second to open.
Now, without a ref, It's not even possible to setVisible(false) programmatically as I can not reach the inner element.
@unix IMO, adding a ref would be great, let me know your thoughts and if you want to consider a PR.

@eladg
Well, I agreed with you. For controlling between multiple selects, ref is indeed very useful.
To export ref in a mock native component, we must have a set of mock ref export functions to match multiple scenario. I'll try to add this feature in the next canary version.

Thanks @unix, let me know if there is any way I can help!


Types

add types (user&issue) only into one object or something like this?

so we can also get length instead of writing manually a number

add types (user&issue) only into one object or something like this?

Maybe it will not works if I put it all in one object 🤔