Fixes #3: Modifying Regex

Fixes Regex Part of the Issue.
Check this link for checking regex.
@EmberCS15

Your regex is ok but the javaScript syntax for regex is wrong. Correct the syntax. Run the Code and the application. Try out a few Strings and see if it should be passed by the regex. Also if possible try out the following -

From any string, I need only the till the following portion v=w0EF3AxJwLU in string
https://www.youtube.com/watch?v=w0EF3AxJwLU&list=RDMMw0EF3AxJwLU
Similarly for any string, if it is valid extract on the part till https://www.youtube.com/watch?v=w0EF3AxJwLU and feed it to the downloader.
2)To modify the regex enclose regex between '/' eg. /regex/.

I am not able to run the project locally. Django is not able to install I checked the error online but got no solution and got to know as with latest python release it doesnt works.
Can you help me on this?

Download and install previous python version(3.5). I am currently running
python 3.6 and Django is working properly on my lappy. Use pip to install
Django.
On Wed, Dec 27, 2017 at 8:33 PM, Mohit Sharma<EMAIL_ADDRESS>wrote:

I am not able to run the project locally. Django is not able to install I
checked the error online but got no solution and got to know as with latest
python release it doesnt works.
Can you help me on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NJACKWinterOfCode/Wizzy-Downloader/pull/9#issuecomment-354126136,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXKmHzt2rtgXDjWregbhk6e9XRvIBUGrks5tElwogaJpZM4RM-99
.

I have made the given changes @EmberCS15
Please review

Yeah i made it to work out @EmberCS15
And checked and corrected the regex

Try out the other things I suggested and make PR.

By other things you mean which part @EmberCS15 ?

Thanks will try out other things with the project

I mentioned two points above. Try your hand at the first point. Also, you can look into the other issues present. Cheers.


flutter-devicelab-mac-6 is quarantined - Device healthcheck failed: attached_device: No device is available

flutter-devicelab-mac-6 complains No device is available.

https://chromium-swarm.appspot.com/bot?id=flutter-devicelab-mac-6

Duplicated of https://github.com/flutter/flutter/issues/66153


is bugsnag integration possible ?

i would love to see the bugsnag ability in the supercronic.
is it too much hassle to add ?

We don't use BugSnag, but we will try to accept well-tested 3rd party integrations from the community.


Remove ActiveSupport definition dependency; Update to Unicode 7.0.0

Closes #816

Just ran into this problem with mail in a sinatra project, which does not use activesupport. Definition of ActiveSupport in mail (unicode.rb) does cause problems with thirdparty gems.
I don't want to include ActiveSupport in my project, so which would be my best approach at the moment?
Any plans of merging this fix with the master?

@jeremy I just rebased this against master (though there were no merge conflicts 934f02f85cab14f415208fd573be093dea23b3bd )

looks like unicode 8.0 is now released

It would be really nice if this got merged :)

Thank you!

:rainbow:


bazel: ensure @envoy_mobile references

Add @envoy_mobile to all absolute bazel references (target dependencies which start with //)
Clean up the aar_with_jni macro and include sources and javadoc generation as part of the macro
Ensure we use java8 for executing mac os (dokka requires java8 rather than java14 which is what is used by default)

Signed-off-by: Alan Chiu<EMAIL_ADDRESS>For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description: bazel: ensure @envoy_mobile references
Risk Level: low
Testing: ci + local
Docs Changes: n/a
Release Notes: n/a
[Optional Fixes #Issue]
[Optional Deprecated:]

👀 @keith  -- most of this is pretty vanilla: find+replace or some small tweak to a target.
The main/big change is the bazel/aar_with_jni.bzl file which I hope organizes things a little better

1. Add `@envoy_mobile` to all absolute bazel references (target dependencies which start with `//`)

Can you explain why this is needed? I have not seen targets pertaining to a workspace need to reference the project with an @project prefix before. For instance, envoy does not have this.

@junr03

Can you explain why this is needed? I have not seen targets pertaining to a workspace need to reference the project with an @project prefix before. For instance, envoy does not have this.

I think I misunderstood a bazel error and I'll need to load the appropriate rules. Let me fix this up.


WIP: Chore: Update CI, Reformat Code

Implementation of #291

Will be closed in favour of other PR's


APP-1339 - Changes to block the main buttons while executing an action

Codecov Report

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

@@          Coverage Diff          @@
##             dev     #99   +/-   ##
=====================================
  Coverage       ?   88.6%
=====================================
  Files          ?      41
  Lines          ?    1132
  Branches       ?     134
=====================================
  Hits           ?    1003
  Misses         ?      87
  Partials       ?      42

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 357ed16...5b69147. Read the comment docs.

@luanapp Please verify the conflicting files.


different colors for different paths

Hi! It would be great to be able to give stations different colors (or other visible attributes) in order to create a kind of differentiation. For example, paths could be marked in different colors to represent different levels of difficulty (very useful for school).

Sure, I can think about that when I find some free time - but right now I need to earn a living.

I assumed this was a "someday" idea, but under the content type it said "More suggestions are welcome!", so I thought I'd leave the idea here :). Cheers.

More suggestions are welcome! But that doesn't mean that everything will make it (timely) :-)


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.2 to before v5.15.13",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=83374e035b6286731c5aa617844c7b724294c2a7",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=249ddfbe00570d6dc76208e88017937d4d374c79"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "83374e035b6286731c5aa617844c7b724294c2a7",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "249ddfbe00570d6dc76208e88017937d4d374c79",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "usb: mtu3: fix list_head check warning\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.13 by commit 249ddfbe00570d6dc76208e88017937d4d374c79, it was introduced in version v5.2 by commit 83374e035b6286731c5aa617844c7b724294c2a7. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000061


Publish package on PyPI

[ ] publish on PyPI.

Published using poetry here: https://pypi.org/project/open-geo-engine/


cancel I/O (notably attach) when container exits

What type of PR is this?

/kind bug
What this PR does / why we need it:
Previously, the attach code was sending Done too early. This caused clients to detach early while there was still output to process. It previously used the "no output" condition to decide that there was no more output. However, it seems the read pipe will send n == 0 (which I think should be looked into separately)
Really, the condition to stop the attach are two-fold: client detaches, or container exits. the former case should be handled. This PR adds the latter case by using a cancellation token and wiring it throughout the I/O code.
A followup should be checking that we're not CPU cycling when we get no output from the pipes (n == 0 cases that were dropped)
Which issue(s) this PR fixes:
fixes https://github.com/containers/conmon-rs/issues/620

Special notes for your reviewer:
Does this PR introduce a user-facing change?

Fix a bug where the server would detach from an attach session too early

Thank you for digging into this, mostly LGTM but the CI does not seem to be happy right now.

huzzah! @saschagrunert @rphillips PTAL

Nice job! I'll defer to @saschagrunert so he has a chance to look through.


adversarial_abblstm.py  - validation accuracy: 0% / test accuracy: 0%

I am running your code without modifications on the dbpedia dataset and is receiving non-valid results as follows:
..
Validation accuracy: 0.000
Training finished, time consumed :<PHONE_NUMBER>9178772  s
Start evaluating:
Test accuracy : 0.000000 %

I think the problem may related to the issue #4  , and I fixed the problem by changing the shuffle function, and below if my result:

Epoch 1 start !
Train Epoch time:  31.915 s
validation accuracy: 0.732
Epoch 2 start !
Train Epoch time:  32.457 s
validation accuracy: 0.840


TerminationDrainDuration can't be set less than 1s

Bug Description
Update meshConfig.defaultConfig.terminationDrainDuration = 500ms
Check injected env PROXY_CONFIG:
"terminationDrainDuration\":\"5.500s\"

Got the incorrect value.
I think the releated code is https://github.com/istio/istio/blob/master/pilot/pkg/model/proxy_config.go#L136
proto.Merge merge two durations with Seconds and Nanos separately.
Version
latest version

Additional Information
No response
Affected product area

[ ] Ambient
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

Is this the right place to submit this?

[X] This is not a security vulnerability
[X] This is not a question about how to use Istio

this seems due to proto merge stuff
IIRC, @howardjohn know more

We have to use [merge.Merge()](https://github.com/istio/istio/blob/master/pkg/proto/merge/merge.go#L66) instead of proto.Merge to handle duration merge properly.


providers/implementations/kdfs/argon2.c: Include openssl/e_os2.h instead of stdint.h

<stdint.h> may not exist with pre-C99 compilers.  <openssl/e_os2.h> deals
with that, so include it instead.
Similarly, include "internal/numbers.h" rather than <limits.h>, to deal
with things that may be lacking in the latter.

VMS builds currently fail because of the <stdint.h> inclusion.
Arguably, that makes this PR urgent.

Windows buildbot still building, I'll wait...

Merged
46ce0854db51e373ab6ed4982431349107cd9b6d providers/implementations/kdfs/argon2.c: Include openssl/e_os2.h instead of stdint.h

On master with my usual
./Configure shared --debug --strict-warnings -std=gnu90

I now get
In file included from include/internal/common.h:18,
                 from include/internal/cryptlib.h:21,
                 from include/internal/thread.h:16,
                 from providers/implementations/kdfs/argon2.c:27:
providers/implementations/kdfs/argon2.c: In function 'kdf_argon2_ctx_set_t_cost':
include/internal/e_os.h:28:9: error: ISO C90 does not support '_Static_assert' [-Werror=pedantic]
   28 |         _Static_assert((__builtin_types_compatible_p(type, __typeof__(x))),  \
      |         ^~~~~~~~~~~~~~
providers/implementations/kdfs/argon2.c:1213:5: note: in expansion of macro 'ossl_static_assert_type_eq'
 1213 |     ossl_static_assert_type_eq(uint32_t, t_cost);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~
providers/implementations/kdfs/argon2.c: In function 'kdf_argon2_ctx_set_m_cost':
include/internal/e_os.h:28:9: error: ISO C90 does not support '_Static_assert' [-Werror=pedantic]
   28 |         _Static_assert((__builtin_types_compatible_p(type, __typeof__(x))),  \
      |         ^~~~~~~~~~~~~~
providers/implementations/kdfs/argon2.c:1228:5: note: in expansion of macro 'ossl_static_assert_type_eq'
 1228 |     ossl_static_assert_type_eq(uint32_t, m_cost);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~
providers/implementations/kdfs/argon2.c: In function 'kdf_argon2_ctx_set_out_length':
include/internal/e_os.h:28:9: error: ISO C90 does not support '_Static_assert' [-Werror=pedantic]
   28 |         _Static_assert((__builtin_types_compatible_p(type, __typeof__(x))),  \
      |         ^~~~~~~~~~~~~~
providers/implementations/kdfs/argon2.c:1249:5: note: in expansion of macro 'ossl_static_assert_type_eq'
 1249 |     ossl_static_assert_type_eq(uint32_t, outlen);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~
providers/implementations/kdfs/argon2.c: At top level:
cc1: note: unrecognized command-line option '-Wno-tautological-constant-out-of-range-compare' may have been intended to silence earlier diagnostics
cc1: all warnings being treated as errors
make[1]: *** [Makefile:21963: providers/implementations/kdfs/libdefault-lib-argon2.o] Error 1

while it works when leaving out -pedanic:
gcc  -I. -Icrypto -Iinclude -Iproviders/implementations/include -Iproviders/common/include  -DAES_ASM -DBSAES_ASM -DECP_NISTZ256_ASM -DKECCAK1600_ASM -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DVPAES_ASM -DX25519_ASM -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O0 -g -Wno-long-long -DUNUSEDRESULT_DEBUG -Wall -Wmissing-declarations -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wswitch -Wsign-compare -Wshadow -Wformat -Wno-type-limits -Wno-tautological-constant-out-of-range-compare -Wundef -Werror -Wmissing-prototypes -Wstrict-prototypes -std=gnu90 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib64/engines-3\"" -DMODULESDIR="\"/usr/local/lib64/ossl-modules\"" -DOPENSSL_BUILDING_OPENSSL  -MMD -MF providers/implementations/kdfs/libdefault-lib-argon2.d.tmp -MT providers/implementations/kdfs/libdefault-lib-argon2.o -c -o providers/implementations/kdfs/libdefault-lib-argon2.o providers/implementations/kdfs/argon2.c

Did that work before this PR was applied?  Considering that _Static_assert is a C11 construct (which is deprecated in C23 in favor of static_assert), it shouldn't have compiled better before...

Ah, I could verify it on my own, by checking out 46ce0854db51e373ab6ed4982431349107cd9b6d^.  And yup, I still get the same error, so this PR can't be attributed that problem...

So, what this means is that the guard around the definition of ossl_static_assert_type_eq in e_os.h isn't good enough; it needs a bit of calibration

Did that work before this PR was applied?

I can only say that I did not notice the issue before.
Can well be that this it was introduced before and I simply did not experience it before,
because I reconfigure rarely and thus most sources are not re-compiled for long time.

I noticed that -std=gnu90 seems to catch more than -std=c90...  which I find a bit surprising.  However, it still doesn't catch the non-standard (for C90) use of UINT64_C, which is a bit of a disappointment...


Complete endpoints implementations needed for Theia plugins

It's needed to complete endpoints implementations needed for Theia plugins:
Theia defines https://github.com/eclipse/che-plugin-registry/blob/master/v3/plugins/redhat/java11/0.63.0a/meta.yaml protocol, discoverable, type, path which have a bit different location in devfile 2.0 format

On branch use-v1alpha2-and-new-attributes I'm working on the the start of this issue:

Using the new endpoint validated fields: exposure, path, protocol, secure, instead of the old corresponding attributes.

The thing that Devfile 2.0 is missing - a unique host. I've created the corresponding issue on devfile/api side. https://github.com/devfile/api/issues/230

It believe it can be safety closed now.
Devfile API and DevWorkspace Che Operator has their issues to support uniqueHost


Fatal error: Arrays are not allowed in class constants & Case sensitive file class

This mistake I have inline 50, validate.php for PHP version 5.5:
50:  const REG = array(...);
Second problem as Case sensitive file patch.
File have first letter lowercase and class name have first letter uppercase. PSR specification recommend MUST for case sensitive namespace for file patch & class name.

Ok, we have made it combined as strings instead of array.
The sonarcube tells us to rename this files if we make them like TestClass. It should be testClass and class declared in code as TestClass. In fact you always use /tpay/TestClass as reference in tpay namespace so file name is not important.

Not important for you.  But important for framework PHP with autoloader.
Please read: http://www.php-fig.org/psr/psr-4/

Currently the code is being adjusted to be valid PSR2. We will make it PSR4 in future.


MotionDetector with CMSampleBuffer

How i can use MotionDetector with didCaptureBuffer(_ sampleBuffer: CMSampleBuffer) ?

I don't think you can, at least not easily. It requires a texture-backed framebuffer as input (as do almost all GPUImage operations). Is there a reason why you'd want to handle the sample buffers yourself, as opposed to just using a Camera, Movie, or PictureInput instance?

i already have code that  shared the camera between multi ViewController i don't want to change this code

It's honestly not that hard to use a new Camera instance. It's just a couple of lines of code.


Get artifact generation working under JDK 10+

Partially completes #2881
Changes:

Use newer version of spotbugs-maven-plugin that works with JDK 10+ (matches the actual version of spotbugs we're already using)
Specify source version in maven-javadoc-plugin
Add an include filter to process only xml files via xml-maven-plugin (one of the above changes caused non-xml files to be generated in the workingdir)

With these changes, I was able to generate all artifacts successfully using the following commands:
mvn site -f pom.client.xml
mvn checkstyle:checkstyle-aggregate -f pom.client.xml
mvn install -Pspotbugs-reporting -DskipTests -Dgpg.skip -f pom.client.xml
mvn javadoc:aggregate -f pom.client.xml

Can one of the admins verify this patch?


Device addition

a) Teckin Smart Outlet
b) [3/21/2019, 5:34:23 PM] [TuyaLan] Ready to handle Kamera with signature {"1":false,"9":0,"18":0,"19":0,"20":2340,"21":1,"22":649,"23":30787,"24":17570,"25":1185}
c) https://www.amazon.de/TECKIN-Intelligente-fernbedienbar-Stromverbrauch-funktioniert/dp/B07CDCYLQ6
But I have no clue what the dps values other than 20 (Volt) should mean. There is nothing special shown in the Smartlife app for this Outlet.

If all you want to do is use the device as an outlet, go with Outlet as the type; you can switch it on and off through HomeKit.
But if you think there is more to the device and you would rather have them made available to you in the Home app, continue reading :)
To figure out what the dps values are:

disconnect your phone from the home WiFi
configure the device as a SimpleLight
open your Homebridge logs
open the Tuya app and click on different buttons and see what changes you can see showing up in the logs.

Some of those dp keys correspond to volts, amps, and power consumption, and coding for them is still ongoing; I will update the instructions as soon as it has been tested. Some others are for timers and automation that HomeKit doesn't even support. If you see any functionality other than these and you were successful in decoding the dp for each, reopen the issue with your findings.


Implement Push notification of Existing Files

Implement a rake task that can be used to send notifications to share of files already existing in the system.  See #188 for resource types.  Use code created by #201 to send the data for each file.

Handle gracefully existing files in share.

for every file in the system send it to the share service.

Is there a limit for sending information to share.
Is there a batch request?


Ambassador

Name: Rohit Gupta
Github username: guptarohit
Background: 2+ years of Python backend work experience
Interests: building utilites

:snake: :sparkles:

Hi @guptarohit
You've been invited to kennethreitz.org! You'll be receiving an email shortly. You can also visit https://github.com/kennethreitz to accept the invitation.


Use the npm registry for<EMAIL_ADDRESS>

This manually updates our yarn.lock file to download the<EMAIL_ADDRESS>package from the npm registry instead of the yarn registry.
I noticed this locally when I removed my node_modules folder and reran yarn install. Yarn would output this error:
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "https://registry.yarnpkg.com/json-schema/-/json-schema-0.2.3.tgz: read ECONNRESET".

When I tried downloading the file via curl I get something similiar:
$ curl -v https://registry.yarnpkg.com/json-schema/-/json-schema-0.2.3.tgz
> GET /json-schema/-/json-schema-0.2.3.tgz HTTP/1.1
> Host: registry.yarnpkg.com
> User-Agent: curl/7.64.1
> Accept: */*
>
* LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
* Closing connection 0
curl: (56) LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54

I also checked with @blangley28 and he gets the same error when on VPN. I don't know if it is a MITRE-network specific thing or what, but something is blocking access to that file. I am able to download it from the npm registry, which is what this PR changes it to.
To test, run this on master, then on this branch:
rm -rf node_modules
yarn cache clean
yarn install

Is this still needed? I'm able to access the yarnpkg URL just fine

Is this still needed? I'm able to access the yarnpkg URL just fine

Yup, you're right! It looks like it's working now, will close


German Translation

I decided to re-translate everything again, so that's why that diff is quite huge.
In my opinion, it's an improvement in translation quality.

:+1:


Connecting to Angular Frontend

I want to display the tweets from the console to an HTML webpage, how can i achieve that?

Instaed of line "console.log('\n' + tweet.user.screen_name + ' : ' + tweet.text);" pass the tweet object to the Angular View.


Clarify guide-level explanation

Makes the guide-level text more explicit and direct through adding structure, rewording, and adding clarifying formatting.
Previously, some of the text, particularly when describing states and constraints, was difficult to understand.

Applying this PR to a different branch.


Why I can not compile the .tex file with xelatex successfully？

I encounter the following errors when compiling the .tex file with xelatex. I use the texmaker as the latex editor.
!Latex Error:Unknown option 'fontset = adobe' for package 'ctex'.
!Latex Error:Unknown option 'scheme = Chinsee' for package 'ctex'.
!Latex Error:Unknown option 'fontset = zihao=-4' for package 'ctex'.
!Undefined control sequence. \CJKaddEncHook
!Latex Error:Option clash for package color.
!Undefined control sequence. \xeCJKsetup.
!Undefined control sequence. \ctexset.

You probably need to update your ctex package.


Remapping Default Console Keys

Description of the new feature/enhancement
Having the ability to remap the default keys of the host console (CMD, Powershell, etc.). Right now, it is only possible to remap some keys from the Windows Terminal UI. One example of a key I'd like to be able to remap is F8, which in Command Prompt cycles through the history based on the characters you've already typed. I'd like to remap it to something like ctrl+up.
If you know of a workaround for this, it'd be much appreciated if you let me know.

Proposed technical implementation details (optional)
The code currently calls _cycleMatchingCommandHistoryToPrompt when it detects a VK_F8 event. It might be possible to allow this to be changed dynamically.

Hey @FancyKillerPanda! Thanks for the investigation and for the feature request. This is a tough nut, though it might not seem like that on the surface. Here's what's up.
Those key bindings (F6-F9) are part of a legacy part of the console host we all wish we'd never committed to. Back in what feels like 1965 a decision was made: that the console host would store command history and aliases and handle a "cooked" line discipline on behalf of any console application that asks for it.
Since people view those behaviors as being so deeply intertwined with CMD and PowerShell, we can't rip them out of conhost and move them into the shells where they belong. Since they're so deeply integrated in conhost, however, we have to give them a cautious berth. I'm not likely to greenlight work to make them configurable in conhost.
Now, here's the rub. "Conhost isn't terminal!" you might protest. This is where the lines blur a little bit. Terminal doesn't have any idea what the result of sending F8 or Ctrl+Up or what-have-you is going to be. It's not secretly telling conhost that it should pop up the history dialog... it's just telling it "hey the user pressed F8" (which I presume you already know, but I'm in exposition mode) so on the flipside of that, there's no way to tell it not to pop up the history dialog without plumbing a new configuration option down into conhost and a bit of infrastructure to support it. That'd have to come after all the other "we need to be able to tell conhost x, y, or z" issues (like #1882, which needs to tell its nested conhost that "hey the user wanted to delete the buffer, you keen?)
All that to say- this one probably won't make the cut, so I'm going to close it out with an unfortunate Won't Fix. Sorry!


Updating module name to allow easier package imports

Extension on the package export issue #98.
Currently the module name in the go.mod file is osv-detector, which causes go get commands like:
go get github.com/g-rath/osv-detector/pkg/lockfile

to fail with the error:
 module declares its path as: osv-detector
       but was required as: github.com/g-rath/osv-detector

The workaround I'm using at the moment is to add a replace osv-detector => github.com/g-rath/osv-detector v0.7.0 to my go.mod file.
Can you consider changing the module name to github.com/g-rath/osv-detector to allow easier go geting?

Yup happy to consider this - my only concern is what impact this will have on local development; is Go able to handle the fact that the module is "within itself" so continue to act locally, or will it end up treating github.com/g-rath/osv-detector as an external dependency (and so I'd potentially have to wrangle different versions whenever I need to make a change that impacts multiple packages)?
(I'll also look to see if I can remove that dependency entirely for lockfile - I'm pretty sure its just being used for the types, which are not in that package for circular dependency reasons which I might be able to resolve another way)

🤦 ok nope it sounds like I've misunderstood how module works in go.mod: https://github.com/golang/go/issues/33274
so it should module github.com/g-rath/osv-detector instead of module osv-detector

hmm naively just changing that in go.mod breaks things:
osv-detector on  main [$!?] via 🐹 v1.17.9 via 💎 v3.1.2 took 6s
❯ make build
go build -o osv-detector
main.go:9:2: package osv-detector/internal is not in GOROOT (/home/gareth/.goenv/versions/1.17.9/src/osv-detector/internal)
main.go:10:2: package osv-detector/internal/configer is not in GOROOT (/home/gareth/.goenv/versions/1.17.9/src/osv-detector/internal/configer)
main.go:11:2: package osv-detector/internal/reporter is not in GOROOT (/home/gareth/.goenv/versions/1.17.9/src/osv-detector/internal/reporter)
main.go:12:2: package osv-detector/pkg/database is not in GOROOT (/home/gareth/.goenv/versions/1.17.9/src/osv-detector/pkg/database)
main.go:13:2: package osv-detector/pkg/lockfile is not in GOROOT (/home/gareth/.goenv/versions/1.17.9/src/osv-detector/pkg/lockfile)
make: *** [Makefile:6: build] Error 1

In a fork earlier, I did a find and replace for "osv-detector/ and replacing it with "github.com/g-rath/osv-detector/ which seems to work.

Yeah I've just done that too and it seems fine: https://github.com/G-Rath/osv-detector/commit/4223de89971f9b0475b7cc0ef0ade0b4640bb024
I'll make a PR for it shortly - I'm still a little concerned about edge-cases but I'm probably just overthinking it 🤷


"Desktop" section misalignment and missing "Windows Driver" target.

It seems like the "| |Desktop|A driver binary for Windows 10 for desktop editions or Windows Server 2016 can call this DDI.|" section from the end of the article should be a part of the table with Target Platforms.
Another thing is that in the latest release of WDK there is also "Windows Driver" target, but I can't find any documentation for it. Could you please describe it here?
Thanks!

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

ID: c3764139-c203-f295-1591-e8c67ee0eb94
Version Independent ID: 8128169c-8bab-008b-a7e4-bd647f4c02d2
Content: Target platform on driver reference pages - Windows drivers
Content Source: windows-driver-docs-pr/develop/target-platforms.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Hi @dluzak, thanks for the feedback.  Check out https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/getting-started-with-windows-drivers for info on Windows Drivers.

Just pushed the table fix, should appear soon.   Thanks again for the feedback!


Stackstorm HA not retriving data

@armab
When I log back in to my HA Environment, which was previously operating, it now displays this problem.
Unable to retrieve history. See details in developer tools console.
Logging in and registering the setups works for me. However I couldn't retrieve any lists.
Please help on this.

st2 pack install sensu
ERROR: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))

take a look at your stackstorm logs and report back any interesting findings please.


Warning: Failed context type: The context router is marked as required in Link, but its value is undefined.

I just installed react-route with the following version: "^4.0.0-beta.6" inside a create-react-app application and I can't use <Link>.
I just copy-pasted the basic example in App.js and got the following issue:
Warning: Failed context type: The context `router` is marked as required in `Link`, but its value is `undefined`.

I forced the update to beta.7 and now it works. However, I did not see any mentions of this bug in the CHANGES file...

I have seen a couple people mention this issue. Are you sure that both react-router and react-router-dom were beta 6? I'm guessing that react-router-dom was 6 but react-router was 7.
The context changes are mentioned in this line:

Split context.router into two parts: context.history and context.route

Yes this is possible. I don't know what was the react-router version since I only imported react-router-dom.

The problem is that react-router-dom depends on a version range of react-router. Let me explain; look at the package.json of<EMAIL_ADDRESS>https://github.com/ReactTraining/react-router/blob/v4.0.0-beta.5/packages/react-router-dom/package.json#L45
So<EMAIL_ADDRESS>depends on<EMAIL_ADDRESS>which will always resolve the latest 2.x. This means that if you use the exact version, it'll break ("react-router-dom": "v2.0.0-beta.5"), and you'll have a version mismatch.

 Was having the same issue, didn't realize that my react-router and react-router-dom package versions had drifted. Manually installing both at beta.6 solved the issue.

I'm seeing this error without setting any specific version in my package.json.
I have this in package.json:
    "react-router": "next",
    "react-router-dom": "next",
    "react-router-native": "next",

Which results in the following being installed (according to yarn.lock):
react-router-dom@next:
  version "4.0.0-beta.8"
  resolved "https://registry.yarnpkg.com/react-router-dom/-/react-router-dom-4.0.0-beta.8.tgz#907a5a0a36e9190652c80f2feead0eadbbba262e"
  dependencies:
    history "^4.5.1"
    react-router "^4.0.0-beta.8"

react-router-native@next:
  version "4.0.0-beta.8"
  resolved "https://registry.yarnpkg.com/react-router-native/-/react-router-native-4.0.0-beta.8.tgz#cfaab55f8e70cc41e349d1e2f2a2ca3f94b68fc3"
  dependencies:
    react-router "^4.0.0-beta.8"

<EMAIL_ADDRESS>react-router@next:
  version "4.0.0-beta.8"
  resolved "https://registry.yarnpkg.com/react-router/-/react-router-4.0.0-beta.8.tgz#368cfe540d23d5d23419b42fb915d465f268b66b"
  dependencies:
    history "^4.6.0"
    invariant "^2.2.2"
    loose-envify "^1.3.1"
    path-to-regexp "^1.5.3"
    warning "^3.0.0"

Install the 4.0.0 final version to be sure!

Also, what kind of project are you working on that needs both react-router-dom and react-router-native? 😄

Ok, so now with this in my package.json:
    "react-router": "^4.0.0",
    "react-router-dom": "^4.0.0",
    "react-router-native": "^4.0.0",

I still get the same error.
I'm importing both dom and native because we are using react-native-web to get a web app out of our react native code base.

Found it -- my bad!  I had the  component appearing outside the Router component!

Hi @timdorr I'm having similar issues
"react": "^15.6.1"
"react-dom": "^15.6.1"
"react-router": "^4.1.2"
"react-router-dom": "^4.1.2"
There are about 60 console errors for Context/PropTypes on application start, and I have zero idea what to do about it.

here is the answer!
https://github.com/ReactTraining/react-router/issues/4759#issuecomment-318607199


Fixes images wrapping

Without this sampler, images' first line are wrapping from last line.

Thanks again Ilya!


Move training and cluster config to JSON files

Didn't know about keys as a command to jq. Very neat.


Remove manuals observers registry

This PR removes the ManualObserversRegistry and inlines the functionality into the Service classes. This allows us to remove all of the references to "listeners" and instead use more imperative method names in the Service classes.
I've struggled a little bit to come up with names for some of these methods and classes that I have extracted and I think this points to the fact that their functionality is duplicated in part elsewhere in the application. In particular:

NewPublishingApiPublisher <-> PublishingAPIPublisher
NewPublishingApiWithdrawer <-> PublishingAPIWithdrawer
PublishingApiDraftExporter <-> PublishingApiDraftManualExporter <-> PublishingApiDraftSectionExporter

If we're happy with these changes, I might raise issues to capture those three areas as places where we might be able to simplify the code.

Github is showing these commits in a slightly different order to how I have them - in the branch they are grouped 'Extract -> Inline -> Rename'

I'm still going through this branch but just wanted to add a note to apologise for making your life  harder by merging PR #904. I can see that you've extracted classes containing calls to ManualWithDocuments#documents which will need to be changed to ManualWithSections#sections. Sorry and I hope it's not too painful!

The extracted classes all seem to operate on a ManualWithSections. I wonder whether we can use that to come up with more specific (albeit more verbose) names?

PublishingApiDraftExporter -> PublishingApiDraftManualWithSectionsExporter
NewPublishingApiPublisher -> PublishingApiManualWithSectionsPublisher
RummagerExporter -> RummagerManualWithSectionsExporter
RummagerWithdrawer -> RummagerManualWithSectionsWithdrawer
NewPublishingApiWithdrawer -> PublishingApiManualWithSectionsWithdrawer

This might help clarify the differences between, for example:

PublishingApiDraftManualsWithSectionExporter
PublishingApiDraftManualExporter
PublishingApiDraftSectionExporter

I also wonder whether these extracted classes should also live in app/exporters given that there are already other *_exporter and *_withdrawer classes in there?

Replacing the comments with assertions in "Inline ManualObserversRegistry#publication" is a great improvement :-)

In "Inline ManualObserversRegistry#update" it might be worth updating the commit note to mention that you'll handle #update_original_publication_date in a separate commit. It wasn't immediately obvious to me why the alias had been removed and the method name changed.

Despite my comments I think this is a definite improvement. It makes it much easier to see what the various *_manual_service classes actually do. Good work!

The only thing preventing me from accepting the PR at the moment is the naming of some of the extracted classes. What do you think about either the names I've suggested or an alternative that slightly better describes their purpose, @chrislo?

Thanks @chrisroos - I've made the class name and file name changes you suggested, and added some more details in the commit message for ffee3735. I've rebased the changes back in the history and force pushed.

Force pushing in preparation for merging.


Enqueue tests

@tstirrat this was an easy one. I have all day tomorrow and I'd love to continue working on this if you'd like me to continue.

@MattMSumner I will be done with the rest of them tomorrow morning, just doing some refactoring to make the tests a little cleaner and fix a few problems where tests are modifying global state.
If you want to look at some other things, perhaps you can start looking at the default blueprint (ember g emberfire) and start on the following:

add a firebase entry to config/environments.js and print instructions to the console on how to change it
check for existence of app/adapters/application.js and, if missing, create with this template:import config from '../config/environment';
import Firebase from 'firebase';
import FirebaseAdapter from 'emberfire/adapters/firebase';

export default FirebaseAdapter.extend({
  firebase: new Firebase(config.firebase)
});


[Trivial][ML] Remove unnecessary new before case class construction

What changes were proposed in this pull request?
Delete unnecessary new before case class' apply function.
Run find mllib/src/main/scala/org/apache/spark/ml -name "*scala" | xargs -i bash -c 'grep -i "new Data(" {} && echo {}' to make sure that only MaxAbsScaler and MinMaxScaler need modification.
How was this patch tested?
unit test

Test build #64993 has started for PR 14974 at commit ef2c4be.

If both versions do exactly the same thing and call a case class constructor, I'd say this change is actually making it less clear. However this will call Data.apply right -- which I assume will also just call the constructor in just about any case. Is there ever an advantage to it? there may be. If this is changed it should be done consistently across the code.

I looked at the generated byte code and this just calls a constructor anyway. I don't know if this is worth doing, as it doesn't change the actual compiled code. While I would not write new for a case class personally, it's arguably clearer about what is happening. There might be corner cases where it generates better byte code (value classes?) but I don't think this is one.

@srowen I agree that this do not generates better byte code. I make this change just to keep in line with other algorithms.

Test build #64993 has finished for PR 14974 at commit ef2c4be.

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

Merged build finished. Test PASSed.

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

I would only do this if all usages of new were removed for case classes in the code. I'd also like someone else to chime in in support or otherwise before merging this as I'm neutral on it.

I think we can close this PR


BREAKING CHANGE: CertificationAuthority: add code to build certs

It turns out we can further simplify the ooni/probe-cli implementation by adding more methods of *CA to CertificationAuthority.
Part of https://github.com/ooni/probe/issues/2531

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

16 of 19 (84.21%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 84.848%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

unetstack.go
3
6
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.004%

Covered Lines:
2408

Relevant Lines:
2838

💛  - Coveralls


Skyscraper sources

Project Skyscraper (https://web.archive.org/web/20180731053350/http://sourceforge.net/projects/skyscraper/, https://web.archive.org/web/20180605235918/https://www.skyscrapersim.com/index.shtml) does not exist anymore. Are the sources still available somewhere?

Also see https://web.archive.org/web/20161129160822/http://www.skyscrapersim.com:80/downloads.shtml and https://web.archive.org/web/2016*/http://www.skyscrapersim.com/downloads/

Some of them are available, but not everyone.
https://web.archive.org/web/20140120075226/http://www.skyscrapersim.com/downloads/dev/skyscraper-011814-linux-x86.tar.bz2

Then there is https://github.com/hakusdream/skyscrapersim
might this be the copy of the svn?

The official SVN has its last update from 2018-05-10 (https://web.archive.org/web/20180714064230/https://sourceforge.net/p/skyscraper/svn/HEAD/tree/skyscraper/) by ryan. The Git at https://github.com/hakusdream/skyscrapersim has the last update on 2017-10-16 by ryan ("Re-enable XP support"). There might be commits missing.
I will try to contact the authors and if that fails ask on reddit or freegamedev.

I wrote a message to Ryan Thoryk, the author of Skyscraper, through the Sourceforge message system and asked for the source.


Setup segment

TODO:

[ ] Add ENV var setup info for this to README.md

Add ENV var setup info for this to README.md

The generated README for the new app actually mentions setting the environment variable for Segment already. Perhaps this was done already?


Error: Cannot find module 'gulp-traceur'

Using the latest node, npm, gulp I ran into the following error on gulp serve

module.js:338
throw err;
^
Error: Cannot find module 'gulp-traceur'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:278:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/Users/kendallarneaud/Documents/Git/heroku/aurasma-treasure-hunt/gulpfile.js:3:15)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)

gulp-traceur? :scream:
Let me check it

It seems like you worked with a different generator:

There is no serve task in the existent workflow (and never was), gulp dev does the job.
Traceur has never been used.
You can see a list of installed generators by running yo --generators.


Test std backtrace type

:umbrella: The latest upstream changes (presumably #1585) made this pull request unmergeable. Please resolve the merge conflicts.
Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
@rustbot modify labels: +S-waiting-on-review -S-waiting-on-author

Thanks! @bors r+
What happens when isolation is disabled?

:pushpin: Commit 8b10dbfeaab5826fb3d179bb94454a80182a9c3a has been approved by RalfJung

:hourglass: Testing commit 8b10dbfeaab5826fb3d179bb94454a80182a9c3a with merge 4ad1667e9ce03d51a4a003d0241b7d83ffdfba56...

:sunny: Test successful - checks-actions, checks-travis, status-appveyor
Approved by: RalfJung
Pushing 4ad1667e9ce03d51a4a003d0241b7d83ffdfba56 to master...

@RalfJung: It prints disabled backtrace instead


MSBuild process assumes generated file in project root, not at generation site

The Generator generates correct files for me, and places them right by the side of the .csx file.
However, the compile process fails and expects the file in the project root.
I'd rather have the file right beside the .csx file, or in another subdirectory.

If I write the source like this:
 context[$"generated\\Streams.g.cs"].Write($$"""{{source}}""");

This will create ANOTHER subdirectory, and then the MSBuild task will look for the file in 'P:\fennECS\fennecs\generated\Streams.g.cs' (again 1 directory too high)

Running this from the Root of the project (with the files cluttering the root), this works according to the documentation.
However, the build task does not seem to care about dependencies, and runs in full every time the solution is built (instead of tracking which, if any, .csx files were changed). This adds a significant chunk of compilation time that strongly affects test-driven development workflows.

    <PropertyGroup>
        <DisableFastUpToDateCheck>true</DisableFastUpToDateCheck>
    </PropertyGroup>

    <ItemGroup>
        <StreamTemplate Include="generators\Streams.*.csx">
            <OutputFile>generated\%(Filename).g.cs</OutputFile>
        </StreamTemplate>
    </ItemGroup>

    <Target Name="GenerateStreamRunners"
            BeforeTargets="CoreCompile"
            Inputs="@(StreamTemplate)"
            Outputs="@(StreamTemplate->'%(OutputFile)')">
        <Exec Command="dotnet-codegencs template run %(StreamTemplate.Identity) -o generated"
              WorkingDirectory="$(ProjectDir)"/>
    </Target>
    ```

    This is my current workaround.


Correct workspace doc on behaviour of mountPath

Fixes #3716
Changes
Prior to this commit we documented that if a workspace's mountPath was
relative then Pipelines would prepend "/workspace/" to it. This behaviour
has never actually worked that way. Pipelines passes the literal mountPath
value directly to the volumeMount's mountPath, without any other
processing. It's then up to the platform to decide what to do with it.
This commit fixes the workspaces doc to remove the incorrect description.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

Release Notes
Fixed doc issue: relative workspace mountPaths are not prepended with "/workspace/" and never have been.

awesome thanks
/lgtm

awesome thanks
/lgtm

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests


imo_2001_p6 is said to be buggy in HTPS paper

Hi, I see https://arxiv.org/abs/2205.11491 (written by you? ;) ) mentioning that:

... the statement is erroneous. The hypothesis h4 : b + d − a + c actually represents max(b + d − a, 0) + c. This is due to Lean’s nat type behaviour where (a : N) − (b : N) = (0 : N) if b ≥ a...

I have checked https://github.com/facebookresearch/miniF2F/blob/5271ddec788677c815cf818a06f368ef6498a106/lean/src/test.lean#L1483 and seems that it has not been updated. Thus, I guess maybe the minif2f dataset should be fixed?

A similar bug involving natural numbers is also reported here https://github.com/openai/miniF2F/issues/125https://github.com/openai/miniF2F/issues/125
I found that probably this repo is not actively merging pull-request. Maybe I am wrong.

I found that probably this repo is not actively merging pull-request.

I think so :(


Improvments

Added option to show status board first
Sorted versions by timestamp
Sorted issues by priority
Some bugfixes

Added option to show status board first
Sorted versions by timestamp
Sorted issues by priority
Some bugfixes


Add possibility to remove CA key

If CA certificate pair is provided from the third side (not generated by the role itself) it could be wisely to remove at least CA key for security reasons.
Or consider passing CA pair not by file but in memory using for example base64 encoding

Assignee is Mishavint

Created by bissquit at 2023-03-18T12:29:17Z


release: vault api patch fixes

Summary

addresses bugs introduced in last large version release

merging to complete migration


feat: call context

Previously you couldn't distinguish between windows when a method on a plugin was called. This PR gives plugins access to the caller window details.

Nice work. Is there anything we can do to help getting this merged?


AA Test

Hey @mdboom, in order for the benchmarks to be registered, you need to call lib.dump_stats(uri), where uri is a string containing the benchmark's uri, like: path/to/definition/file::benchmark-name, for example  tests/benchmarks/test_bench_fibo.py::test_iterative_fibo_10.
You can try to call it here: https://github.com/mdboom/pyperformance/commit/9234f4d0a75000c1f1b11e187a133ae4949583c6#diff-ef2cbcccccf978441b4d1bb0eeb21883285cc07d766b546ec7ca5d0942f8755eR637

Thanks!  Just noticed that and trying again ;)

@adriencaccia: So I think I have results published from this branch correctly, but it's not finding the baseline results from main.  I manually triggered them here, but is there something more I need to do?

@adriencaccia: So I think I have results published from this branch correctly, but it's not finding the baseline results from main. I manually triggered them here, but is there something more I need to do?

There was an error on our backend during the processing of both the run on master and this pull request. So the runs are not persisted on our end.
I tracked down the bug, and it is because there are multiple codspeed.dump_stats_at("deltablue".encode("ascii")) happening during a single run.
Can you ensure that this line is called exactly once during the run?
In our integrations, we always made sure to have a single dump_stats_at for each uri, so we did not handle the case where there are multiple


Multiples accounts for the same user

Hi guys,
I have many Instagram accounts, Can i connect these different Instagram accounts for a same User?

I think you can, but you'd have to log out of your current account in Instagram each time before adding another one.

Yes, that's what this library will do. You can associate any number of OAuth identities to a user account, including multiple identities from the same provider. But as @moorchegue said, the user has to be logged out, otherwise the provider will not authenticate the right user of course.

The answers given are correct.


Replace the external helpers page with a babel-runtime page

As using self-contained and babel-runtime is the preferred way to handle deduplicating helpers, and using external-helpers is more of a niche case or implementation detail of self-contained, it would be good to have an item in the "Docs" navigation for "Runtime" instead of "External helpers".
Currently the self-contained and babel-runtime information is buried in the "Transformers" page, and "External helpers" has a dedicated page in the main navigation.

I've split it up into a separate page, I'll need to spend some time thickening and cleaning it up though. PRs from anyone appreciated!

I renamed the selfContained transformer to runtime to align with the babel-runtime module that it depends on.
The phrasing could be improved and the language as it isn't super noob-friendly but it gets the job done. I'll try and improve it when I get the time as it's pretty technical.


Option to require Users to change their password if they are created by an administrator

Gitea version (or commit ref): 1.4.3
Git version: 2.18.0
Operating system: Ubuntu 14.04 LTS
Database (use [x]):

[ ] PostgreSQL
[X] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[X] Not relevant

Log gist: Not relevant

Description
Hi,
I've disabled the registration of Users and manage them via the administrator interface. On creation, I give them a big, random password and ask them to change it on login. But I can't enforce the password change. I don't want to know their password and I assume they don't want me to know that either. It would be nice to have a checkbox on the account creation "Require Password Change" on login so the user is forced to change his password once he logs in.
This could be added to the edit user page as well so the administrator could force a password rotation if needed.
Screenshots

Not relevant

I support this suggestion, but as a workaround you could set up the mailer and have Gitea send out a registration e-mail after you create a user.
The registration notification e-mail reads the following by default:

Hi {username}, this is your registration confirmation email for {Instance name}!
You can now login via username: {username}.
https://yourinstanceurl/user/login
If this account has been created for you, please reset your password first. ('Reset your password' has a link to https://yourinstanceurl/user/forgot_password)
© {Instance name}

But I think your suggestion would be a nice addition to Gitea

I would like to work on this but I have been wondering how to identify users created by an admin.. Should I add a new field to the db and *User ?
cc @lafriks @JonasFranzDEV

@jhabdas that is normal practice to need to change password that is issued when creating user, especially in companies

Of course. The point I'm raising is that of roles and privileges. What I'm hoping to draw out are questions regarding who knows what and when.
It may be possible admins are being created when, in fact, a superuser is more desirable. But the bane of this issue seems moreso to be the fact OP ever had the users password to begin with, nuanced as it may be.

If you offer someone admin and ask them to change their password, and they don't, is it possible you dont actually want them administering your software?

@jhabdas  I think permissions are not given out unless the user is activated .

I am currently working on this, would send a PR tomorrow

A checkbox on the user maint page.  Require password change on next login.

@mcg1103 this can be added as separate PR later when this is merged

I would work on that and send it as another PR


file upload not work in AFNetworking 3.0

Hello Team,
I want to upload .zip file on server so i am using AFNetworking 3.0 but i can't able to upload using it but same code works in AFNetworking 2.0  for more details i did ask question on SO check below link
Question Link On Stackoverflow
Waiting for yr reply :)

It seems your problem has been solved on SO. Can you please close this issue?


In multiple models, how to make him pre-load at one time instead of reading one by one. For example, add

In multiple models, how to make him pre-load at one time instead of reading one by one. For example, add

	Admin.GetRouter().Use(&admin.Middleware{
		Name: "preload",
		Handler: func(context *admin.Context, middleware *admin.Middleware) {
			context.DB = context.DB.Set("gorm:auto_preload", true)
			middleware.Next(context)
		},
	})


Clustering/resource management

[ch10188] [ch10325]
Sorry for formatting diffs, but I wrote these files from scratch and then replace old versions with new ones not modified existing stuff.
Basically this does the following

Introduces ResourceManager. This is something like generalization of DatasourceManager and DestinationManager but can't do anything fancy, just manage, shutdown and get by id.
Introduces CachedGetter, small wrapper around memoized I => F[Option[A]] that allows to handle indexed store content changes be handled in outer world.
Introduces WhateverModules as an abstraction used to build resources of datasources and destinations. These modules take care about all those CreateError and so on.
Removes DatasourceManager and DestinationManager, DefaultDatasources and DefaultDestinations
Reintroduces DefaultDatasources and DefaultDestinations using resource manager cache getter and WhateverModules (note, that destinations part is kinda strange a bit, as it has errors in parameters but it's not set anywhere, I preserved this, but not sure if this is intended)
Makes DatasourcesSpec working with Resource[F, Datasources[...]] instead of pure datasources
Adds tests for store being more important than cache.

@wemrysi @jsantos17 Ping 🙂

@cryogenian Sorry for the delay, I'll finish reviewing today.

@jsantos17 @wemrysi I think it's ready for another look

Made create returning EitherT[Resource[F, ?], CreateError[C], MDS]
Changed CachedGetter test message
Moved MDS alias closer to getMDS method
Use datasource.use in DatasourcesSpecs
Updated to master

Chatted with @cryogenian and I'm going to take charge of merging this PR, and all the upstream ones, after my series of breaking RateLimiter PRs lands. 🛑 is up for that reason.


Add an SOW option

After the PM has filled out the approval form, OTF wants a 'View SOW' option along with 'View Approval Form' in the table. This SOW will essentially just show a part of the entries filled in the SOW form as per this doc.

The PAF form is a stream field form that each organisation build themself. There is no way for Hypha to know what part of that form is "SOW" and what is not.

@frjo is there any way to mark those SOW fields on the form builder? or some other way to identify this information?
cc @fourthletter

I'm very hesitant to build that kind of feature. The form fields are overloaded as is making form creation more burdensome.
I would suggest something really simple. E.g that OTF att all the SOW fields at the bottom of the form and then we add a "SOW" link that goes to the PAF with an anchor tag that simply scrolls down.

Okay sounds fine.
Based on my conversation with @fourthletter, they wanted to download and be able to share SOW with external people and sharing Approval form with all the information wasn't serving the purpose. Could you suggest if this is possible in some way?

Then we need to create a completely separate form called "SOW".

okay. Will users have to fill it again? that will not be best :/

There will then be two forms. One PAF and one separate SOW that staff fills in separately with whatever is needed for the two forms.
I do not like this solution since it make the system even more complicated and there is no lack of other things to put dev time on.


steps and other parameters in Gradio

For testing and finding optimal quality it will be nice to have all these arguments and Gradio fields:
in priority order:
seed
negative_prompt:
num_inference_steps
video_num_inference_steps
min_guidance_scale: float
use_linear_guidance: bool
alpha: float
less important - can be --flags for app.py:
save_memory: bool
cpu_offloading: bool
model_dtype

Thank you for your valuable feedback! We will consider adding these features in future updates.

thank you so much
your video model is really great and worth intensive testing

https://github.com/user-attachments/assets/e629a07c-c48e-4db9-bafd-63dfb7541dbb


Allow output directory to be configured

set PACKER_OUTPUT_DIR and that's where the VM builds will end up.
Useful if your drive is constrained. I have a laptop, so I use this to redirect my builds to an external drive.

I'm not keen on this approach to have this in this repo as it enforces to have this environment variable for all other users.

Closing this. Feel free to add comments. I think there are other solutions without adding this change to the code base.


Not compatible with the version of your runing IDE

Not compatible with the version of your runing IDE（IntelliJ IDEA 2023.1）

Are you still want to use this plugin? I thought the official support of emoji & symbol is good enough.


[features request] Container grouping / State colors

Hi !
As I've noticed when doing docker-compose -p TestProject containers are created with project name testproject_ prefix. Would be nice to have containers grouped by project name and be able to start/stop all containers at once from group.
Also visually would be better to have different colors for container names based on state or maybe put states in some colored labels.
Because usually eyes look at green color but state is exited and it's a bit confusing in my opinion.
Both features are not so important just maybe more convenient )
Again thanks for this application.

Yeah looks nice.. I like the one without highlight․․ Thanks )

Decided to highlight only exited not to create a parrot-ui https://github.com/iongion/podman-desktop-companion/releases/tag/4.1.0-rc.21
Grouping into folders is planned - see https://github.com/iongion/podman-desktop-companion/issues/79


send  https request failed

curlcode is  CURLE_SSL_CACERT,  CA peer auth failed

Make sure you are installing the cacert.pem file into your project.  See the iOS Test App as an example.
curl -s https://curl.haxx.se/ca/cacert.pem > cacert.pem


update bun to 1.0.15

Why
users like new things, i like new things, we all like new things
What changed
updated bun to 1.0.15
Test plan

open repl
add bun module
bun --version prints 1.0.15

Rollout
Describe any procedures or requirements needed to roll this out safely (or check the box below)

[ ] This is fully backward and forward compatible

Does this need pkgs/upgrade-maps/mapping.nix ?

and it needs to be locked :D that's why i marked it as a draft for now


wio-terminal board does not support PWM?

Hey,
I am currently looking into the wio-terminal, which is listed as having support for pwm. But the devicetree is built as follows:

dts: boards/arm/wio_terminal/wio_terminal.dts
via #include <atmel/samd5xx19.dtsi> this includes: dts/arm/atmel/samd5xx19.dtsi
via #include <atmel/samd5x.dtsi> this includes: dts/arm/atmel/samd5x.dtsi

and in the file samd5x.dtsi all nodes tcc* are compatible = "atmel,sam0-tcc"; instead of "atmel,sam0-tcc-pwm" which, as far as I understand means that they do not support PWM?

@joelguittet

Hello
PR done to integrate the wio terminal: https://github.com/zephyrproject-rtos/zephyr/pull/54953
Obviously I haven't indicate the PWM was tested. We should verify the datasheet but I will be surprise if this MCU has no PWM at all.
Have you tried to modify the TCC compatible value ? With an overlay for example.
Joel

We should verify the datasheet but I will be surprise if this MCU has no PWM at all.

The documentation of the IC lists

PWM Modes using TC and TCC peripherals:

Up to six PWM channels on each 24-bit TCC
Up to three PWM channels on each 16-bit TCC
Up to two PWM channels on each 16-bit TC

But I am sadly not smart enough to extract the necessary parameter from the documentation (I think page 40ff). My current draft is (with wrong numbers) is:
&tcc0 {
	compatible = "atmel,sam0-tcc-pwm";
	prescaler = <8>;
	#pwm-cells = <2>;
};

&tcc1 {
	compatible = "atmel,sam0-tcc-pwm";
	prescaler = <8>;
	#pwm-cells = <2>;
};

&tcc2 {
	compatible = "atmel,sam0-tcc-pwm";
	prescaler = <8>;
	#pwm-cells = <2>;
};

&tcc3 {
	compatible = "atmel,sam0-tcc-pwm";
	prescaler = <8>;
	#pwm-cells = <2>;
};

&tcc4 {
	compatible = "atmel,sam0-tcc-pwm";
	prescaler = <8>;
	#pwm-cells = <2>;
};

Your draft looks not bad, should check the details (there are other samd board in zephyr to compare)
However, I don t think you should configure all TCC this way : is it suitable even if you don't want to use it as PWM ? (Default configuration should not be PWM except if the pin is dedicated to something that need it, brightness for example why not).

The pin PC27 is on https://wiki.seeedstudio.com/Wio-Terminal-IO-Overview/ listed as PWM0. My goal would be to get it online.

The pin PC27 does not seem to have a TC or TCC connected to it:

I think I will switch to PWM3, which is also BCM13, D6, A6. And it is related to TCC0:

But I have no idea how to choose IOSET 3.

Hello @maxhbr
I'm on it to try making the blinky_pwm sample working on it using the USER LED.
Have you made any progress on your side too ?
Joel

Hey, sorry, I sadly made no progress on the PWM front as the related issue https://github.com/zephyrproject-rtos/zephyr/issues/67049 (maybe, as you have a wio terminal in hand, you could also verify if you see the same behaviour)

Yes I'm on both tickets actually

Got it. I will make a PR soon.

@maxhbr here is the PR: https://github.com/zephyrproject-rtos/zephyr/pull/67126
Can you check on your side if this is working ? Build the blinky_pwm sample and run this on the board. You should have the Blue USER LED near to the USB connector blinking. First slowly, and then faster.
Details to permit you modification/adaptation for your own use case:

PA15 is used and set at the pwm_default entry in the dts. PA15 has PWM using TCC1 channel 3 (PA15G_TCC1_WO3 defined at https://github.com/zephyrproject-rtos/hal_atmel/blob/b0cc87f2a494d8b3c383292d1d6c7d10323932bd/include/dt-bindings/pinctrl/samd51p-pinctrl.h#L593).
tcc1 is used and compatible value is changed in the dts to enable PWM support
pwm_led0 is declared with TCC1 channel 3 in the dts

You should be able to choose another pin with PWM support and adapt the right tcc/channel :)


Connection remote server by Ionic

Is posible external connection in Ionic 5?
(ws://example.com:3000)

I made a capacitor(ionic) plugin that can support websocket remote connection, welcome to try it.


Bump 1.8.5

- What I did
bump to v1.8.5 to take care of the socket listen flag in 1.8.
- How I did it
- How to verify it
- Description for the changelog

/test all

@mrunalp @rhatdan PTAL this is so gree :)

LGTM
Merging.

Can you tag a release, so we can build it for OpenShift.

Yup, doing that as we speak Dan.


Add tool to generate C code from eBPF byte code in ELF file

As part of the plan to produce signed eBPF programs that are loadable in systems with HVCI on, the first step is to permit offline code generation from eBPF byte code.
Sample output for tool using droppacket.o from the build pipeline.
droppacket.c.txt
Signed-off-by: Alan Jowett<EMAIL_ADDRESS>

Latest output with map, helper function binding, and corresponding eBPF instructions in commnents.
droppacket.c.txt

I don't see any tests for this, can you add one? E.g., run droppacket.o through this and compare to known-good output? Or is there a way to take that output and somehow compile it back to ebpf byte code and verify it "matches" the original ebpf byte code (not sure if that's possible).

I was planning on using the test data from here:
https://github.com/iovisor/ubpf/tree/master/tests
They include blocks of eBPF ASM and the expected return value.

Converting to draft until I have the test issues investigated. Tests flagged an issue in 32-bit ALU code, so there are probably more issues.


Update docker file to use the latest python image

cf #304
Use the 3-slim rolling tag instead of using a fixed python version.

Hi @Meallia,
Thank you for your pull request and for your effort to update the Dockerfile.
After careful consideration, we've decided to move this pull request to the "wontfix" category. We wanted to provide some context for our decision:
Security Concerns: Using the latest Python image without specifying a version can introduce security risks. It may include untested or unstable changes that could impact the stability and security of our application.
Version Specificity: We prefer to specify the exact Python version to ensure consistency and maintain control over the environment. This helps us manage dependencies and security patches more effectively.
We appreciate your understanding and thank you for your contribution. If you have any further suggestions or would like to discuss alternative approaches, we would love to hear from you.
Best regards,
The Safety Team


Add text to image pipeline to generic inference

Similar to #244, this PR adds support for text-to-image pipeline.
Here is an example repo that uses BigGAN-deep-128 (the return of pytorch-pretrained-BigGAN). As can be seen, users specify their own requirements.txt and pipeline.py. I struggled a bit with the output, but it's a base64 string of the image. This PR should unblock #131.
Here is a corresponding repo template https://huggingface.co/templates/text-to-image

lgtm! 🚀

FYI @nateraw

looks great, thanks for adding this! could you share a screenshot of what the model output looks like?
The Inference pipeline returns a base 64 string with the image. I'm not fully satisfied with the output and if you look at the example repo it got quite complicated (which I'm sure it's due to my ignorance on some image stuff).

I won't merge this until @Narsil takes a look, since he probably has good insights on the output for this (not high priority so it can wait for a couple of extra days).

The Inference pipeline returns a base 64 string with the image. I'm not fully satisfied with the output and if you look at the example repo it got quite complicated (which I'm sure it's due to my ignorance on some image stuff).

seems good enough for stack overflow 😄

Another thing, is that we can send raw bytes directly with proper mimecode if we're sending only 1 image per inference (which I guess is the case here).
api_inference_community/routes.py (call_pipe) should be the place to look at.

Looks fine, but the multple dummy inheritance withing generic looks very bloated, why not have a single class handle all pipelines ?

Copied from the comment "That was the initial plan, but unfortunately it can be the case that different pipelines require somewhat different behaviour. For example, the audio pipelines also required specifying sampling rate (this is done in #266). Maybe we could have a DefaultPipeline, AudioPipeline, etc. WDYT?"

Another thing, is that we can send raw bytes directly with proper mimecode if we're sending only 1 image per inference (which I guess is the case here).

Yes, the case here is to return one image at a time. Thanks for this pointer, I'll look into this.

I sent #272 based on @Narsil feedback, which allows users to just return the PIL.Image and we take care of the encoding.
Before

img = transforms.ToPILImage()(output[0])
buffer = io.BytesIO()
img.save(buffer, format="JPEG")
img_str = base64.b64encode(buffer.getvalue()).decode('utf-8')
return img_str

Now

return transforms.ToPILImage()(output[0]) # or any other PIL.Image

I'll merge this now to unblock @mishig25. The refactoring can follow in another PR.


Impossible to pass multiple arguments to container app job

This issue is bug report:

[x] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
I it impossible to pass multiple arguments to the container. Neither in portal as the option does not exist nor in the cli (see error below).
The documentation explicitly states that this the expected format:
    --args                           : A list of container startup command argument(s). Space-
                                       separated values e.g. "-c" "mycommand". Empty string to clear
                                       existing values.

Steps to reproduce

$ az containerapp job update -n jobname -g rgname --args "-m" "test_service"

Expected behavior [What you expected to happen.]
Multiple args are set
Actual behavior [What actually happened.]
$ az containerapp job update -n jobname -g rgname --args "-m" "test_service"
unrecognized arguments: -m test_service

Examples from AI knowledge base:
https://aka.ms/cli_ref
Read more about the command in reference docs

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Cli:
$az --version
azure-cli                         2.53.1

core                              2.53.1
telemetry                          1.1.0

Extensions:
account                            0.2.2
azure-devops                      0.26.0
bastion                            0.2.1
containerapp                      0.3.33
ml                                 2.6.1
serviceconnector-passwordless               0.3.8
ssh                                1.1.1
storage-preview                    0.8.0

Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2

Python location '/usr/local/Cellar/azure-cli/2.53.1/libexec/bin/python'
Extensions directory '/Users/user/.azure/cliextensions'

Python (Darwin) 3.10.13 (main, Nov  1 2023, 17:29:04) [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Duplicate of #27011

this is so bad... trying to set up a migration job and there's no simple way to pass a command with args using the az containerapp job start command. Is there any expected fix for this soon?

This is a CLI limitation. We're looking into it. For now, please use YAML. If you're updating the job:
az containerapp job show -n $NAME -g $RG -o yaml > job.yaml
az containerapp job update -n $NAME -g $RG --yaml job.yaml

Unfortunately this not work if you have a secret in config.

Do we have any option for 'az containerapp job start' with --yaml option, how would that look ?

Do we have any option for 'az containerapp job start' with --yaml option, how would that look ?

Yes. See https://learn.microsoft.com/en-us/azure/container-apps/jobs?tabs=azure-cli#start-a-job-execution-on-demand


Ability to create custom patterns using the operator

Other than given patterns, users should be able to deploy custom patterns.

https://github.com/wso2/k8s-wso2am-operator/pull/28


Erro In install - Supervisor

I'm trying to climb the docker but this is error.
I already performed the installation of the supervisor on my kali linux and yet returns this error from the image

Hi @meetgyn
Looks like an apt cache issue similar to https://github.com/ApolloAuto/apollo/issues/6743.
6c39f05 should fix it, you may want to try again after a pull on the main branch.


add setCacheProperties(Class cacheServiceClass)

FederatedStoreProperties.java add setCacheProperties(final Class cacheServiceClass)

probably needs null check, or if null clear the key.

Codecov Report

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

@@            Coverage Diff             @@
##             develop    #1511   +/-   ##
==========================================
  Coverage           ?   65.22%
  Complexity         ?     1718
==========================================
  Files              ?      645
  Lines              ?    21628
  Branches           ?     2855
==========================================
  Hits               ?    14107
  Misses             ?     6386
  Partials           ?     1135

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 fc7b7a9...ae28697. Read the comment docs.


Chocolatey automation scripts

To check for a new release and build:
msbuild scripts\chocolatey\build.proj

If you have private chocolatey keys set in your environment variables, then it will be pushed to chocolatey.org, otherwise you just get the nupkg.
I'll setup a build on the same Bamboo server that is building rack, once this is merged. That way we'll have a push button to sync to chocolatey. If in the future, we publish releases on commits to master, then everything can be automagic.

Awesome thank you so much! 🙇🏻

We can build in the triggers on Travis or Circle CI, on the tags the same way we do in rack.


fixing a bug where dragging.style.display was not restored on dragend

Coverage decreased (-0.5%) to 86.312% when pulling d7cac8bdf8b1bf544fb6870ffdfea415352fbb36 on tkrakowiak:hotfix/dragend-fix into 0f860ff5d1f25c141eaab29b43e3f9e17b80db60 on lukasoppermann:master.


[SIZE optimization]remove git from image

Apparently there still is something that needs git in the image, so this is a placeholder / test for now.

@enggb @mohitsingalarm Do you need git on the Yocto LmP image?

@enggb @mohitsingalarm Do you need git on the Yocto LmP image?

@enggb @mohitsingalarm Do you need git on the Yocto LmP image?

How much space we are saving by removing git ? It is required by PERTS as of now.

@enggb @mohitsingalarm Do you need git on the Yocto LmP image?

@enggb @mohitsingalarm Do you need git on the Yocto LmP image?

How much space we are saving by removing git ? It is required by PERTS as of now.

about 28MB. I think there is alsom something wrong on the way git image is generated as it contains multiple copies of the same physical file in /usr/libexec/git-core . I think those should be just links.

@enggb @mohitsingalarm Do you need git on the Yocto LmP image?

@enggb @mohitsingalarm Do you need git on the Yocto LmP image?

How much space we are saving by removing git ? It is required by PERTS as of now.

@mohitsingalarm As suggested by Janne K in the meeting, we should be able to use curl instead of git to pull the repo.
I just tried these commands and it works -
curl -LSs https://github.com/PelionIoT/pelion-edge-ready-test-suite/archive/refs/tags/v2.4.0.tar.gz -o perts.tar.gz
tar -xvzf perts.tar.gz

We should update the docs to use curl then instead of git.


PR: Fix a bug when introducing commands in normal mode

Description of the change
I fixed a bug.
Steps to occur the bug
In the NORMAL mode of Vim, when you only type ":", the Issue reporter shows up.

Thank you for your contribution.
Don't worry about failed test. The failure in our tests seems unrelated to this.
I leaved a simple code suggestion.

I leaved a simple code suggestion.

Where is your suggestion? Sorry if I misunderstood.

I leaved a simple code suggestion.

Where is your suggestion? Sorry if I misunderstood.

I'm sorry. I forgot submitting the suggestion.

Thank you for your suggestion. It looked totally better, so I adopted it.

It seems we need to fix our tests first, as @ok97465 mentioned.
@ok97465, do you have time to take a look at that?

It seems we need to fix our tests first, as @ok97465 mentioned.
@ok97465, do you have time to take a look at that?

Yes, I will do this weekend.
Can we merge this PR before fixing the test?

Yes, I will do this weekend.

Great!

Can we merge this PR before fixing the test?

I don't think that's a good idea because we don't if it breaks the test suite somehow. So, it's better to fix it first and then ask @ryohei22 to merge with master afterwards.

@ryohei22, please rebase this one as well.

Merging according to @ok97465's feedback.


Tutorial use-case is against SAP license terms

Hi,
For the tutorial https://developers.sap.com/tutorials/btp-app-ext-service-add-consumption.html
The use-case is:

This tutorial shows you how to extend your CAP application to manage risks associated with suppliers. For that you will consume supplier information that is part of the SAP S/4HANA Business Partner to your CAP application.

Ie. taking data from a SAP product into a custom application(ie. non-SAP product)
SAP has licensed CAP as per described in https://tools.hana.ondemand.com/developer-license-3.1.txt
See section

(d) permit mass data extraction from an SAP product to a non-SAP product, including use, modification, saving or other processing of such data in the non-SAP product

Ie. the tutorial actively suggests a use-case that is against SAP license terms for the software used

Hi there @larshp ,
Thanks for raising this point!
We're looking into it and will get back to you ASAP after we check all aspects of the matter.
Best regards,
Svetoslav

Hi Lars,
here we go again... :-)
As written in my last email: After discussions with our legal team we were under the impression that the license only permits mass data extraction from a SAP system for the purpose to use it exclusively in a non-SAP systems. In this case we assume that we do not work against the license as CAP is being positioned as programming model for the SAP BTP. License situation is currently changing for CAP as we open source CAP in a step-wise approach and use the Apache 2.0 license for the Open Source modules, see: https://github.com/cap-js
As always our general disclaimer: we are no legal experts, the statements represent our current understanding...
Best regards
Sebastian

thanks, see email

Hi @larshp,
As it has been 2 Weeks I will be closing this issue. Please open another one if you need support regarding our tutorials.
Best regards,
Manju

heh, well, I did not get an answer to my email
I'm trying to not do the arguments for the license here, but we can do that if you prefer?


Add multi-tenant support for OAuth authentication

Motivation
Currently, KoP stores all group and offset metadata in one topic, public/__kafka/__consumer_offsets. It's not easy to extend and might encounter performance issues for large amount of consumers.

in the long run as consumers keep increasing as all these consumers share the same topic would there be slowness in committing the offsets etc.

To solve this issue, we can specify the tenant in PLAIN authentication's username, for example:
required username="public/default" password="token:xxx";

But when using OAuth authentication, there is no way to specify the tenant.
In this PR, we will introduce a way to specify tenants on OAuth authentication, and we will add a new property in credentials_file.json. For example:
{
  "client_id":"Xd23RHsUnvUlP7wchjNYOaIfazgeHd9x",
  "client_secret":"rT7ps7WY8uhdVuBTKWZkttwLdQotmdEliaM5rLfmgNibvqziZ-g07ZH52N_poGAb",
  "tenant": "my_tenant"
}

Internal design
The tenant will be encoded to a token sent by the client, the token format will be {tenant} __with_tenant__{token}, since the token only allows to (?<token>[-_\.a-zA-Z0-9]+), so here used __with_tenant__  as the delimiter. On the KoP server side, it will try to extract the tenant and token, the tenant will be used as KoP metadata tenant.
Modifications
Add multi-tenant support for OAuth authentication.
Documentation
Check the box below.
Need to update docs?

[x] doc-required
(If you need help on updating docs, create a doc issue)

[ ] no-need-doc
(Please explain why)

[ ] doc
(If this PR contains doc changes)

The tenant will be encoded to a token sent by the client, the token format will be {tenant}__delimiter__{token}, since the token only allows to (?<token>[-_\.a-zA-Z0-9]+), so here used __delimiter__ as the delimiter. On the KoP server side, it will try to extract the tenant and token, the tenant will be used as KoP metadata tenant.

Out of curiosity, is there a reason we are not setting the tenant as a claim on the token created by the authorization server? In the design proposed here, we limit a client to a single tenant, so it seems like putting this information in the client could simplify the flow and while it would require a little more configuration up front, it would mean that applications inherit the right configuration and they would not be able to supply the wrong tenant.

Out of curiosity, is there a reason we are not setting the tenant as a claim on the token created by the authorization server?

Though now we assume JWT as the token from OAuth2 authorization server in KoP. However, the token can be another format. So I think it would be better to separate the tenant info from the token.

Though now we assume JWT as the token from OAuth2 authorization server in KoP. However, the token can be another format. So I think it would be better to separate the tenant info from the token.

Makes sense. I am not familiar with other implementations of OAuth2. Is it possible that those others offer a mechanism to embed the tenant information? If so, we could have an implementation per variation.

Is it possible that those others offer a mechanism to embed the tenant information?

There is no general token format for OAuth2, see https://www.rfc-editor.org/rfc/rfc6749#section-1.4

Access tokens can have different formats, structures, and methods of
utilization (e.g., cryptographic properties) based on the resource
server security requirements.

@BewareMyPower - I agree that the spec is generic. However, if I understand correctly, we already assume that the token is a JWT right now, which implies to me that we can use those features. When another implementation comes along, it seems highly likely that those implementations would provide for a way to customize the oauth token.

we already assume that the token is a JWT right now

Yes. We can adopt the implementation that integrates the tenant with the JWT claim field for the current implementation. And it does not conflict with the quick implementation in this PR.


Sense update

Description:
Changed the way devices update.  The main component now will update every minute and dispatch the updates to the devices.  This prevents devices updating at the same time and getting closed connection errors
Related issue (if applicable): fixes issues reported in PR#21698

Is it to late for this to make the 0.94 release train ?


Proposal: technical concept for a TransferProcessStore based on SQL

What this PR changes/adds
This PR adds a document outlining some key aspects of the TransferProcessStore based on SQL such as table schema, SQL statements.
Why it does that
Before the implementation of #865 can start, there needs to be a vetted proposal in place.
Further notes
I put the file in extensions/sql/transfer-process-store, but once the proposal is accepted it should go into the appropriate folder in docs/developer
Linked Issue(s)
Closes #865
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[x] added/updated copyright headers?
[ ] documented public classes/methods?
[x] added/updated relevant documentation?
[ ] added relevant details to the changelog? (skip with label no-changelog)
[ ] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #899 (a7d0ff0) into main (b5a5d34) will decrease coverage by 0.65%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #899      +/-   ##
============================================
- Coverage     60.07%   59.42%   -0.66%
+ Complexity     2262     2165      -97
============================================
  Files           607      579      -28
  Lines         13071    12531     -540
  Branches        912      884      -28
============================================
- Hits           7853     7446     -407
+ Misses         4792     4685     -107
+ Partials        426      400      -26

Impacted Files
Coverage Δ

.../dataspaceconnector/boot/util/TopologicalSort.java
92.85% <0.00%> (-2.39%)
:arrow_down:

...taspaceconnector/azure/cosmos/CosmosDbApiImpl.java
0.00% <0.00%> (ø)

...ansfer/demo/protocols/stream/DemoTopicManager.java

...ansfer/demo/protocols/http/PubSubHttpEndpoint.java

...demo/protocols/DemoProtocolsTransferExtension.java

...tream/PushStreamProvisionedResourceDefinition.java

...o/protocols/spi/stream/message/PublishMessage.java

...mo/protocols/common/AbstractQueuedProvisioner.java

...r/transfer/demo/protocols/ws/WebSocketFactory.java

...nsfer/demo/protocols/ws/NonClosingInputStream.java

... and 22 more

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 2ce5cb2...a7d0ff0. Read the comment docs.

@paullatzelsperger Same as for the ContractNegotiationStore proposal: Would you please be so kind and define a concrete value range on each of the columns?
 Denis Neuling<EMAIL_ADDRESS>Daimler TSS GmbH, legal info/Impressum

@paullatzelsperger Same as for the ContractNegotiationStore proposal: Would you please be so kind and define a concrete value range on each of the columns?

I did the same modifications as for the other proposal (rename files, add comments). Ok for you?


Small-window mode PN processing errors

When running epchain on small-window mode without some extra configuration, it will throw errors when it finds that most of the CCD IME files are missing (small window just uses one). These errors aren't fatal to the epchain process, but they do contaminate the stderr output which DAXA parses to try to find any truly fatal errors.
As such we should identify which CCDs are available a priori and pass that list to the ccds parameter of epchain. Ideally this will eventually be done by parsing the SAS summary file (issue #34), but for now I think I can just search through files in the ODF directory.

Incidentally the reason it's important to not have non-fatal errors in the epchain stderr is because DAXA will class a process as having failed if there are any errors (not warnings), even if the final file exists.


Update Log retention to 90 Days

Update following CloudWatch log group retention to 90 days

[ ]  1. aws/rds/instance/mojo-production-nac-admin-db/error 7 Yes
[ ]  2. /aws/rds/instance/mojo-production-nac-admin-read-replica/audit 7 Yes
[ ]  3. /aws/rds/instance/mojo-production-nac-admin-read-replica/error 7 Yes
[ ]  4. /aws/rds/instance/mojo-production-nac-admin/audit 7 Yes
[ ]  5. /aws/rds/instance/mojo-production-nac-admin/error 7 Yes
[ ]  6. /aws/rds/instance/mojo-production-nac-db/error 7 Yes
[ ]  7. /aws/rds/instance/staff-device-production-dhcp-admin-db/audit 7 Yes
[ ]  8. /aws/rds/instance/staff-device-production-dhcp-admin-db/error 7 Yes
[ ]  9. /aws/rds/instance/staff-device-production-dhcp-admin-db/slowquery 7 Yes
[ ]  10. /aws/rds/instance/staff-device-production-dhcp-db/audit 7 Yes
[ ]  11. /aws/rds/instance/staff-device-production-dhcp-db/error 7 Yes
[ ]  12. /aws/rds/instance/staff-device-production-dhcp-db/slowquery 7 Yes
[x]  13. mojo-production-nac-admin 7 Yes
[x]  14. mojo-production-nac-admin-vpc-flow-logs-vpc-flow-logs-log-group 7 Yes
[x]  15. mojo-production-nac-server-log-group 7 Yes
[x]  16. mojo-production-nac-server-nginx-log-group 7 Yes
[x]  17. mojo-production-nac-vpc-flow-logs-log-group 7 Yes
[ ]  18. staff-device-production-infra-cloudtrail-log-group 7 Yes
[ ]  19. staff-device-production-infra-vpc-flow-logs-log-group 7 Yes
[ ]  20. staff-infrastructure-production-network-services-vpc-flow-log-group 7 Yes
[ ]  21. staff-infrastructure-production-smtp-relay-server-log-group 7 Yes
[ ]  22. staff-infrastructure-production-smtp-relay-server-nginx-log-group 7 Yes
[ ]  23. staff-infrastructure-production-smtp-relay-server-postfix-exporter-log-group 7 Yes

NAC and DNS-DHCP admins are blocked due to the Pipeline having pending update, It will be released in to production that should update ideally from 1-12 CloudWatch log group within the list.

we no longer need to do 18 and 19 as its part of log shipping infrastructure which is to be decommissioned.	https://github.com/ministryofjustice/staff-device-logging-infrastructure

all the RDS log groups are created by the DB instance and provisioned by AWS. I am unable to find any configuration for retention of these log groups. Some further info on the stack-overflow here
Default would have been never expire however I think this was changed manually on the console to 7 days to keep it the same as other log group.
Going forward option are:

Use a script to update the retention to 90 days
use a local provisioner and run STATIC command to set the retention
change it on the console to 90 days


Added French and Spanish as possible second langages

Dear Liu,
These changes allow to set (fr-en) o (es-en) as default.

We could modify the language button in order to add more than two languages
I didn't figure out how to set language dependent xAxisFormat in plot_types.js: '%-m/%-d' || '%-d/%-m'
-map-translation script: en2fr and en2es are not used yet => English as default.

Best wishes,

Thank you! I'll try to modify the button to support multiple languages.


How to distribute tests on multiple agents?

I'm struggling to find a good link and/or description of this in the documentation.

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

ID: 57dd4383-2206-3912-993e-773e8dc69c2d
Version Independent ID: 537e5ce0-d483-2b56-5ec9-8bdef2d01635
Content: Visual Studio Test task - Azure Pipelines
Content Source: docs/pipelines/tasks/test/vstest.md
Product: devops
Technology: devops-cicd
GitHub Login: @PBoraMSFT
Microsoft Alias: pbora

@marcussonestedtbarium Thank you for the feedback, assigning this to the author for review.

@marcussonestedtbarium - you can find a detailed doc here.
And, using the multi-agent capability for distribution with other test runners is outlined here

Hi @PBoraMSFT,
Thanks for your response! The first link explains not with YAML, but with gui config.
The second is what I was looking for. I think ti would help if that page was linked directly from the doc for the VSTest task.
Thanks for your awesome work on Azure devops
BR
/Marcus

@marcussonestedtbarium - yes, we will get the topic linked from the VSTest task doc.
Also will enhance the doc to include the YAML snippet for job setup.

👍👍
Den tis 12 nov. 2019 12:19Prachi Bora<EMAIL_ADDRESS>skrev:

@marcussonestedtbarium https://github.com/marcussonestedtbarium - yes,
we will get the topic linked from the VSTest task doc.
Also will enhance the doc to include the YAML snippet for job setup.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/vsts-docs/issues/6325?email_source=notifications&email_token=AM5JN7OAFYSK6ZI2VSRYDUTQTKGNDA5CNFSM4JLTAZE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDZ5RSQ#issuecomment-552851658,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5JN7NHKRC36BHS4PO2CLTQTKGNDANCNFSM4JLTAZEQ
.


ESP32 doesn't compile in master

used toolchain version:
xtensa-esp32-elf-gcc (crosstool-NG crosstool-ng-1.22.0-80-g6c4433a) 5.2.0

compilation error in samples/hello_world:
...
[ 30%] Building C object zephyr/CMakeFiles/zephyr.dir/arch/xtensa/soc/esp32/esp32-mp.c.obj
[ 31%] Building C object zephyr/CMakeFiles/zephyr.dir/arch/xtensa/core/cpu_idle.c.obj
[ 33%] Building C object zephyr/CMakeFiles/zephyr.dir/arch/xtensa/core/fatal.c.obj
[ 34%] Building ASM object zephyr/CMakeFiles/zephyr.dir/arch/xtensa/core/xtensa-asm2-util.S.obj
/home/matthias/workspace/zephyr/arch/xtensa/core/xtensa-asm2-util.S: Assembler messages:
/home/matthias/workspace/zephyr/arch/xtensa/core/xtensa-asm2-util.S:161: Error: unknown opcode or format name 'wsr.lbeg'
/home/matthias/workspace/zephyr/arch/xtensa/core/xtensa-asm2-util.S:163: Error: unknown opcode or format name 'wsr.lend'
/home/matthias/workspace/zephyr/arch/xtensa/core/xtensa-asm2-util.S:165: Error: unknown opcode or format name 'wsr.lcount'
/home/matthias/workspace/zephyr/arch/xtensa/core/xtensa-asm2-util.S:198: Error: unknown opcode or format name 'rsr.lbeg'
/home/matthias/workspace/zephyr/arch/xtensa/core/xtensa-asm2-util.S:198: Error: unknown opcode or format name 'rsr.lend'
/home/matthias/workspace/zephyr/arch/xtensa/core/xtensa-asm2-util.S:198: Error: unknown opcode or format name 'rsr.lcount'
zephyr/CMakeFiles/zephyr.dir/build.make:198: recipe for target 'zephyr/CMakeFiles/zephyr.dir/arch/xtensa/core/xtensa-asm2-util.S.obj' failed
make[2]: *** [zephyr/CMakeFiles/zephyr.dir/arch/xtensa/core/xtensa-asm2-util.S.obj] Error 1
CMakeFiles/Makefile2:521: recipe for target 'zephyr/CMakeFiles/zephyr.dir/all' failed
make[1]: *** [zephyr/CMakeFiles/zephyr.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

@lpereira FYI

I meeting same issue， My toolchain gcc vesrion is 6.3.0

This seems to be related to the new assembly framework.  @andyross, could you take a look here?
In the meantime, please use an older version of the SDK.
@lgl88911 What toolchain are you using that comes with GCC 6.2.0?

I can't reproduce this, unfortunately.  I just pulled and installed a clean version of the "g6c4433a" toolchain (md5sum 3e00f8faa7360ebfc39971d2d2f3522d xtensa-esp32-elf-linux64-1.22.0-80-g6c4433a-5.2.0.tar.gz, just in case they're playing games) and got a working build and executable from a bunch of different tests.
Can you verify that you're using the toolchain you think you are?  ESPRESSIF_TOOLCHAIN_PATH is set to the new one and not the old one?  Try make with VERBOSE=1 and manually check the compiler path?
@lgl88911 : you're most definitely using the wrong toolchain.  That one is for the qemu emulator.  Xtensa toolchains are not portable across different variants.  You need one built for the particular CPU in question.

@locomuco A shot in the dark here: what's the esp-idf version you're using? This code in particular depends on something that core-isa.h defines, and this file is provided in esp-idf.

Do you have the full build output? I think I've nailed it down here to a set (but empty) ZEPHYR_GCC_VARIANT environment variable that was superseding ZEPHYR_TOOLCHAIN_VARIANT. This was calling the wrong assembler. By fixing the environment variables and a clean build directory, I got this CMake output:
-- Generating zephyr/include/generated/generated_dts_board.h
-- The C compiler identification is GNU 5.2.0
-- The CXX compiler identification is GNU 5.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /.../esp/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc

Which shows that it correctly found the ESP32 toolchain.  The build works as usual.  I'm sending just a simple PR that enables Zephyr to be built with the latest ESP-IDF.

@lpereira thanks, the variables fixed it on my side too

@lpereira Thanks, I export ZEPHYR_GCC_VARIANT=zephyr cause"ZEPHYR_GCC_VARIANT is deprecated, please use ZEPHYR_TOOLCHAIN_VARIANT" and using the wrong toolchain. Now remove ZEPHYR_GCC_VARIANT=zephyr ,compile pass

Hello, I'm using the zephyr-sdk-0.10.3 and I can't build the "hello-world" with esp32 board. The error is the same as the original posted.
Thanks.