an ByteBuffer help you to convert to string? It's not very good at using ByteBuffer

Describe what you would like to know or do
A clear and concise description of what the problem is.
Describe the solution you'd considered
A clear and concise description of any solutions you've considered.
Additional context
Add any other context or links about the question here.

Please clarify your issue, currently it's not possible to understand it.
If you want to convert a ByteBuffer to String,  use the following code:
String s = StandardCharsets.UTF_8.decode(byteBuffer).toString();

This line of code is used, but it's still garbled

for example :x���[k�0�����gO9G�,9o��l5���1�P�3�Rlg����I���a��s���<���u��hȒ\��_��A���L�VoM�{�7�S�%K��C�+Ww�!n}c(lۯ�Ur�v�lf�oK_��M�Ț��ɚza�c�ŉ޻��.;����m����T���2���\��56�)��xò�]?vPD����%���Oi�Rr>Do�u��s�.k��d�x�#��@�/��%iz7�	~�U^�G"T'�.�ѓ|4���1JAc~�i��H1�By�.�}W����pWI���e��U^��@����(Sn�<�TF��ݑ���.��.����M���}�69�����KeA�ҧ��g��D+%*��104O���fh�2CB�����a�Y�f�:ok_��Qcr     ���Lũ%C;W�e_q�~Ⱦ3�s��H	o

Thank you very much.can you help  me

Well that means the buffer contains binary data and not UTF-8 text. If you have questions about the received data format, ask whoever is maintaining the client/server that sends this data (or look at their documentation).
This issue has nothing to do with the library, so I'm closing it.

ok


Save Parse error

Heyo, I dunno if this is the right place for these issues, but this is what I get when I put my save file in the predictor:
Im on the latest version of STV and have no mods installed.
Save Parse Error
The app was unable to process the save file. This is most likely a bug with the app, so please let the dev know about it. Details below.
TypeError: save.objects[fallbackList[roll]] is undefined
predictTrash@https://mouseypounds.github.io/stardew-predictor/stardew-predictor.js?v=5.0.6:4420:29
updateTab@https://mouseypounds.github.io/stardew-predictor/stardew-predictor.js?v=5.0.6:9039:13
window.onload/updateOutput/<@https://mouseypounds.github.io/stardew-predictor/stardew-predictor.js?v=5.0.6:9085:57
each@https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js:2:2715
each@https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js:2:1003
updateOutput@https://mouseypounds.github.io/stardew-predictor/stardew-predictor.js?v=5.0.6:9085:30
window.onload/handleFileSelect/reader.onload@https://mouseypounds.github.io/stardew-predictor/stardew-predictor.js?v=5.0.6:9120:16

I've seen this reported once before but am not sure why it is happening. If you can send me a copy of the save file that tripped it I will investigate further


Fixes issue 206, removed Nimbus JWT and BouncyCastle, adds Vertx JWT

Hello, this commit fixes #206 by replacing dependency on org.bouncycastle.bcpkix-jdk15on and com.nimbusds.nimbus-jose-jwt
with io.vertx.vertx-auth-jwt.
It also adds a script that generates expected certificates and JKS (for Liberty).
Commit tested with these configurations:

MP21, TOMEE, JWT_AUTH
MP22, PAYARA_MICRO, JWT_AUTH
MP22, LIBERTY, JWT_AUTH
MP22, THORNTAIL_V2, JWT_AUTH

Next, files.lst is sorted now:
find src/main/resources/files -type f -name "*.tpl" |sort > src/main/resources/files.lst

Hello @Emily-Jiang

Is there equivalent functionality in Keycloak? It is a bit odd to depend on vert.x for JWT.

We need a JWT library, unless we want to include a lot of somewhat irrelevant boilerplate code into the examples source base.
.JSONArray / Object
We used to depend on Nimbus and we haven't been using Javax.json.JsonArry and JsonObject either, we were using net.minidev.json.JSONArray etc.  vert.x jwt, the same as Nimbus jwt, has its own JsonObject and JsonArray. Unlike Nimbus that pulls in Jackson, vert.x operates with JSON B and that is more in line with MicroProfile.
vert.x jwt
This pull request swaps one implementation for another, adjusting code to adhere to the another library's  API. We are not pulling the whole vert.x, just the necessary minimum.
We are also getting rid of BouncyCastle as it is not needed (we don't use Elliptic Curve crypto in the example). It was a dependency of Nimbus.
Keycloak
It has nothing to do with Keycloak or I don't understand the question. Could you rephrase, please?
Replacing Nimbus jwt
I tested the example using vert.x jwt works with TOMEE, PAYARA_MICRO, LIBERTY, THORNTAIL_V2, so I deem it a fit one-for-one replacement for Nimbus.
The motivation, as explained on #206, is to make Quarkus native build easily possible for MicroProfile Starter JWT_AUTH example. I believe it is O.K. as long as it works for all servers.

Or we can use Jose4j (https://bitbucket.org/b_c/jose4j/wiki/Home) to keep it vendor neutral.

ok @Karm ! I took at a look at the vert.x a bit more. It is ok to use its JWT util to generate JWT. The reason I brought up Keycloak as it is well-known security tool and thought to ask you to check whether it offers the equivalent functionality for JWT generation.

Not merging to 0.9.4 as it lacks 1 more ack.
We can cut 0.9.4 later   (@rdebusscher )

Hold on merging, I need to resolve Kumuluzee - probably a small conf error.

I would move gencerts.jks out of src/main/resources as it is now included in the war on the site (not a big issue but unnecessary)
Can you document the usage and basic stuff around gencerts.jks in the technical documentation of the readme.
Looks good for the rest

@rdebusscher Addressed

@rdebusscher I would like to have this merged. Could you re-review, please?

I tested it with all servers; configs marked in the description of the PR
CQ is not needed as the dependency on Vert.x is in generated code
Questions addressed

We have 2 acks, I am merging this change.


frontend-webapp-springboot3 with "PKIX Path Building Failed" error

After imported the cert to truststore, I could run the demo apps like backend-api-springboot, backend-api-springboot3 and frontend-webapp-springboot successfully.
However, frontend-webapp-springboot3 app would have below error message:
Caused by: org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://id.acme.test:8443/auth/realms/acme-internal/.well-known/openid-configuration": PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Do you have this error too?
Best regards

Found the problem, it was because the projects run on different java homes on my IDE setting, just make sure to import the cert to the correct java truststore, it will run fine after that.


[QUESTION] Custom Queries?

Good evening,
I am trying to add certain features to my program which involve features which are not implemented yet inside of PocketBase and require me to do raw SQL queries. This is things such as counting the amount of records, which right now is technically possible by querying all the records and then counting the amount in the frontend but this causes alot of extra unneeded data transfer.
I'm reading the documentation and I am kinda unclear about it, am I correct that to do raw SQL queries you have to write your own Go code as outlinged here. Or is there a builtin way to query the API with a custom SQL query?
Hope to hear back soon because if I am able to execute raw SQL queries that would fix my last gripe with moving to PocketBase for everything.

Closing this as I see this is possible via a view collection

Reopening as my question still stands as * are not available via view collections right now, are they available via other methods?

Why the lack of wildcard (*) is an issue for you use case? You can define the column explicitly and it should work with any query the same way as if * is used.
If you want to execute parameterized custom db queries then you have to use PocketBase as framework and query the database via the available db abstraction


2.1 introduced uninitialized constant Watir (NameError)

I have upgraded to page-object 2.1 and I faced this issue:
/Users/visko/.rvm/gems/ruby-2.3.3/gems/watir-6.2.0/lib/watir/extensions/select_text.rb:1:in `<top (required)>': uninitialized constant Watir (NameError)
	from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements/element.rb:2:in `require'
	from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements/element.rb:2:in `<top (required)>'
	from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements.rb:29:in `require'
	from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements.rb:29:in `<top (required)>'
	from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/widgets.rb:1:in `require'
	from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/widgets.rb:1:in `<top (required)>'
	from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object.rb:11:in `require'
	from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object.rb:11:in `<top (required)>'
	from my_test.rb:1:in `require'

I don't use Watir on the project but Selenium only. Please let me know if further details are required.
Downgrading to 2.0.0 resolved the problem, could you please check?

I’m looking into it now.

On Mar 7, 2017, at 4:21 AM, Peter Viskovics<EMAIL_ADDRESS>wrote:
I have upgraded to page-object 2.1 and I faced this issue:
/Users/visko/.rvm/gems/ruby-2.3.3/gems/watir-6.2.0/lib/watir/extensions/select_text.rb:1:in <top (required)>': uninitialized constant Watir (NameError) from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements/element.rb:2:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements/element.rb:2:in <top (required)>' from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements.rb:29:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements.rb:29:in <top (required)>' from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/widgets.rb:1:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/widgets.rb:1:in <top (required)>' from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object.rb:11:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object.rb:11:in <top (required)>' from my_test.rb:1:inrequire'
Please let me know if further details are required.
Downgrading to 2.0.0 resolved the problem, could you please check?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/cheezy/page-object/issues/414, or mute the thread https://github.com/notifications/unsubscribe-auth/AACGKiFNzTa1el_oEfZZ6V1isyEDqoy4ks5rjSF-gaJpZM4MVOdI.

Peter,
Can you try to remove the require statement that is on line 2 of lib/page-object/elements/element.rb and see if that resolves the problem?
-Cheezy

On Mar 7, 2017, at 4:21 AM, Peter Viskovics<EMAIL_ADDRESS>wrote:
I have upgraded to page-object 2.1 and I faced this issue:
/Users/visko/.rvm/gems/ruby-2.3.3/gems/watir-6.2.0/lib/watir/extensions/select_text.rb:1:in <top (required)>': uninitialized constant Watir (NameError) from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements/element.rb:2:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements/element.rb:2:in <top (required)>' from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements.rb:29:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements.rb:29:in <top (required)>' from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/widgets.rb:1:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/widgets.rb:1:in <top (required)>' from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object.rb:11:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object.rb:11:in <top (required)>' from my_test.rb:1:inrequire'
Please let me know if further details are required.
Downgrading to 2.0.0 resolved the problem, could you please check?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/cheezy/page-object/issues/414, or mute the thread https://github.com/notifications/unsubscribe-auth/AACGKiFNzTa1el_oEfZZ6V1isyEDqoy4ks5rjSF-gaJpZM4MVOdI.

Peter,
I have not been able to reproduce the issue but I think I have it fixed.  Can I provide you with a version of the gem and have you test it out to ensure it resolves your issue?
-Cheezy

On Mar 7, 2017, at 4:21 AM, Peter Viskovics<EMAIL_ADDRESS>wrote:
I have upgraded to page-object 2.1 and I faced this issue:
/Users/visko/.rvm/gems/ruby-2.3.3/gems/watir-6.2.0/lib/watir/extensions/select_text.rb:1:in <top (required)>': uninitialized constant Watir (NameError) from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements/element.rb:2:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements/element.rb:2:in <top (required)>' from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements.rb:29:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements.rb:29:in <top (required)>' from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/widgets.rb:1:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/widgets.rb:1:in <top (required)>' from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object.rb:11:inrequire'
from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object.rb:11:in <top (required)>' from my_test.rb:1:inrequire'
Please let me know if further details are required.
Downgrading to 2.0.0 resolved the problem, could you please check?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/cheezy/page-object/issues/414, or mute the thread https://github.com/notifications/unsubscribe-auth/AACGKiFNzTa1el_oEfZZ6V1isyEDqoy4ks5rjSF-gaJpZM4MVOdI.

hi Cheezy,
Thanks for the reply. Removing
require 'watir/extensions/select_text'
from lib/page-object/elements/element.rb:2 did not resolve the issue:
/Users/visko/.rvm/gems/ruby-2.3.3/gems/watir-6.2.0/lib/watir/elements/html_elements.rb:3:in `<module:Watir>': uninitialized constant Watir::Element (NameError)
	from /Users/visko/.rvm/gems/ruby-2.3.3/gems/watir-6.2.0/lib/watir/elements/html_elements.rb:2:in `<top (required)>'
	from /Users/visko/.rvm/gems/ruby-2.3.3/gems/page-object-2.1/lib/page-object/elements/table_row.rb:1:in `require'

Yes I can try the fixed version, I would be happy to test it :).

Give this version a try.
page-object-2.1.1.gem.zip

It looks fine, could you please proceed with release? Thank you very much for your efforts!

It's released


How do I play local songs and/or set up my own server?

I've been messing around with this source code and I'm struggling to see where I can implement playing local songs. Do I need to add in a local file browser to the MusicProvider class? Or possibly modify the RemoteJSONSource?
On a second question. I am wondering where I can find more information on how to host my own storage server and have files available to be grabbed via JSON?
I am new and getting familiar with this, any links or code examples would be much appreciated!

Hey. Sorry, but the issues here are intended for problems or feature requests for the Android Universal Music Player, not for general support issues. I'd recommend checking out Stack Overflow and asking your question there.


Revert "rip out progrock socket plumbing"

Reverts part of #6456
Turns out this is still needed by legacy Dagger (dagger run, go run + auto-started dagger session, etc).
It's unfortunate to bring all this plumbing back but we obviously can't break that yet.
Kept everything as-is, including propagating parents, because #6505 prevents the cache-busting issue that we originally ripped all this out to avoid.
This reverts commit 3309a8e799e1f4d66506bdc5e540613ae4bab90a.

SGTM, but I'll also let @sipsma confirm :tada:


chore: bdd-sbhg-1587682164 to 0.0.1

chore: Promote bdd-sbhg-1587682164 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
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

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


Extra profile_list options on main pangeo cluster

Context
On both LEAP and M2LInES clusters, we have extra options (large CPUs, GPUs, etc.) for people with certain status.
Proposal
I would like enable this also for the original Pangeo cluster. Specifically, I would like members of @pangeo-data/cds-lab team to have the same large, huge, and GPU options as on the LEAP and M2LInES clusters.
These special privileges correspond to people directly funded by the grant that is supporting the cluster (Moore Foundation Climate Data Science Lab).
Updates and actions
No response

https://github.com/2i2c-org/infrastructure/issues/1307 is related I think?

Maybe a dupe (or maybe this one is a little bit more specific request), @rabernat can you clarify if that is the case?

So sorry, my bad. 🤦


zos: don't error when killing a zombie process

On z/OS, EPERM is returned if the process being killed is a zombie. However, this shouldn't be treated as an error in uv_kill() since it's already terminated, so return 0 instead.

Draft: https://github.ibm.com/open-z/libuv/pull/16
Upstream: https://github.com/libuv/libuv/pull/3620

This seems consistent with the errata section of the relevant standard noting that some known implementations are not entirely standards compliant in this manner https://pubs.opengroup.org/onlinepubs/9699919799/functions/kill.html despite claiming standards compliance at https://www.ibm.com/docs/en/zos/2.1.0?topic=functions-kill-send-signal-process

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/2248/


pgrep: Add TerminalType::Unknown and implement Display for TerminalType

fix #136

Hmm... I'm not quite sure what kind of commands I should add to test, can you give some examples please?

You could add something like pgrep --terminal=? kthreadd and pgrep --terminal=tty1 kthreadd. The first case should succeed and the other fail with your fix.

You could add something like pgrep --terminal=? kthreadd and pgrep --terminal=tty1 kthreadd. The first case should succeed and the other fail with your fix.

Nah I think this doesn't work on my system :(
$ pgrep --terminal=tty1 kthreadd
$ echo $?
1
$ pgrep --terminal=? kthreadd
$ echo $?
1

Hm, are there any PIDs returned with pgrep --terminal=??

Hm, are there any PIDs returned with pgrep --terminal=??

After my investigation I realized that it was my procps version that was too low to support this syntax, and now I can get the output.
Now our implementation also works, but there are some problems: some high-privileged pid can't get to the terminal it belongs to, but the GNU implementation can.
❯ cargo run pgrep --terminal '?'
2977
2985
2986
2989
2992
2993
...

❯ pgrep --terminal=?
1
2
3
4
5
6
8
10
11
12
13
14
...
2977
2985
2986
2989
2992
2993
...

I don't know what to do about the above point for now, but for the TerminalType enumeration for ?  support is now complete.

And, is TerminalType::Orphan perhaps better than TerminalType::Unknow?

I think TerminalType::Unknown is better.


erroneous 'redundant alternative'

namespace Lean
syntax "foo " binderIdent : term
example : Syntax → MacroM Syntax
  | `(foo _) => `(_)
  | `(foo $x:ident) => `($x:ident) -- redundant alternative
  | _ => `(_)

I would also suggest making this check optional / a warning, because it doesn't impede either code generation or correctness.

Actually the error message is not erroneous, but rather the pattern  `(foo _) is matching foo followed by anything, rather than the previous behavior of matching foo followed by a literal _. We already have the syntax  `(foo $_) for matching foo followed by anything, but now we can't match just foo _ anymore, so I would consider this a bug.

@Kha This is the <|> issue again. We have
def binderIdent : Parser  := ident <|> hole

It has nothing to do with <|> or any new behavior of _. The issue here is that _ is an atom and therefore matches everything.
The obvious fix here is to standardize on syntax binderIdent := ident <|> hole with syntax hole := "_"  so that the underscore gets its own node.  See also #1275 and https://github.com/leanprover-community/mathport/pull/152#issuecomment-1173841553

A big +1 from me on making the grammar more regular and having only one way to write ident <|> "_"


pin pragmas to 0.8.25

Standard best practice with contracts is to keep pragmas pinned to a single compiler version whenever possible. The main exceptions are for interfaces and consumer facing inheritable contracts, where it's best to leave them open.
Our foundry config was set to only use a single compiler version, 0.8.25, so this PR actually has no affect on the bytecode. But if we introduce other compilers in the future, this will ensure the compiler we test with & deployed with is the one we continue to use for the life span of v1 contracts.

Are we sure this won't break mainnet contract upgrade planned for next week?

Are we sure this won't break mainnet contract upgrade planned for next week?

@kaisbaccour
100% sure. But I think as a good rule we shouldn't make any changes to source code b/t testnet and mainnet deployments. So I'm happy to wait to merge this until we deploy to mainnet.


Show user count for group PMs

It is currently hard to distinguish group PMs from 1:1 PMs in the left side bar, especially when the first participant's name is long enough to hide the others. There is also no way to distinguish a conversation with users A, B, C vs. A, B, C, D, assuming only the first couple of names fit.
To improve the UI, we should replace the presence dot for group PMs with the number of users in the group.

@zulipbot claim

Relevant discussion on CZO : https://chat.zulip.org/#narrow/stream/101-design/topic/private.20messages.20UI

@alya
I have implemented the numbers, do you think it's better to leave the dots for groups and just add the number like this? I feel like the dots are still helpful to know that people are online.

Cool! I think removing the circles looks better. Otherwise, group PMs end up being offset from 1:1 PMs, and it's also not very intuitive how to interpret the circle when there are multiple people on the list.
I like the idea of having some styling, but the styling matching unread counts feels off to me, since the meaning is very different. Could you try using a plain box the way we do with the starred message unread counts that just got implemented (screenshot below)?
Thanks!


Health check does not work if you customize the listen port

Because the healthcheck is testing port 8080, if you customize the listen port with --listen it will fail.
https://github.com/aerokube/selenoid-ui/blob/673c5d795b47c419433fcc303d872928b0268aee/healthcheck/main.go#L12-L15

Why would you do that inside the default container? Can you give the usecase? I could imagine a custom container, but then its possible to override the healthcheck command as well

I am hosting it on port 80. This are the args:
--selenoid-uri=http://selenoid:4444 --listen :80 -allowed-origin *

Yes, can override the healthcheck, I hadn't thought of that. This is what I'm doing on Docker Compose:
    healthcheck:
      test: ["CMD", "/health-check", "--uri", "http://localhost/ping"]
      interval: 60s
      timeout: 1s
      retries: 3

This solves my problem.
But would it be possible for the listen args propagate to the healthcheck, so we don't have to customize it?

@giggio I don't get why do you need to override listen port inside container whereas you can just use something like -p 8080:80 when launching your container?

I'll try that soon and report back. I don't remember why we did not do that.

Ok, I remembered why we couldn't use port forwarding, we are using a MacVlan network, and initially SelenoidUi was exposed directly. Recently we started using Nginx to host the same server for Selenoid and UI, and I was able to forward the port that way. Now the healthcheck works without customization (except to fix #295).

It would be a good idea to document this. If the person uses --listen they have to also customize the healthcheck.

@giggio PRs to documentation welcome! :D


Update SDK VERSION to 1.1

Automatic update of SDK VERSION

Restart tests when 1.1 CV SDK has been built


started renaming process; DSL changes still to be done

did all the rust changes, have not started on the removal of walk: {} and layout: {}

Included in #6


Entities should not render/show when out of view

When entities (html, labels, shapes) are drawn on the screen and the globe is rotated they still render even though they are on the opposite side of the globe.
https://youtu.be/ly96vcVrGaA

<EMAIL_ADDRESS>
I can assist with this if you need. I have not looked at it in detail and not sure how or why some components work properly (labels render properly and don't show- see the video) but the html and points still render when they should not.

Hi Andy,
About the points, the cesium disableDepthTestDistance parameter controls the visibility of the point, the default value is Infinity for making the points always visible on top of the editor lines.
Indeed if your system work in globe zoom level it can cause an issue, so you should change the  disableDepthTestDistance to undefined.
About the ac-html, it is missing the check if the html element is in the camera view.
It is an edge case that happens when you work in globe zoom level.
Should be handled in the future also PR is welcomed :)


Scaling with the KEDA azure-pipelines scaler?

I can't get autoscaling to work with the KEDA azure-pipelines scaler. Here's my bicep configuration.
resource container_app 'Microsoft.Web/containerApps@2021-03-01' = {
  name: 'mycontainerapp'
  location: 'eastus'
  properties: {
    kubeEnvironmentId: container_app_environment.id
    configuration: {
      activeRevisionsMode: 'single'
      secrets: [
        {
          name: azure_devops_url_secret_name
          value: azure_devops_url
        }
        {
          name: azure_devops_pool_name_secret_name
          value: azure_devops_pool_name
        }
        {
          name: azure_devops_token_secret_name
          value: azure_devops_token
        }
        {
          name: container_registry_password_secret_name
          value: container_registry.listCredentials().passwords[0].value
        }
      ]
      registries: [
        {
          server: container_registry.properties.loginServer
          username: container_registry.listCredentials().username
          passwordSecretRef: container_registry_password_secret_name
        }
      ]
    }
    template: {
      containers: [
        {
          image: '${container_registry.properties.loginServer}/repo:123'
          name: 'mycontainerapp'
          env: [
            {
              name: 'AZP_URL'
              secretRef: azure_devops_url_secret_name
            }
            {
              name: 'AZP_TOKEN'
              secretRef: azure_devops_token_secret_name
            }
            {
              name: 'AZP_POOL'
              secretRef: azure_devops_pool_name_secret_name
            }
          ]
        }
      ]
      scale: {
        minReplicas: 1
        maxReplicas: 10
        rules: [
          {
            name: 'azure-pipelines'
            custom: {
              type: 'azure-pipelines'
              metadata: {
                poolId: azure_devops_pool_id
                targetPipelinesQueueLength: '1'
              }
              auth: [
                {
                  triggerParameter: 'organizationURL'
                  secretRef: azure_devops_url_secret_name
                }
                {
                  triggerParameter: 'personalAccessToken'
                  secretRef: azure_devops_token_secret_name
                }
              ]
            }
          }
        ]
      }
    }
  }
}

The container deploys successfully with 1 replica. However, it doesn't scale no matter how many jobs are waiting in the Azure Pipelines queue.

Adding @SebastianSchuetze who is looking into this as well, I'll take a look from the KEDA side to see if we need to do something.

Same thing here and thanks @tomkerkhove  for adding.
We have also no visibility if KEDA throws exceptions. Logs of Container Apps themselves during runtime should be surfaced as well.

For comparison I am adding my ARM template into the mix I used:
{
    "$schema": "https://schema.management.azure.com/schemas/2019-08-01/deploymentTemplate.json#",
    "contentVersion": "<IP_ADDRESS>",
    "parameters": {
        "location": {
            "defaultValue": "northeurope",
            "type": "String"
        },
        "environment_name": {
            "type": "String"
        },
        "azp_url": {
            "type": "String"
        },
        "azp_token": {
            "type": "String"
        },
        "azp_pool": {
            "type": "String"
        },
        "azp_poolId": {
            "type": "String"
        },
        "registryEndpoint": {
            "type": "String"
        },
        "registryUserName": {
            "type": "String"
        },
        "registrySecret": {
            "type": "String"
        },
        "registryImage": {
            "type": "String"
        }
    },
    "variables": {},
    "resources": [{
        "name": "azdo-agent-scaled",
        "type": "Microsoft.Web/containerApps",
        "apiVersion": "2021-03-01",
        "kind": "containerapp",
        "location": "[parameters('location')]",
        "properties": {
            "kubeEnvironmentId": "[resourceId('Microsoft.Web/kubeEnvironments', parameters('environment_name'))]",
            "configuration": {
                "secrets": [{
                        "name": "azp-url",
                        "value": "[parameters('azp_url')]"
                    },
                    {
                        "name": "azp-token",
                        "value": "[parameters('azp_token')]"
                    },
                    {
                        "name": "azp-pool",
                        "value": "[parameters('azp_pool')]"
                    },
                    {
                        "name": "azp-poolid",
                        "value": "[parameters('azp_poolId')]"
                    },
                    {
                        "name": "registry-secret",
                        "value": "[parameters('registrySecret')]"
                    }
                ],
                "registries": [{
                    "server": "[parameters('registryEndpoint')]",
                    "username": "[parameters('registryUserName')]",
                    "passwordSecretRef": "registry-secret"
                }]
            },
            "template": {
                "containers": [{
                    "image": "[parameters('registryImage')]",
                    "name": "basedockeragent",
                    "resources": {
                        "cpu": 0.75,
                        "memory": "1.5Gi"
                    },
                    "env": [{
                            "name": "AZP_URL",
                            "secretRef": "azp-url"
                        },
                        {
                            "name": "AZP_TOKEN",
                            "secretRef": "azp-token"
                        },
                        {
                            "name": "AZP_POOL",
                            "secretRef": "azp-pool"
                        },
                        {
                            "name": "AZP_POOLID",
                            "secretRef": "azp-poolid"
                        }
                    ]
                }],
                "scale": {
                    "minReplicas": "1",
                    "maxReplicas": "5",
                    "rules": [{
                        "name": "azdo-agent-scaled",
                        "custom": {
                            "type": "azure-pipelines",
                            "metadata": {
                                "poolID": "[parameters('azp_poolId')]",
                                "organizationURLFromEnv ": "[parameters('azp_url')]",
                                "targetPipelinesQueueLength": "1"
                            },
                            "auth": [{
                                "secretRef": "azp-token",
                                "triggerParameter": "personalAccessToken"
                            }]
                        }
                    }]
                }
            }
        }
    }]
}

@SebastianSchuetze You are providing the actual URL of your organization which should point to an environment variable.
What if you try this?
{
    "$schema": "https://schema.management.azure.com/schemas/2019-08-01/deploymentTemplate.json#",
    "contentVersion": "<IP_ADDRESS>",
    "parameters": {
        "location": {
            "defaultValue": "northeurope",
            "type": "String"
        },
        "environment_name": {
            "type": "String"
        },
        "azp_url": {
            "type": "String"
        },
        "azp_token": {
            "type": "String"
        },
        "azp_pool": {
            "type": "String"
        },
        "azp_poolId": {
            "type": "String"
        },
        "registryEndpoint": {
            "type": "String"
        },
        "registryUserName": {
            "type": "String"
        },
        "registrySecret": {
            "type": "String"
        },
        "registryImage": {
            "type": "String"
        }
    },
    "variables": {},
    "resources": [{
        "name": "azdo-agent-scaled",
        "type": "Microsoft.Web/containerApps",
        "apiVersion": "2021-03-01",
        "kind": "containerapp",
        "location": "[parameters('location')]",
        "properties": {
            "kubeEnvironmentId": "[resourceId('Microsoft.Web/kubeEnvironments', parameters('environment_name'))]",
            "configuration": {
                "secrets": [{
                        "name": "azp-url",
                        "value": "[parameters('azp_url')]"
                    },
                    {
                        "name": "azp-token",
                        "value": "[parameters('azp_token')]"
                    },
                    {
                        "name": "azp-pool",
                        "value": "[parameters('azp_pool')]"
                    },
                    {
                        "name": "azp-poolid",
                        "value": "[parameters('azp_poolId')]"
                    },
                    {
                        "name": "registry-secret",
                        "value": "[parameters('registrySecret')]"
                    }
                ],
                "registries": [{
                    "server": "[parameters('registryEndpoint')]",
                    "username": "[parameters('registryUserName')]",
                    "passwordSecretRef": "registry-secret"
                }]
            },
            "template": {
                "containers": [{
                    "image": "[parameters('registryImage')]",
                    "name": "basedockeragent",
                    "resources": {
                        "cpu": 0.75,
                        "memory": "1.5Gi"
                    },
                    "env": [{
                            "name": "AZP_URL",
                            "secretRef": "azp-url"
                        },
                        {
                            "name": "AZP_TOKEN",
                            "secretRef": "azp-token"
                        },
                        {
                            "name": "AZP_POOL",
                            "secretRef": "azp-pool"
                        },
                        {
                            "name": "AZP_POOLID",
                            "secretRef": "azp-poolid"
                        }
                    ]
                }],
                "scale": {
                    "minReplicas": "1",
                    "maxReplicas": "5",
                    "rules": [{
                        "name": "azdo-agent-scaled",
                        "custom": {
                            "type": "azure-pipelines",
                            "metadata": {
                                "poolID": "[parameters('azp_poolId')]",
-                                "organizationURLFromEnv ": "[parameters('azp_url')]",
                                "targetPipelinesQueueLength": "1"
                            },
                            "auth": [{
                                "secretRef": "azp-token",
                                "triggerParameter": "personalAccessToken"
+                            },{
+                                "secretRef": "azp-url",
+                                "triggerParameter": "organizationURL"
                            }]
                        }
                    }]
                }
            }
        }
    }]
}

What is the difference? Isn't KEDA using this anyways the same way? Docs say mine is also valid from what I understood.

organizationURLFromEnv needs to be the name of the environment variable on your workload. But you specify the actual URL, instead of that name.

oh okay. Very good point!

@tomkerkhove it is f***ing working!!!

@guythetechie I don't see where you set the value for azure_devops_pool_id in your snippet.

Great to hear that it's working and the pool ID seems to be missing indeed!

@SebastianSchuetze  - Glad you got it working. Now I know it's possible. :) It would definitely be useful to have KEDA/DAPR logs.
@tomkerkhove - I pass the pool ID as a parameter, but please let me know if I'm doing it wrong. Just to be clear though - the pool ID is a number (as opposed to a GUID), right? If my template looks good, next stop is making sure the values I'm passing are correct.
Here's the full Bicep file, parameters included:
param container_registry_name string
param container_app_environment_name string
param azure_devops_url string
@secure()
param azure_devops_token string
param azure_devops_pool_name string
param azure_devops_pool_id string

var azure_devops_url_secret_name = 'azure-devops-url'
var azure_devops_pool_name_secret_name = 'azure-devops-pool-name'
var azure_devops_token_secret_name = 'azure-devops-token'
var container_registry_password_secret_name = 'container-registry-password'

resource container_registry 'Microsoft.ContainerRegistry/registries@2021-06-01-preview' existing = {
  name: container_registry_name
}

resource container_app_environment 'Microsoft.Web/kubeEnvironments@2021-02-01' existing = {
  name: container_app_environment_name
}

resource container_app 'Microsoft.Web/containerApps@2021-03-01' = {
  name: 'mycontainerapp'
  location: 'eastus'
  properties: {
    kubeEnvironmentId: container_app_environment.id
    configuration: {
      activeRevisionsMode: 'single'
      secrets: [
        {
          name: azure_devops_url_secret_name
          value: azure_devops_url
        }
        {
          name: azure_devops_pool_name_secret_name
          value: azure_devops_pool_name
        }
        {
          name: azure_devops_token_secret_name
          value: azure_devops_token
        }
        {
          name: container_registry_password_secret_name
          value: container_registry.listCredentials().passwords[0].value
        }
      ]
      registries: [
        {
          server: container_registry.properties.loginServer
          username: container_registry.listCredentials().username
          passwordSecretRef: container_registry_password_secret_name
        }
      ]
    }
    template: {
      containers: [
        {
          image: '${container_registry.properties.loginServer}/repo:123'
          name: 'mycontainerapp'
          env: [
            {
              name: 'AZP_URL'
              secretRef: azure_devops_url_secret_name
            }
            {
              name: 'AZP_TOKEN'
              secretRef: azure_devops_token_secret_name
            }
            {
              name: 'AZP_POOL'
              secretRef: azure_devops_pool_name_secret_name
            }
          ]
        }
      ]
      scale: {
        minReplicas: 1
        maxReplicas: 10
        rules: [
          {
            name: 'azure-pipelines'
            custom: {
              type: 'azure-pipelines'
              metadata: {
                poolId: azure_devops_pool_id
                targetPipelinesQueueLength: '1'
              }
              auth: [
                {
                  triggerParameter: 'organizationURL'
                  secretRef: azure_devops_url_secret_name
                }
                {
                  triggerParameter: 'personalAccessToken'
                  secretRef: azure_devops_token_secret_name
                }
              ]
            }
          }
        ]
      }
    }
  }
}

And here's the deployed revision's resource JSON in Azure:
{
    "id": "/subscriptions/***/resourceGroups/***/providers/Microsoft.Web/containerApps/***/revisions/***--azbpvln",
    "name": "***--azbpvln",
    "type": "Microsoft.Web/containerapps/revisions",
    "location": "eastus",
    "properties": {
        "createdTime": "2021-11-15T18:56:19+00:00",
        "fqdn": "",
        "template": {
            "containers": [
                {
                    "image": "***.azurecr.io/***:3873",
                    "name": "***",
                    "env": [
                        {
                            "name": "AZP_URL",
                            "secretRef": "azure-devops-url"
                        },
                        {
                            "name": "AZP_TOKEN",
                            "secretRef": "azure-devops-token"
                        },
                        {
                            "name": "AZP_POOL",
                            "secretRef": "azure-devops-pool-name"
                        }
                    ],
                    "resources": {
                        "cpu": 0.5,
                        "memory": "1Gi"
                    }
                }
            ],
            "scale": {
                "minReplicas": 1,
                "maxReplicas": 10,
                "rules": [
                    {
                        "name": "azure-pipelines",
                        "custom": {
                            "type": "azure-pipelines",
                            "metadata": {
                                "poolId": "13",
                                "targetPipelinesQueueLength": "1"
                            },
                            "auth": [
                                {
                                    "secretRef": "azure-devops-url",
                                    "triggerParameter": "organizationURL"
                                },
                                {
                                    "secretRef": "azure-devops-token",
                                    "triggerParameter": "personalAccessToken"
                                }
                            ]
                        }
                    }
                ]
            }
        },
        "active": true,
        "replicas": 1,
        "trafficWeight": 0,
        "name": "***--azbpvln",
        "healthState": "Healthy",
        "provisioningState": "Provisioned"
    }
}

@SebastianSchuetze  - If you don't mind, what permissions does your PAT token have? Mine has:

and

For testing I used full scope. I will reduce the scoping later to see when something is not working. But in general "manage pool" should be enough. The PAR is only used for registering new agents. The agents themselves get short like ved tokens and authenticate themselves with their own tokens.

Thank you. I'll try full scope.
In addition to Read & manage* pool permissions, I thought the token might need permissions to read the pipelines queue so KEDA can autoscale.

@tomkerkhove - I pass the pool ID as a parameter, but please let me know if I'm doing it wrong. Just to be clear though - the pool ID is a number (as opposed to a GUID), right? If my template looks good, next stop is making sure the values I'm passing are correct.

The ID should be the pool ID of your Azure DevOps pool - It should not be used randomly. Probably this is your issue then?

@tomkerkhove - I pass the pool ID as a parameter, but please let me know if I'm doing it wrong. Just to be clear though - the pool ID is a number (as opposed to a GUID), right? If my template looks good, next stop is making sure the values I'm passing are correct.

The ID should be the pool ID of your Azure DevOps pool - It should not be used randomly. Probably this is your issue then?

Sorry, my message was unclear. I am not using a random value as the pool ID. I obtained it using a REST API call to Azure DevOps. Just want to confirm that it is supposed to be a number and not a GUID.

Pool ID can also be found easily in the url when opening a pool

I finally got it working. The issue was my Azure Devops URL: it was https:/dev.azure.com/myorganization/ instead of https://dev.azure.com/myorganization. The scaler didn't like the trailing slash.
I had to create an AKS cluster, deploy KEDA on it with my scaler configuration, and look at the KEDA logs to figure out what was going on. As @SebastianSchuetze mentioned, it would be greatly beneficial to surface these logs in Container Apps.
Thanks @tomkerkhove  & @SebastianSchuetze for the assistance!

Happy to help and sorry for not being helpful.
Are you open to submitting a PR on KEDA to improve the docs?
https://github.com/kedacore/keda-docs

Gonna have a look at it. Should I update all docs for all doc versions like 2.3, 2.4, 2.5 or just the latest?

All is prefered but I can backport if it's too much.

Really happy I found this issue with regards to
+                            },{
+                                "secretRef": "azp-url",
+                                "triggerParameter": "organizationURL"
                            }]

I did the mistake of writing the SecretRef value as the actual value instead of a secret. I was considering going back to Azure container instances until this actually. Too early to say if this fixes all my issues, but my revisions have been really unstable, with stuck pipeline jobs, failing revisions and even revisions disappearing out of the blue.

@audunsolemdal regarding your problems you might wanna check my update on the blog post.
Container Apps are not ready for jobs, since you need ScaledJobs from kubernetes in order to do many things properly
https://www.razorspoint.com/2021/11/19/scalable-container-based-azure-pipelines-pools-with-azure-container-apps/

Thanks for the head's up.

I am unable to understand WHY it does not work, so simple operation takes so much efforts, guys, can you look? (secrets reducted)
    "resources": [
      {
        "type": "Microsoft.App/containerapps",
        "apiVersion": "2022-01-01-preview",
        "name": "[parameters('name')]",
        "location": "[parameters('location')]",
        "dependsOn": [
          "[concat('Microsoft.App/managedEnvironments/', parameters('environmentName'))]"
        ],
        "kind": "containerapps",
        "properties": {
          "configuration": {
            "secrets": "[parameters('secrets')]",
            "registries": "[parameters('registries')]"
          },
          "template": {
            "containers": [
              {
                "image": "myimg",
                "name": "azp-agents",
                "resources": {
                  "cpu": 2,
                  "memory": "4Gi"
                },
                "env": [
                  {
                    "name": "AZP_URL",
                    "secretRef": "azp-url"
                  },
                  {
                    "name": "AZP_TOKEN",
                    "secretRef": "azp-token"
                  },
                  {
                    "name": "AZP_POOL",
                    "secretRef": "azp-pool"
                  },
                  {
                    "name": "AZP_POOLID",
                    "secretRef": "azp-poolid"
                  }
                ]
              }
            ],
            "scale": {
              "minReplicas": "1",
              "maxReplicas": "5",
              "rules": [
                {
                  "name": "name",
                  "custom": {
                    "type": "azure-pipelines",
                    "metadata": {
                      "organizationURLFromEnv ": "AZP_URL",
                      "poolID": "10",
                      "targetPipelinesQueueLength": "1"
                    },
                    "auth": [
                      {
                        "secretRef": "azp-token",
                        "triggerParameter": "personalAccessToken"
                      },
                      {
                        "secretRef": "azp-url",
                        "triggerParameter": "organizationURL"
                      }
                    ]
                  }
                }
              ]
            }
          },
          "managedEnvironmentId": "[parameters('environmentId')]"

I suggest reading the material above given the concept of what you are trying to deploy (a job) is not supported on Azure Container Apps since everything is a deamon/deployment.
It will randomly scale in/out in the middle of your running pipelines which makes no sense, you'll need to wait for job-support in ACA

I wonder whether it is related to API type and version , Im using this 2022 preview
"type": "Microsoft.App/managedEnvironments@2022-01-01-preview"
Found out there were this API As well :
Microsoft.Web/kubeEnvironments@2021-02-01

It works, scaling process works, even if you have zero active containers in the ContainerApps it would scale from 0 to desired number of containers.
I was getting pool ID in wrong place, you must get pool ID from organisation settings, not project setting.
Pool ID of target Agent Pool can be found under organization settings of Azure DevOps organisation by navigating to Organisational settings -> Agent pools ->  and Get pool ID number from the HTTP Link above, example: _settings/agentpools?poolId=1&view=jobs Pool ID would be 1
template.json:
{     "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",     "contentVersion": "<IP_ADDRESS>",     "parameters": {         "subscriptionId": {             "type": "String"         },         "name": {             "type": "String"         },         "location": {             "type": "String"         },         "environmentId": {             "type": "String"         },         "containers": {             "type": "Array"         },         "secrets": {             "type": "Array"         },         "registries": {             "type": "Array"         }     },     "resources": [         {             "type": "Microsoft.App/containerapps",             "apiVersion": "2022-01-01-preview",             "name": "[parameters('name')]",             "location": "[parameters('location')]",             "kind": "containerapps",             "properties": {                 "configuration": {                     "secrets": "[parameters('secrets')]",                     "registries": "[parameters('registries')]"                 },                 "template": {                     "containers": [                         {                             "image": "<reducted>",                             "name": "azp-agents",                             "resources": {                                 "cpu": 2,                                 "memory": "4Gi"                             },                             "env": [                                 {                                     "name": "AZP_URL",                                     "secretRef": "azp-url"                                 },                                 {                                     "name": "AZP_TOKEN",                                     "secretRef": "azp-token"                                 },                                 {                                     "name": "AZP_POOL",                                     "secretRef": "azp-pool"                                 },                                 {                                     "name": "AZP_POOLID",                                     "secretRef": "azp-poolid"                                 }                             ]                         }                     ],                     "scale": {                         "minReplicas": "0",                         "maxReplicas": "2",                         "rules": [                             {                                 "name": "<reducted>",                                 "custom": {                                     "type": "azure-pipelines",                                     "metadata": {                                         "organizationURLFromEnv ": "AZP_URL",                                         "AZP_POOL": "Default",                                         "poolID": "1",                                         "targetPipelinesQueueLength": "1"                                     },                                     "auth": [                                         {                                             "secretRef": "azp-token",                                             "triggerParameter": "personalAccessToken"                                         },                                         {                                             "secretRef": "azp-url",                                             "triggerParameter": "organizationURL"                                         }                                     ]                                 }                             }                         ]                     }                 },                 "managedEnvironmentId": "[parameters('environmentId')]"             }         }     ] }
params json should have secrets with values of your use case, template would reference them.


argumentList in mongo grammar should be renamed argument

arguments
: OPEN_PARENTHESIS = '(' ( argumentList (',' argumentList)* )? CLOSED_PARENTHESIS = ')'
;
argumentList      <<=== this is not a list
: literal
| objectLiteral
| arrayLiteral
;

We talked about this during my PR-review. The fix seems bigger than just the variable name - the visitor methods need to be renamed too.

Now's the perfect time to do it, as long as it doesn't take too long.


Tensorflow lite conversion from h5 to tflite increases file size

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): v1.13.1-0-g6612da8951' 1.13.1
Python version: 3.7.3
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: 10.0
GPU model and memory: RTX 2070 8GB

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with: 1. TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" 2. TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the current behavior
Tflite conversion from h5 file increases in size from 141KB to 508KB
Describe the expected behavior
A reduction in size
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
model = tf.keras.Sequential([
    tf.keras.layers.Dense(128, activation=tf.nn.relu),
    tf.keras.layers.Dense(11, activation=tf.nn.softmax)
])

model.compile(optimizer='adam',
          loss='sparse_categorical_crossentropy',
          metrics=['accuracy'])
model.fit(TrainingData, TrainingLabels, epochs=400)

tf.keras.models.save_model(model, keras_file)

converter = tf.contrib.lite.TFLiteConverter.from_keras_model_file(keras_file)
tflite_model = converter.convert()
open("converted_model.tflite", "wb").write(tflite_model)

Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@kartikye Could you create a reproducible code and share the link to that gist? It will help us resolve the issue faster. Thanks!

What should i include in the reproducible code?

@kartikye If you can create a google colab gist or any other way that we can run to reproduce the issue   would be great. The above code is not complete to reproduce the issue. It will make issue resolutions faster. Thanks!

Closing due to lack of recent activity. Please update the issue when new information becomes available, and we will open a new issue. Thanks!


Detect prefixes 'bz' and 'rhbz' commonly used in Fedora

How long after merge for this to be in production? Is there any way of  knowing ?

Thanks for the patch @atodorov. We're only accepting bugfixes and security patches for these services as we're encouraging folks to move webhooks for more flexible integrations that don't need to wait on a GitHub build.


Compile some modules with Cython and add a manylinux wheel build target.

Following #2093, this pull request adds optional compilation support for Python modules in nltk. I also added a Makefile target to build Linux wheels.
For now, only two modules are compiled: nltk.grammar and nltk.parse.chart. They proved to be the main bottlenecks in our application, and compiling them brought us a speedup of 30%. It is easy to add more modules if benchmarks prove their compilation helpful, but any additional compiled module also increases the size of the binary distributions, so this is a trade-off.
I set the CFLAGS so that the extension modules should work on any x86-ish system (-mtune=generic) and include basic debugging symbols (-g1) to get usable C stack traces should they crash.
Note that the compilation is not enabled by default but only when the envvar CYTHONIZE_NLTK=true is set. I added tox build targets to include this setup.

The tests passed in Jenkins apparently, but it doesn't look like they tested the cythonized version. They don't even seem to be driven by tox, so I don't know how to make them use the compiled version.

[CI: retest]

[CI: cythonize-retest]

[CI: cythonize-retest]

[CI: retest]

[CI: retest]

Lets see how far we can push this, i.e. how many modules we can add.

There's still something wrong with the Py3.6 build. It creates Py3.5 binaries, meaning, it's actually using Py3.5 and not Py3.6 (at least for the build):
https://nltk.ci.cloudbees.com/job/cythonize/PYV=3.6.4,jdk=jdk8latestOnlineInstall/ws/.tox/py3.6.4-cythonized/lib64/python3.5/site-packages/nltk/tokenize/

Also, I checked the coverage analysis and the line coverage is still the same as the non-compiled case. That suggests that the binaries might actually not be used, because profiling/coverage support is not enabled by default for Cython compiled modules for performance reasons. Profiling of inner-Cython code requires the directive profile=True, and coverage analysis requires linetrace=True to generate the tracing code and a C compile time macro to enable it in the extension modules.
In the workspace, the nltk source directory in the project root does not have the extension modules, only the .tox/ subdirectory has them. If the tests are executed inside of tox from the subdirectory and not from the project root, that should be ok, but it should also impact the reported coverage results.
A simple way of debugging this is to print the module.__file__ of modules that you expect to be compiled. It should be the path to the shared library and not the .py file.

@scoder sorry for the delayed response. We realized that the old CI had issues and was sunsetting so we moved to Travis and it took a while for us to make it work and clean up while migrating to Travis.
Currently the new CI can be fully controlled by the .travis.yml and tox.ini.
Let me try and see whether I can enable a cython build on the new CI.

Seems like the cythonize build is failing https://travis-ci.org/nltk/nltk/jobs/430825857#L1406
@scoder any ideas how can this be fixed?

I don't have any experience with nose, but the setup seems to be different. It runs the tests from the nltk/test/ directory instead of the project root, and passes the tox.ini file as argument to nose instead of test runner arguments. The py-travis setup seems to use coverage analysis and runs the tests from the project root. Probably worth making both setups behave the same.
You can also enable coverage analysis for Cython modules, but since it slows them down (uses tracing), it's off by default, so it would require two compilation steps, one for the production wheels and one for the test runs. So I'd rather leave coverage analysis out here.

@scoder If you don't mind, lets try this again in #2289 with the fast-forwarded branch.


Adding work around mentioning during sat platform services

IM:CASMTRIAGE-6300
Reviewer:Ryan Haskeen
while running sat bootsys boot --stage platform-services, a traceback error is observed due to instant calls in the code.
The addition of the step which checks for cronjobs that need to be recreated immediately after kubelet is started on all Kubernetes nodes. Hence adding a note in the doc as workaround to re run the cmd and validate, until a permanent fix is added.

Description

Checklist

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[ ] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

This should be backported to release/1.5 as well

/backport release/1.5


changing styles and font

The website seems too basic. Adding some styles and font changes could make it more attractive

@Ishmeetkaur36  propose you design and make it more attractive .

⚠[URGENT]⚠ Reminder for GSSoC 24' Contributors Please join our CogniGuard Project #general GSSoC'24 Discord channel:
Here you can discuss your queries and doubts with your mentors.
See #109 issues section.

⚠[URGENT]⚠ Reminder for GSSoC 24' Contributors Please join our CogniGuard Project #general GSSoC'24 Discord channel:
Here you can discuss your queries and doubts with your mentors.
See #109 issues section.

Hey @Ishmeetkaur36 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Incrementally adding new languages to pre-trained models

Experiments design
Follow discussion here
pointers to code and datasets
Pretrained Models
To allow comparable preplexity values across languages. We need multilingual or monolingual models that are loaded with multilingual vocabulary.

...

Datasets

Oscar dataset tokenized using GPT tokenizer
....

Code

Megatron-Deepspeed finetuning see examples here

We've provided several scripts for pretraining both BERT and GPT in examples directory,
as well as scripts for both zero-shot and fine-tuned downstream tasks including MNLI, RACE, WikiText103, and LAMBADA evaluation. There is also a script for GPT interactive text generation.

...

Progress / Results

I would like to help implement the experiments.

This is quite a large task. For the moment implementation-wise I see 2 subtasks:

[ ] We need an implementation where instead of full finetuning we only finetune specific part of the architecture: eg. input and/or output embedding, normalization, other?
[ ]  Implement adapter layers

Experiment-wise

[ ] adapt English checkpoint to French ( we can take French part of Oscar?) by finetuning embedding layer
[ ] adapt English checkpoint to Korean by finetuning embedding layer
[ ] evaluate multilingual checkpoint to Russian/Japanese/other?
[ ] adapt mutilingual checkpoint to new languages (tbd)

For the task of implementing adapter layers, Adapter Hub has pre-trained multilingual adapters on Wikipedia (Amharic, Arabic, Armenian, Basque, Bengali, Bhojpuri, Burmese, Buryat, Cantonese, Chinese, Czech, English, Erzya, Estonian, Finnish, French, Georgian, German, Greek, Guarani, Haitian Creole, Hindi, Hungarian, Icelandic, Ilocano, Indonesian, Italian, Japanese, Javanese, Komi, Korean, Latin, Latvian, Meadow Mari, Min Dong, Mingrelian, Maori, Northern Sami, Persian, Portuguese, Quechua, Russian, Spanish, Swahili, Tamil, Thai, Turkish, Turkmen, Vietnamese, Wolof).
Referring to Modeling Multilinguality document, Catalan, Urdu, and Bangla are not included in the pretrained adapters on Adapter-Hub.

Hi! @yongzx!
Great stuffs.
All these adapters are for bert-base-multilingual-cased.
Hopefully we will be working with gpt-2 and later adapt our model following this tutorial.
https://github.com/Adapter-Hub/adapter-transformers/blob/master/adding_adapters_to_a_model.md
I see there are already example codes to train an adapter for LM here,
https://github.com/Adapter-Hub/adapter-transformers/blob/master/examples/language-modeling/run_clm.py
Probably we will have to change some stuffs here and there. But I think we are ready to start experiments for adapters. Let's discuss about these details in the next meeting.
@vnikouliNLE

Update - Dec 15, 2021 - We have results for fine-tuning GPT2 embedding layers for German and Korean. We've evaluated it on XNLI, and German's model has comparable performance as mBERT.
Next Steps:

Supervised and 0-Shot Evaluation on XQuAD and PAWS-X
Language Adapters + Finetuned Embedding Layers


Name or service not known

Hi @edbizarro I found this error when migrate:fresh. Am I missing something?
...
Writing lock file
Generating optimized autoload files
$ cp .env.example .env
$ php artisan key:generate
Application key [base64:xNynlz3AAFWMZu/WCEJQcSBB6vGH9ZfFkud2utVab3I=] set successfully.
$ php artisan migrate:fresh --seed

   Illuminate\Database\QueryException  : SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name or service not known (SQL: SHOW FULL TABLES WHERE table_type = 'BASE TABLE')

  at /builds/pathto/app/vendor/laravel/framework/src/Illuminate/Database/Connection.php:664
    660|         // If an exception occurs when attempting to run a query, we'll format the error
    661|         // message to include the bindings with SQL, which will make this exception a
    662|         // lot more helpful to the developer instead of just the database's errors.
    663|         catch (Exception $e) {
  > 664|             throw new QueryException(
    665|                 $query, $this->prepareBindings($bindings), $e
    666|             );
    667|         }
    668|

  Exception trace:

  1   PDOException::("PDO::__construct(): php_network_getaddresses: getaddrinfo failed: Name or service not known")
      /builds/pathto/app/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php:68

  2   PDO::__construct("mysql:host=mysql;port=3306;dbname=core", "root", "root", [])
      /builds/pathto/app/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php:68

  Please use the argument -v to see more details.
Uploading artifacts...
...

.env.example file
DB_CONNECTION=mysql
DB_HOST=localhost
DB_PORT=3306
DB_DATABASE=core
DB_USERNAME=root
DB_PASSWORD=root

.gitlab-ci.yml file
stages:
  - test

variables:
  MYSQL_ROOT_PASSWORD: root
  MYSQL_USER: root
  MYSQL_PASSWORD: root
  MYSQL_DATABASE: core
  DB_HOST: mysql

cache:
  key: $CI_COMMIT_REF_NAME
  paths:
    - vendor
    - node_modules
    - public
    - .yarn

test:
  stage: test
  services:
    - mysql:5.7
  image: edbizarro/gitlab-ci-pipeline-php:7.1
  script:
    - yarn config set cache-folder .yarn
    - yarn install --pure-lockfile
    - composer install --prefer-dist --no-ansi --no-interaction --no-progress --no-scripts
    - cp .env.example .env
    - php artisan key:generate
    - php artisan migrate:fresh --seed
    - ./vendor/phpunit/phpunit/phpunit -v --coverage-text --colors=never --stderr
  artifacts:
    paths:
      - ./storage/logs # for debugging
    expire_in: 1 days
    when: always

hi @Kristories are you sure the mysql service started correctly? Sometimes the service stuck and retry the job solves the problem.

Yep, sometime service stuck. Retry the job solve this problem. Thank you.


Removal of ACCESS_BACKGROUND_LOCATION permission - Validated

Extensive tests over 48hr+ shows removal of permission has no impact
Tested on Pixel 2 running Android 10

Closes #41
Signed-off-by: c19x<EMAIL_ADDRESS>

Please confirm on multiple versions of Android as permission policies have changed over time.

Tested successfully on :

Pixel 2 (Android 10) for 48hr+
Samsung J6 (Android 9, non-advertising) for 16hr+
Samsung A20 (Android 10) for 8hr+

No other Android version available for further testing.

ACCESS_BACKGROUND_LOCATION added in API level 29 (Android 10)
Expect no impact on Android versions before API level 29.


The training code keeps running for a long time

Hi synxlin,
Thanks for the repo!
I have prepared the s3dis data and running the following line
python train.py configs/s3dis/pvcnn/area5/c1.py --devices 0
After I run this line, my code keeps running for a long time(been running for the last 7 hours) and shows no output. It seems like it is stuck somewhere cause doing nvidia-smi shows no GPU utilization.
My command line looks like this:
(pvcnn) datumx@pop-os:~/data_science_experiments/3D_data/pvcnn$ python train.py configs/s3dis/pvcnn/area5/c1.py --devices 0

==> loading configs from ['configs/s3dis/pvcnn/area5/c1.py']

I would be grateful if someone could point me in the right direction.

Hi, @janismdhanbad. What's your Pytorch version?

@synxlin , Thanks for the reply. Pytorch version 1.5 with Cuda 10.2 on ubuntu 18.04. I will change the version to 1.4 and try again, thanks for pointing that out.

Hi, we are looking into the problems in Pytorch 1.5. Perhaps this issue #24 could help you.

Hi, it worked. I was playing with Pytorch and cudatool kit versions and it worked on Pytorch 1.4.0 along with cuda 10.1. Thanks!

hi, is the voxel_features right in the code:
voxel_features, voxel_coords = self.voxelization(features, coords)
I got all zeros elements

same problem with pytorch 1.6


Criar um algoritmo para o Minmax

Alialaa;
Code Explained

Issue move to: https://github.com/201flaviosilva/casino-arbor


Docs

I. Currently, I can modify/overwrite the type section and I can define my own.
************* Invalid Git Commit Message **************
commit message: fix: test
correct format: ():  => Can I modify commit pattern?
example:        docs: update README => This section is hardcoded in hook. Is there any place where I can put README file with my example?
II.
scope:
Optional, can be anything specifying place of the commit change.
For example $location, $browser, $compile, $rootScope, ngHref, ngClick, ngView, etc.
In App Development, scope can be a page, a module or a component.
subject:
A very short description of the change in one line.
Can I change the description in these two sections?

The commit pattern <type>(<scope>): <subject> should not be modified because it is guided by Angular.js Git Commit Guidelines and that is what the linter tools exists for.
example section will be configured in next release soon.
description section will be configured in next release soon too.

New version released. If your requirements are met I will close the issue. @frontlab-ml

@legend80s thanks mate, everything looks good!


Syntax highlighting is inappropriately dark after IIFE

Issue Type: Bug
I have the following code in a file:
export const someNumber = (() => {
	try {
		return 123;
	} catch (ex) {
		return 0;
	}
})();

export const numberIsLucky = (x) => {
	return x === 42;
};

Everything under someNumber (the declaration for numberIsLucky in this case) looks dark, as if the code is unreachable, even though it is not unreachable.
VS Code version: Code 1.45.0 (d69a79b73808559a91206d73d7717ff5f798f23c, 2020-05-07T15:57:33.467Z)
OS version: Darwin x64 18.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz (4 x 3500)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
8, 8, 6

Memory (System)
16.00GB (0.05GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

gitlens
eam
10.2.1

prettier-vscode
esb
4.7.0

pyformat
giy
1.0.1

vscode-docker
ms-
1.2.0

python
ms-
2020.5.78807

vsliveshare
ms-
1.0.2169

language-stylus
sys
1.11.0

selectline-statusbar
tom
0.0.2

This one is caused by microsoft/TypeScript#36828 that already fixed upstream in TS3.9 (and is in May iteration plan)
You can use https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-typescript-next extension which provides nightly builds with the fix.

Thanks for responding. I think I will just wait until it gets fixed in a stable build.


Poole?

Why there is Poole in the title :) ? It's not a poole port but a layon's right?

nvm, lanyon is a derived theme of poole..


"Boogey" isn't a word, and "boogie" is discriminatory

The website uses "boogeyman" as an example of where the -man prefix can be deleted, removing the gender connotations of the word and maintaining the same meaning. However, the definition of "boogeyman" is (according to dictionary.com):

an imaginary evil character of supernatural powers, especially a mythical hobgoblin supposed to carry off naughty children.

It suggests correcting to "boogey", which either is

a lively form of rock 'n' roll, based on the blues.

or

a contemptuous term used to refer to a black person.

In a context of referring to an individual as a "boogeyman", this could likely change a (gendered) term without any connotations into a confusing one with quite a few. Not a great example for the landing page...

True! Could you do a PR to change this line with something else then?


download xcode14.2 error

Describe the bug
此压缩文件“Xcode-14.2.0+14C18.xip”已损坏且无法解压。
To Reproduce
download xcode 14.2
Screenshots

Version

OS: 12.6
Xcodes: 1.8.0（16）

升级到V1.9.0就可以了。

If you upgraded after initiating the download (like I did), you may have to delete the malformed downloaded fragment in the local cache path (in settings) in order to get it to work.

tried deleting the local cache. Does not fix the issue.

@BrentMifsud @Charlotte3240  I see you're on 1.8. Please update to 1.9 which should fix your issue.

Will do.

1.9 and deleting cache fixed the issue for me.

I have done the following, but I keep facing the "Unable to install Xcode" problem:

I have version 1.9
I have cleared the cache (I've even used a new directory)
I'm logged in on my Apple account inside XCodes.app.

I'm on macOS 13.1 (22C65), MacBook Pro M1 14.

I'm not facing the same issue on another Mac which is running macOS 12.3.1 (MBP M1 16"). The install doesn't block on this other machine (it's macOS 12.3.1 so I can't start Xcode 14.2 but the version is downloaded without any issue)

I'm facing the same issue. I updated to the latest version and deleted the cache, and later even changed the directory. Same problem with 1.8.0 and 1.9.0.
I then tried the cli which also doesn't work but gives a better error message. It takes roughly two seconds until the error happens.

For some reason, it works again. Yesterday I downloaded one version manually directly from apple which got recognized by xcodes. For my tooling I had the problem, that I had no xcode Application, only xcode-<version.number>. After I fixed that, I did sudo xcode-select --reset which (I think) fixed "You have to install development tools first"
Today I tried to use xcodes again, and now it works. I'm not sure what exactly fixed it, but maybe it helps other people

I'm not sure how solve this problem.
Using v1.9.0 (17)


subworkflow:

only add init stage if init_task has non-empty parameters
add kwarg in stageview to decide whether subworkflow is scheduled in isolation
(preparing for recursion / loops)

Coverage decreased (-0.02%) to 90.185% when pulling c5090cfcbee82a40837c224fbe86d4d6a5f17efa on subworkflowOptionalInitAndIsolation into bcc263c6b18044d0b77355d88c97fbd39dc4f2ec on master.

Coverage increased (+0.02%) to 90.235% when pulling 187e32f34498be8ad9f0f0eab3f8756a7a7ea856 on subworkflowOptionalInitAndIsolation into bcc263c6b18044d0b77355d88c97fbd39dc4f2ec on master.


apply fix from app/services/newspaper_works/data/work_files_decorator to the iiif_print gem

ref LV: https://github.com/scientist-softserv/louisville-hyku/blob/main/app/services/newspaper_works/data/work_files_decorator.rb
compare to iiif_print: https://github.com/scientist-softserv/iiif_print/search?q=commit_assigned
redefine method in iiif_print to match LV

TODO: Trace down the commit of the project that pulled this fix in, to try to figure out what this fixed. please take notes on findings.

TODO: Trace down the commit of the project that pulled this fix in, to try to figure out what this fixed. please take notes on findings.

LV: https://github.com/scientist-softserv/louisville-hyku/blob/42a0fc837fd9ef4832a9741731672200e0097305/app/services/newspaper_works/data/work_files_decorator.rb
Overrides newspaper_works 1.0.1 to allow update or create based on work state

There are specs to test the paths of this fix


usage ?

Normally  i have to do this..
tailwindcss -o ./public/styles.css --minify --watch

So then how to do this with this package ?
tailwind -o ./public/styles.css --minify --watch

This package is more tailored to programmatic usage. It does come with a CLI, but it's just a simple example. To do what you suggested, you can create your own CLI that uses the library.


added extra parameters to define node for nodeSelector

Added extra parameters to be able to stick to specific cluster node:
serverNode - specify node for netperf server
clientNode - specify node for netperf client
example usage:
./netperf-tester -number 500 -output data.csv -serverNode <IP_ADDRESS> -clientNode <IP_ADDRESS>

This change is

CLA signed

updated user email

Cla still not fixed

@mikedanese could you pleas tell me what is best way to fix CLA issue ? Can I create another PR with proper email address ?


The system did not shut down IR2104 2104 (EN)   buck_Disable  buck_EN,  NO，LOW

The system did not shut down IR2104 2104 (EN)   buck_Disable  buck_EN,  NO，LOW

I think you don't have enough panel to power your 48v battery. Also, why VO dropping? what is the capacity of your battery?

You need to add additional panels and make it close to 80v input. I will close this thread now.


Handling of special characters: preprocessing the notifications before display

Hi all
Thanks for the great work!
Is there a way to decode the special characters (é, à etc. crucial stuff for French speaking people) in the notification?
I encode the special characters before sending them to the FCM web api. When FCM returns the notification, I need to decode the string.
Thanks
RN 0.34.1
Android 5.1 device
App running in background

I'm not sure I understand your question. Can you send notification with é and display correctly?

If I directly send special characters in the text, I never receive anything. It seems that, unsurprisingly, fcm itself (the api at https://fcm.googleapis.com/fcm/send) does not handle it and requires an utf encoding.
So I encode the message and sends it. Problem is that what is then displayed as notification is the encoded version. Not user-friendly. I need to decode the message before displaying the notification.

Does it not work in both OS or just Android?
The best solution is report issue to Firebase team. isn't é part of UTF-8?
or you can do "data" message and in FCM.on callback present a local notification. However if user kills iOS app the callback won't be called.

Sorry, I meant uri encoding, not utf. And yes, I will report this to Firebase. Not everyone uses English :)
For now, I'm focused on Android, so your work around may be enough for the time being.
Thanks

why would you put message title/body in uri encode? shouldn't them be in POST payload?

They are in the POST payload. I got the code from SO. It is server side (AWS Lambda) and looks like below. (I curated it so there may be some small typos/mistakes)
var sendNotification = function(token, msg, user) {
let body = {
"to":token,
"data": {
badge: 1,
"custom_notification": {
"body": msg, //here is where special characters just mess up stuff
"title": user.firstName, //I guess here too special characters wouldn't go well
"priority":"high",
"show_in_foreground": true,
"picture": user.picture
}
}}
_send(JSON.stringify(body), "notification");
});
}
var _send = function(body, type) {
var options = {
hostname: 'fcm.googleapis.com',
path: '/fcm/send',
method: 'POST',
headers: {
"Content-Type": "application/json",
"Content-Length": parseInt(body.length),
"Authorization": "key=" + SERVICE_KEY
}
};
var req = https.request(options, function(res) {
console.log('Status: ' + res.statusCode);
console.log('Headers: ' + JSON.stringify(res.headers));
res.on('data', function (body) {
console.log('Body: ' + body);
});
});
req.on('error', function(e) {
console.log('problem with request: ' + e.message);
});
// write data to request body
req.write(body);
req.end();
}

I just tested with é by sending payload though postman, it works fine. I suggest you use some http library like axios, you life will be easier making http request.

ok. Will check. Thanks!


Taxes - Selected tax rate is not marked with green check mark

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.60-8
Reproducible in staging?: y
Reproducible in production?: y
Issue reported by: Applause - Internal Team
Action Performed:
Precondition:

User is an employee of Collect workspace.
The Collect workspace has at least 9 tax rates.

Go to FAB > Request money > Manual.
Enter amount > Next.
On confirmation page, click Show more > Tax.
Select a tax rate.
Open Tax list again.
Enter any term in search field and clear it.

Expected Result:
The selected tax rate should be marked with a green check mark because it will confuse the users when there is no highlight and check mark on the selected tax rate in a long list of rates.
Actual Result:
The selected tax rate is not marked with a green check mark. After clearing the search field, the selected item is not highlighted which will confuse the users.
Workaround:
n/a
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/8e71aa35-2c14-4d4c-8c76-b7b133ff3ef8
View all open jobs on GitHub

@anmurali I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Taxes - Selected tax rate is not marked with green check mark
What is the root cause of that problem?
We are not setting isSelected as true for selected option for the sections we are passing here
https://github.com/Expensify/App/blob/823e9c94604aba4aff5eaec9147a7d910987babf/src/components/TaxPicker.tsx#L63-L64
What changes do you think we should make in order to solve the problem?

We should set isSelected as true in these two places
https://github.com/Expensify/App/blob/823e9c94604aba4aff5eaec9147a7d910987babf/src/libs/OptionsListUtils.ts#L1284-L1287
https://github.com/Expensify/App/blob/823e9c94604aba4aff5eaec9147a7d910987babf/src/libs/OptionsListUtils.ts#L1332-L1333
and change
https://github.com/Expensify/App/blob/823e9c94604aba4aff5eaec9147a7d910987babf/src/libs/OptionsListUtils.ts#L1279

    const enabledTaxRates = sortedTaxRates
        .filter((taxRate) => !taxRate.isDisabled)
        .map((taxRate) => ({...taxRate, isSelected: selectedOptions.some((option) => option.name === taxRate.modifiedName)}));

and then add here
https://github.com/Expensify/App/blob/823e9c94604aba4aff5eaec9147a7d910987babf/src/libs/OptionsListUtils.ts#L1266-L1267
        isSelected: !!taxRate.isSelected,

What alternative solutions did you explore? (Optional)

Makes sense to fix this as it would be consistent with the design for other fields

CC: @MonilBhavsar this is related to the tax tracking project, not simplified collect configuration. Is it on your radar and being worked on somewhere else? If so, please close this issue!

We missed this small item. Let's do it here. I'll self assign and manage the issue. @hoangzinh let's select a proposal!

@FitseTLT any idea when the PR will be up?

PR will be up in 2 days

This is fixed by other PR as mentioned in https://github.com/Expensify/App/pull/40628#issuecomment-2103240888
I think we can close this

bump @anmurali for the payment. The PR was on the final review stage so Payment is due. Thx.

@anmurali Can u pls process the payment here, it is super ooooverdue?

everyone's been paid.


is parse server stateless or stateful

this might sound like a simple question but I would like to have some insight, from what I understand, in parse, when a parse user logs in for example, a session is created for that user. which is keeping the state of the user which is stateful ?
I quote from stack overflow : here

That is where the ST in REST comes from, State Transfer. You transfer the state around instead of having the server store it. This is the only way to scale to millions of concurrent users. If for no other reason than because millions of sessions is millions of sessions.

for example, being stateless has its advantages as "scaling to millions concurrent users", I want to get an insight of what parse server is starless or statefll, and the consequences and implications.

Parse server is designed to scale horizontally, and doesn't hold any critical state in memory.


enrico_download to be able to support reprocessed data with diffuse response

Is there any plan to implement the download and use of reprocessed data with diffuse response columns in enrico_download?. It might be handy for some unbinned analyses.
http://fermi.gsfc.nasa.gov/ssc/data/access/
ftp://heasarc.gsfc.nasa.gov/FTP/fermi/data/lat/weekly/diffuse/

Hi
this is what is already downloaded
cheers
david


Add ignore::ImportWarning to setup.cfg

~This will resolve #8123.~
This will resolve issues related to import cupy when testing Chainer with pytest. (#8138)

Could you clarify where ImportWarning comes from, specifically, and how it is related to chainer.warnings.PerformanceWarning?

import cupy itself can cause ImportWarning, which is ignored by default.
This can be verified by running python with -W error option:
>>> import cupy
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "******/python3.7/site-packages/cupy/__init__.py", line 12, in <module>
    from cupy import core  # NOQA
  File "******/python3.7/site-packages/cupy/core/__init__.py", line 1, in <module>
    from cupy.core import core  # NOQA
  File "cupy/core/core.pyx", line 1, in init cupy.core.core
  File "******/python3.7/site-packages/cupy/cuda/__init__.py", line 4, in <module>
    from cupy.cuda import compiler  # NOQA
  File "******/python3.7/site-packages/cupy/cuda/compiler.py", line 12, in <module>
    from cupy.cuda import function
  File "cupy/cuda/memory.pxd", line 11, in init cupy.cuda.function
  File "cupy/cuda/memory.pyx", line 1, in init cupy.cuda.memory
  File "fastrlock/_lock.pxi", line 4, in init fastrlock.rlock
ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__

Chainer internally uses cupy, so import chainer or like also imports cupy as well.
Therefore, cupy will be imported by ignore::chainer.warnings.PerformanceWarning in setup.cfg.
However, since import cupy causes an ImportWarning, which is to be regarded as an error (by filterwarnings= error in setup.cfg), this import stops halfway. This failure of import may cause failure of subsequent import cupy with different reason (not 100% confident).
To resolve this, we can simply make ImportWarning ignored. This is why I added ignore::ImportWarning to setup.cfg.
Also, the descriptions in filterwarnings look to be interpreted one by one (not 100% confident).
So, if we add ignore::ImportWarning after ignore::chainer.warnings.PerformanceWarning, PerformanceWarning is interpreted first and import cupy occurs before ImportWarning is made ignored. In this case, the error in import cupy persists. Therefore, we should add ignore::ImportWarning before ignore::chainer.warnings.PerformanceWarning.

@shmurai Thank you for the detailed description.
Tentatively I made an issue on cupy: https://github.com/cupy/cupy/issues/2476

@shmurai
The ImportWarning comes from a Cython issue (https://github.com/cython/cython/issues/1720) and it seems we can do nothing directly. I think the fix in this PR is probably the best option we can take.
However, ignore::ImportWarning could be a bit more specific to limit the affected part. It seems this works: ignore:can't resolve package from __spec__ or __package__, falling back on __name__ and __path__:ImportWarning
Also please write a comment above the line. I think it's helpful to include the following information:

The cause
Link to a GitHub issue, perhaps https://github.com/cupy/cupy/issues/2476?
The reason why it needs to be placed above ignore::chainer.warnings.PerformanceWarning

Just note: the issue to be fixed by this change blocks all other ChainerMN testing and development. I hope this get merged in priority (tagged as prio:high).

I could merge this PR in the current state and handle the above requirements later by myself, if you prefer. @shmurai

I'm working on the requested changes and I will update shortly.

Thanks!
Jenkins, test this please

Jenkins CI test (for commit b16d35e608bcdd24fbcd5b61ab2c5363a8a854f1, target branch master) failed with status FAILURE.

Test failure is unrelated.


vim glitches

Describe the bug
HI Arnaud, the beta version looks pretty good. I spotted a bug with vim (possibly related to buffer refreshing). As you may know, when you vim a file, the file content should “overwrite” everything in the terminal. While WebSSH doesn’t seem to be able to show the content correctly. The screenshot attached is the WebSSH interface in vim. Hopefully this can be fixed soon.
Tianyi
Screenshots

To Reproduce
I’m using vim on Ubuntu 18.04.4 LTS. To reproduce the problem, try to vim an existing file, e.g., vim foo.bar. If there are some lines on the top in the terminal before you vim a file, these lines will be merged with the content of the file you vimed. Also, when you use arrow keys in vim, it shows some problems.
Thank you and good luck!

Knock knock

Hi @tianyi21 👋

Hello @tianyi21  👋
I can't reproduce

@tianyi21 What's yours terminal settings?

That's quite embarrassing. I found my terminal type was somehow set to "DUMB" and this explains everything. Thanks for helping me to troubleshoot the problem. WebSSH is a great piece of work 🆒

@tianyi21 No problem thank you a lot for your feedback 🙏
Have a nice day ☀


Index out of range in get_matches with certain arguments

Rust Version: Tested with both 1.14.0 stable and 1.16.0-nightly (2017-01-03)
Clap version: 2.20.0
Steps to Reproduce
Compile my sample code and run it with any options except the default help and version options
Sample Code | Debug output with backtrace
Removing requires("media_transfer") fixes the issue.

It looks like I ran into a similar problem with this code:
#[macro_use]
extern crate clap;

use clap::{App,Arg,ArgGroup};

fn main() {
    let matches = App::new("myapp")
        .arg(Arg::with_name("req_a").required(true).takes_value(true))
        .arg(Arg::with_name("req_b").required(true).takes_value(true))
        .arg(Arg::with_name("req_c").required(true).takes_value(true))
        .arg(Arg::with_name("group_a").short("a"))
        .arg(Arg::with_name("group_b").short("b"))
        .group(ArgGroup::with_name("group").args(&["group_a", "group_b"]))
    .get_matches();
}

The error seems to be connected to the interaction between required arguments and arg groups. You need at least 3 required options to trigger the error. The ArgGroup only needs one member to trigger the error.
Note: The error seems to not be triggered when the number of group members exceeds the number of required options! If you add a group group_c, the error is fixed. If you then add a required option req_d, the error appears again, but now with the message 'index out of bounds: the len is 3 but the index is 3' instead of 'index out of bounds: the len is 2 but the index is 2'.
Here are the log files, cmpiled with feature = ["debug"], one with `RUST_BACKTRACE=1, and one withouit: clap error log

I just made a PR, #829. It seems to fix the issue for me.
@ShadowNinja Can you please check if it fixes it for you?

@SuperFluffy: Yep, that seems to do it.  :-)