My bot isn't working for some reason

I wanted to use your code to make a bot but with the name of my server, I was giving credit to you but a problem kept showing up, it gave me these errors.

Have you done npm i, in the console, to install dependencies

Lemme try doing that

its still doing this

I ran the npm i command again and its giving me this

unable to deploy need help please provide discord server link

how


Bug: Order of conditional format

Question
Hello,
I have question about order of conditional format
I'm trying to make a new excel sheet wth 20 conditional format
and they are overlapping in some cells but when i open the sheet the order is reversed i tried to reverse the range in my code for i in (0..19).rev() { but it did not work also i tried to use hard code not a loop and played with the order in the code and it aalways give me the same outcome am i doing some thing wrong?
    for i in 0..19 {
        let form = Format::new()
            .set_background_color(Color::RGB(color_array[i].0))
            .set_font_color(Color::RGB(color_array[i].1))
            .set_border_color(Color::RGB(BORDER_COLOR))
            .set_border_top(FormatBorder::Thin)
            .set_border_bottom(FormatBorder::Thin)
            .set_bold()
            .set_align(FormatAlign::Center);

        let rule = format!("$W4>={}", i + 1);
        let conditional = ConditionalFormatFormula::new()
            .set_rule(rule.as_str())
            .set_format(form);
        worksheet.add_conditional_format(3, i as u16, MAX_ROWS, 22, &conditional)?;
    }

The order that the conditional formats are applied should be the same as the order they are added in.
Could you please add a small complete working program and I'll have a look at it. It probably doesn't need 20 conditional formats to reproduce it. Try with 5 or 6.

*This is the desired out come

*and this is the complete project
use rust_xlsxwriter::*;
fn main() -> Result<(), XlsxError> {
    const MAX_ROWS: u32 = 5000;
    //Colors
    let color_array: [(u32, u32); 20] = [
        (0x0000ff, 0xffff00),
        (0x80ff80, 0x000000),
        (0xffff00, 0x3a00ff),
        (0x0000ff, 0xffffff),
        (0xff0000, 0xffffff),
        (0x80ffff, 0x000000),
        (0xff80ff, 0x000000),
        (0xffff80, 0x000000),
        (0x000000, 0xffffff),
        (0xc0c0c0, 0xffffff),
        (0x008000, 0xffffff),
        (0x0000a0, 0xffffff),
        (0x804000, 0xffffff),
        (0x800080, 0xffffff),
        (0xff8040, 0xffffff),
        (0x8080c0, 0xffffff),
        (0x808040, 0xffffff),
        (0x808080, 0xffffff),
        (0x408080, 0xffffff),
        (0x8080c0, 0xffffff),
    ];

    const BORDER_COLOR: u32 = 0xc0c0c0;
    // Create a new Excel file object.
    let mut workbook = Workbook::new();

    // Add a worksheet to the workbook.
    let worksheet = workbook.add_worksheet();

    //Set worksheet name
    worksheet.set_name("WBS")?;

    //Add heading data
    worksheet.write(2, 20, "WBS Code")?;
    worksheet.write(2, 21, "WBS Name")?;
    worksheet.write(2, 22, "WBS Level")?;

    //Add first level data
    worksheet.write(3, 20, "Project Code")?;
    worksheet.write(3, 21, "Project Name")?;
    worksheet.write(3, 22, "1")?;

    //first level format *Complete Later*
    let first_level_format = Format::new()
        .set_background_color(Color::RGB(color_array[0].0))
        .set_font_color(Color::RGB(color_array[0].1))
        .set_font_size(12)
        .set_border_color(Color::RGB(BORDER_COLOR))
        .set_border_top(FormatBorder::Thin)
        .set_border_bottom(FormatBorder::Thin)
        .set_bold();
    worksheet.set_range_format(3, 0, 3, 22, &first_level_format)?;

    //special first level format *Complete Later*
    let s_first_level_format = Format::new()
        .set_background_color(Color::RGB(color_array[0].0))
        .set_font_color(Color::RGB(color_array[0].1))
        .set_font_size(12)
        .set_border_color(Color::RGB(BORDER_COLOR))
        .set_border_top(FormatBorder::Thin)
        .set_border_left(FormatBorder::Thin)
        .set_bold();
    worksheet.set_cell_format(3, 0, &s_first_level_format)?;

    //Conditional format 1
    for i in 0..19 {
        // println!("{i}");
        let form = Format::new()
            .set_background_color(Color::RGB(color_array[i].0))
            .set_font_color(Color::RGB(color_array[i].1))
            .set_border_color(Color::RGB(BORDER_COLOR))
            .set_border_top(FormatBorder::Thin)
            .set_border_bottom(FormatBorder::Thin)
            .set_bold()
            .set_align(FormatAlign::Center);

        let rule = format!("$W4>={}", i + 1);
        let conditional = ConditionalFormatFormula::new()
            .set_rule(rule.as_str())
            .set_format(form);
        worksheet.add_conditional_format(3, i as u16, MAX_ROWS, 22, &conditional)?;
    }

    //set  columns width
    worksheet.set_column_range_width(0, 19, 0.5)?;
    worksheet.set_column_range_width(20, 22, 13)?;
    worksheet.set_column_width(21, 50)?;

    // Save the file to disk.
    workbook.save("test.xlsx")?;

    Ok(())
}

after digging into the problem i tried to see the root cause to see what factor affect it
i think it relate to the add_conditional_format()  i tried to make rule for range that nested inside other range that also has conditional format see the below figure

when i tried this code
    let format1 = Format::new().set_background_color(Color::Red);
    let rule1 = format!("$W4>={}", 1);
    let conditional1 = ConditionalFormatFormula::new()
        .set_rule(rule1.as_str())
        .set_format(format1);
    worksheet.add_conditional_format(0, 0, 5, 5, &conditional1)?;

    let format2 = Format::new().set_background_color(Color::Blue);
    let rule2 = format!("$W4>={}", 2);
    let conditional2 = ConditionalFormatFormula::new()
        .set_rule(rule2.as_str())
        .set_format(format2);
    worksheet.add_conditional_format(0, 1, 5, 5, &conditional2)?;

here you will see the Red rule come before the Blue but the Blue is nested inside it and the outcome is:

if we changed the range without change the order of the code just making the Red inside the Blue
    let format1 = Format::new().set_background_color(Color::Red);
    let rule1 = format!("$W4>={}", 1);
    let conditional1 = ConditionalFormatFormula::new()
        .set_rule(rule1.as_str())
        .set_format(format1);
    worksheet.add_conditional_format(0, 1, 5, 5, &conditional1)?;

    let format2 = Format::new().set_background_color(Color::Blue);
    let rule2 = format!("$W4>={}", 2);
    let conditional2 = ConditionalFormatFormula::new()
        .set_rule(rule2.as_str())
        .set_format(format2);
    worksheet.add_conditional_format(0, 0, 5, 5, &conditional2)?;

the out come will be:

it does not follow the order of the code block it follow who is inside who
but in fact if the two rules have the same range it follow the order of the code
    let format1 = Format::new().set_background_color(Color::Red);
    let rule1 = format!("$W4>={}", 1);
    let conditional1 = ConditionalFormatFormula::new()
        .set_rule(rule1.as_str())
        .set_format(format1);
    worksheet.add_conditional_format(0, 0, 5, 5, &conditional1)?;

    let format2 = Format::new().set_background_color(Color::Blue);
    let rule2 = format!("$W4>={}", 2);
    let conditional2 = ConditionalFormatFormula::new()
        .set_rule(rule2.as_str())
        .set_format(format2);
    worksheet.add_conditional_format(0, 0, 5, 5, &conditional2)?;

i don't know why it behave like this i tried to help as i can but i can't figure out this behavior

From a first look this seems to be standard Excel behavior. Do you get the same or different behavior if you create the rules in Excel?

Actully in excel , the order of the rules doesn't depend on the range size or nesting. It's determined solely by the order in which you create them.
The last rule you create will be on the top and have the highest priority.

Actully in excel , the order of the rules doesn't depend on the range size or nesting. It's determined solely by the order in which you create them.
The last rule you create will be on the top and have the highest priority.

Actully in excel , the order of the rules doesn't depend on the range size or nesting. It's determined solely by the order in which you create them.

In that case could you attach a file with manually applied rules that reflects your desired output.

In that case could you attach a file with manually applied rules that reflects your desired output and mimics the file you are trying to generate in code.

actually i want to say thank you for your strong support second sure i will attach a file
example.xlsx
what i want to achieve is some thing like this

what i want to achieve is some thing like this

Okay. I think I see the issue now and this is probably a bug.
The conditional formats are being sorted by the range whereas you expect (reasonably I think) that the conditional formats appear in the order or creation (or the reverse order of creation). I'll look at putting a fix in for that.

Thank you for your consideration

I've pushed a fix for this to main.
You will need to use for i in (0..19).rev() {} since the ordering corresponds to the order the conditional formats are added in.
Here is the output from your sample code with the WBS numbers filled in manually:

Try it out and let me know how you get on.

i tried now to reverse the loop but i got the same old behavior

do i need to change some thing in the crate it self first?

do i need to change some thing in the crate it self first?

Yes. Until the crate is published you will need to test with the GitHub version by adding it to your Cargo.toml like this
cargo add --git https://github.com/jmcnamara/rust_xlsxwriter.git rust_xlsxwriter

It work perfectly !, thank you :)

Great. I'll release it in a crate (probably 0.79.1) later today.

This fix is now upstream in v0.79.1. Thanks for the report.


Move callback wrapper code from Unity plugin up into Managed-OSVR

There's callback wrapper code (mostly generated, IIRC, using the Lua script) that makes a more idiomatic .NET interface for registering callbacks on interfaces. Any Unity-specific pieces should be factored out and this should go up into Managed-OSVR to be used by other .NET consumers
cc @JeroMiya

This can be closed. It will be implemented as part of this issue:
https://github.com/OSVR/Managed-OSVR/issues/7


Encapsulate generation options in a config struct

Closes #87.
Now whenever we generate text we will also load generation config (sourced from either generation_config.json or config.json).
# Load the config with model defaults
{:ok, generation_config} = Bumblebee.load_generation_config({:hf, "gpt2"})
# Further customize the options
generation_config = Bumblebee.configure(generation_config, max_new_tokens: 10)

This also adds generation strategy option, which is a map like %{type: :contrastive_search, top_k: 4, penalty_alpha: 0.6}. Since there are very few strategy-specific options I think the nesting is fine and we can require all of them. This way we avoid conflicting option names, and listing options that are not relevant for the configured strategy.

CI fails because we try to run too many slow tests and run of resources (likely disk space). Everything passes locally, so I'm merging :)


Update NPM package import to V2

Update import statement to from V1 to V2 plugin name

Thanks for contributing! This repository does not accept PRs because it's a mirror of https://github.com/tauri-apps/plugins-workspace/tree/v2/plugins/store - the next commit to the upstream repo would overwrite this one here.


🚸 Holisic navigation improvements

I wanted to address several problems holistically in this PR (which also resulted in a facelift):
Please see the below 🎦 Loom link or description for summary:
https://www.loom.com/share/42e191943eb94139939a38f6477c5067

Left nav too narrow on some breakpoints that causes unpleasant word-breaks
Reduce left nav font size so it doesn't take away attention from heading
Use typography that's more consistent with the app
Make it easier to link back to dashboard or homepage
Overall responsive design improvements

Tasks:

[x] Typography changes so the left nav looks like the app's nav
[x] Increase stack breakpoint
[x] Sticky left nav
[x] Move home button to header
[x] Increase burger menu hotspot
[x] Left nav use chev icon

Screenshots

Moved back to draft for requested fixes:

[ ] Prevent main content scrolling once I scroll to the end of the left nav
[ ] Remove green bar highlighting current section

Thanks @meiqimichelle for taking a look 🙌 I've reduced the chevron size.

With regards to:

I've also found the "opening" chevron direction interaction clearer than the up-down one.

If you don't mind I'll have a think about this chevron change 🤔 and do it in an upcoming PR. To start, I'll play it safe and use the convention. I'm unsure about the right arrow as it may be misinterpreted as a link rather than an expando/collapso.
That being said, I think the left nav can be better and speak more about the type of content rather than just a conventional nav. For example XCode and Notion docs have interesting treatment (chev on left, pill and icon affordances). I'll need to make more sense of how our doc content can better serve the developers' needs.


Improvements in ExecutorConnectivityService

Fixing responses from ExecutorConnectivityService  - now on different error - the service returns different httpStatus

:x: Build hpe-application-automation-tools-plugin latest.64-gxbcaxia failed (commit https://github.com/hpsa/hp-application-automation-tools-plugin/commit/179001bb34 by @radislavB)

:x: Build hpe-application-automation-tools-plugin latest.64-huiyvuvk failed (commit https://github.com/hpsa/hp-application-automation-tools-plugin/commit/179001bb34 by @radislavB)

approved for test build

@m-seldin  - code reviewed?


Unusable for Average User

Hi,
Many thanks for designing this script but it seems unusable for an average PC user. I am getting these errors when trying to run the .sh script in the terminal and get git to work. Not to mention the .plist file which I don't even know how to run on my Linux system.
A simple GUI app that would monitor file changes and autosync would be a much needed addition to the GitJournal project, in my view.
user@pc ~/ . . . /GitJournal $ bash git-auto-sync.sh
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

user@pc ~/ . . . /GitJournal $ git init
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
Initialized empty Git repository in / . . . /GitJournal/.git/

Hi. Could you please try the latest release? I'll be happy to add more documentation or whatever else you require to get this to work for you.


[Question] invoke a task programatically and watch completion

I have some tasks like the following:
gulp.task('build', gulp.parallel(
	'deps',
	'serve/static',
	'build/js',
	'serve/html',
	'build/css'
));

gulp.task('build:!ilbsr', function build () {
	return new Promise((resolve) => {
		WebSocketServer.isRunning(BUILD_SERVER_ADDRESS).then(() => resolve(), () => {
			console.log();
			gulp.task('build')();
		});
	});
});

And it seems ok, the only issue is that I do not know when the task is actually done, because the gulp.task('build')(); returns nothing. Is there actually a way of invoking a task within another task and somehow check when it is completed?

Pass a function to your invocation.  We do something similar at https://github.com/gulpjs/gulp-cli/blob/master/lib/versioned/^4.0.0/index.js#L66-L70

@phated thanks.


可以提供7B-Chat的Eval评测原始数据吗？

评测代码数据可以看到两位小数和细分的每项目得分
而最后给出的是一位小数和总分
虽然可以自行复现，但是如果方便提供原始数据，可以帮助大家更好地分析。

@luxtiasco 你好，想问一下你这里说的原始数据是什么呢？
如果是指我们使用的数据集的话，我们使用的都是标准测试的数据，代码开头会有下载数据的命令。


Raise max app disk space to 6gb

What
Sets the max disk space property in both places that it's needed. Sets that value to 6gb, because we have legitimate use cases for slightly bigger max disk sizes.
How to review

Deploy this branch to your dev env.
Test you can request 6gb worth of disk, both initially and in an update

cd $(mktemp -d)
echo "Hi" > index.html

cf push six-gig-app -b staticfile_buildpack -k 6G

cf push two-gig-app -b staticfile_buildpack -k 2G; cf scale two-gig-app -k 6G;

cf delete -f -r six-gig-app
cf delete -f -r two-gig-app

This is deployed in the andyhunt dev env, so you could try it there and check my pipeline. It may not be up and running when you're reviewing though.
Who can review
Anyone with a dev env

$ cf push test-6g --no-route -b staticfile_buildpack -k 6G -u process
$ cf ssh test-6g
$ df -h
vcap@5e9a6ec8-44fb-4cde-65bb-85d7:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay         6.0G  5.3M  6.0G   1% /
tmpfs            16G     0   16G   0% /dev/shm
/dev/nvme0n1p2  167G   15G  144G   9% /tmp/garden-init
tmpfs            16G     0   16G   0% /sys/fs/cgroup
tmpfs           2.8M  200K  2.6M   8% /etc/cf-instance-credentials
devtmpfs         16G     0   16G   0% /dev/tty
tmpfs            16G     0   16G   0% /proc/scsi
tmpfs            16G     0   16G   0% /sys/firmware


SAK-28084 Make it easy to add anon and auth role

Make it easy to add anon and auth role to a site using the Site Info
tool.

I've created #419 to add back the HTTP method check. I think it was in our local code as a result of a bad merge.


Remove the unused id properties from page and thumbnail canvas/image DOM elements (issue 11499)

Remove the unused id properties from page and thumbnail canvas/image DOM elements (issue 11499)
As described in the issue, having a DOM element with id=page2 (or any other number) will automatically cause that element to become linkable through the URL hash. That's currently leading to some confusing and outright wrong behaviour, since it obviously only works for pages that have been loaded and rendered.
For PDF documents the only officially supported way to reference a particular page through the URL hash is using the #page=2 format, which also works for all pages regardless if they're loaded or not.
As far as I can tell there's nothing in the PDF.js default viewer that actually depends on the page/thumbnail id at this point in time, hence why I believe that this removal ought to be safe.
Just as a pre-caution this patch adds an aria-label to the page canvas, similar to the thumbnail canvas/image, to at least keep this information in the DOM.

Add helper functions to reduce unnecessary duplication when fetching l10n messages in PDFThumbnailView

Fixes #11499

/botio-linux preview

Thank you for cleaning this up!


final-milestone: Metric App

When the page loads, the webapp shows the list of categories that could be filtered out by some parameter.
Along with the category name, some numeric values per category that come from the API are displayed.
When the user clicks (or taps) on a category item, the application navigates to the details page.
In the details page, the webapp retrieves data from the API to show detailed data in the category.
When the user clicks on the "Back" button (<), the user navigates to the home page.
Created unit tests for pure functions in Redux code.
Created integration tests for my application using the React Testing Library.
I mocked the access to the API, so that tests don't send actual requests.
I mocked the connection to the Redux Store.

STATUS: APPROVED ✔
Hi @Simpleshaikh1 ,
In my opinion, your project is ready for the presentation!  There is nothing else to say other than... it's time to merge it :shipit:

Good luck! 🎉
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.


Issues with Language Settings in Superset: Configuration Not Saved, Partial Translations, and Redirects

I am experiencing multiple issues related to the language settings in Superset:

Partial Translations and Incorrect Translations: While testing different languages, I noticed that not all parts of Superset are translated when switching from English to another language. This issue is compounded by incorrect translations, such as those shown in the attached image, where both ascending and descending order options are labeled as "orden descendente" in Spanish. This forces me to revert to English to differentiate between options. I would prefer that parts of Superset remain untranslated rather than being mistranslated.

Language Configuration Not Saved: When changing the language settings in Superset, the changes are not saved upon closing and reopening the application. For example, if the default language is English and I change it to Spanish, Superset reverts back to English after restarting. Additionally, if I open Superset in a different browser after setting it to Spanish, it also defaults back to English. This becomes problematic when multiple users are involved. If User 1 prefers Spanish and User 2 prefers English, only one default language can be set, requiring one user to change the language every time they log in. The expected behavior is that once a user changes the language setting, it should persist across sessions.
Redirect to Homepage: When changing the language, Superset redirects the user to the homepage, regardless of the current page. Although I understand that a restart might be necessary for language changes to take effect, it would be more user-friendly if the user remained on the page they were working on after the restart.

is this issue resolved?

@Suvendu-UI No, it hasn't been resolved. The issue that concerns me the most is the first one, and even with the configuration that Dosu suggested (which I already had because I read other threads), it still works partially.

Partial translations are not considered bugs, as we'll be chasing that down approximately forever. If you'd like to contribute or fix translations, we encourage you to edit the .po files and open a PR with your changes.

I haven't looked much at the other two issues, but the second one sounds legit, and maybe you can set a cookie or use localstorage to resolve this. The third, I believe, is a duplicated of another open issue. If you or I find that, we might want to close this as a duplicate... I'd encourage you to file issues separately for reasons like this :)

@rusackas Great! I’ll keep that in mind for next time and present the issues separately. Since they all relate to a common theme, I thought it made sense to present them together, but now that you mention it, you’re absolutely right to address them separately. Going back to the topic of partial translations, it’s not really the main issue I see. The bigger problem, in my opinion, is incorrect translations. As I’ve attached in the image, you can see that for ascending and descending order, it shows the same text for both, in this case, descending order. I’ve found myself more than once having to change the language because the translation wasn’t correct. What I mean is, partial translations seem great to me, and actually, being in English right now seems the most optimal at this stage of the language development.
Thank you so much, as always, for your responses!

aprendizlaura
I suggest this option, it suits me, maybe it will suit you too. This solves the problem with redirection and language change
Add it to config.py:
class SupersetIndexView(IndexView):
    @expose("/lang/<string:locale>")
    def patch_flask_locale(self, locale):
        from flask import redirect, request, session
        referrer = request.headers.get("Referer")
        session["locale"] = locale
        return redirect(referrer)

FAB_INDEX_VIEW = f"{SupersetIndexView.__module__}.{SupersetIndexView.__name__}"

@aprendizlaura I have no idea how many incorrect translations there might be in Superset, but @mistercrunch and I are interested in making the experience of contributing/mantaining these translations easier.
We're trying to find ways for both people and AI to fill in the blanks and make corrections, so we hope to follow up there in the future. For now, if you're able to open a PR with these changes (just find the string and change it in the relevant .po file) that would be helpful and appreciated.


Allow to set background color for active panel title

Currently it is possible to change the border color for the active panel title using panelTitle.activeBorder, allow a similar setting for the background color, maybe panelTitle.activeBackground.
Current

Desired

fyi a PR is up for this to address.


Create admin user after container is created

Hi @Team.
Great effort!
How can I create once an admin user as a s6/ or through an init script, during bootstrapping, after containers deployment finishes (through a docker-compose). Skipping /install step.
Thanks.

./gitea admin create-user --help

Yes, I know the command, thanks. What I need exactly is create that user
during deployment, without user manual intervention like s6/ run, setup or
finish scripts. Is it possible, where to place custom init scripts that run
once?
😉
On Fri, Aug 2, 2019, 11:00 PM Lunny Xiao<EMAIL_ADDRESS>wrote:

./gitea admin create-user --help
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/go-gitea/gitea/issues/7721?email_source=notifications&email_token=AA4GYYS3RK6473OGWEAQASDQCTYEFA5CNFSM4IJBFMK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3PFXHI#issuecomment-517888925,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4GYYQD4LIVLFCWG3JVM4LQCTYEFANCNFSM4IJBFMKQ
.

You could have the script write a lock file so that it knows it has been run?

Thanks for your response, that seems a nice option, but does gitea have any
folder where to load default init scripts in a cohesive and standard way?
e.g pre, around, after/post initialization (e.g AOP pointcuts). I tried
several options:

Bash script in /etc/init.d folder (fails)

Bash script in /etc/s6/gitea folder (fails)
exec gitea admin create-user --admin --access-token --username=**** --password=****<EMAIL_ADDRESS>--must-change-password=false"

Appending a line to /etc/s6/gitea/run or setup scripts (fails)
echo "exec gitea admin create-user --admin --access-token --username=**** --password=****<EMAIL_ADDRESS>--must-change-password=false" >> /etc/s6/gitea/run

Then, when the container is running I manually exec my script and it works
like a charm.
So, the missing step here would be using best practices for gitea and move
on,
Thanks. ;-)
El sáb., 3 ago. 2019 a las 18:26, zeripath<EMAIL_ADDRESS>escribió:

You could have the script write a lock file so that it knows it has been
run?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/go-gitea/gitea/issues/7721?email_source=notifications&email_token=AA4GYYT264LVRCCXKVCD673QCYAXPA5CNFSM4IJBFMK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3PWYEY#issuecomment-517958675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4GYYXUX6VQRSC5GW2QLUTQCYAXPANCNFSM4IJBFMKQ
.

Thanks for your response, that seems a nice option, but does gitea have any
folder where to load default init scripts in a cohesive and standard way?
e.g pre, around, after/post initialization (e.g AOP pointcuts). I tried
several options:

Bash script in /etc/init.d folder (fails)

Bash script in /etc/s6/gitea folder (fails)
exec gitea admin create-user --admin --access-token --username=**** --password=****<EMAIL_ADDRESS>--must-change-password=false"

Appending a line to /etc/s6/gitea/run or setup scripts (fails)
echo "exec gitea admin create-user --admin --access-token --username=**** --password=****<EMAIL_ADDRESS>--must-change-password=false" >> /etc/s6/gitea/run

Then, when the container is running I manually exec my script and it works
like a charm.
So, the missing step here would be using best practices for gitea and move
on,
Thanks. ;-)

This should not be added in init script for security reasons

I understand @lafriks , so what workaround can be done?

usually this would be done either manually or by some automation (ansible/chef etc)

I searched on gitea site and it does not talk on image build process?
Can you share those details, I'm trying to exhaust docker via instead doing
it from sources.
Thanks.
El lun., 5 ago. 2019 a las 10:59, Lauris BH<EMAIL_ADDRESS>escribió:

usually this would be done either manually or by some automation
(ansible/chef etc)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/go-gitea/gitea/issues/7721?email_source=notifications&email_token=AA4GYYW3KYVLJL6O57TZQYTQDA55BA5CNFSM4IJBFMK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3SCY3Q#issuecomment-518270062,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4GYYS45CSUCV5UHEP2WO3QDA55BANCNFSM4IJBFMKQ
.

It will not work in service also because only on gitea first start database structure will be initialized and I don't know if gitea cli command does that but this should be tested but you will have to preconfigure app.ini in docker image as this should be run only when gitea is fully configured
Anyway if you take into account previous issues than you could probably write docker entrypoint script to run that command and read password from docker secrets:
[ ! -f /data/admin_user_created ] && gitea .... --password=$(cat /run/secrets/gitea_admin_password) ... && touch /data/admin_user_created

I think you can create your Dockerfile and add that command there. For an official image, we cannot do that.


Purposal  sort fuzzy

Add version sort to fuzzy search of fvm use. Make the latest version to appear on top.

@jascodes I am bringing this in, but have something similar working for the GUI support, so will bring it over.
Thanks again!!

@all-contributors add @jascodes for code, ideas


Add retry mechanism for neural search inference.

Description
This feature is an enhancement to neural-search and the purpose is to improve the availability of the opensearch ml cluster. The core idea is add retry for inference operation, once a request is been sending or have sent to a ml instance which is not available now, rather than simply fail this request we use retry to improve the success rate of requests.
Issues Resolved
https://github.com/opensearch-project/neural-search/issues/92
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Retries would be useful for ephemeral issues, correct? So which exceptions would we expect to be resolved on failure like this?

Two exceptions we're going to handle are: NodeNotConnectedException and NodeDisconnectedException


RadioCommunications deserializes appears to not work

What version of Open DIS Rust is running?
0.1.0-alpha.6
What platform is your computer?
Linux 6.5.6-76060506-generic x86_64 x86_64
What steps can reproduce the bug?
dat in this example is a Vec<u8>, and if I try to deserialize it, it just says Err(InvalidDISHeader), but when I deserialize without header, it deserializes as expected.
loop {
    let dat = match conn.recv().await.unwrap();

    let mut bytes = BytesMut::from(dat.as_slice());
    let pdu_header = PduHeader::decode(&mut bytes);
    let body_data = BytesMut::from(&dat[12..]);

    match pdu_header.pdu_type {
        PduType::Transmitter => {
            // this does not work
            //let xmsn = TransmitterPdu::deserialize(bytes);

            // this *does* work
            let xmsn = TransmitterPdu::deserialize_without_header(body_data, pdu_header);
            println!("{:?}", xmsn);
            println!("{:?}", pdu_header.pdu_type);
            println!("{:?}", PduType::Transmitter);
            println!("{:?}", pdu_header);
        },
        _ => continue,
    }
}

So with
let xmsn = TransmitterPdu::deserialize(bytes);

the output is:
Err(InvalidDISHeader)
Transmitter
Transmitter
PduHeader { protocol_version: IEEE1278_1A_1998, exercise_id: 1, pdu_type: Transmitter, protocol_family: RadioCommunications, timestamp:<PHONE_NUMBER>, length: 104, padding: 0 }

But with
let xmsn = TransmitterPdu::deserialize_without_header(body_data, pdu_header);

The output is:
Ok(TransmitterPdu { pdu_header: PduHeader { protocol_version: IEEE1278_1A_1998, exercise_id: 1, pdu_type: Transmitter, protocol_family: RadioCommunications, timestamp:<PHONE_NUMBER>, length: 104, padding: 0 }, entity_id: EntityId { simulation_address: SimulationAddress { site_id: 50, application_id: 2 }, entity_id: 5 }, radio_id: 1, radio_entity_type: RadioEntityType { entity_kind: 7, domain: 0, country: 0, category: 0, nomenclature_version: 0, nomenclature: 0 }, transmit_state: 2, input_source: 0, padding1: 0, antenna_location: Vector3Double { x: 0.0, y: 0.0, z: 0.0 }, relative_antenna_location: Vector3Float { x: 0.0, y: 0.0, z: 0.0 }, antenna_pattern_type: 0, antenna_pattern_count: 0, frequency: 100, transmit_frequency_bandwidth: 25000.0, power: 40.0, modulation_type: ModulationType { spread_spectrum: 0, major: 0, detail: 0, system: 0 }, crypto_system: 0, crypto_key_id: 0, modulation_parameter_count: 0, padding2: 0, padding3: 0, modulation_parameter_list: [], antenna_pattern_list: [] })
Transmitter
Transmitter
PduHeader { protocol_version: IEEE1278_1A_1998, exercise_id: 1, pdu_type: Transmitter, protocol_family: RadioCommunications, timestamp:<PHONE_NUMBER>, length: 104, padding: 0 }

What is the expected behavior?
Transmission::deserialize should be able to take a BytesMut containing a pdu and pdu header, and deserialize it into a TranssmissionPdu
What do you see instead?
Transmission::deserialize cannot take a BytesMut containing a pdu and pdu header, and deserialize it into a TranssmissionPdu
Additional information
I have also seen this exact case with SignalPdu as well. I looked at the source code and it doesn't make sense why it would fail to detect the proper pdu_type, but for some reason that is the case. Am I doing something wrong here?

I have a hunch as to what this could be, but I'll have to test it myself. It is probably related to the lack of support currently for dynamically sized PDUs, as all of them are statically sized at this point in time. I will get back to this issue as soon as I can test it. Thanks for bringing attention to this.

I've used the library a bit more since I opened this issue and noticed that when the signal pdu has a 16 bit encoded data packets the library panics

Finally got some time to reevaluate this issue. I've been looking through the TransmitterPdu code and referencing your use case above. I have not been able to replicate the issue unfortunately. I would expect my test suite to also fail for the test radio_communications::transmitter_pdu::tests::deserialize_header unit test, but it succeeds. All I'm doing in the TransmitterPdu::deserialize() method is checking the pdu_type field in the PduHeader and returning an error code if it is not a TransmitterPdu. In your example, your debug outputs clearly show that it is a TransmitterPdu header, so I am not sure what could be happening there. I'll continue to investigate, and hopefully I'll get to the bottom of it soon.

I am going to add deserialize_without_header tests to all the PDUs that I currently have implemented. Since I am unable to replicate the issue, and since no other responses have been given here, I am going to close it. If the issue arises again in the future and can be replicated, I'll reopen and address it.


compsize: use upstream's installer

Motivation for this change
Drive-by cleanup - uses install from the Makefile instead of rolling our own.
Cc: @CrazedProgrammer
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

The formatting changes are due to nixpkgs-fmt.

with a force push since eliminating format related merge conflicts is an
explicite goal of nixpkgs-fmt.

One of the benefits of using a common formatter is that since everybody's code is formatted the same way, you're getting fewer conflicts. That's correct. However, all the code needs to be formatted by the tool in order for that to apply which it currently isn't.

One of the benefits of using a common formatter is that since everybody's code is formatted the same way, you're getting fewer conflicts. That's correct. However, all the code needs to be formatted by the tool in order for that to apply which it currently isn't.

Exactly. That's why it might be better to remove for now. Having bits and pieces of formatting is just noise in the commit at this point. If nixpkgs-fmt was currently being used tree wide, I would say it's more acceptable since it should have been conforming and wasn't. Even at that time, I'd probably still recommend it be put in a separate commit.

Exactly. That's why it might be better to remove for now. Having bits and pieces of formatting is just noise in the commit at this point. If nixpkgs-fmt was currently being used tree wide, I would say it's more acceptable since it should have been conforming and wasn't. Even at that time, I'd probably still recommend it be put in a separate commit.

The formatting change is very minor and it is totally fine to include this in another commit and we very often do this to keep the commit count reasonable. It will most likely never create a merge conflict and if we cleanly separate every change the commit count would just explode.

The formatting change is very minor and it is totally fine to include this in another commit and we very often do this to keep the commit count reasonable. It will most likely never create a merge conflict and if we cleanly separate every change the commit count would just explode.

Unaware of the consensus on this, thanks for clarifying.


R.xml.global_tracker  :  cannot resolve symbol 'xml'?

hi:
i clone this demo : google-services/android/analytics/    and when i build this demo  ,     in AnalyticsApplication.java  @ line 40 show: "R.xml.global_tracker  :  cannot resolve symbol 'xml'?"
how to fix it? thx

Looks like you are missing the configuration file, check step 2 here

Closing this issue, no response.

Added the configuration file. Then to having the same error.

Does the package name that you have provided to get the configuration file match the package name that you are using when building your app?

I found this page while also having the same problem. The reply by @silvolu helped me fix the issue. I had renamed the app package and had to recreate a new configuration file for analytics. Thanks!

I just had this issue despite having the config file. The important step is to clean the project once the file is added

Is it possible to use muiltiple application IDs (e.g. using applicationIdSuffix) with Google Analytics? When I set an applicationIdSuffix to a build variant, this error happens, and I can't put multiple versions of the config file.

I don't under stand these emails
On 27 Nov 2015 10:14, "leocadiotine"<EMAIL_ADDRESS>wrote:

Is it possible to use muiltiple application IDs (e.g. using
applicationIdSuffix) with Google Analytics? When I set an
applicationIdSuffix to a build variant, this error happens, and I can't put
multiple versions of the config file.
—
Reply to this email directly or view it on GitHub
https://github.com/googlesamples/google-services/issues/36#issuecomment-160006432
.

The problem is that when we use applicationIdSuffix, the package name of the app change, and then Google Analytics doesn't work with the "google-services.json" config file.
I have the same problem.

@johanvs this is essentially the same issue as #54, please see that discussion for some possible fixes.

Thanks @samtstern. Yes and there is a workaround in the end of the discussion.

See #54 for an update.

same issue

I had that issue. In my case, i had configured google-services.json badly. Because before, i added google-services.json file for google cloud messaging service and then i had to modified google-services.json file for google analytics service..  So you should be careful about these parameters :

You should be sure about "tracking_id"
Set "status" : 2 which is in "analytics_service".
Set "status" : 1 which is in "appinvite_service".
Set "status" : 1 which is in "ads_service".

restart Android Studio and rebuild gradle.

Its 2019, I'm having this issue. When I create such xml file, it then becomes duplicate. Making it another error.

make sure your tracker xml is placed in /res/xml not in /res/values


Retry failed uploads

We should probably retry failed uploads up to a certain threshold, just to account for the internet being slightly unreliable.

This is done now in https://github.com/RecordReplay/sourcemap-upload/pull/2


perf: improve wasm_module_deps_to_dts

100,000 iterations of the test_output test.
Before: 218ms
After: 179ms

Done: https://github.com/denoland/deno_core/pull/992


Adding software development dept. contract

Hi,
I would like to add to this repo a Software development department contract that would serve as a fictional project contract between a Software development department and Product owner/Project management department.
This contract would describe roles for every project member, suggest project team structure and describe key segments of the project development.
This contract will be based on this:
Contract draft 🔒
If you are okay with this addition, please give me some tips on the best-suited directory for this file.

cool, just add it as a PR and we can discuss it there :)
Sounds like something between "culture" and "playbooks" with (in my mind) being a little more of a playbook


Spec allows function literals in initializer list

Example code:
class C {
 final int x;
 C() : x = (){ return 42; }();
}
main() {
  print(new C().x);
}
This errs with the message:
'file:..../initcall.dart': Error: line 3 pos 13: unexpected token ')'
 C() : x = (){ return 42; }();
The grammar allows the syntax.

No milestone now: This correction will be considered as part of a larger update of grammar related parts of the specification, based on Dart.g.

Note: once this is resolved, it would probably make sense to also update the switch expression grammar since there's a similar ambiguity there, too. See: https://github.com/dart-lang/language/blob/main/accepted/3.0/patterns/feature-specification.md#function-expression-in-guard-ambiguity

Thanks for the heads-up!
The error which is reported for the original example today (DartPad, master) is a type error:
The initializer type '()' can't be assigned to the field type 'int'.

This implies that the text () { return 42; } is being parsed as an expression () (the empty record) followed by a constructor body, and the (); that follows is then parsed as the next class member declaration (that has its own syntax errors).
This is all in line with the expected behavior today. There is a rule that prevents function literals from being present in initializer elements. It has never been specified precisely, but that is being clarified now in https://github.com/dart-lang/sdk/issues/54284.
In any case, that rule was (or at least could have been) introduced in response to this issue. The initial message of this issue indicates that the grammar allowed this kind of construct, and it doesn't mention any special exceptions for initializer list elements. In other words, this issue was relevant for the language before that rule was introduced, which means Dart as of 2014 or so.
So we can close this one now, and rely on https://github.com/dart-lang/sdk/issues/54284 to clarify the rule that makes this issue obsolete.


[ENH] Extending the Bot Model Process to be Sequential

Motivation - https://github.com/rwth-acis/las2peer-social-bot-manager-service/issues/208#issuecomment-1679059808 - With how the process is structured now as a star network, a Bot Action that takes a while or fails is not able to be handled properly and the process proceeds to the next IncomingMessage regardless.
Specification - As mentioned by @lakhoune, Bot Actions would lead to a new IncomingMessage. Action Parameters would still be attached in a star structure.
Finalised state - Modeling the process in a sequential way would allow checks to be made so that if a Bot Action fails or in the case where Bot Actions are chained, if one of the Bot Actions fails, the process can be interrupted.

As we discussed before, I would see no problem in  extending the modeling language to allow for such behaviour. The existing specification woul coexist with the new one giving the bot developers the option to choose between the two.

@AlexanderNeumann Do you have any thoughts or example usages for this implementation?

I agree with Ben's comment.
I think Ben has already examples from his thesis. @lakhoune can you provide a concrete example of the mensa bot for example?
From use case scenarios, there are plenty. For example, if the response of a request (when we fetch information from a service/website etc) is relevant to the bot message. If the request fails the state should not change or go into another state (automatically).
It is also a little bit complicated because sometimes we are using webhooks if the requests are taking longer. We first directly give a response to the user that there is a longer process ongoing and when the process is finished we give the result to the user.

An example for sequential behaviour for the mensabot would be the review process.
The process looks similar to this:
'request to make review' -> 'specify canteen' -> 'specify meal' -> 'confirm choices' -> 'give stars' -> '(optional) feedback'
Currently we do this in one state for the first half 'request to make review' -> 'specify canteen' -> 'specify meal' -> 'confirm choices' and then a second half 'give stars' -> '(optional) feedback'
But it would be great to have each as an own bot action


Update contribute page with NCP's design

The tier page was initially implemented to show all the tiers available for a given collective.
Ex: https://opencollective.com/babel/contribute/

The new collective page normally has a link to it (View all the ways to contribute) but the difference in design is disturbing so we're going to remove it for now.
This issue describes the steps to re-enable this button:

[ ] Update contribute page with latest contribute cards design
[ ] Add events
[ ] Re-enable the button on the collective page

@cuiki @raulgrafico Can we get a design update on this page with the new cards for Ben to implement? thanks!

Done in https://github.com/opencollective/opencollective-frontend/pull/2561


accelerator.unwrap_model(model)

accelerator.unwrap_model only takes model as an argument
removed "keep_fp32_wrapper=True"

You need keep_fp32_wrapper to continue training when using mixed precision.


Character callback with modifiers that is ALWAYS invoked for chars with pressed mods

Hi,

initially discussed here:  https://discourse.glfw.org/t/glfw-character-text-input-with-modifier-keys-control-meta-alt/1467
GLFW version: 3.3 (on Ubuntu 19.10)

It is currently not possible to receive character events with modifiers for all characters that were typed in.
My demo was: A user is typing in Ctrl+[ in standard (en_US) keyboard layout works just fine with key as well as char callback but if you use (for example) de_DE (German[y]) keyboard layout, then in order to send a Ctrl=[, what the user has to press is Ctrl+AltGr+8. This is captured by the key callback as Ctrl+Alt+8 (which is not helpful because the user app itself SHOULD NOT re-implement keyboard layout mapping nor do I know what keyboard mapping the user has) and more importantly, the character callback is not invoked for that, neither is the character-with-modifier callback being invoked for that.
My request basically is to let the character-with-mods callback know about ALL characters being typed in with all modifiers - it also feels like a bug to me that this callback isn't invoked on non-en_US keyboard layouts (my test-case: de_DE), so I'm not sure it actually is a bug or a feature request.
p.s.: I didn't find any resource telling me why glfwSetCharModsCallback is being deprecated. It seems this is the only function that makes sense for me to use (even though it's currently not really fully working); maybe someone knows where to look at for this decision?
Many thanks in advance,
Christian.

If you take a look at the issues for glfwSetCharCallback you'll see that it didn't work for the use-case you've described.
Basically a key press such as CTRL+ALT+8 will not result in a character, so there will be no call to glfwSetCharCallback nor to glfwCharCallback. This is not because GLFW is doing something to remove it, but because no character exists to represent this key combination.
However, the key combination ALT+8 does represent a character, [ for the keyboard layout in your example.
So the solution I proposed on the forum is that we need to extent glfwGetKeyName to be able to handle translations in the presence of modifier keys. So the new version would be something like:
const char* glfwGetKeyName ( int key, int scancode, int mods );

Note that glfw would either have to ignore the CTRL mods, or users of the API would need to know that CTRL as a mod will result in no character. I would prefer the later as being more obvious.

Many thanks for clarifying.

Believe or not, working also on a C++ terminal emulator with OpenGL and facing exactly the same issue. Practically I am porting the work under https://github.com/zokrezyl/asciterm to C++.
Do we have any workaround atm? Btw. @christianparpart , would be happy to chat about your design approach if you are planning an open source implementation

Hey @zokrezyl
That sounds amazing, I think it is best to just email me if you want details. I would be happy to chat<EMAIL_ADDRESS>is how you can reach me .
But with regards to glfw. Kitty maintains its own fork and I just ported to QtGui. And to be honest, I don't regret it. :)
See you in your email,
Christian.

Hello, any updates on this?

Hello, any updates on this?

@xslendix I gave up on GLFW3 a long time ago. My way to fix all the input issues I had with GLFW was to simply move to Qt. While it may sound heavy, I only link against QtGui (and now also Qt's QML), because all I needed from it was Window creation and input handling. Qt can be quite slim. I also lately made use of QML and so far do not regret in having moved off GLFW for a project like a GUI terminal emulator. -- I keep the frontend connector code quite slim however, to be free to switch in the future just in case i feel like it must be done (again).

any more updates in 2024?

any more updates in 2024?

Port to QtOpenGL, seriously. Let go of glfw. I gave up on it. I do not regret it. :)


What is the conclusion of this benchmark?

Which framework is best for what? Could you give some hints to a manager (or six year old kid) please ;-)

Thre is no and wont be any conclusions, just metrics.


Source map error:  404

Source map error: Error: request failed with status 404
Resource URL: https://cal.netzpolitik.org/jquery.min.js
Source Map URL: jquery.min.map
something is not being found?

And you are reporting here because of....? ;-)

I was hoping to solve the issue, but as I don't have any experience with coffee script and co. thought I'd see if a developer could assist.

Just to clarify, I need a 'read only' view of multiple calendars and running caldavzap is really overkill. You project seemed like one of the few options out there ;)

Hi @poetaster ,
thanks for clarification.
I just saw caldavzap on the provided url and did not understand why you asked me about this. ;-)
You are not developer, right? BOFH seems to be more like system administrator. ;-)
.map files are just source maps, these files are not required to work, they are just helpful for debugging purposes.
In my opinion your caldav server does not work or is not compatible to my project.
If you need further assistence, i need more details. If you prefer, i can contact you via email, so you don't have to share too much details of your system setup in this issue.


routes with dot don't work when using PHP 5.4 embedded webserver

Whenever the URL includes a dot the PATH_INFO is always "/" and the correct value is located in SCRIPT_NAME... This makes Slim's routing fail.
<?php
require 'Slim/Slim.php';
$app = new Slim();
$app->get('/', function( ){
    echo "FRONT PAGE";
});
$app->get('/hello/:name', function ($name) {
    echo "Hello, $name!";
});
$app->get('/he.llo/:name', function ($name) {
    echo "HE.LLO $name!";
});
$app->run();
?>

Launch:
php -S <IP_ADDRESS>:3000 index.php
http://localhost:3000/hello/Joe will display Hello, Joe!
http://localhost:3000/he.llo/Joe will display FRONT PAGE
http://localhost:3000/hello/Joe.Smith will display FRONT PAGE

I've been trying out Slim 3 and have also ran into this issue. Note that it only occurs when you don't prefix the URL path with the router script name: e.g. it breaks when you use /foo.bar but works fine with /index.php/foo.bar.
Minimal app to reproduce:
composer.json:
{
    "require": {
        "slim/slim": "^3.0@RC"
    }
}

index.php:
<?php

require 'vendor/autoload.php';

$app = new Slim\App();

$app->get('/', function ($request, $response) {
    echo 'ROOT';
});

$app->get('/{name}', function ($request, $response, $args) {
    echo 'NAME: ', $args['name'];
});

$app->run();

PHP invocation:
$ php -v
PHP 5.5.27 (cli) (built: Aug 22 2015 18:20:44)
Copyright (c) 1997-2015 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2015 Zend Technologies
$ php -S localhost:8080 index.php

Results:

Request URI
Expected Output
Actual Output

http://localhost:8080/
ROOT
ROOT

http://localhost:8080/index.php
ROOT
ROOT

http://localhost:8080/foobar
NAME: foobar
NAME: foobar

http://localhost:8080/foo.bar
NAME: foo.bar
ROOT

http://localhost:8080/index.php/foobar
NAME: foobar
NAME: foobar

http://localhost:8080/index.php/foo.bar
NAME: foo.bar
NAME: foo.bar

Inspecting $_SERVER in the above situations makes it pretty clear that the issue is related to the fact that for the request to /foo.bar, PHP sets $_SERVER['SCRIPT_NAME'] to /foo.bar while for all other requests it sets it to /index.php.
Overriding it by setting $_SERVER['SCRIPT_NAME'] to /index.php at the top of index.php fixes the problem, but this seems like something that Slim should correct itself (note that Symfony/Silex doesn't have this issue).

It is probably related to PHP bug 61286. Built-in server will consider request as a static file request if there is a dot in the  SCRIPT_NAME.

@tuupola Yeah, I did notice that bug report, and that appears to be the root cause. Unfortunately, it doesn't look like they're going to change it (marked Wont Fix).
On a related note, I noticed that Slim's ServerRequest factory implementation differs from Zend Diactoros in how it determines the path from the environment. Slim splits the base path and only returns the path info in Uri::getPath(), while Diactoros returns the full request URI including the base path.
@codeguy What do you think? Can you duplicate it with the code above?

I'm struggling with this now and I've just thrown my hands up. I really can't believe that bug is "won't fix", but then I'm frustrated right now and perhaps not thinking it through clearly.

Overriding it by setting $_SERVER['SCRIPT_NAME'] to /index.php at the top of index.php fixes the problem ...

@chriseskow Yes, it does solve the problem of the built in webserver not matching the route, but using that solution causes the server to stop serving static files. Totally bizarre, totally frustrating, and I wish core would just fix the problem already.
/rant

@jeremykendall: I believe this can be worked around reasonably cleanly by adding a routing script to the PHP web server call and returning false for static assets. Ping me if you want more info.

Adding the following line in my public/index.php worked for me (PHP 7.2.1):
if (PHP_SAPI == 'cli-server') {
    $_SERVER['SCRIPT_NAME'] = '/index.php';
}

I  had tried (started with):
if (PHP_SAPI == 'cli-server') {
   $_SERVER['SCRIPT_NAME'] = '/index.php';
   $_SERVER['PATH_INFO'] = $_SERVER['REQUEST_URI'];
   $_SERVER['PHP_SELF'] = $_SERVER['SCRIPT_NAME'] . ($_SERVER['REQUEST_URI'] === '/' ? '' : $_SERVER['REQUEST_URI']);
}

But neither PATH_INFO nor PHP_SELF are used by Slim, so forcing SCRIPT_NAME is enough.
Other workaround which worked (but it's application might not always be possible/desired):
Instead of requesting:
http://localhost:3000/hello/Joe.Smith
request:
http://localhost:3000/index.php/hello/Joe.Smith

Adding the following line in my public/index.php worked for me (PHP 7.2.1):
if (PHP_SAPI == 'cli-server') {
    $_SERVER['SCRIPT_NAME'] = '/index.php';
}

I had tried (started with):
if (PHP_SAPI == 'cli-server') {
   $_SERVER['SCRIPT_NAME'] = '/index.php';
   $_SERVER['PATH_INFO'] = $_SERVER['REQUEST_URI'];
   $_SERVER['PHP_SELF'] = $_SERVER['SCRIPT_NAME'] . ($_SERVER['REQUEST_URI'] === '/' ? '' : $_SERVER['REQUEST_URI']);
}

But neither PATH_INFO nor PHP_SELF are used by Slim, so forcing SCRIPT_NAME is enough.
Other workaround which worked (but it's application might not always be possible/desired):
Instead of requesting:
http://localhost:3000/hello/Joe.Smith
request:
http://localhost:3000/index.php/hello/Joe.Smith

Thanks, it works!

Had same problem. Thanks for your info all! I will leave my workaround.
router.php
<?php
$path = parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH);
if (file_exists($_SERVER['DOCUMENT_ROOT'] . $path)) {
    return false;
} else {
    $_SERVER['SCRIPT_NAME'] = '/index.php';
    require $_SERVER['DOCUMENT_ROOT'] . '/index.php';
}

Launch cli-server: php -S localhost:8004 -t public_html application/tools/cli-server/router.php


Improve BadProof docs

I thought about this as well, but decided against it. As this is highly chain specific, it can be anything and I think having a more generic description here suits better.


Pod Log Issues

I want to propose three improvements for pod log.

[x] #1482
[x] #1480
[x] #1481

All implemented. So, closing the issue


Unable to open/view pdf.

Unable to display uploaded pdf files from profile page.
Unable to display pdf from search in tab.

Fix these.

I would like to work on it. Will try to update as soon as possible

Hello @manjit-hub
When I worked on the Notes Controller issue, I also solved the problem of uploading pdfs to cloudinary and in my PR, I mentioned to change the Settings on Cloudinary in order to view pdfs as by default Cloudinary restricts the viewing of PDFs.
Go to Cloudinary>Settings>Security>PDF and ZIP files delivery(At the Bottom)>Enable it.
Try this and if its still not working @Dhruv80576 can surely work on it and I would also be ready to share any insight or work on this issue.

@Shivansh-0403 thanks for letting me know this. I applied this change. Hopefully it will effect soon.

great !! issue resolved. No need to work on this @Dhruv80576


autotune de-biasing

This fixes an upward bias in the new CR autotuning from dinners that don't finish absorbing by midnight, and removes the upward bias on ISF from ignoring (slightly) positive deltas.
It also fixes a bug that was preventing ISF data from being capped by the min/max limits before being applied, and only capping it afterward.  Fixing that allows us to stop relying on the autotune ISF adjustment ratio hack, so it changes the default value to 1.0 (in preparation for removing it entirely at some future date).
CSF is also removed from the recommendations report to reduce confusion now that ISF and CR are both calculated directly (and somewhat independently).

This has now been tested against 9 individuals' NS data and seems to be giving much better results overall, and all of the results seem to converge on reasonable settings that should be safe to loop with.
At this point I'd be comfortable merging this to dev and suggesting everyone run it, and then PM me their URL etc. if they see results they don't think are right.


signals: Change the json passed to what the proxy expects

The json expected by the proxy for signal handling changed in
the new implementation. Sync the changes as the signal handling
was implemented before the protocol was fully defined and
changes were not synced.
The payload api from the proxy should be probably be vendored
in the mock proxy now, to be done in a separate commit.
Signed-off-by: Archana Shinde<EMAIL_ADDRESS>

LGTM

lgtm

lgtm


Fix $gp calculation when addiu value is negative

Would you mind adding a changelog entry and bumping the version? I'll put out another release after merging this

getImmediate is deprecated. getProcessedImmediate is preferred since it does the two complement calculation on signed instructions


Allow Required Handlers to be a multi-selection field

Current functionality is, required handlers is a list out of which only one option (or none) can be selected. This isn't quite the functionality, because handlers can be stringed together and there could be more than one handler at a time required. So it would be best if the list could turn into something from which multiple items (or none) could be selected at the same time.
Much like the "Return Allowed" list of attribute policy options.

Is "No Required Handler" still a possibility? If so, we'll have to do something like the "Return Allowed" where we have two options of a "No Handlers" radio and then another radio for "Required Handlers" with the multi-select list - since we don't want "None" in that list.

Yes. The field is optional.

Misagh

On Jul 15, 2015, at 1:24 PM, darkape<EMAIL_ADDRESS>wrote:
Is "No Required Handler" still a possibility? If so, we'll have to do something like the "Return Allowed" where we have two options of a "No Handlers" radio and then another radio for "Required Handlers" with the multi-select list - since we don't want "None" in that list.
—
Reply to this email directly or view it on GitHub https://github.com/doodelicious/cas/issues/14#issuecomment-121685849.


Add Simple Czech QWERTZ keyboard

Edit some keyboards names and mistakes

Hey. We no longer working with the branches: all language packs are now on master. I can migrate the Czech pack and then you would be able to create a new PR to add this new layout.
Sounds good?

Hi, thanks for the explanation. Please, migrate Czech pack, if you can. I'll make new PR for it.


segmentation fault 11

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

PyGObject-3.36.1 version when calling Gst.ElementFactory.make getting error segmentation fault 11 , can anybody help

I see that you don't have the gstreamer package installed, so perhaps pygobject is trying to load the library from your system, which could easily cause segfaults. Does it work if you install gstreamer in Conda?


Column reordering does not work if pinning is enabled

Column reordering does not work if enablePinning is set to true:
http://plnkr.co/edit/xbbp7e?p=preview
Also, even if enablePinning is set to false, if an individual column is marked as pinned, column reordering has bugs:
http://plnkr.co/edit/rjwola?p=preview

k


Adjust the HEALTHCHECK for prebuiltdb extension

This turns down the startup time of the container from 1m to 30s, which in most cases is sufficient for the prebuiltdb ones to be ready.

Thanks a lot for the PR, @felipecrs!
@abhisbyk, please review this PR.

@felipecrs so many changes just for a minor health interval  enhancement of 30s is not worth it.
Can you use the --health-interval 30s to your podman run/docker run command to get around this.

I can do many other things to get around this. My goal was to fix it for everyone.
The change I did on all files were to avoid hardcoding the path to the healthchecker. If you don't like it, I can simply copy the path to the healthchecker, thus making the change only on the prebuiltdb.

@felipecrs a pre-built db image also doubles up as a image which can be used to create a new DB from scratch if you provide a mount for the oradata location

That's true, but I think that defeats the purpose of the prebuiltdb extension (meaning we probably don't need to worry about supporting it, I think).

Yes, we do. The XE and Free container-registry images (container-registry.oracle.com/database/free:latest) are all pre-built with DB charset of AL32UTF8. If users need a DB with an alternate charset then we need a fresh DB to be created using the same prebuilt image.
See https://github.com/oracle/docker-images/issues/2673
At this point I don't think there is pressing need for this PR unless we see more users asking for it

Right. Thanks for the feedback.

@felipecrs thanks for understanding and your contribution.


List headers in accordion should not be links.

Actually, they need to be links. https://github.com/zurb/foundation-sites/blob/develop/scss/components/_accordion-menu.scss


[FLINK-1679] rename degree of parallelism to parallelism & extend documentation about parallelism

https://issues.apache.org/jira/browse/FLINK-1679

Very nice and exhaustive change.
One question though: do we want to just rename configuration parameters and methods like that or should we keep the old config keys (parallelization.degree.default) and the old config methods (setDegreeOfParallelism) as well and deprecate them first?
I think I am in favour of option 2.

I think this is very API breaking - in my opinion, we should keep the old methods where it breaks the API, or at least keep them for one more version (deprecated).
That does not prevent us from merging the fixes to comments and docs.

@uce @StephanEwen I agree with you two that it's better to keep the old API methods and mark them as deprecated while introducing the new ones. When the API has been stabilized and 1.0 comes up, we can remove the old methods.

I've updated the pull request to include deprecation of the setters/getters and the config parameter.

Thank you for the huge change! Our users will appreciate the more concise naming and improved documentation.
+1 to merge

Any objections against merging this?

Are we sure that this is breaking no existing API. No method on DataSet or any descendant of it has been renamed? Also not on other user facing types?

With 236 files, that is hard to assess...
That is a point, in general, with humongous pull requests that touch 10 projects at the same time.
I would personally like another +1, from someone who verified that this is not API breaking. But again, PRs of this size are not easily reviewed...

Let me explain how I made out the relevant API facing methods to deprecate. Since I changed all calls to set the parallelism to getParallelism or setParallelism I did not have to change classes which already used these methods. To find the remaining which used setDegreeOfParalleism or getDegreeOfParalleism method, I did a regexp search in the Java and Scala classes:
Java: public .* (get|set)DegreeOfParallelism
ExecutionConfig
Operator
CollectionEnvironment
ExecutionEnvironment
StreamExecutionEnvironment
SpargelIteration
Scala: def (get|set)DegreeOfParallelism
ExecutionEnvironment
StreamExecutionEnvironment
In these classes I deprecated the methods, and made them call the new methods getParallelism and setParallelism. That's how I verified this pull request is not API breaking. For you inspection, I've created a separate commit with these changes. The deprecated methods are also covered in the documentation about how to change the parallelism: http://ci.apache.org/projects/flink/flink-docs-master/programming_guide.html#parallel-execution

Any other opinions on the API breaking nature of these changes?

I think all changes that are in flink-core, flink-java, flink-scala, flink-streaming, flink-spargel are critical. For all those changes, there should be an additional method and the current one should be deprecated.
Other changes (Runtime, Optimizer, tests) can be made without any problem.
NOTE: You are also breaking the system configuration. We should change it to use the new parameter, but we should still accept the config values of the old parameter.

@StephanEwen That's exactly what I did.

Merged in master with 126f9f799071688fe80955a7e7cfa991f53c95af


Exporting constants from iOS TurboModule

Description
Hi. Not sure is it a bug, an overlook in the current documentation, or me missing something; but I just bumped into the following issue with exporting constants from a TurboModule on iOS.
I had a native module exporting constants as said here (for old arch): it overrode - (NSDictionary *)constantsToExport, and all worked fine. I am migrating it to the new arch,  with backward compatibility. When I build it and run in compatibility mode (old arch) - it still works fine; if I build and run for new arch - no constants are exported (I checked, constantsToExport is never called, and on JS side getConstants() returns null). I looked into RN documentation, have not found any mentions of changes in exporting constants for iOS TurboModules, nor in the New Arch sections, nor in Migration to the New Arch sections. I looked into the generated Specs for my TurboModule, it has these both:
- (facebook::react::ModuleConstants<JS::NativeReactNativeStaticServer::Constants::Builder>)constantsToExport;
- (facebook::react::ModuleConstants<JS::NativeReactNativeStaticServer::Constants::Builder>)getConstants;

thus I've tried to override getConstants method instead, and it then works fine for the new arch. But leaves me confused: if we are supposed to override getConstants instead of constantsToExport in the new arch, why the previous constantsToExport is still in specs? If not, why the override is not called - a bug? And why nothing is mentioned in the docs in this regard, am I missing something here?
Version
0.71.2
Output of npx react-native info
N/A
Steps to reproduce
N/A
Snack, code example, screenshot, or link to a repository
N/A

If not, why the override is not called - a bug? And why nothing is mentioned in the docs in this regard, am I missing something here?

Can you share your spec file? Also a reproducer would help here to debug what's going on

Hey @cortinico , I just wanna say, I still remember about this issue I reported, but I had no time yet to look into creating a minimal reproducer.
Though, the library I am working on is public, here: https://github.com/birdofpreyru/react-native-static-server, and the piece of code which I was refering to is this one: https://github.com/birdofpreyru/react-native-static-server/blob/3bd511dbb70bb3fc18b7b346af0db9a83c6602f8/ios/ReactNativeStaticServer.mm#L26-L36
- (NSDictionary*) constantsToExport {
  return @{
    @"CRASHED": CRASHED,
    @"LAUNCHED": LAUNCHED,
    @"TERMINATED": TERMINATED
  };
}

- (NSDictionary*) getConstants {
  return [self constantsToExport];
}

as I said, from the docs it sounds like just having constantsToExport() should make it work, but in my experience with the new arch the JS side actually calls getConstants() instead, thus I had to add that method.

I'm trying to export constants from my Turbo Module on RN 0.73 and - (NSDictionary *) getConstants is not working for me. I don't quite understand the generated code, so not sure how to create an instance of the generated constants struct:

Any help would be greatly appreciated

Codegen doesn't seem to be generating any initialization code, just another method
Here is my spec
import { TurboModuleRegistry, TurboModule } from 'react-native';

export interface Spec extends TurboModule {
  getConstants: () => {
    IOS_DOCUMENT_PATH: string;
    IOS_LIBRARY_PATH: string;
    ANDROID_DATABASE_PATH: string;
    ANDROID_FILES_PATH: string;
    ANDROID_EXTERNAL_FILES_PATH: string;
  };

  install(): boolean;
}

export default TurboModuleRegistry.getEnforcing<Spec>('OPSQLite');

Here is the generated code
/**
 * This code was generated by [react-native-codegen](https://www.npmjs.com/package/react-native-codegen).
 *
 * Do not edit this file as changes may cause incorrect behavior and will be lost
 * once the code is regenerated.
 *
 * @generated by codegen project: GenerateModuleObjCpp
 *
 * We create an umbrella header (and corresponding implementation) here since
 * Cxx compilation in BUCK has a limitation: source-code producing genrule()s
 * must have a single output. More files => more genrule()s => slower builds.
 */

#import "OPSQLiteSpec.h"

namespace facebook {
  namespace react {

    static facebook::jsi::Value __hostFunction_NativeOPSQLiteSpecJSI_install(facebook::jsi::Runtime& rt, TurboModule &turboModule, const facebook::jsi::Value* args, size_t count) {
      return static_cast<ObjCTurboModule&>(turboModule).invokeObjCMethod(rt, BooleanKind, "install", @selector(install), args, count);
    }

    static facebook::jsi::Value __hostFunction_NativeOPSQLiteSpecJSI_getConstants(facebook::jsi::Runtime& rt, TurboModule &turboModule, const facebook::jsi::Value* args, size_t count) {
      return static_cast<ObjCTurboModule&>(turboModule).invokeObjCMethod(rt, ObjectKind, "getConstants", @selector(getConstants), args, count);
    }

    NativeOPSQLiteSpecJSI::NativeOPSQLiteSpecJSI(const ObjCTurboModule::InitParams &params)
      : ObjCTurboModule(params) {

        methodMap_["install"] = MethodMetadata {0, __hostFunction_NativeOPSQLiteSpecJSI_install};

        methodMap_["getConstants"] = MethodMetadata {0, __hostFunction_NativeOPSQLiteSpecJSI_getConstants};

    }
  } // namespace react
} // namespace facebook

It seems on Android the generated code is different and getConstants is shared between the old-arch and codegen, but this is also means it is not overridable and will not work when creating modules that keep compatibility

Can’t keep myself from saying — auto-closing issues by GitHub actions is stupid and harmful — hiding dirt under the carpet doesn’t help solving the issue, if the issue remained open and visible, perhaps it helped to avoid degrading the constant problem even further 🤷♂

The amount of rubbish issues is hard to manage in a repo like react-native, I have sympathy for the maintainers. I think I will create a new issue. I managed to get it working on Android by just implementing the getTypedConstants method. But in any case, the documentation is missing. I also found this small disclaimer on the old arch modules page:

The amount of rubbish issues is hard to manage in a repo like react-native, I have sympathy for the maintainers.

That's the underlying problem @birdofpreyru
If the issue gets stale and closed by the bot, let's open a new one. If an issue has a a linked reproducer, it won't stale.
Honestly we receive so many bugs that we can't cope with the traffic so that's a necessary measure.
@ospfranco let's create a new issue for your particular case. We're specifically prioritizing New Architecture bugs as of now, so this would be really precious

ok, awesome, will create later

Hmm... I am working on migrating my up-to-date fork of react-native-fs to RN v0.73; I just got it working for Android with both new and old archs, and I haven't noticed any significant issues with constants so far (beside a lack of documentation in RN web).
On TS side I have the constants method defined as getConstants(). Codegen seems to work fine and for new arch it generates me the specs like:
protected abstract Map<String, Object> getTypedExportedConstants();

@Override
@DoNotStrip
public final @Nullable Map<String, Object> getConstants() {
  Map<String, Object> constants = getTypedExportedConstants();
  // Here codegen adds a bunch of assertion code for debug & internal builds.
  return constants;
}

so I just implement getTypedExportedConstants() function, and for the old arch I have a stub specs file that just does:
  abstract fun getTypedExportedConstants(): Map<String, Object>

  override fun getConstants(): Map<String, Any>? {
    return getTypedExportedConstants()
  }

So far so good, very curious to see how (whether) it will work for me with iOS.

Yeah, works fine for me with RN v0.73 on iOS, macOS, and Windows as well. I mean, there is no behavior changes from v0.72 to v0.73, only pre-existing issues with logic (which can be worked around) and documentation.

I also managed to get it working, there is just a lot of disparity and missing info in the documentation. @cortinico do you still want me to create a new issue?


Sidebar in mobile(responsive small mode) selects the first item on its own( without user clicking it )

Hello there.
When I was browsing the demo site(https://marmelab.com/admin-on-rest-demo/) in my mobile( chrome browser latest up-to-date ), I saw, whenever the sidebar was opened, the first item (the dashboard) got itself selected without any tapping.
Also, while tapping on the other items in the list, it was not always that the results were loaded( the page remained unchanged i.e. no action ) and the sidebar as usual closed.
Please see into it.

Can't reproduce any of those issues

It is strange because I have tried in atleast two different devices. One of them is Yu Yuphoria.

Have you tried a sample material-ui app on these phones ?

Taking your advice, I browsed http://www.material-ui.com/ (demo) in my mobile and though the UI was not that quickly working but was working as expected( without any functional disruption like admin-on-rest ).

I can confirm the issue with Chrome in simulated device mode.

So, it is a bug. Thanks to @fzaninotto.

whenever the sidebar was opened, the first item (the dashboard) got itself selected without any tapping.

In fact, I can only reproduce this prb when we are on the dashboard page. Opening the Sidebar from any other page does not select the first item automatically

Moreover, if I try to log the onTouchTap event inside the DashboardMenuItem, I do not get any log from this auto selection

hello there!
I thought it would be nice if I could add pictures of what I faced.
So here are the gifs -

Thanks but we finally reproduced it. I have spent several hours on this already but haven't find why it is happening yet.

Hello there!
Any update guys ??
BTW thanks for the efforts. :+1:

Not yet

Hello guys! Any update ?!

On a Chrome in simulated device mode, if you click quickly, the page stays (yeah, the bug). However, if your click stays a little bit longer, you go to the selected page (no bug)!
Therefore, short tap and long tap are handled differently if current page is dashboard.

The cause is that sometimes (on dashboard and products page) the touch event is sent to the MenuItem. This can be confirmed by moving down all the menu items with edited css.
A 200ms delay to show the drawer prevented this on Chome simulation.
I am not 100% sure the 200 ms works for all devices. if it doesn't, try increase it.
#698

It worked, but I increased that too 300 since 200 wasn't making any difference. That's cool.

@astriskit Please increase it to a very large value just to verify the problem is related to "the touch event sent to menu icon is also sent to the first item of the drawer".
If the delay has to be very large for some devices, then we can only fix it by not allowing drawer and its children nodes to accept events when animation is happening.

@wesley6j  Increased it till 2000 ms and the effect seems to be same, i.e., the auto-click is not triggering. But, the menu options are not loaded in chromium.

@wesley6j  Increased it till 2000 ms and the effect seems to be same, i.e., the auto-click is not triggering. But, the menu options are not loaded in chromium.

Can't reproduce it on the next branch anymore. Feel free to reopen.

Reopened as I reproduced it on the demo with the next branch


ensures that upload:complete is dispatched after upload:success or upload:failure

upload:complete is being dispatched before upload:success or upload:failure. I believe this is a bug. I want to track failed uploads and the order of events makes that tricky. I've redacted much of the code for brevity, but it should provide an idea.
class App.NewUpload
  errors: []

  template: (index, filename) ->
    """

        #{filename}

    """

  constructor: (@form) ->
    @setEvents()

  setEvents: ->
    $(document).on 'upload:failure', @form, (event) =>
      @handleFailure event.originalEvent.detail
    $(document).on 'upload:complete', @form, @handleComplete

  handleFailure: (detail) =>
    upload = @findUpload detail.index
    @errors.push upload

  handleComplete: =>
    unless @form.find('input.uploading').length
      if @errors.length
        @toggleNotice 'Warning'
      else
        @toggleNotice 'Success'

Because failure and success are fired before complete,  with only one upload, we can not track the outcome because @errors.length would be 0.

Sounds good to me! Thanks!


Just add some code doc around the use of AddXXX func to avoid any confusion

Signed-off-by: Doug Davis<EMAIL_ADDRESS>

LGTM

LGTM


UpdateServicesServer, UpdateServicesApprovalRule: Fixing Products processing, verbose output

Pull Request (PR) description

Fixed UpdateServicesServer and UpdateServicesApprovalRule

Process multiple product categories with the same name correctly (e.g. "Windows Admin Center")
Verbose output of Products only displayed one product

Fixed verbose output of Languages in UpdateServiceServer
Fixed verbose output of WSUS server in UpdateServicesApprovalRule

This Pull Request (PR) fixes the following issues

Fixes #61
Fixes #62
Fixes #63

Task list

[X] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[X] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

I think I'll need a bit of advice on how to deal with all the failed checks, as they seem to be mostly unrelated to the changes that I made. Should I ignore them? Or do they need to be fixed first, before my changes can be accepted?

Project likes dead. How can we made progression in it that the pull request are approved?

Is this project abandoned?

No, but I need to be reminded (on slack) or see the notifications.
We also need more reviewers that can eventually help maintain the repo.
I'll try to have a look this weekend.

Curious if this PR will be merged?

@NicolasBn has this been included part of your merged changes?

@TheBlackMini or @luzkenin are you able to rebase this branch and re-submit a PR.

@gaelcolas Indeed. To cover issue #61, I need to update UpdateServicesApprovalRule resource.

So, @NicolasBn do I need to do anything?

@TheBlackMini I don't have any time before next week. If you don't want to wait, you can submit your PR :)

I worked on a solution here : Get-UpdateServicesDscProduct
I created a function to find all products based on value passed on Products property.
I 'just' need to use it in UpdateServicesApprovalRule, and adapt pester tests.
It was a few month aga. So I need times to reintegrate my code :)


fix: add missing build dep and fix owner-tool location

Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

we can cut 0.2.0 after this if we all agree @puiterwijk @nullr0ute


Merge to publish.

Docs Build status updates of commit 3d81343:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/subscription-tile-e5.png
:white_check_mark:Succeeded

docs/office-365-developer-program-faq.md
:white_check_mark:Succeeded

docs/office-365-developer-program-get-started.md
:white_check_mark:Succeeded

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.


Pivot Table Conditional Formatting on Cells - Add Colour to Cells

It would be nice if there was a way to add conditional formatting to individual cells to highlight them a certain color if the value in that cell is in or out of a range etc.
This was being worked on at some point in time on older versions of Superset. #3416
However, it looks like progress stopped. Can someone champion this feature and continue what was already done?

it s works for upto 0.34 version

How do I use it?

Look the pull request for row and column configuration
https://github.com/apache/incubator-superset/pull/4394

Need that ! :)

Did this pull request ever make it into the official releases? Are we suppose to just take these extras file and add them to our config?

yes row configuration was not merged yet ,u need to configure manually to get these options

The PR says that will not be merged as it is, it needs to be converted to a plugin before.

Is someone able to convert these into a plugin. Does this PR help with this? #8222

Look the pull request for row and column configuration
#4394
Its working fine in all versions upto the current versions

I was looking into this PR and it's seen dificult to apply to the newer version of Superset.  @kalimuthu123  do you know how to apply it to release 0.34? Any help will be welcome.

i am intersted to add new features of grand total row and column here

@kalimuthu123 Have you tested this PR #4394 on versión 0.34? How do you do it?
Best

I expect the feature!

i also worked column Grand Total feature in this table chart and we have used diferent formulas for the chart @WChCh
you may also use the different library for table chart visualisation such as webdatarocks(free edition),
flexmoster(commercial)
https://www.webdatarocks.com/?r=wdr

@kalimuthu123 Have you tested this PR #4394 on versión 0.34? How do you do it?
Best

hi all, not sure if this is still relevant but I was able to apply it into the current dev version 0.999
here is the fork: https://github.com/henry145145/incubator-superset/tree/develop
(make sure pull the develop branch if you are going to clone it, the master branch is not update yet)
Most of the files from https://github.com/apache/incubator-superset/pull/4394/files can be found in the latest version except superset/assets/visualizations/pivot_table.js
I think the visualizations of the pivot table was converted to be a plugin and it was pointing from a node module library (ref: see https://github.com/apache/incubator-superset/pull/6838/files)
Inside superset/assets/node_modules/@superset-ui/legacy-plugin-chart-pivot-table, we will findPivotTable.js which is the new version of pivot_table.js.
However, I was not able to edit files in node_module.
Here is my attempt steps to solve this issue:
In dev version 0.999, superset/assets/src/visualizations/presets/MainPreset.js, it listed all the plugin and you will see
import PivotTableChartPlugin from '@superset-ui/legacy-plugin-chart-pivot-table

so instead of pointing from @superset-ui blah blah, we just need to make it point from a custom plugin folder
import PivotTableChartPlugin from '../PivotTable/PivotTableChartPlugin';

the custom plugin folder was under superset/assets/src/visualizations/. Currently filter box and time table is also from custom plugin folder. We will need to make a custom plugin folder call PivotTable which should look similar to<EMAIL_ADDRESS>we can edit the PivotTable.js inside our custom folder

Hi, is there any news about implementation of this plugin? Thanks!

would be great if we had that... will help a lot.

@henry145145, I am able to clone your forked repository and pivot table conditional formatting is working perfectly but it is not working on the latest code of superset.
After your changes superset frontend code moved to different folder superset-frontend and other changes as well. Can you please suggest a way to apply your changes on the latest code? That will be really a great help for the superset opensource community.

@piyush-singhal hi, so yeah the repo I had was very outdated compare the latest version of superset, back then there was not a folder called "superset-frontend".
and it look like "superset-fronted" is the "asset" folder that in the old repo, and I believe that the sub directory of those files are still the same, for example, incubator-superset/superset-frontend/src/visualizations/presets/MainPreset.js is the currently superset location for MainPreset.js where incubator-superset/superset/assets/src/visualizations/presets/MainPreset.js is the old location for MainPreset.js
Hence, in order to apply the changes that in from https://github.com/apache/incubator-superset/issues/3416, you will have to manually find those file and add the custom code and point superset to use the custom code, not the default library.
From my understanding, in MainPreset.js, it control which library your chart is going to use, for example, by default, pivot table type of chart is take from import PivotTableChartPlugin from '@superset-ui/legacy-plugin-chart-pivot-table';, and in order to use the custom code, we are going to point it to a custom plugin. An example would be the TimeTableChart plugin, which is default using a custom one (import TimeTableChartPlugin from '../TimeTable/TimeTableChartPlugin';).
For build the custom plugin, my old repo should have that but I would also recommend take a look at the original pivot table plugin library and use it as a template
https://github.com/apache-superset/superset-ui/tree/master/plugins/legacy-plugin-chart-pivot-table/src
I hope this help

hi all (I am @henry145145 btw, this is my second account), this is probably outdated but here is an example pull request of how I glue part of the pull request https://github.com/apache/incubator-superset/issues/3416 into branch 0.38
Notice that the example i am using is for Table chart and I did not glue the row configuration. However, I do believe that once you understand the concept, you can glue it into pivot table chart too.
Here is the pull request: https://github.com/LonelyLok/incubator-superset/pull/1
The pull request show a lot of file changes so here are some key points:

highly recommend read https://superset.apache.org/docs/installation/building-custom-viz-plugins to understand how to use custom ui plug in.
I grabbed the original table plug in from https://github.com/apache-superset/superset-ui/tree/master/plugins/plugin-chart-table as a template for my "custom" plugin (v0.15.13)
put those files in a new directory `superset-frontend/src/visualizations/CTable'
make changes on the superset-frontend/src/visualizations/presets/MainPreset.js to use the custom plugin
add superset-frontend/src/explore/components/controls/ColumnControl.jsx
edit files under CTable directory such as controlPanel.js and TableChart.js

Also, my intention of this pull request is just a "beginning guide" of how to implement https://github.com/apache/incubator-superset/issues/3416 into 0.38 branch since it seem like my last two explanation above was outdated and the mapping between old and new superset directory/files are little bit confusing.
I did zero testing on this so there might be some bug so use it at your own risk.
Here is a gif of what it look like (it took some times to load the chart when I recording it):

I hope this help. I do hope the conditional formatting feature will eventually land on the official Superset.

Hi,
This is definitely a features wiill be asking soon (actually, some are already asking).
This conditional formatting feature should be available on both pivot and raw tables (the use, UI,  and final rendering are almost the same).
Request : This feature is needed for both metrics and dimensions.

+1

+1

+1 for this, we are waiting for this for so long

+1

+1

There's condition coloring in Pivot Tables already. If people need more out of it, I'd suggest creating new Issues with bugs, or new Discussions/PRs with enhancements.


A simple sample for Jetpack Compose in Surface Duo

Also, it would be great if you could add a readme to your project folder!
You could also add your project to the CI pipeline by editing this file https://github.com/microsoft/surface-duo-app-samples/blob/main/.github/workflows/app-samples-CI.yml (basically just copy/paste what we have for the other projects and replace the path with your project's path)

@joyl1216 I've merged https://github.com/microsoft/surface-duo-app-samples/pull/37. Please, rebase your branch with main now. Thanks! :-)


error 30 Failed to remount RootFS

I have been getting this error
Errno: 30
Test: spawnAndShaihuludAndWait("/sbin/mount_apfs","/dev/disk0s1s1","/var/tmp/rootfsmnt", NULL, NULL, NULL) == 0
Filename: ViewController.m
Line: 1575
Function: exploit
Description: Failed to remount RootFS
downloaded unc0ver(proper) from ignition
IOS 11.1 Model Iphone 6s
Stuck in 21/53

@WinstonDT please spell iPhone correctly next time. It's iPhone not Iphone. Also can you post your diagnostics.plist, there's a button in the settings page of unc0ver.


Install requires a lot of space

Related to https://github.com/getodk/docs/issues/1668, for now we'll document this, but it would be great to improve.
Some drivers I can think of:

the postgres migration still being in play. We should make a plan to remove it. Maybe in mid-2024?
Enketo and Central using different node base images. Hopefully that will be addressed soon and won't need to happen again
frontend needing to be rebuilt for several config changes. Would be great if we could ship a built artifact instead.

frontend needing to be rebuilt for several config changes.

A config change specific to Frontend should be pretty rare, right? Currently that's just for SSO I believe. I think docker image prune will also recapture that space.

Ah I see, even if you change a config to Backend, Frontend will get rebuilt. But as long as docker image prune is run, won't the user be OK?

as long as docker image prune is run, won't the user be OK?

I think so "at rest"? But they'll need more space than maybe expected at some point in time. I'm not entirely sure how big the impact is.

For FMTM at HOT I bundle ODKCentral into our stack.
To do that I have a customised backendDockerfile based on the one in this repo (service.dockerfile), to optimise the build.
Building the image from this repo --> 1.2GB
Building the optimised image --> 372MB
Base Image
A good starting point is using the slim images provided by node.
The node:18.17 image is 352MB, while 18.7-slim is 75.37MB currently.
It just requires three additional packages to be installed (not bundled in slim):

gpg
procps
netcat-traditional

Efficient Layering
Dockerfile directives should be bundled together where possible for more efficient layer caching, for two reasons:

Each new directive generates a new layer. There is overhead associated with very layer, and inefficiencies when stacking multiple layers. Also if a previous layer generates temp files that are not cleaned up, then they are carried forward to the next layer.
Each layer is generated as an intermediate image during build. These bloat the filesystem (stored in the Docker image cache) & will increase the space required to actually do the build.

Frontend
I also bundle a central-frontend. It's only 74.9MB.
Contribution
Would it be useful for me to make a PR, is someone already working on this?
Also, as a separate but related issue, it would be great to have the images built and published to something like Github container registry. Is this something you would consider?
The only reason I had to generate my custom Dockerfiles is because there is no official distribution of ODK Container Images.
I build when ODK Central is updated & tag within the container registry of FMTM.
It would simplify our stack if we just used official images & contributed to updates here 😄

I just saw #546 so that answers my questions around providing pre-built images.
As for optimising the current dockerfiles to use multi-stage, efficient layer caching, and slim images, the offer is still there!

Ah yes, I forgot we weren’t on slim images! I don’t remember the details of why not but it’s great to see they may not apply anymore anyway.
Please do submit a PR with your ideal setup and let’s take a look at it together.

Going to close this for now. Using the slim images will help and then the next thing will probably be to use pre-built images.


Add Swift Package Manager Support

Why no package manager support?

Sorry for the late reply here, we now officially have SPM support with this PR merged! https://github.com/Swinject/SwinjectStoryboard/pull/136
You can use version 2.2.2 or greater with SPM.


Add Kami no Kotoba by Luschka

Song Name
Kami no Kotoba
Artist Name
Luschka
Source
Direct file download
Youtube Link
No response
Direct File Link
https://drive.google.com/file/d/1ds2fVvqPkpCM6iHod8lCw75ieudBjrSz/view?usp=drivesdk
Song ID
509162
Start Offset [ms]
No response
Extra
Created from Auto Nong.
Created for level: 64658786

google drive links are not supported. I suggest uploading it to YouTube or using the original song from YouTube


Verify first-interaction action

Hi @ni3-kdm Just a question?
Why did you remove the greetings.yml Is this the github-action that is causing the issue?

@ni3-kdm please share your findings as the description. Also curious if this will be resolved by upstream if we just wait for sometime

Hi @ni3-kdm Just a question?
Why did you remove the greetings.yml Is this the github-action that is causing the issue?

Just verifying the changes, whether it's happening due to greetings.yml file or npm version. We are not merging this PR. I'm closing this PR. The root cause of this checks failing is in first-interaction. We should wait for their PR to merge. For now, we should disable first-interaction action from our repo actions.

@ni3-kdm since this is going on for sometime, lets just remove it for the time being