Error Handling for Graph Types

Based on issue #46 i t seems like the error traceback could be better improved by changing from what was said in the traceback for using the incorrect graph types here:
ERROR:   error: all type parameters to the acset type must be fully instantiated.

  Right: Semagram{WeightedGraph{Int}}(WeightedGraphSema)
  Wrong: Semagram{WeightedGraph}(WeightedGraphSema)

To something like this:
ERROR:   all type parameters to the acset type must be fully instantiated.

Ensure that you are `using Catlab.Graphs`.

As in the traceback, this gets around the specifics of the graph type and makes it much more broader. In theory, I could imagine it linking back to documentation in some way. I really like the idea of this error handling and I think you should keep going with it! Great work!

Is this error message just saying that you need to do using Catlab.Graphs? I guess this is another pain point related to #44.

Hi James,
That's not in the error message now. That was my suggestion for fixing the error "WeightedGraph not found"

Yeah, I think we should fix the fact that using Semagrams without also using Catlab and Catlab.CategoricalAlgebra and Catlab.Graphs causes a bunch of weird errors as the upstream problem to this inaccurate error message.

This is not relevant for next, closed.


Update stable version in repo from 1.4.9 to 1.5.0

Think about update stable version to 1.5.0
Version: stable=1.4.9 (63 days old) => latest=1.5.0 (21 days old)
Installs: stable=254 (34.99%), latest=38 (5.23%), total=726
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 1.5.0 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.5.0 but the current stable version is already 1.5.0.
So this issue should be closed.
@mcm1957 for evidence


com.hbs.hub.ReadSenseHAT=1.0.0 Packages with conflicting dependencies

Good afternoon,
I am Álvaro Puente, a student at the University of Valladolid and I am using your book as a support for my final degree project. The thing is that, when it comes to deploy, both com.hbs.hub.ReadSenseHAT and com.hbs.hub.WriteSenseHAT, fail to deploy and go to BROKEN state.
I've been looking into the logs and I think the problem can be found in the recipe, specifically in the "install" section. This is due to version conflicts of the packages to be installed (in the file requitements.txt). I don't know if fixing that would make everything work correctly or if there would be something else or, on the contrary, it could be my fault.
I would be grateful to receive feedback on this issue. I'm attaching a couple of interesting screenshots I've seen in com.hbs.hub.ReadSenseHAT.log
PS: I am completing the book with a Raspberry Pi 3B and the SenseHAT device.

Acknowledging receipt of the issue. We will troubleshoot on our end this week.

Hi Álvaro, there is an issue with the pip dependency tree that is resolved by updating the versions of awsiotsdk and awscrt in requirements.txt. Fix is below and I will commit a change to the code this week.
However, there was one more blocking issue after resolving that. I'm still tracking down the root cause of the second issue where RTIMULib fails to build in the virtual Python environment. Something related to newer RPi OS, newer Python3 version 3.9 (we wrote the labs originally with 3.7), and the virtual Python environment created by venv. For now, you can get the components working by removing the use of venv. While this isn't a best practice for production, it is fine on a test RPi device. I will continue troubleshooting to see if I can get venv working with latest RPi OS and Python 3.9.
You can make the following changes to unblock deployment of the components that interact with SenseHAT.
chapter3/artifacts/com.hbs.hub.ReadSenseHAT/1.0.0/requirements.txt (drop the lines that no longer appear below, update awscrt and awsiotsdk versions)
awscrt==0.13.11
awsiotsdk==1.11.1
numpy==1.21.0
Pillow==8.2.0

recipes/com.hbs.hub.ReadSenseHAT-1.0.0.json Lifecycle Install script becomes
"Script": "usermod -a -G i2c,input ggc_user && apt update && apt upgra
de -y && apt install python3 libatlas-base-dev -y && python -m pip install -r {a
rtifacts:path}/requirements.txt"

recipes/com.hbs.hub.ReadSenseHAT-1.0.0.json Run script becomes
"Script": "python {artifacts:path}/read_senseHAT.py"

You will need to make similar changes to the WriteSenseHAT-1.0.0.json file and the artifact requirements.txt.

Hello again Ryan,
Thanks for the update. I have applied the changes but still the components go to BROKEN state. Again, I am attaching from com.hbs.hub.ReadSenseHAT.log the problem that arises.

This is one of the reasons using venv is preferred :)
It looks like your device has Pillow and numpy installed in the global Python packages that are earlier versions and thus incompatible with the stated requirements.txt. Python reports it won't uninstall the previous version because the Greengrass directory where the component is running is outside of /usr.
In any case, I'm reviewing the code for those components and I don't see any consumption of either Pillow or numpy in them. I won't have an opportunity to test this for another day, but you could try further slimming the requirements.txt files down to:
awscrt==0.13.11
awsiotsdk==1.11.1

and see if that results in a successful component deployment.

It works! Thank you very much @TheRyanBurke

Hey @AlvaroPuente, @TheRyanBurke,
Let me know if this issue can now be closed and if there is any information regarding this, that should be mentioned in the readme if it could be beneficial for other readers too.

Thanks, Rajat. I will file a PR to correct the issue for future readers and at that time we can close the issue.


Split MICommandFactory.cs

commit 575f78dc174c95b695b2faca52dd741a2fa9d6d3
Author: Gregg Miskelly<EMAIL_ADDRESS>Date:   Mon Mar 21 18:25:35 2016 -0700
Split MICommandFactory.cs

MICommandFactory.cs was one large file which was getting difficult to edit. Ths splits it out to multiple files.

commit 326c9840eadc46d2e45406ea07c2bb1edfc26504
Author: Gregg Miskelly<EMAIL_ADDRESS>Date:   Mon Mar 21 18:24:30 2016 -0700
Fix baseline of LaunchOptions.xsd.types.desginer.cs

Xsd is generating a different LaunchOptions.xsd.types.desginer.cs on my machine than what is checked in. This updates the baseline to match what is generated.

LGTM

:+1:


Issue #13 The initial position set for burst

#13

Thank you! I'm a bit confused: the initial position works great for me with the current code, on both macOS and iOS. Is there somewhere specific that shows the problem you're trying to fix?

To set an initial position for the burst effect in your ConfettiView, possibly due to issues with accessing the proxy. To solve this, I suggest moving the .onAppear modifier to the outer VortexViewReader, ensuring that the initial position is calculated correctly based on the proxy size. By making this adjustment, I can ensure that the burst effect occurs at the desired location when the view is first displayed to the user.

Sorry, perhaps I'm not being terribly clear. You're modifying the sandbox app. Right now the sandbox app seems to work with confetti just fine, no matter where the user first taps. Unless there is a very different bug at play, there is no confetti when the user first sees the view – it's created when they tap, at which point the position is correct.


Explore other options instead of using singleton in API Service

Reason for using singleton:
The API Service is a singleton that stores the last time it pulls from Social Media in an instance variable. We used a singleton because:
1. We wanted a single instance of the service to interact with external api so that we don't hit any api rate limits.
2. We wanted to avoid storing this information in the db if possible because it would often be updated and we thought it would be cheaper as far as performance to have it simply live in memory
Questions:

First of all, do any of the reasons above not make sense?
When is it appropriate/not appropriate to use a singleton in a Rails App?
What are some alternatives we could use?

Thanks!
@pturley, do you have any advice?

Well, there are a few things that we could do instead of the singleton object to basically share state between requests without hitting the database.  The honest truth is that none of them are without problems:

Caching the calls in class variables inside a service class.  This one's big problem is that those class variables wont be shared across processes or threads.  Sometimes it makes for an inconsistent experience for users.
Storing the result of the calls in something like memcache (or the database for that matter).  This seems like a bit of a tough given the fact that we move to being a gem.  Tough to request that people put in a cache solution to use our gem.
Store the entire html in the database and just use the database to be our caching solution completely and that itself prevents us from making the service calls.
Same story but with the filesystem, but if we roll this thing out to multiple servers, that wouldnt be a good idea.


Maven Shade: exclude MANIFEST and produce shaded SOURCE jar

exclude MANIFEST from shaded jars to make sure we keep only the one from the project in the final result
explicitly configure the plugin to  the Disruptor and  all the other dependencies (if not, new project dependencies will be shaded as well if the plugin configuration is not updated)
produce shaded source as well (handy when debugging applications making use of the library)

Related issue: #553

The plugin still issue some warnings after this change:
[INFO] Minimizing jar net.logstash.logback:logstash-logback-encoder:jar:7.0-SNAPSHOT
[WARNING] /Users/brenuart/Documents/projects/git/logstash-logback-encoder/target/classes (Is a directory)
[WARNING] /Users/brenuart/Documents/projects/git/logstash-logback-encoder/target/classes (Is a directory)

This is caused by the minimizeJar option. It seems to be a known issue (see https://github.com/apache/maven-shade-plugin/pull/83) and should be fixed in future releases (issue title is different but seems to share the same root cause).


Typo fix in raylib_structs.c

Found a typo in the cheatsheet and wanted to fix it. My only question is how do I regenerate the .pdf? The tool in cheatsheet/tool/generate_cheatsheet_code.py only regenerates the .c files, not the pdf :(

@ybtre Thanks for the review and excuse the late response.


Drag area covers the output mime type switcher

Steps to Reproduce:

Open GitHub Issue Notebook
Run a query
Click the </> button to switch mime type, doesn't work

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

Expand input/output doesn't work as well from the UI

Verified in OSS.


ansible-navigator inventory -i ../hosts crashes

ProductName:	macOS
ProductVersion:	11.2.1
BuildVersion:	20D74
Python 3.9.2
ansible-navigator 0.6.0
../hosts contains:
[kindle]
<IP_ADDRESS>
[kindle:vars]
banter="Ok kindle. Let's automate!"
voice="Daniel"
[all:children]
kindle
pressing 1 to see the hosts crashes:
Traceback (most recent call last):
File "/Users/pgriffit/ansible-navigator_demo/venv/bin/ansible-navigator", line 8, in
sys.exit(main())
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/cli.py", line 327, in main
run(args)
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/cli.py", line 293, in run
wrapper(ActionRunner(args=args).run)
File<EMAIL_ADDRESS>line 94, in wrapper
return func(stdscr, *args, **kwds)
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/action_runner.py", line 51, in run
self._run_app(interaction)
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/action_runner.py", line 60, in _run_app
interaction = run_action(
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/actions/_actions.py", line 68, in call
return action_cls(app.args).run(app=app, interaction=interaction)
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/actions/inventory.py", line 196, in run
self._take_step()
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/actions/inventory.py", line 244, in _take_step
result = self._interaction.ui.show(
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/ui_framework/ui.py", line 855, in show
result = self._show_menu(obj, columns, await_input)
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/ui_framework/ui.py", line 790, in _show_menu
menu_heading, menu_lines = self._get_heading_menu_items(current, columns, showing_idxs)
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/ui_framework/ui.py", line 750, in _get_heading_menu_items
menu_heading, menu_items = menu_builder.build(
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/ui_framework/menu_builder.py", line 39, in build
return self._menu(dicts, cols, indicies)
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/ui_framework/menu_builder.py", line 56, in _menu
convert_percentage(dicts[idx], cols, self._pbar_width)
File "/Users/pgriffit/ansible-navigator_demo/venv/lib/python3.9/site-packages/ansible_navigator/ui_framework/utils.py", line 23, in convert_percentage
value = dyct[key]
KeyError: 'ansible_network_os'
Also crashes when selecting groups and selecting the first one.

I suspect this issue was fixed earlier when inventory columns were set by a settings file and hosts didn't have these attributes.
ansible-navigator will now show "None" for these columns


Apply Coronavirus question page to all opss flows

Trello ticket
Description
Apply coronavirus question page to all OPSS flows:

Allegation
Enquiry
Project

This work is heavily based on previous work done by @slorek adding the question for trading standards
Few Minitest system tests have been migrating to their corresponding Rspec feature tests.

Checklist:

[x] Have you documented your changes in the pull request description?
[ ] Does the change present any security considerations?
[ ] Is any gem functionality overloaded? Eg: Devise controller methods being overloaded.
[ ] Has acceptance criteria been tested by a peer?
[x] Has the CHANGELOG been updated? (If change is worth telling users about.)

 (2) Apply coronavirus question page to all OPSS flows

Three minor issues:
OPSS flows have back links at the top:

The line of text  Report an unsafe or non-compliant product is only for TS flows.

Perhaps we can see how other pages that are shared between the flows include this line.
The URL path for projects seems to have changed from domain/project/foo to domain/investigation/project/foo -  is this intentional?

Retested this in review app 475, looking good as expected.
also activity log records CV flag if the case is related.
Verified project/enquiry/allegation as opss user, also regression tested TS flow, all good.


Support node scripts in BROWSER

Modify OpenBrowser.js to run node scripts specified with the BROWSER environment
variable as discussed in #1533 . If the value of the BROWSER environment variable ends with '.js' a
child process is spawned to execute the script with node.js. The command
executed in the child process is 'node PATH_SCRIPT'.
Some observations I'd like to discuss:

Since BROWSER now does more than just opening your browser, maybe we should
consider renaming a few things.
The string argument of the script to run with node is not sanitized in any
way. Nothing is checked, the string is passed to the child process as is. I
don't know what is the worst thing that could happen. Scripts ending in '.JS'
are not executed.
The openBrowser() function returns a boolean. I decided to stick with this behavior,
but I noticed that the result is not used in react-scripts/scripts/start.js.

How to test this:
create any 'script.js' file. You can use this one that writes a file to the
current working directory:
const fs = require('fs')

fs.writeFileSync('message.txt', 'script says hello!');

Now in the same directory execute:
BROWSER=script.js npm start

The file should be created in that directory and no browser should be opened.
And of course, the other use cases of BROWSER still work
BROWSER=none npm start
BROWSER=firefox npm start

Any feedback is appreciated.

Feature is useful but behaviour is unexpected (at least for me)
BROWSER=script.js npm start  - I don't expect that it is possible to pass js script into BROWSER variable. BROWSER means browser for me (chrome / firefox / none etc).

Yeah, I was thinking that maybe the variable should be renamed, it's not very intuitive.
Now if somebody could please help me figure out why the travis build fails..

I think BROWSER is fine to be honest. It's an advanced feature anyway.

Actually I'm starting to think that just like with the browser, the url should be passed as a parameter to the script. One of the use cases for this is #1450. It's kinda unreliable to add query strings if you don't know the url. Sure it's localhost, but what about the port? it could have been specified by PORT, or maybe default port was busy so the next available port was chosen. The browser doesn't have to figure this out because it receives the url as a parameter.
If the script is invoked with node script.js localhost:3000 Then it is pretty similar to opening the browser, so the name is fine.
This might make things a bit weirder but I also think that it might be useful to let the script read all the arguments passed to npm start. That would make it possible to start the dev server with any desired query string by doing something like:
npm start foo=1&bar=3

It certainly looks cool, although hardcoding into the script might be good enough since you probably only do npm start once and then manipulate the query string as many times as you want from the browser.
I'd like to know what you guys think, specially the ones that actually want to use this feature.
btw, I changed spawn to cross-spawn as suggested.

If the script is invoked with node script.js localhost:3000 Then it is pretty similar to opening the browser, so the name is fine.

I fully agree.

This might make things a bit weirder but I also think that it might be useful to let the script read all the arguments passed to npm start.

Yes, I think it should work by passing a URL as the first argument, and then passing any additional arguments verbatim.

Since browsers are launched with the url as last argument, I decided to follow that convention. the BROWSER script now receives any arguments passed to npm start and the url as last argument. If you do something like:
BROWSER=myscript.js npm start -- --query=?foo=bar&baz=qux

openBrowser() will start a child process like this:
node myscript.js --query=?foo=bar&baz=qux http://localhost:3000/

Sounds good. Why did CI fail?

react-dev-utils did not have cross-spawn listed as a dependency.

I'd appreciate if you could rebase this on master and fix the naming.
Thanks!

Done

Looks great. I tweaked code style a bit. Thanks!

Please help beta test the new version that includes this change!
https://github.com/facebookincubator/create-react-app/issues/2172

👍 way to go!!

Thanks.


Hypervisor Manager support for API 800,1000,1200

Hypervisor Manager support for API 800,1000,1200

Did you test importing an existing resource from Oneview?

Yes, the import testcases got passed


Doesn't work with groovy 2.3.7

It's impossible to use Glisten with Groovy 2.3.7 and SWF because of cast exceptions

Updating the dependencies still doesn't resolve the problem.

#38
There must have been a parsing change between groovy 2.1.x and 2.3.x, adding a parenthesis around a statement fixed it in newer versions of groovy.


Undefined fix

@shurcooL @neelance
Hope this helps.

Thanks @iansmith, but it looks like this has already been fixed 21 hours ago, see #3.


Dremio datalake engine support

I'm finding a way for the OMD project to rule over every tool's metadata and sort of monitors an extra-compact DataPlatform, this DP uses Dremio as its query execution engine for scalability with bigger datasets and ease of use (it connects well to a lot of data sources). However, OMD hasn't the connector to Dremio for metadata extract and monitoring.
Solution: A Dremio connector to OMD, which can be easily configured through minimal variables like host:port and usrn:pasw, ssl is a nice addon feature but is not essential for now.
Alternative: An external data cataloguing service like HiveDC, DynamoDB, Nessie (Dremio recommended),... Both OMD and Dremio uses this as Metadata monitor and tracking tool. However this exclude Dremio from OMD and bloats the infra a bit (another data solution to take care of).
I'm new to this Cloud Data Engineering thing, a bit suprised about how limited Dremio is, though the engine is still quite powerful.

@capoolebugchat are you interested in picking up this issue?

@TeddyCr I would love to help.

@TeddyCr yes, sorry about the extra late reply

Thanks @capoolebugchat I'll assign it to you then. We have some information about how to build a new connector here. Make sure to join our slack channel and the #contributor channel for any help.
@rogercezidio please check other connectors here for contributing we have many. 😊

Hi folks,
we did a simple implementation for a Dremio custom connector here: https://github.com/TIKI-Institut/openmetadata-dremio-connector.
It can only scrap Metadata. It has no support for Query Usage, Profiling etc. We didn't find a possibility to implement that for a custom connector. For lineage we are simple using DBT at the moment.
We would appreciate any feedback.
Is it possible that this will be integrated into OpenMetadata?

Hey @wobu we would recommend you to directly contribute the connector to the community. This will allow you to leverage the existing code base to implement support for Usage, Profiling, etc.
Here is a link with more information -> https://docs.open-metadata.org/latest/developers/contribute/developing-a-new-connector

We thought about it, and also tried it, but unfortunatley setting up the openmetadata project under windows OS wasn't easy :/ (WSL would maybe an option). So we decided to just start with a custom connector.
The CustomConnector is currently sufficient for us, so we won't provide a direct community integration in the near future until our investment in Openmetadata and Dremio increases.


Remove overrides of Throwable.fillInStackTrace

Motivation:
Since Java 7, there are new constructors available that allow us to avoid initialising the stack traces of certain exceptions.
Modification:
Use these constructors instead of overriding Throwable.fillInStackTrace.
Result:
Cleaner code

I guess the previous test failures were just flakiness.


docs: Mark pod-short option in Hubble metrics as deprecated

As one of source/destination context options in Hubble metrics, pod-short tries to provide a workload name. However, this option is correct only in some cases. It naively cuts two last bits starting with '-' from the pod name. For Deployments this will indeed result in the Deployment name. But e.g. for StatefulSets or DaemonSets, it will cut too much, unless the workload name doesn't contain hyphens. For standalone pods it's completely meaningless.
For example:

Deployment hubble-relay, pod hubble-relay-7c7bf78559-6b46b, pod-short huble-relay - ok
DaemonSet cilium, pod cilium-2kp2v, pod-short cilium - ok
DaemonSet cilium-node-init, pod cilium-node-init-c6gmz, pod-short cilium-node - not ok
standalone pod my-amazing-pod, pod-short my - not ok

There is also workload-name option, which provides the correct workload name from the pod metadata. It should be preferred over pod-short. Additionally, users might want to add pod option as a fallback, to handle bare pods correctly.
This PR only marks the pod-short option as deprecated in docs. Can it be backported to 1.13? Then this option can be removed in the next release.

Any plan to deprecate pod-short in a future version?

@qmonnet You mean to delete? I would consider it deprecated already (ideally this PR would get backported to 1.13) and the plan is to delete it soon.

Sorry I had missed the last sentence of your PR description. OK thanks, I added the label for the 1.13 backport.
In that case it might be worth adding a comment next to pod-short in the source to remember to remove it, see e.g. in pkg/ipam/metrics/metrics.go: // Deprecated, will be removed in version 1.14.

Also I note that pod-short is still used in some test files under pkg/hubble/metric/, would it make sense to update to workload-name|pod in there as well?

@qmonnet Updated with your suggestion.
Regarding tests - I think they should be updated when the option is removed, but I wanted to keep the backport tiny to avoid any conflicts.

I wanted to keep the backport tiny to avoid any conflicts.

v1.13 hasn't shipped yet, it's unlikely we'd hit many conflicts on these test files.

Plus in most of the tests it doesn't really matter which option is used.

Isn't that one more reason to update them? :) But OK

[It's just a question]
I think pod-short contains its namespace as a prefix (like some-namespace/some-deployment), but workload-name doesn't contain the prefix. So, workload-name | pod can not completely replace pod-short.
I think it's ok to mark pod-short as deprecated, but should we add the namespace prefix for workload-name or should we add an option to add namespace as a prefix for whole contexts?

should we add the namespace prefix for workload-name

I would rather go the other way - add another option (e.g. pod-name) for pod without namespace, and recommend using it over pod. Namespace information can be added as separate labels via labelsContext.

or should we add an option to add namespace as a prefix for whole contexts?

Personally I don't really see a reason for doing it. Namespaces can be added as separate labels, and I'd prefer doing that rather than including namespace in source/destination labels. If someone really needs labels in namespace/workload format, then it can be achieved with relabeling rules.
More discussion on that here: https://github.com/cilium/cilium/issues/23122
The workload-name|pod option I suggested might be indeed confusing because of this issue. Although I think it's still better than using pod-short - this one is simply incorrect.

docs only, full test suite not necessary.


Do not render on every frame if text did not change

Everything up to layout is now cached. It's not clear we actually want to cache the final rendering so I'm going to close than and we can come back to it if necessary.


microsoft.exchange.webservices.data.core.exception.service.remote.ServiceRequestException: The request failed. An internal server error occurred. The operation failed.

I get this error using EWS java api :
microsoft.exchange.webservices.data.core.exception.service.remote.ServiceRequestException: The request failed. An internal server error occurred. The operation failed.
at microsoft.exchange.webservices.data.core.request.SimpleServiceRequestBase.internalExecute(SimpleServiceRequestBase.java:74)
at microsoft.exchange.webservices.data.core.request.MultiResponseServiceRequest.execute(MultiResponseServiceRequest.java:158)
at microsoft.exchange.webservices.data.core.ExchangeService.internalFindFolders(ExchangeService.java:377)
at microsoft.exchange.webservices.data.core.ExchangeService.findFolders(ExchangeService.java:425)
at microsoft.exchange.webservices.data.core.ExchangeService.findFolders(ExchangeService.java:461)
at com.neustar.EWSOffice365Reader.main(EWSOffice365Reader.java:189)
Caused by: microsoft.exchange.webservices.data.core.exception.service.remote.ServiceResponseException: An internal server error occurred. The operation failed.
at microsoft.exchange.webservices.data.core.request.ServiceRequestBase.processWebException(ServiceRequestBase.java:548)
at microsoft.exchange.webservices.data.core.request.ServiceRequestBase.validateAndEmitRequest(ServiceRequestBase.java:641)
at microsoft.exchange.webservices.data.core.request.SimpleServiceRequestBase.internalExecute(SimpleServiceRequestBase.java:62)
... 5 more
The error is shown at below mentioned line.
FindFoldersResults findResults = service.findFolders(WellKnownFolderName.Inbox, folderview);
The service code is as below :
ExchangeService service = new ExchangeService(ExchangeVersion.Exchange2010_SP2);
service.setUrl(new URI("https://outlook.office365.com/EWS/Exchange.asmx"));
BearerAccessToken bat = new BearerAccessToken(future.get().accessToken());
TokenCredentials credentials = new TokenCredentials(bat.getValue());
service.setImpersonatedUserId(new ImpersonatedUserId(ConnectingIdType.SmtpAddress , MAILBOX));
service.getHttpHeaders().put("X-AnchorMailbox", MAILBOX);
service.setCredentials(credentials);
service.setTraceEnabled(true);
I get the access token properly but the moment it comes across FindFoldersResults findResults  it throws above mentioned exception.

@skenkre We encountered the same problem. Does all your calls to EWS throws the same exception?

Just wanted to bump this. I provided a PR to fix this.


Undistorting all frames available

I would like to undistort all frames (without skipping any) using the steps in
https://github.com/karfly/learnable-triangulation-pytorch/blob/master/mvn/datasets/human36m_preprocessing/README.md
I have processed the data in H36M so that I have all distorted frames available, but running undistort-h36m.py I am getting skipped frames - 1,8,11,13 ..etc (image attached).
Could you please point out where in the code I would have to adjust to create undistorted frames for all available?
I would like to eval all sequential frames in the eval set instead of skipping any.

Resolved:
The steps 4-6 here need to be re run on the dataset where all frames are processed

@jamalknight can you please share the processed dataset if possible


Cur 289

Pull request for sharing projects in Google Classroom.
The following line needs to go in .env file
GAPI_CLASSROOM_CREDENTIALS={"web":{"client_id":"898143939834-9ioui2i9ghgrmcgmgtg0h6rsf83d0t0c.apps.googleusercontent.com","project_id":"currikiclassroom-1595285707608","auth_uri":"https://accounts.google.com/o/oauth2/auth","token_uri":"https://oauth2.googleapis.com/token","auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs","client_secret":"mCIpvHBXrCj7wfjtvTHhy09g","javascript_origins":["http://localhost:3000"]}}
The javascript_origin will need to be updated according to the studio instance, and also added to the client app in Google console.

Just adding a note for my PR.
There are two migrations, that need to run:

2020_08_24_130222_alter_users_table -> changes gapi_access_token column to JSON. (It first drops the column, then recreates it).
2020_08_27_105045_alter_project_table  -> creates 'shared' column for 'projects' table

And two environment variables then need to be set:

GAPI_CLASSROOM_CREDENTIALS={"web":{"client_id":"898143939834-9ioui2i9ghgrmcgmgtg0h6rsf83d0t0c.apps.googleusercontent.com","project_id":"currikiclassroom-1595285707608","auth_uri":"https://accounts.google.com/o/oauth2/auth","token_uri":"https://oauth2.googleapis.com/token","auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs","client_secret":"mCIpvHBXrCj7wfjtvTHhy09g","javascript_origins":["http://localhost:3000"]}}

CURRIKI_TSUGI_HOST=https://tsugi.curriki.org/mod/curriki/


GitHub Settings nowadays have an extra level of "developer settings"

Affected: Documentation

The current GitHub Settings are slightly more complicated than the current documentation reflects:
Settings page

Developer settings page
Settings / Developer settings / Personal access tokens

The hyperlinks used in the code-settings-sync-readme still work, though!

https://github.com/shanalikhan/code-settings-sync/pull/416
Fixed


pull request for e2e test at 12/13/2016 03:56:03

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


Installation Issues

Pandas UI Display Issue
Installation commands mentioned in the readme file (1) jupyter nbextension enable — py qgrid — sys-prefix 2)jupyter nbextension enable — py widgetsnbextension — sys-prefix) are not working which inturn pandas ui is not displaying in the jupyter notebook.
Workaround:
jupyter nbextension install --user --py widgetsnbextension
jupyter nbextension enable --user --py widgetsnbextension

Thanks for the workaround will include in the documenatation.


New release for eo-0.35.9

New release for eo-0.35.9

PR-Codex overview
This PR updates the version to 0.35.9 across multiple test files and objects, and also includes changes related to package URLs and runtime versions.
Detailed summary

Updated version to 0.35.9 in test files and objects
Updated package URLs and runtime versions for various objects

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@maxonfjvipon maybe it's better to update parser version inside pom.xml AND at the same time update versions of objects?


Possible to view speed as colors?

I would love to be able to visualize the speed of my tracks. For example coloring the track line based on speed, etc? Is this possible already, or could be added?

Thank you for your suggestion, I have re-implemented the website from scratch and now added more information to the tooltip shown when you hover over the elevation profile.
You can check it out here: https://gpx.studio/gpx.studio/ and provide feedback on this new repository: https://github.com/gpxstudio/gpx.studio.


Stack tag pinning

Adds a new subcommand branch for pinning tags for a docker compose stack in the .env file.
Example Usage:
vpdb stack use qa

This example would go to tagger, get the qa image versions, then update your .env file to pin your current docker-compose stack images to those versions.

could we not just use the qa/beta/prod tags of these services instead of the explicit numbers defined in tagger?

That would lead us back to the very problem that lit a fire under this change in the first place, which is stale images in your local cache.  If we just say 'qa', docker is going to check locally, see that you already have an image tagged as 'qa' in your cache, and use that image regardless of whether there is a newer image available on dockerhub with that tag.

That would lead us back to the very problem that lit a fire under this change in the first place, which is stale images in your local cache.

Got it.  Makes sense.  Also maybe systems is doing a similar thing then to avoid this problem on the servers.


md-label for pagination uses white font

Im using the pagination for my site, but the label displays the md-label in white font. if i select the text i can see it.
This is my pagination in as Jade.
md-table-pagination(md-label="{page: 'Page:', rowsPerPage: 'Rows per page:', of: 'of'}",md-limit='$ctrl.query.limit', md-limit-options='$ctrl.limitOptions', md-page='$ctrl.query.page', md-total='{{$ctrl.ingredients.length}}',  md-page-select='true', md-boundary-links='false')

I also am facing the same issue. The pagination labels fail to show up inside a ui-view. Otherwise, they are displayed just fine.
This is the plunk - https://embed.plnkr.co/Nak4XVp4PkJW1EFZUug4/
Both 'username' and 'password' for login are "test".
Is this a bug or am I missing something?

@poojanbabu In your case there is a stylesheet called labels.less that is overriding the color of the label. If you don't have control over the stylesheet you can manually correct the color.
.md-table-pagination .label {
  color: rgba(0, 0, 0, 87%) !important;
}

Thank you, this solved the issue


Confusing statements in the 2.15 announcement blog post

Where to find the issue
DE: https://www.coronawarn.app/de/blog/2021-12-20-cwa-2-15/
EN: https://www.coronawarn.app/en/blog/2021-12-20-cwa-2-15/
Describe the issue
The blog post says:
"After the user has selected a certificate and once again given their consent, the certificate is checked. For this purpose, it is temporarily transmitted in encrypted form to the validation service. The validation service then compares the organizer's rules with the certificate and then informs the booking system whether the certificate complies with the rules or not."
And then, in the next paragraph it says:
"Please notice: the certificates remain on the user's own smartphone and are not stored in the validation system at any time."
This is very confusing and seems to be a contradiction. Yes, one time the text is about "the validation service" and one time about "the validation system". Normal users don't understand the difference. Not even I do. 😅
Suggested change
Make it clearer whether the certificate (and what data of the certificate) is send to the server in the process.
Ping @HannaHei

@Ein-Tim
Thank you for raising this important topic!

https://github.com/corona-warn-app/cwa-website/pull/2232 changed this text.

https://www.coronawarn.app/en/blog/2021-12-20-cwa-2-15/
"The certificates are not transmitted to the booking system and are not stored in the validation service."
https://www.coronawarn.app/de/blog/2021-12-20-cwa-2-15/
"Die Zertifikate werden nicht an das Buchungssystem übertragen und nicht im Validierungsservice gespeichert."
Perhaps you could check if you think this is now solved?

@MikeMcC399
Thanks for the reminder. Yes, it's clearer now, for the remanning issues I'll open a new issue.

@MikeMcC399 @Ein-Tim Thanks for following up!


luci-app-wireguard: import account like glinet

when does openwrt have a wireguard luci that can import accounts like glinet

So far, there are no plans to do so. Besides, you need to give us more information about what it is. Best with pictures and a link where we can look at it, what this exactly is

So far, there are no plans to do so. Besides, you need to give us more information about what it is. Best with pictures and a link where we can look at it, what this exactly is

So far, there are no plans to do so. Besides, you need to give us more information about what it is. Best with pictures and a link where we can look at it, what this exactly is

https://docs.gl-inet.com/en/3/app/wireguard/

So far, there are no plans to do so. Besides, you need to give us more information about what it is. Best with pictures and a link where we can look at it, what this exactly is

https://docs.gl-inet.com/en/3/app/wireguard/

I use glinet and use glinet firmware I really like the wireguard account import feature I hope the openwrt devoloper can make it like that

I use glinet and use glinet firmware I really like the wireguard account import feature I hope the openwrt devoloper can make it like that

So far, there are no plans to do so. Besides, you need to give us more information about what it is. Best with pictures and a link where we can look at it, what this exactly is

hy. I tried the package file which must overwrite the existing config file. When I installed the file I found an error check_data_file_clashes how can I overwrite an existing config file

Current master provides import and export facilities for WireGuard configs.


Fix usb mass storage device issues

disk: disk_access: changed mutex for a spinlock
disk_access functions were called from an interupt context, thus
crashing on mutexes (no sleep is allowed in interrupt context).
The usage of a spinlock is permitted. The functions guarded by
the spinlock are executed very quickly anyway, so the spinlock
is applicable.
Stack trace from VSCode when the crash occured:

Log output from Zephyr:
ASSERTION FAIL [!arch_is_in_isr()] @ WEST_TOPDIR/zephyr-deps/zephyr/kernel/mutex.c:111
        mutexes cannot be used inside ISRs
[00:00:18.066,000] <err> os: r0/a1:  0x00000004  r1/a2:  0x0000006f  r2/a3:  0x00000001
[00:00:18.066,000] <err> os: r3/a4:  0x00000004 r12/ip:  0x0002c1b9 r14/lr:  0x08011ead
[00:00:18.066,000] <err> os:  xpsr:  0x01000059
[00:00:18.066,000] <err> os: Faulting instruction address (r15/pc): 0x0802a468
[00:00:18.066,000] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
[00:00:18.066,000] <err> os: Fault during interrupt handling

[00:00:18.066,000] <err> os: Current thread: 0x20001b18 (idle)
[00:00:18.128,000] <err> os: Halting system

usb: fix wrong capacity report for USB mass storage device
Usb "write" method never copies the input data buffer, it uses the
buffer pointer directly. The fact that it was on the stack made
the buffer ephemeral, and could disappear before the USB transfer
actually occurred. The data transmitted was then random. This commit
converts the transfer buffer to a static buffer, so that it always
exists for the duration of the USB transfer.
Known side-effect: if "read capacity" command is read twice
simultaneously, the same buffer will be used twice. As the capacity of a
USB drive should not change between 2 calls, this side effect can be
ignored.
Signed-off-by: Alexi Demers<EMAIL_ADDRESS>Fixes #77175 and #77176

So to be clear, the issue is that mass_storage_bulk_out is being called from an ISR context? @jfischer-no, should the USB device drivers be calling this from an ISR context? Looking at the Kinetis USB driver, it seems that call is made from a thread context (an ISR notifies the thread)

So to be clear, the issue is that mass_storage_bulk_out is being called from an ISR context? @jfischer-no, should the USB device drivers be calling this from an ISR context? Looking at the Kinetis USB driver, it seems that call is made from a thread context (an ISR notifies the thread)

Yes, this is a known issue in legacy USB device support, most drivers are fixed not to call callbacks from ISR context. Btw, STM32 shim driver has another mutex issue, https://github.com/zephyrproject-rtos/zephyr/issues/61464.

@ademers-axceta How come this PR is targeting v3.6-branch?

@ademers-axceta How come this PR is targeting v3.6-branch?

The bug was encountered on version 3.6. I am suggesting to integrate in in 3.6, as it is still supported as far as I know? I can port it to 3.7 and main branches afterward if it applies?
If you prefer having it on 3.7 or main only, I will adjust.

@ademers-axceta How come this PR is targeting v3.6-branch?

The bug was encountered on version 3.6. I am suggesting to integrate it in 3.6, as it is still supported as far as I know? I can port it to 3.7 and main branches afterward if it applies?
If you prefer having it on 3.7 or main only, I will adjust.

The process for this would be to get the fix into main first and then backport it to the relevant, active releases.
Please change the target branch to main and I'll make the necessary label additions for automated backports to v3.7-branch and v3.6-branch (these require separate reviews and approvals).

k_spinlock_key_t spinlock_key = k_spin_lock(&lock)

Ah ok! I was not aware of that backporting method. I will adjust the target branch, thanks

@ademers-axceta How come this PR is targeting v3.6-branch?

The bug was encountered on version 3.6. I am suggesting to integrate it in 3.6, as it is still supported as far as I know? I can port it to 3.7 and main branches afterward if it applies?
If you prefer having it on 3.7 or main only, I will adjust.

The process for this would be to get the fix into main first and then backport it to the relevant, active releases. Please change the target branch to main and I'll make the necessary label additions for automated backports to v3.7-branch and v3.6-branch (these require separate reviews and approvals).

Ah ok! I was not aware of that backporting method. I will adjust the target branch, thanks

Ah ok! I was not aware of that backporting method. I will adjust the target branch, thanks

You will also need to fix the commit logs by removing `subsys: ´ from the title in order to satisfy the compliance check.

Yes, this is a known issue in legacy USB device support, most drivers are fixed not to call callbacks from ISR context. Btw, STM32 shim driver has another mutex issue, https://github.com/zephyrproject-rtos/zephyr/issues/61464.

So I guess my question is then why don't we fix the STM32 driver, instead of modifying the subsystem functions to be ISR-safe?

Yes, this is a known issue in legacy USB device support, most drivers are fixed not to call callbacks from ISR context. Btw, STM32 shim driver has another mutex issue, #61464.

So I guess my question is then why don't we fix the STM32 driver, instead of modifying the subsystem functions to be ISR-safe?

I would argue that making the functions ISR-safe is a more robust way to fix the issue, and it will probably fix other issues in other drivers. If the mutex was absolutely necessary, then the fix would have been to adjust the STM32 driver, but as the protected code executes very quickly, the spinlock seems to me to be a better option anyway

I would argue that making the functions ISR-safe is a more robust way to fix the issue, and it will probably fix other issues in other drivers. If the mutex was absolutely necessary, then the fix would have been to adjust the STM32 driver, but as the protected code executes very quickly, the spinlock seems to me to be a better option anyway.

I agree that it is certainly a simpler solution. I guess what I'm trying to understand is if the STM32 driver should be making these calls from an ISR, or if the memoryWrite function is only intended to be called from a thread content. Looking at the implementation, it seems to signal a thread that memory is ready to be written to disk, so I suspect the function is intended to be called from an ISR, I just want to confirm. Perhaps @jfischer-no knows the answer here?

but as the protected code executes very quickly, the spinlock seems to me to be a better option anyway

This is generally true, but there isn't a constraint here. For example, the SDMMC disk driver checks card presence when getting disk status. For some card detection methods, the host needs to wait on the SD device to confirm it is present (which is a blocking operation). I'm still not opposed to the spinlock solution, I just want to make sure this is the best option, since when the choice is between changing a vendor driver or changing generic code I tend to bias towards modifying the driver.

I agree that it is certainly a simpler solution. I guess what I'm trying to understand is if the STM32 driver should be making these calls from an ISR, or if the memoryWrite function is only intended to be called from a thread content. Looking at the implementation, it seems to signal a thread that memory is ready to be written to disk, so I suspect the function is intended to be called from an ISR, I just want to confirm. Perhaps @jfischer-no knows the answer here?

This MSC implementation is essentially flawed because it uses global state variables without any proper synchronization. The device-next MSC implementation is significantly better because it correctly sequences operations (always in thread context) and also properly reports errors (e.g. disk removed).
If the disk subsystem works correctly with the device-next MSC, then I wouldn't change the disk subsystem.

I agree that it is certainly a simpler solution. I guess what I'm trying to understand is if the STM32 driver should be making these calls from an ISR, or if the memoryWrite function is only intended to be called from a thread content. Looking at the implementation, it seems to signal a thread that memory is ready to be written to disk, so I suspect the function is intended to be called from an ISR, I just want to confirm. Perhaps @jfischer-no knows the answer here?

but as the protected code executes very quickly, the spinlock seems to me to be a better option anyway

This is generally true, but there isn't a constraint here. For example, the SDMMC disk driver checks card presence when getting disk status. For some card detection methods, the host needs to wait on the SD device to confirm it is present (which is a blocking operation). I'm still not opposed to the spinlock solution, I just want to make sure this is the best option, since when the choice is between changing a vendor driver or changing generic code I tend to bias towards modifying the driver.

The mutex there only protects the dlist (register/unregister), not accesses to the disk device (IIRC there are some in the drivers as well), so I think the changes are fine. Obviously, the second commit does not fix a bug and cannot be backported, but the first commit does.

The mutex there only protects the dlist (register/unregister), not accesses to the disk device (IIRC there are some in the drivers as well), so I think the changes are fine. Obviously, the second commit does not fix a bug and cannot be backported, but the first commit does.

This is true- at the end of the day, this isn't really that large of a change to common code, and it is pretty low risk.

@jfischer-no are you okay with the adjustements I made based on your comments? I need your approval to be able to merge :) (changes requested)


CI checks that magic isn't malformed

Ref: https://github.com/teaxyz/cli/pull/300
It looks like a test as simple as for shell in fish zsh bash; do SHELL=$shell tea --magic | $shell; done might catch malformed magic code before it hits a users shell.

This was done.


WIP: Add long-term vision doc and basic info to README

I have been recently thinking about what should be the long-term vision for OpenTelemetry Agent/Collector. I believe it is important to have a clearly articulated set of high-level goals and guiding principles for the product that we work on. I took a first stab at it and would highly appreciate feedback on it and whether you think it is aligned with the goals of the OpenTelemetry community.
This has been already circulated internally at Omnition and also in Gitter channel https://gitter.im/open-telemetry/community

I signed it

I signed it

@pjanotti @bogdandrutu please have a look.

@pjanotti please merge this.


Remove needless clone

Why
Delete clones for efficiency
What

I erased unnecessary clones

Thanks!
bors r+

changelog internal (first contribution) remove needless clones


Gh 731 authorizations of user ignored when using inputformat

Codecov Report

Merging #735 into develop will increase coverage by 0.08%.
The diff coverage is 80%.

@@              Coverage Diff              @@
##             develop     #735      +/-   ##
=============================================
+ Coverage      59.83%   59.92%   +0.08%
- Complexity      2705     2708       +3
=============================================
  Files            408      408
  Lines          12369    12371       +2
  Branches        1400     1401       +1
=============================================
+ Hits            7401     7413      +12
+ Misses          4388     4377      -11
- Partials         580      581       +1

Impacted Files
Coverage Δ
Complexity Δ

...ndler/dataframe/GetDataFrameOfElementsHandler.java
100% <ø> (ø)
3 <0> (ø)
:x:

...ation/handler/dataframe/AccumuloStoreRelation.java
73.33% <ø> (ø)
6 <0> (ø)
:x:

...n/handler/javardd/GetJavaRDDOfElementsHandler.java
100% <100%> (ø)
3 <0> (ø)
:x:

...andler/javardd/GetJavaRDDOfAllElementsHandler.java
100% <100%> (ø)
3 <1> (ø)
:x:

...umulo/operation/handler/AbstractGetRDDHandler.java
78.94% <100%> (+5.26%)
7 <2> (+1)
:white_check_mark:

...n/handler/scalardd/GetRDDOfAllElementsHandler.java
100% <100%> (ø)
3 <1> (ø)
:x:

...tion/handler/scalardd/GetRDDOfElementsHandler.java
100% <100%> (ø)
3 <0> (ø)
:x:

...k/gov/gchq/gaffer/accumulostore/AccumuloStore.java
69.15% <33.33%> (-1.32%)
17 <0> (ø)

...ov/gchq/gaffer/accumulostore/utils/TableUtils.java
74.35% <0%> (-1.29%)
13% <0%> (-1%)

.../core/AbstractCoreKeyAccumuloElementConverter.java
70.11% <0%> (+4.21%)
57% <0%> (+3%)
:white_check_mark:

... and 1 more

Continue to review full report at Codecov.

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


fix: set initial result to 0 for count

What's changed and what's your intention?
previously it's null
Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)
fix #2475

Looks a bit complicated, will review it later.

Why not simply change the get_output part to return 0 if null 🤣?

Both are okay to me


ExceptionLayoutRenderer - Added support for AggregateException

Renders all AggregateException.InnerExceptions like the current InnerException-chain. Fixes #1738

This change is

Current coverage is 80% (diff: 78%)

Merging #1768 into master will increase coverage by <1%

@@             master      #1768   diff @@
==========================================
  Files           276        276
  Lines         17523      17546    +23
  Methods        2756       2757     +1
  Messages          0          0
  Branches       1975       1979     +4
==========================================
+ Hits          14089      14108    +19
- Misses         2988       2992     +4
  Partials        446        446

Powered by Codecov. Last update cd62cd0...fa71eb8

Cool & Thanks! Another nice feature for NLog  👍


Christina adding tree present function to main.py

Issue number
[Your PR must reference an issue. You can reference the issue by using the # character]
#3
Description
Adds a function for a Turtle that draws a present under the tree.
Checklist

[x] I have read and complied with the Code of Conduct and Content Guidelines as appropriate.
[x] I have followed the Contributing Guide.
[x] I agree to license my contribution under the License in this repository.
[x] The program runs successfully after making my changes.

Removed .DS_Store and added it to the .gitignore file


[tx] Handle _reverse attribute assertions (back references)

An assertion of the form
[[:db/add IDENT :db/_ref-attr ENTID]]

is equivalent to the assertion
[[:db/add ENTID :db/ref-attr IDENT]]

That is, this allows to add back-references.  It's particularly useful using the map shorthand of #180: for example, one can add and install a new attribute into the :db.part/db using:
[{:db/id #id-literal[-1]
    :db/ident :my/ident
    :db/valueType :db.type/long
    :db.install/_attribute :db.part/db}]

See also #202, which is probably a prerequisite to this work.

After #283, this will be ready to roll.  Around https://github.com/ncalexan/mentat/blob/6831925af0eafe9e647a462364b6188748f1e840/db/src/tx.rs#L139, you'll need to:

recognize that an attribute is reversed;
"swap" the e and v values -- this will require some special pattern matching and conversions, and might require type-checking a little earlier than where it happens right now (https://github.com/ncalexan/mentat/blob/6831925af0eafe9e647a462364b6188748f1e840/db/src/tx.rs#L169)
add test fixtures asserting the success and some of the failure cases for reversed attributes around https://github.com/ncalexan/mentat/tree/6831925af0eafe9e647a462364b6188748f1e840/tx/fixtures.  You might learn from the tests at https://github.com/mozilla/mentat/blob/master/test/datomish/db_test.cljc#L509, although they're not comprehensive.

In particular, we should:

test that reversing an attribute which isn't :db.valueType :db.type/ref fails cleanly (since the resulting e won't be an entid);
test that we can specify the value v as a numeric entid or a keyword ident;
think about handling reverse attributes and lookup refs (see #183) cleanly -- both the e and v values could be lookup refs.

@joe this is a good third ticket in the transactor, following on the work in #180.


UX: cursor not compatible with reactivity - modal does not appear

Describe the bug
In the editor step 1 the tab shows up, perfect.

On hovering the yellow marked surface the cursor becomes a hand, indicaiting clicking will give you a reaction (modal to change chart type).
However this expected modal is only ocurring if clicking on the grey circle appearing, which is difficult to hit exactly (especially on mobile screens).
To Reproduce
Steps to reproduce the behavior:

Go to step 1
Hover over chart symbol and watch the hand cursor
Click
get no reaction

Expected behavior
The modal shall be shown also on clicking the symbol.

@ptbrowne well done 👍


Error thrown when input object does not inherit from Object.prototype

The rename function in index.js uses obj.hasOwnProperty, which is not defined when the object does not inherit from Object.prototype. In the most basic example, this would fail with TypeError: obj.hasOwnProperty is not a function:
const input = Object.create(null);
input.a = 0;
require('rename-keys')(input, key => key);

A more realistic example would be trying to rename the keys of an object returned from querystring, which in Node v6 stopped inheriting from Object.prototype.
const querystring = require('querystring'),
    rename = require('rename-keys');

rename(querystring.parse('a=1'), key => key);

(Live example of the same)

@jonschlinkert I will prepare a PR for this now.


[FLINK-26673][changelog] Disable periodic materialization when periodi…

What is the purpose of the change
Do not start periodic materialization when periodicMaterializeDelay is negative.
Brief change log

check periodicMaterializeDelay in PeriodicMaterializationManager and disable periodic materialization when it is negative.

Verifying this change
This change is already covered by ChangelogPeriodicMaterializationITCase#testNonMaterialization().
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive):  no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? no

@flinkbot run azure


setuptools or numpy.distutils for the setup.py file?

We should check the differences between using setuptools and numpy.distutils to configure the setup.py file. Which one should we use?

According to NumPy’s documentation, numpy.distutils extends the standard python library distutils  to easily deal with Fortran files. If we are going to use Fortran code, it would be a good idea to use this.
However, many developers say that setuptools is easier to use. I found this on Stack Overflow:
Setuptools was developed to overcome Distutils' limitations and is not included in the standard library. It introduced a command-line utility called easy_install. It also introduced the setuptools Python package that can be imported inyour setup.py script, and the pkg_resources Python package that can be imported in your code to locate data files installed with a distribution. One of its gotchas is that it monkey-patches the distutils Python package. It should work well with pip. It sees regular releases

@LMMV was suggesting using both as long as the setup.py is functional. We have been doing this with MolSysMT (which has Fortran subroutines). That's why the setup.py file now is importing both packages. If you all agree, we can keep it this way, and if in the future there is no Fortran code in the library, we can remove numpy.distutils.

If we adopt the actions suggested in the MOLSSI cookie-cutter, this issue can be closed. Let's use the setup.py from the cookie-cutter as a template. We will include numpy.distutils only if it is necessary. See #2


OL4 zoom to feature(extent) with animation

Hi
I would like to change ol v3.20.1 to 4.0.1 but have a problem with zoom to feature with animation.
Example: https://jsfiddle.net/6gLweox7/3/
Old method "beforeRender(pan, zoomAnimation)" was removed from OLv4.
I can't find any example for solve this problem.

You can easily achieve this by passing a duration option as 2nd argument to ol.View#fit():
view.fit(vectorLayer.getSource().getExtent(), {duration: 1000});

Thank you very much!

don't work please full working example for fit animate.

See https://codepen.io/ahocevar/pen/GQWYRb?&editors=1010# for a working example.

thanks so much. that was my bad. Sorry


sh error "1 not found"

The first part of the base command doesn't work:
https://github.com/genome/analysis-workflows/blob/295e7b7f51727c0f2d6cc86ce817449b2e8dba3c/definitions/tools/cnvnator.cwl#L7

When we tried to start cnvnator with escape "$" in ${SAMPLE}, there is the error:
'source' '/opt/root/bin/thisroot.sh' && '/bin/bash' 'run_cnvnator.sh' '/var/lib/cwl/stg3a3d11b2-e63c-42de-bc0c-200400b6cf0b/2895499237.bam' '100' 'chr1 chr2 chr3 chr4 chr5 chr6 chr7 chr8 chr9 chr10 chr11 chr12 chr13 chr14 chr15 chr16 chr17 chr18 chr19 chr20 chr21 chr22 chrX chrY' '/var/lib/cwl/stge06e1f61-a72b-43dc-a583-21fda44505cf/chr17_test.fa' 'serge_sample1'
/bin/sh: 1: source: not found

source is a bash keyword, but cwltool is using /bin/sh as its shell :
https://github.com/common-workflow-language/cwltool/blob/cf9d7cdefa6dfb3b678636da02bc55b6108c04ac/cwltool/command_line_tool.py#L618
The simple fix would be to switch to . instead of source, but it looks like /opt/root/bin/thisroot.sh might have at least one thing in it that also doesn't work with /bin/sh, so fixing that will be slightly more complicated.


I forgot my password, how should I reset it?

Installing using Docker

Reference: https://github.com/usememos/memos/issues/188


Fix errors in console

Console yields "Uncaught TypeError: Cannot read property 'setAttribute' of null at (index):48". Problem with document boundaries or what?

It should have been
var avatar = document.getElementById("avatar");
avatar.addEventListener("load", function() {
  avatar.contentDocument.getElementById("circle").setAttribute("fill", "black");
});

, but given that SVG already has black fill I'm going to remove the script whatsoever. In case with résumé page I could add additional check to see if contentDocument is not empty, but I will not do it, because probability of error is very low and I like to keep things tidy so one-liner stays.


Send text notifications utilizing Pinpoint

Value Statement
As a VANotify consumer
I want to send text messages
So that text message notifications can be sent to the Veteran
Acceptance Criteria
GIVEN VANotify receives a request to send a text notification
WHEN Pinpoint is setup
THEN a text message is attempted to be sent to the respective mobile phone
GIVEN VANotify receives a text request
THEN   VANotify passes the request to Pinpoint, and they receive it Pinpoint will try to deliver the text
GIVEN service is newly created
When the service has not specified a sender from number
THEN the text will be sent from the global default sender from number
GIVEN VANotify receives a text request
When the service has been assigned a sender ID / from number
THEN the text will be sent from that assigned sender ID / from number
GIVEN VANotify receives a text request
When the request contains a specific / non-default sender ID / from number that has overridden the assigned service sender ID / from number
THEN the text will be sent from that specific sender ID / from number
GIVEN VANotify receives a request to send a text notification
WHEN VANotify makes a request to Pinpoint
THEN environment-specific project ID is used
GIVEN VANotify receives a request to send a text notification
WHEN VANotify makes a request to Pinpoint
THEN the message type is set to transactional
Checklist

[ ] Infra:

[x] Create a Pinpoint project for each of our environments - Dev, Staging, and Prod using Terraform
[x] Create SMS channel for the Pinpoint project(s): an SMS channel is a Pinpoint concept that is referential to marketing and a channel means a notification type like text, email
[ ] Request a Long Code for each of the environments UPDATE: waiting from Ike to see if long codes can be project (aka env) specific
[x] Modify permissions for execution role (api one) to allow pinpoint access
[x] If possible, define default senderId per environment UPDATE: sender_id is not used in US, so we can't set it.

[x] logs with notification_id
[x] metrics
[ ] --feature flag-- UPDATE: no feature flag, just setting provider active status to false and low priority. Modify per environment when ready.
[x] db migration
[ ] user flows test
[x] config global sender default and other Pinpoint stuff
[ ] investigate what happens when someone replies (right now, 2 way communication is out of scope, but does the message come back to us?)
[ ] Can we update SMS spending limit here? Or does it have to be made via api call?
[ ] Per each environment for existing services, update default "sms_sender" to appropriate Pinpoint origination number, so they aren't random strings anymore. Prioritized services: Vetext, VANotify, VANotify Team

Assumptions

Pinpoint is approved and available for utilization
Pinpoint is defined as the primary provider (has the lowest priority)
Sender ID / from number is the same thing - just different names that might be used for clarity you might also see the term "Service SMS Senders"
We can test without long codes and AWS will utilize some shared number - but we also already have one long code from Pharmacy Use Case and AWS will prefer that
We will have a default number for each environment so if we don't specify a number for the use case the default number can be used
We will use Long Codes for now until we get approved for Short Codes
Most messages sent will be transactional (as opposed to promotional)

Additional Info/Resources

Refer to the CDS setup and config for Pinpoint link
Refer to CDS implementation for Pinpoint PR
We can't specify area codes we want in our Long Code requests via self-service

Resources

Terraform aws_pinpoint_app link
Terraform aws_pinpoint_sms_channel link
AWS Pinpoint recommended developer guide link
AWS Pinpoint Messages API reference link
Pinpoint Python SDK link

methods of interest:

#get_app <-- responses contains application_id
#send_messages <-- requires application_id

Out of Scope

Two-way communication
Delivery status and research mode works
Working on access to a Short Code

Open Questions

Explore can we request long codes automatically via Terraform?
As we are reading through the Pinpoint docs, we will keep in mind to explore whether we will need to create templates on the Pinpoint side. Maybe we do...maybe we don't?

@QaysarA can we review what pinpoint is and how we are using it? I think it is related to the short and long codes right?

List of things to test in QA:
Check provider list to make sure pin point is prioritized
Send a text message to self
one more thing I didn't here

Kickoff questions:

[ ] - Are we doing any additional or modifying existing rate-limits?
[ ] - clarification for out-of-scope item "Delivery status and research mode works" - meaning we do not need to confirm delivery status?
[ ] - enable feature flag?
[ ] - confirm this is adding 'pinpoint' as new SMS provider

Are we doing any additional or modifying existing rate-limits?
No. However I'm curious where did this question come from - maybe we are missing something?

clarification for out-of-scope item "Delivery status and research mode works" - meaning we do not need to confirm delivery status?
Handling delivery statuses and research mode will be handled in a separate story - #273
So you might want to manually confirm in AWS console (if possible) that SMS was delivered. But passing delivery status to VANotify  and subsequent processing is out of scope.

enable feature flag?
I've been changing my stance on that. Initially I wanted all the providers to be behind feature flags. This was primarily driven by the fact that we need to put settings for Twilio provider even when we do not use it, or the application won't start.
However providers already have "active" flag that we can change using an API call (or via DB migrations). So my current stance is to not have feature flags as long as the provider does not interfere with the app (and startup) when not used / deactivated.
I'll appreciate any feedback, thoughts, discussions on that topic.

confirm this is adding 'pinpoint' as new SMS provider
I confirm.

@ffafara-tw
re: rate-limiting:

I may have misunderstood from our group discussion last week on Pinpoint, where we talked about this (straight from my notes)STORMING SESSION AROUND rate-limiting around SMS capabilities with primary focus on Pinpoint. This was towards the end of the chat. There are options to set limits within Pinpoint, but not required.

re: feature flag:

We are kind of all over the place with how we are going about it, the recipient identifier flag is an environment variable set in task defs, whereas the govdelivery client is in our config file...and also maybe we have not been great at managing the flags, for instance we still have our feature flag for GOVDELIVERY_EMAIL_CLIENT_ENABLED. Apart of the downside of managing flags, the upside is how it contextualizes features in our codebase from a product perspective. Leverage an api call or db migration might not express the same level of context. That being said, this is a simple make active true/false scenario, so either way is fine for this instance.

Marisa and I combed through the documentations on both AWS and Python SDK side for Pinpoint. We did some testing in the AWS cli as well as the console. We were trying to send text via the CLI but ran into cli errors...to be continued on Monday. If successful, ducks are in a row to go! 🦆🦆🦆

Possible question for meeting with pinpoint rep: do they know if it's possible to programmatically create long codes?

I don't think it is.
I was looking for that in their documentation and AWS CLI docs and there wasn't anything there.

Cool -lets ask to be sure. @Filip Fafara<EMAIL_ADDRESS>I've
asked Marisa, Ling and Emily to come prepared with some questions for
tomorrow.
M
On Tue, Dec 15, 2020 at 5:24 PM Filip Fafara<EMAIL_ADDRESS>wrote:

I don't think it is.
I was looking for that in their documentation and AWS CLI docs and there
wasn't anything there.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/department-of-veterans-affairs/notification-api/issues/251#issuecomment-745606118,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTMDO7WHHXODCOKGMVHTZDSU7O2LANCNFSM4TPXKIEQ
.

--
Maria Becker
Product Manager
Email<EMAIL_ADDRESS>Telephone<PHONE_NUMBER>
Pronouns they/them or she/her
[image: ThoughtWorks]
http://www.thoughtworks.com/?utm_campaign=maria-becker-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator

Things we hope to bring up during call:

Longcodes - more explanation around this? Can we specific longcodes specific to projects? Seems to be account level setting.
How does 'quiet time hours' get enforced? Does this apply to api calls to Pinpoint?

This is great! Do we need to ask anything  about opt outs?
M
thought with care
written with haste
reading up to you

On Dec 16, 2020, at 10:44 AM, Ling Tran<EMAIL_ADDRESS>wrote:

Things we hope to bring up during call:
Longcodes - more explanation around this? Can we specific longcodes specific to projects? Seems to be account level setting.
How does 'quiet time hours' get enforced? Does this apply to api calls to Pinpoint?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Test plan doc (WIP) - https://docs.google.com/document/d/1XvyGqeji2u8lMCoCS-tHex3vyNTsZ-HCByFlJQOwNS8/edit

Tested in dev Pinpoint integration, cross-referenced with logs. Datadog dev-pinpoint dashboard in the last four hours today (12/23): https://app.datadoghq.com/dashboard/rgg-5ee-rwf?from_ts=1608751307447&live=true&to_ts=1608765707447
It looks like celery workers stopped updating in the logs, so the last few messages I tried to send my phone never got, although the logs indicate success.
Emily and I tested without setting any default sms_sender information for service. The 'FROM_NUMBER' gets set when a service gets created without it. Initially when we tested, we did it without having Pinpoint as the primary provider nor was it active. In that scenario, the two long codes we have are alternately used.
Once activated Pinpoint and gave it a higher priority of 5 (while lowering SNS priority to 10), we were able to verify that Pinpoint was the provider used and text messages were sent. However, rather than use the specified long-code (pinpoint origination number) for dev, the messages were sent to the last number I received from the VA, which happened to be the staging number. We will have to investigate why. We have a feeling it may be related to the 'FROM_NUMBER' usage...at this time the only things we have verified about the 'FROM_NUMBER' config var are:

config['FROM_NUMBER’] == notification#reply_to_text == provider#send_sms(sender arg)
When creating a service, a ‘service sms sender’ is also created, with a default sms_sender value pulled from config[‘FROM_NUMBER’]

Attached are also Datadog graphs. There was an initial error due to access issues (and it was logged...issue has been fixed).

We want to test (1) creating a service with a sms_sender set and (2) see what happens when we reply to the message.
We want to set the Pinpoint app id dynamically on the infra side and set it as a task definition env var. As of now to get to testing, we have set the app id as a config with a default value pointing to the dev pinpoint project.

It looks like celery workers stopped updating in the logs, so the last few messages I tried to send my phone never got, although the logs indicate success.

Which logs indicate success?
It sounds like this might be the problem we have seen in the past where celery stops processing events. Can you check SQS queue?
Sent from my iPhone

On Dec 23, 2020, at 6:38 PM, Ling Tran<EMAIL_ADDRESS>wrote:
It looks like celery workers stopped updating in the logs, so the last few messages I tried to send my phone never got, although the logs indicate success.

end of day update:

verified able to consistently send from assigned origination number in dev, WIP in staging (had to add app id as env var - to test tomorrow)
in staging, made Pinpoint highest priority sms provider and is active; started with vanotify-team service in modifying its default sms sender number

end of day update:

verified able to consistently send from assigned origination number in dev, WIP in staging (had to add app id as env var - to test tomorrow)
in staging, made Pinpoint highest priority sms provider and is active; started with vanotify-team service in modifying its default sms sender number

Update at the moment: dev and staging environments are set with default sms senders to respective long codes. Pinpoint has been elevated in priority over SNS as SMS client in dev and staging. Will tackle prod next

Update at the moment: dev and staging environments are set with default sms senders to respective long codes. Pinpoint has been elevated in priority over SNS as SMS client in dev and staging. Will tackle prod next

Handy cli command to check delivered messages from specific pinpoint project/app (takes about 5 minutes for stats to update after a delivery): aws pinpoint get-application-date-range-kpi \     --application-id <app-id> \     --kpi-name txn-sms-delivered

Handy cli command to check delivered messages from specific pinpoint project/app (takes about 5 minutes for stats to update after a delivery): aws pinpoint get-application-date-range-kpi \     --application-id <app-id> \     --kpi-name txn-sms-delivered

Can you document that CLI command somewhere in vanotify-team repo? Maybe in
documents/support folder?
On Tue, Jan 5, 2021 at 2:25 PM Ling Tran<EMAIL_ADDRESS>wrote:

Handy cli command to check delivered messages from specific pinpoint
project/app (takes about 5 minutes for stats to update after a delivery): aws
pinpoint get-application-date-range-kpi \ --application-id
--kpi-name txn-sms-delivered
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/department-of-veterans-affairs/notification-api/issues/251#issuecomment-754847180,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANNLRX6UWOJHV4CDIPSMEZDSYNRSPANCNFSM4TPXKIEQ
.

--
Filip Fafara
Consultant
Email<EMAIL_ADDRESS>Telephone +1<PHONE_NUMBER> <+1+267+262+0689>
[image: ThoughtWorks]
http://www.thoughtworks.com/?utm_campaign=filip-fafara-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator

Can you document that CLI command somewhere in vanotify-team repo? Maybe in
documents/support folder?
On Tue, Jan 5, 2021 at 2:25 PM Ling Tran<EMAIL_ADDRESS>wrote:

Handy cli command to check delivered messages from specific pinpoint
project/app (takes about 5 minutes for stats to update after a delivery): aws
pinpoint get-application-date-range-kpi \ --application-id
--kpi-name txn-sms-delivered
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/department-of-veterans-affairs/notification-api/issues/251#issuecomment-754847180,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANNLRX6UWOJHV4CDIPSMEZDSYNRSPANCNFSM4TPXKIEQ
.

--
Filip Fafara
Consultant
Email<EMAIL_ADDRESS>Telephone +1<PHONE_NUMBER> <+1+267+262+0689>
[image: ThoughtWorks]
http://www.thoughtworks.com/?utm_campaign=filip-fafara-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator

added user flow test for simple happy path, do not pass in personalisation in payload. do we want to test with personalisation? not sure what will be passed.

added user flow test for simple happy path, do not pass in personalisation in payload. do we want to test with personalisation? not sure what will be passed.

No need to use template with personalization.

No need to use template with personalization.


Connection header not parsed properly, breaks FF websockets

See https://bugzilla.mozilla.org/show_bug.cgi?id=730742 and joyent/node#2849.
In a nutshell, FF sends a header that looks like Connection: keep-alive, upgrade while http-parser only understands Connection: upgrade. Should be fixed on short notice.

You might also want to make your parser/server reply with a HTTP error if parsing goes wrong?  FF simply saw no reply and had to eventually time out the connection.
cheers,
Jason Duell
Mozilla

@jduell: Can you post the verbatim HTTP headers? I can't get http://www.twimbow.com/dashboard.php to send me any WS upgrade headers.

Firefox' WebSockets work just fine with node. Tested with:

node 0.6.11
Firefox 10.0.2
ws 0.4.8

What do you think of moving the header comparison logic out of http-parser and requiring the application to deal with it? A proxy application is going to need this logic anyway (since they're manually generating HTTP bytes for the request/response), and even non-proxies still need to communicate whether or not this is a response to a HEAD request via the on_headers_complete() callback. What if we delegated all header processing logic to the application and added a channel to communicate knowledge derived from those headers (keep-alive? is there a response body? how long is it?) from the application to the parser?

@pgriess, this isn't actually a http-parser bug. It parses Connection: keep-alive, upgrade just fine, and passes it on to node's parser.

@einaros Yeah, but to get message framing right, the parser needs to know if there is a keep-alive or upgrade connect token. Right now, it doesn't know how to tokenize Connection headers -- it just assumes there is a single token in the header value.
If we instead offloaded this header-interpretation work to the application, the parser would get a lot simpler.

@pgriess, I wrote a patch for that earlier today. Unsure if that's fit for the parser, though.

@bnoordhuis:

I can't get http://www.twimbow.com/dashboard.php to send me any WS upgrade headers.

The browser sends the upgrade header (from JS: you have to wait a minute).  Here's a wireshark capture of the resulting HTTP request from the websocket creation:
GET /rand/1789415e9e8fb74eed55c90adb7622bd4ac33773b09ce457c4794ae03246d5a3dfcd2484f4ba4be321fde546d3710cb63f6ed865545c8afa2e913db25f58be2d57b806b65e8ae2771e2719559c73dae3188f48e896b8d29e1c287180aae14ae726bd20888eda1e3188c869bf8628130b7665f4af52c4789d06/433e8a1da527942f2c781ff904ae07b9/twimbow HTTP/1.1
Host: twimbow.com:8125
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120228 Firefox/13.0a1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive, Upgrade
Sec-WebSocket-Version: 13
Origin: http://www.twimbow.com
Sec-WebSocket-Key: kWYBHLg2fBw3KuYTBYFJ2A==
Cookie: __utma=9462832.1788180937.1330419635.1330419635.1330479818.2; __utmz=9462832.1330419635.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmb=94628<IP_ADDRESS>0479818; __utmc=9462832
Pragma: no-cache
Cache-Control: no-cache
Upgrade: websocket

And no, that's not a carriage return after GET and the resource, just a space :)

I can't get http://www.twimbow.com/dashboard.php to send me any WS upgrade headers.

The browser sends the upgrade header (from JS: you have to wait a minute)

You also have to be logged in

@jduell, any luck finding out which version and library they use?

Okay, I think @einaros is right: this is not a node or http-parser bug. I was under the impression that the client sent a Connection header without an Upgrade header (technically a violation of the spec but something we could work around) but that's not the case.

So I think that this particular issue is not an http-parser bug, but it did expose another bug to the light of day: the parser is treating the Connection header as though it always contains a single token. This is a problem because it relies on being able to figure out if Connection: close or Connection: keep-alive was set to handle message framing. For example, if the client sent
GET / HTTP/1.0
Connection: foobar, keep-alive

The parser should recognize this as a valid keep-alive request.

Oh, sweet. It looks like @kolbyjack has a pull request for this already: #100.

Will that pullreq handle Connection: foo, ,bar?
I'd check, but I'm barely able to comment on this windows phone I'm currently on.

It doesn't, but it's a trivial fix.  I'll update the pull request in a minute.

I don't see anything in the rfc about precedence between the settings.  The current PR doesn't deal with lws properly at all, and a quick attempt to fix it isn't working either, so I'll have to wait a bit until I can fix it.  My multi-header, do you mean multiple Connection: headers?  I don't see that explicitly covered in the rfc either.

any luck finding out which version and library they use?

No, but I didn't push hard once it seemed like it wasn't a library-specific issue.  If it is, I can ask him again.

@jduell, well it at least works with my websocket library, so I'd say it probably isn't a node issue.

@einaros: I don't know your core/lib logic well enough to say.  If you want me to email the guy (or put you in touch directly) let me know.

Closing issue, not a bug.
@kolbyjack: I'll review PR #100 later this week.


make the poetry installation work; add dalmatian as a package

We have a working version of poetry for genepy python packages, while ignoring all R packages dependencies. We need to find the necessary functions for depmap_omics to add into that repo

Ah! I didn't fully understand what you meant when you said you added damination, but now that I've looked at the diff, I see you copied the damination into this repo.
I also see bumped the version of python to 3.11.
My guess of what's going on here is:

you want to use python 3.11
firecloud-damination is broken in python 3.11
you copied the damination code into a folder into this repo and made some small fixes to allow it to work with python 3.11

Is that correct?
If so, I propose a slightly different workflow:

use github's "fork" function to make a clone of firecloud-damination called something like cds-firecloud-damination.
Make a branch in the cds-firecloud-damination repo with your python 3.11 fix.
update the dependencies to install dalmaition from that repo instead of from pypi.

this has advantages for maintenance in the future:

If firecloud-dalmatian is updated in the future, we'll be able to easily "merge" their changes into our patched version.
you can provide your 3.11 fix to them as a pull-request. The easier you make it for them to take, the more likely they might just merge it in.
it captures the history better where we'll be able to see that the only difference between our version and their version is just the changes you made. (As opposed to looking like these are entirely new files in this repo)

Yes, it is correct. For the firecloud-damination pypi package used in genepy, it only supports Python 3.4. After a closer look at their latest commit at firecloud-damination github, they already corrected this.
I agree with you on the workflow that will easily update the damination with cds-firecloud-damination fork. I'll make a revision on this poetry pull request using this suggestion


Implement interfaces for providers package

This commit lays the ground work for fetching multi-provider API data by the interface methods that every provider must implement.
It also includes the logic to set log level, which I couldn't pull out as a separate commit. And, an HTTPClient interface signature change.

Implement Provider interface for open-meteo.com
Placeholders for meteoblue.com
Unmarshals the data onto plumber.BaseData struct
Return HTTPClient for HTTPClient.NewRequest() method so that client methods can be chained as resty natively does.

#5 #2

@Yendelevium Have I addressed your concerns? Or, is there something I must resolve for this PR to be approved?

Yeah, looks good to me 👍🏿

Cool, thanks! Please approve the PR by clicking the approve button so that it can be merged @Yendelevium


[Service Bus Client] Test Support for Multi-Cloud

Summary
The focus of these changes is to remove hardcoded assumptions about the Azure cloud environment in which tests are running and, instead, take advantage of an extended set of environment variables in Azure.Core.  Additionally, performed some refactoring of environment variable names
and structure to map more cleanly to the changes introduced with the Azure.Core::TestEnvironment changes.
For consistency, bot the track one and track two test suites will now run against resources defined by test-resources.json, rather than dynamically
created or hardcoded environment assumptions.
Last Upstream Rebase
Monday, August 3, 5:22pm (EDT)
References and Related Issues

New-TestResources.ps1 should set AZURE_AUTHORITY_HOST environment variable (#757)
Event Hubs: AAD Auth failure when testing against other clouds (#12964)

Setting to draft until test passes in the environment can be confirmed.

/azp run net - servicebus - tests

Flipping to non-draft state.  Looks like the failure was a timeout in one of the T1 tests.

/azp run net - servicebus - tests


Fix spurious rebuilds from dumped vars

Commit f49f452f2 greatly tidied up the file, which is nice, but also
introduced some whitespace around the first argument to vars-prereq.
In Make, this causes chaos!
In particular, we ended up checking whether a variable called
something like "$(last-   gen  -vars-loaded)" was defined. It isn't,
but $(last-gen-vars-loaded) is.
Call strip in the vars-prereq function to get rid of the whitespace at
the "entry point" for all this machinery.

Ha! Not that sharp: you should have seen how many $(info ...) lines I had to add before I figured out what was going on...


[WIP] Add tutorial as notebook, and configure Binder

Hi!
I copied the tutorial from the wiki into a Jupyter notebook, and configured binder to be able to run it. Here is an example:
Notes

I'm building MMseqs2 from master, but you can also pick a specific tag to put in the binder link

TODO

[ ] Link in README.md? (or at least back in the wiki?)
[ ] Tutorial from wiki failed for me because --report-mode is missing in the bioconda package?
[ ] Preload data during the postBuild step in binder? Not sure about this one, since it changes the tutorial a bit, but avoids redownloading everything during runtime.

Need to at least preload the taxdump, I think binder is blocking the download (is it an FTP link? binder blocks FTP downloads...)

[ ] Clean up outputs (don't want to spoil what is the mystery pathogen!)
[ ] Fix path to logo in the intro

That's really neat, thanks!
--report-mode will be in release 11, exists currently only in git.
I am however not sure I want to binder version in the main repository. Is it possible to add and run it from the GitHub wiki repo (https://github.com/soedinglab/MMseqs2.wiki)?

Just placed the stickers in the post. Thanks a lot!

--report-mode will be in release 11, exists currently only in git.

Noted!

I am however not sure I want to binder version in the main repository. Is it possible to add and run it from the GitHub wiki repo (https://github.com/soedinglab/MMseqs2.wiki)?

I think it is possible (because it's a git repo), but I never tried that with binder. Will report back.


Added the NewsBlur API Python wrapper

Please find the newsblur_wrapper.py enclosed.
Thanks
(link: https://github.com/dananjayavr/NewsBlur/blob/master/newsblur_wrapper.py)

Thanks for this. I took the liberty of re-writing it. It's now under api/newsblur.py.

Great!


Add submodule support

Is your feature request related to a problem? Please describe.

I want to run two different blogs with the same content. To accomplish this I decided to store the /content folder as a different repo and then add it via git add submodule to the respective repos of both the blogs.
When I built the blogs (on Netlify) using Hugo, there were no issues. However, when I logged in to Netlify CMS, none of the posts was displayed. When I tried to create a post, I got the following error: Failed to persist entry: API_ERROR: GitRPC::BadObjectState.
I expected Netlify CMS to read the content from the submodule and allow additions/modifications to it.
Describe the solution you'd like

Netlify CMS should be able to detect and write content to an existing submodule.
Describe alternatives you've considered

I couldn't think of any other alternative except for cloning the content folder of one blog to the other whenever I make an update. However, an author who doesn't have repo access won't be able to do so.
Additional context

The repo where I was trying to implement this can be found here: https://github.com/ragasirtahk/backend
Just in case I made some mistake and Netlify CMS already supports this ¯_(ツ)_/¯

To add more context:
curl  "https://api.github.com/repos/ragasirtahk/backend/git/trees/master:content" returns:
{
  "message": "Not Found",
  "documentation_url": "https://developer.github.com/v3/git/trees/#get-a-tree"
}

curl  "https://api.github.com/repos/ragasirtahk/backend/git/trees/master" returns a tree entry of:
{
  "path": "content",
  "mode": "160000",
  "type": "commit",
  "sha": "7c6940397cc9b6072b36c39d8e88d4db043df754"
}

@erezrokah - One of our CMS users has reported that they cannot update a post due to:
Failed to persist entry: API_ERROR: GitRPC::BadObjectState.
We are, however, not using Git submodules.

Any ideas?

Hi @kylekirkby that error can come up when not using submodules:
https://community.netlify.com/t/failed-to-persist-entry-api-error-gitrpc-badobjectstate/12639
I would suggest opening a new issue with a reproduction


Javascript Json error

it appears while using it, comes again everytime i write or click around.

@varwone but the app keeps working?

Yes. Just throws out those messages which makes it unable to use.
Ifedapo .A. Olarewaju<EMAIL_ADDRESS>schrieb am Do., 14. Juni
2018, 08:30:

@varwone https://github.com/varwone but the app keeps working?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ifedapoolarewaju/igdm/issues/350#issuecomment-397186071,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIYnNb5yO9Oq1JBAnAYFRNBYH-QNL1hyks5t8gLzgaJpZM4UkYqD
.