NaN BTC: float division by zero

Proxying bug report given to the OpenBazaar helpdesk:

I'm getting prices shown as "NaN BTC" and an error when I try to purchase: "Reason: float division by zero"

Ok, a second person on the helpdesk has this issue.

Hi! I really want a sticker but I cannot order one! It just shows NaN BTC and I receive an error (floating point division by 0). Is it out of stock or is just an error on my end? The stickers are not limited are they?

The error seems to be related to MacOS. I tried OB on WIN and did not have any issue.

Confirmed by multiple reports. Haven't gotten many details on how to replicate though.

We think this may be connected to an issue with the bitcoinaverages api call failing. Can you find out if the same people are also unable to select a currency other than BTC?

A screen cap of the error message would be helpful too, we're not sure when it's actually occurring.

Seems to be related to OB stickers.

How come when I try to buy a OB sticker it says NaN BTC

I'm getting this error when  creating a new listing, I also received the error "your local currency not available" (USD).

This was fixed on the client side in #1252
The server part of this issue is being tracked at https://github.com/OpenBazaar/OpenBazaar-Server/issues/328

I am stilling seeing "NaN BTC" on many of the listings.   I am using an iMac.

@More-decentral what version of the app are you using?

@jjeffryes, I am running 1.1.3 on OSX 10.10.5

@More-decentral are you using the installer, or did you manually install the client?
This problem is caused by an outdated Python library on your Mac. Try the following steps:

Open the terminal and type: xcode-select --install
ruby -e "($curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew update
brew doctor
brew install openssl
brew install libffi
brew install python
sudo env LDFLAGS="-L$(brew --prefix openssl)/lib" CFLAGS="-I$(brew --prefix openssl)/include" pip install cryptography

@jjeffryes,  I downloaded the client from the OB website directly.  How to use the installer?
I did update Python library on Mac.  Now no more "NaN BTC" on the listings.   Thank you.

@More-decentral you should be able to double click on the installer after downloading it. But it sounds like you won't need to.

@jjeffryes followed your instructions, and now NaN does not appear any more. Running OSX 10.10.5.
worked better when using /usr/bin/ruby - from http://brew.sh instructions

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

Is there a solution to this without require the user to open the Terminal?

@jonasbits great to hear that worked.
For 99% of our users, the current installer does this for them and everything's fine. We haven't pinned down why some users have a conflict. Possibly it's from other software that uses the same OpenSSL library but uses a different version.

Even with latest update, OB 1.1.4, all items that I want to buy dispaly NaN BTC as price.  OS X El Capitan, latest update, late 2014 iMac.
I download the official .dmg and drag it to the Applications folder, even deleting the OpenBazaar folder in Library/Application Support to start over with same result.
Please advise.
Thank you!

@smokebox46and2 have you tried the manual steps listed above?

@jjeffryes
Thanks for the reply.
I get a 'command unrecognized' for all commands after the xcode command and install.
This command, ruby -e "($curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)", fails

maybe the ruby components are missing?

@smokebox46and2  try
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
per the suggestion from @jonasbits

I think pyinstaller does something curious where if it thinks it finds python locally installed it will go ahead and use that first and if it's an older version it causes problems. I'm not sure yet why it wouldn't just use the self-contained version.

@jjeffryes
apologies, i didn't notice that.  I'll try that when I get home and report back.
Thanks again OB and community!

@jjeffryes @hoffmabc
It worked!
However, I had to leave off the 'pip install cryptography' part of the last command as it wasn't recognized.  Hopefully it's not detrimental to leave that part off...
Thanks again

I see this bug has been around for a while... Just installed openbazaar 1.1.7 on OSX 10.11.4 and seeing most prices in NaN.  My install was from this link:  https://www.openbazaar.org/download.html  which did not have an "install" process but rather the common on mac "drag to applications folder" process.  I'm sure I could follow the terminal instructions above, but at this point Im more intersted in seeing a solution for the non-terminal friendly masses...  Is there any debug info that would be helpful that I can provide?

I've reopened this issue because while we have a solution to fix the problem if they encounter it, the problem is still occurring for new users. Moreover, the fix that we have involves users digging into the terminal etc, which is unfriendly to mainstream users.
Let's get to the bottom of this and fix the root problem, and then we can close this issue.

Of course, let's not accidentally hit the close button :laughing:

Hi All,
I had the Nan btc problem on an imac running yosemite 10.10.5 because some of my music creation software was not yet compatible with Sierra and El Capitan. I was forced to upgrade to Sierra so I could install XTools.
I have never used a command prompt before. Then I followed jjefryes instructions and nothing happened. Found the comment from jonasbits a bit further down, so I nervously pasted: /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" into the terminal and hit enter, and it worked.
The one by one I pasted in the other commands and hit enter:
brew update
brew doctor
brew install openssl
brew install libffi
brew install python
Nan BTC gone in openbazaar and miraculously my handle appeared as well and a short time later on DUO and Bazaarbay.
My question is what does this last line of code do?:
sudo env LDFLAGS="-L$(brew --prefix openssl)/lib" CFLAGS="-I$(brew --prefix openssl)/include" pip install cryptography
I haven't tried it yet.
Regards Neal

Hi All,
I had the Nan btc problem on an imac running yosemite 10.10.5 because some of my music creation software was not yet compatible with Sierra and El Capitan. I was forced to upgrade to Sierra so I could install XTools.
I have never used a command prompt before. Then I followed jjefryes instructions and nothing happened. Found the comment from jonasbits a bit further down, so I nervously pasted: /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" into the terminal and hit enter, and it worked.
The one by one I pasted in the other commands and hit enter:
brew update
brew doctor
brew install openssl
brew install libffi
brew install python
Nan BTC gone in openbazaar and miraculously my handle appeared as well and a short time later on DUO and Bazaarbay.
My question is what does this last line of code do?:
sudo env LDFLAGS="-L$(brew --prefix openssl)/lib" CFLAGS="-I$(brew --prefix openssl)/include" pip install cryptography
I haven't tried it yet.
Regards Neal

I encountered this problem on OSX 10.11.6, with OpenBazaar-Client 1.1.7, OpenBazaar-Server commit 903ac7f157aa6a67c719affcbcacef1b325b09d1 (v0.2.3-rc4).
The problem came up when I upgraded OpenBazaar-Server to v0.2.3-rc4. Previously I was using OpenBazaar-Server commit da0c261c5b303c558075cd4666d25650d45a7509 and it did not have this problem.

Did you ensure to use python 2.7.9 or higher?

Pardon me, did you make sure to use Python 2.7.9 or higher.


Revive coverage testing, first steps

First step in reviving unit test coverage.
Update bisect_ppx in opam.export (and some other libraries).
Add script to generate coverage files. Update Makefile to invoke that script, which generates coverage files for all libraries. You can call the script with just the libraries you want coverage for, if desired.
Change -conditional flag in dune preprocessing clauses to --conditional.
This PR addresses some of the tasks listed in #6090.

By coincidence I was just researching bisect_ppx.  If I understand the source (register.ml), the --conditional flag unconditionally enables the lib.  Similarly the env var BISECT_ENABLE=YES unconditionally enables.
Plus it looks like the plan is to deprecate --conditional: https://github.com/aantron/bisect_ppx/issues/323

If I understand the source (register.ml), the --conditional flag unconditionally enables the lib. Similarly the env var BISECT_ENABLE=YES unconditionally enables.

I don't believe so. The code reads:
("--conditional",
  Arg.Set conditional,
  " Instrument only when BISECT_ENABLE is YES");

If --conditional is given, then instrumentation only happens when the env var is set.
That's the way it's worked up to now, except for the flag name.
Now that this PR is merged, I rebuilt from develop. I saw a small number (5ish) of .coverage files, in cases where the preprocessing clause did not include bisect_ppx. I'll create a fix PR for those.

Plus it looks like the plan is to deprecate --conditional: aantron/bisect_ppx#323

It will be easy enough to update the dune files and scripts when things change. The example in the dune docs that uses --instrument-with (or some such), which I believe is the plan, doesn't currently work.

On Fri, Sep 25, 2020 at 8:02 PM psteckler<EMAIL_ADDRESS>wrote:

If I understand the source (register.ml
https://github.com/aantron/bisect_ppx/blob/master/src/ppx/register.ml?rgh-link-date=2020-09-26T00%3A40%3A04Z),
the --conditional flag unconditionally enables the lib. Similarly the
env var BISECT_ENABLE=YES unconditionally enables.
I don't believe so. The code reads:
("--conditional",
Arg.Set conditional,
" Instrument only when BISECT_ENABLE is YES");
If --conditional is given, then instrumentation only happens when the env
var is set.

Oh good grief.  I misread  match !conditional with - OCaml uses '!' as
the defer operator, not the negation operator.  How embarrassing/annoying!
Sorry about the noise.
G


@catppuccin_window_*_separator options are not working

Is there an existing issue outlining your problem?

[x] I have searched the existing issues and they do not solve my problem.

Describe your problem.
@catppuccin_window_left_separator, @catppuccin_window_middle_separator and @catppuccin_window_right_separator are being completely ignored. The current variants @catppuccin_current_window_left_separator, @catppuccin_current_window_middle_separator and @catppuccin_current_window_right_separator are working as expected.
Paste your configuration.
set -g @catppuccin_window_left_separator "L"
set -g @catppuccin_window_right_separator "R"
set -g @catppuccin_window_middle_separator "M"

set -g @catppuccin_window_current_left_separator "L"
set -g @catppuccin_window_current_right_separator "R"
set -g @catppuccin_window_current_middle_separator "M"

Attach screenshots.

What tmux version are you seeing the issue on?
tmux 3.5
Any additional comments?
This was working on v0.3.0.

does set -g @catppuccin_window_status_style "rounded" work for you? Literally just came to check the issues cause I cant seem to get it working

Does it work if you set the window status style to "custom"?

@matthiasPOE set -g @catppuccin_window_status_style "rounded" does indeed work for me!
@kjnsn set -g @catppuccin_window_status_style "custom" did the trick! Is this expected behaviour?

Kind of the same problem here. For this configuration I get the following:


[Docs]: torch.distributed.launch is deprecated, torchrun should be recommended

Describe the bug
Many places in our documentation recommends to use torch.distributed.launch.
However, that option is being deprecated by upstream PyTorch: https://pytorch.org/docs/stable/distributed.html#launch-utility
The recommendation is to use torchrun, which is supposed to be functionally equivalent: https://pytorch.org/docs/stable/elastic/run.html#launcher-api
Expected behaviour
SpeechBrain should recommend using torchrun in all the documentation - but we should check which version introduced it, and whether we still support versions that might not have it.
Plus, we should check whether we might encounter any issues with that migration.
Quite a lot of the documentation in SB still recommends using the deprecated option, including the multigpu docs and some recipe READMEs.
To Reproduce
Run any SB training job with DDP enabled (as documented in multigpu docs)
Versions
At the time of writing, the develop tip e353e95 is affected.
Relevant log output
FutureWarning: The module torch.distributed.launch is deprecated
and will be removed in future. Use torchrun.
Note that --use_env is set by default in torchrun.
If your script expects `--local_rank` argument to be set, please
change it to read from `os.environ['LOCAL_RANK']` instead. See
https://pytorch.org/docs/stable/distributed.html#launch-utility for
further instructions

Additional context
No response

Solved in #2158. Thanks @asumagic :)


too many callbacks

sry but .. the delete button does not work .. no log info .. also not in debug mode.. after press the button

you have a bug in admin.. this is a message after press the delete button

Could you try 2.2.7 from Github ?

ahhhh... thx


lua 5.2 does not ship "loadstring" but on debian it does

Issue description
On NixOS, I get this with lua 5.2:
$ lua
Lua 5.2.3  Copyright (C) 1994-2013 Lua.org, PUC-Rio
> loadstring("1 + 1")
stdin:1: attempt to call global 'loadstring' (a nil value)
stack traceback:
	stdin:1: in main chunk
	[C]: in ?

On debian (jessy and stretch) it works, though:
deagol ~ $ lua5.2
   Lua 5.2.3  Copyright (C) 1994-2013 Lua.org, PUC-Rio
   > loadstring( "1 + 1" )
   >
   > loadstring( "print( 'OK')" )()
   OK

(see also https://github.com/lumail/lumail/issues/348#issuecomment-372133003)
It seems that either debian ships some additional lua scripts which "automagically" fix this, or we do something wrong?
Technical details

system: "x86_64-linux"
host os: Linux 4.14.19, NixOS, 18.03pre130932.cc4677c36ee (Impala)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.0
channels(root): "nixos-18.03pre130932.cc4677c36ee"
channels(m): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Pinging lua people: @lblasc

Hm, maybe you want lua_5_2_compat?

yep you need lua 5.2 with compatibility enabled.

Debian builds lua5.2 with:
CFLAGS= -Wall -Wextra -DLUA_COMPAT_ALL $(SYSCFLAGS) $(MYCFLAGS)
CXXFLAGS= -Wall -Wextra -DLUA_COMPAT_ALL $(SYSCFLAGS) $(MYCXXFLAGS)
Nix:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/interpreters/lua-5/5.2.nix#L1
It is a option, so you should override lua package to enable compat just for this package, or use lua5.1/luajit.

Wait, why override manually when lua_5_2_compat is already provided?

Thanks for clearing that for me.
I filed an update of the package in https://github.com/NixOS/nixpkgs/pull/32710 which changes lua to 5.1 - This issue documents how to use 5.2, so I guess it is resolved!
Thank you all!


[BUG] instagrapi.exceptions.MediaNotFound: Media not found or unavailable

Hello writer, my English is not very good, the following is from the translation.
Your example:
->>> cl.story_download(cl.story_pk_from_url('https://www.instagram.com/stories/adw0rd/2581281926631793076/'))
My call:
->>> c.story_download(c.story_pk_from_url('https://www.instagram.com/stories/highlights/18235246471094746/'))
I compared the URL and found that there was something wrong with the parameter in the penultimate path.  When it was replaced by an ins user, the ins indicated that the link was damaged.
https://www.instagram.com/stories/l.ovely_kim/18006184243535317/
Destination URL：https://www.instagram.com/stories/highlights/18006184243535317/
Looking forward to your reply, Thanks♪(･ω･)ﾉ
Report an error:
Traceback (most recent call last):
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/media.py", line 259, in media_info
media = self.media_info_gql(media_pk)
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/media.py", line 208, in media_info_gql
raise MediaNotFound(media_pk=media_pk, **data)
instagrapi.exceptions.MediaNotFound: Not found ({'media_pk': '18235246471094746', 'shortcode_media': None})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/private.py", line 313, in _send_private_request
response.raise_for_status()
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/requests/models.py", line 1021, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://i.instagram.com/api/v1/media/18235246471094746/info/
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/media.py", line 230, in media_info_v1
result = self.private_request(f"media/{media_pk}/info/")
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/private.py", line 461, in private_request
raise e
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/private.py", line 446, in private_request
self._send_private_request(endpoint, **kwargs)
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/private.py", line 368, in _send_private_request
raise UnknownError(**last_json)
instagrapi.exceptions.UnknownError: Media not found or unavailable
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/story.py", line 271, in story_download
story = self.story_info(story_pk)
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/story.py", line 92, in story_info
story = self.story_info_v1(story_pk)
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/story.py", line 63, in story_info_v1
story_id = self.media_id(story_pk)
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/media.py", line 57, in media_id
user = self.media_user(media_id)
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/media.py", line 372, in media_user
return self.media_info(media_pk).user
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/media.py", line 269, in media_info
media = self.media_info_v1(media_pk)
File "/InsSendMessage/098f6bcd4621d373cade4e832627b4f6_venv/lib/python3.9/site-packages/instagrapi/mixins/media.py", line 235, in media_info_v1
raise MediaNotFound(e, media_pk=media_pk, **self.last_json)
instagrapi.exceptions.MediaNotFound: Media not found or unavailable

I am a clown


Support cross-database join within same connection for SDK[FEATURE]

Is your feature request related to a problem? Please describe.
In Tableau 2023.1 a new feature for Snowflake was released that the cross database join is not done by Hyper, but the join query is pushed down to the server side for fast processing: https://www.tableau.com/products/new-features#item-96392.
We wonder if the same capability can be introduced to the SDK as well.
Describe the solution you'd like
Support cross-database join in one connection
Describe alternatives you've considered
Current solution which involve Hyper is too slow, if we can push the query down to our server it will be much faster.
About You
Name: Eric Wang
Company: Databricks

Internal tracking: W-13652666


How to set directory or file to be watched without relying on a previous task

Hello,
How can I watch a folder or file without pipe()-ing livereload to a previous task.
I would like to watch a folder or file wihout running a new task:
Something like this, no sass or css file before.
gulp.task('livereload',function()
{
livereload({basePath:DIST_FOLDER,start:true});
livereload.listen();
});
^ That's not a working example, it's for illustration.
Note: Migrated from https://github.com/vohof/gulp-livereload/issues/103.

If you just want to watch the files within your DIST_FOLDER, you'll have to create two separate tasks:
const livereload = require('gulp-refresh')

gulp.task('reload', () => {
  livereload.reload()
})

gulp.task('watch', () => {
  livereload.listen()
  gulp.watch(DIST_FOLDER, ['reload'])
})

In this case, DIST_FOLDER could be something like dist/**/*, if your destination folder is called "dist". Does this answer your question?

Please also keep in mind that you shouldn't use both livereload.listen() and the start option together. Why? Because each of them already automatically starts the server, so you just need to use one of them.

Closing this now, since it seems to be solved. Please re-open if not, @Francisc.


[FEATURE] Add a Preloader in the website

Description
Something like this

Screenshots
No response
🥦 Browser
Opera
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (blank for no)

Hi there we already have a preloader on our website, which is fine. We will be closing this.


Increment version in meson build file

Increment raylib version and so lib version number.
Actually since this is develop branch I guess incrementing already (so we dont forget) cannot hurt.

Hi @jubalh! Thanks for the update! :D


Control does not support transparent background colors.

Describe the bug
When dragging and dropping a SimpleLogTextBox or a JsonLogTextBox control from the Toolbox onto my Form's Designer View, Visual Studio displays an error in a popup saying, "Control does not support transparent background colors." The control is not added to my Form.
To Reproduce
Steps to reproduce the behavior:

Go to 'Toolbox'
Drag a SimpleLogTextBox control onto your Form.
A popup is displayed with the error, "Control does not support transparent background colors."

Expected behavior
The Control is expected to appear on my Form's Designer View, but doesn't.
Screenshots

Desktop (please complete the following information):

Windows 8.1
Visual Studio 2017 Community
My Project 4.6.1 Framework
NuGet packages
Serilog
Serilog.Sinks.ColoredConsole
Serilog.Sinks.Console
Serilog.Sinks.File
Serilog.Sinks.WinForms

Additional Info
I have tried different projects and have tried adding the following line to my Form, with no luck:
this.SetStyle(ControlStyles.SupportsTransparentBackColor, true);

I will try to fix that tomorrow

@TommyS7000  new version release, v2.2.4 you will find the new TransparentSimpleLogTextBox in toolbox. and sample application is also added

Hi. Thanks for your help and for the fast response.
Unfortunately, I am confused about your response. I took a look at the new TransparentSimpleLogTextBox, and I was able to drag and drop it onto my default WinForms project in Visual Studio. However, it has some serious problems with usability and seems very undesirable. I can discuss those issues if you are interested. However, this response is to figure out how to use the previously provided controls. I am guessing, that since you did not fix the other controls, that they are in fact able to be dragged and dropped onto some Windows Forms. Can you explain this issue and why it wasn't fixed and how I can hack my Visual Studio Environment and/or how to hack the default Windows Form provided to me by Visual Studio, in order to be able to drag and drop your controls onto my default Windows Form?
In addition, I will open a feature request for a RichTextBoxLog control that is draggable onto my default Windows Form, has the same usability, and looks like a default RichTextBox. This is the control that I was searching for, when I came across your project. None of the other controls really fit my needs. I hope you will implement it.
Thanks
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, February 18, 2021 11:08 AM, Umair Syed<EMAIL_ADDRESS>wrote:

Closed #4.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

can you write all the issues in points?
you can still fetch all the controls on your windows form where you are settings the backcolor to transparent but you will not be able to run the application it will show you the error that you are previously getting. and if you use the new transparentlog it will be working. but what are the issues you are facing with the new control?

you can also make your own textbox and get the logs into that.
see this sample project
https://github.com/umairsyed613/Serilog.Sinks.WinForms/tree/master/src/Sample/CustomSimpleTextLog
and I have also released a new version with richtextbox control.

give it a start if your problem solves and you find this project worth having a star :)

Hi. Thanks again for a response, but I am still very confused about your responses.
"can you write all the issues in points?"
Yes, but first I would like to have the first issue addressed before moving on to all the other issues. I will attempt to ask for help with the first issue a 3rd time.
"you can still fetch all the controls on your windows form"
I have no idea what this means and I can't find anything whatsoever in Visual Studio that could possibly have anything to do with "fetching."
"your windows form where you are settings the backcolor to transparent"
I have no idea where you got his information, but it didn't come from me. I am not setting ANY color of ANYTHING whatsoever on ANY form in Visual Studio. As I clearly stated, I created a default Windows Forms App (.Net Framework) C# application and added your NuGet package. The controls that I asked about are not able to be dragged and dropped onto the form. Everything else in Visual Studio and everything else in all of my projects is all working correctly without any errors.

I tried the RichTextBoxLogControl and it has the same problems as the TransparentSimpleLogTextBox and is completely unusable. Having a log with invisible text is unprofessional and doesn't work for me. Additionally, this new control does NOT have the same LOOK and feel as a default RichTextBox.
Thanks for your responses, but I simply don't have the time to keep asking and answering the same questions over and over. I will move on to something else.
Thanks and good luck.


ConversionError does not lead to a failed elem in composite indexing

Description
If we modify the SparqlClient to not send a mediatype header in the sparqlNTriplesResponse method:
        val req = Post(endpoint(index), FormData("query" -> q.value))
          // .withHeaders(accept(SparqlNTriples.mediaTypes.toList), additionalHeaders: _*)
          .withHttpCredentials

Then when running the CompositeViewsSpec integration test, we will see ConversionErrors:
2024-02-23 08:13:31 ERROR org.apache.jena.riot - [line: 1, col: 2 ] Expected BNode or IRI: Got: [PREFIXED_NAME:xmlns:owl]
2024-02-23T08:13:31.807949679Z ch.epfl.bluebrain.nexus.delta.rdf.RdfError$ConversionError: Error on the conversion stage 'NTriples to Graph'
2024-02-23T08:13:31.807972304Z Details: [line: 1, col: 2 ] Expected BNode or IRI: Got: [PREFIXED_NAME:xmlns:owl]

but if we check the data base we don't see any failed elems in the composite_offsets table.
Additional context
This reproduces an issue where Delta was making requests to Blazegraph through a load balancer. When the load balancer stopped forwarding the mediatype header, the response was not in the NTriple format, leading to a conversion error. The composite views were getting stuck as soon as they encountered the first non-discarded element.

It looks like as the header gets removed, we get back application/sparql-results+json so it can't be parsed to n-triples
We should test for the content-type in the response before parsing, this way we will get more relevant error messages.
The indexing getting stuck is not really a problem here because the problem comes from an invalid configuration/deployment and not from the resource


SWC panics when calling get_context on v0.75.*

Describe the bug
SWC appears to panic when calling get_context from a Wasm plugin on v0.75.*. When get_context is called on v0.74.*, however, the program does not panic and an Option is returned as expected.
I've created a reproducible repository as well, which, when built, should reproduce the stacktrace output below.
Expected behavior
When get_context is called with &TransformPluginMetadataContextKind, the function is expected to return Option<String> without panicking.
Actual behavior
Program halts and panics, terminating the process, and outputting the following stacktrace:
Panic: PanicInfo { payload: Any { .. }, message: Some(failed to invoke plugin: failed to invoke plugin on 'Some("input.js")'

Caused by:
    index not found), location: Location { file: "C:\\Users\\runneradmin\\.cargo\\registry\\src\\index.crates.io-6f17d22bba15001f\\swc-0.260.41\\src\\plugin.rs", line: 219, col: 14 }, can_unwind: true }
Backtrace:    0: wasmer_vm_imported_memory32_atomic_notify
   1: wasmer_vm_imported_memory32_atomic_notify
   2: canonical_abi_free
   3: wasmer_vm_imported_memory32_atomic_notify
   4: wasmer_vm_imported_memory32_atomic_notify
   5: wasmer_vm_imported_memory32_atomic_notify
   6: wasmer_vm_imported_memory32_atomic_notify
   7: wasmer_vm_imported_memory32_atomic_notify
   8: wasmer_vm_imported_memory32_atomic_notify
   9: canonical_abi_free
  10: wasmer_vm_imported_memory32_atomic_notify
  11: wasmer_vm_imported_memory32_atomic_notify
  12: canonical_abi_free
  13: canonical_abi_free
  14: canonical_abi_free
  15: canonical_abi_free
  16: canonical_abi_free
  17: canonical_abi_free
  18: canonical_abi_free
  19: canonical_abi_free
  20: canonical_abi_free
  21: canonical_abi_free
  22: uv_queue_work
  23: uv_poll_stop
  24: v8::internal::compiler::ToString
  25: BaseThreadInitThunk
  26: RtlUserThreadStart

failed to handle: failed to invoke plugin: failed to invoke plugin on 'Some("input.js")'

Caused by:
    index not found
Error: Failed to compile 1 file with swc.
    at Object.assertCompilationResult (C:\Users\xxx\swc-get-context-issue\example\node_modules\@swc\cli\lib\swc\util.js:149:15)
    at files (C:\Users\xxx\swc-get-context-issue\example\node_modules\@swc\cli\lib\swc\file.js:201:19)
    at async _default (C:\Users\xxx\swc-get-context-issue\example\node_modules\@swc\cli\lib\swc\file.js:220:9)

Version
swc_core v0.75.*, @swc/core ^1.3.56

I tried on my Windows machine, and it works fine:

Can you trigger example on the CI?

Also your config is incorrect:
https://github.com/jcoon97/swc-get-context-issue/blob/ed6b217b145fc8d72da923c3ae94cd9fa10377f7/example/.swcrc#L6
It should be an absolute path.

Updated project to use absolute path and also created a GitHub Action as well. Still getting an error, though it's RuntimeError: unreachable.
Job can be found here, and raw log output can be found here.

Try to disable lto, looks like latest wasmer have some unexpected behavior with lto optimized binaries.
https://github.com/kwonoj/swc-get-context-issue/commit/f2e675093e882f2e5fec4c5c61e2a0b49181cd60
https://github.com/kwonoj/swc-get-context-issue/actions/runs/4900822397/jobs/8751738024


How to use CredentialsPlugin for specific target endpoint ?

Moya Version: 9.0.0
Hello,
i saw the example in the Authentication docs to use the CredentialsPlugin in order to authenticate a specific request with a basic auth header.
I have an enum conforming to TargetType with a case:
public enum APIService: TargetType {
    case createUser(user: User)
    case loginUser(user: User)

Now i want to add a CredentialsPlugin to my provider, but the provider should only send the authentication header when requesting the .loginUser endpoint. Thats why i was trying to switch over the target the credentialsPlugin is providing in the closure. Unfortunately i am getting this error message:
Pattern cannot match values of type 'TargetType'

Here is my setup for the CredentialsPlugin:
CredentialsPlugin { target -> URLCredential? in
    switch target {
    case .loginUser(let user):
        return URLCredential(user: user.email, password: user.password, persistence: .none)
    default:
        return nil
    }
}

I am not quite sure what I am doing wrong. Any hint for me would be much appreciated.
Thanks,
David

Nevermind i just got it working ...
CredentialsPlugin {
            switch $0 {
            case APIService.loginUser(let user):
                return URLCredential(user: user.username, password: user.password, persistence: .none)
            default:
                return nil
            }
        }

Need to reopen this issue. I just discovered that the authorization header is not sended. Any idea why this is the case ? NetworkLoggingPlugin reveals the following:
Moya_Logger: [20/09/2017 15:12:20] Request: http://localhost:9000/auth
Moya_Logger: [20/09/2017 15:12:20] Request Headers: ["Content-Type": "application/json"]
Moya_Logger: [20/09/2017 15:12:20] HTTP Request Method: POST

@dehlen I ran into a similar issue. The problem is that the URLCredential is only used for authentication challenges, not for preauthorizing the request. So if your API requires an Authorization header in the request this won't work. There seems to be a lot of confusion around how this works, see this issue on Alamofire.
I worked around this with the following:
lazy var provider: MoyaProvider<LoginService> = {
    let endpointClosure = { (target: LoginService) -> Endpoint<LoginService> in
      let defaultEndpoint = MoyaProvider.defaultEndpointMapping(for: target)

      switch target {
      case .login(let username, let password):
        return defaultEndpoint.adding(newHTTPHeaderFields: ["Authorization": "\(username):\(password)".base64Encoded])
      }
    }

    return MoyaProvider(endpointClosure: endpointClosure)
  }()

You could likely extract this to a plugin by using the AccessTokenPlugin as a guide. One reason I went this route instead of using the AccessTokenPlugin is that I wanted the ability to create requests with different credentials without having to create a new provider instance. CredentialsPlugin seemed like it would allow that, but lacked the pre-auth my API required.
If anyone has any better solutions, I'd be very interested to see them.

I ended up improving this by introducing my own plugin as well as my own protocol that targets could conform to:
struct SessionCredentials {
  let username: String
  let password: String
}

protocol SessionAuthorizable: AccessTokenAuthorizable {
  var credentials: SessionCredentials? { get } //If you never mix authenticated and non-authenticated endpoints in your targets, you could make credentials non-nullable
}

private extension SessionAuthorizable {
  func authorization() -> String? {
//Convert credentials to a Base64 encoded string, prefixed with "Basic"
  }
}

class SessionPlugin: PluginType {
  public func prepare(_ request: URLRequest, target: TargetType) -> URLRequest {
    guard let authorizable = target as? SessionAuthorizable, let value = authorizable.authorization() else {
        return request
    }

    var request = request
    request.addValue(value, forHTTPHeaderField: "Authorization")
    return request
  }
}

I chose to build on AccessTokenAuthorizable and it's AuthorizationType enum - alternately you could introduce your own or get rid of it entirely if you only have one supported authentication type.

Thank you very much. Your effort is much appreciated on my side :) I'll close this issue since my problem is solved this way.

I meet both issues when I  want to use CredentialsPlugin :)


[libvpx] Build error

Host Environment

OS: macOS 12.5 (Apple Silicon using arm64-osx)
Compiler: Xcode 13.4.1

To Reproduce
Steps to reproduce the behavior:
./vcpkg install libvpx
Failure logs
Computing installation plan...
The following packages will be built and installed:
    libvpx[core]:arm64-osx -> 1.11.0#1
Detecting compiler hash for triplet arm64-osx...
Restored 0 package(s) from /Users/myname/.cache/vcpkg/archives in 23.25 us. Use --debug to see more details.
Installing 1/1 libvpx:arm64-osx...
Building libvpx[core]:arm64-osx...
warning: -- Using community triplet arm64-osx. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: /Users/Shared/vcpkg/triplets/community/arm64-osx.cmake
-- Using cached webmproject-libvpx-v1.11.0.tar.gz.
-- Cleaning sources at /Users/Shared/vcpkg/buildtrees/libvpx/src/v1.11.0-389889d770.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /Users/Shared/vcpkg/downloads/webmproject-libvpx-v1.11.0.tar.gz
-- Applying patch 0002-Fix-nasm-debug-format-flag.patch
-- Applying patch 0003-add-uwp-v142-and-v143-support.patch
-- Applying patch 0004-remove-library-suffixes.patch
-- Using source at /Users/Shared/vcpkg/buildtrees/libvpx/src/v1.11.0-389889d770.clean
-- Build info. Target: arm64-darwin20-gcc; Options: --disable-examples --disable-tools --disable-docs --disable-unit-tests --enable-pic --enable-static --disable-shared
-- Configuring libvpx for Release
-- Building libvpx for Release
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:96 (message):
    Command failed: /bin/bash --noprofile --norc -c "make -j8"
    Working Directory: /Users/Shared/vcpkg/buildtrees/libvpx/arm64-osx-rel
    Error code: 2
    See logs for more information:
      /Users/Shared/vcpkg/buildtrees/libvpx/build-arm64-osx-rel-err.log

Call Stack (most recent call first):
  ports/libvpx/portfile.cmake:220 (vcpkg_execute_required_process)
  scripts/ports.cmake:147 (include)

And the content of file /Users/Shared/vcpkg/buildtrees/libvpx/build-arm64-osx-rel-err.log is:
make: *** [.DEFAULT] Error 2

Additional context
I just did a pull from vcpkg repo (and a full upgrade of all the packages) before trying to install libvpx as part of Qt 6

Thanks for posting this issue. Is this the only information in the error log? These information is too vague. Could you please provide the /Users/Shared/vcpkg/buildtrees/libvpx/build-arm64-osx-rel-out.log? I can install libvpx succeed locally.

The file /Users/Shared/vcpkg/buildtrees/libvpx/build-arm64-osx-rel-out.log is empty. I have a few brew packages installed too. Maybe related?

Sorry I can't confirm, I don't have arm64-osx machine.
cc @autoantwort, could you help take a look this issue?

@david-antiteum libvpx has been updated to version 1.12.0 by PR #26159. Could you update vcpkg and try install new version of libvpx?

Same problem using version 1.12. The content of vcpkg/buildtrees/libvpx/build-arm64-osx-rel-err.log is:
make: *** [.DEFAULT] Error 2

I see the same problem when building with x64-osx host / target. mac OS 12.6 / Xcode 14.0.1

Removing the entire buildtree/libvpx directory and rebuilding succeeded

Removing the entire buildtree/libvpx directory and rebuilding succeeded

@david-antiteum You can try this solution.

@LilyWangLL All good! Thanks!

That's great! Since this issue has been fixed, so I am closing this issue for now.


Write script without absolute shebang

I've been using Nodejs to make my own Bitbar scripts for years.
There's the shebang in the beginning of my every scripts:
#!/usr/bin/env /path/to/the/node/executable

But recently, for some reason on my work, the path to my node will need to change very frequently.
I can't use absolute path to my node anymore.
I wonder is there a way to use something like:
#!/usr/bin/env node

to let bitbar find it from my env variables?
I've tried a way from this stackoverflow post but it didn't work

That looks right to me. What happens when you execute /usr/bin/env node in terminal?

In my terminal:
$ /usr/bin/env node
Welcome to Node.js v16.1.0.
Type ".help" for more information.
>

Error message from xbar: exit status 127: env: No such file or directory

@RayPS the issue you are facing is with environment variables.
You will have to consider supplying the absolute path to node in the shebang
#!/path/to/the/node/executable

Reason: When env is executed, the PATH isn't set to find node. The same is true with other languages like  python
You can test it using this script (add this as a plugin).
This plugin dumps environment keys and the current PATH into a file TEST_ENV_CONTENT. The output file is placed a level below the plugins folder to avoid this file from being considered for execution.
#!/usr/bin/env bash

awk 'BEGIN{for(v in ENVIRON) print v}' > ../TEST_ENV_CONTENT
echo "---" >> ../TEST_ENV_CONTENT
echo $PATH >> ../TEST_ENV_CONTENT
echo "Dumped ENV"

The output I find in TEST_ENV_CONTENT on my system is:
XBARDarkMode
Apple_PubSub_Socket_Render
BitBarDarkMode
LOGNAME
XPC_SERVICE_NAME
USER
PATH
__CF_USER_TEXT_ENCODING
SHLVL
TMPDIR
SECURITYSESSIONID
HOME
SHELL
_
PWD
SSH_AUTH_SOCK
XPC_FLAGS
---
/usr/bin:/bin:/usr/sbin:/sbin

The number of environment variables set at this point are limited (lower than those which typically get set on terminal once bashrc/bash_profile have been sourced)
Also, observe that the PATH is just /usr/bin:/bin:/usr/sbin:/sbin
cc: @matryer

@pshirali Thanks for the hint. That makes lots of sense.
I solved this by launching Bitbar in my terminal, so my PATH is loaded before bitbar launches.
>　open /Applications/xbar.app

After this my PATHs is appeared in TEST_ENV_CONTENT
Next thing to do I will try to automate this or find a way to launch bitbar with my PATHs.
Thanks!

@pshirali Try adding this one to see if you can get your PATHs?
echo `/usr/libexec/path_helper` >> ../TEST_ENV_CONTENT

Would getting xbar to run path_helper to load paths at startup be a solution?


Update tests.yml

I have spoken with @kiloreux about how I can make the CI Workflows more efficient.
This is my proposal for avoiding double runs in every pull request. It is more or less Abdel configuration from the node SDK. It also empowers us to exclude specific labels or something if we want to.
It tests every push to main and every commit inside of pull requests. It would not go over every commit to every branch without a PR. I think it's a good tradeoff between maximum CI and resources as they are limited by GitHub.
If you are fine with that, I would use that also for TUS. I just wanted to make these changes first
You could play around with the new settings in my new Playground repo: https://github.com/cdr-chakotay/TestCI
I invited you for collaboration.

 Thank you so much for helping save planet resources :heart:


Create a set from alma production

Create a set that will include records with subject headings that exercise Indigenous Studies and Change the Subject .

Created DRDS_test_records_15076907990006421_new.tar.gz for indigenous studies testing and indexing in bibdata_staging.


Random CommandNAKedError occurrence during "capture_to_file(log_file)" call

I created a small python application which shall sample my hardware during boot. Therefore, I start the board every second overnight.
Unfortunately, my application raise a CommandNAKedError already after my approx. 10 reboots. Until the error occurs, the script works as expected.
Any idea how to get them stable?
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "av_kit_mdio_analyzer.py", line 35, in logic_task
    device.capture_to_file(log_file)
  File "/localdisk/twesterm/projects/AVKIT/venv/local/lib/python2.7/site-packages/saleae/saleae.py", line 711, in capture_to_file
    self._cmd('CAPTURE_TO_FILE, ' + file_path_on_target_machine)
  File "/localdisk/twesterm/projects/AVKIT/venv/local/lib/python2.7/site-packages/saleae/saleae.py", line 257, in _cmd
    ret = self._recv(expect_nak=expect_nak)
  File "/localdisk/twesterm/projects/AVKIT/venv/local/lib/python2.7/site-packages/saleae/saleae.py", line 248, in _recv
    raise self.CommandNAKedError
CommandNAKedError

I don’t think this is an issue with this library. It sounds like for some reason the saleae software can’t handle the command you’re sending at that time. Depending on your needs, perhaps your script can catch the exception and retry the command.
If you have some evidence that there’s an actual bug in this library, please feel free to reopen this issue. Thanks!

The following code is not stable. Could you give me an advice how to get them stable?
I have an issue which occures randomly (sometimes once in 2000 boots). Catching a and retry would lose maybe the 1 failed boot. I want to avoid try, expections.
Thanks
#!/usr/bin/env python
import saleae
import time

dir = os.path.dirname(os.path.abspath(__file__))
s = saleae.Saleae()
s.set_capture_seconds(1)

while True:
    file_path = os.path.join(dir, 'mySaleaeFile')
    if os.path.isfile(file_path):
        os.remove(file_path)
    s.capture_to_file(log_file)
    time.sleep(1)

Again I do not think this is a problem that this library can solve — I think this is an issue with the Saleae Logic software. All that this library does is send commands to the Logic software. You (or perhaps Saleae) need to diagnose why the Logic software periodically fails to save the file.


Will this work if the tenant is enabled for multifactor authentication?

Will this work if the tenant is enabled for multifactor authentication? Thanks in advance.

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

ID: 263b9c6e-b581-5b51-0bce-76fa12437e4f
Version Independent ID: be5c7725-f60d-3727-9602-c3df4957be71
Content: Configure a hybrid environment in Skype for Business Server 2015
Content Source: Skype/SfbServer/manage/authentication/configure-a-hybrid-environment.md
Service: unspecified
Product: skype-for-business-itpro
GitHub Login: @MicrosoftHeidi
Microsoft Alias: heidip

Thank you for this feedback and for contributing to the wellness of the content! This is a good idea and we have added it into our backlog for triage and prioritization.


Add Sleep Widget

Sleep Widget
A simple widget for the Bangle.js 2 that completely clears the screen when the watch is locked. I have not done extensive testing, but this should save battery life.
Features

Completely clears screen and stops running app when watch locks
Returns to clock when woken
Widgets continue running even when locked (for apps that use widgets for timers and notifications)

Controls/Usage

Sleeps when watch would normally lock (do not press anything for this to happen)
Once asleep, use any of the controls you would normally use to unlock the watch to wake it

Known Issues

Only works in apps that show widgets
May react badly to widgets that use the full screen for notifications

Creator
kyleplo
See my website for contact information

I'm closing this because I'm working on a better version that doesn't use a widget.


Cleanup conf refactor

Description
Seperated the config file and argparsing from the main file into a seprate module.
Contribution Guidelines
Please Read through the Contribution Guidelines.
Fixed Issues
Resolves #289 .
Contribution checklist

[X] I have read the Contributing Guidelines.
[X] The commits refer to an active issue in the repository.
[ ] I have added automated testing to cover this case.

Notes
I didn't add any functionality, so nothing needs to be added to the tests.

Codecov Report

Merging #310 into master will increase coverage by 0.12%.
The diff coverage is 65.38%.

@@            Coverage Diff             @@
##           master     #310      +/-   ##
==========================================
+ Coverage    59.8%   59.92%   +0.12%
==========================================
  Files          39       40       +1
  Lines        1928     1939      +11
==========================================
+ Hits         1153     1162       +9
- Misses        775      777       +2

Impacted Files
Coverage Δ

kube_hunter/modules/report/collector.py
89.28% <0%> (ø)
:arrow_up:

kube_hunter/conf/parser.py
100% <100%> (ø)

kube_hunter/conf/__init__.py
100% <100%> (ø)
:arrow_up:

kube_hunter/modules/report/plain.py
14.77% <33.33%> (-0.96%)
:arrow_down:

kube_hunter/modules/report/base.py
23.52% <40%> (-2.19%)
:arrow_down:

kube_hunter/modules/report/__init__.py
46.66% <46.66%> (-53.34%)
:arrow_down:

kube_hunter/modules/report/yaml.py
50% <50%> (-4.55%)
:arrow_down:

kube_hunter/modules/report/json.py
66.66% <50%> (ø)
:arrow_up:

kube_hunter/modules/hunting/apiserver.py
71.61% <0%> (+1.98%)
:arrow_up:

Continue to review full report at Codecov.

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

Hi @mormamn !
Thanks for your contribution.
Notice that this PR also indirectly fixes #292.


php artisan migrate:Syntax error or access violation: 1103 Incorrect table name

I am using "zizaco/entrust": "5.2.x-dev", what does this mean?
$ php artisan migrate
Migration table created successfully.

  [Illuminate\Database\QueryException]

  SQLSTATE[42000]: Syntax error or access violation: 1103 Incorrect table name '' (SQL: alter table `r
ole_user` add constraint role_user_user_id_foreign foreign key (`user_id`) references `` (`id`) on delete
 cascade on update cascade)

  [PDOException]
  SQLSTATE[42000]: Syntax error or access violation: 1103 Incorrect table name ''

please refer to https://github.com/Zizaco/entrust/issues/563#issuecomment-210244696
add user table name in migration script

on your database/migrations/_entrust_setup_tables.php ,the code what create role_user table,change "$table->foreign('user_id')->references('id')->on('')
->onUpdate('cascade')->onDelete('cascade');"
to "$table->foreign('user_id')->references('id')->on('users')
->onUpdate('cascade')->onDelete('cascade');"
function on missing code 'users'

Thank you

I have the same error and i fixe it  but the permission and permission_role tables didn't show up on my database

you could check my fork i have solved a lot of issues and a friend of mine and i are maintaining it

Ok thanks

Can you guide me to find the solution

Just follow the instructions of the docs and you are done! :D

Thanks it works for me, put "users' table


add client name to connection and connection pool

What do these changes do?
The changes add client name option to connection and connection pool so it's persistent across connections.
Fixes #713
Are there changes in behavior for the user?
No
Checklist

[x] I think the code is well written

[x] Unit tests for the changes exist

[X] Documentation reflects the changes

[X] If you provide code modification, please add yourself to CONTRIBUTORS.txt

[X] Add a new news fragment into the CHANGES/ folder

#713

Failed tests seems to be unrelated to the change..
@popravich could you review please?

@aviramha publish a null-change to re-run tests. Seems like pypy tests were broken when you pushed the patch.

@aviramha -
Thank you for your contribution and apologies for the radio silence! Maintenance for this project has resumed.
Would you be willing to resolve your merge conflicts? CI will fail for now but that's okay - we're going to fix that in a separate issue.

@seandstewart Great to hear that! I'll fix this soon.

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

@aviramha - great! thanks for merging in master. Last thing to do is sign the CLA then I think we can move forward with a merge 👍

@seandstewart I signed it.
Thanks for restoring maintenance!!


Feature Request: Define page's separation in the preview

Hi @l1xnan,
Thanks for this cool plugin !
I would like to suggest a feature: be able to define page separations for the exported file.
Currently, when I export any of my notes, some parts are cut-off at the end of a page, like a bullet list, or a note preview, ...
It would be awesome to be able to set page breakpoints so that it is easier and prettier to export MD files to PDF.
Thanks in advance for taking it into account !

Do you want to set page breaks manually? You can try to solve it with custom css snippets:
/* print.css */
.page-break {
  height: 1px;
  background-color: gray;
}

@media print {
  .page-break {
    background-color: white;
    page-break-before: always;
    clear: both;
  }
}

Then, in your document node.md, where you want the page breaks to be, add the

Previous page content

Next page content

Not sure if this will meet your expectations?

I'll test this, thx for the snippet

Do you know if we can toggle the light/dark mode when printing the document ?

Do you know if we can toggle the light/dark mode when printing the document ?

When exporting PDFs, the plugin removes the dark theme and adds the light theme (the official PDF export does the same thing):
document.body.addClass("theme-light");
document.body.removeClass("theme-dark");

If you do need it, I can add a config item that does not do this.
In fact, the dark theme export quality is not good. Here's a comparison of the Minimal light/dark themes:

dark theme print background
dark theme remove background
light theme

I don't have a usecase for the dark theme yet, so I think it isn't useful for now, I will get back to you if I encounter a usecase.
I will try adding the dark theme class to the file I print.
Thanks !

+1, it would be great to see how the resulting pdf will be split into pages, and also possibly define the page-splitting in the preview.

This would be amazing! Pasting a div is fine but for people that are not familiar with html it can be confusing. Plus you really want to view how it will turn out add the page breaks where something looks wrong and have it update.


Carbon.txt serve command with Granian should support access logs

We have the choice of multiple servers when running the carbon-txt serve command.
If we want API requests to show up in our logs (we do), then we will need to add support for passing in the --access-log flag when running Granian.
This would help for running the carbon-txt API in production.
Related links:
Granian's logging has some idiosyncratic behaviour we should keep in mind:
https://github.com/emmett-framework/granian/issues/418
https://github.com/emmett-framework/granian/issues/419
Granian's flags
https://github.com/emmett-framework/granian
Our cli module, that contains the logic for calling Granian
https://github.com/thegreenwebfoundation/carbon-txt-validator/blob/main/src/carbon_txt/cli.py

Closed with https://github.com/thegreenwebfoundation/carbon-txt-validator/pull/46


Performance benchmark / regression test for Kitura

I'd like to propose that we create a performance benchmark, similar to the Kitura-Sample application,  which can be used to periodically regression test Kitura.
The primary aim of such a regression test would be to evaluate the effectiveness / impact of code changes and enhancements, for example:

to indicate the benefit of a performance enhancement
the cost of a new feature or bug fix
the impact of migrating to a new Swift snapshot

Things that we would need:

A benchmark (eg. 'Kitura-Bench')
Travis CI support, to ensure benchmark is always runnable against the latest Kitura / snapshot
A method of executing the benchmark in a consistent environment (Docker container?) which contains any dependencies (DB, for example) in a pristine state, and which ensures that each execution of the benchmark is done in a consistent manner

To automate the execution of such a benchmark, we would need:

Performance hardware (dedicated so that a perf measurement is not tainted by other users / uses)
A method of requesting a perf measurement against a branch / PR
A scheduling mechanism, to serialize requests (so multiple requests do not run simultaneously, invalidating results)
Consumable results (simple measures of ops/sec, CPU utilization, response times)
A method of recording and comparing measurements, so that we can compare to a baseline result generated on the current release and determine whether a result is 'better' or 'worse'.

Travis-CI does not itself support performance measurement (https://github.com/travis-ci/travis-ci/issues/3313), so we would need a separate mechanism.  We might be able to use a slack bot.

@djones6 A guy from our local slack group created a set of benchmarks. Kitura seems to perform egregiously bad though. Would you have any idea why this is happening? My understanding is it's not because of libdispatch (Zewo does reasonably well), so what is the bottleneck?

Just double checking, @codeOfRobin , did you mean to write ms instead of us (microseconds) for Kitura? If not, then Kitura actually is running at 0.3 ms which is amazing :)

@rfdickerson It's actually µs (There's a huge standard deviation, so the max is around 277 ms). Can someone ElIiOSDev why this is happening?

This has been delivered in the https://github.com/IBM-Swift/Kitura-Benchmarks project.


Bugfix for task353: removed hardcoded dimensions and added unknown label

http://sunflower.sahanafoundation.org/eden/project/task/353

Ideally, we would deprecate these charts since jqplot was deprecated when we introduced flot, and now flot is deprecated since we moved to D3 - so dinosaurs are more modern than this page design.
Apart from that, this page is normally not accessible for any user except administrators, and thus adds very little value - it merely existed as a PoC (5 years ago), but since we have moved lightyears beyond that, this can really really be removed.

NB when you change layouts or styles, it would make reviewing stuff a lot easier if you could provide screenshots. In this case both - large (desktop), medium (tablet) and small (mobile phone, both landscape and portrait) screen sizes to demonstrate responsive behavior.
Without responsive behavior, this fix would be fairly pointless (yeah, ok, it is anyway - but that is an important general requirement for page designs now).

Hey @nursix ,
Thanks for taking the time to look at this.
Judging from your comments it sounds like removing the /pr pages altogether is the way to go. My plan then is to remove the following:
 controllers/pr.py
 views/pr/

I am guessing that other aspects of the application might be using the pr table so I wasn't going to attempt to remove reference entirely ie. removing modules/s3db/pr.py etc. but I may be wrong about this.
Does this sound like a good plan or is there a better way to go about this?

Oh no, I was merely talking about removing the charts from the pr/index page - the rest of the person module is absolutely essential for Eden!
The only other thing that could be removed is jqplot.

Or in other words: the person registry module is an utterly important, and yet largely invisible module. Most users won't have direct access to this module, and normal users do usually never see the index page - hence the charts add very little to no value. Even if end-users would see them, they do not really provide any relevant information.
They have been a PoC for embedding charts into pages, but we have moved on far beyond that and meanwhile have a generic charting framework, so these charts are obsolete for that purpose.
But the pr module as such is a true core module and there is no (really: no!) other module that would work without it. Even as a whole wouldn't start without it ;) It defines the core entities for everything - and we do want to retain the index page at least for data maintenance (standard CRUD with Admin level access), and for certain simpler use-cases.

@nursix I thought that was a little weird to be removing the pr module hence my comment about how I suspected other parts of the app were using it, but yeah, my bad haha.
So I have updated the pull request to remove the charts from the pr/index page and also noticed similar charts were being used on dvi/index so I removed those as well assuming the same situation applied (ie. they're outdated). As those were the only two uses of jqplot I could find, I also deleted the jqplot files from static/styles/ and static/scripts/ but perhaps I have gone too far by doing this? or maybe there was a more elegant way to remove/disable these jqplot related files?
I've attached screen shots of each the pr/index and dvi/index in firefox, chrome, tablet and mobile renderings.


[#1756] Introduce resolver used to solve duplicate command handling members in Aggregates

Question still need to been confirmed:

does AnnotationCommandHandlerAdapter need to be resolved by DuplicateCommandHandlingMemberResolver?

This pull request resolves #1756

After seeing your PR, some different approaches and ideas dawned on me.
Some that actually adjust the initial description of the issue, which in turn would lead to a different implementation from the PR.
So, my apologies for getting you on the wrong path here @leechedan. Let me provide the current train of thought for issue #1756.
From the perspective of Command Handlers directly registered to the CommandBus, the DuplicateCommandHandlerResolver solves the intended perdicament.
What's important here, is the following:
// Copied from the SimpleCommandBus, lines 186-198
@Override
public Registration subscribe(String commandName, MessageHandler<? super CommandMessage<?>> handler) {
    logger.debug("Subscribing command with name [{}]", commandName);
    assertNonNull(handler, "handler may not be null");
    subscriptions.compute(commandName, (k, existingHandler) -> {
        if (existingHandler == null || existingHandler == handler) {
            return handler;
        } else {
            return duplicateCommandHandlerResolver.resolve(commandName, existingHandler, handler);
        }
    });
    return () -> subscriptions.remove(commandName, handler);
}

Within the subscribe operation prior to potentially invoking the resolver, there's a handler validation check (more precisely, this statement).
The Command Handlers of an Aggregate are combined in the AggregateAnnotationCommandHandler, where the entire object is used during subscription for every command name found.
This is done to intentionally allow Command Handlers that handle the same command, actually.
What is wrong, in this case, is that the entire signature from the command handler isn't validated.
There can for example be situations where an Aggregate contains two handlers for the same command, but with differing metadata additions to the set of parameters.
In that case, the metadata field can dictate which aggregate-creation-method is invoked, thus allowing for different logic in each method.
As you might have noticed through the code, the above is also not in place.
It is this which should've been described in issue #1756 actually.
What I think would be a fair approach, is this threefold of actions:

In the AnnotatedAggregateModel, log if there is another command handler with the same name.
In the AnnotatedAggregateModel, throw an AggregateModellingException if there are two command handlers with the same name and set of parameters (as this does indicate a duplicate).
Expand the test fixtures to validate duplicate command handlers within the Aggregate under test.

Now, this is quite different from the original offset of your pull request @leechedan.
Would you be up for making those changes in favor of what you already have provided? If not, that is completely fine of course.

so. do u mean just  resolve duplicate commandHandlerMember (logging or thronwing excpetion) in AnnotatedAggregateModel?
@smcvb

Yep, the resolution would be ideal in the AnnotatedAggregateModel I think.
More specifically, inside the prepareHandlers method, when a message handling member is added to the list.
At that moment, we can validate the command names, which if identical should trigger a log message.
This is followed up immediately with validation if the set of parameters is identical, that if true should trigger an exception.
Next to this, adding validation (which can be turned on or off) inside the AggregateTestFixture would provide guidance on this in general.
The goal of this guidance is to better help the users of the framework, of course.

thanks for decribe the detail for me, i will commit a  pr when i get ready , not not in this pr directy. so u can close this.


Improve organization view

Because it uses skos:preflabel, it shows nothing atm.

Appears not to be a front-end issue, but API issue.


Plot Airmass Improvments

Accept either a single target or a list of targets
Brightness shading that actually works (from @joshwalawender in panoptes/PEAS)

Note: Really this should all be redone to use a real plt.figure and axes

This looks nice. I have two questions – when you say "Really this should all be redone to use a real plt.figure and axes", what do you mean? And would you agree that it would be easier to read if the default axvspan color were gray?

My understanding is that pyplot should be used for interactive things but you should use the OO interface otherwise. But my understanding of matplotlib isn't that great and pyplot is always easier for me anyway. :).
From the site: "For non-interactive plotting it is suggested to use pyplot to create the figures and then the OO interface for plotting."
http://matplotlib.org/faq/usage_faq.html
I'll test it out with grey too and post a pic.

Yeah, I like the grey more, good call. I kept the slightly thicker lines.

In the example the legend is added outside the plot_airmass function but with multiple targets it becomes a necessity to have and I think most users would just expect it to show. @bmorris3, what are your thoughts about adding it as part of the functionality?

I'm not sure why one of those tests started failing above. The only errors I see don't appear to be related and the reported error is about sphinx but nothing changed there. Let me know what I can do to fix it.

In the example the legend is added outside the plot_airmass function but with multiple targets it becomes a necessity to have and I think most users would just expect it to show.

@wtgee The reason we did not include multiple targets in the plot_airmass function was for that reason – we wanted them to be able to control the plot settings of each target individually. There will be users who still want control over the legend, so I think it should stay outside of the plot_airmass function.
Our intention is to keep the scope of the astroplan plotting functions narrow, so you can build on top of them as you need for your particular work.

Looks good, thanks @wtgee!


DP-3 Missing, Should List CMK

Would you agree that the category "Data Protection" should be included somewhere in Azure security baseline for Azure Cognitive Search | Microsoft Docs given that we have data encryption options for Customer Managed Key? Encrypt data using customer-managed keys - Azure Cognitive Search | Microsoft Docs

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

ID: e9fc827f-bd83-c39d-c615-aecc4bd05252
Version Independent ID: 2fb662e3-9bf5-4995-4867-4ae6fae6d0c3
Content: Azure security baseline for Azure Cognitive Search
Content Source: benchmark/azure/baselines/cognitive-search-security-baseline.md
Service: search
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@jeremiahhoward Thanks for the feedback! We are currently investigating and will update you shortly.

@jeremiahhoward Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

Hello, @EmiFlo.  We recently upgraded the Azure Cognitive Search baseline to the newest version of our benchmark: The Microsoft Cloud Security Benchmark.  The Data Protection section is at https://learn.microsoft.com/en-us/security/benchmark/azure/baselines/azure-cognitive-search-security-baseline#data-protection, and mentions that the "service supports data in-transit encryption for data plane".   Thank you! #please-close


Gh-3002: Ensure CancelScheduledJobHandler is only added when Jobs are enabled.

Previously, the CancelScheduledJobHandler would throw an OperationException with the message 'JobTracker not enabled' if used when Jobs were not enabled. This issue arose because the handler was being added even when Jobs were not enabled. To resolve this, changes were made to ensure that the CancelScheduledJobHandler is only added when Jobs are enabled. This ensures that the handler functions correctly and prevents the unnecessary exception from being thrown.

@GCHQDeveloper314 take a look at this.


Added username to EventHubs in .github/CODEWOWNERS

Description
Added my username into in the ".github/CODEOWNERS" file on line # 105.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/check-enforcer override


Adding JSON Generator

This adds the JSON generator class to the library plus an example notebook.

Codecov Report

Merging #41 (32f5e0e) into dev (f261691) will decrease coverage by 2.14%.
The diff coverage is 50.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##              dev      #41      +/-   ##
==========================================
- Coverage   75.20%   73.06%   -2.14%
==========================================
  Files          12       13       +1
  Lines         375      401      +26
  Branches       51       53       +2
==========================================
+ Hits          282      293      +11
- Misses         75       90      +15
  Partials       18       18

Impacted Files
Coverage Δ

randomdataset/generators/jsongenerator.py
40.00% <40.00%> (ø)

randomdataset/generators/__init__.py
100.00% <100.00%> (ø)

randomdataset/generators/generator.py
69.69% <100.00%> (ø)

randomdataset/schemaparser.py
94.73% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


"cargo doc" is broken

cargo doc fails with:
 Documenting x11rb v0.4.1 (/home/psychon/projects/x11rb)
error: Documentation test in private item
    --> src/generated/xproto.rs:8628:5
     |
8628 | /     /// Iterate over the contained value if its format is 8.
8629 | |     ///
8630 | |     /// This function checks if the `format` member of the reply
8631 | |     /// is 8. If it it is not, `None` is returned.  Otherwise
...    |
8674 | |     /// assert!(reply.value8().is_none());
8675 | |     /// ```
     | |___________^
     |
note: lint level defined here
    --> src/lib.rs:88:5
     |
88   |     private_doc_tests,
     |     ^^^^^^^^^^^^^^^^^

error: Documentation test in private item
    --> src/generated/xproto.rs:8684:5
     |
8684 | /     /// Iterate over the contained value if its format is 16.
8685 | |     ///
8686 | |     /// This function checks if the `format` member of the reply
8687 | |     /// is 16. If it it is not, `None` is returned.  Otherwise
...    |
8728 | |     /// assert!(reply.value16().is_none());
8729 | |     /// ```
     | |___________^

error: Documentation test in private item
    --> src/generated/xproto.rs:8738:5
     |
8738 | /     /// Iterate over the contained value if its format is 32.
8739 | |     ///
8740 | |     /// This function checks if the `format` member of the reply
8741 | |     /// is 32. If it it is not, `None` is returned.  Otherwise
...    |
8781 | |     /// assert!(reply.value32().is_none());
8782 | |     /// ```
     | |___________^

error: aborting due to 3 previous errors

error: Could not document `x11rb`.

I guess this is because x11rb::generated is no longer public, but only publicly re-exported.
So, either of the following needs to happen:

the generated code has to be moved around so that it is "directly public"
suitable #[allow(private_doc_tests)] are placed in src/generated/mod.rs.

This looks like a bug in rustdoc (publicly reexported is still public), so I would go for using #[allow(private_doc_tests)].


Improperly formatted ZonedDateTime in ListTransactions API call

Describe the bug
The MerchantAccountsHandler#listTransactions method is converting the query argument's ZonedDateTime objects to an invalid string format. The current implementation uses the DateTimeFormatter.ISO_ZONED_DATE_TIME format, which generates a string like 2023-01-01T01:01:01.000000001+01:00[Europe/Paris]; however, according to the API documentation, the string must of the format YYYY-MM-DDTHH:MM:SS±HHMM.
When calling the ListTransactions API using the Java SDK, I get the following error:

Invalid value for parameter from: invalid from query param, status=400, traceId=31df24cb-5781-4c2e-8ee1-faa75d72ab87, errors={"from":["invalid from query param"]}

To Reproduce
Steps to reproduce the behavior:

Use the Java SDK to send a ListTransactions request to any merchant account.

Expected behavior
I expect the from and to API parameters to be populated with correctly formatted string representations of ZonedDateTime objects.
Screenshots
Environment (please complete the following information):

OS: Oracle Linux Server 8.8
JVM distribution: JDK 17.0.3
Library version: 9.0.0

Additional context

Looking at the Java 17 docs, the ISO_OFFSET_DATE_TIME predefined formatter is more appropriate than the ISO_ZONED_DATE_TIME formatter.

Thanks for raising this. I think the reason why this is currently not catched by our acceptance tests is that we built the from param this way:
ZonedDateTime from = ZonedDateTime.parse("2021-03-01T00:00:00Z");
By using the the now() and plus*() methods offered by the ZonedDataTime api I was able to reproduce this.
I've raised a PR and I'm looking for internal reviews. In the meantime, if you want to give the prerelease a try you can use this snapshot version: 9.0.1-ewt-328-datetime-bugfix-SNAPSHOT

I've merged the related PR, feel free to reopen this if you see something unexpected.


Sql database reflection level

Tell us what you do here

improving, documenting, or customizing an existing source (please link an issue or describe below)

Short description

Adds reflection level argument: minimal (column names + pk + nullability), full (minimal + data types) , full_with_precision (full + precision)
type_conversion_callback argument to cast one sqla type to another (runs before dlt data type is detected from sql type)
Tests for both

Test pass on dlt devel locally. May not on release version currently.

Related Issues

Fixes #...
Closes #...
Resolves #430

Additional Context

this 90% good.
1. we have a related bug [sql_database source | error with pyarrow BE, if some of the types were not identified correctly #488](https://github.com/dlt-hub/verified-sources/issues/488) see in the review

I added some logic in row_tuples_to_arrow to skip unknown type columns. They are returned without data type in dlt schema to preserve the index. The other backends type is still inferred where possible.

2. please add a test where we have an unsupported type like GEOMETRY in the table. let's try to load it with and without type adapter

Added a kinda massive parametrized test for all backends/type adapter/reflection levels. Using DATERANGE and ARRAY columns. Didn't want to require postgis or anything and make the test setup more complicated. But could be nice to test with snowflake source since they use all custom types that don't inherit regular sqla types.
Type adapter can work in some cases, but for instance trying to load the DATERANGE object to arrow as complex/text type does not work. We would need to run through the data and coerce values for that which would be a big performance hit.

3. we need docs update with examples of type adapter, same thing in sql database pipeline demo

https://github.com/dlt-hub/dlt/pull/1467

@steinitzu is there anything you still want to work on? I merged this PR with #478 because it is fixing a lot of config bugs in sql_database and I needed the minimal reflection level here.
so: if you are done with the code you can close this PR. and take a look at #478. which is ready to be merged

@steinitzu OK 0.5 got released and this PR was merged


Debug Failure when using --build

1>EXEC : error : Debug Failure.
1>      at Object.assertDefined (C:\dev\epro\packages\Microsoft.TypeScript.MSBuild.3.0.0\tools\tsc\tsc.js:1394:24)
1>      at C:\dev\epro\packages\Microsoft.TypeScript.MSBuild.3.0.0\tools\tsc\tsc.js:13822:84
1>      at String.replace (<anonymous>)
1>      at formatStringFromArgs (C:\dev\epro\packages\Microsoft.TypeScript.MSBuild.3.0.0\tools\tsc\tsc.js:13822:21)
1>      at Object.createCompilerDiagnostic (C:\dev\epro\packages\Microsoft.TypeScript.MSBuild.3.0.0\tools\tsc\tsc.js:13863:20)
1>      at checkSourceFilesBelongToPath (C:\dev\epro\packages\Microsoft.TypeScript.MSBuild.3.0.0\tools\tsc\tsc.js:83705:55)
1>      at Object.getCommonSourceDirectory (C:\dev\epro\packages\Microsoft.TypeScript.MSBuild.3.0.0\tools\tsc\tsc.js:82379:21)
1>      at Object.getExternalModuleNameFromPath (C:\dev\epro\packages\Microsoft.TypeScript.MSBuild.3.0.0\tools\tsc\tsc.js:10438:84)
1>      at Object.tryGetModuleNameFromFile (C:\dev\epro\packages\Microsoft.TypeScript.MSBuild.3.0.0\tools\tsc\tsc.js:59905:40)
1>      at transformAMDModule (C:\dev\epro\packages\Microsoft.TypeScript.MSBuild.3.0.0\tools\tsc\tsc.js:72674:33)
1>
1>  [18:16:08] 'build-typescript' errored after 2.65 s
1>  [18:16:08] Error: Command failed: node "../packages/Microsoft.TypeScript.MSBuild.3.0.0/tools/tsc/tsc.js" -b --verbose Framework/Framework.tsconfig.json
1>  C:\dev\epro\packages\Microsoft.TypeScript.MSBuild.3.0.0\tools\tsc\tsc.js:82937
1>                  throw e;
1>                  ^

I'm experimenting with trying to upgrade our solution (25 seconds build time) to --build. I've started with one specific module, looking to pull that out of our monolith.
Here are the three tsconfig files involved:
base.tsconfig
{
    "compilerOptions": {
        "experimentalDecorators": true,
        "module": "amd",
        "moduleResolution": "node",
        "noEmitOnError": true,
        "noImplicitAny": true,
        "outFile": "build/typescript.js",
        "removeComments": false,
        "sourceMap": true,
        "target": "es5",
        "allowUnreachableCode": false,
        "noImplicitReturns": true,
        "baseUrl": "./",
        //"strictNullChecks": true,
        "noImplicitThis": true,
        "noUnusedLocals": true,
        "noUnusedParameters": true,
        //"skipLibCheck": true,
        "lib": [ "dom", "es5", "es2015.promise" ]
    },
    "compileOnSave": false,
    "exclude": [ "node_modules" ]
}

tsconfig
{
    "extends": "./base.tsconfig.json",
    "include": [
        "App/Require.ts",
        "**/*.ts",
        "**/*.d.ts"
    ],
    "exclude": [
        "Framework/*.ts"
    ],
    "references": [
        {
            "path": "Framework/Framework.tsconfig.json"
        }
    ]
}

Framework.tsconfig.json
{
  "extends": "../base.tsconfig.json",
  "exclude": [
      "../node_modules",
      "../Framework/AsyncResponse.ts",
      "../Framework/DispatchPromise.ts",
      "../Framework/Framework.ts",
      "../Framework/Cache.ts",
      "../Framework/CacheContent.ts",
      "../Framework/CacheReducer.ts",
      "../Framework/Component.ts",
      "../Framework/Connection.ts",
      "../Framework/ConnectionBuilder.ts",
      "../Framework/Editor.ts",
      "../Framework/LoadingProps.ts",
      "../Framework/TextInsertionFormatting.ts",
      "../Specs/Framework/CacheReducerTests.ts",
      "../Specs/Framework/CacheTests.ts",
      "../Specs/Framework/ColumnMatcherTests.ts",
      "../Specs/Framework/ConnectionTests.ts",
      "../Specs/Framework/ConnectionBuilderTests.ts",
      "../Specs/Framework/DispatchPromiseTests.ts",
      "../Specs/Framework/LoadingPropsTests.ts"
  ],
    "include": [
        "../redux.ts",
        "../react-redux.ts",
        "../Specs/Helpers/MockClock.ts",
        "../Framework/*.ts",
        "../Specs/Framework/*.ts",
        "../Dependencies/moment.d.ts",
        "../Dependencies/jquery.cookie.d.ts",
        "../Dependencies/rangy-core.d.ts",
        "../Dependencies/jquery.d.ts",
        "../Dependencies/underscore.string.d.ts",
        "../Dependencies/underscore.d.ts",
        "../Dependencies/jasmine.d.ts",
        "../Dependencies/JasmineAddons.d.ts",
        "../Dependencies/react.d.ts",
        "../Dependencies/redux.d.ts",
        "../Dependencies/react-redux.d.ts",
        "../Dependencies/react-dom.d.ts"
    ],
    "compilerOptions": {
        "experimentalDecorators": true,
        "strictNullChecks": true,
        "composite": true,
        "declaration": true,
        "outFile": "../build/framework.js"
    }
}

Not sure what further information is needed, let me know in a comment and I'll try to provide.

Based on my debugging, this occurs if the rootDir option is not set. Also, it seems really dumb how the string formatting function can crash the compiler this way due to a terrible API.

@markboyall can you please share small repro?
Need source structure (apart from tsconfig what do source files look like)
Which project are you trying to build that causes this exception?

Closing this since there is no further information. Please update if you have more details. Thank you.


GPUImageMovie blocking main thread

In the SimpleVideoFileFilter example, if I remove the writer, GPUImageMovie calls readNextVideoFrameFromOutput on the main thread.
Is there a particular reason for this?
I wrapped the whole else part in a async block
dispatch_async([GPUImageContext sharedContextQueue], ^{
...
{);
and it seems to work without blocking the main thread.

So do we having a work-around way to loop now?

I have a fork that solves this issue. Basically I dequeue and enqueue threads for the AVAssetReaders to utilize for reading back frames. This allows smooth performance without any hits to main. The fork is private right now but I'll look at creating a PR this afternoon with just the thread queue logic.

I still have the same issue. Is there a chance that this fix will make it into the main thread soon?


Added language support for GLSL via clang-format

What does this implement/fix? Explain your changes.
Language support for GLSL with clang-format as beautifier
...
Does this close any currently open issues?
No
...
Any other comments?
...
Checklist
Check all those that are applicable and complete.

[ ] Merged with latest master branch
[ ] Added examples for testing to examples/ directory
[ ] Travis CI passes (Mac support)
[ ] AppVeyor passes (Windows support)

Published to v0.29.15


Once an individual selects they are a legal clinic, we need to add an introductory page/landing page. We have already recorded the video

This issue can be worked on after @jmezetin has submitted his redesign that creates a separate path for the legal clinic and seperate path for the public.

Video is here: https://www.youtube.com/watch?v=v96QcDXHS-E


GH-1205: Partitioning Doc Polishing

Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/1205

Codecov Report

Merging #1235 into master will increase coverage by 0.38%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1235      +/-   ##
============================================
+ Coverage        65%   65.39%   +0.38%
- Complexity      802      804       +2
============================================
  Files           126      126
  Lines          3638     3638
  Branches        523      523
============================================
+ Hits           2365     2379      +14
+ Misses         1006      987      -19
- Partials        267      272       +5

Impacted Files
Coverage Δ
Complexity Δ

...ud/stream/binder/AbstractMessageChannelBinder.java
46.88% <0%> (+5.12%)
22% <0%> (+2%)
:arrow_up:

Continue to review full report at Codecov.

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


CUDA/GL Rasterizer

I'm looking into working on a GL renderer for the parquets.
I see that the Inria repository that has now been released wrote the rasterizer completely in CUDA.
Do you have any plans on working on different renderers/rasterizers?
Also, about making the inference completely Taichi field-based, how much work do you believe is left there? Any starting points to work on this?
@wanmeihuali

The cumsum implementation would be very helpful. Looking deeper into Taichi for this!

@aKn1ghtOut Please checkout this scratch for the cumsum implementation.

So, just wanted to provide an update:
I have been reading up on Taichi.
Initially, what I set up as a goal was to try and get the whole rasterizer itself as a Taichi Kernel and use that in AOT.
Functionally, this would have meant any supported platform would've just provided the parameters just like the _custom_fwd function is called, and the rgb image would be returned.
I have found the below issues with this approach(please correct me if I am wrong):

Working with dynamic data types is a pain in taichi. For example, just feeding in the pointcloud and pointcloud_features wouldn't work without providing details of the shape of the ndarray. Thus, any platform using the module would need a preprocessor as well apart from the checkpoints/parquets.
Taichi only appears to have Vulkan backend support for AOT marked as stable currently. Reading up more on this right now.
I believe the inference code also changed a lot since I cloned and started working on the project. Honestly, great work on keeping the velocity!

I feel like my skill set might not be the best suited to tackle the Taichi aspects right now, although looking into it was pretty fun.
Do let me know if there is other stuff I could help with.

Dynamic data types/shapes are not the key issue. Taichi provides a C++ API so for any platform, we can use ti::Ndarray to represent data. A preprocessor is needed but it is shared among all platforms.
Taichi is still in fast-paced development, and the Vulkan backend is kind of "Universal", as it can run on both Android, ios, macOS, and AMD GPU. I believe Metal and CUDA backends shall also work. These functions shall work, but Taichi is just a startup so they don't have enough manpower to fully test them I guess.
As I said I'm still figuring out the reason why my implementation is slower than the official one. So the inference code is still changing... Right now the running time of the rasterization kernel shall be reduced from 6-7ms to 1-2ms.

If you are still interested in the project and want to make some contribution,
I've listed the four tasks that are going on right now(https://github.com/wanmeihuali/taichi_3d_gaussian_splatting/issues/97#issuecomment-1634524532). Feel free to look into any of them.  Also, there are some issues unclosed for this project, e.g. bug reports for tool scripts.
Anyway, thanks for your time!

@wanmeihuali  Hi, I am also trying to migrate 3DGS to Android platform by using taichi AOT, but I have encountered many problems, probably because I am not familiar with the taichi library;
Could you share your details about taichi cumsum implementation?   thanks for your sharing!


Views Controlled Vocabularies TG call Oct 7 14:00 UTC

The Views Controlled Vocabularies Task Group will have an online meeting at 14:00 UTC on Monday, October 7. That corresponds to 7:00 AM Mountain Standard Time (Phoenix), 9:00 AM Central (US) Daylight Time (Chicago), 10:00 AM Eastern (US) Daylight Time (New York), 4:00 PM Central European Summer Time (Copenhagen/Stockholm), and 1:00 AM Tuesday Oct 8 Australian Eastern Daylight Time (Canberra).
At this meeting, we will evaluate our progress on collecting use cases and discuss anything that we want to report at the upcoming TDWG annual meeting.
I'll post a Google Hangout link as a comment under this issue about an hour before the meeting.

Don't forget the Views Controlled Vocabularies TG meeting coming up soon on Monday, Oct. 7 at 14:00 UTC.  See this issue for times in various time zones.
I will post a hangout link here shortly before the time for the meeting to start.

Here's the link for the Views Controlled Vocabularies TG Google Hangout:
https://hangouts.google.com/call/hTz_cxQ-_zKSKUVfvanlAEEE

Meeting notes for the Views CV TG hangout are here


Port "Robot Model and Robot State" tutorial

Port tutorial to ROS2.

This was ported: https://moveit.picknik.ai/main/doc/examples/robot_model_and_robot_state/robot_model_and_robot_state_tutorial.html?highlight=robot model


The basecalling and  alignment can be performed separately?

Hello,
According to the Example, the basecallings and alignments were completed together.
For the part of Methylation Calling from Guppy basecalled FAST5 files, the Guppy basecalled FAST5 files and BAM files containing alignments are required. Can I produce these two files separately as following steps:
First, basecalled fast5 files and  FQ files containing read sequences are generated using Guppy.
Second, BAM files are generated by aligning  FQ files to reference genome using minimap2.
Third, the basecalled fast5 files and BAM files were fed to DeepMod2.
    Thanks!

Hi,
Yes you can definitely separate basecalling and alignment steps. The example only does it in a combined way for the sake of brevity, but even in that case Guppy uses mnimap2 for alignment.
Best,
Umair

Okay. Appreciated it! No questions here. I will close this issue.


[FR] Configurable Date format

Add a column option for date and date time types where you can choose the format


Fix not starting vitest process on windows

This change has been tested on both Windows and OSX test are running and reporting their status back correct.
In order to get it working on windows you have to remove the vitest setting {PATH: "/path/to/node"} from your settings.json.
Fixes #15
Added a new issue which  will maybe make it easier to debug the issue next time #20

This change doesn't work on my windows machine.
@georgemickleburgh any idea on this?

It also doesn't work on my Windows machine, but if I add back in the lines src/pure/runner.ts:106 and src/runHandler.ts:128 then it appears to work again for me.
They are two of the changes that originally made it work on my machine, but do those lines cause issues for you @AlmarAubel ?

Thnx for your quick feedback I changed line 106 en 128 back and now it's working. Sorry that i din't work on your machine the first time!

No problem! I just pulled your changes and can confirm that it's working on my machine now 👍

LGTM. Thanks! @AlmarAubel


Set python3 as default interpreter

This closes #3070

Do I need to run migrations for this? If that is the case, probably we want to do another PR with the missing migrations right now before this one.

This is a change we've been wanting to make for a while now, but it is blocked more on the operations and support side. If we don't want to jump into this change just yet, we can at least keep this PR sidelined for when we are close.
I think we want to eventually just force 3.6 (at least). So perhaps the order of how we merge things would look like:

Make our latest docker image the new 3.0 and make that the default. This image has 3.6
Update this PR to make 3.6 the default python interpreter
Merge and deploy this

There is also likely a change we should coordinate here with our configuration handling and we should make 3.6 the default there too.

Blocked on https://github.com/rtfd/readthedocs-docker-images/issues/62

Not blocked on rtfd/readthedocs-docker-images#62, but this is blocked on making a change to our default image.

So, this will change the default interpreter for new projects, which is probably a safe place to start. We probably need to define a few more things though:

This will make the default database field 'python3', but have we tested what projects will get by default with the config parsing step? We do some weird things in both the rtd config parsing and the rtd-build config parsing where we rely on the default of the respective field value to assume the user hasn't defined anything special. Do we need to change anything here?
Do we need a default null value in this field instead?
Do we want to leave existing projects alone? I don't think there is any way we can determine whether a project is purposely selecting python as the interpreter or if it was just the default.
It sounds like we're waiting until at least the docker 3.0 image is selectable, we could probably target 3.6 instead of 3.5

Do we want to leave existing projects alone? I don't think there is any way we can determine whether a project is purposely selecting python as the interpreter or if it was just the default.

Yes. This should only be for projects going forward, not a change of existing configurations.

With the config file v2, the default version is python3, v1 would respect the setting in the admin panel. This only affects new projects.

Sphinx 2.0 is deprecating python2 http://www.sphinx-doc.org/en/master/changes.html#incompatible-changes. Just a note in case we update sphinx first.

Although, I'd prefer to upgrade our docker images before this PR gets merged and use 3.6 or probably 3.7 as default instead of 3.5.

I'm proposing some direction to achieve this goal at https://github.com/rtfd/readthedocs-docker-images/pull/84 but it involves some months before we get 3.7 working on the docker image (we have to release 4.0 first).
So, I suppose we can do this a smooth migration: first go with 3.6 and then with 3.7. Also, since we are setting only 3 as Python default version here, it will use the default python3 for the image itself. So, to upgrade to 3.7 we will only need to change the pyenv global (which currently is 3.6 https://github.com/rtfd/readthedocs-docker-images/blob/releases/3.x/Dockerfile#L84-L89 but it will be 3.7 after merging my PR)

Sphinx 2.0 is deprecating python2

Sphinx2 is doing a lot of things and I suspect there will be a number of incompatibilities (with our theme possibly but also lots of folks' docs). We will probably have to test this pretty extensively and perhaps have a milestone for it.


set the option to pin chats

hi, first at all congratulate you for this amazing lib
It would be great to be able to pin chats.

You can probably already implement that using room-actions prop:
room-actions="[
  {
    name: 'favoriteRoom',
    title: 'Pin Room'
  }
]"

Then when a room is pinned, you can use room-list-avatar slot for example, and add a star icon on the avatar of the room for example. Or set a specific background color to a room list item using getElementById(roomId).


HamNav fixed and other minor fixes

Mobile Navbar now coming above everything

Icon for mobile size increased as per good practices according to google.

Normal icon size

Icon size for mobile

Lgtm gw


[mtl] Events

Fixes #2809
Passes the relevant Vulkan CTS test! Although, might still have logic flows due to complexity of the synchronization here.
Based on #2840 and #2857
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[ ] tested examples with the following backends:
[ ] rustfmt run on changed code

Rebased and ready for review (@grovesNL ?)

bors r=grovesNL


Ellips reader attribute issues

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

25 of 27 (92.59%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 53.832%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pynxtools/dataconverter/writer.py
16
18
88.89%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
5099

Relevant Lines:
9472

💛  - Coveralls


Higher resolution output

256px seems to be the maximum size of an image. Is there any argument that we can pass for higher resolution output?

Hello! We only use the first two stages of DeepFloyd IF, which goes up to 256x256. DeepFloyd IF also has a third stage (which is just the stable diffusion upsampler), which makes 1024x1024 images. You could try incorporating that, but you might not get great results because it's a latent diffusion model (our method works better for pixel diffusion models. You can check the paper for details). The only other pixel diffusion model that I'm aware of is Imagen, which makes images up to size 1024x1024. Unfortunately Imagen is not available publicly. If there are other pixel-based diffusion models, I would expect them to work with our method (if you know of any I would love to know as well!).


🐛 Need list of cell types that are not supposed to be in organ model

The popV crosswalk lists hepatocyte as a cell type in the heart. However, they should only appear in the liver. We need to check if there are more cell types in the wrong organ model in the popV crosswalk.
PS: This causes downstream issues, such as wrong cell types showing up in the FTU Explorer: to https://github.com/hubmapconsortium/hra-ui/issues/615
PPS: This is also captured in https://github.com/hubmapconsortium/hra-workflows-runner/issues/37

The main reason we can NOT have a table that lists "Need list of cell types that are not supposed to be in organ model" because some cell types like various immune cells will always appear in all organs---different numbers or specific immune cells.
The hepatocyte example is the only one we found because it's such an obvious mistake---hepatocytes should only be in liver not heart or lung.
The other possible issue is if a sample block had contaminating tissue from surrounding organs---example: liver is in close proximity to both heart and lung.  In this case, one would expect that the number of these contaminating cell types in a dataset should fall below the threshold one would expect of cells that natively exist in the primary tissue.  This is one of the preprocessing steps for single cell RNA sequencing analysis--- remove cells that are 3 or below.  This threshold can be modified during the analysis.