seeking help to implement table for dp camp project

I'm taking this biz scenario. Please assign issue to me.

Did the work. Please review it. Thanks.

100%! Excellent!


Add images and gameplay

@BrandonPacewic Ready to merge. The copyright files were causing most of the conflicts. Later in the future we could write a program to automatically put them on.

I'm getting ready to merge and updating the change log - please @me if any other changes are pushed.


Tries to return virtual property on insert

Describe the bug
When inserting an entity which has a virtual property by calling em.create(Entity, ...) and em.flush() the query tries to return the virtual property resulting in an error.
Stack trace
InvalidFieldNameException: insert into "entity" (...) values (...) returning ..., "something" - column "something" does not exist
    at PostgreSqlExceptionConverter.convertException (node_modules/@mikro-orm/postgresql/PostgreSqlExceptionConverter.js:36:24)
    at PostgreSqlDriver.convertException (node_modules/@mikro-orm/core/drivers/DatabaseDriver.js:192:54)
    at /Users/willemgovaerts/Documents/projects/valcori-api/node_modules/@mikro-orm/core/drivers/DatabaseDriver.js:196:24
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at PostgreSqlDriver.nativeInsertMany (node_modules/@mikro-orm/knex/AbstractSqlDriver.js:285:21)
    at ChangeSetPersister.persistNewEntity (node_modules/@mikro-orm/core/unit-of-work/ChangeSetPersister.js:85:21)
    at ChangeSetPersister.executeInserts (node_modules/@mikro-orm/core/unit-of-work/ChangeSetPersister.js:29:13)
    at ChangeSetPersister.runForEachSchema (node_modules/@mikro-orm/core/unit-of-work/ChangeSetPersister.js:68:13)
    at UnitOfWork.commitCreateChangeSets (node_modules/@mikro-orm/core/unit-of-work/UnitOfWork.js:708:9)
    at UnitOfWork.persistToDatabase (node_modules/@mikro-orm/core/unit-of-work/UnitOfWork.js:660:13)

To Reproduce
Steps to reproduce the behavior:

create an entity with a simple virtual property

@Property({ persist: false })
  public something: number = 0;

create and flush this entity

Expected behavior
Virtual properties should not be included in the returning clause
Additional context
The fix implemented in 35d51fe seems not to work since hydrateProps also contains the virtual property
Versions

Dependency
Version

node
v18.10.0

typescript
v4.3.5

mikro-orm
v5.5.1

your-driver
PostgreSqlDriver

Fixed in master

https://github.com/mikro-orm/mikro-orm/releases/tag/v5.5.2


Fluent NHibernate V2.0.1 types are not CLS compliant

My first issue on GitHub - sorry if this isn't the right forum for it.
The assembly FluentNHibernate V2.0.1 is not marked CLS Compliant. V1.4 was.
Is this an oversight? If the file src\CommonAssemblyInfo.cs is generated by build tools (I downloaded the source and it isn't there) then should those tools add a CLSCompliant attribute, or are the types genuinely no longer CLS compliant?
When I update FluentNhibernate to V2.0.1, my builds raise warnings that my CLS-compliant types that depend on it cannot be CLS compliant.

Sounds like you're right, let me look into it. If that's true, will be fixed in next release - I'm planning on rolling out some minor fixes soon.


I cannot access the Wifi configuration UI nor the Update UI. No buttons are responsive, I also can not leave the UI, I only can force shutdown the device.

How can the issue be reproduced? (If applicable)
Not sure. It's just that I go to Options>Wifi and nothing there is responsive. Same for Options>Update. Which means I cannot update ArkOS also, even when I plugin in ethernet cable via usb-c adapter.
What device are you using?
Anbernic RG351V
What version of ArkOS are you on?
ArkOS 2.0 (03112023)

Hello,
Unzip and stick the .sh script in the link below in your tools folder on your roms card.
https://github.com/christianhaitian/arkos/files/13062162/Restore.ArkOS.Settings.zip
then

Take the attached compressed file (arkosbackup.tar.gz) below and put it in your roms/backup folder. Do not uncompress the contents! Just place the file as is in your roms/backup folder. If you don't have a backup folder in the roms folder, just create it.  If you're using a 2 SD card setup on your device, this must be done from SD1(TF1 Slot).

Then go into the Emulationstation Menu, scroll to Options, hit A, then go to Advanced, hit A, then scroll all the way down to Restore Settings, hit A.

Once completed, Launch wifi and verify it functions correctly again

https://github.com/christianhaitian/arkos/files/13059782/arkosbackup.tar.gz

Hello any update on this issue?

Hey yeah, so I have a single SD Card Setup, I can not access the files of that SD Card on another computer (ext4 ?)
I tried to transfer the files via fat32 usb stick on the device but it doesn't mount when I try to do it via Options menu. So I don't know how to transfer files at the moment. I ran out of patience then..

The Roms partition on a single sd card should have been in exfat format and accessible via a mac or windows pc.  Oh well, take care.

I tried it again and now everything is fine.. except that the volume buttons still don't work .. mhh


AWS Simple Storage Service - S3

Task: https://github.com/EPAM-JS-Competency-center/cloud-development-course-initial/blob/main/task5-import-to-s3/task.md
Done 22.09.2021 / Deadline 22.09.2021
Score:
Evaluation criteria

[x] File serverless.yml contains configuration for importProductsFile function
[x] The importProductsFile lambda function returns a correct response which can be used to upload a file into the S3 bucket
[x] Frontend application is integrated with importProductsFile lambda
[x] The importFileParser lambda function is implemented and serverless.yml contains configuration for the lambda

Additional tasks

[x] (for JS only) - async/await is used in lambda functions (+1)
[ ] (All languages) - importProductsFile lambda is covered by unit tests ((for JS only) aws-sdk-mock can be used to mock S3 methods - https://www.npmjs.com/package/aws-sdk-mock)
[x] (All languages) - At the end of the stream the lambda function should move the file from the uploaded folder into the parsed folder (move the file means that file should be copied into parsed folder, and then deleted from uploaded folder) (+1)

Frontend

https://github.com/kastrubait/shop-angular-cloudfront/pull/4
https://d1mkje9otd9k5.cloudfront.net/admin/products

Hello Tatsiana. When I try to upload files from front I've got a mistake:

You should set appropriate headers. It worked for me

Let me know if you correct it

Hi! Good job! For signedUrl mock worked:
test('Get correct mocked-url if result correct', async () => {
const MOCKED_URL = 'https://mocked-url.com';
AWSMock.mock('S3', 'getSignedUrl', MOCKED_URL);
const response = await importProductsFile(event);
expect(JSON.parse(response.body)).toEqual(MOCKED_URL);

});

Hi! Good job! For signedUrl mock worked:
test('Get correct mocked-url if result correct', async () => {
const MOCKED_URL = 'https://mocked-url.com';
AWSMock.mock('S3', 'getSignedUrl', MOCKED_URL);
const response = await importProductsFile(event);
expect(JSON.parse(response.body)).toEqual(MOCKED_URL);

});

Привет! Молодец! Для signedUrl сработал макет:
test ('Получить правильный mocked-url, если результат правильный', async () => {
const MOCKED_URL = ' https://mocked-url.com ';
AWSMock.mock ('S3', 'getSignedUrl' , MOCKED_URL);
const response = await importProductsFile(event);
expect(JSON.parse(response.body)).toEqual(MOCKED_URL);

});

This is the first thing I tried. But for some reason, it doesn't work for me ((


Trouble to display data in the year mode

Hi,
I really like your chart and wanted to reuse it. I just have a problem when I put overview={'year'}  . The data aren't displayed when the page is done loading, I have to go on global mode before going back to the year one in order for my data to be displayed. I didn't have the problem when I tried to put overview={'day'} or overview={'global'} . But I really wished to be able to display the year mode first.
thanks :)

The default view in the demo is the year overview.
Can you share the changes you've made to the source? Maybe you could fork the project and share the link?

Hi,
Sure.
So as you can see in the picture, the first part in the for is where I organize the data that I got from my api, then I create my chart with these data as well as other informations needed

Thanks for sharing the screenshot, the formatted data looks correct.. although I can't see what heatMapData data looks like. If it's not too much trouble could you upload an example somewhere? Maybe you could fork the project and share the link with me here, or use a jsfiddle or similar? That would help with debugging. Thanks!

Sure I can share an example. It is an array with a bunch of data, but the way I get it from the api doesn't work with the chart so I just reformatted it in a way for it to work. Actually I also had the same problem when I was testing with the exemple you used in the README.

sorry about the delay, were you able to get it to work correctly? Let me know if there's a way I can help, I'd appreciate a fork with your data/ or a simple js-fiddle with an example where you get that buggy behavior.

Hi, I wasn't able to make it works. So I tried to start again from the begining and using the following data which doesn't require to use my api call :

But again I wasn't able to display them in year mode

I have to click on the arrow button and then on the global graph to correctly display them in the year mode

I will let you know if I'm able to make it works somehow.

Thanks, let me know! In the meantime, I'd love to help if you could provide other examples (that I could copy/paste) or what's even better - a link to a cloned fork of the project or something similar I could download and reproduce this issue.

Even I'm not able to display the year data, can someone provide me with some sample data to test with, I tried the one in the documentation but it doesn't work:-<

Hi @Deveshb15 - let me try to help you get some data for testing. In our demo we generate random data for the visualization using this method: https://github.com/g1eb/reactjs-calendar-heatmap/blob/master/index.html#L29
// Initialize random data for the demo
let now = moment().endOf('day').toDate()
let time_ago = moment().startOf('day').subtract(10, 'year').toDate()
let data = d3.timeDays(time_ago, now).map(function (dateElement, index) {
  return {
    date: dateElement,
    details: Array.apply(null, new Array(Math.floor(Math.random() * 15))).map(function(e, i, arr) {
      return {
        'name': 'Project ' + Math.ceil(Math.random() * 10),
        'date': function () {
          let projectDate = new Date(dateElement.getTime())
          projectDate.setHours(Math.floor(Math.random() * 24))
          projectDate.setMinutes(Math.floor(Math.random() * 60))
          return projectDate
        }(),
        'value': 3600 * ((arr.length - i) / 5) + Math.floor(Math.random() * 3600) * Math.round(Math.random() * (index / 365))
      }
    }),
    init: function () {
      this.total = this.details.reduce(function (prev, e) {
        return prev + e.value
      }, 0)
      return this
    }
  }.init()
})

Could you try running the above snippet and see if the generated data works for you?
Let me know if you run into any issues!

Hi did you manage to get this to work? I'm facing the same issue and I am not sure what to do as I'm new using react
I can get the example to work but if I send json data I can't seem to get it right. in the decade/ years view the heatmap disappears


Authenticated routes?

Hi. I've attempting to use this library to run lighthouse on authenticated routes, but i'm having some difficulty. I see you're setting disableStorageReset:
https://github.com/abhinaba-ghosh/playwright-lighthouse/blob/88699bff7ad9038a5c9c38d69e79454b60bb53a3/src/task.js#L57
This is good, but the problem is auth state is not shared between browser contexts.
I understand the problem as:

Playwright launches chrome
Playwright creates a new isolated browser context (incognito)
Playwright injects the auth state into this browser window
Lighthouse opens an entirely new window (and browser context) from the chrome instance
Auth state is not carried across to the lighthouse window

Did you ever get this to work? Can you offer any advice?

This appears to only work when using launchPersistentContext:
const userDataDir = '/path/to/data/dir';

const browser = await chromium.launchPersistentContext(userDataDir, {
  args: ['--remote-debugging-port=9222'],
});
const page = await browser.newPage();
await page.goto('http://localhost:3000/');

// Perform your login steps here which will save to cookie or localstorage

// When lighthouse opens a new page the storage will be pesisted meaning the new page will have the same session (either via cookie or localstorage)
await playAudit({
  page: page,
  port: 9222,
});

Unfortunately I can't figure out how to use launchPersistentContext with the Playwright Test Runner.

Thanks @badsyntax

I've figured out how to do this here: https://github.com/microsoft/playwright/issues/7447#issuecomment-879803423
But I want to wait for some feedback from the playwright authors before adding that info to the README in this repo.

You can add the info to the readme and change it later if needed. 😇


Add a service to retrieve a device definition and dump it in the log.

This requires https://github.com/iMicknl/python-tahoma-api/pull/51

Do we really need this in our Home Assistant integration? We can easily pull the details for a user based on their details from the debug log, is there a need for them to do this themselves?

My use case was to find the exact command tu use to refresh the thermostat state by using the execute_command service.
As a power user, I was able to get it from the api itself, but I would have liked to have a solution to dump the commands to the log.


about license

Hi! Thanks for great work.
Can i get license info?
Thanks you :)

Hi @sujyQ, thanks for your interest!
The license information has been now uploaded.


[Bug]: Invalid Route Causes Dev Server to Crash

Version
System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
    Memory: 7.62 GB / 15.85 GB
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.19041.4355
  npmPackages:
    @rsbuild/core: ^1.0.1 => 1.0.7
    @rsbuild/plugin-react: ^1.0.1 => 1.0.2

Details
Just try to reach http://localhost:3000//someroute

Reproduce link
no link
Reproduce Steps

npx create-rsbuild -d some-project -t react
cd some-project
npm i
npm run dev
open browser and goto http://localhost:3000//someroute

Thank you guys for fixing it
Have a nice journey developing such a wonderful tool

Our pleasure 😄


⚠ Bofrost.lu has degraded performance

In 3c2abb5, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1640 ms

Resolved: Bofrost.lu performance has improved in 4dcc0bf.


[libiconv] Build error

Host Environment
issue_body.md

OS: [e.g. Windows/Linux etc...]
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
./vcpkg install xxxx
Failure logs

Cut and paste the appropriate build messages from the console output.
Attach every failure log file mentioned in the console output.

Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.

Thanks for posting this issue. Could you use a short path to clone vcpkg and install libiconv again? Like C:/Users/DELL/vcpkg.

    FAILED: cmTC_4c13c.exe
    cmd.exe /C "cd . && C:\Users\DELL\Downloads\sw-master-windows-client(1)\vcpkg\downloads\tools\cmake-3.24.0-windows\cmake-3.24.0-windows-i386\bin\cmake.exe -E vs_link_exe --intdir=CMakeFiles\cmTC_4c13c.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\mt.exe --manifests  -- C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1433~1.316\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_4c13c.dir\testCCompiler.c.obj  /out:cmTC_4c13c.exe /implib:cmTC_4c13c.lib /pdb:cmTC_4c13c.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    'C:\Users\DELL\Downloads\sw-master-windows-client' is not recognized as an internal or external command,

It is not the length but (1).

@dg0yt I have tried this and now I am getting the error for "building openssl:x64-windows failed with: BUILD_FAILED"
issue_body.md

[DEBUG] Downloading https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-<IP_ADDRESS>-32bit.zip
[DEBUG] Download failed -- retrying after 1000 ms.
[DEBUG] Download failed -- retrying after 2000 ms.
[DEBUG] Download failed -- retrying after 4000 ms.
Error: Failed to download from mirror set:
https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-<IP_ADDRESS>-32bit.zip: WinHttpSendRequest() failed: 12002
https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-<IP_ADDRESS>-32bit.zip: WinHttpSendRequest() failed: 12002
https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-<IP_ADDRESS>-32bit.zip: WinHttpSendRequest() failed: 12002
https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-<IP_ADDRESS>-32bit.zip: WinHttpSendRequest() failed: 12002
[DEBUG] D:\a_work\1\s\src\vcpkg\base\downloads.cpp(766):
[DEBUG] Time in subprocesses: 0 us
[DEBUG] Time in parsing JSON: 9 us
[DEBUG] Time in JSON reader: 0 us
[DEBUG] Time in filesystem: 4272 us
[DEBUG] Time in loading ports: 0 us
[DEBUG] Exiting after 1.533 min (91958139 us)
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):
  Failed to download file with error: 1
  If you use a proxy, please check your proxy setting. Possible causes are:

  1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
     to `https://address:port`. This is not correct, because `https://` prefix
     claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
     , etc..) is an HTTP proxy. Try setting `http://address:port` to both
     HTTP_PROXY and HTTPS_PROXY instead.

  2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
     will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
     Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
     Change `http=address:port;https=address:port` to `address`, and fill the port number.

  3. Your proxy's remote server is out of service.

  In future vcpkg releases, if you are using Windows, you no longer need to set
  HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
  Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
  and (https://github.com/microsoft/vcpkg-tool/pull/77)

  Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
scripts/cmake/vcpkg_download_distfile.cmake:273 (z_vcpkg_download_distfile_show_proxy_and_fail)
scripts/cmake/vcpkg_find_acquire_program.cmake:628 (vcpkg_download_distfile)
ports/openssl/portfile.cmake:28 (vcpkg_find_acquire_program)
scripts/ports.cmake:147 (include)

openssl build failed due to download failed, you could try manually download https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-<IP_ADDRESS>-32bit.zip

Ping @ham12u for response.

Thanks for posting this issue. Please reopen this issue if this is still a problem for you.


Add tests to cover slicing behavior when changing layers and data

References and relevant issues
Related to #6198 and #6199
Description
This adds tests to cover cases when either layers are added, removed, or their data changes in ways that should trigger data to be sliced and the canvas view to be updated. Some of these cases pass due to recent changes (e.g. #5522), but some fail due to remaining issues (e.g. #6198 and #6199).

This is not a real problem, and it is not a proper solution. Accepting this will make adding a bunch of layers a quadratic operation, as adding a single layer will have linear complexity. The proper solution is to update layers when the range is changed.
Some signal is not emitted from the Dims object when, because of a change of range, the current slider position represents a different value in real-world coordinates.

Sooo, after some research on how the event system works I added a new event for point and connected it to the update_layer.
It appears that it is only updating all layers one when the point property changes.

This solution looks working, but dims.points are updated on the moving dims slider. And, as you show in the first post, after moving the slider, the layers are updated. So with this change we will have the double update of layers.
But I'm not familiar with this part of the napari codebase. Calling @andy-sweet, who may better know what needs to be done.

Ok I'm confused... It looks from the diff that there was already a point event on dims? But I looked at that specifically when I responded yesterday and didn't find it:
In [5]: viewer = napari.Viewer()

In [6]: viewer.dims.events.emitters
Out[6]:
{'ndim': <napari.utils.events.event.EventEmitter at 0x15022ecb0>,
 'ndisplay': <napari.utils.events.event.EventEmitter at 0x15022d180>,
 'last_used': <napari.utils.events.event.EventEmitter at 0x15022d5a0>,
 'range': <napari.utils.events.event.EventEmitter at 0x15022ec20>,
 'current_step': <napari.utils.events.event.EventEmitter at 0x15022d6c0>,
 'order': <napari.utils.events.event.EventEmitter at 0x15022c400>,
 'axis_labels': <napari.utils.events.event.EventEmitter at 0x15022dde0>}

At any rate, the test failures are real... Not sure immediately what the fix is.
But @Czaki @mstabrin, I think the fix to the double update is simply to remove the current_step connection from the line above.

How could I miss the current_steep connection line above...
Yes. It is a proper solution from my point of view.

Ok I'm confused... It looks from the diff that there was already a point event on dims? But I looked at that specifically when I responded yesterday and didn't find it:

There is a little extra magic in EventedModel that adds an event to any property with a setter. So the event is not on main, but it is after the current changes in this PR.

This is not a real problem, and it is not a proper solution.

Seems like a real problem to me - the view should update when adding a new layer. But I don't understand the current solution at all.

I am not sure how to test this, I will look into it later.

I think the following test should work. It tests some private state, which is not ideal, but seems fine to me. Also no need for the out_of_slice_display to reproduce the core bug here.
def test_add_points_layer_with_different_range_updates_all_slices():
    """See https://github.com/napari/napari/pull/4819"""
    viewer = ViewerModel()
    point = viewer.add_points([[10, 5, 5]])

    other_point = viewer.add_points([[8, 1, 1]])

    np.testing.assert_array_equal(point._indices_view, [])
    np.testing.assert_array_equal(other_point._indices_view, [0])

I think the solutions I would go to have already been tried/mentioned.

Connect the range event to _update_layers because point is dependent on both current_step and range.
Update all the layers whenever any layer is added.

The quadratic performance of adding lots of layers with the same extent is concerning, but I believe the early return condition in Layer._slice_dims should prevent us from actually doing much work in that case.

Seems like a real problem to me - the view should update when adding a new layer. But I don't understand the current solution at all.

the current problem is that adding a new layer does not cause recalculation of the slider position. So 0 in the current steep happens to be 0 in a new steep, but calculation from value to world space changes. (so current_step does not change but its implementation change).

the current problem is that adding a new layer does not cause recalculation of the slider position. So 0 in the current steep happens to be 0 in a new steep, but calculation from value to world space changes. (so current_step does not change but its implementation change).

I see. Thanks for a different perspective. I guess the implied desired behavior is that we should try to maintain the value of point (which effectively defines the slicing plane in world coordinates) when a new layer is added?
In general that won't be possible because the slider has integer positions. But we could snap to the closest slider position. I think that behavior is effectively defined by Dims.set_point already. So maybe there's a solution where we called Dims.set_point with the value of Dims.point before the layer is added?

Thank you all for the discussion :)
@andy-sweet thank you for the test suggestion!
I followed the suggestion of @andy-sweet and connected the range event to _update_layers and thinks appear to be working as expected (from my perspective).
That means: If I add a new layer with points being inside the current dim range only the newly selected layer is updated, but if a point is outside of the range all layers are updated.
I removed the point setter again, since I did not want to introduce any recursion issues ^^

Ok I experimented with the idea to utilize set_points. I still have some issues with it, but I will just leave it here for now :)

I dumped my attempt to just update the slider to stay at the same world coordinate position before and after the addition, because I failed to reliably get the point coordinate before the insertion in the _on_add_layer function.
I found a related even more concerning issue when removing a layer which unfortunately cannot be fixed by calling the _update_layers function
viewer.add_points([[10, 5, 5]]) # Insert a point at 10,5,5
viewer.add_points([[8, 5, 5]]) # Insert a point at 10,5,5
viewer.dims.set_point(range(3), (10, 5, 5)) # Move the dims slider to 10 (world coordinates)
viewer.layers.pop(0) # Remove point 10,5,5

This leaves the dims slider at 10, however the dims slider disappears and the Point at 8,5,5 is invisible and inaccessible forever.
The same is True for the following:
point = viewer.add_points([[10, 5, 5]]) # Insert a point at 10,5,5
point.data = [[10,5,5], [8,5,5]] # Simulate to add a new Point to the Data
viewer.dims.set_point(range(3), (10, 5, 5)) # Move the dims slider to 10 (world coordinates)
point.data = [[8,5,5]] # Simulate to remove a Point from the Data

Which means that if the second last point of a 3D Point layer is removed from the layer, the remaining point cannot be accessed by the user and is invisible forever.
To my quick tests only a call to viewer.dims.set_point call to the final slice of the data point will make it appear again.

Ok, thank you all for your input :)
I tried to make the most out of it and sorry for the spam on this PR during the last hours.
But...
I think I found a working solution which keeps the slider of the Dims.point value at the same world coordinate during insertion, and hence updates the view only if the lower boundary of range changes.
I hope that this keeps the layer updates required to a minimum for the desired behavior. :)

Thanks for the effort here @mstabrin! I'll try to find some time to give this a more thorough review, as it's important to think through the consequences of changes in core napari components like this.

@andy-sweet I think I addressed most of the considerations and I learned a lot :) Thanks for that ^^
I understand that this is a fundamental decision, so I made now sure that at least the existing tests pass with the current implementation :)
I have to admit that I do not know why this one test is failing here... It is passing on my computer :/

I have to admit that I do not know why this one test is failing here... It is passing on my computer :/

We have some flaky tests and my guess is that is one of them and the error has nothing to do with this change. I suspect if we rerun that at the same commit it would pass - so I triggered a new run.

@mstabrin : like @jni I'm not trying to be deliberately annoying here! I think we can some version of this PR through. One of the issues is that we already have some problems with Dims (e.g. around dimensional correspondences between different layers), so I'd prefer to avoid making too many changes or adding too much new logic before we fix those fundamental issues, as that will make that work harder.

@andy-sweet Oh it is quite the opposite for me :) It is very refreshing to have such an active development team that knows and cares about their code base! I also love this discussion from an educational point of view, it is really great that you take the time to justify your decision and concerns for me to learn about the napari project.
I pushed another version of the code accounting for your nicely described ndim logic :)
I think that is a great idea, since this is not only happening when the number of layers is 1, but also when higher dimsional layers are added or removed.
I will look into the failing tests tomorrow, they might be related to the new midpoint logic, but I will check :)

@andy-sweet Hello again :) I fixed the failing tests (Still 3 failing, but unrelated I think).
I added way more comments describing what is going on. I needed to change the order of the point dimensions, since new points are prepended and not appended and good thing some tests were complaining :)
I put the n_layers 0->1 logic into this if/else block which reduces the call to the update method by 1. Not sure if it really matters in practice, but one update less cannot harm? ^^
But we can also move it back to the _on_add_layer function, I do not have too much heart feelings about it since the number of layers is only 1 at this point in time and always will be.
Since the logic is now splitted again (talking about the self.reset_view() maybe we should also move this one either into the _on_layers_change function or move all of it to the _on_update_layers.
I will keep it splitted like that for further discussion :)
I also added some tests for the behavior when the second last point of a layer is deleted and with the current changes things work out like I would expect them if I would use the program :)

Yep, I suspect the test failures are unrelated. Thanks for the extra tests and comments. I might be able to look at this this today, otherwise I won't get to it until next week.

This will need a rebase to fix some of the test, and I think the rebase needs to be manual.

Hi all, coming a little late to this - first want to see if I understand correctly:
The problem right now is that when we add new data to layer we might change the world range which will change the sliders range, which means point will change as current_step will remain the same and point get's derived from current_step and range.
We derive point from current_step and range as sliders always have a current_step that is an integer, and moving the slider changes that. Maybe though we should have derived current_step from point. We may have done that at one moment in time, I honestly can't remember. Reading this PR now makes me think we probably should have done that - point and range would then be true stored attributes, and current_step would be derived. One way to address this PR would be to make that change.
Instead right now this PR adds a restore_point arg to set_range. My immediate thought is there ever a time where you want the range to change and you don't want to keep the point in world coordinates the same? I don't really think so, so I might ask why don't we drop set_range and instead grab the point value before the range updates and then reset it before the function ends.
In general I'd love if we could drop all the set_* methods in this file and use evented lists for these properties, but we've just never gotten around to that. If we ever do though having more args inside the set_* methods will make it harder.

Hello @sofroniewn :)
We had this exact conversation about the point value within the set_range  a few days ago here: https://github.com/napari/napari/pull/4819#discussion_r934018951
The problem is, that by assigning the ndim property in the code the root_validator is triggered which changes the range property, hence the point property.
Therefore I came up with this idea of providing the point to the function as a compromise instead.
We could remove it from the set_range as an argument and call the point adjustment outside of it as it was done before, but since changing the range and keeping the point is so tightly connected, it maybe should stay connected?
How about we add a new function, something like:
def set_range_and_dim(self, range):
    point = self.point
    self.ndim = len(range)
    self.set_range(point)
    self.set_point(self._get_point_in_ndim(point))

Just an idea, but I also would like to know more about the change towards current_step depending on point and range :)
Another quick thought:
The new _get_point_in_ndim function could also be always called when set_point is called?

I cannot agree. Pydantic approach for validation is not nice for object like dims. Because of strong dependencies between Dims attributes I think that best option is to reimplemented Dims and provide attributes as proxy view. This will allow to perform validation before any event is emmited and do not use events to exchange information between attributes.
The core problem, for me, with evented list is that someone could connect to such list event and someone else could assign new list to this attribute that will break code. And workaround for this will be much more problematic than proxies.

The core problem, for me, with evented list is that someone could connect to such list event and someone else could assign new list to this attribute that will break code. And workaround for this will be much more problematic than proxies.

I don't know, we just have to intercept the setter and then move that list's content to the evented list. wouldn't actually be terrible, but we don't need to discuss that now

The problem is, that by assigning the ndim property in the code the root_validator is triggered which changes the range property, hence the point property.

hmm, that should only matter when the ndim changes though. i'll admit it's not quite clear to me why that's a problem, but that's ok

Just an idea, but I also would like to know more about the change towards current_step depending on point and range :)

I think that's a real option we should consider - i'm not sure of any downsides, does anyone else see any?

@mstabrin : I didn't entirely forget about this! I'm going to try to re-review this over the next week or. Generally, I feel like it's too big of a chance to bring into the next patch release (0.4.17) being made now, but is definitely a great candidate for the next minor release (0.5) in case this has any unexpected side-effects.

@andy-sweet No Problem, I also had more urgent features to work on for release 0.4.17 :)
Once the release is done I will come back here for sure :D

@mstabrin: if you can merge main into this and push, I'd be happy to take another look and get this one over the line.

@andy-sweet Hello andy, sorry for the late answer I was busy on another project :)
I am confused, I merged the main into this and push, but it seems to really not like it ^^
On my machine I can merge back and forth now without any issues, though.

Ok, forget about my last comment, it was just too early in the morning :D
Now it is merged.

@Czaki Do you think the failing test is also due to the pint version?

@Czaki Do you think the failing test is also due to the pint version?

Looks like it. It should be fixed because pint 0.20.1 is live. I've rerun it.

@mstabrin : I created https://github.com/mstabrin/napari/pull/2 to address some of the minor comments here. I would love to find a solution where we can remove some of the special casing in ViewerModel and avoid some unnecessary updates, some of which are pre-existing in napari. I tried to do that today, but failed, so it might just be best to compromise and bring this in as is and look for improvements later.

@mstabrin : we discussed this in the recent napari PR party. I'd still love to get some form of this PR in, since it addresses a real bug and you already wrote tests to cover that.
@brisvag has been making some changes to Dims recently that could affect this, so I'm going to wait for those to settle, then I'll put some effort into getting this over the line - or let me know if you'd like to do that.
At a minimum, I think we could get the tests in, mark them with xfail, then create an issue so this isn't lost.

@mstabrin : I decided to pick this up one more time. And I have mostly good news :)
I merged main into this and mostly accepted changes from main. See the diff with main on that branch for more details.
The good news is that test_add_points_layer_with_different_range_updates_all_slices passes without any changes needed to core napari. So I think this means that the recent changes from @brisvag fixed those issues.
The bad news is that the other two tests (test_last_point_is_visible_in_viewport, test_dimension_change_is_visible_in_viewport) still fail. I think the core reason that happens is because while Dims.range changes correctly, we only respond to changes to Dims.point. I think point does change, but its event is never emitted because it happens in the root validator of Dims. I don't remember if that was the same reason when this PR was written.
My suggestion is to merge in the passing test (test_add_points_layer_with_different_range_updates_all_slices), which runs quickly and should prevent future regressions. Then create an issue (or maybe two) to cover the other failing tests, which we can use as reproducers. I'm happy to handle both of these. What do you think?

@andy-sweet: Glad to hear that the first test is passing with the recent changes! :)
I think it would be a good idea to have the passing test merged.
Maybe the other two could be merged as well marked with xfail like you suggested in your previous comment?
So the new issues could directly link to the already failing existing test?

I think it would be a good idea to have the passing test merged.
Maybe the other two could be merged as well marked with xfail like you suggested in your previous comment?
So the new issues could directly link to the already failing existing test?

We don't have many xfails in napari, but I don't think we're against them either, so that sounds good.
Do you mind if I push directly to this branch? Or would you prefer if I pushed to my own and made a PR to yours?

I don't mind :) You can merge directly!

Done! The two tests are marked with xfail where the reason links to the bugs. I think the bugs are slightly different, so I created separate ones, but I think they may share a solution.

@brisvag : I added you as a reviewer because I think your recent work on dims (i.e. making it fundamentally based on point rather than current_step) fixed some of the issues here. I think the remaining failing tests (marked with xfail) could be fixed relatively easy as a small extension of that work (e.g. by ensuring a change in point always emits an event).

I'm not sure I follow the difference in the succeeding and failing tests... Are all the asserts in the xfail tests supposed to fail?

No, only one fails currently in each test. I think that's clarified in the reproducers in the bug write ups. Can also add comments in this PR if desired.

I fixed this connection in #5697, but you could try adding it here.

Oh yeah, I forgot that change is not in yet!

I doubt the event is not happening, that would be a pretty huge issue deep down in the evented model which would affect the whole codebase.

Even if that change comes in, I think there's still an issue. Here's a reproducer that shows the issue when changing Dims.range causes Dims.point to change but doesn't emit its event:
from napari.components.dims import Dims
d = Dims()
d.events.range.connect(lambda: print('range change'))
d.events.point.connect(lambda: print('point change'))
print(d.point)  # -> (0, 0)
print(d.range)  # -> (RangeTuple(start=0.0, stop=2.0, step=1.0), RangeTuple(start=0.0, stop=2.0, step=1.0))
d.range = ((1, 2, 1), (1, 2, 1))
# -> 'range change'
# but not -> 'point change'
print(d.range)  # -> (RangeTuple(start=1.0, stop=2.0, step=1.0), RangeTuple(start=1.0, stop=2.0, step=1.0))
print(d.point)  # -> (1, 1)

I suspect the issue is that the change to point happens in the root validator and that may bypass the setter, which is why our event never gets emitted. We could also connect to the range event for slicing, but that might cause more slicing than desired in some cases (at least for sync slicing). Happy to write up a general issue for this since I think it applies to any values updated in the root validator.

I suspect the issue is that the change to point happens in the root validator and that may bypass the setter, which is why our event never gets emitted. We could also connect to the range event for slicing, but that might cause more slicing than desired in some cases (at least for sync slicing). Happy to write up a general issue for this since I think it applies to any values updated in the root validator.

I was about to say that this shouldn't be an issue, but I think you're right actually... Cause when we check for equality, we only check for dependency of properties, and we don't have any concept of dependencies of fields... @Czaki, do you think we could simply manually add dependencies even if they're not properties, and get proper behaviour from our current logic?
The brute force alternative is to always check equality for all values (maybe special-casing Dims) instead of just dependent ones... More expensive, but guarantees events are fired.

We have a few other changes to our evented model which may not be ported there yet (like the most recent changes from @Czaki). We should definitely try to port those these and also solve this, and then use psygnal as a dependency :P

I went ahead and merged this since the test cases are valuable and everything is green. We have the two issues to follow up on, which might share a more common general fix around EventedModel or not.
Thanks again for your help and patience here @mstabrin . Hopefully we can get the remaining issues fixed soon.


Release new version for azure-devops 0.16.0

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/ishitam8/azure-cli-extensions.git@users/ishitam8/devopsCLI015version#subdirectory=src/$EXT&egg=$EXT"

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/ishitam8/azure-cli-extensions.git@users/ishitam8/devopsCLI015version#subdirectory=src/$EXT&egg=$EXT"


Button Color Blue=Cyan

[X] I have searched the Issues to see if this bug has already been reported
[X] I have tested the latest version

Steps to reproduce
https://github.com/themesberg/flowbite-react/blob/main/src/components/Button/theme.ts#L21
Current behavior
Describe what is currently happening and why it's a problem.
<Button color="blue">        Publish post    </Button>

Expected behavior
Describe what you expected to happen.

Context
What are you trying to accomplish? Does this only happen on a specific browser, screen size, or operating system?
If possible, provide a live example URL, screenshot, video, or a repository with the minimal reproduction of the issue.

Hi, the other colors are also broken in dark mode. The bg-color-xxx are missing the dark: attribute.

Hi, the other colors are also broken in dark mode. The bg-color-xxx are missing the dark: attribute.

Ok I will take a look. Separate issue.

@MateoWartelle I've created an issue https://github.com/themesberg/flowbite-react/issues/1045


Add basic Eulerian model class

This pull request adds a basic Eulerian model class for adding Eulerian model data (e.g. GEOSChem) onto the OpenGHG platform.
Several additional considerations here:

At the moment this is stored using the "model", "species" and "date" keywords but this will most likely not provide enough detail for this to be stored uniquely. This is something we need to iron out (and may involve not storing against keywords specifically).
This has been tested against GEOSChem data but will also want to test this against other Eulerian model inputs (in particular WRFChem and may want to try out MOZART as this is something we have access to at the moment).

Hopefully this is a fairly innocuous change to merge in, as it's a new piece of functionality but are we happy to merge this in? Would be useful to have this functionality in devel and other branches moving forward.


Kaido doesn’t loading any stream source

Source information
Kaido v14.9
Source language
English
Steps to reproduce
Try to watch any episode from any anime, it shows no stream available.
Expected behavior
When selecting it should show the available stream to watch
Actual behavior
No stream available
Aniyomi version
Dantotsu v3.1.0-alpha01
Android version
Android 14
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

it's works fine


Gryseels 2020

Reference
doi or URL: https://www.pnas.org/content/117/22/12222.long

I am closing this issue since the HIV genome(s) in question dates to after 1950


Unable to install the app on Android 5 and iOs8

Hi Simon! i compile the app perfectly from https://build.phonegap.com/ but when i try to install it on my android device 5.0 it won't install. No error shows except "Can't install the app"
If I remove the lines to invoke your plugin from the config.xml, it installs fine.
 <gap:plugin name="phonegap-plugin-push"  source="npm">
        <param name="SENDER_ID" value="THE-ID"/>
    </gap:plugin>

I can't find any other issue here about that so I have to ask you for help.

Hi Simon, n
o,
I
've check everything, only
let me install it
,
if I remove the push plugin
El 21/3/2016 17:59, "Simon MacDonald"<EMAIL_ADDRESS>escribió:

@vousys https://github.com/vousys do you have two apps with the same
bundle ID on your device?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/phonegap/phonegap-plugin-push/issues/731#issuecomment-199482448

@vousys I'd like to see the terminal output when you run the adb install -r myapp-release.apk command. As well consider doing adb uninstall com.mypackage.app before trying to do an install.

Hi Simon, I don't use this, I scan the QR code and install it on the device, and for iOs I use diawi to upload.
I try with an empty config with only this information:  (new ID, new Version, none of parameters) but nothing works. I remove the app from build.phonegap.com and then upload again, but the https://build.phonegap.com/apps/1977569/builds  says:
"Oh geez. Your build failed. Sorry, but a problem occurred on the build server"
<?xml version="1.0" encoding="UTF-8"?>
<widget xmlns     = "http://www.w3.org/ns/widgets"
        xmlns:gap = "http://phonegap.com/ns/1.0"
        id		    = "XXX"
        versionCode = "49"
        version   = "1.0.2">
    <name>XXX</name>
    <description><![CDATA[XXXX]]></description>

    <preference name="android-build-tool" value="gradle" />
    <preference name="android-minSDKVersion" value="17" />  <!-- min android version: 4.2  !-->
    <preference name="deployment-target" value="8.0" /> 	<!-- min iOS version 7  !-->

	<preference name="permissions" value="none"/>
    <preference name="phonegap-version" value="cli-5.2.0" />
    <preference name="android-maxSDKVersion" value="" />
    <preference name="android-targetSdkVersion" value="12" />

    <!-- PLUGINS !-->
    <gap:plugin name="cordova-plugin-whitelist" source="npm" />

    <gap:plugin name="cordova-plugin-push" source="npm">
        <param name="SENDER_ID" value="XXX"/>
    </gap:plugin>

</widget>

My built information:
App ID
1977569
Version
1.0.2
Owned by
xXXX
PhoneGap (iOS / Android / Windows)
cli-5.2.0 (3.9.1 / 4.1.1 / 3.8.1)
Plugin	Source	Version	Installed	Latest	Platforms
cordova-plugin-push   	npm	*	n/a	n/a	android,ios,winphone
cordova-plugin-whitelist   	npm	*	n/a	n/a	android,ios,winphone

Installed version of plugins will only be available after a successful build.

If I comment your plugin, I can compile it, check please
App ID
1977569
Version
1.0.2
Owned by
<EMAIL_ADDRESS>PhoneGap (iOS / Android / Windows)
cli-5.2.0 (3.9.1 / 4.1.1 / 3.8.1)
Source
.zip package
Last built (2)
1 minute
Plugin	Source	Version	Installed	Latest	Platforms
cordova-plugin-whitelist   	npm	*	1.2.1	n/a	android,ios,winphone

Installed version of plugins will only be available after a successful build. Update your config.xml with the snippet below to lock your plugins to the specific version used in this build:

Maybe the Build online has a bug

@vousys you are using the wrong plugin ID, notice your config.xml has cordova-plugin-push:
<gap:plugin name="cordova-plugin-push" source="npm">
        <param name="SENDER_ID" value="XXX"/>
</gap:plugin>

but it should be phonegap-plugin-push.

Hi Simon. My mistake, I was so tired testing and removing plugins and settings to make it work since yesterday.
I recompile it with the right tag, the build finished ok but when i try to install the app it says: Aplication not installed. I don't know what else to test.

@vousys I think you should download the .apk file and try to install it using the adb tool. You will get a better error message. I'm pretty sure there is another app on your device using the same ID.

it's imposible because I put the name XXXFuckingTesting .
I'll check how to install it using that because it sounds me that's a
native tool for develop in android

Salu2!
Vero | VOUSYS.com
http://www.vousys.com/
VOUSYS.com Office: Buenos Aires, Argentina | +54.011.5231-2082
http://www.vousys.com     [image: Facebook]
https://www.facebook.com/vousys [image: Twitter]
http://www.twitter.com/vousys [image: Google Plus]
https://plus.google.com/u/0/b/111673332818765301661/+Vousys/posts [image:
Pintrest] http://www.pinterest.com/vousys/ [image: Skype]
https://www.vousys.com/ https://www.vousys.com/exportador
http://www.tusfacturas.com.ar/ http://www.e-xpensas.com/
http://www.micampeonato.com/
2016-03-22 11:03 GMT-03:00 Simon MacDonald<EMAIL_ADDRESS>
@vousys https://github.com/vousys I think you should download the .apk
file and try to install it using the adb tool. You will get a better
error message. I'm pretty sure there is another app on your device using
the same ID.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/phonegap/phonegap-plugin-push/issues/731#issuecomment-199829241

Simon, if it was a problem with the ID, I shouldn't be able to install it without the push plugin, and I could.

Hi Simon! I create a new empty projects only with the files of your example (https://github.com/phonegap/phonegap-plugin-push/tree/master/example/www)  and this little config , I compile it fine but can't install it on my device motox xt1058 android lollipop
and happens the same in my iphone 4, ios8
<?xml version="1.0" encoding="UTF-8"?>
<widget xmlns     = "http://www.w3.org/ns/widgets"
        xmlns:gap = "http://phonegap.com/ns/1.0"
        id          = "mitest.com.testing"
        versionCode = "49"
        version   = "1.0.2">

    <name>Testing</name>

    <description><![CDATA[testing]]></description>

    <author href="http://www.tttt.com"<EMAIL_ADDRESS>        ttt
    </author>

    <preference name="android-build-tool" value="gradle" />
    <preference name="android-minSDKVersion" value="17" />  <!-- min android version: 4.2  !-->
    <preference name="deployment-target" value="8.0" />     <!-- min iOS version 7  !-->

    <preference name="permissions" value="none"/>
    <preference name="phonegap-version" value="cli-5.2.0" />
    <preference name="android-maxSDKVersion" value="" />
    <preference name="android-targetSdkVersion" value="12" />

    <!-- PLUGINS !-->
    <gap:plugin name="cordova-plugin-whitelist" source="npm" />
    <gap:plugin name="cordova-plugin-device"    source="npm" />

    <gap:plugin name="phonegap-plugin-push" source="npm">
        <param name="SENDER_ID" value="XXX"/>
        <!--<param name="GOOGLE_APP_ID" value="1:265882065897:ios:aaa"/>!-->
    </gap:plugin>

        <gap:platform name="ios" />
        <gap:platform name="android" />

    <access origin="tel:*" launch-external="yes" />
    <access origin="geo:*" launch-external="yes" />
    <access origin="*"/>
</widget>

Hi simon, I found the solution !!! reading and testing all the other issues, but please check because something is wrong with the default version of phonegap and plugin push
At this issue https://github.com/phonegap/phonegap-plugin-push/issues/741 they use
<preference name="phonegap-version" value="cli-5.4.1" />
<plugin name="phonegap-plugin-push" spec="~1.4.5" source="npm">

I changed that in my config and it works


istioctl manifest with empty profile does not create EnvoyFilter CRD for pilot

Bug description
When using profile=empty and addonComponents.pilot.enabled=true, it fails to create resources due to missing envoyfilters.networking.istio.io CRD.
[X] Installation
Expected behavior
Following command deploys pilot without error.
istioctl manifest apply \
--set profile=empty      \
--set addonComponents.pilot.enabled=true

Steps to reproduce the bug
step-1. Run following command for brand-new cluster:
istioctl manifest apply \
--set profile=empty      \
--set addonComponents.pilot.enabled=true

step-2. You will see following error:
unable to recognize "STDIN": no matches for kind "EnvoyFilter" in version "networking.istio.io/v1alpha3" (repeated 1 times)

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
$ istioctl version --remote=false
1.5.1

Additional Info
I have checked some docs, but this docs says it can work as a base profile.
https://istio.io/docs/setup/additional-setup/config-profiles/

empty: deploys nothing. This can be useful as a base profile for custom configuration.

This is working as expected. It literally deploys nothing, including CRDs

I expected that pilot is deployed as I specified addonComponents.pilot.enabled=true. But it should deploy nothing?
Here is the full error log and exit code, btw:
$ istioctl manifest apply \
> --set profile=empty      \
> --set addonComponents.pilot.enabled=true
Detected that your cluster does not support third party JWT authentication. Falling back to less secure first party JWT. See https://istio.io/docs/ops/best-practices/security/#configure-third-party-service-account-tokens for details.
- Applying manifest for component AddonComponents...
2020-03-26T16:24:58.025501Z	error	installer	error running kubectl: exit status 1
✘ Finished applying manifest for component AddonComponents.

Component AddonComponents - manifest apply returned the following errors:
Error: error running kubectl: exit status 1

Error detail:

Error from server (NotFound): error when creating "STDIN": namespaces "istio-system" not found (repeated 9 times)
unable to recognize "STDIN": no matches for kind "EnvoyFilter" in version "networking.istio.io/v1alpha3" (repeated 1 times)

clusterrole.rbac.authorization.k8s.io/istio-galley-istio-system created
clusterrole.rbac.authorization.k8s.io/istio-pilot-istio-system created
clusterrole.rbac.authorization.k8s.io/istiod-istio-system unchanged
clusterrolebinding.rbac.authorization.k8s.io/istio-pilot-istio-system created
clusterrolebinding.rbac.authorization.k8s.io/istiod-istio-system unchanged
validatingwebhookconfiguration.admissionregistration.k8s.io/istio-galley created
validatingwebhookconfiguration.admissionregistration.k8s.io/istiod-istio-system configured
mutatingwebhookconfiguration.admissionregistration.k8s.io/istio-sidecar-injector created

✘ Errors were logged during apply operation. Please check component installation logs above.

Error: failed to apply manifests: errors were logged during apply operation

$ echo $?
1

$ kubectl get pod -n istio-system
No resources found.

We should be creating the namespace (your other issue), which is why nothing is created

Ah, I understand. Let me confirm if I can avoid this issue if I create the namespace beforehand. (I will test it tomorrow.)

Ummm... No, the namespace is not related to this issue. Even if istio-system ns exists, the error happens.
$ kubectl create ns istio-system
namespace/istio-system created

$ kubectl get ns istio-system
NAME           STATUS   AGE
istio-system   Active   2m1s

$ istioctl manifest apply \
> --set profile=empty      \
> --set addonComponents.pilot.enabled=true

Detected that your cluster does not support third party JWT authentication. Falling back to less secure first party JWT. See https://istio.io/docs/ops/best-practices/security/#configure-third-party-service-account-tokens for details.
- Applying manifest for component AddonComponents...
2020-03-26T23:28:24.518193Z	error	installer	error running kubectl: exit status 1
✘ Finished applying manifest for component AddonComponents.

Component AddonComponents - manifest apply returned the following errors:
Error: error running kubectl: exit status 1

Error detail:

unable to recognize "STDIN": no matches for kind "EnvoyFilter" in version "networking.istio.io/v1alpha3" (repeated 6 times)

clusterrole.rbac.authorization.k8s.io/istio-galley-istio-system created
clusterrole.rbac.authorization.k8s.io/istio-pilot-istio-system created
clusterrole.rbac.authorization.k8s.io/istiod-istio-system created
clusterrolebinding.rbac.authorization.k8s.io/istio-pilot-istio-system created
clusterrolebinding.rbac.authorization.k8s.io/istiod-istio-system created
validatingwebhookconfiguration.admissionregistration.k8s.io/istio-galley created
validatingwebhookconfiguration.admissionregistration.k8s.io/istiod-istio-system created
mutatingwebhookconfiguration.admissionregistration.k8s.io/istio-sidecar-injector created

serviceaccount/istiod-service-account created
configmap/istio created
configmap/istio-sidecar-injector created
configmap/pilot-envoy-config created
deployment.apps/istiod created
poddisruptionbudget.policy/istiod created
horizontalpodautoscaler.autoscaling/istiod created
service/istio-pilot created
service/istiod created

✘ Errors were logged during apply operation. Please check component installation logs above.

Error: failed to apply manifests: errors were logged during apply operation

Yes, that is working as expected. With the config you have, you are essentially saying "Do not install any CRDs, but create an EnvoyFilter". If you want the CRDs create (which, I believe you do) then you'll need to set base.enabled=true (or not use profile=empty). Because profile=empty is disabling the "base" component which installs the CRDs

Oh, I see. Thank you. I am closing this issue.


flextable example index column not rendering properly

I noticed on the example page, the flexTable "index" column is no longer populated. Bisect shows:
f07effd1c08bffa115d870e803cd073c70560498 is the first bad commit
commit f07effd1c08bffa115d870e803cd073c70560498
Author: Brian Vaughn<EMAIL_ADDRESS>Date:   Sun Jan 10 15:00:49 2016 -0800
Added InfiniteLoader example and refactored demo app/components to share mock data

I won't have a chance to look at it closely for a bit but thought i'd put up a flag.

Haha, nice catch. I remember doing this. Whoops. :D

Fixed via 5034040


XY PAD Filtering

When Adding fixtures to XY PAD it needs to filter out heads that don't have Pan or tilt.
http://www.qlcplus.org/forum/viewtopic.php?f=5&t=8560#p37135

Thanks,
Fixed by https://github.com/mcallegari/qlcplus/commit/6984eb0037656c9ba88dfe1ee6d7438a2099f4c0


Service missing permission to start

Hi,
I installed you app on my YNH instance (11.1.16).
I had an 'internal server error' message when I tried to access it the first time. So I tried to restart the tandoor service, but its unable to do so because of missing permissions.
Also you mentioned additional setup for the "superuser" is needed, but I have no clue. That would be nice to have some detailed instructions for this part.
Install logs: https://paste.yunohost.org/raw/epuzofekuh
Service logs: https://paste.yunohost.org/fozogamuba

Everything is working fine after the upgrade:
sudo yunohost app upgrade tandoor -u https://github.com/YunoHost-Apps/tandoor_ynh/tree/testing --debug
Thanks !

I will look into creating more documentation for the superuser


[DEVOPS-517]  configuration | staging | csl-daedalus | applicationVersion:  de-bump to 4

…

Closing, in favor of https://github.com/input-output-hk/cardano-sl/pull/1933


Documented 2nd arg (e.g. :hex) for hash functions doesn't seem to exist

The wiki documents and code imply a second arg can be passed to hash functions to allow the return of different string/data types from those functions.  This does not appear to exist in the code or the tests.
https://github.com/cryptosphere/rbnacl/wiki/Hash-Functions
# compute the SHA-512 digest of the message and hex-encode it.
RbNaCl::Hash.sha512(message, :hex)
#=> "ab67..." # a string of hexidecimal bytes.

Specs & Code References:
https://github.com/cryptosphere/rbnacl/blob/master/spec/rbnacl/hash_spec.rb
https://github.com/cryptosphere/rbnacl/blob/master/lib/rbnacl/hash.rb#L24
https://github.com/cryptosphere/rbnacl/blob/master/lib/rbnacl/hash.rb#L40
https://github.com/cryptosphere/rbnacl/blob/master/lib/rbnacl/hash.rb#L58
Am I missing something?
Cheers,
Glenn

@namelessjon Not sure why you closed this.  The issue (referencing a non-existent second arg) is still present in the inline docs and line numbers I linked to above. I didn't think this minor doc issue needed a pull-request.  Maybe I was wrong?

Fixed in 4d7d67d


HIVE-27978: Tests in hive-unit module are not running again

What changes were proposed in this pull request?
To fix hive-unit tests running by removing a jupiter dependency.
Why are the changes needed?
Because tests in hive-unit module are not running again.
Does this PR introduce any user-facing change?
No.
Is the change a dependency upgrade?
Not an upgrade, just removing a test-scoped dependency in hive-unit module.
How was this patch tested?
Precommit tests.

LGTM


Add  tuhu.cn to powered by page

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

Coverage decreased (-0.002%) to 15.606% when pulling 6719e68f3b32d5d20dbe05803a9778134a8678eb on pengweiqhca:master into ab58baa753f77783c822c7c601ca79796a3c4b14 on apache:master.


IDEA hangs during test generation

Description
I've faced the problem that IDEA becomes not responsible during several test generations with the latest RC builds. While it's most probably caused by insufficient memory allocated to IDEA, UTBot test generation should not cause hang of IDEA without ability to cancel test generation process.
To Reproduce
Most of the times I've faced that problem after the following steps:

Open UTBot project
Generate tests for org.utbot.examples.algorithms.Sort

Expected behavior
Tests are generated
Actual behavior
Test generation started but in a about a minute IDEA stops to respond to user interaction. Once it finished generation in about 17min, but latter hanged again. Other times I killed IDEA after waiting for several minutes.
Visual proofs (screenshots, logs, images)
Thread dumps
Environment
IDEA 2022.1.4, with default -Xmx2022m in VM settings
UTBot - utbot-intellij-2022.10.465.
Additional information
Increasing IDEA memory to 4Gb seems resolves the problem. But I believe UTBot still should not cause hangs in IDEA and still be cancelable.

Additional details
Same happened to me once - on IDEA 2022.2.3
IDE hanged after test generation had already finished - and some imports and build project were being made.
It hanged for about 16 hours and only kill process helped.

That seems caused by #1225. If we try to open such file in IDEA it would warn that this file is too big and would skip formatting and analyzing it. We may implement similar or the same check, to prevent such problem.

Tested with build from main branch #483
IDEA 2022.1.4 & 2022.2.3


Add a responsive map in contact section.

For your reference: https://blog.duda.co/responsive-google-maps-for-your-website
website link: https://sharma-academy.netlify.app/

please assign this to me.

@KIET7UKE  Assign me this issue

@Chavda-Mitul @abhishekpatil4 assigning both of you.


Optimistically deleting an entity?

patchQueryResults and updateQueryResult make sense to me with regards to Update mutations. But I can't tell if optimistically deleting an entity is possible in a similar manner?
Referring to this area in the docs: https://rtk-query-docs.netlify.app/concepts/optimistic-updates

Do you mean deleting a whole cache key or deleting part of something cached?
The first doesn't really make sense - rtk-query will handle that in 60 seconds anyways and you don't know where else it is used.
As for the other thing, the example might not be clear enough: you can do everything within that other result:
          api.util.updateQueryResult('getPost', id, (draft) => {
            delete draft.foo;
            draft.bar = "hahaha"
          })

Do you mean deleting a whole cache key or deleting part of something cached?
The first doesn't really make sense - rtk-query will handle that in 60 seconds anyways and you don't know where else it is used.
As for the other thing, the example might not be clear enough: you can do everything within that other result:
          api.util.updateQueryResult('getPost', id, (draft) => {
            delete draft.foo;
            draft.bar = "hahaha"
          })

ahh okay yeah that helps! Thank you.


optimize: upgrade easyj-maven-plugin to 1.1.5 for support maven 3.9.0, and optimize github actions

optimize: upgrade easyj-maven-plugin to 1.1.5 for support maven 3.9.0, and optimize github actions

upgrade easyj-maven-plugin to 1.1.5 for support maven 3.9.0
优化github actions
github actions里，添加打印maven版本，用于参考。

Codecov Report

Merging #5402 (f68ca08) into develop (28b3413) will decrease coverage by 0.12%.
The diff coverage is n/a.

: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              @@
##             develop    #5402      +/-   ##
=============================================
- Coverage      48.69%   48.58%   -0.12%
+ Complexity      4187     4178       -9
=============================================
  Files            744      744
  Lines          26687    26687
  Branches        3332     3332
=============================================
- Hits           12995    12965      -30
- Misses         12295    12323      +28
- Partials        1397     1399       +2

Impacted Files
Coverage Δ

...ava/io/seata/server/metrics/MetricsSubscriber.java
29.56% <0.00%> (-11.31%)
:arrow_down:

...in/java/io/seata/server/session/GlobalSession.java
80.15% <0.00%> (-3.82%)
:arrow_down:

...in/java/io/seata/server/session/SessionHelper.java
63.63% <0.00%> (-1.82%)
:arrow_down:

...rage/redis/store/RedisTransactionStoreManager.java
75.71% <0.00%> (-1.31%)
:arrow_down:


making it readable

@4c74356b41 : Thanks for your contribution! The author, @rwike77, has been notified to review your proposed change.

@rwike77 - I'd recommend that you pull these commits to the private repo for staging, once pulled over, when private is merged to public this PR will be closed automatically.

@GitHubber17 I back your pardon?

@4c74356b41 , I pulled your commit into https://github.com/MicrosoftDocs/azure-docs-pr/pull/51621 and staged using our internal builds.  There were a lot of formatting changes, so I wanted to see a staged build before publishing.  Your updates look good. That new PR was just merged, which auto closed this PR here.  So your commits will publish live later this afternoon.  Thanks for your updates.

@rwike77 ok


Allow a graph vertex to take up more than one pixel

Right now, an underlying assumption is for each pixel in a raster to be a unique graph vertex, but this may not fit all use cases. Allow a single vertex to "occupy" multiple raster pixels in geographic space.
The lift shouldn't be too hard, but need to test that it works, particularly in converting paths or pathstates back to rasters.
Another consideration would be converting paths to lines. Right now path(s)_to_linestring(s) require a nodemap with unique node indices for every pixel. Maybe these functions just aren't offered in this case.

Needs to be developed with get_cartesian_indices() in mind -- right now, that function is fast because it relies on the nodemap being constructed in a certain way, but those assumptions will be broken in the above case.


mc quiz modeling page

In GitLab by @lakhoune on Oct 16, 2020, 13:00
this page should present an list of the questions which were already added. The user should be able to add new questions by clicking at a + button at the end of the page which will open generate a new question/ answers field

In GitLab by @lakhoune on Oct 16, 2020, 13:00
changed title from mc quiz modeling {-o-}age to mc quiz modeling {+p+}age

In GitLab by @lakhoune on Jan 17, 2021, 17:09
assigned to @jungerjunge2

In GitLab by @erdzan on Jan 20, 2021, 18:55
changed the description

In GitLab by @erdzan on Jan 20, 2021, 18:56
backend func. for mc cards for adding and updating implemented