Gem::Version raising ArgumentError for weirdly versioned Jenkins plugins...

Hi there,
we ran into the same issue with a dependency (jquery 1.7.2-1) upon installation of the build-pipeline-plugin. This fix addresses the issue around Gem::Version in both :install (covered in @autodesk-azepeda's PR) as well as install_plugin_from_update_center in the plugin library (which was not covered).
Do let me know if you have any further questions or remarks - thanks in advance for merging this in!
Kind regards,
David

I pulled this and tested it, works well on my end.

Thanks for your feedback Adam - hope this PR can get merged soon...
Kind regards,
David

Thanks for merging this PR!
Kind regards,
David


Adding support for Azure OpenAI Deployment Types (Global Standard, Standard, Provisioned)

Purpose
This PR add support for Azure OpenAI Deployment Types: Global Standard, Standard, and Provisioned. The default deployment type remains Standard.
Does this introduce a breaking change?
When developers merge from main and run the server, azd up, or azd deploy, will this produce an error?
If you're not sure, try it out on an old environment.
[ ] Yes
[X] No

Does this require changes to learn.microsoft.com docs?
This repository is referenced by this tutorial
which includes deployment, settings and usage instructions. If text or screenshot need to change in the tutorial,
check the box below and notify the tutorial author. A Microsoft employee can do this for you if you're an external contributor.
[ ] Yes
[X ] No

Type of change
[ ] Bugfix
[X ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

Code quality checklist
See CONTRIBUTING.md for more details.

[ ] The current tests all pass (python -m pytest).
[ ] I added tests that prove my fix is effective or that my feature works
[ ] I ran python -m pytest --cov to verify 100% coverage of added lines
[ ] I ran python -m mypy to check for type errors
[ ] I either used the pre-commit hooks or ran ruff and black manually on my code.

Thanks Zed! We actually are hoping to be able to default to GlobalStandard in the future, so this helps set us up for that. What about adding the sku name for the embedding deployment and vision deployment as well? I would think that if you need GlobalStandard for one, you'd need it for the others?

@zedhaque Yes please make those configurable as well.

I did an "azd up" from this branch on an existing environment, and that went fine, so it looks like this doesn't introduce any backwards incompatibility issues. I'll merge once CI completes.
Thanks @zedhaque !

Is there any documentation on how to deploy a provisioned Model after this merge? Thanks. :)

Thank you so much, I had overlooked that while researching!


Failed to download image

Just tried the latest release, all was fine, but it failed to download the image
This line appears to be incorrect: $(dirname "$0")/../ht"
Logs are as follows:
Partial screen refresh
eips: paint_image> cannot open "./dash.png":can't fopen
Going to suspend, next wakeup in s
Wed May 25 12:06:42 UTC 2022 Battery level: 97%.
./dash.sh: line 111: ./next-wakeup: Permission denied
sh: 3600: unknown operand
Refreshing dashboard
Wi-Fi connected
./local/fetch-dashboard.sh: line 4: ./local/../ht: not found
Partial screen refresh
eips: paint_image> cannot open "./dash.png":can't fopen```

Equally, if I move ht folder to some other place in the directory structure I get line 4: local/../ht: Permission denied

Hi, I'm having the same issue - did you manage to fix this? I'm on a Kindle 4

Ensure the images is coming from http a non secure location. HTTPS isn't available on the Linux build of kindle 4

Hi sorry for my late reply. I'll try to look into this later this week. It seems to be a file permissions issue.
Btw HTTPS should work. The HTTP client (ht) uses rusttls with bundled root certificates.

cool, this is now working perfectly with a github pages HTTPS page  - I think my error was because I had failed to make one of my files executable
Thanks so much for your code @pascalw !!

@iantearle @floftus-at-csm I've looked into this and indeed it seems this must be related to (some of the files) somehow missing the executable bit in your case. I've checked the last release however and the tarball does have the right permissions set on the files. Do you remember how you've extracted the tarball and copied it to the Kindle?

Btw HTTPS should work. The HTTP client (ht) uses rusttls with bundled root certificates.

In my case the image download doesn't fail for permission issues, but for xh somehow not being able to parse the system certificates file.
I found curl working very well on my Kindle PW Touch for https links, and it should be a pretty standard utility, present almost everywhere, so I filed a pull request with this and another fix to make it work on PW Touch.
Thank you for this great piece of software!

Hi there, I've come back to this and am attempting to run kindle-dash via KUAL. I am consistently getting this error in my logs
xh: error: builder error: Could not load PEM file "/etc/ssl/certs/ca-certificates.crt" Caused by:     Could not load PEM file "/etc/ssl/certs/ca-certificates.crt" Not updating screen, fetch-dashboard returned 1
I am on a Kindle 4
Do you know how to get around this?
The url I am attempting to get is an HTTPS url, the same as I was using before

Yes, it's exactly the problem I was talking about. You should try to use curl. You may want to try my fork or wait for it to be merged. https://github.com/penguin86/kindle-dash
Sorry for the lack of details, but I'm currently away from my computer.

@floftus-at-csm which Kindle model are you using? On my kindle 4 NT I do have a system certificate bundle at /etc/ssl/certs/ca-certificates.crt. I guess that other models might not have this?
The reason that I provide the xh http client is that curl and wget on the kindle 4 NT are too old to communicate with modern HTTPS endpoints. If you have a newer kindle then the built-in curl might work for you. In that case you can just modify fetch-dashboard.sh to use curl instead of xh.
Thinking about this now it might make sense for kindle-dash to include a recent set of root certificates. xh can be compiled with root certificates built into the binary. That's pretty useful given that most kindles that are used for this purpose are old and don't receive updates anymore.

hey, thanks both for your response - I have tried to use the CURL solution but this gives me the error you predicted @pascalw
curl: (35) error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version Not updating screen, fetch-dashboard returned 35
This is on a Kindle 4 (version 4.1.2)
If you could compile xh with root certificates at some point that would be amazing :)

I can confirm my kindle is slightly newer, it's a Paperwhite Touch. I've seen it referred also as "Kindle 5" somewhere. On mine, unfortunately xh does fail with error Could not load PEM file "/etc/ssl/certs/ca-certificates.crt". The file exists and, as long as I can see, is readable.

@floftus-at-csm or @penguin86 could you try if the attached xh build works for you?
xh.zip

Unfortunately I still get the same error with this build
`xh: error: builder error: Could not load PEM file "/etc/ssl/certs/ca-certificates.crt"
Caused by:
Could not load PEM file "/etc/ssl/certs/ca-certificates.crt"`
However! I went back to the ht method from kindle-dash-1.0.0-beta.3 and it worked - images downloaded from an HTTPS url no problem

Humm that's interesting. I guess it might be a bug in xh then. I don't have much time to dive into it now unfortunately, maybe I'll have another look later. It's a bit difficult since I can't reproduce this myself on my kindles.

Hi @pascalw, thanks a lot for creating this dashboard. Your Kindle firmware might be the reason why you couldn't reproduce this error.
Kindle-dash was working without issues for my K4 on firmware 4.1.4, but since I downgraded to 4.1.1 using the Kubrick tool, I also receive the error Could not load PEM file "/etc/ssl/certs/ca-certificates.crt".
As @floftus-at-csm mentioned, reverting to kindle-dash-1.0.0-beta.3 does indeed seem to solve this problem.

@infinitewhileloop my devices are on 4.1.3 and 4.1.4, so indeed that might explain why I can't reproduce the issue.
I might downgrade one of my devices later if I have some time, to debug this issue.
Can I ask why you would downgrade to 4.1.1?

I downgraded the firmware because I was unable to install KUAL, due to the This device is not authorized as a test Kindle by the developer of this item. error. A MobileRead user suggested to downgrade the firmware using Kubrick. Getting Kubrick to work was quite complicated, I needed an ancient laptop to boot from their live USB.

I found a workaround for the error
`xh: error: builder error: Could not load PEM file "/etc/ssl/certs/ca-certificates.crt"
Caused by:
Could not load PEM file "/etc/ssl/certs/ca-certificates.crt"`
Upload the file /etc/ssl/certs/ca-certificates.crt from a more up-to-date linux to the kindle and use the --verify option in xh.
For example: "$(dirname "$0")/../xh" --verify "$(dirname "$0")/../ca-certificates.crt" -d -q -o "$1" get https://raw.githubusercontent.com/pascalw/kindle-dash/master/example/example.png

I found a workaround for the error
xh: error: builder error: Could not load PEM file "/etc/ssl/certs/ca-certificates.crt"

Caused by:
Could not load PEM file "/etc/ssl/certs/ca-certificates.crt"

Upload the file /etc/ssl/certs/ca-certificates.crt from a more up-to-date linux to the kindle and use the --verify option in xh. For example: "$(dirname "$0")/../xh" --verify "$(dirname "$0")/../ca-certificates.crt" -d -q -o "$1" get https://raw.githubusercontent.com/pascalw/kindle-dash/master/example/example.png

Hi - where did you get a working crt file from? Could you paste a link? Thanks!

I found a newer crt file, but how do you overwrite it?
mv: overwrite './ca-certificates.crt'? y
mv: cannot remove './ca-certificates.crt': Read-only file system

Actually, I realised that even when you specify http github is forcing https (maybe a redirect?)
I downloaded your image and hosted it on server where http is permitted and dashboard works fine

I got the file from another up-to-date Linux system.
You don't have to overwrite the file /etc/ssl/certs/ca-certificates.crt. Just save the new certificate file wherever possible and link it in the xh-command as shown in my example.

Hey sorry for my lack of participation in this thread. Good that we have a workaround available for older FW versions.
I think a nice solution could be to include certificates in the xh binary. This seems to be supported by reqwest which is the underlying http client used in xh. It's however not directly supported by xh it seems, but should be quite simple to do. I don't have time currently to look into this, so if anyone else would be willing to look into that, that would be awesome!


bitcoind: WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting

Error in the bitcoind debug.log:
sudo tail -n 20 /mnt/hdd/bitcoin/debug.log

WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting

Error in JoinMarket:
[ERROR]  Failure of RPC connection to Bitcoin Core. Application cannot continue, shutting down.
[ERROR]  Critical error updating blockheight.

Error in Specter:
Server error!
Exception: Server responded with error code 500: Work queue depth exceeded

Details:

Traceback (most recent call last):
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask/app.py", line 1950, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask/app.py", line 1936, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask_login/utils.py", line 272, in decorated_view
    return func(*args, **kwargs)
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/controller.py", line 1164, in wallet_receive
    wallet.check_unused()
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/wallet.py", line 105, in check_unused
    while self.rpc.getreceivedbyaddress(addr, 0) != 0:
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/rpc.py", line 308, in fn
    r = self.multi([(method, *args)], **kwargs)[0]
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/rpc.py", line 301, in multi
    "Server responded with error code %d: %s" % (r.status_code, r.text), r
cryptoadvance.specter.rpc.RpcError: Server responded with error code 500: Work queue depth exceeded

Mentions:
https://github.com/bitpay/bitcore-node/issues/463#issuecomment-269063216
https://github.com/zkSNACKs/WalletWasabi/pull/3056
Solution:
setting:
rpcworkqueue=64

in the bitcoin.conf (default is 16) and will monitor.
EDIT: same issue with rpcworkqueue=64
Increased to: rpcworkqueue=100
Note the extreme usecase with many services connecting to the JSON-RPC:
24 wallets active in Specter
2 JM YieldGenerators running
LND

It seems to be caused by Specter querying all the monitored addresses at the same time.
Problematic since LND might miss some onchain action while the JSONRPC is flooded.
Good news is that @stepansnigirev is already working in the solution for a future release of Specter: https://github.com/cryptoadvance/specter-desktop/pull/588

Putting this on the v1.7 milestone as a reminder to revist this then.

One more PR to Specter-Desktop that reduced number of RPC calls:
https://github.com/cryptoadvance/specter-desktop/pull/631
We plan a release tomorrow.

Created issue to update Specter for v1.6.2 release #1793 ... but will keep this issue listed for v1.7 to check if this is still an issue by then.

This is not coming up any more when importing and scanning for 20 wallets in Specter v0.10.4.
JM and LND with 30+ channels running using a 64 bit blitz with the latest scripts.
Closing. To be reopened if the issue surfaces again.

This is not coming up any more when importing and scanning for 20 wallets in Specter v0.10.4.
JM and LND with 30+ channels running using a 64 bit blitz with the latest scripts.
Closing. To be reopened if the issue surfaces again.

With the upgrade to version 1.9 this happend to me again. I checked the logs and got a massive amount of
WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting

In my bitcoin.conf file I could not find any information regarding the rpcworkqueue so I added that and restarted the node. Hopefully it works now again and syncs the last %.

@openoms
For rpcworkqueue, is the number how many CPU threads the wallet will use?
Trying to find documentation on what the number represents, which led me to this thread.

For rpcworkqueue, is the number how many CPU threads the wallet will use?
Trying to find documentation on what the number represents, which led me to this thread.

It is the threads offered by bitcoind forbapps connected through the RPC interface, not the internal wallet.


ND4S: Unit test failure on CUDA

2 tests in ND4S are currently failing on CUDA (look like the same thing)
Looks like maybe a simple datatype issue, but that should not be backend specific...
NDArrayExtractionInCOrderingTest:
num2Scalar
- should convert number to Scalar INDArray *** FAILED ***
  [1] did not equal [1] (NDArrayExtractionTest.scala:321)

NDArrayExtractionInFortranOrderingTest:
num2Scalar
- should convert number to Scalar INDArray *** FAILED ***
  [1] did not equal [1] (NDArrayExtractionTest.scala:321)

Reproducible using:
cd nd4s
mvn clean test -Ptestresources -Ptest-nd4j-cuda-10.2

Fixed in branch.

Fix merged.


Social login buttons not showing up with adblock

I just posted a question on Stackoverflow and the answer showed a weird behavior:

"Its a bit weird but it looks like while Meteor is unminified it blocks anything with facebook or twitter in its url such as the facebook/twitter packages' js code."

PS. I am not sure if this is the right place to report this.

Hi @niranjans!
...yes this is a good place, but pherhaps it would be better to open issues non specific to a particular fromnt-end in the issue tracker for the core repo.
This sounds weird to me (I'm developing under linux) because I used to get many different OAuth providers work without any problem!
...I've just read on SO that you somehow solved it: is this correct?
Which browser are you testing it on?
We might report this problem within the documentation as a known bug in case we can confirm it.
Let me know!

Hi @splendido
Yes, the problem was solved. It was just a very trivial solution - Disabling Adblock Plus for localhost. Everything works fine once that is disabled. This had me stumped for hours though.
Initially I thought this was a system specific problem but I realized this problem is only on my Chrome browser with the AdBLock Plus plugin (on Linux Mint 17).
Maybe UserAccounts is pulling something that is in the block list? But again, this does not happen on other browsers or even chrome on a Mac system.
Thanks,
Niranjan

Ok, but lets keep an eye on this.
I'd like to have some warning about these kind of problems among the docs in case it's a general case.
Thank you!

I'm running into something similer, I did test it in a different bowser still not seeing the social login https://github.com/meteor-useraccounts/core/issues/553


Niobium Mine Fluid Box location

Mod source
Factorio Mod Portal
Operating system

=Windows 10

What kind of issue is this?

[ ] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[ ] Pypostprocessing failure
[X] Other

What is the problem?
Location of the Fluidbox of the niobium mine does not match the actual location.

Did work before (1.1 migrated save)
Steps to reproduce

Place niobium mine
Observe mismatching locations

Additional context
No response
Log file
No response

fixed in pycp 3.0.21


Add eslint-formatter-git-log

Thanks for maintaining this list @dustinspecker 🤜💥🤛
I'd like to add https://github.com/JamieMason/eslint-formatter-git-log please.

Thank you!


[V3 Scheduler] Cancel task from [p]showscheduled menu

Like in title, I think it would be useful to be able to cancel/unschedule task from the menu which shows when you use [p]showscheduled or [p]scheduleradmin viewall:

Blocked by #122


MongoDB Source

As a user, I'd like to have a MongoDB source so that changes to documents in MongoDB can be replicated to other systems.
Properties:

URI: URI to Mongo e.g. mongodb://localhost/
namespace: the collection to monitor
tail: boolean indicating if the source needs to be tailed on an ongoing basis

Acceptance:

MongoDB source module is available in spring repo
supported properties are documented in the reference guide
On first start the source should read all the documents and stream them
When tail is specified the source keeps running and monitor the opslog

Background
MongoDB provides a feature called oplog. This feature allows for Async replication of data in a MongoDB instance. However, it can also be used to monitor database changes (new/changes to documents)
Here are some examples of what others have done in this area.
https://www.compose.io/articles/continuously-synchronize-your-mongodb-data-to-elasticsearch/
https://github.com/compose/transporter

This is now addressed via spring-cloud/spring-cloud-stream-app-starters#113.


Allow comments inside a tag

allow comments inside a tag.
It is regarding this part of comment: @*CssClass="app-sidebar"*@
This is impossible:
<DxTreeView AllowSelectNodes="true" @*CssClass="app-sidebar"*@
                    AnimationType="LayoutAnimationType.Slide">`

This works but you have to move the code out of the tag and comment it:
@*CssClass="app-sidebar"*@
         <DxTreeView AllowSelectNodes="true"
                    AnimationType="LayoutAnimationType.Slide">`

Could save some time to quickly comment something out with Hot Reload in Blazor Server instead of having to move that part out of the tag.

Would also be useful to explain why specific attributes are set the way they are. At my job, we have some monster components with dozens of attributes, this feature would be very useful.


Not WORKING!!!!

Just waste of time, Not working!!!

PASSWORD_LOGIN_DISABLED error I get When I click the Login button.

Go to your app in firebase
Authentication -> enable -> email & password login.
it will work.


suggestion roblox luac compadiblity

due to roblox complience it also cant use these functions:
Obscuring engine features within scripts, including LuaVMs, getfenv(), and setfenv().
Requiring remote assets, including require(assetId), loadstring(), InsertService:LoadAsset(), and ModuleScript.LinkedSource. Assets that may look useful on the surface could load another "virus" asset at runtime.
they also ban obfuscation but their detection is dogshit its just that they delete any script using the functions i list here

could you elaborate on this idea? it would help us understand what you want more accurately

basicly alot of obfuscations use getfenv ir another engine obscuring functions im basicly just asking if you can make focuas develpment on not having the functions i listed in hyperlink blue

no idea what this was supposed to mean


Use Static Functions

Here's a preliminary PR for what we talked about!
Right now I use attributes: […] consistently everywhere, but functions with no content could use _ attributes: Attribute... instead.
.link(attributes: [.href("blob"), .rel(.alternate)])
// vs.
.link(.href("blob"), .rel(.alternate))

We could also add overloads to accept .async wherever booleans like .async(true) work.

Gonna merge for now! Can make future adjustments before any official release.


Added CROWD_PROXY_SECURE to allow secure cookies.

The //Connector-Element needs the secure="true" attribute to allow Crowd Secure SSO cookie feature (see: SSO Cookie ).

Thank you! Would you be so nice and add an example with explaination in the Readme?

Looks wonderful! Thank you for your contribution!


TypeScript language features frequently dying on large project

Issue Type: Bug
I work on our largest TypeScript project at Shopify (a node + React application). The project has about 6000 source files (I am not sure if this is uncommon, but we have to run tsc with more memory to avoid a dedicated type check process running out of memory). Many developers working on the project report frequent cases where editor functionality like autocomplete, go to definition, and in-editor type feedback dissapear. This happens across a range of different setups (different versions, regular and insider, different sets of extensions).
Are there steps we can take to mitigate this? I am happy to give any other details that would help diagnose, as well as provide more detailed logs, if it would be useful.
 The TypeScript team should better know what type of information would be helpful to investigate this.
Some quick questions: what version of TypeScript are you using? Are developers using a workspace version of typescript in VS Code?

When you run tsc with --diagnostics, what's the output?

Thanks @mjbvz. Yes, developers are using a workspace version of TypeScript in VSCode. We're currently a bit behind on the TS version side of things: we're at 3.1.6. Updating isn't super trivial but I can go through with it if you feel there are changes that might help, but I have experienced the same issues locally when testing out TS 3.2.x as well.
@AnyhowStep here is the output (I need to run it with a bit more heap, otherwise I OOM before type checking completes):
$ node --max-old-space-size=2000 ./node_modules/.bin/tsc --noEmit --diagnostics
Files:           7932
Lines:         814763
Nodes:        3113440
Identifiers:   997351
Symbols:      1627426
Types:         785025
Memory used: 1752701K
I/O read:       0.51s
I/O write:      0.00s
Parse time:    12.42s
Bind time:      1.89s
Check time:    32.02s
Emit time:      0.00s
Total time:    46.33s

Yes please test using the latest TypeScript version 3.4.5 in workspace. This ships as the bundled version the current VS Code insiders build. You don't have to change the typescript version you are using to compile the project

I get OOM's, too, with some projects. I've had moments where type checking would take me 15+ minutes!
I've also had to wrestle with long check times, OOM's, and other weird compile issues for a while now.
The TS team can help you better but I figured I'd throw in my anecdotes that may (or may not) help you.

For one of my projects, when I run,
find . -type f | sed 's/.*\.//' | sort | uniq -c,
I get,
  11 md
2010 ts

What do you get when you run that command on your source folder?

And my diagnostics with --noEmit --diagnostics,
Files:           5178
Lines:         453729
Nodes:        1811212
Identifiers:   626016
Symbols:      2127140
Types:         513976
Memory used: 2092972K
I/O read:       0.25s
I/O write:      0.00s
Parse time:     3.99s
Bind time:      1.15s
Check time:    45.58s
Emit time:      0.00s
Total time:    50.71s

I'd say my project is really heavy on generics, conditional types, type trickery, etc.
And that definitely adds to the long check times.
I've had cases where simply changing a class method to a non-class function dramatically sped up check times (Don't ask me why that worked). So, the solution is not always intuitive.
Does your project have a lot of that? Or does it use any libraries that tend to be heavy with type manipulations?
What are your dependencies, and dev dependencies?

One thing that jumps out at me is that your parse time is 12.42s. That's really long for just parsing.
How many lines of code is your project?
When I run,
find . -name '*.ts' -o -name '*.tsx'  | xargs wc -l

I get,
/*snip*/
66187 total

I'm closing this issue as it is out of date.
If you are seeing performance issue when using current versions of TypeScript, please open a new issue so that we can investigate


Support ignoring some files on upload

Hi! I thought it would be a good feature to support ignoring some files and directories that are zipped up and uploaded. For example, node_modules or src directories that are no longer used by the extension after a build step.

At the moment you just need to put everything into a folder. This also helps you automatically keep all extraneous files out — do you really want to exclude allll your config files explicitly?
At most we could automatically exclude what appears in .gitignore

Hmm, my workspace is a bit different. The folder is the repo. And one of the dependencies is something I'm working on that I have symlinked to my extension while I'm working on both.
I guess for now I can unlink it before I publish.

I don't really want to implement/support this logic here. If you want anything more than "zip this whole folder" you can use another archive tool and then pass the output to chrome-webstore-upload-cli
It would look something like:
7z ./ a.zip --exclude node_modules && chrome-webstore-upload upload --auto-publish

I don't really want to implement/support this logic here. If you want anything more than "zip this whole folder" you can use another archive tool and then pass the output to chrome-webstore-upload-cli
It would look something like:
7z a ./ a.zip --exclude node_modules && chrome-webstore-upload upload --auto-publish

Why though? web-ext has it. My code is like this right now. That folder contains Adobe Illustrator files. Only needed for developement. It's not a mandatory thing but could be useful.
- name: Chrome
  env:
    EXTENSION_ID: ${{ secrets.CHROME_EXTENSION_ID }}
    CLIENT_ID: ${{ secrets.CHROME_CLIENT_ID }}
    CLIENT_SECRET: ${{ secrets.CHROME_CLIENT_SECRET }}
    REFRESH_TOKEN: ${{ secrets.CHROME_REFRESH_TOKEN }}
  run: |
    mkdir -p .builds
    zip -r .builds/ChromeExtension.zip * -x "img/SVG/*"
    npx chrome-webstore-upload-cli@^3 \
      --source .builds/ChromeExtension.zip \
      --extension-id $EXTENSION_ID \
      --client-id $CLIENT_ID \
      --client-secret $CLIENT_SECRET \
      --refresh-token $REFRESH_TOKEN

- name: Firefox
  env:
    WEB_EXT_API_KEY: ${{ secrets.FIREFOX_JWT_ISSUER }}
    WEB_EXT_API_SECRET: ${{ secrets.FIREFOX_JWT_SECRET }}
  run: |
    git checkout firefox
    npx web-ext@^8 sign \
      --ignore-files "img/SVG/**" \
      --channel listed \
      --api-key $WEB_EXT_API_KEY \
      --api-secret $WEB_EXT_API_SECRET

Why though? web-ext has it

web-ext has the whole kitchen sink and I don't want that. Look at the dependency tree: https://npmgraph.js.org/?q=web-ext
Before you know it, someone will ask to support --include just for specific files, then someone opens a bug about excluding sub-files that appear in include and vice versa. This is a solved issue and part of other tools, that can be easily used.
In your case it would be easier to use rm -rf img/SVG in both cases just before calling the tool
	- name: Chrome
	  env:
	    EXTENSION_ID: ${{ secrets.CHROME_EXTENSION_ID }}
	    CLIENT_ID: ${{ secrets.CHROME_CLIENT_ID }}
	    CLIENT_SECRET: ${{ secrets.CHROME_CLIENT_SECRET }}
	    REFRESH_TOKEN: ${{ secrets.CHROME_REFRESH_TOKEN }}
	  run: |
-	    mkdir -p .builds
-	    zip -r .builds/ChromeExtension.zip * -x "img/SVG/*"
+	    rm -rf img/SVG
	    npx chrome-webstore-upload-cli@^3 \
-	      --source .builds/ChromeExtension.zip \
	      --extension-id $EXTENSION_ID \
	      --client-id $CLIENT_ID \
	      --client-secret $CLIENT_SECRET \
	      --refresh-token $REFRESH_TOKEN

	- name: Firefox
	  env:
	    WEB_EXT_API_KEY: ${{ secrets.FIREFOX_JWT_ISSUER }}
	    WEB_EXT_API_SECRET: ${{ secrets.FIREFOX_JWT_SECRET }}
	  run: |
	    git checkout firefox
+	    rm -rf img/SVG
	    npx web-ext@^8 sign \
-	      --ignore-files "img/SVG/**" \
	      --channel listed \
	      --api-key $WEB_EXT_API_KEY \
	      --api-secret $WEB_EXT_API_SECRET

By the way, you don't need to specify those flags:
+	    npx chrome-webstore-upload-cli@3
-	    npx chrome-webstore-upload-cli@^3 \
-	      --source .builds/ChromeExtension.zip \
-	      --extension-id $EXTENSION_ID \
-	      --client-id $CLIENT_ID \
-	      --client-secret $CLIENT_SECRET \
-	      --refresh-token $REFRESH_TOKEN

They've been deprecated and they'll be removed at some point:

#80

It makes a lot more sense now. Thanks for the explanation and the tips.


Fix nack method on frame object

For the NACK method you must specify the destination queue instead of
the subscription id.

I'm digging up an old one here but @jmesnil  or @chepike did you ever get further with this?
I'm on ActiveMQ 5.9.0 and I am having similar issues to others.  I've tried the 8538106 commit and replaced stomp.js from v2.3.3 to no avail.
Below is a snippet of my code - basically it subscribes, successfully gets a message and non-acknowledges all messages, but the message does not stay on the queue.
https://gist.github.com/timgriffin/f541366082e88c52947a121145a8f951
I am connecting over TCP if that makes a difference (var client = Stomp.overTCP(....)).
Any help would be appreciated!


[RELEASE] Operator 6.0.3

Operator v6.0.3 has changes that impact the docs:

[ ] Removes .secrets section from Tenant Helm chart PR #2265

This should be automated.

Automation took care of this.


Date time parsing updates

New ability to parse relative dates if the parsing starts with "in" or has "ago" or "from now" before the optional time zone (or at the end of the string)

LGTM


Log only when previousCuepoint is valid

Signed it.

We're gonna rework the if statements slightly, to make it clearer what's going on, and to share the start time on played cuepoints.


Logitech M570 clicks become unresponsive after application switch

On my MacBook Pro 2012 15", after switching applications, for example clicking on the desktop after having Chrome active, the M570 clicks become un-responsive for 15-20 seconds, occasionally but unreliably registering clicks. The pointer movement still works fine, and using the internal mouse once fixes the problem.

Does this issue still happen in the latest version (Karabiner-Elements v0.90.59)?

Yes, Though it does seem to take less time to start working again. Down to about 5 seconds.

I'm seeing the same issue with my Logitech M705, also working within 5 seconds or so.

Could you ignore the Logitech M570 in Devices tab in Preferences?

That seems to have done it. Thanks.


Fix driver options specified with .options() method being ignored for oracledb dialect

Bug Description
Recently, when working on an application using oracle databse, it became necessary to specify options to the oracle database driver/client on a per-query basis. According to the knex documentation, this is facilitated using the options() method. However, the options provided would not be passed to the oracle database client, even though all options were returned from calling queryBuilder.toSQL().options. In my case, I was supplying the fetchInfo option to oracle, though I would find it's options would not be applied to the query.
The version of the oracle database client node package used was 4.2.x, though the same behavior exists within versions 5.x as they did not alter the API surface dealing with type mappings.
The below example illustrates the expected behavior and the actual behavior:
const knex = require('../path/to/instantiated/knex/import');
const oracledb = require('oracledb');

// NUMERIC_COLUMN is any column in Oracle that has a numeric column type
const result = await knex('TEST_TABLE').select('NUMERIC_COLUMN').options({ fetchInfo: { "NUMERIC_COLUMN": { type: oracledb.STRING } } })

// This returns { fetchInfo: { "NUMERIC_COLUMN": { type: oracledb.STRING } } } as expected
knex('TEST_TABLE').select('NUMERIC_COLUMN').options({ fetchInfo: { "NUMERIC_COLUMN": { type: oracledb.STRING } } }).toSQL().options

// Expected value for result
[
  {
    "NUMERIC_COLUMN": "5"
  }
]

// Actual value for result
[
  {
    "NUMERIC_COLUMN": 5
  }
]

Underlying Cause
After a bit of debugging, I found the cause of the issue to be line 172 in lib/dialects/oracledb/index.js, where a predefined set of options is passed to the oracle client without reading or merging in obj.options, resulting in anything being supplied to .options() on the query builder being ignored when using the oracledb dialect.
Fix Details
The fix was to merge the user-provided options with the set of pre-defined options required by knex (as a bit of digging indicated knex does not support autoCommit on oracle), allowing the pre-defined options to overwrite anything the user may specify. This resulted in the oracle client receiving the expected parameters and the expected return value from the query.
Final Comments
For almost every other dialect, if not all others, proper support for the options() query builder method is working. This seems to suggest that this was unintended behavior. If this is intended behavior, this causes issues for cases where the query result type mapping needs to be altered for a specific query in common conditions detailed here by Oracle (section <IP_ADDRESS> provides a good example). To do this on a per-query basis, this must be done using the fetchInfo option provided to connection.execute() as all other options control this setting on a global level.

Can you add some tests (you can use your example) ?

Coverage remained the same at 92.277% when pulling cf591e79bb7958b92c8ab660caaeb46bd2f4c9fd on ITDeptUtahCountyGovernment:oracledb-options-query into 939d8a219c432a7d7dcb1ed1a79d1e5a4686eafd on knex:master.

@OlivierCavadenti Sure thing. I can write some tests based on my example.

@OlivierCavadenti I've added an integration test based on the example I gave in this PR. It should be ready for review.

Tests fails:
   Error: DPI-1047: Cannot locate a 64-bit Oracle Client library: "libclntsh.so: cannot open shared object file: No such file or directory". See https://oracle.github.io/node-oracledb/INSTALL.html for help
Node-oracledb installation instructions: https://oracle.github.io/node-oracledb/INSTALL.html
You must have 64-bit Oracle Client libraries configured with ldconfig, or in LD_LIBRARY_PATH.
If you do not have Oracle Database on this computer, then install the Instant Client Basic or Basic Light package from
https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html

This is an issue with the Oracle Instant Client not being installed or detected when this test is running. This error gets thrown by the node-oracledb package and is external to the test code. I've seen this one a lot when helping developers setup a new workstation at my workplace. Maybe there is an issue with how the integration2 tests are being run, considering how all oracle tests in integration run queries against oracle without problem. The only reason I can think of as to why it runs fine on my workstation is because I have instant client setup on the machine and its system-level install is always detected by any nodejs app I run.

Just realized that the error was occurring in the non-oracledb tests. Looks like I will need to adjust those test files to make sure that test isn't being run for other DBs.

@OlivierCavadenti or @kibertoad could I get a re-run of the test suite? I've implemented some changes that should resolve the oracle instant client error that was occurring, but I'll want to verify the fix against the CI results.

@Kytech : could you check on this again, please?

@Kytech : could you check on this again, please?

Not really anything else I can do other than wait on that re-review. I'll check and see if the knex maintainers have been doing anything lately and if so, I'll try opening an issue that links this PR to see if that gets better visibility.

@Kytech : could you check on this again, please?

Not really anything else I can do other than wait on that re-review. Knex maintainers seem to have looked over the PRs they have recently, so I'll see if @OlivierCavadenti has anything else they want changed or if the adjustments I made for those failing tests addressed everything needed.

@Kytech : could you check on this again, please?

Not really anything else I can do other than wait on that re-review. Knex maintainers seem to have looked over the PRs they have recently, so I'll see if @OlivierCavadenti has anything else they want changed or if the adjustments I made for those failing tests addressed everything needed.

Yeah, after a long hiatus, I try to reviews as many as I can :D. Sorry for the delay


Access form data and file data

Hi,
thanks for your awesome framework, however i got a question / issue:
How is it possible to access form() data in a request and files() from the request. as both are returning a reference to a multidict: small example:
`fn post_img( r: &mut Request) -> PencilResult {
let mut formvalues = BTreeMap::new();
{
let f = r.form();
for i in f.keys() {
formvalues.insert(i, f.get(i));
}
}
let file = r.files();
for i in file.getlist("data") {
    for j in i {
        let mut ff = File::open(j.path.clone()).unwrap();
        let mut contents: Vec<u8> = Vec::new();
        let data = ff.read_to_end(&mut contents).unwrap();

        let mut fff = File::create("/home/marcom/test.jpg").unwrap();
        fff.write_all(&contents).unwrap();
    }
}
let mut d = BTreeMap::new();
d.insert("status", "ok");
return jsonify(&d);

}
fn main() {
let mut app = Pencil::new("/web/hello");
app.route("/post_img", &[Post], "post_img", post_img);
app.run("<IP_ADDRESS>:9998");
}`
here the compiler complains with the following message:

src/main.rs:73:16: 73:17 error: cannot borrow *r as mutable more than once at a time [E0499]
src/main.rs:73     let file = r.files();
^
src/main.rs:73:16: 73:17 help: run rustc --explain E0499 to see a detailed explanation
src/main.rs:67:17: 67:18 note: previous borrow of *r occurs here; the mutable borrow prevents subsequent moves, borrows, or modification of *r until the borrow ends
src/main.rs:67         let f = r.form();
^
src/main.rs:87:2: 87:2 note: previous borrow ends here
src/main.rs:64 fn post_img( r: &mut Request) -> PencilResult {
...
src/main.rs:87 }

Cheers

by cloning the form data i was able to resolve it. Is this the right way to do?
`fn post_img( r: &mut Request) -> PencilResult {
let f = r.form().clone();
let mut formvalues = BTreeMap::new();
for i in f.keys() {
    formvalues.insert(i, f.get(i));
}
println!("{:?}", formvalues);

let file = r.files();
for i in file.getlist("data") {
    for j in i {
        let mut ff = File::open(j.path.clone()).unwrap();
        let mut contents: Vec<u8> = Vec::new();
        let data = ff.read_to_end(&mut contents).unwrap();

        let mut fff = File::create("/home/marcom/test.jpg").unwrap();
        fff.write_all(&contents).unwrap();
    }
}
let mut d = BTreeMap::new();
d.insert("status", "ok");
return jsonify(&d);

}`

Maybe you can just move the temporary file to the destination.

thanks @fengsp that would maybe a better option... but the question is
if I can use the form values and the files-values without cloning, as both methods:
request.form and request.files are methods with '&mut self' parameter and returning a reference to the multidict.
the removal of the 'mut' in 'fn form(&mut self)' and the files fn would allow the usage of all fields without clone()

Currently you need to clone it if you need it later, in your example, you can use scope to avoid it.  Maybe in the future we will add a method that allows you to consume the form data.

Ok, thanks for the clarification.
Keep up the good work ;) ... will close this issue now.


Server restart at 12AM UTC daily

I am trying to set the server to only restart when no players are connected, and during the early AM hours. Here's what I've set in the ENV variables on my Synology NAS docker config
RESTART_CRON 0 5 * * *
BACKUPS_CRON 0 * * * *
UPDATE_CRON 15 */2 * * *
UPDATE_IF_IDLE true
TZ America/Halifax
Despite the TZ, my local logs are showing UTC, so I just read them as 3 hours ahead of me. The server seems to restart at 00:00, as my logs indicate a rollover at 03:00. This is 11pm for most of my connected players and they are getting upset :)
I can't tell if I am reading your config wrong, because I've set the restart for 5am, which even if it doesn't respect my TZ, would be 2am local time, not midnight.
Also I cannot get the discord webhook to populate. Uncertain if I need to change the Username in the PRE_RESTART_HOOK template. I've created webhooks before so the discord end is set.
Great work on this container, it's running quite well otherwise!

What does date inside the container say?

the logs show UTC time - currently 9:15pm.

I understand that, but the question is what does running the date command inside the container output?
Should be something like Mon Mar 22 05:21:06 ADT 2021 (if properly configured) or Mon Mar 22 08:20:21 UTC 2021 (if not properly configured).

Side note: I just merged https://github.com/lloesche/valheim-server-docker/commit/82c81095301165b286442a1245dddc2bf6002f7e which makes it so that the daily restart by default is only performed when no players are connected. So if you pull the latest version of the image your disconnection problem will be gone.
We should still figure out why the time zone is off in your container.

Sorry about that, yes, running date in an executed container shows ADT correctly
Mon Mar 22 12:50:03 ADT 2021
I don't mind the TZ being off so long as the server isn't rebooting during connections. thanks!

It seems the docker container continues to restart at 12AM UTC (3AM local time). It did so when I set the update_if_idle flag to true, and also when I subsequently set restart_cron to blank, attempting to disable the restart entirely. I'm likely going to blow the container away and try again, as I have no idea what might be causing this. No other containers have this behaviour and I am keeping this one updated as all others via watchtower. thanks for your help.

@mixm1xmix setting RESTART_CRON blank should turn off any restarts. You can confirm by running
$ docker exec -it valheim-server crontab -l
0 * * * * [ -f "/var/run/valheim-backup.pid" ] && kill -HUP $(cat /var/run/valheim-backup.pid)
*/15 * * * * [ -f "/var/run/valheim-updater.pid" ] && kill -HUP $(cat /var/run/valheim-updater.pid)
0 5 * * * /usr/local/bin/valheim-is-idle && /usr/local/bin/supervisorctl restart valheim-server

That last line containing restart valheim-server will not be listed when RESTART_CRON is set to an empty string.

Deleted and started a new container with this script, same reboot at 12AM local time (AT). No idea why this keeps happening.
sudo docker create
--name=valheim-server
--cap-add=sys_nice
--restart unless-stopped
-e PUID=1026
-e PGID=100
-e TZ=America/Halifax
-p 2456-2458:2456-2458/udp
-v /volume1/docker/configs/valheim:/config
-e SERVER_NAME="mixmix"
-e WORLD_NAME="valhallaheim"
-e SERVER_PASS=""
-e RESTART_CRON="0 6 * * "
-e BACKUPS_CRON="/30 * * * *"
-e UPDATE_CRON="0 */6 * * *"
-e BACKUPS_DIRECTORY="/config/backups"
-e BACKUPS_MAX_AGE=7
-e RESTART_IF_IDLE=true
-e UPDATE_IF_IDLE=true
-e VALHEIM_PLUS=true
lloesche/valheim-server
$ sudo docker exec -it valheim-server crontab -l
*/30 * * * * [ -f "/var/run/valheim-backup.pid" ] && kill -HUP $(cat /var/run/valheim-backup.pid)
0 */6 * * * [ -f "/var/run/valheim-updater.pid" ] && kill -HUP $(cat /var/run/valheim-updater.pid)
0 6 * * * /usr/local/bin/valheim-is-idle && /usr/local/bin/supervisorctl restart valheim-server

Ok this output makes sense because you are setting -e RESTART_CRON="0 6 * * ". What happens if you set -e RESTART_CRON=""? The crontab -l should then only return two lines. If the server is then still rebooting every day at 12 AM it's not a container issue but something external doing the restart.
Unrelated but I would also add a data volume like e.g. -v /volume1/docker/data/valheim:/opt/valheim to significantly speed up startup times.
I see that the cron shows a call to /usr/local/bin/valheim-is-idle as a condition for restarting the server. Is your server still being restarted with players connected? If so then it's also pretty safe to say that it's not the cron restarting the server.
Can you attach a complete startup log? I have a feeling that maybe you have an issue similar to #272
Their server always restarted whenever an update check ran. The root cause was that the update check consumed some additional memory and then the Kernel's OOM killer killed the valheim-server as the heaviest user of RAM.

you are correct, when I removed the restart_cron flag crontab -l returned 2 results. I have 16Gb of ram in this NAS, so I do not think it's a resource choke, but hard to tell.
I added the volume to speed up launch, thanks.
The server is indeed restarting with players connected.
startup log:
valheim-server.zip

@mixm1xmix 16 GB is plenty. If the container is allowed to use 4 GB that should be sufficient. All the issues we saw were on systems where the container had 2 GB or less.
The startup log looks fine. Nothing out of the ordinary. Next time the server restarts unexpectedly add another log to this issue and we should be able to get more info as to why and how the server is getting restarted.

Looks like the rebuild may have fixed my issues. I had some cache RAM in the NAS that reached end of life, it may have had something to do with this, but I'm unsure. thanks again for all your help!


Meta Bug: Discussions are no longer accessible

I understand as per #4733 that Q&A has moved to Discord.
However, there seemed to be a wealth of answers already there in Discussions (I can see from search results), but they're just gone now... Any way they could still be accessible for reading? Or even better, reopen them; Discord is a terrible way to document software.
Lexical version: N/A
Steps To Reproduce

Search for "lexical image upload" on Google / DDG
Click the first search result (which at the time of writing points to https://github.com/facebook/lexical/discussions/2167)

Link to code example: https://duckduckgo.com/?q=lexical+image+upload&ia=web
The current behavior
I get a 404.
The expected behavior
I see the actual discussion & answers.

Note that I would've replied to #4733 if I could, but discussion is restricted...

Thanks for raising, will update the link!

I restored discussions - although we don't have the bandwidth to answer everything on there AND on Discord, we don't want to lose all the historical/searchable content there.


Terraform plan shows changes to column types immediately following successful deployment

Provider Version
v0.23.2
Terraform Version
Terraform v0.13.5
Describe the bug
Certain column types are not being tracked consistently: terraform plan shows changes to column types even immediately following a successful execution of terraform apply. This seems to apply to aliases (e.g. DATETIME and TIMESTAMP) as well as to constraints (e.g. the NOT NULL constraint).
The issue can be addressed for aliases by using the resolved type in the Terraform resource (e.g. using VARCHAR(16777216) instead of VARCHAR and using TIMESTAMP_NTZ(9) instead of TIMESTAMP), but I'm not sure what should be done (by a user) to address this issue for the NOT NULL constraint.
Expected behavior
I expect terraform plan to output no planned changes after successful execution of terraform apply.
Code samples and commands
Here I am including an example table resource along with the outputs from 3 executions of Terraform (executed in order, one immediately after the other):

terraform plan
terraform apply
terraform plan

Here is the example snowflake_table resource:
resource "snowflake_table" "table" {

  database = "DATABASE"
  schema   = "SCHEMA"
  name     = "TABLE"

  # VARCHAR without length
  column {
    name = "VARCHAR_NO_LENGTH"
    type = "VARCHAR"
  }

  # VARCHAR with NOT NULL
  column {
    name = "VARCHAR_NOT_NULL"
    type = "VARCHAR(10) NOT NULL"
  }

  # TIMESTAMP alias
  column {
    name = "TIMESTAMP"
    type = "TIMESTAMP"
  }
}

Here is the initial output from terraform plan (prior to any deployment):
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # snowflake_table.table will be created
  + resource "snowflake_table" "table" {
      + database = "DATABASE"
      + id       = (known after apply)
      + name     = "TEST_TABLE"
      + owner    = (known after apply)
      + schema   = "SCHEMA"

      + column {
          + name = "VARCHAR_NO_LENGTH"
          + type = "VARCHAR"
        }
      + column {
          + name = "VARCHAR_NOT_NULL"
          + type = "VARCHAR(10) NOT NULL"
        }
      + column {
          + name = "TIMESTAMP"
          + type = "TIMESTAMP"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.

Here is the output from the initial terraform apply execution:
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # snowflake_table.table will be created
  + resource "snowflake_table" "table" {
      + database = "DATABASE"
      + id       = (known after apply)
      + name     = "TEST_TABLE"
      + owner    = (known after apply)
      + schema   = "SCHEMA"

      + column {
          + name = "VARCHAR_NO_LENGTH"
          + type = "VARCHAR"
        }
      + column {
          + name = "VARCHAR_NOT_NULL"
          + type = "VARCHAR(10) NOT NULL"
        }
      + column {
          + name = "TIMESTAMP"
          + type = "TIMESTAMP"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

snowflake_table.table: Creating...
snowflake_table.table: Creation complete after 1s [id=DATABASE|SCHEMA|TEST_TABLE]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

And here is the output from terraform plan immediately following the deployment:
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

snowflake_table.table: Refreshing state... [id=DATABASE|SCHEMA|TEST_TABLE]

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # snowflake_table.table will be updated in-place
  ~ resource "snowflake_table" "table" {
        database = "DATABASE"
        id       = "DATABASE|SCHEMA|TEST_TABLE"
        name     = "TEST_TABLE"
        owner    = "TERRAFORM"
        schema   = "SCHEMA"

      ~ column {
            name = "VARCHAR_NO_LENGTH"
          ~ type = "VARCHAR(16777216)" -> "VARCHAR"
        }
      ~ column {
            name = "VARCHAR_NOT_NULL"
          ~ type = "VARCHAR(10)" -> "VARCHAR(10) NOT NULL"
        }
      ~ column {
            name = "TIMESTAMP"
          ~ type = "TIMESTAMP_NTZ(9)" -> "TIMESTAMP"
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.

@milldr recently had to something like this to prevent changes
  lifecycle {
    ignore_changes = [
      column[0].type,
      column[1].type,
      column[2].type,
      column[3].type,
      column[4].type,
      column[5].type,
      column[6].type,
      column[7].type,
      column[8].type,
      column[9].type,
      column[10].type,
    ]
  }

Hopefully this can be fixed in the next provider version to remove this workaround

I had this same issue with version 0.31.0. workaround still works ok, but would be nice to solve the root cause

Hi everyone, we released an improvement to how data types are parsed in v0.64.0 that I suspect would have fixed this issue. Can you confirm whether this is still an active issue for any of you?

@vinayman can you show the output of your plan? Would be helpful to know which types are being updated.


test: added custom handler progressPlugin tests

Added test for a custom handler for progressPlugin

What kind of change does this PR introduce?
Tests

Did you add tests for your changes?
Yes

Does this PR introduce a breaking change?
No

What needs to be documented once your changes are merged?
None

Thanks


chinese char support

pls

Hi Lizhi,
can you provide more info? what means "pls"?
Don't know others in the project, but talking about me, I don't know almost anything about Chinese char, so maybe this is a very good opportunity for you to submit a patch to support this. What do you think? it's possible?
Thanks

trace("中国")

Hi Lizhi,
That works for me. I can see that trace work in the browser console.
Do you have the source files saved as utf8?
If that doesn't work, maybe another possible thing to check is to try
(windows example):
set JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8 -Xmx1024m
Others may have other ideas...
On Tue, Mar 19, 2019 at 3:08 PM lizhi<EMAIL_ADDRESS>wrote:

trace("中国")
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/royale-asjs/issues/405#issuecomment-474169762,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEW31myEpR0XLoU0HFBERnViDBbJGy5Fks5vYEaJgaJpZM4b40-V
.

涓夋湀 19, 2019 2:37:15 涓嬪崍 com.google.javascript.jscomp.LoggerErrorManager println
璀﹀憡: F:/proj/spriteflexjs/examples/bin/js-debug/flash/__native/te/CharSet.js:144: WARNING - unreachable code
    if (false) {
               ^^

涓夋湀 19, 2019 2:37:15 涓嬪崍 com.google.javascript.jscomp.LoggerErrorManager println
璀﹀憡: F:/proj/spriteflexjs/examples/bin/js-debug/flash/text/TextField.js:380: WARNING - Variable referenced before declaration: i
    for (i = 0; i < clen; i++) {
         ^

涓夋湀 19, 2019 2:37:15 涓嬪崍 com.google.javascript.jscomp.LoggerErrorManager println
璀﹀憡: F:/proj/spriteflexjs/examples/bin/js-debug/flash/text/TextField.js:380: WARNING - Variable referenced before declaration: i
    for (i = 0; i < clen; i++) {
                ^

涓夋湀 19, 2019 2:37:15 涓嬪崍 com.google.javascript.jscomp.LoggerErrorManager println
璀﹀憡: F:/proj/spriteflexjs/examples/bin/js-debug/flash/text/TextField.js:380: WARNING - Variable referenced before declaration: i
    for (i = 0; i < clen; i++) {
                          ^

涓夋湀 19, 2019 2:37:15 涓嬪崍 com.google.javascript.jscomp.LoggerErrorManager printSummary
璀﹀憡: 0 error(s), 4 warning(s), 98.4% typed

@matrix3d Those are Google Closure warnings.
You can ignore them or fix them in your code.

Hi Lizhi,
please, try to add more phrasing to your tickets/comments, if you writing is so cryptic or there's almost not explanation is difficult to follow you. We're a community, and I think we all need normal conversations. Maybe foreign language is difficult for you, but the same happens to me. And we all should make a little effort. Hope you understand. Thanks in advance :)

Hi everyone
I use Traditional Chinese. In my experience, it works fine with Apache Royale.
Hi Lizhi,
if you don't know how to describe your problems in English,  try to describe in Chinese... may be I can help

@yestaro 嗯，问题不大了。需要加入这行代码 set JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8 -Xmx1024m。但是比较尴尬的是，加入这行代码编译通过了。编译的输出又是乱码了。而且偶尔还是会编译错误，这个编译错误是随机出现的，也可以不管了。就这样吧，能编译就行

@matrix3d 這就有點奇怪。我沒加入任何的JAVA_TOOL_OPTIONS，到現在沒發生過錯誤。
我是用vs code開發的，也許我們編譯的工具是不一樣的。vs code編譯所下達的命令式如下
C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe -jar c:\Users\cwyu0.vscode\extensions\bowlerhatllc.vscode-nextgenas-0.18.0\bin\asconfigc.jar --sdk "c:\Program Files (x86)\Apache Flex\royale-0.9.6\royale-asjs" --debug=false --project d:\workspace\royale\wec-core\asconfig.json
重點可能是這段 bowlerhatllc.vscode-nextgenas-0.18.0\bin\asconfigc.jar

我這邊也是中文亂碼的問題 @@;  我用的編譯工具是Moonshine
這樣的問題會是編譯工具本身的問題嗎?

The tool software I use is Moonshine.In my test, I found that Chinese, Japanese, and Korean could not be displayed correctly. It'is garbled. Has anyone else encountered the same problem as me?

Has anyone else encountered the same problem as me?

We found similar problems in our real project, but we used unicode for special latin characters.
Do you think this could be solved maybe in Royale-compiler?
We use VSCode for now, so don't think tooling is a problem here. I think this could be something to address in compiler, or maybe is just config in html template we use

@yestaro 你是用VS Code來做編譯的嗎? 是否中文字的輸出沒問題?

@JamesPengTW 我是用 VS Code。像trace("中文") 這類程式是沒問題的。昨天細看了一下編譯輸出，一些警告訊息，確是亂碼。但那只是警告訊息，不影響輸出
It worked fine like trace("中文"), but the warning message of compiler does not support chinese

@JamesPengTW 我剛用Moonshine試了一下，的確不行。但VS Code是可以的。
It does not support chinese when use Moonshine, but OK with VS Code.
I test it on the same environment, JDK 10 / Royale 0.9.4
compile the source file ApacheRoyaleTest.mxml.

output js-debug/ApacheRoyaleTest.js from Moonshine encoded in ANSI
output js-debug/ApacheRoayleTest.js from VSCode encode in UTF8

I don't know why their output js file has different encoded....

@JamesPengTW 我剛用Moonshine試了一下，的確不行。但VS Code是可以的。
It does not support chinese when use Moonshine, but OK with VS Code.
I test it on the same environment, JDK 10 / Royale 0.9.4
compile the source file ApacheRoyaleTest.mxml.

output js-debug/ApacheRoyaleTest.js from Moonshine encoded in ANSI
output js-debug/ApacheRoayleTest.js from VSCode encode in UTF8

I don't know why their output js file has different encoded....

I will raise an issue in Moonshine to investigate that stuff. I will try to fix that if not in version 2.1.0 - I should get results in the next one.

@yestaro , @JamesPengTW here is the solution for Moonshine. Probably VSCode have this setup at some point default - I'm not sure. To test that stuff I have used MX Hello World example and newest nightly build 2115 of Royale.
<mx:Label text="來做編譯的嗎? 是否中文字的輸出沒問題" x="20" y="20" />
Go to Windows Environment variables and add -JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8

I have that option setup for a long time now, so I tried build this Hello World without it and I was able to reproduce your problems. Once you setup above parameter in environment variable restart Moonshine.
At the end of the build you should see something like that if option is setup correctly.
: The project 'HelloWorld' has been successfully compiled and optimized.
: 79.393026687 seconds
: Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
: Project Build Successfully.
: Launching application HelloWorld.
: Application HelloWorld started.

Let me know if it helps.

The problem is solved!! I am sure that the Chinese, Japanese, Korean and other languages can be displayed correctly. @piotrzarzycki21  you are right! thank you a lot.
@matrix3d @yestaro   it's solution for Moonshine.

The problem is solved!! I am sure that the Chinese, Japanese, Korean and other languages can be displayed correctly. @piotrzarzycki21 you are right! thank you a lot.
@matrix3d @yestaro it's solution for Moonshine.

Happy to help! :) Thanks for using Moonshine!

This issue should be fixed in commit apache/royale-compiler@b95cd6f3d47e1d21f1693347dc7bce676c72b682


Allow promote customer user to staff user

I want to merge this change because it fixes a bug that does not allow promote customer users to staff users.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-7232 Staff user cannot be invited if that user is already a customer


Unable to plan using Terraform Cloud

System Information
Linux distribution
Fedora 31
Terraform version
Terraform v0.12.18
+ provider.template v2.1.2

Provider and libvirt versions
terraform.d/plugins/linux_amd64/terraform-provider-libvirt 0.6.0+git.1569597268.1c8597df
Compiled against library: libvirt 4.1.0
Using library: libvirt 5.6.0
Running hypervisor: QEMU 4.1.1
Running against daemon: 5.6.0

Checklist

[ ] Is your issue/contribution related with enabling some setting/option exposed by libvirt that the plugin does not yet support, or requires changing/extending the provider terraform schema?

[ ] Make sure you explain why this option is important to you, why it should be important to everyone. Describe your use-case with detail and provide examples where possible.
[ ] If it is a very special case, consider using the XSLT support in the provider to tweak the definition instead of opening an issue
[ ] Maintainers do not have expertise in every libvirt setting, so please, describe the feature and how it is used. Link to the appropriate documentation

[ ] Is it a bug or something that does not work as expected? Please make sure you fill the version information below:

Description of Issue/Question
Setup
We are using Terraform Cloud as a state store and applying to Fedora based server on premise. the main.tf would appear to me mostly irrelevant to problem, hence I have just included the minimal top matter.
We migrated our state from a file in git to Terraform Cloud which worked and a colleague had been able to plan and apply changes.
terraform {
	backend "remote" {}
}

provider "libvirt" {
	uri = "qemu+ssh://user@local-machine/system"
}

Steps to Reproduce Issue

Create a workspace in terrform cloud
Setup a main.tf
Terraform init (pointing the backend at the workspace you created)
terraform plan and get message something like this:

Running plan in the remote backend. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

To view this run in a browser, visit:
https://app.terraform.io/app/Org/workspace/runs/run-id

Waiting for the plan to start...

Terraform v0.12.17
Configuring remote state backend...
Initializing Terraform configuration...
2019/12/17 13:26:46 [DEBUG] Using modified User-Agent: Terraform/0.12.17 TFC/89d40ee98a

Error: Failed to instantiate provider "libvirt" to obtain schema: Unrecognized remote plugin message:

This usually means that the plugin is either invalid or simply
needs to be recompiled to support the latest protocol.

Additional information:
Do you have SELinux or Apparmor/Firewall enabled? Some special configuration?
Have you tried to reproduce the issue without them enabled?

hi @mhill-holoplot! thx for issue. Just one question is terraform cloud opensource? Or one need to pay to use it?
Could you append logs complete with TF_LOG=DEBUG terraform plan tia

closing stale


Python extension fails to find user settings.json in when opened inside a container

Environment data

VS Code version:
Version: 1.60.2
Commit: 7f6ab5485bbc008386c4386d08766667e155244e
Date: 2021-09-22T12:01:43.795Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.11.0-7620-generic
Extension version (available under the Extensions sidebar): v2021.9.1246542782
OS and version: OS: Linux x64 5.11.0-7620-generic
Python version: Python 3.8.11 64-bit (mcr.microsoft.com/vscode/devcontainers/python:0.201-3.8)
Type of virtual environment used: N/A (VS Code Dev container)
Relevant/affected Python packages and their versions: N/A
Relevant/affected Python-related VS Code extensions and their versions: N/A
Value of the python.languageServer setting: "Pylance"

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
When running the Python Extension in a dev container on a Linux desktop OS, expect python extension to read global/User settings.json from the user's home directory.
Actual behaviour
Python extension attempts to read from the home directory of the container user - vscode, and fails to find the actual settings file.

Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

On a Linux computer, checkout this repo: https://github.com/oscarhermoso/vscode-unittest-failure
Build and open in container
Open Output panel, and choose Python from drop down to see stack trace failing to find location

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Python Output
User belongs to experiment group 'pythonaacf'
User belongs to experiment group 'pythonJediLSP'
User belongs to experiment group 'pythonDiscoveryModuleWithoutWatcher'
User belongs to experiment group 'pythonTensorboardExperiment'
User belongs to experiment group 'PythonPyTorchProfiler'
User belongs to experiment group 'pythonDeprecatePythonPath'
User belongs to experiment group 'pythonSortEnvs'
User belongs to experiment group 'pythonRunFailedTestsButtonDisplayedcf'
User belongs to experiment group 'pythonRefreshTestsButtonDisplayed'
User belongs to experiment group 'pythonRememberDebugConfig'
Python interpreter path: /usr/local/bin/python
Error 2021-09-25 05:26:00: Failed to check if file needs to be fixed [EntryNotFound (FileSystemError): Unable to read file 'vscode-remote://dev-container+2f686f6d652f6368656573653835322f446f63756d656e74732f4769744875622f707974686f6e2d7673636f64652d756e6974746573742d6661696c7572652f7673636f64652d756e6974746573742d6661696c757265/home/vscode/.config/Code/User/settings.json' (Error: Unable to resolve non-existing file 'vscode-remote://dev-container+2f686f6d652f6368656573653835322f446f63756d656e74732f4769744875622f707974686f6e2d7673636f64652d756e6974746573742d6661696c7572652f7673636f64652d756e6974746573742d6661696c757265/home/vscode/.config/Code/User/settings.json')
	at _handleError (/home/vscode/.vscode-server/bin/7f6ab5485bbc008386c4386d08766667e155244e/out/vs/server/remoteExtensionHostProcess.js:94:160087)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)
	at async y.readText (/home/vscode/.vscode-server/extensions/ms-python.python-2021.9.1246542782/out/client/extension.js:9:314351)
	at async p.doesFileNeedToBeFixed (/home/vscode/.vscode-server/extensions/ms-python.python-2021.9.1246542782/out/client/extension.js:59:823969)
	at async /home/vscode/.vscode-server/extensions/ms-python.python-2021.9.1246542782/out/client/extension.js:59:823096
	at async Promise.all (index 0)
	at async p.getFilesToBeFixed (/home/vscode/.vscode-server/extensions/ms-python.python-2021.9.1246542782/out/client/extension.js:59:823042)
	at async p.updateTestSettings (/home/vscode/.vscode-server/extensions/ms-python.python-2021.9.1246542782/out/client/extension.js:59:822669)] {
  code: 'FileNotFound'
}
Starting Pylance language server.
> conda --version

Logs are similar to this closed issue.

This is fixed via #17312


collection in CollectionX method should become a more general conversion method

It should also be named to fit the to(  ) naming convention somehow
This will make working with 3rd party data types in monad transformers easier.

Merged


Latest social_feed indexer

Has more error checking for malformed or unexpected social data.

You probably want to add the newest code here. This has the graphql calls in it still.

Wrong code in this branch


Newer version of react-native-camera

This repo is a whole major version behind. You need to use the newer react-native-camera for newest react-native and build tools for android.
What's happening?
Well nothing really, it just works.  We should let people know if they need to use 'general' or 'mlkit' (the former seems to work fine).

Will accept PRs updating to the latest version.

Will accept PRs updating to the latest version.


feat: Better product image view

What

We now can swipe through all images when opened one

Screenshot
https://user-images.githubusercontent.com/39344769/153708001-d122ec8d-23d6-4228-b363-0317c9d2a478.mp4
Open questions
Is it correct that ImageField.OTHER isn't a real image but just a card to add further images

One refactoring commit incoming

OTHER doesn't correspond to anything that's showable site wise.
That said, there's a number of other images. In V1, we have a hidden tab for power users:
https://user-images.githubusercontent.com/71206228/110181616-3655f680-7e32-11eb-8519-3e977034e9f2.png

@M123-dev Let me explain: it's a gallery where we swipe from picture to picture, right? Displaying the title of the picture ("ingredients", "front", ...) could be interesting. Especially when we're confused about that stupid product with an ingredient image saved as a front image and vice versa.

Ohh @monsieurtanuki makes sense, but I'd say showing an snackbar in addition to the title in the appBar is a bit to much action the screen, the people should also recognize what is to be seen in the photo

Now that we have swipe from one to another, #766 is much more practical


Probos Wallet Grant Application

Project Abstract

Please provide a brief description of your project here summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

For which grant level are you applying?

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $50,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for > $100k Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A Polymesh (POLYX) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the terms and conditions.
[ ] The software delivered for this grant will be released under an open-source license specified in the application.
[ ] The initial PR contains only one commit (squash and force-push if needed).
[ ] The grant will only be announced once the first milestone has been accepted.

Hello! Thanks for the feedback.
Yes, we are indeed focused on NFT. And it's great news that you plan to add
them to your network. Therefore, Probos will be able to reveal its full
potential on Polymesh network.
Yes, we understand that Polymesh is not an EVM compatible blockchain and
the fact that we currently support EVM compatible blockchains is a little
unclear. However, I want to assure you that we are already working on the
necessary technical base to support other networks, including Polymesh,
Polkadot, Kusama networks. This task is within our grasp.
At the stage while Polymesh doesn't support NFT, our integration may look
like this - support of your blockchain inside the wallet and POLYX token
listing.
About this part "Assets on Polymesh are primarily targeted at digital
securities. Is Probos aware of the settlement process required for trading
assets on Polymesh?”. We would like to learn more and maybe correct the
path of our integration based on this.
чт, 22 сент. 2022 г. в 17:42, FOB @.***>:

@SofiiaPW https://github.com/SofiiaPW Many thanks for considering
integration of Polymesh into your wallet. Having reviewed your proposal I
have some questions.
It enables you to conveniently hold NFTs & access important info about
them.
I note your proposal appears to have a large focus on NFT's. At this time
Polymesh does not support NFT's, however they will be supported in a future
chain update. Assets on Polymesh are primarily targeted at digital
securities. Is Probos aware of the settlement process required for trading
assets on Polymesh?
Polymesh is a Substrate based blockchain and assets (security tokens) are
native at the protocol and not ERC-20 style tokens controlled by smart
contracts. Does Probos have familiarity with the Substrate framework and
any experience integrating Substrate based chains e.g. Polkadot? I note
most of the experience listed on your site appears to be EVM related.
Any additional information you can provide to help us assess if Probos
wallet is a good fit for Polymesh and that you have an understanding of
integrating Substrate based chains and Polymesh specific criteria for asset
storage and transfers would be appreciated.
—
Reply to this email directly, view it on GitHub
https://github.com/PolymeshAssociation/Grants-Program/pull/5#issuecomment-1255128567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A25VYLQ4V62443TBBDJAQG3V7RV3RANCNFSM6AAAAAAQQ6D5KI
.
You are receiving this because you were mentioned.Message ID:
@.***>


[#610][3] Add All Anchor IDs and All Steps of Tutorial And Style Change

The goal of this PR is to create all necessary Anchor IDs and add all necessary tutorial steps and polish the CSS file.
The library we use to achieve this goal is ngx-tour

The final goal of PR [#610] is to implement a tutorial into new GUI.

Final Result of [#610]

@bobbyfine this screenshot is too old.  Can we use a screenshot of the latest UI?

@bobbyfine this screenshot is too old. Can we use a screenshot of the latest UI?

This is the latest master branch UI

@avinash0161 and @zuozhiw : can you look into it?  I believe even the current master has a different URL than what is shown here.

A couple of changes made:

Updated the testings for the tutorial to test whether an event is triggered when the user starts or ends the tutorial
Fix the issue where the tour panel's position makes the entire tutorial UI appears below the screen by setting the width and the height of the GIF / Image imported from asset.
Resolve the problem for running Texera UI on Microsoft Edge and FireFox. The problem was caused by getting one of the internal properties for the jQuery event, event.toElement, which is currently not supported in both of the browsers. The correct way to call this is to call event.target.


Allow short camera flights.

GlobeAwareDefaultPawn completely ignores requests to do camera flights that have "zero steps" as defined by  its FlyToGranularityDegrees property. With this PR, it will do arbitrarily short flights, including rotation-only flights.
Fixes #678

Thanks for the pull request @kring!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.


queryText being sent to Dialogflow is not the original user query

The user input / queryText being sent to Dialogflow is not the expected, original user query.

I then enabled "Log interactions to Google Cloud" in my Dialogflow project's settings. What I'm seeing is multiple request/response interactions before the actual request that goes to DF. In the example above, this is what I see:

With the first debug resource showing post data with:
"inputs":[{"rawInputs":[{"inputType":"UNSPECIFIED_INPUT_TYPE","query":"how long has it been on the market"}]

And
resource: {
type: "assistant_action"
  labels: {
    project_id: "<MY-PROJECT-ID>"
    version_id: ""
    action_id: ""
  }
},
timestamp: "2021-03-05T18:41:44.142202856Z"
severity: "DEBUG"
labels: {
  channel: "production"
  querystream: "GOOGLE_USER"
  source: "AOG_REQUEST_RESPONSE"
}

The subsequent requests are the same but with modified input queries ("how long has it been on the market" -> "how long has something been on the market" -> "how long has us FDA been on the market"), the last one being the actual user query sent, the channel being preview and the action_id "actions.intent.TEXT".
resource: {
type: "assistant_action"
  labels: {
    project_id: "<MY-PROJECT-ID>"
    version_id: ""
    action_id: "actions.intent.TEXT"
  }
},
timestamp: "2021-03-05T18:41:45.942019959Z"
severity: "DEBUG"
labels: {
  channel: "preview"
  querystream: "GOOGLE_USER"
  source: "AOG_REQUEST_RESPONSE"
}

I should note that I am testing current drafts of an AoG project and have no releases let alone a production release. I have a denied beta, because of branding issues which I address with separate AoG/DF projects for PROD. I do not have any intents enabled for slot filling or any required entity parameters. And I have been noticing this on many occasions when getting unexpected fallbacks.
What are all these requests/responses happening before DF Fulfillment? Why is the query being changed?

To me, this is pretty clear evidence that Actions on Google is attempting entity resolution, before sending data to DF. How can I disable this?

Closing this issue.
After having contacted someone at Google Cloud, I was informed this was something that had been raised by others and that AoG devs were looking into it.
As of a Mar 24 2021 release, I can no longer replicate the issue.


Fix Login method return in AuthController

Fix the AuthController Login method's return in Spark.Templates.Api. It was incorrectly returning a View(); changed it to return a BadRequest with the ModelState.

Minor change but I hope it helps. :)

Nice thanks for catching this. Approved. Will go out with the next minor release.

@caio-basso This change is going live today in Spark 0.9.0. Thank you for the contribution!


Added bootstrap classes to left bar

fixes #92

hey, as requested i have styled the input, toggle button. So now the whole left bar is styled with bootstrap classes

Not accetpable @Aditya-ds-1806. There were a lot more discussion in #93. Add all those changes.

Can you please elaborate? The requirement was to style the left bar with bootstrap classes and I did that.

In the discussion, i was asked to style the input and the toggle button, which I did

I don't think that I have to explain it again, everything is well elaborated there in #93.
Still because you have asked me to elaborate...
<input> tag should be like any normal bootstrap's input form, see screenshot=>

and the toggle collapse button should be like any bootstrap button, read about bootstrap buttons, and for the division of room name you have to be creative, think about it.

All right, now I understand. Will finish it in half an hour. Thanks!

This is the result after the recent commit. Is this fine? This is same as bootstrap default.

Can you check now? I fixed the errors and changed the button to primary

Good work @Aditya-ds-1806. Merging this :rocket:

Great, thanks!


fix parse compact type error

Codecov Report

Merging #47 (c5c1b3c) into main (a1c8fcf) will increase coverage by 0.12%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
+ Coverage   94.72%   94.84%   +0.12%
==========================================
  Files          55       55
  Lines        3281     3300      +19
==========================================
+ Hits         3108     3130      +22
+ Misses        128      125       -3
  Partials       45       45

Impacted Files
Coverage Δ

codec/fetch_resp.go
91.25% <100.00%> (ø)

codec/produce_req.go
91.13% <100.00%> (ø)

codec/record.go
100.00% <100.00%> (ø)

codec/record_batch.go
100.00% <100.00%> (ø)

codec/util_general_bytes.go
97.87% <100.00%> (+7.62%)
:arrow_up:

codec/util_general_string.go
100.00% <100.00%> (ø)

codec/util_general_varint.go
95.74% <100.00%> (+1.15%)
:arrow_up:

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


VNWindow plans

Sorry to bother again I wanted to clarify I was reading https://github.com/nodegui/vue-nodegui/blob/master/src/widgets/Window/VNWindow.ts is there plans / needed help to port all the functions of QMainWindow in the future.
It says right now "You would not be using this widget in your app." I'm making use of it with the react nodegui (for fun) to create systemtray icons, detect the close event, set the title etc.
Happy to try helping with porting the functionality but I'm a bit new to TypeScript.

Currently, the renderer automatically creates the window and renders the app inside that window.
To make it more like react-nodegui (allowing systemtray icons, etc) we would need to implement more props for the VNWindow widget. Once that's done, the user will be able to use <vn-window>  as a component in their code.
If you're interested in trying to implement, you can take a look at the other widgets as an example (VNView or VNText) 🙁


Mitigate crash that can occur when installed version is null

Mitigates #2273 for 1.3, but another change will hopefully be able to fully fix it.
Change
Protect against the installed package returning a null installed version.  This should prevent crashes, while hiding the package from view.
I suspect that embedded nulls in the registry strings are causing the issues, and a future change will try to address that more comprehensively.
Microsoft Reviewers: Open in CodeFlow

/azp run


Default to main branch in prometheus-operator

Description
Branch master was renamed to main in https://github.com/prometheus-operator/prometheus-operator/
jb tool provides the following error while installing/updating:
GET https://github.com/prometheus-operator/prometheus-operator/archive/.tar.gz 404
archive install failed: unexpected status code 404
retrying with git...
...
error: pathspec 'master' did not match any file(s) known to git
jb: error: updating: downloading: exit status 1

Type of change

[ ] CHANGE (fix or feature that would cause existing functionality to not work as expected)
[ ] FEATURE (non-breaking change which adds functionality)
[x] BUGFIX (non-breaking change which fixes an issue)
[ ] ENHANCEMENT (non-breaking change which improves existing functionality)
[ ] NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)

Changelog entry
- default to main branch in prometheus-operator

Closing as a duplicate of https://github.com/prometheus-operator/kube-prometheus/pull/1491


Add Sepolia address for RequesterAuthorizerWithErc721

The reference for the deployment can be found here: https://github.com/api3dao/airnode-protocol-v1/pull/139
The file changes were generated by running yarn axios:build.

@dcroote Not sure if you used the script to update this or did it manually but it is correct. The script is here and it updates several files in the src directory, but maybe you know this.

@wkande - yes I used the axiosBuildScripts.js script via the yarn axios:build command


Query isn't properly formatted when table is partitioned

Hi,
I'm trying to run
{{ config(partitioned_by='day') }}
select
    a,
    b,
    c
 from random_table

I can see that in target/run the query is being compiled to
create table
    dev_datawarehouse.test

    with (
        partitioned_by=ARRAY'day',
        format='parquet'
    )
  as

select
    a,
    b,
    c
 from random_table

Which gives the following error: SYNTAX_ERROR: Unknown type: ARRAY.
the compiled query should instead be
create table
    dev_datawarehouse.test

    with (
        partitioned_by=ARRAY['day'],
        format='parquet'
    )
  as

select
    a,
    b,
    c
 from random_table

Which works just fine. Am I missing something obvious?

Ok I've solved the problem: this is wrong {{ config(partitioned_by='day') }} should be {{ config(partitioned_by=['day']) }}
what is less obvious is that if you declare the parittion column at the project level like so:
example:
      partitioned_by:
          - day

you'll experience the same error. You should declare it like so:
example:
      partitioned_by: [day]

This StackOverflow answer saying that the 2 forms are equivalent threw me off a bit https://stackoverflow.com/questions/23657086/yaml-multi-line-arrays

To partition by a date column, use syntax like this:
{{ config( partitioned_by = [ 'some_date_column' ] ) }}

select a, b, some_date_column
  from random_table


Convert all Run command functions to RunE functions

Convert all os.Exit(1) to return error.New(ERR_STRING) and all os.Exit(0) to return nil
This will make the flow clearer and allow the root.go to have control after a process has ran.
This will also solve the bug where if a command exits prematurely, it will not re-show the cursor after it was hidden.

Implemented in latest commit https://github.com/candrewlee14/webman/commit/dc9c68d6700f970be6a5707588a84e30dd5cc5ff


Bulk segment deletion on Historical causes significant delays of handoff from Kafka tasks

Affected Version
0.22.1
Description
Since I deleted hundreds of thousands of segments, Kafka ingestion tasks have failed even after successfully publishing segments:
2022-01-11T11:14:43,310 INFO [[index_kafka_navi-gps_ae030ea793e6992_omamibla]-publish] org.apache.druid.indexing.seekablestream.SeekableStreamIndexTaskRunner - Published segments: [navi-gps_2022-01-11T09:00:00.000Z_2022-01-11T10:00:00.000Z_2022-01-11T09:11:38.515Z_8, navi-gps_2022-01-11T10:00:00.000Z_2022-01-11T11:00:00.000Z_2022-01-11T10:20:19.334Z_1, navi-gps_2022-01-11T11:00:00.000Z_2022-01-11T12:00:00.000Z_2022-01-11T11:00:00.031Z_7]
2022-01-11T11:14:43,311 INFO [[index_kafka_navi-gps_ae030ea793e6992_omamibla]-publish] org.apache.druid.indexing.seekablestream.SeekableStreamIndexTaskRunner - Saved sequence metadata to disk: []
2022-01-11T11:15:41,912 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:16:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:17:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:18:41,911 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:19:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:20:41,917 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:21:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:22:41,908 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:23:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:24:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:25:41,912 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:26:41,907 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:27:41,915 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:28:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:29:41,910 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:30:41,914 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:31:41,913 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:32:41,908 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:33:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:34:41,912 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:35:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:36:41,910 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:37:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:38:41,909 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:39:41,907 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:40:41,908 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:41:41,913 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:42:41,908 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:43:41,908 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:44:41,912 INFO [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [3] Segments
2022-01-11T11:44:48,187 INFO [parent-monitor-0] org.apache.druid.indexing.worker.executor.ExecutorLifecycle - Triggering JVM shutdown.
2022-01-11T11:44:48,188 INFO [Thread-73] org.apache.druid.cli.CliPeon - Running shutdown hook
2022-01-11T11:44:48,189 INFO [Thread-73] org.apache.druid.java.util.common.lifecycle.Lifecycle - Stopping lifecycle [module] stage [ANNOUNCEMENTS]

The kafka task has waited for Handoff for PT30M which is I guess the default value of completionTimeout of KafkaSupervisorIOConfig.
I found that Historical is busy handling of unannouncement of deleted segments for tens of hours. The newly published segments seem to be registered and become available only after the segments have been all unannounced.
Restarting the coordinator seems to force Historical to register the new segments [1], but it doesn't seem like a solution.
[1] https://groups.google.com/g/druid-user/c/h_E3ZDeVHd4

@eastcirclek , can you provide a stack trace from coordinator and overlord? I suspect this has been fixed already but would be good to confirm!. Thanks. cc @kfaraz .


Feature/prepare for deployment

Didn't add any additional functional features as I managed to add them in the previous homework. In this pr, all work is focused to bring this application to production, and as so most of the work happened on Azure, to configure and deploy the app service and the sql database.

Wanted to add ci/cd for publishing the app, but that will have to be left in the next homework


Bench testing no longer working in Rust 1.26 stable

Code throws an error at benches\bench.rs at line 1:
https://github.com/mrhooray/crc-rs/blob/322576dae7da9a5beec5f45b2f2c8ad694b4febd/benches/bench.rs#L1
Rust error:
error[E0554]: #![feature] may not be used on the stable release channel

@CLomanno if i'm not mistaken, bencher was never in stable.
see https://doc.rust-lang.org/1.26.0/test/struct.Bencher.html

Are you planning on keeping the code in benches/bench.rs or removing it going forward?  In it's current state, it's broken.


add replicate test with file updates

Adds two tests, one of them is failing (the one that uses raf options for the length stuff).

Also, worth noting, if you use archive.download(0) and then archive.createReadStream directly then all is okay. Its only when I waited for replication to finish automatically that it didn't work.


Automated Nginix Config

I updated the bash script to do the full config. I also added the option to configure auto-scale on the VMSS at the time of deployment.

lol; I posted a PR last week with the same goal #2
May the best patch win!  :)


Automated cherry pick of #11788: fix(region): baremetal server resued address nic count should be subtracted

Cherry pick of #11788 on release/3.7.
#11788: fix(region): baremetal server resued address nic count should be subtracted

/lgtm

/approve


Add graffito -> graffiti irregular rule

This PR adds the singular form of the word graffiti.
Currently, graffiti is defined in the code as the irregular singular form of the word.
https://github.com/blakeembrey/pluralize/blob/abb399111aedd1d62dd418d7e0217d85f5bf22c9/pluralize.js#L436
The word graffiti is the plural form of the word, not the singular and only form as defined in the code.
The singular version of graffiti is graffito.
It's an Italian word; that's why it has a weird structure. I should also note that while this is the correct usage of the word, graffito isn't often used in English as many people aren't aware of it.

Coverage remained the same at 100.0% when pulling e0a36c7d2818bcd7e0ed40b2be8279e872b53a03 on nmsmith22389:fix-word-graffiti into abb399111aedd1d62dd418d7e0217d85f5bf22c9 on blakeembrey:master.

Coverage remained the same at 100.0% when pulling e0a36c7d2818bcd7e0ed40b2be8279e872b53a03 on nmsmith22389:fix-word-graffiti into abb399111aedd1d62dd418d7e0217d85f5bf22c9 on blakeembrey:master.