[BUG]  Eww spawns zombie windows and processes

Checklist before submitting an issue

[x] I have searched through the existing closed and open issues for eww and made sure this is not a duplicate
[x] I have specifically verified that this bug is not a common user error
[x] I am providing as much relevant information as I am able to in this bug report (Minimal config to reproduce the issue for example, if applicable)

Describe the bug
Basically, launching widgets will open your widgets, but sometimes they'll spawn, but refuse to close.
As far as I can predict, this issue happens after making eww daemon not a dependency for launching eww widgets. I'm not quite sure though.
Reproducing the issue
Use any config and create a widget. Bind the opening of your window to a keybind. Do not launch eww daemon. Press your keybind. Eww will not open windows immediately which is expected.
Now, before eww has finished opening the window, press the keybind again. Try to close this window with the eww close command. It will not work. The only way to remove the window will be killall eww.
This also happens sometimes randomly even when the daemon is running, but I cannot consistently reproduce it.
Expected behaviour
Eww windows to close with the eww close or eww kill commands.
Additional context
Logs:

The log says Closing all windows. However, windows aren't closed.

So what's happening here is that you're sending a close window command before the window has been fully opened? Am I getting that right?

Nope, an open window command before the windows are fully opened.

could you share the output of eww debug  and eww windows once you encounter an instance of such a zombie window (window that doesn't close)?

I have experienced this as well, when restarting eww due to a WM reload.
Also sometimes these windows seem to have odd properties and size, not sure if this might be a WM issue.
Will also try to catch some logs and maybe xprops, when I get this next time.

Here is the output of eww windows:

And here's the output of eww debug.

Interesting, this means that it actually sees the windows as not open, and thus won't close them. I'll investigate

In my case it does show the window as open.
I'd guess that since the ipc server runs at the last of server::initialize_server which might have took some time, two instances of the main.rs saw that daemon is not running and started running that function and two ipc_server listeners may attempt to listen one might got disconnected cuz of same file to listen.

Actually problem even gets increased due to 5 connection retries, this makes the startup of the server very slow as well as chances of this bug to happen. I'd suggest to reduce that to 3 or 2.
I can see there are two ways for solving this:

The wm I use (herbstluftwm) offer a --locked option which prevent it to draw anything on screen until hc unlock is executed in the autostart script (preferably at the end), similar to that if we can lock the socket file somehow at the start of initialize_server or something. Or maybe make a lock file which indicates some instance already have it opened while not started receiving commands (strategy used by vmware etc).
Revoke open command to attempt to start server to open. Make something like mkdir -p for eww daemon which silently start the daemon if does not exist, or do nothing. And force user to do eww -p daemon && eww open <bar> instead (saves from 5 connection attempts, making startup faster).

well, option 2 is what we had before - it made usage a lot more confusing, and generally more anoying to deal with when developing, too. Having a better check such as a file based lock would work, however it runs the issue of not getting cleaned up correctly - some people do do pkill eww, which then, well, doesn't necessarily give eww the chance to clean up everything.
If you care about the startup speed, then do start the daemon manually before, just as you showed - there the daemon won't do it's 5 connection attempts, and thus will be a lot faster to start up.
Having some better way of making sure no current server is already running is definitely something worth looking at again - having multiple eww instances running from the same config path is definitely an issue that shouldn't happen

Can we just move the init_async_part at the top of server::initialize_server and handle any error to stop the thread handle (instead of ? at end of result)? And reduce connection attempts to 3? Might reduce the chance of this happening to significant extent, but not free from this completely...
Also a regain of lock is something what vmware allows, if a vm is not running & lock is present (I'm not exactly sure how they actually do this).

On a side note:
Using pkill eww currently is the 'clenaer' experience for me as doing eww kill.
When I use eww kill I regularly end up with  one of the three windows I use as my 'bar' being hidden after a WM reload (doing this quite often at the moment as I am working on a few different contributions to leftwm, and checking bug reports).

I had a random thought, can we just apply a lock/mutex for eww [open|open-many|daemon|kill|reload] commands from the start line of main() to the end of main? with a timeout so that subsequent calls to them require to wait until lock is freed or timeout say 5s has been elapsed?
Simple to implement as well as might be free from this unexpected behavior, as the second open command will require to finish old open command if started parallelly 🤔🤔

Random thought came to my mind because eww open bar && eww open bar never had this problem i.e. when one waits for the other to finish. Only when launching parallelly this will occur, which we can fix using a virtual lock file.

Random thought came to my mind because eww open bar && eww open bar never had this problem i.e. when one waits for the other to finish. Only when launching parallelly this will occur, which we can fix using a virtual lock file.

You mean eww daemon && eww open bar? There where also issues, when one tried to open windows before the daemon fully spun up. Therefore I had a script that executed eww open .. until eww window | grep \* returned something.

Oh right, it forks the process and returns the parent before complete initialization 🤔🤔. But we can still pass the responsibility to the child fork to unlock the lock for these server-commands, then let the next command to proceed... That will solve the issue if I'm not wrong 👀

So have a initializing_lock and the child has to wait before returning until the lock is gone as init finished?

It seems like I have a similar issue based on what has been mentioned in the thread although there hasn't been a new update to this issue since September. Has there been an update to this issue or is there a workaround? Thanks

I may have an issue related to this one too.

I run the daemon at startup.
I have an i3wm key binding to toggle the main windows (eww open bar) or close-all (it check for 'eww state' content to choose).

It works fine for a few hours but then there is a glitch and it will open 2 clones, one linked to the daemon process and an independent open process.

From that point, the daemon does not respond and I need to kill it to close the window linked to it. But I can use 'eww close bar' to close the other, independant, window.

It's hard to debug this because it can happen 1 or 5h after daemon launch. I don't know what's the trigger. Maybe xscreensaver?


Training Aux-head and main heads

Just read your paper, amazing work ! I am just about to finish my keras implementation, but have a small understanding problem. When, and in which order do i train the different heads ?
Am i going to:

freeze the weigths of all subheads of aux and main , and than just backprop over one subhead for a whole epoch ?

or

calculate the loss over all main heads for one epoch, sum the loss of them up and backprop than, next epoch do the same for aux ?

or sth completely different?
Sorry i tried to reverse-engineer your pytorch code but i am not into pytorch, and the forks also didnt help me. thanks a lot for your time!

Closer to 2:
heads = [main, aux] # or other order
for ep in epochs:
  for head in heads:
    for batch in data(head):
      compute loss for all sub-heads in head, average over sub-heads, and do full backprop

You could also backprop from a joint loss on both heads at the same time without switching between them, if you have enough GPU memory (we didn't use this).


The content scrolls down when focusing on Input field

react-native, react and native-base version
"react-native": "0.41.2"
"native-base": "0.5.22"
Expected behaviour
I'm using these components: Content > InputGroup > Input.
Actual behaviour
So whenever I fill up the password field (Input component with secureTextEntry enabled) it scrolls the entire content down.
Steps to reproduce (code snippet or screenshot)
  render() {
    return (
      <Container>
        <Header>
          <Button transparent onPress={() => this.popRoute()}>
            <Icon name="ios-arrow-back" />
          </Button>

          <Title>Sign Up</Title>
        </Header>
        <Content padder>
          <InputGroup>
            <Input
              placeholder="First Name"
              onChangeText={(text) => this.firstName = text} />
          </InputGroup>
          <InputGroup>
            <Input
              placeholder="Last Name"
              onChangeText={(text) => this.lastName = text} />
          </InputGroup>
          <InputGroup>
            <Input
              placeholder="Driver's License"
              onChangeText={(text) => this.licenseNo = text} />
          </InputGroup>
          <InputGroup>
            <Input
              placeholder="Contact Number"
              onChangeText={(text) => this.contact = text} />
          </InputGroup>
          <InputGroup>
            <Input
              placeholder="Password"
              secureTextEntry
              onChangeText={(text) => this.password = text} />
          </InputGroup>
          <InputGroup>
            <Input
              placeholder="Confirm Password"
              secureTextEntry
              onChangeText={(text) => this.confirmPassword = text} />
          </InputGroup>

          <Button success block onPress={this._register}>
            Sign Up
          </Button>
        </Content>
      </Container>
    )
  }

Screenshot of emulator/device
iOS
Is the bug present in both ios and android or in any one of them?
I only tried iOS
Any other additional info which would help us debug the issue quicker.
Here are my imports:
import React, { Component } from 'react';
import {
  StyleSheet,
  Text
} from 'react-native';
import { connect } from 'react-redux';
import { actions } from 'react-native-navigation-redux-helpers';
import {
  Container,
  Header,
  Title,
  Content,
  Button,
  InputGroup,
  Input,
  Icon,
  View,
  H1
} from 'native-base';

Does it only happen in the Password filed?

Short answer: No.
The scroll is triggered when I tap that "password" <Input> field. And when I drag the screen back up and tap the <Input> (Contact Number) field before the "password" field it triggers the scroll again.

Okay, can you just remove secureTextEntry and check if that works? Just to be sure about what exactly is causing it.

@sankhadeeproy007 yup removing that attribute secureTextEntry fixes the bug. Looks like that attribute is causing it then.

That is a very strange issue indeed. We are using keyboard-aware-scrollview for <Content /> and didn't come across any issue which matches your use case.

@sankhadeeproy007 strange indeed. If you need more info from my setup let me know. I'll also try and investigate on my end.

I have an issue on mine after a Dynamic  it scrolls up way far.

I have an issue on mine after a Dynamic it scrolls up way far.

@sankhadeeproy007 for some reason it is fixed when I upgraded to<EMAIL_ADDRESS>

Yes, 2.0.x uses a newer version of keyboard-aware-scrollview

@sankhadeeproy007 unfortunately it's back again. I'm sure if it's related but I just updated to<EMAIL_ADDRESS>today.

I was experiencing the same issue. In my case it was due to react-native-keyboard-aware-scroll-view https://github.com/GeekyAnts/NativeBase/blob/master/src/basic/Content.js#L2.
I used enableAutoAutomaticScroll={false} on my  And the frustrating scrolling behaviour disappeared. I've actually found the following props to work really well:
scrollEnabled={false} // the view itself doesn't scroll up/down (only if all fields fit into the screen)
keyboardShouldPersistTaps='always' // make keyboard not disappear when tapping outside of input
enableAutoAutomaticScroll={false} // turn off auto scrolling to the field behaviour, which is unfortunately buggy when autocomplete suggestions disappear from the keyboard as displayed in the gif above

Hm, thinking more about it. I suppose the scroll to input behaviour might be useful for long forms. But in that case unfortunately there's definitely a bug when you focus on an input without autocomplete after having focused an input with autocomplete. Exactly as displayed in the gif. I'll report this issue to react-native-keyboard-aware-scroll-view team.

Hi, Any update in this issue?

Hi all!
react-native-keyboard-aware-scroll-view author here. We would love to fix this issue, but we need a minimum example to reproduce the issue, isolated from Native Base if possible. Can you provide us that? Thanks!

@nooralahzadeh Did you try including enableAutoAutomaticScroll={false} with <Content>?

@SupriyaKalghatgi  hi my issue has been solved by  enableResetScrollToCoords ={false} in

@janzenz I have the same problem as you.
I am using the following versions:
"native basis": "2.1.3",
"Native React": "0.41.0",
And for me, this problem only occurs in IOS.
Change <Content> to <ScrollView> and solved my problem.
And I don't know why this bug occurs with the Native Base Content tag.
@alvaromb Native-Base uses your plugin? And you've found any solution to this bug.

I used react-native-keyboard-spacer - Plug and play react-Native keyboard spacer view.
like below, it solve my issue
        </Content>
        <KeyboardSpacer />
      </Container>;

I have similar issue on ios. It is not related to library, but maybe can give some advice.
I have auto-resizing webview inside scrollview
<ScrollView>
<View>
<WebView style={{height: htmlHeight}}/>
//other views
</View

when I click on input inside html and keyboard opens, webview content scrolls to bottom a lot.


Task xsup 15878 secret and affinity management

Description

Fix indentation bug
Add option to not create deployment secret
Add option to use affinity

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate)

Types of changes

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

Checklist

[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes if appropriate.
[ ] All new and existing tests passed.

@ranberant  can you also release this helm chart please?
$ helm template cortex-xdr --repo https://paloaltonetworks.github.io/cortex-helm --version 1.1.0
Error: chart "cortex-xdr" version "1.1.0" not found in https://paloaltonetworks.github.io/cortex-helm repository


Error 'nativeBackgroundAndroid' on Button

Hi,
I got error on Button when use master branch. Previously it's work on version 0.2.1.

import { Button } from 'react-native-material-design'
...
        <Button
          value='Login'
          raised={true}
          theme='dark'
          primary='googleRed'
          onPress={this.handleLogin.bind(this)}
        />

package.json
{
  "name": "foobar",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node_modules/react-native/packager/packager.sh"
  },
  "dependencies": {
    "apsl-react-native-button": "^2.3.0",
    "immutable": "^3.7.5",
    "moment": "^2.10.6",
    "react": "^0.14.3",
    "react-native": "^0.17.0",
    "react-native-drawer": "^1.10.1",
    "react-native-dropdown-android": "0.0.6",
    "react-native-gcm-android": "0.0.7",
    "react-native-image-picker": "^0.10.0",
    "react-native-image-progress": "^0.4.0",
    "react-native-material-design": "git+https://github.com/react-native-material-design/react-native-material-design.git",
    "react-native-modalbox": "^1.2.4",
    "react-native-progress": "^2.2.0",
    "react-native-radio-buttons": "^0.6.0",
    "react-native-redux-router": "^1.0.5",
    "react-native-simple-store": "^0.1.0",
    "react-pure-render": "^1.0.2",
    "react-redux": "^3.1.2",
    "redux": "^3.0.5",
    "redux-logger": "^2.3.1",
    "redux-thunk": "^1.0.2"
  },
  "devDependencies": {}
}

Tested with Genymotion Samsung Galaxy S3 4.1.1 API 16
OS: Win 8.1 32bit

Right so this is because I swapped out the Ripple component with the RN Ripple, which only supports API 21 upwards.
I can look at bringing it back in if I can somehow get the api version, but 16 is an old api version?

Currently you can get android api version via Android build class or use react-native-device-info. But it will make this package installation more complicated.
api 16 is an old version, but many devices still use this version.
By the way, what is the different between Ripple component and RN Ripple? Performance?

It's okay, I can do something like this:

Get the version using the Platform module from RN.
Get the API level from http://developer.android.com/guide/topics/manifest/uses-sdk-element.html
Create a helper to detect where certain "features" are supported, such as Ripple & maybe elevation.
If it's not supported, use the Polyfil.

Performance wasn't actually as much of an issue, it was more complexity along with a few bugs. I'll bring it back though.
@pewh What happens when you create a View, and add an elevation to it? From here elevation is only available on API 21+. Does it throw an error or simply ignore it?

Thanks, @Ehesp
<View elevation={4}><Text>foo</Text></View> doesn't throw any error. It also render text & no warning on console.

Hi @pewh
I've just committed to master. I've tested this as best I could but I was unable to get my emulator working on API 16.  Basically it checks whether the device has the correct API level for a feature, and if not returns a polyfill for it.
The Ripple pollyfill had to be changed a bit, as I also wanted to implement onLongPress and elevation too. I've implemented this on Button & Drawer.Section. Could you test whether it works for me?
A couple of things I've noticed are:

On press, the background color isn't there, where as natively it is (I can do this, just need to find out what opacity of the ripple color the background color is).
With native, long pressing the button also seems to trigger a normal press. This currently doesn't happen... Need to figure out the actual logic behind this, surely triggering both functions for a long press is a bad idea.

Got API 16 working... Added more fixes in, including a border on components if elevation isn't available.

Sorry for long delay. I've testing on several devices with API 16 and everything is work. Thanks for the great work :+1:

Good to hear, I'm not sure the onLongPress is how I want it yet. I need to properly dig into the logic behind it as it seems to be functioning differently to native at the moment.


Update PyPI documentation URL to RTD

Codecov Report

Merging #12 (639c302) into master (7e5ab00) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #12   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           21        21
  Lines          720       720
=========================================
  Hits           720       720

Continue to review full report at Codecov.

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


add pytest upload workflow

Changes
add the workflow from #590 for testing

it works https://github.com/BAMWelDX/weldx/pull/590#issuecomment-940482814 🎉


isblank fix

What
What does the PR do?
refactor
Why
refactor
How
How is it doing what it does?
How to test, how to integrate, any relevant compromises, etc.?
Changes details

Detail one
Detail two
...

Missed anything?

[ ] Explained the purpose of this PR.
[ ] Self reviewed the PR.
[ ] Added or updated test cases.
[ ] Informed of breaking changes, testing and migrations (if applicable).
[ ] Updated documentation (if applicable).
[ ] Attached screenshots (if applicable).

Duplicate of #29


Need documentation on how to ssh to Jenkins server with code created public-private key-pair

When the default installation options are accepted, the installation completes successfully.  ie. The Jenkins server is created and is accessible via the browser.  But there are no instructions on how to retrieve the private key that would be needed to ssh to the Jenkins server.
Do I use the private_key_pem  value from the state file to construct the private key ?
I tried ssh using that and its looking for a passphrase.

@sundeepdhall it depends where you are deploying the code. In the case of Terraform CLI you need to extract generated private key by using terraform console:
Apply complete! Resources: 22 added, 0 changed, 0 destroyed.

Outputs:

jenkins_login_url = "http://<IP_ADDRESS>:8080"
jenkins_public_ip = "<IP_ADDRESS>"

terraform-server# terraform console
>nonsensitive(tls_private_key.public_private_key_pair.private_key_pem)

-----BEGIN RSA PRIVATE KEY-----
MIIEogIBAAK (...)2NQSMX8FrR1dmFNy0=
-----END RSA PRIVATE KEY-----

EOT
> Ctr-C

terraform-server# vi id_rsa <- here you should inject private key content.

terraform-server# chmod id_rsa

terraform-server# ssh -i id_rsa<EMAIL_ADDRESS><- jenkins_public_ip output
The authenticity of host '<IP_ADDRESS> (<IP_ADDRESS>)' can't be established.
ECDSA key fingerprint is SHA256:sgy0aiE6LSBVmragqEQ5L52Av3O4oSZaJ4RX89qWq+g.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
Last login: Thu Dec  2 10:31:38 2021 from 89-64-91-8.dynamic.chello.pl
[opc@jenkinsvm ~]$

Thank you.  This worked.  I also needed to install the latest version of terraform.  I was on a 0.14.5
with the older version the "nonsensitive" command did not work.  It still gave me the private key, but it had "\n" all over it.
When I use that in a file, I get prompted for a "passphrase"
I replaced it with v1.0.11 and ran the "nonsensitive(tls_private_key.public_private_key_pair.private_key_pem)
This now gave me a well formatted private key. and does not prompt for passphrase
I am able to connect to the jenkinsvm using this.
Thank you so much

That is good news @sundeepdhall. Closing the ticket.


Hot Module Reloading localized pages instead of running the npx astro-i18next generate command manually.

This should be done using injectRoute function in the astro:config:setup to inject localized routes during build time. The generate CLI tool would most probably be discarded. pages folder wouldn't need to include localized pages anymore!
Alternative
Create a Vite plugin and adding it to the astro:config:setup hook.

This should be done using injectRoute function in the astro:config:setup to inject localized routes during build time.

It sounds like astro-18n-aut’s approach, doesn’t it?


Actual command not found, wanted to execute _typescript.didApplyRefactoring/456396

select some code
run the move to new file code action
see this error: Actual command not found, wanted to execute _typescript.didApplyRefactoring/456396

This looks like a premature result disposal to me. E.g the placeholder command that's created is tracked by the code action result set and when that's disposed before the command could run this error happens

@jrieken I wasn't able to reproduce this. Any specific steps that cause this in the vscode repo?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Fix logic for determining prefer-dynamic for a dylib.

The logic for determining if a dylib should use prefer-dynamic used to be something like "do not use prefer-dynamic if it is the current package".
The current logic has a strange behavior where it works as intended if there is only one package in the workspace, but a workspace with multiple packages will always use prefer-dynamic.
Instead of using current_opt, which isn't a good concept to use in a workspace, I switched this to be "primary" (a package selected on the command-line).
History

9879a0a5f621a4ae44b2d9dc62a0175404c05f8f Initial prefer-dynamic behavior.
#3221 changed to the faulty logic (see comments at https://github.com/rust-lang/cargo/pull/3221#discussion_r88535221). I think there was some confusion there.
#3478 fixed the logic for one of the changed conditions, but not the one for prefer-dynamic

r? @alexcrichton
(rust-highfive has picked a reviewer for you, use r? to override)

@alexcrichton, before moving forward with this, I'd like to better understand the motivation for why it works this way. Can you explain what the reasoning is?

Honestly at this point I have no idea. I barely know of any use cases of dylib crate types much less intermediate dependencies.
AFAIK there's no real story about dylib dependencies in Rust right now so changing this seems fine by me.
r=me if you're ok landing

OK, understood.  Since this is clearly broken, I'll go ahead and merge, hopefully it doesn't break anyone relying on it.
@bors r=alexcrichton

:pushpin: Commit 48e0306c42752ca97c3488ad93b56b9831ca3465 has been approved by alexcrichton

:hourglass: Testing commit 48e0306c42752ca97c3488ad93b56b9831ca3465 with merge c43e485eb0d7c97ae7db97821c4c9e735c965fd2...

:broken_heart: Test failed - checks-actions

The lincheck script is a little out-of-sync with the latest nightly (rust-lang/rust#82950), it should resolve itself after the next nightly comes out (~7 hours from now).  I'll wait for that and try again later.

@bors retry

:hourglass: Testing commit 48e0306c42752ca97c3488ad93b56b9831ca3465 with merge 32da9eaa5de5be241cf8096ca6b749a157194f77...

:sunny: Test successful - checks-actions
Approved by: alexcrichton
Pushing 32da9eaa5de5be241cf8096ca6b749a157194f77 to master...


React/Web3 Components

Add Loading, Main and Navbar components
Ensure Web3 functionality

Integrated under: commit 81c399377cdb25a5fadbb6c193cc6a820dd9eb2f .


Trouble with append_fc_toservice.py sample

Greetings,
I'm having trouble with the append_fc_to_service.py sample.
I'm not sure if I need to provide more parameters in the securityinfo dictionary than I am.  Here are the items I have populated:
securityinfo['security_type'] = 'Portal'
securityinfo['username'] = ""
securityinfo['password'] = ""
securityinfo['org_url'] = "http://.maps.arcgis.com"
I am hoping that 'Portal' works for ArcGIS Online?
Do I need a referer url? A token url?
No proxy urls or ports needed to get to the internet.
Here's the error I am getting:
traceback gives me this line - fst = featureservicetools.featureservicetools(securityinfo)
The error text is - TypeError: init() takes at least 3 arguments (2 given)
Any help would be appreciated.
Thanks,

You org url should be
securityinfo['org_url'] = "http://www.arcgis.com"

Ah, Thanks Mike.  I thought org_url meant the url for the organization, and I took the organization name out of the url in my original post..
I changed it to http://www.arcgis.com and I am still getting the same error for the same line.

So I have passed each part of the securityinfo dictionary to the featureservicetools instantiator and it gets past that line.

Here is my script:
`"""
This sample shows how to append a featureclass
to a feature service using ArcRest and ArcRestHelper
version 3.0.1
Python 2
"""
import arcrest, json
from arcresthelper import featureservicetools
from arcresthelper import common
def trace():
"""
trace finds the line, the filename
and error message and returns it
to the user
"""
import traceback, inspect
tb = sys.exc_info()[2]
tbinfo = traceback.format_tb(tb)[0]
filename = inspect.getfile(inspect.currentframe())
# script name + line number
line = tbinfo.split(", ")[1]
# Get Python syntax error
#
synerror = traceback.format_exc().splitlines()[-1]
return line, filename, synerror
if name == "main":
proxy_port = None
proxy_url = None

securityinfo = {}
securityinfo['security_type'] = 'Portal'#LDAP, NTLM, OAuth, Portal, PKI
securityinfo['username'] = "<myusername>"#<UserName>
securityinfo['password'] = "<mypassword>"#<Password>
securityinfo['org_url'] = "http://www.arcgis.com"
securityinfo['proxy_url'] = proxy_url
securityinfo['proxy_port'] = proxy_port
securityinfo['referer_url'] = None
securityinfo['token_url'] = None
securityinfo['certificatefile'] = None
securityinfo['keyfile'] = None
securityinfo['client_id'] = None
securityinfo['secret_id'] = None

itemId = "<myItemID>"#<Item ID>
layerName='Archived Notice Points'#Name of layer in the service
fc=r'<myFCpath>'#Path to Feature Class
atTable=None
try:
    fst = featureservicetools.featureservicetools(securityinfo['username'], securityinfo['password'], securityinfo['org_url'])
    if fst.valid == False:
        print fst.message
    else:

        fs = fst.GetFeatureService(itemId=itemId,returnURLOnly=False)
        if not fs is None:

            fl = fst.GetLayerFromFeatureService(fs=fs,layerName=layerName,returnURLOnly=False)
            if not fl is None:
                results = fl.addFeatures(fc=fc,attachmentTable=atTable)
                print json.dumps(results)
            else:
                print "Layer %s was not found, please check your credentials and layer name" % layerName
        else:
            print "Feature Service with id %s was not found" % fsId

except:
    line, filename, synerror = trace()
    print "error on line: %s" % line
    print "error in file name: %s" % filename
    print "with error message: %s" % synerror`

`"""
This sample shows how to append a featureclass
to a feature service using ArcRest and ArcRestHelper
version 3.0.1
Python 2
"""
import arcrest, json
from arcresthelper import featureservicetools
from arcresthelper import common
def trace():
"""
trace finds the line, the filename
and error message and returns it
to the user
"""
import traceback, inspect
tb = sys.exc_info()[2]
tbinfo = traceback.format_tb(tb)[0]
filename = inspect.getfile(inspect.currentframe())
# script name + line number
line = tbinfo.split(", ")[1]
# Get Python syntax error
#
synerror = traceback.format_exc().splitlines()[-1]
return line, filename, synerror
if name == "main":
proxy_port = None
proxy_url = None

securityinfo = {}
securityinfo['security_type'] = 'Portal'#LDAP, NTLM, OAuth, Portal, PKI
securityinfo['username'] = "<myusername>"#<UserName>
securityinfo['password'] = "<mypassword>"#<Password>
securityinfo['org_url'] = "http://www.arcgis.com"
securityinfo['proxy_url'] = proxy_url
securityinfo['proxy_port'] = proxy_port
securityinfo['referer_url'] = None
securityinfo['token_url'] = None
securityinfo['certificatefile'] = None
securityinfo['keyfile'] = None
securityinfo['client_id'] = None
securityinfo['secret_id'] = None

itemId = "<myItemID>"#<Item ID>
layerName='Archived Notice Points'#Name of layer in the service
fc=r'<myFCpath>'#Path to Feature Class
atTable=None
try:
    fst = featureservicetools.featureservicetools(securityinfo['username'], securityinfo['password'], securityinfo['org_url'])
    if fst.valid == False:
        print fst.message
    else:

        fs = fst.GetFeatureService(itemId=itemId,returnURLOnly=False)
        if not fs is None:

            fl = fst.GetLayerFromFeatureService(fs=fs,layerName=layerName,returnURLOnly=False)
            if not fl is None:
                results = fl.addFeatures(fc=fc,attachmentTable=atTable)
                print json.dumps(results)
            else:
                print "Layer %s was not found, please check your credentials and layer name" % layerName
        else:
            print "Feature Service with id %s was not found" % fsId

except:
    line, filename, synerror = trace()
    print "error on line: %s" % line
    print "error in file name: %s" % filename
    print "with error message: %s" % synerror`

Error message:
error on line: line 53
error in file name: AppendNoticedPoints.py
with error message: AttributeError: 'featureservicetools' object has no attribute '_valid'

which version of ArcRest are you using?  We changed the input to featureservicetools a long time ago, passing in the username should not work with 3.5 and master.

I assume I am using 3.5.4.  I just used the Download ZIP button here on GitHub.

Did you have a previous version on your machine, can you see what is in your python 2.7 folder.  You may have an old version hanging around.

Is there a way to tell what version I have?  How do I start fresh?

I just found my version by typing help(arcrest) - it says it is version 2.0.1.  Can I just delete the arcrest folder out of the site-packages folder?

yes

That was my problem.  I deleted the arcrest folder and the arcresthelper folder from the site-packages folder, then reinstalled the latest version.
Thanks, Mike - and sorry for the bother.


json2capnp: Use named arguments instead of positional ones

Named arguments remove ambiguity on what the argument is and allows for easy command help to be displayed.
It was implemented in https://github.com/chairemobilite/transition-legacy/pull/2060 but it failed to build on docker because the json2capnp build container is based on bullseye, which only supports the clap package v2, while the implementation was done for v3 and v4 (which differ only by a few keyword, unlike v2, which differs quite a bit). When docker containers are upgrade, we can revive this PR.

#423 is pre-requisite


useIntersectionObserver unexpected token

I'm running 2.0.2 just fine and when I upgrad eto 2.2.2:
./node_modules/usehooks-ts/dist/esm/useIntersectionObserver/useIntersectionObserver.js 11:23
Module parse failed: Unexpected token (11:23)
File was processed with these loaders:
 * ./node_modules/react-scripts/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|   } = _ref;
|   const [entry, setEntry] = useState();
>   const frozen = entry?.isIntersecting && freezeOnceVisible;
|
|   const updateEntry = _ref2 => {

rm -rf node_modules fixed that

Thanks @jeanlucmongrain :)

I use<EMAIL_ADDRESS>and have the same error message. Removing node_modules didn't work for me.
I've done a bit of investigation, and found a few solutions.

Update react-scripts to version 5.
Downgrade usehooks-ts to version 2.1.1
Add babel plugins proposal-optional-chaining and proposal-nullish-coalescing-operator into your babel config.

I use craco to tune my build, here's the config to satisfy babel:
module.exports = {
  babel: {
    // need this for usehooks-ts with react-scripts@4
    plugins: [
      ['@babel/plugin-proposal-optional-chaining'],
      ['@babel/plugin-proposal-nullish-coalescing-operator'],
    ],
  }
}

Thanks @arusak!


Any way to use 'yarn add' without immediately rebuilding the DLL?

Adding and removing tiny packages has begun to take several minutes for me as my project has grown. Is there anything I can do to not rebuild until I'm done making package changes, or is this yarn itself doing it?
It ends off with:
 npm run build-dll exited with code 0

Try npm install some-dep --ignore-scripts. The --ignore-scripts could have unexpected side affects. A better solution for you would probably be to create a separate script that looks something like this:
// postinstall.js
if (process.env.arv.includes('--no-build-dll')) return
execSync('npm run build-dll')

Thanks very much @amilajack. For anyone else who comes across this, I'm using Yarn and the --ignore-scripts flag seems apply for it as well.
I'll report back with my results. Thanks again as always!

Works great!

@amilajack I suggest we should add such questions and their resolution to the wiki of this project. What do you think?

@talha131 good idea. I'll make a FAQ section. Ideally, we can incorporate those questions and answers into the video tutorial series

I'll make a FAQ section.

I suggest you should leave these low hanging fruits for rest of the community.

Good call. I actually don't have permission to enable read/write permissions to the public. That's up to @chentsulin. Also would be awesome if @chentsulin could add you as a collaborator

@amilajack It seems wiki is open for editing to all, not just the contributors.
See this page that I just added
https://github.com/chentsulin/electron-react-boilerplate/wiki/Tool-Tips
Secondly, how about we keep tips about tools like npm, yarn, git, flow to "Tool-Tips" instead of FAQ? I think this categorization is better than pilling everything into FAQ.

I think that would be better once our FAQ becomes larger.

I've updated the FAQ. It now mentions using .yarnrc to make ignore-scripts happen permanently (for all or specific commands).


[Feature Request] add option to set background colors for toast

Hi, thank you for providing this crate.
I find the toasts difficult to see/notice as there is little contrast with the background color of the app.
Possible ways to make the toasters more noticeable:

I'd like to be able to configure that e.g. for success toasters the entire background of the toaster becomes green.
Configure shadow or border.

Is this something you agree with?

Very good idea. A shadow would work well I suppose! I also just ran into an issue where the toast was barely visible.

I opened a PR with optional shadow support:
https://github.com/ItsEthra/egui-notify/pull/33


Text Limit with English characters

I found that using this package, the text limit is around 1500 characters.
is it because it is using GET request instead of POST ? As i am expecting a 5000 characters limit.
Thanks

I also think it is using GET request instead of POST。
In my case, I found the author use 'got' module. So I change the index.js file to convert GET => POST.
Here is my change:
           ...             return url + '?' + querystring.stringify(data);         }).then(function (url) {             return got(url,{'method':'POST'}).then(function (res) {             ...
Hope it will work fine with you.


New head of security weapon:Energy Shotgun

About the PR

I added an experimental energy shotgun with four fire modes:
Wide fire(lethal)
Narrow fire(lethal)
Disabler(non lethal)
Ion(emp)
Why / Balance

Was speaking with flare about this, the HoS really needed a unique weapon instead of a bland SMG that can be obtained in other ways. This will hopefully cause more playstyle variety for HoS. The weapon is also high risk, and a steal objective for syndies. My original idea was to add the X-01 from SS13, but flare showed me this shotgun and I instantly loved it.
Technical details

Not really code but... I added a new cartridge yml that deals with all kinds of unique cartridges that aren't player-bound, for example, I used cartridges to make this weapon fire multiple projectiles instead of a single one.
Media

https://github.com/space-wizards/space-station-14/assets/149967078/16865e2d-72fa-4177-9eab-0300981c4f09

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: The HoS has been given a new experimental weapon:An energy shotgun with multiple fire modes. This experimental tech is highly wanted by the syndicate, and agents will try to steal it.

This looks really, really overpowered.
A rechargeable shotgun that has 4 modes that allow the user to deal with most possible combat scenarios that is also roundstart and matches if not outdamages normal shotgun options while having a clip size of 10.
It is of course in single quantity, provided you can kill the HoS, but it's not hard to acquire at all considering it's basically guaranteed the HoS will carry it, and killing the HoS is rather simple as a traitor if you get the alpha strike on them and use one of the multiple "hey I win this encounter" 1v1 options, hypopens come to mind as being the easiest option.
And the clip mechanism is kind of a drawback because you have to get to a recharger, but this doesn't matter for most encounters on the HoS part because after killing or arresting someone they can just go back to sec or bridge and recharge there, 10 clip size is plenty enough even for extended fights so trips like that aren't too bad either.
Now don't get me wrong, I love this concept, but this really needs a balance pass.

This looks really, really overpowered.
A rechargeable shotgun that has 4 modes that allow the user to deal with most possible combat scenarios that is also roundstart and matches if not outdamages normal shotgun options while having a clip size of 10.
It is of course in single quantity, provided you can kill the HoS, but it's not hard to acquire at all considering it's basically guaranteed the HoS will carry it, and killing the HoS is rather simple as a traitor if you get the alpha strike on them and use one of the multiple "hey I win this encounter" 1v1 options, hypopens come to mind as being the easiest option.
And the clip mechanism is kind of a drawback because you have to get to a recharger, but this doesn't matter for most encounters on the HoS part because after killing or arresting someone they can just go back to sec or bridge and recharge there, 10 clip size is plenty enough even for extended fights so trips like that aren't too bad either.
Now don't get me wrong, I love this concept, but this really needs a balance pass.

The 8 tc eshield user:
The 8 tc eshield user then using the shotgun on the rest of the station:

Disabler shot definitely needs to be a single shot and not a shotgun blast. I'm very interested in the laser shotgun though!

Don't try to add this to every map. Before even being considered to be added, remove all the map changes, as those need to be atomized in the first place.

Too not a depot and strong, even for high risk, it is better to transfer the x-01, this is a more balanced weapon for hos

I don't like this weapon because hos will lose it and murderboners get a guaranteed source of a good weapon

this should be a t3 research

I don't like this weapon because hos will lose it and murderboners get a guaranteed source of a good weapon

They already have one via captain's antique laser gun but this adds an alternative.

pretty sure Delta-V already has an x-01 for the HoS, just port it.

I can nerf it, but debate this with flare, they requested it

Okay, going point-through-point:

The main reason for having this over the X-01 (HOS's SS13 weapon) is that the X-01 was always kind of boring. Most people probably couldn't tell you how good it was because it's basically just another laser gun but Slightly Better:tm: and with an ion fire mode. In theory, this provides an interesting spin on the gun and makes it genuinely unique and valuable, like any good objective item should be.

Traitors stealing this gun is kind of a given, I don't really see the point in this being a bad thing unless it's ridiculously overpowered.

Shotgun disablers should be conceptually fine since these are supposed to do less damage per shot (they use the SMG disabler shots.)

I'm kind of indifferent on ion, but it's only 1 bolt per shot so it should be fine, it was a feature of the X-01.

10 shots probably is pretty ridiculous considering how much pain this thing can dish out in theory.

Okay, going point-through-point:

The main reason for having this over the X-01 (HOS's SS13 weapon) is that the X-01 was always kind of boring. Most people probably couldn't tell you how good it was because it's basically just another laser gun but Slightly Better:tm: and with an ion fire mode. In theory, this provides an interesting spin on the gun and makes it genuinely unique and valuable, like any good objective item should be.

Traitors stealing this gun is kind of a given, I don't really see the point in this being a bad thing unless it's ridiculously overpowered.

Shotgun disablers should be conceptually fine since these are supposed to do less damage per shot (they use the SMG disabler shots.)

I'm kind of indifferent on ion, but it's only 1 bolt per shot so it should be fine, it was a feature of the X-01. If it makes the gun too versatile it probably wouldn't be out of the question to remove.

10 shots probably is pretty ridiculous considering how much pain this thing can dish out in theory.

How many shots do you suggest? Five?

Five or four is probably good to put it at for now, considering the relative power of the shotgun.

The main reason for having this over the X-01 (HOS's SS13 weapon) is that the X-01 was always kind of boring. Most people probably couldn't tell you how good it was because it's basically just another laser gun but Slightly Better:tm: and with an ion fire mode. In theory, this provides an interesting spin on the gun and makes it genuinely unique and valuable, like any good objective item should be.
In part I agree with you.  But you can always improve, refine or look at it from a new angle.  Perhaps at the moment, for x-01, ion damage will be more useless, unlike disabler.  As a last resort, it will be possible to look at the Dominator and do something based on its model.  (Lethal, non-lethal and taser).  Although these are all assumptions and ideas that most likely no one will consider in this request.

The main reason for having this over the X-01 (HOS's SS13 weapon) is that the X-01 was always kind of boring. Most people probably couldn't tell you how good it was because it's basically just another laser gun but Slightly Better:tm: and with an ion fire mode. In theory, this provides an interesting spin on the gun and makes it genuinely unique and valuable, like any good objective item should be.

In part I agree with you.  But you can always improve, refine or look at it from a new angle.  Perhaps at the moment, for x-01, ion damage will be more useless, unlike disabler.  As a last resort, it will be possible to look at the Dominator and do something based on its model.  (Lethal, non-lethal and taser).  Although these are all assumptions and ideas that most likely no one will consider in this request.

Did we not have a freeze for new weapons?

all reviews adressed

It should be svallin. Being unable to reload sucks, each shot takes double the energy the pistol does. (High cap is 10)

I don't think it's been mentioned before, but what size is the Gun going to be?
Having it be 4x2 would be wonderful, would also match the size of the Enforcer.

@Boaz1111 is this still being worked on.

not currently

Going to undraft and work on this once #27773 gets merged

closing this because I am doing the scorched earth strategy of making a new pr


autostart on boot

This is an enhancement.
It would be great if there was a way to have a vm auto start on boot. Thanks.

Here you are: https://github.com/utmapp/UTM/wiki/URL-Scheme-–-Automation-for-UTM-app-&-VMs#start-a-vm-automatically-when-you-log-in-macos-12-monterey

Perhaps a followup to this @conath: is it possible to also have UTM shutdown a guest vm at restart/reboot? I have, for example, a macOS virtualization.framework guest that I need to be sure shuts down (better would be: suspends/saves state, but I don't think this works on Apple's framework yet) properly and then starts back up when the system boots and/or user logs in...

@ylluminate No, this is not possible, as UTM does not currently contain a "safe shutdown" feature and adding it for macOS VMs is not possible – Apple would need to add such a feature first in their backend, just like the missing suspend-to-disk feature you mentioned. You would need to use a 3rd party automation tool to trigger the VM shutdown and then the host shutdown in sequence.

@conath is there an updated link to that wiki? The above one no longer works as it seems. Thanks.

@maxpavlov Indeed the Wiki was removed in favor of the new documentation website. Unfortunately this section about the URL scheme automation was not copied to the relevant chapter yet.
Thankfully the wiki page is archived on the Internet Archive.

@conath It might make sense to implement this just for QEMU based VMs for now. And then if/when Apple adds support it can be turned on for MacOS VMs. It seems like there might not be any wasted effort implementing this now vs when Apple adds support.

I noticed a strange behavior so I'd just note it here:
Adding the shortcut to "Login Items" alone is not enough - UTM will launch but it will not start the VM. UTM also needs to be added to the list of "Login Items" for this to work properly.

Because Google brings me here, so for posterity: I find Apple Script to be the easier (cleaner) solution. The docs are accurate and using Script Editor.app to create a macOS binary is trivial. In my case wanting to boot a VM on login:
tell application "UTM"
    set vm to virtual machine named "W11"
    start vm
end tell


Modify all files that depend on the grammar

After modifying the master grammar and components grammar we have to change the entire code to adjust to this new format.

[ ] Load grammar files as needed and according to ids specified in the master grammar


Values in onValues

Hi.
I'm running homebridge and homeseer on an Rpi. I've recently added a co2 meter to my homeseer and homebridge is pulling the readings from homeseer.
How can I tweak the onValues paramter in config.json? I've found this example:
"onValues":[2,2.255]
// Optional - List of all HomeSeer values triggering a "ON" sensor state - Default is any value different than 0
What does 2,2.255 mean? Is the comma a separator or a value? Is it from 2-2.255 where the . is a thousand separator?? Where can I find a explanation on how to tweak the values?
I want the device to report ON when the reading is above 2000.
Br
Hakkespetten

I assume you are using the homebridge-homeseer-plugin with homebridge. In that plugin, the onValues seems to work as a simple listing of alternative integer/boolean values that mean "On". This might be used where a HomeSeer device can return several different numbers, each of which can mean "On". To do what you want, you would have to list each "On" value individually and that would be quite difficult particularly if the sensor reports floating point. Looking at the code, contrary to what seems to be indicated in the codes' comments, I don't think ranges are supported, so the entry "2,2.55" means the value "2" or the value "2.55" but not a range and not any other value.
On a related point, I've been re-writing that plugin to support faster polling. I have a first "release" completed, but I did not include the "onValues" feature.  However, if  you want to explain this use case a bit better, maybe I can try to incorporate some kind of range testing in the future.  Its at: www.github.com/jvmahon/homebridge-homeseer . Please put comments there in its issue forum.
(You probably meant to ask this in the homebridge-homeseer-plugin issues list)

Also, as a follow-up, since the plugin doesn't really do what you seem to want, consider implementing the level reading from the HomeSeer side since HomeSeer is more capable when it comes to reading device values and responding.
One simple approach would be to create a virtual device (such as a simple Switch) on HomeSeer and use a HomeSeer event  to turn this device on / off based on the sensor reading as measured by HomeSeer. Instructions for creating a virtual device and getting it to change based on an event can be found here: https://forums.homeseer.com/showthread.php?t=172120
Then, in your HomeBridge plugin, you would create a corresponding Switch using the "Switch" type in your homebridge-homeseer plugin config.json file (Let's give this virtual switch the "name": value of "HighCO2") and set its "ref": value to the device reference of the virtual one on HomeSeer).
Then, when HomeSeer turns on its "local" virtual switch, the HomeSeer plugin would turn on the corresponding "HighCO2" switch in the iPhone Home app. You could then base automation in the iPhone Home app on whether or not the "HighCO2" switch was on / off.


[DOC] Behavior of ism_template.priority field is not adequately explained

What do you want to do?

[x] Request a change to existing documentation
[x] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
This page explains that ism_template.priority is used to determine which template is applied, but several important pieces of information are missing:

Are higher values applied first, or lower? (seems like higher if I'm understanding the source correctly)
What is the default value? (Turns out it's 0)
What are the limits of this field? Is there a maximum priority? Are negative numbers legal? (they are not)

It might be worth adding more complete documentation for the whole ism_template object to the policies page.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
The existing (limited) documentation was added in PR #186

Adding a forum thread here to make sure we are covering everything. It is also problematic that ISM priority seems to be missing documentation and there is also a priority field under index_priority. Maybe we describe at a high level how priority works across the project and then specify that certain policy elements may implement priority as a tie breaker.
https://forum.opensearch.org/t/which-index-policy-is-applied-when-multiple-match/12886/3

@getsaurabh02 @bowenlan-amzn could you help with answers to these questions on ISM policies

Are higher values applied first, or lower? (seems like higher if I'm understanding the source correctly)
What is the default value? (Turns out it's 0)
What are the limits of this field? Is there a maximum priority? Are negative numbers legal? (they are not)

Are higher values applied first, or lower? (seems like higher if I'm understanding the source correctly)
Template with higher value would be applied first.
What is the default value? (Turns out it's 0)
0
What are the limits of this field? Is there a maximum priority? Are negative numbers legal? (they are not)
Has to be >= 0
No specific maximum limitation, this field itself is an integer type, so it would be 2,147,483,647

Reassigning to Nate, who covers ISM.


http / https confusion with new minikube install

I am new to kubernetes and helm and I'm unable to get "helm init" to work
I am not sure what the resultant error means about error forwarding ports or how to fix it!
Other than this minikube kubernetes install seems to work fine.  I am using Ubuntu 14.04 LTS
jamie@jamie-Ideapad-Z570:~/wip/kube/helm-experiments$ minikube start
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.
jamie@jamie-Ideapad-Z570:~/wip/kube/helm-experiments$ minikube version
minikube version: v0.24.1
jamie@jamie-Ideapad-Z570:~/wip/kube/helm-experiments$ helm init
$HELM_HOME has been configured at /home/jamie/.helm.

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
Happy Helming!
jamie@jamie-Ideapad-Z570:~/wip/kube/helm-experiments$ kubectl get pods --all-namespaces
NAMESPACE     NAME                            READY     STATUS    RESTARTS   AGE
kube-system   kube-addon-manager-minikube     1/1       Running   0          3m
kube-system   kube-dns-86f6f55dd5-rpzrf       3/3       Running   0          3m
kube-system   kubernetes-dashboard-2hdds      1/1       Running   2          3m
kube-system   storage-provisioner             1/1       Running   0          3m
kube-system   tiller-deploy-f665c64f4-6tjr2   1/1       Running   0          16s
jamie@jamie-Ideapad-Z570:~/wip/kube/helm-experiments$ helm ls
Error: forwarding ports: error upgrading connection: error sending request: Post https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-f665c64f4-6tjr2/portforward: http: server gave HTTP response to HTTPS client
jamie@jamie-Ideapad-Z570:~/wip/kube/helm-experiments$ helm version
Client: &version.Version{SemVer:"v2.8.0", GitCommit:"14af25f1de6832228539259b821949d20069a222", GitTreeState:"clean"}
Error: cannot connect to Tiller

+1
I upgraded to helm canary and I'm on a mac using Virtualbox for Minikube
$ helm --debug version
Client: &version.Version{SemVer:"v2.8.0", GitCommit:"14af25f1de6832228539259b821949d20069a222", GitTreeState:"clean"}
Kubernetes: &version.Info{Major:"", Minor:"", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2018-01-26T19:04:38Z", GoVersion:"go1.9.1", Compiler:"gc", Platform:"linux/amd64"}
[debug] context deadline exceeded
Error: cannot connect to Tiller

$ helm --debug ls
Error: forwarding ports: error upgrading connection: error sending request: Post https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg/portforward: EOF

$ kubectl get pods --namespace kube-system
NAME                                    READY     STATUS    RESTARTS   AGE
default-http-backend-gpttj              1/1       Running   0          32m
heapster-dz8qg                          1/1       Running   0          32m
influxdb-grafana-nnwh7                  2/2       Running   0          32m
kube-addon-manager-minikube             1/1       Running   0          33m
kube-dns-54cccfbdf8-k85x4               3/3       Running   0          32m
kubernetes-dashboard-77d8b98585-7xfw4   1/1       Running   0          32m
nginx-ingress-controller-mc29s          1/1       Running   0          32m
storage-provisioner                     1/1       Running   0          32m
tiller-deploy-595dcf9cd-frsmg           1/1       Running   0          16m

$  kubectl --v=9 -n kube-system port-forward tiller-deploy-595dcf9cd-frsmg  44134
I0201 11:15:14.895173   19375 loader.go:357] Config loaded from file ~/.kube/config
I0201 11:15:14.898840   19375 round_trippers.go:417] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.9.2 (darwin/amd64) kubernetes/5fa2db2" https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg
I0201 11:15:14.909749   19375 round_trippers.go:436] GET https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg 200 OK in 10 milliseconds
I0201 11:15:14.909777   19375 round_trippers.go:442] Response Headers:
I0201 11:15:14.909795   19375 round_trippers.go:445]     Content-Type: application/json
I0201 11:15:14.909798   19375 round_trippers.go:445]     Content-Length: 2739
I0201 11:15:14.909800   19375 round_trippers.go:445]     Date: Thu, 01 Feb 2018 00:15:15 GMT
I0201 11:15:14.910575   19375 request.go:873] Response Body: {"kind":"Pod","apiVersion":"v1","metadata":{"name":"tiller-deploy-595dcf9cd-frsmg","generateName":"tiller-deploy-595dcf9cd-","namespace":"kube-system","selfLink":"/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg","uid":"3273405d-06e2-11e8-8e43-080027fc9a5b","resourceVersion":"1081","creationTimestamp":"2018-01-31T23:55:21Z","labels":{"app":"helm","name":"tiller","pod-template-hash":"151879578"},"ownerReferences":[{"apiVersion":"extensions/v1beta1","kind":"ReplicaSet","name":"tiller-deploy-595dcf9cd","uid":"3272e395-06e2-11e8-8e43-080027fc9a5b","controller":true,"blockOwnerDeletion":true}]},"spec":{"volumes":[{"name":"default-token-z78wz","secret":{"secretName":"default-token-z78wz","defaultMode":420}}],"containers":[{"name":"tiller","image":"gcr.io/kubernetes-helm/tiller:canary","ports":[{"name":"tiller","containerPort":44134,"protocol":"TCP"},{"name":"http","containerPort":44135,"protocol":"TCP"}],"env":[{"name":"TILLER_NAMESPACE","value":"kube-system"},{"name":"TILLER_HISTORY_MAX","value":"0"}],"resources":{},"volumeMounts":[{"name":"default-token-z78wz","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"livenessProbe":{"httpGet":{"path":"/liveness","port":44135,"scheme":"HTTP"},"initialDelaySeconds":1,"timeoutSeconds":1,"periodSeconds":10,"successThreshold":1,"failureThreshold":3},"readinessProbe":{"httpGet":{"path":"/readiness","port":44135,"scheme":"HTTP"},"initialDelaySeconds":1,"timeoutSeconds":1,"periodSeconds":10,"successThreshold":1,"failureThreshold":3},"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"Always"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","serviceAccountName":"default","serviceAccount":"default","nodeName":"minikube","securityContext":{},"schedulerName":"default-scheduler"},"status":{"phase":"Running","conditions":[{"type":"Initialized","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-01-31T23:55:21Z"},{"type":"Ready","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-01-31T23:55:48Z"},{"type":"PodScheduled","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-01-31T23:55:21Z"}],"hostIP":"<IP_ADDRESS>","podIP":"<IP_ADDRESS>","startTime":"2018-01-31T23:55:21Z","containerStatuses":[{"name":"tiller","state":{"running":{"startedAt":"2018-01-31T23:55:43Z"}},"lastState":{},"ready":true,"restartCount":0,"image":"gcr.io/kubernetes-helm/tiller:canary","imageID":"docker-pullable://gcr.io/kubernetes-helm/tiller@sha256:a0bb59f866a28a8d3f2bc8aed32b75a79179e761414b03a5cd756b4317565eb2","containerID":"docker://77fab3d7c639dcca6eaf85b21807154dfa21633e5d9a8fcfaeef0df88c870adb"}],"qosClass":"BestEffort"}}
I0201 11:15:14.939958   19375 round_trippers.go:417] curl -k -v -XPOST  -H "User-Agent: kubectl/v1.9.2 (darwin/amd64) kubernetes/5fa2db2" -H "X-Stream-Protocol-Version: portforward.k8s.io" https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg/portforward
I0201 11:15:14.940937   19375 round_trippers.go:436] POST https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg/portforward  in 0 milliseconds
I0201 11:15:14.940949   19375 round_trippers.go:442] Response Headers:
F0201 11:15:14.941334   19375 helpers.go:119] error: error upgrading connection: error sending request: Post https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg/portforward: EOF
$  kubectl --v=9 -n kube-system port-forward tiller-deploy-595dcf9cd-frsmg  44134
I0201 11:15:14.895173   19375 loader.go:357] Config loaded from file ~/.kube/config
I0201 11:15:14.898840   19375 round_trippers.go:417] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.9.2 (darwin/amd64) kubernetes/5fa2db2" https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg
I0201 11:15:14.909749   19375 round_trippers.go:436] GET https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg 200 OK in 10 milliseconds
I0201 11:15:14.909777   19375 round_trippers.go:442] Response Headers:
I0201 11:15:14.909795   19375 round_trippers.go:445]     Content-Type: application/json
I0201 11:15:14.909798   19375 round_trippers.go:445]     Content-Length: 2739
I0201 11:15:14.909800   19375 round_trippers.go:445]     Date: Thu, 01 Feb 2018 00:15:15 GMT
I0201 11:15:14.910575   19375 request.go:873] Response Body: {"kind":"Pod","apiVersion":"v1","metadata":{"name":"tiller-deploy-595dcf9cd-frsmg","generateName":"tiller-deploy-595dcf9cd-","namespace":"kube-system","selfLink":"/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg","uid":"3273405d-06e2-11e8-8e43-080027fc9a5b","resourceVersion":"1081","creationTimestamp":"2018-01-31T23:55:21Z","labels":{"app":"helm","name":"tiller","pod-template-hash":"151879578"},"ownerReferences":[{"apiVersion":"extensions/v1beta1","kind":"ReplicaSet","name":"tiller-deploy-595dcf9cd","uid":"3272e395-06e2-11e8-8e43-080027fc9a5b","controller":true,"blockOwnerDeletion":true}]},"spec":{"volumes":[{"name":"default-token-z78wz","secret":{"secretName":"default-token-z78wz","defaultMode":420}}],"containers":[{"name":"tiller","image":"gcr.io/kubernetes-helm/tiller:canary","ports":[{"name":"tiller","containerPort":44134,"protocol":"TCP"},{"name":"http","containerPort":44135,"protocol":"TCP"}],"env":[{"name":"TILLER_NAMESPACE","value":"kube-system"},{"name":"TILLER_HISTORY_MAX","value":"0"}],"resources":{},"volumeMounts":[{"name":"default-token-z78wz","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"livenessProbe":{"httpGet":{"path":"/liveness","port":44135,"scheme":"HTTP"},"initialDelaySeconds":1,"timeoutSeconds":1,"periodSeconds":10,"successThreshold":1,"failureThreshold":3},"readinessProbe":{"httpGet":{"path":"/readiness","port":44135,"scheme":"HTTP"},"initialDelaySeconds":1,"timeoutSeconds":1,"periodSeconds":10,"successThreshold":1,"failureThreshold":3},"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"Always"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","serviceAccountName":"default","serviceAccount":"default","nodeName":"minikube","securityContext":{},"schedulerName":"default-scheduler"},"status":{"phase":"Running","conditions":[{"type":"Initialized","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-01-31T23:55:21Z"},{"type":"Ready","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-01-31T23:55:48Z"},{"type":"PodScheduled","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-01-31T23:55:21Z"}],"hostIP":"<IP_ADDRESS>","podIP":"<IP_ADDRESS>","startTime":"2018-01-31T23:55:21Z","containerStatuses":[{"name":"tiller","state":{"running":{"startedAt":"2018-01-31T23:55:43Z"}},"lastState":{},"ready":true,"restartCount":0,"image":"gcr.io/kubernetes-helm/tiller:canary","imageID":"docker-pullable://gcr.io/kubernetes-helm/tiller@sha256:a0bb59f866a28a8d3f2bc8aed32b75a79179e761414b03a5cd756b4317565eb2","containerID":"docker://77fab3d7c639dcca6eaf85b21807154dfa21633e5d9a8fcfaeef0df88c870adb"}],"qosClass":"BestEffort"}}
I0201 11:15:14.939958   19375 round_trippers.go:417] curl -k -v -XPOST  -H "User-Agent: kubectl/v1.9.2 (darwin/amd64) kubernetes/5fa2db2" -H "X-Stream-Protocol-Version: portforward.k8s.io" https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg/portforward
I0201 11:15:14.940937   19375 round_trippers.go:436] POST https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg/portforward  in 0 milliseconds
I0201 11:15:14.940949   19375 round_trippers.go:442] Response Headers:
F0201 11:15:14.941334   19375 helpers.go:119] error: error upgrading connection: error sending request: Post https://<IP_ADDRESS>:8443/api/v1/namespaces/kube-system/pods/tiller-deploy-595dcf9cd-frsmg/portforward: EOF

In my case, I was using a CNTLM proxy and had HTTP_PROXY settings (upper and lower and https) which I removed which made it work. presumably I need to add an exclude to my cntlm config for virtualbox range of addresses

I reinstalled repeatedly with slightly different versions of helm and minikube, always with the same results, as above
This morning at work I went through exactly the same set of steps (using current versions) and it worked the first time
Conclusion is that my home laptop is screwed in some subtle way
Home laptop is running Ubuntu 14.04 LTS, work is 16.04
Thanks @JeremyMarshall I'll see if there are any odd proxy settings that I missed

Thanks again @JeremyMarshall I discovered various shell proxy settings
env |grep -i proxy|awk -F= '{print $1}'
NO_PROXY
http_proxy
UBUNTU_MENUPROXY
https_proxy
no_proxy

I unset them all and hurrah!   helm now works
Hope this tip saves someone else a bit of time

Thanks again @JeremyMarshall I discovered various shell proxy settings
env |grep -i proxy|awk -F= '{print $1}'
NO_PROXY
http_proxy
UBUNTU_MENUPROXY
https_proxy
no_proxy

I unset them all and hurrah! helm now works
Hope this tip saves someone else a bit of time

@vorsprung thanks, this tips save me a lot of time!


this is a test

so sorry ,only to study

Do not test on public repositories! You're spamming everyone's notifications here. Please create your own public repositories to use as a testing environment.


chore(main): release dprint 1.15.4

:robot: I have created a release beep boop
1.15.4 (2024-07-22)
Miscellaneous

software: update installed (8a04760)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

dprint-v1.15.4
:sunflower:


Frames in the Market class

@sbenthall and I were discussing the move towards a 'frame'-oriented architecture (#798) today. He mentioned that something he was thinking about was how to deal with aggregate variables like pLvlAggNow. The issue is that these variables do have transition equations and get updated in well-defined frames, but it is not clear what HARK object that frame should belong to.
I argued that frames updating aggregate variables should belong to some external entity that contains the agents, like the Market class that is currently implemented.
My argument is that I assume it is within HARK's vision to eventually allow users to create ABM-type models in which different AgentTypes can interact (say, construct an economy with both IndShockConsumerTypes and PortfolioConsumerTypes). In such an environment, it would be arbitrary to give either of the agent types the responsibility of updating aggregate variables like total factor productivity or pLvlAggNow. These transitions should, in my opinion, be executed by the object that contains the agents (a Market or Economy).
@sbenthall thought that the argument was persuasive and wanted me to share it with everyone else. Hopefully it can spur useful discussions.

Thanks for posting this @Mv77
One idea this points to is how the Economy/Market class will look in cases where Agents are implemented with Frames.
Does the Economy also get frames? (i.e., corresponding to reap, mill, sow, etc.)
How do we determine the order in which frames get resolved?
paging @mnwhite

A literature that you might want to look into and which I studied in a past life is that of "Discrete-event Simulation".
This is a technique used in operational research to simulate things like production chains. I am sure there are many parts of their architectures that are irrelevant to HARK's purposes. The relevant aspect, which I remember very vaguely, is that there is an external "queue" of events that need to happen. Events are (I think) analogous to what we are calling frames and the queue is external in the sense that it does not belong to any of the objects (agents, markets,...) interacting in the simulation, but is a property of the simulation itself.
I naively imagine some external object with an ordered list of all frames that happen within a period (regardless of the object to which they belong). The list has pointers to the transition function of every frame, and time advances by iterating through the list and calling the transition functions.

Ah, thank you, that is very interesting.
I've been looking into agent based models (ABMs) more generally, which are more commonly invoked in the heterogeneous agent modeling (HAM) literature as an alternative to stochastic dynamic programming, which is also a HAM method (the one used currently in HARK and Dolo).
Discrete-event Simulations might be a good intermediary framework or point of reference, especially as the object relations between elements of the economy can be more complex. I like the idea of being able to model a production chain in the same system.

In the meeting today, we seem to be agreeing that the Economy/Market classes should also use Frames.
i.e. reap, mill, and sow should be frames.
This ticket can be for this task.

Question for @mnwhite : my understanding is that the most important part of the Market class for the solver is the calcDynamics method, which is user-defined and computers the aggregate dynamic rule.
Should this method also potentially depend on equations from the model specification, as has been proposed for AgentType solvers? See #856

Sort of.  But it will be hard to describe by equations per se, as it's
often the estimated parameters of a model that uses the previous history as
data.
On Tue, Dec 8, 2020 at 3:22 PM Sebastian Benthall<EMAIL_ADDRESS>wrote:

Question for @mnwhite https://github.com/mnwhite : my understanding is
that the most important part of the Market class for the solver is the
calcDynamics method, which is user-defined and computers the aggregate
dynamic rule.
Should this method also potentially depend on equations from the model
specification, as has been proposed for AgentType solvers? See #856
https://github.com/econ-ark/HARK/issues/856
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/issues/872#issuecomment-740973790, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKRAFNR3KDCUJWFCPAFDD3ST2DH5ANCNFSM4TXK4U4A
.

Ok. This ticket is for the Frames in the Market simulation.
We'll have to punt on calcDynamics.

Revisiting (and claiming) this ticket in light of new Block architecture.
Some notes based on a recent meeting with @mnwhite:

We already have Blocks which represent some part of the dynamic equations governing the system.
Currently, they are only used by an 'AgentTypeMonteCarloSimulator', which interprets these to be equations governing a specific agent, isolated from other agents.
The same DBlocks (and RBlocks) could be used by something else, which interprets them as operating at the aggregate level.
The main issue is that when an aggregate block follows an agent block, it should see the exposed agent state as vector values, and its equations should be able to compute aggregate statistics (such as the mean).
To support agent interaction with such a block, the aggregate block outputs (exposed end state) can also be vector valued.
Implementing this doesn't so much require a change to the block data structure, but rather requires something which creates these interpretations.
Ergo, a TODO is a MonteCarloSimulator (note, not an agent type) which takes in model configurations (blocks, with appropriate metadata, for example, as to whether or not a block is for an agent), and simulates forward.


Switch to use OPEN_CE_CUDA_HOME

This PR will switch the NVCC package to use and rely on the OPEN_CE_CUDA_HOME environment variable instead of the CUDA_HOME environment variable. The reasoning here is to avoid functional collisions with code that uses and relies on the CUDA_HOME environment variable. Such a case was seen in NCCL.
This should be safe as nothing else likely uses OPEN_CE_CUDA_HOME
Recipes will now need to use:
  - script_env:
          OPEN_CE_CUDA_HOME

This also changes the nvcc script to use $* instead of $@ so that everything is passed in verbatim. $@ does some evaluation and strips things like double quotes "

Note, the build images will also need to be changed.


Actually hide NSFW content

Dependent upon https://github.com/lbryio/lbry-redux/pull/53
Currently causes issues with the community top bids section. That will be fixed in a future PR.

This LGTM on the channel and search pages. Gave @seanyesmunt a heads up about subs page - if you are subbed to a channel that has NSFW (and have NSFW off), there's no indication on the sub page that they are hidden.

Actually, found an edge case when my own content is marked as NSFW and going to the channel page - says result is hidden, but it's not. We should not hide it if it's our own content, right? So just need to suppress the message.
https://www.screencast.com/t/vmUvZLTkuPv


python310Packages.miniaudio: 1.52 -> 1.53

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.miniaudio is: "Python bindings for the miniaudio library and its decoders"
meta.homepage for python310Packages.miniaudio is: "https://github.com/irmen/pyminiaudio"
meta.changelog for python310Packages.miniaudio is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.53 with grep in /nix/store/a78cxmrb66siqkv1qq19vn4cqfvm507a-python3.10-miniaudio-1.53
found 1.53 in filename of file in /nix/store/a78cxmrb66siqkv1qq19vn4cqfvm507a-python3.10-miniaudio-1.53

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.apple_tv
python310Packages.miniaudio
python310Packages.pyatv
python39Packages.miniaudio
python39Packages.pyatv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a78cxmrb66siqkv1qq19vn4cqfvm507a-python3.10-miniaudio-1.53 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a78cxmrb66siqkv1qq19vn4cqfvm507a-python3.10-miniaudio-1.53
ls -la /nix/store/a78cxmrb66siqkv1qq19vn4cqfvm507a-python3.10-miniaudio-1.53/bin

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

5 packages built:

home-assistant-component-tests.apple_tv
python310Packages.miniaudio
python310Packages.pyatv
python39Packages.miniaudio
python39Packages.pyatv

Maintainer pings
cc @dotlambda for testing.

Result of nixpkgs-review pr 198897 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.apple_tv
python310Packages.miniaudio
python310Packages.pyatv
python39Packages.miniaudio
python39Packages.pyatv


[8.x] Resolve component class with $attributes property

This small change allows one to type hint the $attributes parameter in the class constructor. This parameter contains an array of all attributes that were passed to this component.
<x-test-subject :foo="'bar'" baz="cookies" />

<?php

namespace App\View\Components;

class TestSubject extends Base
{
    public function __construct($attributes)
    {
        dump($attributes); // contains ['foo' => 'bar', 'baz' => 'cookies']
    }
}

As this change reserves the $attribute parameter name it's technically breaking, although it's pretty small, so not sure whether this is major or minor feature.
I will adjust the tests if this PR gets a green light.

Thanks for the PR, however the tests are failing.

@GrahamCampbell I've fixed the tests.
Also wanted to ask if this is something that can be merged in 7.x instead?

@panda-madness please revert all the unnecessary indentations.

You can access $this->attributes from within the render method.

@taylorotwell here is a reproducible demo showing that that is not the case, $this->attributes is still null even in render. Note the TestSubject component.

@panda-madness you commited your custom changes together with the framework skeleton which makes it super hard to find out what's wrong.

@driesvints Sorry about that. I've added some changes in a single commit to mark every file I modified, I'll know to separate my changes in the future.

Bump in the night, @taylorotwell

@panda-madness I've actually stumbled onto this myself in the meantime. I'll have a look at this today.

@driesvints something related to blade svg I guess? :)

@panda-madness heh yeah.
I discovered that you can still use attributes in your render method like this actually:
    public function render()
    {
        return <<<'blade'
        <div class="

            Foo

blade;
    }

Is there a special reason why you need to access the attributes? It's best that you provide a real-life use case. I'm having a look tomorrow again so let me know.

@driesvints I was trying to make a sort of dynamic component that would render other components and pass along the attributes that it receives, sort of like in Vue. For that I needed to extract 1 defined attribute (the component name), and pass everything else in the template.

@panda-madness I'm looking into doing that exact thing but you have to be aware that $data != $attributes. Data is all the data from the view piped through to components and attributes are the attributes defined in the html tag of the component.
What I would do in your case is dynamically render different views which have these components defined. Then you don't need to define them in your render method.

@panda-madness I've looked further into this but was unable to find a clean solution. I think it's a no-go on attributes being available in the render method for now.

@driesvints would you consider petitioning Taylor to re-open this PR then? I suspect he might have unsubscribed from the discussion here.

No, because I don't think this is the right solution either to mix data with attributes.

@driesvints I might be greatly misunderstanding how component tag compilation works, so please correct me if I'm wrong.
From what I'm seeing, $data initially contains all of the passed HTML attributes, and nothing else. You can see here and here where the attributes are Regex extracted and passed to $this->componentString(). The partitioning afterwards is, I assume, made to specifically enable constructor dependency injection via the service container, since the container needs named arguments for that.
I don't really see where we're mixing anything that's not supposed to be mixed, as far as I can see we are only operating on the attributes that are passed to the component tag.
Again, if I'm mistaken I'm sorry to have taken so much of your time on this.

Technically your change will work momentarily I believe but I think it'll collide with changes made in https://github.com/laravel/framework/pull/32576 for the next major release.

Is there a way to trigger the test suite against the new master branch?

Yeah, run them locally.

This should have been merged.
Attributes and slots should be accessible through the class constructor.
Here is a use case example for a component using Livewire:
class Input extends Component
{
    public $model;

    public function __construct()
    {
        $this->model = $this->attributes->whereStartsWith('wire:model')->first();
    }

    public function render()
    {
        return <<<'HTML'

                <input {{
                    $attributes->class([
                        'w-full placeholder-gray-400 rounded-lg',
                        'border-gray-400' => !$errors->has($model),
                        'border-red-600' => $errors->has($model),
                    ])->merge([
                        'type' => 'text',
                    ])
                }}>

                @error($model)

{{ $message }}

                @enderror

        HTML;
    }
}


Remove duplicate references to error4.c

The error4.c file is already listed in libsrc4_SOURCES, so does not need to be added again later.  The file's contents are only compiled if LOGGING is defined, so is ok to always compile.

Thank you @gsjaardema !


[ bug ] Controller text is selected if we click the new "true/false" toggle, and drag.

This is fixed as well, this issue can be closed


Dredd injects prelude between function declaration keywords

dredd mutates
class foo {
public:
  virtual void bar() const = 0;
};

class a : foo {
  void bar() const override;
};

void a::bar() const {
  int x = 2;
}

to
class foo {
public:
  virtual void bar() const = 0;
};

class a : foo {
  void bar() const #include <cinttypes>
###### PRELUDE #########

It seems that this is due to a bug in the getAssociatedRange function in SourceCode.cpp.
The problem is that this function tries to extend a range to include attribubutes.
The bar function has the override attribute because this is specified in the function prototype.
However, the out-of-line declaration of this function does not have the attribute as part of its declaration. The getAssociatedRange function extends the range to right before the override token in the class version of the function, which is not correct.

A similar issue arises with this:
class foo {
public:
  [[nodiscard]] int bar();
};

int foo::bar() {
  return 2;
}

The [[nodiscard]] in the class, but not the out-of-line declaration, leads to the wrong extended range.

It looks like isInherited could be queried on an attribute to see whether it is inherited from another declaration or not. See here.
This would require a patch to getAssociatedRange.

@JonathanFoo0523 I suppose #336 will also resolve this issue.

@JonathanFoo0523 Do you agree that we can close this now?

Agree. Closing this...


Uncaught error after creating new Dart library. Seems related to outline view

Using version 1.12 of the 64-bit Linux Dart SDK.

Create a new Dart package with pubspec
Create lib directory with file in it
Open Dart file in lib and begin typing library
Outline view does not update with new members

Atom Version: 1.0.10
System: Ubuntu 15.04
Thrown From: dartlang package, v0.4.1
Stack Trace
Uncaught Uncaught Error: NullError: method not found: 'get$iterator' on null
Stack Trace:
TypeError: Cannot read property 'get$iterator' of null
at [object Object].J.get$iterator$ax (/home/austin/.atom/packages/dartlang/web/entry.dart.js:40600:41)
at OutlineView.dart.OutlineView._handleOutline$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:23413:23)
at [object Object]. (/home/austin/.atom/packages/dartlang/web/entry.dart.js:16917:32)
at _RootZone.dart._RootZone.runUnaryGuarded$2 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:30734:20)
at _BroadcastSubscription.dart._BufferingStreamSubscription._sendData$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:29878:20)
at _DelayedData.dart._DelayedData.perform$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:30072:18)
at _StreamImplEvents.dart._StreamImplEvents.handleNext$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:30145:16)
at _PendingEvents_schedule_closure.dart._PendingEvents_schedule_closure.call$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:30120:12)
at _AsyncCallbackEntry.dart._AsyncCallbackEntry.callback$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:29023:30)
at [object Object].dart._microtaskLoop (/home/austin/.atom/packages/dartlang/web/entry.dart.js:27728:12)
at [object Object].dart._microtaskLoopEntry (/home/austin/.atom/packages/dartlang/web/entry.dart.js:27734:11)
at TimerImpl_internalCallback0.dart.TimerImpl_internalCallback0.call$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:16100:35)
at invokeClosure_closure.dart.invokeClosure_closure.call$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:17775:41)
at _IsolateContext.dart._IsolateContext.eval$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:15714:25)
at [object Object].dart._callInIsolate (/home/austin/.atom/packages/dartlang/web/entry.dart.js:15354:28)
at dart.invokeClosure (/home/austin/.atom/packages/dartlang/web/entry.dart.js:16817:18)
At /home/austin/.atom/packages/dartlang/web/entry.dart.js:15723

Uncaught Error: NullError: method not found: 'get$iterator' on null
Stack Trace:
TypeError: Cannot read property 'get$iterator' of null
    at [object Object].J.get$iterator$ax (/home/austin/.atom/packages/dartlang/web/entry.dart.js:40600:41)
    at OutlineView.dart.OutlineView._handleOutline$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:23413:23)
    at [object Object].<anonymous> (/home/austin/.atom/packages/dartlang/web/entry.dart.js:16917:32)
    at _RootZone.dart._RootZone.runUnaryGuarded$2 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:30734:20)
    at _BroadcastSubscription.dart._BufferingStreamSubscription._sendData$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:29878:20)
    at _DelayedData.dart._DelayedData.perform$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:30072:18)
    at _StreamImplEvents.dart._StreamImplEvents.handleNext$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:30145:16)
    at _PendingEvents_schedule_closure.dart._PendingEvents_schedule_closure.call$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:30120:12)
    at _AsyncCallbackEntry.dart._AsyncCallbackEntry.callback$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:29023:30)
    at [object Object].dart._microtaskLoop (/home/austin/.atom/packages/dartlang/web/entry.dart.js:27728:12)
    at [object Object].dart._microtaskLoopEntry (/home/austin/.atom/packages/dartlang/web/entry.dart.js:27734:11)
    at TimerImpl_internalCallback0.dart.TimerImpl_internalCallback0.call$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:16100:35)
    at invokeClosure_closure.dart.invokeClosure_closure.call$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:17775:41)
    at _IsolateContext.dart._IsolateContext.eval$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:15714:25)
    at [object Object].dart._callInIsolate (/home/austin/.atom/packages/dartlang/web/entry.dart.js:15354:28)
    at dart.invokeClosure (/home/austin/.atom/packages/dartlang/web/entry.dart.js:16817:18)
    at [object Object].dart.wrapException (/home/austin/.atom/packages/dartlang/web/entry.dart.js:16669:17)
    at _rootHandleUncaughtError_closure.dart._rootHandleUncaughtError_closure.call$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:30703:17)
    at _AsyncCallbackEntry.dart._AsyncCallbackEntry.callback$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:29023:30)
    at [object Object].dart._microtaskLoop (/home/austin/.atom/packages/dartlang/web/entry.dart.js:27728:12)
    at [object Object].dart._microtaskLoopEntry (/home/austin/.atom/packages/dartlang/web/entry.dart.js:27734:11)
    at TimerImpl_internalCallback0.dart.TimerImpl_internalCallback0.call$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:16100:35)
    at invokeClosure_closure.dart.invokeClosure_closure.call$0 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:17775:41)
    at _IsolateContext.dart._IsolateContext.eval$1 (/home/austin/.atom/packages/dartlang/web/entry.dart.js:15714:25)
    at [object Object].dart._callInIsolate (/home/austin/.atom/packages/dartlang/web/entry.dart.js:15354:28)
    at dart.invokeClosure (/home/austin/.atom/packages/dartlang/web/entry.dart.js:16817:18)
    at /home/austin/.atom/packages/dartlang/web/entry.dart.js:16838:18

Commands
  3x -0:30.1.0 core:close (atom-text-editor.editor.is-focused)
     -0:00.5.0 dartlang:newline (atom-text-editor.editor.is-focused)
     -0:00.5.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:00.3.0 dartlang:newline (atom-text-editor.editor.is-focused)
     -0:00.3.0 editor:newline (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "projectHome": "/home/austin/workspace"
  },
  "dartlang": {
    "sdkLocation": "/home/austin/lib/dart-sdk"
  }
}

Installed Packages
# User
.bin, vundefined
Sublime-Style-Column-Selection, v1.3.0
atom-typescript, v6.0.0
dartlang, v0.4.1
editorconfig, v1.1.1
file-icons, v1.6.9
hex, v0.6.2
highlight-selected, v0.10.1
linter, v1.5.0
minimap, v4.13.2
minimap-bookmarks, v0.1.0
minimap-git-diff, v4.1.8
minimap-highlight-selected, v4.3.0

# Dev
Sublime-Style-Column-Selection, v1.3.0

Seems to be when the Dart file doesn't have any members in it yet. Once I add a member to the file it stops throwing the exception.


About reproducing the proto net results with ConvNet

@Han-Jia , Thanks for your source code! But I have some troubles in reproducing them.
I have achieved only 51.97% for the 1-shot 5-way of ConvNet case and 70.60% for 5-shot 5-way of ConvNet case.  The hyper-parameters I used is:

--lr 0.0001 --temperature 32 --max_epoch 200  step_size (schedulr) = 10, gamma=0.2 for 1-shot 5-way of ConvNet

--lr 0.0001 --temperature 32 --max_epoch 200  step_size (schedulr) = 10, gamma=0.2 for 5-shot 5-way of ConvNet

Should I make any changes to other default parameters to reproduce the result in Table1 (52.61% and 71.33% test acc)?
any information will be greatly appreciated

Hello,
For the ConvNet backbone, please try

--lr 0.0001 --temperature 64 --max_epoch 200 step_size (schedulr) = 50, gamma=0.1 for 1-shot 5-way of ConvNet

--lr 0.0001 --temperature 16 --max_epoch 200 step_size (schedulr) = 30, gamma=0.1 for 5-shot 5-way of ConvNet

For the temperature, it seems high-temperature value will not degrade the results. It's better to try larger temperature values.
You can also increase the number of validation tasks to select the best model.


Brackets 1.10 update does not work on Windows 10 Home

Description
I recently tried to update to the newest version of brackets.io 1.10. When I did I was no longer able to open regular HTML & CSS files other than the bracket's getting started html/css. While these files would appear in the working tree, the editor itself would not open these files (though they had been working in the earlier version of brackets).
Steps to Reproduce

[First Step] - update to 1.10 version of brackets
[Second Step] - map to any folders containing index.html/css, etc...
[and so on...] - try to open them in brackets on Windows 10 home version

Expected behavior: [What you expected to happen]
I would expect that my index.html, css, live preview, etc.. would open and work as normal, but it doesn't.
These were files that had worked before but now, on the new version of brackets, did not.
Actual behavior: [What actually happened]
While the files appear in the tree alongside the text box area, the files themselves will not open. It is as though Brackets does not recognize these files.
Versions
Tried to run this on Windows 10 Home after I updated from the brackets 1.08 ver to the most recent 1.10 version. Previous version worked while the 1.10 version of brackets does not recognize or open any files including basic html & css unless it is the getting started html & css that accompanies brackets.
I did manage to revert back to the 1.08 version, as I reinstalled the older version, and the text editor functioned properly, recognizing and opening my html, css, js, etc.. files.

Try deleting Brackets completely and reinstall Brackets via the latest installer again. There were some backwards incompatible changes to file handling which require the new version of Brackets Shell. Sorry for you troubles!

I should have mentioned this in the initial statement - I uninstalled and reinstalled this newer version 3 times along with restarting the computer each time. Ultimately, I had to go back to the older version in order to get any of the editor's features to work/to get my html files to open.


Blade Pitch Angle Stuck Fault Simulation Issue

Hello,
I hope you’re doing well. I am currently working on implementing a fault in the pitch angle control system. The fault scenario involves Blade 1’s pitch angle being fixed at its exact value at 400 seconds and remaining stuck in that position. To achieve this, I attempted to modify the relevant source code in ServoDyn, specifically the UserSubs.f90 file and the PitchCntrl subroutine, as shown in the attached image. Additionally, I’ve also included the pitch control settings from the ServoDyn module for reference.
However, when I run the simulation on the 15 MW semi-submersible turbine model, I am not getting the expected results.
I intended for the Blade 1 pitch angle to behave exactly like the normal operation curve during the first 400 seconds, but it does not. I kindly ask for your guidance in resolving this issue.
Thank you very much for your help!

Dear @dorsamgh,
I see a few problems with your approach:

The IEA Wind 15-MW RWT OpenFAST model makes use of the ROSCO controller, which would be called by setting PCMode = 5, but you have disabled the ROSCO pitch controller by setting PCMode = 3.  If you want to use ROSCO up until the fault, you'll have to modify ROSCO directly, not UserSubs.f90.
The simulation time (ZTime) may not reach exactly 400 s (depending on the time step, DT).  I would use some tolerance based on DT in the calculation.
Your FixedPitch variable is a local variable that you have not marked with the SAVE attribute, so, its value won't be saved between calls to your routine.

Best regards,

dear @jjonkman
Thank you for your response. Now, I have the question that when PCMode is set to 3, does it completely disconnect from Roscoe? While by changing YCMode to 3 and modifying the source code related to yaw control, I achieved the desired change, as shown in the images. I would like to achieve similar behavior in relation to the blade pitch angle.

Dear @dorsamgh,
ROSCO will only control blade-pitch if you set PCMode = 5 in ServoDyn.  If you want to override ROSCO or other active blade-pitch control actions with a ramp or step function, you can use the override pitch maneuver inputs (TPitManS, PitManRat, BlPitchF).  (A step function could be approximated by setting PitManRat high).
FYI: You could also implement a ramp or step function in yaw through the override yaw maneuver inputs (TYawManS, YawManRat, NacYawF).
Best regards,

Dear @jjonkman
Thank you. I had also thought of this solution and implemented it. However, I wanted the simulation to be such that the blade pitch angle stays exactly at the value it has at time 400 (without considering other parameters like the BTS file, etc.). If I want to use this method, I need to adjust the final blade pitch value at each simulation run to match the normal value it has at time 400, based on the different conditions. Is that correct?

Dear @dorsamgh,
I see two possible solutions: (1) run two simulations, recording the pitch angle at 400 s from the first and setting that to BlPitchF in the second simulation with the override manuever set with TPitManS = 400 s and ; (2) changing the OpenFAST source code to implement this logic and recompiling.
Best regards,

Dear @jjonkman
I feel more comfortable with your first suggestion and have implemented it. I think it's sufficient for my work as it is. Thank you for always providing generous and quick guidance and responses.
Sincerely, Dorsa

Dear @dorsamgh,
I'm glad your problem is solved.  I would call this an "actuator fault".
Best regards,