Temperature of climate entities not taken into account

Heyo everyone!
I came back to this after a while because I noticed that development had picked up a bit and gave it a go. For me one of the main use cases would be to control the thermostats around the house. When testing I noticed that the target temperature of my thermostats does not influence the "on/off" state of the stateful scene. Only the heating mode does I think.
I'm using the latest version of HA and of stateful scenes. I had a short look at the code but couldn't spot the issue immediately. I'll see if I have some more time to look into this. Until then, please let me know if I can test anything or provide more information. :)
Edit: Ok some more information as I did some more testing. The state of the scene is reflected correctly if I set the tolerance to 0. With tolerance 1 I get the following behavior: Say I set one thermostat to 21°C in my scene. If I change it to 20.5°C the scene is still on (as expected). Now when I set it from 20.5°C to 19.5°C, the scene remains activated. So probably the issues lies here where it compares the current value with a wrong base value?

Hi and thanks for your reply!
For my use case I set the tolerance to 0 which helps already. I also set the debounce time to 5 seconds I think because the thermostats take a little bit of time to adjust (now it is shown as 0, not sure, maybe a reload of the scenes has reset it?).
When looking at the tolerance value, my first impression was that a value is accepted as long as it is within the scene value +/- the tolerance. So the behavior described by you is a bit different.
I would also not handle this case differently. Ideally we could find something that works for every case. What issues would occur if every change is deemed relevant and then we check if the new value is within scene value +/- tolerance? I assume it will be an issue together with the debounce value. I haven’t had time to look at the code yet (holiday break was quite packed), but hopefully I get a chance in the coming week.


update plugins for maven 3.6.3+

[ ] validate versions are available internally

mvn clean install site -Pcheckstyle,coverage,pmd,dist worked fully for me


net::ERR_UNKNOWN_URL_SCHEME

Getting his error while using facebook Auth0 as below ,

Issue solved by running on real device but in genymotion it's still giving this error
those who are getting the same error kindly try running on real device rather then any emulator
any way thanks auth0 team ;)


Implement videos

Continuation of #32. Closes #46. Closes #49. Closes #50
Implements playwright automation that creates great videos. I improve the examples a bit on the go so that they look and feel better.
Todo

[x] Make sure all examples use a nice style. For example material. Closes #40
[x] Implement code to generate video examples

[x] basics
[x] components
[x] features
[x] langchain
[x] mistral
[x] openai

[x] Fix test errors
[x] Make tests run fast normally. And slower when recording video.
[x] Collect screenshots and videos and persist them somewhere they can be used in the examples gallery

Videos in the docs are going to be so cool.

Hi @ahuang11
If the tests pass (they do locally) then this is ready for review. If you have the time please consider reviewing and merging it. It will bring many improvements including screenshots and videos for each example. As this one has renamed all files it will require some work to merge if you continue working on main for some time before looking at this. Thanks.

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

Comparison is base (5b56b23) 98.41% compared to head (822a168) 98.41%.
Report is 16 commits behind head on main.

:exclamation: Current head 822a168 differs from pull request most recent head 21a43f9. Consider uploading reports for the commit 21a43f9 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #41   +/-   ##
=======================================
  Coverage   98.41%   98.41%
=======================================
  Files           2        2
  Lines          63       63
=======================================
  Hits           62       62
  Misses          1        1

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

Thanks! It looks awesome. I'll take a look after tackling langchain docs + tests PR

Looks awesome! Thanks!


Regarding resource usage

Crawling using new pages or new browser for each url , which will be resource efficient and fast?

opening new page is considered to use the least amount of resources in comparison to opening new browser/app


install into /usr/sbin not /usr/bin

Perhaps install into /usr/sbin not /usr/bin.
Also note in documentation and scripts etc. that it must be run by root.

That is not the default location where to install binaries. Some distributions such as opensuse use this location instead, but it just confuses. Create_ap should be run as service anyways.


Cmake auto downloading Resource link invalid

I have found this engine&framework today, it looks like most nice, but
bsfDependices & bsfData etc. links was failured, could you fix that please, thx~

resolved for https://github.com/GameFoundry/bsf/issues/416#issuecomment-712781767
close it.


Update LOWER scalar function to support Utf8View

Part of https://github.com/apache/datafusion/issues/11752 and https://github.com/apache/datafusion/issues/11790
Currently, a call to LOWER with a Utf8View datatypes induces a cast. After the change that fixes this issue, it should not.
query TT
EXPLAIN SELECT
  LOWER(column1_utf8view) as c1
FROM test;
----
logical_plan
01)Projection: lower(CAST(test.column1_utf8view AS Utf8)) AS c1
02)--TableScan: test projection=[column1_utf8view]

lower is defined here: https://github.com/apache/datafusion/blob/main/datafusion/functions/src/string/lower.rs
Is your feature request related to a problem or challenge?
We are working to add complete StringView support in DataFusion, which permits potentially much faster processing of string data. See https://github.com/apache/datafusion/issues/10918 for more background.
Today, most DataFusion string functions support DataType::Utf8 and DataType::LargeUtf8 and when called with a StringView argument DataFusion will cast the argument back to DataType::Utf8 which is expensive.
To realize the full speed of StringView, we need to ensure that all string functions support the DataType::Utf8View directly.
Describe the solution you'd like
Update the function to support DataType::Utf8View directly
Describe alternatives you've considered
The typical steps are:

Write some tests showing the function doesn't support Utf8View (see the tests in string_view.slt to ensure the arguments are not being cast
Change the Signature of the function to accept Utf8View in addition to Utf8/LargeUtf8
Update the implementation of the function to operate on Utf8View

Example PRs

Update to use an arrow kernel that already supports StringView:  https://github.com/apache/datafusion/pull/11787
Change the implementation to support StringView directly: https://github.com/apache/datafusion/pull/11676
Change implementation (option 2): https://github.com/apache/datafusion/pull/11556

Additional context
The documentation of string functions can be found here: https://datafusion.apache.org/user-guide/sql/scalar_functions.html#string-functions
To test a function with StringView with datafusion-cli you can use an example like this (replacing starts_with with the relevant function)
> create table foo as values (arrow_cast('foo', 'Utf8View'), arrow_cast('bar', 'Utf8View'));
0 row(s) fetched.
Elapsed 0.043 seconds.

> select starts_with(column1, column2) from foo;
+--------------------------------------+
| starts_with(foo.column1,foo.column2) |
+--------------------------------------+
| false                                |
+--------------------------------------+
1 row(s) fetched.
Elapsed 0.015 seconds.

To see if it is using utf8 view, use EXPLAIN to see the plan and verify there is no CAST. In this example the CAST(column1@0 AS Utf8) indicates that the function is not using Utf8View natively
> explain select starts_with(column1, column2) from foo;
+---------------+------------------------------------------------------------------------------------------------------------------------------+
| plan_type     | plan                                                                                |
+---------------+------------------------------------------------------------------------------------------------------------------------------+
| logical_plan  | Projection: starts_with(CAST(foo.column1 AS Utf8), CAST(foo.column2 AS Utf8))                                                |
|               |   TableScan: foo projection=[column1, column2]                                                                               |
| physical_plan | ProjectionExec: expr=[starts_with(CAST(column1@0 AS Utf8), CAST(column2@1 AS Utf8)) as starts_with(foo.column1,foo.column2)] |
|               |   MemoryExec: partitions=1, partition_sizes=[1]                                                                              |
|               |                                                                                |
+---------------+------------------------------------------------------------------------------------------------------------------------------+
2 row(s) fetched.
Elapsed 0.006 seconds.

It is also often good to test with a constant as well (likewise there should be no cast):
> explain select starts_with(column1, 'foo') from foo;
+---------------+----------------------------------------------------------------------------------------------------------+
| plan_type     | plan                                                                                |
+---------------+----------------------------------------------------------------------------------------------------------+
| logical_plan  | Projection: starts_with(CAST(foo.column1 AS Utf8), Utf8("foo"))                                          |
|               |   TableScan: foo projection=[column1]                                                                    |
| physical_plan | ProjectionExec: expr=[starts_with(CAST(column1@0 AS Utf8), foo) as starts_with(foo.column1,Utf8("foo"))] |
|               |   MemoryExec: partitions=1, partition_sizes=[1]                                                          |
|               |                                                                                |
+---------------+----------------------------------------------------------------------------------------------------------+
2 row(s) fetched.
Elapsed 0.002 seconds.

### Additional context

_No response_

take


Explain why nix.useChroot is false by default

Is this just a holdover from the pre-systemd days?
I can update the manual, but I don't know the reason.

Closing due to upstream issue.


Figure out a way to separate large images from exported css

Currently the CSS for the card component is huge as we export a large image within the CSS. We need to figure out a way to ship the image separately, so we can keep the exported CSS small, and instances that use the special card variant can side-load the background image.

Use a CDN image URL instead of embedding it?

Can this be closed now if we're using the hologram mixin instead of an image?

Yeah let's close. All the remaining images are SVGs.


Proxy error alert

Guys, could we have an alert for cases where there is an issue with the agent's proxy?
We have a couple of workflows that are unable to inject files into Phedex. We dug into the agent (vocms0304) and we found this:
2017-06-01 12:59:32,337:139986848098048:ERROR:PhEDExInjectorPoller:PhEDEx file injection failed with HTTPException: 502 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<title>502 Proxy Error</title>

Proxy Error

The proxy server received an invalid^M
response from an upstream server.
^M
The proxy server could not handle the request POST /auth/complete/phedex/datasvc/json/prod/inject.

Reason: Error reading from remote server

@amaltaro I was wondering whether we have an actual alarm for invalid proxy any such

As replied privately "We have one in wmstats, for the user proxy. It's on my todo list to add the service cert to the watch list."

ok, for example https://its.cern.ch/jira/browse/CMSCOMPPR-822

Proxy warning in wmstats was made fully available as of the last cmsweb upgrade, May 2nd. Though we still have the cronjobs as well, just to keep some redundancy and to make sure CSPs will report on those alarms such that we can renew the proxy in time.


Use priority for most common/used name ref

Fixes https://github.com/Project-OSRM/osrm-text-instructions/issues/30
Still very experimental, but wanted to get the PR sooner than later for visiblity.
Todo:

[x] Integrate prototype into osrm-frontend to see it first-hand
[ ] Make implementation airtight
[ ] Write good extended tests for all cases

I integrated this hacky-ish into osrm-frontend. Results so far are promising, see details below

left is new, right is new
route
This one is interesting since the last part is both on US 29 and US 50, but we prefer US 50 (and don't switch between them within a part anymore, as before)

route
We might want to give ref a boost over name, at least in the beginning CA 210 might have been a better choice.

route

route

One pitfall to this approach of omitting the road names along the route is that route markers for surface streets are often infrequent (especially in rural areas in the U.S.) or poorly maintained (especially in urban areas in the U.S.). This is often true of U.S. Routes but increasingly the case as you go down to the state, county, and township level. A driver consuming turn-by-turn guidance for an exurban/suburban route like this would benefit far more from instructions like:

Turn right on Paxton Avenue to stay on SR 48

when they’re already on SR 48 than:

Turn right on SR 48

To avoid above problems, we might want to keep the current decisions between name and destination, but at least choose for either the most common. That would solve the I-80 problem described in #30

test


Calling stop() does not properly close all active connections, namely websocket connections.

Calling stop() does not properly close all active connections, namely websocket connections.

So i now manually keep track of websocket connections, and before i call stop(), i iterate through all the connections, and call close(). Now it turns out the handler that is dispatched at line 6898 in crow_all.h never gets called. If you do a bit more tracking it goes into boost.asio, at which point I loose track of the stack trace.
Can anybody help? I know this repo is dead, but just checking in case some users have encountered similar problems.

I'll try to look into it if i have time. if you can provide some minimal example where the issue appears it would be great.

Don't worry. I use a combination of https://github.com/yhirose/cpp-httplib and https://github.com/zaphoyd/websocketpp.git. I also sometimes use https://github.com/civetweb/civetweb though i get hanging issues with the last one.

So I looked through the code (I know you said not to worry), It seems that stop() and close() do completely different things.
close() sends a close signal and once a confirmation is received, it closes the socket adaptor.
stop() on the other hand shuts down the IO services that all sockets use (HTTP request sockets or WebSockets). And while that works does work, the client just never receives any notice.

This is indeed a problem if you stop() your server and restart it afterwards without much waiting. It will then fail to start with an exception:
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  bind: Address already in use

Calling lsof gives you the reason:
$ lsof -i :18080
COMMAND     PID       USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
my-server 23405 jf99   44u  IPv4 149122      0t0  TCP localhost:18080->localhost:40806 (CLOSE_WAIT)

This is with reuse_addr = true in the acceptor's constructor (line 9269 in crow_all.h).

From what I've seen in the code (and I might be totally wrong), the primary issue is that Crow doesn't keep track of connections, (with the exception of HTTP connections in debug mode).
And the only solution I can think of is what @pfeatherstone was doing but in crow itself, which is keep track of all active connections and send a close signal right before stopping the server as part of stop().

This is indeed a problem if you stop() your server and restart it afterwards without much waiting. It will then fail to start with an exception:
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  bind: Address already in use

Calling lsof gives you the reason:
$ lsof -i :18080
COMMAND     PID       USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
my-server 23405 jf99   44u  IPv4 149122      0t0  TCP localhost:18080->localhost:40806 (CLOSE_WAIT)

This is with reuse_addr = true in the acceptor's constructor (line 9269 in crow_all.h).

As far as I remember there're OS settings which affect the CLOSE_WAIT timeouts e.g.
net.ipv4.tcp_fin_timeout and tcp_keepalive_time etc.
so it might not always be the case if you tweak your OS for high concurrency and load - to keep these sockfds closed
in a timeley manner.
TYVM

Like everything else in boost, it seems boost.asio is more complicated than what it needs to be.


add_link still used in tutorial

I thought add_link has been deprecated, but it's still used in tutorial (https://docs.chainer.org/en/stable/examples/cnn.html, ResNet152).

Thanks for the feedback.
Chain.add_link is deprecated, but ChainList.add_link (which is used in the docs) is still an alive API.

There're two add_link, I see. Thanks for the clarification.


Implemented multi-node configuration

Resolves #159
After running docker-compose -f docker-multi-node.yaml up command,
four nodes will be created with each node hosting an instance of
Sawtooth Next Directory. Each node will have access to the blockchain
and will utilize a simulated version of PoET. The Next Directory UI
will be available at:
http://<IP_ADDRESS>:4200
http://<IP_ADDRESS>:4200
http://<IP_ADDRESS>:4200
http://<IP_ADDRESS>:4200
Note: Because user accounts authorization is currently being stored in the rethinkdb auth table and not being stored on the blockchain, when a user is created on a specific node, that user cannot sign in on a different node. All other data is shared among the four nodes.
Signed-off-by: Michael Nguyen<EMAIL_ADDRESS>

@adamgering @nadiabahrami - Paths has just been updated in latest commit.


Cartesian Stiffness Values Ignored

When I use the Cartesian pose interface through franka_semantic_components, the arm seems to ignore the Cartesian stiffness values I set through the /service_center. The Joint impedance values are respected, but no matter how low I set the Cartesian stiffness values, the arm is not compliant in Cartesian space.
To replicate this, you can add the following code to the on_configure method of the CartesianImpedanceExampleController class. Am I missing some way to configure the arm for compliant motion in Cartesian space?
  auto client =
      get_node()->create_client<franka_msgs::srv::SetCartesianStiffness>("service_server/set_cartesian_stiffness");

  auto request = std::make_shared<franka_msgs::srv::SetCartesianStiffness::Request>(franka_msgs::srv::SetCartesianStiffness::Request());
  request->cartesian_stiffness.at(0) = 10;
  request->cartesian_stiffness.at(1) = 10;
  request->cartesian_stiffness.at(2) = 10;
  request->cartesian_stiffness.at(3) = 10;
  request->cartesian_stiffness.at(4) = 10;
  request->cartesian_stiffness.at(5) = 10;

  auto future_result = client->async_send_request(request);
  future_result.wait_for(seconds(1));

  auto success = future_result.get();
  if (!success) {
    RCLCPP_FATAL(get_node()->get_logger(), "Failed to set Cartesian stiffness.");
    return controller_interface::CallbackReturn::ERROR;
  } else if (!success->success) {
    RCLCPP_FATAL(get_node()->get_logger(), "Failed to set Cartesian stiffness.");
    return controller_interface::CallbackReturn::ERROR;
  } else {
    RCLCPP_INFO(get_node()->get_logger(), "Cartesian stiffness set.");
  }

This seems to be a small oversight of us - currently there is no way to do CartesianImpedance control (which then would re-act to the Cartesian stiffnesses you set).
But: You can work around it by changing in line 293 to 303 in https://github.com/frankaemika/franka_ros2/blob/humble/franka_hardware/src/robot.cpp to a research_interface::robot::Move::ControllerMode::kCartesianImpedance (or give the initialization function a parameter to be either/or)


Add License

We should add a license file. Typically projects in Julia are MIT licensed and consequently we should add a file like this with title LICENSE.md (should be copy pasted so that GitHub can parse it and mark our projects as such).
I can do it but want to check first you're happy with going MIT license.
The LiveServer.jl package is licensed under the MIT "Expat" License:

> Copyright (c) 2019: Jonas Asprion, Thibaut Lienart.
>
> Permission is hereby granted, free of charge, to any person obtaining a copy
> of this software and associated documentation files (the "Software"), to deal
> in the Software without restriction, including without limitation the rights
> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
> copies of the Software, and to permit persons to whom the Software is
> furnished to do so, subject to the following conditions:
>
> The above copyright notice and this permission notice shall be included in all
> copies or substantial portions of the Software.
>
> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
> SOFTWARE.
>

Yep, MIT is fine for me.


crypto/tls: no cipher suite supported by both client and server when client doesn't set supportedPoints

What version of Go are you using (go version)?

$  go1.18.3 linux/amd64

Does this issue reproduce with the latest release?

I've an IoT server written in Go that IoT devices connect to with TLS. It works fine with a variety of devices. Now I'm trying to connect to it with a new device using a Calypso Wifi module but it wont connect and fails with tls: no cipher suite supported by both client and server.
Debugging by littering the Go TLS code with prints it turns out that it fails because the call to supportsECDHE returns false. It's using secp256r1 ecdsa keys and both server and device are set to use TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256.
Debugging further it looks like the Calypso module is not setting any supportedPoints in its client hello (hs.clientHello.supportedPoints) so then supportsECDHE will always return false.
I'd have guessed that this is a bug with the Calypso module however there is a comment in the code just on from here saying "omitting the ec_point_formats extension is permitted", so should it actually be supported that clients don't send this?
As a quick test I tried the following and it does fix the problem and the Calyspso device is now able to connect:
diff --git a/src/crypto/tls/handshake_server.go b/src/crypto/tls/handshake_server.go
index 7606305c1d..7ae787de80 100644
--- a/src/crypto/tls/handshake_server.go
+++ b/src/crypto/tls/handshake_server.go
@@ -238,6 +238,11 @@ func (hs *serverHandshakeState) processClientHello() error {
                hs.hello.scts = hs.cert.SignedCertificateTimestamps
        }

+       if len(hs.clientHello.supportedPoints) == 0 {
+               hs.clientHello.supportedPoints = []uint8{pointFormatUncompressed}
+               fmt.Printf("****** dbg 1 fixed: clientHello.supportedPoints: %x\n", hs.clientHello.supportedPoints)
+       }
+
        hs.ecdheOk = supportsECDHE(c.config, hs.clientHello.supportedCurves, hs.clientHello.supportedPoints)

        if hs.ecdheOk {

(might be nicer to fix it in the supportsECDHE function though)
So interested in your comments? Is it really ok for a client to not specifiy supportedPoints? If so would you take a PR from me to fix it?

duplicate of #49126?

duplicate of #49126?

Yes, it does look like the fix in #49126 would fix what we are seeing.

Duplicate of #49126


Add new search pages to Pa11y

this cannot be merged until the new search pages are visible on the site by default, without messing with the toggle

Moving this back to Next as the toggle is not blocking the page anymore


JS: Add process.env as source in js/clear-text-logging

Now the query is able to detect this CVE: https://snyk.io/vuln/SNYK-JS-SENECA-460597
The fix commit is still marked by the query.
I've found no new results other than the above (but I haven't used the Chris API).
I've added the extra taint-steps directly into the Configuration as it is a dataflow tracking configuration and not a taint tracking configuration. (Changing the configuration to use taint tracking causes way to much to be marked in the tests).
Performance on a in-progress version was great, and I'm currently running dist-compare on this version.

I wonder if we should generalize the processEnv label a bit to be named something like SensitiveInformationMap (subject to change, please), and let process.getAPropertyRead("env") be the only member of that for now. We are changing a library file (qll), so it would be good to get the abstractions right immediately.

I renamed it to PartiallySensitiveMap for now.
Still subject to change.

@esben-semmle: evaluation is done, including on your passwords.slugs.

Hmm. I fear this is becoming too noisy, although I really like some of the new results that this enables  (ex.: console.log(JSON.stringify(transportConfig))).

console.log('Quality config:', process.env[name]);: this is a large class of FPs, and the most important one to address.
The programmer is clearly in control of the environment variable he prints, I would suggest not to use property reads of the process.env object as taint steps.
https://github.com/Microsoft/vscode/blob/9233b63a1d4a23956ba97a98bd1a87db4f60c92d/build/azure-pipelines/common/release.ts#L79.

creds.password.replace(/./gm, "*")): this is a bad FP caused by the taint tracking formulation, I would suggest to adding a barrier for such "masking" replace calls. Given the rarity and time until next dist-upgrade, this can be done in another PR.
https://github.com/mradamlacey/elasticsearch-tableau-connector/blob/6304c7e20c5286d0eed8dcc63fef59e587a1da11/connector/elasticsearch-connector.js#L207.

The programmer is clearly in control of the environment variable he prints, I would suggest not to use property reads of the process.env object as taint steps.

That seems like an OK solution.
It leaves the new flow-label obsolete, but I'll keep the flow-label in the query.

creds.password.replace(/./gm, "*")): this is a bad FP caused by the taint tracking formulation, I would suggest to adding a barrier for such "masking" replace calls. Given the rarity and time until next dist-upgrade, this can be done in another PR.

I just included it in this PR. I added a simple barrier that does some simple syntactic checks to see it it looks like a masking .replace() call.

Can you do a sanity dist-compare with the recent changes?

I already got one running that has everything except the very recent changes to MaskingReplacer.

@esbena new dist-compare on everything except very recent MaskingReplacer changes: https://git.semmle.com/erik/dist-compare-reports/tree/florian.ti.semmle.com_1573560923578

did we ever perform a performance evaluation of the new formulation?

The linked dist-compare includes default.slugs, so doesn't that work as performance evaluation?

can you confirm that the vulnerability in https://jira.semmle.com/browse/ODASA-8152 is now flagged, and that it remains flagged after the fix

I can confirm that. I just ran the query again on both the vulnerable and fixed version.

The linked dist-compare includes default.slugs, so doesn't that work as performance evaluation?

Doh, I had a scrolbar in the bottom of my view that made it look like you only did an evaluation of a single SHA. The spring-mvc-angular-js-hibernate-bootstrap-java-single-page-jwt-auth-rest-api-webapp-framework project name is at fault...

Lets just run the security suite performance evaluation once more on gecko-dev then - a 9% time increase is scary to look at, and you did add a new default taint step...

Lets just run the security suite performance evaluation once more on gecko-dev then - a 9% time increase is scary to look at, and you did add a new default taint step...

I tried, multiple times, but I'm getting this undescriptive error https://i.imgur.com/eXSFzVY.png
I'll try to investigate.

And now dist-compare gets this error when trying to build a snapshot of gecko-dev (master branch of both code and ql): https://i.imgur.com/42VLuwe.png
I think I'll do the security on defaults (except gecko-dev) and report back.

Pro tip: you can insert images directly into comments via drag-and-drop
. Saves you the trouble of going through an external image hosting site.

Ping @max-schaefer


Updated link on forgotten PaaS passwords

Current link in documentation is out-of-date so it's best to point users
to PaaS docs for appropriate reset links.
Fixes: #2860

thanks, someone will have to merge it  as I don't have privileges


refactor!: rename action ID & uniqueness hash

Based on some discussions and feedback, updating some terms to provide a lot more clarity regarding their purpose.

externalNullifier -> actionId
proofSignal -> signal
nullifierHash -> uniquenessHash

CC @tiago-sada for feedback too

Makes sense @m1guelpf, reverted to nullifierHash, also sharing context from conversation with @philsippl. a) Nullifier is a more established term in this context and b) uniqueness hash may cause confusion with the iris code hash from the orb.


Respect trailing comma style when organizing imports

I use eslint with a typescript react project, and the comma-dangle rule is in direct conflict with the VS Code built in organize imports feature. Currently the organize imports feature supports multiple import variables on their own line, but will remove the trailing comma, causing the eslint rule to complain. Even if I manually fix it, the organize import feature will just remove it again.
PLEASE add the option to ALLOW trailing commas.
import {
    foo,
    bar,
    bloop,
} from "some-package";

That is perfectly valid Typescript and should be configurable.
Example of the setting in question:
"settings": {
	"editor.formatOnSave": true,
	"[typescript]": {
		"editor.codeActionsOnSave": {
			"source.organizeImports": true
		}
	}
}

TIL trailing commas are allowed in import lists...

Trailing commas should be the default because they're objectively better:

They minimize git diffs when adding or deleting new items at the end of the list.
They make copy-pasting and reordering lines easier.


detect and support phred offsets other than 33

Original issue reported here. The current directory formats assume the phred offset is 33, but this is not always the case. Labeling as a bug since it is possible to create a phred offset 33 directory format with phred offset 64 data, and no error is displayed until quality scores are requested in a transformer (e.g. loading into skbio Sequence objects).

This is now handled for demultiplexed data (via #111), but the issue is still possible with multiplexed data. Re-opening this, as we need to handle it for multiplexed data as well.

Will re-open this if this ever comes up as a more common issue on the user forum.


rollup typescript issue when building tooling/api on windows

I am having trouble building tooling/api on windows.
[!] Error: Unexpected token (Note that you need plugins to import files that are not JavaScript)

Full Error
PS C:\Users\ASUS\dev\tauri\tooling\api> yarn build
yarn run v1.22.10
$ rimraf ./dist && rollup -c --silent && node ./scripts/after-build.cjs
babelHelpers: 'bundled' option was used by default. It is recommended to configure this option explicitly, read more here: https://github.com/rollup/plugins/tree/master/packages/babel#babelhelpers
[!] Error: Unexpected token (Note that you need plugins to import files that are not JavaScript)
src\path.ts (13:23)
11:  * @returns
12:  */
13: async function appDir(): Promise<string> {
                           ^
14:   return invokeTauriCommand<string>({
15:     __tauriModule: 'Fs',
Error: Unexpected token (Note that you need plugins to import files that are not JavaScript)
    at error (C:\Users\ASUS\Dev\tauri\tooling\api\node_modules\rollup\dist\shared\rollup.js:5305:30)
    at Module.error (C:\Users\ASUS\Dev\tauri\tooling\api\node_modules\rollup\dist\shared\rollup.js:9750:16)
    at Module.tryParse (C:\Users\ASUS\Dev\tauri\tooling\api\node_modules\rollup\dist\shared\rollup.js:10156:25)
    at Module.setSource (C:\Users\ASUS\Dev\tauri\tooling\api\node_modules\rollup\dist\shared\rollup.js:10057:24)
    at ModuleLoader.addModuleSource (C:\Users\ASUS\Dev\tauri\tooling\api\node_modules\rollup\dist\shared\rollup.js:18403:20)
    at ModuleLoader.fetchModule (C:\Users\ASUS\Dev\tauri\tooling\api\node_modules\rollup\dist\shared\rollup.js:18459:9)
    at async Promise.all (index 2)

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

The steps I followed are such:

Clone the repo, dev branch
run ./scripts/setup.ps1

I've been able to narrow the issue down to the yarn build command that runs in tooling/api.
Interestingly, the specific file that produces the error varies each time, I have no idea why.
But each time the issue seems to be the same, namely for some reason rollup tries to interpret a TypeScript file as if it were JavaScript, and it predictably fails.
I have been able to "fix" this issue by removing the resolve plugin in rollup.config.js like so:
    // code omited for brevity
    plugins: [
      commonjs({}),
      // remove the resolve plugin.
      // resolve({
      //   // pass custom options to the resolve plugin
      //   customResolveOptions: {
      //     moduleDirectories: ['node_modules']
      //   }
      // }),
      typescript({
        tsconfig: './tsconfig.json'
      }),
      babel({
        configFile: false,
        presets: [['@babel/preset-env'], ['@babel/preset-typescript']]
      }),
      terser()
    ],
    // code omited for brevity

I have no idea why this works, and I would suspect this could cause all kinds of issues so I'm not submitting a PR.
OS: Windows 10
Node: v14.16.1 (LTS)
Yarn: 1.22.10

I just tried on the same OS, Node.js and Yarn versions and I couldn't reproduce it :( I'll have to close this, a lot of people successfully built the API package, I just think something weird happened on your install.

thank you for taking the time to review this


docs: ADR-0006 sbom merge

6. 0006-sbom-merge.md
Date: 2024-07-29
Status

Proposed
Context

SBOM merge capability should be supported.
Decision

Ability to take one or more SBOMs in different formats into a singular sbom

Merge components that may match on different identifiers (purls, hash, etc …)

Merge component dependencies
Merge component properties

Ability to take a flag to “flatten” any externally referenced SBOMs

Any nested components should be moved to "top level" components and the depends_on section updated to show the dependency.

Consequences

These changes allow end users to easily consolidate multiple SBOMs from a variety of different sources into one while still being agnostic of the SBOM format being used.

Just to document here for whoever ends up working on this, I think an implementation using a Go generic interface would be a clean way to do it.

Basic example
package main

import (
	"fmt"

	"github.com/protobom/protobom/pkg/sbom"
)

type (
	Merger[T any] interface {
		Merge(*T) error
	}

	MergerBase[T any] struct {
		Base *T
		Merger[T]
	}
)

func (*MergerBase[T]) Merge(t *T) error {
	switch any(t).(type) {
	case *sbom.Metadata:
		fmt.Println("Merging metadata")
	case *sbom.Node:
		if _, ok := any(m.Base).(*sbom.Node); !ok {
			// return error
		}

		fmt.Println("Merging nodes")
	case *sbom.NodeList:
		fmt.Println("Merging node lists")
	case *sbom.Person:
		fmt.Println("Merging persons")
	case *sbom.Tool:
		fmt.Println("Merging tools")
	default:
		// return error
	}

	return nil
}

// Enforce implementation of interface at compile time
var _ Merger[sbom.Node] = (*MergerBase[sbom.Node])(nil)

func main() {
	merger := &MergerBase[sbom.Node]{}
	merger.Merge(&sbom.Node{})
}

Go playground link


[3.x] Revert to using laravel-schemaless-attributes for meta_data

In the version 3.x of laravel-event-projector the laravel-schemaless-attributes dependency was removed.
That dependency allowed us to use the following syntax to update an EloquentStoredEvent's meta_data attribute:
$event->meta_data['ip'] = '<IP_ADDRESS>';

This syntax is the one outlined in this package documentation.
With the dependency removal this syntax no longer works and an ErrorException: Indirect modification of overloaded property is thrown when trying to set a key in the meta_data property using the above notation.
This error is due that attributes from an Eloquent Model are retrieved due through the __get magic method and not accessed directly. This is a PHP limitation as it returns a copy of the value instead of a reference to the underlying array.
When using the laravel-schemaless-attributes package an instance of the SchemalessAttributes class was returned which implements the ArrayAccess interface. As objects are returned by reference, the syntax in the snippet above works as expected.
One workaround is to use the following syntax:
$event->meta_data = ['ip' => '<IP_ADDRESS>'];

This will pass a new array to the __set magic method on the EloquentStoredEvent model and it will replace the underlying meta_data attribute.
The downside is if you have multiple places (listeners for example) that can modify the meta_data property. The user should keep track of the previous value to prevent overriding the whole array and loosing previous changes.
I added a test to make sure the documented syntax works. I appreciate if you can review the tests where I have two doubts:

~I needed to use a database raw cast to JSON to compare against the meta_data column in the database~
I added a EloquentStoredEvent::flushEventListeners(); to the end of the test, not sure if that is needed.

I will happily make any changes to improve this test
EDIT I removed the MySQL specific syntax due to tests failing with PostgreSQL

Epilogue
The tests already have a test against manipulating an event's meta_data property, why this PR is needed?
Indeed there are already two tests that test against an event's meta_data modification, but those tests assert against the new StoredEvent class which is a wrapper around the EloquentStoredEvent.
In this new class the meta_data is a first-party property, so it is not accessed through the __get magic method, thus the modification through the offset set syntax is allowed.

Looks good to me! I thought this wasn't necessary anymore but it indeed is when you want to use the  eloquent lifecycle methods to add meta data, thanks!

Great! Thank you a lot


Fix #448 - monkeys don't emit update events

... I separated out the hashPath function into the helpers.js file so it could be also used in monkey.js.
I then went ahead and manually updated the tree._affectedPathsIndex from within monkey.js... This aspect feels hacky as I'm directly updating the private variable of the baobab tree... That said, I did see several other instances updated tree._data and didn't want to take to many liberties restructuring.
Possibly a tree.addAffectedPath() method could be created to abstract away any access to private vars.
So this pull request does work as is, but could possibly be improved upon. Let me know what it needs to be pulled.
Thanks for the great library!

Hello @roark. This feels hacky indeed but seems to be a good fix for the time being. Let me merge and release asap.


[Feature suggestion] Difficulty levels

I don't know if this is possible but I think it would be cool if either 1) The difficulty (&difficulty=) scaled with the balloon level or 2) The difficulty changed depending on actual level difficulty.

added


feat(utils): add verbose logging and tools call command to gptme-util

Add -v/--verbose flag for debug logging
Add 'tools call' command for direct tool function calls

[!IMPORTANT]
Add verbose logging option and tools call command for direct tool function execution in CLI.

CLI Enhancements:

Add -v/--verbose flag in main() for enabling debug logging.
Add tools call command in tools_call() for direct tool function calls with arguments.

Functionality:

tools_call() initializes tools, retrieves specified tool and function, and executes with parsed arguments.
Handles errors for missing tools or functions, listing available options if not found.

This description was created by  for 14746c0f2044c27fbe76cfa921ceca864dfe9807. It will automatically update as commits are pushed.

Codecov Report
Attention: Patch coverage is 28.12500% with 23 lines in your changes missing coverage. Please review.

Project coverage is 72.95%. Comparing base (0fbafd0) to head (14746c0).

Files with missing lines
Patch %
Lines

gptme/util/cli.py
28.12%
23 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #265      +/-   ##
==========================================
+ Coverage   72.40%   72.95%   +0.54%
==========================================
  Files          64       64
  Lines        4211     4241      +30
==========================================
+ Hits         3049     3094      +45
+ Misses       1162     1147      -15

Flag
Coverage Δ

anthropic/claude-3-haiku-20240307
72.05% <28.12%> (-0.35%)
:arrow_down:

openai/gpt-4o-mini
71.91% <28.12%> (?)

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

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

🚨 Try these New Features:

JS Bundle Analysis - Avoid shipping oversized bundles


[QUESTION] Omnivision: Does token compression method results in an inference speedup?

Question or Issue
I read the interesting blog about omnivision: https://nexa.ai/blogs/omni-vision
I have one question on 9x Tokens Reduction through Token Compression.
From the architecture and following writeup We developed a reshaping mechanism in the projection stage that transforms image embeddings from [batch_size, 729, hidden_size] to [batch_size, 81, hidden_size*9]: it seems the number of floating points of visual tokens will remain the same.
I was wondering if this Token Compression method will result in reduction in inference time. Can you please provide an elaborate answer.
Thanks.
OS
No response
Python Version
No response
Nexa SDK Version
No response
GPU (if using one)
No response

@sguru-sam We have reshape

Question or Issue
I read the interesting blog about omnivision: https://nexa.ai/blogs/omni-vision I have one question on 9x Tokens Reduction through Token Compression.
From the architecture and following writeup We developed a reshaping mechanism in the projection stage that transforms image embeddings from [batch_size, 729, hidden_size] to [batch_size, 81, hidden_size*9]: it seems the number of floating points of visual tokens will remain the same.
I was wondering if this Token Compression method will result in reduction in inference time. Can you please provide an elaborate answer.
Thanks.
OS
No response
Python Version
No response
Nexa SDK Version
No response
GPU (if using one)
No response

Hi, it will reduce inference time! So, the computation of the visual encoder and projection part is the same. However, you still need the computation from the decoder part, the language backbone. Previously, your language model needs to handle 729 tokens, now it becomes 81! Thus, it will greatly reduce the complexity for the decoder part, which is also the main computation time.


Lab directions

move hints to above chunks for all labs, but also explain that certain sections like ___ or ``????` would need to be replaced when typed in the chunk

[ ] Intro
[ ] RStudio
[ ] Reproducibility
[ ] Basic R
[ ] Data IO
[ ] Subsetting
[ ] Summarization
[ ] Data classes
[ ] Data cleaning
[ ] Manipulating
[ ] Esquisse
[ ] Data viz
[ ] factors
[ ] Statistics
[ ] Functions


[Question] Explicit declaration of ui-select module's filter for the logical OR

The propsFilter defined in the demo.js file performs the logical OR to all the available data for a dropdown and this is correct, as we actually want to perform a search operation to some data.
According to the fore-mentioned words, we come to a conclusion that this filtering should be available by default in the module. So, is there any specific reason that it isn't or I did I miss something?
TB

It isn't included as there is nothing special about its relation to ui-select. It is just a normal angular filter that happens to be useful for many peoples use cases when it comes to ui-select. However that doesn't mean everyone needs/wants to use it.
Since angular provides this extension point itself, it is left up to users to customise how they wish.

I have not read the code for ui-select and angular, but if this is about sth that is not supported by default and the user has to do an additional action (write a specific filter, for example) in order to implement it, where is the point of the selectization, from a modular perspective?

I suggest maybe you study the code for ui-select. filter and angular, you will see they are unrelated.
I appreciate your input, but for now it is acceptable to provide an example in demo so I'm closing this.


Fix markers remaining in Rails guides

This is probably not ready yet, but was necessary to stop this gem from leaving junk in the Rails guides for me.
For more context, I was experimenting with adding this gem to Rails for linting all of the code samples in our guides. However, when using --autocorrect-all this would leave #<--rubocop/md--> at the beginning of every line and every code block fence.
Happy to clean this up if there is something here, IDK if it's just me.
Additionally, a question I had was with Layout/IndentationConsistency, I've had to disable this cop when using the gem because it will raise for things like:
  \```ruby
  def foo
  end
  \```

It feels like the indentation should match the start of the code fence, but I'm not really sure what's going on there. Would love to learn more! :bow:

I'm also pretty sure the tests will fail, as I've not looked into that yet.

Thanks for the report!
I'd be glad to help in making this gem work with Rails guides. Could you please share the config/script you used to run it against the guides? Is the a PR or branch to take a look at?

It feels like the indentation should match the start of the code fence,

That makes sense. But the plugin works the way that it ignores all source but Ruby code, so we don't have this information available. And I'm not sure we can configure the Indentation cop to use different settings on-the-fly. So, disabling it seems like the only option.

Hey @palkan! Thanks for your reply.
I've opened a PR at rails/rails#47186, still some open questions but hoping we can get it added. :pray:

I checked the PR branch and was able to reproduce the bug:
-```html
+```#<--rubocop/md-->html
 <div class="field_with_errors">
   <input id="article_title" name="article[title]" size="30" type="text" value="">
 </div>

The problem is html+erb syntax hint: our Regexp doesn't recognize it (it doesn't accept +). See  https://rubular.com/r/AycYybvdcBS0QN
Will fix soon.

Fixed and released in 1.2.0. Please, let me know if there are any issues left.

Hey @palkan Thanks for seeing this through!
I've tried my branch with 1.2.0 and ran into some new and interesting failures:
https://github.com/zzak/rails/actions/runs/4059230802/jobs/6987054226
Some of these might be addressable, but will have to look over them more closely in a bit.
Was just surprised to see so many new corrections found. 🤔

Was just surprised to see so many new corrections found.

I checked locally with the latest rubocop-md and see the same-ish number of offenses. I think, we didn't see them before, because the bug was halting the processing of the file as soon as we hit the unsupported md syntax. Now, we see all the problems.

@palkan After fixing all of the remaining issues, my branch is green! (zzak/rails#8)
One interesting thing was this violation only appeared on my branch, this code hasn't changed in years.
https://github.com/zzak/rails/commit/53eb461


Updates

[Enter feedback here]
Azure Security Center should be updated to Microsoft Defender for Cloud.
Also, Microsoft Sentinel is not listed.

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

ID: 47e39a6c-c05c-8c59-c96c-d7aa4d55c40d
Version Independent ID: 9fe0e0db-ca4b-53d1-3980-d204d9996364
Content: Azure Security Services and Technologies
Content Source: articles/security/fundamentals/services-technologies.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @TerryLanfear
Microsoft Alias: terrylan

@angelicafaber
Thanks for your feedback! We will investigate and update as appropriate.


Can't follow readme

use Visual Studio or MSBuild to compile the pytocs.sln file

I have cloned and there are no *.sln files

Have you looked in the src (source directory) where such files are traditionally put?


Implementation detail: What does finding library spectrum index mean for the a library reader?

We have three explicit unique identifiers for a library spectrum: key, name, and index.

The key is supposed to be a stable numeric identifier, akin to a "primary key" in a database, where the cardinality of the key is historical rather than positional. In theory, should you re-order a library, the key doesn't change.
The name is a theoretically human readable name that describes the spectrum chosen by its creator, which means that it is essentially free text when not stipulated by the source format (e.g. MSP). It should be unique too, leaving it up to the creator to figure out how to make it clear to a human.
The index is supposed to be an externally "unstable" identifier for a spectrum within the library, specifying an ordinal number starting from 0. As read, should you re-order a library, the index does change.

When reading a library, the parser "knows" how many spectra preceded the spectrum it is currently parsing, and so it can automatically "fill in" the index attribute and the authors of a library needn't include it. However, we have explicitly written that it may be included in the output:

Optionally, a library spectrum index (MS:1003062) MAY be included to refer to the ordered position of the spectrum within the library, starting with 0 for the first spectrum. A library spectrum may have its index changed as the library evolves, and therefore SHOULD only be used internally by the library management software (e.g. for random access retrieval). To refer to a library spectrum unambiguously from outside (e.g. using a Universal Spectrum Identifier), the library spectrum key MUST be used.

Should that mean that if a parser reads an index attribute, it's obligated to store it and round-trip it, while also generating its own internal index separately? This is undefined behavior, according to one reading of the spec. Another more restrained reading might suggest that the value index refers to is never actually taken from the source file verbatim but inferred, and so any read value should be ignored because it constitutes information external to the layout of the library itself.
[Term]
id: MS:1003062
name: library spectrum index
def: "Integer index value that indicates the spectrum's ordered position within a spectral library. By custom, index counters should begin with 0." [PSI:PI]
is_a: MS:1003234 ! library spectrum attribute
relationship: has_value_type xsd:integer ! The allowed value-type for this CV term

Suppose we parse this:
<Spectrum=3>
MS:1003062|library spectrum index=0
...
<Spectrum=1>
MS:1003062|library spectrum index=1
...
<Spectrum=4>
MS:1003062|library spectrum index=1000

The first two entries' index attributes match their true coordinates in the sequence of library spectra, but the third spectrum's index is totally different (2 vs. 1000). What should the parser do? I'd argue that it is context-dependent.
If I were writing a spectrum viewing application, I'd theoretically include the index in the text rendering of the spectrum so that the user knows where in the file an entry is. If I then parsed that text back into the program, I'd probably want to respect that value because I wouldn't know if I were just passing that object around to just be shown elsewhere (e.g. sent to a web app to be rendered again, or passed around via federated PROXI requests) where that index information is just as salient as if it were presented locally. I'd treat that index value as something to display, but it'd be ignored for the purposes of actually looking that single spectrum up again.
However, were I writing a library manipulation tool that's not so interactive, I'd probably say "any buffer of one or more spectra constitutes a single library" and want that library to be internally consistent and ignore the input index value. After all, if the user wants to split a library transform parts differently, and re-merge them, they'll just get re-indexed anyway. Especially if the user merges two separate libraries, not slices of the same library.
Can we say explicitly which reading is more accurate, or that both usages are acceptable and it is up to the implementer to choose which way to go?

I don't think I understand exactly what the two options here are. Can you state them a bit more clearly?
I am thinking: if software tool X is not sure that it generated a particular index value itself (i.e. it came from somewhere else or there is doubt), then software tool X is not under any obligation to preserve that index value, and may freely replace the value with whatever value it thinks is appropriate for its library management needs.

This is described on page 16 of the current spec, so this is fine. closing.


Add Plain Text code sample for tests

Add Plain Text code samples for tests on analyzer and scanner

E ae, @JoaoDanielRufino
The samples need to be added to this folder? https://github.com/JoaoDanielRufino/gcloc/tree/master/test/fixtures/code_samples
Do you prefer .txt files or no extension at all?
Thanks!

E ae, @JoaoDanielRufino
The samples need to be added to this folder? https://github.com/JoaoDanielRufino/gcloc/tree/master/test/fixtures/code_samples
Do you prefer .txt files or no extension at all?
Thanks!

Yes, on that folder!
You could use the .txt. extension, thanks.
You have 5 days to work on this, owtherwise I will unassign you


Link to pretrained networks broken

It seems that the primary source to the pretrained networks is unavailable (https://bit.ly/cfnet_networks)
If you have the weights, could you please upload them elsewhere?
Thanks!

I found a link to the weights here under pre-trained networks: http://www.robots.ox.ac.uk/~luca/cfnet.html

@cheripai Thanks for pointing this out. The link of pre-trained networks has been updated.


feat: Add poc for custom methods registration

@askolesov Great POC, thanks.
Let's expand on this logic & as described on the comments, following today's discussion.


Question about muzero network in go game

In paper, a bigger 32 layer network in the large-scale 19x19 Go experiments. The networks used 256 hidden planes, 128 bottleneck planes and a broadcasting block in every 8th layer.
Muzero have representation, dynamics, and prediction.  Representation, dynamics, and prediction all use this 32 layer network? Should  representation, dynamics, and prediction use same size network or different size network?
Paper saids Muzero learn fast than alphazero in go. But if they has same size network,  then Muzero is 2 times slower than alphazero. Because every move Muzero need two network,  and alphazero only need one. (if representation, dynamics, prediction, alphazero has same size network) . So alphazero should learn fast than muzero?
If alphazero use a bigger network, every inference time equal to Muzero's two network inference time,  in ths case, can muzero outperform alphazero?
Muzero training go use K = 5 steps,  I found that the larger the value of K, the more GPU memory it consumes.  Is there a big difference between training with k=3 and training with k=5?

The prediction network usually can be smaller. It serves as the output layer.
I do not have answers to these empirical questions. Maybe look at some existing MuZero implementations.


feat: direct contract call with dynamic link

Description

Closes #144, https://github.com/line/cosmwasm/pull/151
It's a poc implementation.
Gas consumption, security checks, unit tests, CI, etc. need to be checked.
I will change from a draft PR to a full PR once production work is complete.
Types of changes

[ ] Bug fix (changes which fixes an issue)
[x] New feature (changes which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] ETC (build, ci, docs, perf, refactor, style, test)

Checklist

[ ] I followed the contributing guidelines.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] The PR title and commits are followed conventional commit form.

 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.

I changed the target branch and registered it as a new PR.
https://github.com/line/wasmvm/pull/55


Instrumentation Test Typo

https://developer.android.com/codelabs/android-basics-kotlin-write-instrumentation-tests?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-2-pathway-2%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fandroid-basics-kotlin-write-instrumentation-tests#3
In which task and step of the codelab can this issue be found?
4. Writing Your First Instrumentation Test
Describe the problem
On Step 3 the sample code is on one line when it should be on two lines
How it's displayed:
@get:Ruleval activity = ActivityScenarioRule(MainActivity::class.java)

How it should be displayed:
@get:Rule
val activity = ActivityScenarioRule(MainActivity::class.java)

Apologies, handled in https://github.com/google-developer-training/android-basics-kotlin-tip-calculator-app-solution/issues/265


Circular crop parameter

Pass to configurations an option to make a circular crop (0 or 1), as it can be used to profile photos. Then the crop preview will be circular.

Should the produced picture should still be rectangular?
(In general there is a reason we use issue templates like https://github.com/apache/cordova-plugin-camera/issues/new?template=FEATURE_REQUEST.md - issues using those have a much bigger chance to be taken into account)

Yes, the result will be rectangular

just the design as circle

This is not possible on iOS and probably not possible on Android neither, so going to close


Fine grained access tokens

Feature Description
I believe it would be a good feature if users could fine grain their access tokens. This would make it possible to limit what is possible with a specific token and introduce an additional layer of security.
Especially now that we have more features within gitea than just git management this would be a very neet addition.
Screenshots
No response

Duplicate of #8960

Yes but I would suggest to either make the other issue more specific or to keep this one.
Thinks like what packages registries can a token be used for and what action can be used with an token. So it's not only for read only access.
If you think this is being stated in  https://github.com/go-gitea/gitea/issues/8960 then feel free  to close this issue.

No everything fine. Just wanted to link the other issue.

Just for clarification, as I might have run into an issue here: I have configured a mirror repo to pull clone a github repo in my account, using the "new"/beta fine-grained access token (instead of classical tokens).
When setting up the repo in gitea, everything works perfectly and the inital pull is fast. However, the automatic cron pull as well as the manual pull fail complete silently:

The user initiating the pull manually receives the message that the repos will be synced
The cron is marked as "last run at..."
However, in both cases, no sync actually takes place!

As I'm rather new to gitea, I finally stumbled upon the admin logs which are spammed with messages looking like this:
Failed to update mirror repository '<REDACTED>': fatal: could not read Username for 'https://github.com':
terminal prompts disabled
error: could not fetch origin

I have set tup the personal access tokens with read-only permissions and only allow access to that specific repo on Github. As the inital setup with the token worked, I was very surprised that the mirror updates fail afterwards.
Just as clarification for me: are the new Github "fine grained access tokens" fully supported yet? If so, which of the repo access rights (https://docs.github.com/en/rest/overview/permissions-required-for-fine-grained-personal-access-tokens?apiVersion=2022-11-28) are mandatory to work for a read-only pull mirror? Do I actually need to set some of them to write permissions (which I would like to avoid)?

@TheDom42 What you are describing is totally different than what this issue is about.

Sorry, I must have completely misinterpreted the term "Fine grained access token". I thought this was specifically referring to the Github feature and thought that this issue was maybe about the fact that they are not yet supported by Gitea. I will move the described problem to a new one.

Resolved by #20908


copy padding to hidden textarea

In chrome width setted incorectly, this patch fixing it.
But still has problem on mobile chrome.

Thanks for the contribution :+1:
I believe the padding should be taken care of here:
https://github.com/monospaced/angular-elastic/blob/master/elastic.js#L66
and then there
https://github.com/monospaced/angular-elastic/blob/master/elastic.js#L150
Would you be able to provide a plunkr or similar showing this Chrome padding issue in action?

I noticed that if you change the padding during the lifetime of the textarea, then angular-elastic doesn't take the new padding into account.

I think this is related #101 I applied the fix in my repo and the height are now good.


Losing state on hot reload or otherwise triggered rebuild of entire app

This issue is quite common. We should also add it to documentation as a tip.

The solution is to move your BeamerRouterDelegate to a final variable outside build.
class MyApp extends StatelessWidget {
  final _routerDelegate = BeamerRouterDelegate(
    locationBuilder: ...
  );

  @override
  Widget build(BuildContext context) {
    return MaterialApp.router(
      routeInformationParser: BeamerRouteInformationParser(),
      routerDelegate: _routerDelegate,
      ...
    );
  }
}

Hi @slovnicki
In your opinion, is it okay if I want to add more locations at runtime, like enabling some features by activating an option in the settings?
I also encountered the same issue with you, even tested with example from beamer packages.

In your opinion, is it okay if I want to add more locations at runtime, like enabling some features by activating an option in the settings?

Sorry for late response @lam-nv, haven't notice this here. Yes, I think this should be fine.

Beware that https://github.com/slovnicki/beamer/issues/193#issuecomment-821095836 will not help if you're on web and flutter >2.0.6 because of https://github.com/flutter/flutter/issues/79241

Hi @slovnicki !
I got several pages one has bottom navigation so it has its own beamer and BeamerRouterDelegate. Even if I put BeamerRouterDelegate on tabpage outside of build it loses its state and redirects to not found anyway. Is there a workaround for this ? Here an example  .
this is where app runs from
`class App extends StatelessWidget {
final routerDelegate = BeamerDelegate(
locationBuilder: BeamerLocationBuilder(
beamLocations: [
SplashLocation(),
OnboardingLocation(),
GroupTabWrapperLocation()
],
),
guards: [
BeamGuard(
pathBlueprints: ['/'],
check: (context, location) => context
.read(onboardingProvider.notifier)
.isOnboardingComplete,
beamToNamed: '/onboarding',
),
],
);
@override
Widget build(BuildContext context) {
return MaterialApp.router(
debugShowCheckedModeBanner: false,
routerDelegate: routerDelegate,
routeInformationParser: BeamerParser(),
backButtonDispatcher: BeamerBackButtonDispatcher(
delegate: routerDelegate,
),
);
}
}
`
and this is Tab Page with bottom navigation bar
`class GroupTabWrapperPage extends StatelessWidget {
// final String id;
GroupTabWrapperPage() : super();
static GlobalKey beamerKey = GlobalKey();
static const uri = '/groupTabWrapper';
final _routerDelegate = BeamerDelegate(
locationBuilder: BeamerLocationBuilder(
beamLocations: [
FeedLocation(),
SearchLocation(),
InboxLocation(),
ProfileLocation()
],
),
);
@override
Widget build(BuildContext context) {
return Scaffold(
body: Beamer(
key: beamerKey,
routerDelegate: _routerDelegate,
),
bottomNavigationBar: BottomNavigationBarWidget(
beamerKey: beamerKey,
),
);
}
}`

Hi @oyont
Could this be because you're using flutter version >2.0.6 as pointed out in this comment above?

My flutter version is 2.2.0 but I'm running the app on web. It's happening on mobile too

This is in README so I'll close

Just curious about this issue of losing state on rebuild :

I experienced the same issue and resolved it using the comment #193(comment) in flutter 2.5.0.
Then reading down the thread this comment from you to @oyont

Conclusion
Why do you suggest that this issue is experienced because @oyont  is using flutter version >2.0.6 ??.... kindly can you suggest a way forward

Can be this thread reopened? I've the same issue but moving BeamerDelegate to a final property does not work

I'm also have this same issue

same issue :(


[Docs] Minor changes suggestion in getting started steps in README to avoid potential bug when starting up

Hi!
First of all, awesome template thanks for sharing this 🙏
I cloned the repo, installed the dependencies and ran the dev server and the first thing that displayed on the screen was the following error:

Turns out I had forgotten to create a .env.local file to enable the environment variables and since they're used in some <Link> components it resulted in this error. I thought "my bad" but also that maybe I could suggest a minor change to the README to move this step up and clarify it in the "Getting started" section as it can be forgotten if not specified clearly:

[...]
Getting started
The easiest way to try this starter is to run it locally on your computer.
First, you'll need to create your own copy of this starter. You can do so by clicking the "Use this template" button on GitHub and filling out the form.
Once you've cloned the repository, create a .env.local file to setup the environment variables, you can reuse the default  variables or change them as you will:
cp .env.example .env.local

Then install dependencies and start the Next.js server:
[...]

I didn't know if this repo was open to outside contributions so I didn't create a PR for this but I can open one if you think this small change is relevant 🙃
PS: Also the "Use this template" link leads to a 404, it doesn't seem that the repo has been defined as a template repo yet.
Anyway thanks again for this starter it's great! 👍

Hey there @clairechabas thanks for reporting these issues! Feel free to open PRs to fix this contributions are super welcome! If you can't I'll push a fix on our end :)
@orliesaurus I just pushed a fix to the template link issue you mentioned and am looking into the markdown fix too 🙌


PrettyConfig::new() not found when referenced by crate

Although the examples in the RON crate itself work fine, the example encode.rs fails if I create my own project which uses RON. The compiler cannot find the new() function. E.g:
let pretty = PrettyConfig::new()
^^^ function or associated item not found in ron::ser::PrettyConfig
I did include the following dependencies in Cargo.toml :
ron = "0.5.1"
serde = { version = "1", features = ["serde_derive"] }
serde_json = "1"
And copied the file ../ron/examples/decode_file.rs to the main.rs of my project. All other three examples works, but this ones fails. What is wrong?

The examples in master are written against the code of master. If you need example code for "0.5.1" version, you can find them in the relevant source cached by the docs.rs: https://docs.rs/crate/ron/0.5.1/source/examples/encode.rs

Okay, solved.


Allow 6-digit color spec w/o #

This PR takes a minimalist approach to addressing issue #1657. This does not completely change the color specification syntax to align with the color package or the xcolor package. It does not accommodate RGB notation or a cmyk color model.  It does, however, allow a 6-digit HTML color specification to pass without a leading # symbol, as in xcolor's HTML color model.

The latest commit revises the RegEx pattern as recommended by @ylemkimon. (Thanks!) This simplifies the code but it does not raise a parse error on a mis-typed predefined color name. \color{cherry} will render in black.
I'd like to raise an error on a mis-typed predefined color name, but the only way I can think to accomplish that is via a RegEx pattern that enumerates all 150 of the HTML predefined colors. Is that something I should do?

I'd like to raise an error on a mis-typed predefined color name, but the only way I can think to accomplish that is via a RegEx pattern that enumerates all 150 of the HTML predefined colors. Is that something I should do?

I think it is impossible without access to DOM APIs and there is no need to check the color name is valid.

Just wanted to come in here and say thanks for this!


[dxvk] Handle divide by zero when determining slice count

Fixes crash when making a zero-sized buffer.
May help #1138

As discussed on Discord, this is bollocks - creating buffers of a size of zero is illegal and should be fixed properly.


Timeout requesting block status

Have been mining for a while with latest release, and keep getting timeout requesting block status 3 times before every new block.

This appears to be pool-specific particularly with current network state.  I'll add a feature to make this configurable to increase timeouts.


no "Player leave" notification od Discord

There is no information about player left from server by logout.
When kicked, notification is present.

What version of discord connector are you using? What other mods are you using?

Is there any error message in the log when the player leaves ?

nowy 1.txt
Kto ma dostęp
Nieudostępniony
Właściwości systemowe
Typ elementu
Tekst
Rozmiar
737 bajtów
Zajęte miejsce
737 bajtów
Lokalizacja
VALHEIM
Właściciel
ja
Zmodyfikowano
22:48 przeze mnie
Otwarty
22:49 przeze mnie
Utworzono
22:48 w aplikacji Google Drive Web (Unverified)
Dodaj opis
Przeglądający mogą pobierać
11/07/2022 22:47:28: PlayFab network error in session 'wincls-valheim' and network 2e4a179c-cfe5-43f4-8ee4-9dacd055de8a|AwAuaHWp/mPWVm0C2keqUorieWEOVFdlc3RFdXJvcGUAAAAAAAAAAAAAUXZkEL9Xa34rfnIgJk1n6olEkKykili28X3MawG4mvIpb0pkbnM4MWU1LTkyNTdkZWYxLWM1MTctNDkyZC1hZDNkLTE1Y2RjMjQ2Zjg1ZS53ZXN0ZXVyb3BlLmNsb3VkYXBwLmF6dXJlLmNvbQ==: the operation was called with an invalid handle
the operation was called with an invalid handle
11/07/2022 22:47:28: Failed to send, suspend TX on playfab/32D20C9BB52FA743 while trying to reconnect
Failed to send session data. Error: /Event/WriteTelemetryEvents: The requesting entity is not authorized to write events with namespace playfab.party. Allowed namespaces can be 'custom' or begin with 'custom.'.

DiscordConnector doesn't do anything with PlayFab.party or anything like that besides looking up the socket hostname, which is a read and not write error. Based on the log snipped you posted, I think it's most likely that some other mod is causing an error when the player is leaving; and that mod isn't doing anything when players are kicked. Could it be something with server-side characters and server sync stuff?
When you added 2.0.2, did you update any other mods?

I never saw leave notification.
Propably problem witch ServerCharacters or AzuAntiCheat - these mods use Discord info too.

I checked and without ServerCharacters or AzuAntiCheat, notification about player leave is present but if one of there mods are, this info gone. No matter what mod - there is no information about Player leave on ServerCharacters and/or AzuAntiCheat.
If it will be problem with one of these mods i will ask author for checking compatibility with DiscordConnector but in these case - when with any of these mods, the problem is present, I would like to ask you for checking what is problem because DiscordConnector isn't compatible with two very nice server-side mods


[5.3] Update LengthAwarePaginator.php

Hi there.
New to Laravel, 3 weeks in and absolutely love it.
Ran into minor problem using multiple LengthAwarePaginators on a single page with alternate pageName properties. Traced problem to the attached proposed change.
When checking the current page for a LengthAwarePaginator instance, any non-default pageName is not sent to resolveCurrentPage and as such 1 is always returned (unless pageName of 'page' is used.
Andrew

Hello @jivemonkey2000, can you please provide more details about this issue? How can I replicate it in a fresh laravel 5.3 installation?

ping @jivemonkey2000

Hi @themsaid, sorry, only just got a notification of reply.
Add the following to the base / route:
use Illuminate\Pagination\LengthAwarePaginator;
use Illuminate\Pagination\Paginator;

$collection = collect(['this','is','a','collection','of','items']);
$pageName = 'foo';
$perPage = '5';
$path = '/';

$paginator = new LengthAwarePaginator(
    $collection->forPage(Paginator::resolveCurrentPage($pageName),$perPage),
    $collection->count(),
    $perPage,
    null,
    ["path"=>$path, 'pageName' => $pageName]
);

dd($paginator);

Then, navigate to /?foo=2 you'll see:
LengthAwarePaginator {#170 ▼
  #total: 6
  #lastPage: 2
  #items: Collection {#176 ▶}
  #perPage: "5"
  #currentPage: 1
  #path: "/"
  #query: []
  #fragment: null
  #pageName: "foo"
}

The current page is returning 1, even though the pageName for storing our page number is foo. If we change the request to /?page=2 we then do get the correct currentPage value - but this is what I believe to be incorrect as we have specified a non-default value for the pageName.
I also believe this may also be applicable to Illuminate\Pagination\Paginator but I've yet to check.
Thanks.

Thanks.

You're welcome. Keep up the great work.


Enable Overriding extension

This PR is merely copying files from the DTDL repo into opendigitaltwins-dtdl.  Let's pick up this review in a PR on the DTDL repo: https://github.com/Azure/DTDL/pull/151


refactor(refactor breadcrumb): refactor breadcrumb with composition api

🤔 这个 PR 的性质是？

[x] 重构

🔗 相关 Issue

💡 需求背景和解决方案
使用 Composition  API 重构 Breadcrumb组件
📝 更新日志

[ ] 本条 PR 不需要纳入 Changelog

☑ 请求合并前的自查清单
⚠ 请自检并全部勾选全部选项。⚠

[x] 文档已补充或无须补充
[x] 代码演示已提供或无须提供
[x] TypeScript 定义已补充或无须补充
[x] Changelog 已提供或无须提供

跑一下npm run test:update

Codecov Report

:exclamation: No coverage uploaded for pull request base (compositionAPI@e15937b). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head ea84aaf differs from pull request most recent head a125a65. Consider uploading reports for the commit a125a65 to get more accurate results

@@                Coverage Diff                @@
##             compositionAPI     #567   +/-   ##
=================================================
  Coverage                  ?   64.42%
=================================================
  Files                     ?      390
  Lines                     ?    13619
  Branches                  ?     2523
=================================================
  Hits                      ?     8774
  Misses                    ?     4598
  Partials                  ?      247

Continue to review full report at Codecov.

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


Use environment variables and fallback variables

Allows for more flexible configuration and fewer changes in files like docker-compose.yaml.

Self-reviewed


City DB format

For the city db, the old .dat format is still used while for the domain db the new mmdb one is used.
Could the implementation be changed to use the new mmdb format for both databases?
The old .dat format also doesn't have all data in there (DESY squids are not correctly mapped).

And in fact the old .dat format is no longer supported and can't be downloaded anymore.  An update to the GeoLite2 .mmdb format is required.
The cvmfs-server package has code for downloading and keeping up to date a copy of GeoLite2-City.mmdb.  For the wlcg-wpad package I just depended on that.

And this is now blocking me so unless you say you're working on this or have already done it, I'll develop a PR for it.

We found that some sites where not correctly mapped to a location, e.g DESY. It was the same in the mmdb as well as dat files we tested. Solution for us so far was to use the CVS version which can be edited easily (e.g. automated), and then convert to dat, which also allows to keep the old interface so far.
@colsond would know what the status of the native mmdb implementation is.

I have not noticed any differences between the GeoLite2-City .csv and .mmdb files.  If you can give me a specific example I would like to know about it.  As far as I understand it they generate the two formats from the exact same data.
I have had very good luck with submitting change requests to maxmind through the standard web form.  They never reply and say they're going to make the change, but when I check a few weeks later the changes are there.

That is correct that all formats that can be downloaded have the same content. However, adding/fixing entries using the cs files is easy and can be automated too. And if using the csv anyway, we can convert to dat and still use that format. But I agree that shoal currently uses a mix of mmdb and dat and that should be consistently be mmdb.
When DESY registered with shoal, their IP range was missing in the db and no location mapped; and it seems it still seems to be the case (a year later).That was the initial reason to switch to csv and converting to a usable format after editing.

If you know what the correction for DESY is, please submit it to maxmind.  I have so far been able to avoid having any mechanism for applying local corrections because of that.

The new mmdb format is used now. We test the new version, updated to CentOS7, and will make it available then.

issue solved with the new shoal version


JWT plugin does not like custom secret beginning with "$"

Summary
While building a custom auth system based on JWTs signed by bcrypt-hashed passwords, I discovered that while the JWT plugin works fine for verifying against all kinds of custom secrets, it always returns "Invalid signature" when verifying against a secret beginning with the $ (dollar-sign) character (such as is generated by bcrypt-hashing). Important to note: I am using a heavily customised Kong (openresty compiled from source, extra nginx modules, custom-created .debs with FHS layouts, patched configs/templates, etc), but have made no modifications to any kong plugins (or kong at all, other than the config-templates), and I went to great pains to isolate that the problem is happening below the server-level, on the plugin-level, and does so even in a minimal context. I have been running it with other plugins (key-auth, CORS, request transformer) in production for months without problem. If necessary I could try to find somewhere to install a vanilla Kong to test, but that would probably take much longer than for someone else to reproduce from the below steps on an existing install (please?). Also, I verified a jwt (signed by a secret starting with $) at http://jwt.io as valid, but the same jwt was deemed invalid in kong. If someone could point me to which part of the plugin's lua code deals with the decoding/validating of jwt's I might be able to help debug more quickly...
Steps To Reproduce

add an api
add jwt plugin to an api
add consumer
add/update jwt-cred to consumer with custom secret (long, short, whatever, but not beginning with $)
sign a jwt using that cred
request against the api with that jwt (success)
do steps 3 to 5 with lots of variations (success)
update that jwt-cred to set a custom secret beginning with $
sign a jwt using that secret
request against the api with that jwt (fail)

Additional Details & Logs

Kong version

0.9.3

Kong debug-level startup logs2016/12/15 18:51:23 [verbose] Kong: 0.9.3
2016/12/15 18:51:23 [debug] ngx_lua: 10006
2016/12/15 18:51:23 [debug] nginx: 1011002
2016/12/15 18:51:23 [debug] Lua: LuaJIT 2.1.0-beta2
2016/12/15 18:51:23 [verbose] no config file found at /usr/local/etc/kong.conf
2016/12/15 18:51:23 [verbose] reading config file at /usr/local/etc/kong/kong.conf
2016/12/15 18:51:23 [debug] admin_listen = "[::]:8101"
2016/12/15 18:51:23 [debug] anonymous_reports = false
2016/12/15 18:51:23 [debug] cassandra_consistency = "ONE"
2016/12/15 18:51:23 [debug] cassandra_contact_points = {"<IP_ADDRESS>"}
2016/12/15 18:51:23 [debug] cassandra_data_centers = {"dc1:2","dc2:3"}
2016/12/15 18:51:23 [debug] cassandra_keyspace = "kong"
2016/12/15 18:51:23 [debug] cassandra_port = 9042
2016/12/15 18:51:23 [debug] cassandra_repl_factor = 1
2016/12/15 18:51:23 [debug] cassandra_repl_strategy = "SimpleStrategy"
2016/12/15 18:51:23 [debug] cassandra_ssl = false
2016/12/15 18:51:23 [debug] cassandra_ssl_verify = false
2016/12/15 18:51:23 [debug] cassandra_timeout = 5000
2016/12/15 18:51:23 [debug] cassandra_username = "kong"
2016/12/15 18:51:23 [debug] cluster_listen = "<IP_ADDRESS>:7946"
2016/12/15 18:51:23 [debug] cluster_listen_rpc = "<IP_ADDRESS>:7373"
2016/12/15 18:51:23 [debug] cluster_profile = "wan"
2016/12/15 18:51:23 [debug] cluster_ttl_on_failure = 3600
2016/12/15 18:51:23 [debug] custom_plugins = {}
2016/12/15 18:51:23 [debug] database = "postgres"
2016/12/15 18:51:23 [debug] dns_resolver = "<IP_ADDRESS>"
2016/12/15 18:51:23 [debug] dnsmasq = false
2016/12/15 18:51:23 [debug] dnsmasq_port = 53
2016/12/15 18:51:23 [debug] log_level = "debug"
2016/12/15 18:51:23 [debug] lua_code_cache = "on"
2016/12/15 18:51:23 [debug] lua_package_cpath = ""
2016/12/15 18:51:23 [debug] lua_package_path = "?/init.lua;./kong/?.lua"
2016/12/15 18:51:23 [debug] lua_ssl_verify_depth = 1
2016/12/15 18:51:23 [debug] mem_cache_size = "128m"
2016/12/15 18:51:23 [debug] nginx_daemon = "on"
2016/12/15 18:51:23 [debug] nginx_optimizations = true
2016/12/15 18:51:23 [debug] nginx_worker_processes = "auto"
2016/12/15 18:51:23 [debug] pg_database = "kong"
2016/12/15 18:51:23 [debug] pg_host = "<IP_ADDRESS>"
2016/12/15 18:51:23 [debug] pg_password = "******"
2016/12/15 18:51:23 [debug] pg_port = 5432
2016/12/15 18:51:23 [debug] pg_ssl = false
2016/12/15 18:51:23 [debug] pg_ssl_verify = false
2016/12/15 18:51:23 [debug] pg_user = "kong"
2016/12/15 18:51:23 [debug] prefix = "/usr/local/share/kong/"
2016/12/15 18:51:23 [debug] proxy_listen = "[::]:8100"
2016/12/15 18:51:23 [debug] proxy_listen_ssl = "[::]:8443"
2016/12/15 18:51:23 [debug] serf_path = "/usr/local/bin/serf"
2016/12/15 18:51:23 [debug] ssl = true
2016/12/15 18:51:23 [debug] ssl_cert = "/etc/letsencrypt/live/olathens.org/fullchain.pem"
2016/12/15 18:51:23 [debug] ssl_cert_key = "/etc/letsencrypt/live/olathens.org/privkey.pem"
2016/12/15 18:51:23 [debug] ssl_only = "on"
2016/12/15 18:51:23 [verbose] prefix in use: /usr/local/share/kong
2016/12/15 18:51:23 [verbose] preparing nginx prefix directory at /usr/local/share/kong
2016/12/15 18:51:23 [verbose] saving serf identifier to /usr/local/share/kong/serf/serf.id
2016/12/15 18:51:23 [debug] searching for OpenResty 'resty' executable
2016/12/15 18:51:23 [debug] /usr/local/bin/resty -V: 'nginx version: openresty/<IP_ADDRESS>'
2016/12/15 18:51:23 [debug] found OpenResty 'resty' executable at /usr/local/bin/resty
2016/12/15 18:51:23 [verbose] saving serf shell script handler to /usr/local/share/kong/serf/serf_event.sh
2016/12/15 18:51:23 [verbose] running datastore migrations
2016/12/15 18:51:23 [verbose] migrations up to date
2016/12/15 18:51:23 [verbose] serf agent not running, deleting /usr/local/share/kong/pids/serf.pid
2016/12/15 18:51:23 [debug] checking 'serf' executable from 'serf_path' config setting
2016/12/15 18:51:23 [debug] /usr/local/bin/serf version: 'Serf v0.8.0'
2016/12/15 18:51:23 [debug] starting serf agent: nohup /usr/local/bin/serf agent -profile 'wan' -rpc-addr '<IP_ADDRESS>:7373' -event-handler 'member-join,member-leave,member-failed,member-update,member-reap,user:kong=/usr/local/share/kong/serf/serf_event.sh' -bind '<IP_ADDRESS>:7946' -node 'node01_<IP_ADDRESS>:7946_465a78ad93cc432ea8369824d49506d6' -log-level 'err' > /usr/local/share/kong/logs/serf.log 2>&1 & echo $! > /usr/local/share/kong/pids/serf.pid
2016/12/15 18:51:23 [verbose] waiting for serf agent to be running
2016/12/15 18:51:23 [debug] sending signal to pid at: /usr/local/share/kong/pids/serf.pid
2016/12/15 18:51:23 [debug] kill -0 `cat /usr/local/share/kong/pids/serf.pid` >/dev/null 2>&1
2016/12/15 18:51:23 [verbose] serf agent started
2016/12/15 18:51:23 [verbose] auto-joining serf cluster
2016/12/15 18:51:23 [verbose] no other nodes found in the cluster
2016/12/15 18:51:23 [verbose] registering serf node in datastore
2016/12/15 18:51:23 [verbose] cluster joined and node registered in datastore
2016/12/15 18:51:23 [debug] searching for OpenResty 'nginx' executable
2016/12/15 18:51:23 [debug] /usr/local/sbin/nginx -v: 'nginx version: openresty/<IP_ADDRESS>'
2016/12/15 18:51:23 [debug] found OpenResty 'nginx' executable at /usr/local/sbin/nginx
2016/12/15 18:51:23 [debug] starting nginx: /usr/local/sbin/nginx -p /usr/local/share/kong -c nginx.conf
2016/12/15 18:51:24 [debug] nginx started
2016/12/15 18:51:24 [info] Kong started

Kong error logs2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:48: load_plugins(): Discovering used plugins
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: syslog
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: ldap-auth
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: rate-limiting
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: correlation-id
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: jwt
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: runscope
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: tcp-log
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: http-log
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: hmac-auth
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: response-transformer
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: basic-auth
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: key-auth
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: request-transformer
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: acl
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: oauth2
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: galileo
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: udp-log
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: cors
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: file-log
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: ip-restriction
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: request-size-limiting
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: ssl
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: datadog
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: loggly
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: statsd
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: response-ratelimiting
2016/12/15 18:51:23 [debug] 21290#21290: [lua] kong.lua:74: load_plugins(): Loading plugin: bot-detection
2016/12/15 18:51:23 [notice] 21290#21290: using the "epoll" event method
2016/12/15 18:51:23 [notice] 21290#21290: openresty/<IP_ADDRESS>
2016/12/15 18:51:23 [notice] 21290#21290: built by gcc 4.9.2 (Debian 4.9.2-10)
2016/12/15 18:51:23 [notice] 21290#21290: OS: Linux 3.16.0-4-amd64
2016/12/15 18:51:23 [notice] 21290#21290: getrlimit(RLIMIT_NOFILE): 65536:65536
2016/12/15 18:51:23 [notice] 21303#21303: start worker processes
2016/12/15 18:51:23 [notice] 21303#21303: start worker process 21304
2016/12/15 18:51:23 [debug] 21304#21304: REAPER: start reaper memstore message with tick time of 5 sec
2016/12/15 18:51:23 [debug] 21304#21304: REAPER: start reaper memstore nobuffer message with tick time of 2 sec
2016/12/15 18:51:23 [debug] 21304#21304: REAPER: start reaper chanhead with tick time of 4 sec
2016/12/15 18:51:23 [debug] 21304#21304: REAPER: start reaper chanhead churner with tick time of 10 sec
2016/12/15 18:51:23 [debug] 21304#21304: MEMSTORE:00: init memstore worker pid:21304 slot:0 max workers :1 or 1
2016/12/15 18:51:23 [debug] 21304#21304: MEMSTORE:00: found my procslot (ngx_process_slot 0, procslot 0)
2016/12/15 18:51:23 [debug] 21304#21304: MEMSTORE:00: shm: 00007FE9D20FFB50, shdata: 00007FE9C0720000
2016/12/15 18:51:23 [debug] 21304#21304: WEBSOCKET_PUBLISHER:init WS publisher llist
2016/12/15 18:51:23 [debug] 21304#21304: THINGCACHE: init fd_cache 00007FE9D2106300

Kong configuration (registered APIs/Plugins & configuration file)

Test was done on empty test API with only the JWT plugin activated. If parts of the server-configuration are needed I can spam you with them on request, but I suspect it isn't relevant. As for kong-configs, it seems that is covered by the debug startup log output above anyway.

Operating System

Debian Jessie

I forgot to mention the obvious - that I encountered this problem while using the HS256 algo. I haven't even used RS256 yet, but at some point later on will migrate to that. Having drilled down a bit, I can see at this point in the parser-code that it doesn't seem to do any weird data-massaging before passing the the secret to luacrypto for verification, so I wonder if something is happening at this point in the handler code. The dao doesn't look like it does anything strange though, so I think it is getting to a low-and-messy enough point that I will wait to hear what others suggest before trying to dig any deeper. For now I am using a workaround of just chomping the leading $ from secrets when signing and verifying JWTs.

Due to some recent work with the JWT plugin I decided to give this a try. I used a secret of "$abcdefghaijklmn" with HS256 and can't reproduce this issue. I'm running the current state of the repo built from source as my testing instance. It is possible that this there is some other edge case at play here or this is no longer an issue with the current version of Kong.

Having not had the opportunity to use Kong for a while now, I would expect a lot has changed under the hood, and would be surprised if whatever bug this was has not been at least partially impacted/corrected by now, even if not directly intentionally. Perhaps at this stage, especially given that @brycehemme was able to show recent code not reproducing it, it is better to just close the bug as "whether valid or not at the time, it doesn't apply now, and so much has changed since then that we should just bury it and move on"...?
I will leave the issue open, but whichever maintainer/collaborator wants to make the decision to close this issue, feel free.

Closing this then, thank you for giving this a try @brycehemme!


Enable Dependabot Version Updates

Enable Dependabot Version Updates
This issue is in reference to this Dependabot version updates feature in the https://github.com/JamieBort/Personal-Dashboard/settings/security_analysis page.

Resources

Keep all your packages up to date with Dependabot GitHub blog post

Keeping your dependencies updated is one of the easiest ways to keep the software you build secure. However, while it’s critically important to keep your dependencies updated, in a recent…

This one was a help.

Documentation
Configuring Dependabot version updates

You can configure your repository so that Dependabot automatically updates the packages you use.

A potential source:
https://trello.com/c/7xQFGezu/1319-address-these-dependabot-alerts

Another potential source:
https://github.com/JamieBort/LearningDirectory/tree/master/Git/security#dependabot

Potential yml file
# To get started with Dependabot version updates, you'll need to specify which
# package ecosystems to update and where the package manifests are located.
# Please see the documentation for all configuration options:
# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file

version: 2
updates:
  - package-ecosystem: "yarn" # See documentation for possible values
    directory: "/frontend" # Location of package manifests
    schedule:
      interval: "monthly"
  - package-ecosystem: "yarn" # See documentation for possible values
    directory: "/backend" # Location of package manifests
    schedule:
      interval: "monthly"

Todo

[x] Finish setting up this Issue. To that end, see https://github.com/JamieBort/Portfolio-Website/issues/17 for wording, formatting, process, screenshots, etc.
[x] Research what needs to be done.
[x] Enable this feature.

Status
Done.
However, I may need to go back into settings to manually enable the feature. To that end, see this message below.

Added this
# To get started with Dependabot version updates, you'll need to specify which
# package ecosystems to update and where the package manifests are located.
# Please see the documentation for all configuration options:
# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file

version: 2
updates:
  - package-ecosystem: "yarn" # See documentation for possible values
    directory: "/frontend" # Location of package manifests
    schedule:
      interval: "monthly"
  - package-ecosystem: "yarn" # See documentation for possible values
    directory: "/backend" # Location of package manifests
    schedule:
      interval: "monthly"

to this .github/dependabot.yml file in the fullstack branch.
See commit af07e52aa28900fd85b1fceb63497653a75b1682
This feature should be enabled once the master branch has this .github/dependabot.yml file.
If not, return to this settings page and select Enable next to the Dependabot version updates feature.


Deno implementation

Hey, can you give me some tips on converting this for use with Deno? Is this planned for the future?

No, It is not planned yet because most of our dependencies doesn't support it.
For now you can use the cli version of this package and run it as a child process.
https://www.npmjs.com/package/protocol-registry-cli
Closing this issue for now. Will re-open when we will plan about deno.