Alternative server with https and subdomain support

I created a permanent host to use, and implemented HTTPS support.
lt -h "https://cloudkit.link" -p 80 --subdomain=whatever
PR are welcome at https://github.com/cloudatlasid/tunnel-server

@insign , I start tunnel-server in my cloud, but my client auto disconect. Can you help me?

Hi, sure, you mean the local client or the server service?

I installed the version of the tunnel server and apparently everything
is ok. When I go to my client and direct to connect to my host, he
connects but falls right away. And it on the server shows that you have
a connection. I don't know why it's falling.
E Hélio escreveu:

Hi, sure, you mean the local client or the server service?
--
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
Links:
[1]
https://github.com/localtunnel/server/issues/131#issuecomment-614389491
[2]
https://github.com/notifications/unsubscribe-auth/AKDM7B4765532EQJRBOBTNDRMZY4XANCNFSM4MFIXPSQ

When you try to another server it works completely fine?

Sim...quando eu conecto nesse seu https://cloudkit.link...funciona
perfeito....
But I wanted to set up a server myself, as yours is working I wanted to
know if you could help me to stabilize mine.

Strange... Have you configured ssl?
On Thu, Apr 16, 2020, 06:23 bmkimagem<EMAIL_ADDRESS>wrote:

Sim...quando eu conecto nesse seu https://cloudkit.link...funciona
perfeito....
But I wanted to set up a server myself, as yours is working I wanted to
know if you could help me to stabilize mine.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/localtunnel/server/issues/131#issuecomment-614526941,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIPXVIPD4XQIAELTLEZ2KDRM3FABANCNFSM4MFIXPSQ
.

no, simple http ... ssl is mandatory for connection?

On the server it informs that the client has connected, but in the api /
status it informs 0 in the tunnel.
Do you have any tips on what it might be?
localtunnel:server making new client with id proud-dingo-86 +0ms
{"tunnels":0,"mem":{"rss":43745280,"heapTotal":10969088,"heapUsed":9099968,"external":1907554}}

Have you disabled fw?

That's right, I had to disable ... I was trying to add a rule ... Thank
you
E2020-04-16 17:43, Hélio escreveu:

Have you disabled fw?
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
Links:
[1]
https://github.com/localtunnel/server/issues/131#issuecomment-614884461
[2]
https://github.com/notifications/unsubscribe-auth/AKDM7B6E6MHB4KYTXUXJ7ZLRM5UWFANCNFSM4MFIXPSQ

You are welcome.

@insign How are the dns subdomains handled in the server? Does the server have to host dns for the domain?

@insign
Hello, I'm trying to accomplish the same as you on my own server. I generated my certificates and forwarded both ports 80 and 443 to http://localhost:3000 on my server but I still get no output when I use lt -h "https://myserver.something" -p xxxx. Do you know where it could come from?
Thanks a lot

I'm sorry to say that I'm specialized in that project.

@insign
It’s whatever I finally did it by myself.

hi all! i have a question.. are you sure that the flow is full tls? by using wireshark on my server i see that some packets are in http

Any tutorial on this?


Labels on data points

It would be cool to be able to define whether or not the data points have labels attached to them, both for X and Y axis plots. A simply flag (labels: true/false) for each axis, and the labels would appear above the correct point. Styling and eventual positioning should be done via CSS for configurability.

Interesting, you mean per point or per series?


Zend_Validate_Hostname - updated TLD list to the version<PHONE_NUMBER>

https://data.iana.org/TLD/tlds-alpha-by-domain.txt

Build is failing because of #620

Thanks! :+1:


Add --module node18

Identical to nodenext, except implies --target es2022 like node16 does.
I validated the new baselines with
for f in tests/baselines/reference/*module=node18*; do
  [[ -e ${f/module=node18/module=node16} ]] && echo "$f" && diff "$f" "${f/module=node18/module=node16}";
done

and
for f in tests/baselines/reference/*module=node18*; do
  [[ -e ${f/module=node18/module=nodenext} ]] && echo "$f" && diff "$f" "${f/module=node18/module=nodenext}";
done

Closes #60705

The example you gave has a diff like:
diff --git a/tests/baselines/reference/nodeModulesJson(module=node16).errors.txt b/tests/baselines/reference/nodeModulesJson(module=node18).errors.txt
index b3f36d73fa..033a1c9f7c 100644
--- a/tests/baselines/reference/nodeModulesJson(module=node16).errors.txt
+++ b/tests/baselines/reference/nodeModulesJson(module=node18).errors.txt
@@ -1,10 +1,9 @@
-/loosey.cts(1,36): error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
+/loosey.cts(1,36): error TS2856: Import attributes are not allowed on statements that compile to CommonJS 'require' calls.
 /loosey.cts(6,9): error TS2339: Property 'default' does not exist on type '{ version: number; }'.
-/main.mts(5,36): error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
-/main.mts(6,52): error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
-/main.mts(8,10): error TS1544: Named imports from a JSON file into an ECMAScript module are not allowed when 'module' is set to 'Node16'.
-/main.mts(8,41): error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
-/main.mts(9,42): error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
+/main.mts(2,22): error TS1543: Importing a JSON file into an ECMAScript module requires a 'type: "json"' import attribute when 'module' is set to 'Node18'.
+/main.mts(3,19): error TS1543: Importing a JSON file into an ECMAScript module requires a 'type: "json"' import attribute when 'module' is set to 'Node18'.
+/main.mts(7,21): error TS1543: Importing a JSON file into an ECMAScript module requires a 'type: "json"' import attribute when 'module' is set to 'Node18'.
+/main.mts(8,10): error TS1544: Named imports from a JSON file into an ECMAScript module are not allowed when 'module' is set to 'Node18'.
 /main.mts(10,9): error TS2339: Property 'version' does not exist on type '{ default: { version: number; }; }'.

@@ -42,26 +41,24 @@
       "version": 1
     }

-==== /main.mts (6 errors) ====
+==== /main.mts (5 errors) ====
     import { oops } from "not.json"; // Ok
     import moreOops from "actually-json"; // Error in nodenext
+                         ~~~~~~~~~~~~~~~
+!!! error TS1543: Importing a JSON file into an ECMAScript module requires a 'type: "json"' import attribute when 'module' is set to 'Node18'.
     import typed from "actually-json/typed"; // Error in nodenext
+                      ~~~~~~~~~~~~~~~~~~~~~
+!!! error TS1543: Importing a JSON file into an ECMAScript module requires a 'type: "json"' import attribute when 'module' is set to 'Node18'.

     import config from "./config.json" with { type: "json" }; // Ok
-                                       ~~~~~~~~~~~~~~~~~~~~~
-!!! error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
     import { default as config1 } from "./config.json" with { type: "json" }; // Ok
-                                                       ~~~~~~~~~~~~~~~~~~~~~
-!!! error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
     import config2 from "./config.json"; // Error in nodenext, no attribute
+                        ~~~~~~~~~~~~~~~
+!!! error TS1543: Importing a JSON file into an ECMAScript module requires a 'type: "json"' import attribute when 'module' is set to 'Node18'.
     import { version } from "./config.json" with { type: "json" }; // Error, named import
              ~~~~~~~
-!!! error TS1544: Named imports from a JSON file into an ECMAScript module are not allowed when 'module' is set to 'Node16'.
-                                            ~~~~~~~~~~~~~~~~~~~~~
-!!! error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
+!!! error TS1544: Named imports from a JSON file into an ECMAScript module are not allowed when 'module' is set to 'Node18'.
     import * as config3 from "./config.json" with { type: "json" };
-                                             ~~~~~~~~~~~~~~~~~~~~~
-!!! error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
     config3.version; // Error
             ~~~~~~~
 !!! error TS2339: Property 'version' does not exist on type '{ default: { version: number; }; }'.
@@ -70,7 +67,7 @@
 ==== /loosey.cts (2 errors) ====
     import config from "./config.json" with { type: "json" }; // Error
                                        ~~~~~~~~~~~~~~~~~~~~~
-!!! error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
+!!! error TS2856: Import attributes are not allowed on statements that compile to CommonJS 'require' calls.
     import config2 from "./config.json"; // Ok
     import { version } from "./config.json"; // Ok
     import * as config3 from "./config.json";

Maybe this is preexisting, but with:
@@ -70,7 +67,7 @@
 ==== /loosey.cts (2 errors) ====
     import config from "./config.json" with { type: "json" }; // Error
                                        ~~~~~~~~~~~~~~~~~~~~~
-!!! error TS2823: Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'nodenext', or 'preserve'.
+!!! error TS2856: Import attributes are not allowed on statements that compile to CommonJS 'require' calls.
     import config2 from "./config.json"; // Ok

If someone wants to dual emit CJS/ESM but needs to write an attribute for JSON, are they out of luck? require allows JSON so I would have sort of expected us to say "okay" to this. But maybe it was already this restrictive?

Yeah, that is preexisting, but a good point.

Well, you can't write import = if you want to be able to emit ESM, but you can of course always just read the file from the FS (ignoring potential emit path differences).
Just to be clear, is it preexisting as in "always", or preexisting in 5.7 specifically due to our added checks for attributes?

That’s not true; import = compiles to createRequire(import.meta.url)(...)
This looks like a new problem for us because of the new checks, but Node.js has enforced import assertions/attributes on JSON imports even while we have not, so we aren’t closing any doors with this. Anyone trying to do this previously has already had to work around it for runtime reasons, without help from TS.

Wow. I had no idea we did this:
import blah = require("react");

console.log(blah);

import { createRequire as _createRequire } from "module";
const __require = _createRequire(import.meta.url);
const blah = __require("react");
console.log(blah);


Docs validator

list as of right now:
'SpawnInfo', 'set', 'HttpRequest', 'UdpServer', 'customtheme', 'size_t'

SpawnInfo - no idea, little documentation, no examples
set - we have maps, sets, vectors, tables, arrays - would be great to decide on like one name, or because of the standard objects come with some extra functions, maybe would be good to not rename them and just write a documentation?
HttpRequest and UdpServer - no idea
customtheme - should just ignore? it's in the force_custom_subtheme and force_custom_theme, as they are written in a "non standard" way compared to other stuff
size_t - if i remember correctly, sol2 doesn't handle unsigned 64bit well, also this is only used for get_address and get_rva which i don't think should be in the API doc, as almost no one except people who work on this project/reverse engineer the game use this

We can stop renaming the stl containers and link to https://sol2.readthedocs.io/en/latest/containers.html in the first section for reference.
I think the idea of returning the socket types was to transfer ownership or something, but I don't really know how it all works out.
Why keep the debug functions a secret though?

We can stop renaming the stl containers and link to https://sol2.readthedocs.io/en/latest/containers.html in the first section for reference.

Don't think this has any value to someone that just wants to write a mod and have no knowledge about C++, standard library etc.

Why keep the debug functions a secret though?

Hard to keep something secret in open source project 😄 . It's just that normal people don't have use for those. And for example: if i ever needed to get address for pattern, i would never think to look in the API doc for something like this

Don't think this has any value to someone that just wants to write a mod and have no knowledge about C++, standard library etc.

Just write a doc section about the container types yourself then if you think that's not good enough. It's would probably be enough for most people if we just say that all of these containers can be used like lua tables, but maybe add a matrix of available operators/methods too.

Hard to keep something secret in open source project 😄 . It's just that normal people don't have use for those. And for example: if i ever needed to get address for pattern, i would never think to look in the API doc for something like this

I don't know where else you would look for something like this, but I'd rather remove the deprecated functions before this, and I don't want to do that either. If it's in the api, it should be in the api doc. It's just more confusing if people find these functions and we intentionally left them undocumented.

set - we have maps, sets, vectors, tables, arrays - would be great to decide on like one name, or because of the standard objects come with some extra functions, maybe would be good to not rename them and just write a documentation?

arrays and tables can be different tho, luals has some advanced types related to that https://luals.github.io/wiki/annotations/#documenting-types

I am using the address functions through string.format("%x") always though, so returning hex strings automatically would just make it easier.

We can use * in the comments again, instead of this funny snowflake ✱

['HttpRequest', 'UdpServer'] left

I think the idea of returning the socket types was to transfer ownership or something, but I don't really know how it all works out.

So should i make them return nil or do actually ownership transfer and ignore the type in the validator?

right now there is no ownership, so the pointer is just dangling, if i do ownership transfer it will mean that using just udp_listen("url", foo) without saving the return will prompt sol to just delete the object
so it's kind of breaking change, but probably the right solution

The idea was to transfer the UdpServer to lua so it could have methods like close()... I just didn't add the type cause there were no methods yet and lua usertypes are only required by this validator. You can add an empty type or even implement :close() for it, definitely not return nil.
HttpRequest is a similar story, although it has a pretty short lifespan and doesn't really matter what it returns, as the callback handles success and error. As long as it doesn't turn to garbage before the request even finishes.

And it's fine if garbage collection closes the udpserver when the lua handle is gone, that's how it's already documented but it just doesn't work like that.


Rename DeRecPairable to something else

Use creative powers to come up with a name that describes the role of the class as being "the representation at the sharer of a helper".

Looks good.


Layout problem

Game does not fit to display neither portrait nor landscape orientation.
Smartphone display with 1280x720 resolution.

Done. The game is displayed correctly on the mobile devices.
For example, on 720x1280 looks like this:


repeated flags are truncated

@mikkelhegn was trying to us a repeating flag for an az-mixin command and ran in to the problem of the corresponding az command not accepting multiple parameters of the same name (basically only taking the last into account).
Here’s his setup:
Porter.yaml snippet:
  - az:
      description: 'Deploy Web API configurations'
      arguments:
        - webapp
        - config
        - appsettings
        - set
      flags:
        ids: '{{ bundle.outputs.WEBAPI_ID }}'
        settings:
        - 'PGHOST={{ bundle.outputs.POSTGRES_HOST }}'
        - 'PGUSER={{ bundle.outputs.POSTGRES_USER }}'
        - 'PGPASSWORD={{ bundle.outputs.POSTGRES_PASSWORD }}'
        - 'PGDB={{ bundle.outputs.POSTGRES_DB }}'

The generated ‘az’ command – according to debug output:
az webapp config appsettings set --ids /subscriptions//resourceGroups/MyRG/providers/Microsoft.Web/sites/webapi-b2g2ndukr2eqy --output json --settings PGHOST= --settings PGUSER=******* --settings PGPASSWORD=******* --settings PGDB=*******
This results in only the last --settings argument is being stored by the RP. Now is it a “wrong” mixin or az implementation?
(For a second let’s disregard that the command takes a json-file as an input for a collection of settings as an alternative)
Reading through this, I tend to be of the opinion, that there could be a better az command implementation: https://github.com/Azure/azure-cli/blob/dev/doc/command_guidelines.md#collection-management-with-commands
e.g.
webapp config appsettings setting set --ids xxxxx --setting-name PSUSER --setting-value *****
webapp config appsettings setting set --ids xxxxx --file settings.json
The implementation which the mixin assumes, is not the recommended implementation, however it’s acceptable ☺: https://github.com/Azure/azure-cli/blob/dev/doc/command_guidelines.md#collection-management-with-actions
Two questions:
Do you agree it’s right to raise the issue towards the command owner to get the command fixed?
Should the az mixin support repeatable flags, if it’s an anti-pattern in az?

I do think it may be worth inquiring upstream (w/ the az cli maintainers) if adjustment of the --settings flag on that command, to support repeated invocations, might be possible.  I believe there are other az commands where this repeated form is used, so there is precedent.
For unblocking this particular use case, we can always fall back on exec mixin use.  It isn't as nice to read/compose, but it should get the job done:
  - exec:
      description: 'Deploy Web API configurations'
      command: az
      arguments:
        - webapp
        - config
        - appsettings
        - set
        - --ids '{{ bundle.outputs.WEBAPI_ID }}'
        - --settings 'PGHOST={{ bundle.outputs.POSTGRES_HOST }} PGUSER={{ bundle.outputs.POSTGRES_USER }} PGPASSWORD={{ bundle.outputs.POSTGRES_PASSWORD }} PGDB={{ bundle.outputs.POSTGRES_DB }}'

Lastly, I do think it might be worth considering adding configurability on how a repeated flag is parsed and turned into a cli invocation.  I could see this being applicable to any of our mixins.  For instance, maybe a toggle like repeat: true/false and a new repeatedFlags section, such that:
  repeatedFlags:
  repeat: false
    settings:
        - 'PGHOST={{ bundle.outputs.POSTGRES_HOST }}'
        - 'PGUSER={{ bundle.outputs.POSTGRES_USER }}'

results in ... --settings PGHOST={{ bundle.outputs.POSTGRES_HOST }} PGUSER={{ bundle.outputs.POSTGRES_USER }}
and the default can be repeat: true (behavior remains the same as what it is today):
  repeatedFlags:
    settings:
        - 'PGHOST={{ bundle.outputs.POSTGRES_HOST }}'
        - 'PGUSER={{ bundle.outputs.POSTGRES_USER }}'

results in ... --settings PGHOST={{ bundle.outputs.POSTGRES_HOST }} --settings PGUSER={{ bundle.outputs.POSTGRES_USER }}
Just spitballing there... design/approach could definitely be changed; but the gist of the functionality that we might want is there.


Cells Function Rebuilds Entire Array Every Time

Table.cell  performs very badly for large tables as it appears to rebuild the cell array every time you call it.
I found this to be an issue when using the htmldocx package. When adding a table, the cell function is called once for each cell which degrades performance significantly.
I have been able to circumvent this issue by getting _cells once and then referring to that array inside of the loop instead. However, this is a private property and it might be good to have an "official" way to do this without hacking around.

You may have a look here: https://github.com/toxicphreAK/python-docx-ng
I tried to implement this in https://github.com/toxicphreAK/python-docx-ng/pull/1 https://github.com/toxicphreAK/python-docx-ng/pull/8 and https://github.com/python-openxml/python-docx/pull/1196
Hopefully it may help you.

Yeah, tables in Word are complicated because they are so flexible. So you really need at least all prior rows as context to compute whether a particular cell is merged and so forth.
Add this to the characteristic of python-docx that all document state is (necessarily) stored in the XML, and the fact we can't tell whether you've mutated the table between two Table.cell calls, then you get this situation.
I think what's called for here is two alternatives (three if you count the current functionality), depending on whether you're reading or writing:

In the reading case, there could be a table "snapshot" that you can read as much as you want without anything needing to be recomputed. The contract would be that any table mutations are ignored by the snapshot, but as long as folks know about that and know they aren't going to be changing anything, they can get much higher read performance.
In the writing case, there could be a table "buffer" object that you could write to performantly, but didn't actually mutate the document until you called its .save() or maybe .sync() method.

I'm making this a feature request. Not sure when or if we'll get to it, but it would be a solid enhancement.


Instant crash with BD 1.2.1

Describe the bug
Discord crashes after saying "starting..." I think it happens when applying themes.
To Reproduce
Steps to reproduce the behavior:

Start Discord.
Wait for the main window (with the Discord facts) to pop up.
See the crash while themes are applied.

Expected behavior
Discord should open normally and I should see my beautiful theme and custom background.
Screenshots
https://imgur.com/a/qK9QuVZ
System Information:

OS: Windows 11 Pro
Discord Version: Stable 1.0.9011

Additional context
Found the version number in the installation folder of Discord.
I use BD 1.2.1
I use the "SoftX" theme and I have ~20 plugins as well.

See https://github.com/BetterDiscord/BetterDiscord/commit/fbff8e2e52b8076cbab5e908ecdb2524665702e5, this commit should fix the crashing.
Either do a manual to apply or download the betterdiscord.asar from the commit artifact https://github.com/BetterDiscord/BetterDiscord/suites/11792215423/artifacts/615230861

Thank you @maenDisease . the ".asar" file fixed the issue. I guess this will get fixed with an update so I am closing this.


Need a release of 9.4.15-1.pgdg80+1

I'm looking for a release of Postgres image containing version 9.4.15-1.pgdg80+1.
I see the commits on master for this, but then the current rendered Dockerfile for this says 9.4.15 rather than 9.4.15-1.pgdg80+1. So that seems strange...
Then there seems to be the issue that hub.docker.com only has a tag for 9.4.14. So that leads me to believe that the 9.4.15* image hasn't been released at all.
I'm not really aware of how the image release sequence of events caries out. So please forgive me if I'm jumping to conclusions that are opposite of what really happens.

This is causing issues for me because my Dockerfile extends postgres:9.4. Within the Dockerfile I've got the common RUN set -xe && apt-get update && ... lines, which means postgres is getting updated to 9.4.15-1.pgdg80+1. Then another lines upgrades triggers the upgrade of postgres-9.4.
I'd image under most circumstances this wouldn't be an issue, but for a yet to be determined reason it's causing my resulting container to not allow external connections.

See https://github.com/docker-library/postgres/blob/b84ddd1619ee3a7f6e318bb9ac33f39818b3b548/README.md, especially the following bit:

See a change merged here that doesn't show up on the Docker Hub yet? Check the "library/postgres" manifest file in the docker-library/official-images repo, especially PRs with the "library/postgres" label on that repo. For more information about the official images process, see the docker-library/official-images readme.

We have @docker-library-bot which auto-commits any buildable/test-passing result of running ./update.sh (which bumps the version numbers), and then creating that final PR to update library/postgres (which is what updates the actual image) is a manual process; see https://github.com/docker-library/official-images/pull/3698. :+1:


STORM-1649 Optimize Kryo instaces creation in trident windowing

This PR is raised as other https://github.com/apache/storm/pull/1273 is merged/closed but it is reverted saying that there was a build error. But Travis CI build and my local builds are passed.
Could not reopen https://github.com/apache/storm/pull/1273 as it is merged/closed.

@ptgoetz @harshach
This PR is raised as other #1273 is merged/closed but it is reverted saying that there was a build error. But Travis CI build and my local builds are passed. Could not reopen #1273 as it is merged/closed.

+1
Btw, build passed for my local builds.


el-polyton no space in 'έψ	εύσ'.

I have been attempting to convert these dictionaries to qtwebengine format using qt's qwebengine_convert_dict tool.
I was unable to convert the file el-polyton/index.bdic due to the following error:
Did not find a space in 'έψ	εύσ'.
Most other dictionaries did build using the tool so it leads me to believe that the fault may be with el-polyton/index.aff but as someone who is unfamiliar with hunspell, I am unable to tell if it needs a space instead of the tab.
If so, it seems more useful to report it here than just fix it at my end.

Could you check if the source dictionary, mentioned in the readme, has the same problem?

That's a lot of greek :)
Anyway, replacing the tab with a space using sed works for me here.
sed -i 's/REP έψ	εύσ/REP έψ εύσ/g' dictionaries/el-polyton/index.aff
To answer your question; I'd need a link to index.aff and index.dic
https://translate.google.com/translate?sl=auto&tl=en&u=https%3A%2F%2Fthepolytonicproject.gr%2Fspell%2F
I can't see one on the page you linked and I'm not natively Greek :)
Thanks!

You can get the last version from sourceforge, this includes the dic and off files: https://iweb.dl.sourceforge.net/project/greekpolytonicsp/greek_polytonic_2.0.7.oxt

@heydojo Ping!


Side-by-side buff/HOTs (like default)

Is your feature request related to a problem? Please describe:
Hi - I believe we briefly discussed this before in the comments on curse, but I really think it would be beneficial if we could display buffs stacking side-by-side, as with the default UI. For example, I'd love to have Tranquilty and Renew both show up in the middle of each unit's raid frame; currently, however, only one can be displayed at a time.
Describe the solution you'd like to see implemented:
(see above)
Describe alternatives you've considered:
Currently I could position buffs at different corners of the raid frame. This is useful, however, the left side pretty much cannot be used (since it blocks vital information), leaving only 6 slots available. For most classes, this isn't a significant issue, however it does become problematic with druids, since they have a multitude of HOTs and buffs that need to be displayed on the raid frames.
Additional context:*
None

I agree that it would be a very useful feature!


getDeviceId() returns Build.BOARD for Android

Bug report
Summary
getDeviceId() for Android will return Build.BOARD (see line here), but it seems that the correct intent would be to use Build.DEVICE. Or is there a reason this uses Build.BOARD that I'm not understanding?
Build.BOARD seems to return a string that helps identify the board / chip set, which seems like it could be the same on different device models, while Build.DEVICE should return a proper codename for the device.
For example: on my Samsung s10+ the Build file yields the following for key constants:
MODEL: SM-G975F
DEVICE: beyond2
BOARD: exynos9820
Using the above value in Google Play's current device catalog, if I want to filter by "Device model", I can use that Build.DEVICE codename to filter for that model, but that doesn't seem to be true with the Build.BOARD value. Though if I search by "System on Chip", I can find the chipset Samsung Exynos 9820, which has multiple devices associated with it.
Environment info
Any Android Device
Library version: the latest
Steps to reproduce
N/A see link to code
Reproducible sample code
N/A see link to code

Interesting - probably just an oversight. If I recall I was the one that added all those and I was typing pretty quickly during the v2-v3-v4 thing while trying to handle the "we want constants" / "we want fast startup so it should be async" difference of opinion, so in other words likely just a bug.
If you proposed a PR that re-directed the API to the constant that seems like a better fit and added an API that gave the old information, then we'd have a semver major breaking change but it would be pretty painless for people that needed return-value consistency to handle existing data etc
If you see anything else missing from here https://github.com/flutter/plugins/blob/90924b5727a9dbadbff8aa51db704c007188dd71/packages/device_info/device_info/android/src/main/java/io/flutter/plugins/deviceinfo/MethodCallHandlerImpl.java#L41-L52 it wouldn't hurt to add it either
Cheers

@mikehardy thanks for the reply. I will take a look into a PR then, when I get a chance. Cheers!

@mikehardy Hi,
I have one other issue.
I'm using this module since now ,but it's not working right now.
Problem is, I switched to api level 29 for android X, and the module threw java.lang.securityexception: getdeviceid
How can I solve this problem? I think this is a problem caused by a change in Google policy. So I can't use it anymore?

If that API throws SecurityException (a RuntimeException so they did not have to declare that they were introducing a breaking change, how nice of them...) now on compile target 29, then we should catch it.
If you propose a PR that wraps that API in a try/catch for 'Exception' and returns the default value, I can merge it

If that API throws SecurityException (a RuntimeException so they did not have to declare that they were introducing a breaking change, how nice of them...) now on compile target 29, then we should catch it.
If you propose a PR that wraps that API in a try/catch for 'Exception' and returns the default value, I can merge it

I appriciate for your help. Thank you so much! i did invite for you.

Excellent @bryce0516 ! I don't need an invite though, once you have code you think works, just make a PR here and we may review it and merge it in this repo

Excellent @bryce0516 ! I don't need an invite though, once you have code you think works, just make a PR here and we may review it and merge it in this repo

googlePlayServicesIidVersion = "17.0.0"
buildToolsVersion = "28.0.2"
minSdkVersion = 19
compileSdkVersion = 29
targetSdkVersion = 29
supportLibVersion = "28.0.0"
excludeAppGlideModule = true
mediaCompatVersion = '1.0.1'
supportV4Version = '1.0.0'

i forgot something in your manual.. sorry i have to read more carefully. It's my fault. Your module is working perfectly!


[GCI] Fix travis script

Hello, please avoid opening multiple PRs for one task. Fixing the old PR is a good way to learn git, ofcourse if fixing the PR by yourself is hard you can ask for help!


bind_to_random_port seemingly does not try a new port when its first try is already bound

bind_to_random seems to fail with errno 13 (Permission denied) on Windows (specifically this is windows 7 enterprise SP1, using python 3.4 with pyzmq 14.4.1) when seemingly the real problem was that the port was already occupied, and it should've tried a new one. As far as I can tell, this could be because the ZMQ library itself is returning the wrong error code, but my repro code (see below) has, on occasion, printed out a port that seemed not to be occupied at time-of-failure. I had also added a print statement into zmq/sugar/socket.py which would print if it ever retired to bind a new port, and I never saw that print happen.
My apologies if this bug really belongs over in the main libzmq project - but I figured might as well start here. Additionally, I would suggest it makes sense to add a "bind_to_available_port" function which simply binds to port 0, has the OS give it an available port, and then returns that to the user. I am doing that now, to overcome my problems with this intermittent bug.
import time
import zmq

while True:
    print(loopnum)
    ctx = zmq.Context()
    sock = ctx.socket(zmq.SUB)
    port = sock.bind_to_random_port("tcp://<IP_ADDRESS>")
    print(port)
    sock.close()
    time.sleep(0.1)
    loopnum += 1

Thanks!

bind_to_random_port is a pyzmq feature, not libzmq, so this is definitely the right place. I don't know why failure to bind to an in-use port would raise EACCES instead of EADDRINUSE, but we can catch it anyway.

I would suggest it makes sense to add a "bind_to_available_port" function which simply binds to port 0

That makes sense. The ability to retrieve the last endpoint bound by libzmq wasn't around when I wrote bind_to_random_port, and it's not available on all supported libzmq versions (< 3.0). But we can do it when it's available.

#651 should handle both issues of the wrong errno and using :0 when available.

Great! Thanks much for fixing this so fast.


SA - THANK YOU! The great job!!!!

Sender<EMAIL_ADDRESS>Comment: Dear authors!
Thank you very much for the incredible set of widgets for Angular 4 - it is really the super set!!! Thank you!
I would like to ask the following: can I get binding through some attribute to validation result for inputs components? Will be very thank you for any reply.
Kind regards,
Dr. Hryhoriy Kravtsov
Open #8 in Usersnap Dashboard

Download original image
Browser: Chrome 61 (Ubuntu)
Referer: http://www.amexio.org/showcaseapp/v3/index.html#/home
Screen size: 1366 x 768 Browser size: 1301 x 653
Powered by usersnap.com

We have commonservice which can be used for amexio-components validation. @DatsGawas will create small example on plunker and send you.

Hi,
I have created plunker which will give you idea about how component can be validate.
https://plnkr.co/edit/bHfWM3szKELZFiccjsdX?p=preview


Dependency bump

Pull request

What this PR does / why we need it

Dependency bump

Which issue(s) this PR fixes

Fixes #
Describe testing done for PR

Additional information or special notes for your reviewer

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

Project coverage is 62.23%. Comparing base (38e8ed7) to head (b143bd2).
Report is 41 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #739      +/-   ##
==========================================
- Coverage   70.10%   62.23%   -7.88%
==========================================
  Files          17       22       +5
  Lines         950      985      +35
==========================================
- Hits          666      613      -53
- Misses        263      348      +85
- Partials       21       24       +3

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


Question: Why are there 3 types of OffsetSizeTraits?

Which part is this question about
In our code, there are 3 different OffsetSizeTrait: OffsetSizeTrait, BinaryOffsetSizeTrait and StringOffsetSizeTrait. The only difference between them is that BinaryOffsetSizeTrait and StringOffsetSizeTrait have a const dataType.
My questions are:

Why do we need three of them? Do we have to declare dataType as a const?
Could we just use one OffsetSizeTrait and get the dataType like this:

pub struct GenericBinaryArray<OffsetSize: OffsetSizeTrait> {
    data: ArrayData,
    value_offsets: RawPtrBox<OffsetSize>,
    value_data: RawPtrBox<u8>,
}

impl<OffsetSize: OffsetSizeTrait> GenericBinaryArray<OffsetSize> {
    ...
    pub fn get_datatype() -> DataType {
        if OffsetSize::is_large() {
            DataType::LargeBinary
        } else {
            DataType::Binary
        }
    }
    ...
}

I don't see an obvious reason why they need to be separate traits, especially given that get_datatype() could be a const fn...
Perhaps @alamb or @jorgecarleitao remember some context of why these are the way they are?

Perhaps @alamb or @jorgecarleitao remember some context of why these are the way they are?

They pre-date my time with the project. Maybe @nevi-me  or @andygrove  or @paddyhoran  have some memories or context to share

I introduced them. At the time BinaryArray, LargeBinaryArray, StringArray and LargeStringArray were 4 different structs. The OffsetSizes were introduced to simplify the code via generics. At the time I did not realize that it could be even simpler. I agree that it can be simplified (arrow2 has only one).

So I guess we can simplify the code by just reserving one offsetTrait and adding function const fn get_datatype() for GenericBInaryArray and GenericStringArray to get the DataType of the array.

Close this issue as #1645 has been merged! Thank you for your all opinions!


RecyclerView not sliding the panel on 3.3.1

We have a recyclerview in the sliding layout. On version 3.3.0 it worked ok, had small glitches like firing onclick after swipe up/down is finished (there was a bug for this here). After migrating to 3.3.1 it stopped affecting SlidingUpPanelLayout at all, only using the drag view.

I removed the 'dragView' and now the recyclerview scrolls the panel. I guess, now it is the correct expected behavior and in 3.3.0 it was a bug?
Also, the recyclerview scrolling has become less smoother with glitches when the sliding panel is scrolling from an anchor to fully expanded state.


chore(deps): update mongo docker tag to v7

This PR contains the following updates:

Package
Update
Change

mongo
major
6.0 -> 7.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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

GitHub release
v0.6.2

Your semantic-release bot :package::rocket:


Place the --output-mode in front of job scritp

Fixes #27
--output-mode option was wrongly put in the end of the submit command which cause the problem that stdout of submit command is not json parsable. The test was not able to catch it because the command was defined in the test but not directly get from the scheduler. Test is update to using the commond generated from scheduler and therefore being tested directly.

This is a critical one and leftover from previous change, so I merge it directly.


The SAML logout did not complete properly.

When I try logout, ADFS IDP is returning this error.
I analyzed IDP(Active Directory Federation Service on Windows Server) logs.
it is verify signature issue in logs.
But already, using same signature for IDP and SDP.
I'm success in login but when I try logout on SP, error
Please let me know. what is issue?
I attached screenshot.
Screenshot is ADFS screen after I logout on jangosaml2 project.
It is redirecting to ADFS...
Please guide.

Well, someone has asked you how you have resolved your problema here
https://github.com/IdentityPython/djangosaml2/issues/348
Would you like to give an hint?
Consider this more like a social Exchange 😉
For logout, It depends, we Need to know which logout endpoint the adfs has in its metadata

Yes. I post a solution for issue 348.
Also, SDP and IDP metadata
Service Provider Metadata
<ns0:SingleLogoutService Binding="
urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="
https://test.com/saml2/ls/"/>
<ns0:SingleLogoutService Binding="
urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="
https://test.com/saml2/ls/post"/>
IDP MetaData

For logout, It depends, we Need to know which logout endpoint the adfs has
in its metadata
Can you please check?
logout not working. please guide me, thank you
On Sat, Oct 15, 2022 at 7:23 AM Giuseppe De Marco @.***>
wrote:

Well, someone has asked you how you have resolved your problema here
#348 https://github.com/IdentityPython/djangosaml2/issues/348
Would you like to give an hint?
Consider this more like a social Exchange 😉
For logout, It depends, we Need to know which logout endpoint the adfs has
in its metadata
—
Reply to this email directly, view it on GitHub
https://github.com/IdentityPython/djangosaml2/issues/353#issuecomment-1279609864,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2TQG4IL75OEMHVF6TLNCBDWDH2PZANCNFSM6AAAAAARFVLD2Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

It seems that the idp has the same endpoint for both post and redirect bindings

[image: image.png]
I got SAML LogoutRequest token from saml tracer.
And by using SAML Tokens Tools, I checked token info.
As you see screenshot, SAML LogoutReqeust is invalida Signature.
IDP server log error(signature verification failed of logout request)
SDP djangosaml2 log( Returning form to the IdP to continue the logout
process)
Already, djangosaml2 config file, I set up ('logout_requests_signed':
True,).
Everything is fine except logout part.
Any guide?
Please. thank you
On Sun, Oct 16, 2022 at 7:02 PM Giuseppe De Marco @.***>
wrote:

It seems that the idp has the same endpoint for both post and redirect
bindings
—
Reply to this email directly, view it on GitHub
https://github.com/IdentityPython/djangosaml2/issues/353#issuecomment-1279955406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2TQG4KUJV7J6DL3ZU52W3TWDPVG3ANCNFSM6AAAAAARFVLD2Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

I'm not sure why SAML LogoutRequest is not signature  from SDP.
Please
On Tue, Oct 18, 2022 at 4:58 PM Xian Cai @.***> wrote:

[image: image.png]
I got SAML LogoutRequest token from saml tracer.
And by using SAML Tokens Tools, I checked token info.
As you see screenshot, SAML LogoutReqeust is invalida Signature.
IDP server log error(signature verification failed of logout request)
SDP djangosaml2 log( Returning form to the IdP to continue the logout
process)
Already, djangosaml2 config file, I set up ('logout_requests_signed':
True,).
Everything is fine except logout part.
Any guide?
Please. thank you
On Sun, Oct 16, 2022 at 7:02 PM Giuseppe De Marco <
@.***> wrote:

It seems that the idp has the same endpoint for both post and redirect
bindings
—
Reply to this email directly, view it on GitHub
https://github.com/IdentityPython/djangosaml2/issues/353#issuecomment-1279955406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2TQG4KUJV7J6DL3ZU52W3TWDPVG3ANCNFSM6AAAAAARFVLD2Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

you can disable the signature check if you need

Unfortunately. ADFS logout need signed logout request.
Already, I tried to disable signature, but ADFS logout need Signed Logout
Request.
I'm not sure why signed verification is failed.
any guide?
On Tue, Oct 18, 2022 at 8:50 PM Giuseppe De Marco @.***>
wrote:

you can disable the signature check if you need
—
Reply to this email directly, view it on GitHub
https://github.com/IdentityPython/djangosaml2/issues/353#issuecomment-1282421849,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2TQG4NWZTIGWFWIJNDKC33WD2TLRANCNFSM6AAAAAARFVLD2Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

I think, SAM2 Logout Request will be generated from SP side.
but even though, SP Logout Request signature is valid.
What is reason?
I think, this is djangosaml2 side issue because it is generating saml2
logout request, but signature is not valid after I check saml2 logout
request base64 encoded token.
Please!
On Wed, Oct 19, 2022 at 1:20 AM Xian Cai @.***> wrote:

Unfortunately. ADFS logout need signed logout request.
Already, I tried to disable signature, but ADFS logout need Signed Logout
Request.
I'm not sure why signed verification is failed.
any guide?
On Tue, Oct 18, 2022 at 8:50 PM Giuseppe De Marco <
@.***> wrote:

you can disable the signature check if you need
—
Reply to this email directly, view it on GitHub
https://github.com/IdentityPython/djangosaml2/issues/353#issuecomment-1282421849,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2TQG4NWZTIGWFWIJNDKC33WD2TLRANCNFSM6AAAAAARFVLD2Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Any lucky?
On Wed, Oct 19, 2022 at 1:38 AM Xian Cai @.***> wrote:

I think, SAM2 Logout Request will be generated from SP side.
but even though, SP Logout Request signature is valid.
What is reason?
I think, this is djangosaml2 side issue because it is generating saml2
logout request, but signature is not valid after I check saml2 logout
request base64 encoded token.
Please!
On Wed, Oct 19, 2022 at 1:20 AM Xian Cai @.***> wrote:

Unfortunately. ADFS logout need signed logout request.
Already, I tried to disable signature, but ADFS logout need Signed Logout
Request.
I'm not sure why signed verification is failed.
any guide?
On Tue, Oct 18, 2022 at 8:50 PM Giuseppe De Marco <
@.***> wrote:

you can disable the signature check if you need
—
Reply to this email directly, view it on GitHub
https://github.com/IdentityPython/djangosaml2/issues/353#issuecomment-1282421849,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2TQG4NWZTIGWFWIJNDKC33WD2TLRANCNFSM6AAAAAARFVLD2Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

please , can you check email above ticket?
thank you
On Wed, Oct 19, 2022 at 11:05 PM Xian Cai @.***> wrote:

Any lucky?
On Wed, Oct 19, 2022 at 1:38 AM Xian Cai @.***> wrote:

I think, SAM2 Logout Request will be generated from SP side.
but even though, SP Logout Request signature is valid.
What is reason?
I think, this is djangosaml2 side issue because it is generating saml2
logout request, but signature is not valid after I check saml2 logout
request base64 encoded token.
Please!
On Wed, Oct 19, 2022 at 1:20 AM Xian Cai @.***> wrote:

Unfortunately. ADFS logout need signed logout request.
Already, I tried to disable signature, but ADFS logout need Signed
Logout Request.
I'm not sure why signed verification is failed.
any guide?
On Tue, Oct 18, 2022 at 8:50 PM Giuseppe De Marco <
@.***> wrote:

you can disable the signature check if you need
—
Reply to this email directly, view it on GitHub
https://github.com/IdentityPython/djangosaml2/issues/353#issuecomment-1282421849,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2TQG4NWZTIGWFWIJNDKC33WD2TLRANCNFSM6AAAAAARFVLD2Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

I think that you should share the IDP metadata here, we should have to check which are the logout endpoints and their binding and then check in djangosaml2 if something should be done


Fix non-standard function declaration within kitty strategy and cleanup shellcheck warnings

Addition of non-standard function declaration broke kitty strategy from commit d7008abc25c5593e3d204d5b9508645fd40187e8 onward. This standardizes the function declaration and cleans up some warnings listed in ShellCheck.

Thanks for the review/merge! :-)


display address functionality

This helps partially validate a deposit address is valid.
Even better would be a signing challenge in addition to this, but we'd have to have verifymessage type support also baked in python.

rebased, no time to test this time, so please do


Implementing operation outcomes with BaseOperationOutcome

Hello!
We are implementing some server STU3 infrastructure using hapi-fhir and got ourselves into trouble when returning a collection that could contain OperationOutcome as part of the response.
We are getting an InternalErrorException from hapi-fhir because our OperationOutcome doesn't have a resource id, and if I put one then I get a weird url in the resource.
By reading at the code I can see that BaseResourceReturningMethodBinding allows anything that is a BaseOperationOutcome to not have an id (which is what we want) but STU3 OperationOutcome (the one we are using) does not implement BaseOperationOutcome but IBaseOperationOutcome.
Now looking for implementations of BaseOperationOutcome I couldn't find any within hapi-fhir (I might have missed something here). Is the expectation for the implementer to have their own BaseOperationOutcome implementation? I would expect that OperationOutcome does that but it seems like it's not the case. I quickly went trough the docs but I couldn't find anything helpful for this specific scenario.
I'm wondering now if this is intentional, accidental, or if I'm doing the wrong thing.
Any help/comments would be very appreciated.
Thanks!

Can you elaborate on what you're actually trying to accomplish?

Hi James,
What we are doing is that we've got data that comes from different sources, the FHIR APIs we have are aggregated. When one of the sources are down, we want to return whatever we have but also tell the client that something went wrong. To achieve that, we added an operation outcome in the returned bundle, HAPI should have treated OperationOutcome differently, i.e. not requiring an id, but because of this bug, it throws an exception instead.
Hopefully, my explanation clears it up

On this matter, we've tried implementing our own BaseOperationOutcome, and while it passes the validation in BaseResourceReturningMethodBinding it blows up later in the server when it tries to cast it to a BaseResource (BaseOperationOutcome when it's actually extending IResource -> IBaseResource)

This sounds to me like you want an OperationOutcome in the bundle in Bundle.response.outcome as opposed to having it mixed in with results, no?
You could have your resource providers return a Bundle insetad of a List/IResourceProvider as one way of accomplishing this, if that helps.


Where is the LayoutDesigner sample app code hosted?

Is it in another repo? I opened the .xcproj and there's no macOS app.

nvm, I found it..


Add backfill option to Schedule page

Description & motivation 💭
Adds Backfill option with modal to select start time, end time, and overlap policy on Schedule details page.
Screenshots (if applicable) 📸

Default times
Default times (into next day)

Design
Considerations 🎨
Testing 🧪
How was this tested 👻

[ ] Manual testing
[ ] E2E tests added
[ ] Unit tests added

Steps for others to test: 🚶🏽♂🚶🏽♀
Checklists
Draft Checklist
Merge Checklist
Issue(s) closed
DT-815
Docs
Any docs updates needed?

Code looks good! One question is that the time picker is 24 hour time for backfill and the Create/Edit time picker for Days of the Week/Month is 12 hour (AM/PM). Think we should make them all consistent? I think 24 hour time is better.

Tested it out, looks good!


Cleanup runners with force delete

I somehow ended up with 3 Runners stuck in state "Creating / Idle". Unfortunately, I don't know how this happened.
But I have no way to remove those runners. Even a force delete would not remove them:
garm-cli runner delete -f  garm-3b02ea89-ae22-4b2e-80b2-e91694ef9c1c
Error: sending request: error in API call: runner must be in "running" or "error" state

Of course, this is intended behavior, according to the code.
How do I clean up those runners?
Can we remove the requirement: must be in "running" or "error" state" ?
Michael Kuhnt<EMAIL_ADDRESS>Mercedes-Benz Tech Innovation GmbH (ProviderInformation)

As a quick hack, I think restarting garm should clean those up. Will look into removing that requirement.

This one has been bugging me a bit. A status of creating means the provider is in the process of spinning up a new instance for the runner. Once the CreateInstance() function of the provider returns, the status should transition to running if the operation succeeded or error if it failed.
What is interesting is tha the runner_status is set to idle. That status should be pending if the instance is in creating. If it transitioned to ```idle`` it means that the instance was spun up, it installed the runner and phoned home telling us it finished installing the runner.
This should only happen if garm was killed/restarted while it was creating the instance, and before CreateInstance() had a chance to return. The instance was still created in the provider with the appropriate user data, so it had all it needed to finish bootstrapping.
Do you know if garm was restarted or if it was killed?
At the very least, we should check all instances on startup. If we find an instance in creating when garm starts up, we should consider it to be in error, and clean it up.

Can we remove the requirement: must be in "running" or "error" state" ?

The reason why we have that check, is to avoid race conditions. Force deleting a runner does the following things:

Check if the runner is already registered and idle in github

If the runner is registered and idle, remove it. Runners that are currently executing a job cannot be deleted

Mark the instance as pending_delete and wait for the consolidation loop to reap it

If an instance were in creating when we decided to force delete it, we would mark it as pending_delete, but that status would be overwritten once CreateInstance() would return, setting the instance back to running.
To make this work, we need a mechanism to send a chancel to CreateInstance() and trigger a cleanup of any created resources. For the time being, we should make sure garm just cleans up those instances on startup.

I know this is not a real fix, but garm should clean up those runners if they fail to register within the bootstrap timeout set on the pool. If they do register, they should be cleaned up once they are used by a workflow.
I also added a Wait() on the pool loops when garm is shutting down (this should have been added from the start), so garm will wait for 60 seconds if a loop is busy creating an instance for example. This way we should at least avoid situations where garm bails before the provider returns.
Some consistency checks on startup would be better. When I get some free cycles, I'll look into adding that.


Swift 2.0 support

I would appreciate you would review this pull request.
This pull request is made with Xcode 7 GM.

Thank you for your support!


[BUGFIX release] Update deprecation wording in init.

The deprecation message has been rephrase to emphasize final users don't need to call this._super.
Though the deprecation is still there, I hope rewording the message would prevent new users from panicking when receiving the deprecation warning.
It is easier to update the message than to follow the other steps I suggested in the issue, so it seems like a feasible first step just in case ember-cli-release cannot be easily fixed.

Addressed both suggestions. Thank you!

LGTM
@stefanpenner - r?


Should mention Blazor component parameters are optional and can have a default value?

I was reading this completed ticket (https://github.com/dotnet/aspnetcore/issues/6864) and realized component parameter default values were not something I've been using and not something I recall seeing in the docs. It may also be worth mentioning that component parameters are optional.
I'm happy to create a small PR if it would be helpful.

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

ID: 81a32115-33f8-7d06-aaf0-b8ce918b5527
Version Independent ID: 31ad18df-1904-bbdd-cfed-8d0d0267c10e
Content: Create and use ASP.NET Core Razor components
Content Source: aspnetcore/blazor/components/index.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

@mrlife ... That's fine if you want to submit a PR. Otherwise, let's wait until after the holidays ⛄🎁 ... I'm buried in work right now and will be out for an extended vacation. 😅


test: Try to make rexpect tests more reliable

The flakiness may be because some output matches the prompt that is used
so set a unique one.
cc #625

bors r+


Normal/Normal radio buttons in Add alert

Rancher versions: 2.0 master 2/22
Steps to Reproduce:

Go to Add Alert page

Results:  The second option is Normal/Normal.  I think this supposed to be Normal/Critical?

Version - 2.0 master 2/23
Verified fixed


Variables don't work when quoted

Hi All,
When working with templates I would like to pass a variable that requires quoting.
create policy name={group_policy_name}_Cloud9 effect=Allow resource="*" description="Cloud9" action=[cloud9:*] conditions="aws:RequestedRegion=={aws_region}"
When I run it, the variable aws_region does not get replaced and it's literal value is used as you can see here:
[info]    Dry running template ...
create policy action=[cloud9:*] conditions='aws:RequestedRegion=={aws_region}' description=Cloud9 effect=Allow name=GroupName_Cloud9 resource=*

Same thing happens if I quote the variable on the description param and if I do not quote it, it works (description param).
It would be interesting to replace the variable on quoted fields like description.

Hi,
Thanks for your feedback. Using holes (i.e. missing parameters asked as input of the template) is not possible directly in quoted parameters. However, you can use concatenation (with +) of quoted parameters with holes or references. For example for your template, you could write:
create policy name={group_policy_name}_Cloud9 effect=Allow resource="*" description="Cloud9" action=[cloud9:*] conditions="aws:RequestedRegion=="+{aws_region}

Is this the behavior you expected ?


micronaut: 4.4.3 -> 4.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/micronaut-projects/micronaut-starter/releases.
meta.description for micronaut is: Modern, JVM-based, full-stack framework for building microservice applications
meta.homepage for micronaut is: https://micronaut.io/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.5.0 with grep in /nix/store/z6dhik6z3li8165bl57nxn5c68q31pad-micronaut-4.5.0
found 4.5.0 in filename of file in /nix/store/z6dhik6z3li8165bl57nxn5c68q31pad-micronaut-4.5.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

micronaut

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/z6dhik6z3li8165bl57nxn5c68q31pad-micronaut-4.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A micronaut https://github.com/r-ryantm/nixpkgs/archive/799c6d78e96b01abebf4f478e9e04445b75dbcea.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/799c6d78e96b01abebf4f478e9e04445b75dbcea#micronaut

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/z6dhik6z3li8165bl57nxn5c68q31pad-micronaut-4.5.0
ls -la /nix/store/z6dhik6z3li8165bl57nxn5c68q31pad-micronaut-4.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

micronaut

Maintainer pings
cc @moaxcp for testing.

Result of nixpkgs-review pr 319200 run on aarch64-darwin 1

1 package built:

micronaut


Adds initial support for secretsmanager update_secret

Fixes #2895
The support in this patch is preliminary and may or may not be feature complete.
It provides the basic support for update_secret so that future work can build on it as needed.

Coverage increased (+0.002%) to 94.293% when pulling 92bbc3fbacbbe65fc6d9e134d15e78c97d3e256c on caphrim007:feature.add-secretsmanager-update-secret into 92b0586b8bea979e3ddc617604ab37f59a13dd3d on spulec:master.

@bblommers ready for review


more security in the username

Add username uniqueness requirement (prevent error 500 at the same time).

Codecov Report

Merging #345 into master will decrease coverage by 0.61%.
The diff coverage is 100%.


issue about ioworker close in multi iowoker

Hi crane
i use multi iowoker for extreme stress
but somtimes some ioworker can not close. (detailed no going next step. seems like halt)
All Iowoker process ended  at debug process window but not process close ioworker.
i see UserWarning aboit semaphore_tracker in process debug console in vscode
Are there any additional points I should consider to manage iowokers?
sorry too many question ^^;

We have an example of stress test which starts multiple ioworkers: https://github.com/cranechu/pynvme/blob/master/scripts/stress/endurance_test.py
Try this script in your test platform, and see if any special difference with your script.
Please also upload scripts and logs for more details.
Thanks,
-Crane


Unable to override global mapperFromUnderscoreCaseToCamelCase

I'm trying to override global mapperFromUnderscoreCaseToCamelCase with a mapper that just returns the key untouched (in a different API properties are in camel case). I'm unable to do so because of this line: https://github.com/icanzilb/JSONModel/blob/master/JSONModel/JSONModel/JSONModel.m#L270.

Then don't use a global key mapper. Instead you might want to have a root model class which you inherit from for all your models. e.g.:
@interface MyBaseModel : JSONModel
@end

@interface MyModel1 : MyBaseModel
@end

@interface MyModel2 : MyBaseModel
@end

@implementation MyBaseModel

+ (JSONKeyMapper *)keyMapper
{
  return [JSONKeyMapper mapperFromUnderscoreCaseToCamelCase];
}

@end

@ implementation MyModel2

+ (JSONKeyMapper *)keyMapper
{
  // override standard key mapper for this model only
  return nil;
}

@end

That's a good suggestion, but I wanted to avoid changing all my models - there is quite many of them now.
More importantly - without further explanation I would treat the mentioned line as a bug. It's preventing me from overriding the global keymapper in this scenario (which isn't so uncommon) without any added value.

The global key mapper is there for convenience, but is not typically used in serious projects because it causes global pollution. Similarly, none of the JSONModel built-in networking code would be used by anything other than a hackathon-esque project. It's just there to help you get going more quickly.
I personally would be in favor of deprecating both features entirely, but that would depend on the opinions of the other maintainers.
The behavior of the line may well be considered unexpected, but it ultimately cannot be changed. Doing so is likely to break many projects.

Fair enough, thanks for the explanation. Marking global mapper as depracated would certainly help to avoid confusion.


Problem with known drugs / clinical precedence in beta API

An example of the query currently working in alpha for disease page: Example
An example of how the query does not work in the recently deployed API Example.
There could be more than one issue:

It complains about the activity field
After removing the activity field it does not complain but it returns a null

For BE purposes, you can remove the activity field from the API, if that's not the case already. We will navigate the problem in the FE and perhaps future work in drug index. We will address this in separate tickets.
You can focus on the second part of the problem, why it comes as null once the activity field is removed: Example

The PR fixed the issue with Phase that is Long .
The current issue is about the definition of Reference
The code
        s => s.flatMap(m => ctPattern findAllIn m("urls"))
      ) and```
is wrong.

The reference is [Seq[Map[String, **Seq[String]**]]

So the query breaks due the wrong mapping.

The issue does no longer apply

The issue does no longer apply


Return nil as an error in PreFilter()

#16

Codecov Report

Merging #17 (b1390fc) into main (ccdd582) will decrease coverage by 1.15%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #17      +/-   ##
==========================================
- Coverage   52.69%   51.55%   -1.15%
==========================================
  Files           1        1
  Lines         315      322       +7
==========================================
  Hits          166      166
- Misses        142      149       +7
  Partials        7        7

Impacted Files
Coverage Δ

plugins/podspread/podspread.go
51.55% <0.00%> (-1.15%)
:arrow_down:

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


[NEW] Position field in declarations is only showed for questions

Changes Unknown when pulling 77fe59405d93ddaf315765010e6239ddb3567dd2 on zenika-dev-javi into ** on zenika-dev**.


Admin displaying unstyled images and documents results listing

Issue Summary
When searching images or documents in the Wagtail Admin it is possible to arrive at an unstyled results listing page.
Steps to Reproduce

Create a project,  login to admin and add some images and/or documents
Click Images on Wagtail sidebar
Start typing in a search term to filter the images (don't press return)
Check the urls for the images by hovering over them (?next=/admin/images/results/?q=[search term])
Select an image from the listing
Modify the image (e.g. change focal point) and press Save
Redirected to the 'next' view that is rendered without styling

I would expect we should be returned to the correct image listing but it seems the /results/ in the 'next' parameter is messing things up ... remove this and the listing is correct.
I think it might be related to the listing_results change in 2.15:
"Isolate admin URLs for Documents and Images search listing results with the name 'listing_results'"

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: yes (well a pretty fresh project)

Technical details

Python version: 3.9
Django version: 4.0.3 and 3.2.12
Wagtail version: 2.16.1
Browser version: Firefox 98.0.2

Thanks for catching this, and for the detailed report! Looks like this was introduced in 2.16, in this commit: bafb4352ce9df41c1110555dcbf0c1f568775d7d


Heroku npm err missing script start

2020-04-26T10:24:02.958922+00:00 app[api]: Release v2 created by user<EMAIL_ADDRESS>2020-04-26T10:24:01.792614+00:00 app[api]: Release v1 created by user<EMAIL_ADDRESS>2020-04-26T10:24:02.958922+00:00 app[api]: Enable Logplex by user<EMAIL_ADDRESS>2020-04-26T10:24:01.792614+00:00 app[api]: Initial release by user<EMAIL_ADDRESS>2020-04-26T10:28:06.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2020-04-26T10:28:21.385999+00:00 app[api]: Deploy fced3208 by user<EMAIL_ADDRESS>2020-04-26T10:28:21.404936+00:00 app[api]: Scaled to web@1:Free by user<EMAIL_ADDRESS>2020-04-26T10:28:21.385999+00:00 app[api]: Release v3 created by user<EMAIL_ADDRESS>2020-04-26T10:28:22.000000+00:00 app[api]: Build succeeded
2020-04-26T10:28:25.781438+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:28:25.785303+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:28:25.699650+00:00 app[web.1]: npm ERR! missing script: start
2020-04-26T10:28:25.705042+00:00 app[web.1]:
2020-04-26T10:28:25.705436+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-04-26T10:28:25.705606+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2020-04-26T10_28_25_700Z-debug.log
2020-04-26T10:28:32.673054+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:28:32.491669+00:00 app[web.1]: npm ERR! missing script: start
2020-04-26T10:28:32.501679+00:00 app[web.1]:
2020-04-26T10:28:32.502023+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-04-26T10:28:32.503163+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2020-04-26T10_28_32_492Z-debug.log
2020-04-26T10:33:51.821732+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=bunnyfine.herokuapp.com
request_id=da796ea8-dafa-4a54-bdfd-2b226352765f fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-04-26T10:33:57.173342+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=bunnyfine.herokuapp.com request_id=66e79d8c-90b4-473c-b6ef-b108691333b4 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https2020-04-26T10:35:39.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2020-04-26T10:35:52.730968+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:35:52.475994+00:00 app[api]: Deploy 5044f5bf by user<EMAIL_ADDRESS>2020-04-26T10:35:52.475994+00:00 app[api]: Release v4 created by user<EMAIL_ADDRESS>2020-04-26T10:35:53.000000+00:00 app[api]: Build succeeded
2020-04-26T10:35:57.121560+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:36:08.918958+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=bunnyfine.herokuapp.com
request_id=fbae0a66-8eb5-41c5-8ba5-66b2c336be99 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-04-26T10:36:10.845154+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=bunnyfine.herokuapp.com request_id=79bdcf43-438f-4ce4-890e-6e65e34d6138 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https2020-04-26T10:36:59.668379+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=bunnyfine.herokuapp.com
request_id=796c321a-882b-453f-adf4-64267d7e0596 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-04-26T10:37:01.746798+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=bunnyfine.herokuapp.com request_id=7bc49a00-d9ea-42f3-aab4-8d2e33db2a33 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https2020-04-26T10:38:52.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2020-04-26T10:39:06.061487+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:39:05.868622+00:00 app[api]: Release v5 created by user<EMAIL_ADDRESS>2020-04-26T10:39:05.868622+00:00 app[api]: Deploy 5a71526b by user<EMAIL_ADDRESS>2020-04-26T10:39:06.000000+00:00 app[api]: Build succeeded
2020-04-26T10:39:10.466389+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:39:10.470381+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:39:15.320227+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:39:17.377070+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=bunnyfine.herokuapp.com
request_id=b6e542e1-c7b5-4627-9a83-569d39a8c0d3 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-04-26T10:39:18.214872+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=bunnyfine.herokuapp.com request_id=ecb53441-8db7-4de3-8303-467fb5389fbb fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https2020-04-26T10:40:52.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2020-04-26T10:41:05.654760+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:41:05.473588+00:00 app[api]: Deploy e1a7a413 by user<EMAIL_ADDRESS>2020-04-26T10:41:06.000000+00:00 app[api]: Build succeeded
2020-04-26T10:41:05.473588+00:00 app[api]: Release v6 created by user<EMAIL_ADDRESS>2020-04-26T10:41:09.582801+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:41:17.790829+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:41:21.946329+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:41:26.029574+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=bunnyfine.herokuapp.com
request_id=3bede607-cc34-4f4e-8847-2f4bbdc6359c fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-04-26T10:41:27.352042+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=bunnyfine.herokuapp.com request_id=b8f18ccb-f507-4a7e-b5b8-f3701aa67c53 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https2020-04-26T10:43:30.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2020-04-26T10:43:44.124960+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:43:43.902283+00:00 app[api]: Deploy 4b957007 by user<EMAIL_ADDRESS>2020-04-26T10:43:43.902283+00:00 app[api]: Release v7 created by user<EMAIL_ADDRESS>2020-04-26T10:43:44.000000+00:00 app[api]: Build succeeded
2020-04-26T10:43:47.523942+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:45:11.547343+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=bunnyfine.herokuapp.com
request_id=a39dcf12-bd56-4329-a187-6df81e5b1511 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-04-26T10:45:12.599444+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=bunnyfine.herokuapp.com request_id=deacc36d-be22-4440-9221-97cef512d6c0 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https2020-04-26T10:45:44.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2020-04-26T10:45:57.240795+00:00 app[api]: Deploy d63d7e72 by user<EMAIL_ADDRESS>2020-04-26T10:45:57.240795+00:00 app[api]: Release v8 created by user<EMAIL_ADDRESS>2020-04-26T10:45:57.668040+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:45:57.000000+00:00 app[api]: Build succeeded
2020-04-26T10:46:02.702032+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:46:15.009208+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=bunnyfine.herokuapp.com
request_id=db307e41-2edb-473f-ae10-ea19d864efe3 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-04-26T10:46:17.233958+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=bunnyfine.herokuapp.com request_id=41e2e2f0-dcca-40f8-b5e4-efbaeece386b fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https2020-04-26T10:49:13.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2020-04-26T10:49:26.276618+00:00 app[api]: Release v9 created by user<EMAIL_ADDRESS>2020-04-26T10:49:26.276618+00:00 app[api]: Deploy 01843851 by user<EMAIL_ADDRESS>2020-04-26T10:49:26.531638+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:49:26.000000+00:00 app[api]: Build succeeded
2020-04-26T10:49:30.599658+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:49:38.743691+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=bunnyfine.herokuapp.com
request_id=261cb0d7-8e64-4abd-84f2-3dbc73b3dec6 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-04-26T10:49:40.719777+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=bunnyfine.herokuapp.com request_id=adb878e7-de8b-4fe2-a92a-67704455028a fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https2020-04-26T10:51:19.100652+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:51:23.444800+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:53:09.484941+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:53:13.310489+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:53:26.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2020-04-26T10:53:39.647099+00:00 heroku[web.1]: State changed from crashed to starting
2020-04-26T10:53:39.348896+00:00 app[api]: Deploy de3e81e5 by user<EMAIL_ADDRESS>2020-04-26T10:53:39.348896+00:00 app[api]: Release v10 created by user<EMAIL_ADDRESS>2020-04-26T10:53:40.000000+00:00 app[api]: Build succeeded
2020-04-26T10:53:45.284566+00:00 heroku[web.1]: State changed from starting to crashed
2020-04-26T10:53:50.418199+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=bunnyfine.herokuapp.com
request_id=bbff7ef7-00aa-4fe6-8765-8ae08f4e76ec fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-04-26T10:53:52.351442+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=bunnyfine.herokuapp.com request_id=8fd42b12-9901-42a4-8193-af3ab3161a9a fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https2020-04-26T10:53:57.151704+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=bunnyfine.herokuapp.com
request_id=04dd424b-0f8c-4340-a48a-7cea6e50f8e4 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-04-26T10:53:59.318818+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=bunnyfine.herokuapp.com request_id=de519b3b-a4b2-4133-b9d7-29da4f826f17 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https

Hi, please elaborate, your package.json does not correspond to a Vulcan app


fix: handle outOfRangeData when range sync Deneb

Motivation
Cannot sync lodestar from mekong genesis due to this error Cannot sync blobs outside of blobs prune window
Description
Beacon node should return BlockInputType.outOfRangeData block input instead of throwing that error
Closes #7248

not a complete fix, got
Nov-27 06:31:46.242[chain]           error: Error processing finalized checkpoint epoch=132619 - No block found for slot 4243744 root 0x33644e93138cf253cd809458ca2022213ecc282aab3f2f98faaab3de117cc1ec
Nov-27 06:31:55.124[chain]           error: Error processing finalized checkpoint epoch=132620 - No block found for slot 4243744 root 0x33644e93138cf253cd809458ca2022213ecc282aab3f2f98faaab3de117cc1ec

the reason is all archiveBlocks never finish, and the archiveBlocks for epoch n try to reprocess blocks of epoch n-1. The first failed is
Nov-27 03:13:26.363[chain]           error: Error processing finalized checkpoint epoch=2 - No blobSidecars found for slot 64 root 0xe845c6383893d2ac7e4ec87a3cb836ccaaa4ff9a73f45e64d04ff2f0bb3ddd00

was able to sync with this branch from genesis (in progress, not finish yet), the error is gone
grep -e "Skip blobSidecars migration" -rn beacon-2024-11-27.log | wc -l
778

:tada: This PR is included in v1.23.1 :tada:

:tada: This PR is included in v1.24.0 :tada:


PlasmoCSConfig will not automatically merge configurations

What happened?
My configuration in content.js is as follows.
export const commonConfig: PlasmoCSConfig = {
    matches: ["<all_urls>"],
    world: "MAIN",
    run_at: "document_start",
    all_frames: true
}

The configuration of content in the automatically generated mainfest.json file does not add the field "world": "main" in this JSON section.
{
    "matches": [
      "<all_urls>"
    ],
    "js": [
      "common.04c99ea8.js"
    ],
    "css": []
}

Version
Latest
What OS are you seeing the problem on?
Windows
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
(OPTIONAL) Contribution

[ ] I would like to fix this BUG via a PR

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

@huangguangxuan main world scripts are not injected by the manifest, but in the bgsw. Did they enable the world feature for manifest CS?

Doesn't seem so: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_scripts

Doesn't seem so: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_scripts

Just wanted to point out that Chrome supports it directly in the manifest, so maybe there can be an escape hatch for people who want to just build for chrome?


In production, call reload-prod daily

Once #366 is done, reloads will be much faster. Write a cronjob in production that calls the reload script once a day.

For reference:
41 19 * * * cd /var/www/fitbit.ouguo.us/fitbit-challenges && ./bin/reload-prod


Refactoring prompt

Changes:

Moved value validation and type conversion into __internals.py to make prompt more readable

Codecov Report

Merging #48 (a5a79b7) into master (e646f2e) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #48      +/-   ##
==========================================
+ Coverage   99.65%   99.66%   +0.01%
==========================================
  Files           3        3
  Lines         291      300       +9
  Branches       81       82       +1
==========================================
+ Hits          290      299       +9
  Partials        1        1

Flag
Coverage Δ

unittests
99.66% <100.00%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

beaupy/_beaupy.py
99.55% <100.00%> (-0.02%)
:arrow_down:

beaupy/_internals.py
100.00% <100.00%> (ø)

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


Offsets are wrong

Lots of offsets in client.dll are incorrect.
To name a few:
Sanitized Player name is 0x630 not the 0x7* value
Bone Array is broken
Health is broken.
Is probably much more broken than just those.

Seems the entire pPlayerController structure is wrong. The 0x748 offset is entirely empty. And the sanitized name is now directly stored at the 0x640 offset.

Thanks for letting me know. I missed that some of the fields moved around in the schema related structures.
Could you let me know if all is fine now?

Thanks for letting me know. I missed that some of the fields moved around in the schema related structures.
Could you let me know if all is fine now?

I don't think so. sanitized player name is now at 0x630 and I think CSPlayerPawn + 0x7EB is iHealth now.
It looks like the structure is very off what it should be.

Ok. I've got a meeting in a few minutes, so I'll take a closer look afterwards.

There are no issues for me.
I can get health by reading local player pawn + 0x324 (m_iHealth) and player name by reading local player controller + 0x630 (m_iszPlayerName).
FYI, m_sSanitizedPlayerName is now at 0x740.

BoneArray can not work normally

There are no issues for me.
I can get health by reading local player pawn + 0x324 (m_iHealth) and player name by reading local player controller + 0x630 (m_iszPlayerName).
FYI, m_sSanitizedPlayerName is now at 0x740.

You are right about sanitized player name ptr, being at 0x740.
However reading PlayerPawn + 0x324 does not get m_iHealth.

const auto local_player_pawn = process::read_memory<uint64_t>(client_base + 0x180DB18);
const auto health = process::read_memory<int32_t>(local_player_pawn + 0x324);

printf("health: %d\n", health);

https://github.com/a2x/cs2-dumper/blob/3f6c8940978c16ea9a92714437b53b2ed3ffbd65/output/client.dll.hpp#L5725

DWORD64 GameSceneNode = mem.ReadEx<DWORD64>(EntityPawnAddress+ m_pGameSceneNode); this->BoneArrayAddress = mem.ReadEx<DWORD64>(GameSceneNode + m_fOverrideFogEnd);
It has been working fine before
After updating, it no longer works

Weird, just dumped and recompiled and now 0x324 is working for me as well. Strange...

Only issue now is something changed with the bone array.

still not working with this offsets

What is the bone point offset?

Can the author update cs2-dumper.exe?


Not work at FreeBSD 10.3

"syntax error" before delete all "function" in pduDecoder.sh and pduMain.sh
;-(
if delete all "function" (words) in pduDecoder.sh and pduMain.sh :  136: Syntax error: Bad for loop variable
Good idea but dosen't work

@NUBaster You can adjust the incremental part of the for statements, for example:
This:
for (( i=0; i < ${#input}; i+=2 ));
Would become this:
for (( i=0; i < ${#input}; i=i+2 ));
Be aware that this script is written to run in bash and it might not run as it is on sh (FreeBSD's default user shell) and other adjustments might be required.

After for (( i=0; i < ${#input}; i=i+2 )); have:  136: Syntax error: Bad for loop variable
PS I will read about bash & sh.

http://mywiki.wooledge.org/Bashism - answer for bash & sh differences.
There is two ways: run in bash (install it before - /usr/ports/shells/bash) or change code of pduDecoder.sh and pduMain.sh


Why it doesn't work ? - Bug

I can't download playlist on Youtube.It gives me error exactly under below.
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-i', '--playlist-start', '15', 'https://www.youtube.com/playlist?list=PL7B7FA4E693D8E790', '--verbose']
[debug] Encodings: locale 'UTF-8', fs 'UTF-8', out 'UTF-8', pref: 'UTF-8'
[debug] youtube-dl version 2014.02.17
[debug] Python version 2.7.6 - Linux-3.19.0-30-generic-x86_64-with-Ubuntu-14.04-trusty
[debug] Proxy map: {}
[youtube:playlist] PL7B7FA4E693D8E790: Downloading page #1
WARNING: [youtube:playlist] PL7B7FA4E693D8E790: Playlist page is missing OpenGraph title, falling back ...
ERROR: Unable to extract title; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1511, in _real_extract
playlist_title = self._og_search_title(page)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 428, in _og_search_title
return self._og_search_property('title', html, **kargs)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 416, in _og_search_property
escaped = self._search_regex(self._og_regexes(prop), html, name, flags=re.DOTALL, **kargs)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 356, in _search_regex
raise RegexNotFoundError(u'Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract OpenGraph title; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 493, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 158, in extract
return self._real_extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1517, in _real_extract
r'(.*?)', page, u'title')
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 366, in _html_search_regex
res = self._search_regex(pattern, string, name, default, fatal, flags)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 356, in _search_regex
raise RegexNotFoundError(u'Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract title; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.

You are using an outdated version of youtube-dl. Read our FAQ if you have troubles updating.


Update docker-compose.mkdocs.yaml

Resolves https://github.com/nireneko/ddev-mkdocs/issues/1

@bhanu951 don't forget the install.yml file, creates the folder and the mkdocs.yml file.
Could you check it please?

@nireneko changes made please review.

Checked on local and works, but in existing projects mkdocs.yml and docs folder must be moved out of mkdocs folder, if not, the project won't start.
I'm going to merge this and put one note in the release notes.
Thanks :)


*.map file cannot be parsed by souce-map package (originalPositionFor) correctly

Do you want to request a feature or report a bug?
bug

What is the current behavior?
soucemap mapping incorrectly
If the current behavior is a bug, please provide the steps to reproduce.

https://github.com/xiachaoxulu/sourceMapDemo

What is the expected behavior?
incorrectly
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Looks like problem in vue-loader. Try to update to latest version and feel free create new issue if problem still exists. Thanks!


[SPARK-45967][BUILD] Upgrade jackson to 2.16.0

What changes were proposed in this pull request?
The pr aims to upgrade FasterXML jackson from 2.15.2 to 2.16.0.
Why are the changes needed?
New version that fix some bugs, release notes as follows:

<IP_ADDRESS> https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.16, eg:
Databind #1770: Incorrect deserialization for BigDecimal numbers
2.15.3 https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.3, eg:
Databind #3968: Records with additional constructors failed to deserialize

The last upgrade occurred 6 months ago, https://github.com/apache/spark/pull/41414
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @pjfanning ~ Are there any areas to focus on when upgrading to use Jackson 2.16.0? Thanks ~

@LuciferYang it appears you are hitting some issues with tests but other than that, I don't expect significant issues. The changes are less significant than in 2.15.x.

https://issues.apache.org/jira/browse/SPARK-42854

Thanks for your explain @pjfanning

late LGTM


[BUG]  "old" versions of EKS/AKS/GKE do not show up in the new Dashboard

2.6.7-rc10

"old" / kev1 versions of EKS/AKS cluster deployed - are not seen on Cluster management and Home page.
They are however visible on Ember UI

On 2.6.6

cluster -  "old" / kev1 versions of EKS/AKS-  in Prov state doesn't come up on the Cluster Management UI; But it shows up in the home page and in the side nav
Cluster-  "old" / kev1 versions of EKS/AKS- in Prov state with a failure comes up on the Cluster Management UI

Expected:
As a user, i would expect all clusters to be listed in Cluster Management and Home page. - including EKS/AKS/GKE v1 prov (older versions of these hosted prov clusters)

2.7.5-rc1

"old" / kev1 versions of EKS cluster deployed - seen on Cluster management and Home page.
Visible on Ember UI as well

Thanks @cpinjani, closing as fixed


IconUpdate messages lost

Only the first icon updates for ICON_BIG and ICON_SMALL are detected by the DLL hook. Need to figure out why.
The problem probably reside in the Hookproc function.
Investigations:

Disable the sent_by_current_proc check: Didn't help
Disable the (code == HC_ACTION) check: Didn't help
??

Worked-around by 374e67b80ee5219816cbd2772b9ac7f5d0ee98f7.

The problems have now been properly fixed.


SS-132, SS-133, SS-134, SS-136, SS-415, SS-123, SS-124, SS-126, SS-134, SS-135 and SS-137: remaining manage types functionality

Changes include:

SS-132: Added front-end functionality to enable adding new leave and training types
SS-133: Added front-end functionality to enable drag-drop of the training and leave types to re-order
SS-136:

Added front-end functionality to display leave or training types based on drop-down selection
Created page layout for listing leave and training types

SS-415:

Added front-end functionality to edit assignment types
Displaying warning message if any changes are made

SS-123: Added front-end functionality to expire assignments
SS-124:

Added front-end functionality to display expired assignments
Prevent expired assignments from being edited

SS-126: Added front-end functionality to unexpire assignments
SS-134: Added front-end functionality to expire leaves/training
SS-135:

Added front-end functionality to display expired leaves/training
Prevent expired leaves/training from being edited

SS-137: Added front-end functionality to unexpire leaves/training

The error message I provided doesn't make sense when it comes to updating to duplicate leaves and training, as they don't have a location. I'll fix this.
I noticed visually the even/odd row ordering goes away when Active Assignments is checked or unchecked.. but isn't a big deal.
Other than that looks good.

The error message I provided doesn't make sense when it comes to updating to duplicate leaves and training, as they don't have a location. I'll fix this.
I noticed visually the even/odd row ordering goes away when Active Assignments is checked or unchecked.. but isn't a big deal.
Other than that looks good.

Thanks Travis, The removing of striped is intentional to highlight/distinguish between active and expired types.

Oh ok, sounds good.


Proposal: Changes to retryWhen

These would be breaking changes, but here goes:
Problem
Often with retryWhen there is a desire to reset some "state" of your retries when the stream your retrying starts receiving values successfully again. For example, in a network retry scenario where you want to exponentially step back from the first failure. Once you get a value over that network observable, you want to reset your exponential step back to the first level again, because things are going well now.
Current Solution
The current solution involves adding some peice of mutable state and altering it via side-effects:
let exponent = 2;
let result = source.retryWhen(errs => errs.switchMap(() => Observable.timer(Math.pow(2, exponent++))))
      .do(() => exponent = 0)

Proposed Change (and solution)
I propose a change that says the first successful value to "next" through the retryWhen subscriber causes the retry nofication subscription to unsubscribe, which will "reset" the state of any observable inside of there.
let result = source.retryWhen(errs => errors.switchMap((_, i) => Observable.timer(Math.pow(2, i)));

The behavior:

Subscribe to result
Subscribes to source and passes through successful values and completions
On error from source, the error is pumped into a Subject, and the notifier function passed to retryWhen is called  with an Observable created from that Subject.
The observable returned from the notifier function is subscribed to.
On next from the notifier, the source subscription is retried.
a. On first successful message from source, unsubscribe from notifier, then goto 3.
On error from the notifier, an error is sent down the chain to the result.
On complete from the notifier, the completion is sent down the chain to the result.

I took a look at retryWhen.ts, thought about your suggestions, and I think it's a reasonable breaking change.

I just spoke with @abersnaze here at Netflix, and I think there's a way to do this without a breaking change.
Basically, the idea is to add an optional second parameter that fires for each next from source, and is called with the value from the next, and the subscription from the inner errors subscription.
source.retryWhen(errs => errs.switchMap((_, i) => Observable.timer(2**i)), (value, sub) => sub.unsubscribe());

Another option would be a second arguemnt that was the same idea, but you just returned a boolean of whether or not to end the subscription.

Also, @stealthcode (from Netflix) had some thoughts about a different design (as a new operator). His concern with tearing down the inner subscription and starting it back up was based on the principle that that's an additional teardown and setup that you might not need. He wanted to try to keep the inner subscription  .. so it would look like this:
retryWhenWithNext(notifierFactory: (errorsOrNexts: Observable<any>) => Observable<any>)

The idea here is that each call to next or error would come through the observable passed to the notifierFactory.
given:  source.retryWhenWithNext((errorsOrNexts) => errorsOrNexts.filter(x => x instanceof Error))
source ---a---b---c---d---#
errorsOrNexts ---a---b---c---d---#---a---b---c---d---#

Given that type-checking in JavaScript isn't a thing, I'm not sure how this approach would work for us, so perhaps in our case it would be better to have a stream of Notification in there for that design:
repeatWhenNotified(notifierFactory: (notifications: Observable<Notification<T>>) => Observable<any>)

It's another design, and it's interesting, because it would actually allow for retries on async actions after errors, completions or nexted values.

@mattpodwysocki I'd really like your thoughts here, there's a lot in this thread.

I'm of the mind, that even if we implement a repeatWhenNotified type operator, we might still want to add the optional argument to retryWhen, as it wouldn't break the API, and it would be useful. Also retryWhen has a concise use case, where repeatWhenNotified would not. On the other hand, if those notifications were restricted to errors and nexts, then it would again, and we could call it retryWhenNotified I guess.

I've edited my comment above to clarify the options presented there.

+1

I think this issue still has merit... leaving it for now.

@benlesh I'm having exactly this issue while implementing a polling library based on RxJS. Is there any current, even dirty and extremely hacky, way to workaround this issue?

+1

This is pretty old, and there hasn't been much appetite to change it. However, we did at a "reset" to the retry operator, so perhaps we might go that route at a later time. Closing for now.