Filtering of object recognition

After the predictions of each of the models, we combine all the predictions in one image and filter them as follows:

we find which models classify an object in this area, we look at the intersection of the IOU, if it is greater than the threshold value (HYPERPARAMETER_1), then these models took part in the classification of this object
next, we take the validation weights of these models and use some expression, for example, a sum, convert them to a number. And, if this number is greater than the threshold value (HYPERPARAMETER_2), then we leave the object predicted, otherwise we remove it from the prediction
if the IOU is less than the threshold value, then we select a new object from this new frame

Instead, we remove those predicted boxes that have a small probability of existence, based on the validation weights of the models.

Close this issues with this merge commit.


feat: add client example

Thanks for the example. Can you, however, look at the failed checks (basically, rustfmt complains about some things). Also, there are some minor things in the code.

Seems appveyor failed to download rustup :/
Build started
git clone -q https://github.com/vorner/tokio-jsonrpc.git C:\projects\tokio-jsonrpc
git fetch -q origin +refs/pull/3/merge:
git checkout -qf FETCH_HEAD
Running Install scripts
appveyor DownloadFile https://win.rustup.rs/ -FileName rustup-init.exe
Error downloading remote file: One or more errors occurred.
Inner Exception: The request was aborted: Could not create SSL/TLS secure channel.
Command exited with code 2

I can try to kick it out again if you want.

Yes, it does so from time to time. It's OK, I'll fix one or two more copy-pasted comments I just noticed and merge it.

OK, I merged it with a minor amend, so github wrongly things it is not merged… the technology still has a room for improvement.


View deployment's checkpoint id and end time

Changes

pf deployment view shows model ckpt id and end time
Fix bug in deployment list to list only current project's deployment.

@kooyunmo Thank you! I've addressed your comment!


build: update to Angular 16 & update packages

Hello @thomasnisole & @oscar-guerin,
This PR fixes https://github.com/paddls/ngx-common/issues/33.
What I did:

I upaded the CI Workflow to use Node.js 18

It was using 16.13.2 which isn't supported by Angular anymore
Updated to actions/checkout@v3
Updated to actions/setup-node@v3
Updated to<EMAIL_ADDRESS>

I re-generated the package-lock.json

It now uses "lockfileVersion": 3

Switch package versions from ^ to ~ to prevent breaking changes
Update to Angular 16
Update packages
Remove unused packages
I removed tslint.json as you're using ESLint
I removed jest.config.js as you're using Jasmine/Karma
I bumped supported Angular versions of the lib to support Angular 16

If everything is fine for you, it would be awesome to release a new major version (I did not bump the version nor the compatibility table).
Have a nice day.

Hi @Yberion,
Merging this PR, thanks a lot for your contribution !
I will publish a new version as soon as possible

Awesome, thanks!


Implement supervising strategies for domains

It is a very common case when programmer wants to have high-level API to handle failures. It often makes sense to restart a part of application state in case of failures instead of letting user to encounter an error.
Proposal
A great implementation of fault-tolerance applications is already invented in Erlang-Elixir/OTP framework. They introduce a supervisor entity with several restart strategies. The idea is to return a part of application to its initial state, notify developer about error but let user to continue using the system. Of course these are code issues in most cases but it also covers errors from external sources such as network issues when system will continue performing properly after restart.
Elixir code example
children = [
  MyApp.DB1Connector,
  MyApp.DB2Connector,
  MyApp.Endpoint
]
options = [strategy: :one_for_one]
Supervisor.start_link(children, options)

Now our stores are being supervised with defined strategy.
List of proposed strategies:

one_for_one

Means to restart a store with its initial state in case of error

one_for_all

Means to restart all supervised nodes with initial states

nothing

Keep default behavior to not crash the existing API.
It makes sense to focus attention on supervisor's structure. It is an Erlang process and worker is a process as well.
Hence it can be resolved by wrapping domain around another domain in case of effector terminology especially because Effector supports nested domains.
Also I can redefine restart strategy for particular domain manually to not break a Domain abstraction like this:
Each domain has restart options:

permanent

The child is always restarted(default)

temporary

the child is never restarted
So that I can improve my supervision tree like this:
children = [   MyApp.DB1Connector,   MyApp.DB2Connector,   MyApp.Endpoint.child_spec(restart: :temporary) ] options = [strategy: :one_for_all] Supervisor.start_link(children, options)
This configuration will not restart an app in case of MyApp.Endpoint failure but will do it when MyApp.DB1Connector fails.
OTP keeps sync and async actions separately hence there is a direct analogy with Event and Effect.
Also supervisors and supervised domains would be a great framework to implement effector dev tools.
Effector API change request
   createDomain('supervisedDomain', {supervisor: false, restart: 'permanent'})    createDomain('supervisorDomain', {supervisor: true, strategy: 'one_for_all'})
with default value false for supervisor option.

What should supervisor do with events and effects? (since they also exist in domains)

@goodmind Events and effects should be untouched, restart affects current state only

What about current function in effect's use?

seems like meaning of "restart" needs to be defined beforehand
for example, it looks pretty close to .reset in stores

also, with this approach, we can remove obsolete subscriptions on the fly

at first, we need to add .catch method to get semantic of "child is terminated", I mean, we need to have that anyway, isn't it?
for example

const store = createStore(null)

const computed = store.map(x => x)

computed.catch // event to forward to supervisor or something like that

What should this do?
// old domain
const domain = createDomain('simple domain')

// supervised domain
const supervisedDomain = domain.domain('supervisedDomain', {supervisor: false, restart: 'permanent'})

In this case behavior should remain untouched because supervisor option is not set in domain constructor

https://github.com/elixir-lang/elixir/blob/master/lib/elixir/lib/supervisor.ex
https://github.com/blackberry/Erlang-OTP/blob/master/lib/stdlib/src/supervisor.erl
related links


Add MSSQLServer module

Add MS Server module

[x] acceptLicense
[x] select edition
[x] connect and query, connection uri, and secure password tests
[x] container start
[x] update docs

Hi @wjin17, thanks for the contribution! The test are failing on my M1 mac with the following:
testcontainers:containers [0dbfd11c6c3f] /opt/mssql/bin/sqlservr: Invalid mapping of address 0x400395b000 in reserved address space below 0x400000000000. Possible causes: +65ms
testcontainers:containers [0dbfd11c6c3f] 1) the process (itself, or via a wrapper) starts-up its own running environment sets the stack size limit to unlimited via syscall setrlimit(2); +0ms
testcontainers:containers [0dbfd11c6c3f] 2) the process (itself, or via a wrapper) adjusts its own execution domain and flag the system its legacy personality via syscall personality(2); +0ms
testcontainers:containers [0dbfd11c6c3f] 3) sysadmin deliberately sets the system to run on legacy VA layout mode by adjusting a sysctl knob vm.legacy_va_layout. +0ms

Could it be an issue with ARM/is a fix possible?

Hi @wjin17, thanks for the contribution! The test are failing on my M1 mac with the following:
testcontainers:containers [0dbfd11c6c3f] /opt/mssql/bin/sqlservr: Invalid mapping of address 0x400395b000 in reserved address space below 0x400000000000. Possible causes: +65ms
testcontainers:containers [0dbfd11c6c3f] 1) the process (itself, or via a wrapper) starts-up its own running environment sets the stack size limit to unlimited via syscall setrlimit(2); +0ms
testcontainers:containers [0dbfd11c6c3f] 2) the process (itself, or via a wrapper) adjusts its own execution domain and flag the system its legacy personality via syscall personality(2); +0ms
testcontainers:containers [0dbfd11c6c3f] 3) sysadmin deliberately sets the system to run on legacy VA layout mode by adjusting a sysctl knob vm.legacy_va_layout. +0ms

Could it be an issue with ARM/is a fix possible?
Also looks like the Azure dependencies are incompatible with Node 20 which is LTS, perhaps it's supported with a newer version of the dependency?

Hi @cristianrgreco
Unfortunately, I do not have access to an M1 mac but trying to run mssql on M1 macs seems to be a known issue. Here's a link to a fix from the official MSSQL docker repo mssql docker issue #668.
For the Azure dependency, I tried updating to the latest version of node-mssql using Node 20 but it seems like the official library is still using the deprecated Azure module.
Please let me know how to proceed.

According to https://github.com/tediousjs/node-mssql/issues/1540, node 20 is now supported, will re-run the build now.

According to tediousjs/node-mssql#1540, node 20 is now supported, will re-run the build now.

Awesome! Thank you for the update.

Thanks for the contribution @wjin17 !


Try react-native-web

From @sebgoa on July 11, 2016 7:40
https://github.com/necolas/react-native-web
To be able to render on a browser.
Copied from original issue: skippbox/cabin-sw#14

try to run it.
come up with pros and cons.


Numpy Notebook fix

Partially Solves issue #10
static view link

@Shuvam456 Good work. However, there are some minor changes I would like to request:

There is no need to import the NumPy module in every cell. You can consider importing a module as a global import rather than restricted to that particular code cell.
For markdown text to be rendered as Heading or subheading, you need to give a space after the trail of #. There are some instances where you missed the space.
Since this notebook is focused on NumPy arrays, comprehension of NumPy 1d, 2d and multi-dim arrays would look better.

@Shuvam456  No need to update the notebook name, you can keep the name as Numpy_Notebook.ipynb.

This notebook will serve as base for more changes so merging it for now.


cherry-pick prep_xds.sh changes from v1.37.x into v1.36.x

Should unbreak go xds tests for v1.36.x branch.
https://source.cloud.google.com/results/invocations/055aa485-ed3b-4510-bcac-1ef747918f2e/targets

@ejona86 AFAICT this should fix the java xds failure on 1.36.x as well
https://github.com/grpc/grpc-java/blob/0f772a8f9846264336dd4f3212ca325682fa273d/buildscripts/kokoro/xds.sh#L22

@nicolasnoble  can you please merge?


Missing 'Call' as a function option

at the moment you can't do something like
var cypher = new Query();
cypher
   .match(...)
   .call('apoc.create.setLabels(...)');

See https://neo4j-contrib.github.io/neo4j-apoc-procedures/

As a note you can get around this by using .add('CALL apoc....') . But it would be nice to keep to the same paradigm

That's right indeed @dmk255. CALL was added very recently and I should therefore update the syntax.

Just added the .call method. Can you try & tell me whether this fits your needs before I release a new version on npm.


the SAS definition

Hello, it is quite good document, but it is not clear how to configure Linked service by using SAS uri.  I cant put it in Azure Data Factory GUI when configure the linked service, there is only Storage account access by Account Key is available to choose.
If I try to change json in "Advanced" section I can't save it.
Please, clarify please, how to configure SAS uri based linked service by using ADF User Interface (portal)
Best regards,
Denis Makagonov

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

ID: b8ab834e-461c-b8fc-2056-7d2bfd152630
Version Independent ID: 805724e0-968d-2854-e0a9-6eeae2df9fa2
Content: Copy data to and from Azure Table storage by using Data Factory
Content Source: articles/data-factory/connector-azure-table-storage.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@denmak Thanks for the feedback! I have assigned the issue to the content author to investigate and update the document accordingly.

As I found there are no options to create linked service and dataset based on shared access signature for table storage  in Azure Data Factory v2 GUI, but there a work around, with Azure Powershell. If set the linked service and dataset via powershell, then we can continue to work with GUI as usual.  but this is not clear from the documentation.


Error while updating property 'adUnitId' of a view managed by :RNAdMob

Hi,
When i use AdMobBanner component i face this error, and when i use the AdInterstitial the app crashes.
I tried adding that meta-data to my manifest but another error happens while building.

What is that “another error”?

Execution failed for task ':app:processDebugManifest'.

Manifest merger failed with multiple errors, see logs

Please provide the logs, because this is message is not very helpful without it.


Fix comment for OpenIdConnectMessage.CreateLogoutRequestUrl()

Triggering a build pipeline: /azp run

@Kahbazi can you issue a PR to dev5x ?

Done #1176


Browser specific tests won't be reported

For some reasons I have to run a set of browser specific tests like:
if (browserSupported) {
   describe('specific tests...', function() {
      ...
   });
}

In these cases, item.count will never reach self.numberOfBrowsers (source), so the item. isCompleted stays undefined thus it won't be reported :(
Any workaround for this?

Update: after going through the source code, I got a question around my head: why can't we just print all test results in self.onRunComplete callback?

Is there a link to the repository so that we can run the tests ourselves?

Sorry the repo is currently a private one, but I can give you an example code:
if (navigator.serviceWorker) {
  describe('Service Worker Tests', function() {
    it('should be presented', () => {
      // test code
    });
  });
}

describe('Other Tests', function() {
  it('should be presented too', () => {

  });
});

If you run this code with chrome, firefox and safari, you will only see Other Tests suite in outputs.

@4kochi ah, I think I misunderstood what you meant...
I created a demo that reproduces this issue here: https://github.com/idiotWu/karma-mocha-reporter-demo. To run this demo, you need to have Chrome and Safari installed in your OS.

Thx, will have a look

Added a new option printFirstSuccess. When set to true you will see the reports. Will be released in the next version.

Released in v2.2.2

Much thanks! Now it works like a charm!


Update README

Need to update README.md
Need to add more information.
Need to change formating.

Updated the readme.md and created MR request,


AccessViolationException on BuildImage

I'm getting an AccessViolationException while calling BuildImage on the first page and second (which seem to be bad-quality digitalized images) of a djvu file, is this "normal"?
The faulty lines are: https://github.com/Telavian/DjvuNet/blob/master/DjvuNet/DjvuNet/DjvuPage.cs#L959-L961

Not sure if it helps, but calling Page Information on WinDjView on the faulty pages yields:


HdAurora deployment on Linux and usdview rendering issues

Hello there,
thx for publishing this awesome renderer.
Since I want to use USD and Hydra mostly on Linux I gave it a try to run HdAurora on Linux.
Several steps were necessary to build and deploy hdAurora:

First of all, the  deployHdAurora.py does not support linux for now.
I've made (quick) adjustments here:
https://github.com/lindemeier/Aurora/blob/73809a1291b107742ad7c0571606c40242083835/Scripts/deployHdAurora.py

The lib in pluginInfo.json needs to be named accordingly:
https://github.com/lindemeier/Aurora/blob/73809a1291b107742ad7c0571606c40242083835/Libraries/HdAurora/resources/linux/plugInfo.json

Upgrade boost to 1.78 due to compilation errors.

After executing these steps I was able to run usdview in a conda environment setup with all python dependencies.
After starting usdview directly with Aurora as renderer and the USD "Kitchen_Set" as input scene, I get the following output:

The terminal is spammed with:
v22.11/pxr/base/vt/value.cpp : 'Attempted to get value of type 'VtArray<GfVec2f>' from empty VtValue.'
        Error in '*pxrInternal_v0_22__pxrReserved__::VtValue::_FailGet' at line 562 in file /home/zotlinde/dev/Aurora/externals/src/USD-22.08-Aurora-v22.11/pxr/base/vt/value.cpp : 'Attempted to get value of type 'VtArray<GfVec3f>' from empty VtValue.'

I tried to run it on the following operating systems:

Ubuntu 22.04 (native)
Ubuntu 20.04 (docker image based on a NVIDIA cudagl image). Here step 3 was not necessary, since boost built with no error here (due to the gcc version I'd assume).

Both showed the exact same behavior.
Further information:
I tried gcc and clang-12. No difference.

GPU:
NVIDIA GeForce RTX 3060 Ti
Driver Version: 525.85.12

Hi,
This looks very promising indeed, we have been missing a rasterizer in hydra that can do nice raytraced shadows and reflections. This seems like a great render that fits the gap. However, I'm getting same issue as lindemeier here on Linux Mint.
Getting same issue on Linux Mint
GPU: NVIDIA GeForce RTX 3060 Laptop GPU
Driver version: 470.57.02
Vulkan SDK version:<IP_ADDRESS>
Cheers,
Dan

Tried the new release v23.03.
Now I get these errors:
Warning (secondary thread): in RebuildAuroraInstances at line 201 of /home/zotlinde/dev/Aurora/Libraries/HdAurora/HdAuroraMesh.cpp -- Normal array smaller than points array: /telescope05_10_21/telescope_ref/telescope_mount_electronics_box/telescope_orientation_adj_ref/telescope_upper_mount_ref/telescope_ra_ref/telescope_dec_ref/telescope_optical_tube_ref/telescope_tube_mount/telescope_back_body/telescope_back_trimount/telescope_optic_output/telescope_diagonal/diagonal_mirror/diagonal_mirror_Shape
Coding Error (secondary thread): in _FailGet at line 562 of /home/zotlinde/dev/aurora_externals_root/src/USD-22.08-Aurora-v22.11/pxr/base/vt/value.cpp -- Attempted to get value of type 'VtArray<GfVec2f>' from empty VtValue.
Coding Error (secondary thread): in _FailGet at line 562 of /home/zotlinde/dev/aurora_externals_root/src/USD-22.08-Aurora-v22.11/pxr/base/vt/value.cpp -- Attempted to get value of type 'VtArray<GfVec2f>' from empty VtValue.
Runtime Error (secondary thread): in operator() at line 43 of /home/zotlinde/dev/Aurora/Libraries/HdAurora/HdAuroraPlugin.cpp -- /home/zotlinde/dev/Aurora/Libraries/Aurora/Source/HGI/HGIRenderer.cpp, 307: Unrecognized material type MaterialX for material HdAuroraMaterial//telescope05_10_21/Materials/mirror

Coding Error (secondary thread): in _FailGet at line 562 of /home/zotlinde/dev/aurora_externals_root/src/USD-22.08-Aurora-v22.11/pxr/base/vt/value.cpp -- Attempted to get value of type 'VtArray<GfVec2f>' from empty VtValue.
Segmentation fault (core dumped)

It segfaults directly.
Compiled it with default gcc on Ubuntu 22.04. Will try it with my docker Ubuntu 20.04 setup when I have time.


Bug on CLI printing None with wrong input

CLI is printing None after wrong input.
❯ mathinterpreter 1+
'NoneType' object has no attribute 'type'
None                          <---

I would expect only an error message and after that nothing. It is printing None because it is trying to print the calculated value after the wrong input is given.

I am sorry for not explaining this @hsguidi. This is actually another bug and wasn't fixed by my last PR.
It wasn't captured because there aren't any tests for common errors on the library. This should be a nice addition to the project. As soon as I have some time I will try to a test for this one... meanwhile let's leave this bug open.


Tessellating Block in World

crash-2024-01-22_12.32.51-client.txt
Rendering some chunks or certain parts in the chunks are invisible and it's unplayable.

You need to use Fabric APJ for Indium 1.0.21.
https://modrinth.com/mod/qsl/version/7.2.2+0.88.1-1.20.1

Closing issue: use the suggested version of Fabric API


Give Blocks a spatial grid by default under certain circumstances

Blocks tend not to have spatial grids, and their pin components lack spatial locators. This is because historically, we have not really cared that much where a pin is in particular; usually there are enough instances of the pin components to fit neatly(ish) into a given number of hex rings or whatever, so we infer their locations that way. They are also usually identical, so we never had to care which specific site a pin or collection of pins occupied.
Eventually we added the ability to get more specific in the input blueprints (see https://terrapower.github.io/armi/tutorials/walkthrough_lwr_inputs.html), but we never actually required the user to provide grid layouts for their blocks, since it would break every input file that we've ever written, and going forward, having to explicitly define the layout of trivial blocks would be a major drag. As a result, in most hex reactor inputs, pretty much every Block has no .spatialGrid.
The expectation throughout the code that Blocks "just don't have grids" has led us to whip up grids ad hoc whenever they would be necessary, making (but almost never verifying) all sorts of assumptions about how stuff is laid out. I wouldn't be surprised if this leads to some interesting bugs, or the very least confusion, in cases where a Block has an interesting set of components. Best case scenario is that whipping up the grids where we do so isn't wrong and we are just potentially wasting time making and re-making grids, being too afraid to actually attach the grid to the block itself (and the locators to the components).
I propose that we take the step of actually defining a "trivial/canonical Block layout", and when a Block supports it (EDIT: and doesn't explicitly define one) actually make a spatial grid for it at construction time. Then throughout the code, if we come across a block that doesn't have a spatial grid, we will know that it wasn't just because the input writer just didn't bother, but because it's actually a weird block design and we should think carefully about just whipping up a grid for it.
First stab at a definition for "trivial":

A block where all components have a multiplicity of either 1 or N, where N fits squarely in a number of locations that can be held by an given number of rings.

Thoughts?

I like this idea. I think it's pretty safe as you defined it since having a grid is just extra info and shouldn't change any answers or numbers for plugins that ignore it. It will be quite useful to have for people who can use the pin level info.

I agree with this and also think that it may uncover unexpected issues in client code related to "whipping up" block layouts. I believe that it would be safe to assume:
| Core Grid Type | Block Grid Type |
| Cartesian | Cartesian |
| Hexagon | Hexagon |
| RZT | None |
When determining whether a "pins" or all components fit into the grid will you be checking for geometry overlaps with the "duct" or "can" based on the pitch data or will you just be using the number of available locations? For example, you can jump between 217 pins and 271 pins, but if you define 218 pins then will this just not assume a spatialGrid and present a warning? I recommend that any implicit assignment of spatialGrid types be recorded and reported to the user in the STDOUT so that this is visible and easy to verify.

if you define 218 pins then will this just not assume a spatialGrid and present a warning

In my mind, ARMI would just throw up its hands and not even attempt to set a .spatialGrid for such a block, leaving it as None. I agree that reporting the generated grids to the user in the stdout is a good idea.

Implemented in #323. Thanks, @chris10mckenz !


508 Compliance- Text Alternatives

Provide text alternatives for any non-text content so that it can be changed into other  forms people need, such as speech.

Text alternatives have started.  Other fixes are in work and are being resolved.  Passes initial testing in IE9/11, FF, and CH.
Ricardo will be meeting with the 508 representative to determine further requirements.

Tested Nav icons, Hover over Launch and Bookmark icons and Pop up dialogue box - Launch, Bookmark, Edit and Close icons.
Edit icons say - Unlabel for button
Close icon- says the Header of app but does not indicate it is a close icon that closes the app pop up.

Passed 508 JAWS testing Nav Icons in pop up modal.
Close, Launch, Bookmark( enabled and disabled) , Edit and Tabs.

CHROME - PASSED Close, Launch, Bookmark( enabled and disabled) , Edit and Tabs.
FF- PASSED Close, Launch, Bookmark( enabled and disabled) , Edit and Tabs.
IE FAILED - Bookmark and Edit buttons and Overview and Reviews tabs include extra info

If we are not including IE 11 then it passes.


drivers: bbram: Add it8xxx2 BBRAM driver implementation

Note that the it8xxx2 does not support a status register so that functionality is omitted.
Signed-off-by: Yuval Peress<EMAIL_ADDRESS>

This change is

@mbolivar-nordic I've update the PR to include build-only tests. That's the best I could find for making sure that the bbram drivers are up and running. Please point me in the right direction if there's a qemu platform that could run actual tests on the driver or if there's a better way to do this.

I split this up into 2 commits.


Rip out all things S3Guard / DynamoDB

Fixed with https://github.com/cloudera-labs/cloudera.exe/pull/33


Bug: Custom font not used in item preview pane

Description

The underlined bits of text are not using the font set in the Settings file
Steps To Reproduce

Set a custom font
Open the preview pane

Requirements
A custom font to be set
Files Version
<IP_ADDRESS>
Windows Version
10.0.25336.1000
Log file
debug.log

@i-dont-know-username thank you for reporting this issue.

While looking at this and the other custom font issue I noticed that the Details page uses custom fonts and the general page only partially does. Neither the security or Hashes page use any custom fonts. I'm assuming all the pages should be using custom fonts for all the text? Or is it by design? Thanks! I've attached two images to show what I mean. If this is a totally separate issue I can open one up.

Possible to be assigned to this issue please?

@MrFrawsty I'm creating a new issue for the inconsistencies you've seen in the Properties window : #12553

This issue will be fixed in the upcoming v2.5 release.


Animation not working

Before submitting a bug
[ x ] I updated to the latest version available
[ x ] I cleared the cache of my browser. See here
Describe the bug
Since 2023.9 the animation stopped working. The image is not moving anymore when mower is active.
Still persisting in 2023.10
As opposed to this, the vacuum cleaning card is showing the wanted behavior.
Steps to reproduce

Open panel
Watch the image
Image not animated

Expected behavior
Image animated
Versions:

Browser: chrome
HomeAssistant version: 2023.10.0
Landroid_cloud integration: latest

Check the new release https://github.com/Barma-lej/landroid-card/releases/tag/0.3.2

Perfect Thanks!, new release was the solution and fixed my issue!


Move examples to geoutils-data including an additional float32 raster with NaNs

This PR:

Removes the geoutils/datasets folder that contained example data;
Adds a geoutils/examples.py module that downloads example data from a fixed commit in the repository geoutils-data created just for this purpose;
Adds an example based on an ASTER DEM on Exploradores glacier, Northern Patagonian Icefield which brings diversity to the testing suite because: it is coded in float32 instead of uint8 for the Everest example, contains nodata when the other does not, has a nodata value of -9999 when the other has none;
Modifies the cropped Everest Landsat file to have smaller extent in all directions (see #190);
Updates all occurences of geoutils.datasets into geoutils.examples;
Runs all tests on two examples whenever possible using @pytest.mark.parametrize().

Updating the tests made one bug appear: #286, the related test_info of test_georaster.py is temporarily skipped.
Resolves #117
Resolves #190
With the new tests, found 2 bugs:

The set_ndv function does not update array, opened issue #286;
The crop function has a wrong right bound, opened issue #287.

Thanks for the review. All checks passing, merging! :partying_face:
Not sure it makes any difference for the data repos, I find it fine like that. In any case, we can easily change in the future: it's 2 lines for defining tarball + commit in examples.py, and 5min to create the data repo and copy the data in. A minimal effort now that it is set up.


Unable to correctly sort images with ID going beyond 9999

The sorter is unable to sort images into a specified folder when the list of images being sorted contains filenames/IDs IMG_9999 and IMG_0001. This issue is known to occur with photos taken on an iPhone where they are assigned names from IMG_0001 to IMG_9999. After having taken an IMG_9999, the iPhone camera/photos app will then cycle/loop back to IMG_0001 when the next photo is taken.
For example, if I had 4 images (IMG_9998, IMG_9999, IMG_0001, IMG_0002) and I intended to have them sorted into one folder, IMG_9998 and IMG_9999 will be the included in the specified folder and any other images from IMG_0001 and IMG_0002 will automatically be allocated into a new folder.
If it's possible, instead of having the images sorted based on the image filename/ID, maybe using timestamps of the photos could prevent this issue.

There is now an option available in the GUI to use the dates on images instead of the name for the order.


Forms should be documented in the docusaurus site

Forms were added in #11 but this PR does not include full fledged documentation.

Documentation has been added regarding forms.


JFT issue with text "H&I"

Describe the bug
The JFT is not rendering today due to an ampersand in "H&I".
What version are you running?
2.5.1
Did this happen on prior versions to the one you are running?
Not sure
To Reproduce
Steps to reproduce the behavior:

Go to any fetch-jft.php page.
Page isn't rendering xml.

Expected behavior
Text should show.
Screenshots
N/A
Additional context
N/A

Couldn't repro.


InvalidArgumentError: Unable to find the relevant tensor remote_handle: Op ID: 3940, Output num: 0

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version (use command below):
Python version:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
Describe the expected behavior
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

@Sayanroy1996,
In order to expedite the trouble-shooting process, could you please provide the complete code to reproduce the issue reported here and also the TensorFlow version you are using. Thanks!

I am also getting the same issue, the exact issue is below:
InvalidArgumentError: Unable to find the relevant tensor remote_handle: Op ID: 12, Output num: 0
How can I solve this problem, this is only happening with TPU, with GPU there is no issue.

I also get the same error when trying to work with TPU, when running on GPU I have no problems
InvalidArgumentError: Unable to find the relevant tensor remote_handle: Op ID: 33, Output num: 0

2021년 6월 3일 (목) 20:30, Joost @.***>님이 작성:

I also get the same error when trying to work with TPU, when running on
GPU I have no problems
InvalidArgumentError: Unable to find the relevant tensor remote_handle: Op
ID: 33, Output num: 0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/39296#issuecomment-853796879,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUIQN2DGJIKHCPLZNV2OVBDTQ5RUXANCNFSM4M33UJTA
.


Support for Ember 1.13 / Ember 2

Hey everyone.
I am using ember-select-2 intensively for one of my projects; I'm attempting to update the project and its dependencies all the way up to ember 2, but first we need to pass through ember 1.13 land. :dancers:
Does anyone have any experience with this? Has anyone tried it? Is it worth it?
I'd love to pitch in a hand, but not sure where to start and whether or not it's possible make happen. Is anyone with me?
Thanks!

I'm in ember 1.13 land with no problems. It appears to be fine in 2.0 land except for .fmt() being deprecated.

Is there any plan that this addon is made compatible?
Seems that it gets unsupported? Last commit from June '15

See https://github.com/iStefo/ember-select-2/issues/131

Hey @Kilowhisky - thanks for the direction.
rewrote now the app with a lot of use cases (including some parts where I had to rewrite the select2 component). its quite easy and I could even improve the code a lot with ember-power-select.
nevertheless, thanks for the select2 component. worked great before Ember 2.0.


osgi Bundle activator

Hi btnguyen2k,
how can I implement  BundleActivator class in your ddth-kafka bundle? Do I need to import org.osgi.core libraries?
Thanks.
Marco

Hi @MarcoFierimonte,
Sample of (simple) steps:

You create your own bundle, that imports ddth-kafka.
Implement BundleActivator class in your bundle and initialize needed objects (eg. KafkaClient).

For quick OSGi Bundle testing, you can drop your bundle(s) into a simple OSGi server (https://github.com/DDTH/osgiserver) and see if everything works well.
Regards,
Thanh Nguyen


New version of notary with pkcs11 client integration

Vendoring in new notary version with client-side pkcs11 support.
@jfrazelle took care of all of the building bits that were necessary to have this successfully cross-compile. Thank you Jess!

ouch -- 7,239 additions and 1,854 deletions.
Someone's been busy!

the commits are separated to make it easier

Ping @tianon there a various parts about this that I hate that I hope you have a better solution for but the 2 biggest ones: 1. How to have a dependency in the deb for only experimental, I kinda like how I did it w the rpm but unsure how to do something like that w a control file2. We need a latest clang version for compiling and avoiding clang errors but as you can see their packages don't alias clang-3.8 as /usr/bin/clang 😞Such struggles w this one I hate it all a bit myself

FAIL: docker_cli_push_test.go:235: DockerTrustSuite.TestTrustedPushWithIncorrectDeprecatedPassphraseForNonRoot

yes i know I have informed them

@jfrazelle does the software actually shell out to yubico-piv-tool?  I don't think our dependency on it is quite at the level of Recommends, since it's not actually required for most users, but Suggests sounds pretty appropriate (https://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps for reference).
Until it moves out of experimental, we could do something like we do with putting apparmor into Recommends; ie, https://github.com/docker/docker/blob/9c6e3396ef7ba44837ffaede0345ab3a105e8116/hack/make/.build-deb/rules#L6-L7, so something like:
    echo 'yubico:Suggests=$(shell [ "$DOCKER_EXPERIMENTAL" ] && echo yubico-piv-tool)' >> debian/docker-engine.substvars

there in override_dh_gencontrol and Suggests: ${yubico:Suggests} over in debian/control like https://github.com/docker/docker/blob/9c6e3396ef7ba44837ffaede0345ab3a105e8116/hack/make/.build-deb/control#L15
Is this a tool users of a Yubi are likely to have installed for other Yubi things, or is it something more specific to the way we use the Yubi inside Notary?

Also, if the tool isn't installed and a user attempts to use it for something within Docker, does a nice error message bubble up to the level of the client?

@diogomonica would know better than I but if they have a yubikey but no lib it will just not use the yubikey and create certs on the host
On Thu, Nov 12, 2015 at 6:40 AM -0800, "Tianon Gravi"<EMAIL_ADDRESS>wrote:
Also, if the tool isn't installed and a user attempts to use it for something within Docker, does a nice error message bubble up to the level of the client?
—
Reply to this email directly or view it on GitHub.

It dlopens an so file or dylib depending on architecture so I think recommends? Or whatever you think is best
On Thu, Nov 12, 2015 at 6:40 AM -0800, "Tianon Gravi"<EMAIL_ADDRESS>wrote:
@jfrazelle does the software actually shell out to yubico-piv-tool?  I don't think our dependency on it is quite at the level of Recommends, since it's not actually required for most users, but Suggests sounds pretty appropriate (https://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps for reference).
Until it moves out of experimental, we could do something like we do with putting apparmor into Recommends; ie, https://github.com/docker/docker/blob/9c6e3396ef7ba44837ffaede0345ab3a105e8116/hack/make/.build-deb/rules#L6-L7, so something like:
echo 'yubico:Suggests=$(shell [ "$DOCKER_EXPERIMENTAL" ] && echo yubico-piv-tool)' >> debian/docker-engine.substvars

there in override_dh_gencontrol and Suggests: ${yubico:Suggests} over in debian/control like https://github.com/docker/docker/blob/9c6e3396ef7ba44837ffaede0345ab3a105e8116/hack/make/.build-deb/control#L15
Is this a tool users of a Yubi are likely to have installed for other Yubi things, or is it something more specific to the way we use the Yubi inside Notary?
—
Reply to this email directly or view it on GitHub.

Ok that makes sense, but the tool we're installing isn't the .so, so where
does it fit in?

It includes the so
On Thu, Nov 12, 2015 at 7:44 AM -0800, "Tianon Gravi"<EMAIL_ADDRESS>wrote:
Ok that makes sense, but the tool we're installing isn't the .so, so where
does it fit in?
—
Reply to this email directly or view it on GitHub.

It does?  https://packages.debian.org/sid/amd64/yubico-piv-tool/filelist
:smile:
We probably want that lib package it depends on instead (and in that case
it's just a .so so totally agree that recommends makes more sense).

Shit I think it's their deb package that it's in... :( this could be a problem because we were going to have to build these and I wasn't planning on building that one
On Thu, Nov 12, 2015 at 8:04 AM -0800, "Tianon Gravi"<EMAIL_ADDRESS>wrote:
It does?  https://packages.debian.org/sid/amd64/yubico-piv-tool/filelist
:smile:
We probably want that lib package it depends on instead (and in that case
it's just a .so so totally agree that recommends makes more sense).
—
Reply to this email directly or view it on GitHub.

Because we have to have version 1.1.0
On Thu, Nov 12, 2015 at 8:04 AM -0800, "Tianon Gravi"<EMAIL_ADDRESS>wrote:
It does?  https://packages.debian.org/sid/amd64/yubico-piv-tool/filelist
:smile:
We probably want that lib package it depends on instead (and in that case
it's just a .so so totally agree that recommends makes more sense).
—
Reply to this email directly or view it on GitHub.

Let me look into the lib one making a patch for it so we can get 1.1.0 on like wheezy and jessie etc
On Thu, Nov 12, 2015 at 8:04 AM -0800, "Tianon Gravi"<EMAIL_ADDRESS>wrote:
It does?  https://packages.debian.org/sid/amd64/yubico-piv-tool/filelist
:smile:
We probably want that lib package it depends on instead (and in that case
it's just a .so so totally agree that recommends makes more sense).
—
Reply to this email directly or view it on GitHub.

So close to flipping a table this entire PR is a gigantic nightmare
On Thu, Nov 12, 2015 at 8:04 AM -0800, "Tianon Gravi"<EMAIL_ADDRESS>wrote:
It does?  https://packages.debian.org/sid/amd64/yubico-piv-tool/filelist
:smile:
We probably want that lib package it depends on instead (and in that case
it's just a .so so totally agree that recommends makes more sense).
—
Reply to this email directly or view it on GitHub.

FWIW the rpm installs the so :( so that ones correct
On Thu, Nov 12, 2015 at 8:04 AM -0800, "Tianon Gravi"<EMAIL_ADDRESS>wrote:
It does?  https://packages.debian.org/sid/amd64/yubico-piv-tool/filelist
:smile:
We probably want that lib package it depends on instead (and in that case
it's just a .so so totally agree that recommends makes more sense).
—
Reply to this email directly or view it on GitHub.

This one is what I was going to package for our repo
https://github.com/Yubico/yubico-piv-tool-dpkg
With https://github.com/jfrazelle/repo-pkg
On Thu, Nov 12, 2015 at 8:04 AM -0800, "Tianon Gravi"<EMAIL_ADDRESS>wrote:
It does?  https://packages.debian.org/sid/amd64/yubico-piv-tool/filelist
:smile:
We probably want that lib package it depends on instead (and in that case
it's just a .so so totally agree that recommends makes more sense).
—
Reply to this email directly or view it on GitHub.

@tianon @jfrazelle the yubico-piv-tool is actually necessary for anyone that wishes to check the mode on their yubikey/operate on keys (list, delete, etc)/advanced use cases not covered by docker. I would say that Recommend seems appropriate in this case.
This is something that we can change in the future, as more functionality to manage yubikeys is added onto docker and notary, but for now this seems like the only way to have a decent experience with the yubikeys.
Also, the use of pkcs11 is best-effort, if no .so's are found notary silently ignores it.

Thanks for confirming, Diogo! :heart:
Sounds good enough for me, assuming @jfrazelle can get happy about version
numbers.  Do you want to add a note about version requirements of this to
PACKAGERS.md with this PR?  Our "Recommends" entry should probably encode
the required version too (ie something like "yubico-piv-tool (>= 1.1.0~)").

ok updated w windows fix and also tianons suggestions :) way better than the gross thing i did w install.sh

also updated packagers.md

Very minimal changes to engine side +1
Reviewed vendored in changes, seems OK (nothing horrendous stands out) +1
Tested trusted push/pull functionality (minus yubikey) +1
Tested trusted push/pull going back to 1.9.0 client +1
Soft LGTM

@cpuguy83 I have one for you. You can test it in Barcelona :)

I've tested the following cases, both with a mac binary that I built on a mac using the same method as homebrew, and with a mac binary that @diogomonica built on linux using make cross.

pull/push with yubikey and DOCKER_CONTENT_TRUST=1
pull/push without yubikey and DOCKER_CONTENT_TRUST=1
push/pull without DOCKER_CONTENT_TRUST

Have not tested on Linux.  LGTM as far as macs are concerned :)

Tested pushing and key rotation with yubikey and all seemed to work. LGTM (no review of the packaging).

@tianon would love your explicit LGTM, since this involves building magic.

You need mine too ;)

@jfrazelle would love your explicit LGTM, since this involves building magic.

@diogomonica :metal:
I won't say how long it took me to find that emoji keyword.

LGTM

I really wish this PR could've been in smaller chunks -- it's very hard to review being so massive. :cry:
(I almost didn't even look at c86517e557c93c8cbb26305704d91409dd207e39 because it didn't sound related to building, but glad I did.)

yeah sorry I specifically hated the sym,ink of clang in that one :(

there are def aspects of this PR I hate, it blows

Ok, latest iteration LGTM

No docs required as far as I can tell.


Tabs inside tabs not working properly

@junaidbhura Tabs inside tabs are not working properly.
Here is the example code.
<tp-tabs current-tab="tab-1" update-url="yes">
	<tp-tabs-nav>
		<tp-tabs-nav-item active="yes">
			Tab 1
		</tp-tabs-nav-item>
		<tp-tabs-nav-item>
			Tab 2
		</tp-tabs-nav-item>
		<tp-tabs-nav-item>
	</tp-tabs-nav>
	<tp-tabs-tab id="tab-1" open="yes">

Tab 1: Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

		<tp-tabs current-tab="tab-a" update-url="yes">
			<tp-tabs-nav>
				<tp-tabs-nav-item active="yes">
					Tab A
				</tp-tabs-nav-item>
				<tp-tabs-nav-item>
					Tab B
				</tp-tabs-nav-item>
				<tp-tabs-nav-item>
			</tp-tabs-nav>
			<tp-tabs-tab id="tab-a" open="yes">

Tab A: Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

			</tp-tabs-tab>
			<tp-tabs-tab id="tab-b">

Tab B: Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

			</tp-tabs-tab>
		</tp-tabs>
	</tp-tabs-tab>
	<tp-tabs-tab id="tab-2">

Tab 2: Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

	</tp-tabs-tab>
</tp-tabs>

Thanks @sagarjadhav - @KhokanTP is going to pick this up!

@sagarjadhav @KhokanTP this is released: https://github.com/Travelopia/web-components/releases/tag/0.6.8


715: ecommerce pressing pay jumps back to dashboard without focus on alert

Pre-Flight checklist

[x] Testing

[x] Changes have been manually tested

What are the relevant tickets?
https://github.com/mitodl/hq/issues/715
What's this PR do?
Updates bootstrap and reactstrap in order to improve accessibility of alerts for users with screen readers (refer to associated issue).
How should this be manually tested?

Ensure that you can focus on the close button of alerts when using only the keyboard to navigate.
When an alert is triggered, ensure that the alert is read via screen reader.
When an alert is triggered, ensure that the focus is set to the alert before any other item on the page (after pressing "Skip to main content".
While running this branch locally, visit each page of the application and compare it with RC to ensure that the UI is the same between both.  I did not supply screenshots as this change should not change the current UI in any way.

Additional comments
Use the commits and their comments to help understand what each change in the PR does.

Codecov Report

Merging #1537 (2ca6d63) into main (1168188) will increase coverage by 2.78%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1537      +/-   ##
==========================================
+ Coverage   82.48%   85.26%   +2.78%
==========================================
  Files         315      149     -166
  Lines       13528     4472    -9056
  Branches      953        0     -953
==========================================
- Hits        11158     3813    -7345
+ Misses       2103      659    -1444
+ Partials      267        0     -267

Impacted Files
Coverage Δ

frontend/public/src/components/EnrolledItemCard.js
48.48% <ø> (ø)

...end/public/src/components/NotificationContainer.js
100.00% <ø> (ø)

frontend/public/src/components/OrderSummaryCard.js
10.25% <ø> (ø)

...end/public/src/components/ProgramCourseInfoCard.js
16.66% <ø> (ø)

frontend/public/src/components/TopAppBar.js
100.00% <ø> (ø)

frontend/public/src/components/UserMenu.js
100.00% <ø> (ø)

...blic/src/components/forms/AddlProfileFieldsForm.js
53.84% <ø> (ø)

...end/public/src/components/forms/ApplyCouponForm.js
100.00% <ø> (ø)

...end/public/src/components/forms/ChangeEmailForm.js
100.00% <ø> (ø)

.../public/src/components/forms/ChangePasswordForm.js
100.00% <ø> (ø)

... and 13 more

... and 166 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Adjust width total bar

Is there a simple way to adjust the width of the total bar? Now it overlaps my icons on desktop.

I'm not sure I understand your question. simple-bar is drawn by Übersicht at the lowest layer level just on top of the desktop. You could simply drag you icons a bit farther from the top of your screen.
Let me know I you need any more help about this.


Revert to source link

@helins I reverted the source icon to a  again. I had doubts about the source icon myself for a while, I found it too big and drawing too much attention to itself. After asking I second opinion I got:

the source link is way better
I have no clue what the icon means before I click on it, plus it's big

If you still want to preserve the icon, we could make this an option or so.


[WIP] Cascading Hot-reload / build script for Solidity

Hey again, Lattice,
I played around with making a hot-reload script for solidity files and downstream dependencies utilizing turbowatch.
I produced a couple of different branches experimenting with the Chokidar file watching backend. I've chosen to focus my efforts on said backend mainly due to its ability to ignore paths and not index the entire project.
The branch with the present draft pull request is the first and better working branch with a more simple, stupid approach. It watches all packages and saves each package build time to a map. The map guarantees that no single package is built twice in a row in under a constant time span of seconds. The intention originally was to stop infinite build loops.
My second, less successful, and more complicated approach is this branch, which utilizes a forked turbowatch to take advantage of Chokidars' "unwatch" and "add" functions and adds the ability to pass an additional function to the spawn to run on process kill. Unfortunately, saving a file in rapid succession seems to break reactivity / listening of the file, which I hoped to prevent with the introduction of the the mentioned changes. I included this dysfunctional branch as I think it is interesting and maybe it will spark some ideas.
While I don't like the idea of arbitrary waits in programs, and processes not being able to react to an event based system, I recognize that the simple approach might be working. I think the simple stupid approach might be worth a review or a glance since it seems to achieve hot-reload + cascading builds for solidity.
How to run Turbowatch
ROARR_LOG=true npx turbowatch in project directory to run turbowatch in either branch.
Plays along with another terminal running pnpm run dev, the watch fighting will cause a few additional package builds but no infinite build loops as far as I know.
Other considerations
If this approach for solidity hot-reload is appreciated, maybe it might be worth looking into making turbowatch responsible for typescript files to reduce redundant builds with fighting watch tasks.
I will clean up git history if branch is decided valuable.

thank you for this @Handfish! Could you elaborate on the advantages of this approach versus something like using forge build --watch in a dev script in the solidity packages? The approach in this PR also seems to require manually keeping turbowatch.ts up to date with packages, could that be automated?
I'm going through all PRs right now with the goal of either merging or closing them to reduce the number of open/stale PRs, so I'm gonna close this one for now, but feel free to reopen if you intend to continue working on it.


Queue type isn't thread safe

Python provide several queues implementation as queue, asyncio.queue and multiprocessing.queue.
Due Python features we will provide several dispatcher which one may be more appropriate than the other depending on the scenario. This way the queue being used and all logic around it must take into account this different execution scenarios and yet be simple to understand

Right now there is used asyncio.Queue https://github.com/AsynkronIT/protoactor-python/blob/b296de864d216ea5b90b6512e72d7e50eb03d72b/protoactor/mailbox/queue.py#L2 . I couldn't find other queues in project.
Also as mentioned in this issue : https://github.com/AsynkronIT/protoactor-python/issues/25 we can focus on one working process where standart queue is thread safe.


UITests: "Failed to import bridging header"

"Failed to import bridging header" when trying to run UITests with XCode 7.1and Swift

Maybe you didn't add files to test target.
Also take a look at #143 that covers 2 ways of Swift integration.


parent() api does not return children in shallow rendering

I am trying to get the second child element from the parent and it fails. Below is the example:
Component:
class TestComponent extends React.Component {
  render() {
    return (

            Hello world!

            Hello world!

            Hello world!

            Hello world!

    );
  }
}

TestComponent.displayName = 'TestComponent';

export default TestComponent;

Test:
it('renders parent1 children', () => {
    const wrapper = shallow(<TestComponent />);

    const child1 = wrapper.find('#child1_1');
    const parent1 = child1.parent();
    expect(parent1).to.have.className('parentOne');

    const child12 = parent1.childAt(1);
    expect(child12).to.have.className('childTwo');
  });

The second assertion fails with the below error message:
AssertionError: expected the node in <TestComponent /> to have a 'childTwo' class, but it has undefined

And when I log parent1.children(), I get ShallowWrapper { length: 0 }.
Strangely, expect(child12).to.be.present(); passes.

I'm having the same issue with Enzyme 3 (was working with Enzyme 2):
test('parent() vs parents()', () => {
  const H1 = () => (

  );

  const root = shallow(

  );

  console.log('root:', root.debug());

  const h1 = root.find(H1);
  console.log('h1.parent():', h1.parent().debug());
  console.log('h1.parents():', h1.parents().debug());
});

Output:
    root:

    // ===> Something wrong:
    h1.parent():

    //

    h1.parents():

To sum-up child.parent() does not contain its children while child.parents() does.

@tkrotoff @VidyullathaKandipati what version of react are you both using?

I am using react: 15.6.2 and enzyme-adapter-react-15: 1.0.1

React 16.0.0 + enzyme-adapter-react-16 1.0.1

I am also having this issue with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

I have tests that pass for Enzyme v2. They do the following:
wrapper.find('label[htmlFor="something"]').parent().children().at(1).text()

Now it does not pass anymore in v3. What should I do? I'm just checking the text of the label's sibling (that is not inside any particular tag).

@nbkhope try adding .hostNodes() after .children()?

@ljharb
ShallowWrapper::getNodes() is no longer supported. Use ShallowWrapper::getElements() instead

I tried getElements(), but it returns an empty list. But I went from child to parent and the parent exists, so how can there be no children?

I was kind of reluctant to upgrade to v3 right away, but decided to give it a try. Now am kind of reluctant again. Anyway, I can make my tests pass using the .parents() like so:
// before
wrapper.find('label[htmlFor="something"]').parent().children().at(1).text()

// after
wrapper.find('label[htmlFor="something"]').parents().at(0).children().at(1).text()

Please fix that issue :)

If you start with wrapper.find('label[htmlFor="something"]').hostNodes(), does that help?

@ljharb that does not seem to do anything.
Doing wrapper.find('label[htmlFor="something"]').hostNodes().parent() returns the parent, but then appending a .children() yields nothing:
console.log(wrapper.find('label[htmlFor="something"]').hostNodes().parent().children())
// => ShallowWrapper { length: 0 }

Gotcha, thanks - that seems to be the OP's issue as well.

Seeing similar issue with<EMAIL_ADDRESS><EMAIL_ADDRESS>const Cmp = () => (

      FOO

BAR

);

const wrapper = shallow(<Cmp />);
console.log(wrapper.debug());
console.log('h1 parent text:', wrapper.find('h1').parent().text());
console.log(wrapper.find('h1').parent().debug());

Output:

    FOO

      BAR

h1 parent text:

I would expect .text() not to return a blank string, and for .parent().debug() not to show an empty
 tag.

This has been resolved; as the tests in #769 indicate.
Please file a new issue if not.


Update the README page and the RELEASES sections

Let's make more clarity on what we release for Elemental and where.

This is likely just a subtask of #361


Enforce isUser in withSessionAuthenticationForWorkspace

Description
Enforce isUser in withSessionAuthenticationForWorkspace unless allowUserOutsideCurrentWorkspace is set as option.

Remove all unnecessary call to isUser in internal endpoints
Move to call to getNonNullable methods in all endpoints

For Dust Apps:

We allow external users for:

/w/[wId]/apps/[aId]/index.ts (only public apps are returned if not Builder)
/w/[wId]/apps/[aId]/clone (cloning logic)
/w/[wId]/apps/[aId]/runs/[runId]/status (access to the stored run status of public apps)
/w/[wId]/apps/[aId]/runs/[runId]/blocks/[type]/[name] (access the stored block statuses of public apps)

This is for displaying public/unlisted dust apps (so that they can be cloned)
We don't need it on

`/w/[wId]/apps/[aId]/runs/index.ts

As we are part of the dust-apps workspace, so we have access to runs and we can get other workspace runs because we hare super users.
Only one endpoint below w/[wId] does not use withSessionAuthenticationForWorkspace: data_sources/[name]/documents/index.ts because it's shared by poke. Follow-up actions, cut a different endpoint in poke.
Also the dataset part public dust apps is quite broken. Will fix in subsequent PR. Here we are being restrictive.
More notes:
Suspect we don't use ` anymore
Risk
High - Authorization tweaks
Deploy Plan

deploy front

@philipperolet fixed the comment + replied to your comment which is everywhere the same response :) PTAL


Need to kill GPM via task manager after using "Reset & Close application" button.

This isn't a big issue, but when using the "Reset & Close application" button, I needed to find GPM in the task manager & kill it before GPMDP would open again.
screencaps

I think I'm just going to remove this button altogether, not very useful and far too much hassle


Remove MigrationUtil

Motivation:
I found out MigrationUtil is not used anymore that is intruced token migration in #133.
Modifications:

Remove MigrationUtil
Move initialization logic to ProjectInitializer
Clean up some logs in ZooKeeperCommandExecutor

Result:

Less code

Thanks for reviewing. 😉


How to use navigation components with multi-Module application and BottomNavigationView

https://stackoverflow.com/questions/54616996/android-navigation-component-and-bottomnavigationview-in-a-multi-module-application
I am facing extract same circumstance here... trying to create a multi-module application where every feature is a standalone library (module). Single activity pattern is applied throughout the project, created different navGraphs for different modules and included them in app's navGraph, but can't make it work.
could anyone give me some ideas? Thank you!

@LLin233  You can create a module "navigation" and move your graph(s) there.
References to Fragments will be in highlighted red but it compiles and it works.
All your feature modules can take that navigation as dependency in order to access the safeArgs (if you are using them) and the actions.

@damienlo is this method still the preferred way? or any other better options are available now?

as an addition to @damienlo fix, you can do a "gradle hack" to copy the resources from the navigation module to app module (assuming it has access to all feature modules), this way the fragment names won't be highlighted as red.
credits to @eyal-lezmy in this talk (skip to 44:00):
https://www.droidcon.com/media-detail?video=334638906

First create a new package under main in your navigation module called "sharedRes", and move the navigation resource folder with the navigation graphs xml into it.
in the app's build.gradle add
android { sourceSets.debug.res.srcDirs += "$rootDir/navigation/src/main/sharedRes"}}
in the navigation module's build.gradle add
android {  sourceSets.main.res.srcDirs += "$rootDir/navigation/src/main/sharedRes" }
clean build and rebuild.

If I remember well this hack is not "working" anymore with the rendent versions of Android Studio. But in our project we end up using a symbolic link to duplicate the file in both modules.

@eyal-lezmy weird, it is working correctly on our project, using the latest version of navigation component library and android studio 4.1.1.

@engi2nee Can you explaine what does it do?

@P1NG2WIN Refer the video at 44:00. It is discussed what it does behind the scenes.


Add information about ceiling

minimumHealthCapacity is rounded up but there is no information about this in the docs.

Anders Engström [8:53 AM]: quick question: minimumHealthCapacity - how is “rounding” performed. If I have 3 tasks, and specify 0.7 as minimumHealthCapacity (== 2.1) does that mean that 2 tasks are kept healthy, or is it “ceiled” to 3 (effectively the same as minimumHealthCapacity: 1)?
https://mesos.slack.com/archives/C1L7D22KY/p1511942026000098

@sascala Can you take a look at this?

@janisz thanks for improving our documentation!

thanks @janisz !


Remove system() call for iOS and tvOS

iOS and tvOS don't support system().
Wrapping in these ifdef's seems to solve the issue and I haven't seen any ill side effects.

Properly replacing would probably require using "posix_spawn" or NSTask, but given that my_system is only called for WIN32 message or Zimar plugins DllConfig, ifdef is good enough.


[BUG] Long tweets contain a link in tweet cards

The same problem exists in Fritter. However, Nitter is not affected by this issue. I wanted to open an issue for this error

Should be fixed in v2.1.0

However, long tweets continue to be missing in the content section. I guess it won't be much of a problem.
However, quoted tweets and tweets showing link content are not displayed correctly in the stream.

This issue still exists in Fritter but for some reason is reported that has been fixed, https://github.com/jonjomckay/fritter/issues/644#issue-1599813900 , https://github.com/jonjomckay/fritter/commit/6df541c9fc6cf3fd3a7ae8a66894ec4515362c23 maybe you could check the changes and maybe find a way to fix this @TheHCJ @j-fbriere

I cannot reproduce the issue on the last ci build of Quacker. It has been fixed.
I checked with the Fritter issue #644 referenced in your comment.
Could you install the apk file of the last ci build of Quacker and try again?

Long tweets are not shown also to regular(non-blue) tweeter users
Example3:
Long tweet on Quacker feed: https://imgur.com/a/T7Yecyw
Long tweet expanded: https://imgur.com/a/OSi8yzc
Long tweet on Quacker account wall: https://imgur.com/a/7udnAEg
Long tweet on Fritter account wall: https://imgur.com/a/BPFydmD

@TheHCJ This is the fix for the long tweets (notes) in feeds.
fix_14.patch
@AndiDink00x Note that the long tweets are displayed only in feeds, NOT in the tweets of a subscription.
This is normal behavior if you compare with Twitter itself by browsing for instance https://twitter.com/Navsteva.
You'll see that the long tweet starting with A group of NATO countries is in its short form.

@j-fbriere You're right and im also interesting for long tweets to be displayed only on feed, anyway thank you

Should be fixed with the last ci build.

@j-fbriere @TheHCJ you guys rock!! i confirm that this issue is fixed maybe this should be closed as "fixed in next release"


KeyError being raised when calling GazetteerCache calls unindex

Overview
When the GazetteerCache attempts to incrementally update the in-memory model using historical records, a call to unindex is raising a KeyError.
Demo
An example trace recovered from production item 110331
    "trace": "Traceback (most recent call last):
 File
    \"/usr/local/src/api/views.py\", line 1067, in create
 match_results =
    match_item(country_code, name, address, item.id)
 File
    \"/usr/local/src/api/matching.py\", line 370, in match_item

    recall_weight=recall_weight)
 File \"/usr/local/src/api/matching.py\", line
    255, in match_items
 gazetteer = GazetteerCache.get_latest()
 File
    \"/usr/local/lib/python3.7/contextlib.py\", line 74, in inner
 return
    func(*args, **kwds)
 File \"/usr/local/src/api/matching.py\", line 447, in
    get_latest
 'address': clean(item['address']),
 File
    \"/usr/local/lib/python3.7/site-packages/dedupe/api.py\", line 881, in
    unindex
 field)
 File
    \"/usr/local/lib/python3.7/site-packages/dedupe/blocking.py\", line 83, in
    unindex
 index.unindex(preprocess(doc))
 File
    \"/usr/local/lib/python3.7/site-packages/dedupe/tfidf.py\", line 24, in
    unindex
 i = self._doc_to_id.pop(doc)
KeyError: ('viyellatex',
    'limited')
",

Another unindex example, but a different stack trace. Recoverd from production item 110211
     "trace": "Traceback (most recent call last):
  File \"/usr/local/src/api/views.py\", line 1067, in create
    match_results = match_item(country_code, name, address, item.id)
  File \"/usr/local/src/api/matching.py\", line 370, in match_item
    recall_weight=recall_weight)
  File \"/usr/local/src/api/matching.py\", line 255, in match_items
    gazetteer = GazetteerCache.get_latest()
  File \"/usr/local/lib/python3.7/contextlib.py\", line 74, in inner
    return func(*args, **kwds)
  File \"/usr/local/src/api/matching.py\", line 447, in get_latest
    'address': clean(item['address']),
  File \"/usr/local/lib/python3.7/site-packages/dedupe/api.py\", line 881, in unindex
    field)
  File \"/usr/local/lib/python3.7/site-packages/dedupe/blocking.py\", line 83, in unindex
    index.unindex(preprocess(doc))
  File \"/usr/local/lib/python3.7/site-packages/dedupe/tfidf.py\", line 25, in unindex
    self._index.unindex_doc(i)
  File \"/usr/local/lib/python3.7/site-packages/zope/index/text/textindex.py\", line 57, in unindex_doc
    self.index.unindex_doc(docid)
  File \"/usr/local/lib/python3.7/site-packages/zope/index/text/baseindex.py\", line 176, in unindex_doc
    self._del_wordinfo(wid, docid)
  File \"/usr/local/lib/python3.7/site-packages/zope/index/text/baseindex.py\", line 312, in _del_wordinfo
    del doc2score[docid]
KeyError: 7571
",

Here is where the in-memory gazetteer is updated
https://github.com/open-apparel-registry/open-apparel-registry/blob/2b48bd07193dad20af191af018414cb9fc5a124c/src/django/api/matching.py#L418-L463
This is the loop where each facility history record is processed
https://github.com/open-apparel-registry/open-apparel-registry/blob/2b48bd07193dad20af191af018414cb9fc5a124c/src/django/api/matching.py#L418-L463
If there is an exception while this loop is processing, the _cls.version is not updated even though some of the records may have been processed successfully. The next call to GazetteerCache.get_latest will then try an reprocess the same history records. It makes sense that we would see errors if we attempted to unindex the same record multiple times.
We can address this, at least in part, by moving the updating of cls._version inside the loop. I am concerned though, that this will leave the matcher "stuck" at a history record it can't apply. We will need some way to cope with this. The brute force method would be rebuilding from scratch.

Reopening because this appeared at lease 3 more times during testing on staging
https://rollbar.com/OpenApparelRegistry/OpenApparelRegistry/items/543/
https://rollbar.com/OpenApparelRegistry/OpenApparelRegistry/items/544/
https://rollbar.com/OpenApparelRegistry/OpenApparelRegistry/items/545/


asset_content_type documentation

Hi! I can't find any clear documentation about the asset_content_type field -- what the options are, what this does etc.
If there is some documentation in another place, maybe it'd be worth linking to it in the readme?
Sorry if there's been an existing issue for this -- I couldn't find any.

Any appropriate MIME type associated with the asset should work for asset_content_type field.
Common MIME types associated by type of documents can be found here:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types

Thanks for the link, scouring everywhere for documentations on the inputs... they only document one of the four.


Fix for #3 Firefox MacOS paste problem

Changes Unknown when pulling 73de95795640925201a32b5b127f2515dd0991a8 on stereobooster:master into ** on jcubic:devel**.

Sorry to bothering you again but can you modify -src.js? the 1.0.6 will be overwritten by make.

I can add that fix myself but since you came up with fix you should be on the list of contributors on github.

I've been told this change breaks some things. I tested it only in firefox, though

This breaks the TAB-completion on safari as well as the Backspace key. On chrome it looks that with C-c / C -v pastes twice...

Unfortunetly I don't have a Mac, can you test this codepen on a Mac, for the backspace and TAB and tell me what the results are?
As for C-v it was broken in all browsers, it should work again now.

Tested in VirutalBox and Tab Backspace and paste work.


FilterChain Discovery Service (FDS)

In order to support filter chain updates without forcing a full listener drain, it's been suggested we add a FilterChain Discovery Service. This would allow individual FilterChains belonging to a Listener to be independently discovered and updated.
This would also lend support to finer grained Listener resource naming for incremental and on-demand xDS (generalizing https://github.com/envoyproxy/envoy/issues/2500).
Opening this issue to track any design work and ownership.
@ggreenway @andraxylia @lizan @PiotrSikora @mattklein123

We need this fix for Istio for long-lived connections with SNI @rshriram @costinm .

Related add-on feature: lazy-loading of FilterChains, triggered by a listener-filter that is watching for unknown SNI values.

@htuch does the drain happen when a particular FilterChain is updated, and also when any FilterChain is added or deleted in the listener?

We need this fix for Istio for long-lived connections with SNI

@andraxylia the intention here is to only effect new connections, right? Obviously previous connections will use the old filter chain? I just want to make sure we are on the same page. If so this sounds like a useful and straightforward feature to me.

@mattklein123 All is good if a change in the FilterChain  does not affect existing TCP and GRPC connections - for instance the addition of a host in server_names in the FilterMatch.
@rshriram @costinm told me that because of issues with full drain we cannot move Istio from multiple listeners to 1 listener with multiple FilterChains.

Ack: working on this

@silentdai would you be able to post a brief status update on this issue for followers. Thanks. Dave

#7152 #7246 are the preparation. Not a real fdcs thing but share the motivation that decouple the filterchain and listener flow.
I have several draft PRs on benchmark and FCDS proto. Blocked by #7246
I also have draft design doc supposed to publish by the end of this week.

One more thing to consider as part of this work is decoupling of filter chains from the filter chain matchers. This would not only help with the future on-demand work, but it would also allow multiple filter chain matchers to match to a single filter chain, instead of having separate instances of filter chains for each matcher, since those can be exact copies in some cases.

fwiw, for our use case it would be great to allow multiple matchers to refer to the same chain and avoid the extra copies.

@mattklein123 @lambdai do you think this is needed for 1.12.0 or can we do this as a v3 add-on once shipped?

Add on is fine with me.

I was curious about time-line on this feature (FDS). Looks like lot of work is already committed.

@lambdai thank you for your work on this! It looks like the result may have landed in 1.15.0. Am I mistaken?
listener: added in place filter chain update flow for tcp listener update which doesn’t close connections if the corresponding network filter chain is equivalent during the listener update. Can be disabled by setting runtime feature envoy.reloadable_features.listener_in_place_filterchain_update to false. Also added additional draining filter chain stat for listener manager to track the number of draining filter chains and the number of in place update attempts.

@htuch will this support on-demand filter-chain, based on SNI or similar param

We've pivoted towards not doing filter-chain discovery, instead relying on improvements to LDS update (i.e. drainless updates) and ECDS. I'm going to close this out, as I think the original goals we were shooting towards are satisfied by the aforementioned. Feel free to reopen if this is not the case.

Perhaps a goal that I should have mentioned sooner and the reason I've been tracking this issue is to reduce the blast radius of a LDS NACK. My current NACK handling breaks up Resources into individual DeltaDiscoveryResponses to see which of the Resources produced the NACK and not resend it. This works well for granular resources like SDS, EDS, and CDS which may only affect a single service.
A LDS NACK affects every service with traffic flowing through its port. For me that's thousands of services on a single compute cluster

@phylake what typically causes these NACKs? I'm wondering if you move to ECDS whether enough of the config is out of the Listener resource that this will make a material difference. If not, maybe we should reopen.

I think the original goals we were shooting towards are satisfied by the aforementioned. Feel free to reopen if this is not the case.

We will never have on-demand update of filter chain.

Have you considered doing more extensive validation offline or via canary? I think what you describe is a valid reason to have finer grained resources in the model, but other mechanisms to ensure that NACK is unlikely to happen will pay off more broadly.

 If everything is on-demand, can u please make this also.

I'd like to revisit this after unified filter chain matcher is adopted in istio.
That API enforces the filter chain name. This change greatly reduced the complexity of FDS

I see a few benefits of developing FCDS.

It Allows us modeling customizations built into a single listener.
Example:
Listener
FilterChain1: Some unique rules in fcd1.conf
FilterChain2: Some unique rules in fcds2.conf
...
Support breaking a single LDS file into more manageable multiple FCDS files. Imagine these FCDS files holding several lines (1K+) of envoy yaml.
Filter Chain discovery & FilterChain Only updates (This feature exists as I understand in the lds itself)
Filter chains can be loaded/unloaded on demand. This way all of the Filter Chains need not be held in process memory.
Any other benefit?

Is this feature actively worked on?

Folks, this is the implementation PR for FCDS (SoTW). Plz review.
Pending work:

To tests and possible hook some more changes for FC level connection draining.
Delta updates for FCDS


Returning null when trying to attempt login

I'm using the code to login with guard api provided here.
When I try to debug $cognitoClaim, it is null.
Also an error I get when debugging is
Error executing "AdminInitiateAuth" on "https://cognito-idp.us-east-1.amazonaws.com"; AWS HTTP error: cURL error 77: error setting certificate verify locations: ▶
      CAfile: /Applications/MAMP/Library/OpenSSL/cert.pem\n
      CApath: none (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://cognito-idp.us-east-1.amazonaws.com

Using Laravel 8, package version 1.0.0, PHP 8.0.3.
Email passed exists in the local database.
What are reasons behind this?

This was an issue with a local certificate using MAMP. All good now.


Many error after my bot say is logged in. I can't show you all error because the windows console is full.

result = handler.capture(**kwargs)
File "C:\Python27\lib\site-packages\raven\events.py", line 65, in capture
capture_locals=self.client.capture_locals,
File "C:\Python27\lib\site-packages\raven\utils\stacks.py", line 332, in get_stack_info
f_vars = get_frame_locals(frame, transformer=transformer)
File "C:\Python27\lib\site-packages\raven\utils\stacks.py", line 195, in get_frame_locals
v = transformer(v)
File "C:\Python27\lib\site-packages\raven\events.py", line 32, in transform
return self.client.transform(value)
File "C:\Python27\lib\site-packages\raven\base.py", line 477, in transform
string_max_length=self.string_max_length)
File "C:\Python27\lib\site-packages\raven\utils\serializer\manager.py", line 94, in transform
return serializer.transform(value, **kwargs)
File "C:\Python27\lib\site-packages\raven\utils\serializer\manager.py", line 78, in transform
logger.exception(e)
File "C:\Python27\lib\logging_init_.py", line 1192, in exception
self.error(msg, *args, **kwargs)
File "C:\Python27\lib\logging_init_.py", line 1185, in error
self.log(ERROR, msg, args, **kwargs)
File "C:\Python27\lib\logging_init.py", line 1278, in log
self.handle(record)
File "C:\Python27\lib\logging_init.py", line 1288, in handle
self.callHandlers(record)
File "C:\Python27\lib\logging_init_.py", line 1328, in callHandlers
hdlr.handle(record)
File "C:\Python27\lib\logging_init_.py", line 751, in handle
self.emit(record)
File "C:\Python27\lib\logging_init_.py", line 874, in emit
stream.write(fs % msg)
File "C:\Python27\lib\site-packages\colorama\ansitowin32.py", line 40, in write
self.__convertor.write(text)
File "C:\Python27\lib\site-packages\colorama\ansitowin32.py", line 141, in write
self.write_and_convert(text)
File "C:\Python27\lib\site-packages\colorama\ansitowin32.py", line 169, in write_and_convert
self.write_plain_text(text, cursor, len(text))
File "C:\Python27\lib\site-packages\colorama\ansitowin32.py", line 174, in write_plain_text
self.wrapped.write(text[start:end])
KeyboardInterrupt
Original exception was:
Traceback (most recent call last):
File "pokecli.py", line 493, in
main()
File "pokecli.py", line 127, in main
report_summary(bot)
File "pokecli.py", line 136, in report_summary
metrics.capture_stats()
File "C:\Users\cackbone\Desktop\pokebot\pokebot\pokemongo_bot\metrics.py", line 76, in capture_stats
response_dict = request.call()
File "C:\Users\cackbone\Desktop\pokebot\pokebot\pokemongo_bot\api_wrapper.py", line 106, in call
result = self._call()
File "C:\Users\cackbone\Desktop\pokebot\pokebot\pokemongo_bot\api_wrapper.py", line 63, in _call
return PGoApiRequest.call(self)
File "c:\users\cackbone\desktop\pokebot\pokebot\src\pgoapi\pgoapi\pgoapi.py", line 210, in call
request.activate_signature(lib_path)
File "c:\users\cackbone\desktop\pokebot\pokebot\src\pgoapi\pgoapi\rpc_api.py", line 85, in activate_signature
self.signature_lib = ctypes.cdll.LoadLibrary(lib_path)
File "C:\Python27\lib\ctypes_init.py", line 443, in LoadLibrary
return self.dlltype(name)
File "C:\Python27\lib\ctypes_init.py", line 365, in init
self._handle = _dlopen(self._name, mode)

are you already login or not?
please refer to this #2683

#2768

https://github.com/PokemonGoF/PokemonGo-Bot/issues/2780


[RD] View Elevate commitment on Elevate Information widget

Critical Changes
Changes
We updated the Elevate information widget with a link to the Elevate commitment.
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

Tracking W-8442739

Tracking W-8442739

@RadSFDeveloper @andrewyu-salesforce Ready for your review.
@sam-knox @mattwashington Please review the Change description.
Thanks all!

@RadSFDeveloper @andrewyu-salesforce Ready for your review.
@sam-knox @mattwashington Please review the Change description.
Thanks all!

Thanks @npsp-reedestockton , here are code review comments. I am going to test now and check how it work on a scratch org.

I have tested on the dev env, and it works fine.

Thanks @npsp-reedestockton , here are code review comments. I am going to test now and check how it work on a scratch org.

I have tested on the dev env, and it works fine.

@RadSFDeveloper Thanks for the great code review comments!  All of the feedback is implemented now, and ready for another review.

@RadSFDeveloper Thanks for the great code review comments!  All of the feedback is implemented now, and ready for another review.

@npsp-reedestockton , can you please check into `RD2_ElevateInformation_TEST failing tests?

@npsp-reedestockton , can you please check into `RD2_ElevateInformation_TEST failing tests?


display legacy ids in backoffice details pages

displays legacy id field when set
upgrades RJSF to latest and enables ArrayFieldTemplate override
fixes to providers cmps

Tested details pages, searches and that when editing via form the legacy id is kept.


validate log_bog_logs inputs againts schema

Should the PR summary be "validate log_boot_logs inputs against schema"?

Thanks for pointing this out


while_loading doesn't work with external Hyperloop::Component

The following doesn't appear to work.
class LoadingComponent < Hyperloop::Component
  render do
    DIV do
      'Loading...'
    end
  end
end

class MainComponent < Hyperloop::Router::Component
  render do
    FORM do
      INPUT(defaultValue: User.find_by_first_name('Lily').last_name)
    end
    .while_loading do
      LoadingComponent {}
    end
  end
end

Appears to have something to do with an INPUT's defaultValue.

while_loading also doesn't appear to work when rendering a state variable that depends on data. (Possibly related?)
class LoadingComponent < Hyperloop::Component
  render do
    SPAN { 'loading...' }
  end
end

class MainComponent < Hyperloop::Component
  state last_name: nil

  before_mount do
    mutate.last_name User.find(1).last_name
  end

  render do
    DIV do
      state.last_name
    end
    .while_loading do
      LoadingComponent {}
    end
  end
end

@aberios okay the first case will be closed shortly, but the second case is may be more difficult, as it will require changing the semantics of mutate to be more intelligent, not a bad idea at all, but should be done with some thought.
Meanwhile if you needed to do the second case it could be rewritten like this:
class LoadingComponent < Hyperloop::Component
  render do
    SPAN { 'loading...' }
  end
end

class MainComponent < Hyperloop::Component
  before_mount do
    ReactiveRecord.load do
      User.find(1).last_name
    end.then do |last_name|
      mutate.last_name last_name
    end
  end

  render do
    if state.last_name
      DIV { state.last_name }
    else
      LoadingComponent {}
    end
  end
end

The thing is this second case is really not needed, as your active record model data is already using reactive states, so having the "state.last_name" is just a redundant copy of User.find(1).last_name
It could be the case that you want to have a state like state.user that gets updated by some event change, and that would work fine.


Snapshot-delete action / retention policy in Sunstone

Author Name: Kiran Ranjane (Kiran Ranjane)
Original Redmine Issue: 2634, https://dev.opennebula.org/issues/2634
Original Date: 2014-01-13

As we have snapshot-create action in one, so we should also have snapshot-delete action in schedule action tab in Sunstone.
It is really frustrating when we have to delete the snapshots one by one on each vm.
The snapshot-delete action should have a retention policy when defined for example: "1 week" then it should keep all the snapshots that are within 1 week and rest should be deleted.

Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2014-01-17T09:03:36Z

Moving temporarily it to Request track

Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2014-02-04T14:37:34Z

This requires some support from oned. Moving it to backlog. THANKS for your feedback

Closing as duplicate for #1548


Feature/263541 landing page

## WHAT
[FE] Update Landing page
## WHY
https://c5qcgij075a.sg.larksuite.com/base/KMusbYyPXamBwYs0tQNl9ZREgld?table=tblqPvBWouRYz76w&view=vewGXMNZGI
## NOTES

This MR is solid and can be merged

:tada: This PR is included in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Label and Filter System

Add fields of labels in the pitch prevalence tab, with option to filter by section/phrase levels. See sheet below.
https://docs.google.com/spreadsheets/d/10U90QUdd9yzA5lG6xhseCevKKMHmf9l35kOG8GroAwk/edit#gid=0
We'll want to think about adding details to the queries (but we'll come back to that). But for example, to show sargam, tabluation, and different section and phrase details.

Your template makes perfect sense for when the "phrase" display is selected, and each phrase is shown in a separate column. When the "section" display is selected, how much of this phrase-based information should be shown? It seems to me we should either include none of that information or enumerate all of the phrase labels that are included in that section.
And when "duration" is selected, what (if any) of this information should be shown. I would lean toward showing no information, since the labels won't line up evenly with any of these duration bins.

I have implemented a slightly hacky version of this. But, for reasons I can explain tomorrow, I think I will need to redo this largely from scratch in order to implement your full vision.

Working through implementing the phrase and section filtering options. Not sure how to handle situations in which a phrase attribute (phraseType, elaboration, articulation, incidental) has no options selected. Should these be included/excluded implicitly?

We need a new category: unlabeled.
If there is a conflict, we need a hierarchy for deciding. For example, if you want to include all mukra phrases, but exclude all bols, what happens?


Add a metric that tracks the number of preemptions issued by a ClusterQueue

What would you like to be added:
A metric that counts how many preemptions a ClusterQueue has issued, broken down by whether it was internal to the ClusterQueue, it was a reclamation, fair sharing or priority threshold.
This is somewhat the opposite direction of evicted_workloads_total, but focused on Preemption.
Why is this needed:
Improve observability.
Completion requirements:
This enhancement requires the following artifacts:

[ ] Design doc
[ ] API change
[ ] Docs update

The artifacts should be linked in subsequent comments.

/assign @vladikkuzn

In this case we can just extend
https://github.com/kubernetes-sigs/kueue/blob/1d849aa016c8d3672adb3afcddedc23527f00429/pkg/metrics/metrics.go#L137-L149
and a an additional label for the preemption scope.

Yes, indeed, that would be useful.
But this counter is from the point-of-view of the preemptee CQ.
The request is from the point-of-view of the preemptor CQ.

...  that is a bit different , so count the preemptees but group but group by the preemptor's CQ name. We could ad yet another metric label "preemptor_cluster_queue" but we can end up creating too many metric data-points.

Preemption is one of the few actions that involves two entities.
We could also have one metric that has both clusterqueues as labels, but that could cause explosion of cardinality.
Having one for each side sounds like a reasonable compromise.


chore: remove default value from baseDVNamespace and sourceDiskImageNamespace

What this PR does / why we need it:
chore: remove default value from baseDVNamespace and sourceDiskImageNamespace in pipelines
Tekton probably contains bug, which does not propagate params from PipelineRuns, when resolver is defined. Instead it uses default values defined in pipeline manifest -
https://issues.redhat.com/browse/SRVKP-4329.
Hovewer if the param does not contain any default value, tekton passes correct value
Release note:
chore: remove default value from baseDVNamespace and sourceDiskImageNamespace in pipelines

/cc @0xFelix, @akrejcir, @jcanocan

Doesn't this mean all params with default values are broken?

Not all, only for some unknown reasons the baseDvNamespace uses the default value eventhought the PipelineRun contains different value.
On the another hand, this change makes sense, because if regular user would like to try these pipelines, the user have to change these parameters.
Regular users can't create DVs in kubevirt-os-image namespace. So from my point it is better to remove the default value and keep user to decide where the DVs should be.

Closing, will be replaced by https://github.com/kubevirt/kubevirt-tekton-tasks/pull/360


Can not run RxBluetoothKit (Swift 4.0) on iPhone 5c (10.3 iOS)

I am trying to run the example with my own device and can not do it because at the time that I choose my own device i can not acceded to any method of the library, if I jump, I just can see autogenerated code by xcode. But if I select a simulator device i can Jump to the definition and see all the implemented methods.

We haven't updated the example for Swift 4.0 yet. I will do this today and make sure that all works as expected.

Really thanks I guess can find it at swift 4.0 branch.

Yes, will be available in a couple of hours. Thanks for the patience!

I know you are making changes, but I can not understand why when I try to build I can not find any method from RxBluetoothKit, why xcode autogenerated some code instead of let me see the implemented methods.

I'm not sure why it's like that. Right now working example is available on the swift4 branch. Please run pod repo update and pod install to make it running :)


Respect view constraints when setting view properties

Currently, if you have a view with constraints, they are not respected when you directly set view properties.  For example, the following view has a center constraint based on the provided extent:
var view = new ol.View({
  projection: 'EPSG:4326',
  extent: [-180, -90, 180, 90],
  center: [0, 0],
  zoom: 1
})

I can now set the view center to something far outside this constraint:
view.setCenter([0, -1000]);

The view gladly asks the map to render the same.  And if I ask the view for the center, it reports what I set:
view.getCenter(); // [0, -1000]

This makes constraints seem a bit pointless.
I think we've discussed this before, but I wanted to bring it up again.  What would happen if we made the convenient setters (e.g. setCenter(center)) respect the constraints and provided a different way to bypass the constraint (e.g. setCenter(center, {constrain: false})) or unconstrainCenter(center))?

I don't anticipate major problems with that, except that we'll break applications that (correctly) rely on the setters not applying the constraints.
The view currently exposes constrainX functions that one can use to get constrained values. For example:
view.setCenter(view.constrainCenter(center));

So we do provide the functionality already. For that reason I think I wouldn't break people's applications (and upset them).

I agree with @tschaub that users expect constraint to be applied if they are set as constructor options (like e.g. an extent). I know that @elemoine likes the concept of set*() methods just setting properties, but we are not consequent with that either.
Another story is that it is very awkward to turn off constraints that are set as default, without the user asking for it (e.g. zoom constraint snapping to powers - see #4251, the zoom control relies on additional delta and direction handling).

@ahocevar note that I did not say anything regarding "set*() methods just setting properties". I just said that the proposed change may break existing applications.


WIP ARROW-4558: [C++][Flight] Implement gRPC customizations without UB

I admit this feels gross, but it's less gross than what was there before. I can do some more clean up but wanted to get feedback before spending any more time on it
So, the problem partially lies with the gRPC C++ library. The obvious thing, and first thing I tried, was to specialize SerializationTraits<protocol::FlightData> and do casts between FlightData and protocol::FlightData (the proto) at the last possible moment. Unfortunately, this seems to not be possible because of this:
https://github.com/grpc/grpc/blob/master/include/grpcpp/impl/codegen/proto_utils.h#L100
So I had to override that Googly hack and go to some shenanigans (see protocol.h/protocol.cc) to make sure the same templates are always visible both in Flight.grpc.pb.cc as well as our client.cc/server.cc

cc @pitrou @lihalite

Perhaps it would be useful to ping the gRPC community to know if this is idiomatic.

@lihalite Interesting.
Apparently, https://github.com/tensorflow/tensorflow/blob/ced4fddc0400fedce8ba15fb9a3e6e765ddda757/tensorflow/core/distributed_runtime/rpc/grpc_tensor_coding.cc#L171 shows how to do actual zero-copy writes, i.e. write directy from application data to socket - by creating a bunch of slices that point to application data and chaining them in the ByteBuffer (which can contain any number of slices).

@pitrou That is awesome, maybe we should do that in a follow-up.

@pitrou I was going to propose that on the e-mail thread but you found it already =) Composing a slice from smaller zero-copy constituent slices is the way to avoid memcpy there. The only annoyance is that we'll have to add padding slices but c'est la vie

FWIW, the Java side also adds padding slices (it was one of the incompatibilities between the two implementations)
https://github.com/apache/arrow/blob/27ba26cad39d92713e17d811a65ad0b87c587610/java/flight/src/main/java/org/apache/arrow/flight/ArrowMessage.java#L276-L281

Hmm... why do we need padding slices?

I commented on the gRPC thread

@pitrou a buffer's size may not be a multiple of 8. But a buffer should be padded already so we should be able to round up the buffer size to the next multiple of 8 and avoid the padding slices
https://github.com/apache/arrow/blob/master/cpp/src/arrow/flight/serialization-internal.h#L302

Right... but the "padding" won't be necessarily zero-filled (for example if taking a slice of a buffer). Is it a problem?

I looked at Tensorflow's use of gRPC and it seems they don't do zero-copy on the receiving side. For example with the SendTensor method in eager_service.proto, it seems the server will use regular deserialization for the tensor bytes data sent by the client.
Also there are weird hacks where protobuf-generated definitions are replaced/overriden with a hand-written ones, I'm not sure why that is:
https://github.com/tensorflow/tensorflow/blob/ced4fddc0400fedce8ba15fb9a3e6e765ddda757/tensorflow/core/distributed_runtime/rpc/eager/grpc_eager_service.h#L43
https://github.com/tensorflow/tensorflow/blob/ced4fddc0400fedce8ba15fb9a3e6e765ddda757/tensorflow/core/distributed_runtime/rpc/grpc_worker_service_impl.h#L98

I opened https://issues.apache.org/jira/browse/ARROW-4562 about the composite byte buffer optimization

I'm sure you could ask TF about it and find the right person to talk to.
You might want to try benchmarking with two of the nodes in the UL Nashville network rather than localhost-to-localhost. They are connected with gigabit ethernet only (I'm upgrading the network switches but not sure I can get 10-gigabit working, too many factors out of my control) so it would be interesting to see to what extent we are saturating the network bandwidth

@pitrou regarding padding, I could imagine an application that hashes IPC payloads for some purpose (caching?) having an issue with non-zero padding. It seems like an esoteric concern; I'm not sure it is worth paying the price, or at least having the "sanitize padding" option as something that's disabled by default

Perhaps the price isn't that large either. Ideally the batches are large so adding a 8-bytes zero-initialized slice may be cheap...

OK to merge this with a passing build? This could benefit from an IWYU pass but I might like to do that for all of Flight to clean up all the includes and forward-declarations

I should rename protocol.h to protocol-internal.h so the header is not installed.

OK I'll wait for the build to run again and then merge

Merging. A couple of builds experienced transient failures