fix not able to cancel selected category while creating IOU

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/32872
PROPOSAL: https://github.com/Expensify/App/issues/32872#issuecomment-1851028394
Tests

Log in to the employee's account
Tap on the green plus button (FAB)
Select Request money
Select any currency and amount
Click next
Choose a group policy room
Click on "Show more"
In the category section, select any category
Navigate to the categories section again and click on the selected category marked with a green checkmark
Verify that selected category is cancelled

[ ] Verify that no errors appear in the JS console

Offline tests
Same as Tests
QA Steps
Same as Tests

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/97676131/aebc21cb-c6c7-42a5-a025-d0f0e2114585

Android: mWeb Chrome

https://github.com/Expensify/App/assets/97676131/2893ac55-43df-4c0d-8499-0797b58c8bc6

iOS: Native

https://github.com/Expensify/App/assets/97676131/3b0f4aa1-c4fc-438d-b9a5-8427e341cc31

iOS: mWeb Safari

https://github.com/Expensify/App/assets/97676131/716bda1d-231c-4ba7-b9ad-2a826ad6b5b0

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/97676131/1335477f-a852-4769-a96c-23876c9e6840

MacOS: Desktop

https://github.com/Expensify/App/assets/97676131/f3afafc7-ae63-4524-b352-a7c3564efebe

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/58412969/fd8cb5f0-4d5d-43e6-959c-1b03c277e71b

Android: mWeb Chrome
https://github.com/Expensify/App/assets/58412969/b02fdf7f-99b1-447c-8b58-738216e96f1e

iOS: Native
https://github.com/Expensify/App/assets/58412969/28d81fb7-5a5b-409d-84ed-301712fdaad4

iOS: mWeb Safari
https://github.com/Expensify/App/assets/58412969/b7820908-af3e-4871-90b4-9bf3bc630a47

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/58412969/5f7ed58c-5827-4a4f-8301-45688e87ffda

MacOS: Desktop
https://github.com/Expensify/App/assets/58412969/724916b0-9f5b-4eb3-94f5-d24268b976d7

@Julesssss we still need to CP this one

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

CP in progress

🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.11-25 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Crashes with pistons (1.11 client on 1.10.2 server)

What is the output link of /viaversion dump?
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
1.11 client connecting to ViaVersion 1.0.1 running on BungeeCord 1.11. Minecraft servers are at 1.10.2, no plugin that manipulates packets.
How does this error happen? login? Using an item?
Retract some piston constructions at certain locations.
To reproduce use worldedit to load and paste http://www.mediafire.com/file/bjedvdc9t5d8w5a/pistoncrasher.schematic at -456 100 10. Then use the lever to extend and retract the pistons.
(This also happens while pistons extend and push 3 block high reeds at those locations.)
Is there an error in the console? Use pastebin.com. Is there a kick message?
Client crash log:
http://pastebin.com/HaWPCWF0

I'll try to reproduce it tomorrow.

Experiencing same issue

This looks like the same issue, 1.11 clients crash connected to 1.8.8 server via bungeecord w/ viaversion 1.0.1
We were playing a modified version of SethBling/Cubehamster's Missile Wars (lots of pistons, seems very likely to experience a crash during a game. We had a crash 2/2 games)
https://pste.me/#/AngeW
https://pste.me/#/truKx
https://pste.me/#/crash-1-kiz
https://pste.me/#/crash-2-kiz
https://pste.me/#/kizs-is-smelly-mems-second-crash

bump same issue

As an update to this issue as I finally got a bit of free time today (which sadly I won't have much more free time for a week for so).
It's caused by Minecraft updating the piston to air then triggering the block action packet to extend the piston.
It seems the behaviour for pistons has changed slightly in 1.11 in relation to lots of pistons being pushed causes air updates which leads to this issue.
This is not in vanilla but how easy it is to properly fix is hard to say, i've tried a few solutions of forcing the piston block to be set and it seems not to fix it.
The only current workaround I have is disabling the push animation for pistons, which does work just not as satisfying. I'd be interested to know if you want this patch pushed or if you'd rather wait until we figure out the full fix. (The patch would only touch 1.11 clients)

anythings better than crashing

Pastebin link is dead, but if a new link is provided I can look at what's happening clientside, so if someone can repost it (possibly directly in the issue surrounded by ``` on both sides), that'd be helpful.

@Pokechu22 I believe https://github.com/MylesIsCool/ViaVersion/issues/595 has it

Ah, good.  That's the crash that I expected (even hoped) to see; it's a vanilla issue (not exclusive to ViaVersion): MC-110399.  It was fixed in shapshot 16w50a (and thus 1.11.2), so all that needs to be done is to figure out how it was fixed there.  I'll do that in a bit; I don't have full access to my data right now (should have access in a few hours, though).

OK, I did some research, and that issue doesn't have as much info about it as I thought.  There was a new block-36 NBT tag added in 1.11.2, but that doesn't seem related (given that 36's tile entity usually isn't ever sent).
However, I did identify some other changes in 1.11 to 1.11.2: the block action handler for the piston base switched from setting blocks with mode 2 (used in 1.11 and below, including 1.10.2) to using mode 3 in 1.11.2.  This happens when setting it to an extended piston base (from a retracted one), due to successful extension.  Note that block actions do occur server side, not just clientside.  Quoting from MCP:

Sets the block state at a given location. Flag 1 will cause a block update. Flag 2 will send the change to
clients (you almost always want this). Flag 4 prevents the block from being re-rendered, if this is a client
world. Flags can be added together.

I don't think that would directly effect it, but it's a line of investigation.
I also see that during piston movement, 1.11 uses setBlockToAir (which is equivilient to using mode 3).  1.11.2 uses a more complete set to air with mode 4 instead.  My guess is that those sets-to-air were received after the block action gets to the client, meaning the 36 block entity gets destroyed.  Maybe.  I'll need to test further.
There's a few other changes; I haven't digested them yet.

OK, still no clue as to what originally caused this; however, I will say that the workaround should probably only be enabled for 1.11.0, and disabled for 1.11.2; since that bug was supposedly fixed in 1.11.2, it shouldn't be needed there.

With the above workaround provided going to close this issue unless something comes up in the future.


Added fibonacci number using dp

🛠 Issue
Issue no #825

Issue no #
👨💻 Changes proposed
Added Fibonacci number program in c, cpp, python and Java using dynamic programming.

✔ Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

But the readme files were there so I mentioned there. Now I have to remove the Fibonacci mentions from the readme files. Okay


Use feature detection instead of version detection

Follows the Python porting best practice: https://docs.python.org/3/howto/pyporting.html#use-feature-detection-instead-of-version-detection
Before:
$ python3 -m flake8 ./spyder/py3compat.py --count --select=E901,E999,F821,F822,F823  --show-source --statistics
./spyder/py3compat.py:33:24: F821 undefined name 'unicode'
    TEXT_TYPES = (str, unicode)
                       ^
./spyder/py3compat.py:34:23: F821 undefined name 'long'
    INT_TYPES = (int, long)
                      ^
./spyder/py3compat.py:91:35: F821 undefined name 'unicode'
        return type(obj) in [str, unicode]
                                  ^
./spyder/py3compat.py:101:32: F821 undefined name 'basestring'
        return isinstance(obj, basestring)
                               ^
./spyder/py3compat.py:124:32: F821 undefined name 'unicode'
        return isinstance(obj, unicode)
                               ^
./spyder/py3compat.py:134:20: F821 undefined name 'unicode'
            return unicode(obj)
                   ^
./spyder/py3compat.py:136:20: F821 undefined name 'unicode'
            return unicode(obj, encoding)
                   ^
./spyder/py3compat.py:227:13: F821 undefined name 'raw_input'
    input = raw_input
            ^
./spyder/py3compat.py:229:11: F821 undefined name 'cmp'
    cmp = cmp
          ^
9     F821 undefined name 'unicode'
9

After:
$ python3 -m flake8 ./spyder/py3compat.py --count --select=E901,E999,F821,F822,F823  --show-source --statistics
0

Hello @cclauss! Thanks for submitting the PR.

In the file spyder/py3compat.py, following are the PEP8 issues :

Line 232:5: E301 expected 1 blank line, found 0

Thanks for your contribution, but this PR seems to have no clear purpose and just wants to fix some supposed porting problems in our side.
I'm not fond of this kind of work and, sorry to say it, I'm -1 on it.

Sorry, I don't want to deal with the potential problems that could arise from this, given that it doesn't fix a particular problem.
So, I'm closing this PR.


Stuck on "Loading, please wait..."

Was working fine last night, nothing has changed as far as I know. Loaded in new Google Maps Key, just to be sure. Login with Google, allow permissions, then it just hangs on "Loading, please wait..." which used to only last for 1-2 seconds at most. Anyone have any suggestions?

Update:
Uninstalled completely, removed all local files, rebooted, reinstalled, and used a different google account for map key and login... still same error.
Update 2:
I remoted in to a computer that's never had this program on it before. Installed from scratch using a virgin google account and map key. Got past "Loading, please wait..." but only to get a blank map with the status at the top displaying "Waiting"

I have the same problem

I had the same problem on Linux. It was fixed by installing python-dev and xxhash as was needed for the previous release. This can be done on ubuntu using:
sudo apt-get install python-dev
sudo pip install xxhash

Any suggestions for windows users?

I have the same problem

Thank you shersey42


extract parentContextId from record when updating

When updating a record, we currently pass in the record descriptor int the create options, however if the record has a parent we must set the parentContextId.
In order to do this we extract the parentId from the descriptor, and if it exists we set a parentContextId.

Codecov Report

Merging #494 (35bb8b0) into main (c8e6fa8) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #494   +/-   ##
=======================================
  Coverage   90.55%   90.55%
=======================================
  Files         112      112
  Lines       29085    29091    +6
  Branches     2078     2079    +1
=======================================
+ Hits        26338    26344    +6
  Misses       2712     2712
  Partials       35       35

Components
Coverage Δ

agent
78.83% <ø> (ø)

api
97.89% <100.00%> (+<0.01%)
:arrow_up:

common
98.68% <ø> (ø)

credentials
95.21% <ø> (ø)

crypto
93.81% <ø> (ø)

dids
97.65% <ø> (ø)

identity-agent
96.70% <ø> (ø)

crypto-aws-kms
100.00% <ø> (ø)

proxy-agent
96.70% <ø> (ø)

user-agent
96.70% <ø> (ø)


Radio streaming download: ICY causes BadStatusLine

Hello,
Even if the icy's protocol is broken, I would still need to download the streaming data of a shoutcast server.
When attempting to, I get this issue:
File "/usr/lib/python3/dist-packages/requests/api.py", line 55, in get
return request('get', url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 44, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 455, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 558, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 378, in send
raise ConnectionError(e)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='streaming3.radiocat.net', port=80): Max retries exceeded with url: /;listen.mp3 (Caused by ProtocolError('Connection aborted.', BadStatusLine('ICY 200 OK\r\n',)))
Any workaround or something I could do?
Thanks.

Yes. =) Don't use a HTTP library.
That answer was a bit glib, but it's pretty accurate. Let me show you what RFC 7230 says a HTTP status line should look like:
status-line = HTTP-version SP status-code SP reason-phrase CRLF
That first set of characters needs to be a HTTP version. If it doesn't specify a HTTP version, a HTTP library cannot assume it has the faintest idea what's going on. For that reason, httplib sees a HTTP version called 'ICY', doesn't recognise it, and bails out (quite rightly).
Unfortunately for you, httplib then closes the socket connection and loses its reference to the socket object.
What you really need is something that can fake out a HTTP request using a socket. This shouldn't be very hard: create a socket connection directly to your target and then just write some basic HTTP headers to it.
If you find that helpful, you could write an ICY transport adapter for requests and use it.
Sadly, however, this is outside the scope of requests to help you. =)

Lukasa, thank you for your answer.
How bad would it be to modify the original library like this?
https://mail.python.org/pipermail/web-sig/2005-August/001641.html
It sounds like I'd save a lot of work just by adding two lines. Still, I know it's not a great solution. What do you personally think about it?
Doing everything with sockets will be a lot of pain.

@rubentorresbonet if you choose to modify httplib like that, that's your decision. It's not up to our discretion nor is it our place to recommend it.
I think modifying a standard library is a poor way of handling this, but if that's what you choose to do, there's nothing for anyone to do about it.
Also @Lukasa didn't tell you to do everything with sockets, only portions dealing with ICY.


task bar updates are 100% a checked checkbox

read title

can you elaborate?

read title

Are you saying that Among Us Editor always sets task bar updates to be on? Or are you saying you want a setting for it?
Please explain further so I can understand.

I accidentally pressed "Close with comment" smh

I'm closing this as you've given no response.
In the future I will add a task bar updates setting incase that is the reason you opened this issue.


fix(explore): Filter box full chart height

SUMMARY
Fixes #14604
The filter_box wasn't getting all the available height, making the 'Apply' button appear cut.
BEFORE

AFTER

TEST PLAN

Open a chart in Explore
Set viz type 'Filter box'
Add at least 5 filters
Make sure the 'Apply' button appears correctly

ADDITIONAL INFORMATION

[x] Has associated issue: #14604
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@junlincc @rusackas

The history of cosmetic regressions with this particular area is super high. Let's give this one due diligence in Explore and Dashboards, with various lengths of content to trigger different scrolling needs.
/testenv up

/testenv up

thanks for the fix!! LGTM 🟢 @pkdotson @suddjian please give a review~ 🙏
before

after


Update nf-winbase-readdirectorychangesexw.md

Changed Windows Server 2016 to Windows Server 2019.

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

Thanks!


The name "/resin_supervisor" is already in use by container <container_hash>. You have to remove (or rename) that container to be able to reuse that name..

docker version
Client:
Version:      1.10.3
API version:  1.22
Go version:   go1.6
Git commit:   20f81dd-unsupported
Built:        Mon Sep  5 12:25:41 2016
OS/Arch:      linux/arm
Server:
Version:      1.10.3
API version:  1.22
Go version:   go1.6
Git commit:   20f81dd-unsupported
Built:        Mon Sep  5 12:25:41 2016
OS/Arch:      linux/arm
And the actual error is:
Sep 04 16:23:16 ts-imx6 systemd[1]: resin-supervisor.service: Main process exited, code=exited, status=125/n/a
Sep 04 16:23:17 ts-imx6 docker[11899]: Failed to stop container (resin_supervisor): Error response from daemon: No such container: resin_supervisor
Sep 04 16:23:18 ts-imx6 docker[11907]: Failed to remove container (resin_supervisor): Error response from daemon: No such container: resin_supervisor
Sep 04 16:23:18 ts-imx6 systemd[1]: resin-supervisor.service: Unit entered failed state.
Sep 04 16:23:18 ts-imx6 systemd[1]: resin-supervisor.service: Failed with result 'exit-code'.
Sep 04 16:23:28 ts-imx6 systemd[1]: resin-supervisor.service: Service hold-off time over, scheduling restart.
Sep 04 16:23:28 ts-imx6 systemd[1]: Stopped Resin supervisor.
Sep 04 16:23:28 ts-imx6 systemd[1]: Starting Resin supervisor...
Sep 04 16:23:29 ts-imx6 docker[11924]: Failed to stop container (resin_supervisor): Error response from daemon: No such container: resin_supervisor
Sep 04 16:23:30 ts-imx6 docker[11951]: Failed to remove container (resin_supervisor): Error response from daemon: No such container: resin_supervisor
Sep 04 16:23:30 ts-imx6 systemd[1]: Started Resin supervisor.
Sep 04 16:23:31 ts-imx6 bash[11959]: docker: Error response from daemon: Conflict. The name "/resin_supervisor" is already in use by container 45e7b1d1b444bb0719bb3d2fb08d4d0dba85d54981dd42184fdf08f742192c16. You have to remove (or rename) that container to be able to reuse that name..
Sep 04 16:23:31 ts-imx6 bash[11959]: See '/usr/bin/docker run --help'.
 Front conversations

Issue present also here: https://github.com/docker/docker/issues/23371

This was mitigated by not removing the container with every start.


per-project source file config

I have a project where I only want to generate tags for a specific directory (src). This can be accomplished in one of two ways:

Run ctags as ctags src.
Run ctags as ctags, and include -L filelist in an options file for ctags (where filelist contains only src).

However, neither of these are currently possible with gutentags, as ctags $PROJECT_ROOT is hardcoded here.
Could some mechanism be added to tell ctags to not run on an entire project? (I am unsure of the best way to implement this while maintaining the reasonable default of indexing the whole project -- perhaps if an -L option is found in .gutctags then the CTAGS_ARGS_LAST argument should not be passed, though this seems slightly brittle/hacky.)

A clunky but workable way would be to specify --exclude= entries for everything except src inside the project's .gutctags?
Another option is to simply tell Gutentags that the project root is inside src. You can do that with a combination of g:gutentags_project_root, g:gutentags_exclude_project_root, and, if needed, by writing a custom g:gutentags_project_root_finder.


hacky solution to build controllers for python3.10

Description
This is a hacky solution to build the controllers for Python3.10 (see https://github.com/RoboCup-Humanoid-TC/webots/issues/302).
I don't expect this to be merged, but this branch is maybe useful for other people while the upstream master is not merged into the fork.
Related Issues
#302

IMO it is not that hacky as the upstream implemented it similarly right? Pulling a merging of the upstream should be fine, or are there any other opinions on this?

I think this is not relevant anymore due to the new Webots version, therefore closing it


Run with -p no:doctest

Codecov Report

Merging #4 (ea67662) into master (153e9e1) will decrease coverage by 1.47%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
- Coverage   57.78%   56.30%   -1.48%
==========================================
  Files          11       11
  Lines         694      650      -44
==========================================
- Hits          401      366      -35
+ Misses        293      284       -9

Impacted Files
Coverage Δ

src/pytest_doctest_docutils.py
37.27% <53.57%> (+3.93%)
:arrow_up:

tests/test_pytest_doctest_docutils.py
100.00% <100.00%> (ø)

gp_libs/__about__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

gp_libs/__init__.py
0.00% <0.00%> (-42.86%)
:arrow_down:

src/linkify_issues.py
91.30% <0.00%> (-4.35%)
:arrow_down:

tests/conftest.py
92.10% <0.00%> (-2.64%)
:arrow_down:

docs/conf.py

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Log changes to TokenMetadata

Description
v0 implementation for logging changes to TokenMetadata. The changes include:

For tokenToEndpointMap and bootstrapToken, calculate the symmetric difference per endpoint for its token set before and after the changes.
For pending range calculation, we differentiate between an endpoint leaving and bootstrapping.

Looking at all the places that tokenToEndpointMap is mutated, there is only one call to put and two calls to removeValue. For the call to put, there is already a warning
logger.warn("Token {TOKEN} changing ownership from {ENDPOINT} to {ENDPOINT}"

why not just add similar statements around the one call to bootstrapTokens.put?
What additional information are these calculations doing?


Add Test Support for @RequestMapping NoPath, OnlySlashPath, MissingSl…

…ashLeadingPath. Fix for  #387

@Bhavya-official Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@Bhavya-official Thank you for signing the Contributor License Agreement!


feat(table): loading state implementation and story

Summary

Add loading state to table with configurable row count

Change List (commits, features, bugs, etc)

add loading state to Table
update loading story
update snapshots

Related Issues

Closes IBM/carbon-addons-iot-react#29

Acceptance Test (how to verify the PR)

all changes viewable in the storybook

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.13.0 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


Display nicer error is SSH config permissions are wrong

This can be difficult to see in the output.

lacking context and I am not sure why and how the permissions will be wrong. As vscoder itself right those configs. CLosing because of no activity.
cc: @stirby


Added auto-transitioning background option

Tested on:
-IDE: Visual Studio 2017 (with latest updates)
-OS: Windows 7 x64

Looks OK, but will it break VS 2015? I don't have 2015 installed now (and don't want to support it since 2019 is coming).

Not yet tested on VS2015, but I think it would not break on it, since it's just a reaaallly simple transition between 2 Image Controls, with a DoubleAnimation. (I'm planning to add option to disable animation too).

The package references for metapackage has been updated. I'm going to check and do some modify, but I've no time today.

Sure, take your time :D


make DataLoader a generic to ensure the return type of loader is what you expect

similar to how in next.js, GetServerSideProps is a generic, I think it would be helpful if DataLoader was also a generic to ensure what you return from a loader is what you expect, similarly it would be beneficial to also allow a custom Context type.
here's my patch-package diff
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index f9d7c6c..f8360f8 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -4,12 +4,12 @@ import { Response } from "./fetch";
 /**
  * Some data that was returned from a data loader.
  */
-export declare type AppData = any;
+export declare type AppData<T = any> = T;
 /**
  * An object of data returned from the server's `getLoadContext` function. This
  * will be passed to the data loaders.
  */
-export declare type AppLoadContext = any;
+export declare type AppLoadContext<T = any> = T;
 /**
  * The result from executing a data loader.
  */
@@ -17,12 +17,12 @@ export declare type AppLoadResult = Response | null;
 /**
  * A function that loads data for a route or the global data loader.
  */
-export interface DataLoader {
+export interface DataLoader<AppDataType = any, Context = any> {
     (args: {
-        context: AppLoadContext;
+        context: AppLoadContext<Context>;
         params: Params;
         url: URL;
-    }): AppData;
+    }): AppDataType;
 }
 /**
  * Loads data using the global data loader at `data/global.js`.

I've been using the following to generate typed loaders with corresponding hooks. It's a little silly since it's a noop, but I'm not sure of any other way to ensure the hook matches the loader without some amount of manual typing.
// make-loader.ts
import {DataFunctionArgs} from '@remix-run/server-runtime';
import {useLoaderData} from 'remix';

export type LoaderFunction<T> = (
  args: DataFunctionArgs
) => Promise<Response> | Response | Promise<T> | T;

interface MakeLoaderResult<T, R> {
  loader: LoaderFunction<R>;
  useLoaderData: () => R;
}

export function makeLoader<T, R>(
  loader: LoaderFunction<R>
): MakeLoaderResult<T, R> {
  return {
    loader,
    useLoaderData,
  };
}

// route.tsx
export const {loader, useLoaderData} = makeLoader(async ({request}) => ({
  flash: await loadFlashMessages(request),
}));

I've been using the following to generate typed loaders with corresponding hooks. It's a little silly since it's a noop, but I'm not sure of any other way to ensure the hook matches the loader without some amount of manual typing.
// make-loader.ts
import {DataFunctionArgs} from '@remix-run/server-runtime';
import {useLoaderData} from 'remix';

export type LoaderFunction<T> = (
  args: DataFunctionArgs
) => Promise<Response> | Response | Promise<T> | T;

interface MakeLoaderResult<T, R> {
  loader: LoaderFunction<R>;
  useLoaderData: () => R;
}

export function makeLoader<T, R>(
  loader: LoaderFunction<R>
): MakeLoaderResult<T, R> {
  return {
    loader,
    useLoaderData,
  };
}

// route.tsx
export const {loader, useLoaderData} = makeLoader(async ({request}) => ({
 flash: await loadFlashMessages(request),
}));

export const {loader, useLoaderData} = makeLoader( is an effect. You should not do this.
We have the json<Data>(data: Data, init: ResponseInit) function for type safety here. I actually recommend you return a Response from loaders and actions and use the aforementioned json utility, this leaves room for easy growth / expansion of the functionality of the loader in the future. If you unit test that loader that returns an object, and need to add headers to the response, you've just broken all your tests that should still be passing.

yeah this issue is mine and is way out of date 🥴


No satellite data outside HH jurisdiction

While the LGV satellite imagery is normalised and looks pretty good, it does not provide information for regions outside the HH jurisdiction. Ideally, we should fall-back to some other source that provides global data.

Request to the Bundesamt für Kartographie und Geodäsie resulted in a rejection. They only provide data for either money or important people 😢
Similarly, the SH cartography office provides a DOP20 WMS API — unfortunately, this one does not contain data for every zoom-level and the imagery is somewhat blurry. However, it showed that ?transparent=true is possible which allows us to use the Mapbox provided satellite imagery without any complicated merging logic!


swipe back also for md-theme

This is a (multiple allowed):

[x] feature-discussion (RFC)

Framework7 Version: 2

For users with disabilities (and for the lazy one) it is hard to go to the previous page by clicking the upper back button in md-theme. So either ios-theme with swipe-back is used or md-theme but without swipe back possibility. This is not flexible.
I want to use swipe back but dont want to miss md-look and feel.
So why not let user choose between "swipe back" or not independent of the theme.
Is it possible to extend (or merge this function from ios-theme) to use swipe back with md-theme?
(Swipe back is not about visual styles it s about usability and should not be missed only because of md-theme.)

WeChat App

There are a lot of Apps support this gesture, and sliding back is a very good gesture. iOS theme has been supported, why not transplant it to MD theme?

Как использовать swipe back?


Uncaught Error: ELOOP: too many symbolic links encountered, open '/Users/slauae/.atom/keymap.cson'

I am attempting to store my keymap.cson in another folder (git repo) so I can update and share it on multiple computers. I cannot use the sync package that exists because of network limitations at my office.
To get this error:

move keymap.cson to another folder
create symlink: ln -s /myother/folder/keymap.cson ~/.atom/keymap.cson
attempt to access the keymap file from Atom Settings

Note, my keybindings work like expected, just can't access them from settings.
Atom Version: 1.3.1
System: Mac OS X 10.11.1
Thrown From: Atom Core
Stack Trace
Uncaught Error: ELOOP: too many symbolic links encountered, open '/Users/slauae/.atom/keymap.cson'
At /Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:486

Error: ELOOP: too many symbolic links encountered, open '/Users/slauae/.atom/keymap.cson'
    at Error (native)
    at Object.fs.openSync (fs.js:549:18)
    at Object.module.(anonymous function) [as openSync] (ATOM_SHELL_ASAR.js:137:20)
    at Workspace.module.exports.Workspace.openTextFile (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:528:27)
    at Workspace.module.exports.Workspace.openURIInPane (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:461:23)
    at Workspace.module.exports.Workspace.open (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:393:19)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:337:38
    at Workspace.module.exports.Workspace.openURIInPane (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:454:22)
    at Workspace.module.exports.Workspace.open (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:393:19)
    at AtomEnvironment.module.exports.AtomEnvironment.openLocations (/Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:1035:19)
    at EventEmitter.outerCallback (/Applications/Atom.app/Contents/Resources/app.asar/src/application-delegate.js:201:18)
    at emitTwo (events.js:92:20)
    at EventEmitter.emit (events.js:172:7)

Commands
     -0:03.7.0 settings-view:open (div.pane-item.native-key-bindings.about)
     -0:00.7.0 application:open-your-keymap (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-atom-dark-syntax.theme-atom-dark-ui)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ],
    "disabledPackages": [
      "autocomplete-clang",
      "emacs-mode",
      "transient-emacs",
      "tabs",
      "autocomplete-snippets",
      "tree-view",
      "autocomplete-plus"
    ],
    "destroyEmptyPanes": false,
    "audioBeep": false
  },
  "editor": {
    "invisibles": {},
    "fontSize": 12,
    "showIndentGuide": true,
    "showInvisibles": true,
    "preferredLineLength": 120,
    "softWrap": true
  }
}

Installed Packages
# User
autocomplete-moose, v0.19.0
language-moose, v0.16.0
pane-info, v1.0.0

# Dev
No dev packages

I notice an extra self-referencing symbolic link in my .atom directory, which was the true root of this error.


Unable to connect to a terminal server when license model is for per-device

four prerequisites

The terminal server was configured to function in per-device license mode.
The terminal server have more than one license server.
and one license server is not activationed.
The license server search mode is set to automatic.
If the above condition is met, i can't use freerdp connected to terminal server. But it is ok to use MSTSC to connected.

but if I specify the license server is a license server has been activated , then i can connect to the terminal server .
How can I solve this problem ?

You should report the issue to FreeRDP project.


Big Turbine is breeding?

First time I saw the bug was today affects both of my turbines. Image of bug The hearts don't seem to stop either.

tried it whitout resource pack?

https://github.com/erogenousbeef/BigReactors/issues/457
never mind

Easter egg.


Adding project tinkerbell/hook

Description of changes:
WIP
I have opened this PR to test the image builds in tinkerbell/hook. The image tinkerbell/hook-kernel uses an upstream Dockerfile and hence is resource intensive.
TODO

[x] Setup linuxKit with Builder-base
[x] Add logic to use linuxkit to build in memory OS
[x] Add logic to make tink-docker DIND container
[x] Add readme, CDK

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/test hook-tooling-presubmit

/test hook-tooling-presubmit

/test hook-tooling-presubmit

/hold for CRD changes

/unhold

/lgtm


span breaked on the invoke node of hystrix

Please answer these questions before submitting your issue.

Why do you submit this issue?
[√ ] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

dose skywalking support hystrix with 2.1.5 ?
span breaked on the invoke node of hystrix but not all, i can't find the reason, dose it associate with the hystrix pulgin version?

Bug

Which version of SkyWalking, OS, and JRE?

Which company or project?

What happened?
If possible, provide a way to reproduce the error. e.g. demo application, component version.

Requirement or improvement

Please describe your requirements or improvement suggestions.

dose skywalking support hystrix with 2.1.5 ?

Read the document, too many plugins. impossible to remember all.

span breaked on the invoke node of hystrix but not all, i can't find the reason, dose it associate with the hystrix pulgin version?

You have to debug the plugin by yourself. And find out why.


[DDW-269] Create storybook stories for known issue detection feature

This PR creates a Storybook stories for the "Known issue detection".
Todo:

[x] Create story based on [DDW-280] empty screen stories
[x] Update the support screen for the new "Known issue detection" feature
[x] Add issues found to the stories
[ ] Integrate with backend
[ ] Create flow types - depends on the backend
[ ] Intl for Issues found
[ ] Provide Japanese translations

Screenshots:

Review Checklist:
Basics

[ ] PR is updated to the most recent version of target branch (and there are no conflicts)
[ ] PR has good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance tests are passing (npm run test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (npm run dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (npm run package / CI builds)
[ ] There are no flow errors or warnings (npm run flow:test)
[ ] There are no lint errors or warnings (npm run lint)
[ ] Text changes are proofread and approved (Jane Wild)
[ ] There are no missing translations (running npm run manage:translations produces no changes)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (npm run storybook)
[ ] In case of npm dependency changes both package-lock.json and yarn.lock files are updated

Code Quality

[ ] Important parts of the code are properly documented and commented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-rendering
[ ] Any code that only works in Electron is neatly separated from components

Testing

[ ] New feature / change is covered by acceptance tests
[ ] All existing acceptance tests are still up-to-date
[ ] New feature / change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review:

[ ] Merge PR
[ ] Delete source branch
[ ] Move ticket to done on the Youtrack board

@darko-mijic could you check the missing points for this task? We need the Japanese translations and the backend integration. Thanks.


poetry run exits on KeyboardInterrupt

[x] I am on the latest Poetry version.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: Arch Linux
Poetry version: 0.11.4

Issue

KeyboardInterrupt is not properly handled when executing with poetry run.
If a python script attempts to catch a KeyboardInterrupt exception, instead of it being handled, the entire poetry run ... command exists completely.
Here is an example of running the python interpreter.
$ python
>>> try:
...     while True:
...         pass
... except KeyboardInterrupt:
...     print('hello')
...
^Chello
>>> print('I am still in the interpreter')

poetry run python
>>> try:
...     while True:
...         pass
... except KeyboardInterrupt:
...     print('hello')
...
^Chello
$ echo 'I am back to the shell'

Even worse is the way this affects poetry scripts. Completely exiting the script instead of handling the KeyboardInterrupt exception.
pyproject.toml
[tool.poetry.scripts]
script = 'script:main'

script.py
def main():
    try:
        while True:
            pass
    except KeyboardInterrupt:
        print('Never reached when executed using `poetry run script`')

$ poetry run script
^C

This does not happen when the package is installed with pip and the script is executed.
$ poetry build
$ pip install dist/project.whl
$ script
^CNever reached when executed using `poetry run script`

Not fixing a bug for awhile doesn't make its ticket invalid.  Perhaps I should write a toaster app to respond to everything stale [bot] wants to close.

This is fixed in the newer versions of poetry that are in beta release because poetry run no longer runs it through a popen wrapper and instead exec's the new process directly.

Hell @altendky ,
running the stale bot was necessary to get a better overview about what issues are still relevant, before poetry 1.0 is released. @sdispater explained in another issue, that the bot may be disabled again later.
If you find that an issue isn't fixed, please just leave a comment in the issue. We can reopen it anytime.
Thanks a lot for your contribution!
fin swimmer

In my experience closing tickets due to being untouched usually just means a valid ticket wasn't addressed for a long time.  I'm glad to hear that this case is an exception and that stale [bot] might go away.


'Third-party application access via OAuth' must be enabled (non-default) in order for this to work

I was trying to set this up with a brand new Azure DevOps organisation and Azure Automation today and got 'SourceControls securityToken in invalid'
This is similar to the issue described here:
https://docs.microsoft.com/en-us/answers/questions/813444/an-error-occurred-while-creating-the-source-contro.html
I found that I needed to enable the 'Third-party application access via OAuth' in 'Azure DevOps / Organization Settings / Policies / Application connection policies' in order for the connection to be created.
According to the Azure DevOps documentation this policy is 'defaulted to off for all new organizations.'
https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/change-application-access-policies?view=azure-devops#application-connection-policies
Once this option was enabled it all worked fine. It would be good if the Azure Automation documentation could be updated to reflect this necessary prerequisite.

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

ID: 83c90e64-b615-711f-a53d-fc76606e2ecd
Version Independent ID: 2d164036-6886-4440-50f7-369f99f41cea
Content: Use source control integration in Azure Automation
Content Source: articles/automation/source-control-integration.md
Service: automation
Sub-service: process-automation
GitHub Login: @SGSneha
Microsoft Alias: sudhirsneha

@Borgquite Thanks for your comment! We will review and provide an update as appropriate.

@Borgquite We have updated the document as required. The update will go live in less than 24 hours. Thanks again!


Add VBA script to file I am creating from scratch

I'm working on a program that will generate an excel spreadsheet. I have two goals:

Add data validation drop-downs to cells in sheet1 and use columns of data in sheet2 as the list of available values.
Add a VBA macro that allows me to "multi-select" dropdown selections into a comma separated list.

Looks like data validations are a pro feature, but macros have some support in the community version. Is there a way to attach a VBA macro to an excel file that I am generating in the browser? I have a VBA blob that I want to attach, and then save the output file as a xlsm file. Looks like all mentions of macros are related to reading files in and then doing something with the attached macros, though.
I found an old issue that says it wasn't possible at the time...I assume this hasn't changed?
General flow of my generate workbook function:
  const onClick = () => {
    try {
      const workbook = xlsx.utils.book_new();

      const lookupValues = generateLookupValueRows();
      const lookupValuesSheet = xlsx.utils.json_to_sheet(lookupValues);
      xlsx.utils.book_append_sheet(workbook, lookupValuesSheet, `Lookup Values`);

      const templateRows = generateTemplateRows();
      const templateSheet = xlsx.utils.json_to_sheet(templateRows);
      xlsx.utils.book_append_sheet(workbook, templateSheet, `Template Input`);

      // want to attach a VBA blob to the workbook before writing the file

      xlsx.writeFile(workbook, `Template.xlsm`);
    } catch (err) {
      console.log('Error downloading template');
    }
 };

Thanks!

https://docs.sheetjs.com/docs/csf/features/#vba-and-macros
You can't add to the XLSX target since XLSX does not support macros.  You can add to XLSM or XLSB or XLS.
To extract the macro blob, run this once in NodeJS to generate vba.bin:
var XLSX = require("xlsx"), fs = require("fs");

// this part is from the docs
var wb = XLSX.readFile("path/to/template/file", { bookVBA: true });
var vbablob = wb.vbaraw;

// save to file
fs.writeFileSync("vba.bin", vbablob);

Put the generated vba.bin somewhere that your browser can fetch (usually in a /public directory), then make the marked changes:
  const onClick = async() => { // <-- async function
    try {
      const workbook = xlsx.utils.book_new();

      const lookupValues = generateLookupValueRows();
      const lookupValuesSheet = xlsx.utils.json_to_sheet(lookupValues);
      xlsx.utils.book_append_sheet(workbook, lookupValuesSheet, `Lookup Values`);

      const templateRows = generateTemplateRows();
      const templateSheet = xlsx.utils.json_to_sheet(templateRows);
      xlsx.utils.book_append_sheet(workbook, templateSheet, `Template Input`);

      // want to attach a VBA blob to the workbook before writing the file
      var vba = new Uint8Array(await (await fetch("vba.bin")).arrayBuffer()) // <-- get vba blob
      workbook.vbaraw = vba; // <-- add to file
      xlsx.writeFile(workbook, `Template.xlsm`, {bookVBA: true}); // <-- use XLSM, set bookVBA true
    } catch (err) {
      console.log('Error downloading template');
    }
 };

I'm trying to achieve same results as this thread but vbablob = wb.vbaraw;doesn't seem to be working
I'm manually saving the locally extracted vba.bin in S3 bucket and then trying to fetch it, to attach to the new excel workbook generated using  const workbook = xlsx.utils.book_new();
On downloading the xlsm using writeFile, I'm unable to see the validation/ vba macros on the file
On debugging, I see that the vba.bin is in fact successfully added to the workbook.

My export function flow
`
const onClick = async() => { // <-- async function
try {
const workbook = xlsx.utils.book_new();
  const lookupValues = generateLookupValueRows();
  const lookupValuesSheet = xlsx.utils.json_to_sheet(lookupValues);
  xlsx.utils.book_append_sheet(workbook, lookupValuesSheet, `Lookup Values`);

  const templateRows = generateTemplateRows();
  const templateSheet = xlsx.utils.json_to_sheet(templateRows);
  xlsx.utils.book_append_sheet(workbook, templateSheet, `Template Input`);

  // want to attach a VBA blob to the workbook before writing the file
  var vba = new Uint8Array(await (await fetch("s3 public url/vba.bin")).arrayBuffer()) // <-- get vba blob
  workbook.vbaraw = vba; // <-- add to file
  xlsx.writeFile(workbook, `Template.xlsm`, {bookVBA: true}); // <-- use XLSM, set bookVBA true
} catch (err) {
  console.log('Error downloading template');
}

};
`
Any pointers would be helpful! Thanks!


refactor(mesh): add category slug as search params

Notable Changes
Use category slug as search params and replace useState with useSearchParams.
Use window.history to push/replace search params rather than next.js router to prevent page reload when set search params.
Pages:

Homepage (category section)
Media

感謝幫改！！


Will ribbon automatically update its server list when we using consul?

Hi,
when one node of server list is down, how fast could BaseLoadBalancer refresh the UpServerList. I just find that PollingServerListUpdater will do this job every 30 seconds, is there any other strategy？

yes see https://github.com/spring-cloud/spring-cloud-consul/blob/master/spring-cloud-consul-discovery/src/main/java/org/springframework/cloud/consul/discovery/ConsulCatalogWatch.java


兼容paddlenlp中当gpu为1时对degree默认值当修改

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


fromIteratorBuffered

Fixes #1275
I've run a simple benchmark against fromIterator + bufferSliding and there seems to be a decent gain (around 35%, perhaps more than 3.2.2 because we fixed perf regression on Scala 2.13) but I'm not sure if it is enough to make a difference for your use case @deusaquilus
If it's not, I'm happy to try and help to solve the issue
[info] Benchmark                                               (chunkCount)  (chunkSize)   Mode  Cnt    Score   Error  Units
[info] ObservableIteratorBenchmark.bufferTumbling                      1000         1000  thrpt   40   95.434 ± 0.998  ops/s
[info] ObservableIteratorBenchmark.fromIteratorBufferedUnsafe          1000         1000  thrpt   40  130.350 ± 2.840  ops/s

@Avasil Actually it might be even more then this number in my use-case because the JDBC ResultSet fetches results in a chunked way itself. That means that by synchronizing Monix Chunks and JDBC chunks, we might be freeing a whole lot of IO cycles downstream. Will let you know how it turns out.
Btw what release can I hope to see this in?

@deusaquilus It's already released in 3.3.0 :) Will be waiting for your report


the program crashes...

When the operating system starts, the program works, but after a while of using the PC, the program simply does not want to work (only applications whose icons I made myself work). I tried reinstalling the program, restarting the PC several times. and still the program does not want to work after some non-fixed time. (sometimes it does not work even when the operating system is booted)

It doesn't even show errors. The PC is powerful and the program itself is the latest version

This is most likely because it is not an error, but is actually the auto-hide feature that is enabled by default via the ToggleSwitch auto-timeout feature that emulates the same behavior in the Blue Archive game client. It hides the suite after 5 consecutive minutes of inactivity measured by your system.
To double-check, hover over the top-right corner of your desktop when the suite has disappeared. The ToggleSwitch skin should pop-up once you hover over its general area, and clicking it will repopulate your desktop with the suite.

If you wish to disable this behavior, right-click the ToggleSwitch, select Change Timeout Value and set it to zero or less. Alternatively, if you would like to use this behavior and have your custom apps follow suit, you can add them in the same ToggleSwitch's Edit Database as outlined in the Steam guide or relevant wiki page and extend the timeout threshold to something you are more comfortable with, like 30 minutes or an hour.
If this is not the case and the suite is indeed disappearing completely, please doubly confirm that the above assumptions are incorrect by opening the Rainmeter client and checking that the ToggleOn skin is loaded or not and and I will think of other possibilities.

Note that in the above screenshot, it says ToggleOn is loaded but the skin itself is hidden. This is because my cursor is not hovering over it, which is the correct behavior

I apologize for not noticing this right away. Yes, it turned out that a timeout was simply set. Thank you very much for your help


In this PR, I removed some redundant code under common and adjusted some formats.

Signed-off-by:
Pre-Checklist
Note: Please complete ALL items in the following checklist.

[x] I have read through the CONTRIBUTING.md documentation.
[x] My code has the necessary comments and documentation (if needed).
[x] I have added relevant tests.

Purpose

Some description about what this PR wants to do.
Approaches

Some description about how this PR achives the purpose.
Related Issues

e.g. Close #796
New Behavior (screenshots if needed)

N/A

@BlockLiu @Dkbei @lark @snakev 😂

@hk-lrzy Thank you for your invitation, I am honored to participate in this project, it can help me improve my technical ability, I also see if I can make more contributions to this project.


Loading prebuilt pickle file

def build_dict takes around 30 mins to finish. This patch will just check if the pickle file is already there so it doesn't build it again

Hello. Thank you for your PR. However, this commit will generate an error when there is no pre-trained word_dict.pickle.  I think this way would be better.

Hello
I added the check is the file exists. Also, I noticed that the build_dataset function takes time. any ideas how can we do the same for it?

Saving train_x, train_y, valid_x, valid_y with pickle might help.

Will do. btw I'm curious on which GPU did you train this. on a 1080 it's struggling

I used two TITAN Xp and it takes a long time for me too.

tick tock


docs(contributing): Add link to egghead.io series

As noted here

Thank you for your contribution. We detected an issue with your commit message though and would ask you kindly to fix it.

Commit: d33736d69a18869b337e6d26e2b2cd57eb8ab1f8
Your commit message body contains a line that is longer than 80 characters

Guidelines are available at http://karma-runner.github.io/0.13/dev/git-commit-msg.html and please do not hesitate to ask if you have any questions.

This message was auto-generated by https://gitcop.com

Nevermind, I thought the other PR was merged. I'll just add this change to the other PR. Thanks!


Add ScaleInPolicy and AutomaticRepairsPolicy

Resource Provider
CRP (Microsoft.Compute)
Description of Feature or Work Requested

Add support in Azure CLI to be able to set ScaleInPolicy which is a list of Rules that control which VMs are removed during a scale-in. The available Rules are OldestVM, NewestVM & Default. User can specify one or more rules.

e.g az vmss create --name myScaleSet --resource-group myResourceGroup –scale-in-policy OldestVM
e.g az vmss update --name myScaleSet --resource-group myResourceGroup --set ScaleInPolicy.Rules=OldestVM

Similar to how we can use PS or azcli to add or update VMSS upgradePolicy, we should be able to do the same for automaticRepairsPolicy.
e.g. az vmss update --name myScaleSet --resource-group myResourceGroup --set UpgradePolicy.AutomaticOSUpgradePolicy.EnableAutomaticOSUpgrade=true

Minimum API Version Required
2019-03-01
Swagger Link

https://github.com/Azure/azure-rest-api-specs/pull/7034
https://github.com/Azure/azure-rest-api-specs/commit/14464cf0bec27f838f1649f562c9f98cc4074855

Target Date
ASAP

We have received your feature request. It's added to S161.

For automatic repairs:
e.g. az vmss update --name myScaleSet --resource-group myResourceGroup --set AutomaticRepairsPolicy.Enabled=true AutomaticRepairsPolicy.GracePeriod=PT05 AutomaticRepairsPolicy.MaxInstanceRepairsPercent=100
e.g. az vmss update --name myScaleSet --resource-group myResourceGroup --set --automatic-repairs-policy-enabled=true --automatic-repairs-policy-grace-period=PT05 --automatic-repairs-policy-max-instance-repairs-percent=100
JSON
"properties": {
"automaticRepairsPolicy": {
"enabled": "true",
"gracePeriod": "PT0S",
"maxInstanceRepairsPercent": 100
},
}

Hi Amol, I encounter an error when I specify more than one scale in policy. Can you help?
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"BadRequest","message":"{\r\n "error": {\r\n "code": "BadRequest",\r\n "message": "Virtual Machine Scale Sets scale in policy must contain at least one rule."\r\n }\r\n}"}]}
{
    "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
    "contentVersion": "<IP_ADDRESS>",
    "parameters": {},
    "variables": {},
    "resources": [
        {
            "type": "Microsoft.Network/publicIPAddresses",
            "apiVersion": "2018-01-01",
            "name": "vmss2LBPublicIP",
            "location": "eastus",
            "dependsOn": [],
            "tags": {},
            "properties": {
                "publicIPAllocationMethod": "Dynamic"
            }
        },
        {
            "type": "Microsoft.Network/loadBalancers",
            "apiVersion": "2018-01-01",
            "name": "vmss2LB",
            "location": "eastus",
            "dependsOn": [
                "Microsoft.Network/publicIpAddresses/vmss2LBPublicIP"
            ],
            "tags": {},
            "properties": {
                "backendAddressPools": [
                    {
                        "name": "vmss2LBBEPool"
                    }
                ],
                "inboundNatPools": [
                    {
                        "name": "vmss2LBNatPool",
                        "properties": {
                            "frontendIPConfiguration": {
                                "id": "[concat(resourceId('Microsoft.Network/loadBalancers', 'vmss2LB'), '/frontendIPConfigurations/', 'loadBalancerFrontEnd')]"
                            },
                            "protocol": "tcp",
                            "frontendPortRangeStart": "50000",
                            "frontendPortRangeEnd": "50119",
                            "backendPort": 22
                        }
                    }
                ],
                "frontendIPConfigurations": [
                    {
                        "name": "loadBalancerFrontEnd",
                        "properties": {
                            "publicIPAddress": {
                                "id": "/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/fytest/providers/Microsoft.Network/publicIPAddresses/vmss2LBPublicIP"
                            }
                        }
                    }
                ]
            }
        },
        {
            "type": "Microsoft.Compute/virtualMachineScaleSets",
            "apiVersion": "2019-07-01",
            "name": "vmss2",
            "location": "eastus",
            "dependsOn": [
                "Microsoft.Network/loadBalancers/vmss2LB"
            ],
            "tags": {},
            "sku": {
                "name": "Standard_DS1_v2",
                "capacity": 2
            },
            "properties": {
                "overprovision": true,
                "upgradePolicy": {
                    "mode": "manual"
                },
                "virtualMachineProfile": {
                    "storageProfile": {
                        "osDisk": {
                            "createOption": "FromImage",
                            "caching": "ReadWrite",
                            "managedDisk": {
                                "storageAccountType": null
                            }
                        },
                        "imageReference": {
                            "publisher": "OpenLogic",
                            "offer": "CentOS",
                            "sku": "7.5",
                            "version": "latest"
                        }
                    },
                    "osProfile": {
                        "computerNamePrefix": "vmss2d336",
                        "adminUsername": "fey",
                        "linuxConfiguration": {
                            "disablePasswordAuthentication": true,
                            "ssh": {
                                "publicKeys": [
                                    {
                                        "path": "/home/fey/.ssh/authorized_keys",
                                        "keyData": "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDmzXeK++L20uMK/Ug5wpjnWWyMlHoecEOxyHueHc1gPDj8qgLChiHt1OWJ1sDjiqBJ+hEEwZLjN8lCmUvWzzrl20d7M/BVp1ejulE/zr999kWuY3m5+FpAkbbxeO9LWoafwOir9dPzIOjDGdPWKbgHr3SerOHAuvVdXJDhWHtW5lB/MEnrxi48Pz/8k1lD1YccUAI6zDgKVJPBEk9fWMW8H0hKYsRXmlxdtg2npBQK7kbmcB2NJPEhTVgxVPqSaBVAt2lOCC/QQvAXcoD0lJGujp1IVYqSUarS5RnrYEDZ9Q6EKduWrP0GFkFkF8YzpFe+BRFaV8bLJrvZN43vgzRj fey@DESKTOP-ARGPJS4\n"
                                    }
                                ]
                            }
                        }
                    },
                    "networkProfile": {
                        "networkInterfaceConfigurations": [
                            {
                                "name": "vmss2d336Nic",
                                "properties": {
                                    "primary": "true",
                                    "ipConfigurations": [
                                        {
                                            "name": "vmss2d336IPConfig",
                                            "properties": {
                                                "subnet": {
                                                    "id": "/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/fytest/providers/Microsoft.Network/virtualNetworks/vmss1VNET/subnets/vmss1Subnet"
                                                },
                                                "loadBalancerBackendAddressPools": [
                                                    {
                                                        "id": "/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/fytest/providers/Microsoft.Network/loadBalancers/vmss2LB/backendAddressPools/vmss2LBBEPool"
                                                    }
                                                ],
                                                "loadBalancerInboundNatPools": [
                                                    {
                                                        "id": "/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/fytest/providers/Microsoft.Network/loadBalancers/vmss2LB/inboundNatPools/vmss2LBNatPool"
                                                    }
                                                ]
                                            }
                                        }
                                    ]
                                }
                            }
                        ]
                    }
                },
                "singlePlacementGroup": null,
                "scaleInPolicy": {
                    "rules": [
                        "Default",
                        "NewestVM"
                    ]
                }
            }
        }
    ],
    "outputs": {
        "VMSS": {
            "type": "Object",
            "value": "[reference(resourceId('Microsoft.Compute/virtualMachineScaleSets', 'vmss2'),providers('Microsoft.Compute', 'virtualMachineScaleSets').apiVersions[0])]"
        }
    }
}

I added --scale-in-policy in both vmss create and update.
--set is existing function of Azure CLI. I don't make changes for the 2nd request.
You will see the changes in Azure CLI 2.0.78. Code complete: 12/11/2019 Build to Cloud Shell: 12/13/2019 Official Release: 12/17/2019

@qwordy When will the change for 2nd request be made Feiyue Yu? Do I have to open another request? Why wasn't the change made?

@qwordy When will the change for 2nd request be made Feiyue Yu? Do I have to open another request? Why wasn't the change made?

@hapandar , the command in the 2nd request is already supported before this issue was opened. --set is a general parameter in update command.


Line 108

The line calls the calculate_score method, which is going to change to something else in a current refactoring.  Check with<EMAIL_ADDRESS>to see how to change it.

As the method calculate_score has not yet been completed, skipping this issue, as directed by Professor Gehringer.


Update skin to new version of Spotify CSS

The Spotify app has changed drastically since the last version of Spotio was released, so before we can even think about fixing the crashes and beginning to distribute Spotio again, we need to update the CSS.
If anyone has time to contribute, it would be greatly appreciated!

Hi, I would love to contribute on this project 😃 .

JFYI, @devinhalladay Archlinux AUR port worked last time I used it.
It's just that some menu items are missing.

Currently using Spicetify to mod my Spotify https://github.com/khanhas/Spicetify
While it is currently Windows only as it uses Rainmeter for the GUI you could always just manually run the lua files after changing the locations of files and choosing the settings. It is also based of a linux only script https://github.com/actionless/oomoxify so you could use that instead for your base.


Fix broken links

AutoML client library documentation
Core Auth

Thanks @theacodes -- we need to cut a patch release for this also but can maybe wait until @crwilcox gets here later today.


Adds unit tests [WIP]

Work In Progress - (DO NOT MERGE)
Fixes #11
Changes

Adds test cases
Refactors code

Sorry for the late response. This is a very solid effort! I wonder how we should proceed to get the tests in the codebase as soon as possible, so you're not stuck merging conflicts for the foreseeable future :-)

Hi @phenax, if it's okay with you, I'll take your changes locally and adapt the tests to the current codebase.

Sure. Let me know if I can help.

Thank you again, @phenax! I've pulled in on master some of the tests that make sense on the current codebase.


Command Hooks with console output

If I have a script that prints/echoes some text result, running in some command hook task, it will be printed to the console.
I thought this worked in previous versions, but I'm testing it in the latest version and it no longer works.
For example, a pre_release task from Command Hooks I only received:
Running the pre_release command hook...

but I expected something like this:
Running the pre_release command hook...
--------------------------------------------------
   The code was generated successfully
--------------------------------------------------

It is possible to print the result of a specific task, from command_hooks, to the console, without using --verbosity=obnoxious.

Could be something like
  def run_hook_step(hook, name="")
      # ...

      if (hook[:printable])
        result       = shell_result[:output].strip
        msg = @ceedling[:reportinator].generate_progress( result )
        @ceedling[:loginator].log( msg )
      end

      # ...
  end

Great point, @claudiiolima. The latest pre-release has this ability with the addition of an optional :logging setting for each hook configuration. See the Command Hooks plugin README for more details (the change implements the spirit of your suggestion but is slightly more sophisticated).


91 ai cannot handle being ionized

Closes #91

I'll give this a test tomorrow, but I had an instance tonight while I was testing ElectroChaff and one of the FO bombers got ionised through Disabled Power Regulator. I had the error come up in the game UI. I'm not sure if that's related to and/or fixed by what you've done here or it's something else, I'll see if I can recreate it tomorrow.

If you were playing vs AI, it was likely the error that this resolves. Until this is merged, you'll continue to run into it.


Expose SockAddr::from_raw_sockaddr

I also noticed the SockAddr/InetAddr::to_str functions were entirely redundant - ToString exists for that, & has a blanket impl on T: Display.

@asomers Could you take a look at this again? I split out the other change into #1495 as well.

Huh. I think the failure was just cause of the conflict in CHANGELOG?

bors retry

Ah, shoot, just realized the functionality I was looking for was in sockaddr_storage_to_addr - however, I'm pretty sure that should also be unsafe and take a *const sockaddr instead of an &sockaddr_storage, since it seems like there are some assume_init calls that might not be valid as the full extent of the sockaddr_storage might not actually get initialized if the address is only a couple bytes in size.


Stack not showing in STACKS view, but in hosts it recognizes the stack

Rancher Version:
1.1.4
Docker Version:
Client:
Version:      1.12.3
API version:  1.24
Go version:   go1.6.3
Git commit:   6b644ec
Built:        Wed Oct 26 21:44:32 2016
OS/Arch:      linux/amd64
Server:
Version:      1.12.3
API version:  1.24
Go version:   go1.6.3
Git commit:   6b644ec
Built:        Wed Oct 26 21:44:32 2016
OS/Arch:      linux/amd64
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu server 14.04 LTS
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
docker-compose build
docker-compose up -d
Results:
Services are build and started through docker-compose
In HOSTS view it shows the stack

In STACKS view it DON'T show the stack

Expected:
In STACKS view show the stack

I believe you need to use rancher-compose for the stacks to be recognized in the Rancher stacks view. Can you give that a go and let us know if that works?

The hosts screen just groups containers by labels, so if you add a host that has previously created containers or manually run containers with the appropriate labels they will show up like that in the host view.  But that doesn't make them actual stacks.

@vincent99: what is the difference between a stack created by docker-compose and a stack created in rancher ? I personally see NO difference between the two.
@aemneina: i don't like thinks like rancher-compose, I know that docker-compose files can be used in rancher but at this moment it doesn't  support version 2. Therefore i add the stack through the command line.
I would like to see in rancher that a docker-compose file can be uploaded and even environment file(s) uploaded as well. I understand that docker-compose version 2 will be supported by next release of rancher.

If you use docker-compose we see some containers come into existence and have no idea what YAML template was used to create them.  The original information about the template, variables that will be replaced, etc is just not there anymore because it's transformed by docker-compose into a finished output container.

@pe2mbs v2 syntax should be supported in rancher v1.2.0.

Closing due to inactivity.


C++: GCC: Double/Float comparison warning

When using double/float inside structures it's generating bad comparison (operator==) code which triggers gcc warnings
namespace Test

struct A
{
  0: required double fieldA;
  1: required float fieldB;
};

Run as following:
#:/tmp$ gbc c++ -o ./ ./test.idl
#:/tmp$ g++ -Wfloat-equal -c ./test_types.cpp
In file included from ./test_reflection.h:16,
from ./test_types.cpp:14:
./test_types.h: In member function 'bool Test::A::operator==(const Test::A&) const':
./test_types.h:59:37: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
&& (fieldA == other.fieldA)
^~~~~~
./test_types.h:60:37: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
&& (fieldB == other.fieldB);
^~~~~~

Bond builds with -Wall. -Wfloat-equal is not in -Wall.
Please build Bond-generated code with -Wall and without -Wfloat-equal. Consider using -isystem to add the generated Bond code to you header search path so that warnings are not emitted for it in your code that uses Bond. This should let you continue to use -Wfloat-eqaul in your own code.
The Bond project itself isn't interested in being 100% warning clean for every warning that every compiler can emit. So, we at Microsoft have no plans to change the generated code to handle -Wfloat-equal.


Add ability to invoke transform across all docs

Proposed Changes
Add the ability to take a TransformFunction and generate a SQL file that uses PLV8 to execute the transform across all documents within a table.
Why
The ability to run transforms using the currently built in functionality is great for development time. Generating a SQL file to handle the transform across a table of documents allows people to run the SQL script outside of any code changes. This can help in changing data types in a mapped .NET type. It also affords more capability of automating migrations using something like Sqitch or Roundhouse.
How
The TransformFunction class already has the ability to take a JavaScript file and generate a PLV8 sql script. A new method was added to take an individual transform and generate a new transform execution script that does the following:

create the transform definition using the TransformFunction.GenerateFunction method
select all the documents in the provided table
create an execute transform function

loop over all the documents found

execute the transform on the document
update the document in the table

Optionally perform the execute transform function

Here's what the generated sql looks like:

CREATE OR REPLACE FUNCTION test.mt_transform_get_fullname(doc JSONB) RETURNS JSONB AS $$

  var module = {export: {}};

  // SAMPLE: get_fullname.js
module.exports = function (doc) {
    return {fullname: doc.FirstName + ' ' + doc.LastName};
}
// ENDSAMPLE

  var func = module.exports;

  return func(doc);

$$ LANGUAGE plv8 IMMUTABLE STRICT;

CREATE OR REPLACE FUNCTION test.execute_transform_mt_transform_get_fullname()

RETURNS VOID as $$

  var docs = plv8.execute('select id, data from test.test_table');
  docs.forEach(function(doc) {
    var transformedDoc = plv8.execute('SELECT test.mt_transform_get_fullname($1)', doc.data);
    plv8.execute('UPDATE test.test_table SET data = $1 WHERE id = $2', [transformedDoc[0]["mt_transform_get_fullname"], doc.id]);
  });

$$ LANGUAGE PLV8 IMMUTABLE STRICT;
PERFORM test.execute_transform_mt_transform_get_fullname();

There is also a new method that will generate that sql and pump it into a sql file using the existing SchemaPatch functionality.

@jrios I like the general idea, but can we pull this off w/ two functions, or a function and a straight up sql command:

A PLV8 transformation function
A 2nd command that does a set data = function(data) update?

I'm a tad concerned about the performance by doing the looping within plv8

yeah, the looping isn't great. There's probably a better way to approach the update part of this because it will chug on large data sets.

What do you think about approaching the updates with something like this? See number 7

I can buy that. Do you want something that generates that from a call like:
var script = store.Advanced.WriteTransformScriptFor<TDocument>(string transformName);

We could have that script contain both the plv8 function to do the transformation & a separate func or block that did the batch migration recipe from that blog post.

I like putting it into the AdvancedOptions class. I'm going to see what I can do to get the batch updating working.

Guessing this one never gets done.


Remove progress bar and verbose output during GIF creation

During the creation of gifs, progress bars and other verbose output are displayed in the terminal. This will break the look of whatever else we want to print during training, typically some nice table of training progress.
This unwanted output is a product of moviepy. I have created a moviepy pull request to make this output optional. If this is merged in, then perhaps we can consider changing
clip.write_gif(filename, verbose=True)

To
clip.write_gif(filename, verbose=False, progress_bar=False)

in tensorboardX/summary.py.

I have been thinking about how we could remain backwards compatible for people who haven't got the latest moviepy. One simple option could be:
try:
    clip.write_gif(filename, verbose=False, progress_bar=False)
except TypeError:
    clip.write_gif(filename, verbose=False)

yes, please send a PR~


Update StyleGuidelines.md

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Task list

[x] This PR changes documentation
[ ] This PR changes DscResource.Template

[ ] Updated documentation as necessary in the TEMPLATE_README.md.
[ ] An descriptive entry has been added to the change log
in the TEMPLATE_README.md.

[ ] This PR changes Tests.Template

[ ] The template version number has been increased appropriately.
[ ] An descriptive entry has been added to the CHANGELOG.md under the
Tests.Template folder.

This change is

@kwirkykat - any chance you could merge this one if you get a moment?


corrected some gramatical errors

Why:
Closes [issue link]

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

@Developer-Dennis Thanks for opening a PR! However, we are satisfied with the current wording and what it communicates, so we are not going to accept this change 💛
Please take a look at our help wanted section to find open issues you can work on.
Thanks for your interest in and passion for improving the docs!


I want to connect DBeaver PostgreSQL to excel, as an ODBC driver, to upload a table onto excel

System information:

Windows 10
7.20

Connection specification:

Database name and version

Describe your question:
https://www.devart.com/odbc/postgresql/docs/excel.htm
From the looks of this tutorial, I would need the driver, the server, and the database. The database is pretty self-explanatory - could you please clarify where I would find the information for the other 2 items on DBeaver?

You can export a table in Excel format using DBeaver. For this:

Open Help>Install new software...
Enter in work with field DBeaver Office integration - https://dbeaver.io/update/office/latest/
Go through the wizard to install the extension
Export a table in Excel format.

Will it cover your needs?


Create a slider for these blocks and adjust the padding of the 'Learn More' button.

@Vin205  can you please assign me this task?


[Hotfix] Fix zwave helper getter not to fail on some None results.

Description:
Fix zwave helper getter not to fail on some None results.

Out of curiosity, what device failed? As I don't have that much devices it's impossible to test for all.

Danalock V1
It calls get_value, but there is no matching index.

cherry-picked


Use a different query to detect all graphs

SELECT ?G
WHERE {
 GRAPH ?G {}
}

I see that RDF4j and virtuoso do not implement this. On the other hand I am not sure this is actually valid.
{} creates a binding with no variables set. ?G would therefore be unset and we should not have a result.

I am absolutely sure that it is valid.
The graph pattern GRAPH ?G subpattern is evaluated by iterating over all graphs in a dataset (see https://www.w3.org/TR/sparql11-query/#defn_evalGraph):
Let R be the empty multiset
foreach IRI g in 'set of graph IRIs':
   R := Union(R, Join( 'solutions of the subpattern in graph g' , Ω(?G->g) )
the result is R

The group pattern {} matches any graph (including the empty graph) with one solution that does not bind any variables (see https://www.w3.org/TR/sparql11-query/#emptyGroupPattern).
Thus, the pattern GRAPH ?G {} should detect all graphs in the dataset.
Unfortunately, it is true that many implementations evaluate GRAPH patterns in violation of the specification. For example, for the following query:
select ?g where {
  graph ?g {
    bind (<non_graph_iri> as ?g)
  }
}

Virtuoso returns this result:

?g

<non_graph_iri>

However, there is no graph whose IRI is <non_graph_iri> in the dataset queried!

This is probably a good approach, but its implementation is probably not a priority. IDSM evaluates SELECT DISTINCT ?G WHERE { GRAPH ?G { ?S ?P ?O } } in about 40 seconds. In contrast, it evaluates SELECT ?G WHERE { GRAPH ?G {} } in about 0.2 seconds. This is quite a big difference, but given how long VoID statistics take to generate, the difference is actually negligible.

@galgonek as this was so trivial, I just did it :)


WIP: Make CoreCLR work

Don't merge, I have no Idea what I'm doing :)
See https://github.com/fsharp/FAKE/pull/1281

@ncave - Could you take a look please?

The last commit is not needed... I think it will come with the next visualfsharp merge:
https://github.com/fsharp/FSharp.Compiler.Service/blob/master/src/absil/ilreflect.fs#L1184
vs
https://github.com/Microsoft/visualfsharp/blob/29354edbf0cfb67bc59d9b3d1aaac114bca43ef5/src/absil/ilreflect.fs#L1177
Will clean this up later.

@KevinRansom @dsyme As this commit makes changes in reshapedmsbuild.fs, and RTM is just around the corner, what is the longer term plan, is reshapedmsbuild going to go away and be replaces with msbuild references?

@matthid We've now integrated all the changes from visualfsharp.  Could you merge with master and update the PR please?  Thanks

I guess you were faster :)


Property de-duplication in @font-face produces semantically different CSS (Disregard; fixed in 2.3.10)

This report can be ignored; under v2.3.10 this bug does not reproduce anymore
Given is the following input CSS, which uses linked font-family styles for all browsers that support the full @font-face syntax and falls back to faux-bold (note use of the regular font-face) for IE8 and below:
@font-face {
	font-family : 'Open Sans';
	src         : url('../fonts/opensans-regular.eot');
	src         : url('../fonts/opensans-regular.eot?#iefix') format('eot'),
	              url('../fonts/opensans-regular.woff') format('woff'),
	              url('../fonts/opensans-regular.ttf') format('truetype');
	font-weight : normal;
	font-style  : normal;
}

@font-face {
	font-family : 'Open Sans';
	src         : url('../fonts/opensans-regular.eot');
	src         : url('../fonts/opensans-regular?#iefix') format('eot'),
	              url('../fonts/opensans-bold.woff') format('woff'),
	              url('../fonts/opensans-bold.ttf') format('truetype');
	font-weight : bold;
	font-style  : normal;
}

When processed by CleanCSS (v 3.2.4), even with the --compatibility=ie8 flag, it will produce the following output CSS (reformatted for readability). Note that the rules related to the .eot file format are removed from the set's second block.
@font-face{
	font-family:'Open Sans';
	src:url(../fonts/opensans-regular.eot);
	src:
		url(../fonts/opensans-regular.eot?#iefix) format('eot'),
		url(../fonts/opensans-regular.woff) format('woff'),
		url(../fonts/opensans-regular.ttf) format('truetype');
	font-weight:400;
	font-style:normal
}

@font-face{
	font-family:'Open Sans';
	src:
		url(../fonts/opensans-bold.woff) format('woff'),
		url(../fonts/opensans-bold.ttf) format('truetype');
	font-weight:700;
	font-style:normal
}

Not only is this semantically different CSS, it completely breaks the pattern used to service IE8 and below.
Said pattern ensures IE8 and below, which does not support the format() qualifier gets served an .eot file, while everything else gets whatever supported format is first encountered while going through the list.
Said pattern also protects against a well-known problem with parsing src URLs in @font-face blocks. IE8 and below will treat everything up to the next encountered character-sequence ); as the URL.
As IE8 and below do not support the format() qualifier and also do not load fonts on first use (but rather the moment the definitions are parsed) they will always fetch broken URLs. In my case URLS of the form:
/fonts/opensans-bold.woff) format("woff"), url(../fonts/opensans-bold.ttf) format("truetype"
(For a touch of the truly bizarre: yes; IE's parser does appear to rewrite the single quotes to double quotes inside the unsupported format() qualifiers...)
IE8 and below will also fetch these URLs on each and every page load as the URLs in question will 404 and that result will never be cached but be retried until the end of days.
This is an extremely nasty issue. I am somewhat surprised no-one has noticed this; atleast I don't seem to see this as a resolved issue anywhere.
Will test with more current version as well...
[EDIT]
Seems to be fixed with 2.3.10.

@rjgotten Thank for a detailed bug report! I've just tested locally and here's the output I got:
@font-face{
  font-family:'Open Sans';
  src:url(../fonts/opensans-regular.eot);
  src:url(../fonts/opensans-regular.eot?#iefix) format('eot'),url(../fonts/opensans-regular.woff) format('woff'),url(../fonts/opensans-regular.ttf) format('truetype');
  font-weight:400;
  font-style:normal
}
@font-face{
  font-family:'Open Sans';
  src:url(../fonts/opensans-regular.eot);
  src:url(../fonts/opensans-regular?#iefix) format('eot'),url(../fonts/opensans-bold.woff) format('woff'),url(../fonts/opensans-bold.ttf) format('truetype');
  font-weight:700;
  font-style:normal
}

That's on 3.2.4 and it's the same on 3.2.10.
Would you be able to share a larger excerpt from your CSS source?

Hi. Maybe this is something related to behavior triggered with other configuration flags?
It should reproduce in 3.2.4 with the --s0 --advanced --compatibility=ie8 flags.

I'll give it a try again.

@rjgotten Sorry for a little delay - I still can't replicate it neither with 3.2.4 or 3.3.1 even with options you provided. If you still experience it with 3.3.1 then please reopen the issue.


Add option for shared library. Update -DTRACY_ENABLE option flag

Closes #693 and #714
Added option for shared library. Pass -Dshared=true to build ztracy as a shared library.
Now passing -DTRACY_ENABLE only if the option was specified.

Thanks!


Docs for await in Promise should include a way to watch for broken promises

Since await $p1, $p2 will throw if any of the Promises were broken, we should show an example of how to check for broken promises and fetch the results for kept promises, even if some were broken.
It seems the idiomatic way is to use await Promise.allof( $p1, $p2 ), but currently that will throw if any of the promises is broken. jnthn++ believes that's a bug. See this conversation: http://irclog.perlgeek.de/perl6/2015-11-23#i_11585114
Once the bug  is resolved, the docs should be updated to include correct handling of broken promises, something akin to this, except with Promise.allof() instead of eager:
my $p1 = start die "I'm dead";
my $p2 = start "I'm alive";
try eager await $p1, $p2;
say .result for grep { .status ~~ 'Kept'}, $p1, $p2;

It seems like the bug was fixed? See http://irclog.perlgeek.de/perl6/2016-07-01#i_12770142

There's already a good example in .allof, so I'll close this.


Bookstack Shelves Update - Given Data is Invalid

Describe the Bug
Hello,
I am trying to use the APIs to update shelf books. Unfortunately, I keep getting the following error:
{
    "error": {
        "message": "The given data was invalid.",
        "validation": {
            "tags": [
                "The tags must be an array."
            ]
        },
        "code": 422
    }
}

I'm following the example request given:
https://demo.bookstackapp.com/api/docs#shelves-update
Steps to Reproduce

I've used Postman and Python to test. Python code:

import requests
example_request = {"books": [247]}
auth = "Authorization": "Token token_id:token_secret"
test = requests.post(app_url + '/api/shelves/' + shelve_id, headers=auth, params=example_request)
print(test.text)

Note: The app URL is an example of the request I sent to my Bookstack instance.
2. I've tried the example request sending "[5, 1, 3]" and playing around with the result although I always seem to get the same response,
Expected Behaviour
I expect to see something similar to the example response:
https://demo.bookstackapp.com/api/docs#shelves-update
{
  "id": 14,
  "name": "My updated shelf",
  "slug": "my-updated-shelf",
  "description": "This is my update shelf with some books",
  "created_by": 1,
  "updated_by": 1,
  "owned_by": 1,
  "created_at": "2020-04-10T13:24:09.000000Z",
  "updated_at": "2020-04-10T13:48:22.000000Z"
}

Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
v22.06.2
PHP Version
No response
Hosting Environment
Ubuntu 22.04, using the Docker script provided:
https://hub.docker.com/r/linuxserver/bookstack

Hi @stephencovell,
I'm assuming you're getting caught in the validation for a different endpoint here which is confusing matters.
The shelves-update endpoint is a PUT endpoint, your code is performing a POST request currently.
Additionally, if following the API docs examples, you may better off using json=, described in the requests docs here instead of sending data as query params.
To summarize, this line change should apply both of the required changes:
test = requests.put(app_url + '/api/shelves/' + shelve_id, headers=auth, json=example_request)

Hi,
Thank you for your quick response.
I apologise for putting the POST request, I meant PUT... I copied the wrong code whilst trying to make code for the "snippets to reproduce".
Updating the line works.
Kind Regards,
Stephen Covell

Cool! Will therefore close this off.