Standard file symbol syntax

I was thinking maybe we should just go ahead and add a standard "file symbol" syntax to SCIP so that you can emit occurrences which are references to a file rather than some fake occurrence within the file.
For some languages, there are no package declarations at the top of a file, and we want to be able to emit references to files for import statements. In the past, we've relied on hacks, which don't work when the client tries to do something principled. https://github.com/sourcegraph/sourcegraph/issues/59733#issuecomment-1945520000

Questions from @kritzcreek

I think being able to reference files makes sense. There are a lot of languages that use files as meaningful units (most common would be implicit module).
How'd you represent these symbols? Relative paths to the index root? Would the indexers need to emit definition occurrences for all files. just the ones referenced, or would the file symbols have special resolution logic?
When introducing the features I'd maybe add a guide line along the lines of:
"Where possible we should prefer linking to syntax (think module Data.List where in Haskell, rather than targeting the file)"

Relative paths to the index root?

Yes, relative, syntactically normalized (no . or ..). This is the current syntax for global symbols
<scheme> ' ' <package> ' ' (<descriptor>)+
We should reuse the prefix bit, but the last bit needs to not match any descriptor.
Identifiers cannot be empty, which means that we can maybe we can use some syntax like:
<scheme> ' ' <package> ' ' file://<relative_path>
Based on the grammar, I think this syntax would be illegal, because the sequence :// is not allowed. It is also easy to understand.
We retain the <package> part because you should be able to refer to files in other repos.

Would the indexers need to emit definition occurrences for all files. just the ones referenced

I think having files be referencable in SCIP is a useful concept, and in terms of extra storage, it wouldn't be that much, it's one string per document. So I propose the following:
Add two fields to Document: file_symbol_info: SymbolInformation and file_occurrence.

If one wants to add "file-level docs" for the file, they get attached to file_symbol_info.
If one wants to specify a real source range for the file's occurrence to land (e.g. <Name> in module <Name> in Haskell), they can attach it to the file_occurrence.

As part of Document normalization:

If doc.file_symbol_info?.symbol? is unset, we implicitly construct one with the right name
If doc.file_occurrence?.symbol? is unset, we implicitly set it with the right name.
If doc.file_occurrence?.range? is unset, we implicitly set it to [0, 0, 0] so as to not break other code relying on ranges set for occurrences (not 100% sure about this, feels a bit hacky... - need to be careful that we don't panic or silently drop these elsewhere during Document normalization or insertion)

would the file symbols have special resolution logic?

Hmm, resolution-wise, I don't think we should need anything special at all (maybe I'm missing something -- do you think this would be necessary?). The extra sauce will be needed in client-side code nav.

On 'Go to definition', it needs to not highlight any source range if the file_occurrence.range is zero-length.
It needs to make sure that it provides some ways of doing 'Find references' for files which do not a proper source range for the file_occurrence.

When introducing the features I'd maybe add a guide line along the lines of:

Yeah, definitely, agreed. We've added examples in the past in scip.proto to guide indexer authors.

Follow-up from @kritzcreek

syntactically normalized

Queue the support requests for symlinked setups, or directory mapping like tsconfig paths etc...
I agree syntactically normalized is the best we can do, but I'm still a bit worried people might interpret "files are supported" to mean "file systems are supported"

and in terms of extra storage, it wouldn't be that much

We should definitely keep an eye on this, paths can be relatively long and strings are expensive. I'd hope gzip would compress the repetition in path prefixes relatively well, but we'll have to check.

Hmm, resolution-wise, I don't think we should need anything special at all (maybe I'm missing something -- do you think this would be necessary?)

I was thinking about this in terms of the codeintel backend. If the frontend doesn't "decode" the symbol to request a file (and maybe it can't anyway because of doc.file_occurence), we'd need to add these new file symbols to the codeintel_scip_symbols table, right?

Queue the support requests for symlinked setups, or directory mapping like tsconfig paths etc...
I agree syntactically normalized is the best we can do, but I'm still a bit worried people might interpret "files are supported" to mean "file systems are supported"

We already have the rules written here. https://github.com/sourcegraph/scip/blob/main/scip.proto#L79-L88
We haven't received any complaints about it so far.

and in terms of extra storage, it wouldn't be that much
We should definitely keep an eye on this, paths can be relatively long and strings are expensive

Import statements are generally much fewer than other occurrences in most code (PureScript doesn't count as mainstream :stuck_out_tongue:). I think we really should not worry about this.

I was thinking about this in terms of the codeintel backend. If the frontend doesn't "decode" the symbol to request a file (and maybe it can't anyway because of doc.file_occurence), we'd need to add these new file symbols to the codeintel_scip_symbols table, right?

My point was, the "special-ness" of these symbols would be around normalization (which happens during ingestion) mainly, and special affordances needed in the UI. Storage (at rest) and retrieval/lookup (in the backend) should be unaffected because they're "just" symbols.
In my mind, "resolution" ~ lookup. Since the storage would be like other symbols, resolution/lookup would also be similar.


Test Request

This to test GA action from feature branch do not approve

why this failed -
QOKit test (python simulator only) / build (3.9) (push) Failing after 20s


kubetest not found

need some help while trying to make the e2e test in the k8s the hard way
16-e2e-tests.md
After I install kubetest:
go get -v -u k8s.io/test-infra/kubetest
Then kubetest binary is not found
kubetest --extract=v1.14.1
kubetest: command not found

Can someone help please?

same issue

Run again go get -v -u k8s.io/test-infra/kubetest and check if you get a meaningful error.
I suggest you to follow this other issue as well as it might be related:
https://github.com/mmumshad/kubernetes-the-hard-way/issues/115

Hi @msadofschi @an-t-oine @blasterspike
We have now merged a major change to bring this to v1.24.
Many issues including this have been addressed as part of the upgrade. Please try it now and feel free to raise further issues.
Also note that in the 11 versions that have been jumped, kubetest now has significantly more tests, and takes 18+ hours to run to completion. Not all tests it runs are valid for this setup, so a small percentage of failures is expected.
Thanks.


Terminal buffer doesn't span full width

Issue Type: Bug
When VS Code opens, the usable buffer of the terminal will be severely truncated in width. Using the terminal beyond the limited width, will result in display corruption:

Closing the terminal and opening it again, restores the buffer to full width. This is very cumbersome, as logging out from the terminal often produces an error message that has to be manually closed as well, before ultimately opening the terminal in its desired state.

When restoring the window down from maximized state, the terminal buffer fits perfectly into the new bounds of the window. This suggests that this restored window size (or VSCs handling of window state during startup) is also the reason for this glitch.
 Started happening with the latest update.

I noticed the same issue, especially with pager commands like less. I have the VSCode window split in terminal on the left side, editor on the right side. A workaround is slightly resizing the terminal/editor with the divider in the middle.

I believe this is the same issue I'm facing in the latest 1.55 release.  Terminal goes into an 80 column wrap mode.  To restore I have to close that terminal instance and start a new one.
Looks like a regression as I've not had this problem with prior versions

I've had the same one since the update to v1.55.

I noticed this today as well.
Version: 1.55.2 (user setup)
Commit: 3c4e3df9e89829dce27b7b5c24508306b151f30d
Date: 2021-04-13T09:35:57.887Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

These all appear to be related: #120136, #120427, #116174

I noticed a similar thing with the maximizing/unmaximizing and the terminal width. See this comment

If this helps with troubleshooting: when this issue occurs for me, I can quickly fix it by resizing the terminal window a little, which I guess forces some sort of terminal width recalculation.

I feel like this might be fixed in latest Insiders build. Terminal is coming up full-width pretty reliably today.
Version: 1.56.0-insider (user setup)
Commit: 85f8ebf1687661c45fe2633bdd7f640164a20cc2
Date: 2021-05-04T08:04:43.323Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

I can't reproduce the behavior in Stable on the machine I'm currently working on, but I have already noticed the change in behavior on the workstation I've originally seen the issue on. So I'm inclined to call this /verified


Ruby example for mutual client/server auth

Forked from the greeter example. Illustrates client and server auth with
different CAs and shows how to inspect specific certificate properties.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

@ahoenselaar sorry for letting this sit.
I want to get this in and I think it's helpful, but unfortunately I'll be a bit longer before being able to review

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

OK thanks for the confirmation.
So while I understand that you are abusing the override feature in a way
that is safe (from the security standpoint but not completely from the
semantics standpoint), I am worried that this distinction will be lost on
the majority of gRPC users that will have a look at this code.
That's another way to say that I am concerned about having this code
checked-in as part of the gRPC distrib. The goal though will be to have TLS
bindings that are compatible with spiffe and  would allow you to implement
the semantics that you want, and this we will do in the gRPC repo.
In the meantime, if you need this feature (even in a hackish state), it
seems to me that you can completely drive it from application code.
Does that make sense to you?
On Thu, Jun 15, 2017 at 4:29 PM, Augusto Roman<EMAIL_ADDRESS>wrote:

@augustoroman commented on this pull request.
In examples/ruby/mutual_auth/client.rb
https://github.com/grpc/grpc/pull/10529#discussion_r122217088:

certs = load_test_certs

GRPC::Core::ChannelCredentials.new(certs[0], certs[1], certs[2])
+end

+def main

host_override = 'foo.test.google.fr'
OptionParser.new do |opts|
opts.on('--server_host_override HOST_OVERRIDE',

'override the SSL target host name.') do |v|

 host_override = v

end
end.parse!

NEVER override the target hostname in a production environment. In

production, the FQDN of the server and the name in the certificate have to

match.

Yes, that's what we're doing. Thanks for the SAN and spiffe pointers,
that's very informative!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/10529#discussion_r122217088, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF-P7cG4x8O-FMxWrGzSN1NFQPbfdskYks5sET-5gaJpZM4M3hcO
.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks @jboeuf, yes that makes sense and I'm happy to learn about spiffe and that sounds like a good path forward. I agree that the subtleties involved in doing what we're doing should not be considered general advice since it's applicable only to narrow, specific use case and abuses the semantics of the certificates.

@augustoroman Thanks much for your understanding. I'll let @apolcyn continue with the review with this guideline in mind as I'm going on vacation tonight.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Updated based on your comments. PTAL

@ahoenselaar after some thought, I have to follow the concern mentioned by @jboeuf about the overriding of the server name in a sort of official example.
On the other hand, I'd love to add this in is as an end-to-end test for grpc-ruby, (by converting it into an rspec test and fitting it in with the rest of the tests).
If you'd like to go down that route, I have a couple of notes:

All of the content here could probably be placed under a new directory under the src/ruby/spec directory of this repo. Maybe src/ruby/spec/client_server_auth.

Probably add the openssl gem as a development dependency in here

We should probably convert the protobuf types here to use these generated protobufs

those protobuf could  be required in the test file similarly as is done in this test

Since this is using security features that are intended for tests, IMO this would fit best if it was just a test itself (docs and helpful pointers could still refer to it).
PLMK if this sounds ok to do.
thanks for the content so far.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

@apolcyn  please resolve / close. This PR haven't been updated for >1year

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @ahoenselaar isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot

Per my recent comment, I'd tend to keep this in a test rather than an example, and there is a test which I believe sufficiently covers what's in the example in this PR: https://github.com/grpc/grpc/blob/master/src/ruby/spec/client_auth_spec.rb, so closing


'type:transformer' partitioning doesn't ensure non-zero parameters on each pipeline rank.

Running Megatron-Deepspeed with pipelining seems to call PipeModule with the type:transformer partioning method which leads to this line of code -  (https://github.com/microsoft/DeepSpeed/blob/2eafe41be7049721b77c2f2b0ee702fea1702239/deepspeed/runtime/pipe/module.py#L391)
I tried running this with a model with 42 layers, tensor parallel=4, and pipeline=16. pipe ranks 15 and 16 were assigned 0 layers. Something needs to be changed to ensure that non-zero layers are assigned to each rank.

@siddharth9820, thanks for reporting this error. I am curious if this is a recent regression due to the below PR that changed the balancing algorithm:
https://github.com/microsoft/DeepSpeed/pull/4312
Can you please try earlier DS versions (v. 0.13.0 or 0.12.6) or revert the PR?

@tjruwase I am able to reproduce the error outside of Megatron-DeepSpeed as well -

I'll try the other versions too. Thanks for the pointer.
About potential fixes. - Could you first assign 1 layer to each rank first and then run this function on n-m layers and m ranks? But that wouldn't be an ideal fix if the weights aren't uniform.

@siddharth9820, thanks for the update. This seems like an implementation bug as I find it hard to believe both the new and old algorithms fail these seemingly practical cases.

Old algorithm - Fast Optimal Load Balancing Algorithms for 1D Partitioning
New algorithm - https://www8.cs.umu.se/kurser/TDBAfl/VT06/algorithms/BOOK/BOOK2/NODE45.HTM

About potential fixes. - Could you first assign 1 layer to each rank first and then run this function on n-m layers and m ranks? But that wouldn't be an ideal fix if the weights aren't uniform.

Yes, it does not seem like this approach would be balanced. I think it will only increase the minimum from zero to one. Right?

Yes it won't be balanced. But atleast it will "run" with Megatron Deepspeed. With the current approach, I was getting "empty parameter" errors during optimizer initialization. I believe this was happening on the second last pp rank, since it became parameterless.


fix release script for experimental

got all the way to the end and failed on:
./hack/make.sh must be run before release_binaries

ping @tianon there should be a more graceful way to do this across the board, its repeated in hack/make.sh now

Oh gross, what's this about?  I don't recall a change to make.sh related to this.

its so gross
On Thu, May 28, 2015 at 5:17 PM, Tianon Gravi<EMAIL_ADDRESS>wrote:

Oh gross, what's this about? I don't recall a change to make.sh related
to this.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/13568#issuecomment-106639054.

make it stop
On Thu, May 28, 2015 at 5:18 PM, Jessie Frazelle<EMAIL_ADDRESS>wrote:

its so gross
On Thu, May 28, 2015 at 5:17 PM, Tianon Gravi<EMAIL_ADDRESS>wrote:

Oh gross, what's this about? I don't recall a change to make.sh related
to this.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/13568#issuecomment-106639054.

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-release-script-for-experimental" git@github.com:jfrazelle/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

This will update the existing PR, so DO NOT open a new one.

ok ready :), ping @tianon

updated

Good enough, lol.  LGTM

Good enough, lol. LGTM

Excuse me but i have standards, its just "good enough" ;)

Hah!  Sorry, didn't mean to insult.  I mean the output is good enough.  The functional changes look great. :+1:

hehehehe ok :)

ping @icecrime

LGTM

LGTM


add tag to the signup page in the tutorial

Please add this tag to all the signup links in the tutorial, for future tracking: 8CDa36
Also make sure that all the links to the signup page are binaris.com/signup and not binaris.com/try

Fixed.


Feature Request: Hide Right-Click Menu

Thanks for making this extension! It works really great an I enjoy it.
I would like to request that you add the option to have the right click menu hidden.
Also, with that being said it would be nice to be able to add words in a way other than right clicking (since some sites disable it or change if you right click).
Thanks!

Hey Ray!
First of all thank you for the feedback and support, it's really important 👍
Regarding your request in order to maintain the UI clean I've decided not to add the option to add the word there, however, I haven't thought on those websites who block the right click. I'll update the extension once I've got the time 😀
By the way: how did you got to know the extension?
Regards,

I stumbled upon the extension because I just happen to type in "word
highlighter" when searching for a chrome extension.
Instead of adding the options right in the little menu button you could
always add an options page to keep the clean UI.
Thanks!
On Tue, Dec 6, 2016 at 9:55 AM, Rafael Almeida<EMAIL_ADDRESS>wrote:

Hey Ray!
First of all thank you for the feedback and support, it's really important
👍
Regarding your request in order to maintain the UI clean I've decided not
to add the option to add the word there, however, I haven't thought on
those websites who block the right click. I'll update the extension once
I've got the time 😀
By the way: how did you got to know the extension?
Regards,
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rafaelcpalmeida/Word-Highlighter/issues/1#issuecomment-265170131,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4OgRHX_W6m-CvGX2uxI2cNuI0JBpJtks5rFXdvgaJpZM4LEw6p
.

@RayBB sorry for the absent time. I've been away due to some problems. I'll work on your suggestion and try to implement it during this week or next week tops.


MWPW-163975 Support aem.live and aem.page

Resolves: MWPW-163975
Test URLs
Before: https://stage--dc--adobecom.hlx.live/acrobat/online/word-to-pdf
After: https://MWPW-163975--dc--adobecom.hlx.live/acrobat/online/word-to-pdf

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.04%. Comparing base (847d448) to head (62ccffd).

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #921      +/-   ##
==========================================
+ Coverage   81.02%   81.04%   +0.01%
==========================================
  Files          49       49
  Lines        6452     6457       +5
==========================================
+ Hits         5228     5233       +5
  Misses       1224     1224

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Why there are still '.hlx.page', '.hlx.live', ?

During the migration, both hlx and aem domains should be supported.


Revert STRUCT! definition in mmreg

WAVEFORMATEX and WAVEFORMATEXTENSIBLE need #[repr(C, packed)], see #202.

Any update?
Although using rust-lang/rfcs#1399 would be better, I would like this merged in the meantime to fix a problem I am having.

I possibly have a better fix in https://github.com/retep998/winapi-rs/commit/a06b9bc65019dcfb257d65595c1b43eded972a2c

That works, and is a better solution :+1:


[build-script] Skip option for non-Darwin stdlib tests

What's in this pull request?
It's possible to cross-compile for iOS while skipping stdlib tests on OS X:
$ utils/build-script --ios -- --skip-test-osx

The same is not possible on Linux. Add options to skip builds and tests on non-Darwin platforms: Linux, FreeBSD, and Cygwin. This makes the following possible:
$ utils/build-script --some-other-platform --skip-test-linux

Why merge this pull request?

This ports functionality that exists for OS X to Linux, FreeBSD, and Cygwin.
Although none of these platforms are currently capable of cross-compiling, the Android fork cross-compiles from Linux to Android. These options would immensely useful there, since otherwise there is no easy way to only run the tests for Android when building on Linux.

What downsides are there to merging this pull request?

One could argue that it should be merged alongside the Android fork. However, that would conflate that set of changes (a port of Swift to a new platform) with these (more options for the build script).

@swift-ci Please smoke test


⚠ Spryr has degraded performance

In c225671, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4887 ms

Resolved: Spryr performance has improved in 88251c6 after 7 minutes.


cubox-i + hyperion + xbian

i try to make but i get errors..
i try also:
git clone https://github.com/tvdzwan/hyperion.git
cd hyperion/deploy
sudo tar -C /opt -xzf hyperion.tar.gz
sudo ln -fs /opt/hyperion/bin/hyperiond /usr/bin/hyperiond
sudo ln -fs /opt/hyperion/bin/hyperion-remote /usr/bin/hyperion-remote
sudo ln -fs /opt/hyperion/bin/hyperion-v4l2 /usr/bin/hyperion-v4l2
sudo ln -s /opt/hyperion/config/hyperion.config.json /etc/hyperion.config.json
hyperiond /etc/hyperion.config.json
but i get error:
hyperiond: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
is there any way to install or make compatible????
Thank you

After cloning the repository you have to compile, not just extracting the version for RPi.
Try following:
git clone https://github.com/tvdzwan/hyperion.git
mkdir hyperion/build
cd hyperion/build
cmake -DENABLE_DISPMANX=OFF -DENABLE_SPIDEV=OFF -DENABLE_X11=OFF -DENABLE_V4L2=OFF -DENABLE_PROTOBUF=OFF ..
make
create a config file and test it by running bin/hyperiond hyperion.config.json

ok i try and i get errors:
xbian@xbian /tmp/hyperion/build $  cmake -DENABLE_DISPMANX=OFF -DENABLE_SPIDEV=OFF -DENABLE_X11=OFF -DENABLE_V4L2=OFF -DENABLE_PROTOBUF=OFF ..

Please set them or make sure they are set and tested correctly in the CMake files:
LIBUSB_1_INCLUDE_DIR
used as include directory in directory /tmp/hyperion/dependencies/build/hidapi
used as include directory in directory /tmp/hyperion/libsrc/leddevice
LIBUSB_1_LIBRARY
linked by target "hidapi-libusb" in directory /tmp/hyperion/dependencies/build/hidapi
linked by target "leddevice" in directory /tmp/hyperion/libsrc/leddevice
-- Configuring incomplete, errors occurred!
See also "/tmp/hyperion/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/hyperion/build/CMakeFiles/CMakeError.log".
thanks

You seem to be missing the libusb library:
sudo apt-get install libusb-1.0-0

ok the libusb-1.0-0-dev was missing ..

after success make i get error for framebuffer...
xbian@xbian ~ $ sudo hyperiond /etc/hyperion.config.json
Application build time: Jan 16 2015 09:32:02
QCoreApplication initialised
Selected configuration file: /etc/hyperion.config.json
ColorTransform 'default' => [0; 101]
Device configuration:
{
"colorOrder" : "rgb",
"name" : "MyPi",
"output" : "/dev/ttyACM0",
"rate" : 115200,
"type" : "adalight"
}
Opening UART: /dev/ttyACM0
Black border threshold set to 0.01 (3)
Creating linear smoothing
Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
Effect directory can not be loaded: /storage/hyperion/effects
Initializing Python interpreter
Hyperion created and initialised
XBMC video checker created and started
The dispmanx framegrabber can not be instantiated, becuse it has been left out from the build
terminate called after throwing an instance of 'std::runtime_error'
what():  Json server could not bind to port
xbian@xbian ~ $

comment out framegrabber settings from your config

ok i did looks ok now, leds light up white but leds doesnt work on video :(
Application build time: Jan 16 2015 09:32:02
QCoreApplication initialised
Selected configuration file: /etc/hyperion.config.json
ColorTransform 'default' => [0; 101]
Device configuration:
{
"colorOrder" : "rgb",
"name" : "MyPi",
"output" : "/dev/ttyACM0",
"rate" : 115200,
"type" : "adalight"
}
Opening UART: /dev/ttyACM0
Black border threshold set to 0.01 (3)
Creating linear smoothing
Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
Effect directory can not be loaded: /storage/hyperion/effects
Initializing Python interpreter
Hyperion created and initialised
XBMC video checker created and started
Json server created and started on port 19444
XBMC Connected
Message from XBMC: {"id":666,"jsonrpc":"2.0","result":[]}
XBMC checker: switching to OFF mode
Message from XBMC: {"id":668,"jsonrpc":"2.0","result":{"System.ScreenSaverActive":false}}
Message from XBMC: {"id":670,"jsonrpc":"2.0","result":{"version":{"major":13,"minor":2,"revision":"20141203-e4e8391","tag":"stable"}}}
Message from XBMC: {"jsonrpc":"2.0","method":"Playlist.OnClear","params":{"data":{"playlistid":1},"sender":"xbmc"}}
Message from XBMC: {"jsonrpc":"2.0","method":"Playlist.OnAdd","params":{"data":{"item":{"title":"Hot Tub Time Machine 2 - Trailer","type":"movie"},"playlistid":1,"position":0},"sender":"xbmc"}}
Message from XBMC: {"jsonrpc":"2.0","method":"Player.OnPlay","params":{"data":{"item":{"title":"Hot Tub Time Machine 2 - Trailer","type":"movie"},"player":{"playerid":1,"speed":1}},"sender":"xbmc"}}
Message from XBMC: {"id":666,"jsonrpc":"2.0","result":[{"playerid":1,"type":"video"}]}
XBMC checker: switching to VIDEO mode
Message from XBMC: {"id":667,"jsonrpc":"2.0","result":{"item":{"file":"plugin://plugin.video.itunes_trailers/trailer/play/http%3A%2F%2Fmovietrailers.apple.com%2Fmovies%2Fparamount%2Fhottubtimemachine2%2Fhottubtimemachine2-tlr_h720p.mov","label":"Hot Tub Time Machine 2 - Trailer","type":"unknown"}}}
Message from XBMC: {"id":669,"jsonrpc":"2.0","result":{"stereoscopicmode":{"label":"None","mode":"off"}}}

They won't, because there is no suitable frame grabber for imx6 at the moment. I'm working on one, but still testing, look here https://github.com/tvdzwan/hyperion/issues/149

seems i have to wait for it ... nothing seems to work...

The framebuffer grabber was merged into the main source tree, so try to compile it (see https://github.com/tvdzwan/hyperion/blob/master/CompileHowto.txt for flags) and test.
close the issue if it works.

Looks Perfect :) thanks


Update hybrid-use-benefit-licensing.md

Minor change from "Configuration" tab to "Operating system" tab where the Azure Hybrid Benefits can now be seen and toggled.

@ju-shim
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

#sign-off


Trex doesnt copy into my Clipboard

I have tried all kinds of text, but my clipboard doesn´t  store it.

screen sharing permissions were not set. My fault sorry.


Explicitly cast from unsigned ints to ints in Netty Epoll

Motivation:
SetIntArrayRegion takes an array of jints as its last arg, but
netty is passing in an array of unsigned ints.  This makes the
linter unhappy, and complains when -Werror=pointer-sign is on.
Java doesn't really have unsigned ints (except for chars) so
it doesn't really make sense to pass unsigned ints back up.
Modifications:
Explicitly cast from unsigned ints to jint.
Result:
Less naggy linter.

@carl-mastrangelo I think this is a proper fix which also fix the problem with truncated values (without API breakage) : https://github.com/netty/netty/pull/7011

Let me close this as https://github.com/netty/netty/pull/7011 fixes it probably


adding files back, resetting redirection.json

OPS Build status updates of commit a1208a1:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit a1208a1:
:clock10: Incremental building: average incremental building time is 21 sec(s)

OPS Build status updates of commit a1208a1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

msteams-platform/redirects/activityfeed.md
:white_check_mark:Succeeded

msteams-platform/redirects/appcapabilities.md
:white_check_mark:Succeeded

msteams-platform/redirects/apps-package.md
:white_check_mark:Succeeded

msteams-platform/redirects/apps-sideload.md
:white_check_mark:Succeeded

msteams-platform/redirects/auth.md
:white_check_mark:Succeeded

msteams-platform/redirects/authentication.md
:white_check_mark:Succeeded

msteams-platform/redirects/botapis.md
:white_check_mark:Succeeded

msteams-platform/redirects/botevents.md
:white_check_mark:Succeeded

msteams-platform/redirects/botmenu.md
:white_check_mark:Succeeded

msteams-platform/redirects/bots-channel-conversation.md
:white_check_mark:Succeeded

msteams-platform/redirects/bots-personal-conversation.md
:white_check_mark:Succeeded

msteams-platform/redirects/bots.md
:white_check_mark:Succeeded

msteams-platform/redirects/bots1on1.md
:white_check_mark:Succeeded

msteams-platform/redirects/botsadd.md
:white_check_mark:Succeeded

msteams-platform/redirects/botsconversation.md
:white_check_mark:Succeeded

msteams-platform/redirects/botscreate.md
:white_check_mark:Succeeded

msteams-platform/redirects/botsinchannels.md
:white_check_mark:Succeeded

msteams-platform/redirects/botsmessages.md
:white_check_mark:Succeeded

msteams-platform/redirects/cards-actions.md
:white_check_mark:Succeeded

msteams-platform/redirects/code.md
:white_check_mark:Succeeded

msteams-platform/redirects/compose-extensions.md
:white_check_mark:Succeeded

msteams-platform/redirects/composeextensions.md
:white_check_mark:Succeeded

msteams-platform/redirects/connectors.md
:white_check_mark:Succeeded

msteams-platform/redirects/createconfigpage.md
:white_check_mark:Succeeded

msteams-platform/redirects/createcontentpage.md
:white_check_mark:Succeeded

msteams-platform/redirects/createpackage.md
:white_check_mark:Succeeded

msteams-platform/redirects/cross-domain.md
:white_check_mark:Succeeded

msteams-platform/redirects/crossdomain.md
:white_check_mark:Succeeded

msteams-platform/redirects/custom-bot.md
:white_check_mark:Succeeded

msteams-platform/redirects/debugging.md
:white_check_mark:Succeeded

msteams-platform/redirects/deeplinks.md
:white_check_mark:Succeeded

msteams-platform/redirects/design.md
:white_check_mark:Succeeded

msteams-platform/redirects/faq.md
:white_check_mark:Succeeded

msteams-platform/redirects/feedback.md
:white_check_mark:Succeeded

msteams-platform/redirects/get-started-dotnet.md
:white_check_mark:Succeeded

msteams-platform/redirects/get-started-nodejs.md
:white_check_mark:Succeeded

msteams-platform/redirects/getusercontext.md
:white_check_mark:Succeeded

msteams-platform/redirects/graph.md
:white_check_mark:Succeeded

msteams-platform/redirects/index.md
:white_check_mark:Succeeded

msteams-platform/redirects/jslibrary.md
:white_check_mark:Succeeded

msteams-platform/redirects/messaging-extensions.md
:white_check_mark:Succeeded

msteams-platform/redirects/outgoingwebhook.md
:white_check_mark:Succeeded

msteams-platform/redirects/prerequisites.md
:white_check_mark:Succeeded

msteams-platform/redirects/previewfeatures.md
:white_check_mark:Succeeded

msteams-platform/redirects/publicpreview.md
:white_check_mark:Succeeded

msteams-platform/redirects/ratelimiting.md
:white_check_mark:Succeeded

msteams-platform/redirects/requirements.md
:white_check_mark:Succeeded

msteams-platform/redirects/samples.md
:white_check_mark:Succeeded

msteams-platform/redirects/scenarios.md
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Provide proper metrics for web based services

Impact of the new feature
Based on recent incident INC2542764 with low service performance of Python based services on k8s it would be extremely helpful to provide proper set of metrics from service stack. Since all cmsweb Python based services (DBS, ReqMgr2, CRAB etc.) are based on WMCore codebase it is natural to implement service metrics in WMCore rather in upstream services. This will allow proper monitoring of web services.
Describe the solution you'd like
Extend ProcessStats.py metrics to include the following

number of requests
status code stats
response time of request
number of connections
number of open file descriptors
if DB is in use DB related stats

Is your feature request related to a problem? Please describe.
Please see this incident discusssions INC2542764
Describe alternatives you've considered
None, currently we run our services without proper knowledge how they behave, what is their throughput and how the perform under production load
Additional context
Once metrics are added to ProcessStats.py we need to modify WMCore WebTools and REST interface to add /metrics or /status end-points and enable this by default that it would not be required in upstream code to change anything in order to have them. Once they are available we can setup proper exporter (code should be developed in CMS Monitoring group) and integrate it into Prometheus metrics for each individual service.

Valentin, sometime ago we have implemented the CherryPy based statistics through:
https://cmsweb.cern.ch/reqmgr2/data/stats
looking at the output, I see lots of potential on the type of data that can be provided, but - apparently - most of them are either empty or reporting a default value.

yes, this can be good candidate too, please put the pointer to the code as well here that we can refer and look at. I don't mind where/how it will be reported but we do need this for every service, e.g. CRAB, DBS, etc.

one problem which I immediately see with this output is set of dynamic keys (usual issue with Python dev), while for metrics to be integrated with exporter/Prometheus it is not acceptable. The keys of all keys should be static, i.e. we need a fixed schema. For example, key "Cheroot HTTPServer<PHONE_NUMBER>37712" or "CP Server Thread-10" are not good. The schema should not rely on dynamic keys which may change from app to app, from one config to another. Instead we need a static schema which will be independent from underlying app and service configuration.

Valentin, here are the pointers to the code:
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/REST/Server.py#L700
and
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WebTools/Welcome.py#L55
the latter is on the Welcome module, so I think it's of no use to DBS/CRAB services at the moment.
About the data structure, note that we simply return the output of the native cherrypy API. Of course, nothing stops us from applying a data schema on top of that. Only problem is that it can break in future releases (if they change that format).

@todor-ivanov please review this feature request too which should be fixed by #9940 PR I requested you to review too.

@amaltaro , please review and decide if we need to proceed or close it. The correspoding PR #9961 and #9940 are still open for 2 years.


Add Special Entity Subtypes to be Unit attributes

From @lfunkhouser on November 5, 2014 21:37
Any suggestions on how we are going to handle the special entity subtypes? I don't believe they are in our solution.
These "codes" are
xxxx95 for Headquarters element
xxxx96 for Division and below support
xxxx97 for Corps support
xxxx98 for Theater/echelons above Corps support

Copied from original issue: ArcGIS/military-features-pro-data_RETIRED_DONT_USE#97

From @csmoore on November 5, 2014 21:46
Can you just have an attribute/field/domain on units with values/strings
95 - Headquarters element
96 - Division and below support
97 - Corps support
98 - Theater/echelons above Corps support
If the attribute is there, I can figure out how to handle (it was a tremendous pain making this crazy/exceptional case work from the SIDC, but I think the attribute will be easier than that was)

From @jrweakland on April 13, 2015 22:42
We can add another domain to the FGDB with the four values.

This issue was duplicated when migrating the issues. Closing this issue.


Support for nested params

This is related to closed issue #33
Sometimes this is really needed, e.g. if search parameters are nested by API design.
Please consider.

Thanks for your contribution, @shhavel. I think nested parameters are something that make sense for the next major version of sinatra-param. As far as implementations go, I think I prefer the nested version in #60, and will likely go that route instead.


Support private repo import

When sandboxing new skillets or working with pre-release code want to have a way to import a private repo into panhandler with ssh. Currently spins and times out. Then when trying to add additional repos, errors out with stderr: 'fatal: bad revision {branch name}

You can do this today, however, you must mount your .ssh dir inside the container for ssh based private repos to work. The following command works (assuming your default ssh key has access to the private repo in github)
docker run -p 8081:80 -v ~/.ssh:/root/.ssh paloaltonetworks/panhandler
note the -v ~/.ssh:/root/.ssh bit there

there seems to be a bug though when adding a repo fails and subsequent ones also then fail, so leaving open to track that for sure

fixed issues with importing failures and subsequent failures
https://github.com/PaloAltoNetworks/pan-cnc/commit/7d257d2c4e2ff44da630cac0819804decbf8a432


Multi-tenancy support

I couldn't find anywhere in the documentation. Is Multi-tenancy planned for future release?

Multi-tenancy at which level? Right now we have a project_name key you can add to your config.toml that will namespace your horizon database, allowing multiple apps to use the same RethinkDB cluster.

Multi-tenancy in the horizon level. Do i need to run multiple servers i.e one per app?
It will be really convenient if one horizon server is enough to run multiple apps. kinto has buckets for this purpose. Something similar to that would be really helpful.

Ah, ok, thanks for the clarification. So right now, you'll need to run multiple standalone horizon servers to take advantage of this, if you don't want to write backend code. We don't have a server configuration option to talk to multiple horizon apps at the moment.
If you write your own backend and import horizon as a library, you can attach two horizon servers to the same http server instance, which would get you this effect. You'd just need to specify different paths to mount them on.
I'll change the name of this issue to to reflect that we're talking about multiple apps without a custom backend


Release v4.0.0-alpha.3

Changes since v4.0.0-alpha.2

Expose more apis for KubeObjectListLayout usage (#1194)
Add actions/labeler for auto label PRs (#1193)
Fix UI staleness after network issues (#1192)
License extension  (#1174)
Fix proxy upgrade socket timeouts (#1190)
Add missing kubeObjectDetailItems observable to LensRendererExtension (#1187)
Expose KubeObjectListLayout to extensions (#1186)
Telemetry improvements (#1180)
Expose kubeObjectDetailRegistry via extension-api (#1185)
Status bar visual fixes (#1182)
PoC: using external styles for extensions (#1173)
Improve how extensions can manage cluster/workspace stores (#1176)
Fix: path checks in custom extension loader (#1170)
Optimize ExtensionManager#load (#1171)

Build blocked by https://github.com/lensapp/lens/issues/1202


Missing Code Documentation

Using FluentAvalonia v1.4.0, I see that the source code is well documented, but when importing it from NuGet, there is no code documentation whatsoever. XML doc hasn't been generated as part of the package.

I've added the <GenerateDocumentationFile> tag to the csproj which should fix this. If it doesn't feel free to reopen this and we'll go from there


RemoteScheduler: use urljoin on base URL & suffix to form a full URL

I usually wants commits to be squashed, but I might make an exception here as I suppose this is pretty urgent.
Thanks. :)

i will squash!

Awesome, thanks for the quick fix @paxan, I hope this didn't have drastic consequences for your or anybody else production environments!

:+1:  (i've worked around it by ensuring scheduler_url arg has no trailing /)

But after this patch it works regardless, right?

I'll check master against my setup later today.

@Tarrasch @paxan @graingert Looks like this is functioning correctly for me.  Thanks :+1:

@tarrasch right.


[Feat] New Beta Feedback Form and button

New user feedback form for our Beta,  This form will be able to be used to submit feedback directly from the Admin Dashboard.

!coauthor


[Auth] #377 Auth Request Subscriber

close #395

@MisterVants committed your RPCID suggestion, maybe later we can use typealias to not import JSONRPC lib all over the sdk


[OTHER] Change the colors of the discord and github icons on hover

What would you like to share?
Change the hover color of the discord icon to indigo-500 and lime-500 of github

Additional information
Keep it a good first issue

Would love to fix it

Hey! if no one is working on this issue can you assign it to me? I would love to fix it.

Hey, I think @djv03 was first, so I'll assign it to them. Feel free to pick another issue or ask for help 🙏

@Vishvsalvi I have fixed the issue but I don't know how to test it!
can you please help me  with this

Read the documentation for testing it on your local machine

First you need to install the Playwright dependencies with npx playwright install --with-deps.
After that you can run the test script from the package.json

Hey @Cahllagerfeld, is this issue resolved???

#300 is already opened for it, it should be merged very soon I think

apologies for delayed work...getting some issues with my git...get back to
you by tomorrow evening
On Wed, Feb 22, 2023 at 1:10 PM Cahllagerfeld @.***>
wrote:

#300
https://github.com/EddieHubCommunity/good-first-issue-finder/pull/300
is already opened for it, it should be merged very soon I think
—
Reply to this email directly, view it on GitHub
https://github.com/EddieHubCommunity/good-first-issue-finder/issues/280#issuecomment-1439560234,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWIPI4NC3RWTNKF5B7KCIP3WYW7FFANCNFSM6AAAAAAUGCQAOY
.
You are receiving this because you were assigned.Message ID:
@.***
com>

@Cahllagerfeld Looks like Pr is merged but issue didn't close because creator of PR forget to add link to this issue. Can you close as approved?

thank you @BurakTaner for pointing this out!


Logging nbl::video device call failures

Problem
Many device functions return a boolean to indicate a successful call to lower level api (Vulkan) function.
But the return value is often ignored making it hard to debug the cause of the problem.
Even if not ignored, simply returning false on a failure doesn't help much pinpointing the exact cause.
There is also createXXX functions that may return nullptr due to reasons such as invalid creation params
for example inside ILogicalDevice::createFramebuffer
if (!params.validate())
    return nullptr;

may fail due to 30+ reasons specified in vulkan specification and handled manually in IFramebuffer::SCreationParams::validate
that's why we need to "error log" the exact cause of the failure each time we return false on device calls
Solution
use system::logger_opt_ptr m_logger in ILogicalDevice` to log every possible scenario that fails.

Btw it would be enough to just
log("Short Message: `%s` in `%s` at line %p.",system::ILogger::ELL_ERROR,__FILE__,__FUNCTION__,__LINE__);

Instead of writing custom exact log messages, because we're an Open Source project, source is there and the extended comments about why something fails are in the source anyway.

now thinking of it, it would be useful to also have an _NBL_COMMIT_HASH_ in there too in case someone runs non-development exes without a local copy of the source

Exactly what i was thinking about


Updating unity package so it meets Unity Asset Store requirements

Microsoft will be publishing their most recent Mixed Reality UPMs to the Unity Asset Store.  In prepartion for this, this Stapial Audio package must be updated to meet Unity's requirements.
The following were changed to meet Unity's requirements

Minimum version of Unity updated to 2021.3.26f1. This is the minimium version of Unity supported by the UPM Asset Store.
Added the unityRelease.  This is required by the UPM Asset Store.
Added a CHANGELOG.md that follows the Keep a Changelog formatting.
Added documentationUrl. This is required by the UPM Asset Store.

/azp run


Bug reading undefined

Description
feed storage need to wait for ready field
adjusted log.error props
About #3786 #3747
Checklist:

[x] PR title matches follow: (Feature|Bug|Chore) Task Name
[x] My code follows the style guidelines of this project
[x] I have followed all the instructions described in the initial task (check Definitions of Done)
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have added reference to a related issue in the repository
[x] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[ ] I have added screenshots related to my pull request (for frontend tasks)
[ ] I have pasted a gif showing the feature.
[ ] @mentions of the person or team responsible for reviewing proposed changes

@roma-hladilka how does it related to the #3747 ?

#3747 is the issue about incorrect logging, message and error object were swapped

@roma-hladilka please re check PR after changes


Implement prioritized matching

So far the API only does a match sans coordinates. Implement a series that looks first for a match with coordinates. If that fails to produce a match, go to a match with verbatim coordinates. If that fails, go to a match sans coordinates. In the output, capture which matching method was used.

Done


No object is visible in find_object_3d launch

Hi,
I did the data annotation with an object. When i try to do the object detection, its not detecting any object, i am getting white screen.

This is my code:
<launch>

    <node name="find_object_3d" pkg="find_object_2d" type="find_object_2d" output="screen">
        <param name="gui" value="true" type="bool"/>
        <param name="settings_path" value="~/.ros/find_object_2d.ini" type="str"/>
        <param name="subscribe_depth" value="true" type="bool"/>
        <param name="session_path" value="$(find my_object_recognition_pkg)/saved_pictures/ball_session.bin" type="str"/>
        <param name="objects_path" value="" type="str"/>
        <param name="object_prefix" value="object" type="str"/>

        <remap from="rgb/image_rect_color" to="/camera/rgb/image_raw"/>
        <remap from="depth_registered/image_raw" to="/camera/depth/image_raw"/>
        <remap from="depth_registered/camera_info" to="/camera/depth/camera_info"/>
    </node>

</launch>

It seems the remap is wrong. Maybe try with:
<remap from="camera/color/image_raw" to="/camera/rgb/image_raw"/>
<remap from="camera/depth/image" to="/camera/depth/image_raw"/>
<remap from="camera/color/camera_info" to="/camera/depth/camera_info"/>

still getting the same error screen

Actually, I cannot get the same error than you with exactly the same launch file than you:

which seems to work fine.


make the login more reliable

++ we need to add the follwoing to the login :
1)Dr first and last name .
2)phone number
++ we need to make sure that the email is a valid email .
++ make sure that duplicate entries(email or username) return a user friendly error

30% work done so far :
1)added firstname + last name + country to the register page .
next actions :
1)make sure that duplicate entries(email or username) return a user friendly error.
2)we need to make sure that the email is a valid email .

90% done.
next actions :
validate Email using javascript.


Enrich additional register form attribute (or Twig block)

Please describe the feature you would like to see implemented.
For some reasons our customers want to serve upload fields within the register form.
Here we need the following attribute:
enctype="multipart/form-data"

Actually we copy the whole form from the core template or resolve it with a little JS hack:
<script type="text/javascript">
   const registerForm = document.getElementsByClassName("register-form")[0];
   registerForm.enctype = "multipart/form-data";
</script>

Both solutions are working for now, but are kind of ugly.
So I like to ask for an additional Twig block at this point:
https://github.com/shopware/platform/blob/6179a94fa19aa26b46e9d0c5d77b20bfa5c5bb5b/src/Storefront/Resources/views/storefront/component/account/register.html.twig#L13
Kind regards
Philipp

I'll be working on this one.

Hello,
Within our company roadmap and work capacity, we try to address each bug or improvement request but admit that not each one will be resolved. To continue our culture of honesty and openness, we are closing this issue to focus on our roadmap on behalf of all Shopware users.
If you feel like this issue is still impacting you, please create a new issue and let us know.
Thank you again for your valuable feedback.


Add HGPlaceholders Library

Project URL
https://github.com/HamzaGhazouani/HGPlaceholders
Description
Nice library to show placeholders and Empty States for any UITableView/UICollectionView in your project
Checklist

[x ] Only one project/change is in this pull request
[ ] Addition in chronological order (bottom of category)
[x ] Supports iOS 9 / tvOS 10 or later
[ x] Supports Swift 3 or later
[ x] Has a commit from less than 2 years ago
[ x] Has a clear README in English

          1 Warning

:warning:
Found 2 link issues, a project collaborator will take care of these, thanks: )

Link issues by awesome_bot

Line
Status
Link

314
Error
http://oclint.org/  getaddrinfo: Name or service not known

2453
Error
https://iconresizer.com/  Connection refused - connect(2) for "iconresizer.com" port 443

  Generated by :no_entry_sign: Danger

Hey @HamzaGhazouani, thanks for contributing and good job on your lib.
Please add your library at the end of the Table View section please.

Hey @lfarah, it's done :) thanks

@HamzaGhazouani thank you!

you are welcome :)


state should change to offline when no connection established

This problem is not reproducible. Can you provide more details or steps to reproduce? @congtan0224


Layout preview

Currently I mocked up this layout. It's using a three column layout so the missing settings can be added.

Thoughts on the general style?

Maybe have a little SVG schema describing the workspace. It doesn't need to be updated with input values, but at least having a picture with all measurements values visible might help people understand how these values are used on a real laser cutting machine

If you're saying that only line color, workspace size and file format are related to laser cutter, then maybe add a specific fieldset "Laser cutter settings" to know there's a difference between midi-to-laser output & machine config.

Good idea, I then propose to move all settings to below the preview together with a heading so it's clear that it's for the laser cutter.

Has been migrated to https://github.com/Wintergatan/MIDIPunch/issues/1


fix: using latest sasjs headers, closes #231

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


doc: conf.py: revert 2e99de80 (unnecessary and breaks PDF build)

This reverts commit 2e99de80472b80f36303ff85c8ed5d54dfe73ef4 as it's introducing an unneeded change that also happens to break PDF build as it is making the assumption that the build output folder is always html (but it can be latex, etc.)

@JordanYates please confirm I didn't oversee anything.
BTW, it looks as if html-live and html-live-fast require html target to have run once first, as it wants the html build folder to exist. Should the html-live CMake target depend on html?

The commit is definitely required on my end.. Reverting it results in
(.zephyr_venv) jordan@TAURUS:~/code/zephyr/zephyr/doc$ make html-live
cmake \
        -GNinja \
        -B_build \
        -S. \
        -DDOC_TAG=development \
        -DSPHINXOPTS="-j auto -W --keep-going -T" \
        -DSPHINXOPTS_EXTRA="" \
        -DLATEXMKOPTS="-halt-on-error -no-shell-escape" \
        -DDT_TURBO_MODE=0
Loading Zephyr module(s) (Zephyr base): doc
-- Found Python3: /home/jordan/code/.zephyr_venv/bin/python (found suitable version "3.10.12", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: /home/jordan/.cache/zephyr
-- Found west (found suitable version "1.2.0", minimum required is "1.0.0")
-- Zephyr base: /home/jordan/code/zephyr/zephyr
-- Found Doxygen: /usr/bin/doxygen (found version "1.9.1") found components: doxygen dot
-- Found LATEX: /usr/bin/latex  found components: PDFLATEX
-- Configuring done
-- Generating done
-- Build files have been written to: /home/jordan/code/zephyr/zephyr/doc/_build
cmake --build _build --target html-live
[0/2] Generating Devicetree bindings documentation...
[1/2] Running Sphinx HTML autobuild...
[sphinx-autobuild] Starting initial build
[sphinx-autobuild] > sphinx-build -b html -c /home/jordan/code/zephyr/zephyr/doc -d /home/jordan/code/zephyr/zephyr/doc/_build/doctrees -w /home/jordan/code/zephyr/zephyr/doc/_build/html.log -t development -j auto -W --keep-going -T /home/jordan/code/zephyr/zephyr/doc/_build/src /home/jordan/code/zephyr/zephyr/doc/_build/html
Running Sphinx v6.2.1
usage: sphinx-autobuild [OPTIONS] SOURCEDIR OUTPUTDIR [FILENAMES...]
sphinx-autobuild: error: unrecognized arguments: --watch --ignore /home/jordan/code/zephyr/zephyr/doc/_build/src /home/jordan/code/zephyr/zephyr/doc/_build/html

Traceback (most recent call last):
  File "/home/jordan/code/.zephyr_venv/lib/python3.10/site-packages/sphinx/config.py", line 354, in eval_config_file
    exec(code, namespace)  # NoQA: S102
  File "/home/jordan/code/zephyr/zephyr/doc/conf.py", line 12, in <module>
    args = get_parser().parse_args()
  File "/usr/lib/python3.10/argparse.py", line 1848, in parse_args
    self.error(msg % ' '.join(argv))
  File "/usr/lib/python3.10/argparse.py", line 2606, in error
    self.exit(2, _('%(prog)s: error: %(message)s\n') % args)
  File "/usr/lib/python3.10/argparse.py", line 2593, in exit
    _sys.exit(status)
SystemExit: 2
...

There is also no requirement to run html before html-live, it takes care of the first build.

@JordanYates at the risk of stating the obvious, are you rm -rf _build prior to building? Also, which version of autobuild are you running? Latest version has a hard check for html folder existence (but it might be a bug?) https://github.com/sphinx-doc/sphinx-autobuild/commit/41a7d8ced2a23a3dc533341a2950209ab871eece

On main:
cd doc
pip3 install -r ./requirements.txt --no-cache-dir --force-reinstall -U
rm _build -Rf && make html-live

...

[1/2] Running Sphinx HTML autobuild...
Traceback (most recent call last):
  File "/Users/kartben/zephyrproject/.venv/bin/sphinx-autobuild", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/Users/kartben/zephyrproject/.venv/lib/python3.12/site-packages/sphinx_autobuild/__main__.py", line 34, in main
    args, build_args = _parse_args(list(argv))
                       ^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/kartben/zephyrproject/.venv/lib/python3.12/site-packages/sphinx_autobuild/__main__.py", line 101, in _parse_args
    args.outdir = Path(sphinx_args.outputdir).resolve(strict=True)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 1240, in resolve
    s = self._flavour.realpath(self, strict=strict)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen posixpath>", line 427, in realpath
  File "<frozen posixpath>", line 462, in _joinrealpath
FileNotFoundError: [Errno 2] No such file or directory: '/Users/kartben/zephyrproject/zephyr/doc/_build/html'
FAILED: CMakeFiles/html-live /Users/kartben/zephyrproject/zephyr/doc/_build/CMakeFiles/html-live
cd /Users/kartben/zephyrproject/zephyr/doc/_build && /opt/homebrew/Cellar/cmake/3.30.3/bin/cmake -E env DOXYGEN_EXECUTABLE=/opt/homebrew/bin/doxygen DOT_EXECUTABLE=/opt/homebrew/bin/dot DOCS_HTML_DIR=/Users/kartben/zephyrproject/zephyr/doc/_build/html /Users/kartben/zephyrproject/.venv/bin/sphinx-autobuild --watch /Users/kartben/zephyrproject/zephyr/doc --ignore /Users/kartben/zephyrproject/zephyr/doc/_build -b html -c /Users/kartben/zephyrproject/zephyr/doc -d /Users/kartben/zephyrproject/zephyr/doc/_build/doctrees -w /Users/kartben/zephyrproject/zephyr/doc/_build/html.log -t development -j auto -W --keep-going -T /Users/kartben/zephyrproject/zephyr/doc/_build/src /Users/kartben/zephyrproject/zephyr/doc/_build/html
ninja: build stopped: subcommand failed.
make: *** [html-live] Error 1

@JordanYates at the risk of stating the obvious, are you rm -rf _build prior to building? Also, which version of autobuild are you running? Latest version has a hard check for html folder existence (but it might be a bug?) sphinx-doc/sphinx-autobuild@41a7d8c

Okay, the behavior has changed after updating from 2024.04.16 to 2024.09.03. Presumably something to do with:
Fix running sphinx-autobuild via entry point scripts.
https://github.com/sphinx-doc/sphinx-autobuild/blob/main/NEWS.rst#20240903---2024-09-03

There is also no requirement to run html before html-live, it takes care of the first build.

That's also what I seemed to remember from having tested the PR a few weeks back.
So could it be that both this PR is needed, and a bug should be filed against sphinx-autobuild given it doesn't seem to properly address "clean builds" anymore?

There is also no requirement to run html before html-live, it takes care of the first build.

That's also what I seemed to remember from having tested the PR a few weeks back. So could it be that both this PR is needed, and a bug should be filed against sphinx-autobuild given it doesn't seem to properly address "clean builds" anymore?

Looks like it already exists: https://github.com/sphinx-doc/sphinx-autobuild/issues/177.
As for the rest, I'm not convinced that attempting to re-parse the CLI arguments is the best solution, but I guess it doesn't break non-HTML output like my change did. Alternate option is to make a change like the following and use the new variable in conf.py:
add_doc_target(
  html
  COMMAND ${CMAKE_COMMAND} -E env ${SPHINX_ENV} OUTPUT_FOLDER=${DOCS_HTML_DIR}
  ...
)

Linked PR in Sphinx autobuild has been merged and a new release is available.
I validated that make html-live now works correctly from the doc folder without a previous run.


Router  not working properly

Hi there,
I'm making a redirect from one url to another:

This works for all links on the site who links to /news, however it won't work if i manually type /news on the URL.

@dgrana could you add a bit of code for people to look at?

If you manually type /news the browser hits your server. Are you using (RR) React-Router on the server as well?
If so, do you have an end point that intercepts /new and hands control to RR?

I've the same issue.
On my route definitions, I've this:
 <Redirect from="/:lang" to="signup-page" />
 <Route name="signup-page" path="/:lang/welcome" handler={SignUpPage} />

When I go on /fr, I'm redirected on /signup-page, not on /fr/welcome has expected.

    <Route path="news/page/:page" name="newsLanding" component={ require('./components/News/Landing') } />
    <Route path="news/:slug" name="newsDetail" component={ require('./components/News/NewsDetail') } />
    <Redirect from="/news" to="/news/page/1" />

here are my routes run with HashLocation.
<Route name='home' path='/'>
    <Route name='foo'>
      <Route name='bar'></Route>
      <Redirect from='/' to='bar'></Redirect>
    </Route>
    <Redirect from='/' to='foo'></Redirect>
  </Route>

when visiting localhost or localhost#/foo/ it can be redirect to localhost#/foo/bar properly
But localhost#/foo, which should just be equal to localhost#/foo/, didn't work as expected,  the redirect seems not working when the last slash is missing.
The version of react-router is 0.13.3

@kpaxqin 0.13 cares about the trailing slash, do path="foo/?" in your route config to make it optional
@dgrana I can't reproduce, if you could provide a failing test case we can take a closer look, but that's pretty basic functionality.


devel: add k8s 1.18 support

What this PR does / why we need it:
Adds support for K8S_VERSION=1.18 to the devel/cluster/create.sh script, to allow us to enable testing against Kubernetes 1.18.
Release note:
NONE

/area testing
/kind feature

/test pull-cert-manager-e2e-v1-11
/test pull-cert-manager-e2e-v1-12
/test pull-cert-manager-e2e-v1-13
/test pull-cert-manager-e2e-v1-14
/test pull-cert-manager-e2e-v1-15
/test pull-cert-manager-e2e-v1-16

/assign @JoshVanL

/lgtm


Update babel config for new transform format

Issue
When using v1.1.0 of the babel-plugin-react-transform, it throws warnings that the format for transforms is outdated and needs to be updated.
Job Story
N/A
Solution
Update the babel-plugin-react-transform config format to the new, non-deprecated format from upstream. (v1.1.0+)

Thank you!

Should I update the babel plugin to '^1.1.0' in the examples package.json files as well?

Good catch, yes please do!


PHP docker not working on GCE

RancherOS Version: (ros os version)
0.7.1
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
GCE
I have sucessfully installed rancheros 0.7.1 on google cloud compute, and most containers work fine, however Docker images w/ php/apache are not working. They work with HTML, but not php.
Try:
docker run -d -p 80:80 php:apache
OR
docker run -d -p 80:80 k0st/alpine-apache-php
Load an html into the root www directory and everything works fine.
Load a php file (e.g. <?php phpinfo(); ?> ), and it spins and never loads in browser. No useful info in the container's apache error/access logs.
When running both above containers in CoreOS and Ubuntu images on GCE, PHP pages work fine.
Running both containers above in RancherOS installed in virtualbox on my laptop works fine as well w/ php.
Only place it is not working is RancherOS installed on GCE (html pages do work though).
Any thoughts?

wow - this'll be fascinating to track down.

I'm not even sure where to start...

Any thoughts or progress on this? Anyone else experienced a similar issue?

Issue still persists with 0.9.1

@SvenDowideit Any suggestions where I should start working this up or looking into it? I currently use RancherOS for our servers on bare metal and I love it, but we are moving to GoogleCloud, and I would really prefer to stay w/ RancherOS, so I'm trying to work out what's going on, but w/ no obvious errors/logs, I'm at a loss.

I would start with tcpdump on the host; if there's a response sent then tcpdump on the client, otherwise maybe strace of the process on Google  vs somewhere else.

Thanks, I'll start looking into it.


No documentation on how-to

After entering the command:
$result = $MailChimp->get("lists/$list_id/members");
How does one access $result?

$result is a variable containing the result! A good place to start would be to print_r() it to see what's there.


Support page displays error

The support page displays "Not Found
Status 404".

I haven't thought about what should go on the Support page. Maybe some kind of chat service integration or a simple feedback form (which would require viewing and processing pages)

Yes maybe a feedback form could be included and frequently added questions could be added on top of the page.


Arrow keys takes the user to a weird page

@hkirat  is it in production? since the issue still persists


Pusher crashing when tried to subscribe to a channel (Works in simulator only)

I am facing the same issue "Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[PTPusherEventDispatcher addEventListenerForEventNamed:block:queue:]: unrecognized selector sent to instance 0xa6a40b0" when i try to subscribe to a channel.
last week it used to work for simulator and fail for iOS device. But now it fails for both. Please help :(
if it is the compilation problem for the library, Where can i download the latest 1.5 libpusher compiled lib?

Closing as stale


Enable feedback through GitHub.

Addresses #376.

Docs Build status updates of commit 0387bd7:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/quantum-docs-pr, working directory: W:\mnps-s, target branch: master, target branch commit: 39c030284c5b2a8e17cf54369fbfac958660fe77, source commit: 0387bd7a386d04f1b4504e69a9563d9dba7c7534.

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

Docs Build status updates of commit 8b292ba:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/docfx.json
:white_check_mark:Succeeded

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

Docs Build status updates of commit 487476e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/docfx.json
:white_check_mark:Succeeded

articles/docfx.json
:white_check_mark:Succeeded

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

Docs Build status updates of commit 8246a10:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/docfx.json
:white_check_mark:Succeeded

articles/docfx.json
:white_check_mark:Succeeded

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

Docs Build status updates of commit e3713a3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/docfx.json
:white_check_mark:Succeeded

articles/docfx.json
:white_check_mark:Succeeded

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


Shaking text in body while hovering over nav bar items

Once a page loading completes hovering over nav bar items makes the text in the body of the page shake. This is most notable in "Tools" page.

@abhaymaniyar  Could you post a gif or a video of this?

Closing this for now 😃


Add get all rewriter rest endpoint #76

And add after method to fix flanky tests.
Response format is now:
{
  "responseHeader": {
    "status": 0,
    "QTime": 1
  },
  "response": {
    "rewriters": {
      "commonrules1": {
        "class": "querqy.solr.rewriter.commonrules.CommonRulesRewriterFactory",
        "config": {
          "rules": "notebook =>\nSYNONYM: laptop"
        }
      }
    }
  }
}

The format is also prepared to add meta data into the reponse element.

Merged via ae074db

Merged via ae074db


⚠ ClamAV has degraded performance

In 3f22c62, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 70 ms

Resolved: ClamAV performance has improved in 3b7232d.


CH592

Just curious... Will the CH592 also work? Or does that require different code.
WeAct CH592: https://a.aliexpress.com/_mNbe7W4
I was going to buy the 582 but the 58 2 seems cheaper and newer.
Awesome project btw! I hope to try it out

I'm curious about this too. Looking at their examples, it seems like the code is largely the same. The pre-compiled BLE stack has a different filename ("CH592"), but the API looks the same.
My guess is that it would work by just replacing the BLE stack, startup.S file, and linker. But again, just a guess. I don't have a CH592 board yet to verify this.
P.S. This project wouldn't be possible without your Zig blinky, so thank you!!

Wow awesome as. My end goal was to create keyboard firmware too! But I didn't understand how to do this kind of programming, so it was too hard for me 😅
I will be so happy to use your firmware 👍👍
Currently I have a Corne Keyboard, but thinking to design a new keyboard with CH582 or CH592

Awesome, go for it!
I'd just advise not to use B16-23 for row pins because there are no GPIO interrupts there (for less power consumption). For columns, any pin's good.

Looking at their examples, it seems like the code is largely the same. The pre-compiled BLE stack has a different filename ("CH592"), but the API looks the same.
My guess is that it would work by just replacing the BLE stack, startup.S file, and linker. But again, just a guess. I don't have a CH592 board yet to verify this.

I had a try at this. https://github.com/rgoulter/kirei/commits/try-ch592/

I wondered whether the CH58x code would run on the CH592 board. It did not. (The code that runs Kirei on CH582 didn't run Kirei on CH592).

I'd hoped that replacing 58x-specific stuff would be enough. -- I replaced the startup.S, link.ld, replaced the ch58x/lib headers/libraries from the CH592 EVT; some small adjustments were needed to get things to build.

While I was able to get the LED blinking in a loop on the CH592, the code tripped up when calling c.GAPRole_PeripheralInit() in initPeripheralRole() in ble.zig. -- With a bit of printf debugging, I could observe print statements up until that point, but nothing after.
If I understood why, I'd be able to avoid the problem.
I think maybe the configuration of BLE in the CH592 EVT is slightly different than the EVT that the Kirei CH58x platform ported over.

Slight progress on this. https://github.com/rgoulter/kirei/commit/e49d0ada8c00cdae62f61c97fb52551207f574e4
I noticed that the CH592 EVT includes BLE/LIB/ble_task_scheduler.S. I noticed that the BLE Peripheral example requires this to build, and that the CH58x EVT doesn't include this file.
This relies on a g_LLE_IRQLibHandlerLocation, g_LLE_IRQLibHandlerLocation = (uint32_t)LLE_IRQLibHandler. (In the EVT, this is implemented in the CH59x_BLEInit function in BLE/HAL/mcu.c.
The assembly file has .func/.endfunc` directives, which are apparently GNU specific.
With that, the BLE peripheral is at least discoverable; although still doesn't successfully connect. (UART1 output shows ble_dev: GAP state connected, quickly followed by disconnected).

While trying to narrow down on differences between the kirei code above, and BLE code from the WCH EVT: I noticed that the Peripheral example from the CH592 EVT doesn't work if I change its config.h HAL_SLEEP to true. (More specifically: by default, it's false, and I can connect to "Simple Peripheral"; but, by using HAL_SLEEP, I'm unable to connect to "Simple Peripheral").
I tried seeing if that was a smoking gun for the above; after commenting out cfg.idleCB = ... on the kirei code I linked above ... and removing all the BLE/GATT services (battery, device info, HID), then the zig code works as a simple peripheral example.


Don't simplify case expressions containing custom type constructors

Fixes #36
The rule now doesn't simplify case expressions that refer to a custom type defined in the project, though it will keep doing this for custom types that come from dependencies (Just _ -> ...) as well as patterns like 1 ->, [] ->, etc.
@janiczek @stefan-wullems @lydell if you'd be willing to try this change and tell me what the experience is like, that would be great :pray:
If you configured the rule to use ignoreCaseOfForTypes, you will likely get new global errors.
elm-review --template jfmengels/elm-review-simplify/preview#case-of-constructors

The status at work is:

We want to use the simplify rule, but it wanting to simplify many case-ofs has made us not enable the rule, because there are too many places where it’s unclear how we should solve it. It seems to be 15 places, which right now doesn’t seem like that much, but apparently enough for us to never having enabled the rule.
I ran this PR one the code base. It’s perfect! All the simplifications suggested were relevant and good, and it still found a case foo of Just _ -> bar Nothing -> bar case and simplified it.
It found zero places where we cased on other custom types from dependencies unnecessarily. All of our “unnecessary” case-ofs seem to be of types from our own code.
I don’t have use for the option to exclude some custom types.

I’m excited! Apart from simplifying some things, the rule also found some conditions like questionId == questionId && which I need to take a look at! With this change we can enable this rule at work and get these benefits all the time.


"Displaying" selector misleading when viewing Details chart

From a conversation with @dlaliberte, it is misleading that changing the Displaying selector doesn't change the a Details chart being displayed.
suggestion: changing the Displaying selector to also change the Details chart

One problem/conflict with this idea is we should also update the Displaying selector to show whatever is showing in the Details chart.  So when the user clicks the magnifier icon for one of the small multiples, this would not only show that indicator in the Details chart but also change the Displaying selector, and maybe unexpected side effect is that this will then change what is shown on the map.

@bweaver-work can you take a screenshot and point out what should change?  I'm have trouble envisioning this issue.

There are three displays of the indicator that should remain in sync, which you can see in this screenshot.

The "Displaying" selector in the upper left corner can be changed to (currently) change what is displayed on the map.
The small multiple for the same indicator shows a magnifying glass icon.  You can mouseover other small multiple charts to see the magnifying glass icon for each one.
The Detail View displays the details of the small multiple that you clicked on.

Changing the selected indicator with the "Displaying" selector should update the small multiple and the Detail View, if it is displayed.  Clicking one of the small multiple magnifiers should update both the "Displaying" selector and the Detail View.

Another solution could be to make it more obvious that the Detail View is floating above the map, rather than replacing the map. That could make it more clear that the Displaying selector is changing the Map below, rather than the Detail View above.

Let's close this as obsolete since we're going to change how this works in the redesign.


SkipList unit tests

Write JUnit tests to verify the correctness of our SkipList implementation

Closed by #2 and #7


be able to use the specified edoclet in deps

%% rebar.config
{edoc_opts, [
             {doclet, edown_doclet}
           ]}.
{deps, [
             {edown, ".*", {git, "git://github.com/uwiger/edown.git", {branch, "master"}}}
           ]}.

This becomes available.

Cool. Will merge when tests finish.

Oops, my bad, @soranoba you should add a line to cleanup the code path at the end, like https://github.com/rebar/rebar3/blob/master/src/rebar_prv_compile.erl#L60


Added support of autocert (lestencrypt) and encrypted sensitive files on disk

This PR includes some minor fixes and updates as well as two important new features, both optional:

Added optional autocert support as embedded feature of the binary. No need to use nginx to get HTTPS working anymore! Just run and configure domain name and it will do everything for you using autocert library from golang.org/x/crypto.
Added optional encryption for invocies.macaroon, tls.cert and files stored by autocert. Files are encrypted with a password, which should be entered manually in the terminal every time the binary is launched. If the enemy gets access to the server's hard drive, but not RAM, it won't get anything valuable.

Alternatively you can specify file path in password_file field. You can specify path to docker secret or a similar secure file.
Alternatively specify password_file: NO PASSWORD to disable encryption completely.

I updated instructions in README and tested that both new features work.
Important new dependencies:

golang.org/x/term to input password from command line
golang.org/x/crypto/acme/autocert to use Let's Encrypt
gitlab.com/starius/encrypt-autocert-cache to store autocert's files encrypted
github.com/Luzifer/go-openssl/v4 to decrypt files invocies.macaroon and tls.cert encrypted using openssl
golang.org/x/crypto/hkdf to produce HKDF derived key from password (used in autocert encryption).

Hi, and thanks very much for the contribution!
I like the idea of adding autocert support :+1:
but i'm not sure adding an encryption layer is necessary here. If a user wishes to keep their sensitive files secure against exposure to physical theft, they should be mounting those files on a volume with full-disk encryption. If they are concerned about other programs on the same machine having access, then those files should be chmoded and chowned with secure permissions. I don't think lndaddrd is the right place for an encryption layer, as it's meant to be as lightweight as possible (fewer dependencies = easier to audit and safer against supply chain attacks).
With that said, if you're open to splitting the encryption changes out (possibly into a separate PR if you'd like to continue discussion), we can move forward with autocert support in this PR

Hi! I removed the commit adding encryption and tested it.
I would like to open another PR re-adding encryption in the future.


(Sometimes) EMI does not load

As the title says. This time, I managed to organize the log into a single file. There is both the client log and the server log (which is localhost). In this specific log, EMI did not load even after 20 minutes. I mention this because sometimes it still shows me the message "EMI experienced a critical exception...", but it still loads afterwards.
Client log: https://mclo.gs/WImpRUk
Server log: https://mclo.gs/opOkag4 (sending this because I don't know if it might be useful. The times don't match because the server has been open for some time).

I believe this is due to either a self mutating item, or a bug in Nature's Aura which throws exceptions in its JEI subtype interpreter, please report this to Nature's Aura.

This issue seems to be on EMIs side, as the subtype handling code assumes there's a subtype with no NBT data to set as a default comparison. This works for most items, but not for Nature's Aura ItemEffectPowder, as all subtypes have some NBT to mark which specific type they are.


Mousedrag doesn't release the slider after mouseUp

Issue description:
Currently having an issue (with both horizontal and vertical axis) where if you click one of the items in the slider it keeps dragging the slider. Seems as it isn't releasing it after mouseUp, see the gif below. In the gif I am not holding down the mouse but I am releasing it and it gets stuck. I've tried swipeAngle but that doesn't seem to help.
Demo link/slider setting:

Tiny-slider version:   2.6.0
Browser name && version:   Chrome (latest)
OS name && version:   Windows 10

I'm experiencing the same issue - the mouse remains 'stuck' and the carousel continues to drag even though I've clicked and released.
options: {
  items: 2,
  edgePadding: 0,
  slideBy: 1,
  loop: false,
  mouseDrag: true,
  nav: false,
  responsive: {
    577: {
      items: 3,
      slideBy: 3,
    },
    992: {
      edgePadding: 40,
      items: 3,
      slideBy: 3,
    }
  }
}

Any idea here @ganlanyuan ?

Will check this shortly.

You are fantastic!

Hi, May I know your slider options?

@ganlanyuan
options: {
  axis: 'vertical',
  loop: false,
  mouseDrag: true,
  items: 3,
  controlsText: ['',''],
  gutter: 20,
  nav:  true,
  swipeAngle: false // tried everything here but same issue occurs
  }
}

Cheers! I tried it out bit it kinda made it worse :/

Could you create a demo on codepen or somewhere?
Because I actually couldn't reproduce the issue on my side.

@ganlanyuan Thank you for the raf branch, I had the same bug on this configuration:
Tiny-slider version: 2.6.0
Browser name && version: Chrome (latest)
OS name && version: Windows 7
But with the raf branch code all is Ok.

@ganlanyuan Unfortunately, more extensive testing has shown that the error still exists.
Error occurs when mouseDrag: true. Then mouse click on the slider element, the elements of the slider are move forward.

@ganlanyuan ,
Any update on the issue?

Here is the codepen https://codepen.io/ssinghi/pen/OZqWXp

@ganlanyuan Seems to be working! Fantastic!

Can confirm in v2.8.1 and 2.8.2 this bug is present. Had to disable mouseDrag for the time being. Ocurring on a div element with an image background.

@DMCK96 Could you make a demo?
I didn't see this issue (on div elements with background image) when tested locally.

I'm experiencing the same issue on version 2.8.5 with background images on the slides and the following settings?
{           items: 4,           lazyLoad: true,           loop: false,           nav: false,           controls: false,           arrows: false,           container: this.navSliderNode,           mouseDrag: true,           fixedWidth: 70,           gutter: 8,           responsive: {             768: {                 fixedWidth: 140,             }, }
HTML structure is:
`

...
`
I assume the script is listening for a mouse up / mouse down function, but is there any possibility that the propagation is being stopped by another event somewhere? The issue occurs about 80% of the time I use the slider, so 20% of the time it works correctly.

Update, So I incorrectly updated my version of tiny slider before, after actually updating the slider version to the latest things started to work for my slider... but the issue appeared on another slider.
The new broken slider was functioning before the update. I did some testing with the latest version of the slider and I realized the issue was that my slider had a full width and height  tag, so I am assuming there were event conflicts.
Digging deeper, I started looking at the onPanStart method, which uses on the preventDefaultBehavior function upon certain conditions. I adjusted the conditional (!isTouchEvent(e) && ['img', 'a'].indexOf(getLowerCaseNodeName(getTarget(e))) >= 0) so preventDefaultBehavior would be called every time the event is not a touch event. This seemed to be fix the issue, and all of my sliders are running as expected.
@ganlanyuan, Can you foresee the removal of  && ['img', 'a'].indexOf(getLowerCaseNodeName(getTarget(e))) >= 0 causing any issues?
Also, do you have instructions on how to get the build running. I tried npm install, bower install and then gulp min found out there were a handful of missing packages and a missing /www/package.json file


Set the range of value in Single Input of type range

Are you requesting a feature, reporting a bug or ask a question?
I am asking a question
What is the current behavior?
Editing the question I can't find a place to set the range of values to a range type input. And I can't find an example too.
What is the expected behavior?
I want to know where I put the range of number in my input with type range.
How would you reproduce the current behavior (if this is a bug)?
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
your_code_here

Specify your

browser: Chrome
browser version: 58.0.3029.110
surveyjs platform (angular or react or jquery or knockout or vue): jquey
surveyjs version: 0.12.16

@andrewtelnov can you help me in this silly question too? Thanks

@GuiAfonso Sure, use the rateValues property:
http://surveyjs.org/builder/#48323384-676a-46b6-b4be-8c10c8b5c0fb

Thanks again @andrewtelnov, I'am already using rateValues in other question. Single input of type range don't have a rateValues tab.
http://surveyjs.org/builder/#48323384-676a-46b6-b4be-8c10c8b5c0fb
I add a question in the above link. Can you see please?

@GuiAfonso Sorry, I do not get you. Are you talking about dropdown question?
http://surveyjs.org/examples/jquery/questiontype-dropdown/

@andrewtelnov If I add a simple input, and change that input to range type (it will change the input to a slider) how i add the range of that slider(the interval of values). In this case, I don't have a rateValues tab.

@GuiAfonso Yes, I got you finally. Sorry about that.
We will add into text 3 properties: rangeMin, rangeMax and rangeStep.
Here is their description: https://www.w3schools.com/jsref/dom_obj_range.asp
Thank you,
Andrew

Hey there.
How is the state about adding this feature ?
I still cannot find or see it ... or did you add it somewhere else?
Also it would be nice, if the user can see directly, which value he is currently sliding and what are the Minimum, Maximum.
Best regards,
Julian

@JayDLX Sorry, that I did write back to you. After the discussion, we decided that it is probably better introduce a new range question. The only problem we have with it, that it will look and have different behavior in different browsers. As result we did not come to any solution.
Will the custom solution work for you?
https://www.surveyjs.io/Examples/Library/?id=custom-widget-nouislider
We may update the demo and add minimum, maximum and some other properties.
Thank you,
Andrew


FileList v4.3.2

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

This command cannot be run due to the error: The specified executable is not a valid application for this OS platform..

Looks like the manifest is broken, so the ZIP-file is not being extracted correctly. We'll check on that and try to push it again.


Allow changing between "all", "partial" and "none" spot-instance-config.

Currently, the cluster UI shows a simple button that allows "enable" and "disable" of the spot-instance feature. This should be changed to show all the three possible options "All", "Partial" and "None" and the user should be allowed to choose any of these. Whatever the option is selected, it should be sent via json to axops (which forwards the request to axmon). The option that is chosen should be sent as the value of the "asgs" json field in the http request.
The request should be like this if the user chooses "all".
 curl -H "Content-Type: application/json" -X PUT -d '{"asgs":"all"}' http://localhost:8901/v1/axmon/cluster/spot_instance_config

Earlier, the only key value pair sent was "enabled" : "True" or "False".
Please use buttons group to represent selected state:

PR: https://github.com/argoproj/argo/pull/173


implement figurl BoxLayout, Altair

Fixes #107

See this example: https://github.com/magland/sortingview/blob/magland/issue107/devel/figurl_box_layout.py
which generates the following layout of Altair plots:

I chose altair for the charts because it is based on a very nice declarative plot system called Vega/Vega-Lite which interoperates between javascript and python (and there is a react-vega npm library). See https://vega.github.io/vega-lite/


Fix domain_word to return correct output in ru locale

domain_word returns incorrect value while locale is set to 'ru'

you make my day


Toggl Button popup not showing inside a trello card

OS version: Windows 10
Browser version: 76.0.3809.132
Extension version: Version 1.40.7

Relevant integration (if any):
Regular Trello integration
🐛 Describe the bug
I have the button inside trello but when I click on it it just starts a timer, no popup:

Expected behaviour
A popup allowing me to change the time entry description should show

I was unable to replicate this issue. I tried in both Firefox and Chrome with the versions currently in their respective web stores.

Can I work on it.

Hey @Whizkevina, you're most welcome to work on this if it's still an issue! :)
@VeljkoTN can you let us know if you're still experiencing this? I tried to reproduce it as well but wasn't able to.

Not known to be an issue in the current version. Please re-open if it comes up again.


Set the HTML title to something more descriptive than just "GoTTY"

Suggestion: "GoTTY - #{command} (#{hostname})"

Or a command line option to pass the title (perhaps with tokens)?

Sounds good. I'll add a format option.

👍

The current pre-release (master HEAD) shows   "GoTTY - #{command} (#{hostname})" in the window title. You can specify the format of window titles by providing --window-format option.
Let me know if there are any other parameters that can useful for window titles.


1.16.5 spongeforge - ModList was loaded too early

latest.log
As the title said.
When i add in spongeforge to mods folder i get this and it stops loading. No crash log.
SpongeForge: spongeforge-1.16.5-36.2.5-8.0.0-RC1130-universal.jar

Don't attach log as file in issue next time. Use gist/paste service plz.
You need provide the way to reproduce the issue when you submitting. There is a template when you submit issue in correct repo. SpongeDocs is the repo of docs.spongepowered.org.

Apologies, I usually use paste bin but recently learned i could drag and drop!
To reproduce you could simply go to technic and install Tekxit Journey, Use mods in a server environment and make sure it boots as is and then drag and drop spongeforge into mods folder.
Should provide errors in the current available update.
If not ill update this when i release my next update for that modpack.


gdb server non-stop mode support

This PR adds support for non-stop mode. This feature allows for accessing memory while the target is running.
These changes were tested with command-line arm-none-eabi-gdb version <IP_ADDRESS>50604 from GNU ARM Embedded 2015q2. To enable non-stop mode, issue the set non-stop on command before connecting to the gdb server. Note that you need to use continue& to run the target and still have gdb command access.
Eclipse supposedly has support for non-stop mode. However, it doesn't seem to work at all. Setting this preference doesn't actually cause non-stop mode to be requested to the gdb server.

Rebased onto latest master.

What commands can be run while the target is running?  All of them?  If so, it seems like this could cause some undefined behavior and exceptions.

Being able to access memory while the target is running is a major feature of the Cortex-M debug architecture. So not being able to make use of this feature from gdb is an issue. Erich Styger has said that many people are asking for it in KDS, since it was available in CodeWarrior. Other debug vendors (including Segger) have said they are looking into adding non-stop mode support.
I'm not completely sure what all commands can be run. I know you can't do things like get back traces or view stack frames and local variables of a running thread. The most important thing is that you can read global variables or other memory.
The gdb docs for non-stop mode are here.

I agree, having a non-stop mode in KDS would be incredibly useful.  I use a Lauterbach debugger sometimes and stop mode is a great feature on it.  Did the eclipse version of CodeWarrior support non-stop mode?
If the memory access commands are the ones that primarily get run then that is good news for stability.  Those functions already have error reporting, and are safe to run when the target is executing code.
Also, good work on this patch.  I kinda wrote off non-stop mode as something that would be infeasible to implement.  It looks like you already have it working though :smile:.
Finally, if this patch can wait a couple days I can try it out at work.  Don't feel like you need to wait on me to merge it though.  I did some preliminary testing with GDB and Eclipse yesterday, and after importing signals, everything worked.

I think we should wait until you can try it out! I would really appreciate your help testing.
I had also written off non-stop mode as not very useful until Erich asked about it. I'm pretty sure it was the Eclipse version of CodeWarrior that he was referencing, but I don't think CW uses gdb. It has its own debug infrastructure. (They still use it for the LayerScape chips with the Cortex-A5x cores.)
Please let me know if you can get non-stop mode to work with Eclipse. It works fine with command-line gdb, but Eclipse seems to ignore the non-stop mode preference and gets confused if you force non-stop to be enabled via set non-stop on. I'm not sure if it has something to do with the GNU ARM Eclipse plugin.