larger input fields in the desktop layout ?

hello, and thanks for your great work ...
on my desktop, i don't see any difference between mobile and desktop layouts for the server settings ; for some plugins (like erland custom scan) one have to enter a comma separated list which can potentially be quite long, but only 2-3 terms are visible so it' s not very comfortable and frustrating as there is more space in the screen ...
which enhancement could be done ? might the input fields be larger and/or multiline in the desktop layout ? or at least have a tooltip to see all the text if too long for the field?
thanks in advance for your reply

Just installed Custom Scan so that I could see the issue. Yeah, some fields are small. But then I checked with the default web UI skin, and they are small too.
Material does not set the size of these fields - only a min size and a max size (which is the view width - 32px). Its up to the plugin author to decide what width of text field they want.


Please include Version.java in VERSION_REPLACEMENT_FILENAMES

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
I would like to have a robust way to embed my client's version in the client. This is necessary to enable DirectPath despite customer applications shading client artifacts.
Describe the solution you'd like
I would like to add a Version.java file to bigtable client and it be auto updated during release. Currently I either have rely on resource filtering gymnastics or hijack the existing allowlist entry for GoogleUtils.java
Describe alternatives you've considered

Using resource filtering gymnastics to populate files with a version from a maven property. This is pretty clunky and will probably cause issues when importing in g3
Using the already allowlisted GoogleUtils.java. This is a bit hacky and intended for a different audience.

Additional context
https://github.com/googleapis/java-bigtable/pull/451

@igorbernstein2 @chingor13, I believe we'd actually need to make this change here:
https://github.com/googleapis/release-please


Brazilian Portuguese Translation

Hello, i'm a student of Computer Science at Rio Grande do Norte State University in Brazil.
I've been working on a translation to Brazilian Portuguese with a friend. We'd like to contribute to your repo translating the whole articles. I've made a fork and if you check my github you'll see that we've already started translating.
Thanks in advance.

That's awesome! Please make a pull request if you'd like to have your translation added to this repo

Should I make a pull request regularly or just when I finish everything?

Regularly is probably better

Okay, thanks for the answer.


RHIDP-4158: fix(ui): hide menu items with no title in sidebar nav

Description
Menu items should be hidden when title is not defined, instead of showing an empty row in menu.
Which issue(s) does this PR fix

Fixes RHIDP-4158

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[x] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[x] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer
https://github.com/user-attachments/assets/bccef970-1c97-4cc3-80b6-35771cd73d4d

/retest

/retest

/retest

/retest

/test e2e-tests

/test e2e-tests

/override ci/prow/e2e-tests


prowlarr: <IP_ADDRESS>44 -> <IP_ADDRESS>85

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for prowlarr is: Indexer manager/proxy built on the popular arr .net/reactjs base stack
meta.homepage for prowlarr is: https://wiki.servarr.com/prowlarr
meta.changelog for prowlarr is: https://github.com/Prowlarr/Prowlarr/releases/tag/v<IP_ADDRESS>85
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS>85 with grep in /nix/store/17v7ispzlf1fykhmfzqi9ixcnl7hdalf-prowlarr-<IP_ADDRESS>85
found <IP_ADDRESS>85 in filename of file in /nix/store/17v7ispzlf1fykhmfzqi9ixcnl7hdalf-prowlarr-<IP_ADDRESS>85

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

prowlarr

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/17v7ispzlf1fykhmfzqi9ixcnl7hdalf-prowlarr-<IP_ADDRESS>85 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A prowlarr https://github.com/r-ryantm/nixpkgs/archive/5736cebc5c14b9596a6be0cdd586ae4b8a32f036.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5736cebc5c14b9596a6be0cdd586ae4b8a32f036#prowlarr

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/17v7ispzlf1fykhmfzqi9ixcnl7hdalf-prowlarr-<IP_ADDRESS>85
ls -la /nix/store/17v7ispzlf1fykhmfzqi9ixcnl7hdalf-prowlarr-<IP_ADDRESS>85/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

prowlarr

Maintainer pings

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Looks good to me, deployed to my home lab and working fine.


DLL Exception Error

Does Yolo work with Asp.net Core? I am using Yolo in a Asp.net Core 2.2 environment on Windows 10. I am seeing the following error:
DllNotFoundException: Unable to load DLL 'x64\yolo_cpp_dll_cpu.dll' or one of its dependencies: The specified module could not be found
Here is my MVC Controller action:
    public IActionResult TestYolo()
    {
        string imgPath = contentRootPath + "\\wwwroot\\images\\input.jpeg";
        string configFile = contentRootPath + "\\wwwroot\\data\\yolov2-tiny-voc.cfg";
        string weightFile = contentRootPath + "\\wwwroot\\data\\yolov2-tiny-voc.weights";
        string nameFile = contentRootPath + "\\wwwroot\\data\\voc.names";

        using (var yoloWrapper = new YoloWrapper(configFile, weightFile, nameFile))
        {
            var items = yoloWrapper.Detect(imgPath);
            //items[0].Type -> "Person, Car, ..."
            //items[0].Confidence -> 0.0 (low) -> 1.0 (high)
            //items[0].X -> bounding box
            //items[0].Y -> bounding box
            //items[0].Width -> bounding box
            //items[0].Height -> bounding box
        }

        return View();
    }

please try the alpha package Install-Package Alturos.Yolo -Version 3.0.2-alpha

After I installed version 3.0.3-alpha there is now a different issue - the debugging process crashes.  The browser window closes and debugging stops.

Have you some information in the event log? what the output if you start the website with dotnet run

You may close this issue. It is not important for me to get this to work. I was simply experimenting and comparing it to Yolo.

You may close this issue. It is not important for me to get this to work. I was simply experimenting and comparing it to DLib.


Incorrect traffic_light initialization in green_wave_env.py

Choose an option
This is a:

[ ] Question
[ ] Feature request
[x] Bug report

Describe the issue
In green_wave_env.py, line 101:
            for i in range(self.rows * self.cols):
                self.k.traffic_light.set_state(
                    node_id='center' + str(i), state="GGGrrrGGGrrr")

This assumes three traffic lights per edge, which is not correct. Running this results in three green lights in on three edges and one red light which is clearly not intended. Should be changed to 'grgr'.

hi @FarshadKoohifar thanks for the catch! I'll create a PR about this now


all: remove support for OS X 10.8 and 10.9

Per discussion on #23011, Go 1.11 will remove support for OS X 10.8 Mountain Lion and OS X 10.9 Mavericks. This issue is to remember to do that, and to document it in the Go 1.11 release notes.

@andybons documented it in https://tip.golang.org/doc/go1.11#ports
So closing this.


Azure static webapp with WS02 as custom identity provider - redirect from ws02 to staticwebapp does not work after the

Describe the issue:
Hi,
I have deployed an Azure static web app using WS02 with OIDC as custom identity provider. Unfortunately the logout process won't redirect back to Azure static web app.
Does someone have any experience using Azure static webapp with WS02
Kindly regards
JB

Hi,
Is there any updates?

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Vertical spacing for form with both p.text-help and p.text-muted is broken

A form layout we use very regularly is an input with a help-text below which also can have an error message.
Right now, the error case looks like this:

IMO the spacing is broken, it should look like this:

The generated html for this case is:

  Name
  <input class="string required form-control-lg form-control" placeholder="Name" type="text" value="" name="registration[name]" id="registration_name">

can't be blank

Lorem

A possible css fix might be something like this:
p.text-help ~ p.text-muted {
  margin-top: -16px;
}

Note: I cannot just add a .m-b-0 in this case since the html is generated by simple_form which has no way of distinguishing those cases.
Questions:

Is there a "proper" way to write this kind of form? What would be a better alternative to the P-Tags that uses the default-font-sizing but not the P-Tag-Margins?
Is this a usage that should be fixed in Bootstrap4 with specific css or should I work around it in my custom css?

Improvements coming in #19141.


Unable to combine mixins for collection

It is possible to combine many simblie mixins (like Setter mixin) for a collection like this
Style Key="StyleDialogButtonRefresh" {
	TargetType: RadButton
	#Setter("Content", resource "ContentRefreshSmall")
	#Setter("MinWidth", 100)
}

but when mixin contains 'combine' keyword like following
mixin DialogBasic() for Style {
	combine Setters: [
		@ASetter("HorizontalAlignment", "Stretch") {}
		@ASetter("Margin", resource "CoolMargin") {}
	]
}

it is unable to use constriction below
Style Key="StyleDialogButtonRefresh" {
	TargetType: RadButton
	#Setter("Content", resource "ContentRefreshSmall")
	#Setter("MinWidth", 100)
	#DialogBasic()
}

It is necessary to use syntax
combine Setters: [
	@ASetter("Content", resource "ContentRefreshSmall") {}
	@ASetter("MinWidth", 100) {}
]
#DialogBasic()

with alias definition
alias ASetter(property, value, targetName=none)  {
  Setter { Property: $property, Value: $value, TargetName: $targetName }
}

Is this possible to make this a little bit simpler?

Well, one solution would be to define DialogBasic as such:
mixin DialogBasic() for Style {
  #Setter("HorizontalAlignment", "Stretch")
  #Setter("Margin", resource "CoolMargin")
}

You initial problem is that you are using both implicit content property and property assignments. Basically what is generated:
<Style>
  <Setter />
  <Style.Setters>
    <Setter />
  </Style.Setters>
</Style>

I think XAML parser just doesn't like that. I mean theoretically Ammy could have hard-coded rules for that. Like if there is Setters assignment inside a Style, then move all setters there.


How to use it?

Dont know how to use this. I have Fusion solar in my browser, but cant see anything like the KIOSK thing u refere to.
Installation guide could be better.

@Picorama feel free to help me with improving the documentation.
I have added a FAQ section with information on how to retrieve the kiosk url: https://github.com/tijsverkoyen/HomeAssistant-FusionSolar#where-can-i-find-the-kiosk-url


pixi environment are recognised as "global" by pip

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
$ pixi run pip --require-virtualenv freeze
ERROR: Could not find an activated virtualenv (required).

Issue description
With --require-virtualenv flag, pip refuses most operation unless a virtual environment is detected, such as to avoid installing stuff globally by mistake.
This issue happened to me because:

I have PIP_REQUIRE_VIRTUALENV=1 set globally.
maturin develop calls into pip behind the scenes

Workaround: explicitly set PIP_REQUIRE_VIRTUALENV to zero (which is easy enough for us as the maturin call is actually behind a task).
Expected behavior
Ideally, pip would think it's ok to install stuff in pixi-managed environments (though there might obviously be implications that I ignore).

It is an issue with any conda environment, and not only pixi ones. See for instance https://stackoverflow.com/questions/54263894/how-do-i-allow-pip-inside-anaconda3-venv-when-pip-set-to-require-virtualenv
Using tasks seems like a good way around the issue.

This issue is inherent to conda environments as explained by @olivier-lacroix . Closing this for now as won't fix.


Make the method abstract on the Bridhe pattern

Make the method abstract instead of empty method

Merged, thanks for the fix and sorry for letting you wait so long to get it merged!


update(docs): Minor improvements to the your-first-plugin guide

Made all ' changed to ’.
Made all important code examples use code highlight.

Birthday cake breaking mobile UI:

In my last fix commit, it removes it.


[WFCORE-787] Discard any management model changes before beginning ro…

…llback
See http://lists.jboss.org/pipermail/wildfly-dev/2015-July/004170.html
After James Perkins reported WFCORE-788, which looks to be a flaw with the WFCORE-787 fix, I debugged how operations were executing and realized the support in AbstractOperationContext  for the no-longer used recursive execution mode was making the logic far too error prone. So I decided to clean that up, and filed WFCORE-792. The second commit in this PR is for that.

Windows Build 1622 is now running using a merge of 40168e5537a2b7039070efa273e8863547a2f970

Linux Build 2084 is now running using a merge of 40168e5537a2b7039070efa273e8863547a2f970

Core - Full Integration Build 1218 is now running using a merge of 40168e5537a2b7039070efa273e8863547a2f970

Windows Build 1622 outcome was SUCCESS using a merge of 40168e5537a2b7039070efa273e8863547a2f970
Summary: Tests passed: 3348, ignored: 62 Build time: 0:32:25

Linux Build 2084 outcome was SUCCESS using a merge of 40168e5537a2b7039070efa273e8863547a2f970
Summary: Tests passed: 3348, ignored: 62 Build time: 0:34:42

Core - Full Integration Build 1218 outcome was SUCCESS using a merge of 40168e5537a2b7039070efa273e8863547a2f970
Summary: Tests passed: 2924, ignored: 371, muted: 1 Build time: 0:47:51

Hold while I sort WFCORE-788.

Windows Build 1627 is now running using a merge of 292e1b2c86e846334c5a78d37ca2e85f11d6d499

Linux Build 2089 is now running using a merge of 292e1b2c86e846334c5a78d37ca2e85f11d6d499

Core - Full Integration Build 1224 is now running using a merge of 292e1b2c86e846334c5a78d37ca2e85f11d6d499

Windows Build 1627 outcome was SUCCESS using a merge of 292e1b2c86e846334c5a78d37ca2e85f11d6d499
Summary: Tests passed: 3348, ignored: 62 Build time: 0:32:26

Core - Full Integration Build 1224 outcome was SUCCESS using a merge of 292e1b2c86e846334c5a78d37ca2e85f11d6d499
Summary: Tests passed: 2927, ignored: 371 Build time: 0:47:55

Linux Build 2089 outcome was FAILURE using a merge of 292e1b2c86e846334c5a78d37ca2e85f11d6d499
Summary: Execution timeout (new); tests passed: 3002, ignored: 47; org.wildfly.core:wildfly-core-testsuite-domain Build time: 1:00:08
Build problems:
Execution timeout
Process exited with code 137

Core - Full Integration Build 1225 is now running using a merge of 5db8c3ee2e8f0d69e79a98d2d62544d3373385a2

Windows Build 1628 is now running using a merge of 5db8c3ee2e8f0d69e79a98d2d62544d3373385a2

Linux Build 2090 is now running using a merge of 5db8c3ee2e8f0d69e79a98d2d62544d3373385a2

Windows Build 1628 outcome was SUCCESS using a merge of 5db8c3ee2e8f0d69e79a98d2d62544d3373385a2
Summary: Tests passed: 3348, ignored: 62 Build time: 0:32:22

Linux Build 2090 outcome was SUCCESS using a merge of 5db8c3ee2e8f0d69e79a98d2d62544d3373385a2
Summary: Tests passed: 3348, ignored: 62 Build time: 0:34:02

Core - Full Integration Build 1225 outcome was SUCCESS using a merge of 5db8c3ee2e8f0d69e79a98d2d62544d3373385a2
Summary: Tests passed: 2926, ignored: 371, muted: 1 Build time: 0:48:14

Core - Full Integration Build 1226 is now running using a merge of 03628e05bffeff6dd9ed527099ddd1477f2de8d7

Windows Build 1629 is now running using a merge of 03628e05bffeff6dd9ed527099ddd1477f2de8d7

Linux Build 2091 is now running using a merge of 03628e05bffeff6dd9ed527099ddd1477f2de8d7

Windows Build 1629 outcome was SUCCESS using a merge of 03628e05bffeff6dd9ed527099ddd1477f2de8d7
Summary: Tests passed: 3348, ignored: 62 Build time: 0:32:45

Linux Build 2091 outcome was SUCCESS using a merge of 03628e05bffeff6dd9ed527099ddd1477f2de8d7
Summary: Tests passed: 3348, ignored: 62 Build time: 0:34:20

Core - Full Integration Build 1226 outcome was FAILURE using a merge of 03628e05bffeff6dd9ed527099ddd1477f2de8d7
Summary: Tests failed: 113 (113 new), passed: 2703, ignored: 367, muted: 1 Build time: 0:49:03
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.web.SimpleWebTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.registry.RegistryTestCase: <no details avaliable>

org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredQueue: <no details avaliable>

org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredTopic: <no details avaliable>

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: <no details avaliable>

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed: <no details avaliable>

org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeExecutionDisabledTestCase: <no details avaliable>

org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeTestCase: <no details avaliable>

##### there are 103 more failed tests, see build details

Core - Full Integration Build 1227 is now running using a merge of 03628e05bffeff6dd9ed527099ddd1477f2de8d7

Core - Full Integration Build 1227 outcome was SUCCESS using a merge of 03628e05bffeff6dd9ed527099ddd1477f2de8d7
Summary: Tests passed: 2928, ignored: 367, muted: 1 Build time: 0:48:24


fix: use of replacer to fix the circular ref issue with .stringify()

The issue is that parsing the swagger schema object can take a lot of circular references in certain cases. Then we are stringifying it in openapi-to-kong plugin. However, JSON does not support circular reference (see this). The MDN suggests a simple arrow function to track the reference of what's already read as a replacer function to be passed in JSON.stringify() method. I attempted to use it, and this fixed the issue.
It's probably fine to use the WeakSet way suggested by MDN for now unless we want to find a specific library to stringify that handles circular dependency.
Before this fix:

After this fix:

@dimitropoulos this is a case that is stringifying what's parsed. 'ignore' was added to actually skip the circular reference check.
Swagger doc also suggests to use a custom replacer function when serializing a dereferenced api as JSON.

The use of bundle method instead of validate method is also suggested, but this will attach all the internal references and seems it may need a bigger scope.
Now, we can possibly look for a library as I mentioned in the PR description.

It's probably fine to use the WeakSet way suggested by MDN for now unless we want to find a specific library to stringify that handles circular dependency.

I would be fine looking for a library now to stringify with circular reference support. Please feel free to leave any suggestion.
@Tieske I am not sure if this needs test coverage on the Kong configuration as the code usage seems to be limited to the declarative configuration. Please feel free to educate me where it is used for Kong configuration since I am still new to the codebase. Test case is in progress.

After investigation, these two libraries seem to be good candidates if we really want to pick a library for it. However, one still requires "replacer" function and the other is bigger than what we need. I am not sure if this is necessary. I would be keen to look at any suggestion.
https://github.com/davidmarkclements/fast-safe-stringify
https://github.com/WebReflection/flatted

@Tieske I am not sure if this needs test coverage on the Kong configuration (if you meant for Kong for Kubernetes) as the code usage seems to be limited to the declarative configuration. Please feel free to educate me where it is used for Kong configuration since I am still new to the codebase. Test case is in progress as I mentioned.

The typical circular reference is in the JSON schema. These schemas will be passed on when the Kong request-validator is configured. So the output should also get the circular references for the validator to do its job. So imo; yes, it will need a test case.
To enable that Kong plugin add x-kong-plugin-request-validator: {} to the root of the document, see https://github.com/Kong/openapi2kong/blob/master/examples/learnservice_oas.yaml#L55 (that repo is deprecated, but the example is still valid)


Update m365-dr-workload-other.md

Made changes to reflect Yammer vs viva engage
Fixes https://github.com/MicrosoftDocs/microsoft-365-docs/issues/12277

@JohanFreelancer9 Please copy review

@kelleyvice-msft Gentle reminder


hi

thank you

this is 7coil isn't it

yes. yes it is.

new command idea: mattparker, shows a random picture of matt parker


Reason for removing jsons-schema resolver?

I see the feature was merged, but reverted in short order.
Can't seem to find a reason for this.
Would appreciate an insight into what happened?

We had difficulty getting it to work at the time from memory, the package itself is quite old and hard to get it working with our build, I would recommend building a custom resolver at your own app.

We had difficulty getting it to work at the time from memory, the package itself is quite old and hard to get it working with our build, I would recommend building a custom resolver at your own app.

thanks for the quick turnaround. will do.

thanks for the quick turnaround. will do.

thanks for understanding.

thanks for understanding.


need Help to Install additional drivers

Hi. In our Forum we wanna try to run Chimera on PS4. It's still an idea yet. But in past there were many Arch Linux on ps4linux. I wanna try these drivers https://github.com/whitehax0r/ArchLinux-PS4-Drivers.
For the first steps i need to Install wget, git etc. but pacman seems not working.

The system is immutable. But you can unlock it (until next update) with:
sudo frzr-unlock
That is good for testing things. Once you have it figured out, you can create your own fork with the packages you need by following these instructions:
https://github.com/ChimeraOS/chimeraos/wiki/Development#forking

Hi. In our Forum we wanna try to run Chimera on PS4. It's still an idea yet. But in past there were many Arch Linux on ps4linux. I wanna try these drivers https://github.com/whitehax0r/ArchLinux-PS4-Drivers.
For the first steps i need to Install wget, git etc. but pacman seems not working.

Keep me posted on your progress. I'm rather interested in seeing if the community can get ChimeraOS running on the PS4.

Yeah, sure. First i have to battle with llvm-14.06. I will update you.


Two smaller bug fixes for DE time and number parsing

See commit messages for details:

Fix a bug in time rules (00.00. is not a valid date)
Fix a bug in parsing float number with thousand separators.

Pls. let me know if you agree with the general change for the latter to use NumberFormat.parse instead of performing string replacements and use Double/parseDouble instead. If you dislike it, I would change back to string replacement for the bug.

Thanks a lot!


Automatic tweets

We can make the bot automatically tweet when a new recording is online. To not make is too monotonous, we should have a handful of tweet templates, similar to how https://twitter.com/plotocop does it.
Are there any other things that we can automatically tweet?
Please leave possible tweet formulations as replies—in order for this to not sound too automatic, it's good to rotate through a few templates.

@greplova to make progress here, can you please apply for a developer account for virtsciforum (via https://developer.twitter.com/en/apply-for-access)


if.yaml:9-13: Strange Output of the IfAgent. The output...

The puzzle 404-a600311d from #404 has to be resolved:
https://github.com/objectionary/opeo-maven-plugin/blob/5d9295d319f44e65dfad71ce8e9d5d7657011035/src/test/resources/agents/if.yaml#L9-L13
The puzzle was created by volodya-lombrozo on 21-Aug-24.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@yegor256 Currently the following java code
if(0L > 1L){
  //iftrue
}

(bytecode instructions:  LCONST_0, LCONST_1, IF_ICMPGT LABEL:iftrue)
is transformed to the following eo code:
  *
    long
      00-00-00-00-00-00-00-00
    .gt
      long
        00-00-00-00-00-00-00-01
    .if
      label
        69-66-74-72-75-65
      nop

It looks...strange. What would be the best eo representation of the if statement? Could you help please?

@0pdd Thank you for reporting a new bug! 🐛 As per our team policy, you've earned 16 points for this valuable contribution. Your diligence helps improve our project's quality. If you notice anything else in the repository that doesn't look up to par, please don't hesitate to report it. Keep up the great work! Your current balance is now 11 points.

@0pdd Thank you for reporting a new bug! 🐛 As per our team policy, you've earned 16 points for t...

I see you're talking to me, but I can't reply since I'm not a chat bot.

@0pdd Thank you for reporting a new bug! 🐛 As per our team policy, you've earned 16 points for t...

I see you're talking to me, but I can't reply since I'm not a chat bot.


First time transferring Kas token

Hi team, I'm using @okxweb3/coin-kaspa, in the example:
let wallet = new KaspaWallet(); let p: CalcTxHashParams = {     data: {"transaction":{"version":0,"inputs":[{"previousOutpoint":{"transactionId":"ec62c785badb0ee693435841d35bd05da9c8a40aa2d568dddb0dd47410e7e78a","index":1},"signatureScript":"411687d956de8e3cc53b9dbf20ede3922b422595abbad31ecf38ff90c0cf8ef7c3b5ae71628e041a3a0f1b9ad6e14bb6d49dd7c35f06c46316b67c10d477c29ac001","sequence":0,"sigOpCount":1}],"outputs":[{"scriptPublicKey":{"version":0,"scriptPublicKey":"200395c7c9703e0ff81596043f0a5e00684f860a1ab0f24c5a94931d1e0d94c4beac"},"amount":587700}],"lockTime":0,"subnetworkId":"0000000000000000000000000000000000000000"},"allowOrphan":false}, }; let txId = await wallet.calcTxHash(p);
I don't know How do I get the "transactionId" when I don't have any transactions?

Hi team, I'm using @okxweb3/coin-kaspa, in the example:
let wallet = new KaspaWallet(); let p: CalcTxHashParams = { data: {"transaction":{"version":0,"inputs":[{"previousOutpoint":{"transactionId":"ec62c785badb0ee693435841d35bd05da9c8a40aa2d568dddb0dd47410e7e78a","index":1},"signatureScript":"411687d956de8e3cc53b9dbf20ede3922b422595abbad31ecf38ff90c0cf8ef7c3b5ae71628e041a3a0f1b9ad6e14bb6d49dd7c35f06c46316b67c10d477c29ac001","sequence":0,"sigOpCount":1}],"outputs":[{"scriptPublicKey":{"version":0,"scriptPublicKey":"200395c7c9703e0ff81596043f0a5e00684f860a1ab0f24c5a94931d1e0d94c4beac"},"amount":587700}],"lockTime":0,"subnetworkId":"0000000000000000000000000000000000000000"},"allowOrphan":false}, }; let txId = await wallet.calcTxHash(p);
I don't know How do I get the "transactionId" when I don't have any transactions?

Hey there @ClarkLusm !
I hope your issue has been resolved by now. If not, I sincerely apologize for the delayed response. It appears that you're experiencing a transcript error. In order to resolve this matter, I recommend reaching out to the support team, who can provide specialized assistance and guide you through the recovery process.
I've already created a support ticket for you under the ID KSP7638, which you will need to provide when contacting them. You can access the recovery guidelines and additional help by visiting this link: Kaspa Wallet Dapps Support Ticket Requests.
Once on the page, you'll find a live chat bubble in the bottom right corner. Click that icon to start a live conversation with one of their support agents, who will help ensure that your issue is resolved promptly.
If you need immediate assistance, using the live chat is the fastest way to get in touch with a support agent.
Thank you for your patience, and I hope this gets resolved for you soon!

@Dapssupport11
Thanks for supporting!

Kaspa is a UTXO system similar to BTC. If you don’t have assets, you cannot transfer them out or construct transaction data. You can first obtain the assets of the chain and then construct the transaction or use false transaction data.


adonis4 disable csrf protection

According to doc, this should disable csrf, but it works anyway
  csrf: {
    enable: false,
    methods: ['POST', 'PUT', 'DELETE'],
    filterUris: [],
    cookieOptions: {
      httpOnly: false,
      sameSite: true,
      path: '/',
      maxAge: 7200
    }
  }

Yes, it's a bug. Will push the fix soon

Fixed and release as @adonisjs/shield:1.0.3

enable: false results in 500 for me:
E_INVALID_MAKE_STRING: Ioc.makeFunc expects a string in module.method format instead received App/Controllers/Http/Api/v1/SessionsController


Change the model name in the Spleen seg example dataset to model.ts

This is to avoid confusion as the .pt and .ts are used by some model sources to distinguish PyTorch and TorchScript model files, e.g. Clara MMAR.
A new dataset zip file has been uploaded to Google drive, and the Jupyter notebooks in the tutorials have been updated to download the new zip file and use the updated model file name. The original dataset zip file is still available on the Google drive, in case existing version of the Spleen Seg Jupyter notebook is used.
Noted again that Jupyter notebooks 04 and 05 copied some steps from the Spleen Seg; the duplication inevitably causes duplicated effort when the source changes.
Signed-off-by: mmelqin<EMAIL_ADDRESS>

@MMelQin do you mind updating the comment with links to both new .zip and old in the Google shared folder? Easier to follow the PR.
Also please, add labels and move to 0.3? Thanks!

@dbericat Please see file changes in this PR; the zip link is encoded, adding them in the comment does not help much at all. The diff shows exactly what have changed.

My bad @MMelQin. You are right. Thanks!


Problem doing the setup at the 'npm run prep' step

First I want to thank you for making deeplearn.js available. I have been waiting for such a GPU-capable js-based deep learning system since Karpathy's ConvNet.
While going through the Getting Started guide trying to set it up, I got stucked at the npm run prep step with the following errors:

$ npm run prep

<EMAIL_ADDRESS>prep /mnt/ml/tests/deeplearnjs
 npm install && bower install && mkdirp dist

npm WARN deprecated<EMAIL_ADDRESS>..psst! While Bower is maintained, we recommend Yarn and Webpack for *new* front-end projects! Yarn's advantage is security and reliability, and Webpack's is support for both CommonJS and AMD projects. Currently there's no migration path, but please help to create it: https://github.com/bower/bower/issues/2467
npm WARN<EMAIL_ADDRESS>No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@types/lodash):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: EEXIST: file already exists, mkdir '/mnt/ml/tests/deeplearnjs/node_modules/.staging/@types/lodash-321a893a/mapValues'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: File exists: /mnt/ml/tests/deeplearnjs/node_modules/.staging/@types/lodash-321a893a/mapValues
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/remap-istanbul):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, open '/mnt/ml/tests/deeplearnjs/node_modules/.staging/remap-istanbul-3e55a54e/tmp/remap-html-report-inline/support/inlinesource.ts.html'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/shelljs):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, chmod '/mnt/ml/tests/deeplearnjs/node_modules/.staging/shelljs-c180d202/src/grep.js'

npm ERR! path /mnt/ml/tests/deeplearnjs/node_modules/.staging/bower-30447fb7/lib/node_modules/ansi-regex/readme.md
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/mnt/ml/tests/deeplearnjs/node_modules/.staging/bower-30447fb7/lib/node_modules/ansi-regex/readme.md'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR!  Exit status 254
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prep script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!
Please help.

Turns out likely to be my own doing. Somehow the npm and bower installations on my system were kind of messed up.
Issue closed.

Awesome, glad you found the fix.
Sorry we were late to getting to this, let us know if you have any more problems :)


version to 1.4.0-SNAPSHOT

Codecov Report

Merging #2003 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2003      +/-   ##
============================================
- Coverage     50.21%   50.19%   -0.03%
  Complexity     1979     1979
============================================
  Files           400      400
  Lines         12349    12349
  Branches       1275     1275
============================================
- Hits           6201     6198       -3
- Misses         5691     5693       +2
- Partials        457      458       +1

Impacted Files
Coverage Δ
Complexity Δ

...mework/apollo/portal/component/PortalSettings.java
65.07% <0%> (-4.77%)
5% <0%> (ø)

Continue to review full report at Codecov.

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

Coverage decreased (-0.02%) to 53.899% when pulling 5a11683895ee4289ae2696523159b50c2aadf1d9 on nobodyiam:1.4.0-SNAPSHOT into c5eb3259edb129ada0ee2b943f8baa9e5811fad1 on ctripcorp:master.


Python version for installation

Hi, sorry to disturb haha. When I cloned the repo and tried to follow the instructions on ReadMe, the installation of the requirements.txt always fails. I tried using Python 2.7, Python 3.8 and Python 3.6, but Python 3.8 failed to install scipy==1.2.1, Python 2.7 and Python 3.6 failed to install faiss_cpu==1.6.3.
Thus, I wonder could u pls offer me some help on more details(like the python version) of installation? Thank you so much! : )
System: Windows 10
IDE: PyCharm Community 2020.01

Hello, can you please share the error log so that I can help you out? The codebase was tested with python 3.7.


Credentials issue

Hey,
thanks for that package first. I try to log through /api/login/social/session/ as explained in the doc but I got the following error: 401 {"detail":"Authentication credentials were not provided."}
I know it is due to django rest framework that is expecting some credentials but how am I supposed to handle that? I don't have credentials to provide because this is what the route is suppose to return me.
My settings look like this

REST_FRAMEWORK = {
    'DEFAULT_PERMISSION_CLASSES': (
        'rest_framework.permissions.IsAuthenticated',
    ),
    'DEFAULT_AUTHENTICATION_CLASSES': (
        'rest_framework_jwt.authentication.JSONWebTokenAuthentication',
    ),
}

Hi, Alexis!
Have you tried /api/login/social/jwt/ url to login?

Same behaviour on /api/login/social/jwt/
If I remove the REST_FRAMEWORK from my settings.py I got {"detail": "Not found."}

The problem can be caused by invalid input data.
Please take a look at example project in this repo, does it work for you?

OK problem was that I did not put the social.backends.facebook.FacebookOAuth2 in AUTHENTICATION_BACKENDS
But new problem sorry... Now I got error 400 without error message. My payload is provider ("facebook") and code that I get from here https://developers.facebook.com/tools/debug/accesstoken for the corresponding facebook app.
After some debugging I see that this Exception is thrown : https://github.com/st4lk/django-rest-social-auth/blob/master/rest_social_auth/views.py#L110
I guess this is because it cannot create new user (the access_token I provide in my payload is not linked with any user account so I expect it to create a new user)

Could you please confirm me that this package should return JWT token just from a facebook access_token and create new user if no user exists with that facebook account?
This was not so clear for me in your documentation

The flow is the following:

Javascript get the code from facebook
Javascript POST this code to django application
django application exchange this code to access token (using this package). Then using this access token get user data (email) from facebook; get or create the user in database; generate jwt; return it
Later, javascript can use this token in requests (same as session id)

So you need to submit the code, not the access token.
I can suggest to read this article. Two strategies of OAuth 2.0 are described there, and current project use "OAuth 2.0 with server".
Please try the example project, does it works for you?

OK thank you for these explanations. I think the problem comes from the
fact that I submit access_token ans I should send authorization code
instead. I'm using ng-cordova-oauth to get the access_token but this does
not provide the autorization code, I'll have a look at your website +
google thanks
On Sun, Mar 6, 2016 at 3:41 PM, Alexey Evseev<EMAIL_ADDRESS>wrote:

The flow is the following:

Javascript get the code from facebook
Javascript POST this code to django application
django application exchange this code to access token (using this
package). Then using this access token get user data (email) from facebook;
get or create the user in database; generate jwt; return it
Later, javascript can use this token in requests (same as session id)

So you need to submit the code, not the access token.
I can suggest to read this article
http://www.lexev.org/en/2015/oauth-step-step/. Two strategies of OAuth
2.0 are described there, and current project use "OAuth 2.0 with server".
Please try the example project, does it works for you?
—
Reply to this email directly or view it on GitHub
https://github.com/st4lk/django-rest-social-auth/issues/19#issuecomment-192900625
.

Alexis,
have you solved the problem?

Yes I'm using django-rest-framework-social-oauth2 that allows me to do what
I need. Thanks
Le sam. 2 avr. 2016 23:56, Alexey Evseev<EMAIL_ADDRESS>a
écrit :

Alexis,
have you solved the problem?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/st4lk/django-rest-social-auth/issues/19#issuecomment-204809131

Ok, i think we can close the issue in that case.


luci-app-nft-qos: move limit_mac_enabled

fix luci error

Can you please describe what is actually the problem here? I can't do much with update.

@feckert
using such a configuration results in an error
`config default 'default'
option limit_enable '1'
option limit_type 'dynamic'
option dynamic_bw_down '100'
option dynamic_bw_up '100'
option limit_mac_enable '1'
option priority_enable '1'
option priority_netdev 'lan'
`

Interesting, I don't understand the problem. Why it should work after this change. It should also work before the change.

Interesting, I don't understand the problem. Why it should work after this change. It should also work before the change.

It is because of this code:
https://github.com/openwrt/luci/blob/ff8e6a3772a01cd87059c6bedf77d7ca40d9bed2/applications/luci-app-nft-qos/luasrc/model/cbi/nft-qos/nft-qos.lua#L197-L199
The s (section) variable is overwritten with another CBI section definition only if option limit_enable '1' is set, afterwards the o = s:taboption("limitmac", Flag, "limit_mac_enable", translate("Limit Enable"), translate("Enable Limit Rate Feature")) declaration fails because s now refers to another CBI section, not the one with the declared tabs. Moving the option declaration further up indeed fixes this.

@jow- thanks for your explanation
@qiuzi Please update your commit message with luci-app-nft-qos: fix lua trace by moving limit_mac_enabled option.
Also add a proper Signed-off-by. Have a look at the other commits.

@feckert Submit it, I'm familiar with these

Please read my comments in my previous post!

Update your commit message with luci-app-nft-qos: fix lua trace by moving limit_mac_enabled option.
Also add a proper Signed-off-by. Have a look at the other commits.
Also squash your commits to one, so we have only one change commit.

@feckert I use the web version of github to submit and can't use Signed-off-by


Add support for overriding schema building options and tests for supporting non-standard content-types

Depends on https://github.com/Zooz/api-schema-builder/pull/24 being merged first, feature-complete otherwise.

@kibertoad as https://github.com/Zooz/api-schema-builder/pull/24 was merged and released, you can now use the official version.

@kobik Yeah, it almost works now, but I'm currently blocked by https://github.com/Zooz/api-schema-builder/pull/26 😂

@kobik I believe it is ready for review now!


[Bug]: Segmentation fault when restarting/reloading polybar

Checklist

[X] I have read the appropriate section in the contributing guidelines
[X] I believe this issue is a problem with polybar itself and not a misconfiguration on my part
[X] I have searched for other open and closed issues that may have already reported this problem
[X] I have checked the known issues page for this problem.
[X] I have followed the debugging guide to narrow down the problem to a minimal config.

Steps to reproduce
Run kill -9 $(pgrep polybar) ; polybar -c ~/.config/polybar/test.cfg -r main & a few times in a row.
I believe the issue is related with the new tray module.
I only started experiencing these crashes after switching from the old tray system due to the deprecation warnings.
Minimal config
[bar/main]
;monitor = ${env:MONITOR:HDMI1}
width = 100%
height = 20
;offset-x = 1%
;offset-y = 1%
radius = 1.0
fixed-center = false

background = ${colors.background}
foreground = ${colors.foreground}

line-size = 1
line-color = #fff

border-size = 2
border-color = #00000000

padding-left = 0
padding-right = 1

module-margin-left = 1
module-margin-right = 1

font-0 = fixed:pixelsize=10;1
font-1 = unifont:fontformat=truetype:size=8:antialias=false;0
font-2 = siji:pixelsize=10;1
font-3 = Noto Emoji:scale=15:antialias=false;0

modules-left = i3
modules-right = tray

cursor-click = pointer
cursor-scroll = ns-resize

[module/i3]
type = internal/i3
format = <label-state> <label-mode>
index-sort = true
wrapping-scroll = false

label-mode-padding = 2
label-mode-foreground = ${colors.foreground}
label-mode-background = ${colors.primary}

label-focused = %index%
label-focused-background = ${colors.background-alt}
label-focused-underline = ${colors.blue}
label-focused-padding = 1

label-unfocused = %index%
label-unfocused-padding = 1

label-visible = %index%
label-visible-background = ${self.label-focused-background}
label-visible-underline = ${self.label-focused-underline}
label-visible-padding = ${self.label-focused-padding}

label-urgent = %index%
label-urgent-background = ${colors.alert}
label-urgent-padding = 1

[module/tray]
type = internal/tray
tray-padding = 1

[global/wm]
margin-top = 5
margin-bottom = 5

Polybar log
otice: Loading module 'tray' of type 'internal/tray'
notice: Loaded 2 modules
notice: Loaded font "fixed:pixelsize=10" (name=Fixed, offset=1, file=/nix/store/2n3gp57bb21vq93ca0817b5g2ip5n2fy-font-misc-misc-1.1.3/lib/X11/fonts/misc/6x10-ISO8859-1.pcf.gz)
error: tray: Failed to unembed window '' (0x2e00890)
error: tray: Failed to setup tray client '' (0x2e00890) removing... (XCB_WINDOW (3))
error: tray: Failed to unembed window '' (0x127573f)
error: tray: Failed to setup tray client '' (0x127573f) removing... (XCB_WINDOW (3))
error: tray: Failed to unembed window '' (0x0600a4b)

# Stack trace and error log collected by systemd:

Apr 12 14:50:03 magnetar xsession[128875]: error 140: BadRegion request 138 minor 14 serial 9845787
Apr 12 14:50:03 magnetar xsession[128875]: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 9852286
Apr 12 14:50:12 magnetar xsession[128875]: error 140: BadRegion request 138 minor 14 serial 9907108
Apr 12 14:50:12 magnetar xsession[128875]: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 9912069
Apr 12 14:50:12 magnetar xsession[128875]: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 9912455
Apr 12 14:50:12 magnetar xsession[128875]: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 9912456
Apr 12 14:50:12 magnetar xsession[128875]: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 9913212
Apr 12 14:50:12 magnetar xsession[128875]: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 9913213
Apr 12 14:50:12 magnetar xsession[128875]: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 9914695
Apr 12 14:50:12 magnetar xsession[128875]: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 9914696
Apr 12 14:50:13 magnetar systemd-coredump[142819]: [🡕] Process 142767 (polybar) of user 1000 dumped core.
                                                   Module libcap.so.2 without build-id.
                                                   Module libmp3lame.so.0 without build-id.
                                                   Module libmpg123.so.0 without build-id.
                                                   Module libogg.so.0 without build-id.
                                                   Module libopus.so.0 without build-id.
                                                   Module libvorbisenc.so.2 without build-id.
                                                   Module libvorbis.so.0 without build-id.
                                                   Module libFLAC.so.12 without build-id.
                                                   Module libsystemd.so.0 without build-id.
                                                   Module libsndfile.so.1 without build-id.
                                                   Module libkeyutils.so.1 without build-id.
                                                   Module libkrb5support.so.0 without build-id.
                                                   Module libcom_err.so.3 without build-id.
                                                   Module libk5crypto.so.3 without build-id.
                                                   Module libkrb5.so.3 without build-id.
                                                   Module libunistring.so.5 without build-id.
                                                   Module libbrotlicommon.so.1 without build-id.
                                                   Module libxcb-render-util.so.0 without build-id.
                                                   Module libdbus-1.so.3 without build-id.
                                                   Module libpulsecommon-16.1.so without build-id.
                                                   Module libzstd.so.1 without build-id.
                                                   Module libgssapi_krb5.so.2 without build-id.
                                                   Module libssh2.so.1 without build-id.
                                                   Module libidn2.so.0 without build-id.
                                                   Module libnghttp2.so.14 without build-id.
                                                   Module libXdmcp.so.6 without build-id.
                                                   Module libXau.so.6 without build-id.
                                                   Module libexpat.so.1 without build-id.
                                                   Module libbrotlidec.so.1 without build-id.
                                                   Module libbz2.so.1 without build-id.
                                                   Module libxcb-shm.so.0 without build-id.
                                                   Module libxcb-render.so.0 without build-id.
                                                   Module libXrender.so.1 without build-id.
                                                   Module libXext.so.6 without build-id.
                                                   Module libX11.so.6 without build-id.
                                                   Module libpng16.so.16 without build-id.
                                                   Module libz.so.1 without build-id.
                                                   Module libgcc_s.so.1 without build-id.
                                                   Module libstdc++.so.6 without build-id.
                                                   Module libxcb-xrm.so.0 without build-id.
                                                   Module libxcb-cursor.so.0 without build-id.
                                                   Module libpulse.so.0 without build-id.
                                                   Module libnl-3.so.200 without build-id.
                                                   Module libnl-genl-3.so.200 without build-id.
                                                   Module libmpdclient.so.2 without build-id.
                                                   Module libasound.so.2 without build-id.
                                                   Module libjsoncpp.so.25 without build-id.
                                                   Module libxcb-xkb.so.1 without build-id.
                                                   Module libxcb-composite.so.0 without build-id.
                                                   Module libxcb-randr.so.0 without build-id.
                                                   Module libxcb-image.so.0 without build-id.
                                                   Module libxcb-util.so.1 without build-id.
                                                   Module libxcb-icccm.so.4 without build-id.
                                                   Module libxcb-ewmh.so.2 without build-id.
                                                   Module libxcb.so.1 without build-id.
                                                   Module libfreetype.so.6 without build-id.
                                                   Module libfontconfig.so.1 without build-id.
                                                   Module polybar without build-id.
                                                   Stack trace of thread 142767:
                                                   #0  0x00000000006260e0 _ZNK7polybar4tray6client6mappedEv (polybar + 0x2260e0)
                                                   #1  0x000000000054c8d0 _ZNK7polybar4tray7manager11calculate_wEv (polybar + 0x14c8d0)
                                                   #2  0x000000000054d0b9 _ZN7polybar4tray7manager17recalculate_widthEv (polybar + 0x14d0b9)
                                                   #3  0x000000000054d9b8 _ZN7polybar4tray7manager11reconfigureEv (polybar + 0x14d9b8)
                                                   #4  0x00000000005330d7 _ZNK3xpp1x5event10dispatcherIRN7polybar10connectionEEclINS_5event8registryIS5_JNS_5randr9extensionENS_9composite9extensionENS_3xkb9extensionEEE7handlerEEEbT_RKSt10shared_ptrI19xcb_generic_event_tE.isra.0 (polybar + 0x1330d7)
                                                   #5  0x0000000000534a29 _ZNK7polybar10connection14dispatch_eventERKSt10shared_ptrI19xcb_generic_event_tE (polybar + 0x134a29)
                                                   #6  0x000000000048b0d0 _ZN7polybar10controller7conn_cbEv (polybar + 0x8b0d0)
                                                   #7  0x00000000004a5439 _ZN7polybar9eventloop10PollHandle13poll_callbackEP9uv_poll_sii (polybar + 0xa5439)
                                                   #8  0x00007f95f524f2ea uv__io_poll (libuv.so.1 + 0x242ea)
                                                   #9  0x00007f95f523c8d0 uv_run (libuv.so.1 + 0x118d0)
                                                   #10 0x00000000004a66be _ZN7polybar9eventloop4loop3runEv (polybar + 0xa66be)
                                                   #11 0x000000000048d55f _ZN7polybar10controller11read_eventsEb (polybar + 0x8d55f)
                                                   #12 0x000000000048e994 _ZN7polybar10controller3runEbNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEb (polybar + 0x8e994)
                                                   #13 0x000000000044c40c main (polybar + 0x4c40c)
                                                   #14 0x00007f95f4a3efce __libc_start_call_main (libc.so.6 + 0x27fce)
                                                   #15 0x00007f95f4a3f089 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x28089)
                                                   #16 0x000000000044f915 _start (polybar + 0x4f915)

                                                   Stack trace of thread 142776:
                                                   #0  0x0000000000000000 n/a (n/a + 0x0)
                                                   ELF object binary architecture: AMD x86-64

Expected behavior
No segmentation fault
Actual behavior
Segmentation fault. Especially when replacing an existing polybar instance screenchange-reload = true
Window Manager and Version
i3 version 4.23
Linux Distribution
NixOS 23.11
Polybar version
polybar 3.7.0

Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) +composite +xkb +xrm +xcursor

Build type: Release
Compiler: /nix/store/ihhhd1r1a2wb4ndm24rnm83rfnjw5n0z-gcc-wrapper-12.3.0/bin/g++
Compiler flags:  -O3 -DNDEBUG -Wall -Wextra -Wpedantic -Wdeprecated-copy-dtor -Wsuggest-override
Linker flags:  -Wall -Wextra -Wpedantic -Wdeprecated-copy-dtor -Wsuggest-override  -Wall -Wextra -Wpedantic -Wdeprecated-copy-dtor -Wsuggest-override

Additional Context / Screenshots
No response

I can't reproduce this myself unfortunately. Which applications were running in your tray at the time? This behavior probably depends on how those applications interact with polybar.
Looking at the code, I found one issue that may cause this. I have fixed that in #3112, feel free to try it out and see if it fixes things.

Tried the patch and repeated the steps and couldn't replicate the segfault.
From this quick test it looks like the patch fixes the issue. Thanks!

Nice, thanks for testing. Glad this was an easy fix, tray stuff usually is anything but


Danfo.js benchmarks?

Hello!
I have a few quick questions!
Are there any performance benchmarks of danfo.js? I am trying to decide if Danfo would be faster than vanilla JS operations for groupings, getting distinct values by column, and joins. How does memory consumption compare?
Also, which TF.js backend is used when running in the browser (Chrome)? Does danfo.js block the main DOM thread when used in the browser?
Thanks!
-Alex

Some answers to your questions.

There are no performance official benchmarks for now. Most operations (especially mathematical ops) should be faster because we're using tfjs under the hood.
In the browser, we are using @tensorflow/tfjs, it's optimised with webgl and makes math ops faster as well.
Most functions are asynchronous, and should not block the main thread.

@opeyemibami can you do some benchmarks comparison between danfojs ops and vanilla Js?

On this topic, it would be very interesting to see how/if mentioned Danfo operations benefit from the tfjs wasm backend (https://www.npmjs.com/package/@tensorflow/tfjs-backend-wasm). If you benchmark, please include that in the benchmarks! :)

On this topic, it would be very interesting to see how/if mentioned Danfo operations benefit from the tfjs wasm backend (https://www.npmjs.com/package/@tensorflow/tfjs-backend-wasm). If you benchmark, please include that in the benchmarks! :)

A related topic would be memory requirements.
I'm only minimally familiar with pandas and don't know how they do it, but how are large datasets affecting memory usage? If I have a 10MB json and apply a few transforms on it that return new data frames each time, is any stream processing used that Node is very famous for, for example?

I'm just doing a spike with danfo, and came across this post.
I might be missing something, but I have this spike:
https://codesandbox.io/s/danfojs-sandbox-ivyzk
A simple groupBy with lodash takes 53ms, and with danfo 42s.
What am I missing?
t1 53.80000001192093
t2 42480.09999996424


Project status

Hi,
Is this project actively maintained? seem to be a lot of open issues and PRs left to rot
Are the owner not interested in the project, or simply overwhelmed by the popularity?
Can the owner (@troolee) maybe use some help, from me or from some of the other active contributers
Best!

+1

+1

+1
I've been waiting for v0.2.4 for past couple of months.

+1

ping @troolee :)

+1 I got here because the original gridster looks dead too.

+1 I've sent @troolee also an email.

I almost feel like we may need to make a new "official" fork. With more maintainers/contributors. I e-mail him as well back in December. I never got a reply.

I've made a fork that we can continue work on :)
https://github.com/jippi/gridstack.js
poke me if you want commit-bit :)

+1

I've updated my fork to be an actual organization, to lift it above just one person / alias :)
let me know if you want to have commit-bit to that :)

I see the issue got closed without any explanation.
@jippi I see your fork. Have you applied any changes/pr to it or is it a mirror to this repo?

See #290 where @troolee has indicated that he's back to working on cleaning things up.

@str i just forked it directly from this repo yesterday

@genachka its great @troolee is back, but history show that the project is larger than him - would be great if he could share commit-bit to other contributers as well, so the project got less risk of stalling for 6months+ again :)

+1

@jippi I completely agree that this should be opened to additional committers. Whether he opens that up here, or on one of the forks like the one mentioned in #316, I agree it should be done. It would be a shame to continue having this happen on a project that has good potential.

I've setup slack chat https://gridstackjs.slack.com so if someone is interesting to be a part of the project — you're welcome. I would like to discuss the project milestones and main goals. So we can be on the same page.
To join: http://gridstackjs.troolee.com


Compilation fails on Debian Bullseye amd64 (gcc version 10.2.1)

Info

Which version of Pi are you using: N/A
Which github revision of software: e649a01
Which board version: N/A
Which computer is the RaSCSI connected to: None

Describe the issue
Compilation fails on Debian Bullseye amd64 (gcc version 10.2.1) with the error messages below.
(This relates to adding Bullseye support to https://github.com/akuker/RASCSI/pull/819.)
#12 22.03 g++ -O3 -Wall -Werror -DNDEBUG -Wno-psabi -std=c++17 -iquote . -D_FILE_OFFSET_BITS=64 -MD -MP  -DFMT_HEADER_ONLY -DCONNECT_TYPE_FULLSPEC -c ./devices/scsi_printer.cpp -o obj/fullspec/scsi_printer.o
#12 26.31 ./devices/cfilesystem.cpp: In member function 'void CHostFilename::SetEntryName()':
#12 26.31 ./devices/cfilesystem.cpp:1094:20: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
#12 26.31  1094 |    m_dirHuman.add[i] = *p++;
#12 26.31       |    ~~~~~~~~~~~~~~~~^
#12 26.31 In file included from ./devices/cfilesystem.cpp:23:
#12 26.31 ./devices/cfilesystem.h:207:8: note: at offset [2, 10] to object 'Human68k::dirent_t::add' with size 10 declared here
#12 26.31   207 |   BYTE add[10];   ///< +12 File name addition (PADDING 0x00)
#12 26.31       |        ^~~

Replication steps:

Install Debian Bullseye amd64 on a VM
apt install git sudo
Add pi user (in sudo group)
Switch to pi user
git clone https://github.com/akuker/RASCSI.git --branch develop
cd RASCSI && ./easyinstall.sh
Select option 10 (standalone RaSCSI)

Alternatively:
git clone https://github.com/nucleogenic/RASCSI.git --branch docker-dev-environment
cd RASCSI/docker
OS_ARCH=amd64 OS_VERSION=bullseye docker compose build --progress=plain rascsi

I also tried Debian Bullseye arm32v7 (gcc 10.2.1) and Ubuntu 22.04 amd64 (gcc 11.2.0), but I was unable to replicate the issue.
Any help, hints or advice would be much appreciated.

@nucleogenic Your platform is not a supported build platform. I'm afraid I therefore have to reject this ticket, because we cannot test building on any available Linux platform. Supported platforms are Raspian and Ubuntu.
IMHO the error message is wrong. In case you think ithe message is correct and you can fix the problem, please do so and create a PR.

We could probably look at cleaning up that file at some point. The Sharp X68000 specific host device hasn't been tested in a long, long, long time, and at this point, we don't have any way to test or support it. So... any functionality that just supports the Human OS could be removed (IMO)

Even though I closed this ticket I have not forgotten that it exists ;-). The problem the compiler reports (only on this platform it seems, but whether gcc warns about something or not appears to change with gcc versions) reminds me of some of the SonarCloud issues reported for cfilesystem.cpp.
I am probably not good enough in juggling with pointers, because for some of the reported issues I could not figure out whether the code is right or wrong, i.e. whether a pointer might point to unallocated memory or not. But usually SonarCloud is right and there are code issues, indeed.
The complete Human OS code is a mess, and it is responsible for almost all remaining SonarCloud issues.

@nucleogenic And yet one more comment: Have you already tried clang++ instead of g++? On my Linux PC I switched from g++ to clang++ for compiling RaSCSI because clang++ is about 30% faster, which is a lot. clang++ might accept the offending code.

@uweseimet Now compiling OK on Bullseye with clang++, so the Docker patch file workaround is no longer needed. This will be removed shortly 😎


Don't Merge! Regression PR perf testing with metadata validation

Docs Build status updates of commit df8ea6f:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit df8ea6f:
:clock10: Full build: the average full build time is 28 min(s) 30 sec(s), this is based on the last 2 build(s) for this repository.

Docs Build status updates of commit df8ea6f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

azuresmps-4.0.0/include/sb-deprecation.md
:warning:Warning
View (azuresmps-4.0.0)
Details

azuresmps-4.0.0/include/aa-deprecation.md
:warning:Warning
View (azuresmps-4.0.0)
Details

TestingPullRequest.md
:white_check_mark:Succeeded

azuresmps-4.0.0/include/sb-deprecation.md

[Warning] Missing attribute: title. Add a title string to show in search engine results.
Line 11: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.
Line 12: [Suggestion] Link 'https://docs.microsoft.com/en-us/powershell/module/azurerm.servicebus' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

azuresmps-4.0.0/include/aa-deprecation.md

[Warning] Missing attribute: title. Add a title string to show in search engine results.
Line 11: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

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.


Improve the performance of report name generation

This speeds up the report name generation by about 200%. I tested this on an account with 4,000 reports. Before the change, it took 30ms to generate all the report names. After this change, it only takes 10ms.
Fixed Issues
$ https://github.com/Expensify/App/issues/11609
Tests

Have an account with several chats with other users
Some of the users should have first and last names, while others shouldn't
Verify in the LHN that the report names look correct. For people with names, the names should be shown, for people without names, their email/phone should be shown

[ ] Verify that no errors appear in the JS console

QA Steps
Same as the tests above

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

### Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

I ran into some really fundamental problems with the optionlistutils, so I am putting this back into draft mode to see if I can figure it out.

OK, I figured it out and this is good to go again.

Durn conflicts :'(

Actually will probably wait to test till conflicts are resolved, so I don't have to retest :D

Oops, just noticed this PR
I don't have the bandwidth right now, could you unassign me please?

Shucksadoodle, I'm not able to test this on all platforms today, but most likely will be able to tomorrow 🙏

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

### Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

99.9% sure I saw the green checkmark indicating all tests were passing 🙃

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @Beamanator in version: 1.2.24-0 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.2.24-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.2.24-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.2.24-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

This PR has been linked to a regression reported here: https://github.com/Expensify/App/issues/12487
The fix was kind of simple and the mistake we made was that we changed a method signature and didn't update a usage.
One thing we can learn from this is to be hyper vigilant about method signature changes and always double check that any usages of a function are updated.
We also would have caught this automatically if we used some kind of type checking like TypeScript.

Good catch @marcaaron , definitely good idea to be hyper vigilant about method signature changes, even when reviewing 👍


Add Python 3.6 to the testing

Python 3.3 goes EOL today but leave it in for good measure.

https://docs.python.org/devguide/index.html#branchstatus

Codecov Report

Merging #463 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #463   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          14     14
  Lines        3189   3189
  Branches      229    229
=====================================
  Hits         3189   3189

Continue to review full report at Codecov.

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

Thanks @cclauss!  We've actually got an existing PR https://github.com/crsmithdev/arrow/pull/429 that will be merged shortly that adds 3.6.  Please comment on that PR if there's something else you'd like changed.
We always appreciate the PRs.  Cheers!


haveEquipped Alice Army Card Failing Test

Noticed that have_equipped() counts the Alice Army Card in the card sleeve as equipped even when the card sleeve itself is not equipped.
Haing done some digging around, this behaviour also seems to be the case for the stickers on the scratch 'n' sniff sticker sword, and the folders in the folder holder. These are all $slots that are technically within equippable items.
However, in my testing, it does not appear to be the case with regards the skin & spur that are equipped to the "your cowboy boots" relevant slots - these appeared to never count as equipped, even when the "your cowboy boots" were equipped.
Not sure whether this is expected or wanted behaviour, but figured I'd query it, as it feels like it should be made consistent in some fashion at least. I would definitely prefer things in these equippable slots do not count as equipped when the equipment holding the slot is not equipped, but shrugs
Only managed to do a failing test as my Java is rudimentary at best and I am still trying to get some way to understanding the mafia codebase

Nice start. I assume you have a development environment set up and can actually build.
Your code is failing code formatting standards.
Fix it like this:
./gradlew spotlessapply
Run just your (file of) tests:
./gradlew test —tests=EauipmentManagerTest

Also, I like assertTrue and assertFalse as appropriate.

Haha I prefer assertThat! Though I do wish there was a isTrue matcher

Also, I like assertTrue and assertFalse as appropriate.

Haha I prefer assertThat! Though I do wish there were an isTrue matcher

Any test that increases coverage, logically or as measured, is fine whether it uses my preferred idiom or not :-)
That said, I tend to shy away from "==" because I have dealt with buggy code with a typo that used "=".  Similarly I think about x.equals() because I have tried to use it when x is null.  So assertEquals and assertNotEquals are my preference if equal is the comparison.  If I already have a boolean I will use assertTrue or assertFalse.  If I need anything else the complexity of the test is likely to be pushing the bounds of my expertise :-)

In any case what do we think about this @kolmafia/staff. Is this intended behaviour? I can see both sides to be honest.

Me too. It is the only way to tell which card is in your card sleeve. If you don’t have the card sleeve equipped, we already do not count the card in your active modifiers.
If a script is considering using a card sleeve, it already has to know that you have one and be willing and able to equip and configure it.
The maximizer can do that. But if it doesn’t know what card is currently in the sleeve, how will it deal with it?
What benefit is had by declaring a card to be unequipped unless the sleeve itself is equipped?
If you want consider which cards are available, in order to see which one is in the sleeve, you’d  have to equip it in order to look.
I don’t think that is an improvement.

If I had concept of something being equipped I would expect it to mean that the thing was equipped and that is was providing "benefits".  So I am inclined towards

things in these equippable slots do not count as equipped when the equipment holding the slot is not equipped

understanding that

What benefit is had by declaring a card to be unequipped unless the sleeve itself is equipped?

is answered with some vague statement about consistency and meeting my expectations given the name of the function.
If there is some idiomatic use where equipment is checked in order to determine some kind of configuration I am not in favor of breaking that but would be interested in a FR that provided a more direct answer.

Additional thought.
This is from api.php:
"equipment":{"hat":"10804","shirt":"10702","pants":"10596","weapon":"10920","offhand":"8437","acc2":"5460","acc3":"1795","container":"10242","familiarequip":"9138","fakehands":0,"cardsleeve":0},
"stickers":[0,0,0],
"folder_holder":["22","26","20","00","00"],

I have no sticker sword, my card sleeve is empty and in storage, and my folder holder is in storage.
I pulled the card sleeve, slid a card into it.
I pulled the folder holder.
I made a sticker sword.
"equipment":{"hat":"10804","shirt":"10702","pants":"10596","weapon":"10920","offhand":"8437","acc2":"5460","acc3":"1795","container":"10242","familiarequip":"9138","fakehands":0,"cardsleeve":"4993"},
"stickers":["3514","3509","3511"]
"folder_holder":["22","26","20","00","00"],

Notice that KoL tells us what is in the card sleeve, folder holder, and sticker sword - even though none of them are equipped.

Great! Thanks for the PR @Tokoeka but we're closing as Not a Bug


[cargo doc] build.rs does not cover the use cases very well

With docs.rs out, we’ve noticed a problem with cargo running build.rs scripts when documenting each crate, while it shouldn’t be necessary in majority of the cases.
Namely, most of the crates use build.rs scripts for one of these three large categories:

Native library discovery (pkgconfig/etc);
Building of dependencies written in other languages (gcc-rs/etc);
Generating rust code (syntex/lalrpop/etc).

First and second use case will not influence the resulting documentation in meaningful ways, while the third use-case almost always will. First and second use-cases are target-dependent and may require cross-compilation toolchains, whereas the third use-case as well as documentation generation are obviously target-agnostic and can be done without any extra tooling or knowledge about the target platform.
It is counter-productive to not make any distinction between these cases. A project like docs.rs ideally shouldn’t need to install any native dependencies (see https://github.com/onur/docs.rs/issues/23) in order to generate documentation (because they are irrelevant for documentation generation purposes!)
There’s multiple ways one could proceed here:

Introduce generate.rs, do not run build.rs scripts on cargo doc;
Introduce extra keys to Cargo.toml (e.g. run_build_script_for_docs = false) defaulting to not running build.rs before generating documentation and making people using third use case specify that variable to true;
The least breaking change would be to add a way in cargo API to not run build.rs scripts when building docs, so docs.rs could implement some sort of scheme itself (e.g. via [metadata] Cargo.toml section instructing docs.rs to run build.rs);
etc.

cc @onur

Build scripts can also output rustc-cfg features, which may affect the documentation.

@cuviper I do not disagree, but as I already said, the influence is not meaningful. Those cfgs reflect the build environment of whatever is building your documentation and not the environment your user (the person reading documentation) has. This leads to essentially the same problem as showing linux documentation for a user using windows (resulting in empty os modules etc).
In order to specify cfgs for docs.rs, I think one would end up using similar scheme as the one you’d use to specify features (https://github.com/onur/docs.rs/issues/29).

Yeah it's true that build scripts are basically just large black boxes today, so I think it's correct for now to default to trying to run them to generate docs. I'd be up for exploring the space of more targeted build scripts for situations like this, but that's certainly RFC territory to be implemented.

@alexcrichton what about

The least breaking change would be to add a way in cargo API to not run build.rs scripts when building docs, so docs.rs could implement some sort of scheme itself (e.g. via [metadata] Cargo.toml section instructing docs.rs to run build.rs);

We could perhaps add a flag to cargo doc that doesn't run build scripts like that, yeah, but I don't think we could switch the default behavior to not running build scripts when building documentation.

Can't the build script check $PROFILE and skip things that aren't relevant to docs?

Any progress on this issue?

This sounds like it might fall under eRFC 2136, Cargo build system integration.

As far as I can tell, #8811 is a dupe of this but since it has more recent notes on direction, I'm closing this in favor of it.


Is the Flops calulated wrong?

https://github.com/microsoft/Swin-Transformer/blob/2622619f70760b60a42b996f5fcbe7c9d2e7ca57/models/swin_transformer.py#L583
where
self.avgpool=self.norm: self.num_features * self.patches_resolution[0] * self.patches_resolution[1] // ((2 ** (self.num_layers  - 1)) ** 2)

so flops += self.num_features * self.patches_resolution[0] * self.patches_resolution[1] // (2 ** self.num_layers) // 2
eg. 768 * 7 * 7 * 2 = 768 * 56 * 56 // 16 // 2

Hi @choasup, you are right, but the flops of avgpool is so negligible compared with the overall flops, so we just ignore it.

Hi @choasup, how did ((2 ** (self.num_layers  - 1)) ** 2) simplified into `(2 ** self.num_layers)'?
I'm so confused about the calculation of FLOPs for norm here, as in #165
Does anyone can answer my question？
Thanks alot!


remove prompt to create API key and data source, send user straight to docs

Currently, if the API key is not found when the --cloud flag is used, the user is guided to generate an API key, go through data source creation, etc.
We should instead simply provide them with a link to the instructions for storing an API key and adding the data source id to dbt_project.yml: https://docs.datafold.com/development_testing/cloud

Let's see if tests pass. @dlawin I will not at all be offended if this PR is closed and you takes a different approach to addressing the ticket, but I wanted to take a stab at it.

@dlawin I think I may have resolved the merge conflicts 🤞


Incorrect Show Alert Embed

Setting no alert will show "No Show" as field title.

This is likely a copy-paste mistake I've made during the creation of the bot, but I'll take a look at it later tonight and push out a fix

Fixed in PR #7


latest download no longer available

The download instructions are not currently valid as https://dl.embulk.org/embulk-latest.jar is not available.  Is this planned?

Actually I should revise this... latest does indeed point to https://dl.bintray.com/embulk/maven/embulk-0.9.8.jar which is not there.

@rickrdvaughn Sorry. Embulk v0.9.8 was released just yesterday. Library jars were uploaded successfully in Bintray, but the all-in-one exexutable embulk-0.9.8.jar was not uploaded there silently.
I manually uploaded that just now.


fix: issue with storing false values in data model not validating as …

Description
This PR fixes an issue where setting falsy values in input fields with boolean or integer data model fields triggered warnings of not being set when submitting or navigating the form.
Related Issue(s)

closes #1746

Verification/QA

Manual functionality testing

[x] I have tested these changes manually
[ ] Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
[ ] No testing done/necessary

Automated tests

[ ] Unit test(s) have been added/updated
[x] Cypress E2E test(s) have been added/updated
[ ] No automatic tests are needed here (no functional changes/additions)
[ ] I want someone to help me make some tests

UU/WCAG (follow these guidelines until we have our own)

[ ] I have tested with a screen reader/keyboard navigation/automated wcag validator
[x] No testing done/necessary (no DOM/visual changes)
[ ] I want someone to help me perform accessibility testing

User documentation @ altinn-studio-docs

[ ] Has been added/updated

[x] No functionality has been changed/added, so no documentation is needed
[ ] I will do that later/have created an issue

Support in Altinn Studio

[ ] Issue(s) created for support in Studio

[x] This change/feature does not require any changes to Altinn Studio

Sprint board

[x] The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
[ ] I don't have permissions to do that, please help me out

Labels

[x] I have added a kind/* label to this PR for proper release notes grouping
[ ] I don't have permissions to add labels, please help me out

The group-test that fails is not related to the functionality of this PR. All relevant tests are passing :innocent:


Can h2ogpt chatbox retain the context of previous questions?

The chat context is always included when talking to LLM.  If it gets too long, the oldest stuff gets cut truncated.
If a collection is selected, only the document context + query is provided, because nominally the context is too small to handle the chat context + document context + query.
Also, most LLMs start to get quite confused if so much extended mixed types of information is in the context.
I can add some options, but it's easy to ask LLM with all context by switching to ChatLLM "collection"