No errors reported when functions fail to start

Some context: I'm trying to containerize Functions to run them in Kubernetes. I'm using mcr.microsoft.com/azure-functions/dotnet-isolated:3.1.3-dotnet-isolated5.0-slim image to do so.
The problem is our Functions have dependency on ASP.NET Core Runtime which is not installed in the image. And it wouldn't be a big deal if I got a clear error message what exactly is missing. I wasted like half a day trying to figure it out and after adding

finally made it work.
Expected behavior
When user code fails to start for whatever reason (e.g. missing ASP.NET Core Runtime) show/throw exception to make it clear what's wrong.
Actual behavior
No errors is thrown, no reason is given. Process just hangs for 5 minutes and when shuts down with "Did not find any initialized language workers" exception.
Repo steps

func init MyFunctionProj --docker --worker-runtime dotnetIsolated
Add any Nuget package that depends on ASP.NET Core Runtime (e.g. GraphQL.Server.Transports.AspNetCore.SystemTextJson)
Try to run in container. It'll hang for 5 mins and exit with useless "Did not find any initialized language workers" error.

net6 images and later has Microsoft.AspNetCore.App shared framework included. .NET5 is out of support. So this won't be fixed for net5. Please let us know if you run into issues with the latest stable version of images.


出现 Last few GCS 怎么办

Pls show your details if you want to resolve it. I'll close the issue since that you posted nothing. Reopen this issue when you have more details.


OCM: support bearer token access and other refactoring

Adding support for bearer token auth when exposing OCM shares to remote users, following latest OCM developments, and similarly access remote OCM shares via bearer token. OCM 1.0 is still supported when remote users access Reva, but we still don't implement accessing remote OCM 1.0 shares via basic auth.
OCM client incorporated in the ocmd package
The "open" invite manager is now truly open for use without ScienceMesh
Some comments/logs added for clarity
Introduced /.well-known endpoint for OCM

Merging this to allow further testing by @MahdiBaghbani in the scope of the NLnet-funded OCM activities. None of the changes in this PR are yet used in production at CERN, therefore I consider the PR safe to merge.


Ensure scala file is on disk

@lewis6991 much better idea. Regarding

Do we need to also update the autocmds so the relevant ones are buffer local?

I don't believe this should be an issue, but which ones did you have in mind?

I needed to make the autocmds buffer local to prevent the error:
Error detected while processing CursorHold Autocommands for "*.scala":
RPC[Error] code_name = MethodNotFound, message = "method textDocument/documentHighlight is not supported by any of the servers registered for the current buffer"

Because even though we don't attach to non-existent files, the autocmds will be already set up for all buffers. Also given since the autocmds are setup each time we attach to a buffer, it doesn't make sense for them to be global.
Steps to produce:

Open a scala file on disk which nvim-metals will attach to. This sets up the autocmds for all *.scala files.
Run Gitsigns diffthis. Autocmds trigger for this buffer even though nvim-metals doesn't attach.

Additionally, any autocmds that need to be global should be setup outside of the attach callback.

Huh, yea that makes sense. I'm a bit fuzzy on autocmds and need to learn them better. I was actually having issues with one firing in the past
  api.nvim_command([[autocmd BufEnter <buffer> lua require'metals'.did_focus()]])

Because when I'd navigate back to a file, it wouldn't fire again causing issues. So making them global actually didn't happen that long ago.
https://github.com/scalameta/nvim-metals/pull/164/files
The error about the document highlighting I hit on every once in a while, and yea we should fix that.
I'm assuming changing these two to be buffer local will fix the issue.
  api.nvim_command([[autocmd CursorHold  *.scala lua vim.lsp.buf.document_highlight()]])
  api.nvim_command([[autocmd CursorMoved *.scala lua vim.lsp.buf.clear_references()]])

And this one too:
  api.nvim_command([[autocmd BufEnter,CursorHold,InsertLeave *.scala <buffer> lua vim.lsp.codelens.refresh()]])


Makes text transparent too

I don't know if it's intended or a bug on my end, but this extension applies transparency to literally everything, not just the background UI elements. If it's intended, then I don't get the point of this extension, since this can already be achieved from the compositor settings (or by using an external app on windows).
If it's a bug on my end, here are some details about my setup:
I'm using BSPWM with Picom.
I can confirm that the compositor works flawlessly with other apps that request transparency only for background and not for text, such as alacritty, kitty  and transparent QT themes
Here's a screenshot of the issue

I have the same issue on Ubuntu 22.04. Would love the option to keep text solid

Same issue on Windows 10.

it's probably by design
references :
Windows
Linux

Same here, the Idea is getting just the background transparent, the code is the most important part, why would I make it transparent? - If this can be solved, by at least adding an option would be amazing

Update: This can be archived using the UI++ Extension. U need to play a bit with the conf, a good ext btw

Update: This can be archived using the UI++ Extension. U need to play a bit with the conf, a good ext btw

Could you please guide on how you achieved this?


modify info file

I modify a .info file generated in the GCEED part. Just to make sure, I checked that the calculations for the ARTED part and the GCEED part successfully finished.

Thank you for developing, @mn2007. I will check it later.

I confirmed this PR modifies the data format of SYSNAME.info file. And, I have checked the output file is quantitive equivalent to the previous results. I think this PR is available to merge.
Thank you for contribution, @mn2007 san.


isAuthenticated always returning false

Describe the problem
When following the sample code the isAuthenticated flag is always returning false, even after login.
Any guidance here would be much appreciated as I'm scratching my head over this one.
What was the expected behaviour?
When a user has successfully logged in, that the isAuthenticated flag is set to true.
Reproduction
I have created a minimal repository here: https://github.com/grug/auth0-bug-reproduction

Clone the repo
Run yarn install
In the Auth0Provider, substitute your own client id and domain
Run yarn start
Hit the login button
Confirm redirect back into app
Observe that isAuthenticated is false

Environment

Version of auth0-react used: 1.9.0
Which browsers have you tested in? Chrome/Firefox
Which framework are you using, if applicable (Angular, React, etc): React
Other modules/plugins/libraries that might be involved: N/A

Hi,
It looks like you are using the useAuth0 hook outside of the Auth0Provider:
const App = () => {
  const { isAuthenticated } = useAuth0();

  console.log("isAuthenticated", isAuthenticated);

  return (
    <Router>
      <Auth0ProviderWithHistory>
        ...
      </Auth0ProviderWithHistory>
    </Router>
  );
};

That is not something you want to be doing, instead ensure the useAuth0 is only called in children of the Auth0Provider. I opened a PR that changes this in your sample: https://github.com/grug/auth0-bug-reproduction/pull/1
Using the changes from that PR, I get the following output in the console:

Closing as it looks like it should work now, happy to reopen if needed.

Oh lord that's embarrassing 😂
Good catch - how silly!
As a side note - would you be happy accepting a PR from me to add a warning when the hook is used outside of the context (it's not a big PR and would be cool to contribute to your library)?

Haha no worries! 😝
We always appreciate PRs that help other people integrate our SDKs as seamlessly as possible.
Let me pull in @adamjmcgrath to see what he thinks about a change like this!

Excellent! As a point of reference, Kent Dodds recommends the throwing-when-not-used-within-the-provider-context pattern here: https://kentcdodds.com/blog/how-to-use-react-context-effectively

Let me pull in @adamjmcgrath to see what he thinks about a change like this!

sgtm 👍

Excellent - I'll hopefully get a PR up soon :)


Can this be done using nextn13?

Sorry I couldn't find the support/help link
I am using next 13, and I try to add the provider in my layout.tsx file
I had a doubt with the current implementation of ton-connect, despite installing it always shows

Sorry I couldn't find the support/help link I am using next 13, and I try to add the provider in my layout.tsx file I had a doubt with the current implementation of ton-connect, despite installing it always shows

Ok


XCode 12 build warning, minimum deployment target

XCode 12 warning on build:
... SourcePackages/checkouts/IGIdenticon/Package.swift The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99.
Consider bumping the minimum deployment target to 9.0 to address the warning? (Package.swift)

Fixed. Thanks you!


Setup of Kanbab board - Final Group Capstone

Hello reviewer,
We are a team of  3 members :

[ ] @ForHemer
[ ] @mateo951
[ ] @blessedjasonmwanza

Kindly help us review our kanban board.

Hi @ForHemer, @blessedjasonmwanza, @mateo951,
In my opinion, your project is complete!
Good luck! 🎉
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.


[DOCFIX] Move generated docs to separate dir

move location of generated docs created by bin/alluxio docGen, separating them from non-generated files in docs/_data/table

alluxio-bot, merge this please


v7.3.0 is not available at https://pkg.go.dev/

The last available version for go ecosystem is v7.1.0 but this release has a several security vulnerability issues opened with score > 7 (high), like CVE-2020-28852, CVE-2020-28851, CVE-2021-33194, CVE-2020-14040, CVE-2020-28851 and etc.
Seems like most of issues solved already in v7.3.0.
The question is when that release will be published/available for https://pkg.go.dev/ ?
Thanks.

Hi @alex-gilin, can you please explain your use case in more detail? https://pkg.go.dev/ is not something that our team currently supports, nor is it included in our current release process. We're happy to reconsider this.

One use case is for building plugins.   I would guess the knowledge was lost given it was previously published regularly.

Thank you @alex-gilin for your submission. If you still run into this issue with the latest CLI v8,  please open a new ticket with the necessary information mentioned in our issue template.


Spotipy/Flask

I hope all is well. I am currently self-studying Python and am working on a Spotify web app using Spotipy, but am having a bit of trouble setting everything up. I was wondering if you might have any tips on how to set up app.py with Spotipy so that it includes @app.route('/'), requests.get, and return render_template, in a way where Flask Run can run successfully? Do Spotipy and Flask work well together? I am a beginner so would appreciate any advice. Thank you!

See https://github.com/plamere/spotipy/blob/master/examples/app.py

Thank you Peter! Checking out the link right now. Much appreciated

Hi Peter,
I've checked out the document and everything has been going smoothly except upon clicking http://<IP_ADDRESS>:8888/  or http://<IP_ADDRESS>:8080/ subsequent to  python3 -m flask run --port=8888 or  python3 -m flask run --port=8080, I get a "This site can’t be reached <IP_ADDRESS> refused to connect" message on Chrome. Would appreciate any thoughts on how this issue can be resolved.
Thanks so much

@Sticks111 Sorry, but I've actually never used flask. I just knew that example existed. ask @stephanebruckert .

Thanks, will do!

@Sticks111 check what's outputted in the console, it should give you the correct URL for the flask app. In my case it is http://<IP_ADDRESS>:5000/, and not 8080 or 8888

Indeed, I just resubmitted the steps and what I see in my console is the output: Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)  However when I click on it, I am led to this message:
This site can’t be reached <IP_ADDRESS> refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
I tried adjusting my internet settings with the exception of firewalls; should I be removing any firewalls?
Thank you

Looks like there has been a breakthrough; am now on the Sign In page after experimenting in the console and adding two redirect URIs in my Spotify settings. May have to come back later with a quick question but am progressing
Thanks!

@Sticks111 glad you're progressing. I'm closing this for now but feel free to reopen it with further questions

@Sticks111 glad you're progressing. I'm closing this for now but feel free to reopen it with further questions


[QA] Camera zooms in and out

Explorer Alpha build versions:
0.39.0
Issue Description:
When a user is near the social buttons from Genesis Plaza , you will be able to see that the camera zooms in and out by itself
STR:

Open 0.39.0
Go to Genesis Plaza
Step right next to the social buttons
Check that the camera will zoom in and out by itself

Expected behavior:
Camera should not be zooming in and out
Current behavior:
When a user is near the social buttons from Genesis Plaza , you will be able to see that the camera zooms in and out by itself
Evidence:
https://github.com/user-attachments/assets/1a91e7d6-90b0-4939-a72a-976c8af7ac2b
Additional Notes:
This issue can be reproduced on Windows and Macos

This issue is still happening on latest dev and latest release (0.49.0)


Autocomplete styling updates

Updated the styling of the code autocomplete drop down menu. It's easier to read, a little larger, and the color swatches are better aligned. A couple of screenshots of how it looks now...
Light theme with code...

Dark theme with swatches...

Fixes https://github.com/mozilla/thimble.mozilla.org/issues/2452

Fixed a nit and mergin'


Create the "Transit PNR Maps" macro

Creates maps showing PNR productions and attractions. Closes #355

@lfhuntsinger @Si-Shi just pinging you both to make sure you see this PR. This is adding a transit summary requested by Chris and is one of our GitHub issues.

Thanks for pinging me. This allows me to easily update my notes for
the progress report! Nice progress! :)
On Wed, Oct 9, 2024 at 10:06 AM Kyle Ward @.***> wrote:

@lfhuntsinger https://github.com/lfhuntsinger @Si-Shi
https://github.com/Si-Shi just pinging you both to make sure you see
this PR. This is adding a transit summary requested by Chris and is one of
our GitHub issues.
—
Reply to this email directly, view it on GitHub
https://github.com/Triangle-Modeling-and-Analytics/TRMG2/pull/425#issuecomment-2402449094,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP57ZQMUQPJGKNGPTM23AI3Z2UZ5JAVCNFSM6AAAAABPUUB4GGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBSGQ2DSMBZGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Reference base is not defined

https://github.com/oicr-gsi/debarcer/blob/6729c7e69d62480609e98d224f9e867910dd1f4d/debarcer/src/generate_consensus.py#L154
Reference base is the empty string when position of the read in the pileup column  > length of reference sequence.
Ref base is not always captured as expected. Need to review how reference and alternative alleles are extracted from slicing the reference and read sequences.

It looks like the issue is always with read2. get_query_position returns a index larger than the length of the reference sequence


Carla UE4 Exporter

Description
A new plugin can be used from the UE4 editor to be allowed to export meshes (selected or all) in a .OBJ file ready to be used by Recast library to generate the navigation binary (through RecastBuilder).
The process is described in the documentation here ...
https://carla.readthedocs.io/en/latest/how_to_generate_pedestrians_navigation/
Where has this been tested?

Platform(s): Linux and Windows
Python version(s): Any
Unreal Engine version(s): 4.22

Possible Drawbacks
None

This change is

Is the license ok? the files appear to be from Epic.


bug with onPressed state on API_16

Hi!
Thank you for the lib!
I didn't find an issue for this, so I've created a new one.
Here's the problem, I've used the bottombar in an almost empty app and started it on API 16 and API 23 emulators. It works perfect with API 23, but on API 16 I see this when I tap on a tab:

Is there a fix for this? Or maybe it's possible to disable some features on old APIs?

I've updated some libs and now it works fine. Sorry for bothering.

I'm using all the latest support libs. Emulator with API 19 works fine. Emulator with API 16 still has this bug.

Ok, seems like it happens because my API 16 emulator doesn't have Google APIs

Aaand now it suddenly works on API 16 without Google APIs.
I've learnt my lesson today: don't create issues if you're working on Preview version of IDE.


Use improved deflate/gzip compressor.

This pure-Go library (by yours truly) has optimized gzip/deflate function. At default compression levels this gives ~70% improvement in throughput for web content, as well as fewer allocations.
For performance comparisons see the package and https://blog.klauspost.com/gzip-performance-for-go-webservers/
I would love to give revel-specific benchmarks, but the benchmarks in "compress_test.go" appear broken, since it doesn't seem like compression is applied at all.

@klauspost :+1: Well done and the blog post is great.

This sounds exciting. I'd like to run some tests before we merge. I'd also like to see if there is a problem that I can fix in the compress_test.go that you mention. I'm unaware of any specific bugs there.

@klauspost the compress_test.go benchmarks work for me:
$ go test -bench=.
PASS
BenchmarkRenderCompressed	   30000	     42463 ns/op
BenchmarkRenderUnCompressed	   30000	     41268 ns/op
...

There was an error in BenchmarkInvoker, but that seems unrelated here.

@brendensoares - the "BenchmarkRenderCompressed" doesn't appear to apply compression, so you are not benchmarking compression ;)

@klauspost How do you know it's not applying compression?
When I test this PR I get an improvement:
BenchmarkRenderCompressed	   30000	     40650 ns/op
BenchmarkRenderUnCompressed	   30000	     41156 ns/op


Flutter upgrade fails with TLS error on Linux

Steps to Reproduce
Run:
% flutter upgrade
Downloading Dart SDK from Flutter engine ae8e6d9f46990b9585dc1fb5b8aabe491c08aaf3...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  120M  100  120M    0     0  4585k      0  0:00:26  0:00:26 --:--:-- 6649k
Building flutter tool...
Got TLS error trying to find package mime at https://pub.dartlang.org.
Error: Unable to 'pub upgrade' flutter tool. Retrying in five seconds... (9 tries left)
Got TLS error trying to find package mime at https://pub.dartlang.org.
Error: Unable to 'pub upgrade' flutter tool. Retrying in five seconds... (8 tries left)

Logs
~/flutter % git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
~/flutter % git branch
* master
  stable
~/flutter % git log -1
commit 1cf7b3e2c31462e74eac2a9357f39687fa971e35 (HEAD -> master, origin/master, origin/HEAD)

% cat /etc/os-release
NAME="Ubuntu"
VERSION="19.04 (Disco Dingo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 19.04"
VERSION_ID="19.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

Flutter Doctor
% flutter doctor -v
Building flutter tool...
Got TLS error trying to find package mime at https://pub.dartlang.org.
Error: Unable to 'pub upgrade' flutter tool. Retrying in five seconds... (9 tries left)

Tried on Windows 10 and I get the same error:
C:\Users\mjohn>flutter upgrade
Checking Dart SDK version...
Downloading Dart SDK from Flutter engine ae8e6d9f46990b9585dc1fb5b8aabe491c08aaf3...
Unzipping Dart SDK...
Building flutter tool...
Running pub upgrade...
Got TLS error trying to find package mime at https://pub.dartlang.org.
Error (69): Unable to 'pub upgrade' flutter tool. Retrying in five seconds... (9 tries left)

Waiting for 0 seconds, press CTRL+C to quit ...
Running pub upgrade...
Got TLS error trying to find package mime at https://pub.dartlang.org.
Error (69): Unable to 'pub upgrade' flutter tool. Retrying in five seconds... (8 tries left)

Waiting for 3 seconds, press CTRL+C to quit ...
Terminate batch job (Y/N)? y

@dangerousHobo Did you manage to solve the issue? do you have any firewall or proxy?

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


fix csharp build error

add app.config to Avro.Pref project
remove '-framework' parameter from nunit-console test command.

Please review it.

@rdblue This looks good to me. I had to make these changes as well to get it to build properly.

Merged. Thanks @Naruto for the contribution and @jcustenborder for reviewing!


style(auth): use block braces for if statement in SAMLIdPLogin function

This PR addresses a code style issue in the SAMLIdPLogin function within the idp-login.tsx file. Previously, we were using a single-line if statement without block braces. However, this can potentially lead to confusion and errors in more complex code.
To improve readability and maintainability, we've updated the if statement to use block braces. This makes it clear where the conditional code starts and ends, and ensures that we follow best practices for code style.
Changes include:

Updating the isReady check in SAMLIdPLogin function within idp-login.tsx to use block braces for the if statement.

This change should make the code in idp-login.tsx easier to read and maintain.

@Musyonchez You could combine all the "block braces" PRs for ease of merging.

In order to send different PRs I had to git checkout -b every issue so my
local repo is the same as the main repo on boxyhq.
On Thu, Mar 28, 2024 at 2:05 AM Deepak Prabhakara @.***>
wrote:

@Musyonchez https://github.com/Musyonchez You could combine all the
"block braces" PRs for ease of merging.
—
Reply to this email directly, view it on GitHub
https://github.com/boxyhq/saas-starter-kit/pull/1196#issuecomment-2024127038,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU3A7LDZX2SFRY3L2YDRMFTY2M7CZAVCNFSM6AAAAABFLMBQQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUGEZDOMBTHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Raising error does not increase the num_delivered, and the server keep retrying the same message

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Raise error in Map Handler with Server
Check the logs that the Map Handler will run again with same message

Expected behavior
A clear and concise description of what you expected to happen.
Raising error in map handler should crash and gracefully shutdown
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

Kubernetes: [e.g. v1.18.6]
Numaflow: [e.g. v0.5.1]
Numalogic: [e.g. v0.2.0]
Numaflow-python: [e.g. v0.1.1]

Additional context
Add any other context about the problem here.
https://numaproj.slack.com/archives/C03GQ3AMHE1/p1681697184895659

Message from the maintainers:
Impacted by this bug? Give it a 👍. We often sort issues this way to know what to prioritize.

If the expectation is that the pod will restart for every user exception, then i dont think thats the right thing to do.
if thats what is needed, users can force the exit of a udf container in the catch block.
However, if the intent is to retry for an exception, then i think we should bake that behavior in to gRPC error handling semantics (especially for map).

The problem is more on the num_delivered is not increasing. as discussed in the slack thread.

hmm, May I ask is there nay update on this issue?

we added #88, @jy4096/@ashwinidulams is this fixed?

The problem is more on the num_delivered is not increasing. as discussed in the slack thread.

As mentioned above, num_delivered is not increasing after I raise an exception in map handler function.

Is the pod getting restarted after you raise the exception?

I don't think so.

This will be resolved via https://github.com/numaproj/numaflow/issues/719

will be released in 0.10


Backslashes 932100, 932110

This PR updates the comments for rules 932100 and 932110 to use the \x5c representation of the backslash character.
This is part of ongoing issue https://github.com/coreruleset/coreruleset/issues/2332.

Thanks for approving!
Merging.


Broken in Cordova 8

Looks like this plugin is broken in cordova 8.  I get the error that /platforms/android/AndroidManifest.xml does not exist. It looks like Cordova changed the folder structure.

Hmm...
The platform file should be created at run-time, right?
See here: https://github.com/gordol/cordova-brother-label-printer/blob/master/plugin.xml#L39
        <config-file target="AndroidManifest.xml" parent="/manifest">
            <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
            <uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
            <uses-permission android:name="android.permission.INTERNET"/>
            <uses-permission android:name="android.permission.USB" />
            <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
            <uses-feature android:name="android.hardware.usb" android:required="true" />
        </config-file>

According to the release notes, this actually changed in Version 7 of Cordova, not 8.
https://cordova.apache.org/announcements/2017/12/04/cordova-android-7.0.0.html
<!-- An existing config.xml -->
<edit-config file="AndroidManifest.xml" target="/manifest/application" mode="merge">

<!-- needs to change to -->
<edit-config file="app/src/main/AndroidManifest.xml" target="/manifest/application" mode="merge">

Can you give that a try? If it works, I'm happy to accept a pull request.

We may need to overhaul permissions to request at run-time too...

is is broken in cordova 8 which includes cordova-android 7 :-)


interactive visualization is based on working dir, not model if model passed

If you pass in a model to rasa interactive, the stories that create the visualization do not come from that model. This is due to the fact that the data for the visualization comes from the data path and not from the model itself: https://github.com/RasaHQ/rasa/blob/1.5.3/rasa/cli/interactive.py#L90
To reproduce:
cd rasa/examples/moodbot
rasa train
cd ../formbot
rasa interactive -- model ../moodbot/models/<moodbot model>

the visualization that appears comes from formbot stories, but if you talk to the bot in interactive, it is the moodbot.

Not feasible since the stories are not packaged in the model, behavior clarified here: https://github.com/RasaHQ/rasa/pull/4834#discussion_r358737104


p2p: restore the type p2p.ID

This change was introduced by https://github.com/cometbft/cometbft/pull/4148, where p2p.ID has become p2p/nodekey.ID.
Sorry, but this does not make sense.

In fact, in more general terms, any package that uses the p2p layer to implement a reactor should be able to do so by only importing the p2p package.
Now it has to import a bunch of packages, this is not great.

Good point 👍 Will revert


Option to skip insertion of ?

It seems dash_tabulator_min.js always inserts the default style in the form of a

Could you show an example, might make it easier to track down
Not sure if it's something I did or upstream in react-tabulator or tabulator or even dash

@jkorinth I've just added react-tabulator themes where you can specify in the dash-tabulator constructor one of the existing themes https://github.com/preftech/dash-tabulator#themes
There is also an option to turn off a theme by setting the theme parameter to ""
dash_tabulator.DashTabulator(
        id='tabulator',
        theme="",
        options=options,
        downloadButtonType=downloadButtonType,
        clearFilterButtonType=clearFilterButtonType,
    ),

import 'react-tabulator/lib/styles.css'
is still included as it's a requirement for tabulator to work. But the main themes are now configurable.

Assuming this is resolved

Assuming this is resolved


How to write new line at markup in emulator?

AFAIK emulator have Markdown markup language

In Markdown, you can insert a single break with two newline characters: \n\n
You can insert multiple breaks by using the <br/> element.
More details here: http://daringfireball.net/projects/markdown/syntax#p

 works, \n\n - not!


Object.keys throws an error if the 2nd argument is not a function

I've had a small issue with the Object.keys extend, when combined with the following pattern :
[obj1, obj2, obj3, obj4, obj5].map(Object.keys)

Object.keys will be called with 3 arguments here, which passes the check "arguments.length > 1" (https://github.com/andrewplummer/Sugar/blob/master/lib/object.js#L298). But since the second argument is not a function, fn.call will throw an error right after.
Are you open to a PR to change this behaviour? Checking that the second argument is a function would make this quite safer.
Thanks!

Hi, so there's a couple of things about this. First of all a lot has changed since in the new version that's soon to be released. It's still doing only a basic existence check, which will not fix this error, but I'm willing to add a function check to make this stronger. Additionally, 2.0.0 has a new method lock that is designed for exactly the kind of situation. It will create a new function that calls the original with a locked number of arguments. So in you're case here you would simply have to do this:
[obj1, obj2, obj3, obj4, obj5].map(Object.keys.lock(1));

Or, since Object.keys is fixed at a length of 1, just this:
[obj1, obj2, obj3, obj4, obj5].map(Object.keys.lock());

Either way will work.

Hi!
Thanks for the workaround. Although here I can't apply it.

Hi. I've applied a fix to the new branch for v2.0.0 for this. Sorry, a lot has changed in the new version so I just went ahead and made this change (also wanted to add unit tests). Anyway thanks for your work on this. Will go out in 2.0.0 (should be quite soon).

Update: Note that Object.keys is going to lose its callback in 2.0.0. (preferred method of iteration will be Object.forEach instead), so this problem will go away in any case.
Still will be released soon but taking longer than expected. Thanks for your patience.

No longer impacted by the issue as I changed some of my build tasks, but thanks for working on this nonetheless!


JSONB arrays are sorted when using a rename transform

PGSync version: 2.2.1
Postgres version: 12.5
Elasticsearch version: Opensearch 1.2.4
Redis version: 6.0.10
Python version: 3.10
Problem Description: JSONB columns containing lists cannot be renamed without being sorted.
Steps to reproduce:
Schema:
[
  {
    "database": "mydb",
    "index": "myindex",
    "nodes": {
      "table": "mytable",
      "schema": "public",
      "columns": ["id", "array"],
      "transform": {
        "rename": {
          "array": "renamed_array"
        }
      }
    }
  }
]

Postgres Table
CREATE TABLE mytable (
    id SERIAL PRIMARY KEY,
    array JSONB NOT NULL
);

Some example rows
INSERT INTO mytable (array) VALUES ('[3, 2, 1]'), ('[19, 12, 13]');

Once those rows are synced with elastic you will see the array values have been sorted and do not match those in postgres.
This was very surprising behavior and took a while to debug. If sorting can't be removed, it should at least be called out in the documentation.

Sorry about this.
I can remove the sorting. I can see why this is not desirable as its modifying the result.
I will change this to not sort
PS: We also sort the output from Elasticsearch to make the tests more predictable.
Is this an issue for you as well?

No problem! I appreciate you getting back to me.
I think it's completely reasonable for test code to sort output after it is retrieved from Elasticsearch. As long as it has no impact on the production behavior.

To be clear I mean that PGSync should not sort or mutate data in any way from postgres when using the rename transform. I don't care what happens in test code.

PGSync no longer sorts the data returned from the db.
This was originally done in transform


Unable to pay projects on Goerli with NFTs

Summary
Users have reported that they are unable to pay for projects on Goerli using NFTs. Additionally, some users have reported that they have encountered this issue multiple times. The bug is related to the mainnet terminal address being used on the Goerli network. The terminal address that should be used on Goerli is 0x55d4dfb578daA4d60380995ffF7a706471d7c719, but instead, the mainnet terminal address 0x594Cb208b5BB48db1bcbC9354d1694998864ec63 is being used. The hypothesis is that the issue occurs when users start the create flow on the mainnet and then switch to Goerli midway through, but the mainnet address is already saved in local storage. This issue poses a risk for the mainnet network as well, as projects launched on Goerli could be launched on the mainnet if a user starts on Goerli and then switches to the mainnet.
Steps to reproduce

Start the project creation flow on the mainnet
Switch to the Goerli network midway through the flow
Attempt to pay for the project using NFTs after deploy

What is the expected correct behavior?
The project should be paid for using NFTs on the Goerli network.
Discord Link
https://discord.com/channels/775859454780244028/1066931705627291739/1066931709205037106

I am trying to recreate this one @aeolianeth and am having trouble. Looking at the code, it seems that the terminal is set on the fundAccessConstraint. From what I can see, this is set when changing the distribution limit. This is what I have tried to recreate it:
1. Start a new project creation on goerli with wallet = mainnet
2. GO through project creation, making sure to set a specific distribution target
3. On review, change network
4. Deploy
5. Check console logs

![image](https://user-images.githubusercontent.com/104132113/214209293-94da4887-9862-45f8-96e6-cb9fdccf0a38.png)

Wait, I might have the ticket address info backwards, let me investigate

Need reassurance, but I think 0x55d4dfb578daA4d60380995ffF7a706471d7c719 is the goerli and 0x594Cb208b5BB48db1bcbC9354d1694998864ec63 which would mean everything is working as intended?

Just for sanity testing, I changed my local to mainnet and it produces 0x594Cb208b5BB48db1bcbC9354d1694998864ec63 even when following the same steps above in reverse

and for further sanity, I tried the same on goerli.juicebox.money

Closing:

https://discord.com/channels/775859454780244028/1066931705627291739/1067296312489431121


request i18n on tutorial

I am having trouble searching for how to i18n a web app in flask, so it would be nice if i18n is included in the tutorial.

Sorry, that's outside the scope of the tutorial. There are quite a few other resources around about doing that.


Correct C++ debug optimization flag order.

To properly support gcc's _FORTIFY_SOURCE feature some optimization
level above zero (i.e., "-O0") is required.  Mptcpd explicitly adds
the "-Og" flag when debugging is enabled, but that flag was being
overridden for the mptcpd C++ build test, `test-cxx-build', due to the
way it was appended to the C++ compiler flags variable, CXXFLAGS.
CXXFLAGS ended up containing "-Og -g -O0".  The trailing optimization
flag "-O0" superceded the earlier "-Og" flag, which ultimately caused
optimization to be disabled entirely.  That triggered a preprocessor
warning on some platforms:
/usr/include/features.h:397:4: warning: #warning _FORTIFY_SOURCE
requires compiling with optimization (-O) [-Wcpp]
Append the "-Og" flag to CXXFLAGS in the `configure' script rather
than the Makefile to work around the optimization flag ordering
issue.  CXXFLAGS now contains "-g -O0 -Og", which causes "-Og" to
supercede "-O0" on the compiler command line.  This enables enough
optimization to support both debugging and _FORTIFY_SOURCE.
This change also allows the default optimization level "-O2" to be
used for the test-cxx-build program when debugging is disabled.
Fixes #80.

Thanks Mat!


Swift3 Updates

Updated for the latest Swift 3 syntax, and @FranciscoAmado even fixed some bugs that popped up in the conversion!
Things got a little messy since updates were done to the master between now and when I created the fork, but it should be at the very least helpful for updating to Swift 3.

It's unwise, to mix a lang update (2.2 -> 3.0) plus fixes, in the same PR. It makes it very difficult for us to review.

An alternative may be a PR with the migration and another, with the fixes, after that one is accepted?! But how would you accept the first if, functionally, the app is broken?

I'll redo it purely as a Swift 3 update in a day or two. It needs to be redone anyway, since master changed since I started the Swift 3 updates. And then we can figure out those bugs after, if that's what you want.

Closing this as https://github.com/MailOnline/ImageViewer/pull/58 has been merged in. Could you @FranciscoAmado create a new PR with the fixes if they are still relevant? Many thank 👍


[tool_crash] Tried run on oldest device and flutter crashed with message: String: <57 characters>

I tried to debug my application on the oldest device (Samsung SM-T287) and flutter crashed. Only a black screen appeared. Following output generated by flutter command line tool
Command
flutter --no-color run --machine --track-widget-creation --device-id=310088c61c2c5400 --start-paused --no-sound-null-safety --profile --cache-sksl --dart-define=flutter.inspector.structuredErrors=true lib/main.dart

Steps to Reproduce

Connect oldest device, mine was Samsung SM-T287 7'' Tablet
And try running any application

Logs
String: <57 characters>

[✓] Flutter (Channel stable, 3.3.9, on macOS 12.1 21C52 darwin-arm, locale en-GB)
    • Flutter version 3.3.9 on channel stable at /Users/ndasim/fvm/versions/3.3.9
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b8f7f1f986 (7 weeks ago), 2022-11-23 06:43:51 +0900
    • Engine revision 8f2221fbef
    • Dart version 2.18.5
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/ndasim/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F100
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.74.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.56.0

[✓] Connected device (4 available)
    • SM T287 (mobile)                     • 310088c61c2c5400 • android-arm    • Android 5.1.1 (API 22)
    • Android SDK built for arm64 (mobile) • emulator-5554    • android-arm64  • Android 10 (API 29) (emulator)
    • macOS (desktop)                      • macos            • darwin-arm64   • macOS 12.1 21C52 darwin-arm
    • Chrome (web)                         • chrome           • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Flutter Application Metadata
Type: app
Version: 3.0.14+214
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 5464c5bac742001448fe4fc0597be939379f88ea
Plugins
android_id-0.1.3+1
audio_session-0.1.13
background_fetch-1.1.2
connectivity_plus-3.0.2
device_info_plus-8.0.0
file_picker-5.2.4
flutter_background_geolocation-4.8.5
flutter_barcode_scanner-2.0.0
flutter_jailbreak_detection-4e235efd4d5df9d1994cd1d377a0093833293684
flutter_keyboard_visibility-5.4.0
flutter_keyboard_visibility_linux-1.0.0
flutter_keyboard_visibility_macos-1.0.0
flutter_keyboard_visibility_web-2.0.0
flutter_keyboard_visibility_windows-1.0.0
flutter_plugin_android_lifecycle-2.0.7
flutter_tts-3.5.3
geolocator-9.0.2
geolocator_android-4.1.4
geolocator_apple-2.2.3
geolocator_web-2.1.6
geolocator_windows-0.1.1
google_maps_flutter-2.2.3
google_maps_flutter_android-2.4.0
google_maps_flutter_ios-2.1.12
google_maps_flutter_web-0.4.0+3
heresdk-navigate-flutter-<IP_ADDRESS>.3261
image_picker-0.8.6
image_picker_android-0.8.5+4
image_picker_for_web-2.1.10
image_picker_ios-0.8.6+5
just_audio-0.9.31
just_audio_web-0.4.7
optimize_battery-0.0.4
package_info_plus-3.0.2
path_provider-2.0.11
path_provider_android-2.0.22
path_provider_ios-2.0.11
path_provider_linux-2.1.7
path_provider_macos-2.0.6
path_provider_windows-2.1.3
permission_handler-10.2.0
permission_handler_android-10.2.0
permission_handler_apple-9.0.7
permission_handler_windows-0.1.2
sentry_flutter-6.18.1
shared_preferences-2.0.15
shared_preferences_android-2.0.14
shared_preferences_ios-2.1.1
shared_preferences_linux-2.1.2
shared_preferences_macos-2.0.5
shared_preferences_web-2.0.4
shared_preferences_windows-2.1.2
sqflite-2.2.2
store_redirect-2.0.1
url_launcher-6.1.7
url_launcher_android-6.0.22
url_launcher_ios-6.0.17
url_launcher_linux-3.0.1
url_launcher_macos-3.0.1
url_launcher_web-2.0.13
url_launcher_windows-3.0.1
vibration-1.7.6
wakelock-0.6.2
wakelock_macos-0.4.0
wakelock_web-0.4.0
flutter_zebra_utility-4029f3615b6f440d77f91d1ba375fefd07f1eb82

Thanks for the report @ndasim
Do you get any error log while running the app ? If so, can you provide the same ?
Going by the error, it looks similar to https://github.com/flutter/flutter/issues/108812


Hugo not made executable using govendor since latest update - Ubuntu 17.04

I've run up a new VM of Ubuntu 17.04 and attempted to install Hugo following the instructions listed on the website for installation via Govendor.
It's a brand new VM with apt updates fully installed, prior to installing hugo.
Installed Go and verified the installation, same with govendor, and verified the versions for both.
taubin@localhost:~$ go version
go version go1.7.4 linux/amd64

taubin@localhost:~$ ls $HOME/go/src/github.com/gohugoio/hugo
appveyor.yml  config           docshelper      i18n        output            source
bench.sh      CONTRIBUTING.md  examples        LICENSE.md  parser            tpl
benchSite.sh  create           goreleaser.yml  livereload  README.md         transform
bufferpool    deps             helpers         main.go     releaser          utils
cache         Dockerfile       hugofs          Makefile    requirements.txt  vendor
commands      docs             hugolib         media       snapcraft.yaml    watcher

taubin@localhost:~$ hugo version
The program 'hugo' is currently not installed. You can install it by typing:
sudo apt install hugo

taubin@localhost:~$ ls $HOME/go/bin/
govendor

Expected output from hugo --version: version installed given
Actual output from hugo --version: The program 'hugo' is currently not installed. You can install it by typing: sudo apt install hugo

Thanks for getting in touch, but it feels like this is a question  that would be better suited to the Hugo Discussion Forum.  We prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug. You may also find the answers you search for in Hugo Documentation.

This is a bug in either your software, or in your directions, so it should belong here. Posting in the discussion forum is not going to fix this, as it cropped up with the latest update to your software. I'm not sure what else you are expecting me to prove to prove that this is a bug. Your instructions, or your software are broken, which makes this a bug that needs correcting if you want people to continue to use your software.
Posting in a forum about the issue will not get it fixed.

Hi @Taubin,

This is a bug in either your software, or in your directions, so it should belong here.

Well, that is the thing: There are many new GitHub issues that come in daily, and someone need to "triage" them to determine whether they are actual bugs or not.  Usually we get them right, but when a report is incomplete or ambiguous, like the one you filed, then we are not so sure.
Please allow me to

Subject: Hugo not made executable using govendor since latest update - Ubuntu 17.04

My first reactions when I see that title:

Huh?  Govendor creates a hugo file but make it with 0644 permission?
Since lastest update?  You mean the exact instructions were working before?  When?  Or with which older version?
Since latest update of what?  Of Hugo?  Of govendor?  Of Go?

I've run up a new VM of Ubuntu 17.04 and attempted to install Hugo following the instructions listed on the website for installation via Govendor.

There are many different pages on the Hugo website, sometimes with duplicate information.  Could you please be more specific by providing the actual URL?  Did you mean to say https://gohugo.io/overview/installing#fetch-from-github ?  Or did you find the instruction somewhere else?

Installed Go and verified the installation, same with govendor, and verified the versions for both.

Which is nice, thank you, but you didn't tell us specifically what commands you ran to arrive at what you have right now, a.k.a. "Steps to Reproduce".  Are these the two exact commands that you ran prior to arriving at the current situation?
go get github.com/kardianos/govendor
govendor get github.com/gohugoio/hugo

If so, please do spell it out so that others may try to follow your exact steps to reproduce the bug, avoiding ambiguity and potentially preventing a mistriage.  :wink:
So, here is how I would have written if I were you:

Steps to Reproduce
$ cd ~
$ export PATH=/tmp/foo
$ go get github.com/kardianos/govendor
$ $GOPATH/bin/govendor get -v github.com/gohugoio/hugo

Expected Result
Like what the Hugo documentation at https://gohugo.io/overview/installing#fetch-from-github says:

govendor get will fetch Hugo and all its dependent libraries to $HOME/go/src/github.com/gohugoio/hugo, and compile everything into a final hugo (or hugo.exe) executable, which you will find sitting inside $HOME/go/bin/, all ready to go!

Or, in our case, we should see a file at $GOPATH/bin/hugo, i.e. /tmp/foo/bin/hugo.
Actual Result
No $GOPATH/bin/hugo, i.e. no /tmp/foo/bin/hugo.

Apparently, govendor get isn't doing what we think it would do, and it is not quite exactly doing what govendor claims it would do, i.e.:
get      Like "go get" but copies dependencies into a "vendor" folder.

No, it is not quite like go get at all, as go get always builds the library.
Worse yet, I could not get govendor to tell me what it is actually doing even if I were to add the -v verbose flag to the govendor get command, and it happily exits with 0.  Grr...
So, thank you for reporting this issue!  Reopening...

@anthonyfok this issue belongs in the discussion forum. I closed this for a reason. There are plenty of other more important issues floating around that needs attention. If thread started cannot get govendor working (it works fine with make), I suggest he tries an alternative way of installing.

/cc @moorereason, see Issue #3153, PR #3181, and commit d6093aba4d0b74804378013c2326deb3cca58d7e
go get github.com/kardianos/govendor
cd $GOPATH/src/github.com
$(go env GOPATH)/bin/govendor get github.com/gohugoio/hugo
ls -l $GOPATH/bin/hugo

@bep Let @moorereason or @rdwatters fix it.

Workaround in documentation added, see https://github.com/gohugoio/hugoDocs/commit/c4e21471adb2ff32250346fcdaa4e1df11d7d7d2.
The changes will appear on the gohugo.io website probably around the time of the next Hugo's stable release, about a month from now.

Hi @Taubin,
Here is a final wrap up:
It turns out there was an issue with govendor:

"govendor get" does not create $GOPATH/bin/pkgname like go get does (kardianos/govendor#330)

which has been kindly fixed by govendor's author in kardianos/govendor#336 (commit kardianos/govendor@cf990b2) 8 days ago.
Also, in the all new Hugo documentation, copyeditor @rdwatters had carefully included a final go install step (since April) at https://gohugo.io/getting-started/installing/#fetch-from-github, which should serve as an elegant catch-all in case the end user is somehow stuck with an older version of govendor.
Last but not least, thank you for bringing up the issue.


Errors using InplaceAdd with from multi-select LookupEditor

I am seeing multiple issues utilizing the InplaceAdd function within a LookupEditor where Multiple=true.
For example, take the Representatives field within the Northwind Customer Row and add InplaceAdd=true:
[LookupEditor(typeof(EmployeeRow), Multiple = true, InplaceAdd = true), ClientSide]
The New/Edit button then appears as expected next to the field.  If there are one or zero selections, this function works fine.  However after selecting a couple items, this feature produces several errors:

If you just click on the Edit button, an error of "Input string was not in a correct format" is shown.
If you select the option "*** No results. Click to define a new one ***, it selects that item and does not produce the New Employee dialog as expected.

Is there a workaround for allowing these two great features to work together?

That feature is not compatible yet with multiple select

haha,I met the same problem

I am facing the same problem. Can I get any help on this as it is one of the requirements in my project.
Thanks

I solved that issue as, not editing inplace when it is multiple. if it is multiple, always add new things.
firstly at addInplaceCreate method in serenity.Script.UI.js
     if (!this.$multiple)            inplaceButton.attr('title', (isNew ? addTitle : editTitle)).toggleClass('edit', !isNew);
it is at line 4468 in serenity.Script.UI.js.
and then, add if multiple control also at line 4719.
`                    if (!self.$multiple)
self.set_value(null);
                if ((dci.type === 'create' || dci.type === 'update') && ss.isValue(dci.entityId)) {
                    if (self.$multiple)
                        self.set_value(self.get_value() + ',' + dci.entityId.toString());
                    else self.set_value(dci.entityId.toString());
                }

`


KYLIN-3293, fix FixedLenHexDimEnc that return a wrong code length lea…

…ds to cut bytes error.

Can one of the admins verify this patch?

Codecov Report

Merging #123 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master     #123      +/-   ##
============================================
- Coverage     21.83%   21.83%   -0.01%
  Complexity     3886     3886
============================================
  Files           999      999
  Lines         60067    60069       +2
  Branches       8675     8675
============================================
- Hits          13117    13115       -2
- Misses        45729    45732       +3
- Partials       1221     1222       +1

Impacted Files
Coverage Δ
Complexity Δ

...he/kylin/cube/gridtable/TrimmedCubeCodeSystem.java
62% <ø> (ø)
5 <0> (ø)
:arrow_down:

.../org/apache/kylin/dimension/FixedLenHexDimEnc.java
82.17% <0%> (-1.3%)
22 <0> (ø)

.../apache/kylin/cube/cuboid/TreeCuboidScheduler.java
64.56% <0%> (-0.79%)
0% <0%> (ø)

...g/apache/kylin/metadata/cachesync/Broadcaster.java
55.22% <0%> (-0.5%)
21% <0%> (ø)

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build 3086

0 of 2 (0.0%) changed or added relevant lines in 1 file are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.002%) to 23.871%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core-metadata/src/main/java/org/apache/kylin/dimension/FixedLenHexDimEnc.java
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

core-cube/src/main/java/org/apache/kylin/cube/cuboid/TreeCuboidScheduler.java
1
68.5%

core-metadata/src/main/java/org/apache/kylin/dimension/FixedLenHexDimEnc.java
2
82.95%

Totals

Change from base Build 3078:
-0.002%

Covered Lines:
14339

Relevant Lines:
60069

💛  - Coveralls


Client is not getting all retained messages for subscribed topics (Clean Session: false)

Environment

OS:  Ubuntu 14.04
Erlang/OTP:  19 / 8.3
EMQ: 2.2

Description

Client A subscribes to 1000 topics, using Clean Session: 0 (false)
Client A Disconnects
Client B connects publishing 1 retained message to these 1000 topics (1 message per topic)
Client A re-connects (clean session False) - and is not getting all the messages
but only part (varying).

If the subscription is accomplished (Client B) after the messages are published (Client A),
all messages are received once client B subscribes to the topics. - with retained flag: True
if Client B subscribed before the publish (and disconnects like steps above), it will only get part of the messages, and the retained flag will be False (which is expected by the spec)

It MUST set the RETAIN flag to 0 when a PUBLISH Packet is sent to a Client because it matches an established subscription regardless of how the flag was set in the message it received [MQTT-3.3.1-9].
ref: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html

Yet I got only 972 messages out of the 1000, and emq disconnects the client.
some logging, last message is not 999 but 884 - disconnecting the client
2017-10-07 11:16:02.513 [info] <0.17640.48>@emqttd_protocol:trace:350 Client(12345@<IP_ADDRESS>:60839): SEND PUBLISH(Q0, R0, D0, Topic=test_topic_884, PacketId=undefined, Payload=<<"{\"type\":\"SIMPLE_MESSAGE\",\"date\":\"2017-10-07T11:11:26.568Z\",\"message\":\"this is a test message -884-\",\"id\":884}">>) 2017-10-07 11:16:11.776 [info] <0.17640.48>@emqttd_protocol:trace:347 Client(12345@<IP_ADDRESS>:60839): RECV DISCONNECT(Q0, R0, D0)

@syberkitten
 Client(12345@<IP_ADDRESS>:60839): RECV DISCONNECT(Q0, R0, D0)

？？？

@turtleDeng
Tested again, and results are ok :)
issue was something to do with the tooling on my end.
I'm not able to reproduce the same problem again
Thanks.


Remove goversion ldflag

Fixes #2

:+1: but depends on https://github.com/prometheus/alertmanager/pull/296


Adding versioning to schema?

A common problem with parsing through tournament data and stats is lack of versioning for when points are used. Especially around the times points are updated, event organizers often specify that points updates after XYZ date are no longer valid, but it's effectively impossible to store that data, so effectively there are many lists that appear illegal or like junk, despite being legal in the previous points cycle. This would allow for things like pulling lists from listfortress with specific versions, for example:
Current example:
{"faction":"galacticrepublic","pilots":[{"id":"anakinskywalker-btlbywing","ship":"btlbywing","points":6,"upgrades":{"force-power":["shatteringshot"],"turret":["ioncannonturret"],"torpedo":["protontorpedoes"],"astromech":["r4pastromech"],"modification":["afterburners"]}},{"id":"obiwankenobi-eta2actis","ship":"eta2actis","points":5,"upgrades":{"force-power":["patience"],"talent":["marksmanship"],"cannon":["autoblasters"],"astromech":["r7a7"]}},{"id":"ahsokatano","ship":"delta7aethersprite","points":4,"upgrades":{"force-power":["compassion"],"astromech":["c110p"],"configuration":["calibratedlasertargeting"]}},{"id":"barrissoffee","ship":"delta7aethersprite","points":3,"upgrades":{"force-power":["instinctiveaim"],"missile":["concussionmissiles"],"configuration":["calibratedlasertargeting"]}},{"id":"contrail","ship":"nimbusclassvwing","points":2,"upgrades":{"configuration":["alpha3bbesh"]}}],"points":20,"vendor":{},"version":"2.5.0"}
Suggested example:
{"faction":"galacticrepublic","pilots":[{"id":"anakinskywalker-btlbywing","ship":"btlbywing","points":6,"upgrades":{"force-power":["shatteringshot"],"turret":["ioncannonturret"],"torpedo":["protontorpedoes"],"astromech":["r4pastromech"],"modification":["afterburners"]}},{"id":"obiwankenobi-eta2actis","ship":"eta2actis","points":5,"upgrades":{"force-power":["patience"],"talent":["marksmanship"],"cannon":["autoblasters"],"astromech":["r7a7"]}},{"id":"ahsokatano","ship":"delta7aethersprite","points":4,"upgrades":{"force-power":["compassion"],"astromech":["c110p"],"configuration":["calibratedlasertargeting"]}},{"id":"barrissoffee","ship":"delta7aethersprite","points":3,"upgrades":{"force-power":["instinctiveaim"],"missile":["concussionmissiles"],"configuration":["calibratedlasertargeting"]}},{"id":"contrail","ship":"nimbusclassvwing","points":2,"upgrades":{"configuration":["alpha3bbesh"]}}],"points":20, "pointsversion":"2.5.1","vendor":{},"version":"2.5.0"}
Similarly, we could use this versioning in listfortress itself in event details to distinguish what events were run with what points.
Example use case:
Richmond Open is an event planned for May 27th-29th. AMG has stated there is a points update coming on or before the 27th, so when this data is imported into ListFortress, it will not have the context that despite being after the release date of points. Anyone attempting to use this data will potentially need to infer that it was played with out-of-date points.
Similarly, if the points update happens on say May 25th, players at events will be unable to use squad builders for the event itself, since they will have been updated to latest points. Having a repository of all previous points/upgrade slots as part of the XWS spec itself may allow for easier support for squadbuilders to support different point values as well.

Given that I don't believe the official documents have version numbers, but instead an "effective date", should that be considered as the unique identifier, to avoid any potential confusion around what "2.5.1" means? Or is there an honest-to-god version number I'm not seeing?
Worth considering additionally a pointsSource attribute? Just using a version number/effective date wouldn't cleanly allow for something like a builder for a custom event that uses some other method of points. Maybe not necessary, just thinking about future-proofing.

You're right, there is no official versioning. But, we often get effective date overlap, especially when they push out smaller changes. I'm not sure it's worth preserving the mistakes that tend to only stay up for a couple of days, but if I remember correctly in the last few points changes we have 2-3 different minor versions, all with the same effective date. We'd have to create a master versioning number/system system accordingly to avoid that, if everyone else is concerned about it as well.
By points source, do you mean for allowing some API that could be hosted to access points directly in realtime used by other services like squadbuilders etc? Or for custom rulesets, like for one off tournament rules with different points, etc? I think both are pretty valid, but wasn't sure which you meant!

You're right, there is no official versioning. But, we often get effective date overlap, especially when they push out smaller changes. I'm not sure it's worth preserving the mistakes that tend to only stay up for a couple of days, but if I remember correctly in the last few points changes we have 2-3 different minor versions, all with the same effective date. We'd have to create a master versioning number/system system accordingly to avoid that, if everyone else is concerned about it as well.

The small mistakes that get ironed out actually make me more in favor of using "effective date" as the versioning, I think :D If we're using ~semantic versioning, it's not clear whether those mistakes should/would be preserved (at least to me), whereas if you're using "effective date" versioning, I think it's pretty obvious they shouldn't be (effective date 3/01/2022 is the "latest state" of everything on that effective date). This assumes that we don't get anything other than a few minor mistakes fixed soon after an effective date doc, which... I think is the case? But I'm not positive?

By points source, do you mean for allowing some API that could be hosted to access points directly in realtime used by other services like squadbuilders etc? Or for custom rulesets, like for one off tournament rules with different points, etc? I think both are pretty valid, but wasn't sure which you meant!

I was thinking of the second. The specific example that came to mind was the REMEMBER THE GOOD TIMES tourney, where every ship was at its lowest historic price point. I don't think there's really any way to support that without some special "other" source of points. That said, an API that folks can call to get points for certain versions does seem like the sort of mature service that would be really useful...
One other thing - I'm realizing that "points*" is a bit of a misnomer, given that the version also includes loadout values, slots, and keywords... but given that that misnomer is sort of enshrined by AMG calling it a "points document", I guess that's probably an upstream issue that's not worth fretting about :)

Actually, slight correction. It seems like there is an official numbering system, but it's extremely opaque. The filename for the latest points document is: SWZ_Ship_Points_1.4.1.pdf. I'm having trouble finding previous versions of the documents, but would be great to have as a reference to see if it's something we could actually use or if it is not going to be maintained well.

The small mistakes that get ironed out actually make me more in favor of using "effective date" as the versioning, I think :D If we're using ~semantic versioning, it's not clear whether those mistakes should/would be preserved (at least to me), whereas if you're using "effective date" versioning, I think it's pretty obvious they shouldn't be (effective date 3/01/2022 is the "latest state" of everything on that effective date). This assumes that we don't get anything other than a few minor mistakes fixed soon after an effective date doc, which... I think is the case? But I'm not positive?

I somewhat agree with this, but, it seems like a large amount of confusion could/would come from these, as the effective dates listed in the documents have historically not lined up very well with the actual date they're released. From both AMG/FFG we've commonly gotten documents listed that came into effect the prior month. If I'm creating some interface, which one of these is less confusing to pick when users are trying to pick a points version?
1.4.1 (Released 24 Feb 2022)
1 Mar 2022 (Released 24 Feb 2022)

Actually, slight correction. It seems like there is an official numbering system, but it's extremely opaque. The filename for the latest points document is: SWZ_Ship_Points_1.4.1.pdf. I'm having trouble finding previous versions of the documents, but would be great to have as a reference to see if it's something we could actually use or if it is not going to be maintained well.

Oh, neat! That seems like the best option, assuming that AMG remembers to increment the versioning, which... I would THINK they would 😅

1.4.1 (Released 24 Feb 2022)
1 Mar 2022 (Released 24 Feb 2022)

Do we really care what day it was released? I guess there would potentially be confusion for tournaments played on Feb. 26... but then, theoretically those lists should have the pointsVersion embedded and pointing to "1 Mar 2022".

Maybe the real answer is we don't trust AMG enough to do either dates or versions with any consistency and each points environment gets a GUID identifier and gets decorated with metadata like version number and effective date... but I think that requires some additional engineering to maintain, obviously... probably too much :)

Do we really care what day it was released? I guess there would potentially be confusion for tournaments played on Feb. 26... but then, theoretically those lists should have the pointsVersion embedded and pointing to "1 Mar 2022".

I think so? At least I do, one of the main cases something like this would be to fix is the confusion around those edge cases. I think you're right that it could be mostly fixed by just using the effective date in whatever dropdown and not listing the release date at all, but I can already see the bug reports coming in for something like metawing saying "i chose march 1 points but tournaments in february showed up".
Maybe the best course of action is to see what happens with the next points update? It's coming in a few weeks, and it's not like any of this would be done by the time those release anyways. Most of the interesting/hard work is only possible once we have multiple versions of points regardless!

That makes sense to me! And the truth of it is as long as the historical points are being recorded, the id/reference that gets used seems like it should be pretty easily updateable in the future.

Oh, they stopped adding IDs, so let's use dates.

CTRL+F for the four IDs we have and replace with those dates

Sounds like a good idea. I’ll just add that this repo often has incremental error corrections as we notice problems with it, and we need to do a new “release” tag on GitHub to make vassal pick up any changes. So we will need some kind of semantic versioning scheme because list fortress won’t care about bug fix level version changes, only “new points” or “new ships” level of changes

I've been thinking on this more. Any thoughts? Starting to think the only user of this historical data would be me so seems silly to build out a huge standard for it for everyone to have to deal with, but curious if others have a desire/want for it.

I think it's a decent addition but agree it has limited utility. Most people don't really care about old points values and old events - it's usually enough just to look at the lists used and not worry about the points tallies.
How would you handle changes in squad building logic? Not just points changes but something like the 2.0->2.5 shift

I'm thinking of something like an array of dates/versions with associated costs/loadouts? Basically something like this:
[   {     "2.0.1": 5   },   {     "2.0.2": 5   },   {     "2.5.1": {       "cost": 5,       "loadout": 10     }   } ]
With a reference of versions to dates somewhere as well.

Let's see - so as things stand now, you'd need:

squad points
loadout value
slots
keywords (maybe not, if there's no precedent for change)
...anything else?

Including all that information on every pilot could be quite cumbersome for
us maintainers, but I’m not sure where else to store it. I also hope that
they don’t change squad building again and make us change the logic…
On Tue, 16 May 2023 at 11:39 am, Doug Stone-Weaver @.***>
wrote:

Let's see - so as things stand now, you'd need:

squad points
loadout value
slots
keywords (maybe not, if there's no precedent for change)
...anything else?

—
Reply to this email directly, view it on GitHub
https://github.com/guidokessels/xwing-data2/issues/542#issuecomment-1548929899,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLOVLOVR2UWAQI6YI7XG6TXGLZI3ANCNFSM5VDC4GKQ
.
You are receiving this because you commented.Message ID:
@.***>

Here's maybe a really dumb thought, because my experience using tags and releases in Git is nonexistent, but can we handle this with Git tags? Like, tag whatever commit with that version number version, and then consumers could (if they wanted) potentially pull from those commits? It feels a little funky to have to clone the repo multiple times to get multiple versions, but you get full versioning with almost no additional maintenance cost, and the cost to utilize it doesn't seem much worse than it would be to have it as a "native" concept...

Hah, I never thought of that, but it's probably the least bad solution of all the suggested changes. Yes, there will be some mistakes to be corrected along the way, and a lot of image references will be wrong, but it's all in the history.
Maybe the better solution is to make a branch of each "version" of points, that can be up to date with correct images and such?  Could even use the github releases versions to have clear labeling of them as well.

I think that’s a good idea as well. The only issue will be if there isn’t a
clean commit that lines up with a each past version. If we are lucky then
there should be, probably? Then all we have to do is go back and add tags
to this repo for points versions.
If not, you could fork this repo and create a branch which just has a
commit for each points revision but that would involve more messing about
with git commands
On Wed, 17 May 2023 at 1:24 am, chrisalleng @.***>
wrote:

Hah, I never thought of that, but it's probably the least bad solution of
all the suggested changes. Yes, there will be some mistakes to be corrected
along the way, and a lot of image references will be wrong, but it's all in
the history.
Maybe the better solution is to make a branch of each "version" of points,
that can be up to date with correct images and such? Could even use the
github releases versions to have clear labeling of them as well.
—
Reply to this email directly, view it on GitHub
https://github.com/guidokessels/xwing-data2/issues/542#issuecomment-1550077327,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLOVLJAISE6XZZWXVKNOZTXGOZ5VANCNFSM5VDC4GKQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I think it's safe to say we don't have the manpower for this now. Maybe later down the road it's worth taking a look at, but that time isn't now


Can't access memory locations larger than 0xFFFF

Due to the data size limit it's unable to access more than FFFF addresses

Possible solution: fragmenting ram to sections

Implementation: use an instruction to change memory bank, UpTo 0xFFFF banks making the max ram amount 0xFFFFFFFF which is more than plenty


CI: Remove duplicated x86_64-unknown-linux-gnu target from build job

It's already defined on line 613 and is running twice, for example:

https://github.com/uutils/coreutils/actions/runs/4518817884/jobs/7959076091
https://github.com/uutils/coreutils/actions/runs/4518817884/jobs/7959076264

Good catch, thank!


base directory naming typo

https://github.com/ptavares/zsh-terraform/blob/18213bf3b340a5f014bdaf12c9e535220bf17962/zsh-terraform.plugin.zsh#L24

https://github.com/ptavares/zsh-terraform/commit/397a75af29240a8154638de200c435387c87f6cc


v4 Suggestion: Add fallbacks for when JavaScript is disabled

It's just a thought, rather than relying solely on Javascript/jQuery for a lot of the components, how about implementing as much as possible using CSS. Seeing as CSS can do a lot of functions that can make Javascript unneeded these days, for those people that don't use jQuery, it would at least still allow them to use Bootstrap. And maybe still have some Javascript functions to make things like tooltips do extra things that Javascript is needed for, but the components can still work in at least a rudimentary form if jQuery, or Javascript isn't used. Anyway, just food for thought.

Any specific/concrete suggestions related to this?

Not as such, I was thinking that it would be nice to be able to have the majority of components that need or require Javascript to not have to rely on having Javascript at all. Might make for a nice fallback for those that purposely disable Javascript. We might be able to get some .onion sites working with BS that actually look nice without the use of Javascript, lol.
A thought I had for the tooltips though, is to have classes that force positioning. I noticed in your Blog post that you mentioned about have auto-positioning, which obviously wouldn't work if Javascript is disabled, unless of course there's a way to do auto-positioning with pure CSS, not that I've ever come across such a thing before, lol.
Also, feel free to check out some of the extra's I've added onto BS for my own purposes, if only for idea's.
http://studiojunkyard.github.io/LibreICONS/

@StudioJunkyard we no longer include any icon fonts with Bootstrap as of V3 so the LibreICONS wouldn't be applicable here

Sorry, wrong link, I meant the CSS I added to Bootstrap here, http://studiojunkyard.github.io/LibreICONS/examples.html#custom

Understood. It basically comes down to what @fat & @mdo are willing to implement/support.
Current policy in this area for reference: http://getbootstrap.com/javascript/#js-disabled

Cool, sorry, I seen "Owner" on your comments, and assumed you were one of them.

I am on the Core Team, but they're the primary contributors.

+1

Probably not going to happen. That's a bit of a shift in our approach to the framework and not something I'd like to see us take on right now.


Is it safe to use this repo?

Hi
Guys I'm a bit scared to use this repo, since it will have access to my api key and secret key, now i can make my own, but i just don't want to reinvent the wheel if this repo and it's creator is trustworthy.
please share you thoughts!

recent updates now?


"exclude" in ditaval results in ant BUILD FAILED

I just migrated from DITA-OT 1.x to 2.0.1 and noticed that the same, unchanged project fails the ant build with BUILD FAILED result when there is an "exclude" in ditaval:
<val>
	<prop att="audience" val="developer" action="exclude"/>
</val>

As soon as I replace 'exclude' by either 'include' or 'flag', the result is BUILD SUCCESSFUL.
I assume that this is not my fault as the project runs well on DITA 1.x, so this looks like a bug.

Please link to a Gist with the verbose log output.

https://gist.github.com/quipsy-karg/b70ca43f22dd95bfc5ee

Seems to be a issue in PDF output. When particular elements are removed, the resulting FO file is invalid.

I hereby confirm that the solution provided by eerohele works like a charm even in my really complex filtering real-world environment. Thank You for providing this solution! :-)
@jelovirt Please merge to master! :-)

Fixed with commit 0d73b27


Unhandled top-level exception: $exn

2020-01-27 10:15:54 UTC [Info] Moving peer $peer to disconnected peer set
peer: {
"host": "<IP_ADDRESS>",
"discovery_port": 8303,
"communication_port": 8302
}
2020-01-27 10:16:55 UTC [Fatal] Unhandled top-level exception: $exn
Generating crash report
exn: "(monitor.ml.Error\n  (Failure\n    "Tried to handle a committed transaction in the pool but its nonce doesn't match the head of the queue for that sender.")\n  ("Raised at file \"stdlib.ml\", line 33, characters 17-33"\n    "Called from file \"src/lib/network_pool/transaction_pool.ml\", line 257, characters 14-107"\n    "Called from file \"list.ml\", line 117, characters 24-34"\n    "Called from file \"src/list0.ml\" (inlined), line 22, characters 40-81"\n    "Called from file \"src/lib/network_pool/transaction_pool.ml\", line 229, characters 8-1023"\n
"Called from file \"src/lib/pipe_lib/broadcast_pipe.ml\", line 89, characters 25-28"\n    "Called from file \"src/pipe.ml\", line 827, characters 4-56"\n    "Called from file \"src/job_queue.ml\" (inlined), line 131, characters 2-5"\n    "Called from file \"src/job_queue.ml\", line 171, characters 6-47"\n    "Caught by monitor coda"))"
☠  Coda Daemon crashed.
The Coda Protocol developers would like to know why!
Please:
  Open an issue:
    <https://github.com/CodaProtocol/coda/issues/new>

  Briefly describe what you were doing and attach the crash report /root/.coda-config/coda_crash_report_2020-01-27_10-16-55.131751.tar.gz

Dup of #4298. Closing.


Format ts/js with prettier, update TS

Adds .prettierrc (default) because some prettier setups check its existence for formatting to work, and it is more convenient to have settings in a separate file.
Adds format:js command to package.json
Formats ts/js with prettier
Updates TypeScript version (because there were type errors in newly installed vscode-language deps during tsc compilation)
Adds tsc compilation task in .vscode/tasks.json (to run auto compilation while development)

Thanks.


Please package testsuite to the distribution tarball

I would like to fix packaging for OpenSUSE, but your release tarball does not contain the tests directory. Could you please distribute it as well?

I meant just adding something like
recursive-include tests *

to MANIFEST.in. You need to test with python3 setup.py sdist what is included (I think it has precedence over excludes, but not sure), and you may end up with something like
recursive-include tests *.py *.pem *.der *.b64 README *.pgp *.dat *.p7* *.crt *.txt

(from my M2Crypto MANIFEST.in).


Tenant delete not working without --no-verifier-check

Is your an issue a feature request? If so, please raise it as an enhancement
Environment

OS / version: Fedora
Processor architecture:
TPM Manufacturer: tpm2-emulator
Keylime version: 16a9cfd

Description
If the verifier is hosted on a different machine than where the tenant is called, the keylime_tenant -c delete command will not work without the --no-verifier-check flag. This is because of the line of code here
https://github.com/keylime/keylime/blob/115d9cf7b4d2e7a25fbc61fca2b1eb6e5ce74e52/keylime/tenant.py#L655
When calling the tenant with a verifier flag for a verifier not in the CONF file, the tenant will first retrieve the status from the verifier. The tenant then uses the verifier address returned by the verifier as opposed to the address passed in the command line. The result is the status check passes, but the delete check fails to connect and shows a url that differs from what was passed in. In our case we had our CONF file set to <IP_ADDRESS>
Expected behavior vs. actual behavior
Expected: delete command works without --no-verifier-check
Actual: --no-verifier-check flag is needed.
Steps to reproduce problem

Stand up a verifier with address <IP_ADDRESS>
Call delete to the verifier using the tenant on a different machine than where the verifier is set up

Relevant logs
Attach any relevant log files that can help to debug your issue.
HTTPSConnectionPool(host='<IP_ADDRESS>', port=8881): Max retries exceeded with url: /agents/4c4c4544-0034-4410-8056-cac04f4d3032 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fd82565edd8>: Failed to establish a new connection: [Errno 111] Connection refused\

@apoorvemohan This is related to the "single database for multiple verifiers" introduced by your PR.
@ljmcgann @mpeters I see this as a problem of documentation, instead of code. My proposal is to add a message alongside the following lines: "it was not possible to connect to verifier at <IP>:<port>. If you are attempt to contact a verifier directly - without a load balancer in front of it, please add the --no-verifier-check flag`"

HTTPSConnectionPool(host='<IP_ADDRESS>', port=8881): Max retries exceeded with url: /agents/4c4c4544-0034-4410-8056-cac04f4d3032 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fd82565edd8>: Failed to establish a new connection: [Errno 111] Connection refused\

@ljmcgann Can you share the tenant command?

Thanks for getting back to me @maugustosilva. Could you clarify what this flag does that it requires a load balancer on the veriifer?

@apoorvemohan
keylime_tenant -c delete -v "<IP_ADDRESS>" -vp 8881 -u 4c4c4544-0034-4410-8056-cac04f4d3032
The CONF file the vm with our verifier has its address set to <IP_ADDRESS>.

@ljmcgann In the CONF on the verifier, if you specify "<IP_ADDRESS>" instead of "<IP_ADDRESS>", do you still see the error?

@apoorvemohan Setting the verifier to <IP_ADDRESS> makes it not require the --no-verifier-check flag

Setting IPs to <IP_ADDRESS> is a very common thing to make systems work where multiple IPs on the host might be involed. We need to make sure it's something that is supported.

Thanks for getting back to me @maugustosilva. Could you clarify what this flag does that it requires a load balancer on the veriifer?

The main idea behind the absence of the --no-verifier-check is that keylime_tenant will, in case of delete operation, query the current status of the agent, in order to figure out which verifier the agent belongs to, before actually issuing the delete. Obviously, this means that the -v parameter might be dynamically overridden if needed.

Setting IPs to <IP_ADDRESS> is a very common thing to make systems work where multiple IPs on the host might be involed. We need to make sure it's something that is supported.

We can support this by having a different bind and public ip fields as suggested here.

My guess @maugustosilva and @apoorvemohan is that this can be closed since the bind addresses for each service part has been merged.

@maugustosilva can you confirm this is fixed?

Not solved yet. Solution seems to be simple, will do it promptly.


OAuth 2.0 plugin and Kong documentation

Summary
In OAuth2 plugin docs, I didn't find any chapter about OAuth2 token generation except the 'Migrating Access Tokens' chapter: https://getkong.org/plugins/oauth2-authentication/#migrating-access-tokens
cURL request
I can generate access tokens using the 'oauth2_tokens' path:
curl -i -X POST http://localhost:8001/oauth2_tokens/ --data "credential_id=dd141531-04bb-48c6-8920-1fd7ee2e9e10" --data "expires_in=3600"
HTTP/1.1 201 Created
Date: Thu, 23 Feb 2017 16:02:09 GMT
Content-Type: application/json; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Access-Control-Allow-Origin: *
Server: kong/0.9.9
{"token_type":"bearer","id":"edaa469e-57e9-4677-a44d-759635f3fe93","expires_in":3600,"credential_id":"dd141531-04bb-48c6-8920-1fd7ee2e9e10","created_at":1487865729000,"access_token":"5a2782be7dfd439482e0ca039afccfad"}
Question
To generate an OAuth2 token for a consumer, should we use /oauth2_tokens path ?
This path is not reserve for migrating access tokens?
Additional Details & Logs

Kong version: 0.9.9
Operating System: Ubuntu

These are the endpoints using for requesting a new authorization code/token https://getkong.org/plugins/oauth2-authentication/#endpoints

Looks the endpoints are not working for me
/oauth2/token
it returns  the follows:
{
"message": "Not found"
}
what is going on here?

You need to consume those endpoints on top of the API that you are targeting.
ie: if you have an API on Kong that maps to a specific "request_path" or "uris", for example, /test, then the endpoints will be available at /test/oauth2/token.
If instead you are using a Host header to map your APIs, you will have to pass the appropriate Host header value to trigger the specific API you are targeting while requesting /oauth2/token.

Thanks @thefosk
After I added Host header, the response changes somewhat.
But still it returns the following error message. What can I do?
{
"error": "unsupported_grant_type",
"error_description": "Invalid grant_type"
}

You need to pass a valid grant_type parameter, as per OAuth 2.0 specification.

This discussion for this is at #2219, considering this as answered :)


Run on e2-standard-8

Description of your changes
Changes runs-on from [e2-standard-8, linux] to e2-standard-8
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

Could you also update this one? https://github.com/upbound/official-providers-ci/blob/main/.github/workflows/pr-comment-trigger.yml#L45

and this one https://github.com/upbound/official-providers-ci/blob/main/.github/workflows/pr-comment-trigger.yml#L115 :)


Remove files built by webpack

This PR updates the .gitignore to ignore the main.js file that is built by Webpack.  Typically any scripts built by module loaders or task runners are ignored, as they can be created on the fly by developers.

IMO keeping the compiled file is a good idea so people can start the repo immediately without building anything. The behavior that I'm trying to get is "npm install and npm start are sufficient to run everything" (although admittedly I haven't added the start script yet...)

Fair enough @vkarpov15, this just means that you will have to ensure you build this file on every change and subsequent commit.

Yeah I'm not a huge fan of that TBH, but I also like to honor the contract that npm install + npm start is sufficient to be able to go to localhost:4000 and see a working site. What would you think about putting webpack in a postinstall or prestart script?


Remove check for 'difficult' attribute in Pascal VOC

Summary

Remove check for 'difficult' attribute in Pascal VOC
How to test

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

@zhiltsov-max , do you think we need to do this for all attributes?

Yes, but I'd also consider changing AC code, or adding an option to convert in "compressed" mode.


linux: Switch to schedutil governor

Motivation for this change
Since 4.9, the Linux kernel has included the "schedutil" CPU governor (in its current implementation):  https://cateee.net/lkddb/web-lkddb/CPU_FREQ_GOV_SCHEDUTIL.html
This governor adjusts the CPU frequency based on utilization data provided by the scheduler.
Switching to this governor should allow for energy-savings while still making "high-performance" possible.
Closes #41003
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Add these to my config:
boot.kernelParams = [ "intel_pstate=passive" ];
powerManagement.cpuFreqGovernor = "schedutil";

λ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
schedutil
λ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
performance schedutil
λ systemctl status cpufreq.service
● cpufreq.service - CPU Frequency Governor Setup
   Loaded: loaded (/nix/store/lzk05z7a3l0gslpsbrmh8qcacmvzw65x-unit-cpufreq.service/cpufreq.service; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2018-06-21 10:30:01 EDT; 35min ago
  Process: 838 ExecStart=/nix/store/c1zaswjv476fyxdkl78yr6816wnp9qrb-cpupower-4.16.16/bin/cpupower frequency-set -g schedutil (code=exited, status=0/SUCCESS)
 Main PID: 838 (code=exited, status=0/SUCCESS)

Jun 21 10:30:01 nixus-desktop systemd[1]: Starting CPU Frequency Governor Setup...
Jun 21 10:30:01 nixus-desktop cpupower[838]: Setting cpu: 0
Jun 21 10:30:01 nixus-desktop cpupower[838]: Setting cpu: 1
Jun 21 10:30:01 nixus-desktop cpupower[838]: Setting cpu: 2
Jun 21 10:30:01 nixus-desktop cpupower[838]: Setting cpu: 3
Jun 21 10:30:01 nixus-desktop cpupower[838]: Setting cpu: 4
Jun 21 10:30:01 nixus-desktop cpupower[838]: Setting cpu: 5
Jun 21 10:30:01 nixus-desktop cpupower[838]: Setting cpu: 6
Jun 21 10:30:01 nixus-desktop cpupower[838]: Setting cpu: 7
Jun 21 10:30:01 nixus-desktop systemd[1]: Started CPU Frequency Governor Setup.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: linux
Partial log (click to expand)
while evaluating the attribute 'linux_4_14' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/top-level/all-packages.nix:13599:3:
while evaluating 'callPackageWith' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:113:35, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/top-level/all-packages.nix:13599:16:
while evaluating 'makeOverridable' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:72:24, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:117:8:
while evaluating anonymous function at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/os-specific/linux/kernel/linux-4.14.nix:1:1, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:74:12:
while evaluating 'buildLinux' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/top-level/all-packages.nix:13914:16, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/os-specific/linux/kernel/linux-4.14.nix:5:1:
while evaluating 'callPackageWith' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:113:35, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/top-level/all-packages.nix:13914:23:
while evaluating 'makeOverridable' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:72:24, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:117:8:
while evaluating anonymous function at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/os-specific/linux/kernel/generic.nix:1:1, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:74:12:
assertion failed at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/os-specific/linux/kernel/generic.nix:48:1

Success on aarch64-linux (full log)
Attempted: linux
Partial log (click to expand)
wrong ELF type
wrong ELF type
wrong ELF type
wrong ELF type
wrong ELF type
wrong ELF type
wrong ELF type
wrong ELF type
cannot find section .dynamic
/nix/store/x1v2mnr78smxfiw3dhkm4nccr0z5r8fh-linux-4.14.51

Failure on x86_64-linux (full log)
Attempted: linux
Partial log (click to expand)
  CC [M]  drivers/usb/host/isp1362-hcd.o
  CC [M]  drivers/staging/lustre/lustre/llite/vvp_dev.o
  CC [M]  drivers/staging/lustre/lustre/lmv/lmv_intent.o
  CC [M]  drivers/scsi/esp_scsi.o
  CC [M]  drivers/usb/host/ohci-hcd.o
  CC [M]  drivers/staging/lustre/lustre/llite/vvp_page.o
  CC [M]  drivers/staging/lustre/lustre/lmv/lmv_fld.o
  CC [M]  drivers/scsi/am53c974.o
building of '/nix/store/vsiillchn2k6di0nnrwaazp226pg2pw9-linux-4.14.51.drv' timed out after 1800 seconds
error: build of '/nix/store/vsiillchn2k6di0nnrwaazp226pg2pw9-linux-4.14.51.drv' failed

If this is a fairly new scheduler, is it a good idea to make it the default? What do the kernel developers recommend? What do other distributions do?

I only checked with Arch and Ubuntu, and they both use schedutil as the default.

It's good to build schedutil (probably as a module, like other governors), but it is not an alternative to performance and should not replace it. The default built into the kernel does not matter on NixOS anyway because nixos-generate-config configures powerManagement.cpuFreqGovernor that overrides it, currently to ondemand or powersave; and this list may be changed to prefer schedutil. Note that the unset powerManagement.cpuFreqGovernor is documented to mean performance.

It's good to build schedutil (probably as a module, like other governors), [...]

Note: As I understand it now, on recent kernel versions schedutil can no longer be built as a module.

As mentioned above, schedutil cannot be built as a module.
Not sure how we should proceed with this. Any suggestions?
Set CPU_FREQ_GOV_SCHEDUTIL but not CPU_FREQ_DEFAULT_GOV_SCHEDUTIL (if that is valid)?

For now, let's enable schedutil but not make it the default, and review the default for 19.03 after people have used it for a while.

Right, e6a37e3ce4e.  We can continue the discussion about the default, though that might be better after several months (I don't really know, I haven't researched pros and cons).

Can we close this?

enabling schedutil is solved by e6a37e3
setting it as the default as it is done in this PR is not effective
setting it as the default should be a separate PR
Thanks!


AMEL-20281 - Camel-AWS Components: Make it possible to use AwsSessionCredentials to support temporary credentials - AWS Config

Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

/component-test aws


How do i localize the message in the event when rest API return 409 conflct

Hi - I am trying to show the message by leveraging 409 http status code. Can you tell me how can i localize it? In order for me to localize i need to pass ui_locales to rest api so that it can return the message accordingly. Is there any way to pass ui_locales to rest api.

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

ID: af62e857-35e1-498d-5a8f-49fe9c15ca9c
Version Independent ID: 40e1240b-e79e-f6e8-28c9-c61731fa64cf
Content: Integrate REST API claim exchanges in your Azure Active Directory B2C user journey
Content Source: articles/active-directory-b2c/active-directory-b2c-custom-rest-api-netfw.md
Service: active-directory
Sub-service: b2c
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@rupeshprasad
Thanks for the feedback! We are currently investigating and will update you shortly.

@rupeshprasad I do not think that is possible now but I will check internally with the product team and let you know.

Thanks for the feedback, we'll update the document soon. Meanwhile see the guidance. To customize the 409 error message coming from the REST API, you need to send the current language ID to the REST API. The REST API reads this parameter and returns an error message related to the current language.
Create a claim type lang
<ClaimType Id="lang">
  <DisplayName>Language name</DisplayName>
  <DataType>string</DataType>
  <AdminHelpText>Add help text here</AdminHelpText>
</ClaimType>

In the REST API technical profile add an the lang claim type as an input claim, and set the default value to one of the culture claims resolver.
<InputClaims>
  <InputClaim ClaimTypeReferenceId="lang" DefaultValue="{Culture:LanguageName}" AlwaysUseDefaultValue="true"/>
</InputClaims>

Thanks

@yoelhor I used your code, but claims resolver always returns same value regardless user's language evenif user changes language setting on browser.
<InputClaim ClaimTypeReferenceId="lang" DefaultValue="{Culture:LanguageName}"   "AlwaysUseDefaultValue="true"/>
Please let me know how can I get actual user's language setting in custom policies.


CMake + Ccache: two popular approaches

In spirit of this stackoverflow question, I want to raise awareness about how Ccache is activated in openvdb:
There seem to be two approaches, with only a slight tendency to the second one (CMAKE_*_COMPILER_LAUNCHER).
You can select it per language, leave users the freedom to overwrite it with ENV variables and change it per directory + target.
This book also recommends the second one.
If you have a parent project using this second approach, for some reason you end up with nested ccache ccache calls (which fail).
My current workaround is to set(USE_CCACHE OFF) for openvdb to avoid the recursive calls. But it would be cleaner to have openvdb also use the compatible approach. I can prepare a PR after a discussion, but it should be only changing:
https://github.com/AcademySoftwareFoundation/openvdb/blob/5ecc250302807c3854e05f1f6a0ea6bf7daf29bb/CMakeLists.txt#L404-L405

Why not use
export CC=/usr/lib/ccache/clang-12
export CXX=/usr/lib/ccache/clang++-12

I don't see a reason why the built system should handle the usage of ccache at all. Of course you can also use the CMAKE_*_COMPILER_LAUNCHER approach, but does this require having ccache in the CMake script at all?

If I would need to guess, I'd say the reason CMake is involved, is convenience. You want to give new developers / users the chance to use ccache, but not enforce it. For experienced ccache users like you, of course you can use the manual injection-from-the-outside method.
To my knowledge, the whole reason cmake implemented these CMAKE_*_COMPILER_LAUNCHER variables is caches like ccache.  It probably exists to reduce the manual labour setting up the environment around a project.
In the end I don't want to discuss WHY it is there, but HOW. Thanks for pointing out yet another option.
As for your question, you can also seed this variable from an environment variable, without support of the cmake script. Again, it's convenience why you let cmake look for ccache automatically and enable it when found.

But you can use CMAKE_*_COMPILER_LAUNCHER without having them in the CMake script.