Capitalization of windows.h for cross compilation

Reported by rfranke on 18 Mar 2016 04:23 UTC
Modelica/Resources/C-Sources do include the file Windows.h.
ModelicaInternal.c:701:#include <Windows.h>
ModelicaRandom.c:132:#include <Windows.h>
ModelicaStandardTables.c:320:#include <Windows.h>
This file is not available under MinGW. They call it windows.h with small w. This makes a difference when cross compiling on a platform that cares about capitalization (in particular Linux).
Wikipedia calls it windows.h as well. See:
https://en.wikipedia.org/wiki/Windows.h
Here is an example how another cross-platform project dealt with this:
https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-qt4/qt-4.8.0-fix-include-windows-h.patch
Can't these three Windows.h in C-Sources be changed to windows.h?
Can this possibly still be done for the 3.2.2 release, because there can hardly be any negative consequence of this change?

Migrated-From: https://trac.modelica.org/Modelica/ticket/1962

Comment by sjoelund.se on 18 Mar 2016 05:40 UTC
rfranke: I found it does not matter much when cross-compiling OpenModelica; the easiest way to solve it is to add a file windows.h that includes Windows.h for MinGW. If you are using clang to cross-compile using Visual Studio headers, they simply need to be installed on a case-insensitive file system (Microsoft internally changes the capitalization in all of its headers; MinGW is consistent).

Comment by beutlich on 18 Mar 2016 07:20 UTC
I discussed this with sjoelund.se some months ago. It is impossible to fix in a consistent way. See screen shot.

Comment by beutlich on 18 Mar 2016 09:28 UTC
Well, maybe we still should do it. There is no Windows.h on Linux (from MinGW or Wine) and Windows is case-insensitive.
But I cannot decide the milestone.

Comment by rfranke on 18 Mar 2016 09:39 UTC
As you said: Windows is case insensitive and Linux is consistent windows.h. Moreover we have a reference from the Qt project.
Who can decide to already fix it in 3.2.2?

Comment by otter on 18 Mar 2016 09:43 UTC
3.2.2 will be released soon. There will be no changes any more with respect to RC.3 (with exception of very important bugs)

Comment by beutlich on 5 Apr 2016 07:55 UTC
Resolved by 7cb159b78d4f5d55f2c41c3f33c1baf9301dea5d (trunk), c134387de6203a464668f835acb6cb7f3b09dc95 (maint. 3.2.2) and 34f3f0d2f05091444bdb71626ca0f69f0aa0e593 (maint. 3.2.1).

Changelog modified by beutlich on 5 Apr 2016 07:55 UTC
Improved suppport for cross-compilation on Linux


Open Id Connect implementation does not play well with Web Application Firewall

The default implementation of Open Id Connect uses a Data Protection Provider that generates strings that fall foul of a Web Application Firewall implementing the OWASP rule set's SQL Injection checking. For example, a Nonce cookie is created where the name of the cookie has Options.StringDataFormat.Protect(nonce) appended. This means the cookie often has the string "--" somewhere within it. This then gets picked up as a potential SQL Comment Sequence and blocked. I have also seen the SQL Hex Encoding rule triggered.
Other places I have seen the issue:

Contents of the Authentication Cookie
Contents of the Anti Forgery Cookie
Contents of the Anti Forgery request verification token form data

For my WAF I am using the Azure Application Gateway Web Application Firewall. I can configure its Exclusion rules to mitigate against these last three instances of the issue. However, Exclusions are only available in "Preview" of the WAF so should not be used in production. Also, they don't help with the Nonce issue as the exclusion rules only exclude the checking of a cookie's value, not of its name!
My only alternative is to turn off the checks for SQL Injection... however since that is the considered the most common attack vector it seems to go against the point of using a WAF!
To Reproduce
Steps to reproduce the behavior:

Create an ASP.Net Core web application and use an Identity Server for authentication (using the code id_token flow)
Host the application behind Azure Application Gateway
Turn on WAF in the Application Gateway, enabling the Firewall, setting the Firewall mode to Prevention and use the OWASP 3.0 rule set
Repeatedly log in and log out of the application

Expected behavior
I would expect the log in and log out to always succeed, however perhaps 1 in 5 / 1 in 10 attempts to login will fail with a 403 returned by the Application Gateway.
Additional context
Using the Preview exclusion feature I have added the following exclusions to the WAF on the Application Gateway:

Field
Operator
Selector

Request attribute name
Equals
id_token

Request attribute name
Equals
state

Request cookie name
starts with
.AspNetCore.OpenIdConnect.Nonce.

Request cookie name
starts with
.AspNetCore.Correlation.oidc.

Request cookie name
starts with
.AspNetCore.Cookies

Request cookie name
starts with
ABC.AuthCookie

Request cookie name
starts with
.AspNetCore.Antiforgery.

Request attribute name
starts with
__RequestVerificationToken

But as I said above, Exclusions should not be used in production and they do not fix issues with the names of cookies containing character sequences that trigger SQL Injection rules.

The data protected state string is what he's talking about. // @HaoK

Yea, the trigger here is "--" and we're not about to invent a new encoding just to bypass an overly sensitive rule.
The Azure folks said exclusions are available in production and that's their solution.

@murtag I was very sure at the time I raised this that it was the name that had a problem. The logging by the WAF was quite explicit about the cause. Currently we are having to run our system with the rules "942440 SQL Comment Sequence Detected" and "942450 SQL Hex Encoding Identified" turned off.
I raised this on the WAF UserVoice forum as it seems to be the only place to communicate with the team:
https://feedback.azure.com/forums/217313-networking/suggestions/36260122-web-application-firewall-cookie-exclusions-only-ex
No feedback yet.

Yea, the trigger here is "--" and we're not about to invent a new encoding just to bypass an overly sensitive rule.
The Azure folks said exclusions are available in production and that's their solution.

I do know those exclusions are app-wide, and can't be set for a specific path/url, so unfortunately this means the entire app will not longer have the rule in place, rather than just the redirect uri for OIDC.

First step is to get an app set up with WAF and see if we can reproduce the "bad SQL injection rule" thing, and then come up with possible alternative cookie characters that do pass the rule.

Closing because we decided not to make any change to the Auth behavior because we believe the current behavior is correct.

@Eilon It would be good if you suggested a work around... or are you able to raise this with the team responsible for the WAF. To those of us outside of Microsoft there only seems to be a UserVoice forum to allow us to suggest new features rather than report bugs.

I still have problems with compatibility between Open Id Connect and Microsoft Authentication and WAF Firewall throwing unauthorized access errors some times. It was seeming random, and if I reproduce the sign out/sign in multiple times, sometimes it works, others it gets blocked.
Is there any workaround beside of disabling/adding exceptions to the rules?

No... it still appears to be an issue. From the above, the ASP.Net Core team are not going to fix it and it looks like the WAF team are not doing anything about it either. Please vote on their uservoice account:
https://feedback.azure.com/forums/217313-networking/suggestions/36260122-web-application-firewall-cookie-exclusions-only-ex


Append all client-side errors

cc @robskillington @cw9
We use the length of the errors slice as the number of errors so we need to append all errors. Besides it provides full context about the errors, which helps debuggability

Coverage decreased (-0.02%) to 78.292% when pulling 75554d3024d49dcb1d1742fe7fb45f1199446db0 on xichen-fix-client-error into cbe05ccab688ae15d67e02dabf34ee6a50544cab on dev.

Coverage decreased (-0.1%) to 78.21% when pulling 9420ab14907dd59bfac8882b889ea4084141d78e on xichen-fix-client-error into cbe05ccab688ae15d67e02dabf34ee6a50544cab on dev.


ol.interaction.snap support for multiple layers

We'd like to enable user to snap to any vector geometry in a map while drawing/editing new features.
Currently, we can add all current features to features collection of ol.interaction.snap. Or we can add one "virtual" layer/vector source and add all the features. In both cases, all features are duplicated and it is necessary to update the collection or source whenever map viewport is changed during draw action.
So we have a change request to extend the ol.interaction.snap so that more sources/layers can be added (or all visible vector features in a map can be used).

@jakubbican could you find any better solutions for this issue?

Not yet. We'll be trying some workarounds soon.

Is there any better solutions for multiple layers snapping?

Is there any better solutions for multiple layers snapping?

Here is what we finally do in our solution (with jakubbican):
import { Vector as layerVector } from 'ol/layer';
import { Snap } from 'ol/interaction';

--------

let interactions = [];
this.map.getLayers().forEach((layer) => {
  if (layer instanceof layerVector) {
    let interaction = new Snap({
      source: layer.getSource()
    });
    interactions.push(interaction);
  }
});

for(let snap of interactions ) {
  this.map.addInteraction(snap);
}

Plus the interaction collection is saved in memory in order to be able to remove the interactions later.

Here is what we finally do in our solution (with jakubbican):
import { Vector as layerVector } from 'ol/layer';
import { Snap } from 'ol/interaction';

--------

let interactions = [];
this.map.getLayers().forEach((layer) => {
  if (layer instanceof layerVector) {
    let interaction = new Snap({
      source: layer.getSource()
    });
    interactions.push(interaction);
  }
});

for(let snap of interactions ) {
  this.map.addInteraction(snap);
}

Plus the interaction collection is saved in memory in order to be able to remove the interactions later.

Thank you @vojtech-osvald

Thank you @vojtech-osvald

Here is what we finally do in our solution (with jakubbican):
import { Vector as layerVector } from 'ol/layer';
import { Snap } from 'ol/interaction';

--------

let interactions = [];
this.map.getLayers().forEach((layer) => {
  if (layer instanceof layerVector) {
    let interaction = new Snap({
      source: layer.getSource()
    });
    interactions.push(interaction);
  }
});

for(let snap of interactions ) {
  this.map.addInteraction(snap);
}

Plus the interaction collection is saved in memory in order to be able to remove the interactions later.

This solution only snaps with latest layer for me. Is there other solution?


Feature merge from enhex fork

Basically changes from https://github.com/Enhex/premake-cmake/pull/16 plus one additional change (honoring C(XX)FLAGS) as well as two regression fixes.

@tritao: Conflicts are indeed blocking,
Then I have to test it. (fortunately I have https://github.com/Jarod42/premake-sample-projects for that).
Sorry for delay :-/ (wrong notification settings :/ )


Remove JLD and HDF5 dependency

Don't need JLD or HDF5 since PR #329 removed the last use of a JLD output writer.
This should speed up CI testing by quite a bit.

Beautiful!


handling for 'unknown' gendered names

The current gender detector script will label many names as being of 'unknown' gender.
[ ] @nllz has requested a feature that would, when using the detector over a large set of names, export the gendered lists of names, and especially the 'unknown' list.
That would open the list to inspection to see if any names could be labeled, or the gender detector otherwise improved.
[ ] A related feature might support the use of an additional, custom data file assigning names to (known) genders.

I've been doing this by outputting a CSV file (after entity resolution and gender estimation), manually making changes (to add/correct known gender, or to manually consolidate names/addresses that I know to be the same person) and then importing that CSV back into a dataframe.
I do think it would be possible and potentially useful to researchers who are studying overlapping communities (like IETF and W3C groups), to be able to import a CSV file with email addresses known to the researcher along with information the researcher manually annotates (gender, nation of origin, etc.).

Connects to #509


Update SQLite to v3.40.0 and include fix for changeset generated by old code fail to apply.

SQLite updated from itwin-sqlite-v3.40.0-r0
Update SQLite to v3.40.0 with the following additional changes from master.

Fix a comment in ext/session/test_session.c.
Prevent the sessions rebaser from generating changesets containing UP…

Also updated UpdateSqlite.bat to update source from https://github.com/iTwin/sqlite fork.

I see something here about rebasing. We should never be doing any rebasing, right?

I see something here about rebasing. We should never be doing any rebasing, right?

The code that generated the changeset is PID which is using code from Feb 2021. I assume we have rebase enabled at the time and it creates a changeset that cannot be applied by latest code. Checkpoint service failed to apply it.
Dan from SQLite figure out that the issue was caused by rebaser and fix it and also make sure that new code can still apply that old changeset.


sqls binary file name miss suffix in windows

sqls binary file name miss suffix(.exe) in windows
before I change the code, extension can not find sqls binary in windows:

after I changed the code, extension can find sqls binary in windows:

@MrScallion Thanks!!! I try to support windows.

windows support was released on v0.5.7.


cmd/objbench: Fixed the latency calculation method

Codecov Report
Base: 58.45% // Head: 58.43% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (2d4ab24) compared to base (8222512).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3100      +/-   ##
==========================================
- Coverage   58.45%   58.43%   -0.02%
==========================================
  Files         141      141
  Lines       25167    25167
==========================================
- Hits        14711    14707       -4
+ Misses       8507     8506       -1
- Partials     1949     1954       +5

Impacted Files
Coverage Δ

cmd/objbench.go
60.86% <100.00%> (ø)

pkg/chunk/utils_unix.go
66.66% <0.00%> (-25.00%)
:arrow_down:

pkg/chunk/disk_cache.go
73.95% <0.00%> (-1.00%)
:arrow_down:

pkg/vfs/handle.go
85.56% <0.00%> (ø)

pkg/vfs/reader.go
79.41% <0.00%> (+0.21%)
:arrow_up:

pkg/fuse/context.go
75.00% <0.00%> (+10.71%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Generate only mix-manifest.json on specific folder

Laravel Mix Version: #.#.# (npm list --depth=0)
Node Version (node -v):
NPM Version (npm -v):
OS:

Description:
I need your help about the file mix-manifest.json, when webpack compile my js and css files he place them on my www folder with (in my webpack.mix.js):

in my racine "/" i have myApp folder and www folder and all laravel logic is placed in myApp folder
and my index.php is in www folder, i want that the file mix-manifest.json be generated in myApp folder and the rest of compiled files (js,sass,less...) in www folder
how can i do this please ?
Steps To Reproduce:

You can't override the default location of the mix-manifest.json file. It will always be placed in the project's public directory. You can use mix.setPublicPath() to explicitly set the public folder for your app.


Naming conventions on config files and their folders

Archive, current, latest (unet versions, etc.), different materials maybe, model structures.
Will require reorg of current files/folders

All: Naming conventions on config files and folder conventions in config (GH issue #78)
Archive, current, latest (unet versions, etc.), different materials maybe, model structures


Crypto API isn't detected on alternative platforms

I run across this using Cloudflare Workers. It should be possible to use this library by instead checking for a crypto global instead of trying to detect `window. Documentation from Cloudflare here: https://developers.cloudflare.com/workers/reference/apis/web-crypto/.

Hoping this aligns with the original point of this issue, but I've noticed too that on some platforms like Mobile Safari on iOS 8-10.3, crypto is window.webkitCrypto, not crypto or msCrypto as read in the source: https://github.com/ulid/javascript/blob/master/lib/index.ts#L123
Along with using a generic global lookup, perhaps expand the crypto lookup to include the webkit reference?

I also could not use ulid in Web Worker of Chrome or Safari by the same reason.

@SokichiFujita Added an issue for that at #83. Should be fixed by my PR at #82.

@DavidJFelix I've made a supported fork here, in case that's of interest: ulidx. There's also another fork designed specifically for cloudflare workers: ulid-workers.


bug?Wild Garlic have two diff type

same name A and B Wild Garlic
i can only get typeA for vanilla recipe.
the DLS use typeB , i can not get it from forage.
i dont know how to use github, if send to a wrong location, i am sorry for that

It was today that I found out that Github has not been sending me any notifications for this repo >.<
Can you give more details on the issue here, such as what recipe is affected? Looking at the code, the only garlic referenced is the one from the vanilla game so I'm not sure what other type of garlic there is.

Ignore my previous response, I see what you mean now. I guess Type B is an older version of garlic that's no longer used. I'll have it fixed shortly.

Ignore my previous response, I see what you mean now. I guess Type B is an older version of garlic that's no longer used. I'll have it fixed shortly.

is this try to fix？I still feel not right about garlic，inculd new garlic from Scavenging this day（but old savegame）

Hmm, it should be the right one but I will test it when I get the chance, maybe next week

Hmm, it should be the right one but I will test it when I get the chance, maybe next week

thanks，I still get typeA from scavenging，this typeA can use in vanilla med 。cannot make sugar，cannot packup （all DLTS receipes）。I can only  see typeB from recipe helper mod。just try to say clearly

Sorry it took me so long to get around to checking this, I forgot about it. So I did some test foraging and found some wild garlic.

When I use Craft Helper to look at what recipes it can be used in, it shows up in all the right recipes, LTS ones included.

I used the cheat menu to give myself some of the old garlic, which no longer spawns in the game. You can tell which is the old garlic by the fact that it doesn't have any nutrition. Basically the new garlic can be used as a food while the old garlic cannot.

And the only recipe the old garlic can be used for according to Craft Helper is the poultice. (I guess they just left that recipe in there)

So unless I'm missing something, I'm using the correct garlic (the edible one) in the LTS recipes. If there's something I'm misunderstanding, it might help if you included some screenshots.

i don not know why, now it works well in my new and old saves, i am not change anything from report bug, any way its ok now,thanks


Did i miss something or is the example not working?

Hey,
i just downloaded the this repo and the latest sdk (<IP_ADDRESS>) and the latest server (3.3.0), removed the password (https://github.com/TeamSpeak-Systems/ts3_sdk_dotNet/blob/master/examples/Client/Program.cs#L71) and tried to start the example.
But all i get is an FailedConnectionInitialisation at (https://github.com/TeamSpeak-Systems/ts3_sdk_dotNet/blob/master/examples/Client/Program.cs#L84).
Is this sdk no longer maintained because you are working on Teamspeak 5 or do i have to do something different?
And by the way: Will Teamspeak 5 also have and sdk?

The SDK can only connect to a SDK-Server. You can find a simple example server in the 'server' directory inside the sdk folder. More information about the SDK-Server can be found in the full sdk's documentation.
There is currently no c#-wrapper for the sdk server.
As for TeamSpeak 5: A TeamSpeak 5-Client will be able to connect to a TeamSpeak 3-Server.


[Bug] Locked at Python 3.9 because of protoc-wheel-0 dependency

What are you really trying to do?
I'm attempting to install pip install temporalio in Alpine v3.18 (Python 3.11.6). This doesn't seem to be possible given protoc-wheel-0 does not yet support newer versions (locked at 3.9). However, it does seem a minimal dependency that could be easily be isolated and eliminated.
Is this on the roadmap for removal/deprecation?
Describe the bug
ERROR: Could not find a version that satisfies the requirement protoc-wheel-0 (from versions: none)
ERROR: No matching distribution found for protoc-wheel-0

Collecting temporalio (from -r requirements.txt (line 1))
  Downloading temporalio-1.3.0.tar.gz (944 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 944.6/944.6 kB 19.6 MB/s eta 0:00:00
  Installing build dependencies: started
  Installing build dependencies: finished with status 'error'
  error: subprocess-exited-with-error

  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1
  ╰─> [17 lines of output]
      Collecting poetry-core>=1.0.0
        Obtaining dependency information for poetry-core>=1.0.0 from https://files.pythonhosted.org/packages/99/bc/058b8ff87871fce6615ad032d62c773272f243266b110f7b86d146cf78d8/poetry_core-1.8.1-py3-none-any.whl.metadata
        Downloading poetry_core-1.8.1-py3-none-any.whl.metadata (3.5 kB)
      Collecting setuptools
        Obtaining dependency information for setuptools from https://files.pythonhosted.org/packages/bb/26/7945080113158354380a12ce26873dd6c1ebd88d47f5bc24e2c5bb38c16a/setuptools-68.2.2-py3-none-any.whl.metadata
        Downloading setuptools-68.2.2-py3-none-any.whl.metadata (6.3 kB)
      Collecting wheel
        Obtaining dependency information for wheel from https://files.pythonhosted.org/packages/fa/7f/4c07234086edbce4a0a446209dc0cb08a19bb206a3ea53b2f56a403f983b/wheel-0.41.3-py3-none-any.whl.metadata
        Downloading wheel-0.41.3-py3-none-any.whl.metadata (2.2 kB)
      Collecting setuptools-rust
        Obtaining dependency information for setuptools-rust from https://files.pythonhosted.org/packages/e0/34/d88a7ceb193fbcee6c8992d1b1e33ed20361027e07fea1676efc45ec7a43/setuptools_rust-1.8.1-py3-none-any.whl.metadata
        Downloading setuptools_rust-1.8.1-py3-none-any.whl.metadata (9.4 kB)
      ERROR: Could not find a version that satisfies the requirement protoc-wheel-0 (from versions: none)
      ERROR: No matching distribution found for protoc-wheel-0

Notice:       [notice] A new release of pip is available: 23.2.1 -> 23.3.1
Notice:       [notice] To update, run: pip install --upgrade pip
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

Notice:  A new release of pip is available: 23.2.1 -> 23.3.1
Notice:  To update, run: pip install --upgrade pip

Minimal Reproduction
repro.dockerfile
FROM public.ecr.aws/docker/library/alpine:latest

RUN apk update && apk add --no-cache python3 py3-pip

RUN pip3 install temporalio

docker build -f repro.dockerfile .
Environment/Versions

program
version

Alpine
3.18

Python
3.11.6

pip
23.1.2

What happens on musl-based platforms is that your system attempts to rebuild the wheel from scratch. We don't expect runtime users to have this, it is a dev dependency. You're also going to have to have Rust and protoc on the path and everything else that comes with building this project since we don't pre-build a musl wheel.
We do require this dependency for proto generation to put protoc on the PATH, but I'm ok requiring it on the PATH already since we do for building the Rust part anyways. So we can probably remove this dependency, but you're still going to have to have certain things installed when building on an environment we don't prebuild a wheel for.

This seems to be perfectly reasonable to me, this will give those without a choice a path forward. I will move this job onto a debian-based distro for now. Will musl be supported in the future with this sdk?

I am unsure whether it will be supported in the future, but for now (as with windows arm, 32-bit, etc) it requires a custom build

Sounds good, thanks for the help!

So we can probably remove this dev dependency (or make it optional), but you're still going to have to have certain things installed when building on an environment we don't prebuild a wheel for.

I'm running into a similar issue, do you have any news with regards to this, any way to circumvent this?
 > [service 7/8] RUN poetry install --without dev:
1.643 Skipping virtualenv creation, as specified in config file.
2.530 Installing dependencies from lock file
3.263
3.264 Package operations: 38 installs, 0 updates, 0 removals
3.264
...
...
25.12   - Installing temporalio (1.6.0)
25.19   - Installing uvloop (0.19.0)
32.92
32.92   ChefInstallError
32.92
32.92   Failed to install poetry-core>=1.0.0, setuptools, wheel, setuptools-rust, protoc-wheel-0.
32.92
32.92   Output:
32.92   Updating dependencies
32.92   Resolving dependencies...
32.92
32.92   Package operations: 6 installs, 0 updates, 0 removals
32.92
32.92     - Installing semantic-version (2.10.0)
32.92     - Installing setuptools (69.5.1)
32.92     - Installing poetry-core (1.9.0)
32.92     - Installing protoc-wheel-0 (25.3)
32.92     - Installing setuptools-rust (1.9.0)
32.92     - Installing wheel (0.43.0)
32.92
32.92     RuntimeError
32.92
32.92     Unable to find installation candidates for protoc-wheel-0 (25.3)
32.92
32.92     at /usr/local/lib/python3.12/site-packages/poetry/installation/chooser.py:74 in choose_for
32.92          70│
32.92          71│             links.append(link)
32.92          72│
32.92          73│         if not links:
32.92       →  74│             raise RuntimeError(f"Unable to find installation candidates for {package}")
32.92          75│
32.92          76│         # Get the best link
32.92          77│         chosen = max(links, key=lambda link: self._sort_key(package, link))
32.92          78│
32.92
32.92   Cannot install protoc-wheel-0.
32.92
32.92
32.92
32.92   Error:
32.92
32.93
32.93   at /usr/local/lib/python3.12/site-packages/poetry/installation/chef.py:102 in install
32.95        98│             InstalledRepository.load(self._env),
32.95        99│         )
32.95       100│         installer.update(True)
32.95       101│         if installer.run() != 0:
32.95     → 102│             raise ChefInstallError(requirements, io.fetch_output(), io.fetch_error())
32.95       103│
32.95       104│
32.95       105│ class Chef:
32.95       106│     def __init__(
32.95
32.95 Cannot install build-system.requires for temporalio.
32.95
------

I think this happens because we don't have a prebuilt musl wheel and protoc-wheel-0 doesn't either. I am not aware of a way to circumvent this at this time short of removing the dev dependency before building. I am reopening this issue to see if it's reasonable for us to remove this dependency (e.g. maybe put it behind a "extra" or use protoc on the PATH more directly).

I have same issue when I try to install Temporal SDK on FreeBSD
`# python -m pip install temporalio
Collecting temporalio
Using cached temporalio-1.6.0.tar.gz (1.0 MB)
Installing build dependencies ... error
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [10 lines of output]
Collecting poetry-core>=1.0.0
Using cached poetry_core-1.9.0-py3-none-any.whl.metadata (3.5 kB)
Collecting setuptools
Using cached setuptools-70.0.0-py3-none-any.whl.metadata (5.9 kB)
Collecting wheel
Using cached wheel-0.43.0-py3-none-any.whl.metadata (2.2 kB)
Collecting setuptools-rust
Using cached setuptools_rust-1.9.0-py3-none-any.whl.metadata (9.3 kB)
ERROR: Could not find a version that satisfies the requirement protoc-wheel-0 (from versions: none)
ERROR: No matching distribution found for protoc-wheel-0
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.`

You can probably remove the https://github.com/temporalio/sdk-python/blob/afadc15ba74d6101109316fd24a6747e8a558187/pyproject.toml#L50 dependency and rebuild. We need to remove this dependency ourselves or make it optional (we will look into doing this). It's only for letting us do proto generation which is not needed at build time.

Hi @cretz,
After removing the above line, I was successfully able to build the dependencies using "poetry install --no-root --all-extras" command  But when I try to build the release build using "poetry build" command , I'm getting the following errors,
`
poetry build
Preparing build environment with build-system requirements poetry-core>=1.0.0, setuptools, wheel, setuptools-rust, protoc-wheel-0
Command ['/tmp/tmpfe6rso36/.venv/bin/python', '/usr/local/lib/python3.8/site-packages/virtualenv/seed/wheels/embed/pip-24.0-py3-none-any.whl/pip', 'install', '--disable-pip-version-check', '--ignore-installed', '--no-input', 'poetry-core>=1.0.0', 'setuptools', 'wheel', 'setuptools-rust', 'protoc-wheel-0'] errored with the following return code 1
Output:
Collecting poetry-core>=1.0.0
Using cached poetry_core-1.9.0-py3-none-any.whl.metadata (3.5 kB)
Collecting setuptools
Using cached setuptools-70.0.0-py3-none-any.whl.metadata (5.9 kB)
Collecting wheel
Using cached wheel-0.43.0-py3-none-any.whl.metadata (2.2 kB)
Collecting setuptools-rust
Using cached setuptools_rust-1.9.0-py3-none-any.whl.metadata (9.3 kB)
ERROR: Could not find a version that satisfies the requirement protoc-wheel-0 (from versions: none)
ERROR: No matching distribution found for protoc-wheel-0
`
Fyi - I'm referring below doc
https://github.com/temporalio/sdk-python?tab=readme-ov-file#development:~:text=written in Rust.-,Building,-Prepare
for building the Temporal Python SDK on FreeBSD.

To remove a dependency with Poetry, you it needs to be removed from toml and lock file. poetry remove command can probably do this.

Hey everyone, fyi, I was able to build and install the Temporal Python SDK on FreeBSD by removing the protoc-wheel-0 and adding the protobuf package. Thanks

Using cached temporalio-1.7.0.tar.gz (1.3 MB)
Installing build dependencies ... error
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [10 lines of output]
Collecting poetry-core>=1.0.0
Using cached poetry_core-1.9.0-py3-none-any.whl.metadata (3.5 kB)
Collecting setuptools
Using cached setuptools-73.0.1-py3-none-any.whl.metadata (6.6 kB)
Collecting wheel
Using cached wheel-0.44.0-py3-none-any.whl.metadata (2.3 kB)
Collecting setuptools-rust
Using cached setuptools_rust-1.10.1-py3-none-any.whl.metadata (9.2 kB)
ERROR: Could not find a version that satisfies the requirement protoc-wheel-0 (from versions: none)
ERROR: No matching distribution found for protoc-wheel-0
end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
base image python 3.11-alpine3.16
getting this error while running python -m pip install temporalio command

I see an issue was opened at https://github.com/temporalio/sdk-python/issues/622 and a new Slack thread was started. No need to double/triple post.


tests: include ES5 and unpin elasticsearch* requirements

[ ] add ES5 to travis matrix
[ ] unpin elasticsearch requirements in setup.py

@lnielsen
I did some background reading (and googling) and now I have couple of questions:

Which Elasticsearch 5 version should be used (5.5.x? -- 5.6.x?)

Currently Travis builds are running Ubuntu Trusty Container-based environment, right?

There is https://docs.travis-ci.com/user/database-setup/#Installing-ElasticSearch-on-trusty-container-based-infrastructure
which describes:env:
  - ES_VERSION=5.1.1 ES_DOWNLOAD_URL=https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-${ES_VERSION}.tar.gz
install:
  - wget ${ES_DOWNLOAD_URL}
  - tar -xzf elasticsearch-${ES_VERSION}.tar.gz
  - ./elasticsearch-${ES_VERSION}/bin/elasticsearch &
script:
  - wget -q --waitretry=1 --retry-connrefused -T 10 -O - http://<IP_ADDRESS>:9200

Should the above one be used to install Elasticsearch 5?
There is also install instructions for VM based Trusty environment here:

https://www.peterbe.com/plog/elasticsearch-5-in-travis-ci
https://github.com/peterbe/autocompeter/blob/dfe2db128e628d6dd300385cc6e422e6e1bed57e/.travis.yml

Use same code for downloading ES2 and ES5?

Include new envvar ELASTIC_URL:- ELASTIC_2_URL=https://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/distribution/tar/elasticsearch/${ES_VERSION}/elasticsearch-${ES_VERSION}.tar.gz
- ELASTIC_5_URL=http://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-${ES_VERSION}.tar.gz

...

env: ELASTIC_URL=$ELASTIC_5_URL

Change to wget -O ${ES_URL} | tar xz --directory=/tmp/elasticsearch --strip-components=1 and old ES install+startup method should continue to work.
(inspired by: https://github.com/mongodb-labs/elastic2-doc-manager/blob/b9230bae11b99ed7da2c3db26ea2bb1c7a1e224b/.travis.yml)

How to propagate .travis.yml test matrix changes to setup.py as elasticsearch version changes?

When ES2 is used setup.py should use elasticsearch>=2.0.0,<3.0.0 and elasticsearch-dsl>=2.0.0,<3.0.0.
When ES5 is used setup.py should use elasticsearch>=5.0.0,<6.0.0 and elasticsearch-dsl>=5.0.0,<6.0.0.
I was thinking something like this:PYTHON_ELASTIC_VERSION = os.environ.get('PYTHON_ELASTIC_VERSION', '>=2.0.0,<3.0.0')
PYTHON_ELASTIC_DSL_VERSION = os.environ.get('PYTHON_ELASTIC_DSL_VERSION', '>=2.0.0,<3.0.0')
install_requires = [
      'Flask-BabelEx>=0.9.2',
      'dojson>=1.2.0',
      'elasticsearch' + PYTHON_ELASTIC_VERSION,
      'elasticsearch-dsl' + PYTHON_ELASTIC_DSL_VERSION,
      ...
]

(inspired by: https://github.com/mongodb-labs/elastic2-doc-manager/blob/683cc482e53a125b6115ff44aba18dd6031b5408/setup.py)

Making note of Elasticsearch version in Travis logs

Should I add version output of Elasticsearch so that it is faster to identify which is elasticsearch version is used when going
through logs of failed build?
For example:- "wget -O ..."
- "elasticsearch --version"
- "/tmp/elasticsearch/bin/elasticsearch &"

Indexing in ES5 vs ES2

@slint mentioned something that different kind of indexing should be used for ES5 and ES2.
How should this be taken into account? Will it cause changes in some other invenio-modules?

How should I setup test matrix so that one set of test uses ES2 and another one ES5?

I'm not that used experienced in configuring Travis, so I'm not sure which is the best way to include new entries in test matrix.
If $ELASTIC_URL which I mentioned above is included and download+install code is identical for both ES2 and ES5, should I just add an new entries under env: -key which use ES5 instead of ES2?:- REQUIREMENTS=lowest EXTRAS=all,sqlite SQLALCHEMY_DATABASE_URI="sqlite:///test.db" ES_HOST=<IP_ADDRESS> ES_VERSION=2.2.0 ELASTIC_URL=$ELASTIC_2_URL
- REQUIREMENTS=release EXTRAS=all,sqlite SQLALCHEMY_DATABASE_URI="sqlite:///test.db" ES_HOST=<IP_ADDRESS> ES_VERSION=2.2.0 ELASTIC_URL=$ELASTIC_2_URL
- REQUIREMENTS=devel EXTRAS=all,sqlite SQLALCHEMY_DATABASE_URI="sqlite:///test.db" ES_HOST=<IP_ADDRESS> ES_VERSION=2.2.0 ELASTIC_URL=$ELASTIC_2_URL
- REQUIREMENTS=lowest EXTRAS=all,sqlite SQLALCHEMY_DATABASE_URI="sqlite:///test.db" ES_HOST=<IP_ADDRESS> ES_VERSION=5.5.3 ELASTIC_URL=$ELASTIC_5_URL
- REQUIREMENTS=release EXTRAS=all,sqlite SQLALCHEMY_DATABASE_URI="sqlite:///test.db" ES_HOST=<IP_ADDRESS> ES_VERSION=5.5.3 ELASTIC_URL=$ELASTIC_5_URL
- REQUIREMENTS=devel EXTRAS=all,sqlite SQLALCHEMY_DATABASE_URI="sqlite:///test.db" ES_HOST=<IP_ADDRESS> ES_VERSION=5.5.3 ELASTIC_URL=$ELASTIC_5_URL

Or something else?

I opened https://github.com/inveniosoftware/invenio-oaiserver/pull/132 so maybe we move discussion to there...

Screenshot from running the official migration tool on a Zenodo ES 2.3 instance:

Some changes to suggesters between ES2 and ES5
ES5 does not support "output" during indexing:

Fix indexers for Invenio-OpenAIRE and Invenio-Opendefinition
Also all deposit suggest fields will have to fetch the output from the _id, since it looks that payloads are also not returned:

Mapping "payloads" is no longer supported:

Remove "payloads" from:

https://github.com/inveniosoftware/invenio-opendefinition/blob/7b08d9ff92431343a1418019c32524de95885679/invenio_opendefinition/mappings/licenses/license-v1.0.0.json#L52
https://github.com/inveniosoftware/invenio-opendefinition/blob/7b08d9ff92431343a1418019c32524de95885679/invenio_opendefinition/mappings/licenses/license-v1.0.0.json#L52
https://github.com/inveniosoftware/invenio-openaire/blob/75ba6ed213a9dbbde1550088544dc2339eae11b7/invenio_openaire/mappings/grants/grant-v1.0.0.json#L106

One issue here is that the user-defined payload object could also contain some extra logic, as done in the invenio-openaire grants indexing (the legacy_id field is used by Javascript in the UI). Of course, this extra logic could be either moved to the body of the document (adding a legacy_id field in the mapping) or to the consumer of the response (Javascript in the UI).


Demo_Calculator: How to initialize gui.result

Hi!
Operating System:  Windows 8.1
Python version:  Python 3.7.4
guietta Port and Version:  guietta 0.3.8
Code or partial code causing the problem:
Start of Code
from guietta import _, Gui, Quit
first = True
gui = Gui(
[ "Enter numbers:",  "a", "+", "b", ["Calculate"] ],
[    "Result: -->", "result",   _,       _,             _ ],
[                _,        _,   _,       _,          Quit ]
)
with gui.Calculate:
if first:
first = False
gui.result = ""
else:
gui.result = float(gui.a) + float(gui.b)
gui.run()
End of Code
Program code: (I could not get the above code to properly indent so I attached the file.)
gCalculator.txt
Screenshots:
First display:

Error message:

Narrative:
The intention is to initialize gui.result to show blank at the first display of the screen instead of showing "result".
The code above worked but upon clicking the "Calculate" button, with or without entries in the two input fields, I get the error:
              "UnBoundLocalError: local variable 'first' referenced before assignment"

Please tell me how to initialize gui.result without causing any error to the program.
Thank you.

Hello, unfortunately the "with" syntax is quite limited and referring to variables outside scope (like "first" in you example) can be problematic.
Instead of a global variable, you can use the "gui.is_running" property:
with gui.Calculate:
        if not gui.is_running:
                gui.result = ""
        else:
                gui.result = float(gui.a) + float(gui.b)

this should work.

Thanks much, it's working now.
On Thu, Aug 13, 2020 at 10:15 PM Alfio Puglisi<EMAIL_ADDRESS>wrote:

Hello, unfortunately the "with" syntax is quite limited and referring to
variables outside scope (like "first" in you example) can be problematic.
Instead of a global variable, you can use the "gui.is_running" property:
with gui.Calculate:
if not gui.is_running:
gui.result = ""
else:
gui.result = float(gui.a) + float(gui.b)
this should work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alfiopuglisi/guietta/issues/29#issuecomment-673504596,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMUV7W534NPTNZZ7BWG6NRDSAPYQNANCNFSM4P6F7YTA
.


swiftmodule file added to linker input files when using cmake -DCMAKE_BUILD_TYPE=Debug

Description
swiftmodule file added to linker input files when using cmake -DCMAKE_BUILD_TYPE=Debug and 128+ swift files. This is mac specific. The issues is reproducible with Xcode14, but is an error in Xcode15. The issue is that when you specify -DCMAKE_BUILD_TYPE=Debug cmake will add "-g" to the options passed to swiftc (as expected) but when you have more than 128 swift source files in your library the .swiftmodule file will be added to the linker input files. Xcode14 and possibly earlier only considered this a warning but Xcode15 reports it as an error. Removing "-g" from the CMAKE_Swift_FLAGS_DEBUG will allow the library to compile but without debug info. Reducing the number of source files in the library will also avoid the issue.
Steps to reproduce
git clone https://github.com/rimim/swiftc-debug-link-issue
cd swiftc-debug-link-issue
make VERBOSE=1
Building the release target in cmake or removing "-g" from the debug flags will allow the library to link successfully:
make clean && make VERBOSE=1 WORKAROUND=1
Building using Xcode 14 will also successfully link the library (with debug info), but a linker warning is generated:
ld: warning: ignoring file swift/DummyLibrary.swiftmodule, building for macOS-arm64 but attempting to link with file built for unknown-unsupported file format ( 0xE2 0x9C 0xA8 0x0E 0x01 0x08 0x00 0x00 0x7D 0x0B 0x00 0x00 0x07 0x01 0xB2 0xC0 )
Building using Xcode 15 generates this error:
error: link command failed with exit code 1 (use -v to see invocation)
ld: unknown file type in 'swift/DummyLibrary.swiftmodule'
Expected behavior
Successfully linking the libDummyLibrary.dylib
Environment

Swift compiler: Reproducible with swiftc 5.8, 5.8.1, and 5.9.
swift-driver version: 1.87.1 Apple Swift version 5.9 (swiftlang-<IP_ADDRESS>.108 clang-15<IP_ADDRESS>)
Xcode version info Xcode 15.0 Build version 15A240d
Deployment target: MacOSX

In the Toolchains/XcodeDefault.xctoolchain/usr/bin directory rename ld to be ld_real and create a shell script named ld instead:
#!/bin/sh
LD_ARGS=()
while [[ "$#" -gt 0 ]]; do
  LD_ARGS+=("$1") # save positional arg
  case "$1" in
    -filelist)
      shift
      LD_ARGS+=("$1") # save positional arg
      sed -i.bak '/\.swiftmodule$/d' "$1"
      ;;
    *)
      ;;
  esac
  shift
done
set -- "${LD_ARGS[@]}"
DIR=$(dirname $0)
$DIR/ld_real $*

I'm hitting this too.  But I don't understand how the workaround @rimim is using could possibly work.  In my command-line the only place .swiftmodule appears is here, which looks like it's a well-formed usage, and it seems that surely if I removed just that path (which is what the workaround does) then the -emit-module-path would be missing an argument.

@rimim How did you determine that the problem starts with exactly 128 files?

@dabrahams After 127 files the swift toolchain switches to using a linker input file instead of passing each object file to the linker. The only problem is that it also passes the swiftmodule file which the linker used to just warn about, but the latest linker now considers an error. The additional complication is that Xcode is signed so modifications are a bit tricky.
Three options to workaround the issue:

Split your project into smaller libraries.

Disable debug (remove -g)

Setup a $HOME/xcode directory with the various versions of Xcode you which to support (full copy).

We use 2 and 3. Our CMakeLists.txt detects that you are building using a toolchain in the $HOME/xcode directory and we add a PRE_BUILD and POST_BUILD step to our cmake library. The PRE_BUILD step calls a script which calls "swift --version" to force the OS to ensure the toolchain gets validated if it hasn't been validated recently. Then we patch the rename the ld binary and replace it with a script that remove swiftmodules from any linker input files and calls the original ld binary. Linking succeeds. And then there is a POST_BUILD step to unpatch the toolchain. You could patch it once but eventually macOS will complain that the Xcode application is corrupt and won't let you run it anymore. Patching/unpatching seems to work reliably.
If our CMake file detects that the project is being built with /Application/Xcode.app or otherwise unwriteable then we just disable debug symbols by removing "-g" from the CMAKE_Swift flags. This also succeeds, but now you can't step through anything of course.

@dabrahams After 127 files the swift toolchain switches to using a linker input file

…which it helpfully deletes after failing! 🤦

instead of passing each object file to the linker. The only problem is that it also passes the swiftmodule file which the linker used to just warn about, but the latest linker now considers an error.

I see :(

The additional complication is that Xcode is signed so modifications are a bit tricky.

Split your project into smaller libraries.

Apparently there is a way to build a single module out of multiple libraries but I don't know how to do it yet; I'm waiting for @compnerd to fill me in.  Splitting into multiple modules might be a hard pill to swallow; we just got finished merging modules for architectural reasons.

Disable debug (remove -g)

Sorta defeats the purpose of a debug build.

Setup a $HOME/xcode directory with the various versions of Xcode you which to support (full copy).

We use 2 and 3. Our CMakeLists.txt detects that you are building using a toolchain in the $HOME/xcode directory and we add a PRE_BUILD and POST_BUILD step to our cmake library. The PRE_BUILD step calls a script which calls "swift --version" to force the OS to ensure the toolchain gets validated if it hasn't been validated recently. Then we patch the rename the ld binary and replace it with a script that remove swiftmodules from any linker input files and calls the original ld binary. Linking succeeds. And then there is a POST_BUILD step to unpatch the toolchain. You could patch it once but eventually macOS will complain that the Xcode application is corrupt and won't let you run it anymore. Patching/unpatching seems to work reliably.

What ~a mess~an impressive workaround!  I was hoping there might be a way to induce swiftc to invoke a clang wrapper instead of the one in the toolchain, but if they're serious about this signing business they're surely not going to leave a hole like that open.
So I guess the point is that until you actually need to use the debugger, a build without -g is fine, and at that point you pay the price for installing a toolchain?

SPM avoids this problem somehow, for what it's worth.  These are the commands it issues through swiftc that involve the offending .swiftmodule file in my project.
Also FWIW, I found the code in the Swift driver that is adding these files, but I can discern no connection to whether debug symbols are enabled.

swift build only calls swiftc directly to compile the source files by passing -c and then it uses swift-frontend. cmake on the other hand is using swiftc to invoke the linker.

Latest cmake solves this problem. Add:
cmake_policy(SET CMP0157 NEW)
And cmake performs a two step use swiftc to generate object files and then swiftc to link the object files.

w00t!  To be clear, that's still a workaround for a Swift bug (this one), yes?

Well I think you could also argue that cmake was using swiftc incorrectly before since swift build doesn't do this. Btw the CMP0157 policy also doesn't seem to work when cross compiling with swift. You only want CMP0157 when compiling for Apple targets. If CMP0157 is active when cross compiling then static swift libraries break for cross targets. It seems to pass -static to libtool but that's a separate issue.

Well I think you could also argue that cmake was using swiftc incorrectly

Is there a cmake bug to be filed?

You only want CMP0157 when compiling for Apple targets. If CMP0157 is active when cross compiling then static swift libraries break for cross targets. It seems to pass -static to libtool but that's a separate issue.

Oy vey.  Thanks for all the detailed info anyhow!

I'm still catching up here, but this looks like a bug in the Swift driver. I can repro it with the following shell script:
#!/usr/bin/env zsh

rm -fr src obj
mkdir -p src obj

# Create sources
pushd src
    touch a.swift

    for i in $(seq 1 1 129); do
        touch hello${i}.swift
    done

    echo "import A" >> hello1.swift
popd

pushd obj
  swiftc ../src/a.swift -module-name A -emit-library -emit-module -emit-module-path A.swiftmodule
  swiftc -g ../src/hello*.swift -module-name Hello -emit-library -I .
popd

Well I think you could also argue that cmake was using swiftc incorrectly before since swift build doesn't do this. Btw the CMP0157 policy also doesn't seem to work when cross compiling with swift. You only want CMP0157 when compiling for Apple targets. If CMP0157 is active when cross compiling then static swift libraries break for cross targets. It seems to pass -static to libtool but that's a separate issue.

What does your cross-compiling toolchain file look like? You'll need to set up the appropriate archiver for the platform you're compiling to and tell CMake what you're compiling for. I know folks are using CMP0157 on other platforms (as I have also used it for various projects) and had it work but I haven't really dug into how well it works for cross-compiling yet.

@etcwilde Technically I don't think what command-line usage is supposed to work in aggregate is actually documented, is it?  I tend to agree that it should be classified as a bug in Swift, though.  It seems quite unreasonable that the above shouldn't work.  It's interesting that your case doesn't require >128 source files.

@rimim I see a swiftc flag that could potentially be used to effect the non-intrusive wrapper workaround I was talking about, FWIW:
  -tools-directory <directory>
                          Look for external executables (ld, clang, binutils) in <directory>

I'm still catching up here, but this looks like a bug in the Swift driver. I can repro it with the following shell script:
#!/usr/bin/env zsh

rm -fr src obj
mkdir -p src obj

# Create sources
pushd src
    touch a.swift

    for i in $(seq 1 1 129); do
        touch hello${i}.swift
    done

    echo "import A" >> hello1.swift
popd

pushd obj
  swiftc ../src/a.swift -module-name A -emit-library -emit-module -emit-module-path A.swiftmodule
  swiftc -g ../src/hello*.swift -module-name Hello -emit-library -I .
popd

Well I think you could also argue that cmake was using swiftc incorrectly before since swift build doesn't do this. Btw the CMP0157 policy also doesn't seem to work when cross compiling with swift. You only want CMP0157 when compiling for Apple targets. If CMP0157 is active when cross compiling then static swift libraries break for cross targets. It seems to pass -static to libtool but that's a separate issue.

What does your cross-compiling toolchain file look like? You'll need to set up the appropriate archiver for the platform you're compiling to and tell CMake what you're compiling for. I know folks are using CMP0157 on other platforms (as I have also used it for various projects, and the CMake Windows CI is testing that it works on Windows) and had it work but I haven't really dug into how well it works for cross-compiling yet.

The issue is apparently just that my Android cross toolchain is missing libtool and CMP0157 requires libtool.

It's interesting that your case doesn't require >128 source files.

It does require more than 128 files to fail, if you turn the sequence down from 129 to 127 or 128, it compiles fine.

Technically I don't think what command-line usage is supposed to work in aggregate is actually documented, is it?

I don't know if it's documented, but this is definitely expected to work;
touch hello.swift
swiftc  hello.swift -g -emit-executable -driver-filelist-threshold=0

The issue is apparently just that my Android cross toolchain is missing libtool and CMP0157 requires libtool.

Something still sounds off about this. CMP0157 doesn't prescribe an archiver any more than CMake did before.  Alternatively, if you can reduce it, run cmake <whatever your flags are> --trace-expand 2> config.log and get me that config.log file, I can try to see where things are going off the rails.

https://gitlab.kitware.com/cmake/cmake/-/issues/25864

Oh, I totally overlooked the loop! 🤦

Alright, I think I have a fix for this; https://github.com/apple/swift-driver/pull/1581

The change merged. Can you try reproducing the issue with a recent toolchain and see if the issue is resolved? Thank you.

@etcwilde did you try @rimim's tiny reproducer?

The change merged. Can you try reproducing the issue with a recent toolchain and see if the issue is resolved? Thank you.

I can confirm that the issue is resolved in org.swift.59202404281a. Let me know if I should close this issue.

I just wanted to make sure that you had a chance to verify before closing. Thanks for checking.


python312Packages.cohere: 5.8.1 -> 5.9.0

Description of changes
Changelog: https://github.com/cohere-ai/cohere-python/releases/tag/5.9.0

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 338441 run on x86_64-linux 1

8 packages built:

python311Packages.cohere
python311Packages.cohere.dist
python311Packages.llmx
python311Packages.llmx.dist
python312Packages.cohere
python312Packages.cohere.dist
python312Packages.llmx
python312Packages.llmx.dist

Result of nixpkgs-review pr 338441 run on aarch64-darwin 1

8 packages built:

python311Packages.cohere
python311Packages.cohere.dist
python311Packages.llmx
python311Packages.llmx.dist
python312Packages.cohere
python312Packages.cohere.dist
python312Packages.llmx
python312Packages.llmx.dist

Result of nixpkgs-review pr 338441 run on x86_64-darwin 1

8 packages built:

python311Packages.cohere
python311Packages.cohere.dist
python311Packages.llmx
python311Packages.llmx.dist
python312Packages.cohere
python312Packages.cohere.dist
python312Packages.llmx
python312Packages.llmx.dist

Result of nixpkgs-review pr 338441 run on aarch64-linux 1

8 packages built:

python311Packages.cohere
python311Packages.cohere.dist
python311Packages.llmx
python311Packages.llmx.dist
python312Packages.cohere
python312Packages.cohere.dist
python312Packages.llmx
python312Packages.llmx.dist


config client not view URI - command java -jar

The my project configuration server client is displaying a difference to build, because when it is started by STS, the
cloud:
config:
failFast: true
uri: http://config-server:9888
property is visible to the maven of the build, but it is stardet to java -jar project.jar the initiator is the default location: 8888. The mvn spring-boot: run command is ok, but my business structure needs to work with java -jar. Can you help me configure config when started with jjar -jar. Thank you
bootstrap.yml
spring:
application:
name: project-name
cloud:
config:
failFast: true
uri: http://config-server:9888
eureka:
instance:
preferIpAddress: true
leaseExpirationDurationInSeconds: 2
leaseRenewalIntervalInSeconds: 2
client:
registerWithEureka: false
fetchRegistry: false
serviceUrl:
defaultZone: ${EUREKA_URI:http://eureka-server:9761/eureka}

Please learn how to properly format the code

Also you have ignored everything written in the comment when you created the issue
Thanks for raising a Spring Cloud issue. What sort of issue are you raising?

Question

Please ask questions about how to use something, or to understand why something isn't
working as you expect it to, on Stack Overflow using the spring-cloud tag.

Bug report

Please provide details of the problem, including the version of Spring Cloud that you
are using. If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

Enhancement

Please start by describing the problem that you are trying to solve. There may already
be a solution, or there may be a way to solve it that you hadn't considered.

Good Morning,
Okay, thanks for the instructions. The bootstrap.yml file was not being included in the application's classpath, I included the:
<resources>
	<resource>
		<directory>src/main/java</directory>
	</resource>
	<resource>
		<directory>src/test/java</directory>
	</resource>
	<resource>
		<directory>${basedir}/src/main/resources</directory>
		<filtering>true</filtering>
		<includes>
			<include>**/bootstrap*.yml</include>
		</includes>
	</resource>
</resources>

tag and the build worked.
Very thanks for return of my question.


Helpscout addition

We added support for use with Help Scout. Our team has tested this internally and it is working smoothly.

Thank you for your contribution. I will release a new version with Help Scout support shortly.


SSL verification is not skipped when refreshing imported automate domains when configured to on the initial clone

When cloning a git repository over HTTPS to import an automate datastore, a checkbox is presented to skip the SSL certificate verification. On future refreshes of the domain, whether via the Automate Explorer UI or the /api/automate_domains REST endpoint, the SSL verification still occurs and will fail when cloning from servers with invalid certificates.
ManageIQ version: euwe-3.20170510134343_ba3bc77

Should be resolved with https://github.com/ManageIQ/manageiq-automation_engine


Installation stuck at Upgrading NC 19

Description
Installation stuck/onhold at Upgrading NC19
Expected Behaviour

Installation running through AND
Information about progress

OR

Error Message

Actual Behaviour
Nothing (waiting already since 15')

Additional Info
it seems that it tries to fetch from nextcloud (wget) but its not displayed in install routine
(it worked after 2h of waiting and >300MB download)

The original project that this repo is forked from has the same behavior as we do, that is not reporting progress. With the low speeds you're reporting (<100KB/s) and the amount of software that we need to download (the NC package alone is 106MB), it's fairly natural that it takes such a long time. (is this your home connection or are you using a cloud provider?)
In my opinion, it might be better to suggest to the folks over at the main project to report download progress, as more people could benefit from such a change.

Really, because I rememer that in the original MIAB project, there was something like a progressbar for the wget command showing the overall progress of the download. I know that this is actually an issue with nextcloud not providing enough capacity, but it would increase the user experience for your project to state, why its currently taking so long and that its not an issue with you.
sidenote: i was using a cloud provider (exoscale)

I get your point: if download isnt instantaneous we will have no idea of how long it will take. Ill see what can be done.

I rememer that in the original MIAB project, there was something like a progressbar for the wget command showing the overall progress of the download.

How long ago was this? After all, if you spin up a new installation of the latest version (0.48 at the moment) of the original Mail-in-a-box project you dont see progress bars either.

The Mail-in-a-Box project updated their NextCloud to version 20, I've imported those changes in here.


Add 'direct_upload_' and 'direct_download_expiration' options to S3Storage to customize expiration of pre-signed URLs

This PR adds 'direct_upload_' and 'direct_download_expiration' options to S3Storage to customize expiration for pre-signed URLs. The default values of expiration are not changed.

@serihiro Thank you for checking. merging.


[ZEPPELIN-4278]: Fixed closing bracket in bin/common.cmd

What is this PR for?
Fixed closing bracket in common.cmd file, that was causing error on running zeppelin in Windows environment
What type of PR is it?
Bug Fix
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-4278
How should this be tested?
User should be able to run Zeppelin on Windows environment
Questions:

Does the licenses files need update?

No

Is there breaking changes for older versions?

No

Does this needs documentation?

No

LGTM

@msid  I have merged it , could you close this PR ?


Added username

Hello!
I am trying/tried to add usernames. It may be unnecessary, I know, but i need it for my project, so why not create a PR?
Disclaimer

I am a Noob with SQL-Stuff, so please don't blame me for the bad code.
I'll revert all the changes to the README before a merge
I am very likely too lazy to write the docs, so help would be really nice ❤ !

I would be very happy if you would give me some tips how I could make the code better.

I really struggle with OAuth...

Yes, I give up for now! I'm having problems with:

The the registration to check if the username is unique
With OAuth at all
Writing useful tests

Things I did:

Implemented the database-schemas
Implemented query-functions
Wrote tests for the database-queries
Made older tests work with adding an username-property
Spent 4 1/2 hours on it


[Bug Report]: what is "internal" in players heads?

Spark link
No response
Server Version
1.16.5
Server Platform
Spigot
Describe the bug
i'm trying to add some custom head from the site "custom heads generator" and some of them has a thing called "internal" which is different from the others, but then the rest doesn't have the "internal: [code]" thing. Why and how to fix it? cause the ones that does not have that code, the head it's just a normal player head.
example:
OverworldDragon:
DisplayName: Overworld Dragon
DisplayItem: PLAYER_HEAD
DisplayAmount: 1
MaxRange: 100
Lore:
- 'The Overworld Ruler.'
- 'Chance: 1%'
Chance: 1.0
Commands:
- 'broadcast %player% has just won the &2Overworld Dragon (1%)!'
Message:
- 'You just won an &2Overworld Dragon (1%).'
Editor-Items:
- ==: org.bukkit.inventory.ItemStack
v: 2586
type: PLAYER_HEAD
meta:
==: ItemMeta
meta-type: SKULL
display-name: '{"text":"Overworld Dragon"}'
internal: H4sIAAAAAAAAAE3PO07DMADGcfOoVAJX4A5O0gZ1YKhKRB3VDqTOw2ZqE1eJ45QqjyrhKpyAEYkDAWsvgUfGT//f8hkAGOBmXXZKPdWvu0KJa3COMgDAZfOCby/m5OPzNDq9/37/GMDQ5CDqthDNFRi3om+7WjSGxmdjMIo2qhPgSwwe5EkOs8RT6YAcvekaKh/Jwx3aR8N2gRxU6b6cO6th9s9O2008Vcz2cr5/7rZVBFd2oMQyMNMqPBLJJY9DSCgzucwKJtGEWIHEb2XPKtfmlWtiy+15RQr8kE4YzSWmpaVNwWOvxDQviQx7nzLoP3qKSVLyhTfbJfBePwB/qZmreAoBAAA=
how we can see there is a thingy called "internal" but in others that thing does not exist... why?
Steps to reproduce

Additional context
if there is a way to fix it please tell me... cause for now the 70% of the create rewards are totally broken and not working...
for any problem, the heads commands are these:
/give @p minecraft:player_head{display:{Name:"{"text":"Overworld Dragon"}"},SkullOwner:{Id:[I;1935363357,54611625,-1309997589,-1679630111],Properties:{textures:[{Value:"eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvNjZjZWU0NTY1ZjdiYjI4N2RjMzkxYmE3ZmE1M2ExZmNiMDc4YThjMTk2N2RiZWJkMThkNjUxOTY0OGJlYjNkZCJ9fX0="}]}}} 1
/give @p minecraft:player_head{display:{Name:"{"text":"End Dragon"}"},SkullOwner:{Id:[I;1185748012,1572095227,-1360977709,1907579260],Properties:{textures:[{Value:"eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvZWFkN2RjYmU5MzQwMWIzZDNiNGU1MjIyZWY4MDk3YWVmNDQzMWY0ODA2NGQwYTA1MzFmYTA5NTJjMjExZTBlNiJ9fX0="}]}}} 1
Agreements

[X] I have searched for and ensured there isn't already an open issue regarding this.
[ ] I ticked all the boxes without actually reading them
[ ] My version of Minecraft is supported by CrazyCrew.

You used /cc additem which doesn't give you control over what it spits out and you can't edit that.
You need to use old papermc builds for 1.16.5 to get player heads to work. We don't control what that command outputs, We only run it as you give it to us. My recommendation is to use the Items: section for giving player heads. I've attached a screenshot.

If this still does not work, There not much else I can do as we don't update with 1.16.5 support included anymore.


[web]: NavigationRail selectedIconTheme not working

In my app, I use
NavigationRail(
            backgroundColor: Colors.grey,
            unselectedIconTheme: IconThemeData(color: Colors.black, size: 30.0),
            selectedIconTheme: IconThemeData(color: Colors.white, size: 30.0),
            selectedIndex: _selectedIndex,

This works as expected on a mobile phone. But on the web, the selected Icon is black,
not white. Debug mode or release mode makes no difference.
Flutter 1.17.0 • channel beta • https://github.com/flutter/flutter.git
Framework • revision e6b34c2b5c (2 weeks ago) • 2020-05-02 11:39:18 -0700
Engine • revision 540786dd51
Tools • Dart 2.8.1

Share with us your Navigation Destinations and onDestinationSelected Function

OK, here is the complete body. (The icons mimic buttons in an elevator. I don't want any labels. The label keyword should be optional, but that is another story.)
      body: Row(
        children: <Widget>[
          NavigationRail(
            backgroundColor: Colors.grey,
            unselectedIconTheme: IconThemeData(color: Colors.black, size: 30.0),
            selectedIconTheme: IconThemeData(color: Colors.white, size: 30.0),
            selectedIndex: _selectedIndex,
            onDestinationSelected: (int index) {
              int toPage = index;
              if (streetNo == 7) toPage = toPage + 6;
              pageController.animateToPage(toPage,
                  duration: Duration(milliseconds: 2000),
                  curve: Curves.easeInOut);
              setState(() {
                _selectedIndex = index;
              });
            },
            labelType: NavigationRailLabelType.none,
            destinations: [
              NavigationRailDestination(
                  icon: streetNo == 7
                      ? Icon(Icons.remove)
                      : ImageIcon(AssetImage('assets/images/7.png')),
                  label: Container()),
              NavigationRailDestination(
                  icon: ImageIcon(AssetImage('assets/images/6.png')),
                  label: Container()),
              NavigationRailDestination(
                  icon: ImageIcon(AssetImage('assets/images/5.png')),
                  label: Container()),
              NavigationRailDestination(
                  icon: ImageIcon(AssetImage('assets/images/4.png')),
                  label: Container()),
              NavigationRailDestination(
                  icon: ImageIcon(AssetImage('assets/images/3.png')),
                  label: Container()),
              NavigationRailDestination(
                  icon: ImageIcon(AssetImage('assets/images/2.png')),
                  label: Container()),
              NavigationRailDestination(
                  icon: ImageIcon(AssetImage('assets/images/1.png')),
                  label: Container()),
            ],
          ),
          Expanded(
            child: PageView.builder(
                controller: pageController,
                scrollDirection: Axis.vertical,
                onPageChanged: (page) {
                  setState(() {
                    if (page < 7) {
                      mask = '2' + (8 - page).toString();
                      color = Color(0xFF7B919E);
                      _selectedIndex = page;
                      streetNo = 3;
                    } else {
                      mask = '1' + (14 - page).toString();
                      color = Color(0xFF977981);
                      _selectedIndex = page - 6;
                      streetNo = 7;
                    }
                    // print(mask);
                  });
                },
                // itemCount: floors.length,
                itemCount: 13,
                itemBuilder: (context, index) {
                  return Card(
                      color: color,
                      margin: const EdgeInsets.all(8.0),
                      child: Column(
                          mainAxisAlignment: MainAxisAlignment.spaceEvenly,
                          children: [
                            AptCard(mask + '1'),
                            AptCard(mask + '2'),
                            AptCard(mask + '3'),
                          ]));
                }),
          ),
        ],
      ),

I tested the web version using Chrome version 81.0.4044.138 on Windows 10 and on an iPad. Same result.

Hi @BoHellgren
Testing this on latest on latest beta channel, selected icon and unselected icons are. black and white

Code Sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      title: 'Material App',
      home: Home(),
    );
  }
}

class Home extends StatefulWidget {
  @override
  _HomeState createState() => _HomeState();
}

class _HomeState extends State<Home> {
  int _selectedIndex = 0;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Material App Bar'),
      ),
      body: Row(
        children: <Widget>[
          NavigationRail(
            backgroundColor: Colors.grey,
            unselectedIconTheme: IconThemeData(color: Colors.black, size: 30.0),
            selectedIconTheme: IconThemeData(color: Colors.white, size: 30.0),
            selectedIndex: _selectedIndex,
            onDestinationSelected: (int index) {
              setState(() {
                _selectedIndex = index;
              });
            },
            labelType: NavigationRailLabelType.selected,
            destinations: [
              NavigationRailDestination(
                icon: Icon(Icons.favorite_border),
                selectedIcon: Icon(Icons.favorite),
                label: Text('First'),
              ),
              NavigationRailDestination(
                icon: Icon(Icons.bookmark_border),
                selectedIcon: Icon(Icons.book),
                label: Text('Second'),
              ),
              NavigationRailDestination(
                icon: Icon(Icons.star_border),
                selectedIcon: Icon(Icons.star),
                label: Text('Third'),
              ),
            ],
          ),
          VerticalDivider(thickness: 1, width: 1),
          // This is the main content.
          Expanded(
            child: Center(
              child: Text('selectedIndex: $_selectedIndex'),
            ),
          )
        ],
      ),
      floatingActionButton: FloatingActionButton(
        child: Icon(Icons.add),
        onPressed: () {},
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel beta, 1.18.0-11.1.pre, on Mac OS X 10.15.4 19E287, locale en-GB)
    • Flutter version 1.18.0-11.1.pre at /Users/tahatesser/Code/flutter_beta
    • Framework revision 2738a1148b (5 days ago), 2020-05-13 15:24:36 -0700
    • Engine revision ef9215ceb2
    • Dart version 2.9.0 (build 2.9.0-8.2.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/SDK
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1

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

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.8052
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

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

[✓] Connected device (3 available)
    • SM M305F   • 32003c30dc19668f • android-arm64  • Android 10 (API 29)
    • Web Server • web-server       • web-javascript • Flutter Tools
    • Chrome     • chrome           • web-javascript • Google Chrome 81.0.4044.138

• No issues found!

Can you please upgrade to latest beta channel and try this code sample?
Thank you

@BoHellgren you cant use ImageIcon with IconThem, Icon Them just change 'Icon' settings.
ImageIcon(NetworkImage('https://cdn.onlinewebfonts.com/svg/img_412615.png'),color: selectedId == 0 ? Colors.black:Colors.white,);
you should use like this

CC @clocksmith

@Abdusin  ImageIcon with IconThemeData works perfectly - on the mobile. So it should work on the web also. But you are right in that it is the use of ImageIcon that causes the problem on the web.
@TahaTesser Your sample works. But when I change
icon: Icon(Icons.favorite_border),
selectedIcon: Icon(Icons.favorite),

to
icon: ImageIcon(AssetImage('assets/images/1.png')),

it still works on the mobile, but not on the web.
I did a Flutter upgrade to
Flutter 1.18.0-11.1.pre • channel beta • https://github.com/flutter/flutter.git
Framework • revision 2738a1148b (5 days ago) • 2020-05-13 15:24:36 -0700
Engine • revision ef9215ceb2
Tools • Dart 2.9.0 (build 2.9.0-8.2.beta)

but it made no difference.

Hi @BoHellgren
Issue exist on beta but not reproducible on dev channel

Code Sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      title: 'Material App',
      home: Home(),
    );
  }
}

class Home extends StatefulWidget {
  @override
  _HomeState createState() => _HomeState();
}

class _HomeState extends State<Home> {
  int _selectedIndex = 0;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Material App Bar'),
      ),
      body: Row(
        children: <Widget>[
          NavigationRail(
            backgroundColor: Colors.grey,
            unselectedIconTheme: IconThemeData(color: Colors.black, size: 30.0),
            selectedIconTheme: IconThemeData(color: Colors.red, size: 30.0),
            selectedIndex: _selectedIndex,
            onDestinationSelected: (int index) {
              setState(() {
                _selectedIndex = index;
              });
            },
            labelType: NavigationRailLabelType.selected,
            destinations: [
              NavigationRailDestination(
                icon: ImageIcon(AssetImage('assets/flight.png')),
                selectedIcon: ImageIcon(AssetImage('assets/flight.png')),
                label: Text('First'),
              ),
              NavigationRailDestination(
                icon: Icon(Icons.bookmark_border),
                selectedIcon: Icon(Icons.book),
                label: Text('Second'),
              ),
              NavigationRailDestination(
                icon: Icon(Icons.star_border),
                selectedIcon: Icon(Icons.star),
                label: Text('Third'),
              ),
            ],
          ),
          VerticalDivider(thickness: 1, width: 1),
          // This is the main content.
          Expanded(
            child: Center(
              child: Text('selectedIndex: $_selectedIndex'),
            ),
          )
        ],
      ),
      floatingActionButton: FloatingActionButton(
        child: Icon(Icons.add),
        onPressed: () {},
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel dev, 1.19.0-1.0.pre, on Mac OS X 10.15.4 19E287, locale en-GB)
    • Flutter version 1.19.0-1.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 456d80b9dd (7 days ago), 2020-05-11 11:45:03 -0400
    • Engine revision d96f962ca2
    • Dart version 2.9.0 (build 2.9.0-7.0.dev 092ed38a87)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/SDK
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1

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

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.8052
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

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

[✓] Connected device (5 available)
    • SM M305F   • 32003c30dc19668f                     • android-arm64  • Android 10 (API 29)
    • iPhone 11  • B00B6F4E-B1CE-44F3-B81E-3EC6D639B008 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-13-4 (simulator)
    • macOS      • macOS                                • darwin-x64     • Mac OS X 10.15.4 19E287
    • Web Server • web-server                           • web-javascript • Flutter Tools
    • Chrome     • chrome                               • web-javascript • Google Chrome 81.0.4044.138

• No issues found!

Please upgrade to dev channel or wait for the fix to land in the beta channel
if you disagree please write in the comments and I will reopen it
Thank you

Further testing shows that this bug has nothing to do with NavigationRail.
The problem is that the AssetImage color property is ignored on the web!
I changed
floatingActionButton: FloatingActionButton(
        child: Icon(Icons.add),
        onPressed: () {},
      ),

to
 floatingActionButton: FloatingActionButton(
        child: ImageIcon(AssetImage('assets/images/2.png'), color: Colors.orange,),
        onPressed: () {},
      ),

On the mobile, the FAB icon i orange, as it should be. On the web, it is black!
Could you make a quick to verify that this is fixed on channel dev?

using icons from  https://material.io/resources/icons/?style=baseline

flutter doctor -v
[✓] Flutter (Channel dev, 1.19.0-1.0.pre, on Linux, locale en_US.UTF-8)
    • Flutter version 1.19.0-1.0.pre at /home/tesser/Code/flutter_dev
    • Framework revision 456d80b9dd (8 days ago), 2020-05-11 11:45:03 -0400
    • Engine revision d96f962ca2
    • Dart version 2.9.0 (build 2.9.0-7.0.dev 092ed38a87)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /home/tesser/Code/SDK
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /home/tesser/Code/SDK
    • Java binary at: /home/tesser/Code/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Android Studio (version 3.6)
    • Android Studio at /home/tesser/Code/android-studio
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.8052
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.45.1)
    • VS Code at /usr/share/code
    • Flutter extension version 3.10.2

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API
      29) (emulator)

• No issues found!


draft:  increase test coverage in packages/{server,tools}

Description

Task Item

Screenshots

Coverage increased (+0.8%) to 39.675% when pulling e88cf1edb04b520236d49fccd44184cec04b2313 on zhixzhan/test-coverage into 74299ee0138136d2b3c70c8d6333891302b5edb5 on master.


remove console and set a basic catch on lock

@Nauna What makes a basic catch different from a regular one?


Version 3.5.1 available

Hi, new version is available on https://www.thepay.cz/ke-stazeni/
Can you update your package?

Thank you, it is out https://github.com/Trejjam/ThePay-lib/releases/tag/v3.5.1


Add Unspecified to SameSiteStatus

fix the bug I found

Hi, thanks for your contribution!
Two comments on this PR:

The JavaScript files shouldn't be changed and shouldn't produce any error since optional chaining is supported by all the JS runtime.
The enum file is generated dynamically so any change here will be overwritten the next time the generator runs.

I am not going to merge this but I will look into a way of adding this enum when it gets generated.


Fix broken badges, update repo names and "❤ OSS" image

Codecov Report

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

@@           Coverage Diff           @@
##           master     #436   +/-   ##
=======================================
  Coverage   39.14%   39.14%
=======================================
  Files           7        7
  Lines         866      866
  Branches      121      121
=======================================
  Hits          339      339
  Misses        527      527

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 978fd2e...cc9a36a. Read the comment docs.


Make the SE driver provider-agnostic

The SE Driver was only targeting the TPM provider. This behaviour has
been changed to be provider-agnostic: by default the SE driver will
target the highest priority provider returned by the ListProviders
operation. Features are introduced to also have a way to select a single
provider.
This commit also pull the newest psa-crypto with the new interface
feature. This SE driver does not need to link with the PSA Crypto
implementation but only needs the interface implementation.
Fix #7
Signed-off-by: Hugues de Valon<EMAIL_ADDRESS>

Depends on parallaxsecond/rust-psa-crypto#39 to be merged and released

I think the CI scripts executed to check this PR are not the ones I changed there and that is why it is failing. It is weird as I think that before it was using the scripts inside the PR.


Duplicated IBFT2 messages are not discarded when counting the Prepare messages included in a Prepared Certificate

Description
Actual Behaviour
Duplicated IBFT2 messages are not discarded when counting the Prepare messages included in a Prepared Certificate
Expected behaviour:**
Either

Duplicated Prepare messages are discarded when counting the Prepare messages included in a Prepared Certificate
Message senders are counted and duplicated senders are discarded

Additional Information
This bug was discovered as part of the formal specification and verification of an alternative BFT consensus protocol based on IBFT2.

Fixed by #1671


refactor(api): mark separate_calibration properties as deprecated

Overview
Tiny PR to knock out a NotImplementedError in the PAPI engine core by way of removal.
Closes RCORE-416
Changelog

Log a warning if you try to use Labware.separate_calibration or ModuleGeometry.separate_calibration

Review requests
Standard code review
Risk assessment
Very low

I'd also support straight-up removing these methods, unless you have reason to believe they're used in user-written protocols.

I had that though, too, but at the end of the day, these methods create almost zero maintenance burden; I think leaving them the safer choice


Wrong use of nls-utils in untitledTextEditorHint.ts

src/vs/workbench/contrib/codeEditor/browser/untitledTextEditorHint.ts
there is string concatenation of nls-strings, like this and much more
This is usually wrong because it assumes that all languages use similar sequences. The localize-function support replacements for cases like this and in this specific case we might be better off using a markdown string with command-links

/cc @isidorn who original did this: please speak up if there is more code like this

I have some changes in joh/innocent-tiger that will fix this


Sea Block compatibility

Sea block changes the recipe for several buildings. When Sea Block is enabled, can you show these as a different tier?

Algae farm 3: T4 > T3
Filtration unit 1: T2 > T1
Crystallizer 1: T2 > T1

Is this Sea Block as it is currently release, or Sea Block as it will be released shortly?

Filtration unit and Crystallizer are the same. This is the current Algae farm 3 recipe:

Commit kirazy/reskins-angels@2a401e0479ecb90596bf38dd0fa39cbec85cd754 fixes this.

Found one more, sorry! Chemical plant 1 needs to go from T2 down to T1.

Adding so it's logged:
Plasma Turret 1 takes red circuits, should be T3.
Plasma Turret 2 takes blue circuits, should be T4.
Higher tiers of plasma turrets are hidden.
All this in Sea Block 0.5.5

Was there something that was still needed for this, Kiwi?

Nope, all looks good from a Sea Block perspective!


Add FAQ to specification.ardalis.com (docs)

Add a FAQ section.
Include information about which versions of apps/EF can consume which version of Ardalis.Specification.
See #312 for example.

Hey @ardalis! Big fan of your work. I opened a PR on this adding this matter to the FAQ.


How to ingrate Sharp to Nuxtjs

Hello,
I have an app Nuxt3 and I want to integrate Sharp to my Nuxt app to optimize image, mainly for resize image for each breakpoint.
I can't find documentation to this on your website.
Can you please show me the link for documentation or instruct me how to integrate Sharp to Nuxt3?
Thank you

Did you see https://image.nuxt.com/providers/ipx ?

@lovell yes I already read it.
IPX only work on localhost, all images work. But when deploy my website to AWS, all images are not rendered. I seems IPX not compatible with AWS because many people have the same problem with me. It also not work with Netlify either.
So I am trying to integrate directly Sharp to my Nuxt instead of using IPX.
Thank you.

seems IPX not compatible with AWS because many people have the same problem with me

There are zero issues when searching for AWS in the ipx repo.
https://github.com/search?q=repo%3Aunjs%2Fipx+(AWS+OR+Amazon)&type=issues

It also not work with Netlify either.

Did you see https://image.nuxt.com/providers/netlify ? What did Netlify say when you asked them?
The summary here is that you will almost certainly be better off using all the great work already done by the Nuxt team rather than rolling your own solution.

Thank you @lovell . I have not checked with netlify. I think there would be some problem with my codes.

I hope this information helped. Please feel free to re-open with more details if further assistance is required.


Perform analysis on multistage Dockerfiles

Describe the Feature
Tern can read a Dockerfile, build and image and analyze the image to provide a report and pin a Dockerfile. However, it cannot do these for multistage Dockerfiles accurately because the intermediate stages get thrown away after a build is complete. Why not enable analysis and pinning for multistage Dockerfiles?
Use Cases
Multistage Dockerfiles are the de-facto build mechanism for golang projects in particular. A Dockerfile will typically use the golang image to build and an alpine image to deploy the built golang binary.
Implementation Changes
A proposed implementation can look like this:

Split the Dockerfile by stage, making a single Dockerfile for each stage
Build and analyze each stage
For reporting, perhaps organize each stage as a different section and indicate that each is a build stage of the next. Pinning a multistage Dockerfile is straightforward.

@nishakm  that sounds awesome i will start looking into it.

Maybe i can work on this issue!

Hi nisha, I am considering this way of spliting:
Multistage Dockerfile
FROM golang:1.7.3
WORKDIR /go/src/github.com/alexellis/href-counter/
RUN go get -d -v golang.org/x/net/html
COPY app.go .
RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app .

FROM alpine:latest
RUN apk --no-cache add ca-certificates
WORKDIR /root/
COPY --from=0 /go/src/github.com/alexellis/href-counter/app .
CMD ["./app"]

into
Stage 1
FROM golang:1.7.3
WORKDIR /go/src/github.com/alexellis/href-counter/
RUN go get -d -v golang.org/x/net/html
COPY app.go .
RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app .

Stage 2
FROM golang:1.7.3
WORKDIR /go/src/github.com/alexellis/href-counter/
RUN go get -d -v golang.org/x/net/html
COPY app.go .
RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app .

FROM alpine:latest
RUN apk --no-cache add ca-certificates
WORKDIR /root/
COPY --from=0 /go/src/github.com/alexellis/href-counter/app . # Copy file from previous stage.
CMD ["./app"]

I am not spliting into seperate stages since the second stage may need to copy files from the previous stage. We can build these two dockerfiles and perform analysis on each image. Then organize the report by stage.

@ForgetMe17 That makes sense to me. All the information collected when analyzing an image built from Dockerfile1 are stored in the Image object. So you can instantiate stage1 = DockerImage(repotag1) for the first image and stage2 = DockerImage(repotag2) for the second image. But some of the reports do not take more than one image (most notably the SPDX tag-value) so, focusing on the default report and Dockerfile lock is enough for this part.


sp_query_store_consistency_check doesn't exist in SQL 2016

"Verify Query Store is collecting query data continuously" section suggests running the sp_query_store_consistency_check procedure if the query store gets corrupted, but this sproc does not exist in SQL 2016, only SQL 2017 and later.
See also: https://dba.stackexchange.com/questions/237521/trying-to-repair-query-store-but-sp-query-store-consistency-check-does-not-exis

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

ID: 155bfbc5-9c63-32c6-9d06-a9b3cdb4c60e
Version Independent ID: c854b2de-e509-e320-8151-67d690d486ed
Content: Best Practice with the Query Store - SQL Server
Content Source: docs/relational-databases/performance/best-practice-with-the-query-store.md
Product: sql
Technology: performance
GitHub Login: @julieMSFT
Microsoft Alias: jrasnick

thanks for the feedback! I've assigned this to the author @julieMSFT
Thanks!

Hi @IanKemp, Thank you for bringing this to our attention. I will be updating the documents to state that sp_query_store_consistency_check only works with SQL version 2017 and later. For a 2016 version that is in an error state the only possible mitigation would be to run the following which will clear out the data:
ALTER DATABASE [YourDatabaseName]
SET QUERY_STORE CLEAR ALL;
Please let me know if you need anything further, or if I can proceed with closing out this Git Issue. Thanks!

#10229

Hi @IanKemp, I have updated the documents to reflect that sp_query_store_consistency_check only works for SQL 2017 and later. The updates will go live later today. I will proceed with closing out this Git Issue, but please feel free to respond should you need anything further. Thanks!

hi, may i know what is the impact of "sp_query_store_consistency_check" ? does it will block the transaction or what is the impact? i have search but found nothing.
thanks

@TwoUnder Matt, can you comment on this customer question?

@maadityo this is a recovery sp and can only execute against a database that has the Query Store feature disabled, so shouldn't affect user workload.


Update Clima and remove LTE Cleaner

Clima has been moved to Codeberg:
https://codeberg.org/Lacerte/clima
LTE Cleaner's development has ceased:
https://github.com/TheRedSpy15/LTECleanerFOSS?tab=readme-ov-file#notice
Sorry if this isn't the proper way to contribute.

Hi!
Thanks.
That's the proper way, I'm not picky. You can also lend me a hand by creaing a pull request ;)
Done with https://github.com/Psyhackological/AAA/commit/2e10cb973d728c5c3fdc1f1065390710fb5a1241.


Real_FITS and FITS

Does Real_FITS get the same result as the FITS experiment? There are slight differences in the code, e.g. self.freq_upsampler

As far as I know, voltage, current, sound intensity, temperature and other physical quantities can be directly measured in the real world. The values of these signals do not contain imaginary components.

They should produce the same result as the FITS. real_FITS just use the commonly used real-valued linear layer to simulate the complex-valued linear combination operation in FITS. We implement the real_FITS just to make it applicable on devices that currently do not support complex operation, e.g. RTX4090.
Yes, indeed. Almost all the signal can be measured are present in real-value. However, FITS perform the linear operation on the frequency domain which is inherently a complex-valued domain. (also the real_FITS)
Hope this can help!

You can check the detail here for your reference: https://github.com/VEWOXIC/FITS/issues/3#issuecomment-1998953111

If there is no further question. I will close this issue.
Please feel free to reopen it if you need any help.

I have a question, should I add linear_end to the evaluation, or use the NTH variable, when using a multivariable prediction model that similar to yours to implement a multivariable prediction for a single variable? Although the output of the NTH variable of the model is different, adding linear at the end will generally improve and the difference is not large

Sorry, what is the linear_end and NTH variable? Are they used in our FITS?

Yes, I did. Your task is to predict multiple variables, and what I'm trying to do is to predict one variable by use multiple variables. linear_end is what I add to the end and turns the output into one variable, which is the NTH variable

What I want to know is whether this comparison should be made using the variable in the output channel or using linear_end to become a channel

Seems you are making some modification on the FITS right?
Using a linear layer to fuse information from multiple channel can be a good idea to boost the forecasting performance. But as you mention, the improvement can be very marginal.
May I know some more detail about the comparison? I still do not get it. What is the task setting and what are we comparing?

Let me make a big example, the height of a glass of water is closely related to the area and temperature, so I use the water level, temperature, and area as variables, but I only need the water level, so I use a linear layer to become a channel, which improves the accuracy.So I'm confused about which precision to use for comparison

Okay, now I understand that you are fusing the information from all the input channels to boost the forecasting performance.
If you are using some standardized benchmark dataset, you can compare some baseline models that already report their performance. It is up to your task definition.

Thanks for your patience. I am using a new data set, so it is difficult for me to choose baseline. Anyway, I'll cite your work, which is really good

Thanks for your recognition! Good luck with your paper!


update whatis.md

@mohamadsolouki could you squash this into one commit and sign it off? it would look something like
git rebase -i HEAD~7 (or whatever the right number is to get your commits), then git commit --amend -s then git push --force-with-lease ...


[fix] empty name query item throws validation error.

Fixes https://github.com/loadimpact/har-to-k6/issues/38

You're right hah 😅 I didn't see the it in the rendered output so I assumed it was working.. however concatenating a string with an empty string doesn't leave much of a trail heh..

Fixing it in a sec..


Create README.md for python tests

Description
Adding test README.md files for various python tests
Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #1984 (889a856) into main (ece7213) will increase coverage by 0.24%.
The diff coverage is n/a.

:exclamation: Current head 889a856 differs from pull request most recent head 204f0d6. Consider uploading reports for the commit 204f0d6 to get more accurate results

@@            Coverage Diff             @@
##             main    #1984      +/-   ##
==========================================
+ Coverage   94.17%   94.41%   +0.24%
==========================================
  Files          95       18      -77
  Lines        4722      412    -4310
==========================================
- Hits         4447      389    -4058
+ Misses        275       23     -252

Flag
Coverage Δ

unittests
94.41% <ø> (+0.24%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

responsibleai/responsibleai/_internal/constants.py

responsibleai/responsibleai/_tools/__init__.py

erroranalysis/erroranalysis/report/__init__.py

...tabalanceanalysis/distribution_balance_measures.py

erroranalysis/erroranalysis/report/error_report.py

...i_test_utils/models/sklearn/sklearn_model_utils.py

responsibleai/responsibleai/__version__.py

...ponsibleai/responsibleai/modelanalysis/__init__.py

responsibleai/responsibleai/_interfaces.py

erroranalysis/erroranalysis/_internal/constants.py

... and 67 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.