Use identityserver4 handling roles,claims,user, etc by EF

I guys, I have to use identityserver4 and EF for authorize a web application. I would like to do that checking scope, roles, claim and users that will be memorize in a SQL Server DB.
I can't find an example, I have read the doc online, where explaining like to implement EF, but it doesn't explain like to use the roles memorize in the store.
So can you help me!? Can you explain me like to receive the roles from DB to ability the property Authorize in c# language ?

Scopes, and Clients can be configured like this: https://identityserver4.readthedocs.io/en/release/quickstarts/8_entity_framework.html
User identity is your responsibility. ASP.NET Identity can be used like this: https://identityserver4.readthedocs.io/en/release/quickstarts/6_aspnet_identity.html
Further questions like this should be asked on StackOverflow. This has the advantage that questions and answers can be easily found by search engines, and that there are more people answering questions than just us.
For IdentityServer4
https://stackoverflow.com/questions/tagged/?tagnames=identityserver4&sort=newest
For commercial support
https://identityserver.io/


WIP: disruptive testing

This provides tests for PR #196.
It is a superset of PR #228, which in turn is a superset of PR #234.

@avalluri I previously pointed you to my sanity-testing-normal-driver branch for testing your PR. Please use this here instead.

I've rebased on top of the changes for PR #236.

Exposing it enables writing tests that are more focused on a particular aspect and thus easier to debug when something goes wrong. I think that's important.
Testing cache volumes will also be easier that way.

To demonstrate what I meant with that I added a test for cache volumes: cd25587ef1e00dd34e954f303512f4cee449d958

@pohly would you mind if I take this PR in #196

Amarnath Valluri<EMAIL_ADDRESS>writes:

@pohly would you mind if I take this PR in #196

Not at all, please do. Merging them together always has been the goal.

Merged via PR #196

The changes already merged as part of #196


create external name service

Here is an example of creating an external name service.
kind: Service
apiVersion: v1
metadata:
#when looking up this service using the service name, the cluster
#DNS will return a CNAME record with the value quotes.rest
name:  random-quote-service
spec:
type:  ExternalName
externalName: quotes.rest #must be a valid DNS name.  e.g. you can't do https://quotes.rest/qod

Here is an example of creating an external name service.
kind: Service
apiVersion: v1
metadata:
#when looking up this service using the service name, the cluster
#DNS will return a CNAME record with the value quotes.rest
name:  random-quote-service
spec:
type:  ExternalName
externalName: quotes.rest #must be a valid DNS name.  e.g. you can't do https://quotes.rest/qod


Add history option to persist slide state across page reloads

Description:
solves https://github.com/animotionjs/animotion/issues/31
Problem:
When editing a presentation with Reveal.js and saving changes, the presentation always reloads back to the beginning. This behavior can be disruptive, especially when working on longer presentations, as it requires manually navigating back to the slide being edited.
Solution:
Add the history option to the Reveal.js initialization configuration. The history option helps preserve the state of the current slide across page reloads, allowing users to continue from where they left off.
Proposed Configuration:
<Presentation
    options={{ history: true, transition: 'slide', controls: true, progress: true, hash: false }}
>

Rationale:
Enabling the history option will significantly enhance the user experience by maintaining the current slide state during development and editing, thus improving workflow efficiency.
Additional Context:
The history option utilizes the browser's history API to store the current slide number. This small addition can make a big difference in usability without affecting other functionalities.

Feel free to adjust the content as needed before submitting the pull request.

Thank you! 😄


ng-options

Hi.
I'm working with an expression in ngOptions, AngularJS v1.4.0-rc.1.
item.SourceID group by item.SourceTypeName disable when item.disable for item in    destination.tempItemList track by item.UUID

The problem occurs when the data is changed and there is an selected element in the ngModel and this is disable in the source. It is only created with the attribute 'disabled', missing the 'selected'
Regards.

Can you please post a reproduction on plnkr.co or similar?

Certainly, the structure in the app is more complex because it has inner objects which feed the select. I did a light version and it's working right.
http://plnkr.co/edit/w21eUVz4Y2gTVJqj0gqI?p=info
I'll try to reproduce the error with a complex structure, and if I get it, i'll let you know it.
Regards.

I believe that you cannot select a disabled element so this would seem like the correct behaviour to me. Or am I missing something?

Does this happend in all browsers? There are a few similar issues, possibly because select + disabled isn't completely specced out.

@petebacondarwin, the selected element isn't the disabled one. anyway I had to change to 1.3 because I started to have problems with ngOptions in a simple select too, if I modified the scope, it didn't update the dom, but if manually I selected an element in the browser, the scope was modified. And certainly I'm not sure if my js code is the problem or the angular one.
When I have time, I'll try to reproduce the error again.
@Narretz The problem happend in FF and chrome. Yep, it's a new feature.

@RafaMedina sorry that this is causing you a problem. I would really like to get to the bottom of what is causing your issue. My understanding is that the plunker that you supplied is not exhibiting the issue. Is that right?

Closing due to lack of response.


Add generic launch.json for debugging unittests and running python files.

Changelog
Add launch.json for debugging unittests and running python files.
Includes "justMyCode": false, to also check interactions with installed libraries (e.g. scanpy)
Issue ticket number and link
~Closes #xxxx (Replace xxxx with the GitHub issue number)~
Checklist before requesting a review

[x] I have performed a self-review of my code

[x] Conforms to the Contributor's guide

Check the correct box. Does this PR contain:

[ ] Breaking changes
[x] New functionality
[ ] Major changes
[ ] Minor changes
[ ] Bug fixes

[x] Proposed changes are described in the CHANGELOG.md

[x] CI tests succeed!

@rcannood as an alternative, we could re-add launch.json back to .gitignore... WDYT

It seems like you prefer adding the launch.json to .gitignore.... So please Add the launch.json to the .gitignore ;)


white edges

I've been working on this :

but when I get the Tkinter-designer result with the white edges buttons:

You can have an extra background layer in the button group which matches the background color to avoid that thing.


Remove infinitescroll in single page

Remove infinitescroll in single page

if url has params or hash, it does not work
https://github.com/TryGhost/Casper/blob/master/assets/js/infinitescroll.js#L4

Thanks for the improvement, @zce !!! 👍


Added smart-leds-matrix crate to the display driver list.

Thank you for helping out with embedded-graphics development! Please:

[ ] Check that you've added passing tests and documentation
[ ] Add a CHANGELOG.md entry in the Unreleased section under the appropriate heading (Added, Fixed, etc) if your changes affect the public API
[ ] Run rustfmt on the project
[x] Run just build (Linux/macOS only) and make sure it passes. If you use Windows, check that CI passes once you've opened the PR.

PR description
Added smart-leds-matrix crate to the display driver list.

Nice work on the crate! Would you mind adding it to the list in alphabetical order instead of at the bottom please?

Thanks!
README is fixed now.


chore: bdd-gh-1586610371 to 0.0.1

chore: Promote bdd-gh-1586610371 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Disable unicode cargo feature in bstr

Disable bstr unicode cargo feature since it is unused in
artichoke-backend. This change removes some dependencies of bstr
from the Cargo.lock file.
Remove bstr dependency from artichoke-frontend. This dependency
likely has not been used since the introduction of the string module
in artichoke-backend.

This PR removed 2 deps from Cargo.lock.


MeshChanged EventHandler is not called when single array elements are changed

Example:

var cube = new Cube();
cube.Colors[2] = (uint)ColorUint.Red; // no event handler

var tmpArr = new uint[] { (uint)ColorUint.Red, (uint)ColorUint.Blue, ... }
cube.Colors = tmpArr; // event handler is called

Possible solution: Observable Collection
may fix: #456

To make things even worse:
https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1819?view=vs-2019

Arrays returned by properties are not write-protected, even if the property is read-only. To keep the array tamper-proof, the property must return a copy of the array.

After talking to @RedImp1470 pushed directly to develop with  66eece2f9769f08bb2a22108b38a03f708b7ea2d and 66eece2f9769f08bb2a22108b38a03f708b7ea2d

Reversed commits as these changes are too broad to merge without review!
New feature branch.

I've implemented an ObservableArray<T> which can be used the same way as the arrays could be used before, however all Mesh attributes are now readonly to prevent any shenanigans with vanishing EventListeners when assigning a new array to an attribute. To assign a new value, a user needs to call the Assign() method, which takes care of everything, as the implicit operator needs to be static and can't be used in this case.

Second try: #533

See #605


MSBuild nuget package restore not working, no instructions

Trying to use msbuild to build our Web Application Project on our build machine (VS2019 not installed) and getting nuget package errors. Says to use nuget, but I don't have nuget(?) . How do I get the nuget packages to install?
I've already tried msbuild /t:pack

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

ID: 906d0438-0338-0167-3a38-d213ee187ddb
Version Independent ID: b558fa0c-f549-1e6a-c2db-fd2e6a2351be
Content: Troubleshooting NuGet Package Restore in Visual Studio
Content Source: docs/consume-packages/Package-restore-troubleshooting.md
Product: nuget
GitHub Login: @JonDouglas
Microsoft Alias: jodou

Please check this guide.
Please note: msbuild /t:pack is for packing not for restore, instead please try: msbuild /t:restore
Do you have packages.config or sdk style projects?


Input applyClass does not take in account [class.name] and [ngClass]

When applyClass using both [class.name] and [ngClass] are not applied:
<svg-icon src="assets/icons/arrow.svg" class="icon" [ngClass]="{'icon-lg': true}" [class.icon-lg]="true" [applyClass]="true"></svg-icon>

Results in:
<svg ... class="icon"></svg>

I think we can read it through this.el.nativeElement.classList then just pass it down to this.setClass

It's an old issue but for anyone stumbling across, a workaround is setting the classes like this:
 <svg-icon
        src="icon.svg"
        [applyClass]="true"
        class="{{ size === 'small' ? 'h-3 w-3' : 'h-4 w-4' }}"
></svg-icon>


Optimal Signature Verification in Account Contracts

The optimal solution (in terms of number of constraints for the entryPoint function in account contracts) is to first compress the payload with an efficient hash function and then sign over the compressed payload:
const message = pedersenCompress(payload);
const signature = this.signer.constructSignature(message, this.privateKey).toBuffer();

Note that pedersenCompress is the turbo-pedersen hash (i.e. crypto::pedersen_commitment::compress_native). This version of Pedersen compression is not supported by Noir (noir supports the lookup-based Pedersen called crypto::pedersen_commitment::lookup::compress_native). Once we have the new design for Pedersen implemented, then we should implement this in entrypoint_payload.ts.

Decided to use the existing crypto::pedersen_commitment::lookup::compress_native which will be drop-in replaced by the new Pedersen (whenever we have it), so I am closing this.


Run ElastAlert rule only once

I'm looking to run multiple ElastAlert instances each as Azure Functions with different rules triggered by external independent timers.
Is there a way to have ElastAlert run a specific action file just once and then exit? i.e. I dont want to utilize the run_every parameter and utilize my external timers to handle when ElastAlert performs the query against ElasticSearch.

If you provide --end, it will exit when it gets to that time. So doing something like elastalert --verbose --end $(date --iso-8601=seconds) will make elastalert run from the last end time up to the present time, then stop.

I have managed to install ElastAlert (pip install elastalert) into a python Azure Function.
Is it possible to run the ElastAlerter class without passing in config & action files and instead programatically set the values that the config/action files would of been parsed into?

Not really. It's technically possible of course, but very difficult.
Do you have access to making temp files?

The solution proposed with the --end-flag seems not to be working anymore. If I get it right, the problem is that with the advent of elastalert 2.0 the job execution has been delegated to apscheduler's BackgroundScheduler. So in this case, the call to self.scheduler.start()is returning immediately and elastalert is exiting before the jobs have been run.
This is very unfortunate as this also breaks the 'run elastalert in Lambda-function' use-case.
Not sure how to run elastalert once now. Any clue would be much appreciated.

@g-io
I haven't tested this myself but the code looks like it supports this still.
           next_run = datetime.datetime.utcnow() + self.run_every
            # Quit after end_time has been reached
            if self.args.end:
                endtime = ts_to_dt(self.args.end)
                if next_run.replace(tzinfo=dateutil.tz.tzutc()) > endtime:
                    exit(0)

Perhaps it's exiting immediately for you because the --end flag is too close to the current time. Can you try making sure that it has at least one full run_every between the start and end times?

@Qmando yes good point, that would work (although it needs to be at least run_every between now and end time it seems?), I've tested it yesterday already after looking into the code. However, would work in most cases and doesn't support the Lambda case really well.
If I get it right (haven't looked into the code but from my experience of running elastalert 1.x on Lambda) the semantics before was: Run until all jobs which have been gathered are finished, and end-time reached. This was ideal for the Lambda case, as I could let the Lambda run with --end=<now> every few minutes, to process the last minutes. The runtime of the Lambda then is usually short, say a few seconds, because elastalert would exit. This leverages the operational savings of running it in Lambda.
Allowing the Lambda to run longer was helping the case of a longer timeframe to cover or a peak in records to query, which I could do because elastalert would quit when the records had been processed, might that be many or few.
Now the processing is done in a different thread from the end-condition checking without any communication about the status of the jobs. Any job could be stopped while running, no matter how wisely I try to choose the runtime by adjusting run_every and --end. So either I try to choose a small timeframe (say 30sec) and hope that usually all jobs will finish in that time or I choose a long one (say 3min) and I will overpay because my Lambda is still running all the time with my elastalert sleeping. (Overpaying will always happen in this scenario because I have to idly wait until check_every has passed and end is reached, it's more a matter of how much, but well, as long as it's just some seconds per minute...)
Also I'm wondering, will elastalert jobs tolerate being stopped by the main thread repeatedly, which could happen? Will the status always be consistent so that I could safely start fresh where before a process has been interrupted? I've come across weird cases with eg
RuntimeError: cannot schedule new futures after shutdown playing with  run_every and --end numbers.
I might be missing something obvious, but decoupling the jobs (running in the background) from the exit condition checking seems harmful.

The solution proposed with the --end-flag seems not to be working anymore. If I get it right, the problem is that with the advent of elastalert 2.0 the job execution has been delegated to apscheduler's BackgroundScheduler. So in this case, the call to self.scheduler.start()is returning immediately and elastalert is exiting before the jobs have been run.
This is very unfortunate as this also breaks the 'run elastalert in Lambda-function' use-case. Not sure how to run elastalert once now. Any clue would be much appreciated.

I ran into this same issue. I ended up extending the ElastAlerter class and overriding the start() method to get it working. Details are here: https://github.com/jertel/elastalert2/discussions/1169


Extend Chain API, fix typos

Sorry this took so long, I had actually forgotten about this until now! I made a few simple additions to the Chain API, added some tests and fixed some typos. Let me know if these changes are ok.
issue #9

Thx it looks great


error_boundary_fix

Supersedes https://github.com/johltn/ifc-pipeline-validation/pull/11

I'm merging this ahead of review so that we can deploy but feel free to still add comments and then they will be addressed subsequently.


Godot not opening

Tested versions
4.2.1, 4.2, 4.1.3
System information
Windows 11, 4.2, 4.2.1, 4.1.2, Mobile
Issue description
When I launch Godot which was 4.2 it just gives me a grey screen and never shows the logo and directly closes like nothing. I tried to go with Godot 4.2.1 and 4.1.3 which was the first version I ever use it never opens.
Steps to reproduce
Please Contact me at my email which is again<EMAIL_ADDRESS>
Minimal reproduction project (MRP)
I have no project If you want to Contact me here is my email<EMAIL_ADDRESS>

Please provide details here, you're not going to get an email, this isn't a support channel this is to report bugs
Please provide your system details, not only operating system, this is very likely due to hardware or drivers

Closing due to lack of response, if you provide the requested information this can be reopened


Revert builtin cost rework

Revert "fix aot contract executor not passing builtinstats (https://github.com/lambdaclass/cairo_native/pull/849[)"](https://github.com/lambdaclass/cairo_native/commit/e2f895c707acf0b5c74fe42eb3d076f4cebfe4f2)
Revert "Builtin costs rework (https://github.com/lambdaclass/cairo_native/pull/837[)"](https://github.com/lambdaclass/cairo_native/commit/9dffb6165200f90263fee24e1db4d90a85a89fd0)

We need to revert this changes, because they are causing some errors when re-executing blocks in Starknet Replay
Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

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

Project coverage is 82.82%. Comparing base (4ba9e16) to head (9dffb61).

Files with missing lines
Patch %
Lines

src/executor/contract.rs
50.00%
4 Missing :warning:

src/types.rs
0.00%
2 Missing :warning:

src/executor.rs
92.85%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #874      +/-   ##
==========================================
- Coverage   82.83%   82.82%   -0.01%
==========================================
  Files         120      120
  Lines       35148    34941     -207
==========================================
- Hits        29114    28941     -173
+ Misses       6034     6000      -34

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


Allow PolylinePipeline.generateArc to accept an array of heights for one position

PolylinePipeline.generateArc accepts either a number or array of numbers for the height value.  However, if there was only one position, the function was only expecting height to be a number instead of an array.  This adds a check so I can do something like this:
var newPositions = PolylinePipeline.generateArc({
    positions: [myPosition],
    height: [30]
});

Good catch.  Update CHANGES.md with this minor fix.

@pjcozzi ready

Thanks!


Xcode 8 (beta 3), Swift 3.0 + Cocoapods - No such module

Setup

Fresh, brand new Xcode 8 (beta 3) project (iMessage extension).
Added the swift3 branch to my Podfile:

   source 'https://github.com/CocoaPods/Specs.git'
   platform :ios, '10.0'
   use_frameworks!

   target 'downlow' do

    pod 'Alamofire',
     :git => 'https://github.com/Alamofire/Alamofire.git',
     :branch => 'swift3'
   end

Ran sudo gem install cocoapods --pre
Install worked fine, and project compiles via workspace file
Import:

import AlamoFire
I get the age old issue: "No such module: Alamofire".
 I don't remember this being a problem in past projects.

Note: I've done clean, re-open Xcode, clean more, re-compile etc. I've added the Alamofire framework to Linked Frameworks and Build phases (although I don't ever remember having to do this before) and it's still not compiling.

So this might be completely wrong, but have you tried Cmd+B to build it first. That usually fixes that error for me.

I've tried to build the project, yes.
Could it be the fact that it's an extension?
Like I said, I've even manually added the framework to Linked Frameworks and Build Phases.

I wasn't included my extension as a target in my Podfile (see below). Closing as fixed.
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '10.0'
use_frameworks!

target 'MyApp' do

 target 'MyExtension' do

  pod 'Alamofire',
   :git => 'https://github.com/Alamofire/Alamofire.git',
   :branch => 'swift3'

 end

end

Thank you !

thank you

So no one had a solution for this bug issue...?

I am also facing the same issue.plz help...

I also have this issue

@terryworona i have the same problem I tried your method but didn't succeed what to do next?

Otherwise make sure you have the most updated version of xcode

1

Same issue
https://forums.swift.org/t/whats-happening-that-i-receive-always-no-such-module-module-name/14752/2

I still have this issue and I have ended my programming life due to it.

Never mind I solved it. most times it will be a problem with your pod file. As of August 2018, the podfile will be
`source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '10.0'
use_frameworks!
target '' do
pod 'Alamofire', '~> 4.7'
end`

LOL to my above comment.


Comments are coming in centre.

I am using your .emacs.d but had my customisation placed in init-local file, i am trying to put a comment but the emacs is automatically putting it into the centre, also while copy some code from browser to emacs, emacs takes lot of time while pasting it into the buffer, could you please help suggest which modules might be initiating this behaviour.
I am attaching the screenshot here.

Use ;; for comments on their own line. ; comments are for adding comments after the code on a single line. Please refer to the Emacs Lisp Reference. Hope that helps!

thanks a lot sir.


Formating error when generating esil

This was a "dumb user" error because I passed not an extracted file but the original file. Perhaps an error msg letting folks know this is not the valid .json file needed.
bin2ml generate nlp --path <file.so> --instruction-type esil --data-out-path . --output-format <single || funcstring>
thread 'main' panicked at src/files.rs:61:51:
Unable to read file: Error { kind: InvalidData, message: "stream did not contain valid UTF-8" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Also if I put an invalid json I get an error as well.
bin2ml generate nlp --path file.so_reg.json --instruction-type esil --data-out-path . --output-format single
thread 'main' panicked at src/files.rs:295:18:
Unable to load and desearlize JSON: ()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

bin2ml generate nlp --path file.so_reg.json --instruction-type esil --data-out-path . --output-format funcstring
thread 'main' panicked at src/files.rs:208:18:
Unable to load and desearilize JSON: ()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Thank you again for the great feedback @cielonet. I will add some checks to the CLI 👍🏼

@cielonet , I have addd some initial validation to the CLI on dev. If you have a mo, could you give it a try?

Hey for the most part your changes worked well. I did find another little one nothing major. Otherwise thank you for the fixes...
bin2ml extract --mode cfg --fpath ../binary --output-dir thisfilefolderdoesnotexists
Unable to create file!: Os { code: 2, kind: NotFound, message: "No such file or directory" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted (core dumped)```

Hey for the most part your changes worked well. I did find another little one nothing major. Otherwise thank you for the fixes...
bin2ml extract --mode cfg --fpath ../binary --output-dir thisfilefolderdoesnotexists
Unable to create file!: Os { code: 2, kind: NotFound, message: "No such file or directory" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted (core dumped)```

I think this behaviour is correct. I didn't want to create repos that could be typos etc automatically and instead assume the directory is created beforehand. Does that make sense for your use case?

Hey for the most part your changes worked well. I did find another little one nothing major. Otherwise thank you for the fixes...
bin2ml extract --mode cfg --fpath ../binary --output-dir thisfilefolderdoesnotexists
Unable to create file!: Os { code: 2, kind: NotFound, message: "No such file or directory" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted (core dumped)```

I think this behaviour is correct. I didn't want to create repos that could be typos etc automatically and instead assume the directory is created beforehand. Does that make sense for your use case?

I am no expert in rust. Far from it, but I believe there is a way to catch these types of errors more elegantly so that core dumped isn't outputed using match.
match file_result {
        Ok(_) => {
            println!("File created successfully!");
            Ok(())
        }
        Err(err) => {
            if err.kind() == io::ErrorKind::NotFound {
                Err(io::Error::new(
                    io::ErrorKind::NotFound,
                    "The specified directory does not exist.",
                ))
            } else {
                Err(err)

This is just the QA guy in me :-). Thank you for looking over it.

Sorry I feel like I'm spamming now :-( --- I tried using dedup this morning and even with valid expected data I was getting an error msg.
# using expected file
root@ae6a62491516:/app# touch out.json
███████████████████████████████████████████ 1/1
root@ae6a62491516:/app# bin2ml dedup esil --filename file_cfg-efs.json --output-path out.json
thread 'main' panicked at src/dedup.rs:282:45:
Failed to create writer: Os { code: 2, kind: NotFound, message: "No such file or directory" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted (core dumped)

# wrong type of json file
root@ae6a62491516:/app# bin2ml dedup esil --filename file_cfg.json --output-path out.json
███████████████████████████████████████████ 1/1
thread 'main' panicked at src/dedup.rs:75:14:
Unable to load function data from file_cfg.json: Error("invalid type: sequence, expected a map", line: 1, column: 0)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted (core dumped)
root@ae6a62491516:/app# ls
file_cfg-efs.json  file_cfg.json  out.json

It's not spam! All of these are valid. I'll look to fix the new one too!

@cielonet, I think I've fixed all of these on main. Could you check them out?

Assuming everything is all good! 👍🏼


Testing on OSX

Now that we're not using apt-get in Travis, it might be a good idea to enable OSX in travis testing.
It should be a simple fix, adding - osx under - linux in the os category.

Huh, not a productive avenue, since there is Travis OSX is pretty hard to wrangle for python projects. no virtualenv on their OSX images, and that's the very first thing executed by most install scripts. Some have gotten this working, but it looks very hacky.
Lame that this works out of the box in other languages (Julia, Go) but not in python...

Of note, though, is their suggestion in documentation of the environment variables not to rely on HOME=/home/travis
We rely on it to set PATH to use miniconda. We might want to call to pwd for the current directory, and install anaconda into a known place using something like -p ./miniconda.

I can work on this.
I have done some previous work to enable a python build on Travis.
A good approach already noted by @ljwolf is installation of Anaconda distribution or (miniconda) on a travis machine, and if required install packages using homebrew.
Some resources which were helpful are conda docs and a particular stack exchange question
I will report if any problems arise for guidance.

A few note that might be helpful:

I would be cautious using homebrew as the dependencies are placed into /usr/local and, if we ever want to do #2, this could be a problem (if pandas were a dependency for example).  The alternative is to use the requirements and run tags in the meta.yaml file to specify the dependencies.
Recently, I have been playing around with binstar to serve dependencies (GDAL, OpenCV, Boost, etc.) to python packages that are not pip installable.  [Here] (https://github.com/USGS-Astrogeology/conda-gdal) is a link to an example where an OSX and Linux build of GDAL are created using TravisCI.  The resultant packages are then uploaded to my binstar so that anyone can do a conda install gdal -c jlaura.

If this looks appealing, I can offer assistance with any setup questions.
P.S. The GDAL build is not 100% stable yet, OpenCV is, but the GDAL one is maybe closer to what PySAL would be.

Testing with OS X will be resolved in #1179


Fixed CI integrity check

Q
A

Bug fix?
no

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets
-

License
Apache 2.0

What's in this PR?

Fixed CI integrity check.
Why?

On Go v1.16.4 the go.sum lines are treated differently than on v1.16.3 by go mod tidy.
Currently the widespread development environment is still v1.16.3, because Homebrew doesn't have a v1.16.4 formulae yet.
As long as v1.16.4 is not available from Homebrew it is safer to leave the CI check on v1.16.3 for local vs CI development environment compatibility.
An alternative would be turning off the Go module dependencies integrity check.
Additional context

1.16.4 (newer than local)

vs
1.16.3 (same as local)

Checklist

~Implementation tested (with at least one cloud provider)~
~Code meets the Developer Guide~
~OpenAPI and Postman files updated (if needed)~
~User guide and development docs updated (if needed)~
~Related Helm chart(s) updated (if needed)~

1.16.4

vs
1.16.3

I was wrong about this one, messed up the repro branch which led me to bad conclusions.
Fixing it in https://github.com/banzaicloud/pipeline/pull/3487


Change Downloads to MultiTypeComponent

This PR makes Download a MultiTypeComponent so custom download components can be made.

Looking great!

Codecov Report

Merging #447 (f3d3d43) into main (aa06e56) will increase coverage by 0.08%.
The diff coverage is 88.50%.

@@            Coverage Diff             @@
##             main     #447      +/-   ##
==========================================
+ Coverage   69.25%   69.34%   +0.08%
==========================================
  Files          76       77       +1
  Lines        8945     8980      +35
==========================================
+ Hits         6195     6227      +32
- Misses       2750     2753       +3

Impacted Files
Coverage Δ

lumen/tests/test_variables.py
98.38% <85.71%> (-1.62%)
:arrow_down:

lumen/downloads.py
86.66% <86.66%> (ø)

lumen/dashboard.py
74.45% <100.00%> (+0.04%)
:arrow_up:

lumen/tests/validation/test_views.py
100.00% <100.00%> (ø)

lumen/util.py
66.95% <100.00%> (+0.43%)
:arrow_up:

lumen/views/base.py
63.98% <100.00%> (-1.15%)
:arrow_down:

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


Flutter sys-account example

Sorry for the large commits, most of them are generated protobuf addition to flutter client.
related to #633  #609 #611
Things to highlight:

GRPCWeb works
Flutter web works => make flu-web-run
GRPC-UI via => make this-run-example followed by make this-run-example-ui

Example UI:

Its GOOD that all generated assets are committed to the REPO.
Will commit this


Spellcheck everything

I don't make typos, I just can't spell 😆

I believe this is done constantly while rewording things. Therefore I am closing this.


storage: Fix unexpected flow control after unsafe destroy range -- cp to 7.1

What is changed and how it works?

Issue Number: Close #17304

What's Changed:
Fix unexpected flow control after unsafe destroy range

Flow controller detects pending compaction bytes jump before and after unsafe destroy range. If there is a jump, the controller enters a state that would ignore the high pending compaction bytes until it falls back to normal. Previously, the controller may not enter the state if the pending compaction bytes is lower than the threshold while long term average pending bytes is still high. Then it would trigger flow control mistakenly.

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[ ] Need to cherry-pick to the release branch

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Release note

Fix the possible flow control after dropping a large table or partition

/test pull-unit-test


turbo-frame "_top" redirect to URLs containing '#' terminates URL at '#'

I noticed this while working with Stripe checkout URLs, which are in the format of:
https://checkout.stripe.com/pay/cs_test_a17h7hJ0yuLabPNRPjNhP6iKpyqkrEGhfQ7tk6Jma0QFC20ppupggSXGbr#fidkdWxOYHwnPyd1blpxYHZxWmJvQmBSTn1ncTxybWtsd2F0YWFmYTF%2FSjU1fzZDNFI0XGgnKSdjd2poVmB3c2B3Jz9xd3BgKSdpZHxqcHFRfHVgJz8ndmxrYmlgWmxxYGgnKSdga2RnaWBVaWRmYG1qaWFgd3YnP3F3cGB4JSUl
A hashtag appears about a third way thru all their URLs. → gSXGbr # fidkdW
I reconfigured the form I'm submitting to use date-turbo-frame="_top" instead of data-turbo="false" so that I could replace the form using turbo streams on validation errors and do a full redirect to Stripe on success. I then noticed the successful redirect to Stripe stopped working — Stripe would load but just hang while trying to load the checkout page. This was caused by the Stripe URL that turbo was trying to redirect to being ended at where the hashtag appears in the URL.

I have crafted a demo showing the issue in action.
Both buttons hit the same endpoint /redirect/ that returns a 303 redirect to an expired Stripe Checkout URL.
It is available here: https://turbo-redirect-test.onrender.com/

Duplicate of https://github.com/hotwired/turbo/issues/211


Prepare for new release of Confluence

Workflow links: https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/6105344594, https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/6105346672, https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/6105348796.

https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/6105344594 fails because Confluence 8.0+ doesn't support running on JDK 8. You have to be running JDK 11 or higher. You're getting classloading errors from Synchrony Proxy because of this


add upload_to_dandi

I am not able to merge

Thanks @bendichter.  I will review and then we can merge.


has no method checkBody

I am using express 4.11.1 and express-validator 2.8.0.
here is the code i used above post action:
var util = require('util');
var express = require('express');
var bodyParser = require('body-parser');
var expressValidator = require('express-validator');
var app = express();

and inside post action i gave
req.checkBody('postparam', 'Invalid postparam').notEmpty().isInt();
i am getting has no method checkBody error, don know whether version is the problem so mentioned the versions above.

Looks like you forgot to register the bodyParser and expressValidator middleware with the app (which will add the validation methods to the request object).
Try:
var util = require('util');
var express = require('express');
var bodyParser = require('body-parser');
var expressValidator = require('express-validator');
var app = express();

// parse application/x-www-form-urlencoded
app.use(bodyParser.urlencoded({ extended: false }))

// parse application/json
app.use(bodyParser.json())

// add validation methods to request
app.use(expressValidator());

// now the methods are available
app.post('/', function(req, res, next) {
    req.checkBody('postparam', 'Invalid postparam').notEmpty().isInt();
});

I'm not using app.post, i'm exporting the function like
exports.postRide = function (req, res) {
  req.checkBody('postparam', 'Invalid postparam').notEmpty().isInt();

so here i'm unable to access the CheckBody method. How can i get access inside exports.postRide?

I too am using exports for my routes, and by adding the middleware as mentioned by @EyEdealist, I have access to checkBody() without issue:
var express = require('express'),
    path = require('path'),
    favicon = require('serve-favicon'),
    logger = require('morgan'),
    cookieParser = require('cookie-parser'),
    bodyParser = require('body-parser'),
    expressValidator = require('express-validator'),
    app = express();

app.use(bodyParser.json());
app.use(bodyParser.urlencoded({ extended: false }));
app.use(expressValidator());

@anbublacky Did this help? If so, please close.

Just a clarifying comment on this issue: make sure you "use" your router's after you add expressValidator. (Which makes sense but I had too look for this for a while)
var bodyParser = require('body-parser');
var expressValidator = require('express-validator');

app.use(bodyParser.urlencoded());
app.use(expressValidator());

// Now we can start adding routers to our app
app.use('/example', exampleRouter);


Importing existing management group at level_1 fails

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions
Terraform v1.3.6

provider registry.terraform.io/hashicorp/azurerm v3.43.0
provider registry.terraform.io/hashicorp/random v3.4.3
provider registry.terraform.io/hashicorp/time v0.9.1
Module version 3.1.2

Description
I want to use this module to manage some additional management groups at level_1 in the hierarchy with custom_landing_zones. The Terraform plan completes and wants to add the group, but as the group already exists I want to import it into Terraform. My reasoning behind this is I want to use the capability of this module to assign policies etc to this level_1 MG.
Steps to Reproduce
main.tf:
data "azurerm_client_config" "core" {}
module "enterprise_scale" {
  source  = "Azure/caf-enterprise-scale/azurerm"
  version = "3.1.2"

  providers = {
    azurerm              = azurerm
    azurerm.connectivity = azurerm
    azurerm.management   = azurerm
  }

  root_parent_id                  = data.azurerm_client_config.core.tenant_id
  deploy_core_landing_zones       = false
  disable_telemetry               = true
  custom_landing_zones            = {
    TestGroup = {
      display_name               = "Test Group"
      parent_management_group_id = ""
      subscription_ids           = []
      archetype_config = {
        archetype_id   = "default_empty"
        parameters     = {}
        access_control = {}
      }
    }
  }
}

Terraform plan:
data.azurerm_client_config.core: Reading...
data.azurerm_client_config.core: Read complete after 0s [id=[...]]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the
following symbols:
  + create

Terraform will perform the following actions:

  # module.enterprise_scale.azurerm_management_group.level_1["/providers/Microsoft.Management/managementGroups/TestGroup"] will be created
  + resource "azurerm_management_group" "level_1" {
      + display_name               = "Test Group"
      + id                         = (known after apply)
      + name                       = "TestGroup"
      + parent_management_group_id = "/providers/Microsoft.Management/managementGroups/[...]"
      + subscription_ids           = (known after apply)
    }

  # module.enterprise_scale.time_sleep.after_azurerm_management_group will be created
  + resource "time_sleep" "after_azurerm_management_group" {
      + create_duration  = "30s"
      + destroy_duration = "0s"
      + id               = (known after apply)
      + triggers         = {
          + "azurerm_management_group_level_1" = jsonencode(
                [
                  + "/providers/Microsoft.Management/managementGroups/TestGroup",
                ]
            )
          + "azurerm_management_group_level_2" = jsonencode([])
          + "azurerm_management_group_level_3" = jsonencode([])
          + "azurerm_management_group_level_4" = jsonencode([])
          + "azurerm_management_group_level_5" = jsonencode([])
          + "azurerm_management_group_level_6" = jsonencode([])
        }
    }

  # module.enterprise_scale.time_sleep.after_azurerm_policy_assignment will be created
  + resource "time_sleep" "after_azurerm_policy_assignment" {
      + create_duration  = "30s"
      + destroy_duration = "0s"
      + id               = (known after apply)
      + triggers         = {
          + "azurerm_management_group_policy_assignment_enterprise_scale" = jsonencode([])
        }
    }

  # module.enterprise_scale.time_sleep.after_azurerm_policy_definition will be created
  + resource "time_sleep" "after_azurerm_policy_definition" {
      + create_duration  = "30s"
      + destroy_duration = "0s"
      + id               = (known after apply)
      + triggers         = {
          + "azurerm_policy_definition_enterprise_scale" = jsonencode([])
        }
    }

  # module.enterprise_scale.time_sleep.after_azurerm_policy_set_definition will be created
  + resource "time_sleep" "after_azurerm_policy_set_definition" {
      + create_duration  = "30s"
      + destroy_duration = "0s"
      + id               = (known after apply)
      + triggers         = {
          + "azurerm_policy_set_definition_enterprise_scale" = jsonencode([])
        }
    }

  # module.enterprise_scale.time_sleep.after_azurerm_role_assignment will be created
  + resource "time_sleep" "after_azurerm_role_assignment" {
      + create_duration  = "0s"
      + destroy_duration = "0s"
      + id               = (known after apply)
      + triggers         = {
          + "azurerm_role_assignment_enterprise_scale" = jsonencode([])
          + "module_role_assignments_for_policy"       = jsonencode([])
        }
    }

  # module.enterprise_scale.time_sleep.after_azurerm_role_definition will be created
  + resource "time_sleep" "after_azurerm_role_definition" {
      + create_duration  = "60s"
      + destroy_duration = "0s"
      + id               = (known after apply)
      + triggers         = {
          + "azurerm_role_definition_enterprise_scale" = jsonencode([])
        }
    }

Plan: 7 to add, 0 to change, 0 to destroy.

Terraform import module.enterprise_scale.azurerm_management_group.level_1 /providers/Microsoft.Management/managementGroups/TestGroup:
data.azurerm_client_config.core: Reading...
data.azurerm_client_config.core: Read complete after 0s [id=[...]]
╷
│ Error: Invalid for_each argument
│
│   on .terraform\modules\enterprise_scale\resources.management_groups.tf line 20, in resource "azurerm_management_group" "level_2":
│   20:   for_each = local.azurerm_management_group_level_2
│     ├────────────────
│     │ local.azurerm_management_group_level_2 will be known only after apply
│
│ The "for_each" map includes keys derived from resource attributes that cannot be determined until apply, and so
│ Terraform cannot determine the full set of keys that will identify the instances of this resource.
│
│ When working with unknown values in for_each, it's better to define the map keys statically in your configuration and
│ place apply-time results only in the map values.
│
│ Alternatively, you could use the -target planning option to first apply only the resources that the for_each value
│ depends on, and then apply a second time to fully converge.

@adhodgson1, please can you ensure you specify the correct value for parent_management_group_id to ensure it reflects the actual parent Management Group of the Management Group you want to import.
If this is the only MG you are managing in this module declaration, you will also need to set root_parent_id to the same value (which may well be the tenant ID).

Thanks, specifying the parent_management_group_id fixed the issue.

If anyone stumbles on this same issue - resolved using Terraform v1.5 feature of an import block.
import {
  # Resource ID of the Management Group
  id = "/providers/Microsoft.Management/managementGroups/<Management Group ID>"
  # Terraform Resource Address of Management Group
  to = module.enterprise_scale.azurerm_management_group.level_1["/providers/Microsoft.Management/managementGroups/<Management Group ID>"]
}

Plan and Apply successful to a pre-existing Management Group:
Plan: 1 to import, 208 to add, 0 to change, 0 to destroy.

Apply complete! Resources: 1 imported, 208 added, 0 changed, 0 destroyed.

Thank you @matt-FFFFFF and @jtracey93


changed background color for premium look

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Other

I don't think a black background would look good for this app.
Maybe you could add this blue gradient.

can i know that the image you want in background or color

The blue gradient you see in the image above, you can use a color picker to get the colors for the gradient.


Implement es Map class #497

Added es Map class methods
Added es Map class interface
Added basic tests for the es Map class
This will be my first contribution to open source and I really appreciate any guidance or advice on contributions going forward. Thanks for your time and patience on this.

@microsoft-github-policy-service agree

Or you can wait until I figure out how export symbols from core but this may take quite some time...

I'm happy to give it a try! Stay tuned.

I didnt think i changed anything with the jacdac submodules at all. I can revert changes if needed my apologies.

Don't worry about the submodules. I'll fix it if needed.
However, it seems you forgot some changes to runtime/index.ts ? see https://github.com/microsoft/devicescript/actions/runs/5523589721/jobs/10154461568?pr=538#step:9:869

yeah i definitely did. Im not sure how it passed my tests. Sorry again should i push up the import in index?


Upgraded H2 to 1.4.200

Signed-off-by: Laird Nelson<EMAIL_ADDRESS>

See also https://github.com/h2database/h2database/issues/2198


Using env variables AFTER build

Environment

Operating System: Linux
Node Version:     v20.11.0
Nuxt Version:     3.9.3
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      runtimeConfig
Runtime Modules:  -
Build Modules:    -

Reproduction
https://github.com/whiterqbbit/poc-variable-nuxt
Describe the bug
I'd like to use environnement variables with an already built nuxt server.
To be extra clear, the server is built with no .env, or EXPORT env.
I'd like to use env variables afterwards, either with .env or EXPORT.
Additional context
I've tried passing env like this
DATABASE_HOST=mydatabaseconnectionstring node .output/server/index.mjs
as described here.
I also tried using node 20 and the --env-file flag as described here
nuxt.config.ts
export default defineNuxtConfig({
  runtimeConfig: {
    public: {
      NUXT_TOMATO: process.env.NUXT_TOMATO,
      TOMATO: process.env.TOMATO
    }
  }
})

Logs
No response

If your runtimeConfig contains public: { TOMATO: 'whatever-here-is-default' }, you have to use NUXT_PUBLIC_TOMATO as env variable to change it.
From the docs:

Setting the default of runtimeConfig values to differently named environment variables (for example setting myVar to process.env.OTHER_VARIABLE) will only work during build-time and will break on runtime. It is advised to use environment variables that match the structure of your runtimeConfig object.

Further info in my video about exactly that common mistake.

Hello, thank you for the quick answer, I actually got stuck behind that for a day.
Also great to discover your channel, the issues you tackle are well calibrated for my current level !


Allow manual selection of IPsec IKE Pseudo-Random Function (PRF). Issue #9309

[ ] Redmine Issue: https://redmine.pfsense.org/issues/9309
[ ] Ready for review

default (current) behavior if checkbox disabled
pfSense <-> Cisco IOS tunnel tested

pfSense 2.5.0.a.20191203.0148

successfully tested different combinations of encryption algos and MD5, SHA1/256/348/512 hash/prfs on IPsec tunnel with Cisco vIOS 15.5,
and different combinations of encryption algos and AES_XCBC hash/prf on IPsec tunnel with two pfSense 2.5

conflicts resolved
tested with Cisco IOS

@vktg please rebase your fork to fix conflicts. While there, could you please squash all these commits in a single one to make the commit history cleaner?

all done

Successfully tested:
2.5.0.a.20200206.2005 < - > Cisco IOS 15.5(3)M
2.5.0.a.20200206.2005 < - > Huawei USG6000V (VRP 5.160)


🚀 Feature: Populate the Backstage Catalog

🔖 Feature description
I want to add our Minecraft servers and services like the Discord bot to our Backstage Catalog
🎤 Context
As a TFB Staff I want to see who is responsible for which service, gives more value the more things we have in Github.
✌ Possible Implementation
I will add a catalog-info.yaml file in a new branch and use it for testing
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find any similar issue

Are you willing to submit PR?
Yes I am willing to submit a PR!

Closing as I created an issue in the Backstage repo instead


release and cleanArtifacts settings seem to be ignored

Environment
Running locally using OSX as well as in. Github Action.
Steps to Reproduce
const sentryWebpackPluginInstance =
  process.env.SENTRY_SOURCEMAPS && process.env.SENTRY_AUTH_TOKEN
    ? sentryWebpackPlugin({
      org: "..",
      project: "..",
      authToken: process.env.SENTRY_AUTH_TOKEN,
      release: `${process.env.VERSION_STRING}-${targetBrowser}-${nodeEnv}`,
      cleanArtifacts: true,
    })
    : () => {
      this.apply = () => { };
    };

Expected Result
Release set to ${process.env.VERSION_STRING}-${targetBrowser}-${nodeEnv} and *.map files uploaded and then removed from the file system
Actual Result
while *.map files were uploaded, the release and cleanArtifacts settings seem to be ignored (ie. the release is derived from the git commit and *.map files are not removed).

seems like release is no an object
https://www.npmjs.com/package/@sentry/webpack-plugin


Give Mice Combat Mode and a 0 Damage Attack

About the PR

Since #30478 was merged, this lets mice spin with the big boys and be extra annoying with an attack that deals 0 damage.
Why / Balance

SSSPPPPIIIINNNNN
Technical details

yml
Media

https://github.com/user-attachments/assets/56f02b83-30ca-42b3-b606-979a3f19b78c

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Mice can now use combat mode with a 0 damage attack

m-my hand is reaching for the merge button...the mice in my hat is controlling me....


Updated Batching Exception Handling

Updating exception handling for the batching interceptor to catch all exceptions and wrap any non ApolloException in one to ensure that they're propagated for handling.
IDK if the when here or a separate catch is preferred so feel free to suggest which way to go there. Happy to go either way.
Closes #3903

@jeffreydecker: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

I think catching everything is ok, we have this in other places too. We could be more precise by catching only IOExceptions but I don't think it's worth the trouble right now


"&" in the password bricks the config file (docker)

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Submission validity

[X] This is not a personal support request, that should be posted on discussions community.
[X] I checked current issues and this request isn't a duplicate of an existing issue, opened or closed.

Self troubleshooting

[X] I've read the documentation and made sure to follow it.
[X] I've read the troubleshooting first steps and frequent issues guides.

Version
latest
Description
inserting a password with "&" in the "YOURLS_PASS" as environment variable messes up the config file
yourls_user_passwords = [
    'user' => 'passwordwithoutand getenv_docker('YOURLS_USER') => getenv_docker('YOURLS_PASS'),',
];

Expectation
i guess the & is actually interpreted
Reproduction steps
set password YOURLS_PASS = sjkdhaadjsk&
Context
should be fixed/escaped

Your code :
yourls_user_passwords = [
    'user' => 'passwordwithoutand getenv_docker('YOURLS_USER') => getenv_docker('YOURLS_PASS'),',
];

Sets a user with username "user", and the password is the following string : "passwordwithoutand getenv_docker('YOURLS_USER') => getenv_docker('YOURLS_PASS'),", which I'm not sure is what you're trying to achieve.
Chars in passwords are not "escaped" and you can use any char in your passwords, see the ones used in unit tests.
There is no bug there. If you're not sure about how to use a setting or config, please open a discussion instead.

Hey @ozh, the code snippet is the result of the config file that is auto-generated if you would set the environment variables

YOULRS_USER="user"
YOURLS_PASS="passwordwithoutand&"

using these settings the docker images fails and just prints a php error, which is due - i guess - to the config.php being generated in a wrong way
i solved it by using another password without "&", and it works now, so i don't care what you do with this information. but i thought you might be interested in this bug, but sure just leave the bug in

if you want to reproduce:
version: '3.1'

services:

  yourls:
    image: yourls
    restart: always
    ports:
      - 8080:80
    environment:
      YOURLS_DB_PASS: example
      YOURLS_SITE: http://localhost:8080/
      YOURLS_USER: example_username
      YOURLS_PASS: "example_password&"

  mysql:
    image: mysql
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: example
      MYSQL_DATABASE: yourls

localhost:8080/admin
Parse error: syntax error, unexpected identifier "YOURLS_USER", expecting "]" in /var/www/html/user/config.php on line 75


getting error while creating producer

Unexpected error: unknown(Error Domain=MediasoupClientErrorDomain Code=3 "The associated promise has been destructed prior to the associated state becoming ready." UserInfo={NSLocalizedDescription=The associated promise has been destructed prior to the associated state becoming ready.}).

Most probably it's one of the next:

Calling createProducer(...) from arbitrary thread (you must make all calls to Device / Transports / Producers / Consumers from the same dedicated thread / serial queue)

onProduce method implemented incorrectly. This method MUST call it's callback either with nil parameter in case of an error, or with producer id value provided by your media server via signaling mechanism. In this case you must hold the callback until signaling is finished and call the callback on main passing producerId provided by your media server.


Document and/or enforce model update order

Is your feature request related to a problem? Please describe.
At the moment, the order at which models are called in for each process (i.e. setup, update) is set by the order of the modules list in the config. So, if modules = ["abiotic_simple", "hydrology", "soil"] then the abiotic_simple model is updated first, then the hydrology model, and then the soil model.
Some models cannot be updated before other models. At present, if the first update of the soil model happens before the first update of the abiotic_simple model the simulation will stall as an undefined soil temperature will be passed to the integrator which then silently fails. The user isn't currently given an indication as to why the simulation has stalled.
Describe the solution you'd like
We need to document the order in which models can be run somewhere. We also need to inform the user that an invalid order has been entered. We also might want to change the core.modules config option to make it more obvious that this sets the model update (etc) order, or alternatively remove this control from the config system entirely. I can't think of any obvious solution for all this atm, and think that it's something worth discussing as a group.
Describe alternatives you've considered
Alternatively, we could rewrite the models so that they can be setup, updated, etc, in any order. However, suspect this might be quite complex to do for minimal gain.

Closed by #352 which introduced the model order settings into the configuration


[datatables] how do I have two global search filter?

Original:

How do I have two global search filter, for eg

search is a global statement in the DataHandler instance.
If you need an other global search, you can use handler.createFilter() or handler.filter() applied to all columns:
<script>
    export let handler
    let value = ''
    const filter = handler.createFilter((row) => row)
</script>

<input type="text" bind:value on:input={() => filter.set(value)>

shortcut:
<script>
    export let handler
    let value = ''
</script>

<input type="text" bind:value on:input={() => handler.filter(value, (row) => row)>

Before you replied I tried to implement my own method:
let globalFilter1 = "";
let globalFilter2 = "";

let globalFilterArr = [];

if (globalFilter1.trim() != "") globalFilterArr.push(globalFilter1.trim());
if (globalFilter2.trim() != "") globalFilterArr.push(globalFilter2.trim());

if (globalFilterArr.length == 1) {
  const globalFilterResults = initialTableData.filter((row) =>
    Object.values(row).some((value) =>
      String(value).toLowerCase().includes(globalFilterArr[0].toLowerCase())
    )
  );

  handler.setRows(globalFilterResults);
} else if (searchTerms.length == 2) {
  let currentFilterResults = [];

  handler.getAllRows().subscribe((rows) => {
    currentFilterResults = rows;
  });

  const globalFilterResults = currentFilterResults.filter((row) =>
    globalFilterArr.every((globalFilter) =>
      Object.values(row).some((value) =>
        String(value).toLowerCase().includes(globalFilter.toLowerCase())
      )
    )
  );

  handler.setRows(globalFilterResults);
}

Do you have any comments for improvements?
By the way,
  let currentFilterResults = [];

  handler.getAllRows().subscribe((rows) => {
    currentFilterResults = rows;
  });

Although the code is running as expected, could I do this?

Yes, but what happens if both filters have a search value ? It seems that only the second one would work.
I don't get exactly what you want to achieve


Invalid segment error when version contains more than 3 segments

According to this blog,
http://blog.soebes.de/blog/2017/02/04/apache-maven-how-version-comparison-works/
Maven now supports more than 3 segments. However the versions plug-in immediately dies with
[ERROR] Failed to execute goal use-latest-versions (default-cli) on project mdm: Execution default-cli of goal use-latest-versions failed: Invalid segment, 1, for the 1 segment version: '<IP_ADDRESS>' -> [Help 1]
Any time it comes across a version with more than 3 segments.  I've been mitigating this in the past with a long long list of -Dexcludes , however that's a manual effort.
I'm wondering if @khmarbaise  you have anything planned to address this. Would it be appropriate to instead of fail and throw an error,  WARN that a version has not been updated, or that it has been skipped?
Thx

Hi...
i use 2.5 of maven-versions-plugin and have Google Analytics as dependency ( https://mvnrepository.com/artifact/com.google.apis/google-api-services-analytics ).
I get the message:
[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.5:update-properties (default-cli) on project aldi-bus-bom: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:2.5:update-properties failed: Invalid segment, 1, for the 1 segment version: 'v3-rev126-1.19.1'
Is this relevant? Is there a work around?
Thanks.

Open from Jan. Still nothing... Is this error expected? Are we doing something wrong?

In my case invalid segment error occurs only if I am ignoring minor & major updates.

I encounter the same issue. Should use-latest-versions skip segments anyway? Or at least propose an option not to process segments?

@blacelle Would you mind filing a PR from your fork?

Also applies to update-properties goal...like @nsidhaye , I am also ignoring minor & major updates.

this is super annoying. fails on multiple like:
a:b:<IP_ADDRESS>
c:d:<IP_ADDRESS> etc.

This basically undoes any benefit of updating through the plugin

I'm getting the same error when I run
mvn versions:update-properties -DallowMajorUpdates=false -DallowMinorUpdates=false
but NOT if I run:
mvn versions:update-properties -DallowMajorUpdates=false
or
mvn versions:update-properties  -DallowMinorUpdates=false
although in the latter case it still implements minor version updates.

Same here for <ojdbc.version><IP_ADDRESS></ojdbc.version> with the following configuration:
<goals>
    <goal>display-property-updates</goal>
    <goal>display-dependency-updates</goal>
</goals>
<configuration>
    <allowAnyUpdates>false</allowAnyUpdates>
    <allowMajorUpdates>false</allowMajorUpdates>
    <allowMinorUpdates>false</allowMinorUpdates>
</configuration>

Not sure if this helps but according to the version rules documentation  on the homepage (see https://www.mojohaus.org/versions-maven-plugin/version-rules.html)
the version rules is as follows:
<MajorVersion [> . <MinorVersion [> . <IncrementalVersion ] ] [> - <BuildNumber | Qualifier ]>
and

If your version number does not match this format, then the entire version number is treated as being the Qualifier.

So (if I read this correctly), a version like <IP_ADDRESS> is treated as a whole a qualifier!
Also versions like a.b.1´ or 1.2.c` are not compliant, hence treated as qualifiers.

Guys, I'll look into it.

I get the message:
[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.5:update-properties (default-cli) on project aldi-bus-bom: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:2.5:update-properties failed: Invalid segment, 1, for the 1 segment version: 'v3-rev126-1.19.1'

Related, has to do with the way segments are determined.

I appreciate the maven versioning policy however it might not suit the reality, but the issue people are dealing with here is that those irregular dependencies act as poison for the plugin: the whole run will be stopped by a single such dependency. This is why some chose to patch the plugin and "sanitise" the exception.
So, I'm working on a fix.

There are 59 more issues to go. I hope that not every single one has to be solved to unblock

https://github.com/mojohaus/versions-maven-plugin/issues/645

The more I look into it, the more issues I see:

segment appears to be 0-based (see e.g. AbstractVersionsUpaterMojo.determineUnchangedSegment), but the comparison against the segment count suffers from the 1-off problem:

if ( segment > segmentCount )
{
    throw new InvalidSegmentException( segment, segmentCount,
            version.toString() );
}

segment determination flags (allowMajorUpdates, etc.) are actually not at all independent, but are actually a sort of enum; so an actual enum or an unchanged segment index would be better;
part of the above: it's not actually possible to have allowMajorUpdates = true and allowMinorUpdates = false; allowMajorUpdates = true implies all others also being true;

There are probably more problems with this, but I'll limit the scope of this item to the issue OP raised only. The other findings will be done as separate issues.

The PR will be rather large due to the fact that I'm leveraging the InvalidSegmentException and InvalidVersionSpecificationException rather than simply ignoring those; they are then handled in the Mojo itself. Due to the fact that InvalidVersionSpecificationException was a RuntimeException and therefore unchecked, a relatively small refactor was due. However, due to the size of the PR, it's possible that it's not gonna fit into the release.

I'm getting the same error when I run mvn versions:update-properties -DallowMajorUpdates=false -DallowMinorUpdates=false
but NOT if I run: mvn versions:update-properties -DallowMajorUpdates=false or mvn versions:update-properties -DallowMinorUpdates=false
although in the latter case it still implements minor version updates.

The reason for that is that the check would only fail if the determined "leftmost unchanged segment" is greater than the determined number of segments in the version.
"leftmost unchanged segment" is based on your "allow{Major,Minor,Incremental}Updates" flags (those flags are actually a sort of enum switch), and will assume -1 for Major (meaning no restrictions), 0 for minor (meaning only major segment is restricted), and so forth.
So, the exception would only be raised if that segment is greater (actually should have been greater or equal because it's 0-based, but that's for another PR) than the total number of segments ;)


Self signed certificate

In our implementation, the client needs to talk to the socketio server (node.js) over https with self-signed certificate. is there a way to assign the ssl context to the socket.io client?
we could do this with iPhone/Android, but i have no clue how we could do this on dotnetclient
Thanks,
Alex

Use this code:
IO.Options options = new IO.Options ();
options.IgnoreServerCertificateValidation = true;
socket = IO.Socket(url, options);

This just blindly trust all the self-signed certificate.
I traced the source code and found out that webclient does have this functionality to take self-signed certificate, but the engine-io-client does not port this.
Will you guys plan to include this feature in the near future?

It is only me and I am not using this library at the moment. I moved to typescript.


Verify SCTs we get from other nodes, and verify the STH we get from the DB.

Addresses #900

Other than the slight tweaking of unique_ptr constructor parameter, LGTM.


Calling Unsubscribe from a channel is still receiving update messages

I have these 2 methods:
    public async void SubscribeToTournamentChanges(int tournament_id, TournamentChangedHandler handler)
    {
        var channelName = "tournaments:" + tournament_id;
        channels.TryGetValue(channelName, out RealtimeChannel channel);
        if (channel == null)
        {
            channel = _supabase.Realtime.Channel(channelName);
            channels.Add(channelName, channel);
            channel.Register(new PostgresChangesOptions("public", "aw-tournaments", ListenType.Updates, "id=eq." + tournament_id ));
            channel.AddPostgresChangeHandler(ListenType.Updates, (_, change) =>
            {
                if (change.Payload?.Data?.Table == "aw-tournaments")
                {
                    //Tournament data changed
                    var model = change.Model<Tournament>();
                    if (model != null)
                    {
                        _mainThreadContext.Post(_ => handler.Invoke(model), null);
                    }
                }
            });
        }
        await channel.Subscribe();
    }

    public void UnsubscribeToTournamentChanges(int tournament_id)
    {
        var channelName = "tournaments:" + tournament_id;
        channels.TryGetValue(channelName, out RealtimeChannel channel);
        if (channel != null)
        {
            channel.Unsubscribe();
        }
    }

When I call channel.Unsubscribe(); i see in the logs that something gets changed:
Socket Push [topic: realtime:tournaments:5, event: phx_leave, ref: 5505e55a-d2d9-484d-8d98-34fc9d3c3d9d]:
	null
UnityEngine.Debug:Log (object)
SupabaseManager/<>c:<Start>b__9_0 (object,string,System.Exception) (at Assets/TcgEngine/SupabaseManager.cs:60)
Supabase.Realtime.Debugger:Log (object,string,System.Exception)
Supabase.Realtime.RealtimeSocket:Push (Supabase.Realtime.Socket.SocketRequest)
Supabase.Realtime.Channel.Push:Send ()
Supabase.Realtime.RealtimeChannel:Unsubscribe ()
SupabaseManager:UnsubscribeToTournamentChanges (int) (at Assets/TcgEngine/SupabaseManager.cs:222)
TcgEngine.UI.TournamentDetailsPanel:OnBack () (at Assets/TcgEngine/Scripts/UI/TournamentDetailsPanel.cs:149)
UnityEngine.Events.UnityEvent:Invoke ()
TcgEngine.UI.AWButtonNew:OnClick () (at Assets/TcgEngine/Scripts/UI/AWButtonNew.cs:34)
UnityEngine.EventSystems.EventSystem:Update () (at ./Library/PackageCache/com.unity.ugui@1.0.0/Runtime/EventSystem/EventSystem.cs:530)

But when I change my tournaments table in the DB, I still get the message. I would expect Unsubscribe to stop getting these (thus saving bandwith)
What is Unsubscribe meant to do if not this?
Thanks!

Thanks for the issue!
To clarify, the websocket it still receiving messages? Or your callback is continuing to be called?

Thanks for the issue!
To clarify, the websocket it still receiving messages? Or your callback is continuing to be called?

Both!

@grimAgent I'm struggling to duplicate - are you sure you don't have multiple socket clients connected?
I wrote the following test in the RealtimeTests project (see the realtime-csharp repo] using a primary channel (demonstrating the Unsubscribe functionality) and a secondary channel (different channel with same postgres_changes parameters but remaining subscribed).
It passes as expected:
[TestMethod("Channel: Unsubscribes")]
public async Task ChannelDisconnectsAppropriately()
{
    var callbackInvokedTCS = new TaskCompletionSource<bool>();
    var primaryClientInvocations = 0;
    var secondaryClientInvocations = 0;

    var channel1 = _socketClient!.Channel("test:unsubscribes");
    channel1.Register(new PostgresChangesOptions("public", "todos", ListenType.Inserts, "user_id=eq.1"));
    channel1.AddPostgresChangeHandler(ListenType.Inserts, (_, changes) =>
    {
        primaryClientInvocations++;
        callbackInvokedTCS.TrySetResult(true);
    });
    await channel1.Subscribe();

    var channel2 = _socketClient!.Channel("test:unsubscribes:2");
    channel2.Register(new PostgresChangesOptions("public", "todos", ListenType.Inserts, "user_id=eq.1"));
    channel2.AddPostgresChangeHandler(ListenType.Inserts, (_, changes) => secondaryClientInvocations++);
    await channel2.Subscribe();

    await _restClient!.Table<Todo>().Insert(new Todo { UserId = 1 });
    await callbackInvokedTCS.Task;

    channel1.Unsubscribe();

    await _restClient!.Table<Todo>().Insert(new Todo { UserId = 1 });
    await _restClient!.Table<Todo>().Insert(new Todo { UserId = 1 });

    await Task.Delay(3000);
    Assert.AreEqual(1, primaryClientInvocations);
    Assert.AreEqual(3, secondaryClientInvocations);
}

With the following console output:
Debug Trace:
Socket Reconnection: Initial
Socket Connected to: ws://realtime-dev.localhost:4000/socket/websocket?apikey=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiIiLCJpYXQiOjE2NzEyMzc4NzMsImV4cCI6MjAwMjc3Mzk5MywiYXVkIjoiIiwic3ViIjoiIiwicm9sZSI6ImF1dGhlbnRpY2F0ZWQifQ.qoYdljDZ9rjfs1DKj5_OqMweNtj7yk20LZKlGNLpUO8&vsn=1.0.0
Socket State Change: Open
Socket Push [topic: phoenix, event: heartbeat, ref: 91de2812-09d7-4fcc-8263-2834ae862423]:
	{}
Socket Push [topic: realtime:test:unsubscribes, event: phx_join, ref: 23775bd6-5117-405d-bdaa-99074b798f30]:
	{
  "config": {
    "broadcast": {
      "self": false,
      "ack": false
    },
    "presence": {
      "key": ""
    },
    "postgres_changes": [
      {
        "schema": "public",
        "table": "todos",
        "filter": "user_id=eq.1",
        "event": "INSERT"
      }
    ]
  }
}
Socket Message Received:
	{"event":"phx_reply","payload":{"response":{},"status":"ok"},"ref":"91de2812-09d7-4fcc-8263-2834ae862423","topic":"phoenix"}
Socket Message Received:
	{"event":"phx_reply","payload":{"response":{"postgres_changes":[{"id":48556260,"event":"INSERT","filter":"user_id=eq.1","schema":"public","table":"todos"}]},"status":"ok"},"ref":"23775bd6-5117-405d-bdaa-99074b798f30","topic":"realtime:test:unsubscribes"}
Socket Message Received:
	{"event":"presence_state","payload":{},"ref":null,"topic":"realtime:test:unsubscribes"}
Socket Message Received:
	{"event":"system","payload":{"channel":"test:unsubscribes","extension":"postgres_changes","message":"Subscribed to PostgreSQL","status":"ok"},"ref":null,"topic":"realtime:test:unsubscribes"}
Socket Push [topic: realtime:test:unsubscribes:2, event: phx_join, ref: 2fcb5d42-4470-4be3-8660-49b3c081dda3]:
	{
  "config": {
    "broadcast": {
      "self": false,
      "ack": false
    },
    "presence": {
      "key": ""
    },
    "postgres_changes": [
      {
        "schema": "public",
        "table": "todos",
        "filter": "user_id=eq.1",
        "event": "INSERT"
      }
    ]
  }
}
Socket Message Received:
	{"event":"phx_reply","payload":{"response":{"postgres_changes":[{"id":48556260,"event":"INSERT","filter":"user_id=eq.1","schema":"public","table":"todos"}]},"status":"ok"},"ref":"2fcb5d42-4470-4be3-8660-49b3c081dda3","topic":"realtime:test:unsubscribes:2"}
Socket Message Received:
	{"event":"presence_state","payload":{},"ref":null,"topic":"realtime:test:unsubscribes:2"}
Socket Message Received:
	{"event":"system","payload":{"channel":"test:unsubscribes:2","extension":"postgres_changes","message":"Subscribed to PostgreSQL","status":"ok"},"ref":null,"topic":"realtime:test:unsubscribes:2"}
Socket Message Received:
	{"event":"postgres_changes","payload":{"data":{"columns":[{"name":"id","type":"int8"},{"name":"name","type":"text"},{"name":"notes","type":"text"},{"name":"done","type":"bool"},{"name":"details","type":"text"},{"name":"inserted_at","type":"timestamp"},{"name":"numbers","type":"_int4"},{"name":"user_id","type":"text"},{"name":"status","type":"todo_status"}],"commit_timestamp":"2023-11-29T03:43:19.106Z","errors":null,"record":{"details":null,"done":false,"id":25,"inserted_at":null,"name":null,"notes":null,"numbers":[],"status":"NOT STARTED","user_id":"1"},"schema":"public","table":"todos","type":"INSERT"},"ids":[48556260]},"ref":null,"topic":"realtime:test:unsubscribes:2"}
Socket Message Received:
	{"event":"postgres_changes","payload":{"data":{"columns":[{"name":"id","type":"int8"},{"name":"name","type":"text"},{"name":"notes","type":"text"},{"name":"done","type":"bool"},{"name":"details","type":"text"},{"name":"inserted_at","type":"timestamp"},{"name":"numbers","type":"_int4"},{"name":"user_id","type":"text"},{"name":"status","type":"todo_status"}],"commit_timestamp":"2023-11-29T03:43:19.106Z","errors":null,"record":{"details":null,"done":false,"id":25,"inserted_at":null,"name":null,"notes":null,"numbers":[],"status":"NOT STARTED","user_id":"1"},"schema":"public","table":"todos","type":"INSERT"},"ids":[48556260]},"ref":null,"topic":"realtime:test:unsubscribes"}
Socket Push [topic: realtime:test:unsubscribes, event: phx_leave, ref: 998db8ee-771d-43f8-be6a-11d82334af56]:
	null
Socket Message Received:
	{"event":"phx_reply","payload":{"response":{},"status":"ok"},"ref":"998db8ee-771d-43f8-be6a-11d82334af56","topic":"realtime:test:unsubscribes"}
Socket Message Received:
	{"event":"phx_close","payload":{},"ref":"23775bd6-5117-405d-bdaa-99074b798f30","topic":"realtime:test:unsubscribes"}
Socket Message Received:
	{"event":"postgres_changes","payload":{"data":{"columns":[{"name":"id","type":"int8"},{"name":"name","type":"text"},{"name":"notes","type":"text"},{"name":"done","type":"bool"},{"name":"details","type":"text"},{"name":"inserted_at","type":"timestamp"},{"name":"numbers","type":"_int4"},{"name":"user_id","type":"text"},{"name":"status","type":"todo_status"}],"commit_timestamp":"2023-11-29T03:43:19.150Z","errors":null,"record":{"details":null,"done":false,"id":26,"inserted_at":null,"name":null,"notes":null,"numbers":[],"status":"NOT STARTED","user_id":"1"},"schema":"public","table":"todos","type":"INSERT"},"ids":[48556260]},"ref":null,"topic":"realtime:test:unsubscribes:2"}
Socket Message Received:
	{"event":"postgres_changes","payload":{"data":{"columns":[{"name":"id","type":"int8"},{"name":"name","type":"text"},{"name":"notes","type":"text"},{"name":"done","type":"bool"},{"name":"details","type":"text"},{"name":"inserted_at","type":"timestamp"},{"name":"numbers","type":"_int4"},{"name":"user_id","type":"text"},{"name":"status","type":"todo_status"}],"commit_timestamp":"2023-11-29T03:43:19.155Z","errors":null,"record":{"details":null,"done":false,"id":27,"inserted_at":null,"name":null,"notes":null,"numbers":[],"status":"NOT STARTED","user_id":"1"},"schema":"public","table":"todos","type":"INSERT"},"ids":[48556260]},"ref":null,"topic":"realtime:test:unsubscribes:2"}
Socket Closed at 11/28/2023 9:43:22 PM


bug: Page do not reload

Type: bug
Platform: ios 8 webview
Beta 14
At the moment I'm testing it on iOS simulator
When I first load states main.first and main.second all works fine.
If I go back only the nav-bar reloads his content. The ion-content remain last one loaded.
Here some of my code:
app.js
.state('main', {
      url: "/main",
      abstract: true,
      templateUrl: "templates/main.html",
      controller: 'MainCtrl'
    })
    .state('main.first', {
      url: "/first",
      views: {
        'main-first': {
          templateUrl: "templates/main-first.html",
          controller: 'MainFirstCtrl'
        }
      }
    })
    .state('main.second', {
      url: "/second",
      views: {
        'main-second': {
          templateUrl: "templates/main-second.html",
          controller: 'MainSecondCtrl'
        }
      }
    })
    ...

main.html:
<ion-view>
  <ion-nav-view name="main-first"></ion-nav-view>
  <ion-nav-view name="main-second"></ion-nav-view>
</ion-view>
```

Here for you guys: http://codepen.io/anon/pen/gbLPoP
BTW: Happy new year!! :)

Here for you guys: http://codepen.io/anon/pen/gbLPoP
BTW: Happy new year!! :)

The issue is with how the abstract view is set up. You should only have one ion-nav-view in there.
http://codepen.io/mhartington/pen/ZYKypw
You could even go as far as remove the abstract state.
http://codepen.io/mhartington/pen/mymwOW
Closing this.

Oh, ok!
Thanks for your help and sorry.


Fix keepkey enumeration so it does not appear as Trezor

Fixes https://github.com/bitcoin-core/HWI/issues/517

ACK https://github.com/bitcoin-core/HWI/pull/521/commits/6a481134fb3954470f1e0ca713f52063f251894c
thanks picking this up so quickly, @prusnak ! i ran the tests locally, and also ran with trezor emulator. confirmed that now trezor is the only device seen:
./hwi.py enumerate
[{"type": "trezor", "path": "udp:<IP_ADDRESS>:21324", "model": "trezor_t_simulator", "needs_pin_sent": false, "needs_passphrase_sent": false, "fingerprint": "a83bd035"}]

note: i have not tested with the keepkey emulator. also not sure if the build failures are related; seems like they've been failing previously as well


Does this work with just a .shp file that is not in a zip?

I have an <input> where a user can upload a file and I noticed whenever you upload just the .shp file then you run into the following error:

However, using the entire zip folder works fine. Am I misunderstanding the first part in the documentation where you can use this on just the .shp file?
Here is a code snippet of the function that is using shpjs to translate to geojson:
onInputChange(file: File) {
  file.arrayBuffer().then(buffer => {
    shp(buffer).then(geojson => {
       console.log(geojson);
    })
  })
};

parseShp

@GinoVillalpando I have the same issue could you fix it?


Icons don't form a connected line

Testing #91329
The icons for the entries in the timeline view are not connected

I have seen this representation in other tools, but in there the rendering is slightly better, with the dots being connected:

The commit icon is just the icon provided by the Git timeline provider (and the fact that our commit icon is vertical rather than horizontal). As other providers are mixed in there will be many different icons in that space.


Feature/slingbucks2

Rewrite of the Slingbucks sample with HTL, service user and JCR Content Package using the new WCMIO Content Package Plugin (1.5.0).
For the time being the WCMIO Content Package must be download from https://github.com/wcm-io/wcm-io-tooling/releases/tag/wcmio-content-package-maven-plugin-1.5.0 and installed locally until the plugin is available on Maven Central.

With the upcoming migration to git this repository will be deleted. If the pull request contains data that should be re-submitted I suggest that you save the changes locally and resubmit them after the migration, which will likely happen on Monday the 9th of October.
Note that we'll likely revisit the package situation once the filevault-package-maven-plugin has its first release in Jackrabbit.


Vet clinic database: Add Join Table for Visits Completed

I have completed adding 'Join Tables' for Visits

Implemented on branch 'join-visits
Created vets table with id, name, age and date_of_graduation columns.
Created a "join table" called specializations, for many-many relationship between vets and species
Created a "join table" called visits to handle many-many relationship between vets and animals

- Inserted the following data for vets:

Vet William Tatcher is 45 years old and graduated Apr 23rd, 2000.
Vet Maisy Smith is 26 years old and graduated Jan 17th, 2019.
Vet Stephanie Mendez is 64 years old and graduated May 4th, 1981
Vet Jack Harkness is 38 years old and graduated Jun 8th, 2008.

- Inserted the following data for specializations:

[ ] Vet William Tatcher is specialized in Pokemon.
[ ] Vet Stephanie Mendez is specialized in Digimon and Pokemon.
[ ] Vet Jack Harkness is specialized in Digimon.
[ ] Insert the following data for visits:
[ ] Agumon visited William Tatcher on May 24th, 2020.
[ ] Agumon visited Stephanie Mendez on Jul 22th, 2020.
[ ] Gabumon visited Jack Harkness on Feb 2nd, 2021.
[ ] Pikachu visited Maisy Smith on Jan 5th, 2020.
[ ] Pikachu visited Maisy Smith on Mar 8th, 2020.
[ ] Pikachu visited Maisy Smith on May 14th, 2020.
[ ] Devimon visited Stephanie Mendez on May 4th, 2021.
[ ] Charmander visited Jack Harkness on Feb 24th, 2021.
[ ] Plantmon visited Maisy Smith on Dec 21st, 2019.
[ ] Plantmon visited William Tatcher on Aug 10th, 2020.
[ ] Plantmon visited Maisy Smith on Apr 7th, 2021.
[ ] Squirtle visited Stephanie Mendez on Sep 29th, 2019.
[ ] Angemon visited Jack Harkness on Oct 3rd, 2020.
[ ] Angemon visited Jack Harkness on Nov 4th, 2020.
[ ] Boarmon visited Maisy Smith on Jan 24th, 2019.
[ ] Boarmon visited Maisy Smith on May 15th, 2019.
[ ] Boarmon visited Maisy Smith on Feb 27th, 2020.
[ ] Boarmon visited Maisy Smith on Aug 3rd, 2020.
[ ] Blossom visited Stephanie Mendez on May 24th, 2020.
[ ] Blossom visited William Tatcher on Jan 11th, 2021.

- Wrote the queries to answer the following:

Who was the last animal seen by William Tatcher?

How many different animals did Stephanie Mendez see?

List all vets and their specialties, including vets with no specialties.

List all animals that visited Stephanie Mendez between April 1st and August 30th, 2020.

What animal has the most visits to vets?

Who was Maisy Smith's first visit?

Details for most recent visit: animal information, vet information, and date of visit.

How many visits were with a vet that did not specialize in that animal's species?

What specialty should Maisy Smith consider getting? Look for the species she gets the most.

- Wrote the queries to answer the following:

Who was the last animal seen by William Tatcher?

How many different animals did Stephanie Mendez see?

List all vets and their specialties, including vets with no specialties.

List all animals that visited Stephanie Mendez between April 1st and August 30th, 2020.

What animal has the most visits to vets?

Who was Maisy Smith's first visit?

Details for most recent visit: animal information, vet information, and date of visit.

How many visits were with a vet that did not specialize in that animal's species?

What specialty should Maisy Smith consider getting? Look for the species she gets the most.


Update beatrust-tutorial.md

Modified because the configuration value has changed: changed from auth.beatrust.com to beatrust.com.
https://learn.microsoft.com/ja-jp/entra/identity/saas-apps/beatrust-tutorial
I will create a separate PR, but if anyone knows how to fix this Japanese document, it would be very helpful.
There is no edit link.

@jeevansd
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@charly24, thanks for the pull request!!
we're updating the document as suggested in the PR in our repo. For Japanese version, will connect with the team and update it.
#please-close


Sync downstream master with upstream default v1.7-branch

Sync downstream master with upstream default v1.7-branch
Pulling all the changes from upstream v1.7.0-3 tag to the repo.
Related-to: https://github.com/opendatahub-io/notebooks/issues/273

Merging this to make the freeze feature complete.


How to show the quickstart again?

Validations

[ ] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[ ] I'm not able to find an open issue that requests the same enhancement

Problem
After I click 'I have complete the onboard', there's no way to say how to setup from start.
No matter I delete all config or reinstall continue extension.
I hope there's a way to show the quickstart again.
Solution
No response

Hi @hitzhangjie, the setting for showing the quickstart/onboarding is in localStorage. You can clear the value and restart with the following steps (in VS Code):

Open the command palette (cmd/ctrl + shift + p)
Type Developer: Toggle Developer Tools
Click Application in the top toolbar
In the lefthand pane, clear the values under Storage > Local storage

I'm curious what your need to revisit the quickstart is for?

Thanks very much.


refactor: we need storybook review :)

build storybook and PR comment
refs: https://github.com/moxci/moxci

Artifact can be viewed here: :

🤔

Artifact can be viewed here: :
https://3-280051086-gh.circle-artifacts.com/0/packages/components/storybook-static/index.html

Artifact can be viewed here: :
https://4-280051086-gh.circle-artifacts.com/0/packages/components/storybook-static/index.html

it's too slow to render this page (It's been over 3 m and it's still not showing up 🤣 ), but do you have any idea?
https://4-280051086-gh.circle-artifacts.com/0/packages/components/storybook-static/index.html

for example,  netlify hosting 💸

Artifact can be viewed here: :
https://22-280051086-gh.circle-artifacts.com/0/packages/components/storybook-static/index.html


Document how to load code in the editor

Apparently you can pass URLs to text files, and I think base64 is an option too? Can this be documented in the README, so that it's easier to use rgbds-live externally & programmatically?

I agree.  RGBDS live already supports loading fileds from URLs (github gists)
Relevant part of the code: https://github.com/gbdev/rgbds-live/blob/master/www/js/storage.js#L32

there are 3 options

#https://gist.github.com/.... load all files from gist example
#https://link/to/file/... loads single file as main.asm example
#LZString.compressToEncodedURIComponent - loads hash as and decompress usingLZString,decompressFromEncodedURIComponent example

Should we have a mini rgbds-live website? or put this in some kind of help dialog?

maybe redesign about menu to show a dialog with tabs like info uses help


[storage-resize-images] "functions: Cannot find module 'object-assign'"

Extension name: storage-resize-images
Extension version: 0.1.29
Configuration values (redact info where appropriate):

ALLOWED_EVENT_TYPES=firebase.extensions.storage-resize-images.v1.complete
DELETE_ORIGINAL_FILE=false
EVENTARC_CHANNEL=projects/${param:PROJECT_ID}/locations/us-central1/channels/firebase
FUNCTION_MEMORY=1024
IMAGE_TYPE=jpeg
IMG_BUCKET=projectname.appspot.com
IMG_SIZES=300x300
IS_ANIMATED=true
LOCATION=southamerica-east1
MAKE_PUBLIC=false

[REQUIRED] Step 3: Describe the problem
With firebase-admin, firebase-functions, and tools, all at the latest version, the extension does not trigger within the emulator, but it fails instead.
Steps to reproduce:
Create and initialize firebase to the latest version, call firebase init and create a new functions folder. Then enable the emulator, and extensions, and then put this into index.ts
import { onCustomEventPublished } from "firebase-functions/v2/eventarc";

export const eventhandler = onCustomEventPublished(
    "firebase.extensions.storage-resize-images.v1.complete",
    (e) => {
        console.log('Extension triggered');
    });

And upload a image.
Expected result
Function trigger to work normally
Actual result
⚠  functions: Cannot find module 'object-assign'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /usr/local/lib/node_modules/firebase-tools/lib/emulator/functionsEmulatorRuntime.js
⚠  Your function was killed because it raised an unhandled error.

Here is my pubspec, its newly made in a new firebase init: I added a dev dependency of object-assign, to see if it would work,it does not
{
  "name": "functions",
  "scripts": {
    "lint": "eslint --ext .js,.ts .",
    "build": "tsc",
    "build:watch": "tsc --watch",
    "serve": "npm run build && firebase emulators:start --only functions",
    "shell": "npm run build && firebase functions:shell",
    "start": "npm run shell",
    "deploy": "firebase deploy --only functions",
    "logs": "firebase functions:log"
  },
  "engines": {
    "node": "16"
  },
  "main": "lib/index.js",
  "dependencies": {
    "firebase-admin": "^11.0.1",
    "firebase-functions": "^3.22.0"
  },
  "devDependencies": {
    "@typescript-eslint/eslint-plugin": "^5.12.0",
    "@typescript-eslint/parser": "^5.12.0",
    "eslint": "^8.9.0",
    "eslint-config-google": "^0.14.0",
    "eslint-plugin-import": "^2.25.4",
    "firebase-functions-test": "^0.2.0",
    "object-assign": "^4.1.1",
    "typescript": "^4.5.4"
  },
  "private": true
}

I believe this issue is resolved with the latest version of the extension. I'll close this as resolved. If the issue persists, i'm happy to reopen and investigate further.


Add a way to for a Builder() to specify it's sources should not be scanned.

Describe the Feature
The enhancement is to add a NullScanner to SCons.
When defining a builder the user can add a source_scanner or target_scanner to control how a given target or source node should be scanned. If a scanner is not provided SCons will look at the extension of the file and try to scan it with a global scanner. This can cause unwanted side effects to the build time as time is wasted looking for implicated dependencies that do not affect the action of the given builder.
For example:
One could make a .7z builder that would add provided sources file to a package (another example might also be a manifest file generator or rpm.spec generator). If this builder does not provide a source_scanner and the sources are a set of .c and or .h files, SCons will try to scan for #include statements in the source and add these as implicit depends on the target of the builder.
This has two negative effects.

time is wasted on scanning the files for implicit depends that have to affect the final target output.
changes in the implicit depends can cause rebuilds of the targets when in reality they have to effect on the target.

SCons does not provide a clear way to say I want this builder scanner to:

use the default global scanner
Do not scan at all

At the moment it is common to not add a scanner to a builder. This practice means a lot of builders can waste a lot of time scanning files that they should not. For a user to define logic to not scan, currently mean that user has to define something like this:
NullScanner = SCons.Script.Scanner(function=lambda *lst, **kw: [], name="NullScanner")
It would be ideal for this to be defined in SCons so it can be reused to allow a clear and definable way to say do not scan the nodes.
It also might be nice to define an object to make explicit when defining a builder that this builder will use the global scanner. This will help clarify the intent of the builder to others

#3974  was a duplicate

Any fresh thoughts on this?


Try fixing "Check Runtime and Extrinsics" CI job

Description of proposed changes
Since the extrinsics ordering check was passing 2 weeks ago, maybe pinning @polkadot/metadata-cmp to the version from >=2 weeks ago will fix it?

Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #1090 (342b1e8) into dev (e700a76) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1090   +/-   ##
=======================================
  Coverage   74.50%   74.50%
=======================================
  Files          74       74
  Lines       10674    10674
=======================================
  Hits         7953     7953
  Misses       2721     2721

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


ImportError: cannot import name LogentriesHandler

Hi,
I'm using Mac OS X 10.9.4 and Python 2.7.5
I have created my account on Logentries, and using the code generated by the app (with token), running the logging.py on the Terminal.
The installation:
$ sudo pip install logentries
Downloading/unpacking logentries
Downloading Logentries-0.2.1.tar.gz
Running setup.py egg_info for package logentries
Installing collected packages: logentries
Running setup.py install for logentries
Successfully installed logentries
Cleaning up...
$ sudo pip freeze | grep entries
LogentriesLogger==0.2.1
The snippet that I use:
#!/usr/bin/env python
from logentries import LogentriesHandler
import logging
import time
log = logging.getLogger('logentries')
log.setLevel(logging.INFO)
test = LogentriesHandler('--- MY TOKEN ---')
log.addHandler(test)
log.warn("Warning message")
log.info("Info message")
time.sleep(10)
When run the snippet show this stack trace:
$ python logging.py
Traceback (most recent call last):
File "logging.py", line 3, in
from logentries import LogentriesHandler
File "/Library/Python/2.7/site-packages/logentries/init.py", line 1, in
from .utils import LogentriesHandler
File "/Library/Python/2.7/site-packages/logentries/utils.py", line 9, in
import logging
File "/Users/myuser/Desktop/logging.py", line 3, in
from logentries import LogentriesHandler

Can you try the latest version? https://pypi.python.org/pypi/Logentries

Thanks, it works!