Tests failed in cosmogony run

Hi, I hope you're all doing well!
I have tried building and launching my own Cosmogony, because I have my own genre of this project(https://mappumappu.000webhostapp.com/index.html), albeit on a smaller scale  so it really picked my interest!
But when I try to do a full flow of the cosmogony process
(1 - Fetch an ...osm.pbf from Geofabrik;
2 - Build a .json with the Cosmogony project;
3 - try to run Cosmogony Explorer with the .json.)
I get an error in the tests assertion part. I have tried with the Portugal-latest and Poland-latest osm.pbf files. It does, however, build the Explorer with the files already in the Cosmogony project(for example the luxembourg_filtered.osm.pbf in the cosmogony\tests\data folder), although it shows nothing besides the UI of the explorer(don't know if that's the expected behaviour). Do I need to add the .osm.pbf file to the ../tests/data so it knows what to expect?
I don't know what I can do to fix it so all help would be appreciated.
P.S.: There are two images attached, the first with the result of cosmogony json build and the second with more info of the error.
Also, the commands I'm running are:
cargo run --release -- generate -i portugal.osm.pbf
PATH_TO_COSMOGONY_DIR=../cosmogony_data pipenv run inv -e run-local --cosmogony-file-name=cosmogony_Portugal.json --build-dockers
(cosmogony build)

(error in Docker run)

This issue has been addressed in the cosmogony-explorer, where I originally opened it, so it's fixed!


Google Data APIs are deprecated

The Google Data APIs that this script is based on was deprecated May 15, 2013 (https://developers.google.com/google-apps/provisioning/)
According to the deprecation policy (https://developers.google.com/google-apps/admin-api-terms), the service might not be operated after April 20, 2015.
The solution is to port to the Admin SDK API.
Please assign to me, I'm working on the port. I will do it in two parts:

Abstract out calls to the APIs, so we have a clean separation between our program logic and the API calls. Unfortunately, the APIs use different property names for some things.

Rewrite to use the Admin SDK API. An incomplete PoC is in the google-api branch on my fork of this repo.

@trevore I'd like you to start thinking about a possible problem with the fix for this.
The OAuth2 APIs need a client key, which is defined in a client_secrets.json file. I don't want to check the client_secrets.json file into the (public) repository. I'm thinking that we can save the file in Google Drive for our domain, and let that be visible for all domain members. If a potential user in our domain is not part of the Apps domain, then we can manually give it to them.
For completeness, we would document how to create the client_secrets.json file for anyone else who wants to use this code.
Also note that I'm currently doing the port in the new-google-api branch on cjs/galias


sprockets-rails v3 support

Asset precompilation and asset dependency behavior is going to change in sprockets-rails v3.
See https://github.com/rails/sprockets-rails/issues/191
Opening this as a placeholder and reminder for when that's all hashed out.
This dependency will be required for future Rails v5 support

Any news on this, since sprockets-rails v3 is out?

Sorry, no news. It would be super awesome if someone had the time to investigate this further.

@rmm5t the issue you link to is closed. Does that resolve it all? Because this issue is blocking https://github.com/bokmann/font-awesome-rails/pull/159.

the issue you link to is closed. Does that resolve it all? Because this issue is blocking #159.

@why-el Unfortunately, no. If you look at the Travis-CI build, we're still failing against the rails master branch. However, I think our current problem might be with changes in the latest sass-rails.

Yes, sass-rails is pushing for the latest Sprockets. Perhaps you can fix sass-rails to the version still using Sprockets v3?

Perhaps you can fix sass-rails to the version still using Sprockets v3?

Perhaps, but heavily restricting dependencies like that increases the likelihood of dependency hell for everyone later. Plus, I'd like to maintain complete backwards compatibility with all currently supported Rails versions (e.g. 4.2). To many gemspec version restrictions makes that more difficult.

With all that said, pull-requests that keep the current build green and pass against rails master are very, very much welcome. I spent a rushed ~20 minutes on this problem a couple weeks ago, but didn't get to a full resolution.

Yes, completely agree. Would a <= v3 do it? I guess that satisfies the backward compatibility requirement and solves this issue. I can either leave a note in https://github.com/bokmann/font-awesome-rails/pull/159 for this or submit a PR that has both https://github.com/bokmann/font-awesome-rails/pull/159 and my change to fix this issue.

Would a <= v3 do it? I guess that satisfies the backward compatibility requirement and solves this issue. I can either leave a note in #159 for this or submit a PR that has both #159 and my change to fix this issue.

I think we're talking more along the lines of a sprockets restriction like < 4.0.
Also, just to clarify, a PR only helps if time is also spent in going through and making sure that everything runs green against all the gemfile permutations (specified in .travis.yml and gemfiles/*.gemfile). If it's just a version lock against sprockets, great, but that needs to be verified.

Actually, I just relaxed the versions in the rails-master.gemfile, and I have a passing build there now.  Sanity checking. Might be able to get this sooner than expected.

Closed by 100f9d76ac7c5f6d48256f61e8f8357b528726c1

@why-el Thanks for the nudge. I think we're good now. I'll get a new release out once all automated builds verify as green.

Fabulous, thank you for the prompt response.
On Tuesday, February 9, 2016, Ryan McGeary<EMAIL_ADDRESS>wrote:

@why-el https://github.com/why-el Thanks for the nudge. I think we're
good now. I'll get a new release out once all automated builds verify as
green.
—
Reply to this email directly or view it on GitHub
https://github.com/bokmann/font-awesome-rails/issues/125#issuecomment-182086296
.

--
Wael Khobalatte

v<IP_ADDRESS> is now on rubygems


run test-tidy --self-test

fixes https://github.com/servo/saltfs/issues/318

This change is

Do we still need the previous run of ./mach test-tidy?

Yes; that's performing the actual tidy checks over the real source files. This new run is just testing that the tidy checks are actually catching errors as expected.

Gotcha; I thought self-tidy meant running tidy against itself. @bors-servo r+

:pushpin: Commit fc4c0b3 has been approved by aneeshusa

:hourglass: Testing commit fc4c0b3 with merge 1b791b4...

:sunny: Test successful - travis


[Mention The Feature]: Navbar is not aligned properly and chatbot is not working

Is your feature request related to a problem? Please describe.
Here's an expanded version of the issue:

Navbar Alignment Issue: The navigation bar's alignment is incorrect, particularly when viewed on expanded or larger screen sizes. Elements in the navbar appear misaligned and shift out of place. The issue is related to the CSS or layout structure.
Adjustments are needed to ensure proper alignment.
Chatbot Malfunction: The website's chatbot feature is currently not functioning. It does not respond to user queries or engage in any interaction, even when prompted. This issue affects the overall user experience, as the chatbot is designed to assist visitors with navigation and provide information.
Here's the screenshot of it:

Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

@TanyaaSrivastava sure go ahead
Make sure to join the discord server for further communication
Don't forget to star the repository
Complete the task in next 2 days and kindly mention your issue # in your pr like this:
Closes #IssueNumber
Note: the level of the issue may change based on the quality of the PR cod

Kindly assign it to me.

@Vanshika-OFFICIAL please stop spamming in other peoples issue otherwise i will block you from contributing in this repo

@Vanshika-OFFICIAL you can create a new issue

@aditya-bhaumik Thank you for assigning.
I'm starting to work on it and update you soon.

Its been a week and no pull request was made so we are closing this issue.


Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'axis')

Not happening with npm run autobuild but is with npm run build  when I deploy my code, I'm getting this

And the chart isn't rendering
For a dataset that looks like this

And a svelte config like

    {#if loaded}
    <Bar {data} options={{ responsive: true  }}/>
    {/if}

So it took two steps:

delete the rollup uglify plugin
Add scales in the options

    {#if loaded}
    <Bar {data} options={{ responsive: true,legend: {
        display: true, position:'top'
      },
      scales: {
        x: {
          type: 'category'
        },
        y: {
          type: 'linear',
          labels:['website text', 'imgae text', 'document text']

        }
      } }}

But now it's rendering two y-axis ?

@LKing12 Hi. Could you please fork this sandbox and reproduce the issue?

@LKing12 Hi. Could you please fork this sandbox and reproduce the issue?

Same issue, we are developing the same app (using Rollup). I have sandboxed the snippet within the app. These are the results:
Using npm run build

Using npm run autobuild

@Zedespook @LKing12 What version of svelte-chartjs are you using?

In our package.json we specified "svelte-chartjs": "^2.1.1".

@Zedespook Please try v3

Installed svelte-chartjs 3.0.1. Unfortunately, this provides the same results.

@Zedespook Could you please provide minimal repo with reproduction?

@Zedespook Could you please provide minimal repo with reproduction?

Here you go, I made this sandbox. In the sandbox itself, nothing will show. You will have to download it, and you can re-create the issue by the following steps:

Terminal 1: npm install
Terminal 1: npm run build
Open another terminal to serve the page
Terminal 2: cd public
Terminal 2: npx serve (install it, or use your favorite server)
Open localhost:5000 (or whatever port you use)
There is no chart

Now when we talked about the npm run autobuild having the chart fully functional, I can show you what we mean:

Go back to Terminal 1
npm run autobuild
Open/refresh localhost:5000
The chart should appear

The problem here is that if we would like to use this in production, we would have to deal with this bug, and autobuild is just not ideal in production.
Let me know if you figured something out.

@Zedespook
      terser({
        // mangle: { properties: { regex: /^_/ } },
        output: { comments: false }
      })

it is unsafe to mangle properties, so just disable this option and all will work perfectly

That indeed works on build thanks!


Minor updates to address a few issues

Proposed changes
Closes #534
Closes #529

I'm not sure what is going on with the isort here.. I didn't do anything ... seems like there is some discrepancy happening in the implementation side.


Angular 7 virtual scroll

Hey there after years! I know commafeed still uses Angular 1 and migrating to Angular 2 is not trivial but personally were interested to know what virtual scroll of angular 7 can offer to commafeed (memory and UX wise) and maybe a motivation to upgrade Angular version.
Thanks!

Hey! Long time no see :)
I'd love to upgrade the UI to something more modern, Angular 2+ is a really good candidate too.
It'd be a good time to change the dated look & feel of the app.
It's a huge amount of work though, I don't know when I'll have the time to learn and use the new framework.

I've started playing with TypeScript and React here https://github.com/Athou/commafeed-ui/
It's just a sandbox/prototype for now, I can't guarantee it'll ever replace the existing UI :)

That is just great! I like React also, let me if I can help you also :)

I've heard https://material-ui.com/ is pretty popular, maybe worth to see and integrate.


Add Additional Forecasting Evaluation Functions/Classes

Sktime's forecasting performance metrics currently only cover a limited number of metrics discussed in the forecasting literature.
I propose to add the metrics discussed in: Another look at measures of forecast accuracy, which has a nice discussion of different metrics for evaluating forecast accuracy.
I also propose adding root mean squared scaled error, which is related to MASE and the forecast metric used in the M5 Competition
Beyond these performance metrics the availability of an asymmetric forecasting loss function is useful when forecasting errors in one direction have a higher cost than those in another direction.  I propose adding an asymmetric error function too.
In addition to these changes, I also propose two changes to make Sktime's performance metrics more compatible with Scikit-learn:

Scikit-learn adapted many (all?) of its regression metrics to handle multioutput regression problems. I propose providing this functionality for each of the forecasting metrics in the above resources so that compatability with Scikit-learn's metrics is maintained and so that the functionality exists if future multivariate forecasting functionality is added.
Scikit-learn's metrics write out the full name (e.g. mean_absolute_error) and I propose updating Sktime's forecasting performance metrics to do the same

The end result would be the following performance metric functions (each with a corresponding class version for scoring):

relative_error
mean_asymmetric_error
mean_absolute_scaled_error
median_absolute_scaled_error
root_mean_squared_scaled_error
mean_absolute_error
mean_squared_error
root_mean_squared_error
median_absolute_error
median_squared_error
root_median_squared_error
symmetric_mean_absolute_percentage_error
symmetric_median_absolute_percentage_error
mean_absolute_percentage_error
median_absolute_percentage_error
mean_squared_percentage_error
median_squared_percentage_error
root_mean_squared_percentage_error
root_median_squared_percentage_error
mean_relative_absolute_error
median_relative_absolute_error
geometric_mean_relative_absolute_error
geometric_mean_relative_squared_error

I've already started work on this and will start a draft pull request soon.

Thanks @RNKuhns - this looks great! Let's reuse as much of scikit-learn's functionality as possible.

This is also related to https://github.com/alan-turing-institute/sktime/issues/352


REPGRANT-109 - renamed question

changed a question on printFinalPage to {PrintCertifiedCopies} to show where that data goes onto the P2

Due to the merge conflicts, the changes have been manually incorporated and will be included in future PRs.


Can't upgrade nor reinstall via brew cask

brew cask install fails.
❯❯❯ brew cask upgrade clipy                                                                                ✘ 1
Updating Homebrew...
Warning: Calling brew cask upgrade is deprecated! Use brew upgrade [--cask] instead.
==> Upgrading 1 outdated package:
Warning: Unexpected method 'license' called on Cask clipy.
Follow the instructions here:
  https://github.com/Homebrew/homebrew-cask#reporting-bugs
Error: Cask 'clipy' definition is invalid: invalid 'depends_on macos' value: unknown or unsupported macOS version: :mavericks

The issue was sorted:

open /usr/local/Caskroom/clipy/.metadata/1.1.0/20161229095355.375/Casks/clipy.rb
remove the line "depends_on macos: '>= :mavericks'"
then, upgrade works.


As a user, I would like more flexibility in NPSP Lead Convert, to specify an existing or new Account

thread on the hub: https://powerofus.force.com/0D58000001hrBkL

Story deleted from ScrumDo


--filter-trace-tc option doesn't work with Cilium

Hi, I’m running the pwru in the k8s server which running the cilium 1.11 version.
everything works well but failed to start when I enabled the filter-trace-tc options, it showed the following error.
Failed to load objects: Verifier error: load program: invalid argument
func#0 @0
func#1 @37
func#2 @859
func#3 @1044
Subprog __send_drop_notify doesn't exist
Program fentry_tc: load program: invalid argument: Subprog __send_drop_notify doesn't exist (5 line(s) omitted

As I know, the _send_drop_notify is the function defined in the cilium code base and I don’t know how to fix it to ensure I can run the filter-trace-tc option with pwru in my server, any clue or options I can check?
Environment:
OS: Ubuntu 20.04
Kernel: <IP_ADDRESS>
pwru: master branch(2024/02/01).

@hwchiu Thanks for the issue! Have you tried running with more recent Cilium version?

Encountered the same issue on cilium 1.11.5, kernel 5.6

I just ran into this as well with an ebpf program I wrote.
I compiled it with clang and embedded the btf information.
Clearly the subprog in question exists.
What kind of extra info would be needed to investigate this? I can try to reduce my program to the minimal repro case.

What kind of extra info would be needed to investigate this? I can try to reduce my program to the minimal repro case.

Which kernel and what Cilium vsn, what distro and how do you run K8s?

The PR #383 fixes this issue.
This issue will happen when the very first function name in BTF info is out of the traced bpf prog.
I reproduce this case, and fix it by PR #383 .
2024/06/12 11:25:26 Failed to run xdump: failed to create filter: failed to trace tc progs: failed to trace tc progs: failed to trace prog(39230): failed to load objects: Verifier error: load program: invalid argument:
	func#0 @0
	func#1 @293
	func#2 @350
	Subprog phy_on_ingress doesn't exist
	processed 0 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0

program fentry_tc: load program: invalid argument: Subprog phy_on_ingress doesn't exist (4 line(s) omitted)

The PR mentioned above has been merged.


QueryFailedError: SQLITE_READONLY: attempt to write a readonly database

Hi all,
Firstly this tool is very very cool - just want to mention that.
However, I launch it in my terminal using npx flowise start. This works correctly, then I set up the following flow:

Once that's done, I am trying to setup a credential for my model to Azure AI studio ( the interface has been updated a bit since the docs were created, but done what I can)
I've used the openAI key as my API key, the instance name as gpt-4, the deployment name as my deployment name as shown in Azure AI studio and finally the relevant version of gpt-4, 1106-preview as the version.
However, I get the following error in my terminal when I press 'add':
QueryFailedError: SQLITE_READONLY: attempt to write a readonly database
Am I missing a step, or is this a bug? I'm not sure if the config should be slightly different since the UI in the docs has since been updated from Azure.
Also noticing that when I had {input} as my text prompt, I get the same error in my terminal.
Not sure if anyone else has seen this, would be great to know more on how I can fix this.
Thanks in advance!

Hi @r-pathak, which platform are you running Flowise on Mac/Win/Linux?

Ah yeah, ofc I forgot to mention - running on Mac. Although once I'm done testing locally will likely deploy as an Azure app service on Linux

Flowise automatically create a SQLite database stored in user home directory /.flowise, you need to grant write access to that with sudo chown -R "$USER":"$USER" /path/to/my-folder

what to do if I am on WIndows?


local machine - security information leak

By using curl to push the data to the splunk server, the spunk auth ids can be viewed by observing the process table.
For example, run: ps -ax when the call occurs.

Since we are already requiring WWW:Mechanize for the APC scraper, consider using this instead of Curl to submit the data to Splunk.

Updated as specified in comment.


Plans to support Elasticsearch >= 5.0?

Elasticsearch 5.0 has been released and this plugin has not yet been updated to support the new version. Are there plans to support future versions of ES?
My findings so far
I attempted to edit build.gradle, gradle.properties, and plugin-descriptor.properties to reflect my current version of Elasticsearch (5.0.2) and build the plugin myself using gradle plugin.
When I do this, there are many instances of Elasticsearch-specific classes not being found. In particular, these statements seem to cause problems
import org.elasticsearch.common.logging.ESLogger;
import org.elasticsearch.index.mapper.MappedFieldType.Names;
import static org.elasticsearch.index.mapper.MapperBuilders.binaryField;
import static org.elasticsearch.index.mapper.MapperBuilders.stringField;
import org.elasticsearch.index.query.BoostableQueryBuilder;
import org.elasticsearch.index.query.QueryParsingException;

Note: these statements are all in different files and do not appear one right after another in the actual code.
These seem to be actual issues stemming from the differences between 2.4 and 5.0. I've confirmed that MapperBuilders is a file that existed in 2.4 but was removed in 5.0.

5.0 ia not compatible with 2.x, basically it need to completely rewrite, it
is difficulty to just do it because lack of plugin documentation.
Yes , I ams plan to support 5.0, some how I am quite busy recently, no time
to work on this (and  also due to my poor knowledge).
On Dec 3, 2016 12:17 AM, "Nick Stanisha"<EMAIL_ADDRESS>wrote:

Elasticsearch 5.0 https://www.elastic.co/v5 has been released and this
plugin has not yet been updated to support the new version. Are there plans
to support future versions of ES?
My findings so far
I attempted to edit build.gradle, gradle.properties, and
plugin-descriptor.properties to reflect my current version of
Elasticsearch (5.0.2) and build the plugin myself using gradle plugin.
When I do this, there are many instances of Elasticsearch-specific classes
not being found. In particular, these statements seem to cause problems
import org.elasticsearch.common.logging.ESLogger;import org.elasticsearch.index.mapper.MappedFieldType.Names;import static org.elasticsearch.index.mapper.MapperBuilders.binaryField;import static org.elasticsearch.index.mapper.MapperBuilders.stringField;import org.elasticsearch.index.query.BoostableQueryBuilder;import org.elasticsearch.index.query.QueryParsingException;
Note: these statements are all in different files and do not appear one
right after another in the actual code.
These seem to be actual issues stemming from the differences between 2.4
and 5.0. I've confirmed that MapperBuilders is a file that existed in 2.4
https://github.com/elastic/elasticsearch/blob/2.4/core/src/main/java/org/elasticsearch/index/mapper/MapperBuilders.java
but was removed in 5.0
https://github.com/elastic/elasticsearch/tree/5.1/core/src/main/java/org/elasticsearch/index/mapper
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kiwionly/elasticsearch-image/issues/20, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAKqGRdRhBds-Zo4SFMUBoO2ZDSIAhn5ks5rEESKgaJpZM4LCuIG
.

heres to hoping that you find time to update it :)


Logout route added, Secret string changed

This is a new pull after cloning develop branch, removing conflicts, adding log out route and creating env for super secret string.

So shall I close this pull request and make another one from develop branch @twishasaraiya

Yes @sounak07.


Pin python version to 3.11

Changes

Pin python version to 3.11

@upodroid PTAL, we have noticed that GH runners may vary on Ubuntu version. Spanning between 24 and 22 LTS release, the culprit is that Ubuntu 22 has default Python 3.10 that doesn't have --break-system-package yet. For our limited use case it seems like a good enough to pin the version. WDYT?
https://github.com/actions/runner-images/blob/ubuntu22/20241006.1/images/ubuntu/Ubuntu2204-Readme.md#language-and-runtime
FYI, per our chat earlier.
/cc @ReToCode @skonto

/cc @upodroid


Issue 207 The "Test Id Attribute Name" project setting is not being picked up when executing tests as Typescript

#219 207

#219


New boards

Enabling sam architecture.
Boards enabled :
Arduino Due board (native/edbg), Arduino Leonardo, Arduino Leonardo Ethernet 2, Arduino Micro, Arduino Esplora, Arduino Robot, LilyPad, Arduino Mega 2560, Arduino Mega ADK, Arduino Leonardo XS, Arduino M0s and Arduino Uno XS

wrong variant file for leo-xs


Typo fixed

Fixed a typo in example description

Docs Build status updates of commit 54944fd:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

.openpublishing.publish.config.json
:x:Error

Details

Line 117: [Error] Restore nuget package W:\1b0p-s\.optemp\dependentPackages\opbuild.templates.azurecli\packages.config in folder:W:\1b0p-s\.optemp\packages failed, possibly due to transient errors from nuget servers. Please retry building your content. If the issue still happens, open a ticket in http://SiteHelp and include the build report and the following error message for our team to troubleshoot:  Errors in packages.config projects     Unable to find version '1.67.3' of package 'opbuild.templates.azurecli'.       D:\Windows\system32\config\systemprofile\.nuget\packages\: Package 'opbuild.templates.azurecli.1.67.3' is not found on source 'D:\Windows\system32\config\systemprofile\.nuget\packages\'.       https://www.myget.org/F/op/api/v2: Package 'opbuild.templates.azurecli.1.67.3' is not found on source 'https://www.myget.org/F/op/api/v2'.

.openpublishing.publish.config.json

Line 290: [Error] Restore of dependent packages failed. Please check your .openpublishing.publish.config.json?on the configuration of the dependent packages or ask for help?in Docs Support teams channel. Please also include the following error code for our team to troubleshoot: 1

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


use selectedState instead of isSelected for deselect all files if one row is selected

[ ] I have tested my component
[ ] I have updated the documentation or there is no documentation needed

Libraries that use the DS (need to merge first)

[ ] BCF Components
[ ] BIMData Components
[ ] Building maker

Repos that use the DS (and that I need to check after libraries have been merged)

[ ] Viewer
[ ] Platform
[ ] SDK
[ ] Marketplace
[ ] Documentation

Très propre. :+1:

Très smart d'y avoir pensé (presque) toute seule. :+1:

:tada: This PR is included in version 2.1.0-rc.29 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Vue 3 support?

Hi,
can you add a support for VUE 3?
Thank you in advance.

+1

Made some progress on next branch.
It is not easy upgrade :)

+1 Hopefully it works for Vue 3

+1 would like to use it, instead of having to build something myself

+1 Especially since there seems no alternative for Vue 3 (not even a simple spinner).

I have significant progress on next branch. :rocket:
You can expect a beta version soon.
Next todo

[ ] Update readme, usage guide
[ ] Add upgrade guide
[ ] Update test case
[ ] Update type defs
[ ] Manual testing
[ ] Upgrade to Webpack 5

Thanks for your patience.

You can try the latest beta now
yarn add<EMAIL_ADDRESS>
Check next branch for docs

Rocket speed

@ankurk91  does support Composition API Vuejs 3?

@zeyadsharo
Undocumented yes
https://github.com/ankurk91/vue-loading-overlay/blob/master/src/js/api.js#L4


Fixed some more typos

I tried to ignore UK English, but it was killing me to see Serialized and Serialised next to each other on the same file.

@06b I know for a fact @grumpydev will want you to spell serialized with an s

@albertjan I had a feeling someone was going to say that. I've reverted those commits. I'll make sure to leave UK English alone next time.

This is nice! Thanks, @06b :+1:

@khellang No Problem, Love the work the Nancy Team does and happy to be able to help out even if it's in small ways.


Improvements in conda recipe

Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers.

Thanks @marcelotrevisani  this pr is now merged


Disable story action items that are not usable

For beta we should disable story action items on the context men (vertical three dots) that aren't ready to be interacted with. These are create template and preview. Preview on hover of the story should also be hidden for release to avoid confusion.

@BrittanyIRL "Preview on hover of the story should also be hidden for release to avoid confusion."
Is this hovering over the story cards in the dashboard and seeing your story play?

@samitron7 - just the button that says 'preview' when you hover over a story - since that button doesn't do anything yet.

@o-fernandez Shouldn't you be able to preview your story using the story runtime preview here? It's just seems weird to not allow that.

Eventually yes, but it's not implemented yet, hence hidden. Or do you mean something else?

Agree with @swissspidy if we have that ready to go then it'd be great, but if that's not something we can have implemented now, I'm ok doing it post Beta and hiding the button for now.

To be clear, hiding this button is exactly what this issue is about and has already been implemented and is now awaiting UAT>

@swissspidy Ah ok, I thought it was implemented for some reason since we have it inside the editor.
Verified in UAT


add PatentsviewReader for reading patent abstract

Description
Created a new loader for loading patent abstract given patent numbers.
Refer to README for usage.
Shuai

@EmanuelCampos Thanks!
I've updated __init__.py, should work now.


Does Header really need HeaderRow or HeaderTabs inside?

I'm trying to implement http://www.getmdl.io/templates/dashboard/index.html with the react-mdlmodule.
All of it except the header part of the drawer is possible to do. The top part of the drawer looks like this;
...

<EMAIL_ADDRESS>

    <button id="accbtn" class="mdl-button mdl-js-button mdl-js-ripple-effect mdl-button--icon" data-upgraded=",MaterialButton,MaterialRipple">
      arrow_drop_down
      Accounts

    </button>

    ...stripped...

...

If I try to do this with the  component, it required one of the children to be a <HeaderTabs> or <HeaderRow> or it will just wrap it with a <HeaderRow>.
I would like to avoid that wrapping. Can that be done?

You can put whatever you want inside the Drawer component. So you can add your custom header if you want instead of using the Header component. (Which doesn't seem to be the case in this mdl example anyway).

@tleunen Hey, I've got similar question. I'd like to add a back button to the header:

  <button class="mdl-layout-icon mdl-button mdl-js-button mdl-button--icon">
    arrow_back
  </button>

    Some title

I guess it's not possible with the current Header component? I can always use plain HTML, just asking :)

Everything you put in a  will be wrap inside a HeaderRow, unless it's already a row, or a tab.
So with the current implementation, you cannot achieve exactly the same thing as what you describe, but you can have something quite similar I think using this:
const customTitle =
<IconButton name="arrow_back" /> Some title
;

This works:

  <IconButton name="arrow_back" className="mdl-layout-icon" />
  <HeaderRow title={title}>
    ...
  </HeaderRow>

@tleunen Thanks for this awesome library!


T0: Race condition with misaligned configuration values for archiveDelayHours vs. blockDeletionDelayHours

Impact of the bug
T0
Describe the bug
While working on the issue with disentangling the workflow archival process  and block level deletion for the T0 system we were always having in mind the situation where the archival time would far exceed the block deletion time and  we should never have the opposite situation.
The way how  we are checking for blocks suitable for deletion for the T0 workflows right now is as follows:

We fetch from the dbsbuffer_* tables at the agent all completed blocks together with the names of the workflows producing them [1]
We fetch from wmbs_* tables all deletable workflows (but still in the system) [2]
We make the intersection of those both and all matching blocks we consider suitable for deletion and we proceed with the block level deletion.

This works perfectly fine as  long as block level deletions happen while the workflows are still in the system, so we are capable of making the above two sets and the needed intersection. But once we loose the workflows from the system we have no way to tell which of the blocks left behind were adjacent to a chain of workflows in a completely terminal state (meaning both Parent and Child workflows have reached completed state - e.g. Repack and Promptreco). This may happen if someone by mistake sets archiveDelayHours  to be short enough such that the following becomes true:

(workflow lifetime + archiveDelayHours) <= blockDeletionDelayTime

Here we need to take into account that the clock for keeping the workflow into the system (until archived) starts with the moment of submitting and ends upon exceeding archival delay time, while the clock for we keep the block in the system starts with the moment of creating the block and ends with either the moment of the block being closed or the moment blockDeletionDelayTime expires, which ever comes last. This  misalignment of starting the two clocks  (the one for archivalDalayHours and the one for blockDeletionDelayHours) we knew from the very beginning is something that is not quite comfortable to work with. If we were to have them both started simultaneously with the workflow completion time, this mistake would have been much more difficult to make, but still not impossible. Unfortunately  we had no cheap way to query for the workflow completion time from the agent, so this was a compromise we accepted.
The effect of making this mistake becomes twofold:

We leave orphaned blocks in the system
Those blocks would continue entering the query to dbsbuffer_* tables for fetching the completed blocks, but would never be matched to a set of deletable workflows and would contribute to eventual performance degradation of that query, until cleaned manually.

How to reproduce it
just set the tow configuration variables: {arche,blockDeletion}DelayHours in a way such that the blocks persist in the system beyond the workflows' lifetime + archival delay
Expected behavior
To not allow a workflow still having blocks in the system to get archived.
Additional context and error message
[1]
https://github.com/dmwm/WMCore/blob/d143d0d205050dff23cc699e61d0dcf7af5d912e/src/python/WMComponent/RucioInjector/Database/MySQL/GetCompletedBlocks.py#L25-L53
[2]
https://github.com/dmwm/WMCore/blob/d143d0d205050dff23cc699e61d0dcf7af5d912e/src/python/WMCore/WMBS/MySQL/Workflow/GetDeletableWorkflows.py#L50-L58

FYI: @amaltaro  @klannon @drkovalskyi  @germanfgv @jhonatanamado

Upon two consecutive discussions with @amaltaro we decided to create a new DAO giving a proper map of the sort:
[{"workflow_name": "blah", "num_blocks_deleted": X, "num_blocks_not_deleted": Y}]

And call it GetDeletedBlocksByWorkflow or CountDeletedBlocksByWorkflow
Upon testing many things in vocms0193 , here is the cheapest and shortest sql query that may collect such information I could come up with:
SQL> SELECT
  2     count(*),
  3     dbsbuffer_block.blockname,
  4     dbsbuffer_block.rule_id,
  5     dbsbuffer_block.deleted,
  6     wmbs_workflow.name as workflowname
  7  FROM dbsbuffer_block
  8  INNER JOIN dbsbuffer_file ON
  9     dbsbuffer_file.block_id = dbsbuffer_block.id
 10  INNER JOIN dbsbuffer_workflow ON
 11     dbsbuffer_workflow.id = dbsbuffer_file.workflow
 12  INNER JOIN wmbs_workflow ON
 13     wmbs_workflow.name = dbsbuffer_workflow.name
 14  GROUP BY
 15     dbsbuffer_block.blockname,
 16     dbsbuffer_block.rule_id,
 17     dbsbuffer_block.deleted,
 18     wmbs_workflow.name;

  COUNT(*) BLOCKNAME																		  RULE_ID				      DELETED WORKFLOWNAME
---------- ------------------------------------------------------------------------------------------------------------------------------------------------------ ---------------------------------------- ---------- ------------------------------------------------------------
       114 /RelValProdQCD_Pt_3000_3500_13/CMSSW_8_1_0-ProdQCD_Pt_3000_3500_13_TaskChain_MC_May2022_Val_Alanv15-v11/GEN-SIM#4def6145-0f49-46ad-b15f-7d18c87c3517   42c1755400bb4dee8b05d58d0832b46a		    0 amaltaro_TaskChain_MC_May2022_Val_220520_123841_7232
	19 /RelValProdQCD_Pt_3000_3500_13/CMSSW_8_1_0-RECOPRODUP15_TaskChain_MC_May2022_Val_Alanv15-v11/MINIAODSIM#27d3cbbb-83b0-4162-9498-42ca1bf33c33 	  aab8a0b6dca548aebfc0d1dd25a73d75		    0 amaltaro_TaskChain_MC_May2022_Val_220520_123841_7232
	27 /b_bbar_4l_TuneCP5_13TeV-powheg-pythia8/RunIISummer20UL16wmLHEGENAPV-myTask1_TaskChain_Prod_May2022_Val_Alanv15-v11/GEN#8e2c867b-7117-46ee-911c-582dd2 3ae8ab7cf9bc4c3aadd9f30bac46ee08		    0 amaltaro_TaskChain_Prod_May2022_Val_220520_123843_5700
	28 /RelValQCD_Pt15To7000_Flat_14/Integ_Test-SC_MultiPU_May2022_Val_Alanv15-v11/GEN-SIM-DIGI-RAW#91562e40-86e0-4565-b076-3b193b5ae5a5			  a723ec09ef6a4b2893526530d8fe302f		    0 amaltaro_SC_MultiPU_May2022_Val_220520_123836_4765
	15 /RelValTTbar_14TeV/CMSSW_11_2_0_pre2-RecoPU_2024PU_SC_ReDigi_Harvest_Prod_May2022_Val_Alanv15-v11/MINIAODSIM#f766f0d4-e6d5-4559-85e2-035719c1e63c	  6e04b2e4725a46a79a4df95a499b7715		    0 amaltaro_SC_ReDigi_Harvest_Prod_May2022_Val_220520_123827_55
	18 /RelValQCD_Pt_600_800_14/CMSSW_11_2_0_pre8-RecoPU_2024PU_TaskChain_PUMCRecyc_May2022_Val_Alanv15-v11/DQMIO#c657cac5-845f-45ad-91a2-394061dd8f40	  88772e306ae54ce484bfc8e555ce036e		    0 amaltaro_TaskChain_PUMCRecyc_May2022_Val_220520_123832_7102
	70 /RelValDarkSUSY_14TeV/Integ_Test-SC_LHE_Ext_May2022_Val_Alanv15-v11/GEN-SIM-DIGI-RAW#9f2cf79e-1d15-4822-8a6a-b4fce3e1a71b				  f4438c97080e4ba79901c0e5dea29196		    0 amaltaro_SC_LHE_Ext_May2022_Val_220520_123825_8709
	27 /b_bbar_4l_TuneCP5_13TeV-powheg-pythia8/RunIISummer20UL16MiniAODAPV-myTask6_TaskChain_Prod_May2022_Val_Alanv15-v16/MINIAODSIM#9bfddce8-29f8-43b9-99d9- b944d56789e34e1cb88ce522b73a9b10		    0 amaltaro_TaskChain_Prod_May2022_Val_220520_123843_5700
	19 /RelValProdQCD_Pt_3000_3500_13/CMSSW_8_1_0-RECOPRODUP15_TaskChain_MC_May2022_Val_Alanv15-v11/DQMIO#ab37657a-67f7-4247-8e4e-d52dd57f327c		  e345c1f628dc437dbbff7421559ce36a		    0 amaltaro_TaskChain_MC_May2022_Val_220520_123841_7232
       418 /JetHT/CMSSW_7_2_0-RECODreHLT_TaskChain_LumiMask_multiRun_May2022_Val_Alanv15-v11/RECO#37849a49-4e9c-4edb-822d-9eec483f5e04				  d2521df2cd55460ba861ac6d41dfa526		    0 amaltaro_TaskChain_LumiMask_multiRun_May2022_Val_220520_1238
	14 /RelValProdMinBias/Integ_Test-RECOPROD1_TC_Drop_PhEDEx_Ext_May2022_Val_Alanv15-v11/AODSIM#55caf0e2-7b6c-4bbd-844a-cc5c73672c8a			  4bbab352276640149fc5fa4d4554f02d		    0 amaltaro_TC_Drop_PhEDEx_Ext_May2022_Val_220520_123823_128

  COUNT(*) BLOCKNAME																		  RULE_ID				      DELETED WORKFLOWNAME
---------- ------------------------------------------------------------------------------------------------------------------------------------------------------ ---------------------------------------- ---------- ------------------------------------------------------------
       324 /RelValQCD_Pt_600_800_14/CMSSW_11_2_0_pre8-DigiPU_2024PU_TaskChain_PUMCRecyc_May2022_Val_Alanv15-v11/GEN-SIM-DIGI-RAW#1dea3b5d-cd3c-457f-9be6-d80f58ed d460e45995b94512a2ca90e0b07e69db		    0 amaltaro_TaskChain_PUMCRecyc_May2022_Val_220520_123832_7102
	22 /JetHT/CMSSW_7_2_0-SiStripCalZeroBias-RECODreHLT_TaskChain_LumiMask_multiRun_May2022_Val_Alanv15-v11/ALCARECO#c609310e-df8c-44f3-9f53-57d6a14be03e	  8f547ec63a6b468fadd87130a388fc63		    0 amaltaro_TaskChain_LumiMask_multiRun_May2022_Val_220520_1238
	22 /JetHT/CMSSW_7_2_0-RECODreHLT_TaskChain_LumiMask_multiRun_May2022_Val_Alanv15-v11/DQMIO#5f4850cc-a794-4018-b808-8a1d31a07458 			  33f52db85727414f9e57b46e930bd068		    0 amaltaro_TaskChain_LumiMask_multiRun_May2022_Val_220520_1238
	30 /RelValTTbar_14TeV/CMSSW_11_2_0_pre2-RecoPU_2024PU_SC_ReDigi_Harvest_Prod_May2022_Val_Alanv15-v11/DQMIO#e1509f19-4c7d-4fda-a02d-b9375f8fe2ba 	  a9750d392ec6474f9c9dc312fdd7824c		    0 amaltaro_SC_ReDigi_Harvest_Prod_May2022_Val_220520_123827_55
	15 /RelValTTbar_14TeV/CMSSW_11_2_0_pre3-Nano_2024PU_SC_ReDigi_Harvest_Prod_May2022_Val_Alanv15-v11/NANOAODSIM#20df31f7-b943-4e06-a533-9b3772855ceb	  0af90261b7434e6ca1177b5c7e1dd45d		    0 amaltaro_SC_ReDigi_Harvest_Prod_May2022_Val_220520_123827_55
	44 /JetHT/CMSSW_7_2_0-TkAlMinBias-RECODreHLT_TaskChain_LumiMask_multiRun_May2022_Val_Alanv15-v11/ALCARECO#a504298b-3758-4db2-8dbd-9616b0a1f8fb		  02fde34157504a4d9ef8564c41f6124a		    0 amaltaro_TaskChain_LumiMask_multiRun_May2022_Val_220520_1238
       180 /RelValTTbar_14TeV/CMSSW_11_2_0_pre2-RecoPU_2024PU_SC_ReDigi_Harvest_Prod_May2022_Val_Alanv15-v11/GEN-SIM-RECO#f8bb1ae5-fe97-46d1-85f4-58a6954aa121	  a85e964c4c8b4141a830f56f916e6880		    0 amaltaro_SC_ReDigi_Harvest_Prod_May2022_Val_220520_123827_55
	27 /b_bbar_4l_TuneCP5_13TeV-powheg-pythia8/RunIISummer20UL16wmLHEGENAPV-myTask1_TaskChain_Prod_May2022_Val_Alanv15-v11/LHE#1d79c8ab-0692-458d-9a89-879d58 06a4a6fef38c47f9b12217bcd8720393		    0 amaltaro_TaskChain_Prod_May2022_Val_220520_123843_5700
       108 /b_bbar_4l_TuneCP5_13TeV-powheg-pythia8/RunIISummer20UL16HLTAPV-myTask4_TaskChain_Prod_May2022_Val_Alanv15-v14/GEN-SIM-RAW#a6587b1e-5a8c-4492-8563-89c 67d1be5de6c74b2baa66faa39123d5d5		    0 amaltaro_TaskChain_Prod_May2022_Val_220520_123843_5700
       288 /RelValQCD_Pt_600_800_14/CMSSW_11_2_0_pre8-RecoPU_2024PU_TaskChain_PUMCRecyc_May2022_Val_Alanv15-v11/GEN-SIM-RECO#49a70845-cbbc-49ce-a7bd-b9ad6f0610df e51c702a19ce439abc545dda53f208bc		    0 amaltaro_TaskChain_PUMCRecyc_May2022_Val_220520_123832_7102
	18 /RelValQCD_Pt_600_800_14/CMSSW_11_2_0_pre8-RecoPU_2024PU_TaskChain_PUMCRecyc_May2022_Val_Alanv15-v11/MINIAODSIM#95fad55e-fd4b-4954-b8f5-877504d16b96   92f58c96ff094bf298828d3328a79467		    0 amaltaro_TaskChain_PUMCRecyc_May2022_Val_220520_123832_7102

  COUNT(*) BLOCKNAME																		  RULE_ID				      DELETED WORKFLOWNAME
---------- ------------------------------------------------------------------------------------------------------------------------------------------------------ ---------------------------------------- ---------- ------------------------------------------------------------
	19 /RelValProdQCD_Pt_3000_3500_13/CMSSW_8_1_0-RECOPRODUP15_TaskChain_MC_May2022_Val_Alanv15-v11/AODSIM#a1499d68-aa99-4e43-a2cb-f936095954f7		  0f4a8631460e4a05b6190a8b91555a57		    0 amaltaro_TaskChain_MC_May2022_Val_220520_123841_7232
	14 /RelValProdMinBias/Integ_Test-RECOPROD1_TC_Drop_PhEDEx_Ext_May2022_Val_Alanv15-v11/GEN-SIM-RECO#2301cd7b-e52d-43aa-8c1e-39c6c5a9f190 		  fab536e44603408da1ef4af87a267c20		    0 amaltaro_TC_Drop_PhEDEx_Ext_May2022_Val_220520_123823_128
	21 /RelValDarkSUSY_14TeV/Integ_Test-SC_LHE_Ext_May2022_Val_Alanv15-v11/GEN-SIM#abd1b6fd-3973-415c-8280-81bc1a6c55e9					  d626a20872384ee5a7d1ed11f1809ad9		    0 amaltaro_SC_LHE_Ext_May2022_Val_220520_123825_8709
	 5 /NoBPTX/Integ_Test-ReReco_LumiMask_May2022_Val_Alanv15-v11/NANOAOD#202b476c-56f4-4317-9e7b-fc6434117736						  31339c348e2a43c78c84a4670c9db914		    0 amaltaro_ReReco_LumiMask_May2022_Val_220520_123824_6760
	22 /JetHT/CMSSW_7_2_0-SiStripCalMinBias-RECODreHLT_TaskChain_LumiMask_multiRun_May2022_Val_Alanv15-v11/ALCARECO#af33012b-6489-41ed-8b72-a6a6efdd6a6d	  d7e1fedefcdd42f8bdc5f92ede919259		    0 amaltaro_TaskChain_LumiMask_multiRun_May2022_Val_220520_1238

27 rows selected.

Well it does need some more rearrangement and the rule_Id is there just for testing purposes, but more or less this is the basic idea.


Inconsistent streaming behaviour with ChatGoogleGenerativeAI via callback handlers

Issue Description
I am encountering an issue with the ChatGoogleGenerativeAI model where the responses are not streamed as expected when using callback handlers. The expected behaviour, which I observe with ChatOpenAI and ChatAnthropic, is to receive responses in a chunked format. However, with ChatGoogleGenerativeAI, responses are returned as a whole, which deviates from the expected behaviour.
Using ChatOpenAI for comparison:
const handler = BaseCallbackHandler.fromMethods({
  handleLLMNewToken(token) {
    console.log({ token });
  },
});

const openAIModel = new ChatOpenAI({
  streaming: true,
  callbacks: [handler],
});

openAIModel.invoke('Tell me a joke?').then((res) => console.log(res));
/**
 * { token: '' }
{ token: 'Sure' }
{ token: ',' }
{ token: ' here' }
{ token: "'s" }
{ token: ' a' }
{ token: ' l' }
{ token: 'igh' }
{ token: 'the' }
{ token: 'art' }
{ token: 'ed' }
{ token: ' joke' }
{ token: ' for' }
{ token: ' you' }
{ token: ':\n\n' }
{ token: 'Why' }
{ token: ' don' }
{ token: "'t" }
{ token: ' scientists' }
{ token: ' trust' }
{ token: ' atoms' }
{ token: '?\n\n' }
{ token: 'Because' }
{ token: ' they' }
{ token: ' make' }
{ token: ' up' }
{ token: ' everything' }
{ token: '!' }
{ token: '' }
AIMessageChunk {
  lc_serializable: true,
  lc_kwargs: {
    content: "Sure, here's a lighthearted joke for you:\n" +
      '\n' +
      "Why don't scientists trust atoms?\n" +
      '\n' +
      'Because they make up everything!',
    additional_kwargs: {}
  },
  lc_namespace: [ 'langchain_core', 'messages' ],
  content: "Sure, here's a lighthearted joke for you:\n" +
    '\n' +
    "Why don't scientists trust atoms?\n" +
    '\n' +
    'Because they make up everything!',
  name: undefined,
  additional_kwargs: {}
}
 */

Using ChatGoogleGenerativeAI with the same handler:
const model = new ChatGoogleGenerativeAI({
  modelName: 'gemini-pro',
  callbacks: [handler],
});

model.invoke('Tell me a joke?').then((res) => console.log(res));
/**
 * {
  token: 'Why did the golfer wear two pairs of pants?\n\nIn case he got a hole in one.'
}
AIMessage {
  lc_serializable: true,
  lc_kwargs: {
    content: 'Why did the golfer wear two pairs of pants?\n' +
      '\n' +
      'In case he got a hole in one.',
    name: 'model',
    additional_kwargs: { finishReason: 'STOP', index: 0, safetyRatings: [Array] }
  },
  lc_namespace: [ 'langchain_core', 'messages' ],
  content: 'Why did the golfer wear two pairs of pants?\n\nIn case he got a hole in one.',
  name: 'model',
  additional_kwargs: {
    finishReason: 'STOP',
    index: 0,
    safetyRatings: [ [Object], [Object], [Object], [Object] ]
  }
}
 */

Expected Behavior
The handleLLMNewToken method should stream responses in a chunked format for all models, including ChatGoogleGenerativeAI.

@dosu-bot ChatGoogleGenerativeAI model does support streaming via .stream():
const stream = await model.stream('Tell me a joke.');
for await (const chunk of stream) {
  console.log('Chunk received:', chunk);
}
/**
 * {
  token: 'Why did the scarecrow win an award?\n\nBecause he was outstanding in his'
}
Chunk received: AIMessageChunk {
  lc_serializable: true,
  lc_kwargs: {
    content: 'Why did the scarecrow win an award?\n\nBecause he was outstanding in his',
    name: 'model',
    additional_kwargs: {}
  },
  lc_namespace: [ 'langchain_core', 'messages' ],
  content: 'Why did the scarecrow win an award?\n\nBecause he was outstanding in his',
  name: 'model',
  additional_kwargs: {}
}
{ token: ' field!' }
Chunk received: AIMessageChunk {
  lc_serializable: true,
  lc_kwargs: { content: ' field!', name: 'model', additional_kwargs: {} },
  lc_namespace: [ 'langchain_core', 'messages' ],
  content: ' field!',
  name: 'model',
  additional_kwargs: {}
}
 */

still the similar issue appears with python module. Can some one look into that plz


Remove quotes

I'd like to remove the quotes that are displayed when we run bosco commands.
Reasons:

not everyone knows the A-Team and that Bosco is a member
the quotes are sometimes a bit offensive (e.g. being told I'm glad I didn't know you when I was a kid or being called a crazy ass fool)
it feels a bit alienating to have these kinds of in-jokes displayed by a tool that is so widely used across the whole of Tes engineering when not everyone understands them

Coverage remained the same at 81.284% when pulling d659df721309179ea93aa9383a6ab8a35deca662 on remove-quotes into 366e7866ee770f5f8a5bbb64c849a6fbb2bd2973 on master.

build failing :(

Oh dear, CI is failing! Looks like it has been failing for a month!

I've fixed the build and rebased.

Thanks a lot for fixing @rouanw !


[Feature] router.go support object-style query string

object-style query string maybe a good idea on store some object to query without merge then,
just like jquery.param() do:
obj = {   a: {     one: 1,     two: 2,     three: 3   } }==> a[one]=1&a[two]=2&a[three]=3

@yyx990803 is there someone implementing this? How can I help?

@paulohp the qs library supports this, maybe see how it's implemented there and submit a PR? :)

I'm working on advanced data-table component and this functionality is "must have", cause I want to implement saving state of filters and pagination in query strings

vue-resource does this.  Perhaps vue-resource and vue-router and vue-resource should shared a common vue-url module or similar?

@seaneagan this issue is for 0.7 and is outdated. 2.x already supports this.

It looks like the latest code does support Arrays, but not with the ?foo=1&foo=2 rather than ?foo[]=1&foo[]=2, and it doesn't support objects e.g. ?foo[a]=1&foo[b]=2&foo[c]=3, you will instead get e.g. ?foo=[object Object]

Why is this closed? Is this a "wontfix"? As of<EMAIL_ADDRESS>is still unsolved:
{ "filter": { "title": "bla", "actions": 1 } }
returns
?filter=%5Bobject%20Object%5D
Are there any official workarounds?

in vue-router 3 you have to provide a custom and more powerful query parser (like https://github.com/ljharb/qs) to vue-router: https://router.vuejs.org/api/#parsequery-stringifyquery

Thanks, I just found #1259 with the explanation :)


Make seat backend optional

It adds a dependency on libseat and not all compositors need it.

@emersion It allows building a smaller binary, and reduces the total size of the dependency tree for those (such as Qubes OS) who will only be using software rendering and virtual inputs.

-Dsession=disabled doesn't need libudev as well, see #2257. This may help NetBSD and OpenBSD to make an initial port of wlroots as nested-only + headless-only.

I can see a rootless nested backend being quite useful in practice.

I don't really buy the "smaller binary" argument, libseat is a few KiBs on my system, probably even less with everything disabled.

That is still a bit less code, and for projects that need to review all of the code they use, it is less code to review.

Yes, I haven't considered the udev dependency, and it's definitely a good point.

wlroots has migrated to gitlab.freedesktop.org. This pull request has been moved to:
https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/3256


[v6]CoreUIv4 final CSS polish needed

Reported by Pedro: Borders on links are huge in CoreUI v4. Some stuff is missing or not aligned

In addition, I've made a video going through the CoreUIv4 theme and mentioning the things that bother me. Please make a list of the ones that you agree with, and let's start taking them down 💪

https://www.loom.com/share/a23774c829f54d039afe5ac172dd7036?sid=2e8e1947-dc03-488d-ab50-5cb8234cbdea

Hey @tabacitu, none of the issues highlighted in this task (including the ones in your video) exist anymore – my best guess would be when @karandatwani92 replaced the old demo CSS references with the updated CSS reference from CoreUI's CDN, we received the goodies.
Examples:

This issue can be closed IMHO.

Hey @phpfour ,
I was talking about CoreUIv4 not CoreUIv2 😀
I think Karan's back and can take this over though. Right @karandatwani92 ?

Note: this is overdue. It was supposed to be done this week.


Recommended/canonical way for an offset delay?

Is there a recommended way to generate frame-based numbers with an offset?
A normal D4 gives me a bang every 4th frame. What if I wanted 4th+2 (i.e. frames no. 2, 6, 10, ...)? I can think of several different approaches (a D4-spawned E that travels for two cells before banging), but no straightforward (and easily configurable) solution.

If your offset is just two frames, there's this really neat way of doing this:
3O..
.*..
.3O.
....
...D

The most minimal way to do this is simply using L.
.......D6
6L.*.....


The mAP of ImageNet is different from that on paper

Can you share the parameters setting on ImageNet?
I follow the settings described on paper, but obtain a bad result:

The pytorch version of the code perform badly on ImageNet. We do not find the reason yet. Please use the caffe version if you want to run on ImageNet.

Could you share the link of caffe version? I can't find it on github.

check caffe directory

I directly use your pretrained caffe's model to evaluate the mAP on ImageNet, and some results are as follows;

16bit: 0.4643
32bit: 0.5934

However, the results on your paper are as follows:

What makes this difference?

Maybe it is because the caffe framework changes or other reason such as initialization. I'm sure it can reproduce the results at publishing.

I retrained the model and obtain an ideal result. Thank you~

I retrained the model and obtain an ideal result. Thank you~

请问是如何训练的？我用PyTorch在DSH、DHN和HashNet三个算法上复现，均是在Imagenet数据集上表现奇差。

I retrained the model and obtain an ideal result. Thank you~

请问是如何训练的？我用PyTorch在DSH、DHN和HashNet三个算法上复现，均是在Imagenet数据集上表现奇差。

我之前跑过HashNet的作者提供的PyTorch版本，也自己复现过，但是在ImageNet上表现都不好，但我感觉你的表现好像比我的还更差。不过如果直接跑caffe的版本的话，结果和论文差不多。


Add as_sortable_control() to unify Container checks

There are lots of repetitive checks in each Container for node being a visible non-top-level Control. This PR adds a method to unify it. Now every such condition will check for is_visible_in_tree() and is_top_level() (previously it was inconsistent, like checking is_visible() instead, or omitting one of the checks). Maybe it's a bit awkward that it returns Control or null, but it makes the code simpler.
Right now the method is not exposed, but it would be useful for users making custom Containers, so it can be considered.

There is also SplitContainer, GraphElement, GraphNode, GraphFrame, and TabContainer which could use this.

Right, I'll add them too.

Though TabContainer needs invisible children. So, it could be made virtual and overridden so it can include invisible children itself.

I think it this case it could just do a manual check.

Added changes to remaining classes except TabContainer. Also Graph nodes seem to use invisible children for calculating minimum size, so I left that too (not sure if it's intended though).

Thanks!


feat: json schemas + examples and testing

WHAT
This PR include a gradle project artifacts that contains

JSON schemas for all messages
JSON-LD context for DCP
Example of messages
Tests that covers JSON schema validation and JSON-LD expansion/compaction process
GH action for running tests

Once this PR is accepted and merged to be done:

Publish maven artifacts with JSON schemas
Publish JSON schemas and JSON-LD context in GH pages
publish schemas and JSON-LD context under https://w3id.org/dspace-dcp/[version]

Closes #64
How was the issue fixed?
Briefly state why the change was necessary.
More context
List other areas that have changed but are not necessarily linked to the main feature. This could be naming changes,
bugs that were encountered and were fixed inline, etc.

/cc @arnoweiss


[BUG] disableTelemetry prop in <Refine> component

Describe the bug
AuthBindings; DataProvider: Required; NotificationProvider: ()=>Required<...>; RouterProvider: RouterBindings; DisableTelemetry: boolean; Resources: ({...;} | {...;}) []; Options: {...;};} " Assign to type 'IntrinsicAttributes&RefineProps'.
The attribute 'disableTelemetry' does not exist on type 'IntrinsicAttributes&RefineProps'. Ts (2322)
(property) disableTelemetry: boolean
Steps To Reproduce
<Refine               authProvider={authProvider}               dataProvider={DataProvider(API_URL + /api`, axiosInstance)}
notificationProvider={notificationProvider}
routerProvider={routerBindings}
disableTelemetry={true}

`
Expected behavior
Telemetry can be turned off.
Screenshot
No response
Desktop
No response
Mobile
No response
Additional Context
No response

Hello @zhou0219 sorry for the confusion. You need to pass disableTelemetry to options prop, not in the root. You can disable telemetry as seen below:
<Refine options={{ disableTelemetry: true }}>
  ...
</Refine>

It seems it's overlooked in our docs, we'll update it soon.


Fix EDS discrepancies after #175 merge

After merging #206, this changed some things in the CCSDS header and there needs to be a corresponding update to the EDS XML files and related items to ensure that the EDS actually matches the running code.
This change circles back to the EDS side and updates the XML files so they correspond to the code.

Imported from trac issue 217.  Created by jphickey on 2017-10-26T19:58:26, last modified: 2019-03-05T14:58:28

Trac comment by jphickey on 2017-10-26 20:33:39:
I have a few updates for consideration, split into separate commits for independent review.  They are all minor and nothing actually changes any functionality except for the one bugfix.

[changeset:f10a142] XML and corresponding header changes

This is the main objective.  This updates the XML EDS files to once again match the implementation post #206.  However, I did had to circle back to the code again and make some minor changes to the way the structs were defined in order to get things to really match.  The changes are fairly trivial and low risk but we can discuss.

[changeset:6e3ecbd] Move CFE_SB RoutingTblIdx type

Less critical but should be included for correctness.  The "CFE_SB_MsgRouteIdx_t" is not an external type and should not be used externally.  This moves it from the public header into the private header.

[changeset:cc5c8fc] Fix bug route file output

In doing this changeset I noticed a minor off-by-one bug in the route output file.  It should be writing a raw number into the file but it was writing the internal index.  This was not quite compatible with the old behavior, so this corrects it.  This is the only commit in this set that actually changes behavior at all.

[changeset:c6008ca] Improve forward compatibility

Finally - If there is a plan to improve the type safety of CFE_SB_MsgId_t values going forward, then we need include these wrappers in CFE 6.6 in order to get some forward compatibility.  With this, apps can be updated to use the wrapper, which in turn can make them compatible with a future release that implements strong typedef for Msg Id.
This avoids the chicken and egg problem by introducing the egg here.  Nothing uses the wrapper yet.  It is just there for future code to make use of.

Trac comment by cdknight on 2017-10-27 10:50:20:
recommend approve (FYI Joe ticket #245 has the "wrappers". I created it and forgot to cc you, and now can't add you to the cc)

Trac comment by glimes on 2017-10-27 12:50:23:
recommend approve

Trac comment by sstrege on 2017-10-27 12:55:47:
Recommend/approve

Trac comment by jhageman on 2019-03-05 14:58:28:
Milestone renamed


Add support for Mastercard and American express

This PR will add the option to choose between 3 credit card providers.
usage :
$request->setPaymentMethod('mastercard');
or
$gateway->purchase(['paymentMethod' => 'mastercard]');
or
$gateway->setPaymentMethod('mastercard');
supported methods:

Visa (visa )
Mastercard ( mastercard )
American express ( amex )

if none of the currently supported payment methods is selected, there will be a fallback to
Brq_setrequestedservices  = 'visa,mastercard,amex';
which redirects the user to a page in buckaroo where they will select supported creditcard provider they wish.
to make sure this functionality is only available for credit card, i created the
buckaroo gateway. (src/BuckarooGateway.php)
the Creditcard, Paypal, and iDeal gateways now extend  BuckarooGateway , instead of extending CreditCardGateway

Merged. Please confirm that this works in production and then I will tag for release.

This had been checked and I can confirm it works in production.


Failed to download CSV

Hello, I just installed the plugin (from your PCM repo), fired it up and this error pops up:

@Polsaker Thats new, in the past JLC just randomly returned a 404 when users tried to download the CSV, nw they seem to actively block the use by tools like this here.
Adding a browser user-agent header seems to solve this for the moment.
Lets hope they don't add additional measures to prevent this 😬


Update narwhal dependency

hoping to have this land soon to unblock another narwhal pointer update. @asonnino lmk if this can land soon, happy to take over if you need

hoping to have this land soon to unblock another narwhal pointer update. @asonnino lmk if this can land soon, happy to take over if you need

I think we can land. Let's just confirm with @huitseeker

@asonnino Here is the algorithm for merging this PR:

go to our production config repo,
recursively search our config (yaml files) for the following string pattern:

socket_addr: "(((25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)(\.?)){4}):([1024-65536])"

replace the IPs by the same expressed as a multiaddr ( /ip4/\1/tcp/\2/http)
Open the PR updating the prod configs, linking to this PR,
Merge this PR.


Update some dependencies for NativeScript 5.2

Some dependencies described in package.json can be bumped.

I will do this myself.

Thank you for the PR.


Any plans to push the source code? Really looking forward to it.

I am currently implementing this. 😅 I will take some time for implementation and experiments.

Sure, no issues. :) It would really help me also implement it on my end if you could please share some references repositories that you're probably looking at right now to implement NANSY.
Regards
Rahul Bhalley

Hmm, I'm currently trying to implement it from the paper. librosa/torchaudio/parselmouth was helpful.

Ok, thanks!

Hi @rosinality any updates on this?

I have almost implemented the model, but I found aligning features which have different sampling ratios/window sizes (wav2vec features vs mel, yingram features) is not straightforward. Currently I am stopped at that point.

Ok, thanks for updating me. :)


fix: fix indentation of repos.yaml in configmap-repo-config

The last release v4.23.0 contains a typo / bug in the configmap-repo-config.yaml template where a indent is used instead of nindent, causing a templating error if the repoConfig value is set.

Hi @nobbs , thank you for the fix. Can you please bump the patch version?

sure, give me a sec


Memory leak when returning bytes from input argument

Bug description
I found a memory leak when I return bytes object from njitted function that I put inside as argument. It can be illustrated by example below (function leak).
Amount of leaked memory does not depend on the size of the bytes object (i.e. when I set arg to b"a"*100000 I get the same behaviour).
The leak is also present when I return slice of the bytes object (leak2), but not when I only return one character (noLeak2). Also, the leak is not present when I don't use numba (noLeak3). The workaround that works for me is to return numpy array of bytes (noLeak)
I used numba 0.53.1, which I believe is the current version as of writing this report. The bug works on both windows and linux systems which I tested. Python version is 3.8.7.
Minimal example
#!/usr/bin/env python3
import numpy as np
from numba import njit,version_info
import psutil,os
print(version_info,end="\n\n")
pythonProcess = psutil.Process(os.getpid())
def printMem():
    print("mem: %.2fM"%(float(pythonProcess.memory_info().rss)/1e6))

@njit
def leak(b):
    return b
@njit
def leak2(b):
    return b[0:1]
@njit
def noLeak(b):
    return np.frombuffer(b,dtype=np.uint8)
@njit
def noLeak2(b):
    return b[0]

def noLeak3(b):
    return b

arg=b"a"
for fcn in (leak,leak2,noLeak,noLeak2,noLeak3):
    print(fcn.__name__)
    for _ in range(3):
        for _ in range(100000):
            fcn(arg)
        printMem()

Example output
version_info(major=0, minor=53, patch=1, short=(0, 53), full=(0, 53, 1), string='0.53.1', tuple=('0', '53', '1'), git_revision=None)

leak
mem: 98.61M
mem: 103.41M
mem: 108.27M
leak2
mem: 114.58M
mem: 119.44M
mem: 124.23M
noLeak
mem: 125.41M
mem: 125.41M
mem: 125.41M
noLeak2
mem: 125.59M
mem: 125.59M
mem: 125.59M
noLeak3
mem: 125.59M
mem: 125.59M
mem: 125.59M

Thanks for the report. This is fixed in https://github.com/numba/numba/pull/6937.


donut.system/stop-failed-system throws exception if dependency instance is missing

If an exception is thrown during donut.system/start, that exception contains the partially started system and may be passed to donut.system/stop-failed-system to stop it. However, this stopping procedure does not work if the missing component(s) are dependencies for other components, despite the fact those other components are never started.
I'm using version 0.0.239 of donut-party/system. I have discovered two variants of apparently same issue as described above. The following example namespace shows both of them:
(ns example.donut-issue
  (:require [donut.system :as ds]))

(def two-component-system
  {::ds/defs {:group {:component-b {::ds/start (fn [_] (throw (RuntimeException. "Error starting component-b")))}
                      :component-c {::ds/config {:component-b (ds/local-ref [:component-b])}
                                    ::ds/start (fn [_] (println "Starting component-c"))}}}})

(def three-component-system
  {::ds/defs {:group {:component-a {::ds/start (fn [_] (println "Starting component-a"))}
                      :component-b {::ds/config {:component-a (ds/local-ref [:component-a])}
                                    ::ds/start  (fn [_] (throw (RuntimeException. "Error starting component-b")))}
                      :component-c {::ds/config {:component-b (ds/local-ref [:component-b])}
                                    ::ds/start  (fn [_] (println "Starting component-c"))}}}})

(defn start [system]
  (try
    (ds/start system)                 ; Should fail to start
    (catch Exception e
      (print (ex-data e))             ; Correctly complains start signal could not be applied to [:group :component-b] ...
      (ds/stop-failed-system e)       ; ...but throws another exception instead of stopping the system (see below)
      )))

(comment
  ;; Fails with this exception:
  ;; Execution error (ExceptionInfo) at donut.system/group-ref-exception (system.cljc:304).
  ;; Invalid group ref: '[:group :component-b]' references undefined component group ':group'
  (start two-component-system)

  ;; Fails with this exception:
  ;; Execution error (ExceptionInfo) at donut.system/ref-exception (system.cljc:297).
  ;; Invalid ref: '[:group :component-c]' references undefined component '[:group :component-b]
  (start three-component-system)
  ;
  )

I've found a consequence of this issue is that donut.system.repl/start often does not work as intended if the system fails to start, as this uses donut.system/stop-failed-system. The exception from donut.system.repl/start is the one thrown during stopping rather than starting the system, which was unexpected and frustrating as I had to look elsewhere to debug why the system was not starting correctly.

Sorry you ran into this! Thank you for reporting this

Fixed as of version 0.0.241, thank you 😊


Don't drop buffered input data in findOffset()

Sometimes when fzf takes a while to startup, I start typing but my input gets dropped once the UI actually renders, and it's slightly annoying. It's rare (because fzf is usually quick), but noticeable particularly on first run after booting.
To reproduce, you can simulate a slow load with:
git ls-files | (sleep 1; fzf)

Currently anything you type in the first second will be dropped, with this change it gets consumed as search input once fzf loads.
I don't know if it's a bit weird to modify r.buffer during findOffsets(). It could alternatively return (skipped, row, col) and leave it up to the caller to add skipped to r.buffer, but that might get awkward.
I also don't know if this is the only place which needs this fix - is there a dark TUI as well as a light one?

Although I can't reproduce the issue with the command above, I do experience drops when using CTRL-R binding for bash and your patch fixes it.
findOffset is not a pure function already, so I can live with it appending leftover keystrokes to the internal buffer. I'll just merge the patch, thanks!

is there a dark TUI as well as a light one?

Ah, no. LightRenderer was named "light" just because it did not depend on ncurses unlike the old FullscreenRenderer :)


support the new thermometer

support the new thermometer with the correct humidity value
reference #17

Hi,
i created a new integration for new temp sensor of xiaomi for HA, can you download from https://github.com/gallynero/mitemp2_bt

Please enhance the integration tests so that whoever has a real device can test it.

Closing since the integration found a new home in a separate package.


/var/tmp mounted as memory-based

Is there any particular reason, why /var/tmp is configured to be mounted in RAM for most of the boards?
According to FreeBSD Handbook its content should be preserved across a system reboot.
The particular problem is Raspberry Pi 3, where the default 50MB memory-based /tmp is too small even for pkg install to work. Could 12MB memory for /var/tmp be released and reallocated to /tmp by default?

How big do you think /tmp should be?


Packaging request: Oversteer

Project description
Steering Wheel Manager for GNU/Linux
Metadata

homepage URL: https://github.com/berarma/oversteer
source URL: https://github.com/berarma/oversteer
license: GPL-3.0
platforms: linux

Would love to see this packaged as well!
Tried it myself, but I'm afraid I don't have the needed knowledge yet. Got it to build but no output.

Merged in #211423 thanks to @srounce

Thank you, @srounce!


Fixing supabase service

Applied the fixes found here: https://github.com/coollabsio/coolify/issues/2696
Tested and working for me :)

Thank you for the PR!


feat(vue-demo-store): display more info about not handled entities

Description
closes: #1091

propagates the API error to the nuxt upper levels
adds console error with the API details
makes the 404 error for unknown seoUrl consistent

Type of change

New feature (non-breaking change which adds functionality)

ToDo's

Screenshots (if applicable)

console:

Additional context

@kstala please check the 404 scenarios for:

products (clearance setting for products)
categories
landing pages


Missing Class Features

Not avalaible in the Class Features compendium
https://aonsrd.com/MechanicTricks.aspx?ItemName=Tech Tinkerer

https://aonsrd.com/MechanicTricks.aspx?ItemName=Recalibrate Engine

Shock And Awe fighting style
https://aonsrd.com/FightingStyles.aspx?ItemName=Shock and Awe


Add more context to vip test app names

High-level description
Debugging apps with just a random hash is hard. This changed introduces
more context to each app name so that they are unique and human
readable.
Please see https://github.com/dcos/dcos/pull/3043.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-2115 test_vip failed with RetryError on MarathonApp.wait

Related tickets (optional)
Other tickets related to this change:
Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change: it's integration tests
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot bump-ee

Thank you so much Sergey!

@mesosphere-mergebot override-status teamcity/dcos/build/dcos/windows DCOS-42046


Allow _ in project name

closes https://github.com/softwaremill/adopt-tapir/issues/30

Has conflicts unfortunately

Thanks :)


[EAS][ANDROID] Build fails due to character parsing error

Build/Submit details page URL
https://expo.dev/accounts/seegno-labs/projects/unimoney/builds/47330489-7fbc-4ca2-9448-a43cbac3c9fd
Summary
After upgrading to expo-sdk-46 i can't run eas android builds. I can seem to find the cause for that, because local builds work as expected.
Running on eas on the cloud or locally (--local option) produces the error output bellow.
I've tried:

Manually install @react-native-community/cli-platform-android (as suggested in expo discord)
Remove expo | expo-cli | eas-cli and add them again.
Remove plugins entries one by one to check if some of them were causing the issue.
Debugging configs described here.

This error output bellow leads to this code block on<EMAIL_ADDRESS> try {
      json = new JsonSlurper().parseText(reactNativeConfigOutput)
    } catch (Exception exception) {
      throw new Exception("Calling `${reactNativeConfigCommand}` finished with an exception. Error message: ${exception.toString()}. Output: ${reactNativeConfigOutput}");
    }
    def dependencies = json["dependencies"]
    def project = json["project"]["android"]

    if (project == null) {
      throw new Exception("React Native CLI failed to determine Android project configuration. This is likely due to misconfiguration. Config output:\n${json.toMapString()}")
    }

By running the command described in the error manually i get a valid json file:
Managed or bare?
Managed
Environment
Expo env info
  expo-env-info 1.0.5 environment info:
    System:
      OS: macOS 12.0.1
      Shell: 5.8 - /usr/local/bin/zsh
    Binaries:
      Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
      Yarn: 1.22.10 - /usr/local/bin/yarn
      npm: 8.15.1 - ~/.nvm/versions/node/v16.16.0/bin/npm
      Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
    Managers:
      CocoaPods: 1.11.3 - /usr/local/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
    IDEs:
      Android Studio: 2021.2 AI-212.5712.43.2112.8512546
      Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild
    npmPackages:
      expo: ^46.0.2 => 46.0.2
      react: 18.0.0 => 18.0.0
      react-dom: 18.0.0 => 18.0.0
      react-native: 0.69.4 => 0.69.4
      react-native-web: ~0.18.7 => 0.18.7

Expo doctor
Expected package<EMAIL_ADDRESS>Found invalid:
<EMAIL_ADDRESS><EMAIL_ADDRESS>  (for more info, run: npm why expo-modules-autolinking)
Expected package<EMAIL_ADDRESS>Found invalid:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  (for more info, run: npm why @expo/config-plugins)
Expected package<EMAIL_ADDRESS>Found invalid:
<EMAIL_ADDRESS><EMAIL_ADDRESS>  (for more info, run: npm why @expo/prebuild-config)

Error output

```[RUN_GRADLEW] Running './gradlew :app:assembleRelease' in /var/folders/sb/705339xs6kg83h_n36j2d4mh0000gn/T/eas-build-local-nodejs/b9779d56-0e8b-4427-aa6c-7da7eac469c1/build/android
[RUN_GRADLEW] FAILURE:
[RUN_GRADLEW] Build failed with an exception.
[RUN_GRADLEW] * Where:
[RUN_GRADLEW] Script<EMAIL_ADDRESS>line: 250
[RUN_GRADLEW] * What went wrong:
[RUN_GRADLEW] A problem occurred evaluating script.
[RUN_GRADLEW] >
[RUN_GRADLEW] Calling `[node<EMAIL_ADDRESS>config]` finished with an exception. Error message: groovy.json.JsonException: Unable to determine the current character, it is not a string, number, array, or object
[RUN_GRADLEW]
[RUN_GRADLEW]   The current character read is 'i' with an int value of 105
[RUN_GRADLEW]   Unable to determine the current character, it is not a string, number, array, or object
[RUN_GRADLEW]   line number 1
[RUN_GRADLEW]   index number 0
[RUN_GRADLEW]   info Run CLI with --verbose flag for more details.
[RUN_GRADLEW]   ^. Output: info Run CLI with --verbose flag for more details.
[RUN_GRADLEW] * Try:
[RUN_GRADLEW] > Run with --stacktrace option to get the stack trace.
[RUN_GRADLEW] > Run with --info or --debug option to get more log output.
[RUN_GRADLEW] > Run with --scan to get full insights.
[RUN_GRADLEW] * Get more help at https://help.gradle.org
[RUN_GRADLEW] BUILD FAILED in 3s
[RUN_GRADLEW] Error: Gradle build failed with unknown error. Please see logs for the "Run gradlew" phase.

Reproducible demo or steps to reproduce from a blank project
I couldn't reproduce the by simply adding a eas.json config to blank project, so'll paste my package.json file:
{
  "name": "not-relevant",
  "version": "0.27.1",
  "private": true,
  "description": "Not relevant",
  "license": "UNLICENSED",
  "scripts": {
    "android": "expo run:android",
    "build": "eas whoami &>/dev/null || eas login && eas build --non-interactive",
    "build-storybook": "build-storybook",
    "changelog": "github_changelog_generator --no-issues --header-label='# Changelog' --future-release=v$npm_config_future_release",
    "debug": "open 'rndebugger://set-debugger-loc?host=localhost&port=8081'",
    "eject": "expo eject",
    "flipper": "METRO_SERVER_PORT=8081 open -a Flipper.app",
    "generate": "node ./bin/generate.js",
    "generate-graphql": "graphql-codegen --config codegen.yml",
    "postinstall": "patch-package",
    "ios": "expo run:ios",
    "lint": "eslint --ext .js,.ts,.tsx .",
    "lint-staged": "lint-staged",
    "lint-styles": "stylelint './src/**/*[^.d$].ts?(x)'",
    "start": "expo start --dev-client",
    "storybook": "start-storybook -p 7007",
    "test": "jest",
    "test-watch": "jest --watch --notify",
    "transform-svgs": "./bin/transform-svgs.sh",
    "type-check": "tsc --project tsconfig.json --noEmit",
    "version": "npm run changelog --future-release=$npm_package_version && git add -A CHANGELOG.md",
  },
  "pre-commit": [
    "lint-staged"
  ],
  "resolutions": {
    "@types/react": "~18.0.0",
    "@types/react-native": "~0.69.1",
    "react-native-skeleton-content/expo-linear-gradient": "~11.4.0",
    "react-native-skeleton-content/react-native-reanimated": "~2.9.1"
  },
  "dependencies": {
    "@apollo/client": "^3.6.9",
    "@expo/config": "^7.0.0",
    "@formatjs/intl-datetimeformat": "^4.2.6",
    "@formatjs/intl-getcanonicallocales": "^1.8.0",
    "@formatjs/intl-locale": "^2.4.41",
    "@formatjs/intl-numberformat": "^7.2.6",
    "@formatjs/intl-pluralrules": "^4.1.6",
    "@react-hook/debounce": "^4.0.0",
    "@react-native-async-storage/async-storage": "~1.17.3",
    "@react-native-community/blur": "^4.1.0",
    "@react-native-community/datetimepicker": "6.2.0",
    "@react-native-firebase/analytics": "^15.3.0",
    "@react-native-firebase/app": "^15.3.0",
    "@react-native-firebase/auth": "^15.3.0",
    "@react-native-firebase/crashlytics": "^15.3.0",
    "@react-native-firebase/firestore": "^15.3.0",
    "@react-native-firebase/messaging": "^15.3.0",
    "@react-navigation/elements": "^1.3.4",
    "@react-navigation/native": "^6.0.11",
    "@react-navigation/stack": "^6.2.2",
    "@seegno/react-forms": "^0.15.0",
    "@types/color": "^3.0.2",
    "@types/config": "^0.0.39",
    "@types/jest": "^28.1.6",
    "@types/jsonwebtoken": "^8.5.5",
    "@types/lodash": "^4.14.172",
    "@types/react": "~18.0.0",
    "@types/react-native": "~0.69.1",
    "@types/semver": "^7.3.9",
    "@types/styled-components": "^5.1.25",
    "@types/styled-components-react-native": "^5.1.3",
    "ajv": "^8.6.3",
    "ajv-formats": "^2.1.1",
    "apollo3-cache-persist": "^0.14.1",
    "babel-plugin-module-resolver": "^4.1.0",
    "bignumber.js": "^9.0.1",
    "color": "3.2.1",
    "config": "^3.3.6",
    "country-iso-to-coordinates": "^1.0.2",
    "date-fns": "^2.28.0",
    "deprecated-react-native-prop-types": "^2.3.0",
    "events": "^3.3.0",
    "expo": "^46.0.2",
    "expo-application": "~4.2.2",
    "expo-clipboard": "~3.1.0",
    "expo-community-flipper": "^45.1.0",
    "expo-dev-client": "~1.1.1",
    "expo-device": "~4.3.0",
    "expo-font": "~10.2.0",
    "expo-linear-gradient": "~11.4.0",
    "expo-linking": "~3.2.2",
    "expo-localization": "~13.1.0",
    "expo-location": "~14.3.0",
    "expo-notifications": "~0.16.1",
    "expo-secure-store": "~11.3.0",
    "expo-splash-screen": "~0.16.1",
    "expo-status-bar": "~1.4.0",
    "expo-system-ui": "~1.3.0",
    "expo-updates": "~0.14.3",
    "expo-web-browser": "~11.0.0",
    "graphql": "^16.5.0",
    "i18n-iso-countries": "^6.8.0",
    "i18next": "^20.4.0",
    "ibantools": "^4.1.4",
    "is-promise": "^4.0.0",
    "jwt-decode": "^3.1.2",
    "libphonenumber-js": "^1.9.37",
    "lodash": "^4.17.21",
    "nanoid": "^3.1.30",
    "patch-package": "^6.4.7",
    "react": "18.0.0",
    "react-countdown-hook": "^1.1.1",
    "react-dom": "18.0.0",
    "react-i18next": "^11.18.3",
    "react-native": "0.69.4",
    "react-native-draggable": "^3.3.0",
    "react-native-email-link": "^1.12.2",
    "react-native-flipper": "^0.156.0",
    "react-native-gesture-handler": "~2.5.0",
    "react-native-known-styling-properties": "^1.1.0",
    "react-native-map-clustering": "^3.4.2",
    "react-native-maps": "0.31.1",
    "react-native-modal": "^13.0.1",
    "react-native-pure-jwt": "^3.0.1",
    "react-native-reanimated": "~2.9.1",
    "react-native-safe-area-context": "4.3.1",
    "react-native-screens": "~3.15.0",
    "react-native-skeleton-content": "^1.0.24",
    "react-native-svg": "12.3.0",
    "react-native-swipe-list-view": "^3.2.9",
    "react-native-web": "~0.18.7",
    "react-signal": "^0.2.1",
    "semver": "^7.3.5",
    "styled-components": "^5.3.5",
    "styled-tools": "^1.7.2",
    "typescript": "^4.6.3",
    "typescript-styled-plugin": "^0.18.2"
  },
  "devDependencies": {
    "@babel/core": "^7.18.6",
    "@graphql-codegen/cli": "2.6.2",
    "@graphql-codegen/near-operation-file-preset": "^2.2.9",
    "@graphql-codegen/typescript": "2.4.8",
    "@graphql-codegen/typescript-operations": "2.3.5",
    "@graphql-codegen/typescript-react-apollo": "3.2.11",
    "@storybook/addon-actions": "^5.3",
    "@storybook/addon-knobs": "^5.3",
    "@storybook/addon-links": "^5.3",
    "@storybook/addon-ondevice-actions": "^5.3.23",
    "@storybook/addon-ondevice-knobs": "^5.3.25",
    "@storybook/react-native": "^5.3.25",
    "@storybook/react-native-server": "^5.3.23",
    "@svgr/cli": "^5.5.0",
    "@testing-library/jest-native": "^4.0.5",
    "@testing-library/react-hooks": "^8.0.1",
    "@testing-library/react-native": "^11.0.0",
    "@typescript-eslint/eslint-plugin": "^4.22.0",
    "@typescript-eslint/parser": "^4.22.0",
    "babel-loader": "^8.2.2",
    "cli-color": "^2.0.1",
    "eas-cli": "^0.58.0",
    "eslint": "^6.8.0",
    "eslint-config-seegno": "^17.0.0",
    "eslint-plugin-react-native": "^3.11.0",
    "eslint-plugin-typescript-sort-keys": "^1.7.0",
    "expo-cli": "^6.0.1",
    "generate-template-files": "^3.2.0",
    "jest": "^26.6.3",
    "jest-expo": "^46.0.0",
    "jest-styled-components": "^7.0.8",
    "jsonlint": "^1.6.3",
    "jsonwebtoken": "^8.5.1",
    "lint-staged": "^11.1.2",
    "pre-commit": "^1.2.2",
    "sort-package-json": "^1.55.0",
    "stylelint": "^13.12.0",
    "stylelint-config-seegno": "^0.5.0",
    "stylelint-react-native": "^2.3.0",
    "tsconfig-paths": "^3.11.0",
    "yarn-deduplicate": "^3.1.0"
  },
  "engines": {
    "node": ">= 16"
  }
}

Any updates on this issue? Did you find a solution?

Any updates on this issue? Did you find a solution?

Hi @itseramin , reproducible version can be found here:
https://github.com/expo/eas-cli/issues/1263
The expo team closed the issue, but i still think it's a bug, because i shouldn't need dev dependencies to bundle my app (ex: jest, eslint, etc).
The workaround is to place all (except @babel/core) your devDependencies on dependencies.

You can also get this if you don't have @expo/webpack-config installed

Hey
Did you find any solution ?? I tried all what you suggested (even moving the devDependencies) and it's not working.. I'm using a mono repo and completely struggling on it

Same error, moved from expo build to eas, and cant build anymore
Tried to update all packages to last version, move devDependencies, no changes, same error
pls help if you have some info

Hey Did you find any solution ?? I tried all what you suggested (even moving the devDependencies) and it's not working.. I'm using a mono repo and completely struggling on it

devDependencies trick worked for me at the time. Don't know if recent updates may raise the same error, but for other reason now :(
Sorry, i've been out of expo development for a while now


An error occured while checking your authorization.

Hi
Managed to launch the "launchpad" app but got the following error when tried to check the prerequisites.
An error occured while checking your authorization.  Please assign the XS_AUTHORIZATION_ADMIN role collection to your user and retry.
As per below screenshot, the  Role collection was already assinged.
Thank you for your support

Can you clarify if you are  installing shine via  web ide or SCA
Best Regards
Stephen

Hi @CHERIANS
This one was through the web ide

I should probably reinstall by I am quite sure I removed the "extra" / and put https://hxehost:39032/uaa-security
Maybe that was my mistake?

Hi,
I hope the issue was solved. Hence closing the issue. Feel free to reopen if this issue still exists
Best Regards
Stephen


Store tempdir in UhyveFileMap instead of attaching it to the open() hypercall

Depends on https://github.com/hermit-os/uhyve/issues/818.


NO-ISSUE: Try to make triage report relient to errors

Default missing values from Jira ticket to a default value. That way,
the report is still sent to the channel even if tickets are malformed.
x-ref: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-assisted-assisted-installer-deployment-master-triage-status-report/1618141654198259712

/cc @osherdp @nmagnezi


Unidentified warnings when using bottleneck. Feature request for description

After training the Bottle neck scenario, I have few doubts in understanding and analyzing. If someone could help me understand, it would be highly appreciated. I encountered some warnings and it took so much time to start the training. During this time, it was giving warnings as follows:
Warning: Vehicle 'flow_0.111' ends teleporting on edge '4', time 274.00.
Loading configuration... done.
Success.
Loading configuration... done.
Warning: Invalid departPos 296.00 given for vehicle 'rl_4'. Inserting at lane end instead.
Warning: Teleporting vehicle 'rl_0'; collision with vehicle 'flow_0.27', lane=':4_0_2', gap=-1.00, time=114.00 stage=move.
Warning: Vehicle 'rl_0' ends teleporting on edge '4', time 114.00.
Loading configuration... done.
Success.
Loading configuration... done.
Warning: Invalid departPos 296.00 given for vehicle 'rl_4'. Inserting at lane end instead.
Warning: Teleporting vehicle 'flow_0.141'; collision with vehicle 'flow_0.144', lane=':4_0_1', gap=-1.00, time=357.80 stage=move.
Warning: Vehicle 'flow_0.141' ends teleporting on edge '5', time 357.80.
Loading configuration... done.
Success.
Loading configuration... done.
Warning: Invalid departPos 296.00 given for vehicle 'rl_4'. Inserting at lane end instead.
Warning: Teleporting vehicle 'flow_0.91'; collision with vehicle 'flow_0.82', lane=':4_0_3', gap=-1.00, time=230.20 stage=move.
Could some one please explain how are the collisions happening and how can I avoid these collisions? Also, second question, in bottle neck, there are no 'rl' vehicles added. Then how is there warning telling "Invalid departPos for 'rl_4' ". From where is this warning coming and how can I verify it.
Also, I would appreciate if some documentation help would be there. Given descriptions are not enough for understanding. Especially regarding parameters and features.
Finally, Where are the rewards being calculated( I have seen compute_rewards function but didn't find it's implementation/calling usage in examples) and how can I give my own rewards?
Any help regarding these 4 questions is sincerely thanked.

hi @pnp91 I'll create an issue about adding some more documentation to the bottleneck environment and see if we can resolve it in the next few days. As for the first issue, @eugenevinitsky do you know how to prevent collisions in this network?

as an update, I started documented and testing some of the features in this environment in PR #437, but unfortunately do not know too much about this environment. Will try to assign this to someone soon


The "S" within inputString is highlighted

Not sure why the middle S is highlighted.

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

ID: 6e60cc3d-fd45-2a73-aa40-536051e9f54d
Version Independent ID: ddf2d9c5-6855-66e7-06c6-b4036dea1276
Content: TRANSLATE (Transact-SQL) - SQL Server
Content Source: docs/t-sql/functions/translate-transact-sql.md
Product: sql
Technology: t-sql
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

Hi @renjieliu. Thanks for your feedback. There's not much we can do about this unfortunately, so I'm going to report it internally and close this issue. We appreciate your help to make Docs better!
#please-close


Jump to desired page in pagination

Hi,
I have created a product list using pagination of list.js. The product number is huge.
So I want to create input number and a button where I can put the desired page then click the button, the page jumps to the desired number.
Is it possible to do that?
Thank you so much!

I was able to do that with this:
var tableList = new List('tableID', options);

tableList.i = SOME NUMBER; // This is the index of the list that the page starts at.  The index starts at 1
tableList.update();  // Rerenders the list.

Also, you may want to use the show method.
http://listjs.com/api/#show

It works, thank you!


trailingSlash override functionality

Describe the problem
Issue: Looking for a way to override trailingSlash from always -> never in a route sub-path
Is it possible to override the default configuration for 'always' or 'never' for a childless leaf node route?
If I'm not mistaken, before the August breaking changes, this was possible to override at the folder/page level with something like:
<script context="module"> export const trailingSlash = 'never'; </script>
Trying to export this from a +page.server.ts does not seem to convey to the current build.
It's nice to use always/never instead of using ignore to ensure all urls have a single canonical, but there are use cases where it's nice to enforce always as the default, and then apply never to childless node pages.
For example:
/topic/ - trailing slash
/topic/subtopic/ - trailing slash
/topic/subtopic/leaf-content-with-no-children - Would like to use trailingSlash = never for content here?
Asked on discord, was advised this was intentional but possibly worth creating an Issue to confirm this is a permanent, intentional design decision.
Describe the proposed solution
This would only make sense in the context of using always as the site-wide default, then allowing over-rides in subfolders.
The config option would need to be overridable server-side in a +layout.server.ts or +page.server.ts in a sub-folder.
In this example, a +page.server.ts in /topic/subtopic/ would be applied to flip always to never for children of subtopic.
Routes matching a regex like /topic/subtopic/[slug] would not receive a trailingSlash.
Alternatives considered
Using ignore and building the enforcement manually in JS or enforce with rewriterules at the LB layer.
Definitely possible, but feels undesirable.
Importance
nice to have
Additional Information
It feels like a fairly common canonicalization practice has been that folders get a trailing slash, child-most content pages do not.
If you are in a situation with a legacy site that behaves this way, you must make some tough, permanent decisions about lots of 301's if they have used a structure where only child-most content does not have a trailing slash.
Without a built-in method to replicate, it increases the level of difficulty to migrate existing sites.
Again, all possible, but it would feel smoother if this was possible without adding in nginx/custom logic/etc :)

The hesitation here was that a page option forces you to load the code before determining whether you need to redirect or not, which slows things down. If you can return a redirect response as soon as you know which route matched, you save yourself some work.
But now that I think more about it, maybe we're optimising for the wrong thing. There might be some gotchas involved in moving to a page option that we won't find until we try and implement it, but perhaps it's worth trying.


Use a hexadecimal representation for the example checksum.

As per @julz comment on https://github.com/knative/serving/pull/8123 this is more usual. I like it better anyway as the Checksum function now controls the representation.
/assign @julz

👍 love it.
/lgtm

/assign @mattmoor


Generate reports and barcharts from golr

Current:
http://geneontology.org/page/current-go-statistics
Given a little time, we could just abandon the images and make some nice
web-only charts using D3 (http://bl.ocks.org/mbostock/3886208) or
flotcharts (http://www.flotcharts.org/flot/examples/stacking/index.html)
or something.

I see this is in the 2.4 milestone. Which framework did you decide in the end?

I many ways, the count of experimental annotations is most meaningful. It's not hard to boost automatic annotations. Would it therefore make sense to always make the experimental block always show up at the bottom of the stack, to make visual alignment easier?

[ ] Annotations by Species by Aspect.  Like the one that is already there for Annotations by Source by Aspect, but by Species (for the same species listed in the current one for Annotations by Species).
[ ] Curation of experimental annotations: publications.  Num unique publications (for all EXP annotations only) by Assigned by.  This shows how many publications have been curated by each group, and is probably the best metric for literature curation effort by the different contributing groups.
[ ]  Curation of experimental annotations: annotations/publication.  Num annotations (EXP only) / Num unique publications, by Assigned by, stacked bars for each aspect.   Gives an idea of how different groups annotate relative to each other (over- or under-annotation, or focus on high-throughput papers).
[ ] Curation of homology annotations. Num annotations (for all manual similarity evidence) by Assigned by, stacked bars for each aspect. Shows who is doing manual curation of inferred annotations.
[ ] Annotations by different IEA methods. Num annotations (IEA only, same limited list of genomes as in #1) by With field (i.e. method), stacked bars for each aspect. Shows which methods are used to provide computational annotations.

The go-site link, and graphics choice: geneontology/go-site#149
Implementation here.

http://tomodachi.berkeleybop.org/amigo/base_statistics

Okay, more-or-less have the replacement framework in place. Now let's looks at these new ones...

@cmungall has bumped down priority here, so I'm going to close this out and let people add new items that they might want to a wishlist item.