#262 pylint-fixes

trailing-whitespace,trailing-newlines,missing-final-newline,ungrouped-imports,wrong-import-order,no-else-raise,useless-return,unnecessary-pass. (see #262)

Codecov Report

Merging #263 (a7cc543) into master (5361938) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #263      +/-   ##
==========================================
+ Coverage   61.89%   61.92%   +0.03%
==========================================
  Files          32       32
  Lines        1850     1849       -1
  Branches      118      118
==========================================
  Hits         1145     1145
+ Misses        674      673       -1
  Partials       31       31

Flag
Coverage Δ

unittests
61.92% <100.00%> (+0.03%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

selene/api/base/__init__.py
0.00% <ø> (ø)

selene/core/command.py
56.25% <ø> (ø)

selene/core/wait.py
87.03% <ø> (ø)

selene/support/jquery_style_selectors.py
0.00% <ø> (ø)

selene/support/shared/config.py
82.30% <ø> (+0.33%)
:arrow_up:

selene/support/shared/jquery_style.py
100.00% <ø> (ø)

selene/core/configuration.py
100.00% <100.00%> (ø)

selene/core/entity.py
59.55% <100.00%> (ø)

... and 1 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #263 (a7cc543) into master (5361938) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #263      +/-   ##
==========================================
+ Coverage   61.89%   61.92%   +0.03%
==========================================
  Files          32       32
  Lines        1850     1849       -1
  Branches      118      118
==========================================
  Hits         1145     1145
+ Misses        674      673       -1
  Partials       31       31

Flag
Coverage Δ

unittests
61.92% <100.00%> (+0.03%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

selene/api/base/__init__.py
0.00% <ø> (ø)

selene/core/command.py
56.25% <ø> (ø)

selene/core/wait.py
87.03% <ø> (ø)

selene/support/jquery_style_selectors.py
0.00% <ø> (ø)

selene/support/shared/config.py
82.30% <ø> (+0.33%)
:arrow_up:

selene/support/shared/jquery_style.py
100.00% <ø> (ø)

selene/core/configuration.py
100.00% <100.00%> (ø)

selene/core/entity.py
59.55% <100.00%> (ø)

... and 1 more

Continue to review full report at Codecov.

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

Not ready yet.

Not ready yet.


Add source locations to annotations.

Proposal to address issue #285.

Yes, I still have to update the spec. Hope to get to it tomorrow.

Finally got around to this.
I just ran the update_go.sh script, so if the CI passes we should be good to go.

Sweet, thanks. Indeed I did not check the rendering. Fingers crossed.

@antoninbas are we ready to merge then?

@smolkaj we are ready to merge as far as I'm concerned. Did anyone from your side (Konstantin / Stefan) want to review this?


Export ReactQuill namespace

This is a copy of https://github.com/zenoamaro/react-quill/pull/433. I deleted my fork and recreated the PR since it seems other people are experiencing this problem.
Importing the ReactQuill namespaced types do not work in Typescript. This PR exports the namespace, which allows for the following usage:
import ReactQuill from 'react-quill'; // Import the React component
import { ReactQuill as rq } from 'react-quill'; // Import the namespace

Once the namespace is imported, it can be used like so:
function(editor: rq.UnprivilegedEditor): void { ... }

This fixes https://github.com/zenoamaro/react-quill/issues/350
Can you take a look @alexkrolick. I also updated the README.

I've also noted that the types.d.ts file doesn't include preserveWhitespace? as an option in the IComponentProps. Between the export of the namespace and the preserveWhitespace, I can't build my Amplify console app since I've made these changes locally to accommodate my development.
I don't suppose it would be possible to get you to add that in there too while you're at it @dimes ?
Then hopefully @zenoamaro can come along and just merge it all up and republish!

As an update, for anyone dealing with issues that haven't got PRs accepted for things like types, but can't just edit them locally (such as myself because I'm deploying to AWS Amplify) - you can publish a scoped version of this repository, once you fork it.
Best etiquette I've seen others mention is to fork the project on your Github, keeping everything intact, license and more. Once done, clone it and make your changes (for example to types.d.ts). Push it back to your branch (master, or otherwise). Sign up to NPM, login via the cli, and set your user scope. I.e., @wyrdathru.
Once done, you can publish a publicly accessible, scoped version with your changes, at least until the PRs are in and you want to move back to the main stream.
See these for more details:

https://stackoverflow.com/questions/39350233/how-can-i-preserve-local-changes-made-to-an-npm-module
https://opensource.stackexchange.com/questions/7024/etiquette-around-forks-npm
https://docs.npmjs.com/creating-and-publishing-scoped-public-packages

Would TS users be OK with moving the typedefs to the definitely typed third party repository? These PRs aren't merged because 1) I don't actively use TS 2) there aren't any tests for TS 3) it's unclear if the changes proposed require a major or minor version bump

Would TS users be OK with moving the typedefs to the definitely typed third party repository? These PRs aren't merged because 1) I don't actively use TS 2) there aren't any tests for TS 3) it's unclear if the changes proposed require a major or minor version bump
https://definitelytyped.org/

I actually think this would be the best option - yeah. A lot of projects are supported on there and removes some of the maintenance responsibilities from this project directly.

Going to close this then.

Oh, man... I hoped to use this fix and now I can't.


Add auto-compiled models to What's New

Release notes
The team has been working primarily on EF Core internals, so there are no new big features in EF Core 9 (EF9) Preview 3. However, this means we really need people like you to run your code on these new internals and report back what you find. We want to fix bugs in the new internals as soon as possible in order to have a strong GA release later in the year.
That being said, there are several smaller enhancements included in preview 3. For full details, see What's new in EF Core 9. To discuss the EF9 release, go to Try EF Core 9 now! on GitHub.
Auto-compiled models
Auto-compiled models allow the EF Core compiled model to be automatically regenerated when the model project is built. This means you no longer need to remember to re-run the dotnet ef dbcontext optimize command after your EF model changes. See Auto-compiled models in the What's New docs for more information.
Sugar for HierarchyId path generation
First class support for the SQL Server HierarchyId type was added in EF8. In EF9, a sugar method has been added to make it easier to create new child nodes in the tree structure. See Sugar for HierarchyId path generation in the What's New docs for more information.
Everything else in preview 3
Preview 3 contains:

6 enhancements
5 bug fixes

EF Core 9 preview 3 (and Microsoft.Data.Sqlite) contains work from the EF Team at Microsoft (@roji @AndriySvyryd @maumar @ajcvickers @cincuranet @SamMonoRT @luisquintanilla) as well as contributions from the EF Core community. The community PRs in EF9 Preview 3 are:

@lauxjpn: Cleanup duplicate tests (same test ID)
@clement911: Fixed typo in getting-and-building-the-code.md
@Rezakazemi890: 32943-Sugar for HierarchyId path generation
@lauxjpn: Change Where_math(f)_log_new_base queries, so they fail if LOG() parameters are swapped
@SteSinger: 33196 command timeout allow zero

@jamesmontemagno Release notes draft in comment above.


gpu support?

i installed tensorflow-gpu but when i run with vctk-corpus i can see my CPU at 100% while my GPU isn't being used at all. graphics card is 1080ti, drivers are up to date, cuda and cudnn are installed. can someone confirm where the path files need to be if that's the problem?

Can you check your CUDA_VISIBLE_DEVICES environment variable?
You can also look at the logs. This can be set by setting the flag log_device_placement=True  while creating the session

    config = tf.ConfigProto(allow_soft_placement=True, log_device_placement=True)
    config.gpu_options.allow_growth = True
    config.gpu_options.per_process_gpu_memory_fraction = args.gpu_fraction
    sess = tf.Session(config=config)```
This way you can see if there was any GPU found when the session was created.

i don't seem to have that environment variable. what should it point to?

Say you have 2 or 3 GPUs. They are indexed 0,1,2, etc.
If you want to use all 3, you can set the variable as
CUDA_VISIBLE_DEVICES=0,1,2
If you want to use only one, say 1
CUDA_VISIBLE_DEVICES=1
PS: I see that you are using Windows. I am not entirely sure it is applied in the same way in Windows as Linux. But give it a try. Good luck!

haha thanks, I tried ubuntu already but i am completely new to linux OS so i'm trying to use what i already have. if it gets too hard i'll switch back to ubuntu and keep trying to learn it (or another linux OS if there's a better one)
tried what you said, did you want me to set log_device_placement=true in line 269 of train.py? tried that and got a massive block of text being returned in powershell, not sure if i can paste it all but i'll try. it seems to only be seeing my CPU even though i set the environment variable like you said.
powershell output.txt

You can see in it lines such as
(Const)/job:localhost/replica:0/task:0/device:CPU:0
This means that the task was deployed on CPU and not on GPU.
At the beginning, you should see a log stating whether it found a GPU or not. That part is missing from this log file.

here is the beginning of the file. it doesn't say anything about the GPU.


integration-test

Addresses the following issues: #316
Signed-off-by: Nivedita Prasad<EMAIL_ADDRESS>

The blockdevices on path /dev/sdb /dev/sda is  in inactive status, here are the outputs:
kubectl get bd -n openebs -o wide
NAME                                           NODENAME                           PATH        FSTYPE   SIZE           CLAIMSTATE   STATUS     AGE
blockdevice-18d185d10824b64718b1810910d14c25   lenovo-ideapad-l340-15irh-gaming   /dev/sdb    vfat<PHONE_NUMBER>     Unclaimed    Inactive   35h
blockdevice-062f9e63a8f738c5c80a8dd9c76da379   lenovo-ideapad-l340-15irh-gaming   /dev/sda3   ntfs<PHONE_NUMBER>16   Unclaimed    Inactive   35h
blockdevice-f6de9bcc39618e718d875ea8819914e6   lenovo-ideapad-l340-15irh-gaming   /dev/sda2            16777216       Unclaimed    Inactive   35h
blockdevice-5b37fad69bea6352f6c107c555acdce0   lenovo-ideapad-l340-15irh-gaming   /dev/sda1   vfat     272629760      Unclaimed    Inactive   35h
blockdevice-38b0bba94a9f1313fcb344c725869d5e   lenovo-ideapad-l340-15irh-gaming   /dev/sda4   ntfs<PHONE_NUMBER>     Unclaimed    Inactive   35h

Codecov Report

Merging #653 (05149dc) into develop (9fe3968) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #653      +/-   ##
===========================================
- Coverage    46.09%   46.04%   -0.06%
===========================================
  Files           78       78
  Lines         3820     3820
===========================================
- Hits          1761     1759       -2
- Misses        1901     1903       +2
  Partials       158      158

Impacted Files
Coverage Δ

cmd/ndm_daemonset/probe/udevprobe.go
47.43% <0.00%> (-0.80%)
:arrow_down:

Continue to review full report at Codecov.

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

Hey @Nivedita-coder, are there any updates to this PR?

@Nivedita-coder Are there any updates on this PR?


ihaskell: remove unnecessary ihaskell-display package

Motivation for this change
ihaskell-display is a deprecated package that isn't used by IHaskell anymore.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

@sternenseemann is this the kind of change you were hoping for? I actually used this NixOS module definition as the basis for IHaskell's own release.nix a couple of years ago, although I've made a few modifications since then.

Sure! The rest of the expression is still correct I gather?

/rebase haskell-updates

Yes, the other packages are still maintained and in use!

Thank you!


Fix Next.js and Remix form examples

Tested the examples locally and found some issues. I used the Zod API incorrectly, Next.js server actions must be async functions, and had the wrong type for remix actions.

TS build won't work until I actually hit publish on main.


Generate docs for version v1.7.0-beta.2

SUMMARY

As part of ibm_zos_core collection v1.7.0-beta.2 release, the docs have been updated, latest is on main branch.
ISSUE TYPE

Update Collection

ADDITIONAL INFORMATION

UPDATE REGISTRY.YML

################################################################################
# Copyright (c) IBM Corporation 2020, 2021
################################################################################

################################################################################
# Configuration for Red Hat certified collections as part of the
# IBM Red Hat Certified Collection on Z offering
#
# For documentation to be generated and included in the offering pending the
# certfied registry process you must also include the required fields below.
#
# Instructions:
#  <item>: The collection repository name as a dictionary element such as
#          'ibm_zos_core', 'ibm_zos_ims', etc
#  git:    The collection repository git url such as 'bm_zos_core.git'
#  stable: The Git tag or branch name to generate stable documenation.
#  latest: The Git tag or branch name to generate latest documenation.
#
# Notes:
#   Only one version of documetation is currently generated and supported.
#   Documentation is only generator for the latest branch or tag, there is plans
#   to support both latest and stable in the near future.
################################################################################
collections:
  ibm_zos_core:
    git: git@github.com:ansible-collections/ibm_zos_core.git
    stable:
    latest: main
    origin: main
  ibm_zos_ims:
    git: git@github.com:ansible-collections/ibm_zos_ims.git
    stable:
    latest: main
    origin: main
  ibm_zos_cics:
    git: git@github.com:ansible-collections/ibm_zos_cics.git
    stable:
    latest: main
    origin: main
  zhmc-ansible-modules:
    git: git@github.com:zhmcclient/zhmc-ansible-modules.git
    stable:
    latest: 1.4.1
    origin: master
  ibm_zos_sysauto:
    git: git@github.com:ansible-collections/ibm_zos_sysauto.git
    stable:
    latest: v1.0.1
    origin: main
  ibm_zosmf:
    git: git@github.com:IBM/ibm_zosmf.git
    stable:
    latest: dev
    origin: main

Doc site has been refreshed for z/OS Core release 1.7.0-beta.2 per commit f305e40.
Coloring of module params was lost which is a known issue that needs to be addressed.

@fernandofloresg and I also both experienced an issue with the site-deploy.yml playbook where it seems the behavior of the partial invocation of site-teardown.yml was incorrectly deleting parent files and directories above what is specified in the playbooks which was very puzzling, but due to lack of time to spend debugging the issue further, I opted for a manual deployment of the updated docs so that we can re-visit the deployment playbook issue at a later time.

@itsBryantP - I am not seeing or completely understanding the issue, a month back I walked @fernandofloresg through the process and had success, we did see some edit he had made in his version of the  site-builder.yml that when reverted all worked fine.
As for the lost coloring, that can be corrected by using the requirements.txt specific in this repository, I just updated the setup.py and built a new vent using it and had no issues with coloring. I will say the frozen versions in the requirements.txt are concerning , I have an issue open on Ansible-extractor where in ansible-core 2.15 we will not be able to build doc. So as time progress and we reach a point when ansible-core 2.14 goes out of service we will have had to solve the issue.

@ddimatos - thanks for revisiting this, I would have to go back and try generating again to see if this is still a problem. At the time the coloring also didn't seem to correct itself when switching between old and new requirements.txt. Now that I have a new machine, when time permits I can attempt to generate the docs with to confirm if there are still any issues. This issue can be closed for now.

@ddimatos I got back around to this and regenerated this time without any issues, so considered the reported issue above resolved.


Accuracy results on MNIST

Hi,
I was reading your paper and got surprised by a few results.
First, the accuracy of what you call logistic loss is much lower than what you can typically obtain on MNIST. With the same model as your describe in the paper, I am able to obtain 99.3% accuracy on the MNIST test set in 10 epochs of SGD training. How can you obtain 98.08% accuracy with 500 epochs of training on clean samples?
Second, I was trying to reproduce the results with label corruption and I am seeing the same issue. With 50% label corruption, the same model and 10 epochs of SGD training, I am able to obtain 98% accuracy on the test set.
How do you explain such low results in your experiments?

Hey, sorry for the late reply.
You should probably give a bit more details about the validation part and the hyperparameters of the optimizer such as learning rate policy, weight decay, momentum, etc.
However, I am still skeptical about a few things. When I train with 50% of label corruption (both in train and validation), I can still get ~98% accuracy on the test set. You mentioned the overfitting of the model to the train set. If this was true, and you based your model selection on the corrupted validation set, it would (and it indeed does) dramatically increase the validation loss after a few epochs. When trying, I observe that the train accuracy and validation loss increase so the final model is actually one from the first few epochs and it gets 98% on the test set which is more than the 15.82% claimed. And this is without any regularization other than the model dropout (so no weight decay, no momentum, constant learning rate of 0.1).


[Mention The Feature]: Add styling to the web page by changing UI to key features component.

Is your feature request related to a problem? Please describe.

There is no UI for the key features part in the website
Describe the solution you'd like.
I want to change Ui to that particular part and want to apply styles to it.
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots

Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

this issue has been solved, so we are closing this issue.


Editor: live-edit virtual programs

I know @jmgrosen and @nmichaud have made edits that have enabled this on their systems. Either of you feel like contributing a version of those patches to address this?


Handle input_names to list only necessary for onnx_ops

it looks only a style change, what's the issue fixed?

it looks only a style change, what's the issue fixed?

If I want to do oopb.apply_op, it will fail for apply_prelu, appl_crop because apply_op automatically transfer the input to list, so we cannot concatenate like the current way.

Change apply_ops in keras2onnx to fix the issue, see here


e2e/ui: Fix timeout issue which happens with RKE2 + latest RM (2.7.2-rc6)

Follow-up of https://github.com/rancher/elemental/pull/731
As mentioned there, I will fix timeout issue when testing RKE2 + latest RM (2.7.2-rc6)

When you create the rke2 cluster, the status stays in updating status and looks like you have to refresh the page to see it active, maybe another bug on Rancher Manager, I will try to increase the timeout a little bit before.
I just pushed a branch to debug the issue.
Test is running here https://github.com/rancher/elemental/actions/runs/4445659222


Rancher moves loadbalancer to new host and it stops routing traffic correctly

Rancher Version: v1.0.0
Docker Version: v1.10.3
OS:
Original Host: Debian 8
New Host: Ubuntu 14.04
Steps to Reproduce:

Create a service
Create a loadbalancer to forward a domain name to the service.
Add a new host

Results:
Rancher moved the loadbalancer to the new host (and left all the other containers on the original host). The loadbalancer is no longer forwarding to the service. Rancher says all services are healthy but the service is not configured for a health check.
Expected:
The loadbalancer continues to route traffic to the service.

Can you share your docker-compose.yml of your stack?
Also, when you added a new host, did anything happen to your old host? If your old host went into reconnecting, Rancher knows nothing of the state of those containers (as they don't have a health check), where as it sounds as if the load balancer (which comes with a health check) determined there was something wrong with the old host and moved to the new one. In order for targets of a load balancer to move to the new host, they would need to be enabled with their own health checks.

Here is the app's docker-compose.yml (is this what you meant?):
gitlab-data:
  labels:
    io.rancher.container.start_once: 'true'
  entrypoint:
  - /bin/true
  hostname: gitdata
  image: gitlab/gitlab-ce:8.6.4-ce.0
  volumes:
  - /etc/gitlab
  - /var/log/gitlab
  - /var/opt/gitlab
gitlab-server:
  ports:
  - 22:22/tcp
  - 9801:80/tcp
  environment:
    GITLAB_OMNIBUS_CONFIG: |
      nginx['listen_port'] = 9801
      nginx['listen_https'] = false
      gitlab_rails['smtp_enable'] = true
      gitlab_rails['smtp_address'] = "smtp.mailgun.org"
  labels:
    io.rancher.sidekicks: gitlab-data
  hostname: git.optick.io
  image: gitlab/gitlab-ce:8.6.4-ce.0
  volumes_from:
  - gitlab-data

I didn't see anything happen to my old host. Also, when I deactivated the new host, the loadbalancer didn't go back to the old host, which is troubling. When I manually deleted the server through Packet, the loadbalancer did go back to the old host and is routing traffic correctly again.

I should also note that the loadbalacer and the application are in different stacks. I didn't want to put them in the same stack because the loadbalancer is listening on 443 and will be routing traffic to different services based on domain.

Can you share your docker-compose.yml for your load balancer?

loadbalancer:
  ports:
  - 443:80
  external_links:
  - gitlab/gitlab-server:gitlab-server
  labels:
    io.rancher.loadbalancer.ssl.ports: '443'
    io.rancher.loadbalancer.target.gitlab/gitlab-server: git.mydomain.com:443=9801
  tty: true
  image: rancher/load-balancer-service
  stdin_open: true

What about your rancher-compose.yml?
The different stacks shouldn't matter.
Before you added another host, was the load balancer active and running. I haven't seen anything here that should have triggered the re-deploying of the load balancer onto another host.
When you added your new host, were both hosts in Active state?
Are you able to reproduce this?

Just tried it again and it did not happen as it did before. I'll close this and re-open if I can reproduce after some more testing. Thanks for your help.


Update Getting started with Cadl link

After rename, we need to update the link in:

Current error is:

@mikekistler could you give us the new link we should use?

@maririos @mikekistler I'm not sure if it is correct link. https://microsoft.github.io/typespec/

What is the current link?

What is the current link?

https://github.com/Azure/cadl-azure/blob/main/docs/cadl-getting-started.md#getting-started-for-azure-data-plane-services

Then we should replace it with:
https://github.com/Azure/typespec-azure/blob/main/docs/typespec-getting-started.md#getting-started-for-azure-data-plane-services

Fix deployed to Prod


Enable per-workspace provider/model combination

Pull Request Type

[x] ✨ feat
[ ] 🐛 fix
[ ] ♻ refactor
[ ] 💄 style
[ ] 🔨 chore
[ ] 📝 docs

Relevant Issues

resolves #698
What is in this change?
Enable per-workspace model & provider combination with persistence and auto-config on selection.
Additional Information
Developer Validations

[x] I ran yarn lint from the root of the repo & committed changes
[x] Relevant documentation has been updated
[x] I have tested my code functionality
[x] Docker build succeeds locally

RTM


feat: support content navigator

Summary
add poc of content navigator
add a temporary authorize command to logon without submitting code.
Testing
not yet.
#56

Hey @boyce-w . I pulled these changes into https://github.com/sassoftware/vscode-sas-extension/pull/57

Hey @boyce-w . Do you mind if we close this one out as those changes are all in #57 ?

No problem. I've closed this PR.


fix: make hover card tappable

Let's just remove this.
In Radix Primitives for React this doesn't even do anything as the event there is some weird React abstraction.

#802

Looks great!
I didn't see this PR and opened another one almost identical, but I already closed it. Sorry.
I also suggest replacing the end of docs with the real keyboard interactions: docs/content/components/hover-card.md
## Accessibility

The hover card is intended for sighted users only, the content will be inaccessible to keyboard users.

### Keyboard Interactions

<KeyboardTable :data="[
    {
      keys: ['Tab'],
      description: 'Opens/closes the hover card.',
    },
    {
      keys: ['Enter'],
      description: 'Opens the hover card link',
    }]" />

This comes from Radix UI.


How to translate ValidationMessage

Hello. How can i translate ValidationMessage if i can use my StringLocalizer or standart StringLocalizer ?

Hi,
The only thing you can do now, is to change the value of "ValidationMessage" on "RecaptchaOptions". I'll look into a better way to do localization when I have a chance

Hey Paul, how can i set the language for recaptcha ?

Hi,
@hugoterra  check out this to localize the recaptcha control

@vov4ik08 - you can find implemented ValidationMessage localization in my fork of reCAPTCHA.
@PaulMiami - is there a chance you'll merge my changes?

I’ll review it this weekend
From: antyrama<EMAIL_ADDRESS>Sent: Tuesday, December 12, 2017 7:02 AM
To: PaulMiami/reCAPTCHA<EMAIL_ADDRESS>Cc: Paul Biccherai<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [PaulMiami/reCAPTCHA] How to translate ValidationMessage (#13)
@vov4ik08https://github.com/vov4ik08 - you can find implemented ValidationMessage localization in my fork of reCAPTCHA.
@PaulMiamihttps://github.com/paulmiami - is there a chance you'll merge my changes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/PaulMiami/reCAPTCHA/issues/13#issuecomment-351031795, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGrmwrvN1VcmA6OSibB0-UhozjEuchyDks5s_mtDgaJpZM4NTnl7.

Any news on this? @PaulMiami is @antyrama pull request ok?


support stdin and stdout for conversion command

When there is no input file or output file passed, there should be used stdin and stdout respectively.

done in https://github.com/rkluszczynski/avro-cli/releases/tag/avro-cli-0.2.3


Allow controlling the output dir from other extensions

The pull request introduces an spi and new build item that allows controlling the output directory of helm.

@Sgitario: can you have a look please ?


breaking: removes INBOUND_ERROR_DATA in favour of INBOUND_DATA_ERROR.

Currently we had the two variables but only one of them was used, given that modsecurity also has INBOUND_DATA_ERROR (see https://github.com/SpiderLabs/ModSecurity/blob/5f632a5ed5cf79fde9dee3ae518631951cee8762/Makefile.am#L218) it appears that INBOUND_ERROR_DATA was a typo.
Closes #564.

I removed code, no way coverage got worst @codecov


Rename String containsSequence to containsSubsequence and add a proper containsSequence

Summary
String containsSequence should be renamed to  containsSubsequence since its behaviour is behaviour is actually containsSubsequence and add a proper containsSequence
PR
Since there is nothing specific to Java 8, the Pull Request should be created from the 2.x branch

I will take a look at this.


incrementing debian version based on git commit

partial resolution for RackHD/RackHD#310
Basically pulling the same scenario we used in https://github.com/RackHD/on-taskgraph/blob/master/HWIMO-BUILD to include an increasing version as we made additional builds on a branch. Date string is formatted to be increasing over time, and mapped (pretty closely) to the last commit merged into the branch.

👍

:+1:


[BUG] Not working well with flutter tabs

Describe the bug
Not working well with flutter tab. The content of the HtmlEditor reset when come back to the tab.
To Reproduce
Steps to reproduce the behavior:

Create 2 tabs
Put one HtmlEditor in each tab
Go to tab 2 and write something in HtmlEditor
Go to tab 1 and come back to tab 2
The content you have just written is gone

I had similar problem with Forms, then I found out that using a global key can help preserve the content when the widget is rebuild. I think it should works similar for tabs, you can give it a try.

I am using a form key since the start but it isn't helping.
class _EditPropertyState extends State<EditProperty> {
  final GlobalKey<FormState> _formKey = GlobalKey<FormState>();

      body: SingleChildScrollView(
        child: Container(
          margin: const EdgeInsets.all(20),
          child: FittedBox(
            child: Form(
              key: _formKey,
              child: Column(

I am using like so.

I am using a form key since the start but it isn't helping.
class _EditPropertyState extends State<EditProperty> {
  final GlobalKey<FormState> _formKey = GlobalKey<FormState>();

     body: SingleChildScrollView(
       child: Container(
         margin: const EdgeInsets.all(20),
         child: FittedBox(
           child: Form(
             key: _formKey,
             child: Column(

I am using like so.

I believe in your case you need a key for the your HTMLEditor, as you want the content to be memorized in HTMLEditor. Something like:
HTMLEditor(         key: _someKey, ... )

I have assigned a different controller to each HtmlEditor. Isn't it enough? I have tried your recommendation as well but still not working. I am still trying around.
TabBarView(
  children: [
    Column(
      children: [
        InputField(controller: _myanmarTitleController, label: 'Myanmar Title'),
        rowSpacing,
        HtmlEditor(
          key: UniqueKey(),
          controller: _myDescriptionController,
          htmlEditorOptions: HtmlEditorOptions(
            hint: "Property description in Burmese",
            initialText: _myDescription,
          ),
        ),
      ],
    ),
    Column(
      children: [
        InputField(controller: _englishTitleController, label: 'English Title'),
        rowSpacing,
        HtmlEditor(
          key: UniqueKey(),
          controller: _enDescriptionController,
          htmlEditorOptions: HtmlEditorOptions(
            hint: "Property description in English",
            initialText: _enDescription,
          ),
        ),
      ],
    )
  ],
),

I tried to put the key at each Column widget as well but the result is the same.

I found the root of the cause! I am setting initialText content but not updating it when the input is change. So, I added the callback like so
HtmlEditor(
  controller: _myDescriptionController, //required
  htmlEditorOptions: HtmlEditorOptions(
    hint: "Property description in Burmese",
    shouldEnsureVisible: true,
    initialText: _myDescription,
  ),
  callbacks: Callbacks(
    onChangeContent: (String? changed) {
      if (changed != null && changed != _myDescription) {
        setState(() => _myDescription = changed);
      }
    },
  ),
),

But now, the HtmlEditor rebuilds every time I type and it is so inefficient. I am quite sure that the following part
if (changed != null && changed != _myDescription) {
  setState(() => _myDescription = changed);
}

and the rebuilding issues should be handled by the package itself. What do you think?

It's been me the whole time. I forgot to delete the UniqueKey() I set on TabBarView(). That's why it is rebuilding every time the content is changed. Final working code looks like this
HtmlEditor(
  controller: _myDescriptionController, //required
  htmlEditorOptions: HtmlEditorOptions(
    hint: "Property description",
    initialText: _myDescription,
  ),
  callbacks: Callbacks(
    onChangeContent: (String? changed) {
      setState(() => _myDescription = changed);
    },
  ),
)

Thank you @sscast for your helps.


Proposal: Package Categories

In the conversation on chocolatey/chocolatey.org#223, I brought up the idea of adding package categories to the ChocolateyGUI user interface. @gep13 and I discussed the UI for the Mac App Store, and I provided screenshots. @RichiCoder1 mentioned that the gallery does not provide enough metadata to implement categories well.
I agree that the organization for packages on the community feed is not very well-designed. My opinion as to how to correctly fix this is to institute the standardization of package tags to provide the required metadata, but that is a major change that would take significant time to apply. In lieu of that, I would recommend providing an XML file or similar that contains category metadata and a list of packages that the category contains. Does this sound like a reasonable solution?
I would probably put the XML files into a directory inside AppData and have ChocolateyGUI pick them up from there. This would allow users to supply their own categories through adding their own XML files into this directory. (The XML files would be shipped alongside the app -- or embedded within it, a la chocolatey.resources -- and copied upon first run.)

Will I like the idea in theory, you'll understand that I'm not super comfortable with shipping a custom solution, especially one that will require the kind of extensive support this will.

Related https://github.com/chocolatey/choco/issues/1363

This one is likely to be helpful. Browsing the apps is a bit of a pain as they're not sorted by type, but at the same time, there's currently over a hundred pages of programs, so doing this for each one individually can be a pain in the rear.

This is an old issue but one that I have come across now.
Package 'categories' isn't supported as part of NuGet v2 or v3 so we would have to use tags. Even if we added a custom field to the .nuspec file, this would be a custom solution for CCR only. Other repository manager would not support it. Given the limited number of users who request this and the limited support it would have in other repository managers, balanced with the huge undertaking to categorise packages, this isn't something we are looking to undertake.
The best way of doing this that works everywhere, is to implement a set of standard tags that could then be used as 'categories' which would be supported everywhere.
I'm going to go ahead and close this just now, but we can always reopen it again if necessary.


Result href decode

Tried a href with a space in the filename. sections/s ection2.xml the outURIresolver will give us sections/s%20ection2.xml will be docoded to sections/s ection2.xml.
With a % in the filename the decoder will throw a IAE(Illegal hex chars in escape (%) pattern)

We need test coverage. Would be interesting to give result-document: "folder space/folder%20encoded/file.xml"


If cling loads libblas, it should also define HAVE_CBLAS

otherwise, we still use the FLENS overloads.

We can also discuss to enable HAVE CBLAS by default.


[enhancement] light and dark mode easy way

Most of the websites these days allow users to switch between dark and light mode with just one click.
With current bootstrap coloring model to implement dark mode classes such as dropdown-menu-dark navbar-dark, .text-bg-light ... have to be added separately to each component. Implementing dark mode this way is not an easy task since you will need to add classes to entire elements manually or add them by default and then remove them by JavaScript  when light mode requested.
With this some components are still not behaving correctly (hard-coded colors in component).
However an easier way would be adding a single dark class to body and that is it.
To implement it, I define all light mode (default) color variables in :root and then define same variables for dark mode in another ,dark group class.
for example
.dark{
    --body-bg:rgba(var(--bs-dark-rgb), 0.9);
    --bs-border-color:#343a40;
    --bs-link-color:#3d8bfd;
    --bs-link-hover-color:#9ec5fe;
}

With this configuration I can also add theme variants to group classes and then add them to body tag to instantly change entire theme of the website in one go. again default theme will be defined in :root
.theme-red{
    --header-bg:#d50000;
    --drawer-bg-0:#b71c1c;
    --drawer-bg-1:#c62828;
    --drawer-bg-2:#d32f2f;
    --drawer-bg-active:#a70c0c;
}

Obviously pre-defined colors (primary secondary, danger, success, ...) stay same but dark and light will reverse.
Since I just started to use bootstrap, I'm not sure if this is a good idea or is it even feasible, but I had to change a lot of bootstrap css to make this happen and still a lot more places are not working correctly. for example I had to change .btn-close svg like this
:root
    --btn-close-icon: url("data:image/svg+xml,%3csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16' fill='%23000'%3e%3cpath d='M.293.293a1 1 0 0 1 1.414 0L8 6.586 14.293.293a1 1 0 1 1 1.414 1.414L9.414 8l6.293 6.293a1 1 0 0 1-1.414 1.414L8 9.414l-6.293 6.293a1 1 0 0 1-1.414-1.414L6.586 8 .293 1.707a1 1 0 0 1 0-1.414z'/%3e%3c/svg%3e");
    --btn-close-hover: var(--bs-dark)
}

.dark{
    --btn-close-icon: url("data:image/svg+xml,%3csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16' fill='%23fff'%3e%3cpath d='M.293.293a1 1 0 0 1 1.414 0L8 6.586 14.293.293a1 1 0 1 1 1.414 1.414L9.414 8l6.293 6.293a1 1 0 0 1-1.414 1.414L8 9.414l-6.293 6.293a1 1 0 0 1-1.414-1.414L6.586 8 .293 1.707a1 1 0 0 1 0-1.414z'/%3e%3c/svg%3e");
    --btn-close-hover: var(--bs-light)
}

.btn-close{ background:transparent var(--btn-close-icon) center/1em auto no-repeat; }
.btn-close:hover{ color:var(--btn-close-hover); }

Would be nice to have this implemented by default.

Implementing this will require changing for example
.form-control-dark {
    background-color: rgba(255, 255, 255, .05);
    border-color: rgba(255, 255, 255, .15);
}

to
.dark .form-control {
    background-color: rgba(255, 255, 255, .05);
    border-color: rgba(255, 255, 255, .15);
}

We shipped dark mode in our latest alpha release almost a month ago :). https://blog.getbootstrap.com/2022/12/24/bootstrap-5-3-0-alpha1/

Oh, haven't seen it yet, I do production code so I normally don't download alpha. but I'll look at it. Thanks again.
Does it support themes too? 5.2 had too many hard coded color codes at component level


Added Stack storage.

As discussed here. Added  stack implementation to storage-plus

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Nice job including all the tests.
I don't fully understand the use case for Stack::add_suffix. It looks like you want Stack to be both a stack implementation and a manager/factory of Stacks, all at once?

Nice job, including all the tests.
I don't fully understand the use case for Stack::add_suffix. It looks like you want Stack to be both a stack implementation and a manager/factory of Stacks, all at once?

Suffix does what Key() does in Map. Creates new Path

I'm wondering if it wouldn't make more sense to

implement a Stack that only allows you to have one stack at a fixed prefix, and then
think about some sort of StackMap<K, T> type to aid in managing access to multiple Stacks in a similar way Map helps in managing access to multiple pieces of data.

That way the new types have clearer purposes and the use case of "one value defined as a constant to manage multiple stacks" is still achieved.
With the current Stack implementation there might be a name collision issue too if someone actually tries to add new items to both a "root" Stack and a "derivative" Stack.

That could be done as well. Right now, you can have or not have a suffix, it's your choice. I'll happy to do that as well. Just making sure that everyone is on board with the idea, and then I'll do a coding sprint in the coming days. Just keep on adding any other suggestions and ideas as well.

Hey @itsHaseebSaeed! Are you still working on this?

Hey @itsHaseebSaeed! Are you still working on this?

@uint funnily enough, I just added this to my weekly to-do list just today. It's will be done max by Friday then I'll start working on deque store

Hey, @itsHaseebSaeed! We currently have both a need for this functionality and the resources to develop this in-house. Additionally, we might have some ideas around how to make a "map of stacks" functionality better fit our current system. Rather than spam you with change requests, we'd like to take over the implementation. Thank you for your contribution!

Closing in favor of #807


Adds new_with_capacity() for all other geometry types

This PR adds new_with_options() and their required methods for the remaining geometry types (excluding Rect).
Per https://github.com/geoarrow/geoarrow-rs/discussions/276#discussioncomment-7676936

@kylebarron oops! Thanks for catching. Should be fixed.


nova-password: 0.5.6 -> 0.5.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/sapcc/nova-password/releases.
meta.description for nova-password is: Decrypt the admin password generated for the VM in OpenStack
meta.homepage for nova-password is: https://github.com/sapcc/nova-password
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.5.7 in filename of file in /nix/store/d2mrajnjhpl0x9ywhzmj9laimkcfw2mm-nova-password-0.5.7

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

nova-password

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d2mrajnjhpl0x9ywhzmj9laimkcfw2mm-nova-password-0.5.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nova-password https://github.com/r-ryantm/nixpkgs/archive/e3173c822085ad9c7acbba94cd93145e9d955651.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e3173c822085ad9c7acbba94cd93145e9d955651#nova-password

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d2mrajnjhpl0x9ywhzmj9laimkcfw2mm-nova-password-0.5.7
ls -la /nix/store/d2mrajnjhpl0x9ywhzmj9laimkcfw2mm-nova-password-0.5.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

nova-password

Maintainer pings
cc @vinetos for testing.

https://github.com/sapcc/nova-password/compare/v0.5.6...v0.5.7


Add contentSearchMatches to response state

Hello, can we get this merged?

Hi @deferdie , thank you for the nudge. I will review and merge later today.

@deferdie A new version with your updates is now available: https://www.npmjs.com/package/ping-monitor#v082


add docs for MSBuild breaking change around serialization of certain types

Summary
This is a preemptive breaking-change notice for this linked MSBuild issue/discussion, because we want to get this announcement out with the Preview 4 blog post.
Details are still slightly fuzzy about the action items for this particular breakage, because there will be no replacement, but as that discussion goes on I'll be sure to keep this document updated.

@Forgind and @rainersigwald can you spot-check the details?

I reworded slightly the last area under discussion, so this should be ready to go.


New SecurityHub standards support

Solves #112

@lukaspour Sorry for the delay! LGTM, thanks for the PR!


Leading Comments - can they not affect if other things break?

There are a number of issues popping up around comments causing lines to break. Some code was already added to pull comments outside of a group, but is there a better solution to keep comments from causing groups to break? Or do we have to adjust each node type to deal with comments?

It appears leading comments only affect some edge cases, and most of them have been easy to deal with.
The problem is less with leading comments, and more with how the doc tree is built up.


How to set the lane follow distance when there is a special vehicle in front of ego car?

In some scenarios, keep safe distance from some special vehicles is necessory, but I can't find an easy way to reach this goal. I have almost read all codes of planning module but still can't solve this problem. Can you offer me some suggestions? I know it may be in speed planning module.
System information

Linux Ubuntu 18.04:
Apollo installed from binary:
Apollo version 8.0:

Supporting materials (screenshots, command lines, code/script snippets):

Here it is:
In nonlinar optimizer: https://github.com/ApolloAuto/apollo/blob/d5f88cb390d01cc15bc11d9af484d8e5a34d218f/modules/planning/tasks/optimizers/piecewise_jerk_speed/piecewise_jerk_speed_nonlinear_optimizer.cc#L286C69-L286C69
In linar optimizer:
https://github.com/ApolloAuto/apollo/blob/d5f88cb390d01cc15bc11d9af484d8e5a34d218f/modules/planning/tasks/optimizers/piecewise_jerk_speed/piecewise_jerk_speed_optimizer.cc#L114

Thanks!


v2.0.0beta issues

When I use v2.0.0beta instead of v1.2 I have the following issues:
$ pip --version
pip 1.5.6 from /builds/pod/sls-stacks/venv/local/lib/python2.7/site-packages (python 2.7)
$ sls deploy -s staging
Serverless: Installing required Python packages...

  Error --------------------------------------------------

Usage:
  pip <command> [options]

no such option:
     --isolated

When I upgrade to pip 9.0.1 I still get the following error:
$ SLS_DEBUG=* sls deploy -s staging
Serverless: Installing required Python packages...
Serverless: Linking required Python packages...

  Error --------------------------------------------------

     EEXIST: file already exists, symlink '.requirements/tests'
     -> './tests'

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

  Stack Trace --------------------------------------------

Error: EEXIST: file already exists, symlink '.requirements/tests' -> './tests'
    at Object.fs.symlinkSync (fs.js:1019:18)
    at fse.readdirSync.map.file (/usr/local/lib/node_modules/serverless-python-requirements/index.js:83:13)
    at Array.map (native)
    at ServerlessPythonRequirements.linkRequirements (/usr/local/lib/node_modules/serverless-python-requirements/index.js:82:40)
    at runCallback (timers.js:651:20)
    at tryOnImmediate (timers.js:624:5)
    at processImmediate [as _immediateCallback] (timers.js:596:5)
From previous event:
    at PluginManager.run (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:160:22)
    at Serverless.run (/usr/local/lib/node_modules/serverless/lib/Serverless.js:91:31)
    at serverless.init.then (/usr/local/lib/node_modules/serverless/bin/serverless:23:50)

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues

     Please report this error. We think it might be a bug.

  Your Environment Information -----------------------------
     OS:                 linux
     Node Version:       7.6.0
     Serverless Version: 1.6.1

ERROR: Build failed: exit code 1

With v1.2 everything works fine.

Yeah, i should document and add a check that a newish version of pip is required (the docker way automatically upgrades it, but I don't feel comfortable upgrading stuff on a users box).
The second error is because you have a library called test required and a dir in your service by the same name. I'll at least make the code catch the linking error and explain it, not sure what else to do with out requiring you to alter your code like in v1. It'll of course work if you use the zip method which does still require you to change your code.


[Bug]: Navigating to about:blank fails non-headless (regression in 14.0.0)

Bug description
Navigating to about:blank when not headless works fine with<EMAIL_ADDRESS>but fails with 30s timeout on 14.0.0:
const puppeteer = require('puppeteer');
(async () => {
  const browser = await puppeteer.launch({headless: false});
  const page = await browser.newPage();
  await page.goto('about:blank');
  console.log('ok');
  await browser.close();
})();

Headless mode works also on 14.0.0.
Puppeteer version
14.0.0
Node.js version
16.15.0
npm version
8.5.5
What operating system are you seeing the problem on?
macOS
Relevant log output
No response

Hey, thanks for the report! Unfortunately, it's a bug upstream (Chromium M102) and we added a workaround for it yesterday https://github.com/puppeteer/puppeteer/pull/8330 (to be released soon). The upstream issue is also fixed and it will be back-merged into the m102 branch (crbug.com/1324138) and then hopefully we are able to re-roll the Chromium binary and remove the workaroound.

The workaround is released in 14.1.0.

Thanks, this seems to work in 14.1.0 and 15.3.1 (latest), closing issue.


Next.js buld. TradingView is not defined for SymbolOverview component

I am using Next.js. Everything works fine for dev mode.
The application crush for "SymbolOverview" component if "npm run build" --> npm start -->ReferenceError: TradingView is not defined
Steps to reproduce:

npx create-next-app@latest --ts
npm i react-ts-tradingview-widgets
pages/index.tsx :
`import type { NextPage } from "next";
import { SymbolOverview } from "react-ts-tradingview-widgets";

import styles from "../styles/Home.module.css";
const Home: NextPage = () => {
return (

<SymbolOverview symbols={[["BIB"]]} width="100%" />

);
};
export default Home;`

npm run build
npm start

Hey, will look into this when I get home from work.

Not sure how to fix this yet, but for now you can manually load the needed script in the _document.tsx file:
`import { Html, Head, Main, NextScript } from "next/document";
import Script from "next/script";
export default function Document() {
return (

);
}`

What is the difference with your code and this? -> https://github.com/JorrinKievit/react-ts-tradingview-widgets/blob/main/src/components/Widget.tsx with https://github.com/JorrinKievit/react-ts-tradingview-widgets/blob/main/src/components/SymbolOverview.tsx
The scripts required by the widgets are not loaded by NextJS because of server side rendering

After consideration I think you should disable SSR and render the charts client side, example below:
const Home: NextPage = () => {
  const SymbolOverviewWidget = dynamic(
    () =>
      import("react-ts-tradingview-widgets").then((mod) => mod.SymbolOverview),
    { ssr: false }
  );

  return (
    <div className={styles.container}>
      <SymbolOverviewWidget colorTheme="dark" />
    </div>
  );
};

export default Home;

I don't know how I looked over this for so long, fixed in version 1.0.12. You should still import the charts dynamically ->
const SymbolOverviewWidget = dynamic(
  () => import("react-ts-tradingview-widgets").then((w) => w.SymbolOverview),
  {
    ssr: false,
  }
);```

Thanks a lot. For me iin v 1.0.12 it working even without dynamic import


Command Palette Revert File does nothing.

VSCode Version: 1.20.1 (1.20.1)
OS Version: OS X 10.12.6

Steps to Reproduce:

open file -> make changes -> cmd+shift+p -> revert file -> file is not reverted.
open file -> make changes -> select File > Revert File -> file is reverted.

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

@chrmarti fyi https://github.com/Microsoft/vscode/issues/44057#issuecomment-367070742 makes no sense

Why was this closed? It is not a duplicate of the referenced tickets.

/findDuplicates

Better :)


Announcement: RealSense SDK version 2.35.0 now available

Hi everyone,
Version 2.35.0 of the RealSense SDK, which contains a substantial number of bug-fixes and improvements, is now available from the link below.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.35.0
API CHANGES
RS2_OPTION_THERMAL_COMPENSATION - Provisioning for Thermal Compensation mechanism for selected SKUs.
https://github.com/IntelRealSense/librealsense/wiki/API-Changes#version-2350
NEW FEATURES

Extended cam sync mode to support full slave and genlock modes
D4xx: Firmware version <IP_ADDRESS>.
T265: Firmware version <IP_ADDRESS>1.

Make initial yaw consistent when starting forward, backward, up and down.
Fix intermittent descriptor / imu corruption

The full release notes, including all linkages and a list of bug-fixes and improvements, documentation changes and unresolved Known Issues, can be read here:
https://github.com/IntelRealSense/librealsense/wiki/Release-Notes#release-2350

We may have an issue with the release, I'll re-open once its clear.


New config to turn off TypeScript autocomplete suggestions

A new typescript.suggestions.enabled config (boolean, default true)
Setting false removes all autocomplete suggestions provided by typescript via the built-in typescript-language-features extension.
The default is true, so that existing behaviour remains the same.
Why?
The typescript autocomplete suggestions are a great feature, when you're working on a typescript project.

But when you're working on a flow project using the flow-for-vscode plugin, it provides its own autocomplete suggestions via flow. So your autocomplete gets littered with duplicate suggestions coming from both typescript and flow:

What this config does is turns off the typescript suggestions, so you get this instead:

I.e. no duplicates, only theflow-for-vscode suggestions. Problem solved.
Prior Issues
There have been a few existing issues raised about this problem both on the flow-for-vscode project and here.

This one
Which leads to this one
Which leads to this one, which claims to address the problem.

Quoting from the third issue there

We have requests to support disabling all TS functionality. Instead of introducing a setting we should allow disabling built in extensions.

So, what am I doing submitting a PR for a setting? Why doesn't #17068 solve the problem?
Well, the thing is, as I commented here, I don't want to disable all of the javascript & typescript extension. I only want to disable the autocomplete suggestions coming from typescript.
Why? Because the extension also provides some other functionality I can't do without.

Cmd+click to imports and variable definitions
Name based suggestions in js
There may be others (I haven't spent enough time with the extension turned off to find them all!)

It's actually worse to lose this functionality, than to just deal with the duplicates in autocomplete. So this is definitely not a solution to the problem.
I really believe vscode needs the ability to turn off typescript autocomplete, specifically. Flow support provided via the awesome flow-for-vscode combined with all of the rest vscode's great feature set makes it a really good editor for flow projects, but this autocomplete issue is one of the last remaining obvious and annoying things that just get in the way of productivity. And it's so easy to fix!

Just a note, my PR here is just a reference implementation to highlight how simple this change could possibly be to land. I have tested it in real usage and with my own workflow it is working well, but I may have missed some corner cases / features I don't use. I'm more than happy to fix anything that's pointed out myself, or just to have this completely redone by someone who knows more in depth about how this could be done better if my implementation is too simple/naive. I just want this feature in mainline vscode! And I know a lot of other people do too.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: davnicwil sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

The idea behind this PR seems fine. However I believe this new setting should disable all completions from js/ts, including name based suggestions. This is what similar settings like javascript.format.enable and javascript.validate.enable do, as it lets another extension fully take over responsibility for these areas
Also keep in mind that we make no guarantees that our built-in js/ts support will work at all for flow code (and operations like formatting or refactoring may even break flow code). That's why we recommend disabling the built-in js/ts support if you are using the flow extension. The flow extension really needs to implement these tooling feature on their side to ensure they work properly

Great. You are right about the approach of having extensions take over full responsibility for things being better. But that might take a while and this config change is pretty simple (and would also be simple to remove later) and solves the problem today.
I will remove the distinction between name suggestions / others, and just have it disabled every suggestion. You make a good point that it would break from the convention a bit.

You can now manage built-in extensions: https://code.visualstudio.com/updates/v1_21#_extensions which will disable TS/JS autocomplete and you can easily use flow in VS Code, so why this is needed? Or I'm missing something?

If you disable the builtin "TypeScript and JavaScript Language Features" extension, you'll loose a whole lot of other things than autocomplete suggestions, too. JSDoc completion, symbol renaming etc.
Although @mjbvz does make a valid point about those being the responsibility of the Flow extension in this case.

@noppa Thanks, good to know. Also, I totally agree with @mjbvz it is Flow extension responsibility, but as I know they actually don't care and to be honest TypeScript is way better since it works way faster, you get refactoring for file names, paths, etc. If you really want good support for Flow and to use VS Code you should create your own extension.
Maybe it makes sense to control built-in JS/TS language features instead of disabling them all, like checkboxes with variuos features like renaming, jsdoc completion, linting, autocompletion, etc. I believe it would be good feature request.

Just a heads up:  I'm renaming this setting to typescript.suggest.enabled and javascript.suggest.enabled to be consistent with our other extensions


add hinit to options to help user

Ran cmake-format

[approve ci]

PR title says "hinit", but it should say "hint".

Most of this PR is formatting changes - could you undo those to make the actual change clearer?

The formatting changes are done by the formatter we agreed to use for consistency. Maybe it can be split into 2 separate commits?


The token endpoint should get from the well-known configuration

Fixes #7952
Motivation
Currently, the token endpoint is created by append '/oauth/token' directly,
we should fetch the token endpoint from the well-known configuration.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


Need More robust ways to exclude multiple directories, paths, and/or files

./jsdoc --help shows no way to set ignore of directories, whereas jsdoc-toolkit provided for the -nocode flag (only documenting anything with an @name, though I didn't find this as useful as the ability to ignore directories, or at the very least set a recursion depth (though, again, recursion depth is more useful if you can set explicit directories/paths to ignore)).
I keep getting java.lang.OutOfMemoryError: Java heap space errors when running against an entire solution (on a latest gen MBP that is maxed out), since there is a lot to recurse in the entire solution (some of which I want to flat out ignore, such as 3rd party libraries). The addition of this ability would add a lot of flexibility...unless I'm missing something in --help or the sparse documentation that provides for this.
The excludePattern handles this somewhat, but its more problematic for multiple directories, files, and/or patterns to exclude.

care to share the solution thanks


Autocomplete and syntax highlighting in embedded queries very slow

Version and Environment Details
Operation system:
macOS 10.15.4
IDE name and version:
PhpStorm 2020.1
Build #PS-201.6668.153, built on April 13, 2020
Plugin version:
2.4.0
Schema stats:
472 types, 20 interfaces, 82 inputs, 30 enums, 13 unions, 1 scalars, 5 directives
Expected Behaviour
The syntax highlight should be instant and the other two mentioned functions also shouldn't take longer than a second ideally.
Actual Behaviour
We found that in queries which are embedded in our javascript files the syntax highlighting takes 5sor more seconds to show up. Opening our schema.graphql directly does not show the same behaviour there.
The Navigation on query fields (Cmd+Click on mac) sometimes takes several seconds till PHPStorm jumps to the schema.
The autocomplete popup when typing a new field in a query or pressing Ctrl+Space to open the autocomplete takes also several seconds.
Sometimes syntax highlighting never kicks in, but the navigation still works.

We have a rather large (I think) schema, so that might be too much to handle?
Steps to Reproduce / Link to Repo with Reproduction and Instructions
I cannot share our schema but I'm happy to provide profiling snapshots if you tell me how to create them.

Hi Daniel.
I did a lot of work to make the plugin usable with the GitHub schema which is also quite large (326 types). I just tested with a gql tagged query and while it's not instant, completion and highlighting is still usable: http://g.recordit.co/ziz64sLenY.gif
Given that the plugin looks for gql in all javascript and typescript file types, you could see a performance gain by limiting which of these files are part of your schema. You can use the includes glob in your .graphqlconfig file to manage this. See https://jimkyndemeyer.github.io/js-graphql-intellij-plugin/docs/developer-guide#project-structure-and-schema-discovery
Let me know what you find.
Best regards,
Jim.

I tried adding includes and excludes, but that did not help.
Is there any way to debug, so I could check what is taking so long sometimes, or why syntax highlighting does not kick in at all in some files?

Hi Daniel.
The perf issue could be due to hitting a GC limit. Have you tried increasing the memory using Help> Edit custom VM options...:
For larger projects I have increased the defaults to:
-Xmx4g
-XX:MaxPermSize=1g

If you already have enough memory I suggest you download a trial of IntelliJ Idea Ultimate and check out the source code of the this plugin. To start the plugin in a sandbox you can profile the runIde gradle task. As mentioned I already uses JProfiler when I looked at perf for the GitHub schema so it'd be interesting to see what's happening in your project setup.
Best regards,
Jim.

I have tried what you suggest, and what worked for me was reducing the scope of the includes glob. The performance is directly related to the amount of files being included: very responsible (1-2s) if 1 file is included, less responsive (3-5s) if 50 are included and terrible if 500 are included (10-15s)

To add to the last comment of Rendez: we have 2200 graphql template strings (across 2000 files) in the codebase so far, which most of the contain one fragment or less often one mutation.
The schema itself is now:
543 types, 22 interfaces, 125 inputs, 50 enums, 19 unions, 1 scalars, 6 directives
I also run a profiler run on our codebase (it includes startup, fileindexing and highlighting of one graphql template string in one file). I myself can't make anything of this, as I don't see any timings at all there. So not sure how to work with intellijs profiler interface.
https://github.com/danez/graphqlplugin-profile
Do you have any idea?

We're not acquainted with Java and specially Intellij plugins, I did what you suggested and run gradle runIde to get Intellij in a sandbox. I only see traces from .diagnostic.PerformanceWatcher, which may or not be useful to determine plugin's performance, how do I run jProfiler while in sandbox? In any case, I attach the logs that I got when the UI freezed (which seems to be what I got for free):
2020-04-14 17:42:00,417 [ 902434]   WARN - .diagnostic.PerformanceWatcher - UI freezed for 8176ms, details saved to /Users/merino/dev/js-graphql-intellij-plugin/build/idea-sandbox/system/log/threadDumps-freeze-20200414-174152-IU-193.6494.35-ConcurrentHashMap.computeIfAbsent-8sec
2020-04-14 17:42:25,474 [ 927491]   WARN - .diagnostic.PerformanceWatcher - UI freezed for 7880ms, details saved to /Users/merino/dev/js-graphql-intellij-plugin/build/idea-sandbox/system/log/threadDumps-freeze-20200414-174217-IU-193.6494.35-TIntObjectHashMap.index-7sec
2020-04-14 17:46:54,410 [1196427]   WARN - .diagnostic.PerformanceWatcher - UI freezed for 5991ms, details saved to /Users/merino/dev/js-graphql-intellij-plugin/build/idea-sandbox/system/log/threadDumps-freeze-20200414-174648-IU-193.6494.35-_JSXLexer.advance-5sec
2020-04-14 17:47:24,729 [1226746]   WARN - .diagnostic.PerformanceWatcher - UI freezed for 10017ms, details saved to /Users/merino/dev/js-graphql-intellij-plugin/build/idea-sandbox/system/log/threadDumps-freeze-20200414-174714-IU-193.6494.35-Unsafe.park-10sec
2020-04-14 17:49:04,961 [1326978]   WARN - .diagnostic.PerformanceWatcher - UI freezed for 5393ms, details saved to /Users/merino/dev/js-graphql-intellij-plugin/build/idea-sandbox/system/log/threadDumps-freeze-20200414-174859-IU-193.6494.35-UserDataHolderBase.putUserData-5sec
2020-04-14 17:49:47,312 [1369329]   WARN - .diagnostic.PerformanceWatcher - UI freezed for 5512ms, details saved to /Users/merino/dev/js-graphql-intellij-plugin/build/idea-sandbox/system/log/threadDumps-freeze-20200414-174941-IU-193.6494.35-Throwable.fillInStackTrace-5sec
2020-04-14 17:52:51,315 [1553332]   WARN - .diagnostic.PerformanceWatcher - UI freezed for 5411ms, details saved to /Users/merino/dev/js-graphql-intellij-plugin/build/idea-sandbox/system/log/threadDumps-freeze-20200414-175245-IU-193.6494.35-LeafElement.leafTextMatches-5sec

log.zip

Ok, so I managed to profile runIde, here's a JProfiler snapshot:
graphql-completions-snapshot.jps.zip

Any news on the status of this one? We have a large schema as well (101 types) and it appears that the issue is the GC limit as adding the vmoptions fixed it

I am using hasura and easily reached
751 types, 1048 inputs, 150 enums, 21 scalars
That makes using this plugin pretty much unusable. I tried the suggested fixes, but doesn't seem to work.


I am getting deployment successful message on vs code but not reflecting changes in deployment center (Azure app service)

•	VS Code’s App Service extension utilizes zip deploy method for deployment.
•	When deployment is initiated, the extension should make a POST request to ‘/api/zipdeploy’ followed by a GET request to ‘/api/deployments/latest’ which would then redirect to the latest set of logs for the ongoing deployment.
•	In my case, no requests are being made to ‘/api/zipdeploy’ , but directly to GET ‘/api/deployments/latest’  which in turn is helping return the logs from the last available successful deployment data.

Is anyone looking into this issue ?

Hi @bhushan-ss
How did you deploy to the web app for the successful case? Is the deployment method for your current web app still set to "None"? "None" would be using the zip deploy API.
Could you please share some screen shots of your deployment?

Today, I tried to deploy my code from vs code, it worked and code deployed successfully to azure app service.
Whenever I deploy code, I just right click on the folder/directory from vs code and it gives me an option 'deploy to web app'. Through Azure authentication I select the instance(created app service) and deploy on it. And when code is deployed, pop-up message comes stating the deployment is successful.

Above image shows how I deploy the code.

Above screenshot is taken when there was issue.
It is initiating deployment from VS code at 3.58 PM IST, but instead of deploying the code it was just pulling in logs from last successful deployment done via Local Git at 3.53 PM IST. At the same time I had confirmed with Azure tech support team that no new deployment requests were reaching to them for their zip deployment endpoint on which VS code was supposed to perform deployment on.
This is frequent behavior while deploying code from VS code.

Hi @nturinski , Can you please check this ?


Incompatible with kong 3.x

Hello, first thing first, thanks for your work!
I'd like to report that the plugin does not work on kong 3.x + due to this: https://github.com/Kong/kong/pull/8874
(Partial) Stack trace:
Jul 07 12:19:56 ip-10-0-0-142 kong[25264]: Error: /usr/local/share/lua/5.1/kong/tools/utils.lua:710: error loading module 'kong.plugins.kong-upstream-jwt.handler':
Jul 07 12:19:56 ip-10-0-0-142 kong[25264]: .../share/lua/5.1/kong/plugins/kong-upstream-jwt/access.lua:4: module 'kong.singletons' not found:No LuaRocks module found for kong.singletons

@skyreginag Thanks for the feedback, if you have a chance to hack in the raw source code changes with your deployment feel free to try this: https://github.com/Optum/kong-upstream-jwt/pull/30 and see if that fixes all the errors you see and plugin is working for your use case once more!

Should be fixed w latest release so closing this.


Fix updating legacy projects using CPM

Updating currently fails for projects using the old project style with central package management, due to an oversight in #538.
Projects using the old project style need to remove the package before updating (due to a long standing NuGet bug), but this is not necessary or possible when using CPM.
This PR adds a check to avoid attempting to remove the reference if the package is centrally managed.

When can I expect this change to be included in a release?


Object referance not set to an instance of  an object

I keep getting this error
NullReferenceException: Object reference not set to an instance of an object EpicTransport.EOSSDKComponent.Tick () (at Assets/Mirror/Runtime/Transport/EpicOnlineTransport/EOSSDKComponent.cs:147) EpicTransport.EosTransport.ServerEarlyUpdate () (at Assets/Mirror/Runtime/Transport/EpicOnlineTransport/EosTransport.cs:106) Mirror.NetworkServer.NetworkEarlyUpdate () (at Assets/Mirror/Runtime/NetworkServer.cs:1717) Mirror.NetworkLoop.NetworkEarlyUpdate () (at Assets/Mirror/Runtime/NetworkLoop.cs:193)

I believe you have the EOSSDKComponent on the same object as the NetworkManager and you use the offline/online scene feature. This will destroy the network manager with the EOSSDKComponent and recreate it in the next scene while switching from the online to the offline scene.
Move the EOSSDKComponent to its own object that is in DDOL to prevent this.


Add documentation for 'useTransferState'

This is one of the best features we have, and it isn't in the docs. It isn't discoverable on our site. There aren't any examples of it in our repo. We need something for this.
Also... this should prompt a larger ticket where we make sure that each API is in the docs. @SanderElias can you orchestrate that?

We should at least add a sample to this page:
https://scully.io/docs/Reference/ngLib/transfer-state-service/

We should add a ticket for all of our Angular-facing APIs to make sure that they are documented. The ScullyLibModule.forRoot API. The TransferState API. The ScullyRouteService API. And any others.
We shoudl create tickets for each of these to verify that the docs are up to snuff with the APIs, and htne we can mark then with the good-first-issue label so that the community can help us with them. On a meetup the other day, https://twitter.com/vneekman mentioned that he would help with these doc issues. I am guessing that some others would help with them too.

Also, We should create a couple of chapters to learn about things like transferstate. Not everything should go that, but at least transferState. Preferable including some video demo.

I just checked, all except the forRoot(config)  do already have some docs. Most of it does need some TLC tho.


[Improve] [Doc] Improve OSSFile Connector title

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
update OssFile  to OssFile[Jindo]  is better.

SeaTunnel Version
dev
SeaTunnel Config
*

Running Command
*

Error Exception
*

Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

please assign to me; thx。


[AUTO-PR] Automatically generated new release 2021-03-03T20:42:24.912Z

What are you changing?

[x] Releasing a new version of Notify
[ ] Changing kubernetes configuration

Provide some background on the changes
⚠ The production version of manifests is behind the latest staging version. Consider upgrading to the latest version before merging this pull request.
NOTIFICATION-API

Update AWS CLI when building containers (#1242) by Antoine Augusti

NOTIFICATION-ADMIN

Rate limit settings (#917) by Ren-David

NOTIFICATION-DOCUMENT-DOWNLOAD-API

Update AWS CLI when building containers (#27) by Antoine Augusti

NOTIFICATION-DOCUMENT-DOWNLOAD-FRONTEND

Increase keepalive between Gunicorn and LB (#35) by Antoine Augusti

NOTIFICATION-DOCUMENTATION

Update AWS CLI v2 when building containers (#66) by Antoine Augusti

If you are releasing a new version of notify, what components are you updating

[x] API
[x] Admin
[x] Document API
[x] Document UI

Checklist if releasing new version:

[x] I made sure that both API and Admin changes are present in Notify
[x] I have checked if the docker images I am referencing exist - ex: https://gallery.ecr.aws/v6b8u5o6/notify-admin

Checklist if making changes to Kubernetes:

[ ] I know how to get kubectl credentials in case it catches on fire

@jimleroyer Releasing this one before releasing the new navigation. Moved back the admin and document download frontend to appropriate versions. Update the PR description in consequence.


Infinite loop on events due to inacurracy between seconds and miliseconds ?

My bot has been stuck reposting the same event over and over.
From my investigation, I'm surprised the problem didn't seem to emerge earlier and I don't totally get it.
curl 'https://api.opensea.io/api/v1/events?collection_slug=cryptocubes&occurred_after=1645787316' -H 'Accept: application/json' -H "X-API-KEY: $API_KEY" | jq '.asset_events[-1]'

Result
{
  "approved_account": null,
  "asset": {
    "id": 17168260,
    "num_sales": 3,
    "background_color": null,
    "image_url": "https://lh3.googleusercontent.com/1juN1Mbi52rVbspQtDG9-Ichs8_WdCH2L6gwx3yFlpv-PKfETMZ8haemFX8veXul31wwLb_ScwxIN0RkDUPF8gMmKQ",
    "image_preview_url": "https://lh3.googleusercontent.com/1juN1Mbi52rVbspQtDG9-Ichs8_WdCH2L6gwx3yFlpv-PKfETMZ8haemFX8veXul31wwLb_ScwxIN0RkDUPF8gMmKQ=s250",
    "image_thumbnail_url": "https://lh3.googleusercontent.com/1juN1Mbi52rVbspQtDG9-Ichs8_WdCH2L6gwx3yFlpv-PKfETMZ8haemFX8veXul31wwLb_ScwxIN0RkDUPF8gMmKQ=s128",
    "image_original_url": "https://ipfs.io/ipfs/QmQQPBFQ221xKcMo31k4pKbEwQwHAZugV2qHjWhdGZ47c8/image.gif",
    "animation_url": null,
    "animation_original_url": null,
    "name": "CryptoCube#136",
    "description": "Join the punk movement.  \n\nExhibit your CryptoCube in 3d platforms.",
    "external_link": "https://app.rarible.com/token/0xdbb163b22e839a26d2a5011841cb4430019020f9:152",
    "asset_contract": {
      "address": "0xdbb163b22e839a26d2a5011841cb4430019020f9",
      "asset_contract_type": "non-fungible",
      "created_date": "2020-10-04T16:51:37.658205",
      "name": "CryptoCubes",
      "nft_version": "3.0",
      "opensea_version": null,
      "owner": 12077606,
      "schema_name": "ERC721",
      "symbol": "CC",
      "total_supply": "0",
      "description": "CryptoCubes are algorithmically generated metaverse-native 3d NFT collectibles.\r\n\r\nLimited to 256\r\n\r\nCreated by Han.",
      "external_link": "https://app.rarible.com/collection/0xdbb163b22e839a26d2a5011841cb4430019020f9",
      "image_url": "https://lh3.googleusercontent.com/X_V_EbYK5XpjO_j1AETDTUkolFCx-HJzcpM5TtMbI3bVN1ny4wVvXcX_BYzcAkzbTHjtW0mgGNmqOSRiejhr3tPt=s120",
      "default_to_fiat": false,
      "dev_buyer_fee_basis_points": 0,
      "dev_seller_fee_basis_points": 1000,
      "only_proxied_transfers": false,
      "opensea_buyer_fee_basis_points": 0,
      "opensea_seller_fee_basis_points": 250,
      "buyer_fee_basis_points": 0,
      "seller_fee_basis_points": 1250,
      "payout_address": "0xbf28421a82186bf50f496ab937c3368b55adbf19"
    },
    "permalink": "https://opensea.io/assets/0xdbb163b22e839a26d2a5011841cb4430019020f9/152",
    "collection": {
      "banner_image_url": "https://lh3.googleusercontent.com/eMwxxLlB7W8Psnr61OLliEFQlA8Bt5Y4tz1KXiEZaDD83t4IxIJcQMIZfm9ClVr5ATBOZxSLKcuGhtV_kdl4dVcs=s2500",
      "chat_url": null,
      "created_date": "2020-10-20T19:31:14.007197",
      "default_to_fiat": false,
      "description": "CryptoCubes are algorithmically generated metaverse-native 3d NFT collectibles.\r\n\r\nLimited to 256\r\n\r\nCreated by Han.",
      "dev_buyer_fee_basis_points": "0",
      "dev_seller_fee_basis_points": "1000",
      "discord_url": "https://discord.gg/cryptocubes",
      "display_data": {
        "card_display_style": "contain"
      },
      "external_url": "https://app.rarible.com/collection/0xdbb163b22e839a26d2a5011841cb4430019020f9",
      "featured": false,
      "featured_image_url": null,
      "hidden": false,
      "safelist_request_status": "verified",
      "image_url": "https://lh3.googleusercontent.com/X_V_EbYK5XpjO_j1AETDTUkolFCx-HJzcpM5TtMbI3bVN1ny4wVvXcX_BYzcAkzbTHjtW0mgGNmqOSRiejhr3tPt=s120",
      "is_subject_to_whitelist": false,
      "large_image_url": "https://lh3.googleusercontent.com/X_V_EbYK5XpjO_j1AETDTUkolFCx-HJzcpM5TtMbI3bVN1ny4wVvXcX_BYzcAkzbTHjtW0mgGNmqOSRiejhr3tPt",
      "medium_username": null,
      "name": "CryptoCubes",
      "only_proxied_transfers": false,
      "opensea_buyer_fee_basis_points": "0",
      "opensea_seller_fee_basis_points": "250",
      "payout_address": "0xbf28421a82186bf50f496ab937c3368b55adbf19",
      "require_email": false,
      "short_description": null,
      "slug": "cryptocubes",
      "telegram_url": null,
      "twitter_username": "CubesCrypto",
      "instagram_username": null,
      "wiki_url": null
    },
    "decimals": 0,
    "token_metadata": "https://ipfs.io/ipfs/QmaMDuYvnNU9HcLKXm419Lu3KafRPt56kccj7xmtHJiRtU",
    "owner": {
      "user": {
        "username": "Futureis"
      },
      "profile_img_url": "https://storage.googleapis.com/opensea-static/opensea-profile/23.png",
      "address": "0x1fdc7ec0a099dadf4643faea7cd0fcee23075932",
      "config": ""
    },
    "token_id": "152"
  },
  "asset_bundle": null,
  "auction_type": null,
  "bid_amount": "10000000000000000000",
  "collection_slug": "cryptocubes",
  "contract_address": "0x7f268357a8c2552623316e2562d90e642bb538e5",
  "created_date": "2022-02-25T11:08:36.706701",
  "custom_event_name": null,
  "dev_fee_payment_event": null,
  "dev_seller_fee_basis_points": 1000,
  "duration": null,
  "ending_price": null,
  "event_type": "offer_entered",
  "from_account": {
    "user": {
      "username": "M4T"
    },
    "profile_img_url": "https://storage.googleapis.com/opensea-static/opensea-profile/15.png",
    "address": "0x6bf97f2534be2242ddb3a29bfb24d498212dcded",
    "config": ""
  },
  "id":<PHONE_NUMBER>,
  "is_private": null,
  "owner_account": null,
  "payment_token": {
    "id": 2,
    "symbol": "WETH",
    "address": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2",
    "image_url": "https://storage.opensea.io/files/accae6b6fb3888cbff27a013729c22dc.svg",
    "name": "Wrapped Ether",
    "decimals": 18,
    "eth_price": "1.000000000000000",
    "usd_price": "2630.679999999999836000"
  },
  "quantity": "1",
  "seller": null,
  "starting_price": null,
  "to_account": null,
  "total_price": null,
  "transaction": null,
  "winner_account": null,
  "listing_time": null
}

The returned event created_date is 2022-02-25T11:08:36.706701
Now if we make a moment out of it, we get
> const moment = require('moment');
> moment("2022-02-25T11:08:36.706701").unix()
1645787316

The resulting request will be https://api.opensea.io/api/v1/events?collection_slug=cryptocubes&occurred_after=1645787316 again, and that will fetch and post the same event again. Just incrementing the timestamp by 1 will prevent the problem to happen (but we might miss some events !)
Am I the only one experiencing the problem ? Was occured_after exclusive of timestamp and became inclusive ?

looks like OpenSea recently changed their API without telling anyone, removing occured_after & replacing it with occured_before. PR's welcome

looks like OpenSea recently changed their API without telling everyone, removing occured_after & replacing it with cursors.
PR's welcome

How would we go about fixing this? Replacing occured_after with cursor?
(Sorry, barely know what I'm doing when it comes to coding. Haha)

@AstralsCoding not to diminish dsgriffin's work here (which is superb) but id highly recommend you use his other work here which relies tools like Alchemy or Moralis for getting the actual transactions from the blockchain and only relies on OS for getting nft metadata.
As OS continues to lose marketshare and trust - no point in making your API entirely reliant on them.

@skiisinjeans Cheers, I'll look into it!

Should be resolved now, see
https://github.com/dsgriffin/opensea-sales-twitter-bot/issues/21#issuecomment-1071317313


dbstat virtual table is not available on Android

Virtual dbstat table is not available on Android, but iOS works fine.
SELECT SUM("pgsize") FROM "dbstat" WHERE name='<any existing table name>'

Expected Behavior
This query should return calculated size in bytes for this table on Android.
Current Behavior
Database throws an error:
query failed:  SELECT SUM("pgsize") FROM "dbstat" WHERE name='<any existing table name>'
"no such table: dbstat (code 1 SQLITE_ERROR): , while compiling: SELECT SUM("pgsize") FROM "dbstat" WHERE name='<any existing table name>'"

Possible Solution
Enable compile option SQLITE_ENABLE_DBSTAT_VTAB=1 for SQLite on Android
Steps to Reproduce (for bugs)

Use latest<EMAIL_ADDRESS>Install react-native-sqlite-database (i'm using it with TypeORM)
Run query: SELECT SUM("pgsize") FROM "dbstat" WHERE name='<any existing table name>'

Your Environment

React Native SQLite Storage Version used: 4.1.0
React Native version used: 0.61.2
Operating System and version (simulator or device): MacOS 10.14.6 or MacOS 10.15
IDE used: WebStorm
Link to your project: under NDA

Debug logs
ExceptionsManager.js:118 query failed:  SELECT SUM("pgsize") FROM "dbstat" WHERE name='templateConfiguration'
"no such table: dbstat (code 1 SQLITE_ERROR): , while compiling: SELECT SUM("pgsize") FROM "dbstat" WHERE name='<any existing table name>'"

Could you please guys advice a workaround maybe how to get table size in bytes for Android?
This solution works fine fo iOS, but not for Android. I s it possible to enable dbstat virtual table for Androids too? Thanks a lot

I am not sure but can you please try to see the database in Android Studio? You can find any clue if it is creating the table in the DB or not?
Here is the way you can see the database in Android Studio
How to See SQLite Database Data Saved in Device using Android Studio


Expand on caller information

That said, I just learned about the utility of the various caller information attributes as described at https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/caller-information. These are great,  but I often have a number of classes that implement an interface and thus all use the same member name. I'd like to be able to use this in my logging, but differentiate by the caller type, but this doesn't appear to be obtainable from the various attributes.
Thus, I'd like to file a feature request for a CallerMemberType attribute to return the type of the member that called the method. Ideally, it'd follow the same implementation approach as CallerMemberName:
public class SomeClass
{
  public void SomeMethod([CallerMemberType]string memberType = "")
  {
    Console.WriteLine(memberType); //Ideally, this outputs the type of the calling method
  }
}

Just as the caller info for the method name is emitted as a literal at compile time, so too it seems like the method type could be emitted in a similar manner.
I appreciate you considering this request!
Also, if this is the wrong place to have filed this issue, please point me to the correct repo and I'd be happy to open a new issue.

Issue moved to dotnet/runtime #34695 via ZenHub


Create a user profile page that opens when a user clicks on their profile picture

Hey @AtriSukul1508 , I would like to  work on this issue under JWOC. Can you assign it to me?

I would like to work on this issue under JWOC. Can you assign it to me?

@Laxmankohar  Since you are already working on an issue, i cannot assign you

@VaibhavTalkhande Assigned, while creating a PR, make sure to attach a screenshot and maintain the current color combination

@AtriSukul1508 ok i will do it

i am not able to run this project on my machine . you can assign it other person.
sorry for inconvenience.

@Laxmankohar you can now work on that

@AtriSukul1508 , I think i have to set profile picture on profile icon on the navbar beside logout button.

@Laxmankohar any updates?

@AtriSukul1508 , I am getting this error, how can i resolve it?

@Laxmankohar Yeah but you can just use a placeholder values for now, i will implement the signup functionality later

@Laxmankohar Yeah but you can just use placeholder values for now, i will implement the signup functionality later

I am not getting. Can you please elaborate a little more.

@Laxmankohar just create a static page, i will add the required infos of the user later

@Laxmankohar just create a static page, i will add the required infos of the user later

@AtriSukul1508 , like this?

Yeah

when i click on the profile of user in the navbar,profile component render but the content inside profile page is not displaying, what would be the reason?

@AtriSukul1508 bro, please check and confirm it.
https://user-images.githubusercontent.com/73365025/223692336-0fdb6935-427f-44b8-a023-bd05ad98bc9c.mp4

Hey, @Laxmankohar There's just a box popping up

Hey, @Laxmankohar There's just a box popping up

yes, What you need then?

@Laxmankohar , There should be an entire page, doesn't need to contain a lot of complex functionality, but a decent one would be fine since there is no authentication at the moment, just use placeholder values for username, email, etc.

So, should i  kept the popping box or not?

@Laxmankohar example website - https://dribbble.com/shots/17219796-My-details-settings-page-Untitled-UI

React App - Google Chrome 2023-03-09 15-08-07.zip

Nice, make sure you fetch the repo before making the PR

Ok.


Add keys function for Map objects

See https://github.com/json-path/JsonPath/issues/439

is this good? can you merge?

I really need this function, can you merge,? thanks


context menu position is not consistent

I've been struggling for a while with the context menu, I already noticed it didn't position correctly between layers panel and layer panel, and it is still more evident in the edit geometry panel

the markup for the ContextMenuFactory is different for the markup in the header, and while being the same in layers panel and edit geometry panel it position the menu vertically centered so it varies depending on the height of the header
ideally we should use the same markup for this element, as well as the same markup for the three headers
involved templates
https://github.com/CartoDB/cartodb/blob/master/lib/assets/javascripts/cartodb3/editor/layers/layer-header.tpl
https://github.com/CartoDB/cartodb/blob/master/lib/assets/javascripts/cartodb3/components/context-menu-factory-view.js
https://github.com/CartoDB/cartodb/blob/master/lib/assets/javascripts/cartodb3/editor/editor-header.tpl

fixed!, but i'll take a look for consolidate some components, thanks @matallo


Nixpacks does not make the installed node_modules executables available

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
When building a node project with custom commands (i.e.: --build-cmd), the installed npm packages are not available to be used in the image.
For example, trying to build a Blitz project and passing blitz build to --build-cmd fails because blitz is not found.
Note that in a simple project, the build works without a custom command, but the point is that I'd expect whatever was installed to be available in the image.
To reproduce

Clone this repo: https://github.com/crondinini/blitzjs
Run nixpacks with: nixpacks . build --build-cmd 'blitz dev'
See the error:

[+] Building 36.6s (11/12)
 => [internal] load build definition from Dockerfile                                0.2s
 => => transferring dockerfile: 626B                                                0.1s
 => [internal] load .dockerignore                                                   0.2s
 => => transferring context: 2B                                                     0.0s
 => [internal] load metadata for ghcr.io/railwayapp/nixpacks:debian-1657820962      0.6s
 => [internal] load build context                                                   0.1s
 => => transferring context: 681.65kB                                               0.1s
 => [stage-0 1/8] FROM ghcr.io/railwayapp/nixpacks:debian-1657820962@sha256:f116f7  0.0s
 => CACHED [stage-0 2/8] WORKDIR /app/                                              0.0s
 => CACHED [stage-0 3/8] COPY environment.nix /app/                                 0.0s
 => CACHED [stage-0 4/8] RUN nix-env -if environment.nix                            0.0s
 => [stage-0 5/8] COPY . /app/                                                      0.1s
 => [stage-0 6/8] RUN --mount=type=cache,id=mgAt8pKUNJE-/usr/local/share/cache/ya  35.0s
 => ERROR [stage-0 7/8] RUN --mount=type=cache,id=mgAt8pKUNJE-node_modules/cache,t  0.4s
------
 > [stage-0 7/8] RUN --mount=type=cache,id=mgAt8pKUNJE-node_modules/cache,target=node_modules/.cache blitz dev:
#11 0.412 /bin/bash: line 1: blitz: command not found

Expected behavior
I'd expect the installed packages to be available by adding node_modules/.bin to the PATH.
Looking at the code for other providers, both python and ruby have a step during the install process that adds what looks like the bin folder related to the packages installed (I'm assuming this based on the folder name, but I could be wrong as I'm not familiar with those languages).
Environment
MacOS Monterey 12.4
nixpacks 0.2.11

That is a good idea.
In the meantime you can run npm|yarn|pnmp blitz dev and it will use the correct binary.

@coffee-cup Thanks for the quick reply!
In this case, I'm using npx in front of it to be able to retrieve it and that works fine.
AFAIK doing npm blitz dev would not work as it's not an npm command, this would have be inside the scripts for npm to find it, so something like npm run <script> (or yarn|pnpm equivalent), where <script> has the blitz command.
For the implementation, do you mind if we put a PR for it?

For the implementation, do you mind if we put a PR for it?

Not at all! It should be a fairly simple implementation.


pull request for e2e test at 11/25/2016 09:56:04

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Small amount of rotation does not appear to stick on first rotation

Describe the bug
I'm attempting to animate the rotation of my map in increments of 5 degrees.  There are a couple of cases where there appears to be a twitch in the display.
Here are a couple of animated gifs that highlight the issue (I'm assuming they are related):

Rotating from 0 to 5 degrees and clicking to pan the map resets to 0 degrees
I have a custom rotation button that rotates the map by 5 degrees.  The first time I click the button to rotate, the map rotates correctly.  But when I click on the map to try and pan it, it seems to reset to zero degrees rotation.
If I apply the rotation more than once, the subsequent rotations work and panning the map after them does not result in this reset behavior.  So, the reset behavior only appears to happen after the first 5 degree rotation.

During the second rotation the map flicks back to 0 and animates to 10 degrees
When I click to rotate by 5 degrees the second time it appears to flick back to zero and then animate to 10 degrees.  It's as if the results for the first animation aren't correctly saved somewhere (guessing).
After the second click of the rotate button, this does not occur.  However, if I use the OL rotate button to go back to zero, the problem shows up again on the second rotation click.

To Reproduce
I have a function I call that uses View#animate.  The code looks roughly like:
function rotate(map) {
  const degrees = 5;
  const radians = (degrees * Math.PI) / 180;
  const view = map.getView();
  const currentRotation = view.getRotation();
  const newRotation = currentRotation + radians;
  view.animate({
    rotation: newRotation,
    duration: 300,
  });
}

The twitch occurs on the second rotation, so doing something like the following should reveal the issue:
rotate(map); // first rotate from 0 to 5 degrees
rotate(map); // second rotate from 5 to 10 degrees where the twitch appears

That is expected behaviour. See the API https://openlayers.org/en/latest/apidoc/module-ol_View-View.html

Rotation constraint. false means no constraint. true means no constraint, but snap to zero near zero. A number constrains the rotation to that number of values. For example, 4 will constrain the rotation to 0, 90, 180, and 270 degrees.

The default is true snap to zero near zero  You either need to specify either  constrainRotation: false in the View constructor for no constraint or .constrainRotation: 72 for 5 degree intervals.

Ah, nice!  That was it.  Thank you so much for pointing that out.