Additional prism language (shell-session) is not colored.

🐛 Bug Report
As per Docusaurus docs, I added
prism: {
  additionalLanguages: ['shell-session']
}

under themeConfig in docusaurus.config.js.
I can see that the block of code where I use shell-session is being correctly tokenized, by inspecting it in the browser via "inspect element". However, no colors are applied! I see that in docusaurus, again via inspect element, other language blocks have colors applied directly via inline style tag on the elements of the code that should be colored. This is not happening for code I marked with shell-session. On the other hand, I see on PrismaJs website that in their example, shell-session code is colored by CSS coming from prisma.css, while that is not happening in Docusaurus.
So, it seems to me that shell-session is mostly working due to tokenization working, but for some reason nor inline styling nor styling via prisma.css is happening.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

Add prism: { additionalLanguages: ['shell-session'] } under themeConfig in docusaurus.config.js.
Create block of code in a markdown doc file, and mark its language as shell-session:

$ ls
some output

Expected behavior
I expected code to be colored, as in example at PrismJs webpage, where $ was yellow and command was red.
Actual Behavior
Code was not colored, it is just grey, as if no known language was specified. But I can see tokenization happening.
Your Environment

Docusaurus version used: 2.0.0-alpha-64
Environment name and version: 80.0.1 (64-bit), Node 12, I am using npm and not yarn
Operating system and version (desktop or mobile): Archlinux

Reproducible Demo
Link to file containing the problematic code block: https://github.com/wasp-lang/web/blob/tutorial/docs/tutorials/todo-app.md .
As seen from the link, repo is https://github.com/wasp-lang/web, and branch is tutorial.
Repo is docusaurus, so just do npm install and npm start and then in the Sidebar, go to Tutorials > Todo App and you will see the code blocks.

Hi,
I've debugged this issue.

The tokens are in the DOM, you should add the shell-session flag to all your codeblocks, many don't have it.
It's not a highlighter problem,  it's just that Docusaurus default syntax highlighting themes don't have anything to highlight properly the  shell-session tokens.
Replacing or importing some additional prism theme classes do solve the problem.
import 'prismjs/themes/prism-tomorrow.css'

$ cd TodoApp
$ wasp start
$ cd ..

If you don't know where to load such theme, you can try the customCSS

@slorber thank you for quick response!
Yes, as I mentioned, tokens are in the DOM, but no style was being applied to them. I had shell-session only on one code block because I wanted to compare the difference between one working and one just being plain once I get it working.
Great, your suggestion solved the problem! I wonder though, how is Docusaurus user supposed to figure this out on their own? Nothing is mentioned about possibly missing CSS when explaining how to add additional languages, and figuring out what to add and where (and that it even should be added) seems to require pretty good understanding of how both docusaurus and prismjs work. Maybe it should be mentioned in the docs, next to the part where addition of additional prism languages is explained?

@Martinsos great to know your problem is solved.

how is Docusaurus user supposed to figure this out on their own?

we are alpha, it's open source, our doc is not perfect and we rely on other open-source projects whose doc is not perfect either .
I had no idea that default prism themes had missing classes for specific languages, I don't know what to do about it right now, and have other more important things to fix and missing docs to write.
If you do not submit a doc PR with possible enhancements about what you have learned, you are also part of the problem 😅  and the reason others will stumble and complain in the future for this missing doc. You can be part of the solution instead, contribute code, doc or money to open-source projects you rely on.

@Martinsos great to know your problem is solved.

how is Docusaurus user supposed to figure this out on their own?

we are alpha, it's open source, our doc is not perfect and we rely on other open-source projects whose doc is not perfect either .
I had no idea that default prism themes had missing classes for specific languages, I don't know what to do about it right now, and have other more important things to fix and missing docs to write.
If you do not submit a doc PR with possible enhancements about what you have learned, you are also part of the problem sweat_smile and the reason others will stumble and complain in the future for this missing doc. You can be part of the solution instead, contribute code, doc or money to open-source projects you rely on.

Hi @slorber, I am maintaining an open source project myself, and I often try to contribute to other projects when I encounter an issue like this, so I very much understand what you are saying -> when I asked how is user supposed to figure this out on their own, I did it because I was interested if I am missing something or if this information is genuinely missing. I did not ask the question in order to nag or to complain, although I get a feeling from your last comment that this is how you perceived it, and I think it would be a wasted opportunity if the conversation continued in that tone. In my l last sentence I asked if it should be mentioned in the docs because I thought I could add it via PR if you say that makes sense.
Since you said even you don't know about this, and this information is actually missing, I will look into creating a PR for this, to add something to documentation.

Sorry for misinterpreting as a complaint then.
I don't know if this should be in the doc or not. We have setup prism, loaded a theme. I think user should rather look at prism doc. We can't duplicate doc of prism, MDX webpack etc in docusaurus doc without cluttering our own doc.
Maybe we could just mention that the default themes may not include highlighting classes for all languages or something. Honestly I don't even know if this is the problem, maybe we did something wrong, or maybe it's a React-prism-renderer issue

Sorry for misinterpreting as a complaint then.
I don't know if this should be in the doc or not. We have setup prism, loaded a theme. I think user should rather look at prism doc. We can't duplicate doc of prism, MDX webpack etc in docusaurus doc without cluttering our own doc.
Maybe we could just mention that the default themes may not include highlighting classes for all languages or something. Honestly I don't even know if this is the problem, maybe we did something wrong, or maybe it's a React-prism-renderer issue
If you want to submit a doc PR please do, we rarely reject them

Got it -> I created PR, it is very simple, so let's see, if that makes sense great, if not maybe it will at least start discussion about the correct solution for this.
PR: https://github.com/facebook/docusaurus/pull/3563 .
Thanks!

Hi, just following up here as I faced this issue today. I believe this issue should remain open:
It is still valid, and it was not addressed in any way: nor through a fix in docusaurus, or through a documentation change as proposed by https://github.com/facebook/docusaurus/pull/3563.
The official docs says:

To add syntax highlighting for any of the other Prism supported languages, define it in an array of additional languages.

That's not true, as this issue states, doing only this is not going to work. More and more people will face the same challenge.
So, I suggest to reopen the issue, until it's properly fixed or documented.

@felipecrs so let's re-open the issue then. However, I don't plan to work on this myself so if you know how to fix it or document it properly, please submit a PR

I think I discovered the root cause of the issue:
Palenight:

GitHub:

So as it seems, the themes (https://github.com/FormidableLabs/prism-react-renderer) are not complete enough. I'll open an issue there.


BSQL Q04 fails multi-node SF10K with UVM off

BSQL Q04 fails at SF10K on the 17-node cluster with TCP and UVM off ("existing" allocator for blazing)

This has been resolved. Closing.


genes link

this page  doesn't have the genes listed
https://www.pombase.org/ref_genes/PMID:16884933

Oh dear.  Looks like all publication pages that contains orthologs have the bug.  I'll fix that now!

I think I've fixed that in time for the nightly load.  I'll check in the morning.

Fixed.


Extend submitter factory

This change extends the submitter factory such that it can create new QIR submitters for standalone executables.

/azp run

/azp run

Closing in favor of  https://github.com/microsoft/qsharp-runtime/pull/1004.


@joaoasilva Corrected file

@joaoasilva Corrected file
ts0601_trv_rtitek.py.zip
Originally posted by @jacekk015 in https://github.com/zigpy/zha-device-handlers/issues/1159#issuecomment-982556768
Hi, I tried this file but I get the following sliders that look wrong. As soon as I touch one of them, I'm unable to set the temperature any more and I have to reset the thermostat

Such values does not make sense, it seems it depends on a wrong initialization in the quick but I coulnd't find how to fix them

This is what I find from row 38:
RTI_TARGET_TEMP_ATTR = 0x0202  # target room temp (decidegree)
RTI_TEMPERATURE_ATTR = 0x0203  # current room temp (decidegree)
RTI_MODE_ATTR = 0x0401  # [0] schedule [1] manual [2] off [3] on
RTI_CHILD_LOCK_ATTR = 0x010C  # [0] unlocked [1] locked
RTI_TEMP_CALIBRATION_ATTR = 0x0265  # temperature calibration (degree)
RTI_MIN_TEMPERATURE_ATTR = 0x020F  # minimum limit of temperature setting (decidegree)
RTI_MAX_TEMPERATURE_ATTR = 0x0210  # maximum limit of temperature setting (decidegree)
RTI_WINDOW_DETECT_ATTR = 0x0108  # [0] alarm not active [1] alarm active
RTI_BOOST_ATTR = 0x0104  # [0] off [1] on
RTI_BOOST_COUNTDOWN_ATTR = 0x0205  # (seconds)
RTI_VALVE_POSITION_ATTR = 0x0266  # opening percentage /10
RTI_VALVE_STATE_ATTR = 0x0406  # [0] closed [1] opened
RTI_BATTERY_ATTR = 0x020D  # battery percentage remaining 0-100%
BECA_SCHEDULE = 0x1111  # schedule
# [6, 0, 40, 11, 30, 42, 13, 30, 44, 17, 30, 46, 6, 0, 48, 12, 0, 46, 14, 30, 44, 17, 30, 42, 6, 0, 38, 12, 30, 40, 14, 30, 42, 18, 30, 40] for :
# Monday to friday : 06:00 20°C / 11:30 21°C / 13:30 22°C / 17:30 23°C
# Saturday : 06:00 24°C / 12:00 23°C / 14:30 22°C / 17:30 21°C
# Sunday : 06:00 19°C / 12:30 20°C / 14:30 21°C / 18:30 20°C )
RtiManufClusterSelf = {}


Reword accepting of client messages

After an identity has been assigned, it is mandatory to accept messages
from other clients.
Fixes #135

I believe our intention was to state that at least one client-to-client communication MUST be accepted but further clients MAY be accepted. I'm not sure whether we've handled that in the description.


error: Long constructor is no longer supported, use BigInt type instead

Can't use the module!

maybe start using a real proxy? using pinkie's proxy was your first mistake.
https://discord.gg/maqBmJV
If you install Caali's tera-proxy, it will auto update and download the latest opcodes, packet definitions, and compatible modules - meaning you'll never have to manually update anything!
A more detailed explanation can be found in the #info and #proxy channels of the linked discord.

WP kasea


Rolling back docker version

Doesn't look like this is resolving the issue, but maybe the :latest image that it pulls needs to be created with the same version of Docker? If so, it could resolve after the next release. Hard to say. What was the reason for changing to this version?

We wanted compatibility with singularity (for automatic image size
assessment), but it did not work anyway. No benefits for using the never
version. We can try with this one and do a quick release fixing the
conformation issues.
On Tue, Jun 13, 2017 at 10:21 AM, Chris Markiewicz<EMAIL_ADDRESS>
wrote:

Doesn't look like this is resolving the issue, but maybe the :latest
image that it pulls needs to be created with the same version of Docker? If
so, it could resolve after the next release. Hard to say. What was the
reason for changing to this version?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/pull/556#issuecomment-308187909,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkpxCNJ-3o3Bs4W9E_NM_03Eyh-MXQks5sDsUXgaJpZM4N4vsZ
.

I'm okay with merging this without a full build... it'll get built after merging anyway.


Replace All should run search if no search ran before

Testing #8184.

VSCode Version: Insider 6/29
OS Version: Windows 10

Steps to Reproduce:

" View: Show Search"
Expand Replace field
Enter a search string
Tab to replace field
Enter a replace string (or keep it empty)
Tab to Replace All button
Press Enter

You get:

Fixed by #8302 and #8330


feat: Add site content

Create site content for landing page (override default templates)

Hey @rojoneon !
Please update all fields that includes the following syntax:
@todo []

Also if you have any idea to add more content, please see the following markdown reference: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
Please consider using this conventional commits guide: https://www.conventionalcommits.org/en/v1.0.0/


[Python Client 2.6.1] Unable to pip install 2.6.1 client for Python

Describe the bug
Documentation says Python Client for 2.6.1 is available https://pulsar.apache.org/docs/en/client-libraries-python/
but executing pip install only shows the latest as 2.6.0
To Reproduce
Steps to reproduce the behavior:

$ pip3 install pulsar-client==2.6.1
Get Response  ERROR: Could not find a version that satisfies the requirement pulsar-client==2.6.1 (from versions: 2.5.1, 2.5.2, 2.6.0) ERROR: No matching distribution found for pulsar-client==2.6.1

Expected behavior
Python Client for Pulsar 2.6.1 is found and installed
Screenshots
See above
Desktop (please complete the following information):
 $ python3 --version Python 3.8.5  $ pip3 --version   pip 20.1.1 from /usr/local/lib/python3.8/site-packages/pip (python 3.8)
Additional context
Add any other context about the problem here.

@wolfstudy Could you please help take a looks at this issue? look 2.6.1 does not upload to the pypi

@frankjkelly Now we can use the client of python 2.6.1 normally

Thanks - confirmed on my side too. Just for my understanding was there some "fix" or perhaps just some delay of some sort in PyPi caches?

Just for my understanding was there some "fix" or perhaps just some delay of some sort in PyPi caches?

Yes, Can you install pulsar_client 2.6.1 locally?

Yes I can.

Yes I can.

Thanks @frankjkelly feedback this issue, will close it, If there are other related questions, please reopen it or let me know, thanks.


Changed parameterization of run_callbacks to make it run on Rails 4

This change makes before_render run with Ruby 2.1.0 on Rails 4.0.2

+1


Does Microsoft Project Actually Import to ADO?

I see several references in this page to importing from Microsoft Project related to successor-predecessor relationships. From the research I have done into this, I there is no default way to import from project to my ADO board, nor is there an extension that has worked for my organization. If there isn't a reliable way to connect project to ADO, I'm concerned that this document is promoting something that doesn't really exist (or perhaps doesn't exist yet).
Alternatively, if there is a way to connect project to ADO reliably and I am just ignorant I would love some support to get that up and running!
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: d9818350-b7e0-7789-95b4-77d5c5dd472e
Version Independent ID: e4318c77-d744-e056-fc2a-4aa879be22cc
Content: Link types reference guide - Azure Boards
Content Source: docs/boards/queries/link-type-reference.md
Service: azure-devops-boards
GitHub Login: @chcomley
Microsoft Alias: chcomley

@EmmettRoehr -- Emmet, thank you for your feedback.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@chcomley -- Chrystal, please look into this issue.

Hi @EmmettRoehr, thanks for bringing this to our attention. Since this integration has been deprecated for years, I've removed the references. I'm sorry for the confusion and happy that others will now have clarity!


Regarding beginner friendly Dart webdev resources

Hi angularDart team!!
I must say that I'm a huge fan of your work and please do feel free to close this issue as it's more about having more beginner friendly resources rather than some technical debt.
The thing is, I'd love to build some AngularDart UI and for that I need to know how the entire

FIRST priority -> Code and Feedback cycle work, something like live-reload.
This could be added to the generic template menu in IntelliJ dart stagehand package

SECOND priority -> How exactly am I supposed to use the DDC with the IntelliJ plugin.

A bit more stress on the AngularDart documentation from the perspective of someone who's getting started with AngularDart itself rather than TypeScript.

There is no live-reload support for Dart web development (currently only Flutter)
There is currently no DDC support for Angular (seems to come with version 4)

So @zoechi , could something like that demo from Dart Conference be used to achieve the same effect?
https://github.com/vsmenon/dart-jsinterop-quill

i think, the talk at the conference was a proof of concept that with ddc and regular chrome you can get a development cycle similar to what we have now with dartium and pub serve.
interaction with dartium from an IDE is not supported by the free intellij community edition, you can do it only with webstorm.
you can always run pub serve from the command line and use dartium/chrome webdev tools.(using regular chrome is WAY slower because there is always a compile step with dart2js included).

@abhi18av with DDC it's not Dartium but plain JS (generated by DDC) with Chrome which does support life reload.
AFAIK with WebStorm/IDEA it doesn't work because Dartium is a few versions behind (perhaps this has changed with updates since I tried a few months ago, but it seems it's not officially supported with Dartium by Jetbrains)

Hot reload is tracking via https://github.com/dart-lang/angular2/issues/160
DDC support is planned for pub - tracking via https://github.com/dart-lang/angular2/issues/171
Please file bugs directly against our documentation if you can: https://github.com/dart-lang/site-webdev


Linode 400: Invalid JSON;

Home Assistant release with the issue:
0.67
Last working Home Assistant release (if known):
Unsure
Operating environment (Hass.io/Docker/Windows/etc.):
pip3 install on Debian 9
Component/platform:
https://www.home-assistant.io/components/linode/
https://www.home-assistant.io/components/binary_sensor.linode/
Description of problem:
Component fails to load with 400 error
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
linode:
  access_token: !secret linode_api_key

binary_sensor:
  - platform: linode
    nodes:
      - 'linode2008320'

Traceback (if applicable):
2018-04-13 21:42:01 ERROR (Thread-12) [homeassistant.components.linode] 400: Invalid JSON;
2018-04-13 21:42:01 ERROR (Thread-12) [homeassistant.components.binary_sensor.linode] Node linode2008320 is not available

Additional information:
This has been broken for quite some time now but I'm finally wanting to get back to leveraging the component for monitoring of my VPS.

I am seeing the same behavior on 0.69


⚠ gorzdrav.org has degraded performance

In 028b830, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 1911 ms

Resolved: gorzdrav.org performance has improved in 977819f.


cupy raw kernel cannot handle view of cupy ndarray

Description
When feeding a view of cupy ndarray into a kernel, for example, a slice of a big ndarray, the result looks like the kernel read the original big ndarray not a slice of it.
To Reproduce
import cupy as cp
x = cp.arange(10, dtype=cp.complex64).reshape(2,5)

show = cp.RawKernel(r'''
#include <cuComplex.h>

extern "C" __global__
void show(const cuFloatComplex* x, const int N){
  int i = blockDim.x * blockIdx.x + threadIdx.x;

  if(i == 0 ){
      printf("%f\n",cuCrealf(x[N]));
  }
}
''', 'show')

When call the kernel:
show((2,), (5,), (x,cp.int32(6)))
cp.cuda.runtime.deviceSynchronize()

It will print:
6.000000

But if feed a slice of x:
x_slice = x[:,:4]
show((2,), (5,), (x_slice,cp.int32(6)))
cp.cuda.runtime.deviceSynchronize()

It also print:
6.000000

which is not as wanted.
However, if a copy is fed:
x_slice = x[:,:4].copy()
show((2,), (5,), (x_slice,cp.int32(6)))
cp.cuda.runtime.deviceSynchronize()

It print:
7.000000

as expected.
Installation
Conda-Forge (conda install ...)
Environment
OS                           : Linux-3.10.0-1127.18.2.el7.x86_64-x86_64-with-glibc2.17
Python Version               : 3.9.13
CuPy Version                 : 11.2.0
CuPy Platform                : NVIDIA CUDA
NumPy Version                : 1.23.4
SciPy Version                : 1.9.3
Cython Build Version         : 0.29.32
Cython Runtime Version       : None
CUDA Root                    : /users/kangl/miniconda3/envs/rapids-22.10
nvcc PATH                    : /users/kangl/miniconda3/envs/rapids-22.10/bin/nvcc
CUDA Build Version           : 11020
CUDA Driver Version          : 11040
CUDA Runtime Version         : 11070
cuBLAS Version               : (available)
cuFFT Version                : 10702
cuRAND Version               : 10301
cuSOLVER Version             : (11, 4, 0)
cuSPARSE Version             : (available)
NVRTC Version                : (11, 7)
Thrust Version               : 101000
CUB Build Version            : 101000
Jitify Build Version         : 343be31
cuDNN Build Version          : None
cuDNN Version                : None
NCCL Build Version           : 21403
NCCL Runtime Version         : 21403
cuTENSOR Version             : None
cuSPARSELt Build Version     : None
Device 0 Name                : Tesla V100-SXM2-32GB
Device 0 Compute Capability  : 70
Device 0 PCI Bus ID          : 0000:15:00.0

Additional Information
No response

This is expected. When you only pass a raw pointer to a kernel, it's assumed that the array is contiguous in memory. If you want to handle views, you should also pass the array shape/strides and distribute the workload to each thread yourself. CuPy has the machinery for doing so, but I am not sure if they are considered public API. If it's simple Elementwise operation, it's better to just use ElementwiseKernel instead.

Thank you @leofang for your comments! I didn't find the public API in cupy document so I will run deep copy before feeding my RawKernel. I want each thread work on a small patch of a big array. I didn't find the way to use ElementwiseKernel. If there are any smart way to achieve, please let me know! I appreciate it!

I want each thread work on a small patch of a big array.

It's unclear to me what you intended to do. If you can show us a version that you expect to work with contiguous arrays, we might be able to suggest alternative approaches.

Thanks for your nice help! I finally find a way to implant it with elementwise kernel with the raw keyword so I don't need to bother you for this question.
I wonder if there is any easier way to index a multidimensional array? For example, the element of the diagonal of a N*N matrix a can be easily indexed by a[i,i], but in the kernel, I have to use a[i*N+i] which is not intuitive. Thanks!

Glad to know it works for you! AFAIK you need to use 1D indexing with ElementwiseKernel. It has to do how the internal machinery is designed to handle array views. Moreover, 1D indexing should be familiar for most C/C++ programmers 🙂


Add Colorblind options from nightfox.nvim

It would be really neat to have the colorblind customization options that are in nightfox.nvim. Not sure what's possible via Zed's extension API.

Thanks for looking into it! :)


Factories use the wrong connection when called from a PHPUnit v10.x static data providers

When I use a Factory to prepare some fixture data in a static data provider, the records are created in the default database rather than the testing database
This is the kind of thing I'm doing:
    /**
     * @dataProvider normalizeArgVariants
     * @param $input
     * @param $expected
     * @return void
     */
    public function test_someMethod($input, $expected)
    {
        //test logic;
    }

    public static function normalizeArgVariants(): array
    {
        $oldNode = NodeFactory::make(1)->persist();

        return [
            [$oldNode, $oldNode->id],
            [12, 12],
            ['122', 122],
    }

I'm struggling a little with this change to static data providers in general, so perhaps this is the wrong approach?

This seems to be related to #187 .
Aliasing the connection as jamisonbryant suggested in his March 16 update to his issue helped, but didn't completely solve my issue.
Making the changes in bootstrap got me past a 1062 Duplicate entry '1741177057' for key error but records are still being written to the wrong db. That result is actually more confusing.


Add some basic checks to not make forks break

This MR makes sure that my own fork will do some basic tests still, so I can submit my MR with confidence beyond "runs on my machine"


model: tensorflow: 2.2.0 Support

Yesterday (May 7th 2020) TensorFlow 2.2.0 was released. It looks like it broke
something. Probably related to the docstring parsing we're doing to generated
configs.
Going to temporarily set the install range to >=2.0.0,<2.2.0
Ping: @0dust

When we fix this we should re-enable the Python 3.8 in .github/workflows/testing.yaml by removing the tensorflow dependent packages from the if statement that is exiting 0 if we're on Python 3.8.

@pdxjohnny I am working on it.


Docker image - server fails to initialise correctly

The Docker image pulled from ibmcom/ibm-fhir-server fails to start correctly.
To Reproduce
Steps to reproduce the behavior:

Pull the Docker image from https://hub.docker.com/r/ibmcom/ibm-fhir-server
Ensure Docker Desktop is running (I am using Windows 10)
In a bash shell in WSL2, start an instance of the image using docker run -p9443:9443 ibmcom/ibm-fhir-server
Once the server appears to have started, use the recommended health-check: curl -k -i -u 'fhiruser:change-password' 'https://localhost:9443/fhir-server/api/v4/$healthcheck'
Observe the console output.

Expected behavior
FHIR server startup, followed by a successful health check.
Observations
The console output suggests an issue with the embedded Derby database:
[ERROR   ] Encountered an exception while bootstrapping the FHIR database
java.sql.SQLNonTransientConnectionException: No current connection.

And the servlet context fails to initialise:
[ERROR   ] SRVE0283E: Exception caught while initializing context: java.lang.RuntimeException: Encountered an exception while initializing the servlet context.
        at com.ibm.fhir.server.listener.FHIRServletContextListener.contextInitialized(FHIRServletContextListener.java:208)
        at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:2433)

Additional context
My environment:
Windows 10 Professional Edition
Version	10.0.18363 Build 18363
Docker Desktop: v3.1.0
Docker Engine: v20.10.2
Using the WSL2 integration.
I have saved a complete copy of the console output in a public gist: https://gist.github.com/searjeant/1ba53621abe92cc783eec0a9a3969574
I did read (and re-read) the configuration documentation on the Docker Hub page, but I wanted to ensure I could start the default container first, before making any of the changes described on that page.
Apologies if I have missed something obvious - I'd appreciate a hint.

Can you please try setting the following environment variable?  FHIR_TRANSACTION_MANAGER=120s
What we've seen from some folks is that the derby bootstrapping is timing out.
We really should move that bootstrapping step to the image startup so that its not bound to the same transaction timeout as normal requests are, but we havn't gotten to that yet.
If this doesn't help, then let us know and we can look at the logs.

Can you please try setting the following environment variable?  FHIR_TRANSACTION_MANAGER=120s
What we've seen from some folks is that the derby bootstrapping is timing out.
We really should move that bootstrapping step to the image startup so that its not bound to the same transaction timeout as normal requests are, but we havn't gotten to that yet.
If this doesn't help, then let us know and we can look at the logs.

@searjeant did Lee's comment address your issue?

I am getting the exact same issue on Windows 10. Setting FHIR_TRANSACTION_MANAGER=240s did not fix the issue.

My apologies.  The variable name is FHIR_TRANSACTION_MANAGER_TIMEOUT and not FHIR_TRANSACTION_MANAGER.
I can force a very similar stack trace on my MacBook by launching like this:
docker run -p 9443:9443 -e FHIR_TRANSACTION_MANAGER_TIMEOUT=10s ibmcom/ibm-fhir-server:4.5.4
and so I really think this is the issue.

Thanks for the quick response - unfortunately I am still receiving the same error when FHIR_TRANSACTION_MANAGER_TIMEOUT is set to 240s.

@danarteaga can you post an updated log? the reference in gist is without running with the FHIR_TRANSACTION_MANAGER_TIMEOUT=240s (as shown in the commandline)

Ahh, setting FHIR_TRANSACTION_MANAGER_TIMEOUT=600s did the trick. Just for your information, here is my hardware setup:
Processor	Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz, 2112 Mhz, 4 Cores
RAM         	16.0 GB
Thank you for your help with this.

Right, it's the allocated resources in your Docker setup.  You can cap the total cores and available memory.

@danarteaga @searjeant I hope all is well.  If there is any followup, we're happy to re-open.
Keep asking questions/opening bugs, we'll work on it.


[feature] Add a way to beam back when there is only one page in the stack

Use case
The way beamer work is by having a stack of page. When there is only one page in the stack then there is no pop button because there is nowhere to beam to.
However it is very common that you'd have some pages that would de facto need a back button (not a pop, a back button).
For example, an AboutThisApp page, you can access it from anywhere in your app, because most often this type of page is accessible via a menu.
The build method of the BeamLocation for the about page is very simple:
  List<BeamPage> buildPages(BuildContext context, BeamState state) {
    return [
      BeamPage(
        key: ValueKey('about-screen'),
        child: AboutScreen(),
        title: '${AppInfo.appName} - About',
      ),
    ];
 }

Then in the scaffold of the about page, you have to add a back button that beams back to the last page in history.
          appBar: AppBar(
            title: Text('Preferences'),
            leading: Beamer.of(context).canBeamBack ? BackButton(
              onPressed: () => Beamer.of(context).beamBack(),
            )  :  null,

Proposal
What I'm proposing is to have an option to do this automatically, so the back button is added and the behavior is changed to beam back instead of pop.
      BeamPage(
        key: ValueKey('about-screen'),
        child: AboutScreen(),
        title: '${AppInfo.appName} - About',
        // something here, a callback would allow for more customization
      ),

Hi @cedvdb
This is an interesting feature that I somewhat ignored in the past mostly because it's not straightforward to implement, but I think we should put some efforts into this.
Facts

BeamPage.beamBackOnPop: true can be used to call beamBack() instead of pop() when one presses the AppBar's BackButton
BackButton is added automatically as AppBar.leading widget if automaticallyImplyLeading == true (which is the default)
it would seem that to determine if BackButton should be the leading, Flutter checks if Navigator.canPop (this is false if there is only 1 page in the Navigator.pages stack), but after a coser look, it doesn't go like that. It checks ModalRoute.of(context).canPop

ModalRoute.of(context).canPop
bool get canPop => hasActiveRouteBelow || willHandlePopInternally;

  bool get hasActiveRouteBelow {
    if (_navigator == null) return false;
    for (final _RouteEntry entry in _navigator!._history) {
      if (entry.route == this) return false;
      if (_RouteEntry.isPresentPredicate(entry)) return true;
    }
    return false;
  }

  bool get willHandlePopInternally {
    return _localHistory != null && _localHistory!.isNotEmpty;
  }

This seems very complex to override.
Possible solutions

Harder: Somehow override the ModalRoute.of(context). The only place this can be used is at BeamPage.createRoute, but I'm not sure how would it go from the top of my head. We would definitely need to create a custom Route for this. Seems like a lot of trouble and maybe highly susceptible to future changes in Flutter framework.

Easier: add BeamerAppBar widget that would be exactly as AppBar (would return AppBar in its build), but will assign leading back button if Beamer.of(context).canBeamBack || Navigator.of(context).canPop (otherwise it would leave the leading: null) and fallback to beamBack if it didn't pop.

BackButton(
  onPressed: () async {
    final didPop = await Navigator.of(context).maybePop();
    if (!didPop) {
      Beamer.of(context).beamBack();
    }
  }
),

Conclusion
I think Solution 2 is a way to go.
Would you like to work on this feature and make a PR?

possibly not receiving updates that the flutter framework can offer, etc

Not if we are literally returning AppBar in the build method, but I understand your concern; I also don't want beamer to go into UI much.
(and this would also be the case with solution 1 where we would need to override things)

I've trouble understanding without context

I'll try to explain some more.

the decision to show a BackButton to the AppBar is made by Flutter
this BackButton always does Navigator.of(context).maybePop()

One would assume that Flutter therefore checks Navigator.of(context).canPop to determine to show the BackButton, but this is not the case. Snippets that I pasted are from Flutter source code that follow the logic needed for determining whether to show the BackButton, i.e. the logic we would need to override.
In the AppBar source code we have this
Widget? leading = widget.leading;
    if (leading == null && widget.automaticallyImplyLeading) {
      if (hasDrawer) {
        leading = IconButton(
          icon: const Icon(Icons.menu),
          iconSize: overallIconTheme.size ?? 24,
          onPressed: _handleDrawerButton,
          tooltip: MaterialLocalizations.of(context).openAppDrawerTooltip,
        );
      } else {
        if (!hasEndDrawer && canPop)
          leading = useCloseButton ? const CloseButton() : const BackButton();
      }
    }
    if (leading != null) {
      leading = ConstrainedBox(
        constraints: BoxConstraints.tightFor(width: widget.leadingWidth ?? _kLeadingWidth),
        child: leading,
      );
    }

The rest of the snippets I pasted follow the implementation of canPop from this part
 if (!hasEndDrawer && canPop)
          leading = useCloseButton ? const CloseButton() : const BackButton();

Yeah I'd personally not use it and prefer to add the button myself if that was there, you know, just in case. If new params are added to the AppBar, then the BeamAppBar won't have it from the get go because of the constructor.


Full Support for Type Providers on .NET Core 2.0

From #2400:

This also takes a dependency on RefEmit. We’ll need to investigate this further, since it’s currently not on the .NET Core 2.0 roadmap

Also would like to add this comment here from @KevinRansom on #2400:

The problem with generative TypeProviders is that ref emit on coreclr doesn't implement Save(). Ref emit is not actually a part of .Net Standard 2.0 the System.Reflection.Emit package will work with fine with .Net Standard 2.0, it's just those Apis are not part of the .Net Standard set of Apis and so ... there is no urgency to improve it's desktop compatibility. The problem for F# is that generative type providers need to produce a P.E file and since the the Save() API doesn't exist, we need a clever solution to that problem. There are in fact plenty of approaches we could take ... we just haven't settled on one that is the obvious winner.

I cornered Jan Kotas in the corridor the other day and tried to push him to commit to getting us Save, he urged us to seek other solutions ...

So ... we need an alternate solution, regardless until .Net Standard 2.0 we can't do much with type providers given that Type has a private constructor on the coreclr, at least in the reference assemblies it is, the implementation still has a protected constructor. So I suppose we could do type reference magic to get something working.

and from @cartermp

Erasing Type Providers (which are more common) should not require System.Reflection.Emit, but Generative Type Providers will. We'll first need to ensure that with the .NET Standard 2.0 APIs coming along, that we can at least support Erasing Type Providers. If that's the case, then many of the type providers in the wild could conceivably be used, assuming there are no other issues we run into.

For Quotations, it's a somewhat similar story. They don't require System.Reflection.Emit, but they are needed for fully-fledged quotation evaluators/compilers, and are needed if they are used as input to a Generative Type Provider.

What I think may be likely is that we'll have support for the "95% case" in these areas, but we could still be blocking key libraries and library authors if they are building full-on quotation compilers and Generative Type Providers.

All of the above is assuming that we don't do any work in those areas ourselves. @KevinRansom can speak more towards the feasibility of that, but given the amount of work we're doing right now, I don't find it likely that rewrites of those areas of TPs and Quotations will come from someone in Redmond between now and .NET Standard/.NET Core 2.0.

Do we know why Save() from System.Reflection.Emit is not part of .NET Standard 2.0? Explanation page or some discussion that may be linked? // cc @terrajobst
What alternatives we have if Save() will not be part of .NET Standard 2.0?
I think that I have a TP that should be generative - SwaggerProvider.
In we could keep this TP generative and port it to .NET Standard 2.0, it will allow mobile developers to consume generated types in C# / Xamarin.Forms projects. If generative TP is not supported, I will have to convert this TP to erasing and discontinue C# support. 😢

The issue is tracked here
https://github.com/dotnet/corefx/issues/4491
and there is a linked issue created by Kevin explaining in-depth what this means for F#...

Ok, found issue created by Kevin - https://github.com/dotnet/coreclr/issues/1709

Duplicating my comments from the other issue this is linked from:
One of the big things is that generative type providers service the wider ecosystem not just F#, they are the most important aspect in that respect.
Unchecked quotations for generative providers is also something that sorely needed to avoid having to reflectively call quotation builders to build the type provider.

How about the successor(?) of IKVM.Reflection.Emit from Jeroen Frijters as his name already mentioned in the System.Reflection.Emit.AssemblyBuilder.Save corefx issue [1]? A preview release are available from NuGet.
"Managed.Reflection is a fully managed replacement of System.Reflection and System.Reflection.Emit. Unlike System.Reflection, it is not tied to the runtime it is running on.
It targets .NET Standard 1.3, which means it runs on .NET Core 1.0 and .NET Framework 4.6 and up."
Repository:
https://github.com/jfrijters/Managed.Reflection
[1] https://github.com/dotnet/corefx/issues/4491#issuecomment-189756092

@zpodlovics considering the comments I think (after discussing with the maintainers of course) such a PR making it work would be welcome... Its just nothing they have time for right now

Ive partially patched reflection stuff with IKVM.Reflection when I was working on an iOS feature for xamarin so it could be worth investigating.

@dsyme / etc Would a PR that used a dotnetcore version of ilvm reflection be accepted here?

@7sharp9 You mean Managed.Reflection?

Could Erasing Type Providers already work (in theory)? IDE (e.g. Visual Studio) is run on non-dotnet-core mode and the compiled code should be run on dotnet core / standard?

@Thorium Yes, in theory Erasing TPs should work on .NET Core 2.0, and thus could target .NET Standard 2.0.  That assessment still has to be done.  Just last week, support for .NET Core 2.0 has been merged as in-band for the .NET Core SDK, so the assessment and proper work here can now be done.

@sergey-tihon Yeas I meant Managed.Reflection, with that project hanging in the balance Im in two minds whether to use it as a replacement.

To get generatives working do we just have to re-write providedtypes.fs to use an alternative @cartermp / @sergey-tihon

The problem with generative TypeProviders is that ref emit on coreclr doesn't implement Save().
Save is used unless the  FX_NO_LOCAL_FILESYSTEM define is there.

Well, can I help here somehow?

I believe we are blocked on having the compiler target .NET Core 2.0

What's current status of the issue? There are too many issues related to TP support in .Net Core/Standard, not easy to pick needed info.
Thanks!

No update on status at the moment.  We're looking at this once .NET Core 2.0 is released.  #3303 is a workaround for now.

What's the status of this?

Is this at the top of the list now that 2.0 has been released?

@sjuberman Not at the moment.  Top item for us is enabling support for .NET Core projects in Visual Studio.

from https://github.com/Microsoft/visualfsharp/issues/1496#issuecomment-244315047

re-architect the fundamental F# compiler API used by type providers to no longer use any F# quotations or any extensible reflection (inheriting from Type/MethodInfo/FieldInfo/... types). While this would be architecturally cleaner and more independent in many ways, it is also a big undertaking, and would require significant corresponding changes to the ProvidedTypes programming model for authoring type providers. This model uses extensible reflection in many places, e.g. here and here

@dsyme Would a PR with this be accepted? Even if this means changing the ITypeProvider interface or adding another interface in addition? Even if this means that another dependency (like Mono.Cecil) is introduced?

@dsyme Would a PR with this be accepted?

Hmmm... it's a big, big job, and with .NET Standard 2.0 it's no longer clear it's worth it to me.
The really hard thing is the representation of code (currently quotations).  Duplicating out a representation code free of System.Type would be a huge job, and probably bring as many problems as it solves.
With .NET Standard 2.0, I'm much more confident that System.Type and MethodInfo etc. are here to stay as a fundamentally reasonable representation of code, even still with plenty of quirks.  My investigation of building type providers using just .NET Standard 2.0 was very encouraging.

Even  if this means changing the ITypeProvider interface

No, backward compat would be needed

or adding another interface in addition?

Yes, you'd probably need a set of new interfaces

Even if this means that another dependency (like Mono.Cecil) is introduced?

Another dependency wouldn't be accepted

@dsyme So I'd assume that would be a no? I'm just curious if there would be a benefit in rethinking this, for example better fable support by being more independent of IL?

... for example better fable support by being more independent of IL?

Yes, I was wondering what the situation would be with Fable.  Is System.Type and/or quotations considered part of the Fable programming model?

At some point there was quotation support in Fable but I removed it because it was flaky and I didn't find many practical uses for it. About System.Type and reflection in general, there's some limited support in Fable.
However, I don't think this is an issue. Fable 0.7 was compatible with TPs (I'm only talking about erasure TPs here) and FCS already gave you the erasure code in the AST, so I didn't have to worry about quotations, etc (FCS did crash sometimes when accessing the AST generated by TPs but most of the cases were fixed).
The main issue with TPs and Fable was that most of the TPs generated code that used BCL APIs not supported by Fable (IO, networking). That's the reason Fable and TPs haven't had a nice story together so far.
Example of a type provider that was compatible with Fable at the time.

However, I don't think this is an issue. Fable 0.7 was compatible with TPs

Hmmm... that's probably with the F# compiler running as a .NET Core or .NET Framework component. I think the Fable-compiled FSharp.CompilerService was compiled without TP support, cc @ncave

Yeah, sorry. I was talking about running Fable on .NET. When compiling FCS to JS I'm not sure, maybe it makes sense to have a specific mechanism for Fable that emits JS directly, similar to how the Emit attribute works.

I'm more interested if we could fundamentally improve the situation with different APIs. For example does fable even have to know about type providers or could that be an implementation detail?
Also should TP resolve/introduce their own dependencies or use an API provided by the compiler for that?

@dsyme @7sharp9 @matthid I'd like to discuss the current difficulties in generative type provider support for .NET Core.
I am still new in the land of type providers, so I could ask really silly things, but could you please give me the directions? Please correct me if I'm saying anything wrong.
We've done a small research with @Dolfik1 on that matter, and have came to the following conclusions.

The main (or at least the first) issue is the usage of AssemblyBuilderAccess.Save in the type provider template:

This isn't possible on .NET Core (AssemblyBuilderAccess.Save doesn't even exists).
There's the supporting code under the FX_NO_LOCAL_FILESYSTEM flag, but I highly doubt it does the right thing.
Compiler really need these bytes (it will load load them and use the code from that generated assembly).

That means that we need to somehow generate the bytes from the dynamic assembly generated by the type provider, no matter what.
We cannot change the public API of ProvidedTypes.fs, but we could change its' implementation if we really need to.

If these conclusions are correct (and saving the generated assembly is really the biggest problem), then we could really come up with some hacky (hopefully not very intrusive) solution to make it work. Currently I'm thinking about using Mono.Reflection to parse the bytecode of the dynamic assembly generated by the type provider (✓ have verified that it works on .NET Core 2.0) and then Mono.Cecil to generate the byte array of that assembly.
I have some questions regarding that.

Are my conclusions right? Or is there something I haven't noticed yet?
Is that okay to change internals of ProvidedTypes.fs without touching the public API?
Will it work in the long term? Or do we have some bigger plans for the generative type providers (migrating them to the new API with or without compat. layer, obsoleting them entirely etc)?
Could such a (hacky?) contribution into FSharp.TypeProviders.SDK be accepted?

I found the System.Reflection.Metadata library, it seems that we can generate assemblies using this library only.

While I can't answer your questions (@dsyme is much better suited for that) i doubt a dependency and third party libraries would be accepted, as that would mean that FSharp.Core will get a dependency outside of BCL. Though I'm  glad someone is looking into this, it's a much needed requirement ;).

@abelbraaksma if that's the biggest issue, we could solve that in one way or another.
One option is to either port or rewrite in F# the corresponding parts of Mono.Cecil/Reflection and/or System.Reflection.Metadata.
But, if I'm following Don correctly, in this comment he suggests us to use the ILReader / ILWriter abstractions from the compiler code. Probably that's the best option for our situation?

@Fornever so far I see the situation we should pick everything existing up. Still though, dependencies are only being added to the F # compiler, not F# Core (how did this come up?).
Your conclusion make sense to me. We should focus on fixing type providers...
I hope to see a response soon from @dsyme (as soon as he can spend time for our questions :) )

@ForNeVeR Yes, your analysis is correct

But, if I'm following Don correctly, in this comment he suggests us to use the ILReader / ILWriter abstractions from the compiler code. Probably that's the best option for our situation?

Yes, I'm wondering if we should just go down that route.  There are pros and cons but it seems like a good option to be free of dependencies.

Alright, then. We have the following plan.
@Dolfik1 is now implementing a prototype of a Assembly -> byte[] function that'll be able to turn any Assembly into a byte array using System.Reflection.Metadata package. I'll work with him to turn that prototype into something useful for type providers.
I propose we first try to convert any simple type provider with our prototype. If that will work (and we won't encounter any blockers), then we could proceed with reimplementation of the prototype in F# with ILWriter or whatever we'll consider useful and @dsyme will approve for use in the Type Provider SDK.
Is that okay?

not F# Core (how did this come up?).

My bad, sorry for the fog. As @dsyme stated:

That's not the case: it is the FSharp.TypeProviders.SDK bits we are talking about, not FSharp.Core

Which moots my comment ;).

@Dolfik1 can you keep me in the loop on the results of your prototype ... it is an interesting proposal.

@KevinRansom Of course. At the moment we have been able to generate a basic assembly, it is not yet valid, but at least dotPeek shows that all the metadata and the IL code are in place.
Right now, me and @ForNeVeR trying to fix validation errors.

@ForNeVeR I'm not sure it's necessary to do a prototype via System.Reflection.Metadata.  I think we should just add the appropriate IL generator and binary writer to ProvidedTypes.fs https://github.com/fsprojects/FSharp.TypeProviders.SDK/tree/master/src

@KevinRansom asked offline

"We have a compiler, why don’t we use it to emit the il?  Is the issue the transformation between refemit types and il?"

Yeah it’s a good question.
First the usual background…
Historically generative type providers were only introduced to allow other code generators (e.g. C# compiler, or svcgen.exe etc) to be hosted as TPs, with a thin erasing wrapper.  In that scenario “some other tool” did the codegen.
Over time the community (I think it was @v2m acting in community mode) added an ability to take this way of specifying erasing type providers (the TP SDK) and repurpose it as a way to author generative TPs, basically the Generate method in the TPSDK.  That uses reflection emit but ended up duplicating some fragments of compiler logic.  (It also has some oddities like allowing DateTime and TimeSpan in the emittable Value constants rather than requiring the user to generate the appropriate quotation for the code to resurrect these.)
On the positive side, the code was outside our repo, and we didn’t need to know anything about it - if people wanted a new feature or to expand the range of quotations allowed then they just sent a simple PR, and all the QA was on the TP SDK.  On the negative side it used Reflection Emit so can’t do cross-targeting.  But the approach basically worked.
So to your question – yes, in theory it would be possible to abandon this approach and instead have the compiler to give each TP a utility method in the TypeProviderConfig, e.g.
member GenerateAssembly: (Assembly -> bytes)

which would internally to the compiler be implemented as either
GenerateAssembly == Assembly --> Abstract IL --> ilwrite.fs --> bytes

Or
GenerateAssembly == Assembly --> TAST --> Abstract IL --> ilwrite.fs --> bytes

Either way this would not use reflection emit and would reuse the ilwrite in the compiler.
However, this still means implementing either Assembly --> TAST or Assembly --> Abstract IL.   That’s largely new logic either way.
Now, for technical reasons Assembly --> TAST is hard.  Not impossible, but it’s hard.   It can only be done inside the compiler for sure and would make use of the “full” compiler stack – IlxGen, state machine generation, optimizer etc. etc.   So reusing the compiler in its full glory is not impossible, but hard.  Somehow it also feels against the original goals of type providers, which was to leverage external code generators in a fairly lightweight way (I'm not saying we achieved that, but this adds extra weight)
However, in reality the code generated by TPs tends to be very simple, and TPs tend to call into runtime library code for anything complex.  That’s why @v2m's  “do assembly generation in the TP SDK” approach worked well enough.  After all, the generated code doesn’t really require full optimization, nor tailcalls, nor any magic done in IlxGen.fs.  And with the TP SDK the community could iterate fast.  And there are some advantages to disincentivizing people from generating complex code using TPs anyway - e.g. there's no debug story for that code.
Anyway, all these are reasons as to why redoing some compilation logic in the TP SDK has historically made sense.
I’ll think it over more, but it still feels to me that the most simple path to unblock is to prototype the Assembly --> Abstract IL --> copy-of-ilwrite.fs in the TP SDK – it feels like just a day’s work to be honest.  It’s much easier to get this stuff up and running outside the compiler (but writing it in such a way that we can bring it in later). If we decide to later reuse what’s in the compiler then we can do that for both ilread.fs and ilwrite.fs together.
p.s. One thing that could force us to go down the Assembly --> TAST route is if generative TPs ever wanted to refer to types in the assembly actually being compiled by the F# compiler, e.g. see https://github.com/fsharp/fslang-suggestions/issues/450 and https://github.com/fsharp/fslang-design/issues/125

@dsyme thanks so much for your comment. It's both interesting and valuable.
Regarding to the "prototype" based on System.Reflection.Metadata: @Dolfik1 just was too enthusiastic about that approach, so he's already done a large part of work, and I feel bad about abandoning it. We could eventually even make this prototype an externally-useful (e.g. not tied to F# type providers) artifact of the research. Also, it seems that we're almost done with the prototype, and it could give us an insight on any further issues we'll encounter while integrating binary writer with the Type Provider SDK.
I agree with your rationale, and we'll try to follow that path soon (probably in a week or two). If anybody wants to begin integrating ilwriter.fs with the Type Provider SDK right now — you're welcome, we'll try to provide any possible help then. If not — then I hope we'll eventually do it.

@dsyme please also consider https://github.com/fsharp/fslang-suggestions/issues/154
Also maybe it's a silly suggestion but maybe we can make the GenerateAssembly  little shorter
And start from TAST it means that type provider produce TAST instead of ProvidedAssembly

@ForNeVeR I'm trying to understand what the role of the AssemblyGenerator would be.  It seems it assumes the assembly coming in has code backed by IL, e.g. here.  But in that case the Assembly would already normally have corresponding bytes in its existing on-disk image.
For generative F# type providers authored using the TPSDK, the situation is that we have an artificial Assembly (i.e. a ProvidedAssembly from the TPSDK) with code given by F# quotations (e.g. InvokerCode in ProvidedMethod).  It is this data that needs to be used to generate the assembly.

@dsyme please also consider fsharp/fslang-suggestions#154

Also maybe it's a silly suggestion but maybe we can make the GenerateAssembly little shorter. And start from TAST it means that type provider produce TAST instead of ProvidedAssembly

The TAST is not a public data structure.
Currently, generative type providers authored using the TPSDK specify the code contents of a generated assembly using quotations, e.g. InvokerCode in ProvidedMethod, in the context of an overall ProvidedAssembly.

@dsyme at the same time, to me it looked like a generative TP would emit the code into the dynamically generated assembly: https://github.com/fsprojects/FSharp.TypeProviders.SDK/blob/36c892674c276265f2c028b8a2e36a99445acb3e/src/ProvidedTypes.fs#L7495-L7496
...and then get its' bytes using the standard assembly.Save call: https://github.com/fsprojects/FSharp.TypeProviders.SDK/blob/36c892674c276265f2c028b8a2e36a99445acb3e/src/ProvidedTypes.fs#L7856
Initially I thought that's the essential part of type provider functioning, but now I'm just a bit confused.

@ForNeVeR Yes, that's correct - though at the start of the process the code for each method is an F# quotation - see that same file

@ForNeVeR The TPSDK has now been updated with support for cross-targeting generative type providers by integrating the binary writer.
You should now be able to build generative type providers for .NET Core though that has not yet been specifically tested (and might require an updated F# compiler for .NET Core).

I'm closing this as the TPSDK has now been updated to support generative type providers when targeting .NET Core
If targeting .NET Standard or .NET Core and using type providers you still need to apply the workaround specified here: https://github.com/Microsoft/visualfsharp/issues/3303.  (That is a blunt workaround for issue #3736 which needs to be resolved (and type providers re-published) before type providers can be created which will load into .NET Core-based tooling)


Section title editing breaks onto a new line

When you click on a title that fits on a single line, it sometimes breaks onto two lines.

It should not do this.

https://github.com/twosigma/beaker-notebook/pull/1819


GrpcChannel thread safety

This document says:
> A channel represents a long-lived connection to a gRPC service. When a channel is created it is configured with options related to calling a service. For example, the HttpClient used to make calls, the maximum send and receive message size, and logging can be specified on GrpcChannelOptions and used with GrpcChannel.ForAddress. For a complete list of options, see client configuration options.
>
> Creating a channel can be an expensive operation and reusing a channel for gRPC calls offers performance benefits. Multiple concrete gRPC clients can be created from a channel, including different types of clients. Concrete gRPC client types are lightweight objects and can be created when needed.
Can the same GrpcChannel be reused in multiple threads at the same time? The docs say that it can be reused across multiple requests, but does not say if this allows multiple concurrent requests, or just multiple sequential requests.

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

ID: 3a7ec3c3-918c-6ffd-1ac0-4f88b89d9295
Version Independent ID: 1c1f72f1-3d5d-3397-c17d-1889dbae6fee
Content: Call gRPC services with the .NET client
Content Source: aspnetcore/grpc/client.md
Product: aspnet-core
Technology: aspnetcore-grpc
GitHub Login: @JamesNK
Microsoft Alias: jamesnk

It is thread-safe.


Error thrown on excluded file.

We noticed in the project I work on that there is a bug with some excluded files. In our automation, the plugin throw an error because it tries to delete an excluded file.
Problem occurs with the use of adressables (the file causing the error was a link.xml generated by adressables in unity)

Hello,
Yes, this seems like a very rare corner-case I missed. I'll patch it up. In the meantime, you can just tweak the code yourself so you don't get this error.
Change the lines after ".meta" deletion (not sure which row, your file looks outdated):
result = ShellUtils.ExecuteCommand(SVN_Command, $"delete --force \"{SVNFormatPath(path + ".meta")}\"", COMMAND_TIMEOUT, reporter);
if (result.HasErrors)
    return AssetDeleteResult.FailedDelete;

... to...
result = ShellUtils.ExecuteCommand(SVN_Command, $"delete --force \"{SVNFormatPath(path + ".meta")}\"", COMMAND_TIMEOUT, reporter);
if (result.HasErrors) {
    reporter.ClearLogsAndErrorFlag();
    return AssetDeleteResult.DidNotDelete;
}

If your project has custom build script or any other automation, I'd suggest adding WiseSVNIntegration.RequestTemporaryDisable() at the start of the process and WiseSVNIntegration.ClearTemporaryDisable() at the end of it, preferably in try-finally block. This will disable the WiseSVN plugin from monitoring the file operations so SVN won't get in the way.
Cheers :)


Improve description for BitMap.grow_mask()

This closes https://github.com/godotengine/godot-docs/issues/5370. Thanks @Swanderrr for the description :slightly_smiling_face:

Thanks!

Cherry-picked for 3.4.


Revisit flags in markets.yml and add a repo to encapsulate the parameters for deployment

Extension to https://github.com/megamsys/megam_gateway/issues/209

we will have to dicuss the markets.yml and see what we can allow to configure. I believe deciding if something is an image or not needs to be configured.

Also track it as a repo for deployment and separate it from `Operation:CI, with just the CI saying - yes i want CI, hence enable it via a flag"

Also, use this issue to change "Assembly, Component" as per the new structure.


Support Java 8 standard runtime

Java8 GAE standard runtime is coming in EA.
With the  latest GAE SDK, you can add <runtime>java8</runtime> in the appengine-web.xml, optionally update your web.xml to be servlet 3.1 based, and you'll be running on a Java8 runtime (when allowed), allowing all Java8 language features (lambdas) on a new security sandbox that does not require a whitelist.
Intellij (and Eclipse) plugins should be ready for the EA process. Deployment will still be whitelisted, but it would be nice to allow EA customers to use these plugins to get early feedback.

Thanks Ludo.  Which version of the SDK includes this?  How do you specify
java8 in the appengine-web.xml?
On Tue, Oct 4, 2016 at 10:06 PM, Ludovic Champenois <
<EMAIL_ADDRESS>wrote:

Java8 GAE standard runtime is coming in EA.
With the latest GAE SDK, you can add java8 in the appengine-web.xml,
optionally update your web.xml to be servlet 3.1 based, and you'll be
running on a Java8 runtime (when allowed), allowing all Java8 language
features (lambdas) on a new security sandbox that does not require a
whitelist.
Intellij (and Eclipse) plugins should be ready for the EA process.
Deployment will still be whitelisted, but it would be nice to allow EA
customers to use these plugins to get early feedback.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/issues/946,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5He9Z4ELID2zbp-wHlAEDCx9G2HOtks5qwwYNgaJpZM4KOWXL
.

Does this mean we should close https://github.com/GoogleCloudPlatform/google-cloud-intellij/issues/847 ?

<runtime>java8</runtime>
Should start working on 1942 for both Flex and Standard, and even better with the coming (anyday now) 1944 or 1945.
Beta setting Quickstart will also be automatically inferred not before than 1946 (trick will be to have no web.xml or a web.xml declaring servlet 3.1 at the top, making it obsolete soon.

Send me privately App Ids you want to be whitelisted.

I think this is another symptom of the same root: I can't import javax.servlet.annotation.WebServlet; because eclipse project facet: Dynamic Web Module can't be set to 3.1.
Side question: @ludoch where should the rest of our web.xml settings go?  I found http://stackoverflow.com/questions/25552491/servlet-3-1-security-constraints-without-web-xml but it implies that not everything can move over 1:1.

@ludoch This is very exciting! Is there any way or channel to get an App ID to you for whitelisting? I would be eager to trial my code in the Java 8 runtime, if possible.

@zmeggyesi sorry to have let your questions fall through the cracks.  I believe that Java 8 whitelisting is very restricted at the moment and should open up early next year.  I'll let @ludoch confirm/deny.

@patflynn That's fine, thank you. I'll keep my eyes open for the announcement, since I'm eager to try the J8 runtime.

Looking at DefaultAppEngineProjectService it appears as though we're already tooled for this.

Finally :-) https://cloud.google.com/appengine/docs/standard/java/runtime-java8


fix issue_assignee_query and pr_assignee_query

@JamesKunstle is this still relevent / necessary?

https://github.com/oss-aspen/8Knot/issues/487 confused bc of the closing and comment of this

#487 addresses the problem but misidentifies the cause as being from the materialized view.
This PR just fixes up the application query to be correct SQL, keeping the materialized view as-is.

still a little confused as to why this doesnt work on your branch in current state as it does on mine (even after rebuild) but they are equivalent so lgtm

Did you delete the existing Redis container?
docker compose down; docker compose up --build
The query wasn't fully correct SQL so it shouldn't work anywhere- it doesn't work in dbeaver. I'm guessing the cache container was still warm despite rebuild, which would happen if you didn't down the compose.

sounds good im good to merge


Question: Working on A7III?

Hello everyone.
I was wondering if this works in the latest firmware i.e 3.01. Anyone tried it out on A7III yet?

The A7M3 does not have an Android subsystem. So no, you cannot run apps on that camera.


fastlane deliver: Potential server error received: 'Unexpected Error'

https://github.com/fastlane/fastlane/issues/16621

Thanks for bringing this to our attention! Have your Bitrise builds started failing with this error? If so, could you link a build URL as an example please?

Same problem here. 6 hours ago I got an app through but since then all fail on this step with the same error:
https://app.bitrise.io/build/635789dfcf50856d#?tab=log

Thanks @bvd-filigrade! We are looking into this ASAP, for the time being we recommend everyone use the Application Loader based deployment step instead.

I have same issues.
https://app.bitrise.io/build/343fa66a9f45161b#?tab=log
https://github.com/fastlane/fastlane/issues/16621

hi guys, can u upgrade the plugin with the latest pre-release of fastlane? https://github.com/fastlane/fastlane/releases

I don't usually do this, but
+1

As a temporary fix, you can update the fastlane version to the fixed release candidate under "Debug":

Release is now available -> https://github.com/fastlane/fastlane/releases/tag/2.150.0


Opening Remote Folder via "Open Folder" is not working reliably

VSCode Version: 1.21.0
OS Version: CentOS 7.4

Steps to Reproduce:

Mount a path via sftp on Nautilus
Select "Open Folder" in VSC and navigate to the desired folder on the remote system.
I expect the folder to be opened in VSC all the time, but this does not happen reliably. More often than not, VSC is not able to open the folder.

Output from the Log (Main):
[2018-03-14 11:48:45.243] [main] [error] [uncaught exception in main]: TypeError: Error processing argument at index 11, conversion failure from undefined
[2018-03-14 11:48:45.243] [main] [error] TypeError: Error processing argument at index 11, conversion failure from undefined
at Object.showMessageBox (/workspace/sbiswas/software/visual-code/usr/share/code/resources/electron.asar/browser/api/dialog.js:277:20)
at /workspace/sbiswas/software/visual-code/usr/share/code/resources/app/out/vs/code/electron-main/main.js:411:422
at new n.Class.derive._oncancel (/workspace/sbiswas/software/visual-code/usr/share/code/resources/app/out/vs/code/electron-main/main.js:81:378)
at Object.factory (/workspace/sbiswas/software/visual-code/usr/share/code/resources/app/out/vs/code/electron-main/main.js:411:384)
at t.e.consume (/workspace/sbiswas/software/visual-code/usr/share/code/resources/app/out/vs/code/electron-main/main.js:105:230)
at /workspace/sbiswas/software/visual-code/usr/share/code/resources/app/out/vs/code/electron-main/main.js:105:17
at new n.Class.derive._oncancel (/workspace/sbiswas/software/visual-code/usr/share/code/resources/app/out/vs/code/electron-main/main.js:81:378)
at t.e.queue (/workspace/sbiswas/software/visual-code/usr/share/code/resources/app/out/vs/code/electron-main/main.js:104:955)
at e.showMessageBox (/workspace/sbiswas/software/visual-code/usr/share/code/resources/app/out/vs/code/electron-main/main.js:411:360)
at /workspace/sbiswas/software/visual-code/usr/share/code/resources/app/out/vs/code/electron-main/main.js:396:77

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

@swarnendubiswas  Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/


fix(azure-registry): handle binary files

Hi!
The issue
We had an issue with fetching certificates from the Azure KeyVaults.
Because the certificate were binary files, the Azure KeyVault would base64 encode it, however the @azure/keyvault-secrets library gives no notice or way to detect that the secret is base64 encoded.
Then kubernetes-external-secrets would base64 encode it again, so the binary files were base64 encoded twice, which meant that we had to alter our application to base64 decode the certificates before we could use them.
This change
Here we add a new keyOptions field isBinary so that you can explicitly specify that the Azure KeyVault secret is a binary and that no base64 encoding should happen.
Notice that the isBinary field does not work together with the property field, as the property field does JSON-decode and that would definetly not work on a Buffer.

Thanks for the tracking this down and submitting the PR :100: !


Add support for pendulum timestamps

We already have support for timestamps when using datetime.datetime, this adds support for timestamps to pendulum_dt.DateTime and pendulum_dt.Date types.  👍

Close it in favor of #185


fix(ci_: Remove tagging workflow

Description
Removes the tagging workflow entirely.

Current dependencies on/for this PR:

main

PR #65   👈

This comment was auto-generated by Graphite.


Dynamic import for delta stream socket bundle in odsp driver.

Description
Dynamic import in odsp driver for non-critical code related to delta stream connection. Seems to save about 21 KB in odsp driver which is about 17% of the current size.

@vladsud Please take a look.

Ping

    this._policies = {

Out of curiosity, why do still have _policies here and also on the odspDelayLoadedDeltaStream ?  Shouldn't it be only on the latter ? And we return the policies from it if we need it.
We would only need to initialize it there and remove the argument from the constructor. Isn't it ?
this._policies = {
// load in storage-only mode if a file version is specified
storageOnly: odspResolvedUrl.fileVersion !== undefined,
};
Just curious.

Refers to: packages/drivers/odsp-driver/src/odspDocumentService.ts:127 in 6263764. [](commit_id = 6263764ad23bcbbb9fb2655004fec273fc4326a7, deletion_comment = False)

    this._policies = {

Out of curiosity, why do still have _policies here and also on the odspDelayLoadedDeltaStream ? Shouldn't it be only on the latter ? And we return the policies from it if we need it. We would only need to initialize it there and remove the argument from the constructor. Isn't it ?
this._policies = { // load in storage-only mode if a file version is specified storageOnly: odspResolvedUrl.fileVersion !== undefined, };
Just curious.
Refers to: packages/drivers/odsp-driver/src/odspDocumentService.ts:127 in 6263764. [](commit_id = 6263764, deletion_comment = False)

If I understand your question correctly, then answer is that somebody can ask for policy even if the delayLoadedDeltaStream is not loaded. So, we don't want to load it unnecessarily just because somebody asked for policy. So, we have initialization in document service constructor and a getter in that file while we need to pass it to delay loaded stream, as it can modify that.


Address is not in the correct format.

I am not having much luck with pushing the DnsServerAddress_Config using the following script. I have tried various formats such as (with signal and double quotes). Please advise.
Examples:
'<IP_ADDRESS>','<IP_ADDRESS>'
'<IP_ADDRESS>', '<IP_ADDRESS>'
'<IP_ADDRESS>';'<IP_ADDRESS>'
'<IP_ADDRESS>', '<IP_ADDRESS>'
'<IP_ADDRESS>' '<IP_ADDRESS>'
Script:
<#
.DESCRIPTION
Configure DNS Server for the Ethernet adapter.
#>
Configuration DnsServerAddress_Config
{
Import-DscResource -Module NetworkingDsc
Node localhost
{
    DnsServerAddress DnsServerAddress
    {
        Address        = "<IP_ADDRESS>","<IP_ADDRESS>"
        InterfaceAlias = 'Ethernet'
        AddressFamily  = 'IPv4'
        Validate       = $true
    }
}

}
Error:
PowerShell DSC resource DSC_DnsServerAddress failed to execute Test-TargetResource functionality with error message: Address '<IP_ADDRESS> <IP_ADDRESS>' is not in the correct format. Please correct the Address parameter in the configuration and try again. (DRC0011) Parameter name: Address

@NFCES - I found that commenting out Validate = $true will result in a successful configuration. Full config is:
Configuration DnsServerAddressTest
{
	Import-DscResource -ModuleName NetworkingDsc

	DnsServerAddress Ethernet_2_DnsServerAddress
	{
	        Address        = '<IP_ADDRESS>','<IP_ADDRESS>'
	        InterfaceAlias = 'Ethernet 2'
	        AddressFamily  = 'IPv4'
#	        Validate       = $true
	}
}

Hi @NFCES, @phbits - that is quite strange. The Validate:$true parameter can cause some problems when assigning DNS, but it doesn't usually show up like this.
What happens if you run the command:
Set-DnsClientServerAddress -InterfaceAlias 'Ethernet' -ServerAddresses "<IP_ADDRESS>","<IP_ADDRESS>" -Validate

on the machine in question? Does it report back the error you see?

Figured it out. The following format appears to work.
Address        = "<IP_ADDRESS>","<IP_ADDRESS>"
InterfaceAlias = 'Ethernet'
AddressFamily  = 'IPv4'
Validate       = $true
}

That is really strange @NFCES - I'd expect this to work:
Address        = '<IP_ADDRESS>','<IP_ADDRESS>'
These would also work:
Address        = @('<IP_ADDRESS>','<IP_ADDRESS>')
Address        = @("<IP_ADDRESS>","<IP_ADDRESS>")
Address        = "<IP_ADDRESS>","<IP_ADDRESS>"

But I'll close this one if that is OK? Feel free to reopen it.


Added release notes for PnP PowerShell 2.2.0

Category

[ ] Content fix
[x] New article

Related issues
Contents of the Pull Request
Added  a new  article to describe the new PnP PowerShell release

Hi @VesaJuvonen / @LuiseFreese  - can you please review this and merge it if its ok ?


trackupstream: Remove Juno, add openstack-murano/python-muranoclient

For the "Remove Juno" part, an answer to the "Why" would be good in the commit message. E.g. dont we want to backport security updates onto a github fork? Would probably need the setup.py dist hack again that I used earlier, because we rely on tarballs in _service files.

@bmwiedemann well, it wasn't tracking juno for ages, so I just removed the leftovers. if you want to use some fork, please enable tracking of that fork..

@dirkmueller There is no muranoclient on Mitaka and its gonna be a bit diffucult to push it to rpm-packaging as it would be missing all dependencies. May be better to wait for Newton instead for muranoclient.

@Itxaka I'm not running python-muranoclient for mitaka. all the python*client packages are excluded anyway, since we're not doing trackupstream there.

Ugh, yes you are right. Keep thinking that is an include instead of exclude due to the !


Add troubleshooting page

Add a troubleshooting page to the website that introduces some difficulties users might face using VirtualBox and Vagrant.

This has been added to the documentation.


Added jump rope counter

 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.

Hi @Ravtscheev, could you please sign the Contributor License Agreement (CLA)? Thanks!


Installation in Linux

Hi,
I'm new to linux and was wondering if someone could guide me with the installation process. Thanks in advance!

Hi there!
I'm not a Linux user myself, but there will be a new release of Ramme soon with way better linux installation using AppImages


Increase timeout for IModelTransformer integration test

@calebmshafer Could you please review? This implements the suggestion from Algirdas.


Handling complex data models in moor

We have 3 tables in our moor DB as follows:
itemMaster ==> (itemID, itemType, itemCategory, status, grossWt)
stoneMaster ==> (stoneID, stoneType, stoneColour, stoneCarats)
itemStoneMapping ==> (itemID, stoneID, stoneCount)
Each item can be mapped to more than one stone and each stone can be mapped to more than one item
I have created 2 model object for the Item and Stone tables as follows
class Stone {
int stoneID;
String stoneType;
String stoneColour;
String stoneCarats;
float carats
}
class Item {
int itemID;
String itemType;
String itemCategory;
String status;
double grossWt;
List stones
}
When fetching a list of items, I might want to filter out the items that have a particular stoneType. For this when I construct an instance of the Item class, I want it to contain instances of all the stones that it has been mapped to.
What would be the best way to achieve this?

Each item can be mapped to more than one stone and each stone can be mapped to more than one item

The itemStoneMapping table seems reasonable for this, but I wonder what stoneCount is doing in there?

For this when I construct an instance of the Item class, I want it to contain instances of all the stones that it has been mapped to.

We have an example for many-to-many relationships like the one you're describing in the documentation, does that help?

I'm closing question issues that are older than a year.
This is one of them.


add more search boxes, unsure about efficiency

Description
Adds mores search boxes.
Efficiency issue, should be more familiar with change detection than I am, does it make sense that GetFacetSearchUpdatePipe is being called for all facets even if only one facet is being typed-in/changed?
Issue
https://ucsc-cgl.atlassian.net/browse/DOCK-215
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that your code compiles by running npm run build
[x] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[x] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[x] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[x] Do not use cookies, although this may change in the future
[x] Run npm audit and ensure you are not introducing new vulnerabilities
[x] Do due diligence on new 3rd party libraries, checking for CVEs
[x] Don't allow user-uploaded images to be served from the Dockstore domain

Tried it in the browser and it seems OK; it's only getting invoked once per facet click.

Hmmm. When I tried it, it seemed to be invoked once per facet with a search box every time I typed or even moved the mouse over a specific search box.

FUNCTION CALLS IN THE TEMPLATES!  WUT?!!?!
Just kidding, they look reasonably light-and-airy, it's fine.


Css class - extension of the current api

Linked to https://github.com/Hrabal/TemPy/issues/34, it' would be good to add some extra api to the tempy.elements.Css.
I was thinking  of a few methods:

replace(element, new_style) : searches for element in  css_attrs and replaces his style dict with the new_style dict (i.e: a new init)
clear(*elements): removes the style of the given elements (full depth search of the element) , if no arg is given clears the whole css_attrs dict.

I would like to start working on this issue. My question is how to you consider this example:
Css({'#id_ex': {
            'color': 'red',
            'div': {
                'color': 'green',
                'border': '1px'
             }
        },
        '#myid': {'color': 'blue'},
        'div': {'color: 'black'}
 })

I suppose that the element in the argument of the replace method is a str. If I provide as element='div', should it replace the last div. If the argument was '#id_ex div', it will replace that div inside #id_ex.

This issue is related to https://github.com/Hrabal/TemPy/issues/33 and (forward-ly looking) to https://github.com/Hrabal/TemPy/issues/40 .
Looking at https://github.com/Hrabal/TemPy/issues/33 , I'd already make this issue to consider TemPy tags (classes or instances) as valid keys for the css div. So all those are valid calls: Css().replace('div', my_style_dict}),  Css().replace(Div, my_style_dict}) and Css().replace(my_div_instance, my_style_dict}).
Regarding the matching logic, I'd keep it simple for now and delegate to https://github.com/Hrabal/TemPy/issues/40 a more precise selector matching.
For now I'd apply the replace to the elements at the root of the css dict only (making this explicit in docstring), this way I think is more forward-compatible.
This can be a lot of work for the user (it's forced to copy and modify the dict beforehand) but it will be easier to make a backward compatible "css selector finder" class that will traverse the style dict.
To compensate the extra work for the user maybe it's good to add an argument to the replace method: replace(element, new_style, key=None), so when a key is explicitly given the method will work on this value only, so the above examples would become:
So:

an user that want to replace the color attr in "#id_ex div" will call

Css().replace('#id_ex', {
        'color': 'new_color',
        'border': '1px'
    }, key='div')

an user that want to replace the color attr in  "#id_ex"  will call

Css().replace('#id_ex', 'new_color', key='color')

What you think?

And if you were to have this case:
{'html': {
            'body': {
                'color': 'red',
                Div: {
                    'color': 'green',
                    'border': '1px'
                },
               link: {'color': 'yellow'}
            }
        },
        '#myid': {'color': 'blue'}
    }
}

If I would want to change the inner Div color to grey, how would the method call for replace look like following your example of the method signature?

It would be something like this:
Css().replace('html', {
    'color': 'red',
        Div: {
            'color': 'green',
            'border': '1px'
        },
        link: {'color': 'grey'}
    }, key='body'

Which is ugly and counterintuitive. Any better idea?
Maybe the key argument can be a list of keys, i.e. a path?
Css().replace('html', 'grey', key=['body', Div, 'color'])

Honestly, it looks a bit simpler to have a replace method signature like this:
css.replace_element(['html', 'body', Div, 'color'], 'grey')

which puts the whole path inside the first argument as a list. My second choice would be the option you have mentioned with the key argument.

Yes it makes more sense to put the where in a single argument and the what in another..
This can be the same signature for another add (or something like that) method.. replace throwing a KeyError if the path does not corresponds to an existing path,  add will create keys it they are non-existent..

closed by https://github.com/Hrabal/TemPy/pull/52


Proper SDES forwarding

mediasoup is supposed to forward SDES packets, but that's not true. It's just ignoring SDES packets right now.
I've started a sdes branch for this purpose, which some uncompleted changes for routing SDES:
https://github.com/ibc/mediasoup/tree/sdes
However I'm stuck as I don't know how to properly create a clean SDES packet with just the SDES chunks related to each RtpReceiver.
BTW: not sure if this may cause the Chrome issue in #73 (as it seems that Chrome does not set LSR into its Receiver Reports because it does not "correlate" received Sender Reports).

Invalid. We are sending proper SDES.


sbpack not working on Windows

I've tried to run sbpack on windows, but the command failed.
I've tried two things:

Using a remote file

PS C:\Users\pf1cwu1k\Documents\SBG\demo-workflows>  sbpack cavatica mmattioni/ga4gh-drs-wes-test/gwas_workflow https://raw.githubusercontent.com/elixir-cloud-aai/demo-workflows/dev/cwl/gwas_workflow/CWL/gwas_workflow.cwl

sbpack v2020.09.04
Upload CWL apps to any Seven Bridges powered platform
(c) Seven Bridges 2020

Packing https://raw.githubusercontent.com/elixir-cloud-aai/demo-workflows/dev/cwl/gwas_workflow/CWL/gwas_workflow.cwl
Traceback (most recent call last):
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\runpy.py", line 193, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Users\pf1cwu1k\.virtualenvs\demo-workflows-lyBDTqXS\Scripts\sbpack.exe\__main__.py", line 7, in <module>
  File "c:\users\pf1cwu1k\.virtualenvs\demo-workflows-lybdtqxs\lib\site-packages\sbpack\pack.py", line 355, in main
    cwl = pack(cwl_path)
  File "c:\users\pf1cwu1k\.virtualenvs\demo-workflows-lybdtqxs\lib\site-packages\sbpack\pack.py", line 323, in pack
    cwl, base_url, full_url = lib.load_linked_file(
  File "c:\users\pf1cwu1k\.virtualenvs\demo-workflows-lybdtqxs\lib\site-packages\sbpack\lib.py", line 98, in load_linked_file
    contents = urllib.request.urlopen(new_url.geturl()).read().decode("utf-8")
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 222, in urlopen
    return opener.open(url, data, timeout)
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 531, in open
    response = meth(req, response)
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 640, in http_response
    response = self.parent.error(
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 569, in error
    return self._call_chain(*args)
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 502, in _call_chain
    result = func(*args)
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 649, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 400: Bad Request

Then using the file locally (cloned the repo first). This is the error:

PS C:\Users\pf1cwu1k\Documents\SBG\demo-workflows>  sbpack cavatica mmattioni/ga4gh-drs-wes-test/gwas_workflow .\cwl\gwas_workflow\CWL\gwas_workflow.cwl

sbpack v2020.09.04
Upload CWL apps to any Seven Bridges powered platform
(c) Seven Bridges 2020

Packing .\cwl\gwas_workflow\CWL\gwas_workflow.cwl
Traceback (most recent call last):
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 1476, in open_local_file
    stats = os.stat(localfile)
FileNotFoundError: [WinError 3] The system cannot find the path specified: ''

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\runpy.py", line 193, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Users\pf1cwu1k\.virtualenvs\demo-workflows-lyBDTqXS\Scripts\sbpack.exe\__main__.py", line 7, in <module>
  File "c:\users\pf1cwu1k\.virtualenvs\demo-workflows-lybdtqxs\lib\site-packages\sbpack\pack.py", line 355, in main
    cwl = pack(cwl_path)
  File "c:\users\pf1cwu1k\.virtualenvs\demo-workflows-lybdtqxs\lib\site-packages\sbpack\pack.py", line 323, in pack
    cwl, base_url, full_url = lib.load_linked_file(
  File "c:\users\pf1cwu1k\.virtualenvs\demo-workflows-lybdtqxs\lib\site-packages\sbpack\lib.py", line 98, in load_linked_file
    contents = urllib.request.urlopen(new_url.geturl()).read().decode("utf-8")
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 222, in urlopen
    return opener.open(url, data, timeout)
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 525, in open
    response = self._open(req, data)
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 542, in _open
    result = self._call_chain(self.handle_open, protocol, protocol +
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 502, in _call_chain
    result = func(*args)
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 1454, in file_open
    return self.open_local_file(req)
  File "c:\users\pf1cwu1k\appdata\local\programs\python\python38\lib\urllib\request.py", line 1493, in open_local_file
    raise URLError(exp)
urllib.error.URLError: <urlopen error [WinError 3] The system cannot find the path specified: ''>

Maybe these two are related, or maybe not. If they are not, happy to split in two issues
The repo from wehre the CWL is taken: https://github.com/elixir-cloud-aai/demo-workflows/tree/dev/cwl/gwas_workflow

Thank you for reporting this @mattions.
Analysis notes follow.
From adding windows to the test battery (591712a79289a714) we can see that urllib.request.urlopen is not performing properly on windows when pointed to a local file.
Possible solution will be to use a check that determines if the URL is a local file and then routes the call to a regular file open call, using pathlib for cross platform compatibility. We can look at the Benten code since this is solved in a platform independent manner there.


Improve master use sub-command output/information

$ kontena master use my-master
Using master: my-master (https://my-master.kontena.io)
Using grid: aws-coreos

You have access to following grids and can switch between them using 'kontena grid use <name>'

  * aws-ubuntu
  * aws-coreos
  * secret-sauce

Some minor issue with tests, otherwise :+1:


Command Request: Refresh CMakePresets

Brief Issue Summary
In my daily development work, I mostly work with CMake projects in combination with the C/C++ Package Manager conan.
CMakePresets.json are usually not checked in to my source code, but I rather rely on the generated CMakeUserPresets.json.
Sometimes I either open the project in VS Code without running conan first, or I clean all generated files from the project by removing all files under gitignore.
(Re-)generating the presets does not appear to be recognized by the extension.
The only thing that helps in this situation is to use the Developer: Reload Window command.
It would be nice to have a command that just re-attempts parsing the local preset files which were created in the meantime without having to reload the whole window.
CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
open project with no preset files

open project after generating preset files

open project with preset files after manual window reload

Thanks for bringing this up :)
I was also stumbling over that issue as rebasing branches containing CMakePresets also doesn't consistently trigger a preset reload.
Up to now my approach was to close and reopen VS Code – "Reload Window" works much better and faster.
Would highly appreciate if a preset reload could be triggered from somewhere in the plugin.

@andreas-kurz @dornbirndevelops Does opening the presets file and saving it again work? Assuming you have the cmake.configureOnEdit setting enabled, I believe this should work

Does opening the presets file and saving it again work? Assuming you have the cmake.configureOnEdit setting enabled, I believe this should work

Thank you for responding to my issue @andreas-kurz and @gcampbell-msft !
I just tried your suggestion with setting "cmake.configureOnEdit": true and changing CMakeUserPresets.json and CMakeLists.txt, unfortunately without the desired outcome.
It appears that the setting does nothing if no configure preset is selected.

In our project cmake.configureOnEdit is set to true from the beginning. It seems that is only watching for files likeCMakeLists.txt – at least the comment for the settings says this. Also, we are not using CMakeUserPresets – just CMakePresets.json
So CMakePresets are somewhat different and I don't know what makes the cmake extension parse these files despite a Reload Window which is much better than completely closing and re-opening vs code.
Therefore an option to re-parse the settings would be great or some way of auto-re-parsing if the extension detects changes to the CMakePresets (which also supports includes!).

@andreas-kurz The current implementation should be reparsing on every save of the CMakePresets.json, especially in the most recent version of the pre-release (as of 1.19.44).

Thanks for the hint with "pre-release" – didn't noticed that before :)
I'll test it and will provide feedback – maybe next week as in Germany it's almost weekend ;)
How long does it usually take until pre-release feature make it into the actual release?

Thanks, it already made it to the Release :)
Just switched back and edited some presets and includes and every edit triggered the reparsing of the presets with includes <3

Hello @gcampbell-msft !
I also just tried the pre-release version v1.19.46.
I set "cmake.configureOnEdit": true and generated the CMakeUserPresets.json (there was none before).
This did not work out for me unfortunately.
Since the issue is not solved (at least for me), could you maybe reopen this issue or should I create a new one?

@dornbirndevelops Please create a new issue and we will investigate. Any information about how it's not able to parse would be exceedingly helpful. If it's unable to parse the file, there is either something wrong with your presets file, or there is a bug on our end. Thanks!


Fix newlines in response

Proposed changes:
Fixes #5521

Support new lines in responses.md

Status (please check what you already did):

[x] added some tests for the functionality
[ ] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

Related to https://github.com/RasaHQ/rasa/issues/5800
@m-vdb The above issue mentions that adding \n explicitly already works?
Doesn't this fix also need you to add \n explicitly?

@dakshvar22 it's weird I cannot reproduce the behaviour that the user described in #5800 🤔 When someone adds \n in data/responses.md, the newline character is de facto escaped. The only way to have it unescaped, is to press ENTER, but this would break the current format. So at the moment there is no way to support newlines other than writing \n.
Is it possible that the user is describing that it works because the channel he uses automatically unescapes newlines? (neither rasa shell or Rasa X do this)

build blocked by https://github.com/RasaHQ/rasa/pull/5879

@m-vdb Yeah, I just tested on my side too. Atleast Rasa shell wouldn't do it.

👍 thanks for the changelog suggestion, way better

Hi ,
Can you please tell which version of rasa has this fixed available?
I am facing similar problems with the Facebook messenger channel.
Thanks!

@m-vdb @dakshvar22 I see that last release happened on May 15 only, could you please release this fix?

sure @code-jam20 we'll try to push a micro release in the coming days 👍

@code-jam20 this fix is now released as part of 1.10.2


[VS Code] Joining collaboration session: Cannot create property 'hasRecorded' on boolean 'true'

Error:Joining collaboration session: Cannot create property 'hasRecorded' on boolean 'true'
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS

extensionVersion
1.0.419

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.26.1

platformName
MacOS

platformVersion
18.6.0

Thanks for the issue report. Can you provide more details? What were you doing when you encountered this error?
Your logs may provide us with helpful information. You can find your logs in the %TEMP%/VSFeedbackVSRTCLogs directory. You can attach them to this issue or send in email to<EMAIL_ADDRESS>

Closing due to lack of activity.
I think this issue may have been fixed in a newer version of Live Share anyway.


add client endpoint for python

Current dependencies on/for this PR:

main

PR #48

PR #49   👈

This comment was auto-generated by Graphite.


Fixed compatibility with 1.13+ clients

Looks good, we will make necessary adjustments when BLC 1.13 is released to make compatibility work.


direct messages

Does not synchronize direct messages.

Please start from reading https://github.com/andstatus/andstatus/issues/295
If that won't help, please provide detailed information on a problem here, including error message from Commands in a Queue...