deCONZ - FATAL: No device since 3.4 / 3.5

Today i updated deCONZ addon first to 3.4 and then to 3.5
On both new versions i get this error when i try to start the addon.
[16:52:47] FATAL: No device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1962254-if00 found!
That device path shows under "hassio/system/hardware" and worked on addon version 3.3
I have tried to change the device to this diffrent ones (one by one) but they give same error.
"/dev/ttyUSB0"
"/dev/ttyUSB1"
"/dev/ttyAMA0"
"/dev/ttyAMA1"
"/dev/ttyACM0"
"/dev/ttyACM1"
Restoring from snapshot to 3.3 makes it work again

Hi. I have the same issue. But you can make it work with /dev/ttyACM#. But you have to restart Home Assistant. It is not enough to restart the addon.
This is really annoying. I was so happy when the addon was changed so it accept the by-id links as my Aeotec and Conbee randomly swap between 0 and 1 when I reboot the host machine.
We need that restored again. It is important that you can use these /dev/serial/by-id/blabla links so things are predictable and reliable.

@pvizeli it seems you did the change that broke the use of /dev/serial/by-id links. We had been begging for this feature and finally got it a month or so ago. It would be really good if you would fix your latest changes so it works again. You cannot rely on direct /dev/tty links and you all the normal udev tricks do not work as they also create symlinks that don't work.

Can't see any issue with Supervisor 185 and docker 18.09 or 19.03

My deCONZ addon also broke when updating from 3.3 to 3.5, refuses to start.
Log entrys:
2019-09-03 21:31:23 ERROR (MainThread) [.] Error connecting to deCONZ gateway at <IP_ADDRESS>
2019-09-03 21:31:23 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 5 seconds.

what say the dmesg after start?

This is the complete dmesg from last boot, there are an awful lot of entrys about the conbee…
//Mattias
Från: Pascal Vizeli<EMAIL_ADDRESS>Svara till: home-assistant/hassio-addons<EMAIL_ADDRESS>Datum: tisdag 3 september 2019 22:52
Till: home-assistant/hassio-addons<EMAIL_ADDRESS>Kopia: Mattias Hemborg<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Ämne: Re: [home-assistant/hassio-addons] deCONZ - FATAL: No device since 3.4 / 3.5 (#685)
what say the dmesg after start?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I think the original reporter did not restart HA but only the addon when he reported that it does not work with any device. I can make it work with /dev/ttyACM1.
We may want the original reporter to verify that it works for him if he restarts the entire HA installation.
What is broken is using the /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_.......
The error message is that it cannot find this device. It worked fine until I upgraded to the 3.5 (from 3.3).
In the bare metal host the by-id link is present still.

The question is, what is different on your baremetal setup. Tested with docker 18.09 and 19.03 / supervisor 185 -> HassOS, Debian, Ubuntu 18.04 (Desktop)

@mattias1972 docker is not plug&play. If you plug out the stick at back again, you need restart the add-on, but the device is block by docker and it create a time a new ttyUSBx. Try a full host reboot to become a clean state

@mattias1972 docker is not plug&play. If you plug out the stick at back again, you need restart the add-on, but the device is block by docker and it create every time a new ttyUSBx. Try a full host reboot to become a clean state

It still refuses to start despite a reboot of the Pi. dmesg shows fewer entrys about the combee but still there are 10 of them this beeing the last one:
77.051689] usb 1-1.1.2: USB disconnect, device number 10
[   77.401865] usb 1-1.1.2: new full-speed USB device number 11 using dwc_otg
[   77.536208] usb 1-1.1.2: New USB device found, idVendor=1cf1, idProduct=0030
[   77.537386] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   77.539587] usb 1-1.1.2: Product: ConBee II
[   77.540730] usb 1-1.1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[   77.542019] usb 1-1.1.2: SerialNumber: DE1996448
[   77.545521] cdc_acm 1-1.1.2:1.0: ttyACM0: USB ACM device

I have triple checked again and I have this config
{
  "device": "/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1962724-if00",

and I get the error
starting version 237

[23:21:48] FATAL: No device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1962724-if00 found!

And extra check that I use the correct device

root@homeassistant:/dev/serial/by-id# ls -al
total 0
drwxr-xr-x 2 root root 80 Sep  3 23:31 .
drwxr-xr-x 4 root root 80 Sep  3 22:48 ..
lrwxrwxrwx 1 root root 13 Sep  3 23:17 usb-0658_0200-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Sep  3 23:31 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1962724-if00 -> ../../ttyACM1

Same here. Broke when updating from 3.3 to 3.5 with the same stick. Using /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1995908-if00 which is there, even within the container.

Tested with docker 18.09 and 19.03

Since no one gives details about his installation, I would suggest that you have the wrong docker installed and not docker-ce.

This is hassio, latest everything, except for home assistant itself (0.97.2), and deconz addon (3.3). Let me know where in hassio you'd like to have a dump for more formation about internals (docker, etc.)
As far as I can see from the UI, i've gathered the following info:

hassio supervisor 185
via Portainer, I've discovered i'm running Docker Standalone 18.09.4

docker-ce? BaseOS?

I had setup now a new ubuntu core 18.04. Install all dependencies and docker-ce (From docker repository). Everythings work with "/dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DM01H1ID-if00-port0"
I can't help here. I think there is an issue on setup. There was an update how the supervisor spinup itels. Maybe you run the old service files. Execute:
curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | sudo bash -s
to update the installation and restart the server. That could help

I think we have several populations here.

From #680 people that already had the issue before the 3.4/3.5 update
People that get an error that device is not ready yet
And then we are at least 3 or 4 that have the situation where the by-id link does not work in 3.5 but works in 3.3

They should probably be split on 3 bug reports
I am only addressing case 3 which is what seems to best fit the original report.
I surely run docker-ce. I had upgraded to the latest 0.98.2 before the upgrade of deconz and it worked. I know because when it fails all my automatic light stops working so I would have noticed
Mine broke down the minute I upgraded the deconz addon from 3.3 to 3.5 (did not see the 3.4 update) and to get it back I had to use the straight /dev/ttyACM# link
When I look at the host Ubuntu I notice that udev create symbolic links from /dev/serial/by-id that point back to /dev
When I use the ssh within HA the docker view of things are that /dev/serial/by-id/device_name are "files" and not links. I do not know if this means anything but it is an observation
I also have an Aeotec Z-wave stick using ZHA.
It is configured and WORKS like this
zwave:
  usb_path: /dev/serial/by-id/usb-0658_0200-if00
  network_key: !secret zwave_network_key

So for the zwave integration the by-id works fine.
In the Home Assistant hass.io -> Host System -> Hardware button I can the the two by-id devices
The error message from deconz is "FATAL: No device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1962724-if00 found!"
This is the same error you get if you put some complete nonsense.
The conclusion I have so far that this seems to be an isolated problem to the deconz docker container. Inside this the by-id devices do not exist. We need to find out why. If we go back a few versions of deconz it did not work either. Then the feature was introduced so you could use by-id links. And now it is broken again. And it happens in a release where udev was dramatically chanced as far as I can see in the code without understanding what is it that happens. It seems some udev related stuff was change to using a python based library. But I do not know Python so I am a bit lost

You say everything works with Everythings work with "/dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DM01H1ID-if00-port0"
That is not a deconz device. They are not getting named like that. It is ONLY in deconz things fail. It works just fine in ZHA. A deconz device name has dresden_elektronik_ingenieurtechnik_GmbH in them

Just came home from work so I could access the HA machine from command line.
I tried the script https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh and restarted server - it made no difference
I then tried to restore a snapshot of HA but I kept all current and only restored deconz 3.1. I did not have a snap with 3.3 sorry. But when I restore deconz 3.1 it works again with the 'by-id' device. And when I upgrade deconz back to latest it breaks again. It cannot be a setup or docker version issue. And it is not related to the changes in hass.io done recently. It is isolated to deconz. 3.1 works. 3.5 fails to use by-id links. I have to use simple /dev/tty devices again to make it work.

Five reboots later deCONZ addon suddenly has decided to work again. I have no idea what was wrong and no clue why it works again... Maybe my Conbee II is faulty, only time will tell, for the moment everything work again.

@KennethLavrsen I have all devices from deCONZ. The ID above was a Conbe1.
I'm wrong, after rerunning the installation, you need to destroy the supervisor container to start a rebuild with new parameters. docker rm hassio_supervisor.
I close the issue after I tested it on a HassOS, Debian, Ubuntu with a fresh installation and with latest installer scripts. There is no Python, because it's a complex system between Linux kernel, udev bus, and docker as it is. This work only with "latest" spinup of supervisor. If you run the supervisor container with an older setup before 5 month, there is an issue with trigger reload of udev devices overall containers they are listening to the linux kernel bus.

@balloob I want to complain about how this issue is treated. We are several people with the same issue and there is no resolution.
I will reopen new issue with same content

And for the record
I have done all suggestions so far and I just did the docker rm hassio_supervisor
And I reran the install script.
And it still fails the same way.
It is not correct to close an issue after so short time when several people are reporting the same issue. I can understand if it is one socker that refuse to try anything. But we are multiple people with same issue and there is obvious an issue caused by the changes in deconz 3.5
I will also say that mattias1972 reported a completely different symptom and his resolution has nothing to do with the issue originally reported.
The least one can do is revert the changes back to what actually worked until we understand what goes wrong.

I continue gathering info.
I read up on docker and now I know how to create a bash session on a running container.
And to my surprise I can find /dev/serial/by-id/usb-... links to both sticks and they are symlinks and they point to the right place.
So I tried again to change the deconz config to the by-id device and restarted deconz only. And it worked. Why? What? So I tried to see if this was a lasting fixed by itself situation. No it is not! After a restart of HA I am back to not working with same error message. The container was then manually started and it worked. And then tried many boots of the entire metal machine as well as HA. It works every 3rd time or so.
It seems to be a timing issue. Maybe udev is not done running before deconz is started and trying to access the device. It is a "no device found" error. Not access denied or device busy or similar. So my best guess now is that either udev does not always succeed creating the by-id symlinks or it does it too late. I need advice how to debug this further.
@pvizeli will you be so kind and reopen this so we do not discuss this on a github issue that soon freezes for comments?

I am trying to figure out what is going on at start. But I do not understand how the docker thing works. I am a docker noob obviously.
I can see in my /usr/share/hassio/addons/core/deconz/data directory that there is a run.sh that seems to be a bash script that start up deconz. But it is obviously not this script that runs because when I edit the file no change is done. There is a 3 second delay I would like to increase to 5 or 10 to see if it makes a difference. How do I get this change made effective?

I have been working half the night yesterday, reading HA dev documentation at work, and worked several hours today trying to debug this. I am stuck at how to modify the run.sh script and rebuild the deconz image with the change. I have asked on Discord in the dev_general channel but noone has been there today that could help.
I really tried to understand the addon development documentation and I tried many things that all failed.
I need help to pass the point where I am stuck. I really want to participate and spend the hours debugging and root causeing this and I respect that it is impossible for @pvizeli to fix something he cannot reproduce. But I can reproduce it here. If I restart deconz 10 times it fails 50% of the time. It can work 5 times in a row and fail 5 times in a row. But it is 50/50 that it fails or start normally with by-id device. I have a theory that the delay of 3 seconds may not be enough in some cases. It can also be that udev fails to create the symlink. To find out what it is I need to be able to alter and add debug echos to the run.sh script
I just cannot find out how to get the docker container rebuilt with my changes. I do not understand how it works. I need help. A one liner - this is how to rebuild the container picking up the altered run.sh is what I need. Please

I gave up on using the Home Assistant Addon version of deconz.
I found that it was dead easy to install deconz from the original Debian repository. Then it updates every time I do apt upgrade. Much easier. And it runs on bare metal.  So no more worries about devices swapping around. So if someone else want to escalate this issue then go ahead. I am done. I also moved mqtt and other things back to bare metal some time ago.

I've just locked this addon on 3.3 and will not be updating it anymore. My vacation starts tomorrow, so i'll be out for a while. Hopefully this will eventually get fixed.

Another with same issue
https://community.home-assistant.io/t/deconz-official-thread/100504/577
Sad that the developer refuses to fix it and assume we are all wrong

I think your last comment (the last line) is completely unnecessary, disrespectful and not called for @KennethLavrsen.
Sorry to hear you are having issues, but without a reproduction scenario, it will be hard for anyone to fix (as you've said yourself earlier). Both me and Pascal have a large number of (different) test systems. On none of those, it is reproducible.
This has nothing to do with refusing to fix it.

@frenck
I think closing an issue claiming there is no issue is equally disrespectful to all the people with the problem.  And then repeating it again to a new user closing exactly same issue one more time.
And I am sorry for only being a human with human feelings. I got upset. In the official deconz forum topic there are new people that reported the same issue. It affects many people.
I spent more than 20 hours trying to debug the problem but I got stuck because I still do not understand how to rebuild a docker after changing the script that runs when it starts. I tried to get help in the dev channels on discord but noone was present to help me.
I can see that there is a 3 second delay in the script and my current theory is that the new way of running udev takes more than the 3 seconds on some computers depending on how much hardware that needs to be discovered.
I tried to read the dev docs carefully but I know too little about dockers to understand how to rebuild the containers with changed content. I tried many things but always end up with the original code running with the 3 second delay
I fixed MY immediate issue by moving to a non Home Assistant solution (bare metal). I am trying to help the other users that try to use the HA addon now.
The way forward that I suggest is

Reopen this bug
Try and build the addon changing the 3 second delay to a wait for the serial device to be existing - with a timeout of maybe 30 or 60 seconds so the addon can die if the device was defined wrong by the user
Release this as an update even if you cannot confirm it fixes the issue and ask the people that reported the issue to come back with feedback if it fixes it.


forms and checkout component views only

Assignee Tasks

[ ] added unit tests (or none needed)
[ ] written relevant docs (or none needed)
[ ] referenced any relevant issues (or none exist)

Guidelines
Please add a description of this Pull Request's motivation, scope, outstanding issues or potential alternatives, reasoning behind the current solution, and any other relevant information for posterity.

Your PR Notes Here

Great job!


ci: allow root login by SSH

Noticed that by default on latest SSH root is not allowed to login, requires explicit configuration. This prevents the CI to get stuck attempting to connect to nodes on reboot

Should be added to docs as well, showing our users how to enable root logins in Micro 6.

Indeed, that would be nice to be documented, together with adding a serial console at boot. It was quite annoying not having the serial console while debugging. Gonna verify this change first, next is adding a serial console for tests, so we get all boots and reboots data.


cilium: Add deprecation warning for service ids

The NodePort service frontends are currently expanded early in the K8sWatcher and the IDs used by datapath are allocated for these expanded frontends in pkg/service. A NodePort frontend is created for the Node IP and other routable IPs on the system. As this is now something that can be reconfigured at runtime when devices change, we would like to make the frontend expansion and the service and backend identifiers implementation details of the datapath and not expose them to the user via the REST API (PUT /service/{id}) or the "cilium service update" command.
In v1.14 we will implement this by changing the {id} from int into a string (something like "<IP_ADDRESS>:80:TCP" or "[f00d::1]:80:TCP").
We're expecting this change to only affect standalone load-balancer users that are using the "cilium service" commands directly. We do not expect there to be direct use of the "/service/" REST endpoints. Based on this we deem the backwards incompatible change to the type of the {id} parameter acceptable.
In order to give advance warning to the users, this commit adds deprecation warnings to the cilium-agent logs when the /service endpoints are used and to the cilium command-line utility when "cilium service update" or "cilium service delete" is used.

Are these warnings enough or should there be changes to documentation already in 1.13 (release notes etc)?

/test-backport-1.13

/test


fixing some compilation errors in armgcc

compiling with lots of warnings. Needs a second round.
MAC no synchronizing with 2 motes,
14:05:50 ERROR 9c86 [IEEE802154E] invalid packet from radio, length 249 (code location 0)
to check wit sniffer and see if EBs are sent correctly.
to check MAC layer timing.

do not merge this, sorry was an error.


fix(MD-4208): don't recreated component if already there

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 625

Questions ?
Please refer to the Backport tool documentation


storage/filesystem: dotgit, could not get blob from packfiles

Could not get blob from packfiles, occurs a error packfile not found.
The cause is an unnecessary temporary file parsing error generated by git gc.
We should correctly check the packfile name format and skip over not loading those temporary files,
name format of temporary file:
.tmp-12345-pack-{hash}.pack
I have a PR.

I have run into multiple instances where something like that happens. It seems that regular GIT sometimes produces and consumes a objects/info/packs file with a list of actively used packfiles. Often I have some more pack files in objects/pack that were not cleaned during previous repacking.


Can we drop the MailChimp requirement

Mailchimp's api supports CSS-inlining, but there has to be an alternative to making a call to another email marketing company. It just seems weird to me.
premailer didn't work because it doesn't support external style sheets?
inlinestyler seems to support them...?

So this doesn't feel like a huge priority to me anymore. It seemed really weird at first, but if it works it works. At the very least we should document it in the readme...

Dropped back on 2016-03-18.


ATO-732: Add login_required error code description

Why
We're adding support for a new "login_required" re-authentication error code.
See:

https://govukverify.atlassian.net/wiki/spaces/LO/pages/4092952611/Re-Auth+-+Incorrect+details+provided+by+user#Orchestration
https://govukverify.atlassian.net/jira/software/c/projects/ATO/boards/390?assignee=712020%3Ac05df90e-0476-43ae-85c5-1cd3a261173b&selectedIssue=ATO-732

What

Add a entry to the error code table documenting  when an RP might receive this code and what it means.

Technical writer support
Yes, please provide feedback on any corrections or improvements.
How to review

Check change communicates what is intended clearly.
Check for typos.
Confirm if change is consistent with existing documentation.
Confirm if update to change log was necessary.

Changelog

[x] If this change is significant (for example, launching a new feature or deprecating a feature), you should update the changelog found at partials/_changelog.erb  under the heading 'Documentation updates'.#

Confirm

[ ] I have checked if any docs change here also requires updates to other repositories (ADRs / RFCs, README.md, Team Manual, elsewhere in these docs)
[x] Where there is any overlap I have updated or opened a PR for corresponding changes

Thanks! Not ready for merging as this needs tech writer support. I'll check who can pick this up 👍

hi @BenjaminWCO let me know when the changes have been made and I'll do another review

Thanks @PippaClarkGDS , taking a look now.

Hi @PippaClarkGDS, I've made those changes. Thanks for the help. Just made one small tweak to your recommendations regarding the email as you suggested might be the case. Let me know if you have any other thoughts.

Nice @BenjaminWCO - @sabrinaharris will be able to add her review now

Thanks @ethanmills, @PippaClarkGDS . I'll wait for confirmation from @sabrinaharris and the changes to be in production before I merge this.

Hi, @sabrinaharris, fixed the change log conflict.


leftover changes from PR 746

Changes proposed in this PR

some small fixes

Why are we making these changes?
already committed to making these changes in PR 746

@shamsimam  all green, can you merge


MSSQL: All lines in table are anonymized to same values

Using only the anonymize step to anon existing DB. In tables where row count is low, the records are anonymized correctly. If the row count is higher (e.g. 1000) all records have same values in anon columns.
I would expect that all tables has random values in all lines.
Repro-steps> not having yet (anonymization of customer's database). Before I start to play with the repro steps I want to know if there is some known issue with that to not spend time on something known.
Have used:
pynonymizer.run(input_path="",output_path="",strategyfile_path="./strategy.yml", db_server=".",db_type="mssql", db_name="anon",db_user="myuser",db_password='mypwd',fake_locale="cs-CZ",dry_run=False,verbose=False,start_at_step='ANONYMIZE_DB',stop_at_step='ANONYMIZE_DB')

Seems to corelated with subquery caching mentioned here: https://stackoverflow.com/questions/39101333/force-sql-server-to-stop-caching-subquery

Hi,
Definitely not the correct behaviour / known issue. I had a report of this in behaviour in mssql provider a few years ago but I couldn't replicate it in my mssql instance.
I want to make sure we capture this effort into integration tests for the project since the mssql provider is by far the most touchy one!
There was a similar issue in the postgres provider a while ago: https://gitlab.com/jerometwell/pynonymizer/-/issues/49 , maybe the workaround there (using literal with an uncachable subquery) might work for you until we can fix this?

Thanks,
I have solved the problem partially even I am not python developer...
the prevention of cached subselect(seems that when there is more than x rows the SQL will optimize the subselect because it is not depending on the main data, thus executing it only once and using the result everywhere) is to make it depending on the main data. I did it in this way:
return f"( SELECT TOP 1 {column} FROM [{SEED_TABLE_NAME}] ORDER BY NEWID(),CHECKSUM({SEED_TABLE_NAME}.{column},[{table_name}].[{field_name}]))"

in the __get_column_subquery. It makes the subselect depending on the data of the query. Side-effect is, that if the caching kick in, the result is "deterministic" because same original value is replaced with same generated "pseudo-random" value because the cache, but this is for me even better ;-)
I can create PR for this, but someone must add the tests and somehow tune the code, because really I just did without deep python knowledge.
Another part of the fix was to use "SET ANSI_WARNINGS off" to disable warnings when generated value is truncated because the target field is shorter (had some problem with long city name in cs-CZ fake dataset).

Thanks for your prototype and suggestions, it's a great starting place 😇 It looks like we'll be doing roughly what we did for postgres, i.e. depending upon something in the query which makes it hard to cache, like you say!
I will pick this up for next release.
I've tried to keep strategy.scripts open for stuff like SET ANSI_WARNINGS off but maybe that's not working for you? part of pynonymizers unofficial goals is to remain flexible enough without literally supporting every feature 😅

Ok, thanks, my mistake, have forgot to use the scripts to set the ANSI_WARNINGs... first time I am using pynonymizer... next time I will know... ;-) (but I am not sure if it will work - depends if all is running in same session or not, because this is per session setting).

hey @kine can we chat about ANSI_WARNINGS? I looked at your implementation on your fork - I have some reservations about enabling ansi_warnings for everyone, I'm concerned that the behaviour might not be applicable to everyone. What do you think?

Yes, it could be "too strong" for others. But without this the process will fail if the generated value is somewhere longer than the field in table. You will need to fix that in the code. This setting is solving this without adding the length check in code.
From documentation:
SET ANSI_WARNINGS affects the following conditions:

When set to ON, if null values appear in aggregate functions, such as SUM, AVG, MAX, MIN, STDEV, STDEVP, VAR, VARP, or COUNT, a warning message is generated. When set to OFF, no warning is issued.

When set to ON, the divide-by-zero and arithmetic overflow errors cause the statement to be rolled back and an error message is generated. When set to OFF, the divide-by-zero and arithmetic overflow errors cause null values to be returned. The behavior in which a divide-by-zero or arithmetic overflow error causes null values to be returned occurs if an INSERT or UPDATE is tried on a character, Unicode, or binary column in which the length of a new value exceeds the maximum size of the column. If SET ANSI_WARNINGS is ON, the INSERT or UPDATE is canceled as specified by the ISO standard. Trailing blanks are ignored for character columns and trailing nulls are ignored for binary columns. When OFF, data is truncated to the size of the column and the statement succeeds.

Null values we are not solving, we are not dividing. Thus only the field length is crucial for us thus I think it could be safely used. E.g. possible to enable this through parameter will be nice. But still, situation, where the generated value is longer than field will kill all, thus what else we can use to solve this problem? Shoudl I open separate issue for solving the "value xxxx is longer than..."?

My original thought was more along the lines of "would this cause anonymization to be improperly performed when enabled?" and looking at the docs here I don't have that concern. pynonymizer's goal should be to be compatibile with the database, not the other way around 😅
If people get some truncated replacement data, that seems agreeable to me!
I'll integrated this into #48 and add a test case too.

yes, data are random, I think that there will be something truncated is out of scope... :-)


Bot just went down

I was trying to make a tupper, but the bot just went down.
Any updates?

Tupperbox is being restarted for updates. Please join the support server and see #announcements for more information.

Thanks for letting me know.


Add bonds for structure type entries

In issue #426 I proposed adding more chemical properties to OPTIMADE structures. This PR implements my suggestion on representation of chemical connectivity between pairs of sites in OPTIMADE:
{
    "bonds": [ {"sites": [1, 2]} ]
}

I intentionally omit the bond types as this might be difficult to agree upon, whereas having just the connectivity is already beneficial.
Pinging people who have expressed their interest for comments: @eimrek @BobHanson @Austin243
Edit: I have introduced means to express connections with translation equivalents of the sites in sites.

Pinging @d-beltran for comments on how this proposal suits macromolecules.

Pinging @utf who participated in the discussions.

@eimrek suggested leaving translation vector only for one of the sites as at least one site will stay in the unit cell, or can be translated there. How about this:
{
    "sites": [63, 64],
    "translation_site": 1, // the second of the two sites is translated
    "translation_vector": [0, 0, 1]
}

The translation_site is required as any of the two sites could be translated, and the order of indexes has to be respected in sites. Or is it better to have a more structured way: "translation": { "site": 1, "vector": [0, 0, 1] }?

Workshop: We are happy to merge an explicit bond strucutre datastructure, but we must consider the exact format so the types of queries that one wants to do can be performed (with the present filter language, preferably). Inheriting the current CIF framework for this should be seriously considered.

@merkys I would leave at least the option to provide both of the translations. In the COD there are multiple non-polymeric molecules that spans several unit cells, so both translation vectors will be needed to correctly represent the complete molecule. I attach an example of such molecule to this comment (1540421.cif.txt, remove the txt extension before viewing), but @sauliusg could probably provide an even more extreme example (I seem to recall a molecule that spans 5 unit cells).

It is always possible to back-translate one of the sites into the primary unit cell without losing the connectivity information. Having both non-zero translation vectors is a matter of convenience, I think, or does this retain some more information?

Workshop: We are happy to merge an explicit bond strucutre datastructure, but we must consider the exact format so the types of queries that one wants to do can be performed (with the present filter language, preferably). Inheriting the current CIF framework for this should be seriously considered.

Unless we introduce some data redundancy here, the most powerful queries would be the ones based on correlated arrays (a.k.a. zips), as OPTIMADE does not support anything more intricate than that. To make bonds more friendly for zips, it should be defined as an array correlated with species_at_sites, possibly listing all neighbours of each site (full symmetric matrix). But again, species_at_sites is just an array of labels, thus one could not reliably query for, for example, structures where O atom has three bonds or more.

It is always possible to back-translate one of the sites into the primary unit cell without losing the connectivity information. Having both non-zero translation vectors is a matter of convenience, I think, or does this retain some more information?

Well, if you back-translate sites into the primary unit cell you lose some information and end up with a set of disjointed bonded fragments. You could, of course, translate these fragments from the primary unit cell back into their proper place, however, it is not ye obvious to me that this is a straightforward task. What is the drawback of allowing to specify both sites?


Tiny style improvement to Maxwell filter regularize kwarg

What do you mean specifically? I've been doing it this way for ... ever? 😅

@agramfort and I talked about this and I'm putting this PR on hold; docstrings for the entire function should be consistent.


JavaScript heap out of memory

We have a large project and when we try to run a esdoc compile on the directory we get a JavaScript heap out of memory error. I tried increasing the heap size for node using the command:
node --optimize_for_size --max_old_space_size=2000000 --max_executable_size=2000000 --gc_interval=10 /usr/local/lib/node_modules/esdoc/out/src/Plugin/Plugin.js
and
node --gc_global --optimize_for_size --max_old_space_size=4096 --always_compact  --max_executable_size=8192 --gc_interval=50 /usr/local/lib/node_modules/esdoc/out/src/Publisher/publish.js
The error is:
<--- Last few GCs --->
[37335:0x103003c00] 12058129 ms: Mark-sweep 1388.9 (1479.6) -> 1388.8 (1482.6) MB, 1734.7 / 0.0 ms  allocation failure GC in old space requested
[37335:0x103003c00] 12060057 ms: Mark-sweep 1388.8 (1482.6) -> 1388.8 (1442.6) MB, 1927.9 / 0.0 ms  last resort gc
[37335:0x103003c00] 12061921 ms: Mark-sweep 1388.8 (1442.6) -> 1388.8 (1438.6) MB, 1863.7 / 0.0 ms  last resort gc
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0x2c3e79bc0d39
1: fromString(aka fromString) [buffer.js:~194] [pc=0x20d9fa4819de](this=0x2c3e79b04311 ,string=0x3a018d5f9119 <Very long string[19853353]>,encoding=0x2c3e79bc9949 <String[4]: utf8>)
2: from [buffer.js:~96] [pc=0x20d9fa453d96](this=0xb33a51b1bc9 <JS Function Buffer (SharedFunctionInfo 0x2c3e79be2ee9)>,value=0x3a018d5f9119 <Very long string[19853353]>,encodingOrOffset=0x2c3e79b...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
1: node::Abort() [/usr/local/bin/node]
2: node::FatalException(v8::Isolate*, v8::Localv8::Value, v8::Localv8::Message) [/usr/local/bin/node]
3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
4: v8::internal::Factory::NewRawOneByteString(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
5: v8::internal::String::SlowFlatten(v8::internal::Handlev8::internal::ConsString, v8::internal::PretenureFlag) [/usr/local/bin/node]
6: v8::String::WriteUtf8(char*, int, int*, int) const [/usr/local/bin/node]
7: node::StringBytes::Write(v8::Isolate*, char*, unsigned long, v8::Localv8::Value, node::encoding, int*) [/usr/local/bin/node]
8: node::Buffer::New(v8::Isolate*, v8::Localv8::String, node::encoding) [/usr/local/bin/node]
9: node::Buffer::CreateFromString(v8::FunctionCallbackInfov8::Value const&) [/usr/local/bin/node]
10: 0x20d9fa922c2f
@typhonrt provided a solution with his plugin where he was allowing an array of dirs to compile as a workaround but it doesn't look like it was accepted for the latest version.
we just upgraded to the latest version of esdoc and was wondering if there was or if you could provide a fix or workaround for large projects?

I confirm the same behavior on another large project

Same issue for large project

Same issue for large project. Any solution for this?

Same issue here


Support to add custom contributor

There are people who made contributions without a GitHub PR. So I hope to have a way to add contributors manually.

https://github.com/milvus-io/hero-bot/releases/tag/1.11 now support customUserConfig


llama3.1 (and other models) support

Hi,
Thank you for this fantastic repository. I am relatively new to AI and C, but I am quite interested in modifying this project to support newer models like Llama 3.1 and Mistral Nemo.
I have examined the differences between this project and the original llama2.c. Could you point me to any relevant materials, code samples, or documentation that might help me understand what changes are necessary?
Thank you very much for your assistance.
Best regards.

This llama2.c fork has llama 3.1 support:
https://github.com/trholding/llama2.c


Node: Rename RedisClient, RedisClusterClient to GlideClient, GlideClusterClient

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Please add changelog entry to breaking changes section


Inventories are improperly returning null when they should not be.

We went over this one a long time ago, Aidan. ;) Vanilla doesn't return nulls and you shouldn't either:
https://github.com/CoFH/Feedback/issues/339

Uh oh, I thought I changed all those. What machine was the Itemduct connected to?

Seems to be a logistical sorter:
https://gist.github.com/Brycey92/8796fe3139d2499b7f32

BTW, a good way to handle this is to just have a static ItemStack[] NO_SLOTS = new ItemStack {}; in your code somewhere and just refer to it whenever you need to.

I do exactly that, actually.
Tell them to update Mekanism, they're using v7 :)

Alright then :) Awesome. I'll shut it down.


No Directive annotation found on NgFileSelect

Actually, after adding a package to my project, I get an error:
No Directive annotation found on NgFileSelect

which appears in browser console and project does'n work.

Did you add UPLOAD_DIRECTIVES to your components directive array?

Yes, sure

Actually don't know about that error, try googling or see the demo.

Same problem, it appears for versions of angular >= beta8

Thanks for reporting guys, I will test this and fix ASAP.
On Monday, 14 March 2016, AndrewLosikhin<EMAIL_ADDRESS>wrote:

Same problem, it appears for versions of angular >= beta8
—
Reply to this email directly or view it on GitHub
https://github.com/jkuri/ng2-uploader/issues/16#issuecomment-196286330.

@AndrewLosikhin I have beta 6 version. Interesting remark - when I copied the package from node_packages to the project and injected it localy, I did not faced the issue.

Yes, that is how it should be included right now. Sorry for not documenting
this.
On Monday, 14 March 2016, SergeyMell<EMAIL_ADDRESS>wrote:

@AndrewLosikhin https://github.com/AndrewLosikhin I have beta 6
version. Interesting remark - when I copied the package from node_packages
to the project and injected it localy, I did not faced the issue.
—
Reply to this email directly or view it on GitHub
https://github.com/jkuri/ng2-uploader/issues/16#issuecomment-196522300.

The same problem on Anguar 2.0.0-rc2

Same problem here Angular 2.0.0-rc2. Any fix?

This should be resolved with the 0.5.7.

Im getting this same error on RC4

This could be an issue with not having the same versions for this module and your (RC4) version of an app. I currently use angular nightly builds for this component and I will update to RC5 when released.

Hi jkuri,
I am experiencing this problem. I am at lost.
I am using the RC4 version. Building with webpack for angular 2 universal.
On the client it is dropping this error:
Error: Uncaught (in promise): No Directive annotation found on NgFileSelect
I am suspecting on how webpack is bundling things. Is it possible?
The following link is the webpack.config file:
https://dl.dropboxusercontent.com/u/63904414/webpack.config.js
Is there any other possible cause for this error?
Thanks
Regards
Kevin Vella

Hi,
I've solved the issue by copying the module to the project, added index.ts for every ts file, declaring an export * statement.
This solved the issue of the No Directive annotation found on NgFileSelect, when running the app.
I suspect that before, it was not including the files in the bundle correctly.
If you have another solution, can you please suggest it :)
Thanks
Regards
Kevin Vella

Hi Kevin, can you submit a PR with index.ts and exported * for the component, I will merge it.

Hope you fix it soon, same error on RC4. That's a nice project.
Some other things I noticed on package.json:

change angular 2 version to match the current version (rc4)
remove es6-shim and es6-promise and add core-js instead (look angular2 quickstart package.json).

HI,
Created a pull request to integrate the index.ts for the necessary files.

I am still getting this error. Is there anything wrong i'm doing or someone else is still getting this error?

How do you import module into your app? can you share you code sample?

Hi, I have the same error.
I try to setup "Basic exemple of upload with ng2-uploader" from the documentation.
I import the directives :
import {UPLOAD_DIRECTIVES} from 'ng2-uploader/ng2-uploader';
and i add it into my component as a directive:
directives: [UPLOAD_DIRECTIVES]
I use System JS with this config:
var map = {
    'app':                        'dist', // 'app',
    '@angular':                   'node_modules/@angular',
    'angular2-in-memory-web-api': 'node_modules/angular2-in-memory-web-api',
    'rxjs':                       'node_modules/rxjs',
    ...
    'ng2-uploader':               'node_modules/ng2-uploader'
  };

var packages = {
    'app':                        { main: 'main.js',  defaultExtension: 'js' },
    'rxjs':                       { defaultExtension: 'js' },
    'angular2-in-memory-web-api': { main: 'index.js', defaultExtension: 'js' },
    ...
    'ng2-uploader':               { defaultExtension: 'js' }
  };

And my error is : Template parse errors:
Can't bind to 'ng-file-select' since it isn't a known native property
Anybody has an idea about what is the problem ?

i am importing the module this way.
import {UPLOAD_DIRECTIVES} from 'ng2-uploader';
import {PROGRESSBAR_DIRECTIVES, BS_VIEW_PROVIDERS } from 'ng2-bootstrap/ng2-bootstrap';

I'm also declaring directives.
 directives: [PROGRESSBAR_DIRECTIVES, UPLOAD_DIRECTIVES]

@lacroixdavid1 please check https://github.com/jkuri/ng2-uploader/issues/55#issuecomment-238026400 where I posted example with SystemJS configuration.

Hi, thank you for the help, but I'm going crazy.
My application still does not recognize the Directive, while the example code works fine.
Here's what I've done now:
system.config.js
var map = {
   ...
    'ng2-uploader':               'node_modules/ng2-uploader',
  };

  var packages = {
     ...
    'ng2-uploader':               { main: 'ng2-uploader.js', defaultExtension: 'js' },
  };

my component
import { UPLOAD_DIRECTIVES } from 'ng2-uploader';

directives: [UPLOAD_DIRECTIVES]

It still does not work. The error is in my opinion a compilation problem. Let me explain:
Code exemple of ng2-uploader.js (into node_modules/ng2-uploader)
"use strict";
function __export(m) {
    for (var p in m) if (!exports.hasOwnProperty(p)) exports[p] = m[p];
}
var ng2_uploader_1 = require('./src/services/ng2-uploader');
var ng_file_select_1 = require('./src/directives/ng-file-select');
var ng_file_drop_1 = require('./src/directives/ng-file-drop');
__export(require('./src/services/ng2-uploader'));
__export(require('./src/directives/ng-file-select'));
__export(require('./src/directives/ng-file-drop'));
Object.defineProperty(exports, "__esModule", { value: true });
exports.default = {
    directives: [ng_file_select_1.NgFileSelect, ng_file_drop_1.NgFileDrop],
    providers: [ng2_uploader_1.Ng2Uploader]
};
exports.UPLOAD_DIRECTIVES = [ng_file_select_1.NgFileSelect, ng_file_drop_1.NgFileDrop];
//# sourceMappingURL=ng2-uploader.js.map

My app code of ng2-uploader.js (into node_modules/ng2-uploader)
import { Ng2Uploader } from './src/services/ng2-uploader';
import { NgFileSelect } from './src/directives/ng-file-select';
import { NgFileDrop } from './src/directives/ng-file-drop';
export * from './src/services/ng2-uploader';
export * from './src/directives/ng-file-select';
export * from './src/directives/ng-file-drop';
export default {
    directives: [NgFileSelect, NgFileDrop],
    providers: [Ng2Uploader]
};
export var UPLOAD_DIRECTIVES = [NgFileSelect, NgFileDrop];
//# sourceMappingURL=/Users/jan/Dev/github/ng2-uploader/ng2-uploader.js.map

It seems that typescript has not properly compiled library files. Here's my tsconfig.json:
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "removeComments": false,
    "noImplicitAny": false,
    "outDir": "dist/"
  }
}

I do not see the problem. Anyone has had this error? thank you for any help :)

it's all working in 5.0.13

Still the same error - rc4


Update Container DI to able unbind resolved entry

Useful to mock entry on tests

Could you please add some test cases to check it?


Create new sample to demonstrate BAM deployment and clean up Advanced sample

Create new sample to demonstrate BAM deployment and clean up Advanced sample.
This work item was migrated from CodePlex
CodePlex work item ID: '8580'
Assigned to: 'tfabraham'
Vote count: '0'

[UnknownUser@8/9/2011]
Associated with changeset 61290.

[UnknownUser@8/22/2011]
Associated with changeset 61632.

[UnknownUser@8/23/2011]
Associated with changeset 61683.

[UnknownUser@9/13/2011]

[UnknownUser@9/13/2011]
Associated with changeset 62236.

[UnknownUser@9/15/2011]
Resolved with changeset 62276.

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]


How to exit fullscreen by pressing phone's back key.

使用chewie插件，发现视频全屏播放状态下，按手机返回键不是退出全屏，而是返回上一个页面。如何设置，全屏播放状态下，按手机返回键退出全屏而不是返回上一个页面。
(google translate)
Use chewie plug-in and find that when the video is playing in full screen, pressing the mobile phone's return key does not exit the full screen, but returns to the previous page. How to set, in full-screen playback state, press the phone's back key to exit full screen instead of returning to the previous page.

Please add a full example where you see this problem.

使用chewie插件，发现视频全屏播放状态下，按手机返回键不是退出全屏，而是返回上一个页面。如何设置，全屏播放状态下，按手机返回键退出全屏而不是返回上一个页面。
(google translate)
Use chewie plug-in and find that when the video is playing in full screen, pressing the mobile phone's return key does not exit the full screen, but returns to the previous page. How to set, in full-screen playback state, press the phone's back key to exit full screen instead of returning to the previous page.

Very good issue here! 👏🏻 I encountered the same. I'll have a look into the code and try to add WillPopScope

I've set autoPlay to true and fullScreenByDefault to true, first press on Back button exits full screen but immediately goes back to full screen, second press exits full screen and the third button exits the screen

@Ahmadre  Any updates..?
Not only this issue, I just tried to put WillPopScope on the Scaffold where the grand children has Chewie.

When the player isn't playing, it works normal but when the Chewie is playing a video, it rebuilds itself and pauses the video from playing.


FIX: Job gets queued to the same queue.

The queue of the job was getting overridden by the Scheduler queue. The queue of the job should remain the same.

Could you please attach a testcase for this fix?

I have edited the _create_job in addition because scheduler queue was overriding the queue_name parameter before. I have added tests for each cases.

@selwin Can we get this merged? This would be incredibly helpful.

Thanks!


chore: update npmignore

Warnings

:warning:
:pencil: Please include a description of your PR changes.

:warning:

:man_technologist: Please assign someone to review this PR.

:warning:
:thinking: Well, it seems like that there are no tests in this PR. Please think about the test coverage of the added functionality and feel free to ask for help if you need it.

Messages

:book:
:+1: This PR will not affect the semantic version of the project. Remember: Refactoring is always a good idea. :pray:

:book:
:tada: This PR changed 2 lines of code in the project.

:wave: Hello demirtasdurmus and thank you for your contribution!

Before the reviewers could start with a code review process, please ensure that all the following points in your pull request (PR) are fulfilled:

Each variable and function inside component or service should contain a short code description (JSDoc-TSDoc)
In our Typescript applications we always try to avoid the type any and define new types or interfaces therefore
For the names of classes, functions or variables we use camelCase style (capitalized style for classes)
Code documentation for functions, classes, interfaces etc. should be written in capitalized style

  Generated by :no_entry_sign: dangerJS against 408f1eeddf85192e72abae8adefa0e15ab545d33

:tada: This PR is included in version 3.2.0-dev.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Lambda provisioned concurrency support

We'd like to update the default AWS provider to support provisioned concurrency configuration in stack files. This will enable further mitigation of cold start latency during changes in load to handlers deployed to Lambda.

Implemented as part of: https://github.com/nitrictech/nitric/pull/404

Available in latest dev version of nitric providers.


Migrate readme yaml

what

Add README.yaml

why

Standardize README

Add related project: https://github.com/cloudposse/github-status-updater


The connection is closed, you can't use it anymore! (AMQP::ConnectionClosedError)

Hi,
we've run into a weird error that, when the default gateway goes away for a short time, some of the sensu-clients are dying in an AMQP exception and although the sensu-client keeps running, it will no longer re-connect to AMQP.
{"timestamp":"2015-07-10T10:11:16.385175+0000","level":"error","message":"[amqp] Detected missing server heartbeats"}
{"timestamp":"2015-07-10T10:11:16.385368+0000","level":"warn","message":"reconnecting to transport"}
/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/session.rb:738:in `send_frame': The connection is closed, you can't use it anymore! (AMQP::ConnectionClosedError)
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/consumer.rb:117:in `block (2 levels) in cancel'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/queue.rb:267:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/queue.rb:267:in `block in once_declared'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/em/deferrable.rb:48:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/em/deferrable.rb:48:in `callback'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/queue.rb:264:in `once_declared'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/consumer.rb:116:in `block in cancel'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/channel.rb:936:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/channel.rb:936:in `block in once_open'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/em/deferrable.rb:48:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/em/deferrable.rb:48:in `callback'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/channel.rb:933:in `once_open'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/consumer.rb:115:in `cancel'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/queue.rb:831:in `block (2 levels) in unsubscribe'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/queue.rb:1389:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/queue.rb:1389:in `once_name_is_available'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/queue.rb:829:in `block in unsubscribe'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/channel.rb:936:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/channel.rb:936:in `block in once_open'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/em/deferrable.rb:48:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/em/deferrable.rb:48:in `callback'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/channel.rb:933:in `once_open'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/queue.rb:828:in `unsubscribe'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-3.0.0/lib/sensu/transport/rabbitmq.rb:60:in `block in unsubscribe'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-3.0.0/lib/sensu/transport/rabbitmq.rb:58:in `each'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-3.0.0/lib/sensu/transport/rabbitmq.rb:58:in `unsubscribe'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.19.1/lib/sensu/client/process.rb:431:in `pause'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.19.1/lib/sensu/daemon.rb:199:in `block in setup_transport'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-3.0.0/lib/sensu/transport/rabbitmq.rb:20:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-3.0.0/lib/sensu/transport/rabbitmq.rb:20:in `reconnect'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-3.0.0/lib/sensu/transport/rabbitmq.rb:114:in `block in reconnect_callback'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/callbacks.rb:51:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/callbacks.rb:51:in `block in exec_callback_yielding_self'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/callbacks.rb:51:in `each'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/callbacks.rb:51:in `exec_callback_yielding_self'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/session.rb:874:in `run_skipped_heartbeats_callbacks'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/session.rb:707:in `handle_skipped_heartbeats'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.5.0/lib/amqp/session.rb:981:in `send_heartbeat'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/em/timers.rb:56:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/em/timers.rb:56:in `fire'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run_machine'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.19.1/lib/sensu/client/process.rb:18:in `run'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.19.1/bin/sensu-client:10:in `<top (required)>'
from /opt/sensu/bin/sensu-client:23:in `load'
from /opt/sensu/bin/sensu-client:23:in `<main>'

The only way to get this back to work is to restart sensu-client manually on the host.
Would it be possible to catch this exception and reset sensu-client's state and re-establish a connection to AMQP ? Or something similar if this doesnt make much sense ?
Thanks
Alex

Hmmm, heartbeat failures should be handle gracefully. I'm concerned about Sensu's use of eventmachine-1.0.3, I will investigate the load order.

This sounds very similar to what were experiencing is there any update on this?

Looks like the heartbeat monitor/sender is still sending a frame after a connection has been closed, while Sensu is reconnecting to RabbitMQ. https://github.com/ruby-amqp/amqp/blob/master/lib/amqp/session.rb#L983
I once patched amq-protocol to address this issue: https://github.com/sensu/sensu-transport/commit/3a9da686d6b8ac380303db6395f1e539c568bd98
I will patch sensu-transport to fix amqp heartbeats while reconnecting and submit a PR to ruby-aqmp/amqp.

Cool, when do you think this patch to sensu-transport will make it to sensu-clients?

Open PR https://github.com/sensu/sensu-transport/pull/15

@ryancurrah there are a few other outstanding issues that are going to lead to a release today or tomorrow.

Awesome thanks for quick responses, I look forward to testing the client. I will also post my results here to for anyone else that it is interested.

Thanks @portertech !


chore: add boilerplate around unimplemented black box functions

This PR adds all the boilerplate around reading from / writing to the witness map and defines an interface for the black box functions which need to be implemented.

Superceded by #26


Make label clickable

Ho to use TouchDelegateGroup to make the labels clickable ?

Just add onClickListener to your action buttons. The labels will automatically delegate clicks on them to button.
Reopen this issue if this doesn't work.


Can we develop odata service with Dapper instead of using Entity Framework?

Hi, I have started reading OData today. Could you please help me in clarifying my doubt if we can use Dapper to develop OData service.

Yes, you may use Entity Framework to develop OData services if you are on .NET. Here are some examples:

http://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/odata-v4/create-an-odata-v4-endpoint
http://odata.github.io/RESTier/#01-02-Bootstrap

Hi Dingeins,
Thanks for the swift response. Could you please provide me some examples to develop OData Services with Dapper

I'm afraid I'm not familiar with Dapper. But generally speaking, the OData service stacks (e.g. the Web API for OData) doesn't assume any storage or ORM. It'd surprise me if you can't use Dapper with them.

Thanks Dingeins. I have created a sample OData service using Dapper.Thanks for your valuable inputs once again.

@maheshreeram : do you have any public repository from where I can see how you have integrated dapper and OData?

Yeh I was just thinking that ...
This question feels far from answered IMO, it's routed around the complexity of queries that can be generated from OData query strings.
the net result is that dapper needs decent LINQ to DB integration to work in the same way.
It's non trivial IMO and Dapper whilst offering some decent tooling for "single set based questions with mapping" it gets interesting when you start using complex functions like includes or grouping  ... or when you want to take advantage of cross set referencing between your OData model sets.
This blog post i just dug up talks about the approach in some detail ...
https://jtabuloc.wordpress.com/2018/06/12/migration-from-entity-framework-to-dapper/
... it would be really cool if OData could be put in to "flat set mode" or something to allow the joining of includes / sub queries in the API layer instead of the DB model that way the OData framework could be doing simpler "SELECT * FROM TableX" queries with Dapper doing the object mapping and then OData doing the stitching before a final result Serialize.
This would mean that the ORM doesn't need to be half as "smart".


Can support cum return in percent for stock/future?

Thank you for this good utility.
I noticed that the prices are converted to cumulative returns by
cumr = np.log(prices / prices[0]) * 1e4
I think it is used for forex( bps )
Can it support cumulative return in percent for stock/future?
Thanks.

Sure, could be made as a parameter to the code.  Let me find the locations and adjust

assuming you were referring to the AmplitudeBasedLabeler, I adjusted the label function to take an optional scale parameter as in:
labeler.label (prices, scale = 1e2)

This will then use a return-based scale (x 100).  You may need to adjust other parameters such as minamp appropriately.   For equities intra-day I use basis points.  If you are evaluating on daily returns then understand why bps might be unattractive.


Invalid Entry content_type_uid

This line always sets content_type_uid as literal 'uid':
https://github.com/contentstack/contentstack-management-javascript/blob/3850278886114011665c3c2d5d5ef9044959853e/lib/stack/contentType/entry/index.js#L274
Because of that it's not possible to use this library functions: entry.update(), entry.publish() and so on, because they have invalid urlPath.

Thanks for raising issue @MBO, We will work on the issue and update here once we are done with the changes.


Update changelog

Purpose

$subject

Examples
N/A
Checklist

[ ] ~Linked to an issue~
[ ] ~Updated the specification~
[ ] ~Updated the changelog~
[ ] ~Added tests~
[ ] ~Checked native-image compatibility~

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Ayesh Almeida seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


ACA-Py Admin endpoint for revoking a credential

The initial implementation of the revocation in ACA-Py is that the to revoke a credential, the controller invokes this endpoint:  /issue-credential/records/{cred_ex_id}/revoke.  Given the credential exchange ID, the necessary data to revoke a credential (the rev_reg_id and the cred_revoc_id) can be collected and the revocation executed.
However, in "normal" operation of an ACA-Py wallet, the credential exchange record is deleted upon completion of the protocol execution (there is a start option to change that behaviour). In any high volume issuer, deleting the exchange records will almost certainly be the case.  As such, getting the data elements for the revocation should by default assume to come from the controller, saved off by the controller at the time the credential was issued.
Please create a new endpoint that takes from the controller the rev_reg_id and cred_revoc_id for the specific credential to be revoked.  Presumably, it would be just POST issue-credential/records/revoke (perhaps without records?) with a data structure passed with the necessary fields for revocation.
I would think that unless the app is started with the option to keep credential exchange records (--preserve-exchange-records), the existing option should not be available. The new option should be available in either case.

I can take this on later this week

@sklump, @andrewwhitehead  - the other objects on the ledger (DIDs, schema, cred def) have an ACA-Py admin endpoint that is "list the  entities created on put on the ledger" that takes no arguments and returns a full list.  Should there be an endpoint like that for Revocation Regs?  I'm not sure there should, I was just noticing that when playing with the OpenAPI. It's easy to just get a CredDefId and use the endpoint for the list of RevRegs by CredDef.
What do you think?

I can write this up and submit it for review and we can decide then.

https://github.com/hyperledger/aries-cloudagent-python/pull/461 provides. I think it's a good addition: the search can specify states too, in case an operator needs to audit full rev regs, canvass active rev regs etc.


[Question] Tutorial and other modules documentation

Looking at the tutorials, I see they are not generated when I do cargo doc  --open. I know I could use pandoc on any of them, but I am looking for "the official way" to see all the docs.
Also, checking out the docs of other packages that Cursive uses, even if I generate all (cargo doc --all) don't show up in the docs that I get to browse when doing cargo doc --open. All I get to see is the Cursive documentation. I can open package docs one by one using cargo doc --open -p <package-name>. Is there an overview of package docs (including Cursive) or this just not possible?
So in summary my questions are:

How to show the tutorials? Or do I do that with pandoc manually?
How to show the other package docs?

P.S. I did find there is still an issue on cargo doc (https://github.com/rust-lang/cargo/issues/739) but hasn't been worked on since 2017 so I am not sure how much of that is implemented.

Hi!
I don't have any specific method of showing the tutorials - you can read them on github as it has a nice markdown viewer, or read them as text files (markdown is mostly readable).
Some projects use dummy modules to hold tutorials; that'd be an option too.
Regarding documentation for other packages, do you mean other crates? It should be in the left sidebar:

I just learned about [package.metadata.docs.rs] in Cargo.toml, which would let us have a tutorial feature turned on for docs.rs, but usually turned off.

Your screenprint shows crates, which my page does not. Do you call this with cargo doc --open? If so, then I don't know why I don't see the crates.

I just learned about [package.metadata.docs.rs] in Cargo.toml, which would let us have a tutorial feature turned on for docs.rs, but usually turned off.

That is hopeful! So ...  a change for the Cargo.toml?

Your screenprint shows crates, which my page does not.

Hmm, that's weird. I just ran cargo doc --open as well. What's your cargo version? Do you have a ~/.cargo/config? Or a .cargo/config in the cursive repo?

My cargo version is cargo 1.34.0 (6789d8a0a 2019-04-01). Maybe I need to upgrade cargo somehow. I will check how to upgrade cargo.
I don't have a ~/.cargo/config, although I do have a ~/.cargo directory with a bin directory and a registry directory.

It might be a cargo bug then? You may want to open a ticket on https://github.com/rust-lang/cargo.

I did an update using rustup and got the same version of cargo as I had (1.34.0), so it might be a new feature of cargo. To be sure I will issue a question on github like you suggest.

As it turns out it was my bad: js was disabled. I have that as a precaution. Only certain js sites are enabled.


Question: Is it possible to do case-insensitive search

I would like to do case-insensitive search with startswith,endwith and Contains. Please let me know this is possible or not.

This is related to your SQL-server settings ?

I think, you should able house: title.Contains("string", StringComparison.OrdinalIgnoreCase);  if it works is a question of your linq adapter

@jogibear9988 This will not work for this library I think.

Sadly it doesn't work, the part "StringComparison" is treated as a property and you get an error saying, that the property or field 'StringComparison' exists in the currently used type.
However, you can use the string value of the enum, described in the Enum Type Support Section.
users.Where("GivenName.Contains(\"sa\", \"OrdinalIgnoreCase\")");
Works perfectly for me :-)

@rajeshmuraleedharan With #450, StringComparison is now supported, so the following should work:
users.Where("GivenName.Contains(\"sa\", StringComparison.OrdinalIgnoreCase)");

@wilari932 How would you write a case-insensitive search using standard expression trees? If this would work:
var cols1 = cols.Values?.ToString().Trim();
Query = Query.Where(x => x.Contains(cols1, StringComparison.OrdinalIgnoreCase));

then the following should also work:
var cols1 = cols.Values?.ToString().Trim();
Query = Query.Where("Contains(@0, StringComparison.OrdinalIgnoreCase)", cols1);

users.Where("GivenName.Contains("sa", StringComparison.OrdinalIgnoreCase)");

Still does not work for me in 1.2.6

@khmurach How are you escaping the quotation marks?

@khmurach How are you escaping the quotation marks? Also, is this being run against a database or other Queryable provider?

Yes

@khmurach So the case-sensitivity may very well be determined by the database/provider.
What happens if you write a compiler-generated expression tree:
var lst = users.Where(user => user.GivenName.Contains("sa", StringComparison.OrdinalIgnoreCase").ToList();

@khmurach It works for me:

Which framework are you targeting?

@zspitz I have generic method so there is no properties to use in standard Where(x=>x.Name.Contains("value")).
IQueryable<T> ApplyFilter(IQueryable<T> dataAll, object filter)
This line works fine:
dataQueryable = dataQueryable.Where("{0}.ToLower().Contains(@0)".FormatWith(item.Key), item.Value.ToString().ToLower());
But I would like to get rid of ToLower()

@khmurach This works for me:
var lst = new List<User>();
var qry = lst.AsQueryable().Where("GivenName.Contains(\"sa\", StringComparison.OrdinalIgnoreCase)");

public class User {
    public string? GivenName { get; set; }
}

Visualizing qry.Expression:

Which framework are you targeting?

targetFramework="net451"

@khmurach It seems that .NET Framework 4.5.1 doesn't support this overload of Contains:

How would you do this with a strongly-typed query?
N.B. The filter you are passing into ApplyFilter could also be generic:
IQueryable<T> ApplyFilter(IQueryable<T> dataAll, Func<T, bool> filter) {

}

and then you would have strong-typing on the filter itself. Although I don't quite see what it gives you over the standard .Where.

Even in this simplified example, first two queries works fine but the last one throws error:
var items = new List<ListItem>() { new ListItem { Title = "John" }, new ListItem { Title = "Adam" }, new ListItem { Title = "john" } };
// works fine
var result1 = items.AsQueryable().Where("Title.ToLower().Contains(\"jo\")").ToList();
// works fine
var result2 = items.AsQueryable().Where(x => x.Title.Contains("jo", StringComparison.OrdinalIgnoreCase)).ToList();
// throws exception
var result3 = items.AsQueryable().Where("Title.Contains(\"jo\", StringComparison.OrdinalIgnoreCase)").ToList();

I'm using
object filter
in
IQueryable<T> ApplyFilter(IQueryable<T> dataAll, object filter)
to be able to use any object (projection) as a filter and to use reflection to scan props and values and apply them as a filter to List:
var usersCache = _repository.GetAll<User>();
var filter1 = new User{ FirstName = "jo", LastName = "wes" };
var filter2 = new UserQuery{ Name = "jo" };
var result1 = ApplyFilter(usersCache, filter1);
var result2 = ApplyFilter(usersCache, filter2);

Any updates on how to do an case invariant search?

Closing..


Please correct grammar

Please correct the basic subject-verb agreement (English grammar 101) as shown in the following two sentences on this page:
"Backups of TLS enabled Azure Database for MySQL are not supported. If a backup is configured, you will get failed backups."
And...
"Backups of TLS enabled Azure Database for PostgreSQL are not supported. If a backup is configured, you will get failed backups."
Wording of the second sentences could be better, for example: "If you attempt a backup with this database, it will fail."
And later on the page: "If you make manually settings.." would read better if reworded to "If you manually make settings..."
One of the top issues with Azure, especially compared to AWS, is the quality of Azure's documentation. Issues like basic English grammar and syntax should have been fixed long ago.

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

ID: 4754bcfc-204a-d398-6b86-e452cd0d44a1
Version Independent ID: 157885c4-2579-8f98-1e85-c3063a861207
Content: Back up an app - Azure App Service
Content Source: articles/app-service/manage-backup.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@yobyot Thanks for the feedback! We are currently investigating and will update you shortly.

Appreciate the feedback @yobyot. I have a PR that addresses the grammatical concerns. I will note that Azure Database for MySQL and Azure Database for Postgres are singular product offerings which is why is is used rather than are.


Trying to create a function that adds media queries. Need some help

I thought about going to stackoverflow but I need an advice rather then answer to question.
As the title says, I'm trying to create a small function that adds media query string depending on devices.
import { css } from 'styled-components'

const deviceList = {
  mobile: `(min-width: 0px) and (max-width: 743px)`,
  foldable: `(min-width: 481px) and (max-width: 743px)`,
  tablet: `(min-width: 744px) and (max-width: 1199px)`,
  desktopSmall: `(min-width: 1200px) and (max-width: 1399px)`,
  desktopLarge: `(min-width: 1400px)`
}

// @Issue: can't access 'theme' props inside mediaQuery at the current implementation
const template =
  (device: keyof typeof deviceList) => (styles: Parameters<typeof css>[0]) => {
    return `@media ${deviceList[device]} {
      ${css(styles)}
      }`
  }

const device =
  (...devices: (keyof typeof deviceList)[]) =>
  (styles: Parameters<typeof css>[0]) =>
    devices.map(device => template(device)(styles)).join('')

export type Media = {
  [key in keyof typeof deviceList]: ReturnType<typeof template>
}

export const mediaQuery = {
  mobile: template('mobile'),
  foldable: template('foldable'),
  tablet: template('tablet'),
  desktopSmall: template('desktopSmall'),
  desktopLarge: template('desktopLarge'),
  desktop: device('desktopSmall', 'desktopLarge'),
  device
}

So far so good but the problem is that I can't access 'theme' props inside above function.
The usage is as follow.
const Box = styled.div`
  background-color: red;

  ${media.desktop`
      background-color: blue;
  `}
`

This one works but
const Box = styled.div`
  background-color: red;

  ${media.desktop`
      background-color: ${({ theme }) => theme.colors.black};
  `}
`

This one does not. I'm not sure where to look for nor where I got wrong.

For those of you who are seeking for similar solution:
https://tyhopp.com/notes/styled-components-media-queries


General - Publication upload image buttons do nothing

Welcome to Ghost's GitHub repo! 👋🎉
Do you need help or have a question? Please come chat in Slack: https://ghost.org/slack 👫. Found a bug? Please fill out the sections below... thank you 👍
If your issue is with Ghost CLI, please report it on the CLI repo ➡ https://github.com/TryGhost/Ghost-CLI/issues/new.
Issue Summary
Install new version of Ghost and using chrome or safari the publication image upload buttons do nothing.
Steps to Reproduce

Installed new version of Ghost & uploaded previous posts from over version.
Visit General settings
Publication identity - try using image upload button

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
Technical details:

Ghost Version:  1.3.0
Node Version: v6.10.3
Browser/OS: Safari & Chrome on OSX High Sierra
Database: MySQL

Duplicate of #9292


checkbox can't initial correctly.

main.html
{{#each posts}}

  <input name="c1box" type="checkbox">

{{/each}}

main.coffee
Template.main.events
  "click .checkbox":->
# this is the temp solution, for more 1 click first.
      $('.checkbox').checkbox()

Template.main.rendered = () ->
# this line is no effect,the checkboxes are still disabled before more 1 click first to active checkbox...
  $('.checkbox').checkbox()

How to next?

It looks like your Coffeescript is returning the object $('.checkbox').checkbox() and it shouldn't do that. I don't use coffeescript but the Js2.coffee translator says you should be putting a return statement at the end:
Template.main.rendered = () ->
  $('.checkbox').checkbox()
  return

Hello @carrot93,
I think the problem is a bit more general...
Everytime you have an {{#if}} or {{#each}} of whatever conditional, the HTML elements included therein are not granted to be already in place whn you get the rendered callback triggered.
This is especially true for an if clause which could change reactively during the life of the enclosing template...
The solution is to have something like this:
<template name='posts'>
{{#each posts}}
  {{> post}}
{{/each}}
</template>

<template name='post'>

    <input name="c1box" type="checkbox">

</template>

and then
Template.post.onRendered(function(){
  this.$('.checkbox').checkbox()
});

this should be a general way to use any front-end framework which need elements initialization through JS code.
See also this previous comment

I think this should be written in the README.md.
Feel free to create a PR to add a section about this.
CC @flemay

@splendido is right. deleting my earlier comment!


Always set an internal ip address to OpenStack VMs

in order for all benchmarks to function.
(e.g. Cloudsuite Data Caching)

Signed CLA.


Environment Variable Support

Add support for the following flags:

--kube-context: set what kube-context should be passed down to helm
charts --values: add additional value files to the existing list of value files (for use when using overrides for different environments during CI)
in the Charts.yml file added a new property env for environment vars. It's exactly the same as the set property but all the value fields are run through os.Getenv to resolve their values. Needed this for using secrets in our CI system.

Note: this is my first time working with Go so any and all feedback welcome!

@roboll ready for another look

Perfect. Merging this, thanks again. Closes #1.


typo: Double word "which"

OPS Build status updates of commit 3ade808:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/office-365-management-activity-api-schema.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add volume support for better user experience

For a better user experience and freeing users from configuring too many technical details, we should add volume support in this operator to allow the scheduler plugins to be created with necessary volumes.

This could be done a couple of ways, but I think the most operator-oriented way that we discussed would be to have a field in the CRD to specify a list of volumes and the paths they should be mounted to in the scheduler deployment.
ie,
spec:
  ...
  volumes:
    - name: xyz
      hostPath: /local/dir
      mountPath: /dir/foo

which would be translated in the deployment to
spec:
  containers:
  ...
    volumeMounts:
    - name: xyz
      mountPath: /dir/foo
  volumes:
  - name: xyz
    hostPath:
      path: /local/dir

the question is how many different kinds of volume mounts do we support? Just hostpath and PVCs is reasonable enough, but that also requires some way to tell the operator to differentiate between them.
@swatisehgal could you include more specific details about the use case for volume mounts?

The way you have it in the example above with hostpath satisfies our use case perfectly.  In case of hostpath we would need an additional field hostPathType to specify the type as has been detailed here. I agree that it makes sense to handle PVC in addition to hostpath. My suggestion would be have a type field to indicate whether it is PVC or hostPath. Also, I propose that instead of having a hostPath field we could have a generic field source (or a descriptive) field which in case of hostPath volumes would be used to specify the path of the file/directory and in case of PVC would be used to specify the claimName. Having said that, if you think that is confusing we can have two separate fields hostPath and claimName. Here is how the CRD spec could look like in both these cases:
spec:
  ...
  volumes:
    - name: xyz
      type: hostPath
      source: /local/dir
      hostPathType: Directory # valid values of this field would be Directory/File/FileOrCreate/DirectoryOrCreate/Socket/CharDevice/BlockDevice
      mountPath: /dir/foo

In case of PVCs, it would look like this:
spec:
  ...
  volumes:
    - name: xyz
      type: pvc
      source: <claimName>
      mountPath: /dir/foo

We should make sure we consider access modes here too. I think we don't need them as HostPath is only mounted as readOnly and in PVC the access modes are specified in the PersistentVolumeClaim definition but lets be 100% sure.

Had an offline discussion with @damemi and we agreed that because the primary motivation of this change is to be able to mount in kubeconfig and given that there are better alternatives:

using incluster config
recent changes surfacing kubeconfig in scheduler framework handle

it is best to close this and revisit later when the demand arises.
/close

Thanks for updating, @swatisehgal
For posterity I'm just going to link the relevant scheduler-plugins issues as well: https://github.com/kubernetes-sigs/scheduler-plugins/issues/98 and https://github.com/kubernetes-sigs/scheduler-plugins/pull/287


Timers: Improve tracking

This PR aims to move away from using chatMessage events and instead rely on vars.
Includes improvements for

Charge spell for God spells
Teleblock
Bladed God staves

Removed the need to keep track of widgets/other indicators for recognizing PvP zones for teleblock purposes; The varbit associated with teleblock does this.
Added support for Staff of Balance as it too has the same protective effect.
Fix bug associated with bladed God staves; re-equipping after unequipping a bladed God staff within the effect duration should re-introduce timer as the protective effect hasn't absolutely waned but is made invalid in absence of the weapon.
I could be mistaken on the clearing of effects on death in GameTimer.

I've pushed f647188612eb925c0188172b01e76eaedcf9a5af and 461f8471d68cf653fae9e9efb3d32b7dc5e474a7 for charge spell and teleblock duration tracking since those are done fully. I'd like to do that infobox image API work prior to implementing the sotd (and variants) change. If I don't get around to that, this commit should basically cover the proposed changes from this PR.

Note to self (or for any other devs who might implement this), the wiki is in fact correct, that unequipping a staff of the dead does not end the special attack's effect--it simply does not activate during that minute time unless a staff of the dead (or one of its variants) is equipped at the time of the received melee attack.


Development version3

ready for release

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

644 of 663 (97.13%)  changed or added relevant lines in 23 files are covered.
27 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-1.6%) to 92.816%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

repository/IngSoft2-Model/Board.class.st
49
50
98.0%

repository/IngSoft2-Model/SpeedUpEffect.class.st
5
8
62.5%

repository/IngSoft2-Model/LastPlayedCard.class.st
13
17
76.47%

repository/IngSoft2-Model/RedoCard.class.st
22
33
66.67%

Files with Coverage Reduction
New Missed Lines
%

repository/IngSoft2-Model/SpeedUpEffect.class.st
1
57.89%

repository/IngSoft2-Model/NoEffectBox.class.st
8
50.0%

repository/IngSoft2-Model/WormHoleEffect.class.st
8
60.0%

repository/IngSoft2-Model/Board.class.st
10
88.54%

Totals

Change from base Build<PHONE_NUMBER>:
-1.6%

Covered Lines:
801

Relevant Lines:
863

💛  - Coveralls


selectOnBlur is not implemented even though it is documented

Although the selectOnBlur prop is documented, applying a true value for it does nothing.
I checked the distributed node module and confirmed that selectOnBlur does not exist anywhere in the code.
Please implement this feature or remove it from the documentation.

Sorry, please disregard. I had an older version of the plugin installed. I had checked that code, when I should have checked here in the repo.


Add snowflake_table resource for creating and managing table objects

Add a resource to create and manage tables.  But I am curious how others are managing table objects without this resource available at this time.

@djzempsnowflake We've left TABLE (and VIEW) objects unmanaged so far in edX's Snowflake implementation, as they're relatively dynamic and changing. We manage DATABASE and SCHEMA using Terraform, along with USER, ROLE, permissions-granting, etc.

@djzempsnowflake
The snowflake_table_grant resource has recently had an on_future property added so you can use it to grant on all future tables in a schema. That's enough to manage permissions.
https://github.com/chanzuckerberg/terraform-provider-snowflake#snowflake_table_grant
My tables are created by various other processes, ELT tools, transformation tools like DBT and by analyst users. I have basic Roles that those tools use to make permissions straight forward.
Not possible to pre-define all the tables. There are a few I know up-front, e.g. some metadata tables that ETL tools use, but then I think creating those is the responsibility of those tools, so I don't see any use for a table resource.

I tend to agree that managing tables in terraform is not a great idea for most use cases.
However it would still be good for the provider to support tables. I think the goal of any terraform provider should be to fully wrap the underlying API (or in this case, wrap the API wrapped in a SQL driver).
So, on balance, +1 for this issue. I'll probably need it in about 12 months so if someone builds it before then that will make future me happy.

@sjauld what's the use-case out of curiosity?

I've got a use-case.
We Terraform the following resources:

AWS S3 bucket
AWS Firehose Delivery stream to the S3 bucket
Snowflake Stage for the prefix in the S3 bucket
Snowflake Pipe that COPY's from the stage into the table

Right now I have to manually create the table before I can Terraform anything, but would be neater to have the provider be able to do it.

same problem here

I've got a use-case.
We Terraform the following resources:
* AWS S3 bucket

* AWS Firehose Delivery stream to the S3 bucket

* Snowflake Stage for the prefix in the S3 bucket

* Snowflake Pipe that COPY's from the stage into the table

Right now I have to manually create the table before I can Terraform anything, but would be neater to have the provider be able to do it.

Same problem here

My use case is just about the same as above.  Really need this.

I haven't seen mentioned in the docs whether the table will be dropped when schema change or not?


[QUERY] ProcessingStoppedReason for DeveloperCodeException / EventHubsException

Library name and version
Azure.Messaging.EventHubs 5.7.0
Query/Question
Hi! Is there any reason why ProcessingStoppedReason is set to OwnershipLost when partition processing task was faulted due to exception thrown in user code (DeveloperCodeException) or because particular consumer group does not exists (EventHubsException)? I find it a little misleading. What about having another value (UnhandledProcessingError?) for that case?
I think it is caused by partitionProcessor.ProcessingTask.IsCompleted check.
Environment
No response

I confirmed that changing the reason would be considered a behavioral breaking change, despite it being fairly low risk.  I don't think there's enough value in the proposed change for me to justify driving a breaking change exception request across all languages.  The reason will need to remain "OwnershipLost" for now.
To help better detect the scenario where the event processing handler is not following guidance and exceptions are allowed to propagate, I added a new warning that will be surfaced to the processor error handler that describes the scenario and offers guidance for mitigation.  This should give better visibility to the scenario for applications that are not capturing/monitoring SDK logs.
I also fixed the oversight on validation at startup; the processor will now refuse to start if the consumer group is not valid.
I'm going to mark this as addressed; please feel free to unresolve if you'd like to discuss further.


Proposed: Spec written in markdown

In order for users to report comments to the spec just like the code, we could/should use markdown instead of word to write the specification in the future.
If someone could volunteer that'd be excellent.

This repository is now marked as "private" further discussions on IPSO Objects now are happening in OMA.


Feature/validate with soap

Fixes #4
Implements validators against the SOAP schema which give reasonably sensible errors (KeyError when a key is wrong, ValueError when a constraint is violated) so we can bake this into other parts of the library.

Pull Request Test Coverage Report for Build 55

60 of 68 (88.24%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.0%) to 89.634%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

earthchem/validation.py
60
68
88.24%

Totals

Change from base Build 50:
-1.0%

Covered Lines:
147

Relevant Lines:
164

💛  - Coveralls

Pull Request Test Coverage Report for Build 55

60 of 68 (88.24%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.0%) to 89.634%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

earthchem/validation.py
60
68
88.24%

Totals

Change from base Build 50:
-1.0%

Covered Lines:
147

Relevant Lines:
164

💛  - Coveralls


Meaning that when I click on the button, it opens a Menu, with selected MenuItems, and the same display  (open/close) logic as Selects depending on if it's multiple or not.
There is a lot of helpful logic inside the SelectInput component that handles the state of the Menu and its MenuItems, but I can't extract that functionality and replace the entire Input with a button.
It'd be really helpful if all the Select logic was available through a hook, or if the Select input supported being overriden with a simple button that takes an onClick handler.
Here's a reproduction I was able to create quickly, but a few things are missing, and it's not the simplest code out there:
https://codesandbox.io/s/youthful-galois-s82t2
Maybe this should only be documented, instead of supported?

Could you explain why you'd want to do this? What is currently missing from Select that you're trying to implement?

Well sometimes you want to use a Select as a form component, but you don't want the entire input displayed nor its label, etc.
It allows you to build very dense UIs where the only user interaction is the click of a button.
Maybe there is a simple way of doing this currently and I'm just overcomplicating things?

I don't think you want an actual Select? Not sure what there is left to display if you want to display the input or label? So far I don't see anything that's different to the current implementation.

Select manages the state of the MenuItems, depending on what you select.
I don't understand what is not clear to you, I adjusted my example to feature an IconButton. As you can see, when you click multiple options in this Select, it keeps them highlighted.

That's not really a select. A select needs a label and display the currently selected value.
I'm not sure what you're building or how you envision the UX for this component. Leaving this open for upvotes. If more people are looking for this we can think about building a new component. But it won't be built into the Select.

Alright, if you want we can call it something else, I'm not sure why you're insisting on defining what a select is, it doesn't change what I initially created this issue for.
So to be more accurate: I'm looking to build a component that displays a Menu when clicked on it, and that can manage the open state of the Menu, as well as the selected state of the MenuItems just like a SelectInput does, through the use of a value and an onChange prop.

@Floriferous Maybe something like this: https://material-ui.com/components/menus/#max-height-menus or https://material-ui.com/components/menus/#selected-menus

@KaRkY Yes that's the behavior I'm looking for, though I wish I didn't have to reimplement all of the logic for multiple selects, that comes with a SelectInput. I was looking for a simple way to make it use the exact same API as the Select component. So at minimum basically value, onChange and multiple.

It'd be really helpful if all the Select logic was available through a hook

@Floriferous Would something similar solve your issue https://downshift.netlify.app/use-select?

@oliviertassinari yep, that’s exactly it! Though I wish I didn’t have to bring in another library :)
Thanks for the link.

What feature do you miss from the Menu component?

To me, what would be helpful is the multiple select state management:

Handling of selected state on each of the MenuItems
Handling of the open state of the Menu

i.e. it should stay open after clicking on a MenuItem, and close when you click next to the Menu

Other

Handling of an "Empty" state for single selects

Don't get me wrong, you can just build this right now, but I feel like all of that code has already been written in SelectInput.

To be a bit more generic, I'd like to use Select as is, with all of its props, but simply change what the idle component is. As mentioned in the title of this issue, I just want to replace the Input with a Button.

I assume you have tried the renderInput prop, what was missing from it?

I have not tried using the Autocomplete component, only Select, so I don't know. I assume that would work.

I'm not talking about the Autocomplete, but the renderValue prop of the Select.

Ah sorry, you tricked me because you talked about renderInput in your initial comment ;)
renderValue will not allow me to replace the Input with a Button though, so I'm not sure how that would help me with what I'm trying to build.
I really just want the Input component completely gone, and only render a Button that opens the Menu on click.

Adding that none of the provided examples actually work. There is a warning in the console that no anchor element is defined.  This is important if you put the select anywhere except the top left of the screen.
See the below fork and look at what happens when you click the dropdown:
https://codesandbox.io/s/long-flower-i45un?file=/src/Demo.js
This issue is caused by making the  hidden

It is worth mentioning that the examples above don't work. If you move the component anywhere on the screen except the top left then the menu doesn't anchor correctly. You can see the warning in the console telling you that it is caused by the  Input being hidden.
This is reproduced below: https://codesandbox.io/s/long-flower-i45un?file=/src/Demo.js

@k290 Thanks for the reproduction, I have updated it a bit to get the desired outcome:
import React, { forwardRef } from "react";
import { Select, MenuItem, IconButton } from "@material-ui/core";
import AlarmIcon from "@material-ui/icons/Alarm";

const ButtonInput = forwardRef((props, ref) => {
  const {
    inputComponent: InputComponent,
    inputProps: { open, onOpen, onClose },
    value,
    onChange
  } = props;

  return (
    <IconButton
      onClick={(event) => {
        if (open) {
          onClose();
        } else {
          onOpen();
        }
      }}
      ref={ref}
    >
      <AlarmIcon />
      <InputComponent
        {...props.inputProps}
        value={value}
        onChange={onChange}
        renderValue={() => null}
        IconComponent={() => null}
        SelectDisplayProps={{
          style: { visibility: "hidden", minWidth: 0, height: 0, padding: 0 }
        }}
      />
    </IconButton>
  );
});

/**
 * how you used the components
 */
export default function Demo() {
  const [age, setAge] = React.useState([]);
  const [open, setOpen] = React.useState(false);

  const handleChange = (event) => {
    setAge(event.target.value);
  };

  const handleClose = () => {
    setOpen(false);
  };

  const handleOpen = () => {
    setOpen(true);
  };

  return (
    <>

      <Select
        labelId="demo-simple-select-label"
        id="demo-simple-select"
        value={age}
        onChange={handleChange}
        input={<ButtonInput />}
        open={open}
        onClose={handleClose}
        onOpen={handleOpen}
        multiple
      >
        <MenuItem value={10}>Ten</MenuItem>
        <MenuItem value={20}>Twenty</MenuItem>
        <MenuItem value={30}>Thirty</MenuItem>
      </Select>
    </>
  );
}

https://codesandbox.io/s/crazy-wu-2wp61?file=/src/Demo.js:0-1786
It sounds very much like we should expose a useSelect hook that developers could use to recreate their own Collapsible Dropdown Listbox.

Linking https://github.com/mui-org/material-ui/issues/27170 and https://github.com/mui-org/material-ui/issues/6218 as it might be related.


override_field_test/03 should be extended

TBF: we should check conflicts not only for methods, but for accessors too
This line was in the status file.  Changing to an issue, and putting the issue on the test status line:
override_field_test/03: Fail # Issue XXXXX
No comments or info should be in status files, only issue numbers on the same line as the test they apply to.

This can be closed, as there have been changes made to the status files and this may not be an issue anymore.