RuntimeWarning: invalid value encountered in intersection on my custom dataset

Hello,
I am training maskDINO on my own dataset and I get:
"lib/python3.8/site-packages/shapely/set_operations.py:133: RuntimeWarning: invalid value encountered in intersection".
would it create an issue or it is ok and the model will be trained correctly?
thanks

I am not sure. Is everything going well in your training?

Hi FengLi,
I hope you are doing well and thank you for your response. Yes, the training was done properly. This warning happens because in some of images in tmy dataset there is not objects that I am looking for.

I meet this issue too. It seems that the model training is done properly. So I just ignore this RuntimeWarning by adding a line in the train_net.py:
(starts from line 9)
try:
    from shapely.errors import ShapelyDeprecationWarning
    import warnings
    warnings.filterwarnings('ignore', category=ShapelyDeprecationWarning)
    warnings.filterwarnings('ignore', category=RuntimeWarning)
except:
    pass

Hi well i think in this case you only get rid of warning message but maybe you need to revise your code to make sure that something wired does not happen in your training pipeline.

I meet this issue too. It seems that the model training is done properly. So I just ignore this RuntimeWarning by adding a line in the train_net.py: (starts from line 9)
try:
    from shapely.errors import ShapelyDeprecationWarning
    import warnings
    warnings.filterwarnings('ignore', category=ShapelyDeprecationWarning)
    warnings.filterwarnings('ignore', category=RuntimeWarning)
except:
    pass

Hi well i think in this case you only get rid of warning message but maybe you need to revise your code to make sure that something wired does not happen in your training pipeline.

I meet this issue too. It seems that the model training is done properly. So I just ignore this RuntimeWarning by adding a line in the train_net.py: (starts from line 9)
try:
    from shapely.errors import ShapelyDeprecationWarning
    import warnings
    warnings.filterwarnings('ignore', category=ShapelyDeprecationWarning)
    warnings.filterwarnings('ignore', category=RuntimeWarning)
except:
    pass

Hi well i think in this case you only get rid of warning message but maybe you need to revise your code to make sure that something wired does not happen in your training pipeline.

Yeah I agree with you. I haven't finished reading the code. Do you know which part of code causes the warning?
btw, I find a issue which is almost as same as this one: #https://github.com/facebookresearch/Mask2Former/issues/171#issue-1535705440

I meet this issue too. It seems that the model training is done properly. So I just ignore this RuntimeWarning by adding a line in the train_net.py: (starts from line 9)
try:
    from shapely.errors import ShapelyDeprecationWarning
    import warnings
    warnings.filterwarnings('ignore', category=ShapelyDeprecationWarning)
    warnings.filterwarnings('ignore', category=RuntimeWarning)
except:
    pass

Hi well i think in this case you only get rid of warning message but maybe you need to revise your code to make sure that something wired does not happen in your training pipeline.

Yeah I agree with you. I haven't finished reading the code. Do you know which part of code causes the warning? btw, I find a issue which is almost as same as this one: #facebookresearch/Mask2Former#171 (comment)

As far as I remember it was related to one package in Python dealing with geometry (bounding box and computing the IOU) , probably this metric  produce a NAN during the training.


Data type tree for DT page

create helper utility for taking a slice of a tree/forest
some minor fixes

#6661

Not ready for merging yet


How to align the text and text decoration line with space

How to give space between the text and text-decoration line in react-native.
I have set text-decoration line but it not shows space in between the text and decoration line.
Refer this image https://i.stack.imgur.com/6woPN.png
Also, I have set boderBottom width. It shows in the entire screen
https://i.stack.imgur.com/gNNFY.png
Any solution for this?

It related to the text design of react-native


Receiver filter matching incorrectly

The new receiver dropdown/type ahead filter doesn't filter correctly.
Typed: prodeng
Expected anything including prodeng
Got:

backend-engineering-productivity which includes all characters from prodeng, but in the wrong order
osc-reporting doesn't even include all characters.

@stuartnelson3

@grobie As far as I understand, the receiver dropdown is not filtering but just sorting. As backend-engineering-productivity is closer to prodeng then osc-reporting it is listed first.
Please have a look at my question here ans @stuartnelson3 subsequent answer here.

Oooh, thanks for the clarification. That wasn't clear to me from the ux.
Any reason to not just do plain filtering? Like in editors when searching
for files.
On Sat, Jul 29, 2017, 15:56 Max Inden<EMAIL_ADDRESS>wrote:

@grobie https://github.com/grobie As far as I understand, the receiver
dropdown is not filtering but just sorting. As
backend-engineering-productivity is closer to prodeng then osc-reporting
it is listed first.
Please have a look at my question here
https://github.com/prometheus/alertmanager/pull/910#issuecomment-316009575
ans @stuartnelson3 https://github.com/stuartnelson3 subsequent answer
here
https://github.com/prometheus/alertmanager/pull/910#issuecomment-316011192
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/alertmanager/issues/933#issuecomment-318832596,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAANaHS9NMKRAslIKKei199wqmH1j1sBks5sSzoGgaJpZM4OnVZf
.

Not sure. I would have to redirect this question on to @stuartnelson3.

What we currently do is find string similarity and sort based on that. There's absolutely no reason why we can't add on to this (basic) functionality to e.g. filter out results whose similarity value is below a threshold.
The starts to become difficult because we'll be more or less arbitrarily picking a similarity value as the cut-off, and seeing how it works.
@grobie would you be interested in running a branch at SC with this enabled? It would be super helpful to tune the threshold based on a large production deploy like what is currently there.

I'm unsure about that approach to be honest. If I type prodeng I don't expect to see results for engineering productivity. My personal expectation of that feature would be to use a simple search behavior without any weighting as written in the (updated) issue description.

Ok, I understand. The current search is matching because prod exists in both, but you expect as soon as you type prode that productivity would disappear from the list, because there's no match for the additional e.

As long as the best matches are on top of the list, and the total amount of displayed matches is limited, I actually prefer to show the fuzzy matches, too.
That's also more and more common around the internet (I guess with fuzzy-searching large databases becoming more feasible), thus the moment of surprise @grobie encountered will become less common. The main use-case would be to be resilient against typos.


Doxygen generator code had gotten stale

The CMake build system included some logic to support building the Doxygen-based CFE documentation.  However these rules had gotten out of date with respect to other changes that had gone into the build since they were written, and a couple variable name and path names need to be fixed.

Imported from trac issue 170.  Created by jphickey on 2016-07-01T10:33:58, last modified: 2019-03-05T14:58:28

Trac comment by jphickey on 2016-07-01 10:51:40:
Pushed commit [changeset:80c21b0] with the proposed update.
On branch trac-170-fixup-doxygen

Trac comment by cdknight on 2016-07-12 15:54:21:
+1

Trac comment by jphickey on 2016-07-27 22:40:09:
The branch above has been updated/rebased to include the latest modifications from the EVA documentation effort.  This makes the following additions:

Add support for a top-level mission "doc" directory
change the CFE overview to be just a regular page instead of a "main page", this allows the top level doc directory (mission) to supply the main page.  The CFE documentation becomes a "related page"
hook into cmake build system to append all the application/module directories to the doxygen input.  This includes the PSP and OSAL in use, and NOT the ones that are not in use to reduce clutter in the resulting docs.

Trac comment by glimes on 2016-11-08 14:17:08:
Current crop of cfe-next are all going into CFE 6.6

Trac comment by sstrege on 2017-03-20 14:45:37:
Changing the main.dox file to replace the \mainpage doxygen keyword with a subpage affects the doxygen output generated via the classic build.  The result is an empty index.html file with no links to the the cFE documentation included.

Trac comment by jphickey on 2017-11-15 10:48:48:
UPDATE FOR CFE 6.6:
There needs to be an update in CFE 6.6 in order to make sure we can build the CFE users guide documentation via the cmake build.
This takes a slightly different approach than the previous change in that it leaves the .dox files used by the classic build alone, aside from fixing up a few non-utf8 characters which were causing grief.
Previously the cmake mission-doc target only created something akin to the "detail design" output of the classic build.  To create the users guide as well, another target needed to be added for this.  This has a different, smaller set of inputs than the detail design.
Commit: [changeset:0075b72] branch trac-170-fixup-doxygen

Trac comment by glimes on 2017-11-17 12:48:57:
ignore previous content of this comment,
my test script had the wrong commit.
With the CORRECT merges done,
{{{
make prep
make doc
}}}
at the top level of a normally configured CMake based CFS build
now produces outputs.

Trac comment by sstrege on 2017-11-17 12:19:25:
Recommend/approve commit [changeset:0075b72]

Trac comment by jhageman on 2019-03-05 14:58:28:
Milestone renamed


Add PWA + Metadata capability

Add PWA and Metadata capability to site.

Merging initial version. A later theme update can add additional capability to the PWA. Currently minimal assets are cached.


Incorrect Response for Get Recommendations EndPoint

The documentation for Get Recommendations states that the response tracks array returns a SimplifiedTrackObject.  From experience I see that it returns a TrackObject instead - that is it has the albums and popularity properties.
https://github.com/sonallux/spotify-web-api/blob/c38c5c896e5a9da2426bfbd9743860b0a2ebe9e5/spotify-web-api-generator-open-api/spotify-web-api-openapi.yml#L6858

Thanks for reporting this issue. I also just checked and the get recommendations endpoint is indeed returning the full TrackObject and not a SimplifiedTrackObject even though it is documented that way in the Web API Reference.
I am going to provide a fix for this.


"Cannot read property 'name' of undefined" when i try to connect a psql

Hello guys,
Your project is awesome, i like it :)
But i have a problem ! My connection with MySQL work good, but when i try connection on POSTGRE on the same server, i have a error "Cannot read property 'name' of undefined".
Here a screenshot of my configuration

I think my configuration is good because on the same server, my connection on MySQL with Sqlectron work good.
Maybe you have idea ? I searched on issues, but i dont see this problem.
(sorry for my basic english).
Thanks ! :)

Hi,
thanks for the report,
could you try to give us some logging info,
https://github.com/sqlectron/sqlectron-gui/blob/master/docs/app/logging.md
Thanks


Publish totalConsumption and runtime?

Hi there,
first of all thanks for the great work!
Would it be possible to also publish the total consumption via MQTT or am missing something?
I can get the data by HTTP Request, but it would be great to also have this data directly available as an entity in Home Assistant.
Thanks

All 4 entities displayed in the web ui are published via MQTT along with RSSI and version number. Could you please check the messages published to your broker with MQTT Explorer oder mosquitto_sub on the topic you configured under "settings". Are you using the Arduino IDE or PlatformIO to compile the software? ArduinoJson Version? Operating system?

Could you please check the topic HA discovery topic homeassistant/sensor/wifipowermeter-74DAE9 with MQTT Explorer. You should see 5 entities: pulse_count, total_consumption, current_power, signal_strength and runtime. It might help to remove the power meter's entry from HA's devices page and delete the above mentioned topic. Then restart the power meter to retrigger HA MQTT discovery.

IDE? Operating system? ArduinoJSON version? Did you remove the topic homeassistant/sensor/wifipowermeter-74DAE9?

Just a wild guess: try to increase the size of StaticJsonDocument in mqtt.c (line 30) from 512 to 640.

I have no idea why this topic doesn't show up in your setup. Never had this problem. Could you please post the output from the PlatformIO console, when you compile the software. Everything from "PLATFORM:" up to and including the "Dependency Graph".
I'm on vacation right now, so I can't do any further testing with my wifi power meter. I will get back to you at the beginning of next week.

Hello,
installed the meter yesterday and switched on home assistant discovery this morning.
I do as well only get 4 entities inside home assistant, total consumption is missing here too.
Those are the entities I do have:
homeassistant/sensor/wifipowermeter-7A0979/pulse_count
homeassistant/sensor/wifipowermeter-7A0979/current_power
homeassistant/sensor/wifipowermeter-7A0979/signal_strength
homeassistant/sensor/wifipowermeter-7A0979/runtime

Using firmware 223.
I compiled the firmware using Win10 and VSCode as well. I will later also check on the ArduinoJSON version.
The jsonData published to the other mqtt topic which is not used for home assistant looks just fine:
{"counter":907,"consumption":85492.88,"power":1495,"runtime":"0d0h10m","rssi":-44,"version":223}

I just checked my MQTT broker at home: the home assistant discovery message for "total_consumption" has 405 Bytes and should fit into the allocated char buffer and StaticJsonDocument according to the ArduinoJson Assistant. I'm using VS Code with PlatformIO on MacOS and discovery is working as expected. I'm pretty sure it's all about buffer allocation an different platforms: please try to increase StaticJsonDocument  in mqtt.c (line 30) from 512 to 640 and buf (line 32) from 448 to 512.

Just rebuilt the firmware with the changes mentioned, but the behavior did not change. I did have to set up all the settings again as they somehow got lost. Even had to set up wifi which worked just out of the box after flashing the firmware via USB yesterday (probably because of the firmware installed previously).
I also looked up my ArduinoJson version now, which is 6.19.4. So same as steakneedy.
The other discovery messages have lengths of 338 to 404 bytes. I don't see why the total power one should be a huge difference here...
Is there a way to upload the config without having to set all the settings again? That would be great for testing purposes

Does either of you have TLS enabled?

Is there a way to upload the config without having to set all the settings again? That would be great for testing purposes

Please use config.h for individual sensor presets.

Does either of you have TLS enabled?

I don't

Increasing MQTT buffer size in mqtt.c at line 179 from 480 to 512 bytes seems to fix the problem. Can you confirm?

I am pretty sure I tried that out 2 days ago and uploaded the new firmware via OTA onto my D1 mini, but it still did not send the message, double checked that with mqtt explorer.
Manually building and sending the message to the topic works, and the value also did get updated for a day, but that only worked until a restart of home assistant I believe

It's definitely a MQTT buffer size issue. Actually it has to be increased to at least 672 bytes. Buffer size for the serialized JSON has to be set to 592 bytes and the StaticJsonDocument to 640 bytes accordingly. I'll release a new version with adjusted buffer sizes in mqtt.c shortly after few more tests.
Output of new function publishJSON() in mqtt.c which now explicitly checks for JSON overflow after serialization and the MQTT publish return value using a MQTT buffer of 672 bytes in mqttInit():
Sending home asssistant MQTT auto-discovery message...
MQTT homeassistant/sensor/wifipowermeter-123456/pulse_count/config (341 bytes)
MQTT homeassistant/sensor/wifipowermeter-123456/total_consumption/config (424 bytes) <- OK
MQTT homeassistant/sensor/wifipowermeter-123456/current_power/config (406 bytes)
MQTT homeassistant/sensor/wifipowermeter-123456/signal_strength/config (352 bytes)
MQTT homeassistant/sensor/wifipowermeter-123456/runtime/config (340 bytes)

Same with current and way too small MQTT buffer size (480 bytes):
Sending home asssistant MQTT auto-discovery message...
MQTT homeassistant/sensor/wifipowermeter-123456/pulse_count/config (341 bytes)
MQTT homeassistant/sensor/wifipowermeter-123456/total_consumption/config failed! <- ERROR, not published
MQTT homeassistant/sensor/wifipowermeter-123456/current_power/config (406 bytes)
MQTT homeassistant/sensor/wifipowermeter-123456/signal_strength/config (352 bytes)
MQTT homeassistant/sensor/wifipowermeter-123456/runtime/config (340 bytes)


Fixed Decision Flow

the fixed decision flow is useful to define a predetermined flow - you add the tool and attach choices to it, which then gets matched to the AI's input once your tool is called
added FixedDecisionTool and FixedDecisionChoice with icons
added the returned text to the setMessages since the returned answer wasn't updated, probably because it wasn't sent through the websocket

Hi guys,
I've implemented a simple fixed decision flow.

There was an issue with the frontend not setting the latest message's content, most likely because of the returnDirect, please pay extra attention to reviewing packages/ui/src/views/chatmessage/ChatMessage.jsx (that solved it, it only showed the tool usage). I've put the Choice node into the Tools, since I wasn't sure it would fit into Utilities either.
I've attached a simple example use case export: Fixed Decision Flow Simple Example Chatflow.json
(using the return direct and setting the buffer window memory size to 0 is highly advised)

Thanks for the suggestion @Vertirax !
I was thinking of how do we make it work regardless of the chain/agent, because right now it relies on the tool agent. The goal of this is to allow user to skip calling LLM if certain input question is asked, and we match that to a set of predefined output. To do that, we need a type of sequential flow approach. We're currently working on that feature. For now, will keep this PR in draft mode first until we have the new sequential flow approach feature


Building without GL

Can tinyspline be built without OpenGL headers such as gl.h?
I'm getting the error: GL/gl.h file not found
on Xcode and OS X 10.10.

TinySpline itself does not depend on OpenGL. Only the examples provided in examples do so. I can add an example using only C if you wish to.

How can I remove the examples from the CMake build procedure?

How can I remove the examples from the CMake build procedure?

CMake should exclude the examples if OpenGL is not available by its own... Maybe there is a bug in my CMake files?
The easiest solution is to create the build files directly from the CMake file located in the subdirectory library:
mkdir build # create you build directory
cd build
cmake ../library # create build files

It does not seem to exclude the example folder, rather it tries to build them.

You could delete the line add_subdirectory(example) in file: https://github.com/retuxx/tinyspline/blob/master/CMakeLists.txt#L5. I will have a look at the CMakeLists.txt of the examples.

Maybe the current version enables you to build the examples of TinySpline.

According to https://github.com/retuxx/tinyspline/issues/20 you are able to compile the examples. Thus, I'll close the issue


No Documentation

Thanks for this resource but do you mind creating a readme or some documentation page?

@Samshal I'm asking the same question... I think you might want to fork and create one?

Sorry about that.
This project is quite old and I'm not even happy with the API design anymore. I was considering to rewrite it a few times but didn't find the motivation to actually do it.
Feel free to send a PR to add an actual readme, you'll find two examples on how to use it in the samples directory.


tslint --fix produces syntax errors

Bug Report

TSLint version: 5.16.0
TypeScript version: 3.5.1
Running TSLint via: CLI

Reproduction
This seems to be the same issue as #2862. I am seeing the issue with a custom TSLint rule whose fixer should do nothing but add a blank line over some statement nodes.
Repro steps:

Download tslint-repro.zip
Run these commands:

npm install
npm install --dev
node_modules\.bin\tsc tslint-rules\statementPaddingRule.ts
node_modules\.bin\tslint -p tsconfig.json -c tslint.json --fix

TypeScript code being linted
This is test1.ts in the ZIP file.
export function foo(): any {
    return () => {
        doSomething();
        const a: string = getSomething();
        if (getSomething()) {
            if (getSomething()) {
                const bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb: any = getSomething(
                    "foo"
                );
                if (getSomething()) {
                    const c: any = getSomething();
                    if (getSomething()) {
                        doSomething();
                    }
                }
            }
        }
    };
}

function doSomething(): void {

}

function getSomething(foo?: any): any {

}

Actual behavior
export function foo(): any {
    return () => {
        doSomething();
        const a: string = getSomething();

        if (getSomething()) {
            if (getSomething()) {
                const bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb: any = getSomething(
                    'foo',

                if (getSomething()) {
                    const c: any = getSomething(

                    if (getSomething()) {
                        doSomething();
                    } }
                } }
            }
        }
    };
}

function doSomething(): void {

}

function getSomething(foo?: any): any {

}

Expected behavior
The fixer should just add blank lines above some statements, but TSLint doesn't seem to apply the fixes sequentially. It seems like it tries to apply them all at once, and fixes further down probably operate on the old file content, even though previous fixes had shifted it, which messes up the final result.
I checked the repro steps in #2862 (the content is in test2.ts, and the rules that #2862 used are included in my tslint.json), and test2.ts is actually fixed correctly, as part of the same tslint --fix command.

I think this is essentially the same as #2556, which, unfortunately, is unlikely to get resolved since TSLint is being deprecated soon (#4534).

🤖 Beep boop! 👉  TSLint is deprecated 👈  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


Deployment Failed with "Conflict" on provisioning Web

Deployment Failed with "Conflict" on provisioning Web :

Resolved with this : "Update App Service Plan tier like S2 or S3."


fix fetch offset when topic is null

bug fix for https://github.com/streamnative/kop/issues/202

@dockerzhang Thanks for the help on this. it would be better to add an test case for this fix.


Revert "install-powershell.sh: Adding autodetection of curl / wget" due to regression

Reverts PowerShell/PowerShell#7893
@DarwinJS  This regressed the script.  https://travis-ci.org/PowerShell/PowerShellGet/builds/435897616

Ok I fixed the indenting which shows a couple badly closed if statements.  What is next - can you cancel this revert?

@DarwinJS  Can you open a new PR?

@SteveL-MSFT  Perhaps we should move these to a separate repo?  PowerShell-Tools and then we could add a CI system to verify these scripts work at least on a couple of OSs.

@TravisEz13 I don't think it's worth the effort of a new repo just for a few tools.  It would be better to have some tests for these tools since people are depending on them.


Add Nginx for Deployment section in README

As title, this Slim skeleton uses the Apache as HTTP server in the deployment section.
It should add another guide about using the Nginx as HTTP server in the deployment section.
If possible, I can do that. And I need  to know is where I can get started with this?
Thanks.

Where do you found a Apache specific setup description in the documentation?

Hi @odan, thank you for your reply.
I mention that because I found the .htaccess file on this repository and I don't find any setup description on this repo.
I mean we can add the deployment guides for this repo and let developers build easily.
I think we can provide the Nginx and Apache guides for building this repository.
Thanks.

If you like, you can add a new installation section here:
https://github.com/odan/prisma/blob/master/docs/readme.md


let staticcheck working in ci

PCP Issue

difficult: easy
score: 50
min score required: 0
Recommended Skills: GO

Description
Let the staticcheck running in ci:
GO111MODULE=on staticcheck ./...

And you need fix  the report firstly:
pkg/btree/btree.go:745:16: func (*node).print is unused (U1000)
pkg/mock/mockhbstream/mockhbstream.go:49:2: redundant return statement (S1023)
server/config/config_test.go:212:24: trying to marshal chan or func value, field *github.com/pingcap/pd/server/config.Config.FlagSet.Usage (SA1026)
server/core/region.go:679:3: should replace loop with regions = append(regions, leaders.scanRanges()...) (S1011)
server/core/region.go:684:3: should replace loop with regions = append(regions, followers.scanRanges()...) (S1011)
server/schedule/operator/operator.go:902:65: x = append(y) is equivalent to x = y (SA4021)
server/schedule/range_cluster.go:30:7: const scanLimit is unused (U1000)
server/schedule/scheduler.go:132:6: should use strings.Contains(name, registerdType) instead (S1003)
server/schedulers/balance_test.go:426:2: field lb is unused (U1000)
server/schedulers/balance_test.go:1215:5: ineffective break statement. Did you mean to break out of the outer loop? (SA4011)
server/schedulers/scatter_range.go:216:2: field scheduleName is unused (U1000)
server/schedulers/scatter_range.go:217:2: field storage is unused (U1000)
server/schedulers/utils.go:146:6: func newTaintCache is unused (U1000)
tools/pd-analysis/analysis/parse_log.go:54:19: error strings should not be capitalized (ST1005)
tools/pd-ctl/pdctl/command/config_command.go:28:2: var schedulePrefix is unused (U1000)
tools/pd-ctl/pdctl/command/tso_command.go:24:2: const physicalShiftBits is unused (U1000)
tools/pd-ctl/pdctl/command/tso_command.go:25:2: const logicalBits is unused (U1000)
tools/pd-simulator/simulator/cases/redundant_balance_region.go:69:40: should use make([]int64, storeNum + 1) instead (S1019)
tools/pd-simulator/simulator/cases/redundant_balance_region.go:70:39: should use make([]uint64, storeNum + 1) instead (S1019)
.....

then add the check into Makefile

/pick-up-challenge


Robot output can crash when piping output

robot . | echo
[ ERROR ] Unexpected error: BrokenPipeError: [Errno 32] Broken pipe
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/robot/utils/application.py", line 83, in _execute
rc = self.main(arguments, **options)
File "/usr/local/lib/python3.7/site-packages/robot/run.py", line 439, in main
result = suite.run(settings)
File "/usr/local/lib/python3.7/site-packages/robot/running/model.py", line 222, in run
self.visit(runner)
File "/usr/local/lib/python3.7/site-packages/robot/model/testsuite.py", line 168, in visit
visitor.visit_suite(self)
File "/usr/local/lib/python3.7/site-packages/robot/model/visitor.py", line 84, in visit_suite
if self.start_suite(suite) is not False:
File "/usr/local/lib/python3.7/site-packages/robot/running/runner.py", line 83, in start_suite
test_count=suite.test_count))
File "/usr/local/lib/python3.7/site-packages/robot/output/output.py", line 51, in start_suite
LOGGER.start_suite(suite)
File "/usr/local/lib/python3.7/site-packages/robot/output/logger.py", line 201, in start_suite
logger.start_suite(suite)
File "/usr/local/lib/python3.7/site-packages/robot/output/console/verbose.py", line 36, in start_suite
self._writer.suite_separator()
File "/usr/local/lib/python3.7/site-packages/robot/output/console/verbose.py", line 106, in suite_separator
self._fill('=')
File "/usr/local/lib/python3.7/site-packages/robot/output/console/verbose.py", line 112, in _fill
self._stdout.write('%s\n' % (char * self._width))
File "/usr/local/lib/python3.7/site-packages/robot/output/console/highlighting.py", line 53, in write
self.flush()
File "/usr/local/lib/python3.7/site-packages/robot/output/console/highlighting.py", line 66, in flush
self.stream.flush()
Exception ignored in: <_io.TextIOWrapper name='' mode='w' encoding='UTF-8'>
BrokenPipeError: [Errno 32] Broken pipe

It seems to depend on which command the output is piped to. For example, | less and | tail seem to work fine but | echo and | head cause problems.

OK, I think I know what's going on.

The reason | echo fails is that echo does not read stdin but only prints its arguments and then exists and that breaks the pipe. Related to that, command | echo basically never makes sense. Use command | cat instead.
The reason | head fails is that it (by design) exists and closes the pipe immediately when it's got enough info. Unlike command | echo, command | head is actually useful.

Python's docs actually explain the problem and also explain why disabling SIGPIPE signals is not a good solution: https://docs.python.org/3/library/signal.html#note-on-sigpipe
Now the real question is, how should we handle this? Options include:

Do nothing. Let the program crash. Close this issue.

Handle exception and exit gracefully. That's what the example in the docs referenced above do. In addition to that we should add some error reporting that execution was stopped due to a closed pipe. This fix should probably go to robot.utils.Application.

Ignore broken pipe and run test until the end. AFAIK pipes are typically line buffered so it ought to be enough to add try/except around self.stream.flush() in HighlightingStream. I already tested that it works at least with | head. It can be a bit strange that the output is cut but execution continues, but then again you are explicitly using head and stopping execution doesn't feel that good either.

What do you think @mkorpela?

I tested piping with head command to answer a question on RF slack about removing 3 last rows of output (that contain the locations of output, report and log files). I was thinking something like robot ... | head -n -3 (this does not work on OSX (as it is BSD derivative) but works on GNU derivative linuxes).
In this case the correct option would be number 3.
Just continue execution although output will not go anywhere.

Option 3 feels best to me as well.


Bug with resizing frame after frame is set first time

Hey nice work on the sticker view. I'm having an issue though. Here's what I'm doing...

init and create the sticker view and set the frame
the user can edit the contents inside the sticker (the content view) and sometimes this requires the frame size to change.
ive noticed if the user has previously resized/rotated the view before step2 and in that step the content view frame had to change, if the user then tries to go back and resize/rotate with the handles... the sticker view gets "wonky"... it starts to shrink exponentially and it basically breaks and becomes unusable for the user...

I hope that makes sense... I've tried to go in and tinker around to see if i could fix it... but so far I havent been able to. I'm wondering if the deltaAngle variable needs to be updated based on the new frame or something?
Thanx again for your work and releasing it... I hope you might have a few minutes to look into this, or at least maybe point me in a direction to fix it! Thanx!

Nevermind, I figured it out... it was a problem with the custom code i added. Closing issue... great work by the way!


Incompatible with jekyll 3

Trying to build a site using jekyll 3.1.2 fails with the following Error:

jekyll 3.1.2 | Error:  undefined method `template' for class `Jekyll::Post'

On jekyll 3.1.2 i get
Error:  undefined method lang' for #Jekyll::Drops::UrlDrop:0x007fb2ea984460`

I think we need to rethink the whole multilingual thing.
With Jekyll 3 and the collections, things are much easier now.
After digging deeper into the code and this topic, I'm not sure yet what we even need from the existing plugin anymore.
So far my thinking goes in this direction:

Have different collections for each language
Keep the translations and crossposts
kick out everything that is related to separating posts for different languages (e.g. posts_by_language)

I'm trying to create a multilingual site and getting the same error as @Gondlar. I tried using collections first as @drallgood has suggested, and while it did work, I was only able to paginate the main language blog. The collections would list all posts in a single page. The Octopress Pagination gem readme file discusses multilingual pagination, but I can't get it to work per the aformentioned build error.
I'd be perfectly happy to continue using collections as that is working, if anyone knows how to get pagination to work with collections.

@bradonomics
I had to modify several plugins to get this working properly.
Pull requests are being created right now or have already been created.
You can follow my progress on the multilingual plugin here, if you like: https://github.com/drallgood/multilingual/tree/jekyll3


Potential unintentional panics in the codebase

The command cargo clippy -- -D 'clippy::panic_in_result_fn will reveal several instances of panics occurring within a block returning a result.
Some of there are warranted and unrecoverable (e.g. unreachable! in eval, or assert! instances in many cases). Some are probably not warranted and could probably be recovered (e.g. some instances of .unwrap in src/writer.rs's Write<F> for Expression<F> [^1]).
In the later case, we should fold the error management within the error case of the Result.
[^1]: see also cargo clippy --fix -- -D 'clippy::unwrap_in_result'

Hi team,
Can I work on this issue?

In the later case, we should fold the error management within the error case of the Result.
This means we will change 'unwrap' and 'expect' to Err in the functions found by cargo clippy --fix -- -D 'clippy::unwrap_in_result'.

Thank you!

Sure, go for it 👍🏼


Fix installation instructions

Fixes #32.

I am just going to merge this simple fix to get things done. If there are any objections, I can wait longer next time.


Clean up how we log + time

We currently do a few hand-coded timing of steps. But maybe we should be more systematic and make a timing helper that we can use to "just" wrap specific functions (rather than starting a timer then stopping at the top|bottom of each)

Yeah, removing it is fine too, I guess really we would want to truly profile code like that when experimenting with speedups (e.g. confirming that our partitioning in dbgen works well, when we tackle tpc-ds, etc.)


Implement conditional availability of indicators

Some indicators may not be available for certain cities. Implement that (right now if you click in a indicators that is not available it simply stops the application)

List:

[ ] When a indicator is selected in the world view, cities without this indicators should be greyd out (with popup saying the city is not available for this indicator);
[ ] When a indicator is selected in the city view, the indicator panel should grey out the indicators that are not available - and they should not be clickable;
[ ] The list of cities above should be complete. If the user clicks on a city that doesn't have the current indicator, travel to the city and reset to a indicator that the city has available

This one is not necessary right now - all indicators are available for all cities. But I'll keep it open as a reminder.


[Request] allow fps lower 60

why not?

It's actually the same as how RobTop implemented it, because I copied some of the code from the game.
I could set it to let's say 10 or 15 fps, but i'm not sure there are a lot of use cases.

Changed minimum number to 30 in https://github.com/Prevter/GDOpenHack/commit/c81dea201a57646b5f492e087f4b5aeea00ccdf9


Saving issue with Raknetify

https://modrinth.com/plugin/raknetify
Chest colours were not saved after relogin on servers with prefix. Could you investigate into that please?

Could you send over colorizer.csv? It will make it easier to investigate the issue

colorizer.csv


GDI Error when using Base64QRCode

Type of issue
[x ] Bug
[ ] Question (e.g. about handling/usage)
[ ] Request for new feature/improvement
Expected Behavior
Using the Base64QRCode.GetGraphic() method should not cause a GDI error.
Current Behavior
Under certain conditions (low memory?) calling Base64QRCode.GetGraphic() results in a GDI error.
Possible Solution (optional)
We worked around this by using QRCode.GetGraphic() and doing the base64 conversion ourselves.
We think the problem stems from not properly disposing of the bitmap within Base64QRCode.GetGraphic()
This broke on our production server (but worked in development):
var subject = "Simple Email Test";
var body = "We used a pretty long string. That may be a factor? It was roughly 200 characters long.";
var mailPayloadGenerator = new QRCoder.PayloadGenerator.Mail("", subject , body);
var qrCodeData = new QRCodeGenerator().CreateQrCode(mailPayloadGenerator.ToString(), QRCodeGenerator.ECCLevel.Q);
var qrCodeString = new Base64QRCode(qrCodeData).GetGraphic(3);

This fixed it:
string qrCodeString = null;
var subject = "Simple Email Test";
var body = "We used a pretty long string. That may be a factor? It was roughly 200 characters long.";
var mailPayloadGenerator = new QRCoder.PayloadGenerator.Mail("", subject , body);
var qrCodeData = new QRCodeGenerator().CreateQrCode(mailPayloadGenerator.ToString(), QRCodeGenerator.ECCLevel.Q);
using (var bitmap = new QRCode(qrCodeData).GetGraphic(3))
using (var stream = new System.IO.MemoryStream())
{
    bitmap.Save(stream, ImageFormat.Png);
    var imageBytes = stream.ToArray();
    qrCodeString = Convert.ToBase64String(stream.ToArray());
}

Steps to Reproduce (for bugs)
This is the toughie. It broke on some machines and not others. Most likely, you'd need to test while the system is starved for RAM. The only thing noteworthy beyond that is we are using rather long text (~200 characters).
Your Environment

Version used:  1.3.2
Compiled from source or NuGet package?:  Yes
Payload/Encoded text:  ~200 characters of text for an email
Used payload generator:  Mail
Used ECC-level:  Q
Used renderer class:  None (we send the base64 string to a browser)
Environment: .NET 4.6

Hi @ctsears ,
many thanks for this bug report. (It does not often happen that the report is that detailed.) I tried to reproduce your problem, but couldn't produce a GDI error.
I tried to create 10000 Base64QRCodes in a loop, but the Garbage Collector managed to keep the memory usage at a constant low level. After that I tried to create 10000 BAse64QRCodes in a Parallel.For-loop. This ended in a OutOfMemory-exception - but this isn't a bug. If no memory isn't available, the best code can't do anything...
Nevertheless I see an improvement in you "fixing solution". Using a using clause for Bitmap and MemoryStream seems to be a good idea. So I implemented it in this commit: https://github.com/codebude/QRCoder/commit/41543039c8884e896fb40e4f011f08353794d465
I hope this fixes your problem. Since I can't reproduce the bug, I close this issue with this comment/commit. Nevertheless - feel free to comment or give feedback if this solved your issue or if you know a way to re-produce the error.


Enter key to move down

With less (and partners) one can use the enter key to move down. I realize that I can achieve this with
TerminalPager.set_keybinding("<enter>", :down)

but I would vote for having this as an (additional) default. What do you think?

Hi @carstenbauer !
I have no opinion on this! However, if less uses this as default, I think we should also use it here.


Tooltip issue: "TypeError: tooltipTrigger.outerWidth is not a function"

Hi!
I have some problems with tooltip. When I hover over item tooltip doesn't show up. In console it says
TypeError: tooltipTrigger.outerWidth is not a function
I think that issue come out after updating angular to 1.4 version

Hi!
We have not yet tested LumX with Angular 1.4. We're only managing stable version of Angular for now. But it might be linked to jQuery instead. We did not have time to make LumX work without jQuery, and outerWidth is from jQuery.
Do you have jQuery in your app ?

Yes I do.
Here are all js files that I am using.

From the FAQ of Angular:
between 1.3.15 and 1.4.0 there will be a number of breaking changes

So yeah, it might not work. We won't fix it for now, only when the 1.4 will be stable as the Angular team might change everything from a non-stable version to another.

Okey. Thanks for response anyway :)

same error with angular 1.3.13, on ionic based project

tabs directive in a blank ionic framework app gives this error. I have angular 1.3.13 as rayjax mentioned.


[Coverage] Refactor SIL generation for profiling

This patch moves the ownership of profiling state from SILGenProfiling
to SILFunction, where it always belonged. Similarly, it moves ownership
of the profile reader from SILGenModule to SILModule.
The refactor sets us up to fix a few outstanding code coverage bugs and
does away with sad hacks like ProfilerRAII. It also allows us to locally
guarantee that a profile counter increment actually corresponds to the
SILFunction at hand.
That local guarantee causes a bugfix to accidentally fall out of this
refactor: we now set up the profiling state for delayed functions
correctly. Previously, we would set up a ProfilerRAII for the delayed
function, but its counter increment would never be emitted :(. This fix
constitutes the only functional change in this patch -- the rest is NFC.
As a follow-up, I plan on removing some dead code in the profiling
logic and fixing a few naming inconsistencies. I've left that for later
to keep this patch simple.
rdar://32588741 (& 36061003)

@swift-ci please smoke test

Hey @slavapestov and @shajrawi, mind taking a look (possibly after the winter break :)?

@swift-ci please smoke test

This looks good. I'm curious why you decided to put the profiler instance in SILFunction and not SILGenFunction though -- presumably after SILGen we never need to create a profiler instance again, unless you think the optimizer will need to bump these counts too?


Implement bar searching API calls

Most likely using ORS's POI API or Google Maps API

Addresses still do not work


How can I use two MFRC522 with one Arduino Mega?

Please, I don't know how to use two MFRC522 with one Arduino Mega.
I tried to use 2 differents SS, but not work.
Thank you very much.

The library have a huge documentation. Actually, in README file there is the PIN layout that you need to use to work properly in Arduino Mega.
SS can be literally any digital output, try to use another one.
Best regards!

Hi @ViniciusMoscardini
Also, please check the example examples/ReadUidMultiReader/ReadUidMultiReader.ino by @lmmeng
Greetings.


[feature-request] To add support for lambda expressions

This is a PR for the issue #14650.
I have added the parsing of lambda expression in the CalciteSqlParser class and further continuing to tweak the code.

Hello @maintainers,
This is not the final PR I need to add more commits.
Please help me for further progress.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (59551e4) to head (243a69e).
Report is 1497 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (243a69e). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (243a69e)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
0

skip-bytebuffers-false
7
1

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14699       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <ø> (-61.75%)
:arrow_down:

skip-bytebuffers-true
?

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


adding email alias

Amplify CLI Version
12.1.1
Question
I have an amplify app grown up from version 5 up to now inclusive a painful migration to transformer v2.
Now the first user wants to change the email address. No problem there is a workflow to change the attribute email. But the user can't login with his new email address. He needs the old one which is still in the name. So I learned I need a login alias email. How can I configure it. When I fire amplify update auth and go thru all steps there is no alias question.
Is the perhaps a possibility to change the name also ?
In the name the old email is in Cognito (thru the console) in the email the new one.
How can I login with the new email address ?

Hey @ErhardScampi, thank you for reaching out. The Cognito sign-in attributes cannot be modified once the user pool has been created. Amplify CLI  provides the capability of adding Alias attributes using the feature flag forceAliasAttributes in the amplify/cli.json, but would require us to recreate the Cognito user pool.

A workflow to change the attribute email currently exists, but the user can't login with his new email address.

Curious on what occurred here, could you provide us some on how the auth resource and workflow is currently configured?
Additionally, information on the behaviour the user observed on a login post updating the email address and if you observe the user being updated on the Cognito user pool?

Closing due to inactivity


Stop attributes = "0" from being removed

Hi I can't see if there's a SVGO plugin which I can use to stop attributes which ="0" from being removed. e.g. x="0". An error is thrown in dev tools when trying to animate that attribute. Is there one/parameter to stop this from happening?

Well, x="0" is a default value and thus removed by removeUnknownsAndDefaults plugin.

Thanks for the heads up! :-)


Fractional time with zones fails to parse correctly

This is a valid datetime:
2016-05-21T00:47:46.873709+00:00
Error: [$parse:syntax] Syntax Error: Token 'T01' is an unexpected token at column 11 of the expression [2016-05-21T01:00:59.390463+00:00] starting at [T01:00:59.390463+00:00]

"If necessary for a particular application, the standard supports the addition of a decimal fraction to the smallest time value in the representation."
https://en.wikipedia.org/wiki/ISO_8601

Seems like an error thrown by the Angular template compiler. You probably need to wrap the string you are passing with quotes.


Godot 3.5RC1 Crash/Closes on startup.

Godot version
3.5RC1
System information
OS: Microsoft Windows 10 Home - Version 10.0.19044 Build 19044; RAM: 8,014 MB; Processor: Intel(R) Core(TM) i5-10300H;  GPU: NVIDIA gtx 1650 ti with max q design - driver version 471.68
Issue description
When starting the Godot executable, the initial project selection window appears for a brief second then automatically closes, whilst the window displays it isn't interactable to any extent.
Steps to reproduce
Run Godot.
Minimal reproduction project
No response

Hmmm, this may be because the crashing build is a c# mono build whereas my source built one isn't, not sure how to create the mono version yet. I'll report back on that when I find out how.


How to "reset" props.files?

Hi there,
I'm using vue-transmit on a project, and I would like to "reset" the files slot which is shown in the example. I'm emitting a custom event once a file has been uploaded, and I'd like to use this even to trigger this cleanup. I've tried looking in the vue-transmit doc as well as in the vue doc but couldn't find a way to do so. Can anyone help me?

Do you want to clear the underlying file input, component data, or both?

I'm using vue-transmit for blog image covers.
At first I think I'd like to clear the component data, for when a cover has been successfully uploaded.
Then, since I have a "remove cover" button, I guess I'd like to clear both the underlying file input and the component data.

I would personally recommend using vue-transmit to add those files to your own parent component's data where you have full control, but that certainly doesn't fit every use case. Just food for thought if you haven't considered it.
VueTransmit.removeAllFiles(cancelInProgressUploads = false)
This is the method you'll want to use to clear the component's data array of files. You can pass true to cancel any uploads that are in progress at the time of removal. To call this, place a ref on <vue-transmit ref="vtransmit" /> inside your template, and then once the mounted hook is called, your ref will be populated:
this.$refs.vtransmit.removeAllFiles(true)

As for the file input, that is actually clear on every change event to avoid some browser implementation quirks. Each change event basically scoops out the files and put them in the component instead.

@fbnlsr, let me know if this solve your issue!

@alexsasharegan hey sorry I wasn't able to test your solution as I was out for a few days. I've tried implementing your suggestion but I get an error in the console: Error in event handler for "uploadedImage": "TypeError: this.$refs.vtransmit.removeAllFiles is not a function"
I'm not sure how to deal with that error. 🤔

Can you drop in your component code? It's definitely a function, so something is going wrong elsewhere.

I've put it in a gist, here: https://gist.github.com/fbnlsr/d6d45e825829c45319dba40faa84109a#file-postform-vue-L265

Hey @alexsasharegan thank you so much for your time. Here is the partial: https://gist.github.com/fbnlsr/8aa610665584fd71d09e56d2e396e717

I got it to work! I was thinking about what you wrote and you were right, I had to put the function inside my partial. Thanks again for your help! :)

Nice! Glad we were able to figure it out!

@alexsasharegan I've just noticed something. It seems that if I try to upload a bunch of files, removeAllFiles also removes files that are waiting to be uploaded. It does not remove the files being currently uploaded thanks to its false argument flag but all the other files vanish. Is there another method that could empty only the finished uploaded files from the queue?

@fbnlsr, you can combine the filtered files arrays with the removeFile method to just remove the files you want. Here's all the filtered lists that you can choose from:
let filesToDelete = [
  // copy the array values into your own array
  ...this.$refs.vtransmit.acceptedFiles,
  ...this.$refs.vtransmit.rejectedFiles,
  ...this.$refs.vtransmit.addedFiles,
  ...this.$refs.vtransmit.queuedFiles,
  ...this.$refs.vtransmit.uploadingFiles,
  ...this.$refs.vtransmit.activeFiles,
];

for (let file of filesToDelete) {
  this.$refs.vtransmit.removeFile(file)
}

Thanks! Is there a filtered list for the succesfully uploaded files?

Hmm... there isn't. I'll add one. How does a method called removeFilesWithStatus(...status: string[]) sound?

That sounds perfect. We should be able to pass an array of different status as well, don't you think?

The ... means it's a variadic function—it will accept any number of arguments.
vm.removeFilesWithStatus('added', 'queued', 'uploading');
// if you have an array, just spread the array into arguments
vm.removeFilesWithStatus(...['added', 'queued', 'uploading']);
// or via the backwards compatible method
vm.removeFilesWithStatus.apply(vm, ['added', 'queued', 'uploading']);

That sounds pretty good then! 👍

Are you using the beta version? Or version 8?

We're using v8.0.0 atm but since we're still in the development phase of the app, we could switch to a beta version I guess.

I'll see if I can make the adjustment to 8 as well. I'll post back once I have a release.

Awesome, thanks a lot!

Alrighty, 8.1.0 is available now. Try it out and let me know if it works!

Hey @alexsasharegan  I completely forgot to keep you updated about this issue. The update you've pushed does the job perfectly. Thanks a lot! 👍

Awesome! Glad to hear it!


Teams Engineering CPM is telling us 25k Teams already shipped to GCC

The documentation still lists 10k as the limit for members in a team, and then has a callout below that says the limit in GCC is only 5k. Our Teams Engineering CPM is telling us that the limit was increased to 25k in GCC.

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

ID: 905e2c09-ef3e-07cc-0809-6ff171157c47
Version Independent ID: c0d33162-183d-fff8-32e9-a999f391ea51
Content: Limits and specifications for Microsoft Teams - Microsoft Teams
Content Source: Teams/limits-specifications-teams.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

@npherson  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Update readme files

Fixes https://github.com/oliverlee/phobos/issues/182.

Leaf READMEs should contain:

[ ] short description of what is done
[ ] sample rate
[ ] loop rate (if different than sample rate)
[ ] transmission rate (if different than sample and loop rate)
[ ] description of transmitted message
[ ] list of sensor and drivers that are used.

@mickvangelderen I think this is done.


Map, scale colors are inconsistent across geographies, measures

From Jan (paraphrased): It can be disorienting to see the colors change as you select different measure categories, measures, and geographic groupings (county vs. tract). Since the colors depend on the dataset, you can't use specific colors as a means to compare across different measures.
Background: The map colors are generated by taking the minimum and maximum values (aka the "extent") of the currently-visible dataset, then generating a set number of steps between. Some measures are percentages, while others are literal values.
Options:

scale each measure separately across its county and tract values

issues: doesn't provide color consistency across measures

find a global min, max across all measures

issues: wouldn't work well for percentages vs literal values

allow the user to specify that they want an absolute scale, and then to specify the min and max values for that scale

issues: user might become disoriented switching between, e.g. percentages vs. literals, or measures with wildly different extents

Some things that would help flesh out this issue and make it more concrete:

[ ] examples of pairs of measures where the difference is extreme
[ ] user stories, i.e. specific users who would want this feature
[ ] other options on how to present the data

This is my gut feeling on this:
The behavior we have now should remain the default behavior. I think it's natural and expected that if you change a measure (or any other "input"), the map/scale visibly changes. It's different data. We're talking about catering to a narrower scenario (I think) in which someone is switching from one measure to a directly related one -- for example black vs. white cancer incidence -- and seeing the difference. That said, I still think this is a good option to have somehow, especially given the key nature of that example. Regardless of the solution we choose, I think the behavior should be opt-in by the user, so they're aware they've done something that might prevent them from seeing data properly.
I'm leaning toward the following solution:
Have two number boxes above the "More Options" called "Min/max". They start off in "automatic" mode where they reflect the true min/max range of the selected data. Once the user edits one or both of them, though, they set them to "manual" mode, and a little button appears next to them to reset to auto, and they will not change until the user clicks that.
I feel that we should not get into the hairiness that arises from trying to "smartly" figure out what the "global" range should be for the measure the user is viewing. Not only are there different types of values (%s vs. per 100k vs. absolute count vs. rankings), but there are different subjective groupings (e.g., perhaps "asthma" and "binge drink" shouldn't share the same min/max, even though they are both risk factors and %s, for some ideological reason). Unless someone can come up with a simple and consistent way to make it clear to the user (and ourselves) -- e.g. the range will always be global to the measure category, and if you change the selected category the range should change -- we should probably not do this.

This sounds reasonable, Vince.   Lets keep as is for now.  We can consider changing after getting broader feedback if needed.
Thank you for weighing in.
From: Vincent Rubinetti @.>
Sent: Tuesday, March 19, 2024 2:42 PM
To: colorado-cancer-center/ecco @.>
Cc: Lowery, Jan @.>; Assign @.>
Subject: Re: [colorado-cancer-center/ecco] Map, scale colors are inconsistent across geographies, measures (Issue #49)
[External Email - Use Caution]
This is my gut feeling on this:
The behavior we have now should remain the default behavior. I think it's natural and expected that if you change a measure (or any other "input"), the map/scale visibly changes. It's different data. We're talking about catering to a narrower scenario (I think) in which someone is switching from one measure to a directly related one -- for example black vs. white cancer incidence -- and seeing the difference. That said, I still think this is a good option to have somehow, especially given the key nature of that example. Regardless of the solution we choose, I think the behavior should be opt-in by the user, so they're aware they've done something that might prevent them from seeing data properly.
I'm leaning toward the following solution:
Have two number boxes above the "More Options" called "Min/max". They start off in "automatic" mode where they reflect the true min/max range of the selected data. Once the user edits one or both of them, though, they set them to "manual" mode, and a little button appears next to them to reset to auto, and they will not change until the user clicks that.
I feel that we should not get into the hairiness that arises from trying to "smartly" figure out what the "global" range should be for the measure the user is viewing. Not only are there different types of values (%s vs. per 100k vs. absolute count vs. rankings), but there are different subjective groupings (e.g., perhaps "asthma" and "binge drink" shouldn't share the same min/max, even though they are both risk factors and %s, for some ideological reason). Unless someone can come up with a simple and consistent way to make it clear to the user (and ourselves) -- e.g. the range will always be global to the measure category, and if you change the selected category the range should change -- we should probably not do this.

Reply to this email directly, view it on GitHubhttps://github.com/colorado-cancer-center/ecco/issues/49#issuecomment-2008092654, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBPI3KFFJN4YW4AR5TWYPZDYZCPKTAVCNFSM6AAAAABE6IAHI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBYGA4TENRVGQ.
You are receiving this because you were assigned.Message ID<EMAIL_ADDRESS>


Which tracking node should be used?

Hi,
I am seeing two tracking node, kf_track and klt_track. May I know which tracking node is good to be used?

Sorry for late reply.
I think klt track is better than kf track


Add guidelines on open source development for Eclipse Tractus-X

We should provide some documentation, guidelines and good practices for the Eclipse Tractus-X community and everyone thinking about joining.
This section should contain:

links to important documents for Eclipse Foundation Projects.
Guidelines on how to join the community
Checklists for Contribution reviews
...

Already worked on in branch docs/add-oss-info-to-developer-hub
Suggestions and feedback welcome

Issue can be closed by now. Initial section is already present and will be constantly improved


add support for azure open ai embedder

Similar changes as https://github.com/Abraxas-365/langchain-rust/pull/41.
I changed from Vec<64> to Vec<32> as openai seems to use 32.

Is there any Embedder which uses Vec?

There are parts on the code, which transform the Vec to Vec
src/vectorstore/pgvector/pgvector.rs : 139
src/vectorstore/pgvector/pgvector.rs : 222

I was hoping to avoid mapping, but for now I have set it back to f64.


updated aws-configs

What this does
Fixes issues with our current broken implementation of S3 and static folders.
This PR:

Removes lines 306 & line 308, right now these lines break the ui of the app when USE_AWS_STORAGE is set to true. Line 306 STATICFILES_STORAGE = "{{ cookiecutter.project_slug }}.utils.storages.StaticRootS3Boto3Storage" sets s3 as the static directory (referencing a function in a file that does not exist) and 308 sets the url for each of these files to point to s3 STATIC_URL = f"https://{aws_s3_domain}/static/". However line 314 STATICFILES_STORAGE = "whitenoise.storage.CompressedManifestStaticFilesStorage" overrides the the variable back to whitenoise. This means the static files referenced do not exist.

Removes the core/handlers file and creates the utils/storages file instead. Line 305 sets the PRIVATE_MEDIA_LOCATION to s3 but is pointing to a function in a file that does not exist (prior to this PR)

Line 294 is updated to check if the app is a review app in Heroku and ignores AWS storage. There are a few reasons for this. If we were to use aws storage as is we would need to create a pipeline variable for the AWS_LOCATION variable to save to, additionally when the tear down occurs we would need to delete the folder. So until this work is done I disabled USE_AWS_STORAGE for review apps.

[Jira ticket](Paste Jira link here)

Need rebasing and fixing tests


Select element takes focus from input element on react native web on Safari browser

Description
Only a single character is accepted on controlled input when a Select element is present
CodeSandbox/Snack link
https://snack.expo.dev/MOBQ7fNEN
Steps to reproduce

On Safari browser
In Expo snack, type a letter in input component - shows up
Type another letter - It doesn't show up

NativeBase Version
3.4.7
Platform

[ ] Android
[ ] CRA
[X] Expo
[ ] iOS
[ ] Next

Other Platform
Web - Safari
Additional Information
I think it is the internal input element of a Select element which takes focus.

Hi @jvzTrifork, Thank you for reporting this issue. We will look into it.

Hi there. We have the exact same problem. Do you have any workarounds? Or when will it be updated? We have a big form and lots of Safari users...but changing it to another Select element is painful...

We ended up downgrading to version 3.4.6 which does not have this bug.

Any update on this issue?

Also experiencing this, version 3.4.19. Does anyone know of a compatible Select element for a replacement?

Also experiencing this. Has there been any progress made on this issue?

Any update?

We have this issue too. I'd appreciate any workaround or fix, or even suggestions to other select libraries.
@Krithikj20

not only on Safari, mobile Chrome also has this issue. Any update?

@lts-po and I made a work around in our codebase for this issue by creating two custom components that inherit Select.
The first is basically a no-op but needs to wrap Select from native-base
https://github.com/spr-networks/super/blob/main/frontend/src/components/Select.js
The second is for the web clients
https://github.com/spr-networks/super/blob/main/frontend/src/components/Select.web.js
Here is the implementation
import React from 'react'

import { Select as NBSelect } from 'native-base'

const Select = (props) => {
  const isSafari = () =>
    /Safari/.test(navigator.userAgent) &&
    /Apple Computer/.test(navigator.vendor);

  return (
    <NBSelect {...props} selection={isSafari() ? 1 : null}/>
  );
};

Select.Item = NBSelect.Item
export default Select
export { Select }

Mobile Chrome for iOS has the same issue.

Mobile Chrome for iOS has the same issue.

Yes confirm. Maybe this problem has disappeared in Glustack-ui?


Bind raw HTML

Where agile.js:596 has $node.text(self.model.get(bindData.key).toString()); it might as easily use .html, permitting bindings to inject html instead of text.
I don't see why this isn't the default, as it's useful behaviour.  If it weren't to be the default, it could be conditioned by another data- attribute, say data-bindhtml or somesuch.

I'd also like to suggest that some $node elements would sensibly default to .html() - s for example, where others might more sensibly default to .text() -  for example (although even they might have e.g. )

Using .html() by default is problematic from a security point of view, it'll make the application very vulnerable to XSS attacks.

I do not see that the use of .html() per se provides a vector for XSS attack under jQuery, or therefore under agile.js, as users can't inject HTML - I'm talking about the single-direction value binding - all the HTML has to have been supplied by a server which was trusted to provide .js to the client in the first place.

Even when those values eventually come from the server, in many cases they would be originally user-generated content. For example, a user could comment on a website, get it stored to the database, and than the comment would get fetched from the server into a client-side model and bound to a DOM element. The content of his comment would get inserted as raw HTML into the DOM, rather than as text.

Also, probably more important than the XSS concern - in most cases you'll have regular text and not HTML, and it should be treated as such. Treating plain text as HTML would cause it to render incorrectly if it contains characters that have special meaning in HTML.
imho the default should be text, but it might be a good idea to allow HTML using some option.

Yes, I think so.  It's sometimes necessary.


feat: update lane change (v0.7.0)

Description
Hotfix to beta/v0.7.0
lane change update
https://github.com/autowarefoundation/autoware.universe/pull/2575
https://github.com/autowarefoundation/autoware.universe/pull/2428
https://github.com/autowarefoundation/autoware.universe/pull/2359
https://github.com/autowarefoundation/autoware.universe/pull/2599
https://github.com/autowarefoundation/autoware.universe/pull/2615
https://github.com/autowarefoundation/autoware.universe/pull/2645
https://github.com/autowarefoundation/autoware.universe/pull/2693
https://github.com/autowarefoundation/autoware.universe/pull/2517
https://github.com/autowarefoundation/autoware.universe/pull/2442

Related links

Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

Codecov Report

:exclamation: No coverage uploaded for pull request base (beta/v0.7.0@9a8cd1d). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@              Coverage Diff              @@
##             beta/v0.7.0    #255   +/-   ##
=============================================
  Coverage               ?   3.01%
=============================================
  Files                  ?     165
  Lines                  ?   16802
  Branches               ?    7941
=============================================
  Hits                   ?     506
  Misses                 ?   15891
  Partials               ?     405

Flag
Coverage Δ

differential
3.01% <0.00%> (?)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Extension fails to load due to failing Galaxy API request

Bug Report
Extension fails to load due to failing Galaxy API request.
Possible Solution
This is due to Ansible Galaxy recently updating their API's over the weekend. We should also find better ways to handle these failure instead of causing the extension to hang during activation

Fixed in PR https://github.com/IBM/operator-collection-sdk-vscode-extension/pull/59


chore(Mutations): respond to comments on PR #720

Responding to @josecorella comments on #720 .
Verification failure is due to:

Key Store Admin's Index.dfy not proving Fresh, which has been a long standing issue with the Admin
In AwsCryptographyKeyStore/test/Storage/TestGetItemsForInitializeMutation.dfy, the test assumes type is in the Encryption Context. It is, but Structure.dfy does not prove that, so it must be proven else where.

But in contrast to https://github.com/aws/aws-cryptographic-material-providers-library/pull/754#issuecomment-2375306014,
It is AWESOME that this PR still has approval!
i.e: @josecorella Approved this PR and the PR that was merged into it.
And GitHub retained that!
Super Groovy.

The KMS Code generation check failed due to throttling by Nuget.


Removechangelog

Description

Fix #XXX

Test

To test this pull request, you can run the following commands:

Additional Information
Tradeoff

Potential improvement

PR created by mistake


IFU 2023-01-11

IFU on 1/11/2023 from main branch of upstream transformers.
Performance of huggingface workload before/after changes, avg taken from three runs each:

model
Vanilla Avg
IFU Avg
% Difference

pyt_huggingface_distilbart_cnn
271.2003333
268.468
1%

pyt_huggingface_bert
227.373
223.9877
2%

pyt_huggingface_bart
217.516
214.9063
1%

pyt_huggingface_distilbert-base
499.859
489.9867
2%

pyt_huggingface_deberta-v2-xxlarge
465.2743333
456.2313
2%

pyt_huggingface_gpt_neo
144.6226667
148.1
-2%

pyt_huggingface_gpt2
407.676
407.542
0%

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Change filenames of .dot and .png files in the release package to reflect the version rather than the date

E.g., rather than
Gist2021-05-03.dot
Gist2021-05-03.png

use
gist9.7.0.dot
gist9.7.0.png

or any other formatting that reflects the version number rather than the date.
(Note also lowercase "gist.")

Boris: output filename option already exists.
@uscholdm creates a spreadsheet with a list of terms including domain, range, definition, etc.

Closing this in favor of a bigger issue of auto-generating documentation as part of the release process.


re-initiating AOS animation when revealing hidden elements conflicts with anchor position

In order to trigger a div to - for example - fade-in it has a default anchor point position and depending on the scroll offset it will animate. But if you're running many divs that some of them need to be hidden (by using some JS and display:none) and load them later (by clicking eg. "Load more" button) that means that if you re-initiate AOS again (using the script below) the just-revealed div will animate after it has been already shown on the screen which obviously doesn't look nice as you want the default to be hidden and not be visible with wrong animation.
So my opinion is that when a new div appears on the screen ( the on-screen-code  was hidden with display:none) it needs to be hidden (this time using opacity). In the background you need to calculate its new position according to the applied code (eg. anchor position etc) and if the offset is already far from the point that it would trigger the div to animate (if the div was visible in the first place) then it needs to remain hidden and have it animate when you scroll back to the top and then back down again.
 <script>
        $(function() {
      AOS.init({
        easing: 'ease-in-out-sine'
      });

      $('.js-load-more').on('click', function() {
        var $content = $(this).next('.js-more-content');

        $content.animate({
          height: 750,
        }, 500);
      });

      onElementHeightChange(document.body, function(){
        AOS.refresh();
      });
    });

    function onElementHeightChange(elm, callback) {
        var lastHeight = elm.clientHeight
        var newHeight;

        (function run() {
            newHeight = elm.clientHeight;
            if (lastHeight !== newHeight) callback();
            lastHeight = newHeight;

            if (elm.onElementHeightChangeTimer) {
              clearTimeout(elm.onElementHeightChangeTimer);
            }

            elm.onElementHeightChangeTimer = setTimeout(run, 200);
        })();
      }
    </script>

Hey @mariodermez Thanks for posting this issue, however I think this is an edge case and I won't give it a high priority given other more direct things  that I have to work on. I'm going to close this issue for now and mark as won't fix. The main principle behind this library is simplicity and it's not built to cover all possible cases (and specifically not crazy dynamic ones).
If you however have a decent solution in mind and are willing to submit PR for further consideration - feel free, I'm always happy to see contributions :)


Re-commit PR 1472 to support multiple participants on server side

This PR fixes the conflict and keeps the same logic in PR 1472.

Codecov Report

Merging #1479 into master will decrease coverage by 0.26%.
The diff coverage is 52.13%.

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

Addressed Rob's comments and should be ready for review or be merged


implemention of signup and signin

add encryption /Hasing using bcrypt and jwt and add cookie-session  refer the api docs

Assign me the task

Assign me

I used jwt and brcypt many times

@Yashgupta9330 i have also assigned u the type error issue if no problem ,i think the issue should be assigned to @TammyAlok2 ?tell me

Can this issue be assigned to me, and can the type error issue be assigned to @TammyAlok2 ?

@TammyAlok2 tell what u want to do ??

Give this Authentication task to me

Hii @Tanishq1604 ,
I would like to work on this issue.
Please assign me.

pls assign it to me I already said

ok so @HemantKr071 and @Yashgupta9330 can u work together then ??

I have no issue, I can work together.

Yes we can work together

Ok then assigning both of u, start working on it

any updates on this!? @HemantKr071 and @Yashgupta9330

Today, we will make a PR. Actually, exams are currently ongoing, that's  why we are late.

I have made a pr


correct facts in examples.

corrected the capitals of the states listed in an example.

@EdMaurer : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

@EdMaurer thanks for picking up on that. I guess whomever wrote the example needs a refresher in Geography.
Approved by ADX content team
#sign-off

@YaelSchuster: I'm sorry - only the author of this article, @orspod, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Update lavalink.py

Just removed a few unnecessary empty returns. I left one (return when a connection has been established) because I liked the way it read. Please let me know if you have any issues with this, and please test and let me know that everything works as intended.

Whoops, I read a little too quickly and nearly missed this. Will make a quick patch for it https://i.crimsonxv.pro/e8f7a820c1.png
(That creates a player if one doesn't exist)


Add build-essential pkg

Description

The dagster build-and-publish-container concourse pipeline is now failing with the following error. Looking around grpc repo it might be an issue with a missing build-essential pkg. Looks like it was downloading a wheel before when it was working and now it's a tar pkg.
Motivation and Context

How Has This Been Tested?

Types of changes

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

Checklist:

[ ] My code follows the code style of this project. (Did you install and run the pre-commit hooks?)
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

:+1:


Add support for disabling the auto property naming on interface members

solves #84

Hey @apollo2030 , this is great--but I think you forgot to commit your test interface and implementation. The codez don't compile when I clone your PR :)
Update your PR with these files and I think we'll be good to go.
Thanks!

The issue was that the .gitignore ignores the path /tests/. I did comment it then commit only the missing test files. The path is still ignored in .gitignore as I don't know the reason it was put there.

@apollo2030 your change was released in version 5.1.0


Support vendoring with different revs from same git repo

What does this PR try to resolve?
Fixes #10667
How should we test and review this PR?
test case is included

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon.
Please see the contribution instructions for more information.

:umbrella: The latest upstream changes (presumably #11387) made this pull request unmergeable. Please resolve the merge conflicts.

Rebased with suggested changes.

cc @ehuss

@rustbot ready

@bors r=hi-rustin

:pushpin: Commit f114298149326c435150fecf02b8b58f1cac67e3 has been approved by hi-rustin
It is now in the queue for this repository.

:hourglass: Testing commit f114298149326c435150fecf02b8b58f1cac67e3 with merge 5a574d39f3c0df85ea761f7a660b42e388077de2...

:sunny: Test successful - checks-actions
Approved by: hi-rustin
Pushing 5a574d39f3c0df85ea761f7a660b42e388077de2 to master...


Update Java compiler binary while updating native compilers

This PR updates packages/google-closure-compiler-java/compiler.jar while updating all the native compilers. This is needed  so that the internal versions always match up.

Merging this to unblock future testing. Happy to address comments during a future cleanup.


python311Packages.gotenberg-client: 0.5.0 -> 0.6.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.gotenberg-client is: Python client for interfacing with the Gotenberg API
meta.homepage for python311Packages.gotenberg-client is: https://github.com/stumpylog/gotenberg-client
meta.changelog for python311Packages.gotenberg-client is: https://github.com/stumpylog/gotenberg-client/blob/0.6.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.6.0 with grep in /nix/store/66c55l7gvf6arpgr5yz7ysdkjlrq2rvm-python3.11-gotenberg-client-0.6.0
found 0.6.0 in filename of file in /nix/store/66c55l7gvf6arpgr5yz7ysdkjlrq2rvm-python3.11-gotenberg-client-0.6.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

paperless-ngx
python311Packages.gotenberg-client
python312Packages.gotenberg-client

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/66c55l7gvf6arpgr5yz7ysdkjlrq2rvm-python3.11-gotenberg-client-0.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.gotenberg-client https://github.com/r-ryantm/nixpkgs/archive/016b02fdefcd058ffe1acbca357b618687ab0b10.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/016b02fdefcd058ffe1acbca357b618687ab0b10#python311Packages.gotenberg-client

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/66c55l7gvf6arpgr5yz7ysdkjlrq2rvm-python3.11-gotenberg-client-0.6.0
ls -la /nix/store/66c55l7gvf6arpgr5yz7ysdkjlrq2rvm-python3.11-gotenberg-client-0.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package failed to build:

paperless-ngx

4 packages built:

python311Packages.gotenberg-client
python311Packages.gotenberg-client.dist
python312Packages.gotenberg-client
python312Packages.gotenberg-client.dist

Maintainer pings
cc @leona-ya for testing.

@ofborg test paperless

This update seems to regress paperless-ngx (it's pytest tests fail reliable)

Result of nixpkgs-review pr 319656 at 016b02fd run on x86_64-linux 1

3 packages built successfully:

paperless-ngx
python311Packages.gotenberg-client
python312Packages.gotenberg-client

@ofborg build paperless-ngx.tests

updated in 5a71df92074bd25cb745b2998336421e4825b6b6


Clarify the requirements around interceptors compatible implementation requirements

It was suggested that CDI full compatible implementations could be used as compatible implementations for the interceptors spec. This was questioned due lack of an explicit statement, and some apparent missing signature tests. I believe that CDI has been an Interceptors compatible implementation since its inception. Full should continue to be a compatible implementation, but Lite cannot be due to the lack of support for the @Interceptors annotation, and other issues. The spec and TCK user guide should make this clear.

Added statement about CDI being a Jakarta Interceptors compatible implementation.


fix: go back after reaload

Context
Problem: After reload the back button behaves weirdly, deleting messages he should not delete and showing others he should not show any more.
Description
This pull request fixes this situation.
Status
READY
Todos

[X] Fixes toggle back button
[X] Fixes message show/delete
[X] Adds vars to localStorage
[X] Removes enableStickySession flag
[X] Improves localStorageClear by setting all flags to null
[X] Scrolls to bottom after reload
[X] Saves html messages inside localStorageSave

Please don't merge if changes are ok but only approve the PR. Thanks!

@FrancescElies Please do tech-qa for it since you already worked on it. Thanks

I believe you forgot to push the bundle, I did it on https://github.com/fredknowsit/jquery-expert/pull/46/commits/eed91fe456b85e85152835cb24e3bad192177d39

Well you pushed it but I get a different one when I check out the last commit

Added a small fix for reset message


Update policy apparmor-psp-policy to target high level resources

Update the policy from targeting Pod resource to target higher level objects like deployments. This is a better practice because we prevent the resources to be created instead of failing in the deployment phase when the pods are created.
As an example, see https://github.com/kubewarden/allow-privilege-escalation-psp-policy/pull/33.

I am working on this

assigning it to you! :)

@geeksambhu are you still working on this?

@geeksambhu I'm cleaning the assignees, to unblock this for other people. If you want to work on this, please raise your hand ).

@viccuad, I will work on this.

Reassigning then! Thanks!


Run trained policies for active human environments on static human environments

Hi,
would it be possible to run trained policies for active human environments on static human environments?
In other words, imagine if I trained a policy for the environment "FeedingJacoHuman-v1" and now I want to render this policy for the environment "FeedingJaco-v1".
How can I achieve this?
I tried changing the folder name for the trained policy from FeedingJacoHuman-v1 to FeedingJaco-v1 and run the following command:
python3 -m assistive_gym.learn --env "FeedingJaco-v1" --algo ppo --render --seed 0 --load-policy-path ./trained_models/ --render-episodes 10

however, I get the following error:
Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/gabrigoo/assistive-gym/assistive_gym/learn.py", line 226, in <module>
    render_policy(None, args.env, args.algo, checkpoint_path if checkpoint_path is not None else args.load_policy_path, coop=coop, colab=args.colab, seed=args.seed, n_episodes=args.render_episodes)
  File "/home/gabrigoo/assistive-gym/assistive_gym/learn.py", line 104, in render_policy
    test_agent, _ = load_policy(env, algo, env_name, policy_path, coop, seed, extra_configs)
  File "/home/gabrigoo/assistive-gym/assistive_gym/learn.py", line 58, in load_policy
    agent.restore(checkpoint_path)
  File "/home/gabrigoo/env/lib/python3.8/site-packages/ray/tune/trainable.py", line 388, in restore
    self.load_checkpoint(checkpoint_path)
  File "/home/gabrigoo/env/lib/python3.8/site-packages/ray/rllib/agents/trainer.py", line 818, in load_checkpoint
    self.__setstate__(extra_data)
  File "/home/gabrigoo/env/lib/python3.8/site-packages/ray/rllib/agents/trainer_template.py", line 289, in __setstate__
    Trainer.__setstate__(self, state)
  File "/home/gabrigoo/env/lib/python3.8/site-packages/ray/rllib/agents/trainer.py", line 1698, in __setstate__
    self.workers.local_worker().restore(state["worker"])
  File "/home/gabrigoo/env/lib/python3.8/site-packages/ray/rllib/evaluation/rollout_worker.py", line 1267, in restore
    self.sync_filters(objs["filters"])
  File "/home/gabrigoo/env/lib/python3.8/site-packages/ray/rllib/evaluation/rollout_worker.py", line 1229, in sync_filters
    assert all(k in new_filters for k in self.filters)
AssertionError

Thanks a lot.

This is not supported in Assistive Gym currently. It would require a few changes to do. First, the active human environments use an relic interface, rather than a strict gym interface, see: https://github.com/Healthcare-Robotics/assistive-gym/blob/main/assistive_gym/envs/feeding_envs.py#L44
Then, for active human ends, there are actually two policies trained: https://github.com/Healthcare-Robotics/assistive-gym/blob/main/assistive_gym/learn.py#L34
You will want to pull out and use only the policy for the robot, and make sure to set coop=False when loading the policy: https://github.com/Healthcare-Robotics/assistive-gym/blob/main/assistive_gym/learn.py#L32
and ensure that self.human.controllable is False: https://github.com/Healthcare-Robotics/assistive-gym/blob/main/assistive_gym/envs/feeding.py#L13

Thanks for the help. So I am trying to follow the steps you suggest. In order to pull out and only use the policy for the robot I did the following:
def setup_config(env, algo, coop=False, seed=0, extra_configs={}):
    num_processes = multiprocessing.cpu_count()
    if algo == 'ppo':
        config = ppo.DEFAULT_CONFIG.copy()
        config['train_batch_size'] = 19200
        config['num_sgd_iter'] = 50
        config['sgd_minibatch_size'] = 128
        config['lambda'] = 0.95
        config['model']['fcnet_hiddens'] = [100, 100]
    elif algo == 'sac':
        # NOTE: pip3 install tensorflow_probability
        config = sac.DEFAULT_CONFIG.copy()
        config['timesteps_per_iteration'] = 400
        config['learning_starts'] = 1000
        config['Q_model']['fcnet_hiddens'] = [100, 100]
        config['policy_model']['fcnet_hiddens'] = [100, 100]
        # config['normalize_actions'] = False
    config['num_workers'] = num_processes
    config['num_cpus_per_worker'] = 0
    config['seed'] = seed
    config['log_level'] = 'ERROR'
    # if algo == 'sac':
    #     config['num_workers'] = 1

   # HERE THE CHANGES
    obs = env.reset()
    config['observation_space'] = env.observation_space_robot
    config['action_space'] = env.action_space_robot

    # if coop:
    #     obs = env.reset()
    #     policies = {'robot': (None, env.observation_space_robot, env.action_space_robot, {}), 'human': (None, env.observation_space_human, env.action_space_human, {})}
    #     config['multiagent'] = {'policies': policies, 'policy_mapping_fn': lambda a: a}
    #     config['env_config'] = {'num_agents': 2}
    return {**config, **extra_configs}

Is that how you pull out the policy for the robot only?


Internals: Updated enumeration and Test-DbaDeprecation

Changes:

Added a new Alias for level 2 in the MessageLevel enumeration: Output
Added function: "Test-DbaDeprecation", which shall be used to manage renamed functions/parameters as well as deprecated parameters.

Test-DbaDeprecation

Will write a warning once per session when using a function/parameter/parameteralias we are going to remove
Can be tested against, making sure the content is actually removed in the release we announced to drop it.

yesssss


Instructions to update .NET SDK

It would be great if there was instructions on how to update to a later .NET SDK for the repository.
Specifically, there is a script tools\UpdateDotnetRuntime.ps1 that has no documentation.

I wonder why do need this? It seems it is exclusively maintainer's headache :-)
Current intention is to update to new .Net preview versions as fast as possible to resolve all issues early.
/cc @adityapatwardhan

@xtqqczze For local purposes, you can just edit the .NET SDK version in global.json to one that you have already installed. For exampe, right now you could update it from 5.0.100 to 5.0.102 if you've got the latest patch installed and it will work fine, the only thing that you might have to do is re-import the build.psm1 module. If you also wanted to use the Start-PSBootStrap function of the build.psm1 module for convenience or to make sure that CI runs with that different version as well, then you'd also update the DotnetRuntimeMetadata.json file as well.
And that's about it for most cases. If for example, you wanted to update to a new major version of .NET, then some of the .NET NuGet packages that are not part of the SDK need to be updated as well, most of them start with System.* and you can find the references in the csproj files and do a bulk update with search replace or use Visual Studio's NuGet manager for that. Similarly, when using nightly versions of the .NET SDK, those NuGet packages need updating and the tools/UpdateDotnetRuntime.ps1 takes away some of that manual pain. Also, if you wanted to have a green CI build, you'd also need to update the files.wxs for the Windows installer as the package versions are hard-coded in there. When building the MSI, you will actually be presented with automatic tooling that spits out the new files.wxs file that you can then replace and check in, how to build the MSI is documented here, just be aware that you need to do that on a Windows and have the WiX ToolSet installed, but the commands would give you pointers to the required tooling anyway in case you mis something.
Does that help or are there specific questions?

@xtqqczze For local purposes, you can just edit the .NET SDK version in global.json to one that you have already installed. For exampe, right now you could update it from 5.0.100 to 5.0.102 if you've got the latest patch installed and it will work fine, the only thing that you might have to do is re-import the build.psm1 module. If you also wanted to use the Start-PSBootStrap function of the build.psm1 module for convenience or to make sure that CI runs with that different version as well, then you'd also update the DotnetRuntimeMetadata.json file as well.
And that's about it for most cases. If for example, you wanted to update to a new major version of .NET, then some of the .NET NuGet packages that are not part of the SDK need to be updated as well, most of them start with System.* and you can find the references in the csproj files and do a bulk update with search replace or use Visual Studio's NuGet manager for that. Similarly, when using nightly versions of the .NET SDK, those NuGet packages need updating and the tools/UpdateDotnetRuntime.ps1 takes away some of that manual pain. Also, if you wanted to have a green CI build, you'd also need to update the files.wxs for the Windows installer as the package versions are hard-coded in there. When building the MSI, you will actually be presented with automatic tooling that spits out the new files.wxs file that you can then replace and check in, how to build the MSI is documented here, just be aware that you need to do that on a Windows and have the WiX ToolSet installed, but the commands would give you pointers to the required tooling anyway in case you mis something.
Does that help or are there specific questions?


SASS-9628

We  current do not have a component to add this highlighted text so I have not included it


Allow device information acquisition on physical devices

Fixes https://github.com/gfx-rs/gfx/issues/1671 https://github.com/gfx-rs/gfx/issues/1657 (set to 11.0)
Implements 2nd approach (open device -> query information -> close device) for dx12. For other backends only code has been shifted around.
Main motivation for this is vulkan portability, it doesn't provide new features.

bors r+

bors r=kvark

bors r=kvark


Add parameter for the service mode.

This is used in the composition functions for the labels
Checklist

[x] The PR has a meaningful title. It will be used to auto generate the
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
[x] PR contains a single logical change (to build a better changelog).
[x] Categorize the PR by adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.
[ ] Link this PR to related issues or PRs.

Will adjust the version of the appcat image once the https://github.com/vshn/appcat/pull/194 has been merged and tagged