Unify driver more

This PR:

Adds more cli options for moisture model and energy variable name
Uses the added cli options for dispatching to generalized methods in driver.jl (and post-processing)
Changes a kwarg in center_initial_condition to args (so that we can dispatch)
Adds a convenience parse_arg method to help trim some dynamically parsed arguments
Makes params constant

This is another step towards #339 and #301.

I'm a bit puzzled why this isn't working. I'll break it down a bit.

with the current ambitious ddls, I strongly agree with @bischtob 's suggestion in the amip meeting today, on postpone driver polishing

with the current ambitious ddls, I strongly agree with @bischtob 's suggestion in the amip meeting today, on postpone driver polishing

I agree with @bischtob's suggestion about postponing driver polishing too. This PR is not about polishing the driver-- it's about making the driver more compose-able so that we can combine different physics components. Right now, we cannot combine the newly added radiation pieces with any other TEST_NAME file, because several global variables are being overwritten. Moving variables into cli arguments and allowing us to merge/load these files in a single driver is an essential integration step.

Understood. Then, please modify README accordingly. Some early PRs messed up the hyperlinks there already, making it harder to set up experiment following the README.

actually, since the cli is getting bigger and bigger, I am wondering if it's a good time to start thinking about namelist now?

actually, since the cli is getting bigger and bigger, I am wondering if it's a good time to start thinking about namelist now?

That's a good point. We use both in TC. The cli options overwrite the namelist, which is passed into the "main" function (which runs TC with whatever config is specified in the namelist).
I'm fine with supporting it if people want/need it now, but that would require us to clean up the global namespace (and unify the driver since the separated scripts define several global variables)

Superseded by a bunch of other recent PRs.


Update private and JNI version to released 23.12.0

Update dependencies version to 23.12.0
I will re-trigger all CIs after those artifacts are available on maven central

build

Going to merge this one and I will take care of the following auto-merge conflic


Fixed #30547 -- Doc'd how Meta.constraints are applied to model valid…

Patch with suggested changes.
https://code.djangoproject.com/ticket/30547

Cheers @Ian-Foote. Did you have any comment on my thoughts? (You implemented the constraints right? Unless I've totally mis-remembered that...)

yeah we definitely want a new API to allow constraints to perform validation. This was discussed in #10796 when support for partial unique constraints was added.

I think we can probably convert the Q object backing the constraint into python validation. I've not thought especially deeply about it though, so there may be awkward edge-cases I'm not thinking of.

@Ian-Foote yeah we discussed this solution in https://github.com/django/django/pull/10796#discussion_r244216763 but this is a no go IMO given https://github.com/django/django/pull/388#issuecomment-8863209. We need to pass the actual values to the database backend. We'll probably need to use an union of provided values and existing rows filtered by the condition predicates. That would require adding filtering support to combined queries though.

(Slight aside but I have to salute given #388 (comment) 🏅)


Add support to unlock vault by command line parameter

I would like to use eosc to automatically deploy contracts with GitLab CI.
That means I would like to be able to pass the passphrase as a command line parameter.
Is there a option to do this already that I am missing?

You can use environment variable EOSC_GLOBAL_INSECURE_VAULT_PASSPHRASE to hold the passphrase of the vault.
Note also that most command line parameter can be defined via environment variable by using the prefix EOSC_GLOBAL like: EOSC_GLOBAL_API_URL, EOSC_GLOBAL_VAULT_FILE, etc.

Thank you!

@kthamm we chose to use an environment variable as you can load it without leaving traces in . bash history, you can have a bash . script do:
EOSC_GLOBAL_INSECURE_VAULT_PASSPHRASE=$(cat mypassphrase.txt) eosc vault serve...

Hi,
while this works when I use it on a local machine, it fails when I try to execute it with Gitlab CI in a docker container:
EOSC_GLOBAL_INSECURE_VAULT_PASSPHRASE=$(cat passphrase.txt) eosc system setcontract ...
Enter passphrase to decrypt your vault:
ERROR: setting up wallet: secret boxer: reading password: inappropriate ioctl for device
Any ideas?

The password is ask if the value is not set or if it's the empty string. So this could print if $(cat passphrase.txt) is not doing anything.
Be also sure to have a recent enough version of eosc, this was added in v.1.1.0.
You could try to export first and then run the command, I really doubt it would make a difference but could be.
You can check the actual value as it would be seen within the eosc process:
EOSC_GLOBAL_INSECURE_VAULT_PASSPHRASE=$(cat passphrase.txt) bash -c 'echo "$EOSC_GLOBAL_INSECURE_VAULT_PASSPHRASE"'

Yeah sorry I was stupid. It works now :) Thank you for your help!

@kthamm Excellent :)

What if the passphrase IS an empty string?

@str Normally, I assume it should work. If it doesn't, please open a new issue so we can take a look.

It didn't.   I tried:
EOSC_GLOBAL_INSECURE_VAULT_PASSPHRASE= ./eosc
EOSC_GLOBAL_INSECURE_VAULT_PASSPHRASE="" ./eosc
Ad without setting anything, and it kept asking for the  password.  I'm about to open a new issue then.


Feature request: Increase default value for "items per page"

The default value is 10 at the moment, which is quite low.
Most screens are large enough to display at least 25 rows.
Suggesstion: Increase default to 50 for all pagers

It's not the case for a mobile and tablet devices though.

I feel like 10 is a good default value. As @G07cha mentionned, we aim to support tablet devices as well and this default value makes sense here.
You can just update the value and it'll be persisted in your browser.

Anytime I search for a setting or bug in portainer that I like to fix I found a issue which is closed with a comment like this. Why you don't let users choice the default settings? There are much more scenarios than that what you guess. I.e. the Browser forget this setting because its a private session or you want to make a setting for the whole company. That's so annoying!

@thekk1 this is a pretty old feature request, we're ok going back on our decisions.
Keep in mind that open-source rule: no is temporary, yes is forever.
I'll re-open this item for us to look at.

Thanks dude, I am really looking forward to this.

I'd like to add that a user setting to adjust the default per page would be more sensible.  If you believe most people want 10 per page then make that the system-wide default but let a user adjust their preferences similar to the user themes.

A global setting to adjust the count would be great so it would be saved as part as the userdata instead of the browser cookies, or perhaps a global environment setting.

A global setting to adjust the count would be great so it would be saved as part as the userdata instead of the browser cookies, or perhaps a global environment setting.

This, as setups like mine with authelia and traefik end up regularly "forgetting" this configured setting.

This is one of the most frustrating things about using Portainer. Even on a tablet I can see 20+ containers. On a phone there's always the option to scroll down. I would rather do that then have to click through pages.
You've recently back peddled quickly on the password length enforcement and turned it into a setting. Probably time to rethink this one too.

Users should be able to modify anything that has to do with presentation of data. Columns and rows in tables should be user-modifiable.

Has this been solved in the meantime? It is very annoying that portainer cannot save the number of items shown in a list.

No, still relevant.

I just updated to the latest version and it looks like this was resolved!  I went into containers under environment, changed the items per page, signed out, signed back in, and verified items per page setting stayed how I had it set before logging out.

@jmott85, I did not notice that until I checked yesterday. Indeed, Portainer stores the info in the localStorage of the browser; which I have deleted upon browser restart. I do not really like the concept, because then the info is attached to the browser and not the user account in Portainer... but probably that is good in most scenarios.
Thank you for the clarification, added Portainer host to the whitelist for localStorage not to be deleted.

I just updated to the latest version and it looks like this was resolved! I went into containers under environment, changed the items per page, signed out, signed back in, and verified items per page setting stayed how I had it set before logging out.

It's not fixed.
Yes, the browser is remember the setting now. But this was not the request in this issue.
The setting is not remembered for the user that is choosing it. Log in on another machine or browser bring the user back to the false setting.
No, there is no option for users or the admin to change the default value.
So after 5 1/2 years there is no feedback or reaction to the absolutely sensible and legitimate request.

Our browsers are all limited to private windows & always loose local settings.  Very annoying - please make this a config setting...


[vcpkg_get_cmake_vars,meson] Add OSX_SYSROOT for SDKROOT

Fixes toolchain errors of the type fatal error: 'stdio.h' file not found on macOS.
This error seems to occur when using
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc vs cc for the compiler.

Thx would have helped a lot with the OSX errors in #12945. Unfortunally I did not see this PR until now since I was neither watching my own fork of vcpkg (which I now do) nor was I mentioned in the PR. As such I only saw this PR when I was cleaning up stale branches. Since #12945 will be merged soon I'll close this PR and sync the update_glib branch after that with master.


Docs fix spelling issues

Hello
I found and fixed several minor typos.
Br, Elias.

We just don't accept typo-only fixes from first time contributors.


path_provider mock example needs to be updated

https://flutter.dev/docs/cookbook/persistence/reading-writing-files#testing demonstrates mocking the method channel for path provider, but not all path provider implementations use a method channel (notably, path_provider_linux; see discussion)
Instead it should be showing mocking out the platform provider, as is done here, since that's the recommended way of mocking out plugins that are using the new platform interface structure.

Or it should mock out the whole plugin, per the new https://docs.flutter.dev/development/packages-and-plugins/plugins-in-tests


Reformatted the examples to make them easier to read

There are a large number of examples in the readme. I find them really hard to read and learn from.
In this PR I've gone through all the examples in the readme, checked that the examples work, and reorganised them into two sections:

Basic usage
Optional flags

Both sections are working code examples.

:+1:


Remoting API refactoring

remove casts
remove maps as methods parameters
check order of method parameters
check method & field names
fields should come before methods

This issue is related to all classes that part of a legacy package or subpackage.


Gesture Hooks API

I am trying to make it possible for another plugin to hook onto the opposite gesture of the workspace gesture.
I had the idea of copying hyprexpo's touchpad gesture on a touchscreen by having hyprgrass emit a hook when dragging the opposite way and then have hyprexpo hook onto it.
I have the hook and listen thing figured out, but the gesture part is very unclear to me.
I can't really tell how to listen to a gesture or even if one is recognized at all. Would love to get some info on that.
Thanks!

that's genius! I had the idea of using dispatchers to do somewhat the same thing but it was too clunky to use and so I dropped it.

I think rather than hooking on to the "opposite of workspace gesture" it's easier to provide hooks for a generic "swipe" event (and same for "edge" and others).
for that you can emit the events in handleDragGesture() and handleDragGestureEnd(). A drag basically means the gesture has a clear "start" and "end" point - when a "swipe" is first recognized, handleDragGesture() is called. when the gesture ends, e.g. lifted a finger, handleDragGestureEnd() is called.
not so important to the problem at hand, if handleDragGesture did not do anything (returns false), handleCompletedGesture() will be called instead

I'd like to see some way for hook users to tell us if they did anything: if they handled the gesture, we need to block touch events from going to the app window (among other things). for this, EMIT_CANCELLABLE_EVENT might be useful

So I try having handleDragGesture(), handleDragGestureEnd() and dragGestureUpdate() emit the event but it seems like the workspace swipe takes ownership of any 3 finger swipes if that makes sense.
I try to swipe vertically instead to not trigger the workspace swipe but that does not emit anything during that gesture.

can you push what you have now?

It's not much but here you go

Crashes Hyprland as soon as I do a gesture :(
No crash report in ~/.cache/hyprland

added some checks, so that workspace swipe doesn't crash
notification now works, but idk what the API should look like yet. i think at the very least we'll need 3 separate hook events for start/update/end and possibly more for each gesture type

i think at the very least we'll need 3 separate hook events for start/update/end and possibly more for each gesture type

Yes I was thinking that too.

the events should be namespaced under hypgrass: or something

Yes I agree

I tried your latest commit and it did work to emit changes for swipes, but the workspace swiping wasn't working, is that normal?

yea right now the hook just "consumes" the drag event unconditionally

@horriblename I finally figured out how to make the hooks compatible with hyprexpo's gesture, which was my original goal.
I had to stick with IPointer::SSwipeUpdateEvent instead of using ITouch::SMotionEvent like you said because it doesn't hold any info on the amount of fingers, and I feel like exposing a delta is better than the position when it comes to a gesture.
What do you think?

Also, should I be using EMIT_HOOK_EVENT_CANCELLABLE instead of EMIT_HOOK_EVENT?

Also, should I be using EMIT_HOOK_EVENT_CANCELLABLE instead of EMIT_HOOK_EVENT?

EMIT_HOOK_EVENT is fine. Only the start event needs to check that an event is handled

I had to stick with IPointer::SSwipeUpdateEvent instead of using ITouch::SMotionEvent like you said because it doesn't hold any info on the amount of fingers

uuh I'll mull it over, but I think if we're exposing a hook API I'd like it to be extensible as possible

@horriblename Have you given this PR any more thoughts?
I added a small check list in my original message to clarify what I'm hung up on

Sorry it took this long, I've decided to go ahead with #189 as a stopgap and leave the event hooks for another time.
#189 should cover your use cases (hyprexpo integration), I tested on Hyprspace but please help me test on hyprexpo as well.
I will be generalizing ideas from this PR for a more extensible event hook API.

If you have no problems with #189 I will close this PR and merge that one

No worries!
#189 works perfectly for my use case. Just gave it a shot and I'm happy. Go for it
We can leave this PR open and leave it as a draft imo. It's up to you if you wanna continue it or open another one but it's still a good reference for what's possible and whatnot.


[PIO-92] Bump HBase to 1.2.6

This request upgrade only HBase dependency. Some methods have been deprecated, but they are not fixed in this request for backward compatibility.

I found HBase version inconsistency in documentation and build configuration: https://github.com/apache/incubator-predictionio/pull/391#issuecomment-310151519
So I close this request and confirm the correct state at first.


Artwork Sale Lot Sorting

This PR finishes up #969 by

Taking associated artwork lots and sorting them first by artists that you follow and then everything else
Returning the total number of lots and adding it to the "View All Lots" button

          1 Warning

:warning:
Please assign someone to your PR

  Generated by :no_entry_sign: Danger

Looks good in dev both logged in and out. GTG once tests are fixed 💯

Timezones <3

@erikdstock gave me go ahead offline 👍


SILGen: Cope with overloads when emitting artificial main for @UIApplicationMain.

The overlay may add overloads for UIApplicationMain for various reasons. When we generate the special main implementation for a @UIApplicationMain class, we want to call the original function from Objective-C, so pick that one where there are multiple overloads to choose from. Fixes rdar://problem/42352695.

@swift-ci Please test

@swift-ci Please test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - cba32f79a5dfc838873ceb5edb4da90a9cf06305

@swift-ci Please test Linux


change shape in sidebar

Hi,
I am unable to change shape in drang and drop sidebar. i want diamond shape  in it.
is this possible to customise sidebar shape and and drag them in graph area?

This has nothing do to with react flow and it's not an issue. You can find articles about how to create shapes with css when you search for it https://css-tricks.com/the-shapes-of-css/


Support the Section  tag

Building a single webpage for a short presentation, I used section instead of article which, in my context is more... well, semantically correct.
Section is not supported and the only way I can make it work is to enclose the whole page (apart from header) in a  tag, which I believe is wrong.
Applying the same layout for section and article seems good for me.

Width is now applied to <main>, and the padding is now body margin.


Add test case for proper sta spef annotation

Testing

Add a test case for hier spef annotation with OpenSTA

Depends on https://github.com/efabless/openlane2-step-unit-tests/pull/38
Resolves https://github.com/efabless/openlane2/issues/547

Pulled into #563 to coincide with the OpenSTA update


Junkers Bosch Systemregler CW 400

Is it possible to include the Bosch control unit CW400 into the code.
That unit is communicating via mblan-i and the BOSCH HomeCom iOS App.
Only in home assistant I have the missing data.
So far I am unable to receive data for the recording entities which are marked with an r.

It won't work with my component unfortunately, it's different protocol

I just got the CW400 working, but with a very limited set of accessible data. I am using an MBLAN2 and have been able to connect via IVT HTTP. The component detects a "RC300/RC310/Nefit Moduline 3000" and I am able to control climate.hc1 and water_heater.dhw1.
I wonder if there is anything I can change or maybe even contribute to support more functionality, but I can open up another issue for that.

Nevermind, the sensors are available, they were just deactivated.

@martinsteinorth How did you add the MBLAN2 to the CW 400 ? Because mine doesn't have it i think.

@martinsteinorth How did you add the MBLAN2 to the CW 400 ? Because mine doesn't have it i think.

You can look up how to connect MBLAN2 to your gas boiler unit in the instructions. It is only a matter of connecting two wires to the gas boiler after removing some covers. In my case it is a Cerapur ZSB. The port is called EMS.

I dont have an Mblan2, do i need to buy it seperatly ? Cuz its 300 euros

I dont have an Mblan2, do i need to buy it seperatly ? Cuz its 300 euros

Are you sure you need a MBLAN2 ?
I think it depends on your boiler.
Mine is a Condens 9000i WM (BOSCH/Junkers) and only works with MBLANi (i, not 2)
Today I think Bosch also sells a WiFi- box solution only. MBLAN2 is an older model.

I dont have an Mblan2, do i need to buy it seperatly ? Cuz its 300 euros

You need to check first which box is the right one for your boiler. There are MBLAN2 and MBLANi. MBLAN2 has been discontinued. You cannot and should not purchase it. You can get in contact with Bosch through this form and might be eligible to get a box shipped to you for free: https://www.bosch-homecomfort.com/de/de/wohngebaeude/no-menu/internet-gateway/
If you purchased your boiler in 2022 or later you should be eligible. Just choose "no voucher" and provide them with your boilers serial number and some additional information. Worked for me.


node-mongodb driver compatability

According to the README.md MongoDB is supported up to 3.2, but the native mongodb driver is supported up to 2.0 only.
Here it says you need to have the 2.1 driver to use with mongodb 3.2:
https://docs.mongodb.org/ecosystem/drivers/driver-compatibility-reference/#reference-compatibility-mongodb-node
So does connect-mongo support the 2.1.x node-mongodb driver?

Yes of course. I've updated the README.md.

Thanks!


Implementation of RedeemIntentConfirmed Handler

PR covers below:

Implementation of redeem intent confirmed handler
Tests

Fixes #146

Available for review 🐰


Home-Assistant 2024.2.2 complains about Python 3.11.6

Running the 2024.2.2 home-assistant container you build gives the following warning:
Support for running Home Assistant in the current used Python version 3.11.6 is deprecated and will be removed in Home Assistant 2024.4. Please upgrade Python to 3.12 to prevent your Home Assistant instance from breaking.

It looks like you build on top of an alpine base container of your own: https://github.com/onedr0p/containers/pkgs/container/alpine.  It doesn't look like alpine has python3 3.12 in their 3.19 release.

I saw that too and hoping that Alpine 3.20 will make it out before HASS does, I'll keep this issue open as it should be addressed before April.

It is also worth noting that Alpine Edge doesn't eve have 3.12, so this might be an issue if come April Alpine doesn't package 3.12
https://pkgs.alpinelinux.org/packages?name=python3&branch=edge&repo=&arch=&maintainer=

One option would be to add a  base image based on python:3.12-alpine, the python maintainers just build python from source in their base image.

Good point, we'll see what things are like in a month.

I went with @rtrox suggestion for now until Alpine supports 3.12 in their pkg repos.
https://github.com/onedr0p/containers/issues/978


Is it possible to change the function so that "Full Screen" can be used as "User Function"?

Hi!
It is an simple and good editor.
Is it possible to change the function so that "Full Screen" can be used as "User Function"?
Thanks in advance.

Hi~Thank you for your interest.
Once you have created a custom button, you can find it here.
If you want to run "User Function" after full-screen operation
You can put your code inside the suneditor.js : 1384 (toggleFullScreen) function.
In the current version, the only way to add functions to the original button is to insert the code yourself.


CB-7015 Add support for parent and custom attributes in lib-file element

This enables referring to libraries from the Android SDK directory.
refs: [plugman] Support copying jars from Android SDK

ping @Icenium/core

:+1:


No Need to Protect Extensions

The supported format of browsers/clients needed to be checked on the browser side or on the app side, if the extensions can be changed on the user side, it would be more convenient to use.
I've read in the document, the reason to protect URLs is to prevent DDOS attacks, but as the support of the extensions is limited, the harm is slight and I think the benefit is worth the cost?
By the way, thanks for your great efforts.
This project is awesome!

Hi! Thanks for trying out imgproxy!
What do mean by changing the extension on the user side? Could you give me an example?
The provided extension defines the resulting format of the image, so I can't drop it from the URL. The supported formats list is limited by libvips support.

For example
A source image URL could be something like https://www.domain.com/VALIDATION/filename.png
Some browser could support WebP (and some don't), a javascript can check them out.
When the browser supports WebP, and the imgproxy do not care about the extension, the javascript only need to change the URL to https://www.domain.com/VALIDATION/filename.webp
It would be more convenient to use.

@DarthSim
I've implemented this feature, I'll pull a request if you have considered it's acceptable.

As far as I know frontend, you need to do this replacement before images start to load. To do so, you'll have to put image url to something like data-src instead of src. And if you do so, it's not more complex to generate two URLs, put them to data-src and data-src-webp, and use the one that is best supported by the browser.
Finally, I don't want to break back compatibility for now. So I'm going to close the issue.


Durable Functions Isolated Worker Sample?

Would it be possible to also provide a simple example for a Azure Durable Function using the isolated worked, where the actual call to the Graph API is made from an activity. These samples exist for non-durable Azure Functions, but they're difficult to transfer to the Durable functions for beginners.

I don't know if this fits in this repository. It may fit better with the durable extension: https://github.com/Azure/azure-functions-durable-extension

I don't know if this fits in this repository. It may fit better with the durable extension: https://github.com/Azure/azure-functions-durable-extension

Maybe. Honestly, the repo fragmentation is nothing but confusing. I decided to not use C# due to the lack of documentation.
I'll also save @bhagyshricompany some work and close this before he does anyway.


Upgrade ProdOKE add one more node

Upgrade to 1.26.2 and add one more worker node. Monitoring containers are using ~900% of requested resources.

We no longer have a Kubernetes cluster.


Outdated semgrep version

On macos Ventura 13.4, using miniconda env with python3.10,
Using:
pip install guarddog

will install semgrep==0.112.1as defined in the requirements.txt
Then running it on a local package will fail:
 $ guarddog pypi scan .
Found 0 potentially malicious indicators scanning .

Some rules failed to run while scanning .:

* rules-all: failed to run rule:
An error occurred when running Semgrep.

command: semgrep --config /opt/miniconda3/lib/python3.10/site-packages/guarddog/analyzer/sourcecode --exclude='helm' --exclude='.idea' --exclude='venv' --exclude='test' --exclude='tests' --exclude='.env' --exclude='dist' --exclude='build' --exclude='semgrep' --exclude='migrations' --exclude='.github' --exclude='.semgrep_logs' --no-git-ignore --json --quiet .
status code: 2
output: {"errors": [{"code": 2, "level": "error", "message": "Error while running rules: 0 bytes read on a total of 2 expected bytes", "type": "SemgrepError"}], "paths": {"_comment": "<add --verbose for a list of skipped paths>", "scanned": []}, "results": [], "version": "0.112.1"}

Now updating to latest semgrep using pip install -U semgrep and running the same command above:
 $ guarddog pypi scan .
Found 0 potentially malicious indicators scanning .

What is the reason for using semgrep 0.112.1 and not latest?

Hello,
The reason is that we did not manage to upgrade to Semgrep past 0.112.1 without breaking the current detection rules due to a Semgrep internal error we have been unable to troubleshoot (https://github.com/returntocorp/semgrep/issues/6631)

v.s. (starting from 0.113.0)

We welcome a contribution if someone wants to give it a try!
In the meantime, although outdated, Semgrep 0.112.1 is supposed to properly work as-is - if not, it's an unexpected bug. Can you open a new issue to track it, ideally sharing the package you're scanning as well? Thank you

Got it - do you have an issue to keep track of this already? Otherwise let's use this one

We don't - thanks

Is there any way you can work around the issue? There has been zero traction on the other issue and 0.112 of semgrep also requires a outdated version of packaging as well.

The best way around would be to get someone to troubleshoot the failing rule when we attempt to upgrade Semgrep (as shown in https://user-images.githubusercontent.com/136675/247486778-afad8be0-7eaf-488e-8e97-e521bbd20708.png). It has not been prioritized yet from our side, but we're happy to take a community contribution


MongoDB3 trouble with InsertMany

Hi,
I´m having problems with the InsertMany method. I´m getting the error "MongoError: docs parameter must be an array of documents". I have tried putting the document array in the msg.payload and msg.payload.docs, but I'm always getting this error.
Any help is welcome!
Thanks!

when message payload is an array, each array element is interpreted as a parameter to the selected operation. eg when operation= "update", message.payload=[{surname:"smith"}, {"surname":"Smith"}, {"multi":true}]
since for you are wanting to supply an array as a single parameter, you should wrap it in an object:
message.payload={[1,2,3,4]} and not message.payload=[1,2,3,4]

when message payload is an array, each array element is interpreted as a parameter to the selected operation. eg when operation= "update", message.payload=[{surname:"smith"}, {"surname":"Smith"}, {"multi":true}]
since for you are wanting to supply an array as a single parameter, you should wrap it in a second array:
message.payload=[[1,2,3,4]] and not message.payload=[1,2,3,4]

Thanks!

for insertMany
✗ msg.payload = [ { "name" : "Luffy" , "value" : 1} , { "name" : "Zoro" , "value" : 2 } ]
✓ msg.payload = [ [ { "name" : "Luffy" , "value" : 1} , { "name" : "Zoro" , "value" : 2 } ] ]

this is the correct format  db.collectionname.insertMany([ {} , {} , {}  ])
collectionname would be your collection u have created in ur database
{ } inside this your objects would be there
eg:
try {
db.products.insertMany( [
{ _id: 13, item: "envelopes", qty: 60 },
{ _id: 13, item: "stamps", qty: 110 },
{ _id: 14, item: "packing tape", qty: 38 }
] );
} catch (e) {
print (e);
}
refer this
https://www.mongodb.com/docs/manual/reference/method/db.collection.insertMany/#mongodb-method-db.collection.insertMany


OpenMetadata Ingestion Docker Improvements

Optimizing and creating a better efficient OpenMetadata Ingestion Docker.
For better user experience and making it more configurable.
Tasks

Using volumes for airflow.cfg

@akash-jain-10 lets keep track of it and make sure we follow up on what we need to do here. cc @ayush-shah

Allowing users to upload service account json files for bigquery, sso auth for google (secret_key path) on the volumes.
The flow that user will follow would be -
Edit airflow.cfg and openmetadata.yaml to have all the auth related stuff.
They specify paths for the service account files, but it can be difficult for users to execute / send files in an container.
Instead an easy option would be to allow them to upload the same using volumes.
Same for Bigquery, one of the connection options are credentials_path which points to a service account file.
cc: @akash-jain-10 @harshach

@akash-jain-10 can we add the sidecar facility to ingestion docker image

Another thing we should consider improving is that I believe that currently, the image is built by copying the generated sources from the laptop. This forces us to run a make generate before building the image.
It should be cleaner and less error-prone to install dev dependencies and generate in the Dockerfile.
If we cannot tackle it here, we can open a separated issue for that

@akash-jain-10 @vijaypm could you please add a volume by default to the docker images? This way users will know how to pass config files needed for ingestion. Thanks!

@Vj-L  :)


Update controllers that rely on provider to listen to NetworkController:networkDidChange instead of NetworkController:stateChange

Explanation
Listening to NetworkController:stateChange to catch network changes doesn't guarantee that the provider proxy has also been updated to point to the new network. NetworkController:networkDidChange does however. This PR updates several controllers that rely on the provider proxy to listen to NetworkController:networkDidChange rather than NetworkController:stateChange. GasFeeController and AssetsContractController are already listening to NetworkController:networkDidChange on the extension side despite their constructor param hook names still being onNetworkStateChange (which this PR also renames to be correct)
References

See https://github.com/MetaMask/MetaMask-planning/issues/1713

Changelog
@metamask/assets-controllers

BREAKING: TokensController constructor params onNetworkStateChange replaced with onNetworkDidChange
BREAKING: AssetsContractController constructor params onNetworkStateChange replaced with onNetworkDidChange

@metamask/ens-controller

BREAKING: EnsController constructor params onNetworkStateChange replaced with onNetworkDidChange

@metamask/gas-fee-controller

BREAKING: GasFeeController will subscribe to NetworkController:networkDidChange now instead of NetworkController:stateChange using the passed in messenger param when onNetworkDidChange is not provided
CHANGED: GasFeeController constructor params optional onNetworkStateChange replaced with optional onNetworkDidChange

Checklist

[ ] I've updated the test suite for new or updated code as appropriate
[ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate

Looks good, should get a great performance improvement from this approach. Let's make sure to test the 'infura blocked' (or anything other network change errors) - These controllers will no longer have event handlers called when there is an error in switching the network.

Let's make sure to test the 'infura blocked' (or anything other network change errors) - These controllers will no longer have event handlers called when there is an error in switching the network.

State updates from the network metadata flow would follow soon after a networkDidChange event. We definitely would be firing the listener one less time when migrating away from stateChange, but I don't believe this will cause any regression in functionality. Thank you for pointing this out!

@metamaskbot publish-preview


New MUTCD symbol set and layer file

Create a new set of symbols for the MUTCD sign types.  Additional information found here:
http://mutcd.fhwa.dot.gov/shsm_interim/index.htm
Will want to prioritize which types we focus on first and what environments we are developing for.
FYI @LindsayThomas @jlindemann @HeatherEisan

any status on this?

I work for a state transportation agency, and having access to a pre-built layer file with symbols for each MUTCD code would help us tremendously.


False flag?

I just tried to install the experimental build for dark souls 2 private server and upon opening the zip file and my anti virus flagged it as some kind of Trojan? I'm kinda confused myself.

See the many other issues surrounding this.
https://github.com/TLeonardUK/ds3os/issues/148
It's a false flag, this happens every time a new release comes out, because in windows eyes it's unfamiliar, does process injection related things (common things that malware does as well), and isn't signed (I have no intention of paying for certificates for this project either, they aren't cheap).
The code that runs in the loader/injector is minimal, it's trivial to read through it yourself if your worried.

Thanks for the speedily reply I looked through some of the code and I'm curious if my antivirus flagged and quarantined it does the mod still work? I also love all the work you guys put into making dark souls 2 co op function.


Build failure with Ubuntu 24.04 / Linuxmint 22

I have a fresh installation of Linuxmint 22, which is based on Ubuntu 24.04.
I ran the following, as per the build instructions:
sudo apt install libopencv-dev build-essential v4l2loopback-dkms curl

Then:
mkdir build
cd build
cmake .. && make -j $(nproc || echo 4)

This produced errors, so I additionally installed the following in attempt to fix them based on things that seemed to be missing:
sudo apt install clang clang-format gfortran

However, build errors persisted. There are quite a lot of issues, as I don't know what's going on I've just attached the output as a txt file.
build_error_log.txt

Sorry, been a while since I touched this code. I'll see if I can reproduce it on my machine.

Actually, the build does not work. Would be nice, if anybody knows a fix for Ubuntu 24 :)

If you remove the "Fedora check" in #167 there might be a chance the build works.


Add Check to Automatically Delete Status Translations When a Language is Removed

this shouldn't be needed. closing.


Release 3.9

Includes PR96, PR98 and when approved: PR99
#Add

min, max, height and width utilities
margin and padding up to 50px in utilities
TextField: icon prop and character counter and maxlength error message
MoneyInput and story
Prepend TextField and MoneyInput with error icon on maxlength reached
TextArea: add maxlength error message

#Change

TextField, TextArea, MoneyInput: make outline, counter and label red on maxlength reached
TextField, TextArea: allow user to type after reaching maxlength but show error message

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Wallets created from mixing disappear after upgrade

Upgraded from 1.5.5 to 1.5.6, the post, pre, etc wallets/tabbed disappeared after upgrading. I know if I mix again, they will re-appear, but if I don't mix moving forward I won't be able to see those tabs/access whirlpool coins.

You can add them back immediately using the Add Account button on the Settings tab. Scroll down to Whirlpool accounts.
Unclear why you lost the tabs though, I’ll keep this issue open in case it happens to anyone else.

Ah, I see. Thank you.

Got build 1.7.0 running on RPi (thank you!) and had similar experience...  I copied backed up wallet files from dead machine and premix/postmix/badbank did not show up.


Expose inner error for IngestStoreUnexpectedError

This looks fine, but it’s not obvious to me what (if anything) this changes. Where would we see an error where we wouldn't have seen one before?

The IngestStoreErrors, nest a throwable, they also extend a throwable - when this error is printed the inner error is hidden by the outer one.
s"IngestStoreUnexpectedError: ${e.toString}"


Not able to dim lights on google nest hub

Everything is working fine in the google home app on my phone, all my lights are dimmable from the app.
But my google nest hub shows all my lights as on/off and no level control.
I don't actually know if this is a HAMH issue or an issue with the google nest hub.
Log does not show any errors, but attached is the startup debug log of a bridge with only one of my lights.
491eb00d_hamh_2024-12-06T21-29-46.267Z.log

As soon as I submitted this issue the level control of the light suddenly started to work on my nest hub.
Assuming something had magically solved itself, I started another bridge with all my lights.
None of the lights had working level control, also not the one that worked previously.
Swithing back to the single light bridge also did not work anymore.
Seeing that it briefly worked for some reason I'm also starting to think it might be something in my network.
But all other functions are working just fine, except for the level control from the nest hub.

I assume that to be an issue with google nest.
When you pair it with the google home app, the controls are there. Therefore i don't see any problem on HAMH side.
Additionally the logs show the correct initialization of levelControl cluster.
Did you try pairing the same bridge with both google home app and google nest hub?

Thanks for the quick answer.
My google nest hub is added in the google home app. And after that i've only paired the bridge with the google home app.
Maybe i'm missing something, but I don't think there is an option to pair the bridge directly to the google nest hub.

Hello,
First thanks for this wonderful idea and software!
I've same issue, lights (single or group) are correctly added in Google home and I can dim them from there without issue.
But Google assistant (french) always says that there is no dimmable light added to Google home.

Quick note: I have a DimmableLight "Wohnzimmer Stehlampe" which worked a few versions before (can't remember which) using

Alexa App
Alexa Echo Dot (5th Gen) "Computer, Stehlampe auf 50%" ("Computer, Stehlampe to 50%")
Google Home App
Google Nest Mini (2nd Gen) "Hey Google, Stehlampe auf 50%"

Using 3.0.0-alpha.54, and watching both apps and HA, I now get the following:

Alexa App – works, can dim
Alexa Echo Dot – works, but brightness change not reflected in GH App
Google Home App – works, light is dimmable
Google Nest Mini – "Hey Google, Stehlampe auf 50%" results in "Entschuldige, das habe ich nicht verstanden" ("Sorry, I didn't understand that")
Google Nest Mini – "Hey Google, Stehlampe aus" (switch off) results in light being switched off, which Alexa and HA also see.

Looks like Google Nest devices cannot dim a DimmableLight in this version.

I'm using Nest mini and so we have the same experience.  Google home ok, on
nest lights (tried multiple vendors) are not dimmable
Le lun. 9 déc. 2024, 20:29, Matthias C. Hormann @.***>
a écrit :

Quick note: I have a DimmableLight "Wohnzimmer Stehlampe" which worked a
few versions before (can't remember which) using

Alexa App
Alexa Echo Dot (5th Gen) "Computer, Stehlampe auf 50%" ("Computer,
Stehlampe to 50%")
Google Home App
Google Nest Mini (2nd Gen) "Hey Google, Stehlampe auf 50%"

Using 3.0.0-alpha.54, and watching both apps and HA, I now get the
following:

Alexa App – works, can dim
Alexa Echo Dot – works, but brightness change not reflected in GH App
Google Home App – works, light is dimmable
Google Nest Mini – "Hey Google, Stehlampe auf 50%" results in
"Entschuldige, das habe ich nicht verstanden" ("Sorry, I didn't understand
that")
Google Nest Mini – "Hey Google, Stehlampe aus" (switch off) results
in light being switched off, which Alexa and HA also see.

Looks like Google Nest devices cannot dim a DimmableLight in this version.
—
Reply to this email directly, view it on GitHub
https://github.com/t0bst4r/home-assistant-matter-hub/issues/268#issuecomment-2529196239,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANAXMNYCFIIL4N74VGACOXL2EXVSDAVCNFSM6AAAAABTFSEVT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRZGE4TMMRTHE
.
You are receiving this because you commented.Message ID:
@.***>

A debug log of such a try to dim would be cool - also potentially in commparism where is works and where not

I don't think I will be able to create a debug log of a dim attemp that fails. The google nest hub just does not send the command because the light has no dim capability, only on/off. On the google nest hub it's easy to see right after initialization, because the UI will only show on/off for the light, or it will show the current dim level.
But, as indicated in my previous post, I've also seen that it once worked as intended. So I tried to catch that situation in a debug log.
In the attached log I've tried the following (multiple times, with different bridges):

Add a bridge with one light to the google home app
Verify in the google home app that the light is dimmable
Check on the google nest hub if the light is dimmable
If not remove remove the bridge from the google home app and start over again.

In most of my attemps it failed and I could not control the dim level of the light from the google nest hub (google home app always works).
Around 22:35 I decided to reboot the google nest hub, and after that is suddenly worked. The google nest hub showed the dim level of the light, and I was able to control the dim level from the google nest hub (dim actions should be visible in the log file).
Around  22:45 I added a second light to the bridge, and after that both lights were not dimmable anymore. Again I tried to reboot the google nest hub, but this time it did not work.
491eb00d_hamh_2024-12-09T22-50-55.761Z.log
I don't know if it is possible to install an older version of the addon in Home Assistant. Else it should be easy for me to test with older versions and provide the debug logs.

hello again,
Just capture a single line with device addon  (a philips dimmable bulb):
[ 2024-12-10T11:31:03.654Z ] [ INFO  ] [ Matter / Endpoint                                  ]: 93540fa34d994683a2f6e1b6ba7fd156.aggregator.light_chevet_de_la_chambre ready endpoint#: 15 type: ColorTemperatureLight (0x10c) behaviors: ✓identify ✓groups ✓onOff ✓levelControl ✓colorControl ✓bridgedDeviceBasicInformation ✓homeAssistantEntity ✓descriptor
It works pefectly on google home, while French assistant from google nest mini says " there is no dimmable light in your config, add a new one from google home".
Strange is that color control works fine from assitant (and home).

Here's a one-minute debug log from v3.0.0-alpha.54, for issuing the following commands (both Alexa Echo Dot and Google Nest Mini connected to the same HAMH bridge):

"Computer, Wohnzimmer Stehlampe aus" (Alexa, works)
"Computer, Wohnzimmer Stehlampe auf 50%" (Alexa, works)
"Hey Google, Wohnzimmer Stehlampe aus" (Google, works)
"Hey Google, Wohnzimmer Stehlampe auf 50%" (Google, claims it doesn't understand, no visible log entry)
"Hey Google, Wohnzimmer Stehlampe an" (Google, works)

"Wohnzimmer Stehlampe" is an ExtendedColorLight (WLED). I also tried using a DimmableLight "Büro Stehlampe" (Espurna Dimmer), and it shows the same behaviour.
I wonder if this is a sudden Google Home/Assist issue, or maybe caused because some device tries to set a float (127.5) for brightness?
Btw, setting the brightness using the GH App works, just not when using the Nest Mini.
491eb00d_hamh_2024-12-11T17-27-12.995Z.log

I had the same problem. After saying "hey google, sync my devices" (and waiting several minutes) i am able to dimm all lights via voice command.
I don't know if the "sync my device" was the actual fix.
Maybe someone can try.

Honestly ... thats then a pure google issue and has maybe even nothing to do with Matter ... so if "just" the voice assistant" do not understand you/does not find stuff it is on that side ... seems that all matter related things work

Honestly ... thats then a pure google issue and has maybe even nothing to do with Matter ... so if "just" the voice assistant" do not understand you/does not find stuff it is on that side ... seems that all matter related things work

Hi,
in first hand it looks like that what you are saying is correct.
But in the other hand: with using the nabu casa cloud to GH and with the same stuff as now used in the HA-matterhub the voice assistant is working.
Also in the GH app these devices are shown as dimmable and can used in that way.
So therefore I am assuming that there is still a bit difference within the HA-matterhub which is not totally understood by GH.
Regards
Gerhard

sorry, just hours later, nothing done, nothing changed - it's now functioning.
Just told to GH via voice to change my light to 25% - it was functioning.
Fine - but why?
Regards
Gerhard

maybe  Google fixed the issue in they Firmware/Cloud system?

Yeah, seems like it. I also had this quirk appear after I had returned from a trip without anything having changed. Controls worked in the Google Home app (spoken or manual), while smart speakers failed any dimming. Removing the lights, syncing, re-adding them and syncing was what it took to fix it.
With that in mind this can probably be closed as "not our bug".


Down-scale fish-welfare

The fish-welfare scene, especially the fish models has far too many polygons

https://github.com/vr4vet/Blue-Sector/blob/fish-feed/Assets/FishWelfare/3D Models/Fish_04/Stor_fisk_4_armature.fbx
Example


error during kb_regen_sessions

When running the kegbot-admin.py kb_regen_session command, I"m getting an error stopping the processing.
"Column 'site_id' cannot be null
Full details: http://dpaste.com/675559/

Have you migrated recently? There was a schema change.

I'm pretty sure I didn't miss any migrations, which schema change do you think might be related?  The output of kegbot-admin.py migrate doesn't show any migrations to apply.

You're right; legit bug!


A pull request body can't link when it's created by Probot

Bug Report
Current Behavior
Probot can create a pull request correctly. But its body don't link to a commit.
I check it with @octokit/rest. And it works! So, I don't think it isn't Github API's problems.
This works
const { Octokit } = require("@octokit/rest");
const octokit = new Octokit({
    auth: "..."
});

let body = 'Repo swaglive/action-demo@0c486e5'

octokit.pulls.create({
   ...
    body: body
})

This doesn't work
    let body = 'Repo swaglive/action-demo@0c486e5'

    await context.github.pulls.create({
   ...
      body: body
    })

Expected behavior/code
When probot create a Pull Request. Its body can link to a commit.
Environment

Probot version(s): 9.11.5
Node/npm version: Node 12.9.1/npm 6.10.3
OS: OSX 10.14.6

Additional context/Screenshots
It's not link to commit. But if I edit and preview, it works.

Update
2020-06-08
This bot is watching repo A and create branch, commit, pull request in repo B.
And it's installed in both repos.

This is good as octokit.
curl -XPOST -H "Authorization: token ..." \
    --data '{"title":"Update action-demo","body":"Repo swaglive/action-demo@0c486e5","head":"update-action-demo-0c486e59ce","base":"master"}' \
    https://api.github.com/repos/../../pulls

so I'm wondering if wrapper context.github is broken.

It's really weird. A pull request sent from Probot is not convert to github ref.
But curl and octokit can do it.

Is the commit created right before the pull request? If so, can you wait 3s before creating the pull request? It might be that the commit data did not replicate yet when you reference it in the pull request

It may also be a case where the bot needs additional permissions to be able to link to a resource. Specifically, when linking to a commit, I assume it would need Repo contents: Read. context.github uses a GitHub App installation token to authenticate, that's the biggest difference.

Is the commit created right before the pull request? If so, can you wait 3s before creating the pull request? It might be that the commit data did not replicate yet when you reference it in the pull request

no, I close pull request and redelivered the same request. It's also not working.

It may also be a case where the bot needs additional permissions to be able to link to a resource. Specifically, when linking to a commit, I assume it would need Repo contents: Read. context.github uses a GitHub App installation token to authenticate, that's the biggest difference.

But my bot have Content: Read & Write
Contents
Repository contents, commits, branches, downloads, releases, and merges


initial basic UI for console logging messages

Very basic UI for the console logging work.  There are plenty of details here that need touch-up, but I wanted to wait to get the signed-off design before chasing after those.  What's done here is basic stuff in place for demo purposes.

I tried to rebase from master, and the diffs are showing a bunch of other changes.  Not sure why this is happening.  I may close this PR and re-open another one.  LMK if there's any preference here.

I'm easy. It would be nice if this didn't have the merged in changes, but if its a pain don't worry.

:shipit:


asyncio.run() cannot be called from a running event loop

Hi,
I get this error when executing rest.serve() with
RuntimeError: asyncio.run() cannot be called from a running event loop
sys:1: RuntimeWarning: coroutine 'Server.serve' was never awaited

I have xpublish 0.2.0, xarray 2022.6.0, uvicorn 0.18.3
I don't have asyncio in my conda list, is it expected ?
Actually I need some more explanations on how it works.
I already have a code using fastAPI and the uvicorn server installed.
Should I launch uvicorn for rest.serve() to work ? I get this error when server is switched off too (when I run it in spyder in a quite new environment).
Thank you

It works now, but I don't know why :-)

I got that same error when starting xpbulish from notebooks. I resolved it by running all script in one cell and put the magic
%%python3 --bg --proc a --err err --out std

on top. It was only a test so the script i.e. the cell was short.
I actually do not know how to access the output via the variables a or  err. if you find out, let me know :)


HCLOUD-3073_Extend-stream-execution-logs_Jorge-Brown

Nodes with no endTimestamp are currently running

Task linked: HCLOUD-3073 Extend stream execution logs


[Bug]: Fix TTGO build

What happened?
TTGO Github Actions builds works, but without the display.
I'm working on an automated path for TFT_eSPI lib.
Version
v3.0.1
Distribution
Desktop
OS
Linux
What browsers are you seeing the problem on?
Chrome
If applicable, What Listener Clients are You Using?
No response
TallyArbiter configuration
No response
Relevant log output
No response
Error stacktrace (if applicable)
No response

I noticed for the atom builds, and I assume it’s the same for all the esp variants, it comes hard coded with a TA server IP of <IP_ADDRESS> or something. Which then gets compiled into the binaries we offer for download. This makes them not too useful, right?

Yes, hard-coding the host is useless.
I think that we can replace host setting page with MDNS discovery (or leaving it as "manual setting mode" but adding MDNS).
I'll remove hard-coded IPs when I finish working on flashing devices from UI.

I like what some of the other various esp projects do where they run either a captive portal or a separate SSID on first boot where you can then put in all this config info. MDNS is good. I also anticipate where I might want the device on wifi but connecting to my cloud instance of TA where MDNS would not apply. So the field needs to support both IP and domain name.

The Atom builds do have a captive portal at the moment, when it can't find the ssid to connect to it will startup an AP where you can change the settings

Fixed in #358


main process Store shouldn't use default values.

The current Store tool requires a default value to be set. Usually, it's an object with empty field.
In the frontend, it means I have to check if a field on the object exists, rather than checking the existence of the object, which isn't intuitive.
i.e I want to do if (user) to see if there is a user, not if (user.id) to see if there is a user.
We should check if the electron-store library allows setting the values to undefined, then change the Store tool.

it done


added renderChildrenForDate prop

Add prop renderChildrenForDate which will allow to render any component in addition to day of month.

Can you expand a bit on the use case here?

@martijnrusschen I just need to add text for date. See screenshot.

Very nice idea, I also need this to show some tooltips for given dates, with customer renderer this would be trivial.

Can we get the merge conflicts resolved so I can merge this?

I also need this to customize cell content !
But why a render prop that only adds children to date ? I think a better idea would be to have a render prop for all date cell, isn't it ?


IssueID:1526:improve flash driver framework

[Detail]
Improve flash driver framework.
[Verified Cases]
Build Pass: helloworld_demo@haaseduk1
Test Pass: helloworld_demo@haaseduk1

感谢提交 Pull Requests！
Thanks for submitting a pull request.

Security Check : 83d94eb77d71ae77976ceaabb1d8501c9028e7f1

auto build success,number:42


tabs disappear after changing projects (ctrl+Alt+P)

Appear again after going to tabs settings, disable, and enable.

Happens to me also (pulsar-bin 1.115.0-1).
I don't know if this is relevant: It did happen to me also when using other atom-project-manager, where it was fixed by installing atom-project-util package.


BRS-I acting outside its own scope is a contradiction

In Section 2.1, "BRS-I Recipe", we have this statement:  "A key tenet of BRS-I is constraining behavior outside the scope of BRS-I."  To me, that reads as an impossible contradiction, saying that recipe BRS-I acts outside the realm in which it may act.

I believe this is already taken care hence closing.

The consensus of the Architecture Review Committee is that this sentence reads as self-contradictory:  "A key tenet of BRS-I is constraining behavior outside the scope of BRS-I."  Please find different words to convey what you really mean.

@jhauser-us :
"A key tenet of BRS-I is to ensure there is no unexpected behavior in a generic OS even when there are  features implemented in the system beyond the scope of BRS-I."
Is it acceptable?

This is still contradictory.  I believe the previous paragraph provides most of the intended mandate.  I'd propose dropping the problematic paragraph, and instead adding a new final sentence on the previous paragraph that states: "Any additional firmware features that cause anomalous and unexpected behavior must be disabled by default, and only enabled by opt-in."

Sure. Thanks!


About tensorflow distributed training

Hello, have you tried tensorflow distributed training? I tried distributed training but was unsuccessful!

Hi, I am not familiar with tensorflow distributed training.
I guess PyTorch would be easier for that however.
Did you encounter issues with GPU memory on tensorflow? Training shouldn't be very expensive given the low param count.


Add: Amigos TV Chiquimula

Channel Name
Amigos TV Chiquimula
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
No response
Country
GT
Subdivision (optional)
No response
City (optional)
Chiquimula
Broadcast Area
c/GT
Languages
spa
Categories (optional)
religious
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://amigostv.com.gt/
Logo
https://scontent-yyz1-1.xx.fbcdn.net/v/t1.6435-1/162699231_125115042954479_1031828036337803300_n.jpg?stp=dst-jpg_p200x200&_nc_cat=109&ccb=1-7&_nc_sid=c6021c&_nc_ohc=WeXU8sV41lAAX-YK-y4&_nc_ht=scontent-yyz1-1.xx&oh=00_AfD4xPkUqviLTktTcjDHlkGbp5PMIeEreitB9fOis3mHHw&oe=64990405
Notes
https://tv91.hostingnuclear.com:19360/amigostv/amigostv.m3u8

Please update your request:

logo URL must use the HTTPS protocol

https://github.com/iptv-org/database/blob/master/CONTRIBUTING.md#channels

Corrected


Quote/unquote values of TEXT_MAP carrier when passing via HTTP headers

Unit tests in this repo can be improved significantly by using a real tracer implementation, such as https://github.com/opentracing/basictracer-python

lgtm - I'll try it with crossdock once you're landed


safeguards to return up to max allowed (10000) items upon searches

coverage: 95.652% (-1.1%) from 96.73%
when pulling 18e41f9d4712546b1ef8c350bf71b93963db2a76 on feature/stac-max-return
into e9fae14bf8060c3371f2f98dc4e5347869987141 on main.


51323 clarification

Existing issue https://github.com/Microsoft/vscode/issues/51323 closed.

@ShayCormac1963 You can change keybindings and settings by changing your user keybindings.json and settings.json files. The defaults only exist in memory.

I think this means "Disregard the error.   Override the specific key binding in user settings, if needed."

#51323 was closed by a fix, the little text after the close mark read:

@sandy081 closed this in 37a59a282aa66ac91c77daa8358d8241d3791709 2 days ago

@Gubith Not sure what you mean and how it is related to #51323. Can you please elaborate?

Thread 51323 shows closed still but I was able to post, maybe it was reopened.


small modifications to optionData

Change fire action on menus to accept enter

For my specific use case .. I needed to be able to fire options using enter. but I guess having it customizable should be better. is there already a way to do that ?

Add a more size-dynamic checkbox icon

since my fonts size were a bit large it caused checkboxs to look smaller relative to font size since it only had two fonts. currently it scales with the font and can look suitable for all sizes I tested.

store previous index in OneOf menu option

I needed that for situation where I have another UI element that is like a slide show or charachter chooser. where I needed to hide the previous one first then add make the current one visible.

Add a more size-dynamic checkbox icon
+1 for a more size-Dynamic checkbox icon. But I don't quite like way it's being resized, on some scale ratios it can be blurry, uneven pixels. The reason I chose two different graphics for a small and large checkbox is that the shadow is a bit different on both sizes and I wanted the pixel-crisp style.
This can be improved sure.
I think that it' would be best if the MenuOption graphics be more user-customizable somehow,
Like expand the OptionStyle to include a tilesheet, frame, size
or even I could even rewrite the whole thing to dynamically generate a checkbox and the shadow (optional) at any size, and store it in a bitmapdata and use that. I think this would be the best.
Also I could just code-generate the shadows on the GUI arrows to a custom color with more user parameters (on-off, shadow depth, color etc)
Change fire action on menus to accept enter
Yes, I have thought of this, but there are times where I really need to have a separate START button event, like when I need to close a pause menu!
->press start -> display flxMenu -> press start -> close the flxMenu
I guess I could use a flag under FlxMenu to indicate whether or not the user wants something like that.
e.g.
FlxMenu.flagStartButtonSelects:Bool
// true : The start button sends fire input to options
// false : it does not

store previous index in OneOf menu option
Yes this is useful!

Can I just merge one of your commits? "store previous index in OneOf menu option"?
I'll work on the other matters, and probably make other minor changes.  Sorry I'm kind of new to collaborating with other people, I had always been a lone coder mostly.  😃

cool .. thanks for your feedback and suggestions :D .
and yes, git allows for reverting old commits so I just did that in PR #5 . I think we can close this one now.


Update gpu.go to support older amdgpu

Unblock users trying to run on older GPUs like AMD RX 580 when setting env vars ROC_ENABLE_PRE_VEGA=1 and HSA_OVERRIDE_GFX_VERSION=8.0.3 which should fix the error from https://github.com/ollama/ollama/blob/main/gpu/gpu.go#L62 and https://github.com/ollama/ollama/blob/main/gpu/amd_linux.go#L200 about gpu being too old.

Nope, doesn't seem to work for me, at least on an Ubuntu-based distro using ROCm drivers 6.1.3 or 6.0.0 or even back to 5.7.3 so closing.


Disabling required extension doesn't work from child config

Hi!
It looks like disabling an extension required in parent config doesn't work from the child config.
Assuming we have parent-child configs relationships as following:
Parent, which is shared among many other projects:
require:
  - rubocop-rspec
  - rubocop-rails
...

Child, in particular project which doesn't use rspec:
inherit_from: shared/.rubocop.yml

RSpec:
  Enabled: false
...

Runtime details:
ruby 2.5.1p57
rubocop (0.74.0)
rubocop-rails (2.2.1)
rubocop-rspec (1.35.0)

Expected behavior
Definition in the child config should take precedence over required directive.  So the expected behavior would be to suppress all violations related to disabled extension.
Actual behavior
Running Rubocop in debug mode produces the following info:
$ rubocop -E -S -d --format simple

For /: configuration from /.rubocop.yml
Inheriting configuration from /example/.rubocop.yml
configuration from /usr/local/bundle/gems/rubocop-rspec-1.35.0/config/default.yml
configuration from /usr/local/bundle/gems/rubocop-rspec-1.35.0/config/default.yml
Default configuration from /usr/local/bundle/gems/rubocop-0.74.0/config/default.yml
configuration from /usr/local/bundle/gems/rubocop-rails-2.2.1/config/default.yml
configuration from /usr/local/bundle/gems/rubocop-rails-2.2.1/config/default.yml
For /example configuration from /example/.rubocop.yml
AllCops/Exclude configuration from /.rubocop.yml
Inheriting configuration from /example/.rubocop.yml

and some violations detected for rspec extension (reduced for clarity):
== example/spec/runner_spec.rb ==
C: 32:  7: Example has too many lines [6/5]. (http://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/ExampleLength)

As a result it reduces the power of the configs inheritance as soon as you have an extension used by all but a few children.
Important note
It does work as expected if disabling happens in the same parent file. For example:
Parent:
require:
  - rubocop-rspec
  - rubocop-rails

RSpec:
  Enabled: false
...

Child:
inherit_from: shared/.rubocop.yml
...

Works as expected (rspec related violations are being suppressed).

@aliaksandrb Thanks for your report. Could you put together a complete example? I tried to reproduce your issue with the information given but failed. See here: https://github.com/buehmann/rubocop-issues/tree/7640
➜  rubocop-issues (7640) bundle exec rubocop
Inspecting 2 files
..

2 files inspected, no offenses detected

and when I enable the RSpec department in .rubocop.yml:
➜  rubocop-issues (7640) ✗ git diff
diff --git a/.rubocop.yml b/.rubocop.yml
index fd57358..4a111f4 100644
--- a/.rubocop.yml
+++ b/.rubocop.yml
@@ -1,4 +1,4 @@
 inherit_from: shared/.rubocop.yml

 RSpec:
-  Enabled: false
+  Enabled: true
➜  rubocop-issues (7640) ✗ bundle exec rubocop
Inspecting 2 files
.C

Offenses:

spec/runner_spec.rb:4:3: C: RSpec/ExampleLength: Example has too many lines [11/5].
  it 'foo' do ...
  ^^^^^^^^^^^

2 files inspected, 1 offense detected

Hi @buehmann, thanks for looking into it!
I've played around with your repository and found the difference with my setup, which had shown that the problem tends to be on my side.
In fact, my directory structure is more complicated and looks like rails one (meta gem with multiple gems within it). And between the root /.rubocop.yml and /xxx/yyy/spec/runner_spec.rb file there is /xxx/.rubocop.yml which has no
RSpec:
  Enabled: false

I was thinking that rubocop adopts config relative to the $pwd it being ran, but it looks like it checks the closest config relative to the every file being analyzed (wow, thats a lot of parsing if you have a mono-repo with many configs).
So my fault, works as expected 👌 I am closing this issue.

Good to hear that. Yes, it is the closest config that is relevant for every file, but RuboCop makes sure to parse every config only once. That config is then reused for all files checked in the subtree (unless there is another config in a subdirectory, of course).


DART_VM_OPTIONS for self-executables not working!

As mentioned on README, Dart 3.4.0 supports DART_VM_OPTIONS for self-executables:
README.md:
...
### Dart Runtime

- Dart VM flags and options can now be provided to any executable generated
  using `dart compile exe` via the `DART_VM_OPTIONS` environment variable.
  `DART_VM_OPTIONS` should be set to a list of comma-separated flags and options
  with no whitespace. Options that allow for multiple values to be provided as
  comma-separated values are not supported (e.g.,
  `--timeline-streams=Dart,GC,Compiler`).

  Example of a valid `DART_VM_OPTIONS` environment variable:

   DART_VM_OPTIONS=--random_seed=42,--verbose_gc

...

Example:
foo.dart:
void main(List<String> args) {
  print("FOO>> args: $args");
}

run-foo.sh:
#!/bin/bash

dart compile exe foo.dart

export DART_VM_OPTIONS=--random_seed=42,--verbose_gc
echo "DART_VM_OPTIONS: $DART_VM_OPTIONS"

echo "Running executable:"
./foo.exe

Output of ./run-foo.sh:
Generated: /private/tmp/dart-test-foo/foo.exe
DART_VM_OPTIONS: --random_seed=42,--verbose_gc
Running executable:
Usage: dart [<vm-flags>] <dart-script-file> [<script-arguments>]

Executes the Dart script <dart-script-file> with the given list of <script-arguments>.

Common VM flags:
--help or -h
  Display this message (add -v or --verbose for information about
  all VM options).
--packages=<path>
  Where to find a package spec file.
--define=<key>=<value> or -D<key>=<value>
  Define an environment declaration. To specify multiple declarations,
  use multiple instances of this option.
--snapshot-kind=<snapshot_kind>
--snapshot=<file_name>
  These snapshot options are used to generate a snapshot of the loaded
  Dart script:
    <snapshot-kind> controls the kind of snapshot, it could be
                    kernel(default) or app-jit
    <file_name> specifies the file into which the snapshot is written
--version
  Print the SDK version.

For some reason it's always showing the dart CLI help message.

dart --version:
Dart SDK version: 3.4.0 (stable) (Mon May 6 07:59:58 2024 -0700) on "macos_x64"

FYI: @bkonyi

Thanks for the heads up @gmpassos. I'm able to reproduce and it looks like there was some oversights in the implementation that wasn't caught by testing. I have a fix up for review here.

... I have a fix up for review here.

Please add documentation for DART_VM_OPTIONS, especially for self-executables. This is not documented anywhere.

Cherrypick request has been filed here: https://github.com/dart-lang/sdk/issues/55818.

Please add documentation for DART_VM_OPTIONS, especially for self-executables. This is not documented anywhere.

There's not any obvious spot to put this on the website since it's relatively niche functionality, but I've added documentation in the SDK that should make this a bit easier to discover: https://dart-review.googlesource.com/c/sdk/+/367800

... it's relatively niche functionality.

The default max heap size is 30GB:
https://github.com/dart-lang/sdk/blob/f4cc1eb6480b7838fe30c3700b04974935739b49/runtime/vm/globals.h#L62
IMHO, every self-executable in production should define its memory limit, since running any application with a heap limit higher than the available memory is a recipe for disaster.
Since the only way to define the max heap size in a self-executable is by using DART_VM_OPTIONS, this shouldn't be treated as a hidden property.

I believe this can be closed ?

I believe this can be closed ?

It's already closed :-)


Move partial parsing to end of parsing. Switch to using msgpack for saved manifest.

resolves #3217, #3292
Description
This pull request switches to using msgpack for the partial parsing saved state file, and moves the partial parsing save point to after patches are applied and refs and sources are resolved and docs rendered.
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

Things that were changed to support using msgpack instead of pickle:

Removed MutableMapping as a superclass of BaseConfig. The python code handling subclasses of typing.MutableMapping was buggy and problematic for serialization. There was also a bug in the implementation, so I suspect those features weren't heavily used. I did retain the methods to allow getting and setting a config attribute as a dictionary, since we had tests that required that.
Serialization had a hard time with the abstract base class PackageAwareCache, so I refactored that code to avoid it. In addition I renamed those classes from  '...Cache' to '...Lookup' because they aren't caches.
The various node classes used a resource_type field metadata 'restrict' setting to force one ParsedNode class or another, but that only worked with Hologram. I had to add a mashumaro SerializableType and instantiate a particular node class based on the resource_type, since many of these node classes are not differentiated at all on attributes and we are removing empty attributes.
I had to do a similar thing to the SourceFile and SchemaSourceFile objects

Changes to support partial parsing:

I split SourceFile up into SourceFile and SchemaSourceFile, since they used many different attributes. Mypy had a hard time with some of that. I did my best to make it happy but had to resort to 'Any' for 'file' in the FileBlock class.
I split out Schema parsing so that all non-schema files are parsed before all schema files. That enabled us to resolve node unique_ids when processing schema files and skip the separate patching step (except for sources).
Switched to used file_ids of the format: 'my_package:://models/my_model.sql'. This positions us better for not having access to the actual filesystem.
Moved a bunch of source patching code from the schema parser where it was to the source patcher where it belongs. There is still common code in the parse generic test codepath, but there is less confusion about what object is doing what.
Removed old code that supported the old method of partial parsing (parse_with_cache, sanitized_update, etc).
Added a 'created_at' attribute to nodes. This enables us to skip processing nodes that were created before parsing started.
Added log messages for cases where partial parse is not enabled due to some issue.
Added core/dbt/parser/partial.py with the new partial parsing code
Created test/unit/test_partial_parsing.py and test/integration/067_partial_parsing_tests

Note: testing of most filetypes has not been completed, but that should mainly involve changes in core/dbt/parser/partial.py. The rest of it should be more or less stable.

@gshank I've only taken for a brief spin so far with our internal analytics project, and it works magnificently (and very quickly) when there are no file changes.
When I do make changes and re-parse, I noticed two odd things:

Hooks seem to be parsed twice. We only have one on-run-end hook defined, but during the Manifest load step, I see a compilation error: dbt found two resources with the name "project_name-on-run-end-0"
Dependencies seem to be missing when re-parsing changed resource files / resource properties.

When I get around the hook error (by commenting it out + full re-parse), and I change a model file, I see a dependency-related compilation error:
Partial parsing enabled: 0 files deleted, 0 files added, 1 files changed.
Compilation Error in model model_name (path/to/model_name.sql)
  Model 'model.project_name.model_name' (models/path/to/model_name.sql) depends on a source named 'source.table' which was not found

If I do the same and change a .yml file, e.g. editing a test definition on a source table, I see:
Partial parsing enabled: 0 files deleted, 0 files added, 1 files changed.
Encountered an error:
'source.fishtown_internal_analytics.source.table'

Does that look familiar to you?

The double hook thing is because I'm not preventing hook parsing when partial parsing. I'll fix that.
I'm not surprised about the source thing; I haven't tested source changes at all, only models and model sections in schema files. Will test those next.

Got it, makes sense. Confirmed that the hook-related error went away with the latest commit. Now if I edit just a model file (models/whatever.sql) that depends on other models (only ref, no source), I see:
Partial parsing enabled: 0 files deleted, 0 files added, 1 files changed.
Encountered an error:
'SchemaSourceFile' object has no attribute 'nodes'

Which looks like it's coming from:
  File "/Users/jerco/dev/product/dbt/core/dbt/parser/partial.py", line 182, in update_mssat_in_saved
    unique_id = old_source_file.nodes[0]

I think you don't have Mashumaro 2.5, which is needed to distinguish between SourceFile and SchemaSourceFile. Are you just running from a branch? You probably need to do pip install -r dev-requirements.txt -r editable-requirements.txt

Ok, I was able to get this working! Thanks for helping me debug the error above.
I'm going to jot down some of the things I've noticed while trying this out (in addition to the issues with sources that I noted above). My goal is to help with sketching out test cases—let me know if it would be better to note these elsewhere!

If I disable a model that is ref'd by another model, partial parsing does not raise an error
If I delete a model (remove the .sql file) that is ref'd by another model, it encounters a key error:

Encountered an error:
'model.package_name.deleted_model_name'

  File "/Users/jerco/dev/product/dbt/core/dbt/parser/partial.py", line 193, in delete_node_in_saved
    node = self.saved_manifest.nodes.pop(unique_id)

In both cases, I was expecting to see the message from get_target_not_found_or_disabled_msg: Model ... depends on a node named '...' which is disabled / was not found. (I do see this error with partial parsing if I edit a ref to a bad reference.)
In all cases, it's very fast :)
One funny thing I noticed: the path_count in perf_info.json is now the number of changed files detected by partial parsing, rather than the total number of files in the project. That... makes sense! For the purposes of tracking these metrics, would it be possible to include a total file count as well (perhaps sourced from partial_parse.msgpack)? If that's too tricky, we could switch to using total resource count (models + tests + the rest) as our measure of project size.

Good catch on the refs. Will have to look for those and re-schedule them for parsing.
We could do a total file count too, probably by looping through the files dictionary and counting them. At the end of parsing, maybe.

This is taking me a long time to go through, and I'm not sure I have a full grasp of the edges of this change since it's so big. I would like to see comments on all the individual functions/methods describing more of why they need to exist. Most of them it's clear what they do, but I'm not really sure how they fit into the bigger picture if that makes sense.


remove compile dep on rxjava

NetflixOSS » suro » suro-pull-requests #35 ABORTED

suro-pull-requests #205 FAILURE
Looks like there's a problem with this pull request


Get coordinates and bearing if MyLocationEnabled is set to true

SUMMARY
I would like to get location coordinates and bearing if MyLocationEnabled = true.
DETAILS
An event like OnLocationChanged() which will provide coordinates of location + bearing
PLATFORMS

[x] Android
[ ] iOS
[ ] UWP

We can't support it because OnMyLocationChangeListener in Google Maps SDK for Android does not support.
https://developers.google.com/android/reference/com/google/android/gms/maps/GoogleMap.OnMyLocationChangeListener.html
I have a plan to LocationSource support that can using your own location source.
https://developers.google.com/android/reference/com/google/android/gms/maps/LocationSource


1598/variant product alert

Fix #1606
Hopefully pretty straightforward.

Any updates on this? I thought it was a pretty straightforward fix.

Looks good. We might need to document the new abstract_forms module in the changelog.
Can you also update it against master? If not then i'll can take care of it.
Thanks!

I think I see what I did. I created a separate pull request for the abstract_forms part: https://github.com/django-oscar/django-oscar/pull/1610
This was just supposed to be https://github.com/john-parton/django-oscar/commit/a92e72e1828f668cc852391e5e0265ffd6060525
Sorry, I'm still really new to git & github. (Still used to bzr)
I could create a new pull request for just the tiny change, and then you could review https://github.com/django-oscar/django-oscar/pull/1610 separately?
Let me know what I need to do.
Thanks.

The easiest is to create a new PR with just the email fix. After that you can rebase #1610 on master and we can merge that one. :+

Okay, I created the new PR: https://github.com/django-oscar/django-oscar/pull/1635
Sorry for the confusion. I'm trying to do some "easy" things to familiarize myself with github and oscar.
Thanks again!


Designing a custom layer: grad_req='write' missing?

In the MyDense block, I am wondering whether grad_req='write' is missing for weight and bias? After all, the gradients are needed for them.
Or is graq_req='write' the default? If so, I wonder why you write it explicitly above. Would be good to add a comment.

Good point! I'll look into it
On Nov 18, 2017 6:38 AM, "mseeger"<EMAIL_ADDRESS>wrote:

In the MyDense block, I am wondering whether grad_req='write' is missing
for weight and bias? After all, the gradients are needed for them.
Or is graq_req='write' the default? If so, I wonder why you write it
explicitly above. Would be good to add a comment.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zackchase/mxnet-the-straight-dope/issues/360, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACR4ziVJmXqVbXLMJun4IsNfUQ84pGW3ks5s3uvIgaJpZM4QjBbp
.


Please clarify license?

Hi @bdavid68 nice code, thanks for sharing with the community. Can you lease clarify LICENSE that is distributed, hopefully MIT?

Thank you, @rturk !


IFeatureCollection implementation questions

I have read the source code of IFeatureCollection and FeatureCollection, I notice IFeatureCollection has method object this[Type key] and notice the implementation of FeatureCollection use two dic to hold the values. now i am questing about why just merge the two dic and makes IFeatureCollection just inherit IDictionary<Type, object>,  thanks for some guys who can help me! #

IDictionary has a much larger API surface than we need our want, and the indexer behaves differently for missing values.
The reason there are two collections is for layering. One collection can temporarily wrap another to augment functionality without copying the whole collection.

@Tratcher Thanks for your time. I got it.


Keybinding: Allow colon to be a valid keybinding

Working on a VIM extension. A core key binding of VIM is :.
The below is a workaround:
     {
        "key": "Shift+;",
        "command": "extension.vimMode_colon",
        "when": "editorTextFocus"
      },

but it doesn't work on international keyboards.

@jpoon I can't really add support for that. The keybinding dispatching occurs in a keydown browser event handler, where I only get the keyCode and the modifiers state (i.e. keyboard layout independent, not what would be produced in a keypress).
We need to do something special for vim where all typed characters can be "trapped" and redirected to an extension

@jpoon We cannot add colon as a valid keybinding for now. Please see #713 where the problem is explained. I also suggest #713 as the tracking issue instead of having an issue for each individual desired keybinding character.


Update PedicleScrewPlanner.py

Commented out the sentence 'showsiderselector=True`
No error is prompted again

This change is not needed and merging it would break the current implementation, because showSidesSelector is not a mandatory argument of the DefineROIStep constructor - see:
https://github.com/lassoan/PedicleScrewSimulator/blob/master/PedicleScrewSimulator/PedicleScrewSimulatorWizard/DefineROIStep.py#L9
You either haven't pulled the latest version of the extension from this repository or you still have the old implementation in the "Additional module paths".


code about anchor_manipulator.py

Hi, HiKapok:
I have a question about anchor_manipulator.py:
anchors_to_gt_mask  should move to **_else statements_**? code below:

    # negtive values has no effect in tf.one_hot, that means all zeros along that axis
    # so all positive match positions in anchors_to_gt_mask is 1, all others are 0
    anchors_to_gt_mask = tf.one_hot(tf.clip_by_value(match_indices, -1, tf.cast(tf.shape(overlap_matrix)[0], tf.int64)),
                                    tf.shape(overlap_matrix)[0], on_value=1, off_value=0, axis=0, dtype=tf.int32)
    # match from ground truth's side
    gt_to_anchors = tf.argmax(overlap_matrix, axis=1)

    if gt_max_first:
        # the max match from ground truth's side has higher priority
        left_gt_to_anchors_mask = tf.one_hot(gt_to_anchors, tf.shape(overlap_matrix)[1], on_value=1, off_value=0, axis=1, dtype=tf.int32)
    else:
        # the max match from anchors' side has higher priority
        # use match result from ground truth's side only when the the matching degree from anchors' side is lower than position threshold
        left_gt_to_anchors_mask = tf.cast(tf.logical_and(tf.reduce_max(anchors_to_gt_mask, axis=1, keep_dims=True) < 1,
                                                        tf.one_hot(gt_to_anchors, tf.shape(overlap_matrix)[1],
                                                                    on_value=True, off_value=False, axis=1, dtype=tf.bool)
                                                        ), tf.int64)

Thank you!

@zhangjiamin why?


Some dropdowns not populated correctly

When I reboot my PC and restart Chrome, choose to load a saved state from the dropdown, I see what look like variable names in some dropdowns.
To Reproduce
Steps to reproduce the behavior:

Start PC
Start Chrome
Use factoriolab bookmark
Select a saved state and choose 'Load Saved State'
The dropdowns in the Objectives section are filled with what looks like variables names rather than text. (See screenshot)
Some of the column headings in the Factory section also contain variable names

Expected behavior
Dropdowns with text rather than variable names
Screenshots

(Note I pulled down the top dropdown to shown that every option is using the variable name)
Desktop (please complete the following information):

OS: Windows 10 64-bit Pro
Browser Chrome
Version 109.0.5414.120 (Official Build) (64-bit)

**Additional Information
If I just use 'Skip' after starting factoriolab, the headings are correct, From there, load saved state and aevrything is good.
 Use bookmark again, load saved state, problem reoccurs.

That is extremely strange. Does this only occur after a restart of your PC?
That dropdown was only recently converted to be localized (the text used to be hard coded) so I have to wonder if something is cached on your machine. You could try doing a hard reload of the page (shift + refresh or shift + F5).
I can't seem to reproduce this issue no matter what I do, and I don't see anything in the code that would cause this issue. z
What do the "Items," "Wagons," and "Pollution" column headers in the list view look like when this happens? Those were also updated as part of the same pull request.

I'll produce some more diagnosis when I get back from my 2.5 week vacation!

Enjoy your vacation :)

That is extremely strange.
You could try doing a hard reload of the page (shift + refresh or shift + F5). I can't seem to reproduce this issue no matter what I do, and I don't see anything in the code that would cause this issue.

If I load chrome, load factoriolab, load the named saved state, I have the issue as I describe it.
If I then hard reload the 'corrupt' page, as you suggest, then it is displayed properly.
If I then close chrome, open chrome, load factoriolab, then load the named saved state, the issue is still there!
FWIW, the name of the saved state is '1K + power + shells' and the URL is https://factoriolab.github.io/list?z=eJxFisEKg0AMRP8mhzklBa0e1WXtUhD.YA6lPaooeNxvd1eFJjDvZcjiPjBVpUtgnZ1uhBXyNYQYWJ5Z5ZS1nQEfPZTdclpeGN109Q.5GTt4pH--bgY0HJKbpqO.y.dF2QA0wDij7fGfSvbnAXkVJ0s_&v=7

What do the "Items," "Wagons," and "Pollution" column headers in the list view look like when this happens? Those were also updated as part of the same pull request.

FWIW, I have added a new saved state, and the error no longer occurs. Suggest this issue can be closed, and will do so, but your code, so reopen if you wish.

Thanks for the info, I want to at least check out your old saved state to see if I can repro this issue. It's entirely possible there is a bug in the migration that is causing issues.

Nope, I still can't duplicate this problem with the exact same saved state.


Implement sentiment analysis

Motivation
A reoccurring request I see from mods is that they want to remove comments from (and sometimes ban) users from specific subreddits that are often toxic/antithetical to the member of their subreddit. However, in many cases they do not want to additional context by using RegexRule to check for keywords -- or some other approach. Sometimes this is because they don't know how to write a regex (understandable) but other times its because defining user intent is fundamentally hard and not a task well-suited to just regex.
This makes CM's behavior "blind" to what the user is actually doing in their subreddit which isn't good. Users who participate in toxic subs may be doing so antagonistically (defending the mod's subreddit) or their behavior in the mod's subreddit may plainly just be independent of their history. So acting solely on that history is often not enough to make a good judgement call.
Adding sentiment analysis to the activity being checked, while not a complete solution, is low-hanging fruit for providing SOME signal on what user intent is. It also requires no configuration by the moderator (unlike regex) to be effective.
Implementation
Use VADER sentiment analysis to provide another data point for determining intention of a user. Specifically, the javascript port of the original python implementation.
VADER was chosen over something older like AFINN because it is more attuned to "social media" like text which, while not exactly reddit, is closer than traditional methods.
For the actual implementation we will basically copy-paste the Regex Rule (schema) and replace detection with sentiment analysis. This gives the user the ability to test the current activity as well as sentiment for historical activity (even more context!)

Implemented in 0.11.1


migration code for Node

Make new Node have as_is and to_be fields, migrating from current Node struct.
Existing field values will be put to to_be fields, because no Node setting has ever been applied to modules via review-web.
Related to https://github.com/aicers/review-web/pull/129

Please assign this to @BLYKIM


Making common subclass for Bigtable DirectRow and ConditionalRow.

This is a follow-up to #1557 and prevents strange-ly true statements like isinstance(cond_row, DirectRow).
Sorry it took me so many days. Code has been completely written for 2+ days but I haven't ever had my laptop near internet long enough to push it.

LGTM

@tseaver I rebased after #1602. Will merge once Travis passes.


checkbox - incorrect styling

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Styling as illustrated in the online demo app
What is the current behavior?
Styling looks incorrect:

What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, browsers are affected?
2.0.0-beta.1
Is there anything else we should know?

@michaelb-01 Where is your plunker example to reproduce your issue? Most likely you forgot to include the core theme.

You were right, I had forgotten to include the theme, i've included the following and now the checkbox correct:

However now nothing happens when I click it.. (no errors in the console though)

@michaelb-01 What do you expect to happen when you click the checkbox?
In case you missed the docs for checkbox: https://material.angular.io/components/component/checkbox

Hi @dahaupt, yes i'm expecting to be able to toggle the checkbox as in the link you provided, however nothing happens when I click the checkbox (no tick etc. but no errors either). I created a quick project with angular cli and the checkbox worked fine there so i'm not sure what i've done.. Its a meteor-angular2 project, I don't know if there are any known issues with meteor?

If it has an [(ngModel)], make sure you have defined it in your component code. Make sure the options are valid. Please make a plunkr reproducing the issue. I'd be happy to take a look.

Hi @wbhob, I can't think how to make a plunkr without uploading my whole project, i'm literally just trying the example from the demo site (so no ngModel):
Check me!
I've just updated all my angular packages to check if that was the problem but still no luck, this is my package.json:
{
  "name": "Pipe",
  "private": true,
  "scripts": {
    "start": "meteor run",
    "test": "meteor test --driver-package practicalmeteor:mocha",
    "test:ci": "meteor test --once --driver-package dispatch:mocha-phantomjs",
    "postinstall": "typings i",
    "step": "node ./git-helpers/step",
    "desktop": "meteor-desktop"
  },
  "devDependencies": {
    "@types/chai": "^3.4.33",
    "@types/hammerjs": "^2.0.33",
    "@types/mocha": "^2.2.32",
    "chai": "3.5.0",
    "chai-spies": "0.7.1",
    "meteor-desktop": "^0.4.0",
    "minimist": "^1.2.0",
    "typings": "^1.3.3"
  },
  "dependencies": {
    "@angular/common": "~2.4.0",
    "@angular/compiler": "~2.4.0",
    "@angular/core": "~2.4.0",
    "@angular/forms": "~2.4.0",
    "@angular/http": "~2.4.0",
    "@angular/platform-browser": "~2.4.0",
    "@angular/platform-browser-dynamic": "~2.4.0",
    "@angular/router": "~3.4.0",
    "@angular/material": "^2.0.0-beta.1",
    "@types/mocha": "^2.2.33",
    "angular2-meteor": "^0.7.1",
    "angular2-meteor-accounts-ui": "^0.8.0",
    "angular2-meteor-polyfills": "^0.1.1",
    "angular2-meteor-tests-polyfills": "0.0.2",
    "babel-runtime": "^6.18.0",
    "bcrypt": "^0.8.7",
    "hammerjs": "^2.0.8",
    "meteor-node-stubs": "0.2.3",
    "meteor-rxjs": "0.3.0",
    "reflect-metadata": "^0.1.8",
    "rxjs": "5.0.1",
    "zone.js": "^0.7.6"
  }
}

Then i'm including angular material in my ngmodule:
import { MaterialModule } from '@angular/material';

...
imports: [
    MaterialModule.forRoot()
],

...

Then I include the theme in my index.html:
<link href="https://rawgit.com/angular/material2-builds/master/core/theming/prebuilt/indigo-pink.css" rel="stylesheet">
Have I done anything wrong?

So i've figured out part of the problem, the indigo-pink theme I was using had 'mat-' as a prefix (e.g. mat-checkbox-checked) but the html generated  used 'md-' as a prefix for all the classes... Which one is correct and how should I unify them?

md if you're using the npm beta 1 version, mat if you're using github build
Wilson Hobbs
CEO/Founder/Developer at Canal
11th Grade at The Lovett School
Personal Information
E-mail<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Website: www.wilsonhobbs.com (https://www.wilsonhobbs.com)
Twitter/Instagram/Facebook: @wbhob
Canal Information
E-mail<EMAIL_ADDRESS>Web: www.getcanal.com (https://www.getcanal.com/)
Twitter/Instagram/Facebook: @getcanal
On Feb 15, 2017, 3:36 AM -0500, michaelb-01<EMAIL_ADDRESS>wrote:

So i've figured out part of the problem, the indigo-pink theme I was using had 'mat-' as a prefix (e.g. mat-checkbox-checked) but the html generated used 'md-' as a prefix for all the classes... Which one is correct and how should I unify them?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/angular/material2/issues/3060#issuecomment-279948684), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEPIEuJDtQ87S4MvgzD8_dEgzHXDxG0uks5rcrkDgaJpZM4L-Nl4).

Presumably these will be unified? which one will be used in the future?

No, I believe it is universally mat- now.
Wilson Hobbs
CEO/Founder/Developer at Canal
11th Grade at The Lovett School
Personal Information
E-mail<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Website: www.wilsonhobbs.com
Twitter/Instagram/Facebook: @wbhob
Canal Information
E-mail<EMAIL_ADDRESS>Web: www.getcanal.com
Twitter/Instagram/Facebook: @getcanal
On Feb 15, 2017, 3:08 PM -0500, michaelb-01<EMAIL_ADDRESS>wrote:

Presumably these will be unified? which one will be used in the future?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes, all the css is mat- everywhere now.


cannot import pyasdf

I just installed pyasdf on my Mac, and I tried importing it in ipython, which resulted in the following error:
`In [1]: import pyasdf
AttributeError                            Traceback (most recent call last)
 in
----> 1 import pyasdf
~/miniconda/envs/gmprocess/lib/python3.7/site-packages/pyasdf/init.py in
11
12 from .exceptions import ASDFException, ASDFWarning, WaveformNotInFileException
---> 13 from .asdf_data_set import ASDFDataSet
14
15
~/miniconda/envs/gmprocess/lib/python3.7/site-packages/pyasdf/asdf_data_set.py in
63     SUPPORTED_FORMAT_VERSIONS, MSG_TAGS, MAX_MEMORY_PER_WORKER_IN_MB,
64     POISON_PILL, PROV_FILENAME_REGEX, TAG_REGEX, VALID_SEISMOGRAM_DTYPES
---> 65 from .query import Query, merge_query_functions
66 from .utils import is_mpi_env, StationAccessor, sizeof_fmt, ReceivedMessage,
67     pretty_receiver_log, pretty_sender_log, JobQueueHelper, StreamBuffer, \
~/miniconda/envs/gmprocess/lib/python3.7/site-packages/pyasdf/query.py in
102     "elevation_in_m": _type_or_none(float),
103     # Temporal constraints.
--> 104     "starttime": obspy.UTCDateTime,
105     "endtime": obspy.UTCDateTime,
106     "sampling_rate": float,
AttributeError: module 'obspy' has no attribute 'UTCDateTime'`

never mind, user error (conflict with our module also called obspy.)


WIP: adds segmentation algorithms

Would be glad to hear about things to change/add.
To test:
cargo build --release --package pasture-algorithms --example test_segmentation
execute:
./target/release/examples/test_segmentation
You can look at the segmentation results in a viewer like http://lidarview.com/ and upload the generated las-file.

* The `segmentation.rs` file should have a module-level documentation, describing what algorithms it contains

Did you mean lib.rs?

I think i resolved the comments. Is there anything else i should include/change?

Looks good. Regarding your comment, I meant the segmentation.rs file (every file can have a module-level documentation the way I understood it), but the way you did it in lib.rs is also ok.


Add a wiki: TARDIS (Doctor Who) Wiki

Link to origin wiki: https://tardis.wiki/wiki/Doctor_Who_Wiki
Link to destination (independent) wiki: https://tardis.wiki/wiki/Doctor_Who_Wiki

Duplicate of https://github.com/KevinPayravi/indie-wiki-buddy/issues/516, has been added and will be in the next release.