SchemaUpdateMode=synchronize failed with code 422. Reason: Specified part does not exist in the package.

Press F5 to sync to my local database. Had been working.
now get this error:
SchemaUpdateMode=synchronize failed with code 422. Reason: Specified part does not exist in the package.
output has these lines:
End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Dynamics.Nav.EditorServices.Protocol.RequestRegistry.d__6.MoveNext() in C:\Agent_work\41\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\Endpoints\RequestRegistry.cs:line 59
To Reproduce
Steps and/or AL code to reproduce the behavior: Problem is I don't know where to look from the error message

Go to '...' I have attached my last 3 changed files since my last successful update.
I did get an invalid table extension number first f=which was already in use. I changed it and then received the above error.

Expected behavior
A clear and concise description of what you expected to happen. expected it to publish
Screenshots
If applicable, add screenshots to help explain your problem.
Versions:

AL Langauge: 0.12.17720

Business Central:  (NAV 2018 CU4) on premise

This GitHub repository is dedicated to handling issues and feedback for the latest Developer Preview releases of the AL development tools for Dynamics 365 Business Central.
If you can reproduce the problem on the latest Business Central Developer preview version we will be happy to look further into it. Otherwise please contact the regular support channel.
You can open Support Request to CSS through PartnerSource portal or contact your Service Account Manager (SAM) in the local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also step by step direct you how to open a support request or how to get credentials if this is the first time for you / your company.
For more details please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://github.com/Microsoft/AL/wiki/Frequently-Asked-Questions#i-found-an-issue-on-nav-2018-what-do-i-do


Dynamodb: nested list_append

The list_append operation was already supported - this PR adds the option to use the list_append on a nested list, i.e. a list inside a map.

Coverage increased (+0.03%) to 93.792% when pulling 21a1d4d6046c256cbccc2819e0873c15091a44cb on bblommers:feature/dynamodb_nested_list_append into 502957f1f9560cb6dff75271e6812498f4ff7bba on spulec:master.


Can't perform a React state update when adding a second scene to SceneMap

Current behaviour
I get a warning Can't perform a React state update... when adding a second scene to SceneMap. If I only have one property in the SceneMap, the error doesn't appear. I have reduced my components down to <Text>s and the warning still appears.
Expected behaviour
Not to see the warning.
Code sample
https://snack.expo.io/votgR9yPg
Screenshots (if applicable)

What have you tried
Replaced my original components with <Text>s hoping that would help me debug where the bug was. Did not expect to see the warning when i was only rendering a <Text> as the tab component.
Your Environment

software
version

ios or android
ios simulator

react-native
0.62.0

react-native-tab-view
2.14.4

react-native-gesture-handler
1.5.2

react-native-reanimated
1.7.1

node
12.18.0 (Mac)

npm or yarn
npm

Updated both packages and the issue still exists

Don't create components in render.

I replaced my code with the example in the README, and I still get the warning.
import * as React from "react";
import { Dimensions, StyleSheet, Text, View } from "react-native";
import { SceneMap, TabView } from "react-native-tab-view";

const FirstRoute = () => <Text>One</Text>;

const SecondRoute = () => <Text>Two</Text>;

const initialLayout = { width: Dimensions.get("window").width };

export default function Tabs() {
  const [index, setIndex] = React.useState(0);
  const [routes] = React.useState([
    { key: "first", title: "First" },
    { key: "second", title: "Second" }
  ]);

  const renderScene = SceneMap({
    first: FirstRoute,
    second: SecondRoute
  });

  return (
    <TabView
      navigationState={{ index, routes }}
      renderScene={renderScene}
      onIndexChange={setIndex}
      initialLayout={initialLayout}
    />
  );
}

@satya164 any other ideas of what might be causing it?

Same here.

Same issue

Same here.

Same issue


Core slot incompatibility between sites and jobs: Handle the issue better and make error code more meaningful

Impact of the new feature
Debugging the issues in case of core slot incompatibility between sites and jobs
Is your feature request related to a problem? Please describe.
This is discussed in SI meeting: Recently, we have seen that many prod jobs were failed at T2_TR_METU site due to:
JobKilled (Exit code: 71305)
The job was killed by the WMAgent for using too much wallclock time (WMAgent) Job status was Pending.

In fact, the problem was that the jobs were multicore while the site only has single slots and therefore jobs could not find slots to run. It took really days to figure out the issue. If the error code and its explanation were more meaningful, we would have spotted the issue much earlier.
An example: https://cms-unified.web.cern.ch/cms-unified/report/pdmvserv_task_B2G-RunIISummer16NanoAODv7-03193__v1_T_210120_171738_2342
Describe the solution you'd like
I see two steps to move forward:

Those jobs should fail immediately instead of failing with timeouts. Or better we should redirect those jobs to more suitable sites.
Make the error code more meaningful, so that people can understand the problem right away and act accordingly.

Describe alternatives you've considered
None
Additional context
Any comment is much appreciated

Hasan, if I understand your request correctly, you're basically asking WMAgents to be aware of which kind of resources are provided in a given site, and which kind of pilots is it set to use.
Even though it's a good idea, I'm against of adding resource awareness logic inside WMAgent, changing the behaviour of job creation and submission. I'd rather rely on a proper workflow assignment, and avoid having such complexity in the agent.
This also means the system cannot give you a more meaningful error message.
As discussed in that private thread with Antonio and others, there is a push to move the final T2 sites to 8-core pilots. With that in place, there wouldn't be too much value with this feature as well.
Does it make sense?

Hi Alan, sure, I'm aware that this introduces a new complexity in the agent and I am also aware that this is not needed with the new improvements on the T2 sites. My point was to improve the system such that it has better error handling in case somehow this happens. If you think that what we will gain with this feature is not worthwhile compared to the necessary effort needed to provide it, it's totally fine with me to cancel this feature request.

Hasan, I'm afraid I have to say the effort of such feature (and maintenance) isn't going to pay off. Especially because there are efforts from other groups to avoid this from happening again.

Hi Alan, that's perfectly reasonable. Yesterday, in the SI meeting, we agreed to check if this is possible. Good to have a understanding on the necessary effort for this feature. Feel free to close the issue.

Thanks Hasan, closing this issue then.


Add x86_64-linux-musl to build matrix

@ianks CI errors just seem to be due to crates not being fetched, I think a retry should fix it.

Good news, x86_64-linux-musl build works! Unfortunately, everything else is broken due to a bundler resolution issue. Not sure why, but unrelated. Good work!


brainstorming rules for components and producers

These rules are up for debate

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Other information:

Convention for naming variables:

observe: the final name in the path or an interpretation of that value:
bam = observe.something.bam
title = observe.article.title
isFinished = observe.article.finishedWritingInArticle

update: the prefix update + the final name in the path or an interpretation of that value:
updateBam = update.something.bam
updateTitle = update.article.title
updateIsFinished = update.article.finishedWritingInArticle

get: the prefix get + the final name in the path or an interpretation of that value:
getBam = get.something.bam
getTitle = get.article.title
getIsFinished = get.article.finishedWritingInArticle

_ for pseudo-private props:
_viewId
_producerId
_now

Example:
const A: producer = ({
  foo = observe.foo,
  updateFoo = update.foo,
  getFoo = get.foo
}) => {
  ...
}


Add multiline textboxes

See discussion in #67

There's something broken about dragging to select spans, but I can't figure out what's up with it. @geom3trik can you take a look?

This is now a PR for multiline textboxes and labels in addition to the textbox scrolling stuff.
I am happy with none of this code. I don't know whether this is because I didn't do a good job, because text layout stuff is inherently silly, because we're trying to push morphorm past its intended boundaries, or a little bit of all of them.
This requires my forks of both femtovg and morphorm. None of this code is meant to merge just yet, I just wanted some feedback.

I am happy with none of this code.

After a quick glance at the code I really don't think it's that bad at all. Is there a specific part that you're unhappy with? That being said I haven't looked at what changes you've had to make to morphorm to get this all to work.
I'll do a proper line-by-line review of the code later today but I managed to run the textbox example and have a play with it and overall it works, but here are some bugs I noticed, mostly to do with text transforms I think:

Caret dissapears when at end of text when text is left aligned
Caret dissapears at start of text when text is center or right aligned
Caret shifts text by 1 pixel when moved to the start and text is left aligned
Caret isn't rounded to pixel grid and so sometimes blurs when moving
Cursor icon has stopped working when hovering textbox
Right align of text doesn't seem to work when the text is longer than the textbox
Clicking in a textbox transforms the text but clicking out of the textbox leaves the text transformed
The selection is still visible when the textbox is no longer being edited
Moving the caret through text which has overflowed when right and center aligned causes the text to transform by one character
Text selection with the mouse only works when hovering on the textbox
Caret position is incorrect when moving from across a soft break. The caret should move to the end of the line and then to the beginning of the next line but these two cases have the same index. This is usually solved by introdicing something called affinity, which is a bool to determine where the caret should be in these two cases.
The single line textboxes can be forced into multiline by pressing the enter key in a multiline textbox which is bound to the same data.
On a similar note, adding text into one of the multiline textboxes such that the text in the single-line textboxes overflows causes the text to jitter and not transform correctly.

I think I could probably fix a few of these if you want some help with it.
The test example produced the following:

So this might be an error on my side because I had to guess which branches of your femtovg and morphorm forks were the ones I needed. I guessed feat/word_breaking for femtovg, and feat/secondary_content_size for morphorm.

I believe I've fixed everything that is important to fix for first release.

The single line textboxes can be forced into multiline by pressing the enter key in a multiline textbox which is bound to the same data.

I don't know what better behavior would be! what should a single line textbox do when bound to multiline data? This is the best answer I have...

Alright, I'm sick to death of working on text boxes. I'll open issues for the last few things you mentioned on discord, and then I think we should merge this so we can move towards first release.


[Program]: Write a Rust program to print diamond pattern

Description
Write a Rust program to print diamond pattern
Input  : 5

Output :
    *
   ***
  *****
 *******
*********
 *******
  *****
   ***
    *

How to contribute

Save the solution in program/program/print-diamond-pattern/program/print_diamond_pattern.rs file

!assign


Add support for Windows Subsystem For Android.

This is not so much an issue, more an enhancement.
Currently it is possible to install APK files on the latest WSA preview version. Upon installing FTC Driver Station, it breifly flashes the window but then closes. This could be a WSA limitation, but seems to be because of an earlier issue involving the way Driver Station handles devices without USB support. That is however, just an educated guess. WSA is just an emulation of android.
Some things to note:

WSA is running Android 11
At the time of writing I have only tested this on WSA version RD2A.210905.003
Windows Build is 22483.rs_prerelease.211015-1431

This would be a useful addition to FTC because then we wouldn't need to buy phones and other acessories for the phones and just run it straight off the laptop.
Relevant Information:
https://docs.microsoft.com/en-us/windows/android/wsa/
Thanks,
Levi.

Currently there are two pairing methods, "Wi-Fi Direct" and "Control Hub".
I suggest a third pairing method, say "TCP" or "Debug", meaning a TCP/adb connection from the Driver Station to the Robot Controller.
A new "TCP" pairing method might be an easier and more stable path than trying to get P2P working in WSA or other Virtual Machines.

It would actually need to be UDP. The RC/DS communication uses UDP.

I think https://acmerobotics.github.io/ftc-dashboard/ is probably a better solution for most computer users, it provides more features too.

I think https://acmerobotics.github.io/ftc-dashboard/ is probably a better solution for most computer users, it provides more features too.

Yeah, it's only missing the ability to do very peripheral things like drive the robot 🤣

You can use gamepads with ftc-dashboard and run your opmodes.   While it is
not the same latency, it is typically pretty good for testing subsystems.
--Alan
On Tue, Nov 29, 2022 at 12:12 PM Kevin Frei @.***>
wrote:

I think https://acmerobotics.github.io/ftc-dashboard/ is probably a
better solution for most computer users, it provides more features too.
Yeah, it's only missing the ability to do very peripheral things like
drive the robot 🤣
—
Reply to this email directly, view it on GitHub
https://github.com/FIRST-Tech-Challenge/FtcRobotController/issues/214#issuecomment-1330998155,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAF3Y77FSN2IY4ZD74E5WY3WKY2P5ANCNFSM5G4DOJYQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>


feature: Implement Clickable Logo/Header Link for Homepage Navigation

Basic Description
Add the functionality for users to navigate back to the homepage by clicking on the logo or header. This standard feature improves usability and provides intuitive navigation. Implementing this enhancement will enhance the overall user experience of the website.
Problem :
there is no way of going back to the page showing all slides together after clicking one of the categories of the nav bar shown below.

Solution :
Make the Daily Code header clickable and on clicking link it to the HomePage

Basic Description
Add the functionality for users to navigate back to the homepage by clicking on the logo or header. This standard feature improves usability and provides intuitive navigation. Implementing this enhancement will enhance the overall user experience of the website.
Problem :
there is no way of going back to the page showing all slides together after clicking one of the categories of the nav bar shown below.

Solution :
Make the Daily Code header clickable and on clicking link it to the HomePage

You can navigate back , you have to click on selected catagory again .

I apologize that I didn't notice this, but don't you think this clickable logo feature is basic for every website and should be implemented.


Add kinetic package for Google Dialogflow ROS wrapper

Please add the dialogflow_ros package for documentation and indexing on ros.org.

re triggering travis...

CI passed :+1:


Dictionary mismatches upon model creation

Linkages are not being created due to match failures. ELCI_1 model.
At generation mix stage (from main.py log):
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for OIL - El Paso Electric Company
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for GAS - Electric Energy, Inc.
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for SOLAR - Florida Municipal Power Pool
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for SOLAR - Idaho Power Company
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for SOLARTHERMAL - Nevada Power Company
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for OTHF - Nevada Power Company
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for OFSL - PJM Interconnection, LLC
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for OTHF - PacifiCorp East
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for GEOTHERMAL - PacifiCorp West
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for BIOMASS - Portland General Electric Company
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for OIL - Public Service Company of New Mexico
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for SOLAR - South Carolina Electric & Gas Company
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for OFSL - Southwest Power Pool
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for SOLAR - Southwestern Power Administration
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for WIND - Southwestern Power Administration
WARNING:generation_mix.py:olcaschema_genmix:Trouble matching dictionary for SOLAR - Western Area Power Administration - Desert
At consumption mix stage (from main.py log):
write consumption mix to dict
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Avista Corporation
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Bonneville Power Administration
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Public Utility District No. 1 of Chelan County
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - California Independent System Operator
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Duke Energy Progress West - Duke Energy Progress West
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Gridforce Energy Management, LLC
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce South - Gridforce South
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Idaho Power Company
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Los Angeles Department of Water and Power
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Nevada Power Company
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for New Smyrna Beach, Utilities Commission of - New Smyrna Beach, Utilities Commission of
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - PacifiCorp West
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Portland General Electric Company
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Puget Sound Energy, Inc.
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Seattle City Light
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Turlock Irrigation District
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - City of Tacoma, Department of Public Utilities, Light Division
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Western Area Power Administration - Upper Great Plains East - Western Area Power Administration - Upper Great Plains East
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - CAISO
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - Northwest
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Duke Energy Progress West - Southeast
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Duke Energy Progress West - US
WARNING:eia_io_trading.py:olca_schema_consumption_mix:Trouble matching dictionary for Gridforce Energy Management, LLC - US
See the attached images showing lack of providers in openLCA processes.
The results is a lack of providers in the JSON-LD export and therefore linkages not properly created in openLCA.

In the case of the requirement for OIL generation in El Paso, no generation process exists.

As for the consumption mix mismatches, there seems to be no generating regions for these. like 'Gridforce Energy Management', and some potential naming issues, like some duplicate name listing in the original data as in 'Western Area Power Administration - Upper Great Plains East - Western Area Power Administration - Upper Great Plains East'

Regarding the generation mixes, these are mostly due to a mismatch in the generation mix calculations vs. creating generation technologies. The generation mix calculation doesn't care whether the power plant burning the oil is an "oil power plant", it just sums up all the oil generation in a balancing authority area (for example). What is most likely happening in this and other cases is that there is no "oil" plant being generated because no power plants in El Paso use >95% oil.

Regarding the missing generators (e.g., El Paso - OIL), I think most of the cases will be similar to the El Paso case. In this case, the plant (FacilityID 50241) got categorized as a natural gas plant (in stewi). In 2016, this plant actually only burned DFO, so the percent generation from the primary fuel category was 0 and as a result, this plant got categorized as MIXED fuel plant and thus aggregated with the rest of the MIXED plants in the El Paso BA. This is what happens on the emission side of things.
When using EIA data for creating the generation mix, the algorithm chooses the primary fuel by choosing the fuel code that provided the most generation. In this case, it's DFO, so the generation mix for El Paso BA includes an input for an OIL generator.
I think these particular cases are pretty marginal. A possible workaround would be to ignore the stewi fuel classifications and calculate them on the fly using the eia923 data.

On consumption mixes.
Gridforce is interesting - it doesn't appear at all in EIA 860, which is the source of all plant BA data. The project listing on their website shows that they have projects across the country. Surveying those plants in EIA860 data, these plants appear to be associated with the BA they're actually connected to? I'm not sure how we can reconcile this outside of hard-coding a fix for this handful of plants. The largest share of power provided by the Gridforce BA is around 2% for the Bonneville Power Administration. All others are less than a fraction of a percent.
The 3 plants associated with New Smyrna don't have any reported emissions or generation in EIA923.
Duke Energy Progress West is linked to a single solar PV project - there's a profile for it in the NETL solar PV data, so I'm not sure why that one's getting dropped. The only BA that uses Duke Energy Progress West is itself.
And lastly, there is also no Western Area Power Administration - Upper Great Plains East in EIA860.

Regarding the missing generators (e.g., El Paso - OIL), I think most of the cases will be similar to the El Paso case. In this case, the plant (FacilityID 50241) got categorized as a natural gas plant (in stewi). In 2016, this plant actually only burned DFO, so the percent generation from the primary fuel category was 0 and as a result, this plant got categorized as MIXED fuel plant and thus aggregated with the rest of the MIXED plants in the El Paso BA. This is what happens on the emission side of things.
When using EIA data for creating the generation mix, the algorithm chooses the primary fuel by choosing the fuel code that provided the most generation. In this case, it's DFO, so the generation mix for El Paso BA includes an input for an OIL generator.
I think these particular cases are pretty marginal. A possible workaround would be to ignore the stewi fuel classifications and calculate them on the fly using the eia923 data.

@jump2conclusionsmatt  I'm surprised this issue is affecting ELCI_1 as reported in #116  because i didn't think the fuel types were eGRID fuel classifications were used .. i thought it was based on the EIA data.
this line in the config file
https://github.com/USEPA/ElectricityLCI/blob/0ffeac3300f435b1d32a110a0c209f505760c1bd/electricitylci/modelconfig/ELCI_1_config.yml#L22]
causes this if statement to be true
https://github.com/USEPA/ElectricityLCI/blob/0ffeac3300f435b1d32a110a0c209f505760c1bd/electricitylci/generation.py#L529
but i guess this only does a replacement when the existing fuel Category is NA

Agreed - maybe "replace_egrid" is a bit vague. I think explicity, we replaced eGRID CO2, SO2, and NOx emissions, and replaced eGrid-based generation mixes. I never really thought to replace the plant designations. Doing that probably takes care of the El Paso - oil.
I would like to try implementing a change to the FuelCategory based on EIA923 data and see how many of these go away. It also makes the replace_egrid option more true.
After that, as discussed, any missing technologies in generation mixes will be replaced with a US average profile for that technology (e.g., MISO-OFSL gets created using a notional US-OFSL).

Based on an initial run, changes in branch issues/77 fix the missing technology mixes. This was done by replacing all plant fuelcategory designations with those from EIA data - which is the same way the generation mix was being created. As of now, there are no warnings at generation_mix about not finding a matching dictionary. There's no need to substitute US profiles at this point. This may still pop up in the future if a generation mix includes a technology that has no emissions.
Issues #121, #124 still persist, along with the unmatched dictionaries when creating consumption mixes.

thanks @jump2conclusionsmatt. I'm wondering how much this is going to effect the data...could be potentially a large amount if the egrid fuel category is not based on the same data or similar approach. Any idea of how many plants end up changing fuel categories with this data change?

Duke Energy Progress West is also a separate issue. There is one solar plant (60880) that had 0 generation in 2016 - resulting in 0 emissions across the board. However because it has 0 generation, it's designated as a MIXED plant, and no generation mix is ever created because of 0 generation. I'm add this plant as a manual deletion. Just documenting here so that I have some place to reference in the yml file.

MIXED plant for Duke Energy Progress West is still being created for some reason. Changed the list of plants to keep to refer only to BAs with generation mixes in the dictionary.
Closing this issue.


Support recent binutils

From version 2.38, binutils default to ISA spec version 20191213. This
means that the csr read/write (csrr*/csrw*) instructions and fence.i
instruction has separated from the I extension, become two standalone
extensions: Zicsr and Zifencei. As the kernel uses those instruction,
this causes the following build failure:
riscv-none-elf-gcc -march=rv32im -mabi=ilp32   -c -o startup.o startup.S
startup.S: Assembler messages:
startup.S:5: Error: unrecognized opcode `csrw mtvec,t0'
startup.S:6: Error: unrecognized opcode `csrrsi zero,mtvec,1'
startup.S:74: Error: unrecognized opcode `csrr t5,mepc'
startup.S:76: Error: unrecognized opcode `csrw mepc,t5'
startup.S:133: Error: unrecognized opcode `csrr t5,mepc'
startup.S:135: Error: unrecognized opcode `csrw mepc,t5'
startup.S:192: Error: unrecognized opcode `csrr t5,mepc'
startup.S:194: Error: unrecognized opcode `csrw mepc,t5'

With #9, recent GNU toolchains which support binutils 2.38+ can reproduce the above issue. Then, I attempted to apply the follow change:
--- a/sw/common/Makefile.common
+++ b/sw/common/Makefile.common
@@ -14,7 +14,7 @@ READELF := $(CROSS_COMPILER)readelf
 ifeq ($(rv32c), 1)
 ARCH    := -march=rv32imac -mabi=ilp32
 else
-ARCH    := -march=rv32im -mabi=ilp32
+ARCH    := -march=rv32im_zicsr -mabi=ilp32
 endif

 CFLAGS  := -O3 -Wall $(ARCH) -nostartfiles -nostdlib

make all can therefore generate RISC-V ELF files. However, the ISA simulator failed to load the coremark
clang++    getch.o sim_main.o verilated.o verilated_dpi.o verilated_fst_c.o Vriscv__ALL.a   -lz    -o sim
Illegal instruction at PC 0x000087fc
Illegal instruction at PC 0x00008808
Illegal instruction at PC 0x00008810
Illegal instruction at PC 0x00008814
Illegal instruction at PC 0x00008818
...

If compilation flag is set to -march=rv32im, coremark.elf is still built.
Reference: [PATCH] riscv: Fix build against binutils 2.38

This would be an issue. The xPack GNU RISC-V Embedded GCC doesn't provide rv32im_zicsr library. Since there is no rv32im_zicsr multilib in the library folder, the compiler will link the default library (You can use the "-Wl,--verbose" linking option to see how the compiler resolves the library link order). The default libc.a is compiled with the RV32C instruction set, which can be problematic when using the standard C library. So when you run coremark with the rv32im_zicsr -march option, it gets an illegal compressed instructions in the memset function.
The temporary solution is using "--with-isa-spec=2.2" to use older ISA spec. It does not reflect the latest RISC-V standard and will likely become unmaintainable in the near future. The best solution is xPack GNU RISC-V Embedded GCC which provides rv32im_zicsr lirary.

The temporary solution is using "--with-isa-spec=2.2" to use older ISA spec. It does not reflect the latest RISC-V standard and will likely become unmaintainable in the near future. The best solution is xPack GNU RISC-V Embedded GCC which provides rv32im_zicsr lirary.

Thus, please report to riscv-none-elf-gcc-xpack with the concern of rv32im_zicsr built library.

The xPack GNU RISC-V Embedded GCC is only a binary distribution of the SiFive RISC-V GNU Embedded Toolchain, and does not intend to add new functionality, or to fix existing problems. This is toolchain issues. I have updated Building Toolchains section to build up defaul ISA spec to 20191213, you can build the toolchains from the source.


:boom::sparkles: Regenerate cloudcontroller with up-to-date python (asyncio) openapi generator

This deprecates our usage of our custom python-uplink openapi-generator that was written 2 years ago.
:boom: Breaking changes:

Pydantic 1 -> 2
some models now expect strict types as input
some model fields renamed (for fields that are reserved words: schema_ renamed to var_schema and from_ to var_from)

:sparkles: New features:

Replaced uplink (unmaintained, with deprecated dependencies - and which used a threading approach to request) with asyncio, which uses more efficient asynchronous HTTP requests.
Added methods to allow fetching wallets by group id -- used with our ACA-Py plugin: didx-xyz/acapy-wallet-groups-plugin
autoflake + isort + black added to generate.sh script to clean up and organise autogenerated code

Notes:

Multitenancy API create and fetch wallet methods now supports our wallet group_id plugin
JsonLD verify request body circumvents problematic model validation in ACA-Py (todo: post issue)
boolean query parameters need to be preprocessed (from booleans to strings) to work with ACA-Py. This was previously done at each method using boolean params. Now configured in the rest API client
todo: add notes for other manual changes

Under 20% duplication :peepo_happy:


[incubator/sparkoperator] Upgraded the operator version

Signed-off-by: Yinan Li<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

No
What this PR does / why we need it:
Upgraded the operator version to v1beta2-1.1.0-2.4.5.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @yuchaoran2011


Middleware on app.use that will only get called on '/'?

So I'm serving a web page on the root route '/', and this page had an authentication middleware. Using regular
app.use('/', authorizeFront, express.static('../client/dist'));
would cause every route to be authenticated, which is what I'm trying to avoid. I've also tried using regex to match exactly '/' but it doesn't seem to be working.
app.use('/^/$/', authorizeFront, express.static('../client/dist'));
Is there any official way to do this? Thanks!

Hi 👋 The app.use is a prefix-based route match, so given a path of / it will match all requests that start with it--everything. If you want an exact match for all methods, the app.all would be the appropriate choice 👍


gcr support

What are you proposing we add or change? Please describe.
Please add support for the google container registry.
Additional context
container image of interest is cadvisor

Good point. Ill try to add it!

https://github.com/sbe-arg/simple-compose-service-updates/releases/tag/v0.1.1 was too easy, mcr and gcr use the same registry tech.


Doc component will look better if we add these classes to <a>

Before

After

I agree, please send PR


ARROW-14100: [C++] subtract(duration, duration) -> duration kernel

ARROW-14100

@pitrou could you also take a look at this and #12215?

Sorry for the push. Had to rebase.

Ha, there are conflicts again :-)

It's the overhead price of distributed review chunks :)

@pitrou this and #12215 should be stable now.

Thanks for the review @pitrou. The appveyor issue seems related to the substrait parser. Maybe a rebase will help.


Chart JS not showing On hover with small data

If I have large data with small data in Bar chart, small data are not showing in onhover function.
Here is the link http://jsfiddle.net/ramakrishnap/zju8044k/

Fixed at https://github.com/nnnick/Chart.js/pull/935


Running on multiple servers

Hi,
I was wondering if running periodical tasks on multiple servers and one DB would lock the rest of the servers and only execute the task once.

Hi @ftxrc,
unfortunately this is not a use case for us. Maybe you should just try and submit your lessons learned.


Release notes for 0.3.1 and 0.4

Did i miss anything?

self-ACK df5c4ee85d2f138f180842df6aa09d73c663d51d


GH-43: Add tests for custom lint check configuration options. (resolves #43)

See #43 for details.

There are no code changes required, this just confirms that each configurable check can be configured and updates the docs.  I probably will cut a new version,  as I did also update the dependencies.

@the-t-in-rtf at a glance this looks good— will try to review shortly. I believe @amb26 had filed #28 so he should have the final say on that one.

Thanks for this work, @the-t-in-rtf - I verified that I could follow the instructions to override stylelint rules both internally and with an external config file. The new syntax checks are very helpful too - Cheers

Cheers.  There were no functional changes, but I cut a new release just for the updated dependencies.


Stratified and Balanced boostrap metrics

[x] Stratify sample
[x] Balanced sample

Above features now supported


Added a ton of temporary logging "KILL9" to diagnose why the Python process is getting killed for voterUpdateFips

The fcc api stopped working reliably a few days ago, and I didn't have a try/except in place for it, hopefully that will stop the kill -9
Over the weekend even the FCC api documentation page was returning a 503,
https://geo.fcc.gov/api/census/#!/block/get_block_find, now it is fine.
Thursday I was getting 100% success with the FCC API, Sunday as low as 10%, this morning (9am) it was 17% and in this latest run (10am) it was 100%
So if the FCC API was the problem, I have a backup (from fipsCodesWithPosition.json) that has roughly 97% of the cities in it, hopefully the FCC API partial outage was a one off.
The cities without names in fipsCodesWithPosition could be manually added over time, but those voteraddress records are not marked as invalid_address'es so they will be tried with the FCC api on the next run of voterUpdateFips
9am run of 5000 google queries:
ADDRESESS_TO_PROCESS 653304
GOOGLE_API_ATTEMPTED 5000
GOOGLE_API_FAILED 17
SAVED_UNIQUE 4620
SAVED_DUPES_UPDATED 271
FCC_API_SUCCESS 865
FIPS_FROM_FALLBACK 4118
ADDRESS_NOT_IN_FIPS__BACKUP 162
GARBLED_ADDRESSES 1338

👍


[image_picker] GIF loses animation

Steps to Reproduce
Update to image_picker version 0.6.1+4 and open a GIF file. The image loses animation.
Version 0.6.0+17 retains the animation.
[√] Flutter (Channel stable, v1.9.1+hotfix.2, on Microsoft Windows [Version 10.0.18362.356], locale en-US)
    • Flutter version 1.9.1+hotfix.2 at c:\src\flutter
    • Framework revision 2d2a1ffec9 (3 weeks ago), 2019-09-06 18:39:49 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\john\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 39.0.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] Connected device (1 available)
    • Pixel 3 • 8B8X15F76 • android-arm64 • Android 10 (API 29)

• No issues found!

This suddenly started working after updating gradle, setting the min SDK level to 29, and rebuilding.
Closing.

I have to reopen this. This behavior is random. Sometimes GIFs work normally, sometimes they do not. The animation can break by simply rebuilding and reinstalling the app on a phone with no code changes. Once you have a build that works, it continues to work through multiple installs -- just don't rebuild or you risk losing the animation again.

@ozzy1873 do you encounter it only with one particular app? Is there a way to isolate a small self-contained app that demonstrates the problem (at least randomly)?

I'm only working on one app. I'll try to duplicate the problem, but it will be difficult to find time for a while.

@ozzy1873 Did you get a chance to isolate a small app for us to reproduce the issue?
Also, do you think it is related to this update? https://github.com/flutter/plugins/pull/1896

Sorry, I haven't been able to create an app that reproduces the issue. I upgraded all the referenced plugins in my app to the latest versions, including image_picker, and the animation is working. That doesn't mean it won't break the next time I upgrade, but it's working right now. It could be related to https://github.com/flutter/plugins/pull/1896. It is behaving like it has been changed from a GIF to a different format like jpg or png. Do you have a suggestion for how I might test that?

@ozzy1873 I took a deeper look at flutter/plugins#1896 and it doesn't seem to touch any gif code. Since you couldn't reproduce the issue and this issue hasn't gotten a lot of thumbs-ups, do you think it could be some weird state that your machine was in which picked up a wrong version of the plugin?
If the issue occurs again, you can try to capture the production steps and other details, then post them here so we can further investigate.

I'm removing the regression label since it is not reproducible anymore.

@ozzy1873  Can you please post your flutter code for picking and displaying the gif?

I can no longer reproduce this problem after updating all plugins and flutter to the latest versions. I'll close this and enter another ticket if it recurs. Thanks!


fix(cdk/text-field): autosize text areas using the placeholder

Roll-forward w/ fix for #22197
This reverts commit 431678730b1070b194e9b51ad29bb8a506881c9e.

After looking into the CI failures, I've discovered that this change conflicts with some logic in MatInput that deletes the placeholder to prevent screen readers from reading it out twice. According to the comment it's only there to support the legacy form-field, so we should probably just remove it. https://github.com/angular/components/blob/master/src/material/input/input.ts#L370-L380
I'm going to mark this PR as blocked pending that work

I've created a PR to remove the legacy placeholder logic https://github.com/angular/components/pull/22319

Alternatively, if we don't care about the autosize behavior with placeholder being a little buggy in the legacy appearance, I can just update the test to use a different form-field appearance. (Made a commit with that change, CI should go green 🤞

After some discussion I think its best we just implement this fix for the standard, fill, and outline appearances, not the legacy appearance


WIP: feat: Tooltipを実装

やったこと

feat: Tooltipを実装
参考：https://github.com/pixiv/charcoal/pull/163

To ensure clarity in our component documentation and specifications, I'd like to proceed with adding new components more cautiously. Therefore, I'll be closing the PR for adding a component at this time.


Update test browser list.

Nevermind, the plan is to update test runner so that the custom elements polyfill is not forced instead.


Set -fno-exceptions in CXXFLAGS

A while back, the idea to add no-exceptions to CXXFLAGS in the docker image came up but we held up to keep consistency with the cmake files
https://github.com/WebAssembly/wasi-sdk/pull/271#discussion_r1055011577
I thought it would be good to bring it up again with the cmake files also updated. AFAICT, when using wasi-sdk with C++ it almost always ends up the user's responsibility to set this as exceptions aren't supported, so it can be a bit easier by defaulting it

Seems fairly reasonable.  I wonder if this should be the default in clang?

I wonder if this should be the default in clang?

Not sure what it would involve but seems like a great idea to me. Would we still consider this PR in the meantime or focus on that?
Also looks like will need https://github.com/WebAssembly/wasi-sdk/pull/354 in for the CI


[BUG] Exposing classes causes crash on location load

auto zenjector = Zenjector::Get();

zenjector->Expose<GlobalNamespace::GameEnergyUIPanel*>("Environment");
zenjector->Expose<GlobalNamespace::ComboUIController*>("Environment");
zenjector->Expose<GlobalNamespace::ScoreMultiplierUIController*>("Environment");
zenjector->Expose<GlobalNamespace::SongProgressUIController*>("Environment");
zenjector->Expose<GlobalNamespace::ImmediateRankUIPanel*>("Environment");

This should work, as it's identical to the PC usage found here: https://github.com/Exomanz/UITweaks/blob/sira3/UITweaks/Plugin.cs#L30-L34 - PC mod works fine.
********** Crash dump: **********
Build fingerprint: 'oculus/hollywood/hollywood:10/QQ3A.200805.001/49068160412800150:user/release-keys'
#00 0x0000000000080a74 /apex/com.android.runtime/lib64/bionic/libc.so (prop_area::find_property(prop_bt*, char const*, unsigned int, char const*, unsigned int, bool)+68) (BuildId: 74793b832f73c27f2be0922f70cc8e16)
#01 0x000000000f8b37b4 /data/data/com.beatgames.beatsaber/files/libcodegen.so (std::get_unexpected()) (BuildId: 1c74ec3efe44d71e52f55b03528304b2fa65db11)
Crash dump is completed

Using Gameplay instead as a workaround.

It seems zenjector->Expose(str) causes this crash regardless of what you pass into it.

We have finally gotten a lead on this, and the suspicion is that ListW can do some screwy casting.
https://github.com/raineio/Lapiz/blob/main/include/zenject/internal/Exposers/ExposerManager.hpp#L30

I assume this is fixed now, close issue?


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build 424

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.0%

Totals

Change from base Build 421:
0.0%

Covered Lines:
14

Relevant Lines:
20

💛  - Coveralls

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Pull "Dataset Permission" NFT from Wallet Address

A user should be able to sign into the application (Vizer/Ocean Market), view their profile, and quickly see which permissions they have access to within the application. To simplify this issue, we will add an NFT called "Dataset-Permission" to our test wallets on the Mumbai Testnet. We will then query the backend to see if the user has the asset, and display the appropriate text to the profile window.
No asset filtering will be performed at this stage.

This implementation does not work. The Ocean Subgraph only indexes for assets related to the Ocean Market. Thus, access tokens generated by a third-party site like GenaDrop cannot be queried by the GraphQL database. The GMU team is creating subgraphs that will specifically index the blockchain for assets created by an access token factory.


Compiling error with loop, works if there is a print statement though

Reporting a bug

[x ] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
[ ] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

I have a loop:
for i, row in enumerate(data):
    if something:
       storage.append(thing)

np.vstack(storage)

This throws an error when compiled with jit(forceobj=True)
but if I add a print statement
for i, row in enumerate(data):
    if something:
       storage.append(thing)

    print(i)
np.vstack(storage)

it runs.
Not sure what is gong on

@dsm-72 thank you for reporting this, the example you listed is incomplete so we can not reproduce. Please submit a fully runnable reproducer (including imports) and the error message you receive when trying to compile, thank you.

Closing this issue due to lack of information. If more information becomes available please add it and reopen the issue. Thanks.


Performance optimization of kNN (nearest neighbor) clusterer(s)

A cursory analysis of the current clustering indicates that there are a variety of performance improvements possible. This issue is to capture the results of that brief analysis for future expansion / triage.

higher performance N-gram tokenization is possible
we might want to check for and warn about large blocks that are over a certain threshold since they're going to cause the n^2 distance measurements to blow up
a Levenshtein-specific algorithm would be faster than a generalized Needleman-Wunsch with 1.0 cost parameters as is currently used
integer arithmetic would be faster than the more general floating point that's used by the current implementation
alternate implementations should be benchmarked, such as:

https://commons.apache.org/proper/commons-text/javadocs/api-release/org/apache/commons/text/similarity/LevenshteinDistance.html

since we have a maximum allowable score, we can use thresholded implementations that exit early when the score is exceeded (this is supported by the Apache commons-text implementation)

The Simile Vicino package has a simple benchmark program called Cluster that takes a set of files and a distance metric and times it, which we could use for work in the context of that package, but we would need to replicate it if we did something outside of Vicino. Either way, we would need to assemble some representative data to use for the benchmark suite.
Proposed solution
Apache commons-text with our own normalization and n-gram tokenization is probably a reasonable starting point.
Alternatives considered

Additional context

@tfmorris Thanks for this issue, Tom.  Looking forward to any improvements.

As an aside, we use two different Levenshtein implementations - our reconciliation Levenshtein distance calculation is done using the Apache Commons org.apache.commons.lang.StringUtils.getLevenshteinDistance(), while the kNN clusterer uses the SecondString class com.wcohen.ss.Levenstein (via Vicino)

Another consideration is using the Java Vector API were we can to handle more parallelization during binning, distance computes, etc.  I have several ideas on this if any developer wants to engage with me on an approach.

If nobody is working on this issue, I want to try solving this issue.
Thankyou!

Hi @shriyasankhyan, I have assigned you the issue

Hi @shriyasankhyan, I have assigned you the issue

Thanks a lot :)


Design Change in comparison page

BUGS:

Please describe the issue that you solved if its not filed.

Otherwise please mention issue #id and use comma if your PR
solves multiple issues.

For things other than bugs:

Describe that thing in very short line, word limit is 200.
Otherwise use issue #id if the issue was filed as feature request.

already done in #3432


update RTCIceServer config props to latest spec

:wave: hello!
The RTCIcerServer object shape has changed recently, so I updated the config props in the Web Client Sample accordingly as the deprecated props were causing the server connection to fail. Thanks for the debugging help!

LGTM!


Use some alternative of the msgspec.to_builtins function

the  msgspec.to_builtins function returns a dictionary with no default values that are specified in the model fields. probably something else needs to be implemented

this bug is very relevant for MsgPackSerializer as this serializer converts the model to linked list, and for this it is very important to have default values as well, a simple example for clarity:
import msgspec

class Foo(msgspec.Struct, omit_defaults=True):
    a: int
    b: int = 0
    c: int = 0

# Foo(1, c=3) -> [1, 3] -> Foo -> Foo(a=1, b=3, c=0)


figures-with-ctx app added

@tolgahancepel
Nice use of the new ctx.trigger_id  feature!  I also like how you use the align="center" prop on the dbc.Row so the buttons are centered on the graph when they are side by side.
Here are some suggestions:

remove unnecessary comments
remove server = app.server since that's not necessary to run the app locally.
Instead of using html.Button, how about using dbc.Button so they are styled with the Bootstrap theme?  Also, in the dbc docs, there is an example of how to display a block level buttons - I think this app is a great use-case:

buttons = html.Div(
    [
        dbc.Button("Bar chart", id="figures-with-ctx-x-btn-bar", color="secondary"),
        dbc.Button("Line chart", id="figures-with-ctx-x-btn-line", color="secondary"),
        dbc.Button("Filled area chart", id="figures-with-ctx-x-btn-area", color="secondary"),
    ],
    className="d-grid gap-2",
)

@tolgahancepel Thank you for creating the PNG image. That is thoughtful of you.
For future PRs, no need to create the image files anymore. Ann has developed a script that would generate these images automatically.

I have committed the changes, thank you. @Coding-with-Adam @AnnMarieW

:woman_dancing: Thanks @tolgahancepel  looks great!


[Feature Request] Simulate multiple request same time

How can I do a request multiple times in the same second or instantly?
I wish to simulate a repeated request at sime time for testing an api, in order to have it try creating the same resource in parallel.
Its a scenario where my api should not create that resource, and its happening sometimes, but I cant simulate, so I wish to do with Insominia.
If its a second later the system is validating, and it will not work as I expect to test.

Hello!  it's been awhile, but I'm marking this as a feature request.  I'm not sure right now how possible this is, given Insomnia's architecture within Electron.  But post a couple of changes/ refactors, it could be.  There would still probably need to be limits on how many concurrent requests could be sent.


Remove explicit ==, hashing definitions from RawRepresentable types

This implements @millenomi's review note in https://github.com/apple/swift-corelibs-foundation/pull/2118#discussion_r275510020.
Remove explicit definitions for == and hash(into:) from Foundation's enum-like RawRepresentable types. The stdlib provides identical definitions in conditional extensions of RawRepresentable.
Note: This would be an ABI-breaking change in Darwin's Foundation overlays because it removes these symbols; but it seems a reasonable simplification for corelibs-foundation, where AFAIK we don't have to be compatible with Swift 5's ABI.
Note also that RawRepresentable's definitions are inlinable, while the original definitions weren't. The corresponding definitions on Darwin are already inlinable, so this is unlikely to cause new issues.

@swift-ci test

@swift-ci please test and merge


Build multi-arch image

Fixes: https://github.com/kubernetes/node-problem-detector/issues/586
Because k8s.gcr.io/debian-base-amd64:v2.0.0 does not support multiple architectures, I use debian:buster instead.
buildx can not export multiple architectures image to docker, https://github.com/docker/buildx/issues/59 ,So we directly push the image to the registry
If you want to build this locally, make sure run the following command first , otherwise you may get a error error: multiple platforms feature is currently not supported for docker driver. Please switch to a different driver (eg. "docker buildx create --use")
# run this before build locally
# If you build this on Github Action, Add a step `docker/setup-buildx-action@v1` instead
sudo docker buildx create --name builder --driver docker-container --driver-opt image=moby/buildkit:master

docker manifest inspect xinydev/node-problem-detector:v0.8.9

{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
   "manifests": [
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1368,
         "digest": "sha256:de9f30d2f0aea0b983db7d437a1d58cfd8daa7a2c264e7687687f31e87fd7826",
         "platform": {
            "architecture": "amd64",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1368,
         "digest": "sha256:fb2e84e713932539deb10e5c2773a96c93b6cb334a01b05c60eee175b11a8d91",
         "platform": {
            "architecture": "arm",
            "os": "linux",
            "variant": "v7"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1368,
         "digest": "sha256:b0dd91c795b9cb77aec2308d35086c80cb40a1690d02b964ff92f2e4cb7aa944",
         "platform": {
            "architecture": "arm64",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1368,
         "digest": "sha256:9931eb4f416a94ae8d1cc9f501d06c23a9ec836e7df0b708cf95fc686f3a065c",
         "platform": {
            "architecture": "ppc64le",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1368,
         "digest": "sha256:07a1bb3e16af6345b4985cf3c3d5ee77f899a725c8daba56ba884c1afeafd038",
         "platform": {
            "architecture": "s390x",
            "os": "linux"
         }
      }
   ]
}

/cc Random-Liu

/ok-to-test

/retest

/retest

/remove-lifecycle stale

/retest

Looks like all tests are now passing, can you add a LGTM label here @Random-Liu ? Right now the lack of arm64 image is the only blocker on my environment to have all our daemonsets working on ARM64 nodes :)

+1 for this

/remove-lifecycle stale

@Random-Liu @xinydev
Hi Guy, can I help here to finish this PR? In case you are busy, are you able to ping colleagues?

@Random-Liu @xinydev
Hi Guy, can I help here to finish this PR? In case you are busy, are you able to ping colleagues?

@jkroepke  There is a new PR(https://github.com/kubernetes/node-problem-detector/pull/634) that fixes a bug with the current PR, you can take a look at that.  I am going to close this one.


Button "..." in Edit Item Form Disappears when clicked

The button just disappears but nothing else is shown. That's confusing. Tested in Chrome 38.

Others have given the same feedback, so they "learned" to ignore the button even though it has important functions.

@raphael-m fixed it.


Increase mem limit for gitopscluster controller

[ x ] I have taken backward compatibility into consideration.

/assign @xiangjingli

/lgtm

@philipwu08   Just a reminder that the csv change will be picked up by mch repo next day. Please make sure it is in the mch repo 2.9 branch. Or have to ask installer squad to approve and merge the PR in the mch repo


Search add autocomplete

This PR adds autocomplete to the search box. Selecting a result takes the user to the part directly, if enter or the search button is used the search-page appears.
Closes #280

@SchrodingersGat I do not know how to fix the styling issue, I get either a W503 or W504 error with the operators but have to break the line somewhere

@matmair instead of adding a new View for this, the live search results should be retrieved using the existing API search functionality.
e.g. /api/part/?search="widget" - this already searches across the name, description, keywords, IPN fields and I'd not like to introduce a duplicate method.

@SchrodingersGat the idea was to create a very light endpoint that serves very light responses and could be extended to search more later. While the new view gets me a response in 20ms it takes the normal part-search 500ms - the idea behind a typeahead / autocomplete would be to be as fast as possible.

New method 20ms: https://github.com/inventree/InvenTree/pull/1838/commits/4013abe4de1d3cff06d28fc3aa334016fa550d50
Old methid ~500ms: https://github.com/inventree/InvenTree/pull/1838/commits/43f1e2b8f9162475395e08785bbcfb28d5f234b6

@matmair if the API for part search is taking ~500ms then I think we need to look at where the inefficiencies are there.

It actually seems pretty performant on my end.
I would suggest you limit the number of responses in the API request, so that on a generic query it doesn't return heaps of results (and slow down the response).
/api/part/?search=widget&limit=25&offset=0 (for example)

Looks really good, I'd like to see a couple of visual tweaks:

Increase spacing slightly between search results
Prepend small thumbnail image to each result

It actually seems pretty performant on my end.
I would suggest you limit the number of responses in the API request, so that on a generic query it doesn't return heaps of results (and slow down the response).
/api/part/?search=widget&limit=25&offset=0 (for example)

At least in my dev enviroment I do not go below an average of 500ms even with limits set

My database contains a test-dataset of around 400 parts

Made some significant improvements to the part API speed in #1850  - check that out once merged...

@SchrodingersGat the UI stuff should be finished

Nice work @matmair this looks pretty great now!

Amazing stuff! Bravo @matmair  :clap:


Unknown OpenGL error at LensFlare_ScreenSpace.cpp

I'm running the app for the first time and got the crash at LensFlare_ScreenSpace::initScene
//this line
m_txEnvmap = Texture::Create("textures/env_factory.dds");

Hi - sorry for the very late reply I must have missed the notification.
You need to install Git LFS, it's required for the large data files (textures, etc.).

Thanks, I will try again everithing


Fix batch execute with pasqal device

cirq.Circuit no longer has a device argument.
This wasn't caught as the reset method was not being tested for the pasqal device.  This PR also adds a test that will execute multiple circuits.
I also started converting control_radius to a float so we can start using cirq.pasqal in the automatic test matrix.

should we add a test for reset on that device now too?

covered now by testing batch_execute with a batch.  Also by putting it in the device test suite.

[sc-46688]


unable to test in isolation async actions with jest

I'm encountering an issue (either on jest or in the redux-mock-store) which forces test to not be isolated between calls.
I've created a sample project to illustrate the issue. This is the test code:
https://github.com/mgenov/test-middleware-with-jest/blob/master/src/axiosMiddleware.spec.js
When just one of the test is executed it passes but when whole suite is executed then one of them fails as it keeps the state of the previous test.
Running one test

Running both

@mgenov Hmm, this is an interesting bug.
Looking at your code, if I add a console.log here:
const store = mockStore({ access_token: '::another_access_token::' })
console.log(store.getState()) // { access_token: '::another_access_token::' }

However, adding a console.log here shows me the wrong getState. I'm going to do some more investigating when I have time.

Thanks @newyork-anthonyng.
I've encountered similar issue and with actions (kept actions from previous test) and will try to simulated in this project too.

I added a uid inside of the redux-mock-store code.
// node_modules/redux-mock-store/lib/index.js

// ...some code
return function mockStore() {
    var _getState = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : {};
    var uid = Math.random(); // note this addition

    function mockStoreWithoutMiddleware() {
      var actions = [];
      var listeners = [];

      var self = {
        getState: function getState() {
          console.log(uid);  // note this addition
          return isFunction(_getState) ? _getState() : _getState;
        },
// ...some more code

I ran this test code with a simple redux middleware:
const myMiddleware = store => next => action => {
  console.log(store.getState());
  next(action);
};
const mockStore = configureMockStore([myMiddleware]);

it('first test', () => {
  const store = mockStore({ foo: 'bar' });
  console.log(store.getState());
});

it('second test', () => {
  const store = mockStore({ foo: 'baz' });
  console.log(store.getState());
})

I looked at my output and saw two different random numbers being outputted. This means that there are 2 different stores being used by my custom middleware. This makes sense 👍
@mgenov When I ran your tests, I saw that I was seeing the same number being output. This makes me suspect that redux-mock-store might not be to blame.
Is it possible that redux-axios-middleware is somehow caching the first redux store that it uses? I'm not too familiar with its internals.

It looks like that it's not cached. I wrote this test in test/middleware.js of redux-axios-middleware and it passes as expected.
Here is the test code:
  it('should check state', () => {
    mockAxiosClient.onGet('/test').reply(200);
    const action = {
      type: 'LOAD',
      payload: {
        request: {
          url: 'test',
          adapter: mockAdapter
        }
      }
    };
    const store = mockStore({ myState: true });
    console.log(store.getState()); // outputs: myState: true
    return store.dispatch(action).then(() => {
      expect(store.getState()).to.shallowDeepEqual({ myState: true });
    });
  });

  it('should check another state', () => {
    mockAxiosClient.onGet('/test').reply(200);
    const action = {
      type: 'LOAD',
      payload: {
        request: {
          url: 'test',
          adapter: mockAdapter
        }
      }
    };
    const store = mockStore({ myState: false });
    console.log(store.getState());  // outputs: myState: false
    return store.dispatch(action).then(() => {
      expect(store.getState()).to.shallowDeepEqual({ myState: false });
    });
  });

I suppose the problem is somewhere else.

Confirmed that it's caused from the redux-axios-middleware. It caches adding of interceptors by using the name of the client and the injection of getState and dispatch is permanent for the client.
As test is not creating a new client it uses the getState() function call of the first store that was passed in.
Thanks for your feedback.

thanks @newyork-anthonyng for helping out!


[ScanDependency] Use -fsyntax-only to scan clang module dependencies

Use -fsyntax-only action to scan clang module dependencies instead of -c option. This fixes a non-deterministic output on windows from scan-dependency output because -c implies it needs a temporary object file in the cc1 arguments that makes the pcm compilation command different every run. This can also make the -Xcc commands for PCM compilation simpler and more likely to be deduplicated by build system.
rdar://135319536

@DougGregor Do you remember why dependency scanning is using -c instead of -fsyntax-only in case I missed anything?

@swift-ci please smoke test

@swift-ci please smoke test

rebranch doesn't build now. My local tests passed. Merge.


Please tag a new release

Hi,
we've recently switched to using dep and I've discovered that the last released version ("v1.1") is really old already and does not include my fix for i386 (#6).
Can you please tag a new release? Would you mind switching to semantic versioning for that? I.e. tag the next release as 1.2.0?
Thanks!

Done - https://github.com/elithrar/simple-scrypt/releases/tag/v1.2.0

Great, thanks!


SolrNet and Dynamic fields

How SolrNet is working with Dynamic Data ?
What would be a best practice ?
Should I my class manually ?
Can I describe some attribute with dynamic post-fix ?

public class Product {
    [SolrField("price_t")]
    public decimal Price { get; set; }

Check out https://github.com/mausch/SolrNet/blob/master/Documentation/Mapping.md#dictionary-mappings-and-dynamic-fields


Unit testing and continuous integration

Solves #9. Unit tests thanks to the Catch library (currently on going) and a new and improved folder structure, the previous files named as test* are now put inside the examples folder, while the unit tests are kept within the tests folder.
Continuous Integration trough Travis CI against the following compilers:

gcc 5.4
gcc 6.1
clang 3.6
clang 3.7

152 tests... not bad!


[FT] Add Gemba MQM Translation Metric

Issue encountered
The metrics only include rather outdated translation metrics.
Solution/Feature
Gemba MQM seems to be a current metric. Adding it would make translation evaluation better.

Great, thanks!
Yes, I see two avenues:

Fork their repo, publish a pip package and integrate it like that.
Just copy their prompts and post processing functions.

IMO option 1 is cleaner and also allows other people to use the metric more easily.
@chuandudx Would you be interested in taking this?

This is done: I forked the repo (https://github.com/joelniklaus/gemba) and deployed it to pypi (https://pypi.org/project/gemba/). I also included it in PR #389. We can also think about pulling some metrics from this PR to the metrics_sample so everyone can use them afterwards.


Failed to resolve: com.pierfrancescosoffritti.androidyoutubeplayer:core:10.0.5

Hi,
I have upgraded my application from JCenter() to mavenCentral() and I got the above error. Does anyone have a solution to fix it or any other player recommendation?
Thanks

The library is not on maven central yet, see #703

@PierfrancescoSoffritti
I see, so do you have any plan to move the library to maven? as I just read JCenter is going to be closed next year Feb 2022.
As I am working on some big project, it is good for me to decide now.
Thanks

Yes, you can read the comments on that issue.


Merge upstream changes

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 19 committers have signed the CLA.:white_check_mark: boghyon:white_check_mark: pavelkornev:white_check_mark: RandomByte:x: dimovpetar:x: swennemers:x: clemai:x: tsaleksandrova:x: pvnn:x: GerganaKremenska:x: PetyaMarkovaBogdanova:x: loginger:x: gerym:x: alexandar-mitsev:x: Lonwyr:x: stoyanovski:x: JumpNRun:x: tsanislavgatev:x: IvaHristova:x: codeworriorYou have signed the CLA already but the status is still pending? Let us recheck it.


add rosa-wrapper and move osde2e-wrapper to its folder

First functional version of rosa-wrapper script.
All pending features are included in the TODO section of the readme files

/hold until #43 and #45 will be merge as I will probably need to rebase

/hold until #43 and #45 will be merge as I will probably need to rebase


Alert if Kyverno is not running and inhibit the other alerts

Alert if Kyverno is not running and inhibit the other alerts.

ping @giantswarm/team-honeybadger

I think this will be very hard to achieve. We can try but there are multiple things to overcome:

The information we get from Prometheus reflects Kubernetes which is already distorted if a webhook is broken.
We need to figure out how we can inhibit other alerts without editing all other possible alerts which currently exist.
It is currently not possible to inhibit ServiceLevel alerts - so these would pollute other teams at the least.

@alex-dabija after discussing this internally within the honeybadger team, "alert when kyverno is not running" is fine however the "inhibit other alerts" part is not trivial and we strongly suggest that the solution for that shall be researched by team honeybadger. WDYT?

Do you know when you might have the time to research the inhibition of the other alerts? We would like to not get paged if Kyverno is not running as soon as possible.

We decided to begin with the alert only for now.


PT-619 | Add categorisation section to event page

Description :sparkles:

Add categorisation section to event page

Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #80 (13d1095) into master (f17f809) will increase coverage by 0.45%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #80      +/-   ##
==========================================
+ Coverage   89.77%   90.23%   +0.45%
==========================================
  Files          79       80       +1
  Lines        2053     2078      +25
  Branches      392      397       +5
==========================================
+ Hits         1843     1875      +32
+ Misses        206      199       -7
  Partials        4        4

Impacted Files
Coverage Δ

src/domain/event/eventBasicInfo/EventBasicInfo.tsx
96.96% <100.00%> (+0.09%)
:arrow_up:

...omain/event/eventBasicInfo/EventCategorisation.tsx
100.00% <100.00%> (ø)

src/domain/venue/venueInfo/VenueInfo.tsx
96.29% <0.00%> (+7.40%)
:arrow_up:

...omain/enrolment/enrolmentForm/ValidationSchema.tsx
96.29% <0.00%> (+9.93%)
:arrow_up:

src/icons/IconGarderobe.tsx
100.00% <0.00%> (+60.00%)
:arrow_up:

Continue to review full report at Codecov.

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


[SPARK-7902] [SPARK-6289] [SPARK-8685] [SQL] [PYSPARK] Refactor of serialization for Python DataFrame

This PR fix the long standing issue of serialization between Python RDD and DataFrame, it change to using a customized Pickler for InternalRow to enable customized unpickling (type conversion, especially for UDT), now we can support UDT for UDF, cc @mengxr .
There is no generated Row anymore.

Merged build triggered.

Merged build started.

Test build #36847 has started for   PR 7301 at commit 0972c07.

Build triggered.

Build started.

Test build #36859 has started for   PR 7301 at commit 034a3a4.

Test build #36847 has finished for   PR 7301 at commit 0972c07.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class GenericInternalRowWithSchema(values: Array[Any], override val schema: StructType)

Merged build finished. Test PASSed.

Test build #36859 has finished for   PR 7301 at commit 034a3a4.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
class GenericInternalRowWithSchema(values: Array[Any], override val schema: StructType)

Build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #36887 has started for   PR 7301 at commit e9217bd.

Test build #36887 has finished for   PR 7301 at commit e9217bd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

@JoshRosen Ping!

This looks pretty good to me overall.  Removing the generated Row classes is a very nice code simplification.

Merged build triggered.

Merged build started.

Test build #36952 has started for   PR 7301 at commit 81bef71.

Test build #36952 has finished for   PR 7301 at commit 81bef71.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class GenericInternalRowWithSchema(values: Array[Any], override val schema: StructType)

Merged build finished. Test PASSed.

LGTM.


[Quest] Updating the Tasks generation to on demand instead of all at once

Enhancement context

We currently generate all tasks for a CarePlan.
We would like to update the task generation to an on-demand cycle. This means a task is only generated after a pre-requisite is completed or cancelled.

Implementation

[ ] Generate Tasks on demand instead of generating all the Tasks at once.

[ ] We however want to make this configurable since some items would want the Tasks generated all at once. e.g If we choose to visualize the child immunization schedules using tasks then we would all the tasks for the schedule to be generated at once.

[ ] Make sure that the schedule defined on the CarePlan and StructureMap is adhered to.
[ ] We will stop the generation of the tasks once the executionPeriod.end is >= to the CarePlan period.end date. or whent he activity.scheduledTiming.repeat.countmax is reached.
[ ] Always generate the first tasks on the day of CarePlan creation/generation.
[ ] Adapt the task's executionPeriod.end & executionPeriod.start dates to the schedule depending on when the previous task was closed. e.g For the monthly ANC visit schedule

[ ] If task 1 had a start date of 01/01/2022 and an end date of 31/01/2022. Then the task was closed on 09/02/202
[ ] Then the next task to be generated will have a  start date of 01/03/2022 and an end date of 31/03/2022 instead of the start date of 01/02/2022 and end date of 28/02/2022

Acceptance criteria

[ ] Only generate a task after the previous one has the status completed or cancelled
[ ] The Task should follow the defined schedule on the CarePlan.

This makes sense as the high level plan. What's the technical implementation plan for making sure we generate the new tasks appropriately?
We don't need that know, but who ever is assigned this, please sketch that out in a comment here and request review before coding begins, going to add a blocked label as a reminder of that.

@pld Makes sense. @maimoonak and I are to have a call to define how to approach it. We will update the Technical approach added here.

@maimoonak can you add an implementation plan to this ticket? I think that will unblock it

Hi  @pld @dubdabasoduba . Sorry for late response. I was exploring the current implementation of $apply. Looks like the changes are major and also we would need to

Write CQL for all plan definitions
Remove the StructureMap transforms to handle multiple actions and find a way to map CQL and the transform
Update the current code to call $apply instead of fhir-task-generator

@dubdabasoduba mentioned that the requirement is urgent so we need to have a solid implementation plan rather than the major changes
For current implementation we can write $apply CQL in parallel and add the feature as a separate way of creating CarePlan.

Keep the implementation same and update PlanDefinition and remove the repeat to 1 where we want to keep 1 task per Event. This would allow implementer configure the 'all-at-once' tasks or 'one-per-visit' tasks.
Stopping the generation of the tasks once the executionPeriod.end is >= to the CarePlan period.end date is in place can be added as a separate condition. Rightnow we are marking CarePlan completed based on a specific type of Condition i.e. Sick Child got 'fully-recovered' into questionnaire.answer
Adapt the task's executionPeriod.end & executionPeriod.start dates to the schedule would be done by passing the last task via 'input' -> DataRequirement into StructureMap. And the structure-map would handle the generation of new task. Plz note that currently we have updating the current careplan code inplace so it would be another action into PlanDefinition only.

the PR #1854  allows using both approaches.. i.e. $lite, $apply..The $ apply (2.1.0) can not be used with repeat timings... i.e. can not generate ALL tasks at once with repeat schedule. rather we need to specifiy each as different action. However, $lite can be used for both.

OK cool that's reasonable, thanks, I doubt we'd want to use $apply unless we've already switch to on-demand generation.


Bulb does not respond to HA instruction

Describe the bug
When HA is first restarted, or after Supervisor Restart, I can tap button for this bulb to turn it on, and the bulb comes on. However, HA does not get notified that it is on, and as a result does not set the button to show as "on". (I have other bulbs which work fine).
Subsequent attempts to control the bulb via HA fail, but no error in Log (as see below). I can control bulb via Tuya app.
Expected behavior
Feedback notification of bulb turn on, such that HA can then turn it off.
Home Assistant Version
2021.7.4
Device info (please complete the following information, which can be found in log):
2021-08-03 14:00:11 DEBUG (SyncWorker_3) [custom_components.tuya_v2.light] light kwargs-> {}
2021-08-03 14:00:11 DEBUG (SyncWorker_0) [tuya iot] Request: method = POST, url = https://openapi.tuyaeu.com/v1.0/devices/07573073840d8e8acc92/commands, params = None, body = {'commands': [{'code': 'switch_led', 'value': True}]}, headers = {'client_id': 'e5ksa9nyas3xqxo508jx', 'sign': 'E000940D02B3ABF05C3F4535D907FD8BB895541BCEE169B2434FE3D6A617393F', 'sign_method': 'HMAC-SHA256', 'access_token': 'c4375c2759c479428d06bedd18b14385', 't': '1627995611275', 'lang': 'en'}
2021-08-03 14:00:13 DEBUG (SyncWorker_0) [tuya iot] Response: {
"result": true,
"success": true,
"t":<PHONE_NUMBER>447
}
2021-08-03 14:00:13 DEBUG (Thread-779) [tuya iot] _on_log: Received PUBLISH (d0, q0, r0, m0), 'cloud/token/in/1689da01dc49a0256f6d33b38926f632', ... (348 bytes)
2021-08-03 14:00:13 DEBUG (Thread-779) [tuya iot] payload-> b'{"data":"yrkEe26VYoz9aGADuBPp3ssCq3llfmJx4Vv/gqejdicZMW+5nxiYhp2sh+f3XsOHFmzDVgddJMBlfIlUucNEzcpmG6Clbvfn07KVyRt/HP7A3rlC9+HQ0jPXIlvMlz1lo/JX3wX82sdgqgJPxCPs/uPruXzxTlWu3HQFKWIBxTXSiyv1m51ZWfit6BMye5EIXCeDsDS5mEI0aPjqrRtER57LBll1ss2IaTfSiUcgdWvTHS3mKQPiJM1fPCMLvUUE","protocol":4,"pv":"2.0","sign":"47e6094fc35eae85b3cf3986dd19869c","t":1627995612}'
2021-08-03 14:00:13 DEBUG (Thread-779) [tuya iot] on_message: {'data': {'dataId': '3708b8a9-471c-4f5b-a53b-7e69a6bb86a5', 'devId': '07573073840d8e8acc92', 'productKey': 'yAimpd7WEEwBi5wj', 'status': [{'1': True, 'code': 'switch_led', 't': '1627995612', 'value': True}]}, 'protocol': 4, 'pv': '2.0', 'sign': '47e6094fc35eae85b3cf3986dd19869c', 't':<PHONE_NUMBER>}
2021-08-03 14:00:13 DEBUG (Thread-779) [tuya iot] mq receive-> {'data': {'dataId': '3708b8a9-471c-4f5b-a53b-7e69a6bb86a5', 'devId': '07573073840d8e8acc92', 'productKey': 'yAimpd7WEEwBi5wj', 'status': [{'1': True, 'code': 'switch_led', 't': '1627995612', 'value': True}]}, 'protocol': 4, 'pv': '2.0', 'sign': '47e6094fc35eae85b3cf3986dd19869c', 't':<PHONE_NUMBER>}
2021-08-03 14:00:13 DEBUG (Thread-779) [tuya iot] mq _on_device_report-> [{'1': True, 'code': 'switch_led', 't': '1627995612', 'value': True}]
2021-08-03 14:00:13 DEBUG (Thread-779) [custom_components.tuya_v2] _update--><custom_components.tuya_v2._init_tuya_sdk..DeviceListener object at 0x7f11f11e46a0>;->>{'switch_led': True, 'work_mode': 'white', 'bright_value': 172, 'temp_value': 255, 'colour_data': '{"h":0.0,"s":255.0,"v":255.0}', 'scene_data': '{"h":0.0,"s":0.0,"v":0.0}', 'flash_scene_1': '{"bright":255,"frequency":80,"hsv":[{"h":120.0,"s":255.0,"v":255.0}],"temperature":255}', 'flash_scene_2': '{"bright":255,"frequency":128,"hsv":[{"h":0.0,"s":255.0,"v":255.0},{"h":120.0,"s":255.0,"v":255.0},{"h":240.0,"s":255.0,"v":255.0},{"h":0.0,"s":0.0,"v":0.0},{"h":0.0,"s":0.0,"v":0.0},{"h":0.0,"s":0.0,"v":0.0}],"temperature":255}', 'flash_scene_3': '{"bright":255,"frequency":80,"hsv":[{"h":0.0,"s":255.0,"v":255.0}],"temperature":255}', 'flash_scene_4': '{"bright":255,"frequency":5,"hsv":[{"h":0.0,"s":255.0,"v":255.0},{"h":120.0,"s":255.0,"v":255.0},{"h":60.0,"s":255.0,"v":255.0},{"h":300.0,"s":255.0,"v":255.0},{"h":240.0,"s":255.0,"v":255.0},{"h":0.0,"s":0.0,"v":0.0}],"temperature":255}'}
2021-08-03 14:00:13 DEBUG (MainThread) [custom_components.tuya_v2.light] brightness id-><PHONE_NUMBER>0d8e8acc92,
work_mode-> white,
check true-> False
2021-08-03 14:00:13 DEBUG (Thread-779) [custom_components.tuya_v2] _update--><custom_components.tuya_v2._init_tuya_sdk..DeviceListener object at 0x7f11f11e46a0>;->>{'switch_led': True, 'work_mode': 'white', 'bright_value': 172, 'temp_value': 255, 'colour_data': '{"h":0.0,"s":255.0,"v":255.0}', 'scene_data': '{"h":0.0,"s":0.0,"v":0.0}', 'flash_scene_1': '{"bright":255,"frequency":80,"hsv":[{"h":120.0,"s":255.0,"v":255.0}],"temperature":255}', 'flash_scene_2': '{"bright":255,"frequency":128,"hsv":[{"h":0.0,"s":255.0,"v":255.0},{"h":120.0,"s":255.0,"v":255.0},{"h":240.0,"s":255.0,"v":255.0},{"h":0.0,"s":0.0,"v":0.0},{"h":0.0,"s":0.0,"v":0.0},{"h":0.0,"s":0.0,"v":0.0}],"temperature":255}', 'flash_scene_3': '{"bright":255,"frequency":80,"hsv":[{"h":0.0,"s":255.0,"v":255.0}],"temperature":255}', 'flash_scene_4': '{"bright":255,"frequency":5,"hsv":[{"h":0.0,"s":255.0,"v":255.0},{"h":120.0,"s":255.0,"v":255.0},{"h":60.0,"s":255.0,"v":255.0},{"h":300.0,"s":255.0,"v":255.0},{"h":240.0,"s":255.0,"v":255.0},{"h":0.0,"s":0.0,"v":0.0}],"temperature":255}'}

According to the log which you have provided,
<custom_components.tuya_v2._init_tuya_sdk..DeviceListener object at 0x7f11f11e46a0>;->>{'switch_led': True,
HA has received mqtt device status update message.
So can you provide more logs?

Does the tip at 9:45 help with this issue? https://youtu.be/P-vOwHB83JE


macro example has a hidden require failure

The output is hidden by default since the tests themselves pass despite this require failure, but it shows up with --test_output=all:
~/figma/rules_js $ bazel test --test_output=all //examples/macro:test
INFO: Analyzed target //examples/macro:test (0 packages loaded, 0 targets configured).
INFO: Found 1 test target...
Target //examples/macro:test up-to-date:
  bazel-bin/examples/macro/test.sh
INFO: Elapsed time: 0.216s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
PASSED: //examples/macro:test (see /private/var/tmp/_bazel_johnfirebaugh/3cc5be9735d30b6128426fd19d172550/execroot/aspect_rules_js/bazel-out/darwin-fastbuild/testlogs/examples/macro/test/test.log)
INFO: From Testing //examples/macro:test
==================== Test output for //examples/macro:test:
Failed to load reporter: "mocha-junit-reporter" or "/private/var/tmp/_bazel_johnfirebaugh/3cc5be9735d30b6128426fd19d172550/sandbox/darwin-sandbox/6/execroot/aspect_rules_js/bazel-out/darwin-fastbuild/bin/examples/macro/test.sh.runfiles/aspect_rules_js/mocha-junit-reporter": Error: Cannot find module 'mocha-junit-reporter'
Require stack:
- /private/var/tmp/_bazel_johnfirebaugh/3cc5be9735d30b6128426fd19d172550/sandbox/darwin-sandbox/6/execroot/aspect_rules_js/bazel-out/darwin-fastbuild/bin/examples/macro/test.sh.runfiles/aspect_rules_js/node_modules/.aspect_rules_js/mocha-multi-reporters<EMAIL_ADDRESS>- /private/var/tmp/_bazel_johnfirebaugh/3cc5be9735d30b6128426fd19d172550/sandbox/darwin-sandbox/6/execroot/aspect_rules_js/bazel-out/darwin-fastbuild/bin/examples/macro/test.sh.runfiles/aspect_rules_js/node_modules/.aspect_rules_js/mocha-multi-reporters<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:94:18)
    at MultiReporters.processReporterEnabled (/private/var/tmp/_bazel_johnfirebaugh/3cc5be9735d30b6128426fd19d172550/sandbox/darwin-sandbox/6/execroot/aspect_rules_js/bazel-out/darwin-fastbuild/bin/examples/macro/test.sh.runfiles/aspect_rules_js/node_modules/.aspect_rules_js/mocha-multi-reporters@1.5.1_mocha@10.0.0/node_modules/mocha-multi-reporters/lib/MultiReporters.js:75:36)
    at Array.map (<anonymous>)
    at new MultiReporters (/private/var/tmp/_bazel_johnfirebaugh/3cc5be9735d30b6128426fd19d172550/sandbox/darwin-sandbox/6/execroot/aspect_rules_js/bazel-out/darwin-fastbuild/bin/examples/macro/test.sh.runfiles/aspect_rules_js/node_modules/.aspect_rules_js/mocha-multi-reporters@1.5.1_mocha@10.0.0/node_modules/mocha-multi-reporters/lib/MultiReporters.js:54:44)
    at Mocha.run (/private/var/tmp/_bazel_johnfirebaugh/3cc5be9735d30b6128426fd19d172550/sandbox/darwin-sandbox/6/execroot/aspect_rules_js/bazel-out/darwin-fastbuild/bin/examples/macro/test.sh.runfiles/aspect_rules_js/node_modules/.aspect_rules_js/mocha@10.0.0_th2rfume6p4m5jxelm27wrhnly/node_modules/mocha/lib/mocha.js:981:18)
    at singleRun (/private/var/tmp/_bazel_johnfirebaugh/3cc5be9735d30b6128426fd19d172550/sandbox/darwin-sandbox/6/execroot/aspect_rules_js/bazel-out/darwin-fastbuild/bin/examples/macro/test.sh.runfiles/aspect_rules_js/node_modules/.aspect_rules_js/mocha@10.0.0_th2rfume6p4m5jxelm27wrhnly/node_modules/mocha/lib/cli/run-helpers.js:126:16)
    at async Object.exports.handler (/private/var/tmp/_bazel_johnfirebaugh/3cc5be9735d30b6128426fd19d172550/sandbox/darwin-sandbox/6/execroot/aspect_rules_js/bazel-out/darwin-fastbuild/bin/examples/macro/test.sh.runfiles/aspect_rules_js/node_modules/.aspect_rules_js/mocha@10.0.0_th2rfume6p4m5jxelm27wrhnly/node_modules/mocha/lib/cli/run.js:370:5)
Reporter not found! mocha-junit-reporter

  mocha
    ✔ integrates with Bazel

  1 passing (2ms)

================================================================================
//examples/macro:test                                           (cached) PASSED in 0.6s

Executed 0 out of 1 test: 1 test passes.
INFO: Build completed successfully, 1 total action

This seems specific to the directory / symlink structure set up by rules_js. I thought it might be that mocha-multi-reporters is incompatible with pnpm, but that appears not to be the case because cd examples/macro && pnpm install && MOCHA_FILE=test.xml ./node_modules/.bin/mocha --reporter mocha-multi-reporters --reporter-options configFile=./mocha_reporters.json test.js succeeds and generates test.xml.

Maybe mocha-junit-reporter needs to be hoisted here too https://github.com/aspect-build/rules_js/blob/main/package.json#L12

Fixed by https://github.com/aspect-build/rules_js/pull/355.


BUG: Cannot proxy the given URL

Describe the bug
The activity graph has disappeared.
To Reproduce
Go to my profile repository: https://github.com/FrancescoPaoloL/FrancescoPaoloL
Expected behavior
The activity graph should be visible.
Desktop (please complete the following information):

OS: Zorin OS 15.3 x86_64 (Kernel: 5.4.0-149-generic)
Browser [Firefox
Version 113.0.1 (64-bit)

Additional context
I'm using this code:

I've tried to make ex-novo from here https://ashutosh00710.github.io/github-readme-activity-graph/
but it tells me "Sorry! something went wrong."

Same issue here!! Here's my code:
<img align="center" src="https://github-readme-activity-graph.cyclic.app/graph?username=csfelix&theme=tokyo-night" />


【FIX】Update service topology for k8s 1.21 and unit test

What type of PR is this?

/kind bug

What this PR does / why we need it:
The service takes effect in the new version
Which issue(s) this PR fixes:
https://github.com/openyurtio/openyurt/issues/789

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

@JameKeal Adapt service topology for K8s v1.21.x, but k8s libraries version in go.mod are updated to v1.22.3, I think if we update go.mod in this pull request, maybe other features could not work.

@JameKeal Adapt service topology for K8s v1.21.x, but k8s libraries version in go.mod are updated to v1.22.3, I think if we update go.mod in this pull request, maybe other features could not work.

By your means, if I don't update go.mod, someone who pull the master branch to build code, it's also fail.
If you think it's not a problem, I can recover the go.mod.

I think we can merge #821 before this pr, at that time, everything will be ok.

Fixes #789

@JameKeal please rebase the newest master branch.

/lgtm
/approve


UV_NO_BUILD_ISOLATION=true has no effect

Hello,
I am trying to use the --no-build-isolation option, introduced in https://github.com/astral-sh/uv/pull/2258
It's necessary to make uv/pip use the current venv when installing or building packages.
It's largely used in build systems and environments where a venv is already prepared to build/install packages.
I am finding that the option is not working when set by an environment variable? I think it might not be implemented.
Or the environment variable name/value might be something else. I've tried a few variants I could think of but that did not help.
# pass
uv pip install -e . --no-build-isolation

# fail
UV_NO_BUILD_ISOLATION=true uv pip install -e .

uv version 0.1.39 (latest as of today)

Yeah, we don't provide an environment variable for this yet.


Shell Open With Default Program Master

4.0 edition of https://github.com/godotengine/godot/pull/39075
Will test for a few moments.

The last comment mentioned we should have a list of default extensions to block. This pr is salvageable.


Simplify d4tools image

This PR adds | fixes:

Fix #9

How to test:

Build the image
Run a container and make sure d4tools is executed

Review:

[ ] Code approved by
[ ] Tests executed by

This version is a:

[ ] MAJOR - when you make incompatible API changes
[x] MINOR - when you add functionality in a backwards compatible manner
[ ] PATCH - when you make backwards compatible bug fixes or documentation/instructions

Build image: 🆗

Run image. Nope! ⛔

Fixed by basing the image on bullseye slim instead (has a newer libc6):

Pushed to Docker Hub:


show what exactly went wrong

Currently getting random errors like: ZendeskAPI::Error::NetworkError: the server responded with status 500  ... would be much nicer to receive: ZendeskAPI::Error::NetworkError: the server responded with status 500 -- get https://fail.zendesk.com/api/v2/incremental/tickets.json?include=users%2Cgroups%2Corganizations%2Cmetric_sets%2Cdates&start_time=1425754064
@bquorning @vgrigoruk

fixed

:+1:


React 16 now in RC

React 16 is now at RC stage. Can we expect to see a pre-release of recompose before React 16 stable?

feel free to provide a pr
https://github.com/acdlite/recompose/blob/master/src/packages/recompose/package.json#L21
btw should work even now with warning at install


PM-439 Bug: Do not run watcher if the provider hasn't tried to init

So the reason for wrong network modal showing up was a watcher for changes. It had run before a provider tried to init and those lines of code made the provider available:
    if (!this.walletEnabled) {
      this.walletEnabled = true
      providerUpdate.available = true
    }

I added connectionTried variable and now watcher checks if provider has actually tried to connect.

I do not like in general condition races and its hacks. It should be a real problem if we load providers and then, once they are loaded, we execute the watcher?

@apanizo Ok, will redo it

Before spending too much time, think about it first, if you have any problem let me know.

@apanizo 👌


Implement Secrets

AWS - Secrets
AWS Secrets Manager helps you protect secrets needed to access your applications, services, and IT resources. The service enables you to easily rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle. Users and applications retrieve secrets with a call to Secrets Manager APIs, eliminating the need to hardcode sensitive information in plain text. more info
API: link
Console: link

Also implement RepositoryCredentials for the EcsContainerDefinition subresource and Secret for the EcsContainerDefinition and EcsLogConfiguration subresources