TableView: keyboard traps with certain focusable components

🐛 Bug Report
When including focusable objects in TableView there are focus traps for the following object types

DateField
DatePicker
TimeField
NumberField (not a trap but multiple keypresses appear to do nothing)
RadioGroup (selection gets set unexpectedly)
RangeSlider
SearchField
Slider
Picker (not a trap but unexpected behaviour)
Combobox (not a trap but unexpected behaviour)

🤔 Expected Behavior
There should be no keyboard traps
😯 Current Behavior

DateField - left/right arrow keys do not exit the component - we get stuck
DatePicker - left/right arrow keys do not exit the component - we get stuck
TimeField - - left/right arrow keys do not exit the component - we get stuck
NumberField - It takes 3 left/right keypresses to exit the component and move to the next/previous with no indication that anything happens after each keypress
RadioGroup - when using left/right to move through the component selection gets left on an unexpected entry
RangeSlider - get trapped on the slider. Left/right move the slider. Not sure how this could ever work in a table as you can't even use the component on its own.
SearchField - left/right arrow keys do not exit the component - we get stuck (Textfield works so this should probably be the same)
Picker - focus moves but also changes the selection
Combobox - left/right arrow keys do not exit the component - we get stuck

💁 Possible Solution
Some just need fixing to allow focus to break out
Some others (range slider for example) should be forbidden in a TableView
🔦 Context

💻 Code Sample
https://codesandbox.io/s/tableview-and-focusables-bed1t7
🌍 Your Environment

Software
Version(s)

react-spectrum
3

Browser
Chrome

Operating System
MacOS

🧢 Your Company/Team

🕷 Tracking Issue (optional)

Components that use the arrow keys for something are not currently supported in TableView. We need to implement edit mode for them to work. #2328

Components that use the arrow keys for something are not currently supported in TableView. We need to implement edit mode for them to work. #2328

This doesn't appear to be documented.

Closing in favor of #2328


feat(count-words): count occurrences of given string

Like so

P.S. rust analyzer kept screaming at me about the missing semi-colons

Oops wrong button lmao.

:p formating


data-table: check\uncheck behavior

Once you click "toggle all" checkbox in the header section - all the table checkboxes would be checked.
But once you uncheck some of the checkboxes - header checkbox would be still checked.
I think, it would be correct  to uncheck header checkbox right after any of checkboxes has been toggled off.

The current checkbox functionality is deprecated. Developers should create checkboxes manually and then they are responsible for implementing such functionality.


Support Nodes with Memory

Support nodes with memory, or starred nodes.
As already discussed over the phone, we have an open discussion to understand how nodes with memory shall be specified in COQ:

As @miccol pointed out, this functionality can in principle be delegated to skills.
On the other hand, it would be nice to have this functionality available directly in the BT interpreter itself because of usability (the behavior designer would otherwise have to focus on BT and the skills) and because this enables COQ to reason about the composition of BT and skills.

As for what concerns the implementation, classic functional approach to handle state is to let the semantic function (the tick function in this case) take the current state or store and return the updated state. The store is:

Classically, a map from the variable names to the variable values. This approach would definitively work but it would also incur the additional complexity of handling disambiguation whan BT are composed.
In order to support starred nodes, it is enough to have a boolean variable local to the node itself. For example see the proposed SMV implementation. The picture below highlights the differences between the binary sequence and the binary sequence with memory.

Looks good to me.
Note: I am not very familiar with the language but it is very similar to one I know (TLA+).

Is SequenceStar supported in out BT engine?
I tried with this xml
<root>
  <BehaviorTree ID="bt0001">
    <SequenceStar name="seq0001">
      <Action ID="ConditionTrue" />
      <Action ID="Action1SecondSuccess" />
    </SequenceStar>
  </BehaviorTree>
</root>

but I get the error: BT parsing error: unkown node: SequenceStar
I just updated the code.

Nope, starred nodes are not supported at the moment; you have to translate them manually into Fallbacks.

@altacch I do not understand the "translate them manually into Fallbacks* suggestion.
I added the smv files already in the repo the SMV formalization of the SEQUENCE/FALLBACK nodes for the simple BT semantics and also for the BT semantics with reset.
Can we have a discussion about how to extend the COQ BT interpreter so as to support these nodes at run-time as well? Do you have any idea about how to proceed?

I do not understand the "translate them manually into Fallbacks* suggestion.

I mean something like the discussion in Michele's book, section 1.3.2.

Can we have a discussion about how to extend the COQ BT interpreter so as to support these nodes at run-time as well? Do you have any idea about how to proceed?

This is surely going to be a major change: I don't see how to implement the functionality without adding a notion of state, either into the btree data type or inside the tick function.
In the first case we could, for instance, change the Node constructor from the current
Node: nodeKind -> string -> btforest -> btree
to something like
Node: nodeKind -> string -> btforest -> list return_enum -> btree
where the new argument is a list of return values from the previous tick. Note that this means that each tick updates the data structure (we may call it a btree_with_memory type).
Alternatively, we can add just another nodeKind, say SequenceStar, and manage the state by passing it as an argument to tick. At the moment I don't know which of the two ideas makes more sense.

I was aking because I wanted the robot to follow a path, so I tried with:
<root>
  <BehaviorTree ID="bt0001">
    <Sequence name="seq0001">
      <Action ID="Go_to_location_1" />
      <Action ID="Go_to_location_2" />
      <Action ID="Go_to_location_3" />
    </Sequence>
  </BehaviorTree>
</root>

With simple sequence it is not gonna work, because Go_to_location_1 will always be ticked (also after it succeeded) so as soon as the robot tries to go to location 2, it will come back at the following tick.
SequenceStar will fix this because it basically introduces memory.
Converting the previous sequence into fallback will be something like:
<root>
  <BehaviorTree ID="bt0008">
    <Sequence name="seq0008">
      <Fallback name="fb0008a">
        <Condition ID="Location1_done" />
         <Action ID="Go_to_location1" />
      </Fallback>
      <Fallback name="fb0008b">
        <Condition ID="Location2_done" />
        <Action ID="Go_to_location2" />
      </Fallback>
    </Sequence>
  </BehaviorTree>
</root>

Which basically means to move the memory inside the Condition.
This implies  that each condition must be a skill (executable) that externally (wrt the BT) checks for the condition and stores the value. It shall also be cleared eventually, by who and when?
The other option I see is to to use a blackboard, but this means the blackboard becames a must have also for very trivial BTs.
I think it'll be better if memory required by the BT could be handled internally, otherwise the complexity in integration is gonna explode very quickly.
Anyway, after chatting with @miccol we agreeded to:

for path including many waypoints I created a specialized skill (which in turns calls the basic navigation skill) which holds the memory for aldready accomplished steps.

I'll start to sketch a simple blackboard (in yarp) 'cause I sense it is gonna needed anyway, and I'm waiting for SmartSoft guys to help me fixing an issue

@altacch now I understand the approach suggested. Though, as pointed out also by @barbalberto it requires the designer to explicitly think and model the flag reset logic ("It shall also be cleared eventually, by who and when?") With this in mind, please consider what I propose below.
@barbalberto and @miccol please help us understand what would the SequenceStart would allow you to solve in this specific example. Specifically, how did you came to realize that a SequenceStar was needed instead of a plain Sequence?
I claim that from what I see the choice between e.g. Sequence and SequenceStar often depends on design decision subtleties and thus subject to misinterpretation and errors. If we can capture such subtleties with our formal analysis, then we can provide some value out of the framework we are proposing. More in general, starred operators are quite used in practice, therefore it is worth considering them in the formalization.

@StefanoSoffiaUTRC

Specifically, how did you came to realize that a SequenceStar was needed instead of a plain Sequence?

I'l try to explain it by taking 'snapshots' of the BT state in time.
At the beginning:
    <Sequence name="seq0001">
      <Action ID="Go_to_location_1" />   First tick -> retuns running
      <Action ID="Go_to_location_2" />   Not ticked yet
      <Action ID="Go_to_location_3" />   Not ticked yet
    </Sequence>

The robot moves and reaches location_1
<Sequence name="seq0001">
  <Action ID="Go_to_location_1" />   Robot arrives in location1 -> return Success
  <Action ID="Go_to_location_2" />   First tick -> returns running  ->  robot starts
                         moving  toward location2 -> therefore **away** from location 1
  <Action ID="Go_to_location_3" />   Not ticked yet
</Sequence>

At a certain point
<Sequence name="seq0001">
  <Action ID="Go_to_location_1" />   Robot moved away from location1 -> returns Failure ->
                             got ticked again and halts Go_to_location_2
  <Action ID="Go_to_location_2" />  Halted
  <Action ID="Go_to_location_3" />   Not ticked yet
</Sequence>

So as soon as the robot moves from location_1 to location_2 it comes back.
It is not possible that both "Go_to_location_1" and "Go_to_location_2" are success at the same time because the robot is either in location_1 or location_2.
The ratio is that as long as a "Go_to_location" is ticked, it brings the robot there, hence it prevents the robot to go elsewhere.

In the sequence star node, the memory is inside the node. If we go with the translation "sequence+fallback+memory nodes" we need a way to store those memory nodes somewhere.

Let me point out a subtlety I was thinking about in the last few days.
With the current interpreter, as pointed out by @barbalberto , the only way to have a persistent state between ticks is to implement an ad-hoc Condition node (e.g. Location1_done). Now, the code in this node can do two very different things:

check if the skill Go_to_location1 is done and always return Success from that point on,
check directly the physical state of the robot each time it is called.

Now if we introduce nodes with memory inside the interpreter, we add another "source" of state in a BT execution. Since the BT interpreter is oblivious to the physical state of the robot, this new source of state can only be of the first (i.e., "cache") kind. I am wondering if this can cause problems and, if so, how to avoid them.

Just to clarify, I'm not suggesting to have generic nodes (leaves) with memory, only to have the SequenceStar.
With @miccol we are building the black-board, so that conditions can store their memory in. Better, the skills can write into the black-board, the BT can tick a condition and get a fresh value from the blackboard.
At first we can emulate the Star with "sequence+fallback+condition+blackboard" but it is cumbersome, not efficient and difficult to maintain.
At the end, a generic condition ("is_the_robot_happy?") will need either a specialized skill or the blackboard, but the "internal logic of BT", like SequenceStar shall not rely on external process as the black-board.

@barbalberto your example is clear. Moreover, @miccol BT engine supports starred operators, and Davide Faconti's Groot supports them as well.
I understand that as part of CARVE there is a trade-off between the number of features supported by the interpreter and the formality of the approach. @altacch let us try to reason together about what would be needed in COQ to implement these nodes. Last week I pushed a reference implementation in SMV (the model checker) for both the basic and reactive BT semantics. I'll try to push a simplified proof-of-concept in COQ asap.

@altacch please checkout this branch.
I added a BT_binary_with_memory to experiment our ideas.
Currently there is a lot of repetition in the tick function. Not sure about how to remove it, maybe you can continue from here.

@altacch and @barbalberto, I would like to write unit tests to exercise the Caml code extracted from COQ. What do you suggest?
E.g. to test the reference SMV I created the smv/run_all_verification.py which includes the specification of the unit tests and exercises them by invoking the external executable nuXmv and checking its output.

I think we should make our experiments directly on the arbitrary-branching implementation of BTs, since all the infrastructure (tests included) is geared towards this case.
Sorry for not being of help at the moment; I may be able to allocate some time to the problem tomorrow.


fix: auto-add #{sn} to the name of nft

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[x] Feature

Needs QA check

@kodadot/qa-guild please review

Context

[x] Closes #8100

[x] Check if the name contain #{sn}, if not, we will add for it.

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Screenshot 📸

[x] My fix has changed UI

landing

collection

gallery items

It's blocked by some changes on indexer side
We should add sn to the tokenEntityList entity

Copilot Summary

🤖[deprecated] Generated by Copilot at ceb004a
Added support for displaying NFT serial numbers as suffixes to their names in the UI. Refactored and moved NFT formatting logic to composables/useNft.ts and updated GraphQL queries to fetch sn field from Subsquid API.

🤖[deprecated] Generated by Copilot at ceb004a

Sing, O Muse, of the skillful coder who devised
A clever way to show the serial number of NFTs
By adding sn to the GraphQL query that retrieves
The latest events from the Subsquid API of Kusama.

It's blocked by some changes on indexer side

We should add sn to the tokenEntityList entity
quoting  @vikiival from https://github.com/kodadot/nft-gallery/issues/7462#issuecomment-1744571996

sn - for sort

This filter does not make sense imo as there is nothing I can represent as serial number.

This filter does not make sense imo as there is nothing I can represent as serial number.

The only thing that probably makes sense to represent is amount of nfts

Looks the tests are failing for this one

Looks the tests are failing for this one

reason:
red dot is where it clicks to access collection:

unrelated i suppose, but why it failed only now? hehe

@Jarsen136 inside profile:

@Jarsen136 inside profile:

It's also blocked by change on the  tokenEntityList entity

5. gallery items
It's blocked by some changes on indexer side
We should add sn to the tokenEntityList entity

Looks the tests are failing for this one

reason: red dot is where it clicks to access collection:
unrelated i suppose, but why it failed only now? hehe will fix in a small PR

The width of the nft name changed because we added #{sn} on the end. I bet that's why the red dot could not sit in the same position as before. : ) Thank you for fixing the test.

thanks!
pay 20 usd

😍 Perfect, I’ve sent the payout
💵 $20 @ 5.14 USD/DOT ~ 3.891 $DOT
🧗 16SjUbGKSdjCdWTy3NNT3JxbRVGGqD4mwkHpc6BD9U2Rp29Z
🔗 0x93d7bc89aa76151d56d313afa6a1b0bb878e19562a3cdd66fcee812c7618a6b7
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


0.40.8 release is missing assets

0.40.8 release is missing assets

Thanks for the report! This should be resolved now.


workaround for left recursion

For a grammar rule like follows:
expression = textual_expression;

textual_expression = literal
  / function_invocation;

// lot of lines follows...(shortened for brevity)

function_invocation = expression parameters;

parameters = .

The function invocation is defined that way...While generating the parser it errors out stating possible infinite loop. Is there a workaround I can implement here? (There are several rules like this in specification I am implementing).
PS: WIP grammar file

Change textual_expression and function_invocation, adding an adtitonal rule like so:
textual_expression = primary_expression
  / function_invocation;

primary_expression = literal;

function_invocation = primary_expression parameters;

But, function_invocation is not literal followed by parameters. Its expression followed by parameters. The error I got earlier was something like below:
Possible infinite loop when parsing (left recursion: expression -> textual_expression -> function_invocation -> expression)

You're getting the left recursion error because PEG.js sees that function_invocation starts with expression (that refers to textual_expression), but this rule defines function_invocation as a possible parsing path, which can cause an infinite loop, hence the left recursion error.
The grammar change which I suggested basically stops the error while also leaving you the option to update textual_expression (hence expression) without causing another possible left recursion error.

Thanks for the suggestion. However, I am a bit confused. According to the specification textual expression is a lot more complex.
2. textual expression =
	a. for expression | if expression | quantified expression |
	b. disjunction |
	c. conjunction |
	d. comparison |
	e. arithmetic expression |
	f. instance of |
	g. path expression | filter expression | function invocation |
	h. literal | simple positive unary test | name | "(" , textual expression , ")" ;

The grammar I wrote was WIP. Eventually I have to write stuff to meet the above rules. There is a precedence defined, which was why literal came before function invocation
How should I write primary_expression given the above facts?
PS: Complete specification grammar is linked to here

I would suggest putting everything under 2-h in primary_expression (looking at the spec agian, a better name would be left_expression maybe?).
For a better example to follow, look at the following rules in EdgeVerve/feel/src/feel.pegjs

TextualExpression
TxtExpi
LeftExph
FunctionInvocation

Following the specs is great (makes for consistent software), but you have to fill in the little gaps that can crop up depending on the software you're using or anything left open for implementers of a spec.

Thanks. I got an idea of what to do. However, the way that grammar was written was what inspired me to ask such a question in the first place. :)


Documentation Questions, pyproject.toml and tests

I'm a bit new to pyproject.toml. I'm reading more and more.
I would love to see a short introduction on how a test environment for dephell itself is set up.
What I did now was following an actual travis build.
Next to that, what's the plan for typing support?
I see there's already lot's of support for it, it just doesn't seem implemented all the way through/
For example issue #326 would have been caught with it.

Further more I try to run mypy through dephell, but I'm getting this error.
What do I need to do to fix this?
dephell venv run --env=pytest typing
WARNING executable is not found in venv, trying to install... (executable=typing)
INFO build dependencies graph...
INFO installation... (executable=/home/roland/.local/share/dephell/venvs/dephell-tr3F/pytest/bin/python, packages=1)
Requirement already satisfied: typing==<IP_ADDRESS> in /home/roland/.local/share/dephell/venvs/dephell-tr3F/pytest/lib/python3.8/site-packages (from -r /tmp/tmp9z02q8nz/requirements.txt (line 1)) (<IP_ADDRESS>)
INFO installed
ERROR package installed, but executable is not found

I got to run with:
dephell venv create --env typing
dephell deps install --env typing
dephell venv run --env typing

I would love to see a short introduction on how a test environment for dephell itself is set up.

https://dephell.readthedocs.io/cmd-generate-travis.html
https://github.com/dephell/dephell/blob/master/pyproject.toml

dephell venv run --env=pytest typing

As I see, you realised what's wrong here. You're trying to execute typing in pytest env. However, you need typing env:
dephell venv run --env=typing


run as non-root user

The ability to run as root is not going to be available to us in some cases, so let's not rely on that.
The changes to pkg/validator/* are for moving our internal webhook port to a non-restricted port (8443). So we don't need to be root to listen there. The external port for the service will still be 443 but that's fine.
The rest of the changes are for actually running as non-root. They broadly involve these things:

Remove the old build.sh and docker_build.sh scripts since they aren't used.

Remove the debug target in the Makefile and the (commented-out) debug stuff in the Dockerfile. Those can probably be re-instituted in some form if we want, but Don will probably have to help figure that out and test it.

In the Dockerfile, set up to run as a non-root user, and store our files in that user's home directory. There's a twist here: on OpenShift we won't know a priori what user ID will be used. I've made the changes in Dockerfile and in the associated entrypoint script to try to account for that in the way recommended by operator-sdk, tweaked to support our "redeploy" shenanigans, but I haven't tested this on OpenShift yet. But it at least works on non-OpenShift and may leave less work for us to do if/when we tackle OpenShift support for real. It's also generally nice to be more congruent with what the operator-sdk does by default.

Because the (potentially necessary) entrypoint actions are now fairly complicated, it seems like the best approach is to let the Dockerfile's declared entrypoint command handle things (by running the necessary script) and never override it in the deployment YAML. So I removed the command+args from operator.yaml and deployment-prebuilt.yaml.

Change the definition of configcliSrcFile in kubedirectorcluster/types.go to account for configcli.tgz moving to the kubedirector user's home directory.

Change the "redeploy" target of the Makefile to account for the new locations and permissions of files.

Sometimes it's necessary to run privileged commands, e.g. the mount command for FsMounts. How are you going to accommodate that? Should this PR include changes to give the kubedirector user some kind of sudo access?

Any privileged commands like that should happen in some other utility pod (e.g. a daemonset) rather than inside the kubedirector pod. If a particular K8s deployment is just dead set against allowing any root-user pods then I think it's a somewhat better story to say they don't get particular feature X rather than that they can't use kubedirector at all. We can talk separately in email or whatever though if you have further concerns along those lines.

I talked to Swami a bit more about that... perhaps a good solution for such daemonsets would be to have them run as non-root too, and specify a limited set of sudo commands that they are allowed to do. That would limit concerns about root breakout from the container. I know you're thinking about this in the context of the fork you're working on, and I'd say that's a subsequent-phase (but before final shipping) sort of concern rather than a showstopper for initial implementation.

Since you said that we don't need to address the FsMount issue in the initial implementation can I assume these non-root user changes won't be merged into kubedirector-plus until the issue is addressed?
The reason I ask is that I don't know for sure but I would be surprised if these changes don't prevent the kubedirector user from deploying a privileged daemonset as it is currently implemented.

Let's talk in email/skype.


IAM Grants still not quite right

The IAM policy statement support is still not quite right. Right now, there are 3 grant methods:

Grant.addToPrincipal().
Grant.addToPrincipalOrResource() -- note: OR
Grant.addToPrincipalAndResource()-- note: AND

And some of the mechanics are made possible by IPrincipal.addToPolicy(): boolean, which is supposed to return true or false based on whether or not it added the policy statement. The thinking here was that we can represent principals like myResource.grantWrite(new ServicePrincipal('events.amazonaws.com')), and because its addToPolicy() would return false, the statement would be added to myResources resource policy.
Behavior is supposedly:

Identity-based policies and resource-based policies are both permissions policies and are evaluated together. [...] If at least one policy statement allows the action in the request, the request is allowed. It doesn't matter whether the Allow is in the identity-based policy or the resource-based policy.

Important

This logic applies only when the request is made within a single AWS account. For requests made from one account to another, the requester in Account A must have an identity-based policy that allows them to make a request to the resource in Account B.

Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_identity-vs-resource.html
Grant.addToPrincipalOrResource() tries to do the right thing, but mostly does so by accident. If it can't add the statement to the principal, it will add it to the resource.

Works for created IAM roles: statement gets added to the role.
Works for service principals: statement gets added to the resource (adding a cross-account trust), and we'll assume that the service principal already has the appropriate permissions on their end, which is probably true for supported AWS service interactions.
Works for imported IAM role in same account (before application of https://github.com/awslabs/aws-cdk/pull/2805, and modulo some bugs), statement gets added to resource which is good enough for "same account" access
Does not work for cross-account created IAM roles (inside the same CDK app): the statement will be added to the role policy, but should also be added to the resource policy to support cross-account access.

The latter case is probably not exercised a lot, and if due to a user's extensive experience with manual IAM configuration they weren't expecting it to work just as magically as the rest of the CDK, they would just add the resource permissions by hand and be none the wiser that we have a bug here. But I would argue that we have a bug nonetheless.
The fact is, the trigger for automatically adding to the resource policy is wrong. The current trigger is: "did we failed to add permissions to the identity?", but the trigger should be: "does the principal live in another account OR did we fail to add permissions?".
Then there is Grant.addToPrincipalAndResource() which is yet another crazy beast, and mostly designed to fit the use case of KMS. By default, most (all?) resources exhibit the "inside the same account a statement on either resource or identity is enough" rule, but KMS keys do not. They seem to require explicit statements on the key for every action.

@skinny85 something to be aware of when implementing cross-account CodePipeline


fix: build frontend image

@kartikpersistent why close the PR and create a new commit?

https://github.com/neo4j-labs/llm-graph-builder/commit/b80a16439defde0f6dcf38aa4c9cb63d92f03a09
This commit has the same changes, is PR not welcomed in this project?

We generally not prefer to raise a pr directly to main first it can be raised to DEV then to stage and then to main because it was a critical issue I directly pushed hope you understand

If you find any issues in main/DEV feel free to raise to PR it is highly recommend


web-socket-ruby doesn't provide socket policy file at port 843

The README says that web-socket-ruby provides a socket policy file at port 843.
After not being able to see it listening on 843 (netstat -lntp), I grepped the source, but couldn't find 841 at all.
Am I missing something here?
Thanks,
Chris.

hello chrisdew! I downloaded the web-socket-js directory and web-socket-ruby directory. I want to run the demo. I ran sample Web Socket server: ruby web-socket-ruby/samples/echo_server.rb example.com 10081. Then , I run the Nginx web Server and opened sample.html in the chrome browser. But I can't connect to the Web Socket server. I don't know how i can run it.
Waiting for your help! Thanks

Thanks ! I solved it myself. I have installed Win7 OS in my compute. Then I installed the VMware Workstation  in the win7. And then I installed Linux OS in the  VMware Workstation. So,  use the VMware IP to set the hostname. $ ruby web-socket-ruby/samples/echo_server.rb IP 10081. And  ws://IP:10081 in sample.html. It's OK!


Dependencies broken

Bundler could not find compatible versions for gem "stripe":
  In snapshot (Gemfile.lock):
    stripe (= 1.25.0)

  In Gemfile:
    stripe-ruby-mock (~> 2.1.1) ruby depends on
      stripe (= 1.20.1) ruby

    stripe (>= 0) ruby

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

... running bundle update things fix by backporting Stripe (which is not what i want):

-    stripe (1.25.0)
+    stripe (1.20.1)

Would be desiderable to have that depend. in sync

would be desiderable to have that dep. in sync

@lgs yes, gem is not supported newest version of Stripe yet. But we going to do that.


Better Config Validation

Provide an explicit check verb for config validation, eliminating "required" parameters that we don't need if we're simply dumping configuration.
Fixes #2

Pull Request Test Coverage Report for Build 6

22 of 44 (50.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.8%) to 65.289%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Harbor.Tagd/Program.cs
0
22
0.0%

Totals

Change from base Build 4:
-1.8%

Covered Lines:
237

Relevant Lines:
363

💛  - Coveralls

I'm not concerned about the coverage changes. I'll make a separate PR for improved coverage across the board.


MS0105: reload current scene function.

add a new file menu element: Reload

this should close everything opened and re-open them again.

add toolbar icon for the above.
add keyboard short cut F5
add a popup menu to the model
close all open files after saving their paths in a temp file
reload them again.

Notes:

when opening the main application, two text files are created

OpenSimQtLog_DateTime.txt:  anything happened in the application should be logged in this file.
vsCommand: openmodel path

It should also direct the outputto the messages window.

OpenSim.vs:

the first line is the date and time
contains only the opened components (for now the model paths).

Notice that all IO and critical code should be placed in error handling block that produces reasonable error in the application output and the application log.

HI!
Check this milestone in the latest master commit
the pop up is added but do you want to implement the functions of the popup on this milestone?

Well done!

the pop up is added but do you want to implement the functions of the popup on this milestone?

Is it complicated? I thought you just call the reload function.
I will test the code and give feedback if need.

Just tested it, everything works. If calling the reload function from the popup menu is complicated, you may ignore it for now and close the issue.

call the reload function
it is all the functions like(add Prob,Add Marker,Display, Toggle Parent Frame ...)it is not complicated but it require the work from the Visualizer functions Milestone like linking the visualizer and Navigator  and Navigator element popup menus ...

For the reload function on the popup menu you want to reload just one Model from the model Menu?

Ok, I understand what is the problem now. The reload function should reload only one object, when it is called from the menu or F5, it should reload everything,
Another approach is  something like this:
                reload( ....,std::string object_name ){
                try{
                if object_name is in the navigator tree:
                   reload this object
                } else{
                  reload everything
                }
               }

i did not get it.
The Current Reload Action reload everything when it called from the file that you described OpenSim.vs
For the New Reload Function on the popup menu you want it to reload just the Selected Model ?
Notice that all the model  are present in the Navigator Tree

It ok, you may ignore this for now. This issue is now closed.


Changelog title empty for 0.2.1

Reported by @hzsweers
App
Version: 0.2.1-10-g720c6d4-dev
Version code: 987

Device details
Make: Google
Model: Pixel 2
Resolution: 1794x1080
Density: 420dpi (420)
Release: 8.1.0
API: 27

Logs
No logs provided

Fixed


Remove metadata argument for jpg in make_figs

Metadata argument was not supported for this filetype, was throwing error. CDC wants a minor release for this. I'm going to put in one more annoying behavior fix before I do that.

@alanlujan91 This is a one line bugfix that Chris wanted for #1375 , turning off an illegal argument for jpg in make_figs. He wants a minor release for this (for HAFiscal, I think), so I'm going to do one more little thing (repr behavior for IndShockConsumerType) and then release 0.14.1. Review/merge when you have time.

Let me see if I can add a quick test after I grab lunch.


Images properties not being set by extension

This is an issue in VS Mac, but opening for tracking.

[ ] report upstream and link to this ticket

fixed in  https://github.com/microsoft/FigmaSharp/pull/333


RootMeanSquaredError raises TypeError: loop of ufunc does not support argument 0 of type int which has no callable sqrt method when Nullable types are used

Similar to https://github.com/alteryx/evalml/issues/3919 and https://github.com/alteryx/evalml/issues/3920, we are seeing an error when Nullable types are forcibly used in AutomlSearch that comes from the conversion to the object dtype when converting data with nullable pandas dtypes to numpy arrays.
In this case, it is because metrics.mean_squared_error uses np.sqrt under the hood, which will raise TypeError: loop of ufunc does not support argument 0 of type int which has no callable sqrt method when data with an object dtype is passed in.
This can be reproduced as follows:
    import woodwork as ww

    X, y = X_y_binary
    y_n = ww.init_series(y, logical_type="IntegerNullable")
    root_obj = RootMeanSquaredError()
    root_obj.objective_function(y_n, y_n)

If we handle nullable types for all objective functions in #3919, though, and not just for validate_data, we shouldn't need any additional handling for this error to go away.
Note: This can currently be seen in AutoMLSearch, despite the presence of the replace nullable types component. See https://github.com/alteryx/evalml/issues/3739

many other objectives have issues with nullable types - not all of them below but just to show:

MeanSquaredLogError - TypeError: loop of ufunc does not support argument 0 of type bool which has no callable log1p method
RootMeanSquaredLogError - TypeError: loop of ufunc does not support argument 0 of type bool which has no callable log1p method
RootMeanSquaredError - TypeError: loop of ufunc does not support argument 0 of type bool which has no callable log1p method
evalml.objectives.standard_metrics.MaxError - *** TypeError: objective_function() missing 1 required positional argument: ‘y_predicted’
<evalml.objectives.standard_metrics.MAPE - ttributeError: ‘FloatingArray' object has no attribute 'mean’
MCCMulticlass - ValueError: unknown is not supported
LogLossMulticlass - ValueError: Unknown label type: (0     1
AUCWeighted - ValueError: unknown format is not supported
AUCMacro - ValueError: unknown format is not supported
AUCMicro - ValueError: unknown format is not supported
RecallWeighted - ValueError: unknown is not supported
RecallMacro - ValueError: unknown is not supported
RecallMicro - ValueError: unknown is not supported
PrecisionWeighted - ValueError: unknown is not supported
PrecisionMacro  -
PrecisionMicro
F1Weighted - ValueError: unknown is not supported
F1Macro
F1Micro
.BalancedAccuracyMulticlas - ValueError: unknown is not supported
AccuracyMulticlass - ValueError: unknown is not supported
<evalml.objectives.standard_metrics.MCCBinary
LogLossBinary ValueError: Unknown label type: (0      True
Gini - *** ValueError: unknown format is not supported
AUC ValueError: unknown is not supported
Recall  ValueError: unknown is not supported
Precision
F1
BalancedAccuracyBinary

A decent number of these may be fixed by updating to sklearn 1.2.1

Closing after https://github.com/alteryx/evalml/pull/3983/files upgraded to sklearn 1.2.1 - all remaining incompatibilities listed in https://github.com/alteryx/evalml/issues/3992


merging keytar updates [v0]

KeyTar APIs are now async. Cherry-pick from master.

No product impact right? Only cli changes?

CLI only, nothing a user would see. keytar 4+ does provide pre-built binaries so ''npm install'' should not trigger node-gyp anymore.

Looks good.


Update opensergo docs

Fixed some spelling detail errors

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

cc @sczyh30


Warning: Cannot update a component (StaffLogin) while rendering a different component (Context.Consumer).

Warning: Cannot update a component (StaffLogin) while rendering a different component (Context.Consumer).
Warning: Cannot update a component (`StaffLogin`) while rendering a different component (`Context.Consumer`). To locate the bad setState() call inside `Context.Consumer`, follow the stack trace as described in https://fb.me/setstate-in-render
    in x (created by StaffLogin)
    in StaffLogin (created by LoginStaff)
    in div (created by styled.div)
    in styled.div (created by StyledCard)
    in StyledCard (created by LoginStaff)
    in div (created by styled.div)
    in styled.div (created by LoginStaff)
    in div (created by styled.div)
    in styled.div (created by StyledGrid)
    in StyledGrid (created by LoginStaff)
    in div (created by LoginStaff)
    in LoginStaff (created by Context.Consumer)
    in Route (created by MainRouting)
    in Switch (created by MainRouting)
    in MainRouting (created by App)
    in StoreContextProvider (created by App)
    in Be (created by App)
    in Router (created by App)
    in div (created by App)
    in App

Have a look at:
https://github.com/joegasewicz/react-google-oauth2.0/blob/51faf7046a65b24f6c96355041c882110358e46d/src/components.tsx#L226
https://github.com/joegasewicz/react-google-oauth2.0/blob/51faf7046a65b24f6c96355041c882110358e46d/src/components.tsx#L260


Submit results and obtain image to share

After visiting the website and performing a speedtest, users are offered links to the results and a PNG image they can share containing the results of the test. It would be awesome if speed-test could provide this information, perhaps through a flag.

Duplicate of #18 and #12.


Add a div to control the style of the layer interactor.

Need a way to control the text value of the hover display.

#991be03


Daily update

Automated changes by create-pull-request GitHub action

Build failed because of:
No cached entry, and Spireon, Inc. has issues with logo: spireon_inc.svg, Error in parsing SVG: Unexpected close tag
Line: 5
Column: 7
Char: >
Empty twitter for CSIRO/DATA 61: https://twitter.com/CSIROnews
Empty twitter for TYNYBAY Inc: https://twitter.com/tynybayinc
Empty twitter for Tectonic Labs Ltd.: https://twitter.com/cloud_ridge
Empty twitter for eBaoTech International Pte Ltd: https://twitter.com/Ebaotech
Empty twitter for Truepic, Inc.: https://twitter.com/truepicinc
Empty twitter for China Telecommunications Corporation: https://twitter.com/chinatelecom1
Empty twitter for Apple: https://twitter.com/Apple
Item Spireon, Inc. has no image_data


Singularity Hub Build

heyo! Apologies for taking some time to check out the container you were building - I had a bug in the finish build flow so that the log never returned. I just finished the build and am taking a look, and it looks like your build ran out of memory. Could you tell me the kind of host / environment that the build is intended for? Was the error when you were testing the container? Here is your log:
https://www.doc.fish/containers/38/log

Also, you should know that the folder names aren't meaningful for the collection - since each of your files is called Singularity only one container will be built, and it's the most recent of the three. I'd recommend you either maintain separate collections, or to serve (different) containers in the same, the spec file needs to be named to distinguish a tag. Eg:
Singularity.samtools --> shub://qbicsoftware/qbic-containers:samtools
Singularity.multiqc --> shub://qbicsoftware/qbic-containers:multiqc

Hi Vanessa! No , the container built locally without issues (Singularity 2.4).
I'll update the containers to have the name included, that should help! Thanks for the hint!

The host I intended to run this is a HPC environment (our local cluster). I guess it could be, that the megSAP pipeline is too big for containerization (it pulls ~30GB of reference panel data unfortunately). Maybe I'll try to keep that outside of the actual container for update reasons....

ok cool! Yes that's rather big, haha. if you want to try another strategy that would be great, to avoid those fat containers :P


how to install ipfs on respberry pi3

how to install ipfs on respberry pi3? Is tt possible to install ipfs desktop on respberry pi? if yes how?

(closing as you've asked on discuss.ipfs.io).


⚠ Bofrost.lu has degraded performance

In 933ecee, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1021 ms

Resolved: Bofrost.lu performance has improved in cb25b48.


How does one install Kuberhealthy without helm?

We don't use Helm but do use Kustomize.

We maintain a static yaml file for anyone not using Helm.  This file gets regenerated automatically by a github actions build bot.


Add cloudEvents and knative extensions

Fixes #3459

@lburgazzoli could you check this PR?
Is there a way to have more integration tests. I wonder if there's something we could use to simulate Knative, or do some mock.

The vert.x native error seems to be related to this change I guess : https://github.com/vert-x3/vertx-web/commit/8dda3dec91648eddae01455b8a94cc1c0e25c864

@jamesnetherton @lburgazzoli  Is deleting the reflective classes mandatory for this PR?

Let me know if something needed to explain or improve

@jamesnetherton @lburgazzoli Is deleting the reflective classes mandatory for this PR?

I think it's ok to have the reflective config initially. But we should try to remove it in a future release if possible.

@jamesnetherton @lburgazzoli Is deleting the reflective classes mandatory for this PR?

I think it's ok to have the reflective config initially. But we should try to remove it in a future release if possible.

I can do that for next re

@jamesnetherton @lburgazzoli Is deleting the reflective classes mandatory for this PR?

I think it's ok to have the reflective config initially. But we should try to remove it in a future release if possible.

Okay I'll open an issue and add it to my tasks if this is approved for next release :)


Server sigalgs fix

Checklist

[x] documentation is added or updated
[x] tests are added or updated
[x] CLA is signed

Description of change

This fixes a bug where if we configured client authentication signature algorithms on a server it would wrongly use them when deciding which signing algorithm to use. This affects master, 1.1.0 and 1.0.2 which will need a separate PR as the code is significantly different.
You can reproduce this with:
openssl s_server -client_sigalgs ECDSA+SHA256
openssl s_client -sigalgs RSA+SHA256

the handshake will fail.

Update: moved the test to the simple test: so it can be backported to 1.1.0 more easily.

Ah it looks like this applies cleanly to 1.1.0 (it wont for 1.0.2) OK to backport?

sorry i wasn't clear; yes.

Erk... no it doesn't new PRs coming up for other branches.


Refactor generate_unique_slug

I refactored the clean slug method because it was buggy for new objects.
The main changes include:
- the region and language parameter for checking for existing slugs come from the form object now instead of the form object instance
- the new property translation.foreign_object allows us to get the meta object for different content types, e.g. page_translation.page or event_translation.event
This changes also fixed the issue that POIs could not be created.
Fixes #262
Fixes #260

@ulliholtgrave @svenseeberg Thanks for your reviews, can you have a look at my recent changes? :slightly_smiling_face:


New Provider Bunny (bunny.net)

Hi there,
I need bunny.net DNS support for caddy and created a corresponding provider using the template, while basing tests and structure on the hetzner package. Tests are OK.
I prepared a repository for transport

BUNNY_TEST_API_KEY="***" BUNNY_TEST_ZONE="***.com" go test ./... -v
=== RUN   Test_AppendRecords
--- PASS: Test_AppendRecords (7.43s)
=== RUN   Test_DeleteRecords
--- PASS: Test_DeleteRecords (4.00s)
=== RUN   Test_GetRecords
--- PASS: Test_GetRecords (3.85s)
=== RUN   Test_SetRecords
--- PASS: Test_SetRecords (7.96s)
PASS
ok      github.com/rewilok/libdnsbunny  23.510s

Thank you!


How to add descriptions(SEO) to each pages?

Description of home page(/) and post five is same.
How to add description to each pages?

If you look at the /templates/post, you'll find the SEO components being used.
https://github.com/justinformentin/gatsby-v2-tutorial-starter/blob/6bcb8e47f330de1ac95a46976422add5a2a2923a/src/templates/post.jsx
<SEO         title={title}         description={description || excerpt || ' '} ...
And you can change the description there either programmatically or by hard coding it.

Thank you very much justin, it worked!


i want to add eyeglasses boundary from stylegan ffhq .

i want to add eyeglasses boundary from interfaceGAN stylegan ffhq w or wp. how can i do with suggest distance

We used the directions from this paper: https://github.com/mit-han-lab/anycost-gan
I think they have a direction for eyeglasses as well, but you'll have to extract it from their file and save it into a .pt vector like the ones we use here.
Our model is using StyleGAN2, make sure you use InterfaceGAN directions appropriate for that.


Fix swift concurrency flag

Fix swift concurrency flag
:recycle: Current situation & Problem
This PR fixes the swift concurrency flag.
:gear: Release Notes
Add a bullet point list summary of the feature and possible migration guides if this is a breaking change so this section can be added to the release notes.
Include code snippets that provide examples of the feature implemented or links to the documentation if it appends or changes the public interface.
:books: Documentation
Please ensure that you properly document any additions in conformance to Spezi Documentation Guide.
You can use this section to describe your solution, but we encourage contributors to document your reasoning and changes using in-line documentation.
:white_check_mark: Testing
Please ensure that the PR meets the testing requirements set by CodeCov and that new functionality is appropriately tested.
This section describes important information about the tests and why some elements might not be testable.
:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[ ] I agree to follow the Code of Conduct and Contributing Guidelines.

Thank you for looking into this @Supereg!

@PSchmiedmayer the Xcode 15 toolchain still triggers some concurrency warnings that are not triggered with the Xcode 16 beta 3 toolchain (e.g., Logger has now Sendable conformance with the latest SDKs). Should we aim to host some Xcode 16 runners soon? This could also be useful to enable Swift 6 language mode in which Concurrency warnings are treated as errors which would make efforts in https://github.com/StanfordSpezi/.github/pull/50 to be non-essential.
We could either move with all runners to the beta toolchain for the Spezi Org. Seems relatively stable by now and is probably the easiest to maintain. Otherwise, we could allocate some dedicated Swift 6 runners if we have the capacity.
Let me know what you think.


WIP: node 18 and webpack 5 support

Still lots to test and fix, but here's a start that makes it possible to start volto without errors with webpack 5.
(Targeting a future major release of volto)

https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#webpack4-support-discontinued one more reason to push for this

Feedback
I tested it out with Node 18.14.0:

no problems in Vanilla Volto
yalc'd the PR in our latest project, all good

The idea is to release it with Volto 17, I'd merge it and start an alpha stage.
@plone/volto-team it would be great if you try it out also in your projects. Here are the detailed instructions.
nvm use 18
npm -g i yalc

in your local Volto checkout:
cd volto
git co webpack-5
yalc publish

in your project:
yalc add @plone/volto --no-pure
yarn
yarn start

after testing:
yalc remove --all

@tiberiuichim since you wrote the webpack plugins it would be great if you could take a second look at them, to make sure that they are migrated correctly.

@davisagli waiting for your last polishing and review so we can mark it as "ready for review"

@sneridagh I think this is ready for review. Note that in order to merge it, we need to update which checks are required for branch protection, since the checks now run with node 16 and 18 instead of 14 and 16.


Native error codes are masked in PowerShell pipelines on Unix-like platforms

On Unix-like platforms, with SIGPIPE signals being ignored, as in Ruby, writing to a broken pipe (a pipe whose reader process has since terminated) returns standard error code EPIPE.
However, it seems that in PowerShell - unlike in POSIX-like shells such as bash - the error code is not relayed to the writing process.
Steps to reproduce
Write 100,000 lines via Ruby, but cause the pipe to break via head -n 1 exiting after having received the 1st input line:
ruby -e '(1..1e5).each do |i| puts i end' | head -n 1

Expected behavior
1
-e:1:in `write': Broken pipe @ io_write - <STDOUT> (Errno::EPIPE)
	from -e:1:in `puts'
	from -e:1:in `puts'
	from -e:1:in `block in <main>'
	from -e:1:in `each'
	from -e:1:in `<main>'

Actual behavior
1

That is, the Ruby code never saw the EPIPE standard error code that results from writing to a broken pipe while SIGPIPE signals are being ignored.
PowerShell Core v6.2.0-preview.2 on macOS 10.14.1
PowerShell Core v6.2.0-preview.2 on Ubuntu 18.04.1 LTS

For reference https://github.com/PowerShell/PowerShell/pull/2450

Seems the issue could be fixed with #8420.


Upload to YouTube

Hi there,
I'm constantly getting a 404 error while trying to upload a file to YouTube via their REST API. Since the URI is definitely exisiting (I checked in the browser), I suppose that their might be some troubles with (ultra) long URIs. The URIslook like this: https://uploads.gdata.youtube.com/action/FormDataUpload/AIwbFARgUGqjIzmFQ5SRyz8NGKpmQDNfWx5Ub3el2pO4Zh2lDu4xcNP2AwLmoDkP26LpLGZpFpRnnJAokbl_3k6Mpo-l3_h2jsqPrU5o54RRoW4stvUqh9A.
Are their any suggestions how to solve that problem?
Regards
Maetty
PS.: Hut ab! Hat sich das Studium in Furtwangen bezahlt gemacht. ;)

@blueimp iirc IIS recently introduced a limit on URL length.  I believe it is something like 1000 characters, due to the hashtable attacks that have recently gained attention among the varied web development languages (PHP 5.3.9 will be introducing a maximum _REQUEST var cap itself, as well)

Thanks for the clarification about current safe URL lengths, Damien.
Though I do think this is unrelated to maettyhawk's issue, as his example URL is under 200 characters.
And I really hope they'll implement better fixes (e.g. randomized hash functions) than just limiting the requests further, which only narrows the attack vector.
Here's a good summary of the hash tables issue:
http://cryptanalysis.eu/blog/2011/12/28/effective-dos-attacks-against-web-application-plattforms-hashdos/

Thanks a lot for your detailed explanation!!!
I know this is off-topic in terms of the initial topic of this issue, but is it also possible to get the progress-handler to work with the send API? If I bind it to $("#fileupload"), it only gets fired once right before the "fileuploaddone"-event.
PS.: Da hast du natürlich recht, mir geht's im Endeffekt nicht anders... Web-Entwicklung war nicht gerade das Steckenpferd der HFU.

There's another issue I'm sorry to bother you with... YouTube redirects to another URI when the upload is successful. While using the send API, I always get "200" (success) as a response without any other additional data. By using a pure HTML form solution sending my data directly to the YouTube upload URI, I will be redirected to an URI I added as an additional GET parameter (?nexturl={my_uri}). Is there away to make the file upload widget return the content of the nexturl after the file upload?

The iframe transport doesn't support progress events (other than a manually triggered one when the upload is done).
Unfortunately, since the YouTube API doesn't allow Cross-site XHR uploads, we have to rely on the iframe transport.
The iframe transport should follow redirects automatically. Did you add the nexturl parameter to result.url?
You also need to make sure the redirect points back to the origina of the upload form to allow access to the iframe contents.

I skipped the step of requesting an upload url in your example and did the following (this is an valid token in terms of its structure, but it should be expired in the meanwhile):
$('#fileupload').fileupload({
		forceIframeTransport: true,
		done: function (e, data){
			console.log("DONE", e, data);
			console.log(data.result, data.textStatus, data.jqXHR);
		},
		fail: function (e, data){
			console.log("FAIL", e, data);
			console.log(data.result, data.textStatus, data.jqXHR);
		},
		submit: function (e, data) {
			var that = $(this);
			data.url = "https://uploads.gdata.youtube.com/action/FormDataUpload/AIwbFATQBukiXgQQUC66k3PtUCC7votSP-fq7Oq1Asl9Kw9TbJV4HwVrUWT5hwk98ZDDD-lA2lTy3Uotgw1BgfwTBijds6wwUy63ofZvxZZNeEIU7NRhrYw?nexturl=http://localhost:8080/xyz/videoUpload.jsp";
			data.formData = {token: "AIwbFAQ632FnKyD-YDMBdopBISmcPjIeQKatkZ4CSrw_w3lNsECcpIxsV4WDaX4xHcRCVGb-3eTVo2cgL4QfD9bdJR6Yco3XHuGYuwTtB0QYZb3edwnaNDdfFn_Pf8iueY6SOel5v2enKJnyEXugFXpgopkHfChXjl5bRDFozWLDSvINIOi2fqZt4-iuouIpDCPL8aO-kL4fTHnfJvPSU0RaibPlgsN5U3q76zibS3NR_j4ezk3oMt59bCsvvSnVP8fAjjx7eCWPuS0Wbcm7LebJ8DkXZfFy9fdKp1mp0SWjGyWUdcmZttI4sPh_8yGEDQwNRmsqreqd"};
			that.fileupload('send', data);
			return false;
		}
	});

data.result returns "undefined", the status is "success" and the http code "200".

Thanks a lot! Nexturl and the upload form didn't share the same origin... Now it works perfectly.

Great!
If you like and have the time, please edit the following Wiki page to add some documentation on the server-side implementation details:
https://github.com/blueimp/jQuery-File-Upload/wiki/YouTube

I will!


[BUG] - class CohereEmbeddings was deprecated in LangChain 0.0.30

Description
The class CohereEmbeddings was deprecated in LangChain 0.0.30 and will be removed in 0.3.0. An updated version of the class exists in the langchain-cohere package and should be used instead. To use it run pip install -U langchain-cohere and import as from langchain_cohere import CohereEmbeddings.
GraphRAG dependencies not installed. GraphRAG retriever pipeline will not work properly.
User "admin" already exists
Setting up quick upload event
Running on local URL:  http://<IP_ADDRESS>:7860
Not sure what's wrong with the CoehereEmeddings depreciation? What's the correct model to install?
Reproduction steps
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots
![DESCRIPTION](LINK.png)

Logs
No response
Browsers
No response
OS
No response
Additional information
No response

Hi, this is just a deprecation warning and won't affect Kotaemon functionality. Feel free to raise issue if you have problem using Cohere API for embedding.


⚠ Bofrost.de has degraded performance

In 64ca092, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1488 ms

Resolved: Bofrost.de performance has improved in d1ee064 after 29 minutes.


Relating to multiple principals on the same machine

Enhancement Proposal
Currently, it's not possible to relate the grafana agent subordinate to multiple principals on the same machine. This is something we need to support as it's common in many solutions that deploy to machine substrates.
The suggested way of solving this, is by having each principal contribute a configuration fragment, and then having the snap entrypoint/wrapper concatenate them on the fly at startup.

If a breaking change like the one below was introduced, would that solve the problem in an easier way?

grafana-agent is changing from subordinate charm to machine charm.
grafana-agent can be related with many machine charm apps through cos-agent relation, same cos_agent interface
on any relation change from any related app, it is re-calculating the metrics, logs, traces since those are the different configuration bits per relation.

Rest of /etc/grafana-agent.yaml configuration options are grafana-agent specific so they can be managed by the existing charm configuration options of grafana-agent-operator.

On second thoughts, there is also a need for a check on colocation which is solved when being subordinate. So I do not know but maybe you have a better idea.

Related to https://github.com/canonical/grafana-agent-operator/issues/32


Deep learning Inference C++ example

Hello everyone,
I am currently working on a project that requires implementing deep learning inference in C++, and I'm seeking an example to help me get started.
Thank you,

Why not start with larod Object detection example?

We have a quite new section in the ACAP documentation about computer vision on Axis devices. I hope that can give you a background and point to relevant examples.


"max" operator for Merge and TimeDistributedMerge

Hi,
although keras offers the new LambdaMerge layer I think extending the "regular" Merge and especially the TimeDistributedMerge layer by a "max" mode is a good idea.
Originally, I was interested in a max pooling layer that can pool over the complete input sequence and hence reduces it to a fixed sized vector. This is often done in text classification. However, this is the same as using the TimeDistributedMerge layer with "max" mode.
I am, however, not sure yet if it is sufficient for TimeDistributedMerge to address this issue or if the 1D pooling layers (currently max and average) should offer this functionality as well. The latter would make it semantically more precise.
If you believe that the pooling layers should offer this functionality, too, I can create another pull request with the necessary changes.

I somehow screwed up the history of this merge branch. I will create another pull request when I fixed that. Sorry for that.


where is "product-selection-directive" is defined in solution? How can i customise it??

Please help me out understand the angular directive in catalog module. How can i add a new one like "product-selection-directive"
Thanks.
@thiennn
@fhebel
@sefacan
@hishamco

Hi @amohsyn,
I recently added the possibility to reference "Related Pages" to products, which means that you can simply reference (and reuse) CMS pages on the product details page.
It works like this:

add a new Javascript-file (e.g. src/Modules/SimplCommerce.Module.Catalog/wwwroot/admin/product/page-selection-directive.js), which references the html-part (this was the templateUrl I fixed)
add your new js file to src/Modules/SimplCommerce.Module.Catalog/bundleconfig.json
add the respective html (e.g. src/Modules/SimplCommerce.Module.Catalog/wwwroot/admin/product/page-selection-directive.html)
extend the src/Modules/SimplCommerce.Module.Catalog/Areas/Catalog/Controllers/ProductApiController.cs to serve the gridData needed for your purpose

I hope that helps.
Best regards,
Florian


User authentication fails if user name or password contains character colon ":"

Summary
DefaultClientAuthenticationHandler.authenticateTokenRequest() does not work properly if user name or password contain special characters. For example ":". Based on my specification search the user name and password has to be url encoded.
Actual Behavior
The user with user name containing colon cannot login. The provider returns exception.
Expected Behavior
The user with user name containing colon can be authenticated.
Configuration
Local openid provider.
Version
At least 2.2.x and  2.3.x.
Sample
Test case user credentials:
String userName="my:super:user";
String password ="secret:pwd";
The bug in the source code location:
// line in 32  of org.springframework.security.oauth2.client.token.auth.DefaultClientAuthenticationHandler.authenticateTokenRequest()
case header:
form.remove("client_secret");
headers.add("Authorization",
// original code which does work!
String.format("Basic %s", new String(
Base64.encode(
String.format("%s:%s", resource.getClientId(),
// my fix which works!								clientSecret).getBytes("UTF-8")), "UTF-8")));
String.format("Basic %s", new String(
Base64.encode(
String.format("%s:%s", URLEncoder.encode(resource.getClientId()),
URLEncoder.encode(clientSecret)).getBytes("UTF-8")),											"UTF-8")));
break;

@patrikni
Upon reviewing RFC-7617, it states:

The user-id and password MUST NOT contain any control characters (see
"CTL" in Appendix B.1 of [RFC5234]).

Furthermore, a user-id containing a colon character is invalid, as
the first colon in a user-pass string separates user-id and password
from one another; text after the first colon is part of the password.
User-ids containing colons cannot be encoded in user-pass strings.

I'm going to close this since a user-id containing a colon character is invalid.

user-id containing a colon character is invalid

While that is true it does not apply in this case. RFC-6749 describes the process of converting a client id (which may contain a colon) into a valid Basic auth user-id.

For anybody that encounters this issue. You can work around this by changing the client-authentication-method property of your registration to post.
This sends the client id in a post body instead of basic64 encoded basic authentication header. This means special characters can be used.

For anybody that encounters this issue. You can work around this by changing the client-authentication-method property of your registration to post.
This sends the client id in a post body instead of basic64 encoded basic authentication header. This means special characters can be used.


Loots are displayed as only x1

Major issue I guess.
The loot feed only shows x1 of each loot despite looting stacks

Interesting. Is this from gathering like herbalism? I wasn't seeing this myself. I'm wondering if it's possibly a locale issue 🤔
I'll try to figure out what's going on, thanks!

Not only gathering. First screen are herbs, second is trash from mobs.
Every loot affected and yes I think it's a locale issue

I also wonder if maybe it's related to early access. Do you see this outside of The War Within content?
Either way, I'll look into it as soon as I can!
Thanks for the report 💚

@polki92 give v1.3.3 a try, if you can, once it gets approved on CurseForge / WoWI / Wago. Should be available any minute now 🤞🏼


[SPARK-35655][BUILD] Upgrade HtmlUnit and its related artifacts to 2.50

What changes were proposed in this pull request?

This PR upgrades HtmlUnit and its related artifacts to 2.50.
Why are the changes needed?

We currently uses 2.40 but 2.41+ seem to include bunch of bug fixes and improvements especially for JavaScript and CSS.
https://htmlunit.sourceforge.io/changes-report.html#a2.50.0
Does this PR introduce any user-facing change?

No.
How was this patch tested?

All the UISeleniumSuite which use HtmlUnit pass on my laptop.

@sarutak I am seeing some error message in https://github.com/sarutak/spark/actions/runs/907529561
Are they related?

@gengliangwang I don't think so. I've noticed sometimes, such InterruptedException happens but seems not to affect the result.
https://github.com/dongjoon-hyun/spark/actions/runs/906863634

Test build #139367 has started for PR 32789 at commit d4d0c07.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43889/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43889/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/43889/

Test build #139367 has finished for PR 32789 at commit d4d0c07.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Thanks, merging to master

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/139367/


File not found when creating results after running with .features()

Testing in 0.9.9 RC4
String featureLocation = "/local/file/path/";
List<String> featurePaths = Collections.singletonList("subdirectory_of_features")
List<Feature> featureList = ResourceUtils.findFeatureFiles(new File(featureLocation), featurePaths);
Results results = Runner.builder()
                .features(featureList)
                .outputHtmlReport(true)
                .parallel(8);

The tests run but during the result processing I get:
java.lang.RuntimeException: not found: content-negotiation/content-negotiation-turtle.feature
	at com.intuit.karate.resource.ResourceUtils.getResource(ResourceUtils.java:123)
	at com.intuit.karate.core.FeatureResult.fromKarateJson(FeatureResult.java:90)

I seems that when finding features ResourceUtils.findFilesByExtension() relativizes to the working directory with no classpath prefix. Then later a call to ResourceUtils.getResource() fails the file.exists() test:
        if (path.startsWith("classpath:")) {
           ...
        } else {
            File file = new File(removePrefix(path));
            if (!file.exists()) {
                throw new RuntimeException("not found: " + path);
            }
            Path relativePath = workingDir.toPath().relativize(file.getAbsoluteFile().toPath());
            return new FileResource(file, false, relativePath.toString());
        }

closing as won't fix as .findFeatureFiles() is non-standard usage and more like an internal API
anyone is free to submit a PR against this issue ref


PEOPLE-105 rewrite remaining feature specs

Changes:

total refactor of users index page spec
refactor of user profile spec
tiny changes in factories

Jira:
https://netguru.atlassian.net/browse/PEOPLE-105
https://netguru.atlassian.net/browse/PEOPLE-101
This is the final batch for these tickets.

perfect, approved


Examples need to be updated to Cadence 1.0

Problem
Some of the examples are still written in pre-Cadence 1.0 and need to be updated.
Steps to Reproduce

For example, open the verify_signature/user_signature example
See pre-1.0 keywords like pub: https://github.com/onflow/flow-go-sdk/blob/7eb6328b774496418310a8487a893c070c9e5367/examples/verify_signature/user_signature/main.go#L43
See missing domainSeparationTag argument: https://github.com/onflow/flow-go-sdk/blob/7eb6328b774496418310a8487a893c070c9e5367/examples/verify_signature/user_signature/main.go#L84-L87

Acceptance Criteria
All examples are Cadence 1.0 compatible.
cc @onflow/flow-develop-experience-tools

Good catch! I'll update them.
Thanks for reporting


Downloading 100+ profiles at once

Describe the bug
I have a 500mbps downstream connection. I am attempting to download almost 200 profiles (the ones I follow). The download process seems to be slow (only downloaded 12 profiles, 1.4g) in 12 hours. Can this app be used with parallel with many instances running at once? O do you suspect a ban from IG? (I am using a VPN, though).
To Reproduce
Steps to reproduce the behavior:
Use command line CAT plus instagram username list to download to be fed into the app. Make sure you have dozens or hundreds of profiles.
Expected behavior
Higher download speed. 10 or more profiles per hour.
Error messages and tracebacks
No error message.
Instaloader version
Latest. Pip3 install instaloader.
Additional context
High Internet download speed link. Dedicated computer.

@hgkmaxymus Do You only use people’s usernames or also keep track via UserID converting to userName? E.g. if people changed their username.

@hgkmaxymus Do You only use people’s usernames or also keep track via UserID converting to userName? E.g. if people changed their username.

My calls use the username, but I also have their IDs stored in the folders (there is a id file there).
What I use here is a bash script, which logs when the usernames have been changed.
if [ `grep -c "changed its name" $log` -ne 0 ]; then
	echo " " | tee -a $log
	echo " Profile(s) name(s) have been altered:" | tee -a $log
	echo "$(grep -i 'changed its name' $log)" | tee -a $log
	date "+Date: %d/%m/%y%tHour: %H:%M:%S" >> $alteredprofiles
	grep -i 'changed its name' $log >> $alteredprofiles
	unix2dos -q $alteredprofiles
fi

So I can always double check it just by looking the logs (the $alteredprofile log), like:
Date: 12/07/19	Hour: 15:48:28
Profile <old_profile_name> has changed its name to <new_profile_name>.

Also, sorry for my coding, I am not a developer. But I hope it helps you in some way :)

@hgkmaxymus you’re definitely a coder :) I could never do these things with bash scripts


Feature request for next release

Let's keep updating this list to track our own feature requests that we are interested to merge with the existing code.

Improved keyword search
User able to give twitter access to nawab bot so that they can retweet from the telegram bot itself.

Debug as a logger option.


ts: Migrate peer_data.js module to TypeScript.

This converts the module peer_data.js to TypeScript.
~This is currently blocked by - people.js typescript migration which is progressing well in this PR #25539.~

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@zulipbot add "mentor review" "buddy review"

Looks good to me other than the comment!

@PIG208 Made the changes according to your review, ready for another look now :)

@zulipbot add "area: typescript migration"

@zulipbot remove "mentor review" "buddy review"
@zulipbot add "integration review"

LGTM!

Merged, thanks @Lalit3716 and @PIG208!


[stable/sonarqube] Allow use of custom cacerts

What this PR does / why we need it:
In environments with air-gapped setup, especially with internal tooling (repos) and self-signed certificates it is required to provide an adequate cacerts which overrides the default one:
Which issue this PR fixes
none
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test

/retest

/assign  tsiddique

Please fix the DCO: https://github.com/helm/charts/pull/14413/checks?check_run_id=140683332

Signoff is already fixed.

Signoff is already fixed.

Not according to the bottom checks

/ok-to-test

@rjkernick thanks for the review, now all my changes seem fine.

/ok-to-test

lgtm

/lgtm

Thanks @rjkernick


fix: Deploy pipeline is failed if deploy with ingress

Pull Request Template
Description
Please include a summary of the change and why it is needed.
Fixes # (GitHub Issue)
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Pull Request contains one commit. I squash my commits.

Additional context
Add any other context or screenshots about the feature request here.

/recheck


Remove unused keybind

Space is super common to use as leader, so this was shadowing very important keymaps.

If you have plans to add that debug functionality, I'd suggest mapping it to something else other than Space.

Absolutely right, that didn't need to be there :)


Add support for Digest authentication

Closes #1384
See the included docs for more info please. This effectively requires CAS to be on pac4j 1.9, since Digest AuthN support is heavily borrowed from pac4j.

A great work, but I think we need to fix the issue I mentioned before the merge (and wait for the version 1.9.1 of pac4j).

Sounds good. I'll leave this hanging. Got an ETA?

I'll do the releases at the beginning of next week.

Opened up https://github.com/pac4j/pac4j/issues/606

I released pac4j v1.9.1 and spring-webmvc-pac4j v1.1.1: you can safely upgrade to these ones. Notice that the signature of the validate  method of the Authenticator class has changed.

Great. Thanks for the update


libopusenc: init at 0.2.1

Motivation for this change
The package was missing and is needed by a newer version of pyogg.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build libopusenc


Add Canonical.MicroK8s 2.0.0

Microsoft Reviewers: Open in CodeFlow

Thanks for this @crpietschmann!


Having trouble figuring out how to get the curved text to be spaced closer together

Hey! First off just wanna say awesome job on a really helpful library, thanks!
I was having trouble getting my text to be spaced closer together. I thought it would be simply by playing around with forceWidth and/or forceHeight (still not quite sure how these work), but nothing seems to be working. Here's the text I have right now:

My goal is to get the letters to be spaced closer together so that the text curves up to only around the red lines pictured below. Is there any way to achieve this through the library and/or CSS?

Edit: I did decrease the font-size a bit and it helped a little, but the letters are still spaced out a little more than I'd like. It's so close!

Thanks!

Hey, glad you like the library. Did you try adjusting the CSS letter-spacing property?

I could have sworn I tried that already, but perhaps because I was trying in the Chrome Dev Tools inspector directly the results were coming out wrong since the property was applied post-render, but yes that did that trick! Thanks haha.


[Bug]-[130]:File picker Widget - able to pick a file when Max no of files is defined as zero (0)

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When Max no of files defined in a File picker is set to zero, we are able to pick a file by default.
Expected: The File picker widget should not allow the user to pick any files
Steps To Reproduce

Drag and drop a File picker widget
Change the Max no of files to 0 (Zero)
Now click on "Select file", select a file and click on open

Expected: Error message saying "Cannot upload any files" as max no of file is set to zero
Public Sample App
No response
Version
Release and production

A dev should not be able to set the value of max files to 0. We have to add this validation in this property. If they want to set it 0, it's better they disable it.

@iamrkcheers assigning this issue to you, proposed fix is the following

For the max files field, add a validation to not accept 0.
When 0 is still bound using some api or variable, disable the widget altogether

Stats

Stat
Values

Reach
130

Effort (months)
0.5

@dilippitchika  Can you assign this issue to me ?

Hi @dilippitchika , @somangshu , i have rasied PR on this Bug , could you pls review it.


vend a DEB repo management package?

ziti-edge-tunnel (ZET) is vended as a DEB package for each of the most recent Ubuntu LTS releases. The Ubuntu installer shell script chooses the best LTS release codename in case the system isn't running an LTS release.
How should we handle the situation where ziti-edge-tunnel was previously installed and the codename changes such that the appropriate LTS release also changes?
An example of this scenario is when an OS is upgraded from groovy to lunar because the mapped LTS releases for those vintages are focal and jammy, respectively.
According this AskUbuntu answer, it may be widely accepted that 3rd party sources are reviewed for codename changes during an OS upgrade. This matches my intuition that the system administrator will prefer to audit their sources, not trust a metapackage to manage them automatically. A quick search leads me to think that 3rd party apt sources are not automatically disabled during an OS upgrade, and so it seems to be solely up to the system admin to audit sources at that time.
Alternatives to a repo management (meta?)package may include collapsing the distro differences with install or upgrade scripts built in to a single package for all distros per architecture. In that possible future, all OSs that use DEB packages subscribe to the same apt source (no variation per distro).

This looks like the right approach, and it needs to manage the repo metadata signing pubkey too. That way, we can rotate the key if needed, and because the pubkey was first published with an expiry June 2024, so we need to get the mgmt package out there ASAP to avoid signature errors down the road.


Provide entity auth data to TokenFactory.createMasterToken()

This allows a token factory to use the entity authentication data when creating a master token, which may be useful when generating custom issuer data for the first time.

Pretty straightforward replacement. +1


binstar upload [SSLError] [SSL: CERTIFICATE_VERIFY_FAILED] win64 py34

Hi
Today, I started to get an [SSLError] [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed error when doing binstar upload. It previously worked fine. Not sure if it's related to a recent update of some of the packages. My conda install looks like this:
             platform : win-64
        conda version : 3.9.0
  conda-build version : 1.10.2
       python version : 3.4.2.final.0
     requests version : 2.5.2
     root environment : C:\Program Files\Miniconda3  (read only)
  default environment : C:\Program Files\Miniconda3
     envs directories : C:\Users\fhollebrandse\.conda\envs
                        C:\Users\fhollebrandse\envs
                        C:\Program Files\Miniconda3\envs
        package cache : C:\Users\fhollebrandse\.conda\envs\.pkgs
                        C:\Users\fhollebrandse\envs\.pkgs
                        C:\Program Files\Miniconda3\pkgs
         channel URLs : http://repo.continuum.io/pkgs/free/win-64/
                        http://repo.continuum.io/pkgs/free/noarch/
                        http://repo.continuum.io/pkgs/pro/win-64/
                        http://repo.continuum.io/pkgs/pro/noarch/
          config file : None
    is foreign system : False

And my root env like this:
binstar                   0.10.1                   py34_2
clyent                    0.3.2                    py34_0
conda                     3.9.0                    py34_0
conda-build               1.10.2                   py34_0
conda-env                 2.1.3                    py34_0
dateutil                  2.1                      py34_2
menuinst                  1.0.4                    py34_0
pip                       6.0.8                    py34_0
psutil                    2.1.1                    py34_0
pycosat                   0.6.1                    py34_0
python                    3.4.2                         0
python-dateutil           2.1                       <pip>
pytz                      2014.9                   py34_0
pyyaml                    3.11                     py34_0
requests                  2.5.2                    py34_0
setuptools                12.2                     py34_0
six                       1.9.0                    py34_0

requests.get("https://api.binstar.org") works fine.
Full error message:
PS C:\Users\fhollebrandse> binstar upload -c dev -u openhydrology c:\Users\fhollebrandse\Downloads\win-64_floodestimatio
n-0.3.3-np19py34_0.tar.bz2
Using binstar api site https://api.binstar.org
detecting package type ...
conda
extracting package attributes for upload ...
done

Uploading file openhydrology/floodestimation/0.3.3/win-64/win-64_floodestimation-0.3.3-np19py34_0.tar.bz2 ...
[SSLError] [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)
Traceback (most recent call last):
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\packages\urllib3\connectionpool.py", line 544, in urlopen

    body=body, headers=headers)
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\packages\urllib3\connectionpool.py", line 341, in _make_r
equest
    self._validate_conn(conn)
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\packages\urllib3\connectionpool.py", line 762, in _valida
te_conn
    conn.connect()
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\packages\urllib3\connection.py", line 238, in connect
    ssl_version=resolved_ssl_version)
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\packages\urllib3\util\ssl_.py", line 256, in ssl_wrap_soc
ket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "C:\Program Files\Miniconda3\lib\ssl.py", line 364, in wrap_socket
    _context=self)
  File "C:\Program Files\Miniconda3\lib\ssl.py", line 578, in __init__
    self.do_handshake()
  File "C:\Program Files\Miniconda3\lib\ssl.py", line 805, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\adapters.py", line 370, in send
    timeout=timeout
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\packages\urllib3\connectionpool.py", line 574, in urlopen

    raise SSLError(e)
requests.packages.urllib3.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Miniconda3\Scripts\binstar-script.py", line 5, in <module>
    sys.exit(main())
  File "C:\Program Files\Miniconda3\lib\site-packages\binstar_client\scripts\cli.py", line 94, in main
    description=__doc__, version=version)
  File "C:\Program Files\Miniconda3\lib\site-packages\binstar_client\scripts\cli.py", line 76, in binstar_main
    return args.main(args)
  File "C:\Program Files\Miniconda3\lib\site-packages\binstar_client\commands\upload.py", line 202, in main
    callback=upload_print_callback(args))
  File "C:\Program Files\Miniconda3\lib\site-packages\binstar_client\__init__.py", line 423, in upload
    s3res = requests.post(s3url, data=data_stream, verify=self.session.verify, timeout=10 * 60 * 60, headers=headers)
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\api.py", line 99, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\api.py", line 49, in request
    response = session.request(method=method, url=url, **kwargs)
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\sessions.py", line 461, in request
    resp = self.send(prep, **send_kwargs)
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "C:\Program Files\Miniconda3\lib\site-packages\requests\adapters.py", line 431, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)

I have the same issue, I cannot upload any file on binstar anymore, either from Windows or from Linux (Debian Jessie). Same SSL error.
Even after a "conda update binstar" (so now I have up to date binstar client 0.10.1)

We are currently looking into this error. I suspect it may be the latest release of conda.
If you want a workaround, you can manage your binstar SSL verification settings with:
binstar config --set verify_ssl [true|false|/path/to/root/CA]

Just FYI, after a bit of wiresharking, it seems to be an issue with Amazon S3 storage SSL certificate.

Thanks for the workaround btw!

Many thanks for looking into this. Workaround works well.

Just to say, I get the same error on conda install and conda builds on my own channel.
See for example this build on Travis CI: https://travis-ci.org/OpenHydrology/floodestimation/jobs/51939331

It looks like this is solved with requests 2.5.3?

Many thanks for all your help.

Still broken for channels.
binstar config --set verify_ssl false  not working around it either


Updating to 0.6.1

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Use @rdfjs/express-handler instead of body-parser

it's still using rdf-body-parser. should be replaced with @rdfjs/express-handler.
express-handler doesn't use body-parser anymore and does stream processing.

Not current with v0.5+


GKE ingress in default deployment very slow ? can we deploy without ?

We are testing asyngular server as per docs and it works great. We deployed on GCP as per guides for deployment on Kubernetes:
https://asyngular.io/docs/deploying-to-kubernetes/
and the services works with all services running smoothly. note: the only headache was the TLS certificate configuration, as mentioned
However we are seeing latency of more than 300 ms so after investigation it turns out that the GKE ingress service from Google is very slow:
This is deployed in asia-southeast1 (Singapore). I did some ping test on the master GKE controller and the ingress service public IP. The difference is about 200ms delay due to use of ingress load balancer as opposed to connecting straight to a server/service (which is on the master replica). See below screenshots...
Is there a way to deploy asyngular default configuration without the ingress service ? or maybe with a dedicated LB (nginx) instead ? Some googling shows that Google ingress service has latency issues and that using a dedicated LB solves these issues ?
It is a real problem and it defeats the whole purpose of using asyngular. I see process time for messages in the order of 5 ms but the latency introduced by the ingress service is 200 ms ?
Any recommendation would be appreciated.
Master controller:

ingress public IP:

Results:
On the left is latency to the Cluster master controller and on the right to the ingress public IP

@hervejegou Thanks for this detailed report. I did notice the following issues when deploying to GKE:

It took a relatively long time (maybe 4 to 10 minutes) for the ingress to start working after the initial deployment (subsequent deployments were fast though).
By default, the GKE ingress has a very short connection timeout which kills the WebSocket connection after only 30 seconds (but the timeout can be configured through the control panel; I typically set it to 1 day; 86400 seconds). Obviously this is not a good default for Asyngular.

I didn't check for this third issue related to latency so thanks for pointing it out. It does seem like there is something wrong with GKE's default ingress.
From my experience, I've found that the new version of Rancher installed on plain Amazon EC2 instances was the smoothest experience.
I think it would be worthwhile to come up with a solution which works perfectly on GKE out of the box. I was considering to use https://github.com/kubernetes/ingress-nginx instead of ingress - Maybe the asyngular CLI could expose an option to allow us to choose between the default platform ingress or the nginx service?
This shouldn't be too difficult to implement. If you have some time to make it work with nginx, feel free to make a PR or let me know what needs to be done. Otherwise I will try to make some time in the next few weeks to get it working with nginx.

@jondubois one of the thing that works really well out of the box is the asyngular CLI. In fact earlier we were looking at your baasil CLI for same reason. It really simplifies the work of developing and deploying  (a bit like Meteor Galaxy). And GKE seems to work quite well has good web control panels and logs out of the box.
So I agree using https://github.com/kubernetes/ingress-nginx as an option during deployment would be the easiest solution and has a very good chance of solving this issue.
I do have time but I am a newbie at Kubernetes so modifying your CLI is way above my skillset at this time. The most I can do is try to farm this out to someone more qualified on Upwork?
Could you maybe give me a description of how to modify the asyngular CLI ? and the kubernetes yaml configurations files ? so that it uses the kubernetes ingress-nginx. I will be happy to ask someone more experienced to get it done and submit a PR.
This is a high priority for our project so I am keen to get it resolved and contribute it so it can be a standard option in the CLI (during first deploy command, choose use dedicated ingress-nginx y/N ?)
Meanwhile we will continue our development with current setup but our purpose was to replace a mix of Pusher.js and node js server since Pusher.js has latency in the 200-300ms range.
So we are clearly hoping that with asyngular running on GKE in our region, we should see latencies in the 30-60ms range if we solve this load balancer delay.
If you can give us a clear direction, I will hire someone on Upwork to get it done quickly. I see some very good cloud architects available on Upwork so I can probably get it completed rapidly.

@hervejegou The asyngular deploy command creates all the resources from the .yaml files that are inside your app's kubernetes/ directory. So you can add additoinal .yaml files if you want to run other services alongside your Asyngular cluster. It could be as simple as just copy pasting the .yaml files provided here (under GCE - GKE) https://kubernetes.github.io/ingress-nginx/deploy/

@hervejegou thanks a lot. things are working out really well so far with asyngular server. But the latency is still going wild (200 ms extra latency due to ingress). I will try to test nginx load balancer next week.

@hervejegou To use nginx as the ingress on GKE, you just need to run a few additional commands.
I added a GKE section to the website here which explains: https://asyngular.io/docs/deploying-to-kubernetes/#google-kubernetes-engine-gke
I didn't check the latency though but I suppose that this setup should make things more configurable. To minimize latency, you should make sure that the nginx instance(s) is/are running in the same zone as agc-worker and agc-broker services.

@jondubois We are deploying for beta release and I have monitored for last 2 weeks and in fact ingress was unstable for a while but it seems OK now. I see a maximum of 10ms extra latency when pinging the ingress vs pinging the worker container directly. So this is quite acceptable for  a load balancer.
We can close this issue I think. Thanks for your help.

I'm seeing a really slow GKE ingress now - up to 1 second even. Especially if multiple requests are coming in at the same time.