new GRU QAQC report

Geographic research would like to add a new QAQC report to the portfolio of existing GR QAQC reports.
This new report would compare Historic Footprint BIN vs PAD BIN. This is essentially a version of the existing BIN vs PAD BIN, but using historical data.
Geographic Research would like to be able to run this new report after 24B is released on May 5 to clean up the data ahead of the 24C release.
This is the best place for DE to get historical footprint data

This will need stuff to happen in a couple places
Running of GRU QAQC happens in another repo : https://github.com/NYCPlanning/db-gru-qaqc. This could be moved at this point, because I've removed most of the automation around issues and github actions within the repo in favor of the page on the streamlit app. But that doesn't need to happen now.
In that repo, we'll need

[ ] a new bash script

properly named
generates outputs and exports/uploads just like the other datasets

[ ] presumably, a new python script
[ ] ensure that the main gha can call the target script

Then, in the qa app, we'll need this added as an option for GRU. I think this is largely abstracted, and there's just a csv/dataframe that will need a row added for this test

This test should be called historic-footprints-vs-pad


Fix typo

I initially noticed a typo here:

This is so the appropiate modules can be found when running on Python 2.

But it was already fixed when I forked the repo. So, it seems like the docs on pythonhosted.org are not up to date?
Anyways, I found one more typo (this time in both index.rst and pythonhosted.org):

Python 3 renamed the attributes of several intepreter data structures.

Thanks. I recommend using six.rtfd.org.

@benjaminp ,
Ah ok, I hadn't come across that other site. When I google "six python", the other site was the second link so I just went there.

As you are probably aware, even after your merge of this typo fix, the typo is still there on https://six.readthedocs.io/
Anyways, thanks for your time! I use six quite a bit.


switch_on_off like light_on_off  (CON-619)

is it possible to create an object of type switch that controls two gpio?
that has the same behavior as the light_switch example, but display as a generic switch?

Sure, use strip the light example down to just OnOff (get rid of color and level control). Then make two OnOff endpoints, one for each GPIO. The switch side does not need to change. Just bind the switch to one of the two endpoints.

@jonsmirl
Hi, maybe I explained it wrong.
I would like to create a switch similar to the homekit one
which does not read the inputs but switches an output on and off

That is the light_switch example in the example folder.

Does this mean your hardware does not have any input buttons?
and you want to operate the switch only using App or voice(alexa)?

If you want to do this in an app, you can look at the Google sample app
https://github.com/google-home/sample-app-for-matter-android
Here is where it sends the on/off commands
https://github.com/google-home/sample-app-for-matter-
android/blob/main/app/src/main/java/com/google/homesampleapp/chip/ClustersHelper.kt#L481

@stefano055415 any updates on this?

Closing now. Please re-open in case of anything


2315: change school responsible body

Context
Support third line users need to be able to manually move a school to a new Responsability Body.
Changes proposed in this pull request
Add a row in the school show details view displaying the school current responsability body and a cta to change it.
Guidance to review
User story: GIAS - Move school to a new RB (RFQ-11)

 GIAS - Move school to a new RB (RFQ-11)


Oh, yeah....


Climbing Stairs Problem via DP

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

You are climbing a staircase. It takes n steps to reach the top.
Each time you can either climb 1 or 2 steps.
In how many distinct ways can you climb to the top?

Describe the solution you'd like
Dynamic Programming Approach to solve the problem.
Do you want to work on it
C++

/assign

I have added the solution of the problem in C++ in this pull request #1378 please merge.

Hello!
I am a GSSoC'21 participant.
I would like to contribute the code for this issue in C++/CPP.
Kindly assign it to me.

I'm a GSSOC participant, I can write the code for the same in python, please assign it to me

Hi,
I am a GSSOC'21 participant. I would like to solve this issue in Java. Please assign it to me.


Update formula by clicking on it + inline

A formula (inline and block) can be updated clicking on it. It will open a Dialog with the formula input as text.


fix: add bypass for ams for kas-installer

Motivation
Do not call AMS when using upstream version of the platform/Self installed.
Verification
Non interactive:
rhoas kafka create --dry-run --bypass-checks --name=test -v
Dry run successful, arguments are valid
Interactive mode:
[wtrocki@graphapi app-services-cli (ski-ams-check ✗)]$ rhoas kafka create --dry-run --bypass-checks
❌ Interactive mode is not supported when using --skip-checks flag. Run the command in verbose mode using the -v flag to see more information

Verification steps work fine with prod. Can I get the steps to test it against the kas-installer?

I have verified it yesterday but this instance is now down/unavailable.

thank you @wtrocki - that works, but whilst I can create size x1 successfully, if I chose size x2, the system creates an x1.  I'll raise a separate issue.


Publish the binary on Homebrew

So, "compile the binary and save it somewhere," while totally making sense for a little one-off throwaway script, ain't great for reproducible / stable system configuration that lasts past the current machine's lifetime. :P
Any chance you're willing to see this shipped to Homebrew or similar, as simple as it is?

Hey @bouk - any feedback on this?
There's a CLI dark-mode setting command in Homebrew:
https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/dark-mode.rb
Figured it may be worth a look to see if you're interested in having this very awesome notify version added to it's own homebrew recipe?


N3 files containing rules can't be stored via mashlib

On NSS (inrupt.net) I'm trying to store the cats.n3 file as text/n3
prefix : <https://example.org/cats#>.

:Mika a :Cat .
:Akita a :Cat .
:Luna a :Cat .

{ ?X a :Cat .} => { [ :is :CatFriendly ] .  [ a :Cat ] . }

This presents me with the following error message:

Uploading with another editor doesn't present this problem.

Thanks for reporting.
You seem to miss a dot at the end :

And now you got this issue already referenced at https://github.com/linkeddata/rdflib.js/issues/567
If you have any idea how to solve the issue it will be very nice.


Event dispatching broken in master

Running pyglets examples/windows_event.py does not output keyboard or mouse events to the console.
The commit that broke was
commit 385f1ae2452ac733a0e4b5852b6a98475cea5f52 (HEAD)
Merge: 22fd9889 099e3852
Author: Benjamin Moran
Date:   Tue Feb 19 12:32:22 2019 +0900
EventDispatcher and Clock only hold weakref to methods --> not working

The previous commit does not show that defect
commit 22fd98897778fb0f9cac8a68adf827bcc8496761 (HEAD)
Author: Benjamin Moran
Date:   Mon Feb 18 17:15:12 2019 +0900
Add platform reqirement flags for resource loading integration test. --> working

win7 64bits, python 3.7.2
Discovered while testing cocos, issue https://github.com/los-cocos/cocos/issues/328
Is this an intended change in events API that missed to update the example script or is the events subsystem broken ?

edited the git log entries.

Hi Claudio, Thanks for opening the ticket.
The example was broken. As the change says, the EventHandler now uses weak references.
If you are seeing issues in Cocos, you can solve it by keeping a reference to all event handlers.
Instead of this:
window.push_handlers(SomeEventHandlerClass())

do this:
some_event_handler_class = SomeEventHandlerClass()
window.push_handlers(some_event_handler_class)

Basically, you need to make sure that you keep some reference to all handlers that are pushed. Does that make sense?

Thanks for your promt response Ben.
It makes sense.
Tonight I will look how it applies to cocos
Thanks

Yes, it was a case of .push_handlers(MyClass()), solved.
Thanks!

Great!  I think this is a good opportunity to update the docs so that we mention this behavior.

It would be useful to have  section with short compatibility notes.
We have one for cocos, and this time includes our pyglet 1.4 compat notes discovered while fixing cocos to work with pyglet 1.4
link to the rst document that will be included in the next release (the Sphinx render is still not online)
https://raw.githubusercontent.com/los-cocos/cocos/cocos2019/docgen/compatibility_notes.txt

I added a note to the docstrings, and programming guide explaining usage of weak references.


Investigate initial editorial community page structure

The about page content for each editorial community should follow the same structure, to enable users to easily compare like-for-like.
We should come up with an initial structure based on information available from each of the current communities, and iterate on this based on feedback.

An early suggestion was to include a short bio and then info on review policy (or at least link to more information on review policy). This was based on the assumption that not all ECs will perform reviews in the same way, and therefore users reading reviews might want to find out more about what was done. Or perhaps explore why the review isn't structured as they might expect etc.
Might be a good starting point to test?


Parse more keywords and language constructs

For use in semgrep, it would be nice if tree-sitter-php parsed more keywords and language constructs. Specifically:

$this
isset()
empty()
eval()
exit() / die()
assert()
__halt_compiler()
maybe __CLASS__, __DIR__, __FILE__, __FUNCTION__, __LINE__, __METHOD__, __NAMESPACE__, __TRAIT__?

$this is of course not a real variable, but refers to the current object. The other ones are language constructs, not real functions.
These do not currently trigger a parse error, but are parsed as variable or function call, when that is not technically correct.

The downside of including these in the grammar is that they'll increase the size of the parser, and with the current grammar, these can already be identified at a different layer of abstraction.
If we do add them to these builtins to the grammar, I think they should be done so as one single new token, for efficiency:
builtin_function_name: $ => token(choice(
  'die',
  'exit',
  'isset',
  'empty',
  // ...
)),

function_call_expression: $ => seq(
  field('function', choice(
    $.builtin_function_name,
    $.qualified_name,
    // ...
  )),
  field('arguments', $.arguments),
)

That will reduce the impact on the parser's code size.
On a related note, I think unset is currently treated as its own kind of statement, which is unnecessarily specific (and costly, in terms of code size). It should really be handled the same way as these other built-in functions: either parsed as a simple name, or if we choose to add it, as a builtin_function_name.

After giving this some more thought, I fear my initial enthusiasm was a bit premeditated.
Currently, we have quite a few paths in the parser where we take a relaxed approach to correctness (to keep parser since small) and primarily concern ourselves with syntactic correctness while (mostly?) leaving semantic correctness to another layer of abstraction.
To me, this feels like a cross road where if we implement this, we should also implement other semantic checking (e.g. not allowing functions with names equal to the language constructs) - and I don't think that's in scope of the grammar. However, I'm still learning, so please correct me if I'm wrong 🙂
As far as I can see, the suggestion in the earlier comment would still require Yoann's suggestion of having a fix_funcall or fix_id in Parse_php_tree_sitter.ml. Thus, this change would probably at best only have a small positive impact on Semgrep since further processing will be required anyway. Is that a fair assessment/understanding? If so, I guess the easiest fix would be to remove the __bultin_ prefix from pfff since PHP code trying to declare a language construct as a function will fail compilation - at least in my tests.
I'm inclined to support removing unset as it's own statement and keep the parser as simple as possible, leaving semantics to users of the grammar. At least I'll focus on completing the support for current PHP syntax before thinking more about this myself.


feat: Adding .devfile.yaml

PRs allows using workspaces.openshift.com as a development environment for instructlab website.
Try it out on Developer Sandbox by clicking  on the badge

@mairin @russellb @joesepi please, review


Flickering when zooming out

Hi,
Thanks for that great tool !
How to reproduce issue

Run that code :

void main() async {
  runApp(
    MaterialApp(
      home: ExtendedImage.network(
        'https://upload.wikimedia.org/wikipedia/commons/thumb/3/35/2017-03_Bologna_Mattes_Pana_%2881%29.JPG/1920px-2017-03_Bologna_Mattes_Pana_%2881%29.JPG',
        fit: BoxFit.contain,
        mode: ExtendedImageMode.editor,
        initEditorConfigHandler: (state) {
          return EditorConfig(
              maxScale: 4.0,
              cropRectPadding: EdgeInsets.all(20.0),
              hitTestSize: 20.0,
              cropAspectRatio: 1.5);
        },
      ),
    ),
  );
}

Pinch out to zoom beyond minimum zoom

Observation : The image flickers a bit. It zooms out beyond limit, then is quickly reset to minimum zoom.

i can't zoom beyond minimum zoom at my side

Here is how it behaves when pinching out beyond limit.

it didn't look as we do, ScaleUpdateDetails also provide offset and  scale(>1.0) when we zoom out at that monment.

I/flutter (17909): 1.0
I/flutter (17909): 0.9988947961111486
I/flutter (17909): 0.9988947961111486
I/flutter (17909): 0.9977900020482547
I/flutter (17909): 0.9977900020482547
I/flutter (17909): 0.9958129374301814
I/flutter (17909): 0.9958129374301814
I/flutter (17909): 0.9929633178372261
I/flutter (17909): 0.9929633178372261
I/flutter (17909): 1.0041964297358636
I/flutter (17909): 1.0041964297358636
I/flutter (17909): 1.0001868739590598
I/flutter (17909): 0.9993015553995158
I/flutter (17909): 0.9952925009699909
I/flutter (17909): 0.9944070413042475

please update to 1.1.2

Wow thanks for that quick fix ! The flickering issue is resolved :)
I'm having another small issue on zoom out : #236


lte: restore lens control plane

This PR is the dual of urbit/urbit#1277. %rver implements the new %request-local task (thanks @ixv!), and there's an incredibly basic, one-request-at-a-time lens app. Just enough to get the CI and pill staging back to a working state (on urbit/urbit).

It seems a lot more robust to use the standard eyre app authentication
mechanism, perhaps with a lens token written out into .urb for shell
access. I think a lot of the lens port separation was there to quarantine
code shoehorning "%poke with empty ack, console %peer with several spurious
responses" into a single JSON rpc call-response, which looks like it's now
directly supported / entirely in userspace?
On Tuesday, 14 May 2019, Joe Bryan<EMAIL_ADDRESS>wrote:

Merged #1170 https://github.com/urbit/arvo/pull/1170 into
lighter-than-eyre.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/1170?email_source=notifications&email_token=AAOFPBX5DZKQSWOLCDTBYTDPVMZP5A5CNFSM4HM4WTLKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOROI2F5Y#event-2341577463,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOFPBSS6JM5PSUWKPYAM3LPVMZP5ANCNFSM4HM4WTLA
.

Full stateful http-request handling is now in userspace (with lighter-than-eyre), Lens/herb/urb.py should be changed to work that way, and to support the standard cookie-based authentication. But I still think it's worth keeping around the lens server as a automatically-authorized local-only channel -- it's handy for scripting, CI, etc.


get method using jquery cookie

the get method implementation in (!support) if branch is using jquery cookie when perhaps it should be using angular cookieStore.
recommend change
return privateMethods.parseValue($.cookie(key));
to
return privateMethods.parseValue($cookieStore.get(key));

@agrublev I believe this is corrected already? If so please close the issue. I don't see any jQuery being used any longer.

@agrublev @hppycoder if you need a cookie fallback then just pick ngKookies - https://github.com/voronianski/ngKookies

@hppycoder and where did you see jquery cookie in get method? - https://github.com/agrublev/angularLocalStorage/blob/master/src/angularLocalStorage.js#L91


[RFT] Rewrite LuCI runtime in ucode

This PR adds a mostly feature complete re-implementation of the LuCI server side runtime in ucode instead of Lua. It supports running the complete standard LuCI environment (as selected by the luci meta package) without having to install lua, liblua or any of the Lua specific binding libraries onto the system.
Backwards compatibility with existing Lua based LuCI applications can be achieved by installing the luci-lua-runtime package.
Requires OpenWrt commits https://github.com/openwrt/openwrt/commit/639754e36d849553e288f8e34f51f793761c07db and https://github.com/openwrt/openwrt/commit/94129cbefb6027cdfe2b7801a6e27a36d4ec58b8

We need to cleanup the lua_prefix:
# logread  -e uhttp
Wed Oct  5 08:50:31 2022 daemon.err uhttpd[2545]: Error initializing /usr/lib/lua/luci/sgi/uhttpd.lua Lua handler: /usr/lib/lua/luci/http.lua:143: attempt to index local 'L' (a nil value)
Wed Oct  5 08:50:37 2022 daemon.err uhttpd[3777]: Error initializing /usr/lib/lua/luci/sgi/uhttpd.lua Lua handler: /usr/lib/lua/luci/http.lua:143: attempt to index local 'L' (a nil value)
Wed Oct  5 08:50:42 2022 daemon.err uhttpd[3844]: Error initializing /usr/lib/lua/luci/sgi/uhttpd.lua Lua handler: /usr/lib/lua/luci/http.lua:143: attempt to index local 'L' (a nil value)
Wed Oct  5 08:50:48 2022 daemon.err uhttpd[3911]: Error initializing /usr/lib/lua/luci/sgi/uhttpd.lua Lua handler: /usr/lib/lua/luci/http.lua:143: attempt to index local 'L' (a nil value)
Wed Oct  5 08:50:53 2022 daemon.err uhttpd[3978]: Error initializing /usr/lib/lua/luci/sgi/uhttpd.lua Lua handler: /usr/lib/lua/luci/http.lua:143: attempt to index local 'L' (a nil value)
Wed Oct  5 08:50:58 2022 daemon.err uhttpd[4045]: Error initializing /usr/lib/lua/luci/sgi/uhttpd.lua Lua handler: /usr/lib/lua/luci/http.lua:143: attempt to index local 'L' (a nil value)
Wed Oct  5 08:50:58 2022 daemon.info procd: Instance uhttpd::instance1 s in a crash loop 6 crashes, 1 seconds since last crash

We also need to fix lua_prefix handling in /etc/init.d/uhttpd. After removing lua_prefix from /etc/config/uhttpd:
# /etc/init.d/uhttpd restart
Skipping invalid Lua prefix "="

The empty Lua prefix is not fatal though.

Status > Realtime Graphs > Connections shows 0 for everything.

System > Status > Firewall
NetworkError

HTTP error 404 while loading class file "/luci-static/resources/tools/firewall.js?v=git-22.270.30123-c4d514b"
  at compileClass (https://<IP_ADDRESS>/luci-static/resources/luci.js?v=git-22.270.30123-c4d514b:168:16)

We need to cleanup the lua_prefix:

Fixed by 0a3a13a1a45ba0a8ddcaa7049896451e3fad1b0e

We also need to fix lua_prefix handling in /etc/init.d/uhttpd. After removing lua_prefix from /etc/config/uhttpd:

Fixed by https://git.openwrt.org/?p=openwrt/staging/jow.git;a=commit;h=c10058b706f1816418deba5633e2f983c871b5c5

Status > Realtime Graphs > Connections shows 0 for everything.

The kernel might be lacking legacy /proc/net/nf_conntrack support. Is luci-bwc -c on the cli showing anything?

System > Status > Firewall

This one is unrelated to the ucode rewrite

build failed:
make V=s package/feeds/luci/luci-base/compile
make[2]: Entering directory '/mnt/Data/Sources/openwrt/x-wrt/scripts/config'
make[2]: 'conf' is up to date.
make[2]: Leaving directory '/mnt/Data/Sources/openwrt/x-wrt/scripts/config'
make[1]: Entering directory '/mnt/Data/Sources/openwrt/x-wrt'
make[2]: Entering directory '/mnt/Data/Sources/openwrt/openwrt-feeds/luci/modules/luci-base'
../../luci.mk:115: *** unterminated call to function 'if': missing ')'.  Stop.
make[2]: Leaving directory '/mnt/Data/Sources/openwrt/openwrt-feeds/luci/modules/luci-base'
time: package/feeds/luci/luci-base/host-compile#0.19#0.15#0.34
    ERROR: package/feeds/luci/luci-base [host] failed to build.
package/Makefile:114: recipe for target 'package/feeds/luci/luci-base/host/compile' failed
make[1]: *** [package/feeds/luci/luci-base/host/compile] Error 1
make[1]: Leaving directory '/mnt/Data/Sources/openwrt/x-wrt'
/mnt/Data/Sources/openwrt/x-wrt/include/toplevel.mk:229: recipe for target 'package/feeds/luci/luci-base/compile' failed
make: *** [package/feeds/luci/luci-base/compile] Error 2

Please see if an rm -r tmp/ fixes it. I can't reproduce it here.

@jow-  very strange
on Ubuntu 22.04, my build is good
but failed on Ubuntu 18.04

Please see if an rm -r tmp/ fixes it. I can't reproduce it here.
@ptpt52 - it appears the problem is specific to make 4.2, works with 4.3

sure, it is make 4.1 on Ubuntu 18.04

@jow-  is it possible to make it compatible with make 4.1 ?

@jow-  great.
another issue:
Luci theme bootstrap language translate cannot works.
I change lang to zh_CN, but the UI still in English.

@ptpt52 - fixed as well

git status shows uncommited files.
This maybe?
diff --git a/.gitignore b/.gitignore
index 7834b9bce4..54fce84c96 100644
--- a/.gitignore
+++ b/.gitignore
@@ -10,8 +10,8 @@ package-lock.json
 modules/luci-base/src/po2lmo
 modules/luci-base/src/jsmin
 modules/luci-base/src/contrib/lemon
-modules/luci-base/src/ucode/plural_formula.c
-modules/luci-base/src/ucode/plural_formula.h
+modules/luci-base/src/lib/plural_formula.c
+modules/luci-base/src/lib/plural_formula.h
 modules/luci-compat/src/contrib/lemon
 modules/luci-compat/src/plural_formula.c
 modules/luci-compat/src/plural_formula.h

@dhewg - thanks, fixed.

@jow-
root@X-WRT:~# echo 'require("luci.http")' | lua
lua: /usr/lib/lua/luci/http.lua:143: attempt to index local 'L' (a nil value)
stack traceback:
	/usr/lib/lua/luci/http.lua:143: in main chunk
	[C]: in function 'require'
	stdin:1: in main chunk
	[C]: ?

I am trying to load luci.http but show this error.

@ptpt52 - This module cannot be used anymore in a stand alone manner.


with() should flush with the request logger

If you create a new logger by running req.log.with({ … }), it won’t get flushed at the end of the request, but it should.

why req.log.with({ … }) is different? it returns an instance of the logger with autoFlush = true.

Yes, but withAxiom will only flush the parent logger (e.g. here), we need to keep track of child loggers to flush all of them.

@bahlo This has been addressed in the new version 0.16.0, now flush() will loop over the sub-loggers and flush all of them.


Feature/import upstream

Description
import upstream from origin
There were no conflicts
Checklist

[ ] Required by CI: Code is auto formatted using clang-format
[ ] Extend the tutorials / documentation reference
[ ] Document API changes relevant to the user in the MIGRATION.md notes
[ ] Create tests, which fail without this PR reference
[ ] Include a screenshot if changing a GUI
[ ] While waiting for someone to review your request, please help review another open pull request to support the maintainers

If upstream is imported with #13 reflected, moveit cannot be started
Since #13 has the problem of #25, we will revert #13 once and import the upstream branch
We should then redo the work on #13 again


AtlasTexture does not repeated in sprites

Operating system or device - Godot version:
Godot Engine <IP_ADDRESS> (Ubuntu 16.04 - 64bits)
Issue description (what happened, and what was expected):
The AtlasTexture is not repeated on the sprite.
Steps to reproduce:

Create a Sprite
Load the AtlasTexture (or create a new one)
Check Region on and set Region Rect (0, 0, 300, 300) (to have the "repeated effect")
Click Edit the Texture
Click Edit the Atlas
Check Repeat on ImageTexture Flags.

Image example:

this is a normal situation. it should be

Well, even if it is normal, it would be nice if it is either fixed or explained in the docs.

Can you explain why the AtlasTexture does that ?
I use many AtlasTexture instead of ImageTexture. In this case what is the difference ?

I'm afraid my English it would be hard to do, but I'll try.
The fact that the repetition of the texture makes the graphics api itself. we just do the settings, specify the texture coordinates is greater than 1 and that the texture must be repeated. In the case of an atlas, you can repeat the whole atlas of the whole, but a separate part is unlikely.
In your case, just do not need to add the textures in the atlas that you want to display in this way. I think that these textures you will not have a lot, and it's not like will not affect the performance.

@godotengine/bugsquad: you might consider retagging as documentation if this is so indeed.

@bojidar-bg You're in bugsquad too :)

why would one want to apply a GL_REPEAT to texture atlas ?
the GL_REPEAT applies only when the texture UV mapping exceed the borders of the texture.
AFAIUC*, atlas are used to gather multiple textures into a single one. So, when displaying one of them, it is not possible to set texture UV coords that exceed the borders of the texture-atlas. GL_REPEAT cannot apply.
(*As Far As I Understand Correctly)

@SuperUserNameMan AFAIUC it is so indeed, but I would like a confirmation by either @reduz or someone else knowledgeable.

Ok, I understand better why "it is normal" and it is OpenGL that repeats the entire texture despite the UV.
I have tested with a simple ImageTexture, and the rendering isn't good.
Unlike my atlas, the size of the image is not power of 2.
The repeat option seems not work without MipMaps. And the Mipmaps add a "blur effect".
The AtlasTexture's rendering matched exactly with the Inkscape's export.
How to correctly repeat a "not in power of 2" image in a sprite ?

So this is not a bug but just a documentation issue right?

@DualMatrix Yep.  You can work around it by making a shader and passing in the uv extents of the rect so the shader itself can 'wrap' just the required rect instead of the whole image.

This bug now exists.

Th is no longer the case in master.

The documentation has yet to be updated, however.
https://github.com/godotengine/godot/blob/3472bdd6b6dd7c085b716caabdda16f88e6f167e/doc/classes/AtlasTexture.xml#L8

This is no longer the case in master.

Looks like it doesn't work again and the documentation implies that only nested AtlasTextures won't repeat.


HBASE-24721: rename_rsgroup overwriting the existing rsgroup.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 49s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 58s
the patch passed

+1 :green_heart:
compile
1m  5s
the patch passed

+1 :green_heart:
javac
1m  5s
the patch passed

+1 :green_heart:
shadedjars
5m 44s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 39s
hbase-server in the patch failed.

Pending QA

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  6s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m  4s
master passed

+1 :green_heart:
compile
0m 55s
master passed

+1 :green_heart:
shadedjars
6m  4s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 47s
the patch passed

+1 :green_heart:
compile
0m 57s
the patch passed

+1 :green_heart:
javac
0m 57s
the patch passed

+1 :green_heart:
shadedjars
6m  7s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 35s
the patch passed

_ Other Tests _

-1 :x:
unit
204m  2s
hbase-server in the patch failed.

229m 50s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2059/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2059

JIRA Issue
HBASE-24721

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f4dd1a83c5a8 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3bd54217a0

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2059/2/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2059/2/testReport/

Max. process+thread count
3119 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2059/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m  7s
the patch passed

+1 :green_heart:
compile
1m 23s
the patch passed

+1 :green_heart:
javac
1m 23s
the patch passed

+1 :green_heart:
shadedjars
7m 28s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 46s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
211m 44s
hbase-server in the patch passed.

244m  5s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2059/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2059

JIRA Issue
HBASE-24721

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 242cbee1a67e 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3bd54217a0

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2059/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2059/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2059/2/testReport/

Max. process+thread count
3139 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2059/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


[suggestion] She needs a feature using multiple accounts google or RTS, for faster scanning

This program is simply a bomb. This program is perfectly coped before, but now she needs a feature using multiple accounts google or RTS, for faster scanning and every account that will scan the area to give a random color.

I'd love to see some kind of solution to the limited scanning radius now.  Again... it's not a scanning time for me.  The range of which things are scanned simply isn't like it use to be.  It appears to be around 100m now?  Before the last update, it would scan about .5 mile radius or something like that.

I too would love to see a way to scan with multiple PTC accounts from a single PC, I have a lot of accounts just sitting around that could be running scans for my API but no way for me to utilise them (Or I don't know how to! As I'm far from a pro at this sort of thing), if there is a way to do this, could somebody please let me know? Thanks!

To use multiple PTC accounts, load up multiple instances of the desktop app and log into each instance with a different PTC account but the same Google Maps API Key. The results from all the individual apps will appear on each others maps.
You can also alter the radius of the search area at the bottom of the log-in screen. It defaults to 7, which is 7 search areas in a radius from your center point. You can adjust this to get the right search area you need.


Add more CSV information to the PackageManifest

Description of the change:
Transfer spec.relatedImages, spec.minKubeVersion, and spec.nativeAPIs
information from the CSV onto the packagemanifest response.
Signed-off-by: Vu Dinh<EMAIL_ADDRESS>Motivation for the change:
CSVs are transformed from the in-bundle representation to the packagemanifest
by selecting fields to display. Those additional fields will support the UI.
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

/retest

/retest

/retest

/retest

/retest

/retest

@ecordell Ready for review

/retest

/retest

/retest

/retest

/retest

I expect the RelatedImages info will be a part of registry API response when you query bundle info in the future. Then, we no longer need to parse the raw bundle JSON in the future.

Sorry, I see  https://github.com/operator-framework/operator-lifecycle-manager/pull/1387/files#diff-f23331df68a5aa78273da61eca6bac31R830 to the CSVDescription was applied RelatedImages. I have a question: RelatedImages section will be exposed or this information is encapsulated inside registry? I mean when I have installed operator and I do command: kubectl get csv some-operator -n somenamespace Should response  contains field with relatedImages?

RelatedImages is captured in the registry, not in the CSV object. You can get RelatedImages if you query PackageManifest.

You can get RelatedImages if you query PackageManifest

I see. But, I guess it returns RelatedImages only for latest bundle. Am I correct?

Correct, latest bundle for each channel.

/cherry-pick release-4.4


Support supplying custom pod labels

Hello!
I've added the parameter to allow users to supply additional pod labels, complementing the existing ones. This can help user control over deployments, improve monitoring, and assist in both organization and policy definition based on pod labels.
Please share any concerns or feedback you might have regarding this change!

Hi @glowkey,
Thank you for the approval. I just force pushed to include the commit signature.
Could you please approve having the workflow rerun again in other to pass the check?

Hi @glowkey,
Could you please help to bump a new version if that's convenient to you, so we can pull the latest helm chart from the repo?
Thank you!

We plan on releasing an updated DCGM Exporter in the next few days to coincide with the DCGM 3.3.0 release. It will include this change.


Leaderboard now selects the player when searching by rank

Searching by name selects the player, but searching by rank doesn't. This makes it so that searching by rank also selects the player.

Why does this decrease coverage on ReplayService.java?

Well this might be obsolete soon but ok... Some guys are working on pagination for leaderboard

stale


Watcher stores DiffResult instead of ApolloQueryResult into query's newData

I've been having this problem where the data is sometimes missing for a component during a react update.
After much debugging, I think I have found the cause.  I'm not sure how to reproduce it quite yet, since I'm still learning the working of apollo-client.
I first realized something was wrong when looking in the debugger here:
https://github.com/apollographql/apollo-client/blob/master/packages/apollo-client/src/core/QueryManager.ts#L947
      const { newData } = this.getQuery(observableQuery.queryId);
      if (newData) {
        return maybeDeepFreeze({ data: newData.data, partial: false });  // <--- HERE
      } else {

At this point I see that newData has fields result and complete

it is a Cache.DiffResult instance rather than ApolloQueryResult.

How does this happen?
Well, I can trace it back to:
https://github.com/apollographql/apollo-client/blob/master/packages/apollo-client/src/core/QueryManager.ts#L730
  public updateQueryWatch(
    queryId: string,
    document: DocumentNode,
    options: WatchQueryOptions,
  ) {
    const { cancel } = this.getQuery(queryId);
    if (cancel) cancel();

    return this.dataStore.getCache().watch({
      // ... snip snip ...
      callback: (newData: ApolloQueryResult<any>) => {
        this.setQuery(queryId, () => ({ invalidated: true, newData }));   // <--- HERE
      },
    });
  }

This is where I can see the offending value placed into the query.  On this line, newData is of the wrong type.
Looking at https://github.com/apollographql/apollo-client/blob/master/packages/apollo-cache-inmemory/src/inMemoryCache.ts#L244  I can see that it does in fact pass a Cache.DiffResult to the watcher callback:
  private broadcastWatches() {
    // Skip this when silenced (like inside a transaction)
    if (this.silenceBroadcast) return;

    // right now, we invalidate all queries whenever anything changes
    this.watches.forEach((c: Cache.WatchOptions) => {
      const newData = this.diff({
        query: c.query,
        variables: c.variables,

        // TODO: previousResult isn't in the types - this will only work
        // with ObservableQuery which is in a different package
        previousResult: (c as any).previousResult && c.previousResult(),
        optimistic: c.optimistic,
      });

      c.callback(newData);  // <--- HERE
    });
  }

Notice how newData is the result of diff when passed to the callback.
I'm not sure exactly who the offender is here - that is, where exactly the DiffResult was supposed to become an ApolloQueryResult.  Maybe here: https://github.com/apollographql/apollo-client/blob/master/packages/apollo-client/src/core/QueryManager.ts#L730  it should have constructed one from the DiffResult ?
The symptom I get from this is that the components reload in an endless loop, but I think it may be this bug is just causing some confusion and it thinks something needs to be loaded that is already loaded.

➤ Dobes Vandermeer commented:
See also https://github.com/apollographql/apollo-client/commit/69fcfcc762be8fc055cd8a5fb3dc75b48ace1adb

➤ Dobes Vandermeer commented:
https://github.com/apollographql/apollo-client/commit/69fcfcc762be8fc055cd8a5fb3dc75b48ace1adb#commitcomment-25497374

➤ Dobes Vandermeer commented:
Despite my best efforts I cannot create a simple reproduction for this, it seems like you have to have some sequence of events occur to get the issue I am having, and I don't know what that sequence of steps is.  Anyway, the information above I think does reveal some kind of type mismatch.  Also of interest is that at https://github.com/apollographql/apollo-client/blob/master/packages/apollo-client/src/core/QueryManager.ts#L418 it seems like it does expect a DiffResult for newData as well.


calls / working group

Hi,
are there any working group and periodic calls on this topic related to VPP integration within SONiC ?

We will setup one shortly.


Fix authenticate methods

Description
Documentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

Current dependencies on/for this PR:

users

PR #191

PR #192

PR #193

PR #195

PR #196

PR #197

PR #198

PR #199


There is no "Universal Windows App" for "Application  type" field

The screenshot for creating a new key is out of sync with the current condition. There is no "Universal Windows App" for "Application  type" field.
Please update the screenshot. Thank you!

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

ID: c1326ab8-50fc-edaf-6f91-591b6b813213
Version Independent ID: 6cfd2845-011b-4b84-ed53-b8bc94b9c8d5
Content: Request a maps authentication key - UWP applications
Content Source: windows-apps-src/maps-and-location/authentication-key.md
Product: uwp
Technology: people-and-places
GitHub Login: @hickeys
Microsoft Alias: hickeys

Just checked in a new image. It will be published shortly. Thank you.


Split client installation and configuration so we can reconfigure client several times

Hi,
I added all the client setup in another recipe recipes/setup.rb to be able to call it in different steps. My user case is this:

I bake AWS AMIs using chef; try to install all the packages, libraries, etc and the remove all repositories.
Deploy instances using this AMIs and configure all the services without requesting 3rd party resources (repositories, etc) withoud internet access. That limits my actions (cannot make yum make cache, http requests, etc), that's why I have no yum repos, pip calls, etc in my config layer.

Having setup.rb I may call it in my step 2 without messing with repo stuffs, while the current behaviour is not altered.  I updated unit tests to verify that changes.
Also I found an update in cookbook chef-vault (version 1.3.0 to 1.3.1) that breaks the unit tests for chef-splunk, so I froze Berksfile to use stable version 1.2.5 (1.3.0 can be used as well).
Besides I included changes made by #34. Please review them.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
Non-GitHub Verified Committers
There are 1 commit author(s) whose commits are authored by a non-GitHub verified email address. Chef will have to manually verify that they are authorized to contribute.
Please sign the CLA here.


tintTarget not working

[x] I have verified the issue exists on the latest version
[x] I am able to reproduce it

Version used: 1.6.1
Support Library version: 25.1.0
Android version: 6.0
Hello. After updating library from 1.6.0 to 1.6.1, the tintTarget method doesn't work for me anymore. The same code worked well with version 1.6.0. I'm using it in a sequence to tint a toolbar menu item's icon.
My icon in toolbar is white and should be tinted to yellow, which is my primaryColor. But the icon stays white so it's not visible.
TapTargetSequence sequence = new TapTargetSequence(getActivity()) .targets(
// another TapTargets..
      TapTarget.forToolbarMenuItem(toolbar, R.id.action_one, getString(R.string.guide_title), getString(R.string.guide_subtitle))
                               .cancelable(false)
                               .tintTarget(true))
.listener(new TapTargetSequence.Listener() {

                   @Override
                   public void onSequenceFinish() {    }

                   @Override
                   public void onSequenceCanceled(TapTarget lastTarget) {       }
               });

The only thing that could modify the behavior of tintTarget that is new in 1.6.1 would be the fact that I'm no longer creating bitmaps for targets that are 0x0 big, however from your code it seems like the problem TapTarget is not the first target displayed, so there shouldn't be any race conditions causing your view to be 0x0 in size.
I will have to see if I can reproduce this on my end...

Yes, it's not the first target in the sequence (there are 4 more TapTarget.forView() before), but is's the first ToolbarMenuItem target. And there are no other targets after.
I also forgot to mention that when I exit my app using the home button right in the step, when the icon  should be tinted (but is not), and then open the app again, the icon is tinted properly.

Actually its reproducible by running the sample... Looking into it. Thanks for the report

Hi @lenoch0d I believe I have fixed it. Can you please try the latest snapshot and let me know?

@xiphirx I've tried it and it works!. Thank you for fixing it and for the library!


Migrate Vault User Guide

from https://github.com/bcgov/how-to-workshops/tree/master/vault

@ty2k this is amazing! thank you for the updates!


iree_cc_library INCLUDES directories as -isystem, which disables warnings

The patch https://github.com/openxla/iree/pull/16011 switched the style by which we include IREE directories on the compiler search path. It was doing this with an always-included library generated with iree_cc_library that was an implicit dep for all others. It was switched to be a stock CMake add_library INTERFACE lib. It was expected that this should have been an NFC but it was not: many compilation failures were introduced due to seemingly ignored warnings in the prior state. I fixed the warnings inline with that patch and landed it, but it seems we have been running warning-degraded on headers for a long time.
I compared one of the newly broken invocations before and after the change:
After/good:
ccache /usr/bin/clang++  -I/home/stella/src/iree/third_party/vulkan_headers/include -I/home/stella/src/iree/runtime/src -I/home/stella/src/iree-build/runtime/src -isystem /home/stella/src/iree -isystem /home/stella/src/iree-build -isystem /home/stella/src/iree-build/runtime/src/iree/base/internal/flatcc -isystem /home/stella/src/iree/third_party/flatcc/include -isystem /home/stella/src/iree-build/runtime/src/iree/schemas -O2 -g   -gsplit-dwarf -ggnu-pubnames -std=gnu++17 -fPIC -fvisibility=hidden -fno-rtti -fno-exceptions -Werror -Wall -Wno-error=deprecated-declarations -Wno-ambiguous-member-template -Wno-char-subscripts -Wno-extern-c-compat -Wno-gnu-alignof-expression -Wno-gnu-variable-sized-type-not-at-end -Wno-ignored-optimization-argument -Wno-invalid-offsetof -Wno-invalid-source-encoding -Wno-mismatched-tags -Wno-pointer-sign -Wno-reserved-user-defined-literal -Wno-return-type-c-linkage -Wno-self-assign-overloaded -Wno-sign-compare -Wno-signed-unsigned-wchar -Wno-strict-overflow -Wno-trigraphs -Wno-unknown-pragmas -Wno-unknown-warning-option -Wno-unused-command-line-argument -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef -Wno-unused-private-field -Wno-user-defined-warnings -Wno-missing-braces -Wc++20-extensions -Wctad-maybe-unsupported -Wfloat-overflow-conversion -Wfloat-zero-conversion -Wfor-loop-analysis -Wformat-security -Wgnu-redeclared-enum -Wimplicit-fallthrough -Winfinite-recursion -Wliteral-conversion -Wnon-virtual-dtor -Woverloaded-virtual -Wpointer-arith -Wself-assign -Wstring-conversion -Wtautological-overlap-compare -Wthread-safety -Wthread-safety-beta -Wunused-comparison -Wvla -fno-lax-vector-conversions -fno-omit-frame-pointer -fmacro-prefix-map=/home/stella/src/iree=iree -I/home/stella/src/iree/third_party/flatcc/include/ -I/home/stella/src/iree/third_party/flatcc/include/flatcc/reflection/ -MD -MT runtime/src/iree/hal/drivers/vulkan/CMakeFiles/iree_hal_drivers_vulkan_vulkan.objects.dir/descriptor_set_arena.cc.o -MF runtime/src/iree/hal/drivers/vulkan/CMakeFiles/iree_hal_drivers_vulkan_vulkan.objects.dir/descriptor_set_arena.cc.o.d -o runtime/src/iree/hal/drivers/vulkan/CMakeFiles/iree_hal_drivers_vulkan_vulkan.objects.dir/descriptor_set_arena.cc.o -c /home/stella/src/iree/runtime/src/iree/hal/drivers/vulkan/descriptor_set_arena.cc

Before/Bad:
ccache /usr/bin/clang++  -I/home/stella/src/iree/third_party/vulkan_headers/include -isystem /home/stella/src/iree -isystem /home/stella/src/iree-build -isystem /home/stella/src/iree/runtime/src/iree/.. -isystem /home/stella/src/iree-build/runtime/src/iree/.. -isystem /home/stella/src/iree-build/runtime/src/iree/base/internal/flatcc -isystem /home/stella/src/iree/third_party/flatcc/include -isystem /home/stella/src/iree-build/runtime/src/iree/schemas -O2 -g   -gsplit-dwarf -ggnu-pubnames -std=gnu++17 -fPIC -fvisibility=hidden -fno-rtti -fno-exceptions -Werror -Wall -Wno-ambiguous-member-template -Wno-char-subscripts -Wno-extern-c-compat -Wno-gnu-alignof-expression -Wno-gnu-variable-sized-type-not-at-end -Wno-ignored-optimization-argument -Wno-invalid-offsetof -Wno-invalid-source-encoding -Wno-mismatched-tags -Wno-pointer-sign -Wno-reserved-user-defined-literal -Wno-return-type-c-linkage -Wno-self-assign-overloaded -Wno-sign-compare -Wno-signed-unsigned-wchar -Wno-strict-overflow -Wno-trigraphs -Wno-unknown-pragmas -Wno-unknown-warning-option -Wno-unused-command-line-argument -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef -Wno-unused-private-field -Wno-user-defined-warnings -Wc++20-extensions -Wctad-maybe-unsupported -Wfloat-overflow-conversion -Wfloat-zero-conversion -Wfor-loop-analysis -Wformat-security -Wgnu-redeclared-enum -Wimplicit-fallthrough -Winfinite-recursion -Wliteral-conversion -Wnon-virtual-dtor -Woverloaded-virtual -Wpointer-arith -Wself-assign -Wstring-conversion -Wtautological-overlap-compare -Wthread-safety -Wthread-safety-beta -Wunused-comparison -Wvla -fno-lax-vector-conversions -fno-omit-frame-pointer -fmacro-prefix-map=/home/stella/src/iree=iree -I/home/stella/src/iree/third_party/flatcc/include/ -I/home/stella/src/iree/third_party/flatcc/include/flatcc/reflection/ -MD -MT runtime/src/iree/hal/drivers/vulkan/CMakeFiles/iree_hal_drivers_vulkan_vulkan.objects.dir/descriptor_set_arena.cc.o -MF runtime/src/iree/hal/drivers/vulkan/CMakeFiles/iree_hal_drivers_vulkan_vulkan.objects.dir/descriptor_set_arena.cc.o.d -o runtime/src/iree/hal/drivers/vulkan/CMakeFiles/iree_hal_drivers_vulkan_vulkan.objects.dir/descriptor_set_arena.cc.o -c /home/stella/src/iree/runtime/src/iree/hal/drivers/vulkan/descriptor_set_arena.cc

Leaving aside some warning flag differences that were intentional, we see that the main difference is that in-tree includes are being added with -isystem for the prior state. This was suppressing warnings on a large body of our code.
While the above change set this right for the main include directories, there are still others that I think may be suspect.
I don't remember why this was done, but it was possibly to match Bazel (which suspiciously has been passing this whole time based on a similar setup). I think that was clearly a mistake and a really bad footgun.
We should back out the remaining uses of -isystem and reserve it for cases that truly need it.

Some googling reveals:

https://github.com/RobotLocomotion/drake/issues/8197#issuecomment-388473495
https://groups.google.com/g/bazel-discuss/c/HyyuuqTxKok?pli=1

This is, imho, a massive design flaw for Bazel. I was forced to use that thing for 10 years and didn't know about this build-correctness impacting hitch.


Added a new link in repos.js

solves #81
Summary:
This pull request addresses the issue #81  : Adding a repository link to the ./_data/repos.js file.
Changes Made:
In this pull request, I have added a repository link to the ./_data/repos.js file. The added repository meets the following criteria:

The repository has been updated within the last 3 days.
The repository has 20 or more stars.
The repository is currently accepting contributions.

Repository Link:
https://github.com/developer-student-clubs/npmBox
Testing:
I have tested the changes to ensure that the added repository link correctly fulfills the specified criteria.
Please review this pull request, and if any further modifications or clarifications are needed, I am ready to make them. Thank you for your time and consideration.

Heyy @anand346 ,i am a begineer in open source contributions .
Please review my pull request and add relevant label as this contribution is under hacktoberfest.


[NTR] CD3+ T cell

Preferred term label:
'CD3-positive, alpha-beta T cell'
Synonyms
CD3-positive, alpha-beta T lymphocyte
CD3-positive, alpha-beta T-cell
CD3-positive, alpha-beta T-lymphocyte
CD3+ T cell
Definition (free text, please give PubMed ID)
A T cell expressing an alpha-beta T cell receptor and the CD3 coreceptor.
'mature alpha-beta T cell'
and ('has plasma membrane part' some 'CD3 subunit with immunoglobulin domain')
Parent term
'mature alpha-beta T cell'
related ticket: https://github.com/obophenotype/human-phenotype-ontology/issues/5701
@addiehl does this look okay to you?

We do not need this term.  The alpha-beta T cell receptor contains the CD3 chains by default -- they are part of the TCR protein complex.

Beyond which, all mature T cells are CD3+, because CD3 is a component of the gamma-delta TCR complex as well.  Also, when people say CD3+, they really mean CD3e positive, because that is the CD3 chain that is almost always targeted in a flow cytometry assay.

Thanks, Alex and thanks for your comment on the HPO ticket. We can close this.


Machine type aarch64 not allowed

I will run hass.io on a TV box, quad core, 4GB RAM, 64-bit Armbian.
Looking at the targets in the script, I can pick either qemuarm-64 or RaspberryPi4-64.
There is no generic aarch64 machine. But the images to support is are here: https://hub.docker.com/u/homeassistant
So I added aarch64 as an acceptable machine to the approved list - I assume it should be done so everybody can install on arm64 without pretending to be a Pi. Or is the Pi4-64 a better target to choose ?
Allowing and using machine type aarch64, I now run homeassistant/aarch64-homeassistant:0.105.2 with the pi4-64 target I was running this container:
homeassistant/raspberrypi4-64-homeassistant:0.105.2
So seems there is an image for target machine = aarch64
if [[ ! "intel-nuc odroid-c2 odroid-n2 odroid-xu qemuarm qemuarm-64 qemux86 qemux86-64 raspberrypi raspberrypi2 raspberrypi3 raspberrypi4 raspberrypi3-64 raspberrypi4-64 tinker" = *"${MACHINE}"* ]]; then
    echo "[Error] Unknown machine type ${MACHINE}!"
    exit 1
fi

qemuarm-64 is the generic machine version for the aarch64 architecture...

Docs should be updated then to make it clear. And I really could not find anything telling me what the difference is. And why do the aarch64 version of homeassistabt docker image even exist ?

Machine types and architecture are not the same things.
aarch64 is used on Docker images that are not bound to a machine type, however, we do have images bound to a machine type to support specific machines better. (e.g., the Pi). However, that does not mean each image used on that machine uses a machine-specific version.
Feel free to open up a PR to our documentation if you thing improvements on that part is needed 👍


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade" workflow

Codecov Report

Merging #108 (0d4ed4d) into main (2974dfe) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #108   +/-   ##
=======================================
  Coverage   83.33%   83.33%
=======================================
  Files           2        2
  Lines         126      126
  Branches       31       30    -1
=======================================
  Hits          105      105
  Misses         21       21

Impacted Files
Coverage Δ

example/src/main.ts
88.46% <100.00%> (ø)

src/index.ts
82.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 a31ad6d...0d4ed4d. Read the comment docs.


Flowers Classification

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Flowers Classification
:red_circle: Aim : Build a model based on Tensorflow to classify the flowers from the given dataset.
:red_circle: Dataset : https://www.kaggle.com/datasets/ryanholbrook/tensorflow-flowers
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Full name :Shwetmala Jha
GitHub Profile Link : https://github.com/shwetmala55
Email ID<EMAIL_ADDRESS>Approach for this Project :classification of flowers
What is your participant role?-contributor ,SSOC-2022

Can you elaborate your deep learning approaches? @shwetmala55

@shwetmala55 you have been assigned this issue. All the best.

Can you elaborate your deep learning approaches? @shwetmala55

will use different method to train the model and compare their accuracy, I recently started with deep learning so intend to learn while contributing.

@shwetmala55 you have been assigned this issue. All the best.

Thank you!

@shwetmala55 updates please.

Updates please @shwetmala55

Updates please @shwetmala55

im sorry for delay.. facing some issues.. plz give me more time to complete this project

Okay, take your time @shwetmala55

Full Name:- B Mani Chander
Github Profile link:- https://github.com/manichander429
Email id:-<EMAIL_ADDRESS>Approach for this project:- so recently I developed a cnn model for diabetic retinopathy detection. Coming to the approach First, I will perform data augmentation, so that the model I develop can learn enough features to detect. Then, I would try using different models/architectures like cnn, ResNet, AlexNet, GoogleNet.. Etc. Then I will perform some hypertuning in order to find the optimal hyperparameters and then I will compare the accuracy of the developed models.
What is your participant role?-contributor ,SSOC-Season-2

Hii @abhisheks008 .. I would like to contribute to this repo


[Feature] Case-sensitive functions may be required

Initial checklist

[X] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Problem

[ ] EXACT
[x] FIND
[x] FINDB
[ ] SEARCHB
[ ] SEARCH
[ ] REPLACEB
[ ] MIDB

Solution

Already listed or completed in other issues


Illegal Activity

Your subdomain is being misused for the promotion of illegal gambling sites in Indonesia. url : depo25bonus25.refreshless.com

Thanks for reporting this. I had a wildcard DNS record pointing to GitHub pages, which isn't quite a good idea. I've fixed that, now.


Lbrel

try except pattern for individual fields with missing lbrel values in Fields Files
these fields are skipped with a warning
requires
https://github.com/SciTools/iris-test-data/pull/48
and updated test sha

@pp-mo
this would be very useful for a user if it made it into 1.12.  I have added it to the milestone, please may you consider whether it is suitable and in time?
thank you
mark

However, I think skipping the field is an equally reasonable response to any other possible problems ?

I think this is particularly the case for fields files, yes
the conversion to a PP object in our code may go wrong for a field, and at present that junks the whole load.
I have updated the skip message to pass through the PP exception, I hope this now represents a reasonable approach


[DOCS] Include how to load the Multilevel Hierarchies for example : BOM (Bill of Materials)- Hierarchial Link

Describe the bug
A clear and concise description of what the bug is.
Environment
dbt version:
automate_dv version:
Database/Platform:
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Log files
If applicable, provide dbt log files which include the problem.
Additional context
Add any other context about the problem here.

Hi, it looks like you've not filled in the big report. Can you provide more details please?

Hello. Closing due to lack of information about what you are asking us to add.
Bear in mind the AutomateDV Docs are not intended to be a source of Data Vault training, but guidance on how to use the tool itself. The docs only include examples or details of the Data Vault approach where relevant to support the AutomateDV feature being described.


Fixing issue with empty aws_http_tokens in ocm responce

It fixed e2e test error
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to ocm_cluster_rosa_classic.rosa_sts_cluster,
│ provider "provider["terraform.local/local/ocm"]" produced an unexpected
│ new value: .aws_http_tokens_state: was null, but now cty.StringVal("").
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵

/retitle Fixing issue with empty aws_http_tokens in ocm response


Update architecture.md

What
Updated Visuals
Refs

(this project accepts pull requests related to open issues)
(if suggesting a new feature or change, please discuss it in an issue first)
(if fixing a bug, there should be an issue describing it with steps to reproduce)
(only fixing a minor bug - broken link, typo - an issue is not needed)
(please link to the issue here)

Will be included here: https://github.com/gnosischain/documentation/pull/374


Unable to download update or reinstall

Describe the bug
Getting this error in logs when I try to update or reinstall after removing.
A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/BottlecapDave/HomeAssistant-OctopusEnergy/v10.0.3/custom_components/octopus_energy/gas/next_rate.py, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 4
Reproduction steps
Unknown, I started off by trying to update to the latest version 10
0.3
Expected behaviour
It to download and request a restart.
Tariff Code
Unknown
Integration Version
10.0.3
Home Assistant Version
Latest
Fresh Install?
Not specified
Home Assistant Logs
A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/BottlecapDave/HomeAssistant-OctopusEnergy/v10.0.3/custom_components/octopus_energy/gas/next_rate.py, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 4
Confirmation

[X] I confirm that I cannot find my solution within the documentation
[X] I confirm that I cannot find my solution within the FAQ

Hello. This is unfortunately outside of the integration and you'll need to raise with the HACs team.

This is not a problem with HACS but how your host communicates with GitHub

This implies it may be an issue with your instance. I can't really assist with this, but this thread implies it might be an issue with IPv6 and your instance.


daytona target set non-interactive mode

Is your feature request related to a problem? Please describe.
daytona target set commands are only runnable interactively.
Describe the solution you'd like
They should have flags that can be set to run the entire command non-interactively.

This Issue has been automatically marked as "stale" because it has not had recent activity (for 14 days). It will be closed if no further activity occurs. Thanks for the feedback.

Since targets are defined by providers, we can't provide flags for all inputs (e.g. --remote-username USERNAME --remote-password PASS etc.)
We could allow piping json into the command and then parse that into the target values (similarly to how you can pipe yaml into kubectl)

@quest-bot stash 100

@quest-bot embark

@quest-bot embark

@quest-bot loot https://github.com/daytonaio/daytona/issues/1051

@quest-bot loot https://github.com/daytonaio/daytona/pull/1380


introduce helm chart

add buildkit to dapper

Sorry the build fails, but this has nothing todo with my changes. I'm not able to fix it. It seems to be a docker issue

After disabling Buildkit the buid works

Is there any way you can consume the CRDs from the build artifacts, instead of maintaining a static copy in the chart dir?

@brandond: I think it is a good idea. In addition I would like to package the helm during the build.  But I'm not familiar with the build process, Could you please tell me how to integrate a helm package step after the usual build where the crd.yaml is created ?
Addionally i would relocate it to a crd subfolder according to https://helm.sh/docs/chart_best_practices/custom_resource_definitions/. So please can you tell me how I can change and test the built process ?

I tried bringing up something related here https://github.com/rancher/system-upgrade-controller/issues/172#issuecomment-1123708559

Would you mind updating this to reflect recent changes to the RBAC?

Maybe if you need help, but not in March. Too busy on a new work.

That was intended for the PR author.

@hurzelpurzel Recent kustomization issues involving the latest tag broke our project, we need this helm chart.

I'm using parts of this helm chart  from the PR already to create plans. An official helm chart would be awesome and highly appreciated.

Recently synced my forked repo. Is there anymore that I can do ? Or what is blocking the merge ?

They are not using the cluster admin role anymore, check the latest release 0.13.4

Unfortunately even if this was merged, I don't see any workflow to publish the Helm chart anywhere.

Unfortunately even if this was merged, I don't see any workflow to publish the Helm chart anywhere.

I could look into that

I suggested a helm release action here https://github.com/hurzelpurzel/system-upgrade-controller/pull/1/files
But it requires some additional setup by the owners.
From the documentation:

Pre-requisites
One of these confuguration
A GitHub repo containing a single chart in root directory (Chart.yaml)
A directory with your Helm charts (default is a folder named /charts, if you want to maintain your charts in a different directory, you must include a settings.charts_dir input in the plugin settings).
GitHub branch called gh-pages to store the published charts.
In your repo, go to Settings/Pages. Change the Source Branch to gh-pages.
Create a .drone.yml file in your root directory. Pipelines examples are available below. For more information, reference the Drone CI Help Documentation for Pipeline Overview

Will try To-Do as suggested
simonfelding @.***> schrieb am Mi., 3. Apr. 2024, 10:28:

I suggested a helm release action here
https://github.com/hurzelpurzel/system-upgrade-controller/pull/1/files
But it requires some additional setup by the owners.
From the documentation
https://github.com/otwld/drone-chart-releaser-github-pages:
Pre-requisites
One of these confuguration
A GitHub repo containing a single chart in root directory (Chart.yaml)
A directory with your Helm charts (default is a folder named /charts, if
you want to maintain your charts in a different directory, you must include
a settings.charts_dir input in the plugin settings).
GitHub branch called gh-pages to store the published charts.
In your repo, go to Settings/Pages. Change the Source Branch to gh-pages.
Create a .drone.yml file in your root directory. Pipelines examples
https://github.com/otwld/drone-chart-releaser-github-pages#example-pipeline
are available below. For more information, reference the Drone CI Help
Documentation for Pipeline Overview
https://docs.drone.io/pipeline/overview/
—
Reply to this email directly, view it on GitHub
https://github.com/rancher/system-upgrade-controller/pull/248#issuecomment-2033901652,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADACKDTNHJMT6ZCJOIQ5JE3Y3O4UDAVCNFSM6AAAAAAZ5VNRGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTHEYDCNRVGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Hugo: Add missing css variables

Use css variables everywhere so they can be easily overwritten when we want a dark theme
Use same way of using variables everywhere
Add missing imports & mixin
Add defaults for variables in case variables are not set or coming from outside current component
Change hover state colors of blue button because difference between normal and hover state was too little

For: https://linear.app/usmedia/issue/CUE-130

@JorindeUsMedia please can you rebase this one more time?

Thanks @JorindeUsMedia - I definitely don't fully grok all the CSS stuff, but the commit message made it easier to understand what you're up to here!
Importing into Gerrit now.

@myitcv Rebased and fixed the conflicts

Closed via ccba4785e030ea701f57658a811bc6723f6f843d


Setting device mode

Is your feature request related to a problem? Please describe.
I have a TV backlight strip. I'd like to be able to change between solid color and video (sync to screen) modes, but Govee does not currently provide a field for this in their official API.
Describe the solution you'd like
I contacted Govee to see if they'd be willing to add this but they said no:

I am sorry that we do not have any plans to release the scences and modes now.
So it could not support mode control through API.
Your udnerstanding is highly appreciated.

I figured it wouldn't hurt if you could reach out as well since you have ~500 users 😛.
Describe alternatives you've considered
Sniffing Bluetooth traffic and just replaying the mode-setting packet.
Additional context
Might be related to #36.

@codetheweb  I don't think this is done via BLE, I wanted to do this for a H6003 and that should use only WiFi.
Another approach could be to implement this integration to replicate the functions of the app. As we can find at https://govee-api.readthedocs.io/en/latest/usage.html
            if isinstance(dev, device.GoveeRgbLight):
                # Save initial color
                color_backup = dev.color

                # Set color temperature to 2100 kelvin (warm white)
                dev.color_temperature = 2100

                # Wait a second
                time.sleep(1)

                # Set color to green
                dev.color = colour.Color('green')

                # Wait a second
                time.sleep(1)

                # Set color to red
                dev.color = (255, 0, 0)

                # Wait a second
                time.sleep(1)

                # Set color to dodgerblue
                dev.color = colour.Color('dodgerblue')

                # Wait a second
                time.sleep(1)

                # Restore color
                if color_backup:
                    dev.color = color_backup

Maybe this could work like this:
1: create custom DIY, using simple dropdowns/text fields for colors and wait time
2: test the DIY
3: save the DIY with an ID
At this point, this could become a trigger where instead of setting the color on the lamp, HA runs the custom DIY

I'm not entirely clear on what you're saying but I don't think you can set scenes from the API.
I got it to work by replaying Bluetooth packets but it's a bit flaky.

Have you tried with a WIFI light bulb? https://us.govee.com/products/wi-fi-led-bulb
It doesn't come with Bluetooth, therefore it must work via WiFi and the API will for sure send some packets to it. If you can suggest me a packet sniffer I could use maybe I can try to help

I unfortunately don't have a bulb to test with.
I suspect that the Govee API that this project uses is a sanitized subset of the full API the app uses, so I would be surprised if it was possible to set the mode / scene on that bulb with the current API.

I checked the official documentation at https://govee-public.s3.amazonaws.com/developer-docs/GoveeAPIReference.pdf and it seems that officially it is not supported... so @codetheweb you are right.
What drives me mad is that Alexa can set the scene from its Govee skill, hence it is possible to achieve; any idea if we can read the skill code?

I am interesting for this option too.

Hello guys,
someone tried to sniff traffic with Charles ?
I will receive my govee ambilight in the next few days and try to check the govee app API. If Alexa works, there have to be an endpoint for this.

@Dielee I tried rieaching out to them but the best I got was a simple I have passed along your suggestion to the tech team. which 3 days afterwards resulted in a simple customer service survey...
Since then (October 11th), the api reference hasn't been updated.
I guess packet sniffing is an option we should consider; did you say Charles is the software we should refer to?

Yes, this would be possible with charles. If they are not using certificate pinning, it would be quiet easy. My govee immersion light arrives in the next few days. I will dig into their App API then!

So, checked the app with carles.. First, they do not use certificate pinning, point for us!
But... All changes (Brightness, Light mode, ...) are not captured with charles. Maybe they are using another protocol.
Im sure it's not HTTP or HTTPS. Maybe WS....

maybe with something like this? https://blog.nviso.eu/2020/07/06/introducing-ioxy-an-open-source-mqtt-intercepting-proxy/?amp
also interested in this, every time i turn it on via homekit > hass > govee it turns it to a solid color instead of video sync.. pointless

Yes, I found this too, but don't know two things:

How to route mqtts traffic through ioxy, as there is now option to set an proxy fpr mqtts connections
How to get SSL/TLS Cert from groovys https server, as this is required for mqtts connections

Maybe someone can help here!

If anyone is interested in looking into this, the Homebridge Govee plugin supports setting scene/music/DIY modes. It would be great if that was supported in this integration too.

I found a substitute solution. It isn't perfect but it's better than nothing. I tried to make reverse engineering of the use-case with aws-iot-device-sdk-js from Homebridge Govee plugin but it was too convoluted for me and it was taking too much time.
Solution 1 - No Home Assistant Cloud
First, I decided to use alexa_media_player to change between music and video modes and that solution is fine if you don't use Home Assistant Cloud - execution takes between 3 and 4 seconds - sometimes it was taking a little bit longer in my case.
Video mode:
service: media_player.play_media
target:
  entity_id: media_player.this_device_2
data:
  media_content_type: custom
  media_content_id: set dreamview p1 to vivid

Vivid music mode:
service: media_player.play_media
target:
  entity_id: media_player.this_device_2
data:
  media_content_type: custom
  media_content_id: set dreamview p1 to vivid

Solution 2 - No Home Assistant Cloud
After that, I found out I can use Home Assistant Cloud integration for Alexa and routines in the Alexa app:

Create a helper e.g. input_boolean.music_video_switch_living_room
Define a binary sensor in your configuration .yaml file:

template:
  - binary_sensor:
      - name: "music_video_switch_living_room_alexa"
        state: '{{ is_state("input_boolean.music_video_switch_living_room","on") }}'
        device_class: 'door'

Expose that music_video_switch_living_room_alexa binary sensor via Home Assistant Cloud
Now you should see that sensor in the Alexa app. Add routines for close and open states for the added sensor
Call the input_boolean services (turn_on and turn_off) to switch between modes:

service: input_boolean.turn_on
data: {}
target:
  entity_id: input_boolean.music_video_switch_living_room

The upside of that solution is that it i's much faster because execution takes around 2 seconds.

I’ve been using Alexa Media Player myself as a solution. The delay is definitely not ideal.
It is possible to directly run routines rather than simulating a voice command by using media_content_type: routine. I believe that somewhat improves the speed.
Your second solution also applies to manually setup Alexa integration and probably emulated hue as well.
The release notes of 2022.7 mentions “You can now trigger Alexa routines from switches, toggles, and buttons without the need to wrap them into a binary template sensor first”, but I haven’t been able to get that to work myself.

I found a substitute solution. It isn't perfect but it's better than nothing. I tried to make reverse engineering of the use-case with aws-iot-device-sdk-js from Homebridge Govee plugin but it was too convoluted for me and it was taking too much time.
Solution 1 - No Home Assistant Cloud
First, I decided to use alexa_media_player to change between music and video modes and that solution is fine if you don't use Home Assistant Cloud - execution takes between 3 and 4 seconds - sometimes it was taking a little bit longer in my case.
Video mode:
service: media_player.play_media
target:
  entity_id: media_player.this_device_2
data:
  media_content_type: custom
  media_content_id: set dreamview p1 to vivid

Vivid music mode:
service: media_player.play_media
target:
  entity_id: media_player.this_device_2
data:
  media_content_type: custom
  media_content_id: set dreamview p1 to vivid

Solution 2 - Home Assistant Cloud
After that, I found out I can use Home Assistant Cloud integration for Alexa and routines in the Alexa app:

Create a helper e.g. input_boolean.music_video_switch_living_room
Define a binary sensor in your configuration .yaml file:

template:
  - binary_sensor:
      - name: "music_video_switch_living_room_alexa"
        state: '{{ is_state("input_boolean.music_video_switch_living_room","on") }}'
        device_class: 'door'

Expose that music_video_switch_living_room_alexa binary sensor via Home Assistant Cloud
Now you should see that sensor in the Alexa app. Add routines for close and open states for the added sensor
Call the input_boolean services (turn_on and turn_off) to switch between modes:

service: input_boolean.turn_on
data: {}
target:
  entity_id: input_boolean.music_video_switch_living_room

The upside of that solution is that it is much faster because execution takes around 2 seconds.

Thanks for the info. I've been trying to accomplish this, and I've followed your instructions (Option 2), and although the helper is now visible in the Alexa app, it only shows me info about the device, it doesn't give me on/off toggles. If that makes sense. Not sure if I'm missing something.
I was sure to exclude and expose the entity just be on the safe side, but no luck.

it only shows me info about the device, it doesn't give me on/off toggles

You should be able to use the device as a routine trigger. I forgot exactly how input booleans are exposed to Alexa, but I use input buttons. After exposing the buttons, I can choose to trigger a routine when the button "detects a person" in the Alexa app, then set the action to any Govee scene.
This includes any custom/"DIY" modes which can be exposed to Alexa through the "Command > Tap-to-run" section in the Govee app.

@coun7zero recently I found a 3th option to toggle between color and video mode. It's by making use in the in app automations of govee.
• In your govee app to got command
• add an auto run command and make it trigger on "turn on" and give it a real time act of "turn on DreamView"
Movie mode:
• Simply turn the T1 on via the api integration and the govee automation will automatically switch the lightstrip to Dreamview(movie) mode.
Color mode
• Turn the T1 on via the api integration, wait a couple of seconds (5 in my case) and then again via the API integration push a light.turn_on but this time also provide the desired color. This will again override the Movie mode and put it into color mode.
Want it to turn in to Movie mode again ? Simply turn the lightstrip off and on (via the integration) and the process starts all over again.

Hello, I did some messing around with Postman. Applogies if there is some sort of standards for posting but i hope that this can help.
I am able to switch to video mode from any mode by creating snapshots within the Govee app and then recalling the snapshot via postman. I can create a cur script and call it that way also within Hass.io
I hope this helps or  maybe steer in a direction :)
Interrogate the device to get the snapshot enum
GET /router/api/v1/user/devices HTTP/1.1
Host: openapi.api.govee.com
Content-Type: application/json
Govee-API-Key: XXXX

Search in the response devices.capabilities.dynamic_scene for snapshot and use the value matching the snapshot name you saved e.g.
 {
    "type": "devices.capabilities.dynamic_scene",
    "instance": "snapshot",
    "parameters":
    {
        "dataType": "ENUM",
        "options":
        [
            {
                "name": "TV tracking",
                "value": 356654
            },
            {
                "name": "chill",
                "value": 467874
            },
            {
                "name": "relax tv",
                "value": 467875
            },
            {
                "name": "default day",
                "value": 1050228
            }
        ]
    }
}

And then send the request:
POST /router/api/v1/device/control HTTP/1.1
Host: openapi.api.govee.com
Content-Type: application/json
Govee-API-Key: XXXX
Content-Length: 233

{
  "requestId": "1",
  "payload": {
    "sku": "H605C",
    "device": "XA:XA:XA:XA:XA:XA:XA:XA",
    "capability": {
      "type": "devices.capabilities.dynamic_scene",
      "instance": "snapshot",
      "value": 356654
    }
  }
}


And expression inferrs wrong type.

TypeScript Version:  3.1.0-dev.201xxxxx

Search Terms:
Code
let b: boolean;
let s: string;

let x = b && s;

Expected behavior:
The inferred type of x is boolean | string;
Actual behavior:
The inferred type of x is string;
Playground Link:
https://www.typescriptlang.org/play/#src=let b%3A boolean%3B
let s%3A string%3B

let x %3D b %26%26 s%3B
Related Issues:

Since the type of x seems to take the value of b into account, should the type even be string?
let b: boolean;
let s: string;

let x1 = b && s; // string, (which should it be? x1 is undefined)

b = true;
let x2 = b && s; // string

b = false;
let x3 = b && s; // boolean

With strictNullChecks, you will get string | boolean.

@ahejlsberg in non-SNC we should really be keeping the left operand type in the result when it's a primitive

We've discussed fixing this before, but decided against it because of the breaking change. Do we feel differently about this now?
In general, if you care about precise types you really should be using --strictNullChecks (where we type this correctly).

I don't recall that discussion. We could check RWC for impact - seems like we'd reveal a ton of subtle bugs

RWC results were nothing but false positives. Doesn't seem worth breaking at this point.


Fix manylinux packages

Motivation for this change
This makes sure that the lib output is used whenever available. Working on manylinux support for poetry2nix I noticed problems with missing libraries and realized this was because some of the buildInputs where the bin outputs and thus patching via autoPatchelfHook failed.
Things done
Applying lib.getLib` to make sure we get the library outputs as buildInputs. I tested that it actually works with my WIP poetry2nix code.

Good improvement, thanks. The let ... in are not needed though.

Thanks for the fast feedback @FRidh

The let ... in are not needed though.

Sure. Fine with me either way. Just removed them.


Fixes the latest tag being applied to nightly/dev images

Title

Fixes the latest tag being applied to nightly/dev images
Description

Fixes the latest tag being applied to nightly/dev images.
Related Issue

Fixes #1724
Motivation and Context

I broke it.
How Has This Been Tested?

Test run now only applies the nightly tag:

Screenshots (if appropriate)
Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[x] I have read the CONTRIBUTING document
[x] I have read the  CORE VALUES document
[x] I have added tests to cover my changes
[x] All new and existing tests passed

I've also gone ahead and added a handy GUI checkbox when manually firing off a job to define whether you want a production or nightly build, mainly so its easy to fix the current live latest build on DockerHub.
With the box checked, it correctly uses the master branch and also sets the latest tag, along with a semver tag if one is available (this only appears on a tag or publish event as the ref).
With the box unchecked, it correctly uses the dev branch and also sets the only tag to be nightly-.

Maybe instead of creating new nightly tags just overwrite the old one, because there is no real need to keep the old dev builds.

Maybe instead of creating new nightly tags just overwrite the old one, because there is no real need to keep the old dev builds.

Just pushed that change, now generates just a static nightly tag.


Design News section as event section

Issue Type:
[x] Bug Report
[  ]  Feature Request
[  ] Documentaion
This section is news section

This is event section

I will like to work on this !

roger that


[Docs]: “How to Use Notion as a Database on Appsmith” guide

Is there an existing issue for this?

[X] I have searched the existing issues

Release Number or Date
NA
Documentation Link
https://docs.appsmith.com/learning-and-resources/how-to-guides/use-notion-as-database-on-appsmith
Discord/slack/intercom Link
No response
Describe the problem and improvement.
There are a few inaccuracies in the guide:

Tab label in Notion's UI has changed, Integrations is now called Connections. This is both outdated on a screenshot and in guide's text.
The type of request that is needed to query Notion's database API is POST, screenshot falsely indicate that it's GET
It is worth noting that the created “connection” in Notion needs to be added to the Notion page containing the database (top-right three dots menu → Connections → Add connections)
Notion's API version has changed to 2022-06-28 (ref)

Hiding this page on the docs for now as these will move to the community portal


Once the user scrolled all the way to the bottom, he can't scroll up anymore (BottomSheet)

Instead he drags the BottomSheet down...

Cannot reproduce this problem. Please contact me in private and show me how to reproduce this.

Will not be resolved. Hitbox is bad but it is doable.


build: Enable building binary only on macos

Current config only allows building local binaries on Linux machines so
adding config to allow building binaries on macos without changing the
release config (and hence still only releasing linux binaries as required).

Yes it does always run in a container, but I found it useful to have the binary locally to check flags when I was adding feature gates.
At the same time, if you run make build-snapshot on macos without this pr then literally nothing builds, not the binary, not the image, nada. This pr fixes that as well so a native darwin binary will be built plus the Linux container with relevant arch.


Remove lifetime bounds in higher-ranked lifetimes

Those bounds are ignored by the compiler, and will trigger an error once https://github.com/rust-lang/rust/pull/48326 lands. According to crater, this is the only crate using these bounds. This patch should make the crate work on nightly again.
However, I have been unable to compile the crate even with nightly 2018-02-25, which does not include the change mentioned above. So, I couldn't compile-test this PR.

This change is

Thanks!
Bors r+

We'll see if it builds on CI :)

Looks like it works there atleast

The build failure was caused by https://github.com/rust-lang/rust/issues/48551. That's fixed, but my branch where I develop https://github.com/rust-lang/rust/pull/48326 does not include the fix yet, so I can't test whether this will keep working when my patch lands. However, these are all the occurrences of higher-ranked lifetime bounds that crater found.
Thanks for merging so quickly. :)  Please release a new minor version of the create before the patch hits stable (which will take ~9 weeks).

We will probably release a new major version before that (we have some breaking changes).

AFAIK a new minor version with the fix would be necessary for reverse dependencies that will just do cargo update -- they won't get the new major version automatically, so they would fail to build.

True, I'll get that out tonight.

I compiled rustc with my patch merged into master, and can confirm that this can build current rhusics master (while it fails on the version without my patch, as expected).
So, looking good :)

The breaking changes had not been merged to master yet, so this was easier than I thought it would :) Anyways, new minors have been released.


No R.swift file after migration

I follow your video for migration from 6 to 7 version, from CocaPods to SPM and after all steps build does not run successfully and I can not see file 'R.swift' in my project. Any idea how to solve this?
Thanks

With the modern Build Tool Plug-in, the generated output file R.generated.swift no longer is located in your project directory, but instead in Derived Data.
Whenever you build your project, the file is first generated, and the rest of your code can refer to the generated code.
Are you seeing an error? What error are you seeing when building after migration?

A lot of errors referencing to R.swift:

Make sure to do a clean build. And check the build log to see if the build step actually ran. If the R.swift build step doesn't run, the rest of your code also won't compile.

Hm for some reason after couple of times clean and build I manage to build successfully. Thanks


Reach core team consensus on breaking pieces of framework into modules

https://github.com/silverstripe/silverstripe-framework/issues/5288 (and others) talk about splitting modules out of framework, but:

We don't know to what level we want to split things
We don't know what impacts this will introduce (to performance, etc)
We specifically haven't agreed on whether versioned & campaignadmin should be in the same module.

We need core team agreement before moving forward.

See https://github.com/silverstripe/silverstripe-framework/issues/5640
we've kind of already agreed on most of the modules, as per https://github.com/silverstripe/silverstripe-framework/issues/5289 and https://github.com/silverstripe/silverstripe-framework/issues/5288.
We need to write up the final list of modules for framework and get this closed. It looks like this will be:

asset-admin
asset-backend
versioning
campaign-admin
admin

Have I missed any?

The only RFC yet to be voted on is https://github.com/silverstripe/silverstripe-framework/issues/5641. I think that we can close this issue off on the basis that the other 3 tickets (#5641, #5289, and #5288) cover all the work to be done.
There are other modules that could be split, such as ORM, and forms, but I don't think they're as much of a priority, and can wait, possibly until SS5.


[Bug]: When using forge build, forge test, result is always the same and weirdly not compiling the changes

Describe the bug
This is my function, the compiler should throw error at it, as it previously was :

This is the output of forge test :

When I run forge test -vvvvv result is the same as the image above, previously it was not! I have a couple of tests written that were working before.
To Reproduce

write any code
forge test
does not compile properly

Expected behavior
Compiling and showing error traces
Additional context
Already did cargo update on the foundry folder

this could be windows paths related
could you please share the verbose output of the commands prefixed with RUST_LOG=ethers=trace
like RUST_LOG=ethers=trace forge test

my forge config `[default]
auto_detect_solc = true
block_base_fee_per_gas = 0
block_coinbase = '0x0000000000000000000000000000000000000000'
block_difficulty = 0
block_number = 1
block_timestamp = 1
bytecode_hash = 'ipfs'
cache = true
cache_path = 'cache'
evm_version = 'london'
extra_output = []
extra_output_files = []
ffi = false
force = false
fuzz_max_global_rejects = 65536
fuzz_max_local_rejects = 1024
fuzz_runs = 256
gas_limit =<PHONE_NUMBER>854775807
gas_price = 0
gas_reports = ['*']
ignored_error_codes = [1878]
initial_balance = '0xffffffffffffffffffffffff'
libraries = []
libs = ['lib']
memory_limit = 33554432
names = false
no_storage_caching = false
offline = false
optimizer = true
optimizer_runs = 200
out = 'out'
remappings = [
'@openzeppelin/=lib/openzeppelin-contracts/',
'ds-test/=lib\forge-std\lib\ds-test\src/',
'forge-std/=lib\forge-std\src/',
'openzeppelin-contracts/=lib\openzeppelin-contracts/',
]
sender = '0x00a329c0648769a73afac7f9381e08fb43dbea72'
sizes = false
sparse_mode = false
src = 'src'
test = 'test'
tx_origin = '0x00a329c0648769a73afac7f9381e08fb43dbea72'
verbosity = 0
via_ir = false
[default.rpc_storage_caching]
chains = 'all'
endpoints = 'all'`

I fixed this issue, by using Ubuntu instead of Windows, lol


Ranges and slices with inequalities such as [a<..<b]

Fixes #999 by allowing inequalities in .. ranges/slices, inspired by Swift's a..<b half-open range operator:

Each endpoint can be marked < or <= (or the Unicode equivalent, ≤) for increasing loops, or > or >=/≥ for decreasing loops.
Inclusive (as in <= or >=) is the default behavior, but it forces a loop order, which can be useful.
Slices forbid >, as we don't have a nice way to reverse slice (when dealing with strings).

Because we can now specify direction, the ranges and loops can be a bit more efficient (as well as more consistent/reliable). Compare the old ...:
[0...array#]
for i of [0...array#]
↓↓↓
((s, e) => {
  let step = e > s ? 1 : -1;
  return Array.from(
    { length: Math.abs(e - s) },
    (_, i) => s + i * step,
  );
})(0, array.length);
for (
  let end = array.length, i1 = 0, asc = 0 <= end;
  asc ? i1 < end : i1 > end;
  asc ? ++i1 : --i1
) {
  const i = i1;
}

versus the new ..<:
[0..<array#]
for i of [0..<array#]
↓↓↓
((s) =>
  Array.from(
    { length: array.length - s },
    (_, i) => s + i,
  ))(0);
for (
  let end = array.length, i1 = 0;
  i1 < end;
  ++i1
) {
  const i = i1;
}

Thanks, looks like a nice addition!


TextExtractor selection does not close when selection area containing no text

Microsoft PowerToys version
0.62.0
Running as admin

[X] Yes

Area(s) with issue?
TextExtractor
Steps to reproduce

Trigger TextExtractor with win shift T
Screen darkens to select area for text recognition
Select an area on your screen which does not contain text

You could open empty text file (white background)

✔ Expected Behavior
The selection closes and no text is copied to my clipboard
❌ Actual Behavior
The selection stays open until I find and select something on my screen containing text.
Other Software
No response

Maybe you can add a new option to change the behavior here

This is by design. It can be closed either by pressing ESC key or right-click and then selecting Cancel option

This is by design. It can be closed either by pressing ESC key or right-click and then selecting Cancel option

Other applications such as Microsoft OneNote have created an expectation that after the user selects a region, the gray overlay goes away automatically. To see this behavior, install Microsoft OneNote onto Windows Vista, 7, or 8 (not Windows 10), press WIN+SHIFT+S, and select a region.


"Failed to lex input remainder" upon save of all .clar

I decided to try to use the VSCode Extension.
The syntax highlighting seems to work fine, however ALL(if created by VScode) clarity contracts yield Errors Detected upon saving.
All of them indicate:
"Failed to lex input remainder"
I'm running the latest version of VSCode and Extension.
I first noticed this as I was simply trying to review the hey.clar and hey-token.clar per https://github.com/blockstack/heystack/tree/main/contracts
After having no luck I tested other src per contracts found on chain and they even yield the same error upon local save.
OS: Win10

My Testing:
When I use VSCode to create the .clar files, all files upon save throw Error detected in VSCode error log say "Failed to lex input remainder".
When I use my Dapparatus and write new .clar files with ASCII encoding, I get more specific errors reported back by VSCode error log when subsequently evaluating them and saving them again per VSCode.
When I use my Dapparatus to evaluate (per embedded clarity-cli) the various files I get back:

files created by Vscode as .clar files all return Unexpected end of JSON input
files created by Dapparatus as .clar files all return more robust errors with analysis.

Note: I use a exe node to pass check filename.clar  into the clarity-cli.exe run time and report back errors.
I think this relates to:  #42

Hmmm this might not be ALL files after all.

For windows users, you should make sure that your VSCode is configured for using LF, instead of CRLF.