fix: removed WinitPlugin from headless_renderer example

Objective
The headless_renderer example is meant to showcase running bevy as a headless renderer, but if run without a display server (for example, over an SSH connection), a panic occurs in bevy_winit despite never creating a window:
bevy_winit-0.14.1/src/lib.rs:132:14:
winit-0.30.5/src/platform_impl/linux/mod.rs:
neither WAYLAND_DISPLAY nor WAYLAND_SOCKET nor DISPLAY is set.

This example should run successfully in situations without an available display server, as although the GPU is used for rendering, no window is ever created.
Solution
Disabling WinitPlugin, where the above panic occurs, allows the example to run in a fully headless environment.
Testing

I tested this change in normal circumstances with a display server (on macOS Sequoia and Asahi Linux) and behavior was normal.
I tested with no display server by connecting via SSH, and running the example (on Asahi Linux). Previously this panics, but with this change it runs normally.

Considerations

One could argue that ultimately the user should not need to remove WinitPlugin, and instead bevy should only throw the above panic when the application first attempts to create a window.

Related to this change: from my own testing, the WindowPlugin settings above my change (e.g. setting primary_window to None) are not required, as they are redundant with adding ScheduleRunnerPlugin, which replaces the bevy_winit app runner and prevents a window from being created. Are there non-obvious performance reasons that the primary_window should be manually set to None? Or can these lines be removed?
DefaultPlugins.set(WindowPlugin {
   primary_window: None,
   exit_condition: bevy::window::ExitCondition::DontExit,
   close_when_requested: false,
}),

Its not that it doesn't do anything with WinitPlugin removed, it is that it has never done anything in this example, because of the ScheduleRunnerPlugin that has always been included. I agree that there should be a more explicit way of stating no window should be created, but I don't think I agree with the idea of configuring plugins a certain way for strictly documentation purposes. Happy to leave it in to get this merged, however, as I don't feel particularly strongly about it.
Note about my own experience though, I came to this example to learn how headless rendering works in bevy, and seeing the WindowPlugin lines instantly gave me several false assumptions about how bevy worked that I needed to dig into source code to dispel: that primary_window: None was the reason no window was created (it's actually the alternate app runner), that configs like exit_condition/close_when_requested were external to bevy_winit and so would still apply without a window (they don't), etcetera. So I personally would push for removing them completely, maybe with a new comment above the line that is actually preventing the window from being created (ScheduleRunnerPlugin). I think I would be a little confused coming to the example and seeing the primary_window: None line with a note saying it doesn't actually need to be there.

Added a commit with comments on both.

Definitely think it's weird that we don't just disable WindowPlugin too (or build this up from the new HeadlessPlugins). That said, this is a strict improvement from the existing code, so I'm merging it.


fix race conditions in the connection ID manager

Fixes #2239.

Codecov Report

Merging #2240 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2240      +/-   ##
==========================================
+ Coverage   86.36%   86.36%   +0.01%
==========================================
  Files         106      106
  Lines        7776     7779       +3
==========================================
+ Hits         6715     6718       +3
  Misses        797      797
  Partials      264      264

Impacted Files
Coverage Δ

conn_id_manager.go
93.81% <100%> (+0.2%)
:arrow_up:

Continue to review full report at Codecov.

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


On latest update when stopping, random solution planner error

When stopping, I got a random solution planner error.

This happens when manually breaking and towards the end of the stop


Add ComponentSelector const and enhance VerifyNetworkStatusFromAnnotation

Adds expectedCount to VerifyNetworkStatusFromAnnotation
If there are networkAttachments specificed, but the replicas count of a deployment is 0, this func will return false. This adds an expectedCount parameter and if 0, the func returns true for networkReady.

this requires follow ups to all the consuming operators ...

ack makes sense, will close this and will just not call it in that case in the operator


Updating values from rows view?

Is it possible to execute a SQL update query from changing the text and hitting enter or similar?

Currently - no. Im still trying to find some time and implement row editing functionality. It should be fairly straightforward as long as you try to edit rows in the "browse" mode. Editing rows in custom query result would be complicated and does not make sense.

I would also like to see this. As pgweb is a nice looking GUI, I thought it'd be targeting users who may not necessarily know SQL.
If you could update data through the row view, then someone like an office admin could use this pretty easily.

Hello dear Dan.
First off all thank You very much for your great work.
This project is very valuable and useful.
I will also appreciate very much if row editing and adding functionality is implemented and this feature will bring this wonderful project to whole new level of usability for many users.
Thank you very much.

@sosedoff I think I am missing something.  When:

I use the sidebar navigation and drill into a table (No custom query, no views)
Then I double click a row that has a value
I see a textarea box which allows me to change the value
However I see no way to save my change and issue the update

I am assuming this is what you mean by "Currently - no. Im still trying to find some time and implement row editing functionality."?
Using Chrome [58.0.3029.96 (64-bit)] on OSX [10.11.6 (15G1421)]

Thats correct, row editing is not supported in any form in pgweb at the moment. Textbox is meant to easily copy cell's data.

Hi @sosedoff, I need this for some of my projects. Can I work on this? I intend to extend the API to support insert/update/delete and update the UI to support modifying data.

@cheungpat Any chance you got around to adding editting functionality?

Man, the whole reason I was excited to use this was that I figured you could edit the data. Surprised that is not the case.

lol its still a wicked app, just missing some functionality. Id make a PR but id have to really dig into it to understand it all

Could we at least make the fields not change into an editable text box while this function isn't implemented? I have users coming to my desk confused all the time.

+1 readonly field
On Thu, Mar 14, 2019, 1:02 PM joe<EMAIL_ADDRESS>wrote:

Could we at least make the fields not change into an editable text box
while this function isn't implemented? I have users coming to my desk
confused all the time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sosedoff/pgweb/issues/215#issuecomment-473037780, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQLHtOxZG1_lmOLB4s_ac9S7EUGb-PQks5vWqrVgaJpZM4LmKMc
.

Agree with @joekohlsdorf I spent time on Google to find what I did wrong before reading this thread and understand I won't succeed in.

Got annoyed by this again today. The change is simple, in this line:
https://github.com/sosedoff/pgweb/blob/15c21b63793d5b8e6de252a76902fc09ff87f7cf/static/js/app.js#L1124
Change <textarea /> to <textarea readonly />.

I know +1s don't help but can this please be fixed, even the readonly option would help.

Inline textareas have been completely removed from pgweb in the latest release.
It's no longer needed since there's a context menu to copy the contents of the cell (right click).

3 years later, still can't edit data in a row? 🤪

You can with PgAdmin...

+1 for this feature. Unfortunately, was a deal-breaker for us.


Python3.x compatibility?

Naturally, at the moment this cannot be installed with Python3.4 and Python3.5
How difficult would it be to make it Python3.x compatible?

I would be interested in a python3 version, too.

I've created a PR #7 for this

’m happy to report that we’ve just released PySnpTools for Python 3! Just “pip install pysnptools”.
See https://pypi.org/project/pysnptools for details.
Everything from code & notebooks to API examples now runs on both Python 2.7+ and Python 3.7+.
Thanks for using PySnpTools.


[C++] Fix paused zero queue consumer still pre-fetches messages

Motivation
In C++ client, zero queue consumer (i.e. the consumer's receiver queue size is 0) will still pre-fetch messages after pauseMessageListener is called. It's because ConsumerImpl::increaseAvailablePermits doesn't check the boolean variable messageListenerRunning_, which becomes false after pauseMessageListener is called. Therefore, after the zero queue consumer is paused, it will still send FLOW command to pre-fetch a message to its internal unbounded queue incomingMessages_.
This behavior may cause some messages looks like being lost. For example, for a topic with 10 messages, start a shared consumer to consume 3 messages and pause. Then start another shared consumer to the same subscription. The new consumer will start from the 5th message because the 4th message is cached in the previous consumer.
Modifications
Here're the refactor changes:

Add a util function addAndGet to extend C++'s std::atomic with the Java like operation.
Change messageListenerRunning_'s type to std::atomic_int to avoid usage of mutex.
Change receiveMessages to sendFlowPermitsToBroker, which makes the method more readable and the checks for ClientConnection avoids lots of debug logs code outside the method invocation.

Based on the refactors above, the key changes are:

Add the check for messageListenerRunning_ in increaseAvailablePermits method, and make the implementation consistent with Java client's ConsumerImpl#increaseAvailablePermits. Also the type of availablePermits_ is changed to std::atomic_int.
Since pauseMessageListener doesn't pre-fetch messages any more, add the increaseAvailablePermits invocation in resumeMessageListener to send FLOW command after consumer resumes.

Finally the tests are added to verify the AtomicHelper's util function and the expected behavior of zero queue consumer.
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:

Add AtomicHelperTest for extended operation on std::atomic, which is like Java's atomic addAndGet.
Add ZeroQueueSizeTest.testPauseResume for the case I've described in Motivation section before. Here we use condition_variable::wait_for method but not Latch because the condition may never meet in the previous wrong implementation.

There's a C++ compile problem during building pulsar image. It's weird that cpp-tests passed but image build failed. I'll take a look.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


Improve logging by adding different levels

As a user/developer
I want to set a level of logging that is suitable for my usage
With options for debug, info and error
That can be configured at runtime
So that in production only errors are logged
And in development logs are very verbose

@charlesivie I believe this has been implemented and merge using Pino as the logger for both client and server.


New version of RCSFINTERACT (2021)

Critical bug fix by G. Gaigalas (May, 2021)
This version addresses a bug related to mismatching peel sheel ordering
in the multireference and full list. This can happen for larger, more
complex systems where correlation orbitals added in higher layers, might
end up before spectroscopic orbitals in the list of peel shells, using
standard ordering. This can lead to that a lot of CSF's are removed in
the reduction that should in fact be in there, just that the peel order
is different. The present proposed fix by Gediminas adds an
additional check for this which increases the runtime, but is necessary
to avoid critical mistakes that may pass unnoticed.
This bug fix is to consider as critical and should be adopted by all
users who make use of CSF list reductions using this code immediately.
The main change is the addition of the following (row 90-96) lines in set_CSF_list.f90
      I = LEN_TRIM(S_orbitals_1)
      IF(S_orbitals_1(1:I) /= S_orbitals_2(1:I)) then
         WRITE (6, *) ''
         WRITE (6, *) 'Error in input !!!'
         WRITE (6, *) 'Different order of Peel orbitals'
         STOP ' in files rcsfmr.inp and rcsf.inp'
      end if

You can also press "Files changed" in the menu above - where you can also comment in individual lines etc by pressing the plus sign in the code - don't worry if you do something strange, we can always revert things.
Since this is critical we should try to merge this within a few days - I will give you until Friday this week.
Feel free to comment and suggest additional improvements!
Cheers,
Jon

I forwarded this critical patch information to both Kai, Ran and Sacha since I am wondering if this could not be the source of our problems in Kai's Th+ gf-calculations (Gamrath et al., MNRAS  2018, 480, 4754) and also in Ran's Er I and Fm I excitation energies...

Great @mrgodef, thanks! And thanks also to @mortenpi for the review. I'll merge this now.

Are you merging files or listening to Sema Caliskan ?
😉
Prof. Michel R. Godefroid
Spectroscopy, Quantum Chemistry and Atmospheric Remote Sensing (SQUARES)
Université libre de Bruxelles – CP160/09
50, av. F.D. Roosevelt
B 1050 Brussels, Belgium
Tel: +32-2-650 30 12
Fax: +32-2-650 42 32
Email: @.***
Url: http://www.ulb.ac.be/cpm/
From: Jon Grumer @.>
Reply to: compas/grasp @.>
Date: Friday, 21 May 2021 at 15:53
To: compas/grasp @.>
Cc: Michel Godefroid @.>, Mention @.***>
Subject: Re: [compas/grasp] New version of RCSFINTERACT (2021) (#65)
Merged #65https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcompas%2Fgrasp%2Fpull%2F65&data=04|01|michel.godefroid%40ulb.be|d1c0de54cd47452266c708d91c5fd401|30a5145e75bd4212bb028ff9c0ea4ae9|0|0|637572020211209906|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=GxnkragbqbtCYDtfJjZYs88m72You4GELOgqkoag7Pc%3D&reserved=0 into master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcompas%2Fgrasp%2Fpull%2F65%23event-4779431205&data=04|01|michel.godefroid%40ulb.be|d1c0de54cd47452266c708d91c5fd401|30a5145e75bd4212bb028ff9c0ea4ae9|0|0|637572020211209906|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3Ea23OFpsEwkH5%2FfYjpP%2BCK03gFFqkMiss02QOzpUzE%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADTNJTWCB23TF4J62PIGH6TTOZQV3ANCNFSM45CHJ45Q&data=04|01|michel.godefroid%40ulb.be|d1c0de54cd47452266c708d91c5fd401|30a5145e75bd4212bb028ff9c0ea4ae9|0|0|637572020211219860|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=5%2F0PFNFE4%2FI6X2uFnZ%2BgqsZXSbLPcPdlzDuDrgYdVvM%3D&reserved=0.

Haha so observant! Just pressed the merge button now that the tests were finished, also just saw a short version of her presentation a few days ago ;)


Check if interface is implemented

nice module! is there a way to check at runtime if an interface is implemented by a class / instace?

Hi @21stio.  Thanks for your interest in inferface!
There isn't currently a public API for checking if an object/class implements an interface.  The closest thing is Interface.verify(type), which is what gets called at class creation time when you declare that you implement an interface, but that function is fairly expensive when it fails, because it spends a lot of effort building nice error messages.
I think it makes sense to add a function that just gives back a boolean indicating whether an object/type implements an interface (though I confess I haven't actually needed such a function yet in using interface, which is why it currently doesn't exist).  What would you expect the behavior of such a function to be?  If we added a function named something like check_implements (actual name TBD), I can think of a few potential axes of variation.

Would check_implements(obj, IFace) expect obj to be a type or an instance?  Would we want separate methods for objects and types (analogous to the built-in isinstance/issubclass functions)?
Would check_implements just verify that the object it receives was declared as implementing IFace, or would it dynamically verify that the interface is actually implemented?  The former would likely be much faster, but I could imagine use-cases for both behaviors.

This module makes perfect sense!
I too would really like that boolean check method. My suggestion:

'instance_implements(obj, IFace)' and 'class_implements(cls, IFace)' (analogous to the built-in isinstance/issubclass functions)
Since the actual implementation is checked at class creation, wouldn't it suffice to do the former check, i.e. check that it was declared as implementing 'IFace'?

I just ended up using classes with methods that throw NotImplemented when not being overwritten.
This validation only happens when the method is called tho.
Like this you have full is_instance support, ides let you override methods etc.
just my 2 cents

Since the actual implementation is checked at class creation, wouldn't it suffice to do the former check, i.e. check that it was declared as implementing IFace?

That would work in most cases, but it wouldn't work if you dynamically added or removed interface methods from an object's type after the type was created (class decorators like the new dataclass decoroator in the stdlib often do this, for example).

@dremok @21stio I'd be curious to see if you have concrete examples where you think this functionality would be useful.  My general belief is that idiomatic usage of interface shouldn't require runtime interface checks.  My general usage pattern usually looks like:
class SomeInterface(Interface):
    pass

class SomeImplementation(implements(SomeInterface)):
    ....

class SomeOtherImplementation(implements(SomeInterface)):
    ...

def some_function(arg):  # expects arg to implement SomeInterface
    # Call interface methods on arg.

For this kind of usage, the only thing I could imagine wanting to do with instance_implements and class_implements is use them for assertions, but it's generally more idiomatic to just try to use the object and fail with an AttributeError/TypeError if the received object is incorrect.

@ssanderson Ah, you're right about dynamically added methods, didn't think about that.
Assertion is exactly what I was planning on using these methods for. I have a unit test which calls a method which returns a list of stuff, where the objects are implementing different interfaces. Then I wanted to do different assertions depending on the interface type. But I guess I should really redesign, or just ask for forgiveness instead of permission...

Hi @21stio. Thanks for your interest in inferface!
There isn't currently a public API for checking if an object/class implements an interface. The closest thing is Interface.verify(type), which is what gets called at class creation time when you declare that you implement an interface, but that function is fairly expensive when it fails, because it spends a lot of effort building nice error messages.
I think it makes sense to add a function that just gives back a boolean indicating whether an object/type implements an interface (though I confess I haven't actually needed such a function yet in using interface, which is why it currently doesn't exist). What would you expect the behavior of such a function to be? If we added a function named something like check_implements (actual name TBD), I can think of a few potential axes of variation.

Would check_implements(obj, IFace) expect obj to be a type or an instance?  Would we want separate methods for objects and types (analogous to the built-in isinstance/issubclass functions)?
Would check_implements just verify that the object it receives was declared as implementing IFace, or would it dynamically verify that the interface is actually implemented?  The former would likely be much faster, but I could imagine use-cases for both behaviors.

I was actually expecting that the standard isinstance function would work for checking if an object implements a certain interface

Hi,
Am I reviving a dead thread? Hope @ssanderson is still around to react.
In any case, one example I can come up with that does require such a checking method: when external code that wasn't written using your Interface needs to be checked if it has the necessary methods. Imagine some public protocol that has several implementations that need to work together - your code may use Interface but someone else's code doesn't. This is pretty straightforward with the subclasshook/check that's used with abc.
BtW, I really like your implementation of interfaces. I was not satisfied with abc and kept thinking why a better implementation didn't exist, then one day I searched around a bit and found this project. Awesome!

In any case, one example I can come up with that does require such a checking method: when external code that wasn't written using your Interface needs to be checked if it has the necessary methods. Imagine some public protocol that has several implementations that need to work together - your code may use Interface but someone else's code doesn't. This is pretty straightforward with the subclasshook/check that's used with abc.

I think checking implementations on types that are outside your control is a reasonable use-case. Something like the following seems reasonable to me, for example:
class MyInterface(Interface):
    # Declare methods

class MyImpl(implements(MyInterface)):
    # Implement methods.

from not_my_module import OtherImpl

# Raises a TypeError if OtherImpl isn't a valid implementation of MyInterface.
expect_type_implements(OtherImpl, MyInterface)

I'm less confident that runtime checking on instances is a reasonable thing to support, e.g.:
class MyInterface(Interface):
    ...

def my_function(obj):
    """``obj`` must implement MyInterface
    """
    expect_instance_implements(obj, MyInterface)
    # Use interface methods.

BtW, I really like your implementation of interfaces.

Thanks!


feat(core): propagate add operation to m:n owner even if not initialized

Previously we propagated adding only to initialized collections. This means that we could ignore some changes like adding items from the inverse side that. Now we propagate the add operation to the owning sides of M:N relations even if they are not initialized.
Closes #3240

Codecov Report

Merging #3273 (64f681a) into master (1c56e7a) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master     #3273   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          194       194
  Lines        12122     12129    +7
  Branches      2810      2815    +5
=========================================
+ Hits         12122     12129    +7

Impacted Files
Coverage Δ

packages/core/src/entity/ArrayCollection.ts
100.00% <100.00%> (ø)

packages/core/src/entity/Collection.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Libcloud 782 remove dreamhost vps driver

DreamHost removed support of public API for its VPS product so the driver doesn't work anymore. Documentation and driver should be removed.
DreamHost products are still supported by libcloud using the generic OpenStack driver though, so there is no need to remove DreamHost's logo from the website or other parts of the documentation.

thanks @smaffulli should we leave documentation somewhere pointing users to the openstack driver?

That's a great idea, thanks for suggesting it. Any suggestion of where would be a good place to mention that?

Since the driver no longer works. I'll merge this since we don't want to ship a non-functioning driver, the removal will be included in the release notes and _supported_providers will include a mention

Thank you. Do I need to do something with the Jira ticket? https://issues.apache.org/jira/browse/LIBCLOUD-782


Details on .NET memory management requirements/gotchas

Based on lessons learned from hosting ChakraCore in a larger application, I'd have appreciated if the samples/docs had given some guidance on gotchas related to .NET memory management.
Specifically, I had hard to diagnose and understand problems with access violations, ChakraCore telling me that it was running on the wrong thread, etc. which all came from interop issues with callbacks.
Specifically, the .NET GC was collecting delegates which had been passed to ChakraCore (in my case through JsCreateFunction and JsSetPromiseContinuationCallback), which made it so that all unit tests were running fine but when running in the application with some memory pressure things started go awry.
I ended up adding a layer on top of Native.cs which creates and manages GCHandle (Normal mode, not pinned) instances for all delegates passed into ChakraCore APIs. When a context or a runtime is released, it will automatically release the associated GCHandles. With that all problems vanished...

Hi @avonwyss . This is the wiki detailing ChakraCore's memory management. I added a small para at the end for .NET.

Specifically, the .NET GC was collecting delegates which had been passed to ChakraCore (in my case through JsCreateFunction and JsSetPromiseContinuationCallback), which made it so that all unit tests were running fine but when running in the application with some memory pressure things started go awry.

The AV problem you mentioned is indeed because .NET GC is not aware of ChakraCore GC references. There were some discussions long ago about how to get around that.

ChakraCore telling me that it was running on the wrong thread

Is a different issue because of ChakraCore's rental threading design.

Hi @liminzhu
Thank you for the quick reaction. I think it would be best to somehow include this into the .NET samples, which is why I posted it here.
Regarding the wrong thread error, in my case it was really caused by the memory corruption; I had locks around every single access to JS context and the problem was intermittent with the AV errors. Also, it did not behave the same with and without debugger (got the wrong thread usually without debugger, and AV with debugger).
Note that pinning is not necessary and not advisable, keeping a Normal GCHandle is entierly sufficient. See also the GCHandleType docs.

I think it would be best to somehow include this into the .NET samples, which is why I posted it here.

Generally agree with your sentiment. Will try to come up with some short code snippet and documentation as said in https://github.com/Microsoft/ChakraCore-wiki/issues/5. Meanwhile, feel free to send a PR against Chakra-samples if you're interested in getting a sample online 😄.

Regarding the wrong thread error, in my case it was really caused by the memory corruption; I had locks around every single access to JS context and the problem was intermittent with the AV errors. Also, it did not behave the same with and without debugger (got the wrong thread usually without debugger, and AV with debugger).

Do you have a short repro I can play with? I would love to look more into it.

Note that pinning is not necessary and not advisable, keeping a Normal GCHandle is entierly sufficient. See also the GCHandleType docs.

Yep, I meant extending the lifetime at least till callback/object is no longer needed.


Modal DatePicker

Is it impossible add feature show panel in a modal like this.

Hi @kindslayer, Yes, for such purposes, use <Calendar/> instead of <Datepicker/>. You can put calendar in any modal wrapper like Rodal


clean up .github/workflows/rebase.yml (FINERACT-829)

re. FINERACT-829 (still doesn't seem to work, but if I do get it to work later, this is needed anyway)

@xurror I've also self merged this, to try if and see if /rebase works e.g. on #881 now..


Check app service tunnel status before connecting tunnel proxy

Addresses issue in Microsoft/vscode-azureappservice#435

Thanks, let me verify with a few other people that this is working for them. It works with my personal testing, but I have sent out a .vsix for others to verify. I'll report back later today.

There was just some feedback about cleaning up the logging a bit. It's ready to merge and publish now. Let me know what the process would be to get this out with the next appservice extension release.

Published! This will automatically be included in the next release and we try to release approximately monthly. Let me know if you need more detail than that


New version: Yandex.Messenger version 2.207.0

Created by 🥟 Dumplings in workflow run #6951.

Log
Updated: 2.206.0 → 2.207.0
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run


Rationale behind host network mode

Hi,
as you probably know the Docker's host network mode has its limitation. Please, could you explain why it's the only network mode supported? Have you tried adding support for the other modes, e.g. bridge?

ok, thx


Col component TS error with align prop

Describe the bug
When using the Col component, I get a typescript error when using the align prop even though it works.
Steps to reproduce

Add a new project
Import Col
Add align prop e.g. <Col align="center" />
See error

Expected behaviour
Have no TS error
Screenshots
If applicable, add screenshots to help explain your problem.
Environment / Context
1.0.2-beta.4

strange since there is no such prop named align for column component , I don't think it should work

Hey @samfromaway just as @Dhananjay-JSR there’s not a prop called ‘align’ for ‘Col’ component, here’s the API https://nextui.org/docs/layout/container#col-props

Ok interesting that it still centers the elements in Col.


Markdown Preview not rendering mp4 in video tags

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

VS Code Version: 1.76.0 Insiders
OS Version: Windows 11, macOS 12.6.3

Steps to Reproduce:

Open the vscode-docs repo and open the v1_76.md release notes file
Open Markdown Preview

.mp4 videos such as used in the "Rich Content Notebook Search" section don't render.

1.75.1 Stable still show .mp4 videos with auto start rendering correctly.

I'm able to reproduce with the same OS and VS Code versions.

Repro's on macOS as well

🤔 this works for me in .dev

But doesn't work on desktop

network request in vscode.dev

network request in insider's

Confirmed that this issue also affects the in-product release notes.


SVG rendering issue

Attach (recommended) or Link to PDF file here:
cio6.pdf
Configuration:

Web browser and its version: node.js 10.15.0
Operating system and its version: centos7
PDF.js version: latest from master
Is a browser extension: no

Steps to reproduce the problem:

node examples/node/pdf2svg.js cio6.pdf

What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)

This is the warnings in the console when converting (just for page 1):
Size: 612x792

Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator beginGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented operator endGroup
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask
Warning: Unimplemented graphic state BM
Warning: Unimplemented graphic state SMask

@timvandermeij Any plans on implementing soft masks in the SVG backend? Is there anyone who is familiar with the backend and knows how to implement it?

There is no plan to implement this yet, but we're open to contributions for this.

I want to know what the cause，just implement？


Job Robert Sanya - missing qualifications for all skills

https://lead.asknet.community/profiles/27-Job-Robert-Sanya/

[ ] Update Skill Qualifications

#43 can you follow up on this @romeoplat

I removed this skillset that was present in your profile, if you find time please update using the new form linked above
skills:
  - {name: Web & Software, number: 1, qualification: ''}
  - {name: Hardware & Repair, number: 2, qualification: ''}
  - {name: Community & Moderation, number: 3, qualification: ''}
  - {name: Organizational Development, number: 4, qualification: ''}
  - {name: Media & Art, number: 5, qualification: ''}
  - {name: Open Source & Knowledge, number: 6, qualification: ''}

resolved via #284 #301

so closing


Planrepos autopopulate

I noticed that scheduled planrepos are not showing up in my review UI.
This turns out to be because they are not getting PlanRepos.
This turns out to be because the old PlanSchedule code that I revived doesn't set the PlanRepo.
This is probably because PlanSchedules predate PlanRepos.
Rather than just set the PlanRepo in the PlanSchedule code, I thought it would be better to fix it at a lower level so that if anyone forgot in any context in the future, the __init__() or save() would infer them.
Of course there were no tests for Build __init__ or save() so I had to add a few of those too...

I guess I misunderstood the side effects of creating a PlanRepository.
I'm still confused. PlanRepositories don't refer to branches, so how could it trigger builds? Don't you need a branch or some kind of branch specification to trigger build?
I have been thinking of PlanRepositories as primarily a hook for hanging permissions upon.
Wouldn't it be a "Plan Repository Trigger" which triggers builds?

PlanRepository is what connects a plan to particular repositories. When a github webhook comes in, if there is an active planrepo for the repository where the plan's trigger == 'commit' and plan's regex matches the branch from the webhook, that will create a new build.
PlanRepositoryTrigger is for a different use case: triggering a build in repo Y from builds in repo X (i.e. Abacus depends on NPSP and wants to run a build whenever there are changes to its dependency)


Auto-create access and admin organizational roles in root workspace

Is your feature request related to a problem? Please describe.
We're trying to land on a reasonable set of bootstrap RBAC policies that get added along with organizational workspaces.
Describe the solution you'd like
Having two roles applied to the root workspace:

<org-name>-access: Grants access verb to org workspace
<org-name>-admin: Grants edit verb to org workspace (should translate to cluster-admin)

This should likely be implemented in the organizational workspace controller.

Actually, the current workspace authorizer automatically applies to orgs already by applying the following clusterworkspaces/content verb to group mapping: https://github.com/kcp-dev/kcp/blob/main/pkg/authorization/workspace_content_authorizer.go#L126


AttributeError with LightningModule forward without Trainer

🐛 Bug
LightningModule with Lightning 1.4 assumes to always have the self.trainer not None. No issues with 1.3
To Reproduce
import pytorch_lightning as pl

class MyModule(pl.LightningModule):
    def forward(self, *args, **kwargs):
        self.log_dict({"key": 0})

print(pl.__version__)

model = MyModule()
model()

Outputs:
1.4.0
Traceback (most recent call last):
  File "/home/luca/Projects/CookieTesting/my-new-project/src/my_new_project/commands/mymodule.py", line 11, in <module>
    model()
  File "/home/luca/miniconda3/envs/my-new-project/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/luca/Projects/CookieTesting/my-new-project/src/my_new_project/commands/mymodule.py", line 6, in forward
    self.log_dict({"key": 0})
  File "/home/luca/miniconda3/envs/my-new-project/lib/python3.8/site-packages/pytorch_lightning/core/lightning.py", line 507, in log_dict
    self.log(
  File "/home/luca/miniconda3/envs/my-new-project/lib/python3.8/site-packages/pytorch_lightning/core/lightning.py", line 407, in log
    results = self.trainer._results
AttributeError: 'NoneType' object has no attribute '_results'

Expected behavior
If the Trainer and/or logger are not defined, the log and log_dict calls should be only ignored.
Environment
* CUDA:
        - GPU:
        - available:         False
        - version:           10.2
* Packages:
        - numpy:             1.21.2
        - pyTorch_debug:     False
        - pyTorch_version:   1.9.0
        - pytorch-lightning: 1.4.0
        - tqdm:              4.62.3
* System:
        - OS:                Linux
        - architecture:
                - 64bit
                - ELF
        - processor:         x86_64
        - python:            3.8.11
        - version:           #40~20.04.1-Ubuntu SMP Sat Sep 18 02:14:19 UTC 2021

Additional context
The problem is caused by this line:
https://github.com/PyTorchLightning/pytorch-lightning/blob/ab069876cb19bb9de0179f74c6f83764876a73ff/pytorch_lightning/core/lightning.py#L398
Related PR: https://github.com/PyTorchLightning/pytorch-lightning/pull/7891
@carmocca

self.log_dict({"key": 0})

log_dict is something specific to lightning which is handled by trainer and loggers. So I guess a trainer is required here?

My use case is to re-use the same LightningModule code for training (with the trainer and loggers) and inference/predictions (without the trainers and loggers)

Previous answer on this:
https://github.com/PyTorchLightning/pytorch-lightning/issues/8509#issuecomment-926244005

seems reasonable. just curious, if you are logging inside forward function then how are you differentiating the log keys since forward will be used for training/validating/testing I assume?
you can actually prevent it if you want by simply not calling log_dict during inference using some sort of boolean argument.

Actually, calling self.log or self.log_dict inside forward is highly discouraged. forward should be kept a pure function to compute the network's outputs. Please call it in one of the *_step functions instead! That's exactly what they are for.

if you are logging inside forward function then how are you differentiating the log keys since forward will be used for training/validating/testing I assume?

It will use the *_step method name that called forward


Proposal: Add resource groups filter to azure service discovery

Proposal
Since ARM API requests are rate-limited in Azure, it would be good to be able to reduce the load posed by Prometheus Azure Service Discovery. Especially when running multiple AKS clusters on a single subscription, running Prometheus servers on each, this problem is multiplied. So an additional reduction by resource group would be really good.
Use case: Non-AKS related VMSS residing in a specific resource group which should be discovered by a single prometheus server instance.
Filter could reduce the amount of getScaleSetVMs calls by filtering by resource group:
https://github.com/prometheus/prometheus/blob/5851557a288eb695c7fa450be3c8884ae446bee3/discovery/azure/azure.go#L302-L308
Filter could reduce the amount of getNetworkInterfaceByID by reducing the machines set:
https://github.com/prometheus/prometheus/blob/5851557a288eb695c7fa450be3c8884ae446bee3/discovery/azure/azure.go#L320
https://github.com/prometheus/prometheus/blob/5851557a288eb695c7fa450be3c8884ae446bee3/discovery/azure/azure.go#L351

Thanks for your input. Yes, this would be a great feature.

I'm looking at implementing this, but not sure how to get the current resource group a Prometheus instance is in. Would this be an additional config value, or is there a way to look it up?

@jrauschenbusch I implemented this feature, but don't have access to Azure resources to test my changes. Are you able to test this or know someone who can?

Will close this ticket as it's now implemented and merged.


Fix on surface groups view

Fixed view of surface groups to be displayed correctly with new version o SC.

Closing due to https://github.com/StarcounterApps/Website/pull/172


There is no Android Launcher in the portal

Hello,
yesterday i received the email about the release of the android launcher. Unfortunately I cannot see it in the portal to download it. Just in the sandbox portal, but in the production. Do i something missing here?
Is it only Android 7 compatible? Because our cash systems are running on Android 5, so is there an possibitlity to make the launcher backwards compatible?

Hello @vaztimur,
thanks for reaching out! The Android Launcher is currently only available on the sandbox because we are trying to collect feedback from users before pushing it to the production Portal, but we'll enable it there as soon as possible.
Regarding Android 5: I think re-targeting to Android 5 would be technically possible, but require some additional work. Could you please reach out to<EMAIL_ADDRESS>with some details about your scenario to help us prioritize this?
Thanks!
Tom

Closing this now, as the Android Launcher is available in production for quite some time now. Thank you very much for your questions 🙂


Adjust isort configuration to resolve import issues

Some of the changes made by isort were causing NameError during internal regressions. To fix this, I have adjusted the isort settings to resolve these issues.

Codecov Report

Merging #374 (af4d6e8) into main (85e1c76) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #374      +/-   ##
==========================================
- Coverage   49.71%   49.70%   -0.01%
==========================================
  Files          94       94
  Lines       16602    16601       -1
==========================================
- Hits         8253     8252       -1
  Misses       8349     8349

Impacted Files
Coverage Δ

src/ansys/meshing/prime/core/surfaceutilities.py
60.00% <ø> (ø)

src/ansys/meshing/prime/__init__.py
92.40% <100.00%> (-0.10%)
:arrow_down:

src/ansys/meshing/prime/core/controldata.py
73.33% <100.00%> (ø)

src/ansys/meshing/prime/core/fileio.py
45.45% <100.00%> (ø)

src/ansys/meshing/prime/core/model.py
82.69% <100.00%> (ø)

src/ansys/meshing/prime/core/part.py
51.16% <100.00%> (ø)

src/ansys/meshing/prime/core/periodiccontrol.py
47.36% <100.00%> (ø)

src/ansys/meshing/prime/core/sizecontrol.py
84.21% <100.00%> (ø)

src/ansys/meshing/prime/core/surfer.py
84.00% <100.00%> (ø)

src/ansys/meshing/prime/core/volumecontrol.py
63.15% <100.00%> (ø)

... and 3 more

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


[WIP] adding first BEP010 spec

This is an attempt at adapting the BEP010 spec for this repository. There are probably a bunch of things to update, but it'd be helpful if I could get some high-level feedback on this one.
For example, I basically just tried to adapt word-for-word the google docs version. However, there's probably some redundant information with the base BIDS spec etc. Feel free to recommend sections to remove, move around, etc. Other than that, let me know what I should do. @chrisfilo do you have thoughts on this? Or can you ping somebody who went through this with the MEG spec?

I pointed out some obvious sections with redundancy, but there are plenty of others. Especially referring to BIDS-fMRI, BIDS-MRI, BIDS-iEEG is confusing - those should be replaced with links to specific sections of the spec. You should check out https://github.com/bids-standard/bids-specification/pull/108 and https://github.com/bids-standard/bids-specification/pull/109 for inspiration.
PS I don't quite remember who did the reformatting and merging of MEG.


Build no longer working [Could not locate a valid AppDelegate at root]

Build/Submit details page URL
https://expo.dev/accounts/librex/projects/rtro/builds/96097dbf-c26e-4623-91a7-43df3744bda9
Summary
Setting the update request headers in 'Expo.plist' to '{"expo-channel-name":"production"}'
Could not locate a valid AppDelegate at root: "/Users/expo/workingdir/build/apps/mobile"
Please report this as an issue on https://github.com/expo/expo/issues
Managed or bare?
bare
Environment
expo-env-info 1.2.0 environment info:
System:
OS: macOS 14.3.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.19.0 - ~/.nvm/versions/node/v18.19.0/bin/node
Yarn: 1.22.22 - ~/projects/PX2_Mono/apps/mobile/node_modules/.bin/yarn
npm: 10.2.3 - ~/.nvm/versions/node/v18.19.0/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5
Android SDK:
API Levels: 28, 29, 30, 31, 33, 34
Build Tools: 30.0.2, 30.0.3, 31.0.0, 33.0.0, 33.0.1, 33.0.2, 34.0.0, 35.0.0
System Images: android-33 | Google APIs ARM 64 v8a, android-34 | Google Play ARM 64 v8a
IDEs:
Android Studio: 2023.3 AI-233.14808.21.2331.11709847
Xcode: 15.4/15F31d - /usr/bin/xcodebuild
npmPackages:
expo: ^50.0.14 => 50.0.14
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: ^0.73.5 => 0.73.5
npmGlobalPackages:
eas-cli: 9.1.0
Expo Workflow: bare
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check for issues with metro config
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check native tooling versions
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that native modules use compatible support package versions for installed Expo SDK
✔ Check that packages match versions required by installed Expo SDK
Didn't find any issues with the project!
Error output
[INSTALL_PODS] Pod installation complete! There are 114 dependencies from the Podfile and 168 total pods installed.
[INSTALL_PODS] [!] Can't merge pod_target_xcconfig for pod targets: ["expo-dev-menu", "Main", "ReactNativeCompatibles", "SafeAreaView", "Vendored"]. Singular build setting DEFINES_MODULE has different values.
[INSTALL_PODS] [!] Can't merge pod_target_xcconfig for pod targets: ["expo-dev-menu", "Main", "ReactNativeCompatibles", "SafeAreaView", "Vendored"]. Singular build setting DEFINES_MODULE has different values.
[INSTALL_PODS] [!] hermes-engine has added 1 script phase. Please inspect before executing a build. See https://guides.cocoapods.org/syntax/podspec.html#script_phases for more information.
[CALCULATE_EXPO_UPDATES_RUNTIME_VERSION] Resolved runtime version: 1.0.1
[CONFIGURE_XCODE_PROJECT] Configuring Xcode project
[CONFIGURE_XCODE_PROJECT] Assigning provisioning profile '*[expo] com.rtro AppStore 2024-02-23T12:35:43.285Z' (Apple Team ID: 2BKZ3YTY2W) to target 'rtro'
[CONFIGURE_EXPO_UPDATES] Setting the update request headers in 'Expo.plist' to '{"expo-channel-name":"production"}'
[CONFIGURE_EXPO_UPDATES]
UnexpectedError: Could not locate a valid AppDelegate at root
Reproducible demo or steps to reproduce from a blank project
could not replicate on a blank, currently using a lot of libraries in the project.

@lander854 can you try to update your project dependencies npx expo install --check?

@lander854 have you managed to fix that? And how?

@makbeth what I did was move the project outside of the monorepo, seems like expo EAS is doing a shallow copy when used in a monorepo, missing some deep nested files


Seperate Tutor and Homework exercises in the stats tab

I think it might be helpful to separate the tutor exercises from the homework exercises in the statistics section, so that we can get a better visual representation of how we are doing.

I think tutor exercises, in the course you are implicitly referring to, are all scored with 0 points, so they should not count into the statistics.
You can ask your instructors to use tags with different colors to make sure the exercises can be distinct more easily.
In the future we might allow to sort exercises after tags in the statistics, but for now this is out of scope


Unexpected behavior when debugging standard library

Environment data

VS Code version: 1.37.1
Extension version (available under the Extensions sidebar): 2019.8.30787
OS and version: Regolith (Ubuntu 19.04)
Python version (& distribution if applicable, e.g. Anaconda): 3.7
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: asyncio
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): true

Steps to reproduce:
Create a Python module to run asyncio code:
import asyncio

async def main():
    print("Hello, world!")

if __name__ == "__main__":
    asyncio.run(main())

Create the following launch configuration:
{
            "name": "Debug",
            "type": "python",
            "request": "launch",
            "module": "main",
            "justMyCode": false
}

Place a breakpoint at /usr/lib/python3.7/asyncio/base_events.py:405, then launch the debugger with Python 3.7. You will arrive at the line:
task = tasks.Task(coro, loop=self)

Click the "step in" button.
Expected behaviour
You arrive at the first line of tasks.Task.__init__.
Actual behaviour
You arrive at /usr/lib/python3.7/asyncio/base_events.py:1794, in BaseEventLoop.get_debug.
Logs
No output in Developer console or Output console.

I can't see any obvious reason for this. According to the debugger, the symbol tasks.Task points to the Task class, it hasn't been overwritten or anything. Nobody's overriding __call__. Is this a bug in the debugger?

Hi @geajack, thank you for reporting this!
@karthiknadig would this be a ptvsd issue?

Yep this is a debugger issue. Will transfer this to ptvsd repo.


VancedMicroG doesn't give storage permission by default which causes YTVanced to crash over and over

I am using a Vivo IQOO 5 with android 10 non rooted device, i installed VancedManager and then proceed to install VancedMicroG, login to account,and install YTVanced. The first time i open YTVanced it works perfectly, if i don't kill the app, it keeps working perfectly. But if i kill the app and try to open it, the vanced logo pops up and the app close by himself. I tried this with different version of YTVanced and VancedMicroG and the result was always the same, it kept crashing after the first time you open the app. And i figured that it was because VancedMicroG hadn't storage permissions and that it needed to be manually set to "allow". Once the permission is given, the app works as it is supposed to work.

Bruh why are you even killing the app. It's supposed to run all the time. There is a reason why it needs battery optimization to be disabled, to prevent system from auto killing it. And storage permission can't be granted automatically. You have to manually do it.


Activate problem

If you select two items together at the same time then both items will be activated.

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @pakrentos, @gerxiu, @ybgirgin3, @LetmeBX, @SuyasAgnihotri, @luis-protofire, @SeonjaeHyeon

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @r-rishabh-j, @Liscivia, @tzookb, @Daniel194, @lvgm-protofire, @userxwhoami, @tphilip1116

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @batuhand, @ivkatic, @lucasstoller, @jesusxy, @Blackdevilo3, @mohdxnizamv, @amine123ait

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @raphaelcarlosr, @KnightSoul9, @frtendero, @itsVagabond, @killerkc12, @blackman818, @omaralqady


Fix #12 - Make rayon optional with maybe_parallel_iterator.

This PR introduces a dependency on maybe_parallel_iterator to make rayon optional, adding much better support for WebAssembly. The default is to use rayon, matching the old behavior. Clients can pass default-features=false in their Cargo.toml to avoid it.
Full disclosure: I am the author of maybe_parallel_iterator, which is currently a wrapper around rayon.
Fixes #12

Thanks for this, looks good to me.


Allow results to be filtered by location

Feature
Why is this feature being added?

What should your feature do?

I'd like to try this one. Are there any information or instructions? @rickr

Any direction on this on @rickr

Ah, I think this is dependent on the events endpoint being finished.

@sabrown84 I'm working on the events endpoint. The UI goal is to show events local to the user first, but right now I am just providing the events as json from our API. I am saving the events to the database, so you should be able to access whatever you need. There was some chatter about this being done on the front end. I don't know if anyone has jumped on this on the frontend yet, probably waiting for me!
I can get a WIP pull request hopefully this week so you can see the data format.


Support for Actionable Notifications

The Physical Web project should be able to support actionable notifications as an enhancement, for quick actions. Quick actions are links to more things (URL's or deep links in the app, exposed via an Intent like mechanism.).They give fast 1-click access to frequently used features in the service (without having to visit the webpage).This can be be achieved in a variety of ways.

The Website's manifest file can include quick actions that are supported by the site.
The Website's response could also alternatively include additional HTTP header(s?) to advertise opt-in for this feature. Something like X-PHYSICAL-WEB-NOTIFICATIONS.

Essentially actionable notifications would be discovered by the Physical Web proxy service, and notifications would become richer.
The data included in the manifest for Actionable notifications could look like:
[
  {
    "icon": "icon_url",
     "title": "The Title of the actionable Notification",
     "link": "deep_link_or_url"
  },
 {..}
]

Support for these notifications  would then be built into the Physical Web App using Notification.Builder in Android and its equivalent in iOS.
Comments / Feedback is greatly appreciated. If everyone is okay with the idea, I would like to work on this.

Thanks @tikurahul that's a great suggestion. We actually played around with this a few months ago and did a quick demo around the concept: https://www.youtube.com/watch?v=2J_BMDgnZBY The video shows an android watch notifying you when you're close and giving you a single clean action to do. As we get into personalized interfaces, this becomes even more valuable as the only thing you're likely to want can be exposed.
We didn't use web manifest but JSON+LD, which returned a schema.org action. We ran into a few issues that need a bit more discussion. The first is that schema.org's hierarchy of actions was quite specific, it was hard to find a generic 'buy' action. We had to kind of hack something in to make that happen.
The other issue is a bit more around positioning/safety. If we have these short actions, what do we need to have in place to protect users? There could be an 'info' command that actually is a buy command for example. For example, could this only work if you've gone to the full website first (and have a cookie installed?) the arguement is that you have the full experience first to validate and be clear it's what you think it is. There are lots of ways to proceed with this. If anyone has pointers to any web standard that would be applicable, please chime in.
I'm perfectly fine using the web manifest, there is a previous issue here discussing the many values of that and we're on board with it. We can certainly proceed with the raw technology to get it up and running but I would like to have a bit more discussion around safety and protect though so we don't go down a blind alley.
Hope we can get more discussion traction on this issue, I'd love to see it happen!

Thanks @scottjenson for sharing the demo video. That UX was exactly what I had in mind. This would make things a lot more friction-less.
The info command could be straight-forward. We should support a notion of an info command and perhaps mandate this, for giving the user some information on what those actions are for. It could be as simple as
[
  {
    "type": "info",
    "icon": "icon_url",
    "description": "a html payload",
     // (or)
     "link": "deep_link_or_url"
  },
  {
    "type": "generic",
    "icon": "icon_url",
    "title": "The Title of the actionable Notification",
     "link": "deep_link_or_url"
  },
  {..}
]

The info action can be backed by a DialogFragment which essentially supports showing the  description or an external web page (backed by a WebView) denoted by its link property.
As far as protecting users, I think it should be okay for the actions to launch a flow if they need the user to be signed in, to perform an action. We could figure out the actions that need the user to be signed in by using an optional property on the action. Something like needsAuthentication would work.
If you have other ideas on how  we could go about supporting secured actions or actions that need the user to be signed in - I would love to hear them.

We'd like to work with the http://w3c.github.io/manifest/ team on this so we don't go in a direction that they won't support. Seems like we need to get them on board with this extension before we charge down this road. Would you be willing to discuss it there? It seems like putting it there will enable other uses beyond just the Physical Web so we need to make sure they are on board.

@scottjenson That sounds good. I can definitely work on getting things started with the W3C Manifest team. Do you recommend sending an email to the W3C email list or submitting an issue in the Github Repo?

@scottjenson I re-read your comment about protecting the user from non-idempotent actions like buy. I thought you meant something else. My apologies. You are right. It would be nice to be able to protect the user from apps that expose actions that are malicious.

I submitted an issue with the W3C Manifest project.

How soon do you think the physical web will be ready to use and demo from chrome mobile browser and or android operating system instead of native appliction @scottjenson? Is there a way for what you have built for the physical web to be  incorporated with a chrome beta test just to show proof of concept from the browser?

We get this question a lot (and for very understandable reasons) We very much want this to be about the entire community. When working on something that should be part of the open web, it's important to be open, deliberate, and just a bit slow as we don't want to rush this. I have frequently said that we'd be thrilled if another platform browser did this before Google. However, it's clear now that someone needs to seed the market to get things moving. We are working on bringing this to mobile phones but we can't make any public announcements just yet.

Based on the feedback at https://github.com/w3c/manifest/issues/347, I think it makes sense to support a well known endpoint and piggy back on the http://schema.org/Thing and http://schema.org/docs/actions.html specifications. Does that sound good to you @scottjenson ?

That sounds possible. There seem to be at least three separate issues here so I'd like to take them in turn. From your webmanifest thread, it looks like you won't be using that correct? So by 'well known endpoint' what were you thinking, JSON+LD?  Or were you thinking of something else? We liked JSON+LD as it allowed a wide range of metadata to be expressed by the web page.
As to the actions themselves, we need to make sure we handle the safety issue discussed above. To be honest, the more I think about it, the more I could be over reacting as every concern I have could equally be applied to any web page (i.e. an 'info' button could be a 'buy' action). I just wanted to pause and make sure we weren't creating an attack vector.
If that passes inspection, the final point would be how we'd actually act on these issues. This raises a large UX issue: would you expose these actions int he notification manager? Right now our UI is very sparse and simple on purpose. Our exploration exposed the actions ONLY on the watch as we felt it was the place you'd really want these to take place. It also helped that the watch UI had a very simple 'more' action that you don't have in the phone notification api. Curious if you've thought about this.

Yes, you are correct. It looks like the Web Manifest is not a good fit.
This is what I was thinking.

When we resolve scan a URL being advertised and fetch its content to discover site information, we could additionally check for a HTTP response header X-PHYSICAL-WEB-NOTIFICATIONS whose value would be the endpoint that advertises a list of actions supported.

This endpoint returns JSON+LD and describes both the thing and the list of supported actions as per the schema described at  http://schema.org/Thing and http://schema.org/docs/actions.html.

An example payload returned by the endpoint could look like:
{
  "thing": {
     "@context": "http://schema.org",
     "@id": "#hue",
     "@type": "IndividualProduct",
     "name": "Philips Hue",
     "description": "Philips hue combines brilliant LED light with intuitive technology.",
     "image": "http://www2.meethue.com/media/1076/bulb.jpg"
   },
  "actions": [
    {
      "@context": "http://schema.org",
      "@type": "ControlAction",
      "actionStatus": "PotentialActionStatus",
      "name": "Turn on Lights",
      "description": "Turns on all lights",
      "image": "<an image url>",
      "target": "https://.../lights/turnon"
    },
    { ... }
   ]
}

Thus we can discover a list of actions. As far as the User Interface goes I had something simple in mind. It could look like this. If you have any suggestions, please let me know.

When we first made that video, we were just exploring, seeing what was possible. Now that you and I have had this conversation and I look at your wireframe, I'm beginning to wonder if we're sliding down a slippery slope. Your sub page of actions is starting to feel like a simple web page. Two things come to mind:

The Physical Web is going to encourage very simple and lightweight web pages so just loading the page itself may not be that bad.

Given that we have things like ServiceWorker coming along (which would allow your favorite apps to be cached) the page could  would load nearly instantly and have the full expressive power of the web if needed.

Do you see how I got here? Is it really worth it to work so hard to show a subset of a web page?

Thanks for the feedback. Yes, I am starting to realize that re-creating UI (which is also provided by the web page) is a slippery slope - because it will be much simpler that what can be done by the web page.
That being said, I think there is at least one major advantage here which we ought to consider.

The most frequent/prominent action is one click away. This could become even better when actions are customized based on the user's preferences (which is likely, as that too is just another URL). If there was one such prominent action we could even go as far as including it in the notification itself (or smarter UI guys can perhaps figure out an even better interaction).

For me, it's less about the UI and more about the convenience of 1-click access. This could be I'm feeling lucky button for Physical Web. I think, this could still be an interesting experiment to see if its useful.
--
Based on the discussion we had, I have come to the same conclusion you did. We have to extremely careful when we attempt to resurface portions of the UI pertaining to the web-app.

re: "the most frequent/prominent action"
Once nice option could be to model the intent of this button to the FAB
(floating action button) in Material Design. Limiting it to a single option
would encourage developers to focus that interaction around the most
frequent or impactful action (if one exists). So long as it's clear that
the notification is dual action (i.e. tapping the notification has a
different impact than tapping the action button), I think this would be a
great way to enable users to deep-dive without turning the notification
into an unwieldy widget-like contraption.
To Scott's point about the Physical Web (PW) encouraging "very simple
pages", IMHO the PW has the potential to initiate a significant change in
mindset regarding how small and targeted web pages/sites can be, yet still
deliver value. It's a well documented fact that web pages just keep getting
bigger. Responsive design has only barely affected this (and TBH often made
it worse). Decoupling the delivery of data that a user needs from the
presumption of a (monolithic) web site as the sole delivery point would
parallel lots of what is happening in apps (e.g. smart notifications, card
based anticipatory services like Google NOW) and would IMO improve the
web's value proposition going forward.
Offering a sole action could be great to set the conversation on the right
track with the presumption of smaller pages and focussed interactions from
the very start.
Steph
On Fri, Apr 3, 2015 at 6:50 AM, Rahul Ravikumar<EMAIL_ADDRESS>wrote:

Thanks for the feedback. Yes, I am starting to realize that re-creating UI
(which is also provided by the web page) is a slippery slope - because it
will be much simpler that what can be done by the web page.
That being said, I think there is at least one major advantage here which
we ought to consider.

The most frequent/prominent action is one click away. This could
become even better when actions are customized based on the user's
preferences (which is likely, as that too is just another URL). If there
was one such prominent action we could even go as far as including
it in the notification itself (or smarter UI guys can perhaps figure out an
even better interaction).

For me, it's less about the UI and more about the convenience of 1-click
access. This could be I'm feeling lucky button for Physical Web. I
think, this could still be an interesting experiment to see if its useful.
Based on the discussion we had, I have come to the same conclusion you
did. We have to extremely careful when we attempt to resurface portions
of the UI pertaining to the web-app.
—
Reply to this email directly or view it on GitHub
https://github.com/google/physical-web/issues/307#issuecomment-89175179.

@scottjenson Any further thoughts ?

Sorry, I'm traveling in Singapore so a bit slow to reply right now. I agree that the lure of 'just one click' is strong (It's why we tried it in the first place so we too are intrigued by this) If I can back up, this same issue has applied to the 'description' section as well. Someone suggested just the description could offer the latest bus time info so you'd have 'zero click' action just by looking at the notifications.
What I like about the zero click model is that it only requires that any caching service is careful to not over cache. There was a suggestion that we use the HTTP header, which can specify cache info, as a simple hint at what to do here.
What I'm implying is that there are numerous ways of making this as as fast as possible. The 'one click' solution is tricky, now that we've looked at it for the following (already discussed) reasons:

TO Offer 1 action begs 2, then 3 so it feels like a slippery slope. Unless we're prepared to be really strict and say strongly 'only one' this seems like a hard thing to control. Given that responsive pages can load VERY quicky, it's not clear it's really that much of a win.

I'm just so nervous about attack vectors. I don't think we've really discussed this in detail yet. There is tremendous power we have in leveraging all interaction within the browser as it is SO hardened and has so many ways of protecting the user. If we start executing actions outside the browser, we need to take on that responsibility. I'm not against this, I just take the responsibililty very seriously.

 I just feel we need to be careful. I'm sure we can have a healthy debate on point #1 but point #2 seems very hard to resolve. We're trying to build on top of the web, not replace it. Thoughts?

We're trying to build on top of the web, not replace it. Thoughts?

I agree that all interaction should be within the browser, but for an additional reason: cross-platform functionality. This might not be a problem, but I can see the importance of keeping it simple and similar on all mobile platforms for familiarity. Notification actions work differently on different platforms and might not even exist at all. Similar enough, sure, but it might lead to feature fragmentation of the PW apps and future implementations in operating systems.
If a user is not interested in an action at all it becomes noise. As @scottjenson said, pages can load very quickly, so I'd say we better make the website/web app handle one click actions from there.

@dermike Fragmentation is not an issue. Most modern operating systems offer actionable notifications, and the client can always gracefully fallback to its basic behavior based on feature detection.
However, I must admit that I have not fully considered the potentially new attack surface area. I am beginning to think if we should build on top of the Push Notifications API still gives us the feature we are going after - while being true to the web. The only catch here being, that the user will have to install the web-app which might actually a good thing (as it makes this feature opt-in).
@scottjenson - Does that sound like a good idea ?

Most modern operating systems offer actionable notifications, and the client can always gracefully fallback to its basic behavior based what it can support (similar to feature detection).

@tikurahul This was kind of what I meant... is it really desirable for PW clients to need to have fallbacks and such?
Could actions then be used to influence the ranking or sorting to stand out from the rest?

RE: Push Notifications API - There is a already a demo of this:
https://github.com/sandropaganotti/no-queue
It uses Service Worker + Push notifications. We are VERY excited by this demo as it shows the 'layer approach that the web can do. This demo requires no changes to the Physical Web side of things, it's all done via Service Worker. Another advantage of this is that it keeps the Physical Web notifications quite and on user demand but when thy opt in using a SW, they can then get notified.
Does this meet your needs or would you like to try something different?

Yes this is exactly what I was talking about. This also solves the opt-in problem. Thanks for the link.


Typos in o365 custom learning

Category

[ ] Question
[ x] Typo
[ ] Bug
[ ] Additional article idea

There is a typo in the course selection area:  It reads "Choose the courses that suites you best"  It should read:  "Choose the courses that suit you best."

Thanks for reporting, we'll address this in a future release.


Filter paper by environments/agents/etc

Currently we are doing substring search, so in_context_learning shows up when searching for text

Add a subsection label for each paper?

Added!


How to include zxing-cpp to project without a shared library

Hello,
I'm facing the following problem. I want to build xzing-cpp from source to integrate it with one of my projects - I don't want to install it to (/usr/...).
This is what my CMakeList looks like:
cmake_minimum_required(VERSION 3.0)
project(sample)
set(CMAKE_CXX_STANDARD 20)

set(ZXing_DIR "${CMAKE_CURRENT_SOURCE_DIR}/dependencies/zxing/build")
find_package(ZXing REQUIRED)

add_executable(sample main.cpp ZXingOpenCV.h)

target_link_libraries(sample ZXing)

But when I do so I get the following error:
CMake Error at dependencies/zxing/build/ZXingConfig.cmake:26 (include):
include could not find requested file:
/home/code/crepo/sample/dependencies/zxing/build/ZXingTargets.cmake

Call Stack (most recent call first):
  CMakeLists.txt:11 (find_package)

But why there is no ZXingTargets.cmake file?
I downloaded the source got from the offical repo and did cmake build & make.
What is wrong there, anyone can help?
Thanks

I'm not sure to understand what exactly you try to do and where did you checkout zxing-cpp repo relative to your project, but if 'dependencies\zxing' is the location of zxing-cpp repo, to use it directly in your project, try to include the folder instead:
cmake_minimum_required(VERSION 3.0)
project(sample)
set(CMAKE_CXX_STANDARD 20)

add_subdirectory (${CMAKE_CURRENT_SOURCE_DIR}/dependencies/zxing/core ${CMAKE_BINARY_DIR}/ZXingCore)

add_executable(sample main.cpp)

target_link_libraries(sample ZXing::ZXing)

Question: could you solve your problem? If so, please close the github issue.


NOT work on iPad IOS 13.5.1

Release Veresion 5.6.8 NOT WORK on IOS 13.5.1 (iPad), but works on ios 12.4.4.

same problem here, are there any news?


clientv3: add client side metrics

We do not have client side metrics reporting now. It is important for users that want to understand the load they sent to etcd. We use gRPC for the rpc layer and use Prom as the metrics reporting system. Fortunately, people already have gRPC + prmo integration: https://github.com/grpc-ecosystem/go-grpc-prometheus. We want to use it in our clientv3 lib.
/cc @sinsharat Can you work on this? Thanks!

Sure will start working on it.

@xiang90 From what i have understood, adding only the two lines just before grpc dial option in clientv3/client.go dial func will support the metrics:
// add metrics options
	opts = append(opts, grpc.WithUnaryInterceptor(prometheus.UnaryClientInterceptor))
	opts = append(opts, grpc.WithStreamInterceptor(prometheus.StreamClientInterceptor))

	conn, err := grpc.Dial(host, opts...)
	if err != nil {
		return nil, err
	}

Apart from this we will need to update the glide.yaml and lock.yaml file with github.com/grpc-ecosystem/go-grpc-prometheus entries,
Also will need to add the package github.com/grpc-ecosystem/go-grpc-prometheus under cmd/vendor folder.
Was able to build it with these steps.
Will test it by writing some code and update you on this.
Thanks!

Right.

@sinsharat We also need to write docs for it and probably manually test it to ensure it works.

@xiang90 sure will write docs for it once i am done testing on it.
I have one doubt, how to test it manually, since via code for testing it like a person writing clientv3 will need to call the api grpc_prometheus.EnableClientHandlingTimeHistogram() in order to enable metrics.

@sinsharat Probably you need to write a small driver code for it. Using the client to issue some rpc calls, see the metrics actually changed.

@xiang90 can you elaborate more on the driver part, i didn't quite understand what exactly you meant.
Also i was thinking of writing a test case for it since the clientv3 supports creating a cluster so while testing we could have called the grpc_prometheus.EnableClientHandlingTimeHistogram(), checked the old metrics value, do a certain set of operation on the client and checked the new value on that to ensure the metrics functionality works.

How about something like https://github.com/coreos/etcd/blob/master/integration/cluster.go#L755? And just do some basic parsing?

@gyuho thanks for the reference. Sure will look into it and check how can i do something similar for this.

@xiang90 I was able to test and verify whatever changes i have done is working fine. For this i started etcd manually and using the main code i had written was able to verify the metrics. Also for this i have written an example_metrics_test.go on the same basis under clientv3 package. The issue i am facing now is i am not able to test the clientv3 package since the test case TestDialTimeout is failing :-(. Giving the error as :
	leak.go:96: Test appears to have leaked a Transport:

@gyuho : Need you help in making it run successfully.
Thank you!

@xiang90 What all things do you expect in documentation? Will document it accordingly.
Thank you!

@xiang90 Will start with document section now. Wanted to know what all things you expect in the documentation.
Thank you!

@sinsharat Probably just add one sentence that we support client side metrics, link to https://github.com/grpc-ecosystem/go-grpc-prometheus for more details. Maybe also provide an example link to the example program you wrote. I would like to keep it as simple as possible for now.

@xiang90 I totally agree with you. I too was feeling there is not much to document. Will do the changes as per your suggestion.
Thank you!

@xiang90 i think this can be closed now. Let me know if there's anything which i can look into now.

Closing. Thanks.


gcp.compute.URLMap: tests[*].headers field is missing

A URLMap test can specify custom headers, but the field is currently missing from the provider.

Hi @segevfiner. gcp.compute.URLMap.tests[*] does not have a headers field.
This provider is bridged from a google-maintained TF provider: https://github.com/hashicorp/terraform-provider-google-beta. If you want this feature, I recommend opening an issue upstream: https://github.com/hashicorp/terraform-provider-google/issues/new/choose. As soon as they add this feature, we will have it in pulumi-gcp.


Use io.Writer instead of []byte in Render() method

Discussing with the great developer @valyala in thread https://github.com/valyala/quicktemplate/issues/58 about the amazing Authboss he gave us a suggestion to optimize a bit: https://github.com/valyala/quicktemplate/issues/58#issuecomment-517854569

As for the performance ... superfluous memory allocation when returning the byte slice from bytes.Buffer. The memory allocation could be avoided if Render() could accept io.Writer to write template output to.`

Can we just use io.Writer instead of []byte in Render() method?

Although he's correct, the main reason for this to exist is to enable a JSON renderer which doesn't accept an io.Writer anywhere. I'm really not opposed to the change, but it would have to be a RenderWriter interface we upgrade to from a Renderer otherwise it'd break backwards compatability. I'd accept a PR for this, will not implement it myself.


HIP 29: M-of-N Multisig

Rendered: https://github.com/helium/HIP/blob/sk/multisig/0029-multisignature-keys.md

RFC

Draft looks good to me. Will merge for discussion. This will be HIP 29

This HIP draft has been accepted and merged for discussion. Please direct comments & feedback to the tracking issue: https://github.com/helium/HIP/issues/157

I think when you want to make M-of-N multisig , we should build some functions to get a special private key from other basic private keys .so is the code of Helium have some functions to build a special private key from other basic private keys?
if yes: can you show me the resource code of it?
if not: I can build some functions like this, but here I need to know all about the standard building of helium's private key.


BackgroundColor and BackgroundTexture

Hi,
I just update the three-mesh-ui in my project, and the background texture doesn't change color then i set the background color attribute. Insted it change the over part of the background.
this.background.set({
   backgroundColor: new THREE.Color('#FF0000'),
   backgroundTexture:  this.textureBack,
   opacity: 1,
});

this.object.set({
    backgroundColor: new THREE.Color('#00FF00'),
    backgroundTexture:  this.texture,
    opacity: 1,
})

Hi,
Yes, that's because the background shader picks either your defined background color or the texture color depending on the texture alpha on the fragment :
https://github.com/felixmariotto/three-mesh-ui/blob/25a93326cc60f1374c2b00507f31d9b7c82b7275/src/components/core/MaterialManager.js#L263-L267
It's a shortcoming, I've been wanting to blend the passed texture with the passed backgroundColor and backgroundOpacity, but there is a design issue that kept me from doing so :
The default backgroundColor is grey, which is good for most cases when there is no texture. But when there is a texture, the color should be white by default, or there will be unintended grey blending, that the user might not understand...
The obvious workaround would be to update this generic getter :
https://github.com/felixmariotto/three-mesh-ui/blob/25a93326cc60f1374c2b00507f31d9b7c82b7275/src/components/core/MeshUIComponent.js#L165-L167
into something more complicated, which, when looking for the default backgroundColor, first check if a backgroundTexture exists, and if so returns white. IMO this is clumsy, but I can't think of anything else.
I'm open for suggestion for anything better, and anyway I will add this color blending feature.
I can't tomorrow, but I can the day after.

I've actually had the time to do it today.
The feature was added with v4.3.0.
See live example here.
As your request seems addressed I'm closing this issue, but feel free to reach out.


Ipython history: keep it around for the django shell

Every time you run this command to use the django shell, the history is gone:
docker-compose -f local.yml run --rm django python manage.py shell_plus

Is there a way to keep the ipython history around?
I tried the following:
docker-compose -f local.yml run --rm -v /d/my_project/.ipython/:/root/.ipython django python manage.py shell_plus

but I get a warning from Ipython:
The history saving thread hit an unexpected error (OperationalError('unable to open database file')).History will not be written to the database.

@YAmikep didn't quite look into this one, but I guess you gotta play around with https://github.com/django-extensions/django-extensions/blob/master/django_extensions/management/commands/shell_plus.py#L77.

Related: https://github.com/pydanny/cookiecutter-django/issues/1589


Regarding generation of MIG views

Hi ,
I am trying to generate a MIG network after optimization in readable format ( verilog , other texts etc)
What is the correct command to dump that after reading blif/aig format ?
For example for cout = xy + yz + zx, MIG network could be in format like below :
Y1 = MAJORITY (z , x_bar , y);
Y2 = MAJORITY (y_bar , x_bar , z_bar)
COUT = MAJORITY(x , Y1 , Y2);
Thanks !

There are several formats you can write out. For readable format, write_verilog is available. If you want to visualize the graph, write_dot will output a graphviz dot file.

Thanks Ashton. Will try.

Closing for now


TODO Feature: add router module

Feature
Add router module instead of concatenating the controller path
Tasks

[x] Implementing the feature
[x] Completion of the task

Done


Component:  Upgrade to 10.11.0 of Carbon

This epic includes the issues needed to complete the Carbon upgrade.
The background for this work is included in the closed issue (#1328).  Here is a copy of the last comment from Kenny dated March 6, 2020.

Confirmed that this is not currently affecting us. We are still on<EMAIL_ADDRESS>But we will need to update our Masthead styles eventually, as updating to their latest package will completely break the masthead.
Suggest closing this and creating a new story to audit all components with carbon-components as a dependency and how they will be affected if/when we update to the latest package

.

Linked issues closed.  Closing


object_naming: configuration, make every object type optional

for rule object_naming, its annoying having to specify every object type the rule can check, if only using a few of them,
make object type settings options, if not specified in config file, fallback to default
    "object_naming": {
      "clas": "^ZC(L|X)\\_ASDF",
      "intf": "^ZIF\\_ASDF",
      "prog": "^Z",
      "fugr": "^Z",
      "tabl": "^Z",
      "ttyp": "^Z",
      "dtel": "^Z",
      "doma": "^Z",
      "msag": "^Z",
      "tran": "^Z",
      "enqu": "^EZ",
      "auth": "^Z",
      "pinf": "^Z",
      "idoc": "^Z",
      "xslt": "^Z",
      "ssfo": "^Z",
      "ssst": "^Z",
      "shlp": "^Z"
    },

also specify that its "regex patterns" instead of "patterns",
https://github.com/abaplint/abaplint/blob/main/packages/core/src/rules/object_naming.ts#L10


Add Saru Planet Pack from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of tygoo7, to add Saru Planet Pack to CKAN.
Please direct questions about this pull request to tygoo7.

Part of KSP-CKAN/CKAN-meta/issues/588


New API to configure TLS cipher suites for kube-apiserver, etcd and kubelet

Which issue(s) this PR fixes:
Fixes #3079
What type of PR is this?
/kind feature
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

New API to configure TLS cipher suites for kube-apiserver, etcd and kubelet

Documentation:

NONE

/cc @xmudrii

@kron4eg API looks good, just two minor nits


Scripting (painless/mustache) request processor

As a user of search pipelines, I want to be able to insert a painless or mustache script to manipulate search requests.

manipulate search requests.

@macohen @msfroh Can we have some specific use cases here? In the injest pipeline, for example, script is used to filter/rewrite documents for ingestion.

In this case, I would like the script to manipulate the search request based on logic implemented in the painless script.
The main input to the painless script would be the search request itself, which was probably programmatically generated by the search application.
For example, maybe my pipeline would say "If the search query matches on the date field, then set the size property to min(size, 50)" (as a contrived example).

documentation task to come with fields that can be read/written

documentation task to come with fields that can be read/written

Created https://github.com/opensearch-project/documentation-website/issues/4155

Next steps for script processor

[ ] Support non-primitive types in request body
[ ] Support query context modification


Completing TLV implementation

Codecov Report

Merging #8 (9f2387e) into master (a4f1dad) will decrease coverage by 0.2%.
The diff coverage is 0.0%.

@@           Coverage Diff            @@
##           master      #8     +/-   ##
========================================
- Coverage    63.5%   63.3%   -0.2%
========================================
  Files          24      24
  Lines        3408    3417      +9
========================================
  Hits         2163    2163
- Misses       1245    1254      +9

Impacted Files
Coverage Δ

src/presentation/tlv.rs
0.0% <0.0%> (ø)

Continue to review full report at Codecov.

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


WIP: Styled About page

Fixed the styling and rebased.

On my end the web styling is all squished now, I'm going to try to get it back where it was.


Suggestion: symbols & bidirectional encoding

First off, this is a nice idea and I'm interested to see where it goes :)
We have been looking at whether we could support this standard with "effect/Schema", but there are some lacking features.

Polluting the interface with string keys isn't viable, as we then have to make sure users can't use those names when creating class based schemas
No support for bidirectional schemas, which is a foundational feature of "effect/Schema"

Here is a draft proposal:
export const v1 = Symbol.for("standard-schema/v1")

export const v1Encodable = Symbol.for("standard-schema/v1/Encodable")

/**
 * The Standard Schema v1 interface.
 */
export interface StandardSchema<
  in out Output,
  in out Input = Output,
  out Error = unknown, // allow a library to define the error shape
> {
  readonly [v1]: {
    /**
     * The vendor name of the schema library.
     */
    readonly vendor: string

    /**
     * Validates unknown input values.
     */
    readonly decode: (input: Input) => Result<Output, Error>
  }
}

/**
 * The Standard Schema v1 interface.
 */
export interface Encodable<
  in out Output,
  in out Input = Output,
  out Error = unknown,
> extends StandardSchema<Output, Input, Error> {
  readonly [v1Encodable]: {
    /**
     * Encodes the output value to the input value.
     */
    readonly encode: (input: Output) => Result<Input, Error>
  }
}

export type Result<A, E = unknown> = Result.Ok<A> | Result.Error<E>

export declare namespace Result {
  export interface Ok<A> {
    readonly ok: true
    readonly value: A
  }

  export interface Error<E = unknown> {
    readonly ok: false
    readonly error: E
  }
}

The alternative for us is to export an adapter api, instead of implementing the interface directly. But in either case, the "Encodable" interface would be a welcome addition.

I strongly support this approach; in general, having more tightly typed interactions is invaluable.
A common example would be react-hook-form, which supports the current idea of Schema<A>. The issue is that it accounts only for the output, which means that all the types for the input are jumbled, ruining the developer experience. If a lib does not know the input, it can either use A and A or just declare unknown or never (or even some unique type from the spec)

Also a potential design that supports async too:
export const v1 = Symbol.for("standard-schema/v1")
export const v1Async = Symbol.for("standard-schema/v1/Async")
export const v1Encodable = Symbol.for("standard-schema/v1/Encodable")
export const v1EncodableAsync = Symbol.for("standard-schema/v1/EncodableAsync")

export interface StandardSchema<
  in out Output,
  in out Input = Output,
  out Error = unknown // allow a library to define the error shape
> {
  readonly [v1]: {
    readonly vendor: string
    readonly decode: (input: Input) => Result<Output, Error>
  }
}

export interface StandardSchemaAsync<
  in out Output,
  in out Input = Output,
  out Error = unknown
> extends StandardSchema<Output, Input, Error> {
  readonly [v1Async]: {
    readonly decodeAsync: (input: Input) => Promise<Result<Output, Error>>
  }
}

export interface Encodable<
  in out Output,
  in out Input = Output,
  out Error = unknown
> extends StandardSchema<Output, Input, Error> {
  readonly [v1Encodable]: {
    readonly encode: (input: Output) => Result<Input, Error>
  }
}

export interface EncodableAsync<
  in out Output,
  in out Input = Output,
  out Error = unknown
> extends StandardSchemaAsync<Output, Input, Error>, Encodable<Output, Input, Error> {
  readonly [v1EncodableAsync]: {
    readonly encodeAsync: (input: Output) => Promise<Result<Input, Error>>
  }
}

export type Result<A, E = unknown> = Result.Ok<A> | Result.Error<E>

export declare namespace Result {
  export interface Ok<A> {
    readonly ok: true
    readonly value: A
  }

  export interface Error<E = unknown> {
    readonly ok: false
    readonly error: E
  }
}

Is there any update on this? I know you have exchanged ideas with Colin. From my perspective, according to our readme, encode/decode is currently outside the scope of this specification. But that does not mean that we should not consider it in the long term. The use case for decode/encode is a bit different. Also, a standard spec only makes sense if there are multiple schema libraries containing this functionality. One idea is not to add it to the interface of the current Standard Schema spec, but to provide it as an additional interface.

What kind of update? I think that the spec provided by the previous comment is quite extensive and complete as far as suggestions go 🤔
What would be the next steps if a leveled/tiered spec is the direction?