Caret Positioning broken when input is within a shadow dom

When the text input element is part of the shadow tree of a web component, the caret always jumps to the end after any input.
This happens because the call to the caret() function doesn't actually set the caret position because of this line https://github.com/RobinHerbots/Inputmask/blob/5.0.0/lib/maskScope.js#L1956
When the focused input field is within a shadow dom, document.activeElement will be the element, for which the shadow dom was created and the input will actually be set on e.g. webComponent.shadowRoot.activeElement

@honboubao ,
Do you have a working example to test with?

This can be usefull
https://developer.mozilla.org/en-US/docs/Web/API/DocumentOrShadowRoot

Hi Robin!
sorry, I didn't wanna be rude and just drop this on your head without as much as a hello. I was just in a hurry but didn't want to wait to bring this to your attention.
Here is a reduced example that demonstrates the issue: https://plnkr.co/edit/iqwYXuwS3fGZO99uiXO3

@honboubao ,
No problem, I completely understand ;-)
Thank you for bringing this issue up.  Removing the activeelement check make it all work in the shadowdom, but I want to investigate it a bit more profound, ... maybe integrate it and add support for an inputmask htmlelement, ...

@honboubao ,
I added the input-mask html element.  If you want to use your own, you need to set the shadowRoot in the inputmask property on the input.
   class SuperDuperTextfield extends HTMLElement {
              constructor () {
                  super();
                  var shadow = this.attachShadow({ mode: "closed" });
                  var input = document.createElement("input");
                  input.type = "text";
                  shadow.appendChild(input);

                  new Inputmask({ mask: "9999-999-9999" }).mask(input);
                  input.inputmask.shadowRoot = shadow;
              }
          }

          customElements.define("super-duper-textfield", SuperDuperTextfield);

Hi @RobinHerbots
I'm investigating this case and I thought before I create a pull request out of nothing I inform you about my suggestion.
I decided to write here because the issue is not fixed yet. I tested your Inputmask inside a web-component.
First of all, I am not even sure if input.inputmask.shadowRoot is solving any case. But anyways, instead of differentiating between shadowRoot and document like you do in this line https://github.com/RobinHerbots/Inputmask/blob/ffeb767377b9b928ec3f9cb75af14d263a4cbbf3/lib/eventhandlers.js#L317
I would implement a method like:
function docGetActiveElement(){
 let el;
 let target = document;
 while(el = target.activeElement){
  if(el.shadowRoot){
     target = el.shadowRoot;
  } else {
    break;
  }
  return el;
}

This would solve all the cases if I am not wrong.. even the one you tried to fix with input.inputmask.shadowRoot.
if (docGetActiveElement() !== input) {
	input.focus();
}

What do you think @RobinHerbots ?

@artvel ,
I assume the issue occurs when you use the inputmask in your own web-component?
In that case the inputmask.shadowroot will always be undefined and it will not work.  Have a look at the inputmaskelement.js to see where the shadowroot gets defined.
I agree to put the (input.inputmask.shadowRoot || input.ownerDocument).activeElement in a separate funtion (module).
(use getActiveElement)
I read in https://developer.mozilla.org/en-US/docs/Web/API/Element/shadowRoot that I can check for the shadowRoot directly on the input itself. So I do not need to keep the shadowRoot myself.
About your code why do you need the while loop?

@RobinHerbots
because the actual issue is recursion.
Depending on how many web-components you have and if they are nested..
activeElement returns the next web-component with shadowRoot if the input is inside a web-component and it is active.

@RobinHerbots after investigating a little bit more I figured that there is one other small issue here.
When working with web-compoents all default events are being composed but the custom ones. You are using custom ones so if you want to solve this issue completely all events have to be configured with {composed:true} at the same level where you configure bubbles like {bubbles:true,composed:true}.
There is a "but" here. In one case you are using only the deprecated way to create a custom-event which does not support compose..

@artvel ,
Ok.
https://developer.mozilla.org/en-US/docs/Web/API/Element/attachShadow
mode
A string specifying the encapsulation mode for the shadow DOM tree. This can be one of:
open: Elements of the shadow root are accessible from JavaScript outside the root, for example using Element.shadowRoot:
element.shadowRoot; // Returns a ShadowRoot obj
Copy to Clipboard
closed: Denies access to the node(s) of a closed shadow root from JavaScript outside it:
element.shadowRoot; // Returns null
That is why I stored the shadowroot.
About the composed: true.  I think the browsers who still need the "deprecated" way of custom events, don't support an shadow dom anyway.  So that is not really a problem.
Ok send in the PR!  Thx.

@RobinHerbots Hello, I am facing the same problem.
I'm using VueJs with a custom root element - it creates a Shadow DOM. One of the application components contains a field for entering a phone number (with Inputmask). The caret always jumps to the end after any input.
How can i solve the problem? Thank you!


v 1.3 checklist

images for phase of the Moon
ADDED.

Is sunrise/sunset algorithm broken? I  think so, it does not change from day to day.
FIXED. Was repeating 'now' instead of using the date to be calculated. Otherwise, over some days, the times do not change much.

Include query end date in cache (first record)
FIXED. The cache table may be sparse or even empty, causing the code to think that the cache was
out of date or empty. Fixed by checking the user end date against the query end date, which
is now the first record in the table.

Need to be able to handle empty cache: if the returned table is empty, the query end date
is not written, which will cause the server to be hit unnecessarily. This is even likely because
the user may think there is an error. At this time, should also fix displaying some message when
the table is empty.
FIXED.

More consistent look for table titles?
DEFERRED.

Release v1.3


Fallback to 'exec' if port forward to 15014 unavailable

Resolves https://github.com/istio/istio/issues/27383 by falling back to the exec behavior if port 15014 is unavailable for istioctl version and friends.

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@esnible: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
09a708b06bb425502eda77ab805597950cf77548
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I was working on using ProxyGet from k8 1.19 as it is natively available and face the same issue. https://github.com/istio/istio/pull/25241#issuecomment-685494129
I can query istiod directly with
kubectl get --raw '/api/v1/namespaces/istio-system/pods/istiod-6fc8557fbc-g6fd5:15014/proxy/debug/config_dump?proxyID=details-v1-558b8b4b76-vcd4d.default'

Even istioctl version works with port 15014
kubectl get --raw '/api/v1/namespaces/istio-system/pods/istiod-6fc8557fbc-g6fd5:15014/proxy/version'

@esnible Thanks for this fix.

I think there are 3 methods - proxy, port-forward, and exec. Any reason not to use port-forward?

This code will be deprecated in favor of XDS-based techniques that work with External Istiod, and does not deserve polishing.
I wanted to do as little as possible, which I interpreted as taking the existing code and falling back to the previous technique.

I wanted to do as little as possible, which I interpreted as taking the existing code and falling back to the previous technique.

Sounds like a great reason to me :slightly_smiling_face:

In response to a cherrypick label: #27414 failed to apply on top of branch "release-1.7":
Applying: Fallback to 'exec' if port forward to 15014 unavailable
Using index info to reconstruct a base tree...
M	pkg/kube/client.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/kube/client.go
CONFLICT (content): Merge conflict in pkg/kube/client.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Fallback to 'exec' if port forward to 15014 unavailable
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #27421


cert-manager: Align to upstream

Attention: This is a default app!
Our version of cert-manager distinguishes from upstream cert-manager. We should get this back on track and align cert-manager to upstream.
This will help with features and updates in the future.

Decisions

Installation of cluster issuer required by giantswarm infrastructure will be installed as a post install hook
What happens with Configuration.md - probably needs to be newly created
there are significant differences in the values.yaml

make sure the default config is somehow kept the same
check existing user-values and maintain compatibility or provide an upgrade path (possibly automated)

### Tasks
- [x] Setup vendir in new branch
- [x] Diff vendir branch and current main
- [ ] Make a list of GS requirements for cert-manager as a default app
- [ ] For each item on the GS requirements list document how it's implemented

GS requirements

How Handle CRDs? - Currently we're using a pre install job to install CRDs outside of the helm lifecycle. Upstream handles this with installCRDs for which the template is built when packaging the app. So it's not available in upstream fork. Possibly change upstream fork sync to get upstream master form chart instead of git repo.

List of GS requirements

[ ] Cilium network policies PR
[ ] control-plane toleration PR
[ ] default irsa role for cert-manager-controller PR

Create a sub-chart for any changes that are giantswarm specific and will never be contributed upstream.
This is limited to discrete resources as existing templates can't be replaced by ones from a sub-chart.

We would like to remove business logic from the cert-manager chart to have it as close to upstream as possible.
For CAPI clusters we can use default-app-* to configure the provider specific values.
What can we do for vintage clusters, that use cert-manager and currently rely on business logic inside the cluster to e.g. ServiceAccounts with the correct AWS-roles annotation?
RCF @giantswarm/team-phoenix
For reference:

As we're currently aligning cert-manager with upstream, we're trying to get rid of business logic inside the app chart. I learned about the default-app-* repos which we can use to configure the required serviceAccount annotation (e.g. for configuring IRSA) for capi clusters so that is probably fine.
For vintage context: How do we handle backwards compatibility in these cases?
The version of cert-manager is fixed for a given release.
I can think of two scenarios where this could become an issue:
Customer needs to upgrade cert-manager because they require a feature or bug fix
this could be mitigated by just supplying the required config as user-config
We're releasing a new version of a vintage cluster which uses the newest version of cert-manager
Theoretically this could be mitigated by providing the required config params with the cluster-operater provided values. (Not sure if it's even possible to update a default app. How does cluster-operator reconcile that?)
if a different app by chance uses the same .Values.config.path this could cause issues

From slack thread

cert-manager-app v3.0.0 will be a CAPI first app. Business logic will be removed from the core chart.

Regarding CRDs:
Current release family v2.x.x contains a pre-install/pre-upgrade hook which uses a Job to install CRDs. This means

CRDs are installed without helm ownership annotations
Removing the cert-manager chart does not remove the CRDs
CRs are not removed because CRDs are not removed

The upstream chart includes CRDs as part of regular templates which means on uninstall all CRs are removed because CRDs are removed.
For now (as of https://github.com/giantswarm/cert-manager-app/pull/316/commits/acfffffad5d96c284a00b952bd21bcac00d1acca) upgrading from v2.x.x to v3.x.x is not possible because the new chart does not recognize the old CRDs and cannot apply/update them)
Deployment failed for `2.22.0-acfffffad5d96c284a00b952bd21bcac00d1acca`
    with `already-exists`: `resource already exists: (rendered manifests contain a
    resource that already exists. Unable to continue with update: CustomResourceDefinition
    "certificaterequests.cert-manager.io" in namespace "" exists and cannot be imported
    into the current release: invalid ownership metadata; annotation validation error:
    missing key "meta.helm.sh/release-name": must be set to "cert-manager"; annotation
    validation error: missing key "meta.helm.sh/release-namespace": must be set to
    "kube-system")

We have to decide:

Do we want the CR deletion behaviour of upstream

We have to solve:

How to adopt existing CRDs based on the strategy decided above. Removing CRDs during upgrade should not happen IMO

Next problem seem to be resource names and labels. Our chart uses name cert-manager-controller for the main Deployment while upstream simply uses cert-manager.
Upstream also defines different spec.selector labels. This is an immutable field in many resources. So either we try to bend labels to match previous ones, don't offer an upgrade path at all (requiring uninstall + reinstall) or try to hack something with a pre-upgrade hook job.

CRDs:
We decided to release another v2.x.x chart version with the required helm adoption labels. This allows installation of v3
Selector Labels:
We were able to bend upstream selector labels to match ours
Next steps:

Test and Merge https://github.com/giantswarm/cert-manager-app/pull/316 This will ensure v3.x.x chart can be installed.
Release a new v2 cert-manager-app version and request it in upcoming platform release

Released and requested changes in https://github.com/giantswarm/cert-manager-app/pull/331

closing this, v3.0.0 has been released 🎉


Azure Portal link for Intune Exchange Connector

The URL for Learn how to configure your account and server to connect to the Exchange connector in the Azure Portal (https://portal.azure.com/#blade/Microsoft_Intune_DeviceSettings/ExchangeConnectorMenu/connector/connectorType/) takes you to the instructions for the Clic Portal (https://docs.microsoft.com/en-us/intune-clic/deploy-use/intune-on-premises-exchange-connector).
This should be updated to the Azure Portal information (https://docs.microsoft.com/en-us/intune/exchange-connector-install)

⚠ Idea migrated from UserVoice
Created By: Vanita
Created On: 2017/10/09 01:38:25 +0000
Votes at Migration: 1
Supporters at Migration: 1

Closing as this is a product issue and we don't have a channel to contact the user to find out where the issue was.


LOOKUP bug when filename contains  NFC(Normalization Form C) characters

It looks like macOS client transform all NFC characters to NFD, this cause NFS3ERR_NOENT represented by NoEntException if filename contains NFC.
>>> import json, unicodedata

>>> print(json.dumps('ぶ'))
"\u3076"

>>> print(json.dumps(unicodedata.normalize('NFD', 'ぶ')))
"\u3075\u3099"

>>> unicodedata.normalize('NFD', 'ぶ')
'ぶ'

>>> 'ぶ' == 'ぶ'
False

ref:

https://docs.oracle.com/javase/tutorial/i18n/text/normalizerapi.html
https://en.wikipedia.org/wiki/Unicode_equivalence

work aound https://github.com/ruanima/unicode-normalizer


Cover how to achieve a 'TryGetOrCreate' if it is possible

We had the scenario where we sometimes wanted to abort a GetOrCreate, say if the underlying data isn't ready yet. We couldn't just return null because it would then end up in the cache and might be picked up by another consumer. We went for throwing a custom exception in the end and catching it when calling GetOrCreate, but it would be good to know if there is an intended way to achieve this such as setting a zero expiration time.
Would setting a zero expiration time guarantee that no other caller would pick up the value or would there be a race condition there?

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

ID: 13f5f8f9-18dd-9c12-9ed1-fcc6b44ba7fd
Version Independent ID: 640b4f36-5886-7b69-1c95-cfc8574a02fd
Content: Cache in-memory in ASP.NET Core
Content Source: aspnetcore/performance/caching/memory.md
Service: unspecified
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@mungojam what do you want to GetOrCreate ?  Is it something like TryUpdateModelAsync in Update the Create page

@Rick-Anderson I'm not sure that it is. That doesn't seem to be covering the abort of a cache GetOrCreate.
In my case, I need to be able to retrieve a value from the cache, but if it doesn't exist yet then it could be either because it just hasn't been requested yet (i.e. Create is fine), or because it isn't ready yet in which case I want to abort the GetOrCreate without risking other consumers picking up a null or dummy value.

So I think I want a TryGetOrCreate and in that sense maybe it is similar

You could open an issue in the https://github.com/aspnet/EntityFrameworkCore
It might be a good idea to create a proto-type version to show what you want to do.

Thanks, I've now raised https://github.com/aspnet/Caching/issues/390 with some example code

Thanks.


Updates for optimizing interaction with sign-in action.

Coverage remained the same at 50.745% when pulling 2ccb521e42277972921f112a963ac03232fcbb84 on wknet123:dev-optimize-sign-in into 9f0be6c53d09acf59be69465a2b0f4a64bc779a6 on vmware:dev.


fix(redis): remove unnecessary redis config deprecation warnings in hybrid mode

Summary
When running kong in hybrid mode with ACME plugin the configuration for the plugin is being pushed from CP to DP. When introducing shorthand field expansion to Admin API responses the deprecated fields (defined as shorthand fields) were also pushed from CP to DP which resulted in DP receiving config with both new fields and also old fields. It resulted with DP reporting in logs that ACME plugin is being configured with deprecated fields.
This PR disables the deprecation logs in DPs. The reasoning behind that is that those deprecation logs are not actionable on DP side and should be actually changed on CP if they were indeed configured improperly.
Checklist

[x] The Pull Request has tests
[x] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[x] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

KAG-4515

@fffonion - could you elaborate a bit why you removed the label backport release/3.6.x? Was that intentional? 🤔

@nowNick I deleted the backport labels from CE apart from 3.7.x to prepare for the ongoing backport process changes. I will @ you at slack.

Oh ok. I read the thread but I was confused why only the 3.6 backport flag was removed. Thanks for letting me know 👍


A search based Microsoft Teams Messaging Extension with authentication and access to Microsoft Graph

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?

What's in this Pull Request?
This is my already announced (and presented in PnP General Dev call 6-Aug ) sample on a search based messaging extension authenticating to Microsoft Graph.
An action based variant of this sample (just finished and blogged about) will follow soon. Promised.

Thank you - I was going to ask you for this as I've been following your articles and samples and they are really excellent and very much needed at this point. I'll review tomorrow ... thanks!

Thanks Bob, you and the community are welcome. Like to hear that sharing my practising effort is welcome and that I am not totally on the wrong track ;-)
Take your time to review and once done I can share the next (action based) variant.
Also thinking about a 3rd one: The SPFx way of it ...

Marcus - this is a great sample!
I have an opportunity to feature a couple samples on the Teams Community call on Thursday, October 20, 2020 from 17:00-18:00 CET, and would like to feature this one. Are you interested? Please LMK and we can iron out logistics ... THANKS!


Add the simulation for the Dobot Nova2

Support Dobot Nova 2 for the WRS system.

The forward kinematics error between the simulation robot and the real robot is around 0.2mm

sounds not bad
2023年2月14日(火) 21:02 Hao Chen @.***>:

Support Dobot Nova 2 for the WRS system.

The forward kinematics error between the simulation robot and the
real robot is around 0.2mm

You can view, comment on, or merge this pull request online at:
https://github.com/wanweiwei07/wrs/pull/70
Commit Summary

3005e5d
https://github.com/wanweiwei07/wrs/pull/70/commits/3005e5d49a184f3618b7ed62f38b216727e20b26
Add the simulation for the Dobot Nova2

File Changes
(9 files https://github.com/wanweiwei07/wrs/pull/70/files)

A robot_sim/manipulators/dobot_nova2/init.py
https://github.com/wanweiwei07/wrs/pull/70/files#diff-7c6fd60ca88259202bb5215f234a8de3cf3d4e78a965095b58b7751aa7570452
(1)
A robot_sim/manipulators/dobot_nova2/meshes/base.stl
https://github.com/wanweiwei07/wrs/pull/70/files#diff-910a45ef6ef51f5dcf50962e794c340e8fc4bad05dabd93b680457b45aa98c19
(0)
A robot_sim/manipulators/dobot_nova2/meshes/link1.stl
https://github.com/wanweiwei07/wrs/pull/70/files#diff-628cbf553fa2568fe986dc042fbf825e5f81d81782e9383f8d4144b61c150e85
(0)
A robot_sim/manipulators/dobot_nova2/meshes/link2.stl
https://github.com/wanweiwei07/wrs/pull/70/files#diff-c3407cc91de1fc4cc7f34a4fdca4507a7e1a7429a9d7503fb0bf5884cc3c2eaf
(0)
A robot_sim/manipulators/dobot_nova2/meshes/link3.stl
https://github.com/wanweiwei07/wrs/pull/70/files#diff-a8422c8ab760ad03cfdd2cfa06859a8fcc3aa4912a03bfa1da7a7787d51026d4
(0)
A robot_sim/manipulators/dobot_nova2/meshes/link4.stl
https://github.com/wanweiwei07/wrs/pull/70/files#diff-4df273254dd1214e75b16eacf82415ca5b3c5bf7af865d7e6b9e4a43d511fc76
(0)
A robot_sim/manipulators/dobot_nova2/meshes/link5.stl
https://github.com/wanweiwei07/wrs/pull/70/files#diff-02173a463b88317bc90874eafed8769e87394dc3b025e767cd2470c14d70259e
(0)
A robot_sim/manipulators/dobot_nova2/meshes/link6.stl
https://github.com/wanweiwei07/wrs/pull/70/files#diff-bff00d34992f6bd5795ca3dfa201cabb4de5f1b764b44be6b404627abb9de3da
(0)
A robot_sim/manipulators/dobot_nova2/nova2.py
https://github.com/wanweiwei07/wrs/pull/70/files#diff-dda04ac339080b6a6cfd3bac3a21eaa0afc15ff1095388aa6faaa44a5d4771b9
(163)

Patch Links:

https://github.com/wanweiwei07/wrs/pull/70.patch
https://github.com/wanweiwei07/wrs/pull/70.diff

—
Reply to this email directly, view it on GitHub
https://github.com/wanweiwei07/wrs/pull/70, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYYRXDJ32RKTYYZONV4KTTWXNX4NANCNFSM6AAAAAAU3PAQRE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Not working at edge.

Please review previous closed issues before filling out a new one! Duplicate issues will be closed without comment.
Describe the bug
I linked LH to an existing private repo I used to store my leetcode answer. It already had several .java files. After I solved two leetcode questions, I saw Problem solved as 0 and there were no changes on my repo.
To Reproduce
Go to leetcode, solved question(s), and check repo
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

it worked after 10mins I did another question


please help add missing cell-cell signaling terms

With the decision to eliminate the 'involved in' terms and convert them to GO-CAM models( go-annotation: Check annotations to signaling involved in x #4681 ) we are missing some cell-cell signal terms in the GO, please help add them:
For obsolete "epiblast cell-extraembryonic ectoderm cell signaling involved in anterior/posterior axis specification GO:0060802, please add:
epiblast cell-extraembryonic ectoderm cell signaling
Definition: Any process that mediates the transfer of information from an epiblast cell to an extraembryonic ectoderm cell.
Please add as a child term of cell-cell signaling GO:0007267
For obsolete "cerebellar Purkinje cell-granule cell precursor cell signaling involved in regulation of granule cell precursor cell proliferation GO:0021937, please add:
cerebellar Purkinje cell-granule cell precursor cell signaling
Definition: Any process that mediates the transfer of information from Purkinje cells to granule cell precursors.
Please add  as a child term of cell-cell signaling GO:0007267
Thanks,
Li

https://github.com/geneontology/go-annotation/issues/4681
https://github.com/geneontology/go-ontology/issues/25766

feel free to revise the term label and definition, thanks!

May have to wait for @pgaudet to comment.

@LiNiMGI
We are discussing this on the ontology call:

epiblast cell-extraembryonic ectoderm cell signaling involved in anterior/posterior axis specification GO:0060802

Do you know if this type of signaling only occurs in anterior/posterior axis specification  ? (in this case we improve the label and definition of the existing term, and not obsolete.

@pgaudet Sorry I am not an expert on that.
However, David found a paper that might be helpful: PMID:16793258.
Thanks


Brew update fails when ssh is configured to use environment variables

brew config output
brew config
HOMEBREW_VERSION: 3.4.9-29-gea72240
ORIGIN: https://github.com/Homebrew/brew
HEAD: ea722400cd52bc514475ffccf292ea3ca6463393
Last commit: 2 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 0ceeffe34f55e1d4a14902d0db6f9a998abf0d97
Core tap last commit: 2 hours ago
Core tap branch: master
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_CORE_GIT_REMOTE: https://github.com/Homebrew/homebrew-core
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.Th9buwtQgD/org.xquartz:0
HOMEBREW_EDITOR: vim
HOMEBREW_GITHUB_API_TOKEN: set
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.8 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: octa-core 64-bit arm_firestorm_icestorm
Clang: 13.1.6 build 1316
Git: 2.36.0 => /opt/homebrew/bin/git
Curl: 7.79.1 => /usr/bin/curl
macOS: 12.3.1-arm64
CLT: <IP_ADDRESS>.1.1648687083
Xcode: N/A
Rosetta 2: false

brew doctor output
$ # [None of these warnings are related to my issue]
$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed kegs have no formulae!
This means they were either deleted or installed with `brew diy`.
You should find replacements for the following formulae:
  szip

Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
  docker-machine
  gdub
  ilmbase

Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and which additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew-provided
script of the same name. We found the following "config" scripts:
  /Users/mwerle/.indeed-dev-tools/bin/create-mesh-local-bootstrap-config

Warning: Putting non-prefixed coreutils in your path can cause GMP builds to fail.

Warning: Putting non-prefixed findutils in your path can cause python builds to fail.

Warning: A '.pydistutils.cfg' file was found in $HOME, which may cause Python
builds to fail. See:
  https://bugs.python.org/issue6138
  https://bugs.python.org/issue4655

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  docker
  gng
  gping
  wireshark
  resty

Verification

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
I need to forward sockets for GPG signatures to a remote host, so in my SSH configuration, I have something like this:
Host *.subdomain.example.com
  RemoteForward /run/user/1001/gnupg/S.gpg-agent ${GPG_AGENT_EXTRA}

I also have:
Host tap-repo-server.other-subdomain.example.com
  AddKeysToAgent yes
  IdentityFile ~/.ssh/id_rsa

  # Keep ssh connections alive for 30*30 seconds (15 minutes) to
  # allow for long running pre-push hooks
  ServerAliveInterval 30
  ServerAliveCountMax 25

I also have a tap at: /opt/homebrew/Library/Taps/my-tap-group/my-tap
With the git config:
[remote "origin"]
	url =<EMAIL_ADDRESS>my-tap-group/my-tap.git
	fetch = +refs/heads/*:refs/remotes/origin/*

What happened (include all command output)?
$ brew update
vdollar_percent_expand: env var ${GPG_AGENT_EXTRA} has no value
/Users/mwerle/.ssh/config line 19: Bad forwarding specification.
/Users/mwerle/.ssh/config: terminating, 1 bad configuration options
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Fetching /opt/homebrew/Library/Taps/my-tap-group/my-tap failed!

What did you expect to happen?
The update should succeed because the environment variable configuration is not required in the ssh host configuration relevant to the brew update command.
Step-by-step reproduction instructions (by running brew commands)
1. Tap a repository using an SSH URL.
2. Add configuration to any host (can be a fake one) in `~/.ssh/config` including an environment variable.
3. Run `brew update`.

The update should succeed because the required environment variable is present in the environment when I execute brew update.

Homebrew intentionally filters out all environment variables. We do not support tapped repositories that require environment variables to be passed to work.

The repository I'm trying to pull from does not require environment variables at all. The environment variables are for another host. There is no way to pull from any repository using SSH if any SSH configured requires an environment variable.

I updated the original report to better reflect this. It's arguably a limitation of SSH, but it means that I cannot effectively use any SSH taps and still use any environment variables, even if they have nothing to do with the taps.

Ok, makes more sense. I'm afraid the workaround here would be to allowlist each individual environment variable so the request here, from our end, is whether or not to allow GPG_AGENT_EXTRA here.

If there's nothing generic we can do (which I fear there isn't), you could perhaps have a dedicated SSH config file that repo (which you can Include /some/ssh/config from the main one if you need it) and have core.sshCommand "ssh -F /some/ssh/config" in your git config for the needed taps. If you don't need/want a separate file, you can also alternatively pass any needed options as command args to ssh in the git config and set -F to /dev/null.

It's a git config option, but after writing that I've actually realised we have HOMEBREW_SSH_CONFIG_PATH already - I've overcomplicated things. See https://docs.brew.sh/Manpage.

Thanks -- that sounds exactly what I need; sorry I missed it! I'll report back later today after testing.

Using HOMEBREW_SSH_CONFIG_PATH to avoid the configuration with the variables works great. Thanks!


Inconsistent starting position of chain method continuation

When a method owner is constant or literal, the rule expects the first call to start on the next line.
""
    .plus(1)
    .plus(2)
    .plus(3)
    .plus(4)

Using the same convention, the rule reports an error when the receiver is conditional if or when.
when {
    true -> ""
    else -> ""
} // VIOLATION
    .plus(1)
    .plus(2)
    .plus(3)
    .plus(4)

if (true) {
    ""
} else {
    ""
} // VIOLATION
    .plus(1)
    .plus(2)
    .plus(3)
    .plus(4)

Expected Behavior
The first method call should always start on the next line. Alternatively, the rule could allow the first call in the same line. Kotlin coding conventions state that it's OK to omit the initial line break "if it makes more sense that way".
""
    .plus(1)
    .plus(2)
    .plus(3)
    .plus(4)

when {
    true -> ""
    else -> ""
}
    .plus(1)
    .plus(2)
    .plus(3)
    .plus(4)

// or

"".plus(1)
    .plus(2)
    .plus(3)
    .plus(4)

when {
    true -> ""
    else -> ""
}.plus(1)
    .plus(2)
    .plus(3)
    .plus(4)

Current Behavior
""
    .plus(1)
    .plus(2)
    .plus(3)
    .plus(4)

when {
    true -> ""
    else -> ""
}.plus(1)
    .plus(2)
    .plus(3)
    .plus(4)

Additional information

Current version of ktlint: 1.3.1

In example below, the .plus(1) seems to be disconnected from the root of the method continuation:
when {
    true -> ""
    else -> ""
}
    .plus(1)
    .plus(1)

while in code below the chain operators are not aligned:
when {
    true -> ""
    else -> ""
}.plus(1)
    .plus(1)

Kotlin coding conventions state that it's OK to omit the initial line break "if it makes more sense that way".

Statements like above, can result in discussions on a case by case base how the statement would be written. Both styles could be in use within the same code base, file, class or method. Ktlint tries to avoid inconsistencies, and has (fairly arbitrarly) choosen the second style to be applied always.
Let me be clear, I dislike both ways of writing code like above equally. Personally, I would tend to refactor my code by extracting the when-clause to solve the formatting issue. It is not pretty when ktlint (or whatever formatter) more or less forces you to refactor code, but on the other hand to might see it as a removing a code smell that makes the code easier to read.


tests/kernel/timer/timer_api/ failed on up_squared platform

Describe
set up acrn on up_squared board and run zephyr tests.
To Reproduce
Steps to reproduce the behavior:

sanitycheck -p acrn --device-testing --device-serial /dev/ttyUSB1
-T tests/kernel/timer/timer_api/  -west-flash="acrn_up2.sh"
See error

Screenshots or console output
*** Booting Zephyr OS build zephyr-v2.2.0-622-ge27cf1576338  ***
Running test suite timer_api
starting test - test_time_conversions
PASS - test_time_conversions
starting test - test_timer_duration_period
ASSERTION FAIL [z_spin_lock_valid(l)] @ WEST_TOPDIR/zephyr/include/spinlock.h:74
Recursive spinlock 0x00000000001088e0
E: RAX: 0x0000000000000004 RBX: 0x0000000000000046 RCX: 0x00000000000003f8 RDX: 0x00000000000003f8
E: RSI: 0x000000000000004a RDI: 0x000000000010680e RBP: 0x000000000000000a RSP: 0x0000000000109c88
E:  R8: 0x0000000000000006  R9: 0x0000000000000000 R10: 0x0000000000000000 R11: 0x0000000000000000
E: R12: 0x0000000000000206 R13: 0x0000000000000000 R14: 0x0000000000000000 R15: 0x0000000000000000
E: RSP: 0x0000000000109c88 RFLAGS: 0x0000000000000006 CS: 0x0018 CR3: 0x000000000000b000
E: RIP: 0x00000000001018af
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
E: Current thread: 0x0000000000107e60 (unknown)
E: Halting system
Environment (please complete the following information):

OS: fedora28
Toolchain : zephyr-sdk-0.11.1
Commit ID: e27cf157633

Still a valid issue


Tab handling

2 minor suggestions:

When I open atom, there's usually a Console tab open from a previous coding session. Starting proto-repl however does not reuse the Console tab, but opens a Proto-REPL tab next to it. I believe this is a recent change, either in proto-repl or atom.

When the REPL tab is active, and I select a file to open, it'd be nice if the new tab didn't pop up next to the REPL tab. This is probably the default atom behaviour, but maybe there's a way to override it?

The first issue is better described at #254 (note: I'm using boot, so it's not related to lein).


Run command inside container before compilation

Proposal
Add a pre-build hook, which allows it to run a script inside the container before the build.
Use-case
My use-case is that I submitted a fix to the ESP IDF, but that I need to wait for the fix to be merged. Until then I am basically blocked from using this CI action.
My patchfile looks as shown below and could be applied at the root of the esp-idf via patch -s -p0 < idfgh-6944.patch. I can however not figure out how to apply a patch to the esp-idf inside the container before running the compilation.
--- components/esp_http_client/esp_http_client.c	2022-03-17 08:40:29.726433947 +0000
+++ components/esp_http_client/esp_http_client.c.patch	2022-03-17 08:40:19.238269499 +0000
@@ -512,6 +512,10 @@
     client->process_again = 0;
     client->response->data_process = 0;
     client->first_line_prepared = false;
+    if (client->location != NULL) {
+            free(client->location);
+            client->location = NULL;
+    }
     http_parser_init(client->parser, HTTP_RESPONSE);
     if (client->connection_info.username) {
         char *auth_response = NULL;

Hey @kumekay, thanks for implementing this. This does resolve my issue. I will close this.


Add option to override esbuild config

I ran into No loader is configured for ".node" files<EMAIL_ADDRESS>There is an esbuild workaround (https://github.com/evanw/esbuild/issues/1051#issuecomment-806325487), but I think a Lamba Layer will be better approach in this case. To achieve this I needed to be able to override the esbuild options.
While I was at it I added in override for format and target. I can't imagine any others that can be required.
Sorry the TS isn't as good as it could be.
Thanks for supporting such a useful package.

Nice. Thank you.


nginx support?

Any guidance on using nginx for the web server instead of apache?

.. currently working on pointing nginx at the php, etc. ... database created just fine with setup.py ...

Here is how I configured the nginx server to serve up facade ....
Setting Up Server Blocks (Pretty much necessary if you are running more than one website on the server.)
When using the Nginx web server, you can use server blocks (similar to virtual hosts in Apache) to encapsulate configuration details and host more than one domain from a single server. We will set up a domain called facade, but you should replace this with your own domain name.
Create the directory for facade, using the -p flag to create any necessary parent directories:

sudo mkdir -p /var/www/facade/html

Assign ownership of the directory:

sudo chown -R $USER:$USER /var/www/facade/html

The permissions of your web roots should be correct if you haven't modified your umask value, but you can make sure by typing:

sudo chmod -R 755 /var/www/facade

Create a sample index.html page using nano or your favorite editor:

nano /var/www/facade/html/index.html

Inside, add the following sample HTML:
/var/www/facade/html/index.html

        <title>Welcome to facade!</title>

Success!  The facade server block is working!

```

Save and close the file when you are finished.

Make a new server block at /etc/nginx/sites-available/facade:

> sudo nano /etc/nginx/sites-available/facade

Paste in the following configuration block, updated for our new directory and domain name:

/etc/nginx/sites-available/facade

```bash
server {
        listen 80;
        listen [::]:80;

        root /var/www/facade/html;
        index index.html index.htm index.nginx-debian.html;

        server_name facade www.facade;

        location / {
                try_files $uri $uri/ =404;
        }
}```

Save and close the file when you are finished.

Enable the file by creating a link from it to the sites-enabled directory:

> sudo ln -s /etc/nginx/sites-available/facade

/etc/nginx/sites-enabled/

Two server blocks are now enabled and configured to respond to requests based on their listen and server_name directives:

facade: Will respond to requests for facade and www.facade.
default: Will respond to any requests on port 80 that do not match the other two blocks.
To avoid a possible hash bucket memory problem that can arise from adding additional server names, it is necessary to adjust a single value in the /etc/nginx/nginx.conf file. Open the file:

> sudo nano /etc/nginx/nginx.conf

Find the server_names_hash_bucket_size directive and remove the # symbol to uncomment the line:

/etc/nginx/nginx.conf

```bash
http {
    ...
    server_names_hash_bucket_size 64;
    ...
}

Test for syntax errors:

sudo nginx -t

Restart Nginx to enable your changes:

sudo systemctl restart nginx

Nginx should now be serving your domain name. You can test this by navigating to http://facade, where you should see something like this:
Nginx first server block


fails on empty docstrings

pydocstringformatter v0.7.1 raises an exception on a file that looks like this
class Problematic:
    """ """
    pass

The problem is summary.splitlines()[-1] which fails when summary is empty.
% pydocstringformatter ./problematic.py
Traceback (most recent call last):
  File "/home/stuff/.pyenv/versions/stuff/bin/pydocstringformatter", line 8, in <module>
    sys.exit(run_docstring_formatter())
  File "/home/stuff/.pyenv/versions/3.9.11/envs/stuff/lib/python3.9/site-packages/pydocstringformatter/__init__.py", line 18, in run_docstring_formatter
    _Run(argv or sys.argv[1:])
  File "/home/stuff/.pyenv/versions/3.9.11/envs/stuff/lib/python3.9/site-packages/pydocstringformatter/run.py", line 32, in __init__
    self.check_files(self.config.files)
  File "/home/stuff/.pyenv/versions/3.9.11/envs/stuff/lib/python3.9/site-packages/pydocstringformatter/run.py", line 39, in check_files
    is_changed = self.format_files(filepaths)
  File "/home/stuff/.pyenv/versions/3.9.11/envs/stuff/lib/python3.9/site-packages/pydocstringformatter/run.py", line 121, in format_files
    is_changed = self.format_file(file) or is_changed
  File "/home/stuff/.pyenv/versions/3.9.11/envs/stuff/lib/python3.9/site-packages/pydocstringformatter/run.py", line 78, in format_file
    new_tokeninfo = formatter.treat_token(new_tokeninfo)
  File "/home/stuff/.pyenv/versions/3.9.11/envs/stuff/lib/python3.9/site-packages/pydocstringformatter/_formatting/base.py", line 100, in treat_token
    self.treat_string(
  File "/home/stuff/.pyenv/versions/3.9.11/envs/stuff/lib/python3.9/site-packages/pydocstringformatter/_formatting/base.py", line 178, in treat_string
    new_summary = self.treat_summary(
  File "/home/stuff/.pyenv/versions/3.9.11/envs/stuff/lib/python3.9/site-packages/pydocstringformatter/_formatting/formatters_pep257.py", line 41, in treat_summary
    if _utils.is_rst_title(summary):
  File "/home/stuff/.pyenv/versions/3.9.11/envs/stuff/lib/python3.9/site-packages/pydocstringformatter/_formatting/_utils.py", line 8, in is_rst_title
    last_line = summary.splitlines()[-1].lstrip()
IndexError: list index out of range

I'll release a fix for this somewhere today! Thanks for the report!

Thanks for the swift fix!

No worries, thanks for the report! 😄


Please add my duck. Quack quack :)

Description
Here my contribution to "The Duck Gallery".

You must respect the following conditions

Your contribution must respect the code of conduct
It's your first PR to this repository
You have added your image of the duck downloaded from https://pimpmyduck.zenika.com
You have not changed the image of the duck
The image filename must be your GitHub username (ex: your-username.png)
You are using your own GitHub user and it's the same as the PR author
Into the contributors.js file, the message must be short and respect the code of conduct

If the PR doesn't respect those conditions, it will be closed

Hello @piyush6805 , thanks for your contribution. Your duck have to be in the duck directory. Thanks to move it


Member Role add and Remove on Owner

Hey,
why can the bot not interact with the server owner? For example, giving and revoking roles does not work on the server owner. Is there a cause for this decision.
Best Regards

I'm pretty sure you're just running into the limitations of Discord's API and how permissions work.

I'm pretty sure you're just running into the limitations of Discord's API and how permissions work.

That was my first thought but i looked at the PermissionUtil in the checkHirarchy Method and there is a if block which is executed if the author is the owner. And that block returns false to the class.

That was my first thought but i looked at the PermissionUtil in the checkHirarchy Method and there is a if block which is executed if the author is the owner. And that block returns false to the class.

iirc this is because the owner is technically the highest role possible, and so iirc bots can't interact with them like that.

iirc this is because the owner is technically the highest role possible, and so iirc bots can't interact with them like that.

Hey sorry for my late answer, i understand your point. I think the discord roles are more important than the owner role. Look at these:
How permissions apply may at first seem intuitive, but there are some hidden restrictions that prevent bots from performing certain inappropriate actions based on a bot's highest role compared to its target's highest role. A bot's or user's highest role is its role that has the greatest position value in the guild, with the default @everyone role starting at 0. Permissions follow a hierarchy with the following rules:
A bot can grant roles to other users that are of a lower position than its own highest role.
A bot can edit roles of a lower position than its highest role, but it can only grant permissions it has to those roles.
A bot can only sort roles lower than its highest role.
A bot can only kick, ban, and edit nicknames for users whose highest role is lower than the bot's highest role.
Otherwise, permissions do not obey the role hierarchy. For example, a user has two roles: A and B. A denies the VIEW_CHANNEL permission on a #coolstuff channel. B allows the VIEW_CHANNEL permission on the same #coolstuff channel. The user would ultimately be able to view the #coolstuff channel, regardless of the role positions.

There is nothing mentioned like that, only that the order of the roles on the right side of discord make the permissions. So if i order the bot role above the highest role, so that the bot is the highest role, all stuff should be possible.

If you attempt to do this via the raw REST methods, you will get a 50013 Missing Permissions REST error back from Discord. This is not a bug in catnip.


README example code is incorrect

Running the following code using params 0.2.0, largely copied from the example in the README
extern crate iron;
extern crate params;

use iron::prelude::*;
use params::Params;

fn echo_file(req: &mut Request) -> IronResult<Response> {
    use params::{Map, Params};

    let map: Map = try!(req.get_ref::<Params>());

    match map.find(&["user", "name"]) {
        // Assume, for example, the request URL here is:
        // http://localhost:3000/handler?user[name]=Marie
        Some(&Value::String(ref name)) => assert_eq!(name, "Marie"),
        _ => panic!("Unexpected parameter type!"),
    }
}

fn main() {
    let chain = Chain::new(echo_file);
    Iron::new(chain).http("<IP_ADDRESS>:9001").unwrap();
}

yields the following output when run with cargo run
src/main.rs:15:15: 15:28 error: unresolved enum variant, struct or const `String` [E0419]
src/main.rs:15         Some(&Value::String(ref name)) => assert_eq!(name, "Marie"),
                             ^~~~~~~~~~~~~
src/main.rs:15:15: 15:28 help: run `rustc --explain E0419` to see a detailed explanation
<std macros>:3:43: 3:46 error: mismatched types:
 expected `params::Map`,
    found `&params::Map`
(expected struct `params::Map`,
    found &-ptr) [E0308]
<std macros>:3 $ crate:: result:: Result:: Ok ( val ) => val , $ crate:: result:: Result::
                                                         ^~~
src/main.rs:10:20: 10:49 note: in this expansion of try! (defined in <std macros>)
<std macros>:3:43: 3:46 help: run `rustc --explain E0308` to see a detailed explanation
<std macros>:6:1: 6:32 error: the trait `core::convert::From<params::ParamsError>` is not implemented for the type `iron::error::IronError` [E0277]
<std macros>:6 $ crate:: convert:: From:: from ( err ) ) } } )
               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/main.rs:10:20: 10:49 note: in this expansion of try! (defined in <std macros>)
<std macros>:6:1: 6:32 help: run `rustc --explain E0277` to see a detailed explanation
<std macros>:6:1: 6:32 note: required by `core::convert::From::from`
<std macros>:5:8: 5:18 error: the type of this value must be known in this context
<std macros>:5 if ! ( * left_val == * right_val ) {
                      ^~~~~~~~~~
src/main.rs:15:43: 15:68 note: in this expansion of assert_eq! (defined in <std macros>)
<std macros>:5:22: 5:33 error: the type of this value must be known in this context
<std macros>:5 if ! ( * left_val == * right_val ) {
                                    ^~~~~~~~~~~
src/main.rs:15:43: 15:68 note: in this expansion of assert_eq! (defined in <std macros>)
<std macros>:5:1: 9:27 error: if may be missing an else clause:
 expected `()`,
    found `core::result::Result<iron::response::Response, iron::error::IronError>`
(expected (),
    found enum `core::result::Result`) [E0308]
<std macros>:5 if ! ( * left_val == * right_val ) {
<std macros>:6 panic ! (
<std macros>:7 "assertion failed: `(left == right)` \
<std macros>:8                            (left: `{:?}`, right: `{:?}`)"
<std macros>:9 , left_val , right_val ) } } } } )
src/main.rs:15:43: 15:68 note: in this expansion of assert_eq! (defined in <std macros>)
<std macros>:5:1: 9:27 help: run `rustc --explain E0308` to see a detailed explanation
error: aborting due to 5 previous errors
Could not compile `src`.

To learn more, run the command again with --verbose.

I just fixed this with #16. The previous example had some implicit error handling that I just went ahead and replaced with an unwrap() call. Please try the new example and let me know if you have any further problems! :smile:


Bundle agent with the main package

Currently, we hardcode the path to the agent here. It would be nice if we can dynamically get the path to the JAR. To do so, we could bundle this while running the assembly plugin.

Once this ticket is dealt with, we can start releasing JARs on maven central.

@MartinWit need your help to integrate the release script you wrote so I can also make regular releases of this project. :D

I can have a look tomorrow


loss functions during pretraining

Hi @Arthur151 ,
May I ask what loss functions you have used during your pretraining stage?
Thanks,

Yes, during pretraining, I used

detection loss to train center map
https://github.com/Arthur151/ROMP/blob/12a624f00be92d1f7195f24106d151d2f26961f4/romp/lib/loss_funcs/calc_loss.py#L39
keypoints 2D loss like this
https://github.com/Arthur151/ROMP/blob/12a624f00be92d1f7195f24106d151d2f26961f4/romp/lib/loss_funcs/calc_loss.py#L90
but to learn 2D pose estimation with a separate head.


Upgrading to Angular 4.2 getting Error error TS2420: Class 'CompleterBaseData' incorrectly implements interface 'CompleterData'.   Types of property 'lift' are incompatible.

After Upgrading to Angular 4.2 version ng2-completer component throws the error (attached image below)
.
It was working fine in angular 2(earlier version).  Please let me know how to resolve this issue.

Its because of typescript issue. I changed the version to typescript-2.3.4. Its worked..

I have the same issue, and my tsc-v shows 2.3.4


adding social media icons in page

I find that social media icons were not visible in web page , I want to add up it with functionality. I hope u will give me chance to contribute to this .

Hey, welcome to GSSoC ’23, this is an amazing idea. But half the things have already been done. There’s a Landing Page that’s half completed and there’s the App that’s been half completed too! I’m currently setting things up and also adding the videos for those who are completely new. Will be creating labels and assigning it. Can we please wait for a day max until I make the ReadMe and push the base code and base branches (one for the web and another for the app)? 🙏🏻
Thanks, it won’t be long. A new video will be coming up. Don’t close the issue, we’ll see how we can make it fit. 💪🏻

Also which web page are you talking about?


Issue 9

Resolve #9.

Coverage increased (+0.09%) to 95.833% when pulling f6427340e32a8da5e50c57ea1e68f126153761b5 on issue-9 into 7a4c222eff662004445c99c09111a2be68ef42c7 on master.

Coverage increased (+0.09%) to 95.833% when pulling f6427340e32a8da5e50c57ea1e68f126153761b5 on issue-9 into 7a4c222eff662004445c99c09111a2be68ef42c7 on master.


Place.Types: no associated enum value

Hi there,
I got this error when running the DidAutocomplete():
System.NotSupportedException: 'supermarket has no associated enum value in PlaceType on this platform.'
I cannot access the "place.Types" variable, guess the supermarket value is not included in the enums, right?
Thanks,
Florian

@kantan-florian The only enum that has something related to supermarket is PlaceType.GroceryOrSupermarket. IDK if this a bug in our side or Google side, can you provide a test case? Thanks in advance!

We have not received the requested information. If you are still experiencing this issue, please, open a new issue related to this. Thanks!


Page#to_absolut raises URI::InvalidURIError: path conflicts with opaque

Thanks for an awesome gem! 🌟
When crawling a site, this exception was raised:
URI::InvalidURIError: path conflicts with opaque
from $HOME/.rubies/ruby-2.4.0/lib/ruby/2.4.0/uri/generic.rb:761:in `check_path'
from $HOME/.rubies/ruby-2.4.0/lib/ruby/2.4.0/uri/generic.rb:817:in `path='
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/page/html.rb:283:in `to_absolute'
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/page/html.rb:239:in `block in each_url'
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/page/html.rb:182:in `block in each_link'
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/page/html.rb:189:in `block in each_link'
from $HOME/.gem/ruby/2.4.0/gems/nokogiri-<IP_ADDRESS>/lib/nokogiri/xml/node_set.rb:187:in `block in each'
from $HOME/.gem/ruby/2.4.0/gems/nokogiri-<IP_ADDRESS>/lib/nokogiri/xml/node_set.rb:186:in `upto'
from $HOME/.gem/ruby/2.4.0/gems/nokogiri-<IP_ADDRESS>/lib/nokogiri/xml/node_set.rb:186:in `each'
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/page/html.rb:188:in `each_link'
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/page/html.rb:238:in `each_url'
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/agent.rb:679:in `block in visit_page'
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/agent.rb:605:in `block in get_page'
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/agent.rb:788:in `prepare_request'
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/agent.rb:599:in `get_page'
from $HOME/.gem/ruby/2.4.0/gems/spidr-0.6.0/lib/spidr/agent.rb:665:in `visit_page'

The line in spidr that raises this error is lib/spidr/page/html.rb:283:
new_url.path = URI.expand_path(path)

URI#path= calls URI#check_path which raises the error, see ruby docs for URI:Generic#check_path.
I'm not really sure what the best way to go about this would be, perhaps catching URI::InvalidURIError and returning nil is sensible, since nil already can be returned from Page#to_absolute?

Just curious if you know the page and link that causes this exception?

@postmodern I'm sorry I don't have the exact URL :/ the only thing I know is that it happened on this domain https://www.bls.gov. Real sorry that I can't be more specific.

I encountered this as well and was eventually able to track down the cause.
Page#to_absolute only calls URI::expand_path if the path is not nil. mailto links normally have a nil path. However, there appears to be a bug in the Ruby URI module that returns an empty string rather than nil if a mailto link has headers but no to component:
2.4.1 :011 > URI("mailto:a@b.com?a").path
 => nil
2.4.1 :012 > URI("mailto:a@b.com").path
 => nil
2.4.1 :013 > URI("mailto:?").path
 => ""
2.4.1 :014 > URI("mailto:?a").path
 => ""

This causes #to_absolute to attempt to set the URI's path to URI.expand_path("") (an empty string), which raises an exception because it's an opaque URI.
I'm seeing this bug in the wild with mailto URLs generated by the WordPress Custom Facebook Feed plugin; however, I can consistently replicate it with any mailto URL of that form.
I'm going to report this bug to the Ruby development team unless I find that it's been reported already.

Seeing this behaviour on http://ifdelayed.com/.

Merged!

Finally released in 0.6.1.


fix(notifier): adds notificationsBalance, fix addr

Adds missing notificationsBalance field in the subscription model
Also fixes notifier contract addresses for ganache

All good, just need to add this field in migration file

All good, just need to add this field in migration file

It's here
https://github.com/rsksmart/rif-marketplace-cache/pull/633/files#diff-ccf35de765e23ca21519b8651936f8242792c7e7f9d85107997adfeeb8796994R180-R184

It should be all done, just need to wait for the notifier service to adapt its currency field from token name to token address before merging. This should be already under way, right @vjgene / @artem-brazhnikov?

DO NOT MERGE, please. It should be all done, just need to wait for the notifier service to adapt its currency field from token name to token address before merging. This should be already under way, right @vjgene / @artem-brazhnikov?

yes, it's not merged in develop of the rif-notifier @jurajpiar


Try to concatenate two files when there is a single cut

Example:
import bvsfunc.AudioProcessor as ap
path = r'F:\VPS\ENCO EN COURS\Magia Record\BD\[BDMV][200304][Magia Record][Vol.1]\BD_VIDEO\BDMV\STREAM\00001.m2ts'
ap.VideoSource(infile=path, trimlist="[[None, -48]]", noflac=True, silent=False)

The issue is fixed when using a single dict "[None, -48]", though.

error example:
output_file: F:\VPS\ENCO EN COURS\Magia Record\BD\[BDMV][200304][Magia Record][Vol.1]\BD_VIDEO\BDMV\STREAM\00001_2_temp1.wav already exists and will be overwritten on build
Traceback (most recent call last):
  File "magia_bd01v4.vpy", line 38, in <module>
    ap.VideoSource(infile=path, trimlist="[[None, -24]]", noflac=True, silent=False)
  File "C:\Users\Varde\AppData\Roaming\Python\Python38\site-packages\bvsfunc\AudioProcessor.py", line 203, in VideoSource
    trimfiles, temp_outfiles = trim_tracks_as_wav(extracted_tracks, trimlist, framerate, framenum, silent)
  File "C:\Users\Varde\AppData\Roaming\Python\Python38\site-packages\bvsfunc\AudioProcessor.py", line 87, in trim_tracks_as_wav
    cbn.build(temp_outfiles, outfile, 'concatenate')
  File "C:\Users\Varde\AppData\Roaming\Python\Python38\site-packages\sox\combine.py", line 70, in build
    file_info.validate_input_file_list(input_filepath_list)
  File "C:\Users\Varde\AppData\Roaming\Python\Python38\site-packages\sox\file_info.py", line 238, in validate_input_file_list
    raise ValueError("input_filepath_list must have at least 2 files.")
ValueError: input_filepath_list must have at least 2 files.

Fixed in https://github.com/begna112/bvsfunc/commit/ffadbf97c168b24bdb5d15d1450319558c53bd94


GPU Delegate dynamic tensor input shape (Feature Request)

Click to expand!
Issue Type
Feature Request
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
tf 2.12.0
Custom Code
Yes
OS Platform and Distribution
Android
Mobile device
Android
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Hello, I'm writing you to ask, are there plans to implement dynamic input shape in gpu delegate in near future ?
Right now dynamic input shape working fine on cpu, but on gpu delegate I'm getting the issue
java.lang.IllegalArgumentException: Internal error: Error applying delegate:
This is very important feature, if this feature already exist and it is possible somehow to rung with dynamic shape will be good to have some information in documentation.
Standalone code to reproduce the issue
@Throws(IOException::class)
    private fun initInterpreter(context: Context): Interpreter {

        val tfliteOptions = Interpreter
            .Options()

        if (delegate != null) {
            tfliteOptions.addDelegate(delegate)
            tfliteOptions.numThreads = 1
        } else {
            tfliteOptions.numThreads = 4
        }

        val interpreter = Interpreter(loadModelFile(context), tfliteOptions)

        interpreter.resizeInput(0, intArrayOf(1, modelHeight, modelWidth, 3), true)
        interpreter.allocateTensors()

        return interpreter
    }

Relevant log output
java.lang.IllegalArgumentException: Internal error: Error applying delegate:
org.tensorflow.lite.NativeInterpreterWrapper.createInterpreter(Native Method)
org.tensorflow.lite.NativeInterpreterWrapper.init(NativeInterpreterWrapper.java:110)
org.tensorflow.lite.NativeInterpreterWrapper.<init>(NativeInterpreterWrapper.java:73)
org.tensorflow.lite.NativeInterpreterWrapperExperimental.<init>(NativeInterpreterWrapperExperimental.java:36)
org.tensorflow.lite.Interpreter.<init>(Interpreter.java:214)

Hi @OleksandrGrument, in order to keep TFLite light, we have to compromise on some design choices such as dynamic input shapes. Currently we do not plan to implement this feature in the near future. Apologies we can't help you here soon.


Add project relationship attribute to Dataset(Read) and Workflow(Read)

closes #1063
Checklist before merging

[ ] I added an appropriate entry to CHANGELOG.md

I close this pull request and replace it with https://github.com/fractal-analytics-platform/fractal-server/pull/1082


Make expression proxies notify their deps when their bits resolve - #2214

This is unfamiliar territory for me, so is this a proper fix?

Pretty sure this is correct :+1:


Flutter CI with Github Actions not working

Hello,
I am setinng up flutter CI with github actions.
My app compiles localy without any problem but in Github Actions build is failing.
It fails with this meesage:
[  +98 ms] > Task :app:generateReleaseBuildConfig
[        ] > Task :apple_sign_in:generateReleaseBuildConfig
[        ] > Task :connectivity:generateReleaseBuildConfig
[  +99 ms] > Task :apple_sign_in:javaPreCompileRelease
[        ] warning: [options] source value 7 is obsolete and will be removed in a future release
[        ] warning: [options] target value 7 is obsolete and will be removed in a future release
[+1700 ms] > Task :apple_sign_in:compileReleaseJavaWithJavac
[        ] > Task :apple_sign_in:bundleLibCompileRelease
[        ] > Task :connectivity:javaPreCompileRelease
[        ] warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
[        ] 3 warnings
[        ] warning: [options] source value 7 is obsolete and will be removed in a future release
[        ] warning: [options] target value 7 is obsolete and will be removed in a future release
[        ] warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
[ +399 ms] > Task :connectivity:compileReleaseJavaWithJavac FAILED
[        ] error: warnings found and -Werror specified
[        ] FAILURE: Build failed with an exception.
[        ] * What went wrong:
[        ] Execution failed for task ':connectivity:compileReleaseJavaWithJavac'.
[        ] > Compilation failed; see the compiler error output for details.
[        ] * Try:
[        ] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[        ] * Get more help at https://help.gradle.org
[        ] BUILD FAILED in 3m 11s
[  +98 ms] Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
[        ] Use '--warning-mode all' to show the individual deprecation warnings.
[        ] See https://docs.gradle.org/5.6.2/userguide/command_line_interface.html#sec:command_line_warnings
[        ] 205 actionable tasks: 204 executed, 1 up-to-date
[ +444 ms] Running Gradle task 'bundleRelease'... (completed in 192.3s, longer than expected)
[   +4 ms] "flutter appbundle" took 194,296ms.
[   +3 ms] Gradle task bundleRelease failed with exit code 1
I know this is not the best place to report such things but not sure where to "go" else :(
Thanks in advance for not closing tis issue and for the help. :)

I was able to solve my issue - i dongraded Java from 12 to 8 on my CI. Hope it will save some time for others.


Some text strings are used in older Minecraft versions only

UPDATED TO REFLECT THE CURRENT STATE FROM BETTER PVP VERSION 21.16.0 (AND 21.10.6).
I tested multiple versions of your Better PvP mod, and found a few text strings that are exclusive to specific Minecraft versions. These text strings are listed an grouped below.
For every group, I will have a question. I would be grateful if you could answer these questions.
(1) Only used up to and including 1.16:

gui.xaero_render_layer (line 273)

(2) Only used in 1.14 and newer:

gui.xaero_cross_tp (line 276)

(3) Only used up to and including 1.12:

gui.xaero_box_cave_maps (line 302)

(4) Only used up to and including 1.8:

gui.xaero_waypoints_scale (line 163)
gui.xaero_box_waypoints_scale (line 396)
gui.xaero_entity_radar (line 224)
gui.xaero_entity_radar_type (line 365)
gui.xaero_box_distance (line 305)
gui.xaero_auto_clamp_depth (line 389)
gui.xaero_waypoints_clamp_depth (line 390)
gui.xaero_box_waypoints_clamp_depth (line 393)
gui.xaero_box_waypoints_distance_scale (line 394)
gui.xaero_box_waypoints_name_scale (line 395)

Ad 1: Why it has been removed in 1.17? Do you plan to bring it back or it will stay that way from now on?
Ad 2:  It is probably impossible to backport due to Minecraft/Forge API limitations or simply not worth the effort, but I would like to make sure.
Ad 3: This is probably an oversight. In 1.12 the new text string that superseded this one should be used, as 1.12 has the new ceiling detection.
Ad 4: Versions 1.8 and 1.7 are currently stuck on an older mod version. Will this change in the future? What is your plan here?

Thank you for the feedback!

It was removed because render layers don't exists in 1.17. Never existed on Fabric so the option did nothing and now Forge completely reworked their UI system.
You can't teleport to another dimension pre 1.14.
Didn't realize this was the case. Really appreciate it!
I'm only going to release bug fixes and update translations for 1.7 and 1.8, so these lines are necessary for that purpose. I might drop updating translations but haven't decided yet.

Thank you for the explanation. I have one more question, how long are you going to support 1.8 and 1.7? Any estimates?

Sorry for not responding sooner. I'm not sure. Probably a long time.

I think this is "resolved" now, so I'm closing the issue.


Property resolveToContext is present in docs, but missing in webpackOptionsSchema.json.

Do you want to request a feature or report a bug?
bug probably
What is the current behavior?
Property resolveToContext is present in webpack 2 docs, but missing in webpackOptionsSchema.json.
When I try to use it I get a WebpackOptionsValidationError: configuration.resolve has an unknown property 'resolveToContext'.
If the current behavior is a bug, please provide the steps to reproduce.
Just add this prop to resolve key of configuration object and try to bundle some stuff.
What is the expected behavior?
If webpack doesn't use this prop, related info should be removed from docs.
Otherwise property should be added to webpackOptionsSchema.json.
Please mention other relevant information such as the browser version, Node.js version, Operating System and programming language.
webpack v2.0.0-rc.4

Should be removed from the doc. Could you file an issue in the docs? Or better submit a PR.


Vickel: Watch hanhchinhnhansu.edu.vn

Vickel requests the watch of the watch_keyword hanhchinhnhansu\.edu\.vn. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

hanhchinhnhansu\.edu\.vn has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Allow timeseries scrapers to scrape all, or ranges, of their data, all the time.

Summary
Our current scraping often uses the locale-cast date as a criteria for timeseries, which can cause many scrape "misses".  Timeseries scrapers can (and possibly should) simply scrape and submit some or all of their existing data.
This was originally proposed in https://github.com/covidatlas/coronadatascraper/issues/250.  It's still a good suggestion, and is worth doing.  There are some issues with this idea though, see "Issues" below.
Why this is necessary.
For Italy, and for many other timeseries sources, we have logic like the following:
      scrape ($, date, { getIso2FromName }) {
        const states = $
          .filter(row => row.data.substr(0, 10) === datetime.getYYYYMMDD(date))   // <<< NOTE!!!
          .map(row => ({

Unfortunately, since Italy doesn't publish their data every minute, this often means that their data isn't available at the time of scraping.  e.g., the data at https://raw.githubusercontent.com/pcm-dpc/COVID-19/master/dati-regioni/dpc-covid19-ita-regioni.csv currently has latest date 2020-06-21T17:00:00, but it's now 2020-06-22 in Italy.
For Italy, this means that the scrape returns 0 (and actually throws an exception for that source) fairly regularly -- at least whenever we cross over the "date line".
To me, this handling doesn't make sense.  Italy provides the data for dates that it has.  We should scrape what it has, and use its dates.
Other examples from staging
At 11:55 PM Toronto time, https://api.staging.covidatlas.com/status?format=html shows:

These are all timeseries (cz, it, nl, se), and are using some kind of date filtering.  As a result, they will fail and then go back to reasonable constantly.
Issues
We'll need to think about how this works with regeneration.  Currently, src/events/regenerator request a new scrape for all n dates.  If a timeseries source decides to re-write all n dates during its single scrape, this will result in n*n writes.  Currently, all timeseries data sources only write data for one date, but that feels artificial.
I'd like to come up with a way to handle both scenarios (1. source writes all dates, 2. source writes single date) .  A method that comes to mind right now is something like a conditionalScraper event that checks the database records before running.  Will let this gestate a while to see if another idea strikes me.

@ryanblock cleverly already implemented this, with regen-timeseries schedule and events.  Thanks Ryan, great stuff! jz


Question: Accepting OAuth "Authorization" header as "AuthToken" header

I am using OAuth implicit flow and successfully accepting authorization bearer token on the server side. However, the library I am using  to authenticate the user expects auth header by the name of "AuthToken" instead of "Authorization". Is there a way for me to define that anywhere? Just a note that I am using Swashbuckle ver 5.2.1 and my application is not using OWIN middleware.
Thanks,

This is really a question for the folks who build swagger-ui (https://github.com/swagger-api/swagger-ui). As far as I know, it's not supported through configuration.
However, If you're happy to do a little monkey patching, you could get it working fairly quickly. You just need to inject you're own version of the swagger-oauth JavaScript, with the following line modified ...
https://github.com/domaindrivendev/Swashbuckle/blob/v5.2.1/Swashbuckle.Core/SwaggerUi/CustomAssets/swagger-oauth.js#L280
SB provides a config option to inject custom content - https://github.com/domaindrivendev/Swashbuckle#injecting-custom-content. Follow the instructions and you'll be able to apply this technique for your custom oauth solution:


Can't launch SDK 3.0.10 on MacOS Sierra

I tried opening in Terminal as well but no output. I also have JDK 1.8 installed.

Step 1: dont use 3.0 but 3.1, because 3.0 is not being maintained anymore.

Exactly that.
And for 3.1 we'd need more information about it since when you launch it in terminal you should have some output

I do have exactly the same issue. I'd suggest a notice (README/release notes/website) to spare some time and bandwidth.

And 3.1 fixed it for you? (Because I don't actually think so).
We'd need some debugging output, the best would be some ant run after having built the sdk (./build_engine.sh and then ./gradlew buildSdk).
I can atleast verify that both 3.0 and 3.1 work fine on 10.9.5 and don't see an actual reason why they don't work on sierra, though.

@MeFisto94 jMonkeyEngine SDK 3.1.0-beta2-b001-SNAPSHOT seems to start on macOS 10.12.2 in contrast to the current release tag. I didn't test anything besides that.
I might include some debugging output of the 3.0.0 version if I find the time.

This is the log file for version 3.1.0 (built with ./build_engine.sh and ./gradlew buildSdk and creating an unmodified BasicGame projec and running it once): https://gist.github.com/muellermartin/5f6104a6d2851b34fda24085bdcbdc6f
Currently I'm not able to build the SDK version 3.0.0 stable tag at 283bc294 (using ./gradlew buildSdk - there is no shell script like in the newer version) because of this error:
Warning: getReleaseInfo() found an errorneous tag: "stable". Syntax Error: The Tags Main Version didn't consist of two/three parts
Full Version: 3.1-HEAD-1624
POM Version: 3.1.0-HEAD-SNAPSHOT
NBM Revision: 1624
NBM UC Suffix: HEAD-nightly/3.1/plugins
Download http://jcenter.bintray.com/org/jmonkeyengine/jme3-effects/3.1.0-beta1/jme3-effects-3.1.0-beta1.pom
Download http://jcenter.bintray.com/org/jmonkeyengine/jme3-blender/3.1.0-beta1/jme3-blender-3.1.0-beta1.pom
Download http://jcenter.bintray.com/org/jmonkeyengine/jme3-jogg/3.1.0-beta1/jme3-jogg-3.1.0-beta1.pom
Download http://jcenter.bintray.com/org/jmonkeyengine/jme3-networking/3.1.0-beta1/jme3-networking-3.1.0-beta1.pom
Download http://jcenter.bintray.com/org/jmonkeyengine/jme3-niftygui/3.1.0-beta1/jme3-niftygui-3.1.0-beta1.pom
Download http://jcenter.bintray.com/org/jmonkeyengine/jme3-plugins/3.1.0-beta1/jme3-plugins-3.1.0-beta1.pom

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/martin/Projects/jMonkeyEngine-sdk/build.gradle' line: 130

* What went wrong:
A problem occurred evaluating root project 'jMonkeyEngine-sdk'.
> Could not resolve all dependencies for configuration ':corelibs'.
   > Could not find org.jmonkeyengine:jme3-jbullet:3.1.0-beta1.
     Searched in the following locations:
         http://jcenter.bintray.com/org/jmonkeyengine/jme3-jbullet/3.1.0-beta1/jme3-jbullet-3.1.0-beta1.pom
         http://jcenter.bintray.com/org/jmonkeyengine/jme3-jbullet/3.1.0-beta1/jme3-jbullet-3.1.0-beta1.jar
         http://updates.jmonkeyengine.org/maven/org/jmonkeyengine/jme3-jbullet/3.1.0-beta1/jme3-jbullet-3.1.0-beta1.pom
         http://updates.jmonkeyengine.org/maven/org/jmonkeyengine/jme3-jbullet/3.1.0-beta1/jme3-jbullet-3.1.0-beta1.jar
         http://nifty-gui.sourceforge.net/nifty-maven-repo/org/jmonkeyengine/jme3-jbullet/3.1.0-beta1/jme3-jbullet-3.1.0-beta1.pom
         http://nifty-gui.sourceforge.net/nifty-maven-repo/org/jmonkeyengine/jme3-jbullet/3.1.0-beta1/jme3-jbullet-3.1.0-beta1.jar
     Required by:
         :jMonkeyEngine-sdk:unspecified

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 9.05 secs

I can run 3.0 no problem on Sierra btw.

@normen Do you have Java 8 installed?

The 3.0 SDK comes with Oracles JDK 1.7 included.

I want to comment on that again, sorry that it has been so long.
The build issue should be fixed in the most recent versions and building stable (3.0) won't work as the tag is just wildly set and there is no code in this repo for 3.0, it actually starts post 3.0 I guess.
We now also have a 3.1.0-stable tag anyway

So, close this?


fixed a synchronization issue on thread_list

It was possible for a thread to call ExitThread() before it was added to thread_list. In this case a signal was never sent and was never caught by WaitForSingleObject().
Now is ensured that the thread ID is added to thread_list first by the thread itself or by the thread calling pthread_create(). Since thread_list is synchronized, it should not hurt to add two times the thread ID. This is maybe simpler than to check if the ID is already in the list.
winpr-thread:

added the unit test: TestThreadExitThread
fix: ensure thread_list to be up to date before to call ExitThread()
possibly resolved: Problems with serial redirection #2389

@freerdp-bot test

@eledoux if I'm not mistaken with this pull request it can happen that old thread stick around in the thread_list. List_Remove only removes the first matching element found therefore, if added twice, one item would always stay in the list causing it to grow over time.

@eledoux Wouldn't it be better to use a wait condition for this synchronisation issue? Then thread_launcher would wait until winpr_StartThread updated the list and the race is fixed. No duplicate entries in the thread list.

@bmiklautz you're right there is indeed a possibility to call CloseHandle() before thread_launcher() is done. The @akallabeth's solution is then better. However should we be afraid on a bad impact on performances?

@bmiklautz @akallabeth With this new implementation, I'm not quite sure it is a bright idea to use a winpr's Event object in the WINPR_THREAD structure even if we should not have some circular dependencies here. An implementation based on winpr_sem_t or anything else could have been better?

@eledoux Would suggest using a pthread_condition, CreateEvent uses quite a lot of resources.

please test

Implementation looks good, I can't see any locking problem.
+1

Thanks for the suggestion. I'm getting happy with this implementation which is a bit faster. I also made a try with an implementation that was using only one semaphore (sem_t). This latter was a bit more faster but looking at semaphore.c it seems a such solution is not portable enough, isn't it? (I develop only on Linux)
Otherwise using a semaphore from CreateSemaphore() with WINPR_PIPE_SEMAPHORE still defined was even slower than using an Event.

IMHO you have the optimized version now, don't change anything.

lgtm +1


add option to send ajax data straight to the callback

I have a callback that receives html data, then inserts it in the correct place in the DOM.  Unfortunately, Infinite Scroll corrupts the data before the callback can be called.
This option prevents that.
This is likely too dirty to be merged but, with some feedback from someone who understands how things are supposed to work, I hope it can be turned into a proper fix.
Here's the way I use it:
  //
  //        infinite scroll
  //
  $("#assets").infinitescroll(
    {
      loading: {
        msgText: "Loading more listings...",
        finishedMsg: "No more listings."
      },
      navSelector:  "nav.pagination",
      nextSelector: "nav.pagination a[rel=next]",
      appendCallback: false,
      dontScrewUpTheData: true,
      path: function (page) {
        var query = window.location.search.replace(/([?;&])page=[0-9]+[?;&]/, "$1")  // remove ?page= from querystring
        return "/results" + (query.length > 2 ? query + "&" : "?") + "page=" + page
      },
    },
    function (data,opts,url) {
      if(data.trim() != "") {
        compute_destination().append(data)
      } else {
        return "end"
      }
    }
  )
  // unfortunately infinitescroll doesn't hide the paginators until AFTER it starts
  // ajaxing the new content so the paginators appear & flash off quickly.  Ugly.
  // Quick workaround that won't get in the way if javascript is turned off:
  $('nav.pagination').hide()

I'm very open to comments on how I can do this better.  Just muddling along the best I can...

Infinite Scroll v3 is out!. It's an all new re-write, so take a look at how to upgrade from v2. With the brand new release, this contribution is no longer applicable.
Thank you for your interest and effort in Infinite Scroll. Sorry I had to pass on this one. 🌈🐻


mate.mate-utils: 1.26.0 -> 1.26.1

https://github.com/mate-desktop/mate-utils/compare/v1.26.0...v1.26.1
Description of changes
This is originally part of https://github.com/NixOS/nixpkgs/pull/230843, but I decided to separate this since it has flaky build issues and I want to take a look at it.

https://github.com/mate-desktop/mate-utils/issues/210
Sample failure: here
Sample success: here

As the last resort we can either try to push this as-is and restart the build on hydra.nixos.org :see_no_evil: or disable the pt translations, wow amazing :upside_down_face:
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

I made some noise on the upstream issue. I will do another six attempts a few hours later and hopefully I can undraft this then :upside_down_face:


May you help me? How to remove this HightLight Section  ?

Use this ?  It just could be hide .
 document.getElements('pre').enlight(false);

And remove #div.EnlighterJSWrapper# ?
It can't hightlight again ...   :-(

I wanna remove it  , Because When I execute it many times. It will  show highlight section many times.

Dear XMap,
For performance reasons the enlight(false) call will only toggle the container visibility (EnlighterJSWrapper is set to invisible, you pre container visible again).
In case you remove the DOM it cannot be highlighted again - you have to create a new EnlighterJS instance.
Best regards, Andi

Am 21.08.2015 um 07:28 schrieb XMap<EMAIL_ADDRESS>I wanna remove it , Because When I execute it many times. It will show highlight section many times.
—
Reply to this email directly or view it on GitHub.

En,  I'm know that  ...  but why this framework use this MooTools .Does it conflict with jQuery  or Angulr?

You can use MooTools together with jQuery. But you should take of the the script include priority: http://mootools.net/blog/2009/06/22/the-dollar-safe-mode

i've added an additional dispose() function to the EnlighterJS class which will destroy all generated DOM Elements and restores the original state (unhighligted code).
Element Style
// remove highlighting (drop generated HTML from DOM)
document.id('myHighlightedCode').enlight('dispose');

OOP Style
// create a new EnlighterJS instance
var myEnlighter = new EnlighterJS(document.id('myCustomCode'), {
  language: 'php',
  showLinenumbers: false
});

// enable highlighting
myEnlighter.enlight(true);

// remove highlighting (drop generated HTML from DOM)
myEnlighter.dispose();

:thumbsup:


Shows _UNKNOWN_APP When using HDMI Source

When playing via an HDMI input the UI shows _UNKNOWN_APP instead of the HDMI input name or some other more useful display.

Is your device actually on HDMI 1? The source should only show as an app when the current source is SMARTCAST or CAST

if you are willing to run pyvizio locally you can test what source input pyvizio is seeing. If it is indeed SMARTCAST or CAST, I'm not sure what can be done here because your TV is advertising the wrong source. You may want to try a hard reset of your device (unplug/replug) - maybe the API is hosed

Is your device actually on HDMI 1? The source should only show as an app when the current source is SMARTCAST or CAST

It is indeed on HDMI-1, specifically and Apple TV plugged into that input.

if you are willing to run pyvizio locally you can test what source input pyvizio is seeing. If it is indeed SMARTCAST or CAST, I'm not sure what can be done here because your TV is advertising the wrong source. You may want to try a hard reset of your device (unplug/replug) - maybe the API is hosed

I will give this a shot and see if I can debug further.

Ok, here is the output of two commands from pyvizio when input is set to HDMI-1 and therefore no app is currently running, the first is from get-current-input:
$ pyvizio --ip=<ip>:<port> --device_type=tv --auth=<code> get-current-input
INFO:pyvizio.cli:Current input: HDMI-1
This seems to accurately indicate that HDMI-1 is the current input selected.
When I run get-current-app, here is the result:
$ pyvizio --ip=<ip>:<port> --device_ype=tv --auth=<code> get-current-app
INFO:pyvizio.cli:Can't determine the name of the app, the currently running app's config is AppConfig({'APP_ID': 'hdmi1', 'NAME_SPACE': 8, 'MESSAGE': None})
This looks like an appropriate error because no app is running.  My assumption is that HASS is not using this result properly and showing _UNKNOWN_APP, which while kind of true, isn't the optimal user experience.

thanks this is really helpful. Vizio has been making a bunch of changes to their API recently, and since this package has been built around reverse engineering, it has been a cat and mouse game. I may need some more info but this is really helpful for now, I will keep this open and reach out if I have any other questions

Happy to assist, let me know if you need anything else.


Fixed Pagination not working as expected

[x] Fixed Pagination

Before
Regardless of the pagination setting being configured for 5, all the data will still be displayed
After

No Need Now.


Privacy - GDPR

[ ] Describe nowcontent.xyz and the fact that nothing is stored before you bookmark data, and then in the other services.
[ ] Describe / link to Zapier.com
[ ] Describe / link to Sanity.io
[ ] Describe / link to JSONbin.io

JSONbin.io - https://jsonbin.io/privacy-policy
Zapier.com - https://zapier.com/privacy/
Sanity.io - https://www.sanity.io/legal/privacy

Put it in a footer.

And what GitHub stores (mostly IP's): https://help.github.com/en/articles/github-privacy-statement#github-pages

https://github.com/eklem/nowcontent.xyz/commit/20f1680e465ecceea41bf192f1c3ad4024ef334c

https://github.com/eklem/nowcontent.xyz/commit/20f1680e465ecceea41bf192f1c3ad4024ef334c


chore: update evm types

Description
update new type export naming conventions for unchained evm types
Notice

[ ] Have you followed the guidelines in our Contributing guide?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[x] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

Risk
none
Testing

Screenshots (if applicable)

needs lib package 🧀


caching of Buffer()

I've noticed a discrepancy when caching a Buffer (such as for an image).  The memory cache set/get work fine.  However, on Redis or the FS cache modules, get returns a JSON string like this:
{"type":"Buffer","data":[65,66,67,68,69,70,71]}

Just wondering if there is a suggested way of handling this.  Should the modules themselves store metadata in the cache that a buffer was stored as a value and then deserialize it?  Or should there be an options flag in the cache-manager set command that indicates it's caching a buffer.

I think this would be something that you implement in your store.  I don't think cache-manager is manipulating this data anywhere that I know of.

got it.. so probably just need to create an option in the underlying storage module that understands that a Buffer is getting set.  It seems like cache-manager alreayd supports sending custom options, so I will work with the redis and fs module maintainers with a pull request.

Cool, sounds good.


Implement common place to implement styles

https://developer.chrome.com/docs/extensions/mv3/architecture-overview/

#33


Docs for ALTER ORDER BY

@blinkov Thanks for the comments. https://github.com/yandex/ClickHouse/commit/64bdb2a4040a6a10ce311d16e8553dcfc210cdf3


Update smithy4s-http4s, ... to 0.17.15

About this PR
📦 Updates

com.disneystreaming.smithy4s:smithy4s-http4s
com.disneystreaming.smithy4s:smithy4s-http4s-swagger
com.disneystreaming.smithy4s:smithy4s-sbt-codegen

from 0.17.0 to 0.17.15
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.disneystreaming.smithy4s" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.disneystreaming.smithy4s" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, version-scheme:early-semver, commit-count:1

Superseded by #63.


Porting Avro format enhancements - Part 1

For supporting record and map types in Avro, closes #610
List of ported changes:

ClickHouse/ClickHouse@f98010e37436acac69c39c5b7ce041f4d919623b
ClickHouse/ClickHouse#37525
ClickHouse/ClickHouse@6bf29cb6103ff3a33d6e2fc6cbc5360b7e3f0be0
ClickHouse/ClickHouse@0781e8b4f7f6d84ab0005a1597f204675aacbf20
ClickHouse/ClickHouse@4e76629aafc4e855e6a1d006e655d48ea141c6ea (partial)
ClickHouse/ClickHouse@8479615c485d0cffa574bca83f135104fc65aeeb
ClickHouse/ClickHouse@aa3c05e9d49bcc8f2bcc6d79242742de6b16e51a
ClickHouse/ClickHouse@a1a22b000768f1a1d8525ee8197e9523ea7f9194
ClickHouse/ClickHouse@c36255164271fd1efd64bd034df1b7ca544a0ef3
ClickHouse/ClickHouse@bd10a9d2d4ff2244f5f7aae4bbdb8af322c91534 (partial)
ClickHouse/ClickHouse@235649cb984371cb141f349f07959611062a5e12
ClickHouse/ClickHouse@5ba7a55c18303c9156591b4c03e7eb74d213e778 (partial)

PR checklist:

Did you run ClangFormat ?
Did you separate headers to a different section in existing community code base ?
Did you surround proton: starts/ends for new code in existing community code base ?

Please write user-readable short description of the changes:

(Jove Github Bot) added it to the current sprint.

(Jove Github Bot) moved this ticket out of the GitHub project(up to 1200 tickets for one project).


Misleading error message for !contains option

When step is
And match response !contains { grants : '#array', roles : '#array', firms : '#array' }.

and response includes grants/role/firms array then test fails with message below
com.intuit.karate.exception.KarateException: path: $.grants, actual: [1,2], expected: '#array',
reason: actual value contains expected

This is misleading. Should be something like
com.intuit.karate.exception.KarateException: path: $.grants, actual: [1,2], unexpected: '#array',
reason: actual value contains unexpected

fixed in dev and also made an "un-official" release <IP_ADDRESS> - can you take a look.
here's a sample:
* def response = [{ grants : [1,2], roles : [1,2], firms : [1,2] }]
* match response !contains { grants : '#array', roles : '#array', firms : '#array' }

log:
08:49:12.577 [main] ERROR com.intuit.karate - assertion failed: path: $[*], actual: [{"grants":[1,2],"roles":[1,2],"firms":[1,2]}], NOT expected: {grants=#array, roles=#array, firms=#array}, reason: actual value contains expected

Confirmed <IP_ADDRESS> fixes actual/expected misleading.
However, it seems I was not clear enough in start post - reason is also misleading. It says reason: actual value contains expected, I would expect something like reason: actual value contains unexpected

@avpavlov oops, I totally missed it, was intending to. Thanks for confirming and I've made the change you suggested. Will release later though: https://github.com/intuit/karate/commit/9b85eb676fb1d672131f581c078fdf70d0fc3c9c


Correct secp256k1_gej_add_ge with 2M - S performance hit

Fixes https://github.com/bitcoin/secp256k1/issues/257 by catching the degenerate case, which appears as an intermediate variable being 0/0, and using an alternate expression for that variable in this case.
This results in only a 6% perf hit on signing. This comes from roughly one additional multiplication, so it seems unlikely we'll be able to do better.

Push to fix everyone's comments (comment fixes and Peter's awesome speedup).

We might want to update the citation above to point out that the additive law given in the citation is actually not complete, lest some unwary traveler see the citation and go there rather than reading the code.

For what it's worth, the citation does say that it's assuming the y1 = -y2 case does not occur.

Push with comment fixes and a much-expanded comment about our high-level strategy for obtaining constant-time multiplication for all pairs of points (well, except those with a = infinity).
We might be the first to have produced a fast, constant-time algorithm which works for all pairs of points. When developing this fix I checked both Trezor and OpenSSL, and their constant-time additions both have degenerate cases (specifically both don't work when asked to double) which they avoid by being careful about how constadds are used in their larger algorithms.

ACK


Hyperverse Integration

Integrate Hyperverse to give smart module access to developers.

Nice suggestion; great to have on Celo Sage or Celo Examples, not on Celo Composer.
Closing issue.


Add status command to vmq-admin node

Proposed Changes
Adds a status command to vmq-admin that shows the same information as the status page. This makes it available as vmq-admin command, as well as via the v1 api.
Types of Changes
What types of changes does your code introduce to this project?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes issue #XXXX)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (correction or otherwise)
[ ] Cosmetics (whitespace, styles...)
[ ] DevOps (Build scripts, pipelines...)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

[ ] I have read the CODE_OF_CONDUCT.md document
[ ] All tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if needed)
[ ] Any dependent changes have been merged and published in related repositories
[ ] I have updated changelog (At the bottom of the release version)
[ ] I have squashed all my commits into one before merging

Further Comments
If this is a relatively large or complex change, kick off the discussion by
explaining why you chose the solution you did and what alternatives you
considered, etc.

I think the status page calls for node status every 10 seconds when it is open. So, it's fine doing it manually, in terms of internal load.
Note there's also vmq-admin metrics show for a full metrics snapshot.
PR looks good to me. I hope the CLI table display looks good too :)


Example notebook for radiation evaluation

includes:

global mean time series relative to CERES
monthly bias maps relative to CERES
Gregory-plot relative to CERES/ERA5

Awesome! Danke!


Failed push breaks repo

I believe we had a failed push, which broke a repo in our registry. The logs from the push look like it hung, and was eventually killed. This seem to put a layer in the index which doesn't exist, and we can no longer pull that image.
When pulling, the docker server shows
Server error: 404 trying to fetch remote history for 0554e7f95c4a74fcf9600d76ef62f0c4d32
The pull continues after the 404, but ends with Could not find repository on any of the indexed registries.
This is a prod registry running with S3 as a backend.

Has any progress been made on this issue? I'm currently running into it using AWS ECR.


add link to dwOpen page

gp-common is a great landing place for the other GitHub repos.
But we could consider something like:

Read more about this service on dwOpen

close in favor of #10

to add to top para:

To connect with the IBM Globalization Pipeline open source community, check out developerWorks Open


Test for stillborn entities

This commit adds a failing test addressing dynamic creation and deletion of entities in different systems. The core intent is to check whether components can be inserted immediately after entity creation. Note that in a test which only creates entities (ie. without deleting any) I was not able to detect the problem this test is designed to highlight.
cc @kvark

Thanks for the test case! #66 should fix it...

Great stuff, thank you @malleusinferni , you rock!


Set individual node mass in Force Atlas

HI,
I don't see a way to set node mass individualy in the Force Atlas.
I would like to like to block a node after dragging it by setting a large mass on it.

Hello @Zooip. You can try to increase the node using its weight attribute & by fiddling with the weight settings of the layout. But if what you want is just to fix the node you can also use the fixed attribute & set it to true.


Please add a license to this project

Without one people won't be legally allowed to use the plugin in their Trino clusters.

Sure. will add this weekend

Added. Please check


Update

:tada: This PR is included in version timeclicker_server-v1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version timeclicker_client-v1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: