No implementation for method requestCameraPermission ( 3.0.0-dev.3)

Hi
Using the new version  3.0.0-dev.3 for Android, it works very well in the debug build but if I build an app bundle to test the release build I get "MissingPluginException(No implementation found for method requestCameraPermission on channel de.mintware.barcode_scan)".
This happens every time you try a scan.
Any ideas ? Thanks...

Please provide a minimal working example to reproduce the problem. Are you using proguard?

Thanks for the quick response !
Double checking everything this morning, flutter run --release DOES work - the app asks for the camera permissions etc.
The problem is when you build app bundle or apks and install them outside of flutter.
The flutter_barcode_reader example project does the same thing.
flutter build apk
adb install build/app/outputs/apk/release/app-release.apk

... does not work.
It seems I am using proguard as it is the default. Building the apk's or bundle with the --no-shrink option fixes the problem.

Please try to add -keep class de.mintware.** { *; } to your proguard rules and tell if it works.
Maybe it's because some methods in the platform code are executed by reflection instead of invoking them directly. This will be probably recognized as "dead code" from the release build.

Yes, that works. I had to create the android/app/proguard-rules.pro file as it didn't exist.
I did not myself enable proguard, it's R8 that is enabled by default apparently.
Anyway, thanks so much for your help and for this great package library.

Perfect, thanks for the information! I'll check if I can create a proguard-rules.pro file for the package so users don't need to activate it by them self. If it's not possible I'll update the docs!

The latest version (3.0.0) contains a fix for the problem so you don't need to add the rule to the proguard file.


Allow opa fmt action on a given file

What would you like to be added
Similar to how the Go plugin adds an action to run the formatter on a file, it would be great if we provided one for opa fmt.

agreed it may a bit tedious to have to file open and have the focus to reformat it...


WaveX

If you are reporting a problem with Token Wizard, please include the following information:
Which network did you use? (Mainnet, Kovan, Rinkeby, etc.)
Kovan
If you were able to create it, what is the URL of your crowdsale?
https://wizard.oracles.org/invest?addr=0x68F2f9c2221E7Ed262490127936A56Cae292f76d&networkID=1
Do you have screenshots showing the problem?
well it shows the wrong amount for the goal.. and on other computers besides my own it doesnt show a countdown or any information for the crowdsale
Invalid crowdsale address is indicated in config and/or in query string /is the error message i see.. cannot access tools or any other page
To open the dev console in Google Chrome, press F12, or go to View -> Developer -> Developer Tools, and open the Console tab
If you see errors, please right click on them and "Save as..". Zip saved file and attach it to the Issue.
i am unable to access anything besides the page.. no options.. f12 does not work

well it shows the wrong amount for the goal

What value do you expect for the goal? I see 10400 ETH

and on other computers besides my own it doesnt show a countdown or any information for the crowdsale

Related issue https://github.com/poanetwork/token-wizard/issues/755. User should have MetaMask to display the whole data in invest page.

I redid the crowdsale a third time.. this time the only problem seems to be
it's showing that it's not active.. possibly because my metamask is in main
network and I don't know how to switch it to kovan. Thank you so very much
for replying.. my apologies for making these errors.. but I really really
need your help
On Mon, Apr 16, 2018, 2:29 AM Victor Baranov<EMAIL_ADDRESS>wrote:

well it shows the wrong amount for the goal
What value do you expect for the goal? I see 10400 ETH
[image: screencapture-wizard-oracles-org-crowdsale-2018-04-16-12_24_44]
https://user-images.githubusercontent.com/4341812/38800939-2de32690-4171-11e8-8175-1e1d153b8387.png
and on other computers besides my own it doesnt show a countdown or any
information for the crowdsale
Related issue #755 https://github.com/poanetwork/token-wizard/issues/755.
User should have MetaMask to display the whole data in invest page.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/poanetwork/token-wizard/issues/793#issuecomment-381537616,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkloxkQlGPyW-InGVGWJz2rCNMWMNaR3ks5tpGRngaJpZM4TVZ2t
.

The goal is 100,000 ether.. I was able to change that on the third one I did after these last two.. but now it's still not showing up with a time limit until crowdsale begins.. it just says crowdsale has ended.. :(

On my computer screen it shows as having 14 days.. but if I bring up another browser or use my cell phone.. it says crowdsale has ended

@Gio300 your crowdsale not in Kovan, you have created it in Mainnet &networkID=1

On my computer screen it shows as having 14 days.. but if I bring up another browser or use my cell phone.. it says crowdsale has ended

Without Metamask you will not see the full data of crowdsale

And you can manage any tier of your crowdsale https://github.com/poanetwork/token-wizard/wiki#managing-the-crowdsale before tier is started if you set up a tier as modifiable.


Support ScrollableLists that wrap

Support ScrollableLists that wrap
Adds itemsWrap:bool (default false) to ScrollableList and PageableList. If itemsWrap is true then scrolling past the last item wraps around to the first. Similarly, scrolling before the first item wraps around to the last.
Added abstract ExtentScrollBehavior of ScrollBehavior. Renamed fields called contentsExtents to contentExtent, containerExtents to containerExtent, contentSize to contentExtent, etc.
BoundedBehavior is now a subclass of ExtentScrollBehavior.
Added UnboundedBehavior subclass of ExtentScrollBehvaior; contentExtent and maxScrollOffset are double.INFINITY, minScrollExtent is double.NEGATIVE_INFINITY.

LGTM
Please squash before landing.


fix: check pure text by regex (without emojis)

This pr related to this issue. The regex was wrong and return rtl when any emoji was in the text. I added an extra regex to replace emojis with empty string then main regex check the pure text and return real direction

This bug occurs when write emoji and after that is rtl text and editor make whole text ltr @fantactuka @zurfyx @acywatson

@fantactuka @zurfyx @acywatson Hi, good job I fixed this issue and pass tests now. You make a lot of users happy by fix this bug

Closing this PR due to staleness! If there are new updates, please reopen the PR.


client, always have javadoc description

Msdoc render of javadoc without description is not good.
https://docs.microsoft.com/en-us/java/api/com.azure.resourcemanager.mediaservices.mediaservicesmanager?view=azure-java-stable
Hence we should always add the "description" to javadoc.

Case 3 is on Manager class. E.g. https://docs.microsoft.com/en-us/java/api/com.azure.resourcemanager.mediaservices.mediaservicesmanager?view=azure-java-stable


refactor: Format code

Format code

Updated the code with a very fancy format
Auto-generated by create-pull-request

Why DQ? 😕 It gonna increase your app size :D


Submitting the Seabath project readme markdown

Merging the seabath project readme markdown with the ICESat-2-Hackweek-2023 main project

Thank you for opening this PR @glacierSid
Looks like a typo snuck into the ReadMe on Line 30
throught ==> thought ?

Looks good after addressing the typo

Thanks Joe! :)


[BI-641] - Validate lower and upper limits for correctness

Looks like a big PR, but is mostly changes to test import files. The change to BigDecimal in the scale class required a few extra changes.
This is based off on BI-645, so that should be reviewed and merged before the review of this.

The row numbers in the error messages are off by 2

I checked your file with the new changes for this card and the errors started off at row 2. Let me know if it is working for you now as well.


Zclassic Electrum Wallet Will not connect to server

I downloaded the zclassic electrum wallet and it will not connect to the server.  I sent zclassic from bittrex to my zclassic electrum wallet and it does not show the zclassic in my wallet however it does show on the zclassic block explorer.

Mine worked just fine the first time I installed it yesterday
Adam B. Stevens

 17574 Hardhat rd.

 STE 4

 Covington, La.  70435

 Phone:<PHONE_NUMBER>

 Fax:<PHONE_NUMBER>

From: jvehovic<EMAIL_ADDRESS>Sent: Wednesday, February 21, 2018 2:26 PM
To: BTCP-community/electrum-zcl<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [BTCP-community/electrum-zcl] Zclassic Electrum Wallet Will not connect to server (#115)
I downloaded the zclassic electrum wallet and it will not connect to the server. I sent zclassic from bittrex to my zclassic electrum wallet and it does not show the zclassic in my wallet however it does show on the zclassic block explorer.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/BTCP-community/electrum-zcl/issues/115 , or mute the thread https://github.com/notifications/unsubscribe-auth/AitKWIpxJHquqJuYPGiVCXqS3-cP-Bxxks5tXHvtgaJpZM4SORnH .  https://github.com/notifications/beacon/AitKWDjOIFwjAyeTNSu_5IL7vJy4kbeAks5tXHvtgaJpZM4SORnH.gif

I connected fine when i first downloaded it, yesterday tried to open and same issue cannot connect, any ideas

I turned off the proxy server this morning and it instantly connected.  I’m
in Cambodia traveling though so I’m not sure if that had something to do
with it or not.
On Thu, Feb 22, 2018 at 1:55 PM TA77<EMAIL_ADDRESS>wrote:

I connected fine when i first downloaded it, yesterday tried to open and
same issue cannot connect, any ideas
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BTCP-community/electrum-zcl/issues/115#issuecomment-367585317,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjAxJZnZl9Dn0-OffJj6364jI0EVVO6rks5tXQ9fgaJpZM4SORnH
.

already off, tried turning it on and still nothing

Was this solved? I'm having the same issue.

I was having the same problem, but through research found a working server. My wallet is working fine now, no issues.
https://www.reddit.com/r/ZClassic/comments/87lbpo/zclassic_community_electrumx_servers_are_up_and/


Any reason for requiring failure objects to derive from Error?

Hi!
If I want to return a failure using Result.Fail<MySuccessType>(new MyErrorType("hello")) then you already know it's a failure (since I called Fail) so you don't need the object type in order to tell a successful result from a failure. So is there a good reason or could you remove this constraint?
Cheers

Sorry, I dont understand your question. Can you please explain it in another way.

I'm wondering what the reason is for the constraint that all failure objects (that you pass to Result.Fail must derive from your Error type.

I most of the cases you want to pass error messages. Therefore there is a method to pass only strings. See https://github.com/altmann/FluentResults#creating-a-result
This library supports a hierarchical way of designing errors, details see https://github.com/altmann/FluentResults#root-cause-of-the-error Therefore you need a base class to save the required properties on the error object. See class for more details:
https://github.com/altmann/FluentResults/blob/master/src/FluentResults/Reasons/IError.cs
Whats the problem with this constraint?

It just seems a bit arbitrary. It's not a huge trouble for me to let my error objects derive from Error, I just think it would be cleaner if they didn't have to, since it's not really needed for anything.

You can also derive from IError if you want.


Parser bitbucket repayload

Codecov Report

Merging #16 into master will increase coverage by 4.58%.
The diff coverage is 86.84%.

@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
+ Coverage   72.34%   76.92%   +4.58%
==========================================
  Files           5        6       +1
  Lines          47       78      +31
==========================================
+ Hits           34       60      +26
- Misses         13       18       +5

Impacted Files
Coverage Δ

deeploy/handle_request.py
76.47% <72.72%> (-13.53%)
:arrow_down:

deeploy/parseRequest/service.py
95.23% <90.9%> (-4.77%)
:arrow_down:

deeploy/parseRequest/bitbucket.py
93.75% <93.75%> (ø)

Continue to review full report at Codecov.

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


Added ala to the units.py file

Actually the right one now

@mghosh00 the variables named after me should be capitalised
fix it pls

Plz accept me @ala1705


Github-search for enumerating  urls and secret tokens

Please include Github-search for enumerating  URLs and secret tokens as well .thanks

Hi!,
do you mean TruffleHog-like tools?
If yes, it will be added in the next patch for sure, stay tuned!

and also https://github.com/gwen001/github-search. Github may contain URLs and secrets as well

I've added this to my TODO list. Thanks for the suggestions!


LocalStroage and Session Storage not defined

I was trying to use  data i stored in the svelte store on a new liveview it however came as blank and navigating back the data was logged on the console am still new to liveview and i;m geussing the two are independed i tried calling the client session storage or local storge but neigther works ...
I have been looking for ways to pass data within liveview minus saving in the database initially am handling a multi stage form  how would you go through now that livesvelte is in picture..
sessionStorage is not defined
ReferenceError: sessionStorage is not defined
    at /home/maxino/Value_8/Realest8/realest8_platform/priv/svelte/server.js:9897:3
    at $$render (/home/maxino/Value_8/Realest8/realest8_platform/priv/svelte/server.js:9261:18)
    at Object.render (/home/maxino/Value_8/Realest8/realest8_platform/priv/svelte/server.js:9269:20)
    at render2 (/home/maxino/Value_8/Realest8/realest8_platform/priv/svelte/server.js:9938:22)
    at callModuleFunction (/home/maxino/Value_8/Realest8/realest8_platform/deps/nodejs/priv/server.js:32:23)
    at getResponse (/home/maxino/Value_8/Realest8/realest8_platform/deps/nodejs/priv/server.js:44:26)
    at Interface.onLine (/home/maxino/Value_8/Realest8/realest8_platform/deps/nodejs/priv/server.js:53:39)
    at Interface.emit (node:events:514:28)
    at [_onLine] [as _onLine] (node:internal/readline/interface:422:12)
    at [_normalWrite] [as _normalWrite] (node:internal/readline/interface:616:22)

I am trying to use local storage as opposed to hooks but it crashes with local storage not defined these are all in the svelte folder

Since you're rendering on the server it doesnt have access to localstorage or sessionstorage.
There's 2 options:

Call any localstorage/sessionstorage code inside the svelte onMount function. This ensures it's only called on the client.
Or disable Server Side Rendering (SSR)

Option 1:
<script>
  import {onMount} from "svelte"

  onMount(async () => {
    // Interect with sessionstorage or localstorage here
  })
</script>

Option 2:
<.svelte name="YourComponent" ssr={false} socket={@socket} />

Let me know if that works :)

thanks the example really helped

Thank you very much I had actually figured it out.. Thank you for your work and the help


Fixes disappearing delete and radio check button

Fixes #2894
Describe the changes you have made in this PR -
In the file public/js/data.js there is a function deleteOfflineProject which has some missing components resulting in the disappearing of radio button and the delete icon changing to a cross icon after the delete project confirmation is made. So, I redefined the function to display delete icon as the cross icon was not consistent with the dialog box design and used the custom-radio class.
I also made some changes in simulator/src/css/main.stylesheet.css to improve the dialog box components UI by changing the border-radius to make it more uniform.
Screenshots of the changes (If any) -
https://github.com/CircuitVerse/CircuitVerse/assets/122573982/191c1c6f-2b42-4566-8009-180c924920b7
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Please resolve code climate issues too.

hey @Prerna-0202 I believe I have made all the required changes and also resolved the code-climate issues.

@tanmoysrt I checked that the ruby rails cli run failed for the pr and I'm not able to find the cause of that. Can you help in telling what's the issue with the pr?

@tanmoysrt I checked that the ruby rails cli run failed for the pr and I'm not able to find the cause of that. Can you help in telling what's the issue with the pr?

It's not any issue with your code


Fix wither blinking for the missing players bossbar

I also removed some innecesary code, but i want to test this a bit before i merge, just in case

Is this ready?

@twizmwazin i've been testing this in a couple servers for some days and didn't seem to keep wither alive or anything like that, so i think it's ready

merged


add missing checkPriority

Signed-off-by: Thomas Labarussias<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area config

/area outputs

/area tests

What this PR does / why we need it:
Add missing checkPriority
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fjogeleit, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif,fjogeleit]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: ba0c3ab11609bad5803a0e5531d3b202b779ec1a


MultiMaps controll error

Hi.
http://jsfiddle.net/rm7r1jbz/8/ - When I click on map, then hide the layer with markers.
Error in console: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
If you comment out this line then the error disappears - https://github.com/tombatossals/angular-leaflet-directive/blob/master/src/directives/layers.js#L163
I think this error similar with this issue - https://github.com/Leaflet/Leaflet/issues/2877

This issue was moved to angular-ui/ui-leaflet#39

I'm going to rework&redesign angular-leaflet-directive to be compatible with Leaflet v1.0. It will mantain almost all its functionality, and will be compatible with the current features of the directive, but I must start from a fresh point, so I'm going to close this issue. If you think it must be worked with the new version, please reopen it.


Adds sr-gi

Adding myself to the list.
Thanks for the great initiative btw!

ACK
looking forward to playing with the eye of satoshi


Add version information command-line switch

Add --version command-line switch to use it for scripting purposes, for example to check if proper version of swiftgen is installed.

I don't get the issue?
That's already the case.
$ swiftgen --version
SwiftGen v0.7.4


drive pull does not recieve remote content

Steps to reproduce:
$ drive init ~/Cloud
$ cd ~/Cloud
$ drive pull

Output by drive pull:
Resolving...
X /My Tracks/...
X /My Tracks/...
X /My Tracks/...
X /My Tracks/...
X /My Tracks/...
X /My Tracks/...
X /My Tracks/...
X /My Tracks/...
X /My Tracks/...
X /My Tracks/...
X /My Tracks/...
Everything is up-to-date.

That's it. No files are transferred, directory stays empty (~/Cloud/.gd is created, though). No output shown, except provided above. Cannot add additional info, as no --debug or --verbose options provided.

Hello @tioteath, thank you for reporting this and welcome to drive!
So doesn't drive show you that you have clashing file names right there with the X's?
There are a couple of reasons why it won't pull with conflicts e.g in the README and mainly due to the confusion previously encountered with the file system expecting unique file names within a dir but Google Drive allows for clashing names within the same dir. This confusion has plagued users quite a lot.
Also drive version?
Btw there are ways to turn of rejection of clashing file names

So doesn't drive show you that you have clashing file names right there with the X's?

Well, according to the message this is hard to understand what's going on exactly. Message kind of "File clash detected, aborting" would be helpful. The message "Everything is up-to-date." is especially confusing, as it definitely not up-to-date. Mainly because of that message I've decided that drive misbehaves.

No, not really. I posted above exact message I've got, except I replaced filename with '...'. But you're right, clashes was the problem.

Addressed by PR https://github.com/odeke-em/drive/pull/244. Thank you for reporting this.


key cant be null and cache tostring

@Evangelink side note: feel free at any time to push commits directly to my PR branches


Purpose of the Dockerfile Base Image if we are installing torch and torchvision?

Hi @otamajakusi, sorry if this question is rather unintellectual but may I know what is the purpose of having this base image:
FROM nvcr.io/nvidia/l4t-pytorch:r32.5.0-pth1.6-py3 instead of SCRATCH since it only comes with torch and torchvision packages and we are already installing those in the Dockerfile? Would love some clarification from you. Thanks again!

@joneswilliam1 Oh, I think you're correct. nvcr.io/nvidia/l4t-pytorch:r32.5.0-pth1.6-py3 is an image that has been used since yolov5 supported python3.6. Currently you know yolov5 doesn't support python3.6, so pytorch should be built by yourself.
I think nvcr.io/nvidia/l4t-base can be used.
Thanks!

@otamajakusi Amazing! Thank you very much. Will try it out with the l4t-base image hopefully it will take a little less time build the Dockerfile :)

@otamajakusi update, I have just tested out building the Dockerfile with the l4t-base image and everything seems to work normally. I just have 1 question if you don't mind, you mentioned that the l4t-pytorch image supported python3.6 however I believe recently they have updated to python3.7 in the image nvcr.io/nvidia/l4t-pytorch:r32.5.0-pth1.7-py3 so will this be satisfactory enough and we do not need to even build torch and torchvision from scratch?
Another thing is I thought the reason that you were building torch and torchvision libraries from scratch was because the yolov5 requirements required higher version of torch and torchvision libraries and the l4t-pytorch did not satisfy those requirements. Is that also true?

@joneswilliam1
5a758413de45f454ecb08192c8ff3e6ffdbf4422 uses l4t-base. this fixes package installation problems. thanks!

they have updated to python3.7 in the image nvcr.io/nvidia/l4t-pytorch:r32.5.0-pth1.7-py3 so will this be satisfactory enough and we do not need to even build torch and torchvision from scratch or?

No. All their nvcr.io/nvidia/l4t-pytorch:* containers are python3.6. See https://ngc.nvidia.com/catalog/containers/nvidia:l4t-pytorch
Also you can confirm by running
docker run -it --rm nvcr.io/nvidia/l4t-pytorch:r32.5.0-pth1.7-py3 python3 -c "import sys;import torch;print(sys.version);print(torch.__version__)"

So we have to build pytorch from scratch with python3.7+ to use current yolov5.


Infinite Syntax Errors

Code entered to REPL:
rm(o1)

or
anything(1231312312413012340120oo)

Result:
1: rm(o1)
Syntax Error: Expected ';'
1: rm(o1)
Syntax Error: Expected Expression
1: rm(o1)
... and so on

It also produces 3/2/1 syntax errors when:
3 Errors:
>> anything()
1: anything()
SyntaxError: Expected ';'
1: anything()
SyntaxError: Expected an expression
1: anything()
SyntaxError: Expected ';'

2 Errors:
>> anything(1)
1: anything(1)
SyntaxError: Expected ';'
1: anything(1)
SyntaxError: Expected ';'

or:
>> anything(1);;
1: anything(1);;
SyntaxError: Expected ';'
1: anything(1);;
SyntaxError: Expected an expression

1 Error:
>> anything(1);
1: anything(1);
SyntaxError: Expected ';'

Try to compile with this command: nimble build --multimethods:on.

Or if you are using Mac or Linux, you can do this: ./build.sh.
Before running the command you may need to run this chmod +x build.sh

Thanks.


Is glycopyrronium hospital only?

We have been contacted by a user querying if glycopyrronium injection should be included as "hospital only". Searching the dmd browser we find this list of products and it appears that only two, the Accord gylcopyrronium products are designated "hospital only".
This is a classic mismatch of multiple AMPs to BNF codes. It is unclear if the designation is intentional or not so I contected the company.
Accord declare that this is a hospital only line.
We should manually exclude from definition in our measure.

The BSA team have amended their methodology for classifying "hospital only"

In the past on dm+d for these “hospital-only” pack sizes, they would have been marked as “hospital-only” at both the presentation (AMP) and pack (AMPP) levels on dm+d. Now on reviewing these products on dm+d we agree that to reduce confusion, it makes sense to remove the ‘hospital only’ flag at the presentation level and only mark the pack level with the ‘hospital indicator’.

Therefore glycopyrronium no longer needs to be manually updated as the designation has been removed at AMP level.
We should remove manual exception when we get a chance.

BSA gave removed the hospital only designation at P level from the dm+d.


Access role variables in tests

I'm quite new to pytest/testinfra and I was wandering which is the proper way to access ansible role variables and default to reuse them into the test.
My focus is to take all constants (e.g. configuration files path, usernames, etc..) from role-under-test defaults/main.yml and vars/main.yml to avoid constant duplication in test with may become a pain to maintain.
I suppose the key is something similar to the test_sample.py
testinfra_hosts = testinfra.utils.ansible_runner.AnsibleRunner(
    '.molecule/ansible_inventory.yml').get_hosts('all')

I tried to perform some debug on its methods, but couldn't sort this out, could you please provide any hint? Any update to docs on this would be greatly appreciated.

@aroundthecode you'll need to check testinfra for this.  There are quite a few questions on this topic already.


Unable to use ortex from main

Hey,
I am trying to use silero_vad and for that it seem to me, I need an up to date version of ort and therefore the current versin of "ortex" in main.
I am doing this on window11.
I tried the following. In my dependencies I added ortex:
      {:ortex, github: "elixir-nx/ortex"}

And then I did:
mix deps.get
mix deps.compile ortex

Resulting in:
==> ortex
Compiling 6 files (.ex)
Compiling crate ortex in release mode (native/ortex)
...
Compiling lib/ortex/native.ex (it's taking more than 10s)
   Compiling ortex v0.1.0 (<project_dir>\deps\ortex\native\ortex)
   = note: `#[warn(unused_imports)]` on by default

warning: `ortex` (lib) generated 1 warning (run `cargo fix --lib -p ortex` to apply 1 suggestion)
    Finished release [optimized] target(s) in 19.43s

== Compilation error in file lib/ortex/native.ex ==
** (File.CopyError) could not copy from "<project_dir>/_build/dev/lib/ortex/priv/native/libonnxruntime.so" to "<project_dir>/_build/dev/lib/ortex/priv/native/libonnxruntime.so.1.17.0": no such file or directory
    (elixir 1.16.1) lib/file.ex:864: File.cp!/3
    lib/ortex/native.ex:9: (module)
could not compile dependency :ortex, "mix compile" failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile ortex --force", update it with "mix deps.update ortex" or clean it with "mix deps.clean ortex"

Now, when I look into <project_dir>/_build/dev/lib/ortex/priv/native/
I find a file libortex.dll but not the wanted lionnxruntime.so.
I will look further into this, but if anyone has a hint ...
Thanks,
Nathan

I get the same error under WSL2, only in that case the existing file is called libortex.so.

Hi Nathan, thanks for the detailed description.
I think the issue is coming from lib/ortex/util.ex, specifically here which assumes Linux:
    case "libonnxruntime.so.1.17.0" in onnx_runtime_filenames do
      true ->
        nil

      false ->
        File.cp!(
          Path.join([destination_dir, "libonnxruntime.so"]),
          Path.join([destination_dir, "libonnxruntime.so.1.17.0"])
        )
    end

Does manually removing this chunk solve the issue? We unfortunately do not have Windows machines readily available to check

it makes it compile!
I have solved it for me before, by using ortex 0.1.9 and copying onnxruntime.dll and onnxruntime_providers_shared.dll into my project folder.
This is the code that is working with ortex 0.1.9:
    {output, h, c} = Ortex.run(model, {input, sr, h, c})
    result = output |> Nx.backend_transfer()
    [result] = Nx.to_flat_list(result)

That worked, because the result was indeed a one element tensor with a value between 0 and 1.
But with ortex from main, I get a strange pattern marching error on the last line, which is caused because the result is the outputs have changed.
The shapes of the output are now:
Nx.shape(output) = {2,1,64}
Nx.shape(h) = {1,1}
Nx.shape(c) = {2,1,64}
Suggesting that output is suddenly returned in the middle.
I find that very odd, but maybe there is an explanation?
Thank!

Good find, that's interesting... I validated that it does indeed switch the order of the output. @gregszumel do you think this could be related to the ort 2.0 changes in main?

Sorry for the late reply! It definitely may have something to do with the ort 2.0 changes. I'll dig into this today.

I could confirm that there's an output ordering discrepancy in vanilla ort 2.0, so I think it's safe to assume that ortex is just propagating this issue. Specifically, ort moved to using hash-maps for outputs, which doesn't preserve the order of insertion (which I assume is the main issue here). I'll open an issue with them, and ask for guidance as to how they recommend we proceed.

FYI, I have the same issue on OSX. Commenting the suggested lines from lib/ortex/util.ex makes this compile.

I also had the same issue on OSX, and commenting those lines made it work for me.

we've updated main with fixes for shared library handling. I'm going to close this issue, but please reopen if this did not fix your issue


Unsuported architecture during upload to iTunes Store

I create application with react-native-ble-plx dependency. On phone everything work correctly, but after I archive the bundle for iTunes Store, during the validation of bundle I got error:
iTunes Store Operation Failed Unsupported Architectures. The executable for Drydeco.app/Frameworks/BleClientManager.framework contains unsupported architectures '[x86_64, i386]'.
react-native-cli: 2.0.1
react-native: 0.49.5
react-native-ble-plx: ^0.6.5
I the embeded libraries it is displayed corretly in Xcode.

If you are using carthage you should not manually link and embed framework files. It is the job of copy-framework script to do that correctly as far as I know.

When I remove Linked library, nothing changed.

I'm sure that adding BleClientManager.framework to Embedded binaries is not required. Carthage script should do that for you. Maybe because of that XCode is embedding framework by itself without stripping from unnecessary architectures.

@Cierpliwy it does not change anything when I add or remove BleClientManager.framework from Embedded binaries, but still I am not able to publish archive to iTunes store because of same exception:
 iTunes Store Operation Failed Unsupported Architectures. The executable for Drydeco.app/Frameworks/BleClientManager.framework contains unsupported architectures '[x86_64, i386]'.

@Cierpliwy any update? We are still facing the same issue, and we are not able to publish application to the appStore because of this issue? Any idea what can be wrong?

@psloboda could you look at your target Build Phases and check if you have build script that does /usr/local/bin/carthage copy-frameworks and if it have BleClientManager.framework in input files?

@paweljaneczek  Yes, I go throught setup manual more times to check the project setup.

@psloboda screenshot that you've uploaded only showing General section, not Build Phases.
Also library should not be in Embeeded Libraries, only in Linked Frameworks and Libraries

@paweljaneczek sorry, I probably upload wrong screenshot

Please remove library from embed frameworks.

@paweljaneczek thank you a lot, this solve my issue, I had to also update the react-native-ble-plx because of some swift incompatibility issue reported here https://github.com/Polidea/react-native-ble-plx/issues/274 but now everything works corretly.

Great to hear. I am glad that could help you!
Closing issue.


#16 Replaced string.Format with FormatWith usage

name: Fix for #16
about: Wrong message error displayed
Description
Replaced string.Format with FormatWith usage
PR Domain
Replaced string.Format with FormatWith usage

[ ] Add feature
[x] Fix bug
[ ] Fix Typo
[ ] Extend support

Issue relation
This PR is related to issue #16
Screenshots
'No Screenshots'

oops, fixed it

LGTM


Doesn't compile on latest nightly

error[E0015]: calls in constant functions are limited to constant functions, tuple structs and tuple variants
   --> /home/user/.cargo/registry/src/github.com-xxxx/staticvec-0.10.8/src/lib.rs:771:5
    |
771 |     self.mut_ptr_at_unchecked(length).write(value);
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

https://crates.io/crates/embedded-graphics/0.7.1

The reversion that was causing this issue has been un-reverted now, so the most recent nightly should be able to compile the crate successfully.


Made changes to support pluggable schema registry

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

@shirshanka Sorry about that I opened this too soon. I am still working on this

I will reopen this PR once i get chance to take care of these PR comments


Problem if use in TS context

Hi,
There is a problem with Type on TransformComponent component in TS context (class component)

error :
Type 'TransformComponent' is missing the following properties from type 'ElementClass': context, setState, forceUpdate, props, and 2 more.ts(2605)

https://codesandbox.io/s/boring-firefly-u35d3
Do you have an idea of the problem ?
Thanks.

@PooLP Modifying my tsconfig helped me with this issue:
"allowSyntheticDefaultImports": true /* Allow default imports from modules with no default export. This does not affect code emit, just typechecking. */

@h3nn3 : thanks, this is what i also did while waiting for the bug to be fixed ;)


Out of date

Can you please update this with data from http://projects.fivethirtyeight.com/2016-endorsement-primary/? Or make that data otherwise exportable?

Meh


PL-300 Changes

LODS_Lab_Review_PL300.xlsx
Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:
Please all changes in the attached spreadsheet.

This will be part of a larger lab update later this month.


Add doctrine odm support to be able to use mongodb #70

PR for #70
Think @stof in #71 and #81 meant about something like this.
cc @BernardoSilva @fnash
Please review if this can replace replace PR #71 and and #58
Note that I have tested it only with orm since I don't have mongo enabled environment.

Looking good. :+1:
Nice work @tmilos


Need understanding how we can use types.image in case of three.js

I'm trying to link the types.image theatre property to work with my MeshStandardMaterial map property, Could you suggest this is viable/feasible with the current implementation.
the onValuesChanges function return object in form
{ id: string; type: "image" }

The id only shows the image name.
There is a suggestion in the Docs: that a custom interpolator might be required, please give insights on the usage?
Another thing: https://theatre-playground.vercel.app/shared/dom is down.

Hi @AriaMinaei, could you please suggest on above?
Thanks :)

Hi @AriaMinaei,
Could you please suggest on this?
Thanks :)

Looks like the link that is supposed explain this is broken. Here it is.
Basically:
onst object = sheet.object('My Object', {
  texture: types.image(undefined, {
    label: 'Texture',
  }),
})

object.onValuesChange(({ texture }) => {
  setImageUrl(project.getAssetUrl(texture))
})


test: all_correct

Summary by Sourcery
Add a test case for the 'all_correct' function to ensure it correctly handles scenarios where the 'hamming' metric is NaN and defaults to using 'mae'.
Tests:

Add a test for the 'all_correct' function to verify its behavior when the 'hamming' metric is NaN and falls back to 'mae'.

Thanks for spotting this @n0w0f, that is super important and great that you caught it 🙏🏼


Updated babelfish-query-handling.md to clean up grammar and chattiness

Signed-off-by: susanmdouglas<EMAIL_ADDRESS>Description
This update removes chattiness and cleans up grammar in query_handling.md.
Issues Resolved
This update removes chattiness and cleans up grammar in query_handling.md.
Check List

[x ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

This page needs to be revisited/removed per Rob - the user shouldn't modify the setting (it is for internal use only).


docs(textfield): fix documentation error

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Translation / Localization

Hi there,
thanks for the effort on this project! Any plans to have these lists translated to other languages (e.g. headlines, jobs) or localized to other countries (e.g. colleges, dates) where appropriate? Would be glad to help - in my case for a German version.
Best
Tobias

localization would be great. I'd recommend having the locale as part of the file name or in the folder structure so it can be read programmatically, e.g. addressgermany.json should be address_de.json or de/address.json or address/de.json (leaning towards the first option. but depending on the number of lists and languages, a folder structure might be good - or can be by logical categories)
The naming scheme should be simple but for for both, languages and locations. For example the airports_us.json (US being the 2 letter country code) quotes_de.json (DE being the locale). Also should the default one be no code (being English) or _en to be explicit?

Just saw that there are localized addresses and names already - not sure why I did not see this at first... would be interesting to hear from @jperriere and others whether translations (and more localizations) would fit the basic idea/concept or rather be an overkill.

Hi,
Thanks both of you for your interest in contributing to the Lists. I'm on vacation with limited access to internet, sorry I didn't get back to you sooner.
The vision I have for this project is that we cover the most use cases possible. So the most content we have, the better. As you saw I already started to make some lists country-specific : address and names.
I think the smarter way to go about it is to make it country-specific and not language-specific. For example, Portugal and Brasil both speak portuguese but don't necesarily have the same address format. For the sake of simplicity I'd rather have all the lists in one folder. So we could experiment  with a naming convention like this : address_de.json.
tl;dr : Thanks for your help, go 👍
Julien


[IOTA-22] [IOTA-23]

Rebased the new code and incorporated the changes for the jar name and moving project from spray to play
And hence fixed the issue https://issues.apache.org/jira/browse/IOTA-23?filter=-4&jql=project %3D IOTA ORDER BY createdDate DESC

@barbaragomes : Please review this pull request and let me know your concerns. I have rebased with the new code and made the changes and also please discard the pull request https://github.com/apache/incubator-iota/pull/6 as it is not mergable. Thanks !

@shiv4nsh We apologize for the late response.
I understand that we haven't give you much details about this issue, my apologies.
We haven't accepted this PR because we are working on a better specification of the first steps to integrate play as well as some UI prototypes, so we can make this issue more clear.
We appreciate your contribution.
We will be updating this issue with more details soon.
Thanks.

@barbaragomes : Ok please provide the specifications of this ticket so that we can work efficiently on this ticket. Thanks !

@barbaragomes and @tonyfaustini : I have rebased the code and done the changes again , and have made the pull Request against it i.e #19 and #20 that contains changes for this PR and hence i am Closing this ! Please review those ! Thanks


determine and fix the conditions when the math brute force "divide_cr" test should be run

Currently, the math brute force "divide_cr" test checks whether CL_FP_CORRECTLY_ROUNDED_DIVIDE_SQRT is in the query result for CL_DEVICE_SINGLE_FP_CONFIG.  If it is, it runs the divide_cr test for 32-bit float types and 64-bit double types.
With the latest code in the fp16-staging branch, the divide_cr test is additionally run for 16-bit half types.
Is this correct?
Notes:

The minimum accuracy for an fp64 and fp16 divide is already 0 ULP for the full profile, without passing any special build options.  It is 3 ULP for fp64 and 1 ULP for fp16 for the embedded profile, though.
The name of the build option is -cl-fp32-correctly-rounded-divide-sqrt, and the description refers only to "single precision floating-point" specifically, so it is not clear this option should apply to fp64 or fp16 regardless.
I found this issue while investigating "divide_cr", but the same questions apply to "sqrt_cr" also.

Moving to mobica-backlog, as discussed in the March 26th teleconference.
At the moment, this should probably be done as a PR to the fp16-staging branch, since it will be part of the fp16 fixes.


[typescript] Incompatible types between React.forwardRef and OverridableComponent

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
When I try to define a wrapper for a component that uses the OverridableComponent type helper and uses React.forwardRef, I get a typescript error:
import React from "react";
import MUITypography, { TypographyTypeMap, TypographyProps } from "@mui/material/Typography";
import { OverridableComponent } from "@mui/material/OverridableComponent";

export const Typography: OverridableComponent<TypographyTypeMap> = React.forwardRef(function Typography<
  D extends React.ElementType
>(props: TypographyProps<D>, ref: React.Ref<HTMLSpanElement> | null) {
  return <MUITypography ref={ref} variantMapping={defaultVariantMapping} {...props} />;
});

Type 'ForwardRefExoticComponent<Pick<SystemProps<Theme> & { align?: "inherit" | "left" | "right" | "center" | "justify" | undefined; children?: ReactNode; classes?: Partial<TypographyClasses> | undefined; ... 5 more ...; variantMapping?: Partial<...> | undefined; } & CommonProps & Omit<...>, string | ... 1 more ... | symb...' is not assignable to type 'OverridableComponent<TypographyTypeMap<{}, "span">>'.
  Type 'ReactElement<any, string | JSXElementConstructor<any>> | null' is not assignable to type 'Element'.
    Type 'null' is not assignable to type 'ReactElement<any, any>'.ts(2322)

Expected behavior 🤔
I would expect types to be compatible
Steps to reproduce 🕹
In a typescript project define this in a file:
import React from "react";
import MUITypography, { TypographyTypeMap, TypographyProps } from "@mui/material/Typography";
import { OverridableComponent } from "@mui/material/OverridableComponent";

export const Typography: OverridableComponent<TypographyTypeMap> = React.forwardRef(function Typography<
  D extends React.ElementType
>(props: TypographyProps<D>, ref: React.Ref<HTMLSpanElement> | null) {
  return <MUITypography ref={ref} variantMapping={defaultVariantMapping} {...props} />;
});

Context 🔦
I have an internal package to isolate Mui and either re-export components directly, or wrap them.
If I only export my component without doing an explicit typing with OverridableComponent, I don't have a proper autocompletion working, which is why I'd like to use that in the first place.
If I update the OverridableComponent to the following (returning JSX.Element | null instead of just JSX.Element)
export interface OverridableComponent<M extends OverridableTypeMap> {
  <C extends React.ElementType>(
    props: {
      /**
       * The component used for the root node.
       * Either a string to use a HTML element or a component.
       */
      component: C;
    } & OverrideProps<M, C>,
  ): JSX.Element | null;
  (props: DefaultComponentProps<M>): JSX.Element | null;
}

Then the type issue disappears.
Your environment 🌎

`npx @mui/envinfo`
  System:
    OS: macOS 12.3.1
  Binaries:
    Node: 14.19.1 - ~/.nvm/versions/node/v14.19.1/bin/node
    Yarn: 1.22.15 - ~/.yarn/bin/yarn
    npm: 6.14.16 - ~/.nvm/versions/node/v14.19.1/bin/npm
  Browsers:
    Chrome: 100.0.4896.127
    Edge: Not Found
    Firefox: 97.0.1
    Safari: 15.4
  npmPackages:
    @mui/system: 5.5.0 => 5.5.0

This is not browser related.
Typescript version: 4.5.4
@types/react-dom: 17.0.14
@types/react: 17.0.43

Due to Typescript limitations, wrapping a generic component in a forwardRef causes the generic parameters to be lost (it's similar to what's happening when wrapping a generic component in a styled() utility, as described in https://mui.com/material-ui/guides/typescript/#complications-with-the-component-prop).
To work around this issue, cast whatever the forwardRef(...) returns to the correct type:
This should work:
import React from "react";
import MUITypography, { TypographyTypeMap, TypographyProps } from "@mui/material/Typography";
import { OverridableComponent } from "@mui/material/OverridableComponent";

export const Typography: OverridableComponent<TypographyTypeMap> = React.forwardRef(function Typography<
  D extends React.ElementType
>(props: TypographyProps<D>, ref: React.Ref<HTMLSpanElement> | null) {
  return <MUITypography ref={ref} variantMapping={defaultVariantMapping} {...props} />;
}) as OverridableComponent<TypographyTypeMap>;

Let me know if this helps.

Hi @michaldudak thanks for your reply 🙏
In the issue description I've outlined a change to MUI lib's OverridableComponent that solved the described issue, have you had a chance to try it?
I'm not sure why OverridableComponent is returning just a JSX.Element rather than JSX.Element | null, and when I dived into that it seems to me that it was the source of the incompatibility between ForwardRefRenderFunction and my wrapped component, rather than a generic type issue. In any case, that's rather annoying and I don't think this should be marked as "expected behaviour" (and the issue could be kept open?)

Hi @HHK1, sorry for the delayed response. I took a closer look at OverridableComponent and I don't see a reason for not including null as the return type. Would you like to create a PR? Please not that we have two versions of OverridableComponent - one in @mui/material and the other in @mui/types.

We ran into the same problem in our project and i just found this issue. I seems like there was no PR for this yet, so i took the liberty to open one https://github.com/mui/material-ui/pull/35311b.com/mui/material-ui/pull/35311

@michaldudak - Your solution for casting the returned value of the forwardRef solves the problem, but the issue still exists in "@mui/material": "5.11.0".
It seems that this PR didn't solve the problem.

@michaldudak - Your solution for casting the returned value of the forwardRef solves the problem, but the issue still exists in "@mui/material": "5.11.0".
It seems that this PR didn't solve the problem.

I cannot confirm.
We can now do
import React from 'react';
import type { TypographyTypeMap, TypographyProps } from '@mui/material/Typography';
import MUITypography from '@mui/material/Typography';
import type { OverridableComponent } from '@mui/material/OverridableComponent';

export const Typography: OverridableComponent<TypographyTypeMap> = React.forwardRef(
  (props: TypographyProps, ref: React.Ref<HTMLSpanElement> | null) => (
    <MUITypography ref={ref} {...props} />
  ),
);

That does not produce a Typescript Error, which is what was fixed by the PR.
Either you have a different issue or something went wrong updating your @mui/material

@rotemee Please open a new issue and provide a codesandbox with reproduction steps if you still encounter issues in this area.

found this issue while trying to figure out how to properly wrap mui components. I am struggling with how to get both forwardRef and specifying a component prop to play nicely together.
// button.component.tsx
import React from "react"

import {
  ButtonTypeMap,
  Button as MuiButton,
  ButtonProps as MuiButtonProps,
} from "@mui/material"
import { OverridableComponent } from "@mui/material/OverridableComponent"
import MUITypography, {
  TypographyProps,
  TypographyTypeMap,
} from "@mui/material/Typography"

export type ButtonProps = MuiButtonProps

export const Button: OverridableComponent<ButtonTypeMap> = React.forwardRef(
  function Button<C extends React.ElementType>(
    props: MuiButtonProps<C>,
    ref: React.Ref<HTMLButtonElement> | null
  ) {
    return <MuiButton ref={ref} {...props} />
  }
) as OverridableComponent<ButtonTypeMap>

gives me TS issues if the code that uses the component is something like:
<Button component="a">link button</Button>

I'm composing the components in the following pattern, and if I try to add the muiName property with Typography.muiName = COMPONENT_NAME,  i get an error.
Typography
import type {OverridableComponent} from '@mui/material/OverridableComponent';
import MuiTypography from '@mui/material/Typography';
import type {TypographyProps as MuiTypographyProps, TypographyTypeMap} from '@mui/material/Typography';
import clsx from 'clsx';
import {forwardRef} from 'react';
import type {ElementType, Ref, ReactElement} from 'react';
import './typography.scss';

export type TypographyProps<
  C extends ElementType = ElementType,
  D extends ElementType = TypographyTypeMap['defaultComponent'],
  P = {},
> = {
  component?: C;
} & Omit<MuiTypographyProps<D, P>, 'component'>;

const COMPONENT_NAME: string = 'Typography';

const Typography: OverridableComponent<TypographyTypeMap<TypographyProps>> = forwardRef(
  <C extends ElementType = ElementType>(
    {className, ...rest}: TypographyProps<C>,
    ref: Ref<HTMLSpanElement>,
  ): ReactElement => {
    const classes: string = clsx('oxygen-typography', className);

    return <MuiTypography ref={ref} className={classes} {...rest} />;
  },
) as OverridableComponent<TypographyTypeMap<TypographyProps>>

Typography.muiName = COMPONENT_NAME;

export default Typography;

Error

Any recommended approach to overcome this typing issue.
I've tried the following:
+ as OverridableComponent<TypographyTypeMap<TypographyProps>> & { muiName: string }

With the above, component prop works for native elements like div, span etc, but breaks for already composed MUI components.
✅ Works
<Button component="a" href="https://test.com" />;

❌ Breaks


Database name in configuration has no effect other than labeling the scrape output

We have to monitor several schemas on one host, so we made a config like this:
connections:
 - connection: myuser/mypass@myserver:1850/SOMEID
   database: db1
   instance: db1
 - connection: myuser/mypass@myserver:1850/SOMEID
   database: db2
   instance: db2
 - connection: myuser/mypass@myserver:1850/SOMEID
   database: db3
   instance: db3
[...]

The scrape returns tablemetrics for every schema separately, but they are all identical, propably the default schema based on the connection string. It seems to me that "database" is just a value given back in the scrape and does not trigger a "use [schemaname]" in the scrape process. Even if I enter a nonexisting schema there, I get the same result. Is that intended?

Problem "solved" as there seems to have been a general misunderstanding regarding tablespaces and tables/schemas in Oracle. So nevermind, I grew up with MySQL/MariaDB and thus had no idea of the concept.


museums page won't load coming from explore

tap on museum page from explore and nothing ever loads, works fine in safari

It seems to work fine for me. Are you still experiencing this issue?

@alloy seems to be working fine. I think we have some issues related to first-install or first-session and getting force views. Just a hypothesis but I think it might explain some of the issues I've been seeing. Let's close this for now


Make VID/PID global vars passed into CheckDevice()

The docs say to modify id1 with the device's VID/PID, however, id1 goes unused in CheckDevice(). Instead, the function calls dev := AHI.Instance.GetDeviceId(false, 0x05AC, 0x0204, 1) (with that hardcoded value).
Changes:

make VID/PID global variables to be modified and passed into CheckDevice (and updated README to reflect this)
Removed unused id1
Cleaned up code a bit

great work! thanks for formatting this! how may I cite you in my documentation?

great work! thanks for formatting this! how may I cite you in my documentation?

A credit in the Special Thanks section of the README would be appreciated :)


Removing FlakyTest: memory_test.cc

Removing the test, as behavior varies with system arch also depends on OS and compiler behavior.
Also, the test doesn't test any MXNet related feature.
Github issue:  https://github.com/apache/incubator-mxnet/issues/9649
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@KellenSunderland @nswamy @sandeep-krishnamurthy

Adding @cjolivier01 who is the author of these tests.

Checked with @cjolivier01 offline and there's no concern from him. On the test itself, I think the reporting issue includes concerns that can be fixed by only including this test in our controlled CI environment.
I'm merging this for now to unblock progress.


Add CI trigger on 'push' to 'master'/'release_*' branches

Signed-off-by: Ben Alkov<EMAIL_ADDRESS>
CLOUDBLD-1370

Maintainers will complete the following section

[ ] Commit messages are descriptive enough
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

[x] Checks ran in this PR

[x] Merging a PR to 'master' looks like this.

Also note the (clickable) green check on the front page

[x] Pushing to a 'release_*' branch looks like this. It will also have a green check when selected as the active branch.

N.B. the merges to 'master' and 'release_*' are in my fork.

As an aside, Coveralls seems to be working quite nicely with this; this might restore the missing master-coverage diff


Update formatting and clean up README.md

Includes links to create a new issue and aligns the list formatting so that it renders properly.

Thanks!


How to customize URL

@ZTL-UwU how can I customize the URL as well
The path is always top level section and then the children like getting-started/introduction
Can I have like a docs/introduction, docs/components/bento-grid
This is so that the breadcrumb I'll customize will tally with the URL as well

You can just create a folder called docs in the content folder.
content/
  index.md
  docs/
    introduction.md
    components/
      bento-grid.md

I'd still like it to have the top level heading though.
so:
Getting Started

introduction
installation

Components

bento-grid

etc.

Hmm, I don't think this level of customization of the URL is possible through nuxt content's file based routing.
However, what you can do perhaps is to override the sidebar and maintain the links manually.
https://github.com/unovue/shadcn-vue/blob/ff6d9d0da657a41582beec2b63d6b7e5683ddc8f/apps/www/.vitepress/theme/layout/DocsLayout.vue
https://github.com/unovue/shadcn-vue/blob/ff6d9d0da657a41582beec2b63d6b7e5683ddc8f/apps/www/.vitepress/theme/config/docs.ts

This is not the behaviour I want. Is it possible to have this without having docs as a top-level heading?


Remove jsdom dependency

Hi,
I think the dependency on jsdom is unnecessary. For the purpose of just converting from html to jade, I do believe using the dom produced by htmlparser should be sufficient.
There are a lot of problem surrounding jsdom. Mainly because jsdom has a hard dependency on contextify...which is a binary library that isn't pure js. Contextify has build issue in a lot of environments and some environment (like cloud9 ide) does not allow binary libraries to run on their platform.

Interesting suggestion. I used jsdom instead of using htmlparser directly because I wanted to cover javascript generated document as well. Perhaps a good compromise is to use static HTML conversion as default and make dynamic document conversion an option.

I just realized that removing jsdom dependency from html2jade will require adding a htmlparser-specific layer to simulate DOM API which is required to continue supporting convertDocument method.
Given that amount of change is not trivial, I'm going to defer this issue until later. Of course, you are welcome to fork and hack as always if you can't wait. :-)


Include md output: cli, search commands. Closes #4294

Closes #4294

Thank you for this addition @Saurabh7019, we'll try to review it ASAP when you are ready! ❤

Hi @milanholemans, Could you please re-run the pipelines when you have time? The issue doesn't seem to be related to my changes, and I am wondering if re-triggering them could resolve the problem.

Done!

@Saurabh7019 just checking, is this PR ready to review? Or are some changes needed?

ready to merge 🚀

ready to merge 🚀

merged manually. Thanks for your awesome work. You rock 🤩


re-subscribe, but not received message

Not received second message.
iex(6)> {:ok, pubsub} = Redix.PubSub.start_link()
{:ok, #PID<0.459.0>}
iex(7)> {:ok, client} = Redix.start_link()
{:ok, #PID<0.461.0>}

iex(8)> Redix.PubSub.subscribe(pubsub, "my_channel", self())
:ok
iex(9)> flush
{:redix_pubsub, #PID<0.459.0>, :subscribed, %{channel: "my_channel"}}
:ok
iex(10)> Redix.command!(client, ~w(PUBLISH my_channel hello))
1
iex(11)> flush
{:redix_pubsub, #PID<0.459.0>, :message,
 %{channel: "my_channel", payload: "hello"}}
:ok
iex(12)> Redix.PubSub.unsubscribe(pubsub, "my_channel", self())
:ok
iex(13)> flush
{:redix_pubsub, #PID<0.459.0>, :unsubscribed, %{channel: "my_channel"}}
:ok

iex(14)> Redix.PubSub.subscribe(pubsub, "my_channel", self())
:ok
iex(15)> flush
{:redix_pubsub, #PID<0.459.0>, :subscribed, %{channel: "my_channel"}}
:ok
iex(16)> Redix.command!(client, ~w(PUBLISH my_channel hello))
0
iex(17)> flush
:ok

Hey @takeru, thanks for the detailed and easy to reproduce bug report. So sorry it took me months to fix this, it was quite an easy fix but I only dedicated some time to it now (so much stuff to do!). Anyhow, I closed this in 27cd872. I will release a new version in the next few days but you can try the fix by trying out the master branch :)


feat: allow table drilldown to a new window

Description of what you did:

My PR is a:

[ ] 💥 Breaking change
[ ] 🐛 Bug fix
[ ] 💅 Enhancement
[x] 🚀 New feature

Please confirm that your PR fulfills these requirements

[x] Multiple commits are squashed into one commit.
[x] The commit message follows Conventional Commits, which allows us to autogenerate release notes; e.g. fix(plugins/plugin-k8s): fixed annoying bugs
[x] All npm dependencies are pinned.

/lgtm


Fixing WebProxy._parseSource exception in case of a request with a missing HTTP Host header

Hi Thomas,
I recently noticed that occasionally, the reverse proxy based on Redwire we use in my current project dies with an exception in WebProxy._parseSource due to some client omitting the HTTP Host header from its request that WebProxy._parseSource is expecting to be present. I wrote a small fix that falls back to the configured hostname and port just in that case; I compiled it using my CoffeeScript binary, which is unfortunately at version 1.4 instead of your version :-/

Cheers for the pull request. Merged and released as v2.1.0

Hey, thanks for merging and releasing them that quick :-)


My VS chnaged his settings from English to German. How can I change it back to english

Issue Type: Feature Request
Hello,
after update the language changed to german, where do I find the option to change it back. I cannpt find it.
Best regards
Samuele
VS Code version: Code 1.59.1 (3866c3553be8b268c8a7f8c0482c0c0177aa8bfa, 2021-08-19T11:56:46.957Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

can you search for "Display language" in the command palette (ctrl+shift+p)?

Also, I'm curious how this happened... did you have the German language pack installed?


Question regarding "Supported Microsoft Teams Room systems"

Hello, I am struggling to understand the exact meaning of the "Supported Microsoft Teams Room systems" section.
From my understanding, are those devices that already have the Microsoft Teams Rooms solution installed on them. When trying to create a MS Teams Rooms Console, wouldnt the NUC be the only piece of hardware required?
I thought, that I could create a MS Teams Room Console with only the Intel NUC by installing the image from the "Configure a MS Teams Rooms Console" site, because I have no need for the touchscreen Interface like a "Logitech TAP".
My question is, could I configure a MS Teams Room Console with only a Intel NUC, or do I need one of the listed touchscreen interfaces as well?
Thank you in advance and best wishes
Keyboard243

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

ID: 5bf01435-a73b-4bf2-5845-e4cf50c4c3a2
Version Independent ID: 166e1800-80b1-2496-7160-3040c5b23c3d
Content: Microsoft Teams Rooms requirements - Microsoft Teams
Content Source: Teams/rooms/requirements.md
Service: msteams
GitHub Login: @dstrome
Microsoft Alias: dstrome

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

The answer I got, was that it is not recommended to use just the NUC instead of the bundle. It was not directly denied, that it could or may work but just that it is not recommended.


feat(ssh_tunnel): Create command & exceptions

SUMMARY

Create a command to allow users to generate a SSHTunnel object to be saved once a Database is being commited to the metastore.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

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

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

merging to unblock following PRs

@eschutho let me know if there are any concerns with this approach


--wait-for-jobs causes werf not to track resources during helm install/upgrade

Before proceeding

[X] I didn't find a similar issue

Version
v1.2.288
How to reproduce

Confirm resource tracking works with:

$ ./werf helm upgrade --install --wait jenkins https://github.com/jenkinsci/helm-charts/releases/download/jenkins-5.0.12/jenkins-5.0.12.tgz --set persistence.enabled=false

┌ Waiting for resources to become ready
│ ┌ Status progress
│ │ STATEFULSET                                                                                REPLICAS         READY              UP-TO-DATE
│ │ jenkins                                                                                1/1              1                  1
│ │ RESOURCE                                                            NAMESPACE             WATCHING FOR FIELD
│ │ ServiceAccount/jenkins                                              default               -
│ │ Secret/jenkins                                                      default               -
│ │ ConfigMap/jenkins                                                   default               -
│ │ ConfigMap/jenkins-jenkins-jcasc-config                              default               -
│ │ Role/jenkins-schedule-agents                                        default               -
│ │ Role/jenkins-casc-reload                                            default               -
│ │ RoleBinding/jenkins-schedule-agents                                 default               -
│ │ RoleBinding/jenkins-watch-configmaps                                default               -
│ │ Service/jenkins-agent                                               default               -
│ │ Service/jenkins                                                     default               -
│ └ Status progress
└ Waiting for resources to become ready (3.00 seconds)
Release "jenkins" has been upgraded. Happy Helming!
NAME: jenkins
LAST DEPLOYED: Wed Feb  7 18:15:15 2024
NAMESPACE: default
STATUS: deployed
REVISION: 2
NOTES:
1. Get your 'admin' user password by running:
  kubectl exec --namespace default -it svc/jenkins -c jenkins -- /bin/cat /run/secrets/additional/chart-admin-password && echo
2. Get the Jenkins URL to visit by running these commands in the same shell:
  echo http://<IP_ADDRESS>:8080
  kubectl --namespace default port-forward svc/jenkins 8080:8080

3. Login with the password from step 1 and the username: admin
4. Configure security realm and authorization strategy
5. Use Jenkins Configuration as Code by specifying configScripts in your values.yaml file, see documentation: http://<IP_ADDRESS>:8080/configuration-as-code and examples: https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos

For more information on running Jenkins on Kubernetes, visit:
https://cloud.google.com/solutions/jenkins-on-container-engine

For more information about Jenkins Configuration as Code, visit:
https://jenkins.io/projects/jcasc/

NOTE: Consider using a custom image with pre-installed plugins
#################################################################################
######   WARNING: Persistence is disabled!!! You will lose your data when   #####
######            the Jenkins pod is terminated.                            #####
#################################################################################

Note how it does not work if you add --wait-for-jobs:

$ ./werf helm upgrade --install --wait --wait-for-jobs --set persistence.enabled=false jenkins https://github.com/jenkinsci/helm-charts/releases/download/jenkins-5.0.12/jenkins-5.0.12.tgz
Release "jenkins" has been upgraded. Happy Helming!
NAME: jenkins
LAST DEPLOYED: Wed Feb  7 18:15:32 2024
NAMESPACE: default
STATUS: deployed
REVISION: 3
NOTES:
1. Get your 'admin' user password by running:
  kubectl exec --namespace default -it svc/jenkins -c jenkins -- /bin/cat /run/secrets/additional/chart-admin-password && echo
2. Get the Jenkins URL to visit by running these commands in the same shell:
  echo http://<IP_ADDRESS>:8080
  kubectl --namespace default port-forward svc/jenkins 8080:8080

3. Login with the password from step 1 and the username: admin
4. Configure security realm and authorization strategy
5. Use Jenkins Configuration as Code by specifying configScripts in your values.yaml file, see documentation: http://<IP_ADDRESS>:8080/configuration-as-code and examples: https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos

For more information on running Jenkins on Kubernetes, visit:
https://cloud.google.com/solutions/jenkins-on-container-engine

For more information about Jenkins Configuration as Code, visit:
https://jenkins.io/projects/jcasc/

NOTE: Consider using a custom image with pre-installed plugins
#################################################################################
######   WARNING: Persistence is disabled!!! You will lose your data when   #####
######            the Jenkins pod is terminated.                            #####
#################################################################################

Result
See above.
Expected result
It should work the same way it works without it.
Additional information
No response

Should be fixed in 1.2.289

That's awesome. Thanks a lot!


Increase menu font size

The menu font does not need to be as small as it is. Here are a few recent menus, none take anywhere close to the full space:

Increased from 1rem to 1.25rem. While there's still a lot of space in the box, much bigger than that starts to look a little weird in my option.


Remove object.Keys() method

Fixes #3203.
The Object.Keys() method is a not part of the C# Object class.

As base for this merge was rebased (because its base was squashed), this will also need to be rebased, so the pull request will need to be created again.


Fix PHPStan Level 4-5

@paragonie-scott I am out of fuel :)
One of the remaining ones:

src/Compat.php:2556 Trying to invoke '\Sodium\increment' but it's not a callable.

increment() is a static method of ParagonIE_Sodium_Compat

I suggest you to increase level one-by-one: vendor/bin/phpstan analyze -l 5 up to 7
PHPStan can be installed by: composer require --dev --prefer-dist --no-suggest phpstan/phpstan

I think it makes no sense to add it to TravisCI before reaching error-free Level max in PHPStan.

Basically you will run into

sodium_compat errors
phpstan errors
problems from PHP version as sodium_compat runs on lower versions too
folks pass rubbish as parameter

src/Compat.php:2556 Trying to invoke '\Sodium\increment' but it's not a callable.

This is only callable if the old ext/libsodium (contrast with the newer ext/sodium) is installed.
Sodium_compat is a polyfill library. It calls things that might not exist, then wraps those calls in logic that checks that they exist. Phpstan needs to ignore these failures.

I'll fix the Psalm nits.

Phpstan needs to ignore these failures.

You can define a shim class Sodium { function static increment{} } in bootstrap.php!

Oops, there is no bootstrap.php yet


chore: correct tenancy spell

Summary
Correct Spell.
x teanancy
o tenancy

Thank you @xhiroga for the contribution.


How do I cancel an already accepted push promise?

In my use case, I accept all HTTP/2 push promises and put them in a temporary cache.
After some time, I want to cancel the ones that have not been used yet.
I didn't find a way to do so, did I miss something?
Thanks for the help :)

You can throw a Amp\CancelledException or an Amp\Http\Client\HttpException from the push promise handler to cancel the push promise.

You can throw  from the push promise handler

I spotted that, but I'm not sure that answers my use case. Maybe it's me not being fluent enough with amp.
Inside the push handler, I store pushed req+response-promise in a queue.
Then, later on, I consume from the queue. And from time to time, I want to empty the queue.
Could the push handler be give a 3rd argument: a cancellation source that we could use to cancel the pushed req/resp when needed later on?

Funny you should suggest a cancellation token source as a third argument, since that's how I originally wrote that function. @kelunik I think we should add that back.


Some borders are displayed incorrectly on PDF tables

Expected Behavior
I have a topic containing a CALS table with colsep="1", rowsep="1" and frame="none". I expect my result to look like this

Actual Behavior
I used the last DITA-OT 3.5.3 from your website and run the following command dita -f pdf2 -i sample\tables.ditamap.
My result is the following table:

Something similar can be obtained from the HTML5 output except in this case the borders are more consistent but there is an extra right border on the last column and an extra bottom border on the last row. As there is no frame, there should no be.
Steps to Reproduce

Download sample.zip and unzip it
Run the command line and check the PDF output, the test could also be done using html5 transtype

Environment

DITA-OT version: 3.5.3
Operating system and version: Windows 64
How did you run DITA-OT? Command Line & Oxygen
Transformation type: PDF2 and HTML5

Currently, I overwrote the existing table:get-entry-colsep and table:get-entry-rowsep functions to make them use the dita-ot coordinates to set the colsep and rowsep attributes by comparing them to the total number of columns/rows: functions.zip


Add Elm language support

This adds Elm support to Travis.
Happy to do as much revision to this as necessary! Also I'd be happy to push branches of some of my Elm projects to have them use language: elm in their .travis.yml files for the staging tests.

Hi, there! Thank you for your interest in adding Elm to Travis CI.
If you have not done so, please read https://docs.travis-ci.com/user/languages/community-supported-languages/ for some additional details. (Some of the details are a bit out of date; in particular, the bits on travis-core in https://docs.travis-ci.com/user/languages/community-supported-languages/#Code since that library is no longer relevant to community-supported languages. See https://github.com/travis-ci/docs-travis-ci-com/pull/819/.)

Yep! That page was my starting point. 😁

@BanzaiMan Just wanted to check - is there anything you need from me on this? Or just waiting on review?

Please gather a few other volunteers to provide support. Thanks.

@banzaiman @rtfeldman I can help

I can help as well.  I'll also add this to the elm-community projects list so we can document who's actively part of the support team.

@BanzaiMan done! 😄

@rtfeldman I can help!

@BanzaiMan friendly ping! 😃

@BanzaiMan anything we still need to do to unblock review?

@BanzaiMan friendly ping! 🙂

Am I correct to understand that Elm requires a Node.js/JavaScript image?

Am I correct to understand that Elm requires a Node.js/JavaScript image?

@BanzaiMan Elm doesn't, but elm-test does, and it's reasonable to assume people will want that for CI. 😄

Are there other requirements, such as required Node.js version and NPM version?

@BanzaiMan ideally Node 6 and npm 3 (any minor versions within those major versions should be fine).

This has been deployed to staging. https://staging.travis-ci.org/

Does it make sense to allow specifying elm version (a la node_js key for Node.js builds)?

Does it make sense to allow specifying elm version (a la node_js key for Node.js builds)?

I used config[:elm_version] and config[:elm_test_version] to attempt that...are other steps necessary?
          def elm_version
            config[:elm_version].to_s
          end

          def elm_test_version
            config[:elm_test_version].to_s
          end

by the way, thanks for all the help @BanzaiMan!

Upon further testing, providing a different default Node.js version from NodeJs's appears to be a little more involved. (Because nvm install is invoked in super, where Travis::Build::Script::Elm::DEFAULT_VERSION has no effect.) This means that users must specify node_js in .travis.yml.

What I meant was that, does it make sense for users to have in their .travis.yml:
language: elm
elm:
  - 1.1.0
  - 1.2.0 # or whatever future and past versions that they want to test

allowing (with extra work on my part) users to have a build matrix based on the elm versions.
I am not sure how tightly elm-test versions are coupled with elm versions. It may not make sense to have, for example, elm_test_version in the configuration.

I am not sure how tightly elm-test versions are coupled with elm versions. It may not make sense to have, for example, elm_test_version in the configuration.

They are decoupled for now, but in a future release of the Elm platform, elm-test will be included in it.
I like this idea; a build matrix would be useful. What if I hardcoded mappings between Elm version and elm-test version for now, with the understanding that once they get rolled together that won't be necessary for future releases?

@BanzaiMan what did you think of this idea?

What if I hardcoded mappings between Elm version and elm-test version for now, with the understanding that once they get rolled together that won't be necessary for future releases?

What if I hardcoded mappings between Elm version and elm-test version for now, with the understanding that once they get rolled together that won't be necessary for future releases?

I think this is fine.

@BanzaiMan I believe https://github.com/travis-ci/travis-build/pull/934/commits/b633a4332f80ec13b01cf7dd35e25c4196cc0477 should address https://github.com/travis-ci/travis-build/pull/934#issuecomment-283972005 in a way where users don't have to manually specify the Node version...unless I'm missing something!

Any suggestions on how I should expose https://github.com/travis-ci/travis-build/pull/934#issuecomment-287053155 ? I know what the mappings are, but I'm not sure where to put them in the code such that they'll be recognized by matrix.

@BanzaiMan Friendly ping re: https://github.com/travis-ci/travis-build/pull/934#issuecomment-288936075 - any ideas?
Also, I view matrix as a nice-to-have, and would be happy to revisit that later after getting the current version into a usable state for people. 🙂

@BanzaiMan I'd love for this to be merged. Anything holding it up aside from (as I well understand) the overwhelming weight of life itself? :)

Is elm use latest supposed to succeed in an empty (for Elm, that is) directory? My test is failing. https://staging.travis-ci.org/BanzaiMan/travis_staging_test/jobs/598943#L1098

Hmmm. elm use latest should return 0. Not clear yet why it's failing here.

Oh, I see. elm-use latest returns 1. I don't know why it behaves differently, but it does.
travis@b66175e461f1:~$ elm-use latest
elm-use v1.1.1
travis@b66175e461f1:~$ echo $?
1
travis@b66175e461f1:~$ elm use latest
elm-use v1.1.1
travis@b66175e461f1:~$ echo $?
0

With a switch to elm use …, it goes a little further. https://staging.travis-ci.org/BanzaiMan/travis_staging_test/jobs/598941

@BanzaiMan Ah yeah, I dropped support for latest in favor of explicit versions.
Should be fixed in https://github.com/travis-ci/travis-build/pull/934/commits/7d444528d82596c0f08d97ff6a2f91d5aa49c46a - sorry about that!

Also, fix the specs, please.

Any news on that @rtfeldman ? The latest update was in July.

@BanzaiMan Sorry I took so long circling back to the spec failures on this, but fixed now!

Just to express my moral support for this venture, it would be really cool to auto-deploy Elm apps to, say, Github pages. Keep rocking!

@BanzaiMan Merge conflicts resolved, and tests passing! 😺

Thanks again! I'll take a look next week.

@BanzaiMan awesome! Is there anything else I need to do before merge? Not sure what happens next. 😄

Do we have a list of community maintainers for Elm?

@banzaiman yep!
Earlier in this discussion, @stoeffel, @avh4, and @lukewestby volunteered. I know all of them personally. 😄

Documenting the community maintainers for Elm here: https://github.com/elm-community/Manifesto/pull/87

@BanzaiMan merged master in, so merge conflict is now resolved!
Let me know if there are any other steps I need to take on this. Very excited to have it so close to the finish line! 😄

Any update on this? Would be great to see it merged

Hi @Kurren123 , apologies for the delay on this. The relevant developers who can help with this aren't around this week, but I will get someone to take a look at it on Monday. Thanks for you patience.

Cross posting my comment on the travis-yml repo ... https://github.com/travis-ci/travis-yml/issues/63#issuecomment-408895903

@avh4 @lukewestby @stoeffel  I'd be happy to add a banner in the same way as they've done for Dart, listing the community supporters you mentioned here. As for any bug fixes I'm quite new to travis so it might take me a while.

Thanks @Kurren123
It looks like the errors were a hosts config issue with our staging environment. We've addressed these, so once you've done the banner additions it should be good to go.

Hey @rtfeldman I'm still trying to get consensus on how to proceed with this.
I'm not sure if you've merged this PR into your branch yet?

Ohhh, I misread "After this your fork should be merged as per this PR" as "This [PR] should be merged after your PR." 😅
My mistake - it's been merged now!

Sorry for my radio silence.
There is only one change we should make before merging this in. Instead of using elm_version and elm_test_version we should be using elm and elm_test, which is consistent with what we do with all other languages.
Sorry for only noticing this late in the piece.

@rtfeldman (Or anyone else) let us know if you are ready to have a spin with this. Thanks!

@BanzaiMan Thanks for the ping! There's been a new release of Elm since the last round, and elm-use has become obsolete, so I made updates accordingly in addition to the requested change. 😃
Let me know if there are any additional changes needed in the updated code. Otherwise I think we're good to go!

Tested: https://staging.travis-ci.org/BanzaiMan/travis_staging_test/jobs/734314

Thank you, @rtfeldman! It looks very good.
We'll be moving to https://travis-ci.community/ for support issues. We'll tweak the display text accordingly before releasing.
The current plan is to announce Elm support on December 4, 2018.

Needs docs PR.

Needs docs PR.

Is this something I should do? 😄

@rtfeldman I think I can do this, given the short time frame we've got. I should've pointed this out much earlier.

@rtfeldman What is the intended interactions among elm, elm_test, and elm_format? Currently, these can be independently defined, which I think is OK, but if one changes only elm, then elm_test and elm_format fall out of sync with it. That is to say:
language: elm
elm: 0.20.0 # a future release

will use Elm 0.20.0, but elm_test and elm_format remains at elm0.19.0, which is the default.
I am unfamiliar with the Elm ecosystem, but I imagine that this is not an ideal situation. From the user's perspective, its seems to me that elm value should propagate to the other two tools that depend on it (unless, of course, elm_test or elm_format is overridden.)

On a related note: how useful is the matrix expansion on elm_test and elm_format? It makes sense for the repository to test on multiple Elm versions, but I would like to not have to expand on elm_test and elm_format, to prevent enormous build matrices.

@rtfeldman
We plan to announce this tomorrow (2018-11-27) with the changes I suggested earlier. Namely:

The elm version propagates to elm_test and elm_format tag, unless these are explicitly overridden in the configuration.
There will be no matrix expansion on elm_test and elm_format.

@rtfeldman I can work on the changes I've suggested.

See https://github.com/travis-ci/travis-build/commit/9fbe7e4dcacbf5bd82bbee206a0c207fba0f176c, including specs, which shows that:

The elm value drives elm_test and elm_format versions.
The elm value could be with or without the elm prefix (e.g., 0.19.0 or elm0.19.0) and TRAVIS_ELM_VERSION will retain it if the default is used, or the user supplies it; but TRAVIS_ELM_TEST_VERSION and TRAVIS_ELM_FORMAT_VERSION will always be prefixed with elm.

Looks good, thanks for all your help @BanzaiMan! Super excited to see this land! 😃


Help with Gulp configuration

Hi all,
I just did migration from Ng2 rc5 to RC6.
When I run the app, I have 2 errors with gulp and the systemjs.config.
Please help, I am on it since wednesday 5th september :(

How did you do the migration? Did you also updated the version of the seed with git pull upstream master?


Improve File Tree

[ ] Refactor WebContainer filesystem crawling (use chokidar?)
[ ] Replace uncontrolled RCT with controlled api to improve refreshing
[ ] Fix visuals (top cutoff in PWA scenarios, spacing is off, etc.)
[ ] Add file icons (parse VSCode icon theme format)
[ ] Add handling of renaming files
[ ] Add handling of moving files

Chokidar file watching has been added for when the time comes to update the tree using it.
You can now see file changes in the console.


Fix code due html package, add test-support package, make run() method protected for all widgets

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
-

👍


Use DateTimeOffset

Fixes #274

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (15263ca) 77.50% compared to head (34e1fb8) 77.50%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #434   +/-   ##
=======================================
  Coverage   77.50%   77.50%
=======================================
  Files          98       98
  Lines        2716     2716
  Branches      445      445
=======================================
  Hits         2105     2105
  Misses        492      492
  Partials      119      119

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

👍


Error reporting refactor

Is your feature request related to a problem? Please describe.
Current error reporting is very well documented at https://shaka-player-demo.appspot.com/docs/api/shaka.util.Error.html
This implementation is fine when debugging an app that uses Shaka Player, but it's driving me nuts when working with a crash reporting tool. There's two major problems:

Error codes. Is there any obstacle to just using name strings? Currently, we have code like this:

const getErrorName = (code, shaka) => {
	if (!shaka) {
		return;
	}

	// eslint-disable-next-line consistent-return
	return Object.keys(shaka.util.Error.Code).find(
		errorName => shaka.util.Error.Code[errorName] === code
	);
};

const isNetworkFailure = code =>
	[
		1000, // UNSUPPORTED_SCHEME
		1001, // BAD_HTTP_STATUS
		1002, // HTTP_ERROR
		1003, // TIMEOUT
		1004, // MALFORMED_DATA_URI
		1005, // UNKNOWN_DATA_URI_ENCODING
	].includes(code);

It's not too much of a problem I guess, but is it really necessary? What do the numeric IDs give us that we wouldn't have with strings?

Error details in error.data array. This is fine when debugging, but for filtering and grouping errors in a crash reporting tool it's almost impossible to work with. Those tools usually only support simple operations like "equals" and "contains" in their query languages and we can't access a JSON blob to check elements of an array.

If trying to map this error detail format to something more usable for crash reporting, there's the problem of a "moving target". For example, "original error" is sometimes error.data[0], sometimes error.data[1], etc.
Describe the solution you'd like

Simply replace numeric error codes with strings. If an app sees value in exposing numeric codes to end users, they can come up with their own set.

Switch from an array to a simple key/value pair object. For example, this:

error.data[0] is the URI.
error.data[1] is the status code.
error.data[2] is the response text, or null if the response could not be interpretted as text.
error.data[3] is the map of response headers.
error.data[4] is the NetworkingEngine.RequestType of the request, if one was provided.

would become something like this:
{
	uri,
	statusCode,
	responseText,
	responseHeaders,
	requestType,
}

This would be much easier to use. Some crash reporting tools would probably support it out of the box, for others, mapping by looking for a property of an object is much more straightforward than looking for an array element at an index which depends on error code.
Describe alternatives you've considered
Complex app code to transform shaka errors into something usable by crash reporting tools is the only alternative I can see, but not a great one.
Also, Shaka could provide helpers to extract specific error details, but the above solution seems cleaner to me. The only catch is the above would require a major version bump (changing library API) and helpers would be minor (new feature) according to semver.
Additional context

Thanks for the feedback!  This is really helpful.
We originally assumed that numeric codes would be preferable for logging in production, but perhaps we were mistaken.  The string name of the error is available and provided in debug builds.  It would not be difficult to offer that in all builds.  Here's the code I'm referring to:
https://github.com/google/shaka-player/blob/ec2674a4d891aeec6732b7500ad50faf858f7435/lib/util/error.js#L68-L108
We could also replace the data array with a dictionary.  So long as errors supplied both data and the dictionary for a while, this could be a minor version bump.  Later, we would remove data in a major release.

@joeyparrish In my (enterprise) organization, there is an army of folks (some engineering, some not) looking at analytics before the information makes it to actual developers. I believe that including error names in production would help these people, for the simple reason that a short, descriptive phrase like an error name is easier to remember than a number. Keep in mind that these people may be dealing with errors from multiple domains (different device clients, protocols, vendors, etc).
A requirement that my team has internally is that error codes must be attached to a domain. This allows us to resolve error code collisions. I work on a "video playback sdk" which itself has error codes like 1001, 1002, etc. Errors from Shaka get the domain com.google.shakaplayer and errors from my component get com.myorg.mycomponent. Though Shaka has few dependencies (I think muxjs may be the only one?), adding a "domain" attribute could be a non-breaking, useful enhancement for users of Shaka.
For what it's worth though, I don't think that it makes any different whether error data is provided as a dictionary or array. In either case, clients can (and should, IMO) normalize their error information to an interface particular to their domain.
I think the only advantage to adopting a dictionary would be if it became possible to inspect these errors, and their associated data, statically. Something like this is possible in TypeScript via indexed types and generics. I don't know Closure Compiler but I assume it does not support that.

One more thing to add: I do think numeric error codes are useful in general. Consider HTTP status codes and the implication of error ranges. This attribute is very useful.

Is anyone interested in this? If not in 7 days the issue will be closed.


Powershell completion usage

We don't know how Powershell completion is supposed to work, so anyone with a Windows machine and a bit of patience can help us out by fixing the Powershell help text in cmd/completion.go.

Fixed by #39

Fixed by #39


"Please wait a few minutes before you try again"

Downloading as per normal, an error was discovered.
[E] (1) Download failed: Please wait a few minutes before you try again..
[W] Trying again in 5 seconds.

Can anyone assist me?

Thank you.

@dvingerh


Allow to configure lexer options for sigil lexers

Followup to https://github.com/elixir-makeup/makeup_elixir/pull/34

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Stringify the output of config version commands

If you run puppet apply --custom_version='echo foo' then the last run summary YAML ends up looking like this

version:
config: !ruby/string:Puppet::Util::Execution::ProcessOutput "foo"
[...]
Stringify the process output in order to make the YAML less dependent on Ruby.

Can one of the admins verify this patch?

Waiting for CLA signature by @rhowe-gds
@rhowe-gds - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppet.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppet.com/community/trivial_patch_exemption.html

Thanks Russell for your contribution! I added some additional tests and added your commit to my PR https://github.com/puppetlabs/puppet/pull/6856, so I'll close this one out.


Guessed wrong for https://github.com/choderalab/pymbar

depsy is misclassifying pymbar, a scientific code for analyzing data from multiple equilibrium simulations, as "Not research software".
http://depsy.org/package/python/pymbar

Depsy information is still incorrect for this package.


fix(main-branch): renames from master to main

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


LBR for conferencing section

Feedback & request for a scenario with an ongoing PSTN to Teams (or Teams to PSTN) basic call, if we want to escalate the call into conference with another PSTN participant.
This sentence confirms that the only way is to start a conference first to be able to add all participants via dial-out:
"If the user has an audio conferencing license, the user must start a conference with the relevant users and call the PSTN through the conference bridge to start a conference call"
But, the next sentence sounds like we should be able to dial-out if a PSTN call is already placed. That's confusing and customers are complaining about it when they expect it to work : "If the user is already on a PSTN call, they can add another user or PSTN number to the call via escalating the call using the conferencing bridge to dial out."
Our understanding is that it's not possible, by design no "People" button is displayed on the Teams client when LBR is enabled.
We need this section to be rephrased to clarify what is possible or not with LBR enabled in terms of conferencing, with more details on reasons why.
Thank you,
regards.

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

ID: 5e427e0b-ef18-6947-27a6-eb75ddbdead7
Version Independent ID: baf34a47-7d43-8291-7792-dd0b5dac1931
Content: Plan Location-Based Routing for Direct Routing - Microsoft Teams
Content Source: Teams/location-based-routing-plan.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

Hello, may I ask you if you have any update for this request? Do you know when this change could be taken into account?
Thank you.

Hello, as the chapter has been edited. We can close this ticket.
Thank you,
best regards.