Where is the code of how to compute NWD loss?

@jwwangchn  Where is the code of how to compute NWD loss? I want to put the losss to my own code. Thanks!

Please refer wasserstein_loss()

@jwwangchn Thanks.

hi @jwwangchn
for anchor-based or anchor-free one-stage detector, only use the wasserstein_loss to boost the performace? it seems that label assignment is used for rpn of two-stage detector.


Request: no automatic focus on search field after opening Excalibrain

Open a note in one pane. Open Excalibrain normal. Excalibrain opens in a second pane for the selected note in the first pane. As expected. Yet, the search field is automatically activated and therefor a large dropdown is displayed (and an additional click is needed to make it disappear).
Request: prevent focus on search field when excalibrain is opened (or even better: make it optional).

implemented in 0.1.11


material design dismissed some icons

[x] Review the documentation: https://github.com/oblador/react-native-vector-icons
[x] Search for existing issues (including closed issues): https://github.com/oblador/react-native-vector-icons/issues

Environment
  Binaries:
    Node: 10.15.3 - /usr/local/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
    Android SDK:
      API Levels: 28
      Build Tools: 28.0.3
      System Images: android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
  IDEs:
    Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
    Xcode: 10.2/10E125 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: 0.60.3 => 0.60.3
    react-native-vector-icons => 6.6.0
  npmGlobalPackages:
    react-native-cli: 2.0.1

Description
toggle on and toggle off does not exist in Material design library
Material Design reference

arrow-back-ios is missing too.

photo-album is missing also

file-copy is missing

Should be solved with more recent updates


Essentials, Luckperms and Vault Support

Would it be possible to add support for Essentials, Luckperms and Vault? It would be really useful to be able to manage player permissions with LuckPerms and have the ability to use essentials commands through the API.
Routes:
/v1/players/perms ( Return all player perms )
/v1/player/perms/update ( Update player perms )
/v1/player/:id/mute ( Mute a player )

If implemented, the plugins should have their own route.
/v1/essentials/mute
/v1/luckperms/user/permission/update

That seems like a bit much in my opinion, that would be a lot of routes when you could just have one route with compatibility with existing plugins on the server and fallback to other solutions.

Since we have a dev api now we could just made another plugin that hooks into ServerTap and adds custom endpoints for each plugin. I would say it might be worth integrating a Luckperms endpoint right into ServerTap since it is the most widely used perms plugin.


CONTENT-67: db migrate in containers

This:

builds the migration files and the migration command into the container
configures the deployment to use an init container to migrate the database
Adjusts the migration command to not error if no changes are detected

Would I test this by trying to deploy it?

You can if you'd like:
 bonfire deploy -n $NS --set-image-tag  jlsherri/content-sources=fd5a03268be-test content-sources

with my local bonfire config modified to be:
# Bonfire deployment configuration

# Defines where to fetch the file that defines application configs
appsFile:
  host: gitlab
  repo: insights-platform/cicd-common
  path: bonfire_configs/ephemeral_apps.yaml

# (optional) define any apps locally. An app defined here with <name> will override config for app
# <name> in above fetched config.
apps:
- name: content-sources
  components:
    - name: content-sources
      host: github
      repo: jlsherrill/content-sources-backend
      path: deployments/deployment.yaml
      parameters:
        - name: ENV_NAME
          required: true

Note that repo was changed to point to mine where 'main' has this change.


Make Storyblok Bridge disabled by default

Context
According the current documentation: https://github.com/storyblok/storyblok-astro#using-the-storyblok-bridge:

The Storyblok Bridge is automatically activated by default.

Code:
https://github.com/storyblok/storyblok-astro/blob/d45878d9f1deef23a297931847f1776fbc332d7c/lib/index.js#L57
But that is in fact seems wrong way to approach it, as the users of storyblok-astro package may risk having redundant https://app.storyblok.com/f/storyblok-v2-latest.js script loaded even if they do not use it (that happened for us once 😄 ). It seems package users must add bridge: false explicitly to disable this script in production build targets.
How it works now (opt-out):
bridge: true | undefined,          // load script
bridge: false,                     // skip script

IMHO, it is much more intuitive to go (opt-in):
bridge: true,                      // load script
bridge: false | undefined,         // skip script

Because this way the bridge script is loaded ONLY if it is explicitly needed.
TODO

Change bridge script loading to be disabled by default

Thank you! I agree with your reasoning. We'll look into it. 🙂

Hey @edv-ns, thanks again for your suggestion.
My colleagues and I discussed it but decided against implementing it in this integration. Disabling the bridge by default would create an inconsistency with all our other SDKs. As using the bridge is the most common scenario, we decided to employ an opt-out strategy. If we change it for the Astro SDK, we would have to change it everywhere. Since it can easily be disabled, I'm closing this issue.


ci: using random order when doing the tests

Description
As the title. #GoodPractice
Issue linked
NA
Checklist

[x] I have visited and read Develop PyMAPDL.
[x] I have tested my changes locally
[x] I have added necessary documentation or updated existing documentation.
[x] I have followed the PyMAPDL coding style guidelines.
[x] I have added appropriate unit tests that also ensure the minimal coverage criteria.
[x] I have reviewed my changes before submitting this pull request.
[x] I have linked the issue or issues that are solved to the PR if any.
[x] I have assigned this PR to myself.
[x] I have marked this PR as draft if it is not ready to be reviewed yet.
[x] I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

@germa89 While passing by... Would it make sense for you to use pytest-xdist ? This way you could speed up your tests by running them in parallel. If there is a limitation such that one worker has to work on a whole file, you can also use the option --dist loadfile so that each worker is provided with a test file and handling it totally.

hi @SMoraisAnsys
Thank you a lot for the suggestion! This is a good idea, and believe we did try it in the pass. The main limitation is that I will have to spin several MAPDL instances which is "heavy" since the docker image is huge. So far, our main bottleneck is on the documentation generation where I do want to implement some parallelization technique, probably having more than one MAPDL image.

I'm going into bucle because of the images cache.

I knew that changing the order will increase the time... but yisus.... that's a lot. And I think it is just the respawming of the MAPDL what is taking the time....  but I do not have any probe of this.

@pyansys-ci-bot LGTM.


network deployment of extension to multiple PCs

The ability to import the plugin from within the application is a nice touch for a non-technical stand-alone user, but in a school environment with hundreds of lab PCs used by a couple of thousand students, a zero touch approach to deploying apps and plugins is a must.
In Sketchup 2014, there was a plugins folder you could copy a plugin to and all users had access to a consistant experience.
In Sketchup 2015 the folder landscape and the way "plugins" are handled seems to have changed significantly.  After installing the stl extension on a test machine, I searched against the various filenames to discover where the extension's files landed- and I came up empty.
Perhaps someone in the know could insert a bit of doco with the plugin files to explain mass deployment options would be a good idea.

This isn't specific to the STL plugin, so I would suggest you ask this on the official SketchUp forums[1]  where some very expert users are more likely to see it.
[1] http://forums.sketchup.com/

The folder locations didn't change for SU2015. In SU2014 it was changed so that extensions where installed in the user folder in order to avoid permission issues.
To install extensions for all users you can manually install (extract) them to:
C:\ProgramData\SketchUp\SketchUp 2015\SketchUp (Replace version number as appropriate.)

This is a good topic for a blog article though.


not firing gsapify router on initial app load

hey
this might be a bit hacky but:
wrapping lines 252-257 in a timeout allows passing state.data through to the self.$get function on initial app load
any chance of getting this included?
ta
EDIT: that suggested fix causes other issues, sorry ignore it

could line 146 be optional?
var duration = $state.previous.name === '' ? 0 : from.duration, // don't trigger transition on boot

What are you actually trying to do? Animate a state in at the beginning?
If so then the simplest thing to do is probably just trigger the state by forcing the transition with $state.go('stateName', {reload: true}) or switching to a blank intermediary state and then immediately switching back.

exactly. have been figuring out workarounds to trigger a transition on boot on every site I've used this on, feels a bit hacky though. would making transition on boot configurable cause any issues? if not I don't mind making a pull request...

Well it would be a pretty major change - the reason its setup this way is to mirror the behaviour of ui-router which doesn't cause a transition on initial load, I've taken this to be the expected behaviour now.
The obvious place for this option would be the provider, you'd then set it in the config stage of the app:
gsapifyRouterProvider.initialTransitionEnabled = true; // false by default

Would definitely take a PR for that...

Ah ok, great have sent a PR


xm002 NO SELECT Unsafe Login. Please contact<EMAIL_ADDRESS>for help

163 mailbox database, including the author, everyone should be Chinese, right? I'll use Chinese
I started the stamp service in the mailbox settings, and the authorization code was also set. Using this library, I can connect, but once search (searchcondition. Unseen()) is called
There will be the above error, Baidu said a bunch of links can be verified<EMAIL_ADDRESS>But this link seems to be invalid, and can't be opened. Do you have any solutions???
Thank you all for your contribution

I found the problem. It's said that I want to send the ID command before the login method of the source code. I tried, but I didn't report an error. Someone explained that I need to show my identity before logging in, that is, I want to send the client information, such as name, version no, system version, etc
But here comes a new problem
client.NewMessage += Client_ NewMessage;
When the handler subscribing to the NewMessage event will report: the server does not support the IMAP4 idle command exception. This error completely blinds me

You should seriously consider switching over to MailKit. It seems like ever since MailKit came onto the scene 8+ years ago, all of the other open source IMAP libraries died off. MailSystem.NET, ImapX, S22.IMAP, and AE.Net.Mail.
Check the commit history for this project and you will see for yourself. It's as dead as a door nail.
You are wasting your time continuing to use this library.


fix: matchMedia is not defined

This PR fixes an error when using next.js SSR

This should also fix this issue in tests:
Just add it in toast.test.tsx
Object.defineProperty(window, 'matchMedia', {
  value: () => {
    return {
      matches: false,
      addListener: () => {},
      removeListener: () => {},
    };
  },
});

@timolins any news on this :D?

This is sorely needed. Also for gatsby, or any other SSR for that matter.

Thanks!


HDDS-5514. Skip check for UNHEALTHY containers for datanode finalize.

What changes were proposed in this pull request?
Skip check for UNHEALTHY containers for datanode finalize.
More details in the jira below.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5514
How was this patch tested?
no test

Thanks for the fix @guihecheng. +1 LGTM.


to_graphviz for diagrams with anonymous objects

The method to_graphviz_property_graph(d::Diagram; kw...) would previous fail if given a diagram with anonymous ob/homs in the indexing category. It now checks if the graph associated to the indexing category is a NamedGraph, if so it will use the names in vname, and otherwise empty names are used. This PR also adds tests for both the named and anonymous case, as it seems to_graphviz for diagrams was not previously being tested.

@epatters I've rebased this after #858. Before I request a review, I have a question. As part of this, I am trying to extend the graph method defined in FinCats to accept a Presentation and make a NamedGraph. This will help simplify the graphviz code, and its also nice for other non graphics related programming.
However, I cannot figure out why when I uncomment this line to import the method https://github.com/slwu89/Catlab.jl/blob/graphviz-diagram/src/graphs/NamedGraphs.jl#L14, Julia complains with the error ERROR: LoadError: UndefVarError: CategoricalAlgebra not defined. Do you have any idea how I can extend that method in the named graphs module?

The reason is that CategoricalAlgebra is loaded in Catlab after Graphs, i.e., CategoricalAlgebra depends on Graphs, not the other around. So any interoperability layer between the two should go in CategoricalAlgebra.
In fact, I think the function you are looking for is already available on main: https://github.com/slwu89/Catlab.jl/blob/54b8e25ef13a7e125f36e687f02c58b9f1646cd1/src/categorical_algebra/FinCats.jl#L113

Ah, thanks @epatters for clearing that up!
Yes I did see that graph method, but I think it only works for a FinCator a FinCat presented by an actual graph object. I was interested in implementing something that would work for a Presentation, like:
julia> graph(SchWeightedGraph)
ERROR: MethodError: no method matching graph(::Presentation{ThSchema, Symbol})

But I think that should wait for another PR and this one should just get those tests for visualizing a diagram in.

IIRC, you can just wrap the Presentation in a FinCat, i.e., call graph(FinCat(my_presentation)).


Downloading playlists: playlist folder name

Requested Feature
Need a way to tell spotdl to create a folder with the playlist we are trying to download.
For example in the config file:
"output": "E:\\Perfil\\Downloads\\{PLAYLIST_NAME}\\{artists} - {title}.{output-ext}",
should output for example:
"E:\Perfil\Downloads\my_playlist\some_artist - some_song_name.mp3"
Possible implementation
Add a new variable for playlist names.
If you want to download "Best songs" playlist, the script should be able to parse the playlist name into a {playlist_name} variable so we could tell the script to create the folder structure: "E:\Perfil\Downloads\Best songs\Artist - Song.mp3" using the config:
"output": "E:\\Perfil\\Downloads\\{PLAYLIST_NAME}\\{artists} - {title}.{output-ext}",

Please RTFD before posting - read the documentation.
https://spotdl.rtfd.io/
{list-name}

Suprise! I read it!!!
You can also view them in spotdl --help i believe.
https://spotdl.readthedocs.io/en/latest/usage/#output-variables


Chef related issue

I am trying to install the agent on the node machine by using knife command, but I am getting some issues.

try to run bootstrap in debug mode and try to share full logs and it can be
done by using -v -v -v in command line with your previous command
On Fri, Jul 12, 2019 at 1:13 AM sunnydevops<EMAIL_ADDRESS>wrote:

I am trying to install the agent on the node machine by using knife
command, but I am getting some issues.
[image: error]
https://user-images.githubusercontent.com/31772526/61080254-468db680-a442-11e9-96d1-d907051eef82.PNG
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/QT-DevOps/DevOpsIssues/issues/524?email_source=notifications&email_token=ALT4PAHYO2TAIN63NLO3LTTP66EPTA5CNFSM4IBSVM22YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G6W7CRQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALT4PACKW7RCZU3MJENYTCTP66EPTANCNFSM4IBSVM2Q
.

--
With Regards
Bhaskar Degala
+918142152155
<EMAIL_ADDRESS>

The issue has been solved, Thanks


beginning code of reading and converting protobuf graph to mpc graph

Here's some code that converts a protobuf tensorflow graph into code that just builds a plain tensorflow graph. The idea here to swap out the registered functions with functions that actual create mpc operations instead of plain tensorflow operations. Example coming soon. Just wanted to get a head start on receiving some feedback!

Yeah not sure how important those tests would be right now. I've started getting rid of the 1-to-1 mapping stuff and the final MPC graph will be wildly different from the input graph.

let me take a look later today!

Sounds good! Sorry it got so big 😦


Avoid infinity loop in MatchIterator with zero-width match

Hi, I found an issue with matches() that if the pattern matches an empty string, the next match will start from the same offset, ending up in an infinity loop.
In Perl, using a zero-width pattern with 'g' works as follows.
$ perl -e '$a = "12"; $a =~ s//x/g; print "$a\n"'
x1x2x
With this change, MatchIterator follows this behavior, so if the pattern matches an empty string, the next match will start from the next offset.

Hi, could you take a look?  Thanks!


Make docs clearer by dropping precompiled for compiled

Replaces #36861. This PR just aims to clarify some language without keeping the precompiled word around. The usage in that PR is more confusing and sometimes wrong IMO. Here I just changed it all to compiled, nested the headings for a more logical doc structure, and fixed a few other little issues.

Replaces #36861. This PR just aims to clarify some language without keeping the precompiled word around. The usage in that PR is more confusing and sometimes wrong IMO. Here I just changed it all to compiled, nested the headings for a more logical doc structure, and fixed a few other little issues.

Thank you for your work! I am the one who submitted the issue #36861.
I havn't used and don't understand much of Bootstrap. In fact, I just started to read its documentation.
Now I realized that I am wrong.

All good! Thanks for reporting regardless :).


fix is_enum

as per PyO3/pyo3#2905

Codecov Report

Merging #373 (6d554db) into main (0ce0f57) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

:exclamation: Current head 6d554db differs from pull request most recent head 4eda80f. Consider uploading reports for the commit 4eda80f to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #373      +/-   ##
==========================================
- Coverage   95.36%   95.35%   -0.01%
==========================================
  Files          90       90
  Lines       10131    10129       -2
  Branches        4        4
==========================================
- Hits         9661     9659       -2
  Misses        470      470

Impacted Files
Coverage Δ

src/serializers/ob_type.rs
86.79% <100.00%> (-0.17%)
:arrow_down:

Continue to review full report at Codecov.

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


Add line to readme about review environment guidance

Closing this as the review environment guidance has been moved to Confluence


[Bug] "Click to activate" popup not going away

Device
Desktop
Operating System
Windows
Browser
Chrome/Edge/Chromium
Browser Version
124.0.2478.80 (Microsoft Edge)
Better xCloud Version
4.2.0
Reproduction Steps
After the 4.2.0 update, the option "click f8 to enable/disable the keyboard" remains on the screen even after I enable or disable the keyboard, like no mather what I do it remains on my screen.

Did you try again by refreshing the page?
Did you test with older versions?

Did you try again by refreshing the page? Did you test with older versions?

Yes, I tried to close the browser and open it again, but the problem continues. Also, the previously version of better xcloud was running perfect.

Check this https://github.com/redphx/better-xcloud/raw/typescript/dist/better-xcloud.user.js

What is the status with 4.3.0?

What is the status with 4.3.0? Try other games than Fortnite as it's native MKB game, and emulated MKB won't show.

Yeah, the problem remains in the 4.3.0 update. I wish I could know if this is happening only with me.

Now, I think the problem is definitely my browser, because I made a downgrade for the 4.1.2 and 4.1.0 versions of better xcloud and the problem remains.

What is the status with 4.3.0? Try other games than Fortnite as it's native MKB game, and emulated MKB won't

What is the status with 4.3.0? Try other games than Fortnite as it's native MKB game, and emulated MKB won't show.

I FIXED IT. I just realized that I had two tampermonkeys installed, that was the problem. Appreciate your support!


When will Out-of-Core and cluster support?

Out-of-Core and cluster is very important to big data processing. I really want to know when will modin support this features well(not toy)?
Is there some plan?
Thanks a lot!

Hi @DonYum, you can track this PR: #2848. It will be available when Ray releases 1.3.0.

Hi @DonYum , out-of-core and cluster support should be supported now. Please see the following links:

https://modin.readthedocs.io/en/stable/getting_started/using_modin/using_modin_cluster.html
https://modin.readthedocs.io/en/latest/getting_started/why_modin/out_of_core.html


Constant foldable expression with assignment from literal of different type crashes Intel Mesa compiler

[Shaders, screenshots, error log, reproduction steps, platform info, etc.] [ZIP]
This crashes with:
glsl/ir_expression_operation_constant.h:228: virtual ir_constant* ir_expression::constant_expression_value(hash_table*): Assertion `!"invalid type"' failed

I can reproduce this with just glsl_compiler built from master, so I will report it upstream on that basis.

On 12/07/17 15:51, David R. MacIver wrote:

I can reproduce this with just |glsl_compiler| built from master, so I
will report it upstream on that basis.

Sounds good!
Thanks,
Hugues

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mc-imperial/shader-compiler-bugs/issues/78#issuecomment-314794178,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGakW0TEtRwR-zGt2Aznkl7TEIJfs_Gvks5sNN1bgaJpZM4OViUi.

I have now reported this upstream.

Fixed upstream as of early this morning.


Fix issue #1559: Error writing out logs for job on a retry attempt

Fix https://github.com/azkaban/azkaban/issues/1559.
After making attempt volatile, attempt++ had to be synchronized because of this check:
http://errorprone.info/bugpattern/NonAtomicVolatileUpdate

@HappyRay @chengren311 anyone to review?

Or maybe @kunkun-tang, @jamiesjc ?

@kunkun-tang, I've added two commits.


make some improvements on README.md

Please Review again
On Sat, 3 Oct 2020 at 02:27, satboy78<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/hariskhalil42/Wallet-App-Design-/pull/2
Commit Summary

make some improvements on README.md

File Changes

M README.md
https://github.com/hariskhalil42/Wallet-App-Design-/pull/2/files#diff-04c6e90faac2675aa89e2176d2eec7d8
(4)

Patch Links:

https://github.com/hariskhalil42/Wallet-App-Design-/pull/2.patch
https://github.com/hariskhalil42/Wallet-App-Design-/pull/2.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hariskhalil42/Wallet-App-Design-/pull/2, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANQBCNVRXAPWHUYSB3RAFSDSI3VBHANCNFSM4SCRKEIA
.

sure, done


Not highlighting CoffeeScript

See vuejs/Discussion#307 for description of issue.
I found out, that it's caused by this change. When reverting back this change (by manually editing that file), it works fine.

:+1: Also experiencing this issue.

Hmm, not sure why, but I'm also on Sublime 3 (build 3083) + BetterCoffeeScript, and it's highlighting it correctly for me =/

So I did a couple things that made CoffeeScript syntax highlighting work...
(I am also using ST3 build 3083 and Better CoffeeScript)

I used PackageResourceViewer to open the Vue Syntax Highlighting package
I modified the vue.tmLanguage file to read text.html.basic saved it.
(At this point the CoffeeScript highlights correctly)
I changed it back to text.html.vue and the code is still highlighting correctly
Restarted Sublime Text
Broken again.

Another approach I did was the following:

Uninstall Better CoffeeScript
Reinstall Better CoffeeScript
Still broken
Uninstall Vue Syntax Highlighting
Reinstall Vue Syntax Highlighting
Still broken

@taylorzane yeah i also used PackageResourceViewer to modify it. What OS are you using? I'm on Ubuntu 14.04 (64 bit).
@yyx990803 I looked at sublime docs, they say it should be text.<lang_name>, but I can't figure out where lang_name is coming from, couldn't find it in plugin files. Or is file extension just used as lang_name ?

@azamat-sharapov I'm on Mac OS X 10.10.4 (Yosemite)

Should be fixed now, this is actually caused by a problem with jade detection...(see #5)

Thanks man


Connecting to Packaging Server

After following the getting started guide I hit this error 'No Bundle URL Present':
Stack OF Link
I solved it by adding this to the Xcode target's Info.plist
<key>NSAppTransportSecurity</key>
	<dict>
		<key>NSAllowsLocalNetworking</key>
		<true/>
	</dict>

FYI - A react-native app created from the CLI includes this entry tin the Info.plist:
NSAppTransportSecurity

NSExceptionDomains

localhost

NSExceptionAllowsInsecureHTTPLoads


3.0.1 - Some types does not conform to ConstraintOffsetTarget

New Issue Checklist

[x] I have looked at the Documentation
[x] I have read the F.A.Q.
[x] I have filled out this issue template.

Issue Info

Info
Value

Platform
e.g. ios/osx/tvos

Platform Version
8.0

SnapKit Version
3.0.1

Integration Method
CocoaPods

Issue Description
I used to have some code that did
titleLabel.snp.makeConstraints() { make in
    make.top.left.right.equalTo(self).offset(UIEdgeInsets(top: self.padding, left: self.padding, bottom: 0, right: -self.padding))
}

But now I am getting an error because offset takes ConstraintOffsetTarget, which UIEdgeInsets and CGPoint no longer conform to.
It looks like the NSLayoutAttribute.snp_constantForValue function got migrated into ConstraintConstantTarget.constraintConstantTargetValueFor(layoutAttribute:), so I'm guessing it might not be too hard to add in?
I haven't looked too hard into the implementation, so if I'm missing something, let me know! I just noticed that this was no longer building after upgrading 😅

@cjwirth you're probably going to want to use equalTo(self).inset(UIEdgeInsets) and you no longer need to invert the right or bottom values as SnapKit does this by default.

you're probably going to want to use equalTo(self).inset(UIEdgeInsets)

aah, if this is all it was, then it's definitely my fault, sorry about that!

you no longer need to invert the right or bottom values as SnapKit does this by default.

Aah, so I don't have to do right: -self.padding, I can just do right: self.padding these days? Cool!

@cjwirth CGPoint was removed because it's ambiguous for things like make.top.bototm.equalTo(CGPoint) you have to use constants and separate them out now.

Oh I guess that makes sense. It appears to be working 👍


Check the @botname in /quota@botname

All bots reply to this command because of not checking @botname

Close by #27


when I try to install tensorflow from source by bazel, I got this new problem:

/home/scw4150/Documents/tensorflow/tensorflow/tensorflow/stream_executor/BUILD:5:1: C++ compilation of rule '//tensorflow/stream_executor:stream_executor' failed: crosstool_wrapper_driver_is_not_gcc failed: error executing command third_party/gpus/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -fPIE -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object ... (remaining 112 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
tensorflow/stream_executor/cuda/cuda_dnn.cc: In function 'cudnnConvolutionFwdAlgo_t perftools::gputools::cuda::{anonymous}::ToConvForwardAlgo(perftools::gputools::dnn::AlgorithmType)':
tensorflow/stream_executor/cuda/cuda_dnn.cc:266:10: error: 'CUDNN_CONVOLUTION_FWD_ALGO_FFT_TILING' was not declared in this scope
case CUDNN_CONVOLUTION_FWD_ALGO_FFT_TILING:
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/stream_executor/cuda/cuda_dnn.cc: In function 'cudnnConvolutionBwdDataAlgo_t perftools::gputools::cuda::{anonymous}::ToConvBackwardDataAlgo(perftools::gputools::dnn::AlgorithmType)':
tensorflow/stream_executor/cuda/cuda_dnn.cc:284:10: error: 'CUDNN_CONVOLUTION_BWD_DATA_ALGO_FFT_TILING' was not declared in this scope
case CUDNN_CONVOLUTION_BWD_DATA_ALGO_FFT_TILING:
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/stream_executor/cuda/cuda_dnn.cc: In member function 'virtual bool perftools::gputools::cuda::CudnnSupport::GetConvolveAlgorithms(std::vector*)':
tensorflow/stream_executor/cuda/cuda_dnn.cc:942:7: error: 'CUDNN_CONVOLUTION_FWD_ALGO_FFT_TILING' was not declared in this scope
CUDNN_CONVOLUTION_FWD_ALGO_FFT_TILING,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/stream_executor/cuda/cuda_dnn.cc:947:4: error: no matching function for call to 'std::vector::assign()'
});
any suggestions?

Which version of cuDNN and Cuda toolkit are you using? Gcc version? OS version?

@hholst80
cuDNN v4
Cuda toolkit 7.0
gcc version 6.1.0
CentOS Linux release 7.2.1511 (Core)

I would double check your cuda and cudnn install, I think you have older versions, despite what you think.  Maybe remove the existing cuda and cudnn versions and install them from scratch.
I would also recommend using:

cudnn v4, unless you have GTX1080, in which case use cudnn v5
cuda toolkit 7.5, unless you have GTX1080, in which case use cuda 8.0 RC

thanks,I will try to update cuda and cudnn version.

(I should clarify, you can use cudnn v5 regardless of what GPU you have).
I'm going to close this since I suspect this is a cuda problem, not a TF one (yet).


connection time out

Hi, when I run download_training.py, I always met : Connecting to airlab-share.andrew.cmu.edu (airlab-share.andrew.cmu.edu)|<IP_ADDRESS>|:8081... failed: Connection timed out.
Is there anything wrong with the server?

and I always meet this:
HTTP request sent, awaiting response... 302 Found
Location: https://airlab-share.andrew.cmu.edu:8081/tartanair/abandonedfactory/Easy/depth_left.zip [following]
--2023-09-24 23:45:24--  https://airlab-share.andrew.cmu.edu:8081/tartanair/abandonedfactory/Easy/depth_left.zip
Connecting to airlab-share.andrew.cmu.edu (airlab-share.andrew.cmu.edu)|<IP_ADDRESS>|:8081... failed: Connection timed out.


Support message name with a single alphabetic character, like 'X', 'Y', 'X1', 'Y1'

Is it possible to support these edge cases when validating message names?

Hi @djeube, Is this the same issue addressed by #23?

Hi @ckaznocha, indeed, it is fixed in the master branch, my bad!
I used the binary provided for the latest release.
Closing the issue.


Update extracted resources status on document delete

When applicable the system now links questionnaire response updates with the extracted resource content. This works well for amendments but has no effect when the response gets deleted.

Related to: #111


res.getHeader function does not exist

I'm wondering if this module is not up to date?
test.txt
/home/karl/dev/node/proto-buffer-api-karl/node_modules/lasso/node_modules/send/index.js:761
  if (!res.getHeader('Accept-Ranges')) res.setHeader('Accept-Ranges', 'bytes');
           ^

TypeError: res.getHeader is not a function
    at SendStream.setHeader (/home/karl/dev/node/proto-buffer-api-karl/node_modules/lasso/node_modules/send/index.js:761:12)
    at SendStream.send (/home/karl/dev/node/proto-buffer-api-karl/node_modules/lasso/node_modules/send/index.js:531:8)
    at onstat (/home/karl/dev/node/proto-buffer-api-karl/node_modules/lasso/node_modules/send/index.js:624:10)
    at FSReqWrap.oncomplete (fs.js:82:15)

Express uses the following to set headers: http://expressjs.com/en/4x/api.html
States: res.set('Content-Type', 'text/html');. Same goes for koajs.
Can't see any getHeader function either in expressjs nor koajs.

Express has .getHeaders, as it comes from Node.js. Can you provide the following information?

Version of Node.js you are using.
Version of this module you are using.
Complete code I can copy and paste and run to reproduce the issue.
Instructions for how I can reproduce the issue.

Thank you!

@dougwilson

Tried both v4.5.0 and v6.6.0
^0.13.0
3 & 4:

git clone git@github.com:basickarl/send-error.git
cd send-error
npm install
node index
in the browser visit http://<IP_ADDRESS>:3000/static/test.txt

It's a module called lasso https://github.com/lasso-js/lasso which I'm trying to use. Itself uses send for it's middleware.

I replaced res.getHeader(... with just res.get(... and it seemed to work. Got another error though.
Fair enough nodejs does have it: https://nodejs.org/api/http.html#http_response_getheader_name
Express v4.x doesn't seem to have it: http://expressjs.com/en/api.html#res
Neither does Koajs: http://koajs.com/

Ah, I see. The serveStatic export from lasso does not work with Koa, which is why you are getting that error. You need to file an issue to make serveStatic work with Koa on the lasso module.

Express v4.x doesn't seem to have it: http://expressjs.com/en/api.html#res

Not true; At the top of that section, it says:

The res object is an enhanced version of Node’s own response object and supports all built-in fields and methods.

And Node.js response object (linked to in those docs) has getHeader method.
Regardless, the issue is that you're not using lasso correctly, and the error that occurs in this module is just a symptom of that issue.

@dougwilson Ah. I failed to mention that I hav a pull request waiting for the lasso bug with koa: https://github.com/lasso-js/lasso/pull/163
So it does work (with my fix). The next issue if Send now, which is why I started this issue.

So what your saying is that send does not support koa?

No, I'm saying that lasso didn't. send works just fine with Koa as long as you are actually passing in the correct objects to send. They way you were using it was not doing that. The code you showed me, you were passing the Koa context object to his module where you should have been passing in a request object and then you were passing in the Koa next function to this module where you should have been passing in the response object.

@dougwilson Ok gotcha! Just wanted your view on the whole thing!

No problem, @basickarl I hope that all made sense :)


change status of thru

@cuongcl
Please update test. Even I created a test, if you don't run it, it does not make sense.


Prompt with versioning

Is your feature request related to a problem? Please describe.
When I created multiple assistant, I got a trouble with how to version for each prompt which I cannot control the change among versions. Naively, I can duplicate a prompt and re-configure it, but this is time-consuming.
Describe the solution you'd like
To address this issue, I used prompt management in Langfuse that supports me to version and control the changes through each version.
https://langfuse.com/docs/prompts/get-started
I request a new feature that can version the prompt like that.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@anhphong22 Thank you for your feedback. I agree that it's an efficient way to manage and reuse prompts. We'll aim to incorporate this feature in our product :-)


On pull request #400: copy some lines in Lua causes crash

On #400

There is a bug in the Lua panel: by trying to copy some lines in a Lua function ctrlr crashes.

For debug info:
https://github.com/RomanKubiak/ctrlr/files/7884163/dbg1_CopySomeLinesInLua.txt

This bug has been fixed according to  juce-framework/JUCE#999 . Thanks for reporting.
Let's wait until the change has found its official way into Ctrlr until we close this.

This is not an issue from #400 but #400 fixes it. @tomlem could you please change the title accordingly?


chore: release main

:robot: I have created a release beep boop
log-error: 1.3.5
1.3.5 (2022-09-22)
Bug Fixes

deps: bump @financial-times/n-logger from 10.2.0 to 10.3.0 (8f71181)

middleware-log-errors: 1.2.6
1.2.6 (2022-09-22)
Documentation Changes

clarify middleware mounting order (bc3bc5e)

Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/log-error bumped from ^1.3.4 to ^1.3.5

middleware-render-error-info: 1.1.4
1.1.4 (2022-09-22)
Documentation Changes

clarify middleware mounting order (bc3bc5e)

Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/log-error bumped from ^1.3.4 to ^1.3.5

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/log-error-v1.3.5 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/middleware-log-errors-v1.2.6 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/middleware-render-error-info-v1.1.4 :sunflower:


[Feature Request] Add telephone number formatter

Take a look at https://github.com/marmelroy/PhoneNumberKit. It looks promising.


Add Atomic Habit Book

Book Title?
[Atomic Habits]
Author?
[James Clear]
Genre of Book?
[Self-Help]

Hey @Harsh-00 ! Atomic Habits has already been added with PR #30. You can choose some other book, to see what books have already been added, please checkout fehrist.vercel.app


CircleCI : cache for maven

CircleCI uses cache by default.
But it seems that the cache is not used properly for maven.
CircleCI downloaded maven dependencies, although there is a cache in .m2
=> https://circleci.com/gh/pascalgrimaud/hello-jhipster/3

it's because the 'Save cache' part is done before mvn test
I won't be fixed now, as it's not so important


tests, integ: remove xfail on bridge multicast-snooping from 0 to 1

The bug has been fixed and it is not failing anymore. Therefore, the
xfail must be removed. Indeed, this seems it was failing only in 4.18.0
kernel.
Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1859244
Signed-off-by: Fernando Fernandez Mancera<EMAIL_ADDRESS>

@ffmancera Did you close this PR accidentally?


Two Checkboxes marked "Only" can both be checked at once

as the Administrator, when I click to Send Message to Volunteers, it shows me two checkboxes.  One marked "Cluster Coordinators only" and the other marked "Send to checked-in volunteers only".  It is unclear what happens if I check both boxes.  Is it Cluster Coordinators AND checked-in volunteers, or is it Cluster Coordinators OR checked-in volunteers?  I would recommend changing the labels to "Send to Cluster Coordinators" and "Send to Checked-in Volunteers".  Then if they check both, it is clear that the function is an AND, which would send the message to both.
Should I even be allowed to check both boxes at once?

I followed the code and the labels are more misleading than they look and more questions came up.  I'll attempt to simplify what the code is doing.  At the very least "Send to checked-in volunteers only" should change to "Send to checked-in only".
Checked: "Cluster Coordinators only"
Checked: "Send to checked-in volunteers only"
Results in email to coordinators committed to the disaster that are also checked in.
Checked: "Cluster Coordinators only"
Unchecked: "Send to checked-in volunteers only"
-Results in email to all coordinators committed to the disaster.
Unchecked: "Cluster Coordinators only"
Checked: "Send to checked-in volunteers only"
-Results in email to volunteers committed to the disaster that are also checked in.
Unchecked: "Cluster Coordinators only"
Unchecked: "Send to checked-in volunteers only"
-Results in email to all volunteers committed to the disaster.


Text inverts to white in the NEWS / TOPIC component when dark background is selected. So doesn't show as card is always white.

Remove dark background promotion from Sanity


wble-spawn: how to debug failure to MitM?

I was able to do ble-central -i hci0 -b <target bdaddr> profile mydevice.json to generate a JSON file that looks like it has correct data within it.
However, when I do the command mentioned for the ble-spawn documentation, wble-connect -i hci0 <target bdaddr>| ble-wireshark | wble-spawn -i hci1 -p mydevice.json I do not see a connectable instance of the original device.
Using Sniffle I can see that the first wble-connect is connecting to  just fine. But, if I use Sniffle and run only wble-spawn -i hci1 -p mydevice.json | wshark, I don't see any advertisements as either the bdaddr of hci1, or the original target bdaddr (I don't think you're trying to spoof the original bdaddr right?)
So what's the right way to debug the fact that the wble-spawn isn't advertising?

This specific tool chain connects to a target BLE device and then spawns a similar device based on the cached profile, and yes it should work as stated in the documentation. You can use the --log debug and --logfile options to enable debug messages for both wble-connect and wble-spawn (and save them in two separate files). This is what we use to debug such issues, but it is quite difficult to interpret when you are not familiar with the framework internals.
I guess the problem may be due to the use of ble-wireshark, which is some old tool we used when we started writing the doc. The expected toolchain is the following: wble-connect -i hci0 <target bdaddr>| shark | wble-spawn -i hci1 -p mydevice.json. But I guess you already tried it, as ble-wireshark should not exist anymore in WHAD.

I think I've managed to reproduce the problem you're facing, and figured out what's happening here. I still did not have time to test the exact same setup you mention in your previous comment (and jeez, thank you anyway to provide such details and procedure to reproduce this issue) but I guess I stumbled upon the same problem with a device of mine that sends PDUs right after a Central device connects to it.
The root cause was that once wble-connect connects to a target device, this device sends some PDUs (MTU exchange or even GATT requests in my case) that comes just before the second tool (chained with a pipe, say wble-spawn for instance) connects to the Unix server socket created by the first one. Problem is (or was) that wble-connect uses its own BLE stack to handle these PDUs while it should relay these to the second tool directly. I made some modifications to wble-connect and to WHAD's default connector class (whad.device.WhadDeviceConnector) to avoid this behavior and it seems to have greatly improved the stability of this Man-in-the-Middle attack.
I've tested it against the same device I own and I had no more issues while performing a MitM in both ways (wble-connect | wble-spawn and wble-spawn | wble-connect). Like I said, I've only tested it with some of my devices, I should find some time to flash a nRF52 with Zephyr and check that everything works fine with my fix.
However, I had some other issues when the target device disconnects as my ButteRFly dongle started sending BLE advertisements caught by my wireshark instance, polluting everything... Maybe some further improvements are needed in this specific case to handle it properly.
I also noted your point that the MitM chain displays nothing in the terminal, and that it could be very helpful when debugging what's going on with a MitM attack. For now, I'd be very happy if my fix solves your MitM issues. Will have a look at a more verbose output and graceful exiting later :smile:.

I took some time to test with Zephyr's peripheral_hr example and managed to reproduce the bug as well. I found out another bug in ble-spawn, it was supposed to put received packets in a temporary queue when no connection to the fake device is established but in fact it didn't. I suppose this missing feature has been left without a comment and we forgot to implement it.
I made some modifications to make it work, tried it with the Zephyr HR example peripheral and it worked well. Not sure how the other modifications I made previously impact this result, but things are it seems to work OK.
Modifications have been pushed into branch bugfix/issue-52, if you want to give it a try. I will also add some warnings in case a user tries to perform a MitM with two different devices, i.e. one that supports raw BLE packets while the other does not.

I've just added some code to display a warning message when ble-spawn is used in a configuration where BLE control PDUs may be lost due to the inability of one interface to send control PDUs (does not support raw BLE PDU sending/receiving). Code has been pushed into bugfix/issue-52.

This Zephyr example is getting more and more interesting :smiley: ! I managed to reproduce this issue with the advertising data sent by wble-spawn and identified its cause... Well, I might have forgotten to pass this information to the BLE peripheral class :roll_eyes: (in wble-spawn).  I've just pushed a fix into the bugfix/issue-52 branch to solve this.
The first bug you mention seems weird, could worth it to investigate it further (which device are you using to initiate a BLE connection ?). The third one looks normal to me, as HCI devices cannot be shared between WHAD and the Bluetooth service. WHAD takes full control of the HCI adapter while running, and control is given back to the Bluetooth service once the process is terminated. (This is quite annoying I agree, I did not count the numerous times I've disconnected my bluetooth headset while testing WHAD ...)

That's weird. I tried exactly the same using wble-spawn to create a spoofed device and used nRF Connect on my smartphone to have a look at the advertising data and they are exactly the same (I'm using the old example from Zephyr).

In the screenshot above, 11:22:33:44:55:77 is the Zephyr HR example running on  a dedicated nRF52 USB dongle while the 11:22:33:44:55:66 device is the one spawned with wble-spawn (using a CS4 USB dongle and a spoofed BD address).

Yes, I recently bought some hardware compatible with Sniffle with the idea to port Sniffle's firmware to WHAD :smile:. I get exactly the same result with Sniffle, as shown below:
Scan Results:
================================================================================
AdvA: 11:22:33:44:55:66 (Public) Avg/Min/Max RSSI: -31.0/-31/-31 Hits: 4

Advertisement:
Timestamp: 2.554643  Length: 39  RSSI: -31  Channel: 37  PHY: 1M  CRC: 0xC18AC8
Ad Type: ADV_IND
ChSel: 0 TxAdd: 0 RxAdd: 0 Ad Length: 37
AdvA: 11:22:33:44:55:66 (Public)
0x0000:  00 25 66 55 44 33 22 11  02 01 06 07 03 0d 18 0f  .%fUD3".........
0x0010:  18 0a 18 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
0x0020:  00 00 00 00 00 00 00                              .......

Scan Response:
Timestamp: 2.555495  Length: 33  RSSI: -31  Channel: 37  PHY: 1M  CRC: 0x30A051
Ad Type: SCAN_RSP
ChSel: 0 TxAdd: 0 RxAdd: 0 Ad Length: 31
AdvA: 11:22:33:44:55:66 (Public)
0x0000:  04 1f 66 55 44 33 22 11  18 09 5a 65 70 68 79 72  ..fUD3"...Zephyr
0x0010:  20 48 65 61 72 74 72 61  74 65 20 53 65 6e 73 6f   Heartrate Senso
0x0020:  72                                                r
================================================================================

================================================================================
AdvA: 11:22:33:44:55:77 (Public) Avg/Min/Max RSSI: -33.0/-33/-33 Hits: 57

Advertisement:
Timestamp: 3.022045  Length: 19  RSSI: -33  Channel: 37  PHY: 1M  CRC: 0xB14DA4
Ad Type: ADV_IND
ChSel: 1 TxAdd: 0 RxAdd: 0 Ad Length: 17
AdvA: 11:22:33:44:55:77 (Public)
0x0000:  20 11 77 55 44 33 22 11  02 01 06 07 03 0d 18 0f   .wUD3".........
0x0010:  18 0a 18                                          ...

Scan Response:
Timestamp: 3.022737  Length: 33  RSSI: -33  Channel: 37  PHY: 1M  CRC: 0x950A2F
Ad Type: SCAN_RSP
ChSel: 0 TxAdd: 0 RxAdd: 0 Ad Length: 31
AdvA: 11:22:33:44:55:77 (Public)
0x0000:  04 1f 77 55 44 33 22 11  18 09 5a 65 70 68 79 72  ..wUD3"...Zephyr
0x0010:  20 48 65 61 72 74 72 61  74 65 20 53 65 6e 73 6f   Heartrate Senso
0x0020:  72                                                r
================================================================================

The only difference I can notice is this weird data sent in ADV_IND (37 bytes ?) that has some null bytes padding, but SCAN_RSP is the same.

And when I use a nRF52 USB dongle, I get the exact same advertising data:
Scan Results:
================================================================================
AdvA: 11:22:33:44:55:66 (NRPA) Avg/Min/Max RSSI: -31.0/-31/-31 Hits: 67

Advertisement:
Timestamp: 2.062199  Length: 19  RSSI: -31  Channel: 37  PHY: 1M  CRC: 0x210FCF
Ad Type: ADV_IND
ChSel: 0 TxAdd: 1 RxAdd: 1 Ad Length: 17
AdvA: 11:22:33:44:55:66 (NRPA)
0x0000:  c0 11 66 55 44 33 22 11  02 01 06 07 03 0d 18 0f  ..fUD3".........
0x0010:  18 0a 18                                          ...

Scan Response:
Timestamp: 2.062883  Length: 33  RSSI: -31  Channel: 37  PHY: 1M  CRC: 0x60B82F
Ad Type: SCAN_RSP
ChSel: 0 TxAdd: 1 RxAdd: 1 Ad Length: 31
AdvA: 11:22:33:44:55:66 (NRPA)
0x0000:  c4 1f 66 55 44 33 22 11  18 09 5a 65 70 68 79 72  ..fUD3"...Zephyr
0x0010:  20 48 65 61 72 74 72 61  74 65 20 53 65 6e 73 6f   Heartrate Senso
0x0020:  72                                                r
================================================================================

================================================================================
AdvA: 11:22:33:44:55:77 (Public) Avg/Min/Max RSSI: -33.0/-33/-33 Hits: 37

Advertisement:
Timestamp: 2.054029  Length: 19  RSSI: -33  Channel: 37  PHY: 1M  CRC: 0xB14DA4
Ad Type: ADV_IND
ChSel: 1 TxAdd: 0 RxAdd: 0 Ad Length: 17
AdvA: 11:22:33:44:55:77 (Public)
0x0000:  20 11 77 55 44 33 22 11  02 01 06 07 03 0d 18 0f   .wUD3".........
0x0010:  18 0a 18                                          ...

Scan Response:
Timestamp: 2.054721  Length: 33  RSSI: -33  Channel: 37  PHY: 1M  CRC: 0x950A2F
Ad Type: SCAN_RSP
ChSel: 0 TxAdd: 0 RxAdd: 0 Ad Length: 31
AdvA: 11:22:33:44:55:77 (Public)
0x0000:  04 1f 77 55 44 33 22 11  18 09 5a 65 70 68 79 72  ..wUD3"...Zephyr
0x0010:  20 48 65 61 72 74 72 61  74 65 20 53 65 6e 73 6f   Heartrate Senso
0x0020:  72                                                r
================================================================================

We might have an issue with HCI adapters regarding advertising data. I'll dig into it.

I've just pushed some modifications into bugfix/issue-52 to fix the unexpected ADV_IND padding and it seems to work fine on my side.
Are you sure your JSON file holds the correct data (advertising data and scan response) ? Just to make sure, as you seem to use the correct commit. Can you share this file ? Here is what mine looks like:
{
  "services": [
    {
      "uuid": "1801",
      "type_uuid": "2800",
      "start_handle": 1,
      "end_handle": 8,
      "characteristics": [
        {
          "handle": 2,
          "uuid": "2803",
          "properties": 32,
          "security": 0,
          "value": {
            "handle": 3,
            "uuid": "2A05"
          },
          "descriptors": [
            {
              "handle": 4,
              "uuid": "2902"
            }
          ]
        },
        {
          "handle": 5,
          "uuid": "2803",
          "properties": 10,
          "security": 0,
          "value": {
            "handle": 6,
            "uuid": "2B29"
          },
          "descriptors": []
        },
        {
          "handle": 7,
          "uuid": "2803",
          "properties": 2,
          "security": 0,
          "value": {
            "handle": 8,
            "uuid": "2B2A"
          },
          "descriptors": []
        }
      ]
    },
    {
      "uuid": "1800",
      "type_uuid": "2800",
      "start_handle": 9,
      "end_handle": 15,
      "characteristics": [
        {
          "handle": 10,
          "uuid": "2803",
          "properties": 2,
          "security": 0,
          "value": {
            "handle": 11,
            "uuid": "2A00"
          },
          "descriptors": []
        },
        {
          "handle": 12,
          "uuid": "2803",
          "properties": 2,
          "security": 0,
          "value": {
            "handle": 13,
            "uuid": "2A01"
          },
          "descriptors": []
        },
        {
          "handle": 14,
          "uuid": "2803",
          "properties": 2,
          "security": 0,
          "value": {
            "handle": 15,
            "uuid": "2A04"
          },
          "descriptors": []
        }
      ]
    },
    {
      "uuid": "180F",
      "type_uuid": "2800",
      "start_handle": 16,
      "end_handle": 20,
      "characteristics": [
        {
          "handle": 17,
          "uuid": "2803",
          "properties": 18,
          "security": 0,
          "value": {
            "handle": 18,
            "uuid": "2A19"
          },
          "descriptors": [
            {
              "handle": 19,
              "uuid": "2902"
            }
          ]
        }
      ]
    },
    {
      "uuid": "180A",
      "type_uuid": "2800",
      "start_handle": 21,
      "end_handle": 25,
      "characteristics": [
        {
          "handle": 22,
          "uuid": "2803",
          "properties": 2,
          "security": 0,
          "value": {
            "handle": 23,
            "uuid": "2A24"
          },
          "descriptors": []
        },
        {
          "handle": 24,
          "uuid": "2803",
          "properties": 2,
          "security": 0,
          "value": {
            "handle": 25,
            "uuid": "2A29"
          },
          "descriptors": []
        }
      ]
    },
    {
      "uuid": "180D",
      "type_uuid": "2800",
      "start_handle": 26,
      "end_handle": 33,
      "characteristics": [
        {
          "handle": 27,
          "uuid": "2803",
          "properties": 16,
          "security": 0,
          "value": {
            "handle": 28,
            "uuid": "2A37"
          },
          "descriptors": [
            {
              "handle": 29,
              "uuid": "2902"
            }
          ]
        },
        {
          "handle": 30,
          "uuid": "2803",
          "properties": 2,
          "security": 0,
          "value": {
            "handle": 31,
            "uuid": "2A38"
          },
          "descriptors": []
        },
        {
          "handle": 32,
          "uuid": "2803",
          "properties": 8,
          "security": 0,
          "value": {
            "handle": 33,
            "uuid": "2A39"
          },
          "descriptors": []
        }
      ]
    }
  ],
  "devinfo": {
    "adv_data": "02010607030d180f180a18",
    "scan_rsp": "18095a6570687972204865617274726174652053656e736f72",
    "bd_addr": "11:22:33:44:55:77",
    "addr_type": 0
  }
}

This JSON is definitely valid, I've tested it with the latest version of wble-spawn and I saw the expected advertised values. I cannot reproduce this bug on my machine, advertising data and scan response look OK here. This is puzzling.

I always rely on an HCI adapter for the fake device because the nRF52 WHAD firmware sometimes fail with my BLE5-enable smartphone.
I've tested wble-spawn with the following command line:
$ wble-spawn -i hci0 -p zp_hr.json | wshark

I managed to get it working (advertising) with my CSR4 dongle, nRF52840 dongle running ButteRFly and my onboard Bluetooth HCI adapter. I didn't try to connect to it so far, just checking the advertised data was as expected.

Any update on this issue ? I would like to merge some bugfixes I've made in the dedicated issue branch (bugfix/issue-52) as they solve critical issues related to MitM that have been discovered while investigating this one.

Hi, I was able to reproduce the issue partially(?) - in terms of truncated advertisement in simulation. I used the same target Zephyr Heartrate Sensor working on nRF52, and 2x BLE USB CSR dongles connected to VM with current Kali Linux. In WHAD 1.2.3 and 1.2.4 MITM worked for me, just the simulated device had truncated advertisement data (containing only the type 0x01 - flags). But I was able to connect to this simulated device using nRF Connect Android, and all the packets were forwarded correctly to the Zephyr peripheral. Now in WHAD 1.2.5 the simulated device has proper advertisement data. MITM still works for me the same as before patches, so can't comment on this.

I see what's happening. You tried the following command:
wble-connect -i hci0 11:22:33:44:55:66 | wireshark | wble-spawn -i hci1 -p ZP_HR.json

But wireshark is not compatible with WHAD, you should use wshark which is a compatible wrapper for wireshark:
wble-connect -i hci0 11:22:33:44:55:66 | wshark | wble-spawn -i hci1 -p ZP_HR.json

I've got the same error with wble-spawn complaining about a missing connection handle value but it was in my lastest tests with wfilter (a fix is coming soon for this one).

I tried to reproduce the same setup using a nRF52840 running Zephyr HR firmware and the same commands you tried, and everything is working fine (wait, there's more below).

I am using an old USB Bluetooth CSR 4.0 adapter to connect to the Zephyr HR device (running on a nRF52840 dongle) and my laptop embedded Bluetooth adapter (supporting version 4.2) to create a fake device.  I am using my smartphone to connect to the fake device. This smartphone does support BLE 5 while both my adapters don't, so it falls back to version 4.x and avoids using all the new BLE 5.x features.
We may have an issue with recent USB Bluetooth dongles supporting Bluetooth version 5.x, as WHAD has definitely not been tested with these (and I am not even talking about our BLE stack that only supports v4.x at the moment :sweat_smile: ). I checked your Realtek dongle and it seems compatible with BLE 5.1 based on the information you shared in a previous comment.
I will order two of them pretty soon (it's almost Christmas and I may deserve some more hardware)  and we'll see in January if I can reproduce all the issues you have and fix them. Oh, and support of BLE 5.x will definitely be on the urgent things to fix in WHAD, it may become a top priority as more and more BLE 5 devices are used out there.


Reading coordinates (montage) from vhdr files

I have encountered an issue trying to read coordinate information (i.e., montage) from brainvision vhdr files (from the 'coordinates' field). For example, something like this
raw = mne.io.read_raw_brainvision('filename.vhdr', montage=True, eog=['EOG1', 'EOG2'])

results in ImportError: cannot import name '_sphere_to_cartesian' as this function does not seem to exist in mne.transforms. Another function, _sph_to_cart, does exist, however. The expected argument structure of this function differ slightly though.
One way to solve this issue might be to modify line 438 of mne.io.brainvision from
from ...transforms import _sphere_to_cartesian

to
from ...transforms import _sph_to_cart

and, consequently, also changing line 446 from
pos = _sphere_to_cartesian(r=radius, theta=theta, phi=phi)

to
pos = _sph_to_cart(np.atleast_2d([radius, theta, phi])).squeeze()

to conform with the expected structure of arguments of _sph_to_cart. This seems to solve the issue for me at least but I don't know what your preferred solution is, e.g., if you would rather modify _sph_to_cart.
I am using MNE 0.14.1.

please check if it's still broken in master
remove your current mne version with pip uninstall mne
then:
git clone git@github.com:mne-tools/mne-python.git
cd mne-python
pip install -e .
you should be able to modify the mne-python and send us PRs.
see also:
http://martinos.org/mne/dev/contributing.html

Fixed by  #4531


Memory leak in GB

After almost solving the issue #24, I encountered memory leak. After troubleshooting a bit, it seems the table leaks memory and am not sure if it is originating from the rust or the C side. Without making any modifications this can be reproduced by just downloading the repo and running any of the example. The leak can be triggered by performing multiline selects over and over again. The memory usage starts increasing by KBs initially and eventually starts increasing in MBs. Below is a snapshot of the "simple" example's memory usage

Hi
I think it’s the issue here. It should be fixed in latest fltk-rs, which isn’t released yet.

Thank you. I was not able to reproduce with the latest version. I will close the issue.


Updated TLS socket activation doc since Docker v1.10 supports this fe…

…ature
https://github.com/docker/docker/pull/17211
/cc @joshix @robszumski

@robszumski ping

LGTM.
@joshix thoughts?


Bugs in code-splitting example in react-router-dom/docs

Re packages/react-router-dom/docs/guides/code-splitting.md
1.) The render() method blows up with createElement getting a null type when entered before loading is complete.  This is a repeat of https://github.com/ReactTraining/react-router/issues/4998, which was blown off.
Change
render() {
    return this.props.children(this.state.mod)
  }

to
render() {
   return this.state.mod ? this.props.children(this.state.mod) : null
 }

2.) The bundle shims drop the RouteComponentProps (match, location, history) that often are needed by the routed-to component.  This should be noted, with an example that passes them through, e.g. change
const Dashboard = () => (
  <Bundle load={loadDashboard}>
    {(Dashboard) => <Dashboard/>}
  </Bundle>
)

to
const Dashboard = (props) => (
  <Bundle load={loadDashboard}>
    {(Dashboard) => <Dashboard {...props}/>}
  </Bundle>
)

3.) The code also assumes that the routed-to component is the default export of the split module.  It would be good to say that somewhere, or still better, show an example where it isn't.

Could you package this up as a PR? That will let us discuss the specific changes more directly. Thanks!

Sorry, no, too stretched!

Just go here and click the Edit icon in the top right corner of the file: https://github.com/ReactTraining/react-router/blob/master/packages/react-router-dom/docs/guides/code-splitting.md


nixos/nix-channnel: fix setting up the default channel again

Description of changes
Fixes the issue that I tried to fix in https://github.com/NixOS/nixpkgs/pull/264608
The previous solution was not entirely correct because it appends the default channel on each boot/switch.
Hopefully this time the behaviour is completely correctly.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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.11 Release Notes (or backporting 23.05 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

[x] Fits CONTRIBUTING.md.

@ofborg test activation-nix-channel

https://github.com/ofborg test activation-nix-channel

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/gibberish-nix-channel-being-added-to-my-list-preventing-update/34886/5


[Keyboard navigation - ADF - Azure data factory] Keyboard focus is not visible on Azure data factory control at left panel.

User Experience:
User will find difficulty to see any control if keyboard focus is not visible on any interactive control as they won't be able to take an action on such control and also they will surely miss the functionality and will proceed further.
Test Environment:
Application Version: 1.16.0-dev
Build Number: 20200921.1
Note: User credentials should NOT be included in the bug.
Pre-Requisite:
Navigate to the storage expoler.exe and select it.
Repro Steps:

Launch Azure Storage Explorer app.
Navigate to visual icon Add data factory control at left panel.
Verify focus visibility on visual icon Add data factory control.

Actual Result:
Keyboard focus is not visible on Azure data factory control at left panel and due to this, visual impaired user would difficulty to see the focus visibility on that control and also he/she won't be perform functionality due to no visibility.
Expected Result:
Keyboard focus should be visible on Azure data factory control at left panel so that visual impaired user could easily see the keyboard focus on that control to proceed further.
MAS2.4.7_Azure Data factory.zip

There is a blue indicator when it is in focus state.

Is it acceptable?

This is how VS Code shows the focus except they use a white bar instead of a blue bar.


Internal server error when importing an API Project due to validateKeyManagers function

Description:
When importing an API Project that was created using "apictl init" command, an error occurs from APIM as below.

Steps to reproduce:

Create an API Project using APICTL using the command below.

apictl init Petstore --oas https://petstore.swagger.io/v2/swagger.json

Try to import it to an environment using the command below.

apictl import-api -f <path-to-api-project>/Petstore -e <env-name>

Then you will receive an internal server error.

Affected Product Version:
API Manager 3.2.0-m1 (Tested with APICTL 3.1.2)
Environment details (with versions):

OS: Ubuntu 18.04.4 LTS

"keyManagers" : ["all"],


Obsolete unused NUnit3 arguments

Closes #1651, NUnit3 removed the verbose and full attributes.
I just added the Obsolete attributes to them.

@akamud,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Done and rebased on new changes on develop

Can't see why the OSX build failed.

@akamud  nuget issue, I've restarted the build.

@akamud your changes have been merged, thanks for your contribution 👍


Make allowDelete optional

As I user I would like to have the option to block allowDelete via a config file setting.
In addition it might be an idea to allow/forbid deletion via an environment variable

Is it deletion of topics you think is the main problem? I would like to have a split into allowDeleteTopics and allowDeleteAcls, ref #96

I support #96 as I think it is a good idea as well.
However more generally speaking I really mean that for ANY deletion it should be possibly to block it.

I agree with you two, what is a nice feature of the lightbend config library is that you can override configuration properties from the environment.
I think we can implement this by having detailed config variables:

allow.delete.topics
allow.delete.bindings

and others, I am thinking to keep the CLI options as primary option for now.
The question is what to do with the CLI options in 2.0, remove them ?

Yes indeed, introducing lightbend was a very nice thing!
Regarding this issue I agree that ability to override the two detailed configs with env variables should be enough.
However if you want to make your Kafka cluster really secure (which I think everyone should :-) ) I think the most important measures is how you set up the initial permissions at provisioning of the Kafka cluster. In case KTB should not do topic deletes the GitOps process should not have the topic DELETE ACL operation. Unfortunately I do not think Kafka ACLs provide av way to enable create ACLs and not allow delete ACLs. since these operations are both given by the cluster ALTER acl operation.

Not sure if I understand your comment regarding 2.0 CLI options correct @purbon. :-)
But I think the CLI options should be kept, env variables should only be for overrides. The --allowDelete option should however be removed in 2.0 I think, will only be confusing once the two more detailed is introduced.

Agree to on that. Introducing env overwrites for 2 config values and removing the CLI flag sounds legit to me

Hi @akselh,

However if you want to make your Kafka cluster really secure (which I think everyone should :-) ) I think the most important measures is how you set up the initial permissions at provisioning of the Kafka cluster. In case KTB should not do topic deletes the GitOps process should not have the topic DELETE ACL operation. Relying on this alone is however not the best, since KTB will fail badly if a topic is removed in the topology.

I am confused, from the tool perspective the option to enable/disable deletion selectively I agree is powerful. However I am confused with:

Relying on this alone is however not the best, since KTB will fail badly if a topic is removed in the topology.

can you elaborate a bit more?

Then we have a plan.
Thanks you @Fobhep and @akselh for your comments.

Just as a thought

KTB will fail badly if a topic is removed in the topology.

if the topic is removed, no ACLs are created.
I wonder, where do you see this fail badly? can you help me understand?

Just as a thought

KTB will fail badly if a topic is removed in the topology.

if the topic is removed, no ACLs are created.
I wonder, where do you see this fail badly? can you help me understand?

If the Kafka user for KTB does not have the delete topic ACL permission then KTB will crash with an exception on applying topology changes where a topic is removed. Then some of the changes in the topology will have been applied to the cluster (i.e. new topics and sync topic) and some will not (changed bindings). However, adding the topic to the topology again and doing a re-run will fix the issue.

So not a big problem with KTB really, but with --allowTopicDelete option this will be handled properly.

related to #96 , thanks @akselh for bringing this up.


Some relation instances don't have support evidence label?

I found that some relation instances in train_annotated.json don't have support evidence label.
Here shows an example:
{
	"vertexSet": [[{"name": "John Samuel Bourque", "pos": [0, 3], ...
	"labels": [
		{"r": "P569", "h": 0, "t": 1, "evidence": [0]},
		{"r": "P570", "h": 0, "t": 2, "evidence": [0]},
		{"r": "P607", "h": 0, "t": 10, "evidence": [2]},
		{"r": "P19", "h": 0, "t": 6, "evidence": [2]},
		{"r": "P69", "h": 0, "t": 8, "evidence": [2]},
		{"r": "P1001", "h": 5, "t": 3, "evidence": []},
		{"r": "P131", "h": 5, "t": 3, "evidence": []},
		{"r": "P131", "h": 12, "t": 6, "evidence": []},
		{"r": "P159", "h": 12, "t": 6, "evidence": []},
		{"r": "P159", "h": 20, "t": 3, "evidence": []}],
	"title": "John Samuel Bourque",
	"sents": [["John", "Samuel", "Bourque", ... ]]
}

Yes, some relation can be inferred with common sense or literal meaning

I see it. Thanks.


Add support for ABFS OAuth 2 authentication

Reposting https://github.com/prestosql/presto/pull/5052 to have Azure tests run.

Can we get documentation changes with this PR?

Updated to current tip of https://github.com/prestosql/presto/pull/5052/commits (a67170d6070203f2186f4ae7c246fcd4712b6ab9) rebased against current master.


Remove unused NewConsumer function

Proposed Changes

Remove unused NewConsumer function

/ok-to-test

/lgtm

The coverage in client.go is ok to be below 50%. https://github.com/knative/eventing-contrib/pull/1246#issuecomment-631425586

/approve


Can't read String

If i try to read string value i got error: Unrecognized Type Passed Read from Controller: 208
My code is:
const stringStructure = new Structure('A_AUTOMATIC.RunRecipeName', tagList);
try {
    await PLC.readTag(stringStructure);
    console.log(stringStructure.value);
} catch(e) {
    console.log(e);
}

What is A_AUTOMATIC ? Is it a UDT or a Program?
What type of Controller are you reading from?

I believe I fixed that on latest commit.

Latest commit is better - but I tested a bit more this time:

[ ]  new Structure('A_AUTOMATIC', tagList); returns RunRecipeName:{LEN: 17, DATA: Array(82)}

[ ] new Tag('A_AUTOMATIC.RunRecipeName', null, EthernetIP.CIP.DataTypes.Types.STRING); returns Buffer(88)

[x] new Structure('A_AUTOMATIC.RunRecipeName', tagList); returns This is my recipe

I'll fiddle with this a bit more today.

Submit PR #9 .  Resolved the string within a structure (item 1 above).
I had the 'Tag' read working also, but decided to abandon those changes because it's difficult to correctly support a write without the template.
I also resolved a similar issue with string writes.

Latest commit made it easier to work with structures (See Code Example) and includes PR #9
const { Controller, Tag, TagList, Structure } = require("st-ethernet-ip");

const PLC = new Controller();

PLC.connect("<IP_ADDRESS>", 0).then(async () => {

    const tagList = new TagList();
    await PLC.getControllerTagList(tagList);

    //Setup 'Structure1' Tag
    const structure1 = new Structure('Structure1', tagList, {Optional Program Name});

    //Read value from PLC
    await PLC.readTag(structure1);

    //Display entire structure
    console.log(structure1.value);

    //Change value of structure member 'Integer1'
    structure1.value.Integer1 = 3;

    //Write Changes to PLC
    await PLC.writeTag(stringStructure)

});

Oh I like that change.   Certainly addresses a not-so-obvious behavior of the prior value setter.  Thanks!

Couldn't sleep.  Fixed structure issue with scanning function.  Additional bug fixes.  PR #10


Transform Photography

Feature
As A user I want to have the object to rotate and transform the image
Reason
The photography can be rotated or taken in a wrong angle. To have a good reference picture, I have to have an option to fix this
Criteria

[x] rotate image

Unnecessary feature, as this is handled by the Homography Matrix


duplicated tree-sitter parsers in runtimepath

I’m not sure if here is right place for this issue, sorry if I’m wrong.
I’ve installed tree-sitter parsers via :Rocks install tree-sitter-javscript, and because I’m using aarch64 machine which NURR doesn’t support yet, luarocks tried to build parser locally. Installation is fine but now I can see three duplicated parsers from runtimepath.
vim.treesitter: require("vim.treesitter.health").check()

- Nvim runtime ABI version: 14
- OK Parser: rust                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/site/pack/luarocks/opt/tree-sitter-rust/parser/rust.so
- OK Parser: javascript           ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/site/pack/luarocks/opt/tree-sitter-javascript/parser/javascript.so
- OK Parser: http                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/site/pack/luarocks/opt/tree-sitter-http/parser/http.so
- OK Parser: html                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/site/pack/luarocks/opt/tree-sitter-html/parser/html.so
- OK Parser: css                  ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/site/pack/luarocks/opt/tree-sitter-css/parser/css.so
- OK Parser: toml                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/site/pack/luarocks/opt/tree-sitter-toml/parser/toml.so
- OK Parser: bash                 ABI: 14, path: /usr/local/lib/nvim/parser/bash.so
- OK Parser: c                    ABI: 14, path: /usr/local/lib/nvim/parser/c.so
- OK Parser: lua                  ABI: 14, path: /usr/local/lib/nvim/parser/lua.so
- OK Parser: markdown             ABI: 14, path: /usr/local/lib/nvim/parser/markdown.so
- OK Parser: markdown_inline      ABI: 14, path: /usr/local/lib/nvim/parser/markdown_inline.so
- OK Parser: python               ABI: 14, path: /usr/local/lib/nvim/parser/python.so
- OK Parser: query                ABI: 14, path: /usr/local/lib/nvim/parser/query.so
- OK Parser: vim                  ABI: 14, path: /usr/local/lib/nvim/parser/vim.so
- OK Parser: vimdoc               ABI: 14, path: /usr/local/lib/nvim/parser/vimdoc.so
- OK Parser: css                  ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/lib/luarocks/rocks-5.1/tree-sitter-css/scm-1/parser/css.so
- OK Parser: html                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/lib/luarocks/rocks-5.1/tree-sitter-html/scm-1/parser/html.so
- OK Parser: http                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/lib/luarocks/rocks-5.1/tree-sitter-http/scm-1/parser/http.so
- OK Parser: javascript           ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/lib/luarocks/rocks-5.1/tree-sitter-javascript/scm-1/parser/javascript.so
- OK Parser: rust                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/lib/luarocks/rocks-5.1/tree-sitter-rust/scm-1/parser/rust.so
- OK Parser: toml                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/lib/luarocks/rocks-5.1/tree-sitter-toml/scm-1/parser/toml.so
- OK Parser: css                  ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/rocks_rtp/parser/css.so
- OK Parser: html                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/rocks_rtp/parser/html.so
- OK Parser: http                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/rocks_rtp/parser/http.so
- OK Parser: javascript           ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/rocks_rtp/parser/javascript.so
- OK Parser: rust                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/rocks_rtp/parser/rust.so
- OK Parser: toml                 ABI: 14, path: /home/ubuntu/.local/share/nvim_rocks/rocks/rocks_rtp/parser/toml.so

I even get duplicated captures from tree-sitter attached buffer.
Can we prevent luarocks doing this?

Hey 👋
I'll leave to look into this. It's mostly related to symlinks that rocks.nvim creates.

I even get duplicated captures from tree-sitter attached buffer.

This is strange. I thought Neovim just uses the first parser it finds on the rtp. Does this cause any issues besides Inspect?
Maybe this is deliberate behaviour of the command, but I very much doubt that Neovim uses multiple parsers for highlighting.
Moving this to rocks.nvim


NodeJS support (http proxy)

Add support for NodeJS.
Possibility to connect an HTTP proxy for each account
Run:
node <access_token>
Or with proxy:
node <access_token> <proxy_url>

There's already a nodejs version by @south-paw


On boarding screen required

We need an onboarding screen with the following content:
https://bithyve-workspace.slack.com/archives/C02P2JWALJZ/p1705336226475589

https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/758ff4e0-572d-48f6-821e-29a4b9937255/

Verified this issue on keeper app v 1.2.0(319)


feat(jars): destination jar selector on receive screen

Closes #328.
Not changed / Differences to Figma screen:

Balance is shown directly beneath jars (using the SelectableJar component)
No simple/advanced view toggle on top of page:

Jars are displayed in the "Advanced dropdown" section
Q: This is still shown in "advanced mode" only (Must be enabled on the Settings page).. Refrained from always showing it since this might encourage directly funding other jars: Okay for now?

📸

Oh but one thing: Let's not hide it behind the developer mode. The "Advanced" mode on screen is enough. Whether that'll be a per-screen setting or a collapsible thing like we have now remains to be seen but hiding it behind the soon to be gone developer mode is too much imo.

My view on this is: If a user wants to do that they're gonna do it. We shouldn't encourage it by making this a default option or any other way that could make it easy to do it without knowing. But if it's a setting that's hidden behind an "Advanced" mode, that's perfectly fine imo.

Sounds reasonable. Done!
However, do you think it is a good idea to mention it somewhere, e.g. tooltip on a small info icon or something?


Create helloworldujjwal.js

What the program do ?
----Prints Hello World
In what programming language it is written?
Javascript

Thank you for partipating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Not so fast

Hi,
I ran your code on a single GPU, which is NVIDIA GeForce GTX 1080Ti, but training 24 epochs took me nearly 4 minutes.
I did not change anything in your code except two paths.
Is that we have to configure something before we run your model ?
Thank you.

A V100 vs the 1080ti will make a big difference I believe, because of the half precision stuff

The GPU makes a huge difference. For example, the 1080 Ti actually has worse GFLOPS with half precision compared to single precision (177 vs 10,339 GFLOPS). I think the reasoning was that NVIDIA would still be able to sell data center GPUs.


Generate AST types from tree-sitter node-types.json

TODO:

[x] struct types for nodes
[x] enum types for supertypes
[ ] accessor impls for nodes

Unfortunately tree-sitter's error recovery is not suitable for a parser to be used in a language server. Superseeded by #7


Added test to make sure SSL redirects work as intended when hosted on subdirectory. (#7467)

forceAdminSSL only impacts on the admin route, that is /ghost/, or if you're using a subdirectory of blog, /blog/ghost/.
The relevant test for this is already shown here: https://github.com/TryGhost/Ghost/pull/7588/files#diff-4ce595623abec9034815244c4179da0aR121
But note, you're looking at the master branch, which contains Ghost v1.0 alpha. Perhaps this would all make more sense if you tried to reproduce your original issue on the lts branch?

@SeanHayes it seems to me you should probably be chatting to us in the #dev channel of slack 😉

Sorry, should be fixed now. It's been a few weeks and I forgot exactly what it was I was testing.

Maybe you could enlighten me? The test doesn't make much sense other than as proof that if you don't setup nginx properly, you'll get an endless redirect problem?
As I said previously, I think if you're encountering a real problem, it's possibly with the code on the lts branch, and that's where it might be interesting to see if there's something missing?

This is a regression test that verifies that this has been fixed: https://github.com/TryGhost/Ghost/issues/7467#issuecomment-254297799
When you have a blog hosted on https://www.example.com/blog, when requesting http://www.example.com/blog Ghost used to redirect to https://www.example.com/. This was because req.url was used but has been fixed to use req.originalUrl.

Facing the same issue here with ghost 0.11.3/stable, with this config:
config: {
  production: {
    url: 'HTTPS://example.com/blog'
  }
}

The blog is hosted on https://example.com/blog,
And example.com is running behind nginx and served only with https.
When requesting https://example.com/blog ghost redirects to https://www.example.com website, so blog was not accessible.
Temporary Fix:
Change the config url to HTTP://example.com/blog, and ghost will start work in this case.
The issue now though is that all the links are rendered with http now and not with https instead, eventhough in the end it is served with https.
Hope this helps!

As far as I am able to determine, this test is a duplicate on the master branch, and shows that a bug that exists on the lts branch does not exist on the master branch.
What we really need is a PR that fixes the issue on the lts branch. Therefore I'm going to close this for now. The issue is still open against the lts branch: #7467.


Add registerColumnsProcessor to API

I also introduced the priority for the processor.
Followed the same style as registerRowsProcessor(...) method
Related to #3251

Seems to have failed a number of unit tests.....

sorry, I took a shot in the dark there. I cant seem to run the tests locally for some reason.
I get this:

I'll looking to fix this.

Probably that's the e2e tests.  You can run with:
grunt dev --no-e2e --angular=1.3.0
which works in most instances.

There seems to be an issue, I think with #3211. 3 Specs fail after that build.

OK, that PR was passing all the tests when I merged it.  I can take a look though.

I've fixed those tests in master - you can potentially merge master down again, and then squash the commits and we're good to merge.


I want to run the site

I want to run the site but I am getting various errors, please help me on Discord.

hey there, can you share what error you're getting exactly?

3:53:18 PM: build-image version: fcb0c1b3ada6d25c1cb58e8bc514f5f23cc14f15 (focal)
3:53:18 PM: buildbot version: ecff8a8ea00a7123ac3111778469ca25529769de
3:53:18 PM: Fetching cached dependencies
3:53:18 PM: Failed to fetch cache, continuing with build
3:53:18 PM: Starting to prepare the repo for build
3:53:18 PM: No cached dependencies found. Cloning fresh repo
3:53:18 PM: git clone --filter=blob:none https://github.com/NextJSTemplates/startup-nextjs
3:53:19 PM: Preparing Git Reference refs/heads/main
3:53:21 PM: Starting to install dependencies
3:53:21 PM: Python version set to 3.8
3:53:21 PM: Attempting Ruby version 2.7.2, read from environment
3:53:22 PM: Using Ruby version 2.7.2
3:53:22 PM: Started restoring cached go cache
3:53:22 PM: Finished restoring cached go cache
3:53:22 PM: go version go1.19.13 linux/amd64
3:53:22 PM: Using PHP version 8.0
3:53:23 PM: v18.19.0 is already installed.
3:53:24 PM: Now using node v18.19.0 (npm v10.2.3)
3:53:24 PM: Enabling Node.js Corepack
3:53:24 PM: Started restoring cached build plugins
3:53:24 PM: Finished restoring cached build plugins
3:53:24 PM: Started restoring cached corepack dependencies
3:53:24 PM: Finished restoring cached corepack dependencies
3:53:24 PM: Installing npm packages using pnpm version 8.14.1
3:53:25 PM: Failed during stage "Install dependencies": dependency_installation script returned non-zero exit code: 1
3:53:25 PM:  ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with package.json
3:53:25 PM: Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"
3:53:25 PM:     Failure reason:
3:53:25 PM:     specifiers in the lockfile ({"@next/font":"13.1.6","eslint":"8.33.0","eslint-config-next":"13.1.6","next":"13.1.6","next-themes":"^0.2.1","react":"18.2.0","react-dom":"18.2.0","react-modal-video":"^2.0.0","@types/node":"^18.15.11","@types/react":"^18.0.34","autoprefixer":"^10.4.13","postcss":"^8.4.21","prettier":"^2.8.3","prettier-plugin-tailwindcss":"^0.2.2","tailwindcss":"^3.2.4","typescript":"^5.0.4"}) don"t match specs in package.json ({"@types/node":"^20.8.9","@types/react":"^18.2.33","autoprefixer":"^10.4.16","postcss":"^8.4.31","prettier":"^3.0.3","prettier-plugin-tailwindcss":"^0.5.6","tailwindcss":"^3.3.5","typescript":"^5.2.2","eslint":"8.33.0","eslint-config-next":"13.1.6","next":"^13.5.6","next-themes":"^0.2.1","react":"^18.2.0","react-dom":"^18.2.0","react-modal-video":"^2.0.0"})
Error during pnpm install
3:53:25 PM: Failing build: Failed to install dependencies
3:53:25 PM: Finished processing build request in 7.356s
I get this error when running the site on Netlify.

Netlify doesnt support many features of Next.js, Try Static Exports option if you would like to deploy on netlify or deploy on vercel


Port conflicts are not considered when global flags are set.

Server version - V0.25.0-rc2
Steps to reproduce the problem:
Have 2 hosts with label say "name1=value1"
Add a global service with no scheduling which has port mapping , in my case 8080->80.
Start service.
1container gets deployed in each of the host.
Add another global service with no scheduling which has port mapping , in my case 8080->80.
Start service.
1 container gets deployed in each of the host even though port 8080 on the host is already being used by other containers.
Add another global service with scheduling set to "host must have label name1=value1" which has port mapping , in my case 8080->80.
Start service.
1 container gets deployed in each of the host even though port 8080 on the host is already being used by other containers.
Should we expect containers to not be deployed for global services when there is a port conflict?
-A CATTLE_PREROUTING -p tcp -m addrtype --dst-type LOCAL -m tcp --dport 8080 -j DNAT --to-destination <IP_ADDRESS>:80
-A CATTLE_PREROUTING -p tcp -m addrtype --dst-type LOCAL -m tcp --dport 8080 -j DNAT --to-destination <IP_ADDRESS>:80
-A CATTLE_PREROUTING -p tcp -m addrtype --dst-type LOCAL -m tcp --dport 8080 -j DNAT --to-destination <IP_ADDRESS>:80

This same issue is seen with LB services.
We are allowed to activate multiple LB services with same source port with global scheduling.
This results in multiple LB agent with the same ports being configured on the same host.
Only one LB service is functional.
We should be able to prevent launching LB Agents on hosts where there is a port conflict.

+1
This bit me the other day.. Not too hard, but still ;)


Kulatak restaurant won't load

Obedar doesn't load menu for Kulatak restaurant. It look like they have changed their website, so it might be necessary to rewrite the parser for Kulatak.

Are you willing to do it? I am not sure if anyone wants it anymore.

OK, I'll start working on this issue as soon as possible.


Write function specifications and documentation

(From Milestone 1 Instructions)

Write function specifications and documentation
For this milestone you will write function documentation that will serve as specifications, but you will NOT write any code for your package functions. Specifically:

Set-up empty functions (with appropriate function names) containing no code in the files where you will eventually write code.
Write function documentation (e.g., complete docstrings). These are the functions you wrote about in your proposal.

Work Distribution

To be discussed during group meeting
1 person per function

Function brainstorm ideas

Document matcher between job description and resume
Words related to data science
Sentiment analysis
Data cleaning
Resume filter for keywords (from the job provider point of view)
Word to text
wordcloud maker

Taking up the 3rd function for Document matcher to get the metrics

For this week, I can do the first function on document reading and write the README file - will probably write the README soon, and edit the README to include more specific input/output information when everyone is done with the documentation.
For future weeks, since the reading function is probably going to be too easy, I will help out where needed, probably with the metrics/visualisation stuff, especially since we are looking at including more than 1 metric/visualisation method!


infrastructure: Setup bors

Try to setup bors according to: https://github.com/bors-ng/bors-ng
Signed-off-by: Till Maas<EMAIL_ADDRESS>

This will hopefully allow a bot to rebase/merge PRs after we reviewed them. It will only merge the PRs if the configured automated checks pass. But I am not sure if everything is setup to trigger these checks for bors...

A robot cannot merge, only a maintainer should. By merging a maintainer publicly accepts the change and is willing to support it.
A review ack is not enough, the responsibility of pressing 'rebase/merge' exist.


Helm Chart - secretEnv broken

Hello, I found an issue with the secretEnv today after upgrading to latest version. @xet7
https://github.com/wekan/charts/commit/5dfb6b717bf76847ee9b7199507fd4508b11d7d2#diff-297fc75fd4942cbe9e1736dd8b8f814dffe2f59687bebfe92ac1dcf8dc5a4b92L8
The change itself seems fine, but I guess the indentation was lost in the process.
before it was:
data:
  {{- range $key := .Values.secretEnv }}

now it is;
data:
{{ $key.name }}: {{ $key.value | b64enc }}

if I place values now into secretEnv, they will be added to the secret like:
data:
OAUTH2_SECRET:

with missing indentation and therefore breaking the secret
Helm upgrade failed: error validating "": error validating data: ValidationError(Secret): unknown field "OAUTH2_SECRET" in io.k8s.api.core.v1.Secret
I think i have to open a PR to fix it

Fixed at already released Helm Chart 1.2.7:

PR https://github.com/wekan/charts/pull/18
Helm Chart 1.2.7 release https://github.com/wekan/charts/commit/1d8f1bca7265f5f49ca658389214104f518ff04a
WeKan ChangeLog https://github.com/wekan/wekan/commit/e1984831bd619b0f8c3c0ce71f7f35ba0018fe6b
WeKan Helm Chart https://artifacthub.io/packages/helm/wekan/wekan

ArtifactHub page will update usually within 30mins after release, so it will be visible in near future.

Looks good, works for me :)

it would be cool to extend this to include existing secrets as env vars. or is there another way to do this?

@szechp
I don't know does someone understand what to change, why, where, and send PR this way:
https://github.com/wekan/wekan/wiki/Emoji

it would be cool to extend this to include existing secrets as env vars. or is there another way to do this?

what exactly is your idea?

i have figured it now, i now it already does secret retrieval the way i described it. a problem i have with this right now is this hybrid approach, where if you give a name and a key it generates said secret. but if you leave it blank and the secret already exists it gets somehow stitched together. i mean it works, its just not very intuitive. take a look at how its done in grafana: see here: https://github.com/grafana/helm-charts/blob/main/charts/grafana/values.yaml#L452
they have a separate one for getting secrets as env vars:
## The name of a secret in the same kubernetes namespace which contain values to be added to the environment
## This can be useful for auth tokens, etc. Value is templated.
envFromSecret: ""

and also for multiple secrets:
## The names of secrets in the same kubernetes namespace which contain values to be added to the environment
## Each entry should contain a name key, and can optionally specify whether the secret must be defined with an optional key.
## Name is templated.
envFromSecrets: []
## - name: secret-name
##   optional: true

and one for generating env vars as secrets:
## Sensible environment variables that will be rendered as new secret object
## This can be useful for auth tokens, etc.
## If the secret values contains "{{", they'll need to be properly escaped so that they are not interpreted by Helm
## ref: https://helm.sh/docs/howto/charts_tips_and_tricks/#using-the-tpl-function
envRenderSecret: {}

it would be nice to have this here as well.


David

Not sure how to not include account info in request. Probably should move account info to separate file for easier pull requests.

For the account stuff, I think we can create a separate file for the info so we can exclude that file from commits

Yeah we can put them into a config file. Let me know when you finish addressing these issues.

David dont worry about the account stuff, i moved them into a config file in my branch.


⚠ ClamAV has degraded performance

In 08b1b99, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 216 ms

Resolved: ClamAV performance has improved in 0e4d0c3.


design: add Subdomain Delegation draft

Updates #410
Subdomain delegation is an alternative to TLS Certificate Delegation (#889).
Subdomain delegation introduces the notion of a "root" IngressRoute
object which holds the top level domain definition, ie, .mycompany.com,
along with a TLS stanza block that applies to all delegated subdomains
unless specifically overridden.
Signed-off-by: Dave Cheney<EMAIL_ADDRESS>

/cc @jbeda @mattmoyer @joshrosso @rosskukulinski

I particularly like this spec as the subdomain delegation is likely a common use-case and this allows to having one IR for a domain suffix rather than one IR per subdomain

I believe this proposal should be separate from #889. Specifically, I don't believe this proposal actually addresses the shared TLS cert issue, but is only side-along to the problem. I've commented on the other PR with more details. See https://github.com/heptio/contour/pull/889#issuecomment-465302084

Deferred til 0.11