change description when no static exports found

What kind of change does this PR introduce?
feature/bugfix

Did you add tests for your changes?
No (it's just an info description change and the description wasn't tested anyway)

Summary
Closes #4877

Does this PR introduce a breaking change?
No

Other information
This change makes most of examples a bit inaccurate (they show old info description). I can alter examples if needed.

Thanks


Restore routes for archived whitehall artefacts.

When artefacts are archived, panopticon normally registers gone routes
for them.  Whitehall-owned artefacts are an exception to this; these
ones are skipped ([1] and previously [2]).
There are currently a number of these whitehall-owned artefacts with
gone routes in the router. This means that the unpublishing redirects
(which are normally served by whitehall itself) are not working.
Additionally, there are a small number of gone routes for live content.
This is probably leftover from the mystery unpublishing bug that's now
been fixed[3].
This adds a migration to restore the routes for all whitehall-owned
artefacts to the state they were before they were archived.
[1]https://github.com/alphagov/panopticon/blob/master/app/models/routable_artefact.rb#L30
[2]https://github.com/alphagov/panopticon/blob/release_703/app/observers/update_router_observer.rb#L7
[3]https://github.com/alphagov/whitehall/pull/1974

Tiny comment, otherwise :+1:


Whatsapp data

Requested WhatsApp for my data. This is mainly a reminder to take a look and see how easy it would be to read it in.

Is it so easy that it makes no sense to create a reader just for WhatApp
Is it so variable and complicated that maintaining a reader would not make sense
Or is it in the middle and a reader makes sense

No chat data or really any useful information in the WhatsApp data


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

Codecov Report

Merging #370 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #370   +/-   ##
=======================================
  Coverage   85.04%   85.04%
=======================================
  Files           1        1
  Lines         214      214
=======================================
  Hits          182      182
  Misses         32       32

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 f9258e0...c75e310. Read the comment docs.

Coverage remained the same at 85.654% when pulling c75e310e0ef249179f8bc84040c4c7aa4aa663d4 on template-sync-1 into f9258e05c2af2b94f37734c6490be392b014358a on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


MarkerClusterGroup is not workable with latest version of react-leaflet

'No context provided: useLeafletContext() can only be used in a descendant of ' with latest version of react-leaflet

Uncaught Error: No context provided: useLeafletContext() can only be used in a descendant of <MapContainer>
    at useLeafletContext (:3000/static/js/vendors~main.chunk.js:467)
    at usePath (:3000/static/js/vendors~main.chunk.js:981)
    at ContainerComponent (:3000/static/js/vendors~main.chunk.js:402)
    at renderWithHooks (:3000/static/js/vendors~main.chunk.js:104109)
    at updateForwardRef (:3000/static/js/vendors~main.chunk.js:106131)
    at beginWork (:3000/static/js/vendors~main.chunk.js:108119)
    at HTMLUnknownElement.callCallback (:3000/static/js/vendors~main.chunk.js:93059)
    at Object.invokeGuardedCallbackDev (:3000/static/js/vendors~main.chunk.js:93108)
    at invokeGuardedCallback (:3000/static/js/vendors~main.chunk.js:93168)
    at beginWork$1 (:3000/static/js/vendors~main.chunk.js:112910)
    at performUnitOfWork (:3000/static/js/vendors~main.chunk.js:111746)
    at workLoopSync (:3000/static/js/vendors~main.chunk.js:111683)
    at renderRootSync (:3000/static/js/vendors~main.chunk.js:111649)
    at performSyncWorkOnRoot (:3000/static/js/vendors~main.chunk.js:111266)
    at :3000/static/js/vendors~main.chunk.js:100519
    at unstable_runWithPriority (:3000/static/js/vendors~main.chunk.js:129997)
    at runWithPriority$1 (:3000/static/js/vendors~main.chunk.js:100465)
    at flushSyncCallbackQueueImpl (:3000/static/js/vendors~main.chunk.js:100514)
    at flushSyncCallbackQueue (:3000/static/js/vendors~main.chunk.js:100502)
    at flushPassiveEffectsImpl (:3000/static/js/vendors~main.chunk.js:112569)
    at unstable_runWithPriority (:3000/static/js/vendors~main.chunk.js:129997)
    at runWithPriority$1 (:3000/static/js/vendors~main.chunk.js:100465)
    at flushPassiveEffects (:3000/static/js/vendors~main.chunk.js:112402)
    at flushDiscreteUpdates (:3000/static/js/vendors~main.chunk.js:111329)
    at flushDiscreteUpdatesIfNeeded (:3000/static/js/vendors~main.chunk.js:92882)
    at dispatchDiscreteEvent (:3000/static/js/vendors~main.chunk.js:95049)
index.js:1350 The above error occurred in the <ForwardRef(ContainerComponent)> component:

    at ContainerComponent (http://localhost:3000/static/js/vendors~main.chunk.js:402:9)
    at div
    at MapContainer (http://localhost:3000/static/js/vendors~main.chunk.js:118149:5)
    at div

		"leaflet": "1.7.1",
		"leaflet.markercluster": "1.5.3",
		"react-leaflet": "3.2.2",
		"react-leaflet-markercluster": "3.0.0-rc1",

I also found this issue but with a different error message and a different react-leaflet version here https://codesandbox.io/s/github-leaflet-marker-cluster-bug-6nur7s

Hi @jaballogian
I have the exakt same configuration and the same error message. What did you do about it in the end?
Cheers

Hi @jaballogian
I have the exakt same configuration and the same error message. What did you do about it in the end? Cheers

Hello @ayalpani
Sadly, I still use react v17 and react-leaflet v3 now
In the future, if this library has supported react v18 and react-leaflet v4, I would try to update all the dependencies

Thanks @jaballogian for your quick response. I will have to stick with React 17 then too for the moment


Add Roundtables

Can we add a third tab to the Program page (https://www.chilconference.org/program.html), titled "Research Roundtables"
The 3 titles and abstracts are available here: https://docs.google.com/document/d/1i8-a2sXtmGixOS9ODeS0sA_p8R2qRMUHKoTS5bTwpZo/edit#heading=h.7vkz3qbybx8z
Headshots are being collected but please post these in the meantime

We can most likely do this but it's slightly nontrivial and we're prioritising getting the website functionality finished, so probably we won't get to this before the weekend.


E2E tests are failing

It's been awhile since the last time I toched the extension. When using recent version of VSCode, many tests are failing during run. Error is:
Extension 'Text Tables' failed to update workspace folders:
Error: Entering a new workspace is not possible in tests.

Looks like I need to figure out how to test different configurations without creating workspace from test.

Fixed in #61


Change highlighting from shell to console

The console parser treats the $ as special, which makes it not
be selectable when selecting the text for copying and pasting.
shell is bash script, which by definition does not have $ in the
input/outputs.

I have looked through all episodes and made modifications where needed.

The only possible downside is this kind of construct:
$ git branch experiment master   # create branch called "experiment" from master
                                 # pointing to the present commit
$ git checkout experiment        # switch to branch "experiment"
$ git branch                     # list all local branches and show on which branch we are

The second line has # which gets parsed as a root prompt, not a
comment.  Most of the blocks that aren't marked as console already
had these kind of comments, so maybe it is intentional that they are
not console?
I'm thinking it is better to move them to console now, the
highlighting is not perfect, but since we have been discussing $
not being copied, "not copying $" is more important than "prefect
coloring".  The "#" on the second line will also not be copied,
which can cause invalid syntax on line 2.

Review: comment above

Sample of what this looks like, console highlighting with multi-line comments:

Copying and pasting would produce this (note the problem with the second line):
git branch experiment master   # create branch called "experiment" from master
                                 pointing to the present commit
git checkout experiment        # switch to branch "experiment"
git branch                     # list all local branches and show on which branch we are

Since copying the $ causes problems anyway, I am thinking the new state is no worse than the previous one.

Actually this solves it - for every line that has only comments, prefix with $ (which won't be copied, but forces the following # to be a comment, not a prompt):
$ git branch experiment master   # create branch called "experiment" from master
$                                # pointing to the present commit
$ git checkout experiment        # switch to branch "experiment"
$ git branch                     # list all local branches and show on which branch we are

Any objects to implementing this?

Thanks! This is great. Since I/we will go through all lesson anyway, we can iron out last rendering quirks.


[Snyk] Upgrade @types/luxon from 3.3.0 to 3.4.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @types/luxon from 3.3.0 to 3.4.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 11 versions ahead of your current version.
The recommended version was released a month ago, on 2024-01-19.

Release notes

Package name: @types/luxon

3.4.2 - 2024-01-19

3.4.1 - 2024-01-14

3.4.0 - 2024-01-05

3.3.8 - 2024-01-03

3.3.7 - 2023-12-04

3.3.6 - 2023-11-30

3.3.5 - 2023-11-21

3.3.4 - 2023-11-07

3.3.3 - 2023-10-18

3.3.2 - 2023-08-30

3.3.1 - 2023-07-20

3.3.0 - 2023-04-04

    from @types/luxon GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Fix by PR: https://github.com/percona/pmm-ui-tests/pull/802


dApp - force reload update short circuit service worker

Description
According to my comment here (includes link to W3C specification) a force-reload of the light client can lead to serious issues. Quickly rephrasing, a force-reload will bypass the service worker and loads the assets directly from the server. This means the user is getting the most recent version available on the server, no matter which version was running before. The user probably does not recognize this in first place. There is no notification about an update or anything else. Anyway, as soon as the user closes the tab where he force-reloaded the client and then load the client later again, it will load the former "old" version again as usual. This is because our service worker will always serve the locally available version if the user does not manually trigger the update. Though the force-reload short circuit the service worker and its cache storage, it will keep the cache intact (which the "old" version). In result the user was using the new version for a temporally time frame.
There can be a couple of serious issues because of that. Two obvious ones are the contracts version and the database version. For the first case, the user will load a new version of the client that is linked to a new version of contracts. He will be confused because his old channels are not there anymore. But maybe he doesn't even recognize this and just blindly follows the quick pay or similar. Anyway, when he returns to the old version he also gets back his old channels. This leads to a lot of confusion and frustration, spending unnecessary many for gas costs etc.
The second issue is about the database scheme version of the SDK to persist the client data. New versions of the client can include a new version of the database scheme. The SDK will automatically migrate the old data to the new scheme. But if the user gets back to the old version from his short trip to the new version, the SDK will fail to load the data from the new scheme it does not know about yet. The exact implications are to be cleared, though it is probably clear that the user will not be able to access his channels anymore.
In my opinion there are two strategies to handle such a situation: either ensure a force-reload performs a full mature update or prevent the update. Both approaches come with the challenge how to detect it. I can only repeat myself: what we do here is not a common thing and we have to fight against the current.
Acceptance criteria

decide on strategy to solve the problem
figure out how to detect this issue in the application
implement handling of issue
establish end-to-end tests

Tasks

[ ]

We define critical as bugs that can end to loss of user's funds, and I don't think this fits, although on an edge case (user force-reloading exactly when there's an update pending), it can lead to poor UX.
Could we check the IDB directly, to see if there there's a version different/older than the one we just loaded, and either trigger a normal reload or disable Connect button until the user does?

Andre and I discussed this issue also in regards of having more issues where the browser directly loads the version from the server. We came to the conclusion that it is best to develop a generic solution that prevents this issue on a higher level. This means once the service worker as installed a local version the related version number will be persisted too. When the dApp loads, it will verify itself if it is the expected version that was installed. If not it will block the UI and resolve the issue. Andre and I figured out that it helps to unregister the current service worker and reload the tab. This is the same approach as we handle mandatory updates (when the client is broken). Just that here we just do it automatically. The user might see a quick flicker of the dApp after loading. This is very fast and should never bother the user.
This also aligns with the feedback of Kamal that the strategy must be to prevent any updates the user has not manually confirmed.


patching schedule

Is there any information about patching available? E.g. similar to the docs about it for App Service: https://docs.microsoft.com/en-us/azure/app-service/overview-patch-os-runtime

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

ID: 2f5e4798-d1ea-e82b-0459-2e268387152d
Version Independent ID: 1bb7d77d-0b97-3190-ea91-9a10a014eefc
Content: Supported versions in Azure Database for MariaDB
Content Source: articles/mariadb/concepts-supported-versions.md
Service: mariadb
GitHub Login: @ajlam
Microsoft Alias: andrela

@roelal Thanks for your feedback. I couldn't find the exact document you are looking for.
But I have found the below document which might be helpful:
https://downloads.mariadb.org/mariadb/+releases/
If this is not what you are looking for, I would recommend you to provide feedback at the feedback forum. All the feedback you share, is closely monitored by the Data Catalog Product team and implemented in future releases.
Also, Regarding service general availability, I would suggest to keep an eye on Azure updates.
Azure updates provide information about important Azure product updates, roadmap, and announcements.

We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


[Server Feature Request]: CI builds

Verified issue does not already exist?

[X] I have searched and found no existing issue

What happened?
GitHub allows for Continuous Integration builds through GitHub actions, which are free
Since most users (mainly on Windows) don't want to install npm, yarn, python, Visual Studio Code, etc. just to build the server, maybe we could consider setting up CI builds for various systems (e.g. Windows, macOS. Linux)?
What error did you receive?
No response
Where are you hosting Actual?
Locally via Yarn
What browsers are you seeing the problem on?
No response
Operating System
Windows 11

👋 Hi! Would you mind clarifying what you mean by "ci builds"? What exactly are you looking for here?
The server itself doesn't have any "builds". It's just server-side code you deploy to a server or run locally. If you're looking to use Actual by just downloading a program and running it then look here: https://actualbudget.org/download/
For folks not wanting to install yarn/node - there's always the docker option available.

Right, but all of the Docker images are only for Linux. I'm on Windows and would prefer to self-host without installing node, yarn, etc.

They should be runable on Windows too. Many people on Win use them. Did you try? If so - what problem are you experiencing with running them on Win?

Okay, it was my failure to understand how Actual is structured. I thought you could compile a standalone executable with yarn, and I was having trouble doing that. So I figured having a central place to build executables for Windows, macOS, Linux, etc. would be helpful
I'm trying it on Docker now, but still getting issues. I'll just close this issue and open a new one to track that 👍


Replace native dispatchEvent with fireEvent from react-testing-library

What:
Replace the usage of dispatchEvent with fireEvent from react-testing-library

Why:
Being consistent and I can't think of any reason why we need to keep dispatchEvent

How:
Pretty much just replacing the dispatchEvent with the equivalent of fireEvent. Bit unsure about bubbling but react-testing-library seems to take care of that.

Checklist:

[ ] Documentation N/A
[ ] Tests N/A
[x] Ready to be merged

[ ] Added myself to contributors table N/A

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Additional Tests

Now that tests for the github and transifex webhooks have been merged, I thought it was time to add tests for the rest of the classes in txgh.
@jdoconnor @st33b @zvkemp

Passing test run: https://travis-ci.org/lumoslabs/txgh/builds/103391436


Fixing compatibility issue with Ember.js

I am having some issues trying to use Transcrypt with Ember.js.
So the way the bug works is that Ember modifies the Function prototype. When this happens, the newly created cls inherits all of the attributes attached to the Function prototype. During the for (var attrib in base) loop, these inherited attributes show up. But since they were applied directly to the prototype object instead of by using defineProperty, getOwnPropertyDescriptor returns null. This then fails during the call to defineProperty, saying that the descriptor must not be null.
I know this use case is a little bit niche, but I was wondering if you would consider this fix, or if there is another way to go about resolving this. Thanks!

Hi,
Isn't it a problem that the attribute that Ember added to the prototype will not take part in Transcrypt's inheritance mechanism in this way?
I  may be overlooking something obvious here...
Kind regards
Jacques

The goal in the ember case is to create syntactic sugar like
MyClass.myObserver = (function(){
    alert('otherProp changed');
}).observes('otherProp')

So the added methods, like observes are only meant to be called on instances of functions, and not inherited by other classes. The fact that classes are also functions in JavaScript is an unintended side-effect in this case.
Also, keep in mind that this behavior has been deprecated in Ember for a long time.


How to convert keras model with custom layer to onnx model?

Hello,
Is is possible to convert follow keras model to onnx model with this tool?
The model has customized layer with "disparity" layer named.
https://github.com/yasar-rehman/SLNET/blob/master/SLNET_A_GAP_app_disp.py
While I have model conversion, met the errors.
Any clue may be help.
Thanks for developer teams.

Use set_converter function, see mask_rcnn converter for example, here

Hi, @jiafatom . Thanks for your reply.
I'll try it.

@jiafatom does this also apply for tf.keras (2.1) models? I have implemented set_converter for a custom layer (tensorflow.keras.layers.Layer), however, the converter function never gets called.

It should work. See the example above, you need call set_converter before convert_keras. Then the code will run to get_converter to get the custom converter for you. Try debug_mode=True in convert_keras to see if the log is helpful. Make sure  you write the correct layer type.

@jiafatom: I did insert a print statement in keras2onnx.funcbook.get_converter to see what op_type gets requested. There is a lot of clutter, however, I can see, that the tensorflow ops used in the custom layer are looked up but not the tf.keras custom layer itself. I have implemented the tf.keras custom layer according to this guide. I load the saved hdf5 keras model with a custom_objects dict, providing the tf.keras custom layer.
After reading the examples, I thought, that I could provide the custom layer class either as string (the same string which I used in the custom_objects dict) or as reference to set_converter. This would allow me to provide a converter implementation for the complete custom layer, not for every tf.op used in the custom layer separately.
What do I need to do in order to get the custom tf.keras layer be recognized as one unit?

I think, this behavior may actually be a bug. I opened a separate issue (#538) for further discussion.


boards: arm: stm32_min_dev: Minimal enhancements

Some minor enhancements will follow.
Signed-off-by: Ioannis Konstantelias<EMAIL_ADDRESS>

@dbkinder Do you want me to squash the commits?

OK for the docs, but curious why you removed the links to the blue/black pill boards?

They are not working anymore. I tried to find something similar but with no success.


python and tensorflow version used!

Please mention the python version and tensorflow version or any other dependencies version and how to train and run the project in detail.

Please tell which python version and tensorflow version is used?


Refactor IAP

Refactor IAP module
Tested-by: zlq on AP cluster

/gcbrun

@blackzlq Please test on both AP and standard clusters. Please don't merge untested changes.


Draft: Add and delete module

Commands for adding and deleting module, add-module and delete-module have been added
Corresponding tests have been added
ModelManager, Storage component updated to also store Module

Resolves #15 and #17

Codecov Report
Base: 66.29% // Head: 71.60% // Increases project coverage by +5.30% :tada:

Coverage data is based on head (3487f2d) compared to base (6d3fe6d).
Patch coverage: 71.83% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #60      +/-   ##
============================================
+ Coverage     66.29%   71.60%   +5.30%
- Complexity      399      479      +80
============================================
  Files            77       83       +6
  Lines          1341     1472     +131
  Branches        144      160      +16
============================================
+ Hits            889     1054     +165
+ Misses          420      375      -45
- Partials         32       43      +11

Impacted Files
Coverage Δ

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

...du/address/logic/commands/DeleteModuleCommand.java
0.00% <0.00%> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
84.21% <0.00%> (-15.79%)
:arrow_down:

...ddress/logic/parser/DeleteModuleCommandParser.java
0.00% <0.00%> (ø)

...c/main/java/seedu/address/model/module/Module.java
68.88% <58.33%> (+68.88%)
:arrow_up:

...rc/main/java/seedu/address/model/ModelManager.java
93.33% <71.42%> (-6.67%)
:arrow_down:

...n/java/seedu/address/model/module/ModuleTitle.java
71.42% <71.42%> (ø)

src/main/java/seedu/address/model/AddressBook.java
88.57% <81.81%> (-3.10%)
:arrow_down:

...in/java/seedu/address/model/module/ModuleCode.java
80.00% <85.71%> (+80.00%)
:arrow_up:

...seedu/address/logic/commands/AddModuleCommand.java
100.00% <100.00%> (ø)

... and 12 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


/hello/: Design fixes.

This is a couple design fixes for the /hello/ page to polish it.

Merged, thanks @brockwhittaker!


Create publish.yml

This GitHub Action builds wheels and sdists and pushes them to GitHub's releases page and PyPI.
All you have to do is go to New Release,
fill in a version tag like "v0.1.1", click Publish, and a couple minutes later the .whl and .tar.gz
will be up on Releases and on PyPI.
To get PyPI working, get a PyPI token, give it to GitHub here named PYPI_TOKEN.
To get a feel for it, you can see examples of how this looks in practice at

https://github.com/ivadomed/ivadomed/actions/workflows/publish_package.yml

And the kinds of outputs it makes at

https://github.com/ivadomed/ivadomed/releases/
https://pypi.org/project/ivadomed/#history

Hopefully this makes https://github.com/voxelmorph/voxelmorph/issues/321#issuecomment-863610833 easier! It would help us out too, because then we could build on your work in voxelmorph.


[help] install wechaty and its types

Description
A question about typescript, I notice wechaty has generated index.d.ts. How to add it in my project?
wechaty is installed via npm.
npm install wechaty

The latest version in npmjs.org is v0.6.21.
After referencing the index.d.ts in typings.json, I would like to use wechaty in such way.

Currently, it is imported like a usual module.
const {
  Wechaty
  , Config
  , log
} = require('wechaty');

Project Repo
https://github.com/Samurais/wechaty-vessel

@imzc


Find function does not stop testing ports

This is a problem I found while using https://www.npmjs.com/package/proxy-chain.
Explanation
The proxy-chain module has a function to create a proxy server using a random open port, it finds the port using portastic. One of the ports that was tested gave an error and my PC would freeze for a few seconds after making the proxy server.

I am not sure why my PC freezes, but it is a result of the rejection.
The rejection comes from portastic. It would reject on errors that would occure when opening a server. It rejects after the proxy server is made, so something was messing things up in the background while the server was working fine.
The rejection comes from https://github.com/alanhoff/node-portastic/blob/d27c7d4d5c2eee620aff5e5f7804c28c78848ff0/lib/portastic.js#L37 and / or https://github.com/alanhoff/node-portastic/blob/d27c7d4d5c2eee620aff5e5f7804c28c78848ff0/lib/portastic.js#L53
The rejection is fine, it is just because it is not caught. But when using the find function all exceptions should be caught anyway. I don't change that in this pull request, because I don't think it is that big of a problem.
The biggest issue, and the reason for this pull request, is that the find function does not cancel when it finds the asked amount of open ports. Proxy-chain tells portastic to find a single open port in the range 20000 to 60000, but portastic fails to stop testing ports / cancel the promise.
I have replaced it with a recursive function, that way it is easier to control when the find function should stop, and actually make it stop.
Replicate
To replicate the problem use the following code:
process.env.DEBUG = 'portastic:*';

const portastic = require('portastic');

const opts = {
    min: 20000,
    max: 60000,
    retrieve: 1
};

console.log(opts);

portastic.find(opts).then(function (ports) {
    console.log(ports);
});

It will find the first open port and resolve the promise, but it will keep testing. See the image below for the debug log:

With my fix:

This is related to https://github.com/alanhoff/node-portastic/issues/9

Coverage increased (+0.5%) to 87.097% when pulling 473eec1645068ea54ed3bf4f77e21fc918a57731 on Nicklason:master into d27c7d4d5c2eee620aff5e5f7804c28c78848ff0 on alanhoff:master.

Coverage increased (+0.5%) to 87.097% when pulling 473eec1645068ea54ed3bf4f77e21fc918a57731 on Nicklason:master into d27c7d4d5c2eee620aff5e5f7804c28c78848ff0 on alanhoff:master.

Great job, thanks for that! Any chance to merge this soon?

It was last updated 4 years ago, I doubt it will be merged any time soon.
A different thing I noticed is that the node_modules folder is published in the module on npm. So when it does get merged, hopefully the folder won’t be published aswell.

Omg! This would be awesome! Didn't even know this PR existed, this annoying error is spamming my log from the dawn of time.


open pdf from url

Thank you for submitting an issue to jsPDF. Please read carefully.
Are you using the latest version of jsPDF?
yes
Have you tried using jspdf.debug.js?
yes
Steps to reproduce
I have an iframe which i load a site in to it.
and i use jsPdf to for export the content of that iframe, and as expected i get "Cross origin" exception.
here is my code
exportPdf() {
        let data = this.frame.innerHTML;
        var doc = new jsPDF();
        doc.text(20, 20, data);
        doc.save('Test.pdf');
    }

is there any way to tell jsPdf to load pdf from URL?

Well. What is the issue? Are you loading from the same site? If not, than Cross Origin Security Exception is raised correct because loading binary data from an unknown source into the javascript sandbox is expected as dangerous.

@MrRio
due to no participation this issue should be closed.


Async and Reducer Tests

Added async tests for increment, decrement, and destrory for both on success and on fail
Added .catch for increment, decrement, and destroy

Dispatched 'createTopicFailure' as a placeholder

Added reducer tests for all reducer cases
Added 'error' key on state to manage error messages

Issue #241

:+1: for this
thanks @colinlmcdonald


Expose admin endpoint to backup DB

consider exposing admin or api endpoint to stream bolt db contents
https://github.com/boltdb/bolt#database-backups

I've put quite a bit of thought into how to implement this over the course of the build, but want to get a better idea of how other users would expect this to be done.
Currently, you can just cp the .db files and push those out to a backup machine or storage endpoint. But, I haven't tested it on any database of significant size (over 100MB or so).
There are a couple of ways I have considered this, but all have trade-offs in security, management/maintenance, or complexity. All of the following would implement the Bolt io.Writer approach:

hardcode endpoint with basic auth

would allow easy programmatic remote backup

hardcode endpoint with JWT/cookie auth (like /admin/* route auth)

all admin users could download in browser, or get their cookie and pass it in curl/wget or similar
also fairly easy remote backup, but JWT/cookie expire and would need to be renewed

run-time generated endpoint (pseudo-random) displayed in config to admin user

just obscuring/hiding the security, probably not the best idea

run-time password provided by admin user required in query string or form value of backup request

remote backups would need to hardcode password in routine, also not ideal

Any thoughts on these or other implementations?
p.s. since all routes are registered to the DefaultServeMux using just the stdlib net/http package, you can add any routes with custom handlers as long as they don't conflict with existing ones. These could be added in any package (content, addons, admin, etc)

I like option 1 best - I just want to curl and download on a cron job

@bketelsen - I have most of this implemented now as per option 1. The way into works is there is one new route registered at '/admin/backup' that requires a query string:
'?source={system,analytics,uploads}'
Unfortunately I ran out of time before I'm now traveling back to LA, so I can't wrap up and push until later tonight. Just wanted to let you know it's almost there to save you time implementing it yourself in case you were thinking about it.

@bketelsen - this has been pushed to master. just adding a new release and will then close this issue.

Thanks for this!

Documentation for backups is here: https://github.com/ponzu-cms/ponzu/wiki/Backups in case anyone finds this issue via search while looking for Ponzu backup info.


Basic update of package.json

Updated repository name and some dependencies.
There are still vulnerabilities (see https://stackoverflow.com/questions/68333071/how-to-solve-this-npm-glob-parent-problem if you want to tackle them), and npm run test does not work. But the basic installation should work now, and the actual tools that I tried out seemed to work as well.

Since packages have been updated could you regenerate ThirdParty.json?

This was only an attempt to quickly get this to a state where compiling and certain parts of the tools can be used. I'll try to look closer into this (test failure, check of optimizeGlb, update of ThirdParty.json...) soon.

I have pinned gltf-pipeline to a 1.x version, and updated ThirdParty.json.
The build is still failing, and the tests cannot be run, but I consider this as part of https://github.com/CesiumGS/3d-tiles-validator/issues/7 and the task to integrate the currently open branches.


Update DynamoDBContext api/documentation/examples to include Async methods

Currently there is no code examples around DynamoDBContext's Async methods. Our team is working with .NET Core 2 and it's been difficult to find examples/documentation on how to use Async methods.
After trying different things, we got ScanAsync method working.
public ProjectController(IAmazonDynamoDB dynamoDbClient)
        {
            _dynamoDbClient = dynamoDbClient;
        }
        public async Task<IActionResult> Index()
        {
            var context = new DynamoDBContext(_dynamoDbClient);
            var conditions = new List<ScanCondition>();
            var project = context.ScanAsync<ProjectModel>(conditions);

            while (!project.IsDone)
            {
                var result = await project.GetNextSetAsync();
// do something with result
            }
            return View();
        }

Our team would like to provide examples or update documentation but need to know where to add these examples. Thanks.

The following are some locations that contain examples of asynchronous .NET applications that use the DynamoDB service.

DynamoDB examples in the AWS Code Examples Repository.
.NET and DynamoDB in the Amazon DynamoDB Developer Guide


[BUG] Use wire aliases for ACF2 compatibility

Wiremod has i/o aliasing so that renamed wire ports can still function with old dupes.

Example,
WireLib.AddInputAlias( "Zoom", "FOV" )
WireLib.AddOutputAlias( "XYZ", "HitPos" )

Ah wow they coded that really weird. Here's how ACF would use it
WireLib.AddInputAlias( "acf_ammo", "Active", "Load" )

Also, question. What is the Output  of acf_ammo for? I can't find what it is used for.

Wasn't aware of this WireLib function, let me add it for the inputs that were just renamed. Output [VECTOR] is just a debug output Steve is using as a helper for the stuff he's doing with the entity hitboxes. It's gonna be removed once that work is done.

Sounds good, thanks!

There's also WireLib.AddOutputAlias, gonna be using it once we readd the AmmoCount output to guns. Sadly, we won't be able to do the same with Ready since it was replaced with Status [STRING].

Fixed on a7bd507afe0f61df21daa96097e4c0e4179b55f3.


Optimize instances queries

Due to #122 , we cannot use the pagination in an effective way, and thus the instances page become heavier with the number of instances.
This issue is about optimizing that view once the mentioned issue is fixed.

@joaquimrocha this is fixed

ref #173

Thanks. Closed.


Job submit plugin page with Group NAS

Implement MountDirectories for job submit page. User can pick group settings to use mount info.

Show all user usable group settings

Apply group mount info when group selected. Can select multiple groups, merge groups mount info.

Done. The code is merged to PAI 0.14.0 job submission page.


UI improvements for one-shot mode (--disconnect-after-job)

I'm using buildkite-agent with --disconnect-after-job for containerization reasons, running all of buildkite-agent under sandbox-exec or docker. In this scenario, the WebUI always reports at most one job per agent, as apparently reconnecting the agent (which I do after every job) results in a new agent ID.
For example, every idle agent reports:

... while an active agent will only report a single job, i.e., the one it's currently running:

This is not great, as it complicates debugging worker issues, with no easy way to inspect all runs by this agent.
I'd be happy to have to specify my own UID for this, so that the WebUI can correctly group runs.

Hi @maleadt, thanks for raising the issue.
I'm not sure what we're able to do about this, however: if an agent is started in an ephemeral environment, it's not clear to me how we'd be able to link it to agents that ran in previous ephemeral environments.

Unless set, the hostname that the OS reports to the agent probably varies between Docker containers. (If the hostname is set to some fixed name, that's a whiff of non-ephemerality).
The underlying node running a particular string of executions might change in an environment like Kubernetes, and might not be exposed inside the container.
Each agent registration token is designed to be used for multiple agents, whether they are in parallel or in serial one-shot runs.

maybe tags would work as a way to define groupings?

No easily; in our case we have many workers with identical tags, and I wanted to use the CI to debug a specific worker's inability to complete jobs (after an OS upgrade broke it). So grouping according to tags, while useful in some cases, wouldn't have helped me.
I'd be fine with fixing the container's hostname, or specify anything else to indicate to the agent that different ephemeral environments should map onto a single one. In my case, we have a single systemd service for each agent we launch on a host, e.g<EMAIL_ADDRESS>That service basically launches buildkite-agent --disconnect-after-job in a while loop, under Docker for containerization, so that'd be a straightforward place to add --agent-id=$HOST.$AGENT
That could of course be implemented using tags by adding an "artificial" agent=$HOST.AGENT tag, but that feels a little off.


InvalidArgumentError (see above for traceback): indices[6,4] = 23624 is not in [0, 23624)

I get the following error after running an embedding layer as;
Embedding(23624, 50, input_length=5, trainable=False)

InvalidArgumentError (see above for traceback): indices[6,4] = 23624 is not in [0, 23624)
[[Node: embedding_1/embedding_lookup = Gather[Tindices=DT_INT32, Tparams=DT_FLOAT, _class=["loc:@embedding_1/embeddings"], validate_indices=true, _device="/job:localhost/replica:0/task:0/device:CPU:0"](embedding_1/embeddings/read, embedding_1/Cast)]]

Each datapoint here is a number(index). Upon checking indices[6,4] I found the following
print(ar_train_data[6,4])
5088

ar_train_data is an array of shape (162896, 5) where each value is  between [0, 23624).
The training stops towards the end of the first epoch with the error above.
Am amazed! 5088 is no where out of range for [0, 23624).  Can anyone suggest what could be the issue here?
Please suggest if additional code snippets are required for clarity.
The model roughly goes below as:
inputs =  Input(shape=(None,),dtype='float32')
               <Embedding layer>
               <Convolution layer>
linear_output = Dense(10,input_shape=(72,),activation='relu')(linear_input)

model = Model(inputs=[inputs],outputs=[linear_output])
model.compile(loss='categorical_crossentropy', optimizer='nadam')

Keras version - 2.2.4
tensorflow version: 1.5.0
Regards

Please refer to my answer here:
https://stackoverflow.com/questions/56890244/invalidargumenterror-see-above-for-traceback-indices47-6-24-is-not-in-0/57834436#57834436


SNARK Trusted Setup #51

The comparison chart between SNARK / STARK / Bullet suggests that SNARK's require a trusted setup, but this is no longer true with proving systems like Halo.

https://www.reddit.com/r/Monero/comments/uh4xd2/sethforprivacy_proposes_exploring_trustless/
please reference this linke.


SYN-3798: add lastRunAt and lastRunStatus to GET /tests/ response

I have read the CLA Document and I hereby sign the CLA

I have read the Code of Conduct and I hereby accept the Terms


Full of issues On laravel 5.6

ISSUES LIST

[ ] Logger problem
[ ] Provider problem
[ ] Readme.md problem
[ ] Migration problem

I'm waiting for v4 of this that will support php7 i test that on dev mode but has problem too

Version 3.3.0 should have fixed most of those issues. But, could you, please, be more specific?


Port 80 and 443

Can I use Kestrel with port 80 and 443 and access it from remote computers on Windows 10?
My networking knowledge isn't what it should be.
http://stackoverflow.com/questions/34212765/how-do-i-get-the-kestrel-web-server-to-listen-to-non-localhost-requests was helpful, but netsh http add iplisten ipaddress=::80 didn't open up that port.
I also attempted to add a Firewall setting. http://stackoverflow.com/questions/7363470/windows-server-2008-r2-cant-get-apache-to-run-on-port-80
var host = new WebHostBuilder()
				.UseUrls("http://*:80", "https://*:443")
				.UseKestrel(options =>
				{
					options.NoDelay = true;
					options.UseHttps(testCertPath, configuration["pfxPassword"]);
					options.UseConnectionLogging();
				})
				.UseContentRoot(Directory.GetCurrentDirectory())
				.UseStartup<Startup>()
				.Build();
			host.Run();

You need to remove all the netsh entries and disable IIS if you want Kestrel to listen on those ports. Kestrel doesn't use netsh/http.sys and can't share ports with it.

The recommended way is however to run Kestrel behind a proxy e.g. IIS or nginx

Thanks and understood that IIS is recommended, I'm running this as an internal app, so I'm avoiding having to install the extra dependency.
@Tratcher does that include uninstalling IIS Express?

No, Express doesn't use those ports.


Fix CI after migration to Hyperledger Labs

Seems like CircleCI stopped working since migration to Hyperledger Labs. Pull requests, at least, do not go through CI.

I have finished the configuration:
https://circleci.com/gh/hyperledger-labs/minbft
The build status badge in the README is updated in #22.
I will close this issue after #22 is merged.

NB. https://help.github.com/articles/closing-issues-using-keywords/


MacOS client - black screen on resume

Bug description:

When resuming from sleep the client does not always recover, and a force quit is required.
Steps to reproduce:

Setup

Dual monitor setup (may exist with single monitor setup)
Ferdi Maximized (full screen)

Steps to reproduce

Machine allowed to sleep
Wakeup machine, all apps recover, except for Ferdi which stays as an "open desktop session, but is now all blacked out"

Expected behavior

Upon system resume ferdi resumes
Screenshots

Environment:

Operating System: macOS Big Sur 11.6

Ferdi Version: 5.6.2

Server: Ferdi

Debug information:

{"host":{"platform":"darwin","release":"20.6.0","screens":[{"id":1,"bounds":{"x":0,"y":0,"width":1440,"height":900},"workArea":{"x":0,"y":0,"width":1440,"height":900},"accelerometerSupport":"unknown","monochrome":false,"colorDepth":30,"colorSpace":"{primaries:BT709, transfer:IEC61966_2_1_HDR, matrix:RGB, range:FULL}","depthPerComponent":10,"size":{"width":1440,"height":900},"displayFrequency":59,"workAreaSize":{"width":1440,"height":900},"scaleFactor":2,"rotation":0,"internal":true,"touchSupport":"unknown"},{"id":2,"bounds":{"x":1440,"y":0,"width":1920,"height":1080},"workArea":{"x":1440,"y":0,"width":1920,"height":1080},"accelerometerSupport":"unknown","monochrome":false,"colorDepth":24,"colorSpace":"{primaries_d50_referred: [[0.6592, 0.3295],  [0.2474, 0.6720],  [0.1539, 0.0579]], transfer:BT709_APPLE, matrix:RGB, range:FULL}","depthPerComponent":8,"size":{"width":1920,"height":1080},"displayFrequency":59,"workAreaSize":{"width":1920,"height":1080},"scaleFactor":1,"rotation":0,"internal":false,"touchSupport":"unknown"}]},"ferdi":{"version":"5.6.2","electron":"13.3.0","installedRecipes":[{"id":"franz-custom-website","version":"1.1.0"},{"id":"gmail","version":"1.4.1"},{"id":"googlekeep","version":"1.1.0"},{"id":"linkedin","version":"1.2.1"},{"id":"msteams","version":"3.1.4"},{"id":"office365-owa","version":"1.4.5"},{"id":"slack","version":"1.3.0"},{"id":"telegram","version":"3.2.1"},{"id":"whatsapp","version":"3.3.2"},{"id":"youtubemusic","version":"1.1.0"},{}],"devRecipes":[],"services":[{"id":"8aae8678-fb52-48dc-8ce4-20a0944db271","recipe":"googlekeep","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"23a469b3-f1e0-4166-a820-0cdf249f93fe","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"94d8d9ed-a667-4c4c-80ec-c87bed4de47d","recipe":"msteams","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"8fe4b30c-2fcf-4cb8-8936-1993cc408cfa","recipe":"youtubemusic","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"6af88fee-2402-4627-be95-f614c5614b64","recipe":"whatsapp","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"df93898a-51b5-4d08-b9e7-22a25a081711","recipe":"telegram","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"b6d2144a-4511-4aa3-8b9e-598a4ca9dc45","recipe":"office365-owa","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"6aa1b9a9-8a05-4326-b5ad-31b564e53643","recipe":"gmail","isAttached":false,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"82a077f4-8180-4eea-bed5-00abeb9c0319","recipe":"gmail","isAttached":false,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"ed84c5e8-9bf5-4e45-bfc9-bb3f8b218d1e","recipe":"gmail","isAttached":false,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"d7058078-7727-402e-bb30-dbb8bfbe1bbc","recipe":"gmail","isAttached":false,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"3aefae0c-740d-4ae0-9d54-418ab3881e5c","recipe":"slack","isAttached":true,"isActive":true,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"d8e28adf-a8e7-4154-b723-7a63b492442e","recipe":"linkedin","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false}],"messages":[{"type":"error","info":["error","Warning: Failed prop type: Invalid prop actions.service of type Object supplied to _class2, expected instance of _class.\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by RouterContext)\n    in RouterContext (created by Router)\n    in Router (created by _class)\n    in _class (created by inject-_class-with-stores-actions)\n    in inject-_class-with-stores-actions\n    in IntlProvider (created by _class)\n    in _class (created by inject-_class-with-stores)\n    in inject-_class-with-stores\n    in Provider"]},{"type":"error","info":["error","Warning: Failed prop type: Invalid prop actions.settings of type Object supplied to _class2, expected instance of _class.\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by _class2)\n    in div (created by _class2)\n    in div (created by _class2)\n    in _class2 (created by Jss(_class2))\n    in Jss(_class2) (created by _class2)\n    in _class2 (created by Jss(_class2))\n    in Jss(_class2) (created by _class2)\n    in ThemeProvider (created by _class2)\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by RouterContext)\n    in RouterContext (created by Router)\n    in Router (created by _class)\n    in _class (created by inject-_class-with-stores-actions)\n    in inject-_class-with-stores-actions\n    in IntlProvider (created by _class)\n    in _class (created by inject-_class-with-stores)\n    in inject-_class-with-stores\n    in Provider"]},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"getInfo"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"features"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"all"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","info":["error",{"errno":-2,"syscall":"open","code":"ENOENT","path":"/Users/richard/Library/Application Support/Ferdi/recipes/temp/freshservice/package.json"}]},{"type":"error","info":["error",{"errno":-2,"syscall":"open","code":"ENOENT","path":"/Users/richard/Library/Application Support/Ferdi/recipes/temp/plex/package.json"}]}],"workspaces":[{"id":"f2832704-7b8e-42fb-9ba5-c71a1824d6af","services":["8aae8678-fb52-48dc-8ce4-20a0944db271","8fe4b30c-2fcf-4cb8-8936-1993cc408cfa","6af88fee-2402-4627-be95-f614c5614b64","df93898a-51b5-4d08-b9e7-22a25a081711","d8e28adf-a8e7-4154-b723-7a63b492442e","6aa1b9a9-8a05-4326-b5ad-31b564e53643","82a077f4-8180-4eea-bed5-00abeb9c0319","ed84c5e8-9bf5-4e45-bfc9-bb3f8b218d1e","d7058078-7727-402e-bb30-dbb8bfbe1bbc"]},{"id":"7d7949c7-ce1e-4802-82c6-8399899a9d1e","services":["8aae8678-fb52-48dc-8ce4-20a0944db271","8fe4b30c-2fcf-4cb8-8936-1993cc408cfa","6af88fee-2402-4627-be95-f614c5614b64","b6d2144a-4511-4aa3-8b9e-598a4ca9dc45","d8e28adf-a8e7-4154-b723-7a63b492442e","3aefae0c-740d-4ae0-9d54-418ab3881e5c","23a469b3-f1e0-4166-a820-0cdf249f93fe","df93898a-51b5-4d08-b9e7-22a25a081711","94d8d9ed-a667-4c4c-80ec-c87bed4de47d"]}],"windowSettings":{"width":1440,"height":875,"x":1640,"y":61,"displayBounds":{"x":1440,"y":0,"width":1920,"height":1080},"isMaximized":true,"isFullScreen":true},"settings":{"autoLaunchInBackground":false,"runInBackground":true,"reloadAfterResume":true,"enableSystemTray":true,"startMinimized":false,"confirmOnQuit":false,"minimizeToSystemTray":false,"closeToSystemTray":false,"privateNotifications":false,"clipboardNotifications":true,"notifyTaskBarOnMessage":true,"showDisabledServices":false,"showMessageBadgeWhenMuted":true,"showDragArea":false,"enableSpellchecking":true,"spellcheckerLanguage":"en-us","darkMode":true,"locale":"en-US","fallbackLocale":"en-US","beta":false,"isAppMuted":false,"enableGPUAcceleration":false,"server":"https://api.getferdi.com","predefinedTodoServer":"https://app.franztodos.com","autohideMenuBar":false,"lockingFeatureEnabled":false,"locked":false,"lockedPassword":"******","useTouchIdToUnlock":true,"scheduledDNDEnabled":false,"scheduledDNDStart":"17:00","scheduledDNDEnd":"09:00","hibernateOnStartup":true,"hibernationStrategy":300,"wakeUpStrategy":300,"inactivityLock":0,"automaticUpdates":true,"showServiceNavigationBar":false,"universalDarkMode":false,"userAgentPref":"","adaptableDarkMode":true,"accentColor":"#FF5555","serviceRibbonWidth":45,"iconSize":30,"sentry":false,"nightly":false,"navigationBarBehaviour":"never","searchEngine":"duckDuckGo","useVerticalStyle":false,"alwaysShowWorkspaces":false,"liftSingleInstanceLock":false,"serviceLimit":5,"hibernate":false,"todoServer":"isUsingCustomTodoService","customTodoServer":""},"features":{"isServiceProxyEnabled":true,"isWorkspaceEnabled":true,"isTodosEnabled":true,"isSettingsWSEnabled":false},"user":"82c1cf9d-ab58-4da2-b55e-aaa41d2142d8"}}

Debug info in failed state:
{"host":{"platform":"darwin","release":"20.6.0","screens":[{"id":1,"bounds":{"x":0,"y":0,"width":1280,"height":800},"workArea":{"x":0,"y":0,"width":1280,"height":800},"accelerometerSupport":"unknown","monochrome":false,"colorDepth":30,"colorSpace":"{primaries:BT709, transfer:IEC61966_2_1_HDR, matrix:RGB, range:FULL}","depthPerComponent":10,"size":{"width":1280,"height":800},"displayFrequency":59,"workAreaSize":{"width":1280,"height":800},"scaleFactor":2,"rotation":0,"internal":true,"touchSupport":"unknown"}]},"ferdi":{"version":"5.6.2","electron":"13.3.0","installedRecipes":[{"id":"franz-custom-website","version":"1.1.0"},{"id":"gmail","version":"1.4.1"},{"id":"googlekeep","version":"1.1.0"},{"id":"linkedin","version":"1.2.1"},{"id":"msteams","version":"3.1.4"},{"id":"office365-owa","version":"1.4.5"},{"id":"slack","version":"1.3.0"},{"id":"telegram","version":"3.2.1"},{"id":"whatsapp","version":"3.3.2"},{"id":"youtubemusic","version":"1.1.0"},{}],"devRecipes":[],"services":[{"id":"8aae8678-fb52-48dc-8ce4-20a0944db271","recipe":"googlekeep","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"23a469b3-f1e0-4166-a820-0cdf249f93fe","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"94d8d9ed-a667-4c4c-80ec-c87bed4de47d","recipe":"msteams","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"8fe4b30c-2fcf-4cb8-8936-1993cc408cfa","recipe":"youtubemusic","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"6af88fee-2402-4627-be95-f614c5614b64","recipe":"whatsapp","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"df93898a-51b5-4d08-b9e7-22a25a081711","recipe":"telegram","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"b6d2144a-4511-4aa3-8b9e-598a4ca9dc45","recipe":"office365-owa","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"6aa1b9a9-8a05-4326-b5ad-31b564e53643","recipe":"gmail","isAttached":false,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"82a077f4-8180-4eea-bed5-00abeb9c0319","recipe":"gmail","isAttached":false,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"ed84c5e8-9bf5-4e45-bfc9-bb3f8b218d1e","recipe":"gmail","isAttached":false,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"d7058078-7727-402e-bb30-dbb8bfbe1bbc","recipe":"gmail","isAttached":false,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"3aefae0c-740d-4ae0-9d54-418ab3881e5c","recipe":"slack","isAttached":true,"isActive":true,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"d8e28adf-a8e7-4154-b723-7a63b492442e","recipe":"linkedin","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false}],"messages":[{"type":"error","info":["error","Warning: Failed prop type: Invalid prop actions.service of type Object supplied to _class2, expected instance of _class.\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by RouterContext)\n    in RouterContext (created by Router)\n    in Router (created by _class)\n    in _class (created by inject-_class-with-stores-actions)\n    in inject-_class-with-stores-actions\n    in IntlProvider (created by _class)\n    in _class (created by inject-_class-with-stores)\n    in inject-_class-with-stores\n    in Provider"]},{"type":"error","info":["error","Warning: Failed prop type: Invalid prop actions.settings of type Object supplied to _class2, expected instance of _class.\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by _class2)\n    in div (created by _class2)\n    in div (created by _class2)\n    in _class2 (created by Jss(_class2))\n    in Jss(_class2) (created by _class2)\n    in _class2 (created by Jss(_class2))\n    in Jss(_class2) (created by _class2)\n    in ThemeProvider (created by _class2)\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by RouterContext)\n    in RouterContext (created by Router)\n    in Router (created by _class)\n    in _class (created by inject-_class-with-stores-actions)\n    in inject-_class-with-stores-actions\n    in IntlProvider (created by _class)\n    in _class (created by inject-_class-with-stores)\n    in inject-_class-with-stores\n    in Provider"]},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"getInfo"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"features"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"all"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","info":["error",{"errno":-2,"syscall":"open","code":"ENOENT","path":"/Users/richard/Library/Application Support/Ferdi/recipes/temp/plex/package.json"}]},{"type":"error","info":["error",{"errno":-2,"syscall":"open","code":"ENOENT","path":"/Users/richard/Library/Application Support/Ferdi/recipes/temp/freshservice/package.json"}]},{"type":"log","info":["log","Hogs group",{"tag":"27718961346-1407825356@g.us","renotify":true,"dir":"auto","lang":"en","silent":true,"body":"Scott Goodbrand: 📷 Jirra, I feel lekka","icon":"https://web.whatsapp.com/pp?e=https%3A%2F%2Fpps.whatsapp.net%2Fv%2Ft61.24694-24%2F243071118_1438741789830757_8428065310403707749_n.jpg%3Fccb%3D11-4%26oh%3Daaac5fea7c056c4fe68dee43747e4ddd%26oe%3D615B2CB0&t=s&u=27718961346-1407825356%40g.us&i=1633028375&n=gSRGDwJLvwmRAD7Dajle0X4FlgVZAZS6o0SumKt0yLY%3D"}]},{"type":"log","info":["log","Hogs group",{"tag":"27718961346-1407825356@g.us","renotify":true,"dir":"auto","lang":"en","silent":true,"body":"John Butler: haha glad you alvie","icon":"https://web.whatsapp.com/pp?e=https%3A%2F%2Fpps.whatsapp.net%2Fv%2Ft61.24694-24%2F243071118_1438741789830757_8428065310403707749_n.jpg%3Fccb%3D11-4%26oh%3Daaac5fea7c056c4fe68dee43747e4ddd%26oe%3D615B2CB0&t=s&u=27718961346-1407825356%40g.us&i=1633028375&n=gSRGDwJLvwmRAD7Dajle0X4FlgVZAZS6o0SumKt0yLY%3D"}]},{"type":"log","info":["log","DSC - Team Engineering",{"tag":"27827854374-1389277779@g.us","renotify":true,"dir":"auto","lang":"en","silent":true,"body":"Nosipho Monakali: 📷 we still have overdue tickets","icon":"https://web.whatsapp.com/pp?e=https%3A%2F%2Fpps.whatsapp.net%2Fv%2Ft61.24694-24%2F56524870_314403359245642_5023416525613170688_n.jpg%3Fccb%3D11-4%26oh%3Da97437690b037d72110cb9b4f68bbfab%26oe%3D615B28E3&t=s&u=27827854374-1389277779%40g.us&i=1527149821&n=mB5i9XLHtwsfYNPcmaxgb2GfSpmUPa65mUoRil%2BwMjs%3D"}]}],"workspaces":[{"id":"f2832704-7b8e-42fb-9ba5-c71a1824d6af","services":["8aae8678-fb52-48dc-8ce4-20a0944db271","8fe4b30c-2fcf-4cb8-8936-1993cc408cfa","6af88fee-2402-4627-be95-f614c5614b64","df93898a-51b5-4d08-b9e7-22a25a081711","d8e28adf-a8e7-4154-b723-7a63b492442e","6aa1b9a9-8a05-4326-b5ad-31b564e53643","82a077f4-8180-4eea-bed5-00abeb9c0319","ed84c5e8-9bf5-4e45-bfc9-bb3f8b218d1e","d7058078-7727-402e-bb30-dbb8bfbe1bbc"]},{"id":"7d7949c7-ce1e-4802-82c6-8399899a9d1e","services":["8aae8678-fb52-48dc-8ce4-20a0944db271","8fe4b30c-2fcf-4cb8-8936-1993cc408cfa","6af88fee-2402-4627-be95-f614c5614b64","b6d2144a-4511-4aa3-8b9e-598a4ca9dc45","d8e28adf-a8e7-4154-b723-7a63b492442e","3aefae0c-740d-4ae0-9d54-418ab3881e5c","23a469b3-f1e0-4166-a820-0cdf249f93fe","df93898a-51b5-4d08-b9e7-22a25a081711","94d8d9ed-a667-4c4c-80ec-c87bed4de47d"]}],"windowSettings":{"width":800,"height":600,"x":0,"y":25,"displayBounds":{"x":0,"y":0,"width":1280,"height":800},"isMaximized":true,"isFullScreen":true},"settings":{"autoLaunchInBackground":false,"runInBackground":true,"reloadAfterResume":true,"enableSystemTray":true,"startMinimized":false,"confirmOnQuit":false,"minimizeToSystemTray":false,"closeToSystemTray":false,"privateNotifications":false,"clipboardNotifications":true,"notifyTaskBarOnMessage":true,"showDisabledServices":false,"showMessageBadgeWhenMuted":true,"showDragArea":false,"enableSpellchecking":true,"spellcheckerLanguage":"en-us","darkMode":true,"locale":"en-US","fallbackLocale":"en-US","beta":false,"isAppMuted":false,"enableGPUAcceleration":false,"server":"https://api.getferdi.com","predefinedTodoServer":"https://app.franztodos.com","autohideMenuBar":false,"lockingFeatureEnabled":false,"locked":false,"lockedPassword":"******","useTouchIdToUnlock":true,"scheduledDNDEnabled":false,"scheduledDNDStart":"17:00","scheduledDNDEnd":"09:00","hibernateOnStartup":true,"hibernationStrategy":300,"wakeUpStrategy":300,"inactivityLock":0,"automaticUpdates":true,"showServiceNavigationBar":false,"universalDarkMode":false,"userAgentPref":"","adaptableDarkMode":true,"accentColor":"#FF5555","serviceRibbonWidth":45,"iconSize":30,"sentry":false,"nightly":false,"navigationBarBehaviour":"never","searchEngine":"duckDuckGo","useVerticalStyle":false,"alwaysShowWorkspaces":false,"liftSingleInstanceLock":false,"serviceLimit":5,"hibernate":false,"todoServer":"isUsingCustomTodoService","customTodoServer":""},"features":{"isServiceProxyEnabled":true,"isWorkspaceEnabled":true,"isTodosEnabled":true,"isSettingsWSEnabled":false,"needToWaitToProceed":false,"isSpellcheckerPremiumFeature":false,"isSpellcheckerIncludedInCurrentPlan":true,"isServiceProxyIncludedInCurrentPlan":true,"isServiceProxyPremiumFeature":true,"isWorkspacePremiumFeature":false,"isAnnouncementsEnabled":true,"isServiceLimitEnabled":false,"serviceLimitCount":0,"isCommunityRecipesPremiumFeature":false,"isCommunityRecipesIncludedInCurrentPlan":true,"isCustomUrlIncludedInCurrentPlan":true,"isMagicBarEnabled":true,"isTeamManagementIncludedInCurrentPlan":true,"isTodosIncludedInCurrentPlan":true,"defaultTrialPlan":"franz-pro-yearly","subscribeURL":"https://getferdi.com","planSelectionURL":"https://getferdi.com","hasInlineCheckout":true,"isPlanSelectionEnabled":false,"isTrialStatusBarEnabled":false,"canSkipTrial":true,"pricingConfig":{"currency":"$","currencyID":"USD","plans":{"personal":{"monthly":{"id":"ferdi-free","price":0,"billed":0},"yearly":{"id":"ferdi-completely-free","price":0,"billed":0}},"pro":{"monthly":{"id":"ferdi-still-free","price":0,"billed":0},"yearly":{"id":"ferdi-forever-free","price":0,"billed":0}}}}},"user":"82c1cf9d-ab58-4da2-b55e-aaa41d2142d8"}}


How is app injected into the controllers?

good article..
Can you please clarify how app is injected into the IIFE that wraps the controller?

Such questions are appropriate for post's comments, not Github issues.


Add BlockCache

An alternative caching implementation that's intended as a replacement for BytesCache. The idea is to only ever make requests of size blocksize. At a high-level, the design is

Cache data in a Dict[int, bytes], a mapping from block number to the bytes for that chunk
When serving a fetch_range request,

determine all the blocks touched by start, end, and in between
Make actual get requests for uncached blocks
Return the requested bytes by slicing the blocks and joining

I was kicking around this idea a couple months ago when we were hitting bugs in BytesCache, which has some surprisingly complicated logic.
This implementation tries to get similar characteristics (cache reads as in-memory bytestrings).
I think the main thing to decide is whether we should have some kind of maxsize parameter to control how large this cache will get. Right now, we'll end up caching the full contents of the file if a byte has been requested from every chunk. We could cap that somehow, and evict blocks based on some strategy (least recently used, used the least number of times, etc.)
cc @martindurant if you have a chance to look, though not a priority. I need to do some performance testing / profiling.

Definitely I think this should be done as a LRU cache rather than storing everything; otherwise a good idea.
One possible improvement: when you are fetching more than one contiguous block, would be good to combine the calls, because often it's the total number of fetch calls which is the limiting factor. This is also true for for the CachingFileSystem (which has protocol "blockcache", which could be confusing).
I previously commented that ReadaheadCache might be the best default, what do you think?

I previously commented that ReadaheadCache might be the best default, what do you think?

Just glanced through it. It also seems like a reasonable alternative.
I suppose the main difference is BlockCache would be better for read patterns where you go back to an earlier block?
._fetch(10, 20)
._fetch(20, 30)
._fetch(10, 15)  # in cache

I think third ._fetch would have been a fresh request for ReadAheadCache, and not loaded from cache? So if we expect mostly-sequential reads, then ReadAheadCache is probably the way to go as it's simpler than this BlockCache.

Correct: block cache would be good when you repeatedly access some parts of a file in a random-access pattern; readahead cache for when you are reading mostly serially through the file.
For your example, the third fetch might also hit the cache for the right block-size. For a size of 5, say, you would indeed need to read from remote again.

Refactored to use an LRU cache for getting / setting blocks. Things are more complicated now, and I don't see an easy way to do this LRU caching with the optimization that multi-block fetches be done in a single call.

So our choice is between

Use ReadAheadCache:

pros: simpler, better for large requests
cons: worse for repeated reads, when we're jumping around the file "a bit"

Use BlockCache:

pros: better for repeated reads with jumps
cons: probably more complicated, worse for multi-block requests. Choosing the right maxblocks isn't straightforward.

It's hard for me to know what is better in the abstract :/

Right, so of course it works out workload-dependent, and most users will not expect to have to read the docstrings to work out what's the best for them. I am marginally for read-ahead, because it's easy to understand. The current BytesCache is somewhere between these two, but too complex.

See https://github.com/intake/filesystem_spec/pull/193 for changing the default to readahead. I think that's the right choice for now.
BlockCache may be useful, but isn't a priority right now.

So long as it makes it into the docs, so we can point people to it.

OK, going to merge this in so that we can experiment easily on different workloads. I have a followup PR coming with docs and a reorg.


add a check to ensure QUERY_STRING actually exists in dictionary

A possible fix for a missing QUERY_STRING when using gunicorn

I'm going to merge this in as-is.
A test case to ensure that we don't regress this might not be a bad idea too, but I don't see any reason we shouldn't start off by merging this.
Thank you!

thought i'd get the change in there first, looking at adding a test case, just wasn't sure where to go about it yet.

Probably in test_http, at the bottom. Doesn't really fit in with anything else.

On second thoughts a better way to handle this would be to have our test client omit QUERY_STRING from the WSGI environ when no query string is present.

Followed up in #56 - thanks for highlighting this!


Automate screenshot taking for documentation

To reduce manual updating the screenshots of the webapp and the PWA should be produced automatically on build.
Example library:
https://www.npmjs.com/package/capture-website

Use:
https://github.com/berntpopp/screen-scout


Certificates management

Certificates have to be set at platform / stack deployment, and have to be renewed on a regular basis, or replaced in case of a security issue.

Certificates are deployed as Docker secret, and linked to services that need them.
Docker secrets:

can't be updated
can't be removed as long as a service is using them

Certificates are created with certbot (which has a feature to renew certificates) in standalone mode on one server (nothing is listening on port 443 at that moment), but it's not clear how we can trigger a renewal of a certificate from there, and they expire after 90 days.

What should be the process to easily renew certificates and apply them on the cluster?

Taken from the certificate.md file as it will be removed.
Certificate management for AMP
For local deployment, amp will generate a self signed certificate. You'll have to accept it when you connect the first time to the services on local.appcelerator.io.
For remote deployment, if you want to use a valid DNS domain, you can upload a certificate on the Swarm to enable TLS flows.
If your domain is cloud.mydomain.net, the certificate should be signed for cloud.mydomain.net, dashboard.cloud.mydomain.net, gw.cloud.mydomain.net, examples.cloud.mydomain.net and service.cloud.domain.net. If you can get a wildcard certificate, it's even better.
As an admin user of the platform, you can replace the certificate in the swarm. For that, prepare the secret as a pem file (includind the private key, the certificate, and the certificate chain), create a new Docker secret in the swarm, and update the amp_proxy service to mount it as /run/secrets/certN.pem, with N = 1 to 9.
amp secret create amp_certificate_$(date +%Y%m%d)
amp service update --secret-add amp_certificate_$(date +%Y%m%d) amp_proxy
amp service update --secret-rm amp_certificate_old_one amp_proxy


Set up CI with Azure Pipelines

[skip ci]
Summary
Describe your changes here.
Fixes #Issue_Number, dotnet/docs#Issue_Number or dotnet/dotnet-api-docs#Issue_Number (if available)

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

I'm not sure we want to add Azure pipelines when we already have build validation with GitHub actions.
See: https://github.com/dotnet/samples/blob/master/.github/workflows/build-validation.yml
Tagging @BillWagner and @adegeo

Closing this PR: if you have an idea on how to improve the repo, open an issue for discussion and then we can follow up on a PR.


⚠ SceneTime has degraded performance

In 3cd9421, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1496 ms

Resolved: SceneTime performance has improved in 7e18259 after 8 minutes.


⚠ Bofrost.be has degraded performance

In 9c82200, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1045 ms

Resolved: Bofrost.be performance has improved in 6c6f51b.


Include notification interval (converted to days) in SNS notifications

Updates the SNS notification format to include a new field notification_interval_days to specify the interval that triggered the notification.

Coverage increased (+0.05%) to 60.717% when pulling d278c6e13204500c328f2b52ebce016ffab97e9d on jtschladen:notification-interval-sns into de06f13bb15f0f9eb34cdc5d04531410e45ae62d on Netflix:master.


Pack BoostConfig struct

We can pack the start and end timestamps into a single slot in the BoostConfig to save gas

Actually can pack  one of the addresses in with the timestamps. 32 bits for each timestamp then 160 for the address = 224 bits


Deprecated Error

Hey I get the following error. I tried a lot already but I can't fix it maybe someone has an idea?
used_by is deprecated, please use 'filetype_to_parsername'
Fehler beim Ausführen von "/Users/user/.config/nvim/after/plugin/lspkind.rc.lua":
E5113: Error while calling lua chunk: ...cal/share/nvim/plugged/lspkind-nvim/lua/lspkind/init.lua:123: Vim(echoerr):DEPRECATED replaced by mode option.
stack traceback:
        [C]: in function 'nvim_command'
        ...cal/share/nvim/plugged/lspkind-nvim/lua/lspkind/init.lua:123: in function 'init'
        /Users/user/.config/nvim/after/plugin/lspkind.rc.lua:4: in main chunk

I use these dot files: https://github.com/craftzdog/dotfiles-public
Thanks in advanced

Remove with_text, it's deprecated and you are setting it to default value anyway.

thanks

@onsails And how do I turn the text off now? What's the new name for the option?


Browser support

To properly support browsers, replace re2 with re2-wasm

PR welcome

Are you interested in dropping pre-build tooling and switching to ESM? This would make it easier to get the wasm-reliant code to work.

@Richienb I tried to understand the difference between re2 and re2-wasm, but the second one seems to be based on the first and does not seem to have any major differences. Both modules seem to be useful on the Node.js server side and will not work within a browser. Why prefer second over the first?

Why prefer second over the first?

You can not run native modules in the browser. You can run WASM though.

When would we need url-regex-safe in the browser?  Curious what the use cases are.  Could just have an API endpoint that takes a string and parses it and returns it and then calls new RegExp with value?

For libraries that validate urls before sending a request to them, making the validation an API endpoint would completely invalidate this. In this case, you might as well send the request in the first place and handle the error.

I'm using it in the browser to create a version of the text that will have any URL's converted into HTML with newlines converted to line breaks. Using a module, which was url-regex, instead of my own regular expression made sense.


Update azure-stack-manage-permissions.md

It is not accurate for the two sentences
"Owner: can manage everything, including access to resources.
Contributor: can manage everything, except access to resources."
It should be as below:
Owner: Grants full access to manage all resources, including the ability to assign roles in Azure Stack RBAC.
Contributor: Grants full access to manage all resources, but does not allow you to assign roles in Azure Stack RBAC

@xizhuang Thank you for the contribution, we will get this merged! #sign-off


Fixes shell command missing current context environment variables

Updated shell command to include the run environment variables
Fixes dependency which was causing the pterradactyl command to break if not forced to a downgraded version

You might want to update your PR description to this
Updated shell command to include the run environment variables

Done!

@GiampaoloFalqui Can you add unit test for the change?


tab badge will jump when badge number goes to 0 and from 0 to > 0

The relevant css:
.tab-item.has-badge {
  position: relative;
}

.tab-item .badge {
  position: absolute;
  top: 4%;
  right: 33%; // fallback
  right: calc(50% - 26px);
  padding: $tabs-badge-padding;
  height: auto;
  font-size: $tabs-badge-font-size;
  line-height: $tabs-badge-font-size + 4;
}

I found out that the fix is simply set the position relative regardless of whether has-badge is present or not
.tab-item {
  position: relative;
}

Greetings, @pencilcheck!
We are now requiring all issues to be submitted through our custom issue form so that we have all of the information necessary to fix them as quickly as possible.
Your progress on this issue has been saved at the following url:
link to Ionic issue form
This issue will be closed if not resubmitted through the form. Please fill out the rest of the form so that we may assist you.
Thank you for allowing me to assist you.

+1

Greetings @pencilcheck!
My sensors indicate that I require more information in order to assist you.

Can you provide a detailed description of this issue?
How would a robot go about replicating this issue?
On which platform does this happen occur? (iOS, Android, all, etc.)
On which platform versions does this occur? (Android 4.2, iOS 8, all, etc.)
Is this an issue with the Ionic Framework or Ionic CLI?

Additionally, providing a codepen that replicates the issue is extremely helpful.
If you wish to get help using the framework itself, I recommended visiting the forum, where many humans will be able to offer wisdom and advice.
Thank you for allowing me to assist you.

Greetings @pencilcheck!
My sensors indicate a reply was requested, but we have not received one yet, I am using my robot powers to close this issue. However, if you are still experiencing this issue, please feel free to reopen it by creating a new issue, and include any examples or necessary information.
Thank you for allowing me to assist you.

Greetings @pencilcheck!
My sensors indicate a reply was requested, but we have not received one yet, I am using my robot powers to close this issue. However, if you are still experiencing this issue, please feel free to reopen it by creating a new issue, and include any examples or necessary information.
Thank you for allowing me to assist you.

Is it fixed?

Thanks @pencilcheck your solution works like charm...

saved my day!!


Why are there guidelines about 'embedding for your customers' on this page?

The sentence "If you're embedding reports, dashboards, or tiles for your customers, then you have to place your content within a workspace." is a bit confusing as this page describes embedding for your organization.

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

ID: 90078026-b608-ccf2-f3ef-58021b484f75
Version Independent ID: e51ab568-5610-ff18-c5c0-4d2f27935dfa
Content: Embed content in your application for your organization - Power BI
Content Source: powerbi-docs/developer/embedded/embed-sample-for-your-organization.md
Service: powerbi
Sub-service: powerbi-developer
GitHub Login: @KesemSharabi
Microsoft Alias: kesharab

Hi @Koning53 , thanks for your observation. I am passing it on to the doc author for consideration.

Hi @Koning53,
Thank you for your comment. You're right, this sentence is confusing.
We're in the process of updating all the embedded analytics tutorial, and will shortly update this one too.
Please check these tutorials in a couple of months, once they're updated.
Thansk,
Kesem


Building on case-sensitive volume

… might be unrelated, but besides that, there's not much special.
Xcode: Version 10.1 (10B61), default toolkit
Build MicroExpress_2018-11-29T15-21-11.txt

Since it works for me, I think it is quite likely a case-sensitivity issue. Most likely cause: incorrect use of Debug/Release vs debug/release in some script.


assmble js Test initiative

Travis works for this change.
During this change:
1). replace bower plugin to general nodejs plugin to support both JS download and Test Evaluation.
2). wrap up mocha component, and add one unit Test to evaluate Transfromation from Unix Cron to Quartz.
3). Enforce gradle to download nodejs every time, in order to resolve npm can not be found issue.
4). Bring up rewire.js in order to be able to get local function of javascript file.
5). enforce clean temporary files during gradle clean

@suvodeep-pyne Tools guy taught me how to debug gradle in IDEA. The root cause of npm_install failling in IDEA is that $PATH is not right in IDEA. I enforce gradle always downloadin the specific nodejs version, and resolved.

@fsi206914 Thanks for sharing that.

@suvodeep-pyne Do you have any comment for this pull request? I noticed that our pull request sometimes failed for some reason. This change enforced downloading a specific node js version, might solve that issue.
@HappyRay

"Enforce gradle to download nodejs every time, in order to resolve npm can not be found issue." Is this going to slow down the build process? Is there no other way? How did others solve the same problem?

@suvodeep-pyne could you take a look?

@HappyRay I didn't observe slowness in my local laptop.
Also, it should be one-off process. Unless you do gradle clean, you don't need to download after the first build.

LGTM. Thanks for adding the first JS unit test. With your work, adding more JS unit tests will be easier.
Thanks @suvodeep-pyne for the through review.

Thanks a lot for @suvodeep-pyne 's reviews. Learned a lot.


Ingress values fixed for production and sandbox

Context
Bug fixed for ingress
Changes proposed in this pull request
origin_hostname updated for sandbox and production.
Guidance to review

Link to Trello card
https://trello.com/c/XVe4ftpa/1723-school-placement-domain
Things to check

[ ] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[ ] API release notes have been updated if necessary
[ ] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[ ] Required environment variables have been updated or added to the Azure KeyVault

Screenshots

 School placement domain


Vale missed style definitions.

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

1.0.0
GitHub release

Your semantic-release bot :package::rocket:


Add support for diff3-style git merge markers

TypeScript Version: (2.4.0-dev.20170528)
Code
When merging files with conflicting changes, git puts both changes together with conflicts markers that are correctly supported by TypeScript (markers emit TS1185 errors and only the first block is used, the other one is treated as a comment):
class C {
<<<<<<< HEAD
   v = 1;
=======
   v = 2;
>>>>>>> Branch - a
}

Unfortunately, in many cases it is not sufficient to have just both changes to successfully resolve the conflict. Git also supports diff3 style (merge.conflictStyle = diff3) that shows common ancestors block in addition to both conflicting changes, it is thus superset of the default algorithm:
class C {
<<<<<<< HEAD
   v = 1;
||||||| merged common ancestors
   v = 3;
=======
   v = 2;
>>>>>>> Branch - a
}

Expected behavior:
I'd expect the common ancestors token ||||||| be also recognised as merge token TS1185 and content of this block be treated as a comment.
test.ts(2,1): error TS1185: Merge conflict marker encountered.
test.ts(4,1): error TS1185: Merge conflict marker encountered.
test.ts(6,1): error TS1185: Merge conflict marker encountered.
test.ts(8,1): error TS1185: Merge conflict marker encountered.

var C = (function () {
    function C() {
        this.v = 1;
    }
    return C;
}());

Actual behavior:
Currently it parses the ||||||| token as three || and one |, emits several errors that are unrelated to the root cause (git merge) and the javascript output is wrong.
test.ts(2,1): error TS1185: Merge conflict marker encountered.
test.ts(4,1): error TS1068: Unexpected token. A constructor, method, accessor, or property was expected.
test.ts(4,3): error TS1109: Expression expected.
test.ts(4,5): error TS1109: Expression expected.
test.ts(4,7): error TS1109: Expression expected.
test.ts(4,16): error TS1005: ';' expected.
test.ts(4,23): error TS1005: ';' expected.
test.ts(6,1): error TS1185: Merge conflict marker encountered.
test.ts(8,1): error TS1185: Merge conflict marker encountered.
test.ts(9,1): error TS1128: Declaration or statement expected.

var C = (function () {
    function C() {
        this.v = 1;
    }
    return C;
}());
    ||  ||  ||  | merged;
common;
ancestors;
v = 3;

Fix:
I've already made a fix while trying to resolve this for me in 1ccbaab and added tests in 64a754c.

Sounds like a good idea. That commit you have looks basically ready (probably undo the ch rename just to minimize changed lines), care to send a PR?

Sure, will send in a moment. Thanks!

@CyrusNajmabadi in case you're interested in this too.

Thanks for letting me know.  We'll make a similar change to Roslyn if we hear any feedback about this.


Add NHibernate profile

Hey guys,
I've added a first version of the nhibernate profiler.
Things changed:

added project Glimpse.Ado, containing all of the core SQL stuff, i.e. the GlimpseProfileDb* classes, the SQL plugin, provider stats, ...
removed the common ADO stuff from the EF plugin and use the ones from the Glimpse.Ado package
added project Glimpse.Nh, which contains the GlimpseProfileDbDriver that will be injected into nhibernate to register all executed commands with the provider stats
added project Glimpse.Sample.Nh, which is a slightly modified version of NerdDinner for Nhibernate (http://www.hanselman.com/blog/ExtendingNerdDinnerExploringDifferentDatabaseOptions.aspx)
introduced the concept of an IGlimpseService

Todo:

inject the GlimpseProfileDbDriver automatically into nhibernate, currently is has to be registered in the NH-config
remove the reference to nhibernate from the Glimpse.NH project (if possible)
unit tests, unit tests, unit tests

Cheers,
Steven

@stevenlauwers22 We are going to be doing some work on this stuff tomorrow night. We will bring this in then and setup your account going forward.

Really interested the NHibernate profiler.  Any ETA?

Sorry about that. Lots been happening at the moment.
@stevenlauwers22 Any change you can sync this back up again so I can pull it in?

Hey guys,
In the meanwhile I was able to automatically inject the glimpse driver into NHibernate, so no manual configuration is needed anymore. I still need to to some work to remove the nhibernate reference from the Glimpse.NH package but that shouldn't be to big of a problem.
I'll sync up and include the latest changes in this pull request (will probably do this tonight).

Hey guys,
You should be able to pull it in now.


Vet clinic database: create animals table

Created a database named vet clinic.
Created a table named Animals with the different columns
Inserted data into the table
Queried data from table

removed all  guide instructions

removed  guide instructions

Removed comments from README
Changed   Devimon's neutered value to true
Changed date value from 2019-12-31' to'2019-01-01'
Displayed the names only as suggested by the reviewer

removed FAQ section
updated screenshot for queries


Update async-http-client to 2.12.2

Updates org.asynchttpclient:async-http-client from 2.12.1 to 2.12.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (2.12.1).
You might want to review and update them manually.
.github/workflows/ci.yml
.mergify.yml
project/Http4sPlugin.scala
website/src/hugo/content/changelog.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.asynchttpclient", artifactId = "async-http-client" } ]

labels: library-update, semver-patch, old-version-remains

This should be backported to 0.21 as well.

This should be backported to 0.21 as well.


Scrollbar ??

How can I display a scroll bar for too many rows ?
cheers

Hey @tech-a-go-go  this is not a supported feature directly. You can however use css to make the table scrollable. Currently however there is no way to focus to a cell. If you do end up implementing something like that, a PR is welcome


Cut 5.3.0 in changelog

It's not a user-visible change, so it doesn't really matter. But if we're mentioning Vite, we should mention Playwright too.

Oops! I didn't realize 5.3.0 was not in the changelog yet! Okay, then that's the main point of this PR now, and adding Playwright is a minor thing.


Alternative implementation

Current implementation creates a dummy object. It's possible to get alignment with just pointer manipulation.
        let base = std::mem::align_of::<Foo>(); // First valid non-NULL pointer address
        let ptr = base as *const Foo;
        assert_eq!(0, (&(*ptr).field) as *const _ as usize - base);

I think &(*ptr) is valid and does not actually deference the object, because such construct is also allowed for non-movable values (where *obj causes an error, but &*obj is fine).

Actually it was implement like this at one point, but appearantly it is somewhat of a UB:
https://users.rust-lang.org/t/is-this-pointer-dereference-inherently-unsafe/13428/2

Note that version I'm proposing is substantially different, because it doesn't use NULL.

But it's still a pointer to an un-allocated, unknown piece of memory.
AFAICT null is not special that way.

OK