CloudEvent Result Enrichment only works for Flux or normal Spring Message's but not for Mono

Describe the bug
I have an easy function
@Bean
    public Function<Mono<Person>, Mono<Person>> uppercase() {
        return personMessage -> personMessage.map(person -> {
                person.setFirstName("eh");
                return person;
            }
        );
    }

@Component
public class ProxyActivatedEventMapper implements CloudEventHeaderEnricher {

	private static final String TYPE = "ProxyActivated";

	@Override
	public CloudEventMessageBuilder<?> enrich(final CloudEventMessageBuilder<?> messageBuilder) {
		return messageBuilder.setType(TYPE).setHeader("detail-type", TYPE);
	}

}

Im using the following to invoke:
curl --location --request POST 'localhost:8080' \
--header 'Content-Type: application/cloudevents+json' \
--data-raw '{
    "specversion": "1.0",
    "type": "com.sbsa.payments.proxy.core.api.model.Proxy",
    "source": "https://spring.io/",
    "id": "A234-1234-1234",
    "datacontenttype": "application/json",
    "data": {
        "firstName": "jef",
        "lastName": "dun"
    }
}'

When I receive the result, Its not in cloudevent format (no http headers for cloudevents).
My CloudEventHeader enricher was also not invoked.
After debugging deeper, I can see the following:
https://github.com/spring-cloud/spring-cloud-function/blob/main/spring-cloud-function-context/src/main/java/org/springframework/cloud/function/context/catalog/SimpleFunctionRegistry.java#L844
SimpleFunctionRegistry.java
               if (result instanceof Flux && functionInvocationHelper != null) {
			result = ((Flux) result).map(v -> {
				if (firstInputMessage.get() != null && CloudEventMessageUtils.isCloudEvent(firstInputMessage.get())) {
					return functionInvocationHelper.postProcessResult(v, firstInputMessage.get());
				}
				return v;
			});
		}

		return value instanceof OriginalMessageHolder
				? this.enrichInvocationResultIfNecessary(((OriginalMessageHolder) value).getOriginalMessage(), result)
				: result;

There is no result enrichment happening for Mono? Only Flux?
Proposal:
	if (result instanceof Mono && functionInvocationHelper != null) {
			result = ((Mono) result).map(v -> {
				if (firstInputMessage.get() != null && CloudEventMessageUtils.isCloudEvent(firstInputMessage.get())) {
					return functionInvocationHelper.postProcessResult(v, firstInputMessage.get());
				}
				return v;
			});
		}

I am not sure if the above would work at all, but just wanted to mention this issue Ive faced if it would bring value to the project, as I believe this issue will cause confusion for future developers using cloudevents and spring cloud function. For now Ive changed from using Mono to using Flux which works as a workaround

Thanks a lot @OlegDokuka ! That was some quick response with a fix.

wrong oleg

🤣. I got used to that @olegz 😁. May be it is a sign 😂


request:  Add support for defaulting to either yes or no (or improve --yes / --skip)

Is there an existing feature request for this?

[X] I have searched the existing issues.

Command
flutterfire configure --default no
Description
I would like to default to yes or no to the various command prompts.
This is different than the yes / skip argument, which would always use the default value.
Reasoning
I would like to automate the configure commands in a script and be able to skip user input but use a value other than the default value.
Additional context and comments
Maybe the -y --yes argument could be changed to -s --skip as "yes" is a bit less descriptive. Even better a -s --skip argument could default to the default value, or you could supply either a "default", "yes" or "no" value after to determine what to choose.

I don't think this is an issue on the latest FlutterFire CLI.
dart pub global activate flutterfire_cli 0.3.0-dev.18 --overwrite

The only thing --yes is used for now is for platform selection. If you choose platforms, it is not needed. Example:
flutterfire configure --project=project-name --platforms=android

We auto detect the previous things that required the default CLI flag --yes.


Unable to change background color of gps text

Hi there! Ive changed the symbol colors but the bg color of the text doesnt change ( even in my statusline )
The symbols take colors from my cmpkind highlight groups

But Im unable to change the background color of the text of gps (plugins, config in this case)

Similar issue on lualine. Basically same config.

Similar issue on lualine with the exact same config.

the symbols seem to use bg color from cmpkind highlight groups but the text look normal to me :think

Fixed the issue

I defined a separate list of highlight groups for GPS ( which changes fg/bg color of the symbols) and change bg color of "Statusline" highlight group, ig gps uses that for its text

I defined a separate list of highlight groups for GPS ( which changes fg/bg color of the symbols) and change bg color of "Statusline" highlight group, ig gps uses that for its text

Could you please explain a bit more on how you fixed this? I am having a hard time adding colors to gps-nvim. Thanks

I defined a separate list of highlight groups for GPS ( which changes fg/bg color of the symbols) and change bg color of "Statusline" highlight group, ig gps uses that for its text

Could you please explain a bit more on how you fixed this? I am having a hard time adding colors to gps-nvim. Thanks

local present, gps = pcall(require, "nvim-gps")

if not present then
   return
end

local icons = require "plugins.configs.lspkind_icons"

local options = {
   depth = 5,

   icons = {
      ["class-name"] = "%#GpsItemKindClass#" .. icons.Class .. "%*" .. " ",
      ["function-name"] = "%#GpsItemKindFunction#" .. icons.Function .. "%*" .. " ",
      ["method-name"] = "%#GpsItemKindMethod#" .. icons.Method .. "%*" .. " ",
      ["container-name"] = "%#GpsItemKindProperty#" .. icons.Object .. "%*" .. " ",
      ["tag-name"] = "%#GpsItemKindKeyword#" .. icons.Tag .. "%*" .. " ",
      ["mapping-name"] = "%#GpsItemKindProperty#" .. icons.Object .. "%*" .. " ",
      ["sequence-name"] = "%GpsItemKindProperty#" .. icons.Array .. "%*" .. " ",
      ["null-name"] = "%GpsItemKindField#" .. icons.Field .. "%*" .. " ",
      ["boolean-name"] = "%GpsItemKindValue#" .. icons.Boolean .. "%*" .. " ",
      ["integer-name"] = "%GpsItemKindValue#" .. icons.Number .. "%*" .. " ",
      ["float-name"] = "%GpsItemKindValue#" .. icons.Number .. "%*" .. " ",
      ["string-name"] = "%GpsItemKindValue#" .. icons.String .. "%*" .. " ",
      ["array-name"] = "%GpsItemKindProperty#" .. icons.Array .. "%*" .. " ",
      ["object-name"] = "%GpsItemKindProperty#" .. icons.Object .. "%*" .. " ",
      ["number-name"] = "%GpsItemKindValue#" .. icons.Number .. "%*" .. " ",
      ["table-name"] = "%GpsItemKindProperty#" .. icons.Table .. "%*" .. " ",
      ["date-name"] = "%GpsItemKindValue#" .. icons.Calendar .. "%*" .. " ",
      ["date-time-name"] = "%GpsItemKindValue#" .. icons.Table .. "%*" .. " ",
      ["inline-table-name"] = "%GpsItemKindProperty#" .. icons.Calendar .. "%*" .. " ",
      ["time-name"] = "%GpsItemKindValue#" .. icons.Watch .. "%*" .. " ",
      ["module-name"] = "%GpsItemKindModule#" .. icons.Module .. "%*" .. " ",
   },
}

gps.setup(options)

First set highlight colors to the symbols

those Gpsitemkind.. stuff are the highlight groups, I assume that u know how to define highlight groups with the new nvim api

No i do not know,
I did copy from your config before posting here, but it didn't work, this is the part i was missing surely!!
I will search around your config and the docs (:h api , :h highlight-groups) and i should be able to figure it out.
Thank you!

@LamprosPitsillos
local hl_groups = {
     Normal = {
          fg = "#ffffff",
          bg = "#000000",
     },

     Comment = {
          bold = true,
          italic = true,
     },

     Statusline = {
          bg = "abc", -- the hex color u want gps to take as bg
     },
}

for key, val in pairs(hl_groups) do
     vim.api.nvim_set_hl(0, key, val)
end

check the docs for deep understanding, i showed u a basic example c:
my config btw https://github.com/NvChad/NvChad :joy:

I defined a separate list of highlight groups for GPS ( which changes fg/bg color of the symbols) and change bg color of "Statusline" highlight group, ig gps uses that for its text

Could you please explain a bit more on how you fixed this? I am having a hard time adding colors to gps-nvim. Thanks

Hey @LamprosPitsillos ! Could you try out my new plugin nvim-navic? I have added colours functionality in it.


Exclude types originating in literals from recursion depth limiter check

Fixes #34619.

@typescript-bot run dt
@typescript test this

@typescript-bot test this

RWC tests are clean. DT tests have one new error in tests for mergerino package (7 level deep array literal is now being checked where it wasn't before).

Is there a case where there's an object literal type that's provided as an argument to a symbolless generic (indexed access?) thats somehow nonterminating now?

Don't think so. But if there is, then there is now as well since literals by themselves can't be circular.


Fix evcxr test

Codecov Report
Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 99.68%. Comparing base (04e901f) to head (14ba2dd).
Report is 8 commits behind head on main.

Files
Patch %
Lines

src/plot.rs
50.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #60      +/-   ##
==========================================
- Coverage   99.70%   99.68%   -0.02%
==========================================
  Files          19       19
  Lines        5100     5117      +17
==========================================
+ Hits         5085     5101      +16
- Misses         15       16       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[C-Interface] getMissingDeps return type

When doing the following
let length = automerge_get_missing_deps(automerge)
var buffer = Array<Int8>(repeating: 0, count: length)
automerge_read_json(automerge, &buffer)
let newString = String(cString: buffer)

I would expect  newString to contain a Clock (key value pair [Int: String]). But a String Array is returned.

Got confused by main & performance branch. Sorry


Re-split SQL script buttons

In the 7.3.5 version you merge scripts SQL buttons in one button, could you return to the previous condition?
Thanks.

thanks for suggestion
duplicates #11352


empty_values does not play well with default values in schemaless changesets

Elixir version
1.14.0
Database and Version
PostgreSQL 14
Ecto Versions
3.10.2
Database Adapter and Versions (postgrex, myxql, etc)
0.17.1
Current behavior
There is no way to use the empty_values feature with schemaless changesets while providing default values for the fields:
types = %{title: :string}
data = %{title: "My base title"}

{data, types}
|> Ecto.Changeset.cast(%{title: ""}, [:title])
|> Ecto.Changeset.apply_action(:validate)
# {:ok, %{title: nil}}

Expected behavior
The documentation for Ecto.Changeset.cast/4 has the following example regarding the behavior of empty_values:
# Using default
iex> params = %{title: "", topics: []}
iex> changeset = cast(post, params, [:title, :topics])
iex> changeset.params
%{topics: []}

# Changing default
iex> params = %{title: "", topics: []}
iex> changeset = cast(post, params, [:topics], empty_values: [[], nil])
iex> changeset.params
%{title: ""}

# Augmenting default
iex> params = %{title: "", topics: []}
iex> changeset =
...>   cast(post, params, [:topics], empty_values: [[], nil] ++ Ecto.Changeset.empty_values())
iex> changeset.params
%{}

Which leads to an understanding that giving a param that matches any of the empty values is the same as not providing that param at all, so I was expecting something kinda like this to happen:
types = %{title: :string}
data = %{title: "My base title"}

{data, types}
|> Ecto.Changeset.cast(%{title: ""}, [:title])
|> Ecto.Changeset.apply_action(:validate)
# {:ok, %{title: "My base title"}}

But the actual behavior is described correctly further up in the docs:

Empty values are always replaced by the default value of the respective field.

Which means it only really works for full schema changesets (since those can have default values defined on their fields), and for everything else a param set to an empty value is the same as setting the field to nil.
I feel like we need to either update the code example in the docs to match the current behavior, or update the behavior to match the code example in the docs (unless there's some alternative I'm not seeing here 😅).
If the decided approach is to just update the docs, it would be great to also have a way to define default values for schemaless changesets (maybe data could be the defaults in this case, or allow a triple {data, types, defaults}).
I'd be happy to provide a PR for this, just figured it would be better to open an issue to discuss first 🙂

Thanks for the report.
empty_values means the values are treated as nil. This is not specific to schemaless changesets either. Passing title: "" to a regular schema will also erase its default value, no? If you want to filter empty attributes, then you should filter them before calling cast.
We should update the docs, PR welcome!

This is not specific to schemaless changesets either. Passing title: "" to a regular schema will also erase its default value, no?

Passing title: "" using a regular schema will replace the value in data by the default value of the field (or nil if the field doesn't have a default).
It's just that there's no such "default values" mechanism for schemaless changesets, which would be very handy for parsing untrusted data.
I can start a discussion regarding this on the mailing list, though. It feels out of the scope for this issue.

We should update the docs, PR welcome!

I'll send one over at some point tomorrow!

You are correct. The only option I can think right now is to do a post-pass on the data converting nils back to the default value, sorry. :( I still don't think it is worth supporting the triplet format for this use case. :(


at_onboarding_flutter: If the root server is uncontactable, the error displayed to users is deeply misleading

Which at_widget package you find issue with?
at_onboarding_flutter
On what platforms did you experience the issue?
Android, iOS
What version are you using?
at_onborading_flutter any recent
What happened?
If root service happens to be unavailable for some reason, the error message displayed to the user is deeply misleading, saying Your atSign is not registered yet. Please try with the registered one.
We should instead display something more sensible like atDirectory not responding; failed to look up your atSign. Please try again.

Additional info
See also https://github.com/atsign-foundation/at_libraries/issues/368

Resolved by https://github.com/atsign-foundation/at_widgets/pull/723


[Event Request] Codeunit 90 Purch.-Post - OnRunOnBeforeCommit

Hi Team,
In Codeunit 90 we need possibility to have our additional checks . Having event with handling in procedure OnRun would be a perfect solution:

[IntegrationEvent(false, false)]
local procedure OnRunOnBeforeCommit(InvtPickPutaway: Boolean; SuppressCommit: Boolean; PreviewMode: Boolean; var IsHandled: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Added puppetlabs-stdlib dependency

This module fails without the puppetlabs-stdlib module. Adding it as a dependency will prevent this.

Thanks!
I guess I missed it since I always have stdlib loaded.
Merging!


Adding V8's HeapSnapshot function to the client

Description of the problem
Adding client-side heap snapshots allows users to handle their memory leaks
Desired solution for the problem
V8 has it own function to writeHeapSnapshot , just call it and add the client console command, then generate the file in the altv root directory.
Alternatives you considered
No response
Additional context
v8.writeHeapSnapshot(filename);
Version
No response
Scope
client

Added in 3c1fd78a5e4ac048fa97dd3765b81d2d613d9d84


Docker - Error initialising Private Transaction Manager

Hi, I tried to pull Docker containers on Ubuntu 20.04 and node container is constantly crashing with the following error

uname -a gives '...5.4.0-105-generic #119-Ubuntu SMP Mon Mar 7 18:49:24 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux'
Latest docker
Docker-compose is v2.6.1
Any ideas how to fix it?

Do you have
PRIVATE_CONFIG=ignore docker-compose up -d
settings?

@piotrhalickihah yes, I installed it as per the official instruction.

docker exec requires at least 2 arguments

I also tried to run 'docker exec [my_container_name] env | grep PRIVATE_CONFIG but received 'Error response from daemon: Container my_container_name is restarting'

echo export PRIVATE_CONFIG=ignore > .env
source .env && docker-compose up -d

Thanks, much better now but getting another error 'Cannot start mining without etherbase    err="etherbase must be explicitly specified"
Fatal: Failed to start mining: etherbase missing: etherbase must be explicitly'

Seems like I am not facing this problem - https://github.com/masa-finance/masa-node-v1.0/issues/43
Tried to change quorum to 21.7.1 - did not help

Hi, now your container keeps restarting during this error too? If not, I could show me the list of processes - the output of the command: docker exec <container-id> ps
However, if it keeps restarting and you cannot execute this command, I suggest you replace all dynamic variables in entrypoint, like this:
entrypoint:
  - /bin/sh
  - -c
  - |
    DDIR=/qdata/dd
    GENESIS_FILE="/network/genesis.json"
    CONSENSUS_RPC_API="istanbul"
    NETWORK_ID=190260
    GETH_ARGS_istanbul="--emitcheckpoints --istanbul.blockperiod 10 --mine --miner.threads 1 --syncmode full"
    if [ ! -f /qdata/dd/control_file ]; then
      mkdir -p /qdata/dd/keystore
      mkdir -p /qdata/dd/geth
      geth --datadir /qdata/dd init /network/genesis.json
      echo "Created" > /qdata/dd/control_file
    fi
    geth \
      --identity node1-istanbul-debug \
      --datadir /qdata/dd \
      --bootnodes enode://ac6b1096ca56b9f6d004b779ae3728bf83f8e22453404cc3cef16a3d9b96608bc67c4b30db88e0a5a6c6390213f7acbe1153ff6d23ce57380104288ae19373ef@<IP_ADDRESS>:21000 \
      --verbosity 5 \
      --networkid 190260 \
      --http \
      --http.corsdomain "*" \
      --http.vhosts "*" \
      --http.addr <IP_ADDRESS> \
      --http.port 8545 \
      --http.api admin,eth,debug,miner,net,shh,txpool,personal,web3,quorum,istanbul \
      --port 21000 \
      --nousb \
       --emitcheckpoints --istanbul.blockperiod 10 --mine --miner.threads 1 --syncmode full

Thanks. Sadly, the container constantly restarts. I tried to change entrypoints but it did not help, still getting the same error.

please share the log (preferably text, not a screenshot) from the beginning of the container startup, maybe we'll find something there.

and additional please share the docker version docker --version

Docker version 20.10.17, build 100c701
docker.txt

This line show that you're using chain with id 1 instead the one that is defined in genesis.json.
{"log":"INFO [07-08|06:44:32.729] Initialised chain configuration          config=\"{ChainID: 1 Homestead: 1150000 DAO: 1920000 DAOSupport: true EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Byzantium: 4370000 IsQuorum: false Constantinople: 7280000 TransactionSizeLimit: 0 MaxCodeSize: 0 Petersburg: 7280000 Istanbul: 9069000, Muir Glacier: 9200000, Berlin: \u003cnil\u003e YOLO v3: \u003cnil\u003e PrivacyEnhancements: \u003cnil\u003e PrivacyPrecompile: \u003cnil\u003e Engine: ethash}\"\n","stream":"stderr","time":"2022-07-08T06:44:32.729240597Z"}

Do you have the latest changes from the repository? Please also share output from command cat network/testnet/genesis.json | grep chain
You can try also remove all data in container docker-compose down --volumes (be careful in which folder you do this, so you don't delete other data)


[WIP] Feature: convenient snapshot exploration

Users mentioned many times that it is not obvious and easy to work with the snapshot.
This PR tries to solve it in the following way:

[ ] implement a convenience function that allows to conveniently explore the snapshot dict (similar to this)

Original list of changes of this PR included these items, but they are implemented in #1322:

add notebook that explains snapshots
update docs/examples/The%20Snapshot.ipynb to link to the new notebook
add tests for the snapshot feature of Measurement, Runner, DataSaver, and DataSet

This PR was redefined, because its part have moved to #1322 PR.

closing as this has been solved by the experiment_widget and its subwidget for displaying dicts.


Optionally support custom ipython Jinja templates.

Thanks for the PR. This was added on https://github.com/danielfrg/pelican-ipynb/pull/91


loss not decreasing

hi, I used matlab to generate train data, then use pytorch to train the model, but the loss didn't decrease after train 50 epoch, loss is always around 300~400,  is the loss right, and is the default params available?
 Please evaluate the model by calculating PSNR instead of loss.

@twtygqyy
Thanks for your reply.
After i add PSNR output in every epoch training, i find the PSNR will increase although loss doesn't decrease.

@shikigit how about your result? Can the model get better super_resolution performance when you used 291 dataset?


marathon-lb is always waiting for new haproxy pid

Hello to all, I've got a question in using marathon-lb.  I pull the docker image from mesosphere/marathon and try the following command to run it:
# docker run -d -e PORTS=9090 --net=host mesosphere/marathon-lb sse -m https://<IP_ADDRESS>:8443 --auth-credentials=lbtest:pa#ssbbcu2276kko  --group external
b45bbc6b6170304289a2d82fa3b01f7d8f9240f7aa624c49d79ff2289dce1a6f
# docker ps
CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS               NAMES
b45bbc6b6170        mesosphere/marathon-lb   "tini -g -- /marat..."   2 seconds ago       Up 2 seconds                            gracious_clarke
I create a job with external port in Marathon, ,but I failed to access it by marathon-lb. I think it doesn't work correctly.
# docker logs gracious_clarke
Generating RSA private key, 2048 bit long modulus
.................................................+++
..................+++
e is 65537 (0x010001)
Signature ok
subject=CN = *
Getting Private key
Reloading haproxy
iptables v1.6.0: can't initialize iptables table filter': Permission denied (you must be root) Perhaps iptables or your kernel needs to be upgraded. cat: /tmp/haproxy.pid: No such file or directory 2017-03-28 11:06:13,615 marathon_lb: setting default value for HAPROXY_HTTPS_FRONTEND_AUTH_REQUEST_ONLY 2017-03-28 11:06:13,615 marathon_lb: setting default value for HAPROXY_BACKEND_REDIRECT_HTTP_TO_HTTPS 2017-03-28 11:06:13,615 marathon_lb: setting default value for HAPROXY_MAP_HTTP_FRONTEND_APPID_ACL 2017-03-28 11:06:13,615 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_HEAD 2017-03-28 11:06:13,615 marathon_lb: setting default value for HAPROXY_HTTPS_FRONTEND_ACL_WITH_AUTH_AND_PATH 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_BACKEND_HTTP_OPTIONS 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_BACKEND_HSTS_OPTIONS 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_HEAD 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_HTTPS_FRONTEND_HEAD 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ACL_WITH_AUTH 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_FRONTEND_BACKEND_GLUE 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_USERLIST_HEAD 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_FRONTEND_HEAD 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_APPID_HEAD 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_BACKEND_REDIRECT_HTTP_TO_HTTPS_WITH_PATH 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ACL_WITH_AUTH_AND_PATH 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ACL_ONLY_WITH_PATH 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_HTTP_BACKEND_REDIR 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_BACKEND_SERVER_HTTP_HEALTHCHECK_OPTIONS 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ROUTING_ONLY_WITH_PATH 2017-03-28 11:06:13,616 marathon_lb: setting default value for HAPROXY_BACKEND_TCP_HEALTHCHECK_OPTIONS 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_TCP_BACKEND_NETWORK_ALLOWED_ACL 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_HTTPS_FRONTEND_ACL 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_MAP_HTTP_FRONTEND_ACL_ONLY 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_BACKEND_SERVER_OPTIONS 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_HTTPS_FRONTEND_AUTH_ACL_ONLY 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_HTTP_BACKEND_REVPROXY_GLUE 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_APPID_ACL 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_MAP_HTTPS_FRONTEND_ACL 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_HTTPS_FRONTEND_ACL_WITH_PATH 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ACL 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_TCP_BACKEND_ACL_ALLOW_DENY 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ROUTING_ONLY_WITH_AUTH 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_HTTPS_FRONTEND_ACL_ONLY_WITH_PATH 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_BACKEND_HTTP_HEALTHCHECK_OPTIONS 2017-03-28 11:06:13,617 marathon_lb: setting default value for HAPROXY_HTTPS_FRONTEND_ROUTING_ONLY_WITH_PATH_AND_AUTH 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_BACKEND_SERVER_TCP_HEALTHCHECK_OPTIONS 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_BACKEND_HEAD 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_MAP_HTTP_FRONTEND_ACL 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ACL_ONLY 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_HTTP_BACKEND_PROXYPASS_GLUE 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ACL_ONLY_WITH_PATH_AND_AUTH 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ACL_WITH_PATH 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_BACKEND_STICKY_OPTIONS 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ROUTING_ONLY 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_HTTP_FRONTEND_ROUTING_ONLY_WITH_PATH_AND_AUTH 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_HTTPS_FRONTEND_ACL_WITH_AUTH 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_HTTP_BACKEND_NETWORK_ALLOWED_ACL 2017-03-28 11:06:13,618 marathon_lb: setting default value for HAPROXY_HTTP_BACKEND_ACL_ALLOW_DENY [ALERT] 086/110613 (37) : Cannot open configuration file/directory /marathon-lb/haproxy.cfg : No such file or directory 2017-03-28 11:06:13,626 marathon_lb: starting event processor thread 2017-03-28 11:06:13,626 marathon_lb: fetching apps 2017-03-28 11:06:13,629 marathon_lb: SSE Active, trying fetch events from https://<IP_ADDRESS>:8443/v2/events /usr/local/lib/python3.5/dist-packages/requests/packages/urllib3/connectionpool.py:852: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings   InsecureRequestWarning) 2017-03-28 11:06:13,739 marathon_lb: GET https://<IP_ADDRESS>:8443/v2/apps?embed=apps.tasks 2017-03-28 11:06:13,739 marathon_lb: got apps ['/webtest'] 2017-03-28 11:06:13,740 marathon_lb: generating config 2017-03-28 11:06:13,740 marathon_lb: HAProxy dir is /marathon-lb 2017-03-28 11:06:13,740 marathon_lb: reading running config from /marathon-lb/haproxy.cfg 2017-03-28 11:06:13,740 marathon_lb: couldn't open config file for reading 2017-03-28 11:06:13,740 marathon_lb: running config is different from generated config - reloading 2017-03-28 11:06:13,741 marathon_lb: writing temp file /tmp/tmp722k5epg that will replace /marathon-lb/haproxy.cfg 2017-03-28 11:06:13,741 marathon_lb: checking config with command: ['haproxy', '-f', '/tmp/tmp722k5epg', '-c'] [WARNING] 086/110613 (41) : Can't read first line of the server state file '/var/state/haproxy/global' Configuration file is valid 2017-03-28 11:06:13,756 marathon_lb: moving temp file /tmp/tmp722k5epg to /marathon-lb/haproxy.cfg 2017-03-28 11:06:13,758 marathon_lb: reloading using sv reload /marathon-lb/service/haproxy ok: run: /marathon-lb/service/haproxy: (pid 23) 0s 2017-03-28 11:06:13,774 marathon_lb: Waiting for new haproxy pid... 2017-03-28 11:06:13,791 marathon_lb: received event of type event_stream_attached 2017-03-28 11:06:13,887 marathon_lb: Waiting for new haproxy pid... 2017-03-28 11:06:13,990 marathon_lb: Waiting for new haproxy pid... 2017-03-28 11:06:14,094 marathon_lb: Waiting for new haproxy pid... 2017-03-28 11:06:14,197 marathon_lb: Waiting for new haproxy pid... 2017-03-28 11:06:14,300 marathon_lb: Waiting for new haproxy pid... 2017-03-28 11:06:14,404 marathon_lb: Waiting for new haproxy pid... 2017-03-28 11:06:14,510 marathon_lb: Waiting for new haproxy pid... 2017-03-28 11:06:14,614 marathon_lb: Waiting for new haproxy pid... 2017-03-28 11:06:14,717 marathon_lb: Waiting for new haproxy pid... Reloading haproxy iptables v1.6.0: can't initialize iptables table filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
2017-03-28 11:06:14,820 marathon_lb: Waiting for new haproxy pid...
cat: /tmp/haproxy.pid: No such file or directory
[WARNING] 086/110614 (78) : [/usr/local/sbin/haproxy.main()] Cannot raise FD limit to 100034, limit is 65536.
[ALERT] 086/110614 (78) : sendmsg logger #1 failed: No such file or directory (errno=2)
[ALERT] 086/110614 (78) : sendmsg logger #2 failed: No such file or directory (errno=2)
[ALERT] 086/110614 (78) : Starting frontend marathon_http_in: cannot bind socket [<IP_ADDRESS>:80]
[ALERT] 086/110614 (78) : sendmsg logger #1 failed: No such file or directory (errno=2)
[ALERT] 086/110614 (78) : sendmsg logger #2 failed: No such file or directory (errno=2)
[ALERT] 086/110614 (78) : sendmsg logger #1 failed: No such file or directory (errno=2)
[ALERT] 086/110614 (78) : sendmsg logger #2 failed: No such file or directory (errno=2)
2017-03-28 11:06:14,924 marathon_lb: Waiting for new haproxy pid...
2017-03-28 11:06:15,027 marathon_lb: Waiting for new haproxy pid...
2017-03-28 11:06:15,130 marathon_lb: Waiting for new haproxy pid...
2017-03-28 11:06:15,234 marathon_lb: Waiting for new haproxy pid...
2017-03-28 11:06:15,337 marathon_lb: Waiting for new haproxy pid...
2017-03-28 11:06:15,440 marathon_lb: Waiting for new haproxy pid...
2017-03-28 11:06:15,544 marathon_lb: Waiting for new haproxy pid...
2017-03-28 11:06:15,648 marathon_lb: Waiting for new haproxy pid...
The server environment:
centos-release:
CentOS Linux release 7.1.1503 (Core)
docker version:
Docker version 17.03.0-ce, build 3a232c8
The marathon-lb is always waiting for new haproxy pid...I have no idea about it. The same image works well on my other servers.Any help will be appreciated.

We found the same problem with
cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)
[root@bcn1-server-229:mauso]$ docker -v
Docker version 17.03.1-ce, build c6d412e
Any idea?

I found the same problem and fix it.
You can check the port 80, 8080,9090,if them are listened by other services,marathon-lb can not start successfully.Kill the 80, 8080,9090 ports services.

Apologies for the delay in triaging this issue. Since it has been some time, and there is the possibilty that another service was listening on one of the marathon-lb ports, I'm going to close this issue. If this is still an issue for you on the latest marathon-lb (1.12.x), please comment and I'll reopen it. If you could also include the output of netstat -anlpt.

@jkoelker
Am using marathon-lb internal ( mesosphere/marathon-lb:v1.12.3 ) and getting below error on startup
[ALERT] 139/194050 (38) : Cannot open configuration file/directory /marathon-lb/haproxy.cfg : No such file or directory
Also when Mesos DC/OS apps comes up .. marathon-lb internal service discovery takes upto 60-90 secs to update which gives downtime on apps.
Any clue ? why this happens.
I had installed it from Universe.
Thank You


fix frcition invalid

fix frcition invalid
because "ContactConstraintPoint" struct is copied
need compat old c# version use fixed (pointer)?

@qcbf hey! thanks. If you need a new version it's available here [1] and under releases [2].
[1] https://www.nuget.org/packages/Box2D.NetStandard
[2] https://github.com/benukhanov/box2d-netstandard/releases


Fix memory leak in Future constructor

The Deno.UnsafeCallback objects are not garbage collected: Since their foremost point is to setup a C function pointer that can be passed to C and then may or may not call back later at theoretically any time, there is no way to know from Deno side if the pointer is still needed or not.
As a result, creating callbacks repeatedly without making sure they're also closed causes a memory leak.
This PR fixes the leak in the Future constructor by moving the callback into a "static". Incoming callbacks find their intended Deno side Future instances through a Map<number | bigint, Future> and delete their own instance from the Map once found.
Note by the way that FoundationDB says that fdb_future_set_callback may call the callback synchronously, and it will never call the callback twice. This means that in this code:
const future = new Future(futurePointer);
future.setCallback(() => console.log("Ready"));

the C callback may get called before new Future returns and thus before the setCallback JS call is made, leading to "Ready" never being logged.

Note by the way that FoundationDB says that fdb_future_set_callback may call the callback synchronously, and it will never call the callback twice. This means that in this code:

They do the same here: https://github.com/apple/foundationdb/blob/00055bd76b309b469abd1eaedeb6b7b84f5447c1/bindings/python/fdb/impl.py#L756. So I would leave it as is.

Note by the way that FoundationDB says that fdb_future_set_callback may call the callback synchronously, and it will never call the callback twice. This means that in this code:
const future = new Future(futurePointer);
future.setCallback(() => console.log("Ready"));

the C callback may get called before new Future returns and thus before the setCallback JS call is made, leading to "Ready" never being logged.

According to the official FoundationDB docs, the callback passed to fdb_future_set_callback is guaranteed to be called at least once. Having a map might also not be efficient when there will be many futures. I think there should be a better workaround.

According to the official FoundationDB docs, the callback passed to fdb_future_set_callback is guaranteed to be called at least once.

From the C API docs:

This function guarantees the callback will be executed at most once.

So either once or never.

Having a map might also not be efficient when there will be many futures. I think there should be a better workaround.

A Map is quite efficient, and should be especially so with number keys. It would actually be a bit more efficient to use a u64 instead of pointer for the first callback parameter type to avoid having to get the value of the pointer before looking into the Map. Also note that creating c callbacks is not terribly fast, so a Map insertion and lookup is trivial in comparison

I forgot that we were deleting the keys in the map.

So either once or never.

How in the world do we know if it is never called anyway?

Also, what about calling fdb_future_set_callback in the setCallback method? Does it affect the following problem?

Note by the way that FoundationDB says that fdb_future_set_callback may call the callback synchronously, and it will never call the callback twice. This means that in this code:
const future = new Future(futurePointer);
future.setCallback(() => console.log("Ready"));

the C callback may get called before new Future returns and thus before the setCallback JS call is made, leading to "Ready" never being logged.

How in the world do we know if it is never called anyway?

This presumably would happen if the Future never resolves.

Also, what about calling fdb_future_set_callback when the setCallback method is called? Does it move the following problem?

That would work. Alternatively you could eg. require the callback as a constructor parameter. Or you could mark the Future resolved somehow (private Boolean) and automatically call the callback in setCallback if the Future is already resolved.


perf(BundledCats): more explicit universe annotations

Testing for leanprover/lean4#4085 exposed possible regressions typeclass synthesis which can be ameliorated using explicit universes. We do this and we add references to the issue leanprover-community/mathlib4#12737 tracking these changes.

!bench

Thanks!
bors merge


update tonhue.toml for tesntet 15

[validator.tonhue]
consensus_public_key = "00b82ead1098cc89a26c8af039eb65ecd8ea12fa252bb84c7c141d92cbeeb2be2a"
eth_cold_key = "01037a5982f7484cacc3d9bbaf8b908862f8caf1daed1fd0fb250784487ae487f8c7"
eth_hot_key = "01038aa6811b90dbe2c45ad74bac2b19ea11cf5fcfd5795cf7f90088fd2a93f41e61"
account_public_key = "0016fb62f49de9ee9e41deff64564842605efe8eed2ff3a2d8f188f46d94f2ac07"
protocol_public_key = "002f54477e9646200843b9c89a21074b90c26d25a09845911bb79392997a0a670f"
dkg_public_key = "60000000fc720633ffb2b867d2d7bcb2f9c01503751101106b55b0cdbe5969633fb6d16587a18bc263c19d664c9b0f0321866f15b50ceae0a372a51148cd322c6078fdc43e275bfd3b34fe5219c0b7f225a83284ed18cb43e763ee8372de0eba7ddfbf95"
commission_rate = "0.05"
max_commission_rate_change = "0.01"
net_address = "<IP_ADDRESS>:26656"
tendermint_node_key = "00fe1ed3c1c739bbfa0dca08403af50147656ffce67129620e20569eed0969fb0e"
email =<EMAIL_ADDRESS>discord = "@worth573kwlq"
elements = ""
telegram = ""
twitter = "@IngridHogant781"

Filename contains whitespace
This PR has been automatically closed because it does not follow the correct procedure for updating the genesis file.

Filename contains whitespace
This PR has been automatically closed because it does not follow the correct procedure for updating the genesis file.

Filename contains whitespace
This PR has been automatically closed because it does not follow the correct procedure for updating the genesis file.


username overwrites when a user logs in

If you change your username, log-out and then log back in again, your username overwrites to the one from your log-in method.
This is reproducible when logging in with Google.
Expected behaviour, if username exists, it does not overwrite.

We have Auth Pipeline rule "Create Hasura User", in the rule upsert user query was updating the username if the record already exists.


Volume directoy on host quickly disappears after mount

Hi,
the volume on my DiskStation (2x 920+ in HA) is provisioned correctly and attached as block device (/dev/sdd in my case) on the host system. But it is expected to be mounted in /var/snap/microk8s/common/var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-d1e722ba-35e7-4222-a797-1e66eb40c755/globalmount which does not exists. Only /var/snap/microk8s/common/var/lib/kubelet/plugins/kubernetes.io/csi/pv exists.
On further investigation I found out that this directory shortly appears and disappears (for roughly 1s) during this log entry:
[synology-csi-node-ppzwq csi-plugin] 2021-10-03T21:32:52Z [INFO] [driver/utils.go:104] GRPC call: /csi.v1.Node/NodeGetCapabilities
[synology-csi-node-ppzwq csi-plugin] 2021-10-03T21:32:52Z [INFO] [driver/utils.go:105] GRPC request: {}
[synology-csi-node-ppzwq csi-plugin] 2021-10-03T21:32:52Z [INFO] [driver/utils.go:110] GRPC response: {"capabilities":[{"Type":{"Rpc":{"type":1}}},{"Type":{"Rpc":{"type":3}}}]}
[synology-csi-node-ppzwq csi-plugin] 2021-10-03T21:32:52Z [INFO] [driver/utils.go:104] GRPC call: /csi.v1.Node/NodeStageVolume
[synology-csi-node-ppzwq csi-plugin] 2021-10-03T21:32:52Z [INFO] [driver/utils.go:105] GRPC request: {"staging_target_path":"/var/snap/microk8s/common/var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-d1e722ba-35e7-4222-a797-1e66eb40c755/globalmount","volume_capability":{"AccessType":{"Mount":{"fs_type":"ext4"}},"access_mode":{"mode":1}},"volume_context":{"dsm":"<IP_ADDRESS>","storage.kubernetes.io/csiProvisionerIdentity":"1633291144215-8081-csi.san.synology.com"},"volume_id":"080af020-d433-4ea3-aa2a-1773a9132e3f"}
[synology-csi-node-ppzwq csi-plugin] 2021-10-03T21:32:52Z [INFO] [driver/initiator.go:109] Session[iqn.2000-01.com.synology:Hossnercloud-HA.pvc-d1e722ba-35e7-4222-a797-1e66eb40c755] already exists.
[synology-csi-node-ppzwq csi-plugin] 2021-10-03T21:32:53Z [ERROR] [driver/utils.go:108] GRPC error: rpc error: code = Internal desc = stat /var/snap/microk8s/common/var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-d1e722ba-35e7-4222-a797-1e66eb40c755/globalmount: no such file or directory

At this point I do not know how to debug this further. Possibly a hidden error during mounting.
I am on MicroK8S 1.21 by the way.
Edit: The block device should already be formatted with ext4 at this point but they are not. This is a probably cause of the mount failing. What might hahve skipped formatting during provisioning?
Edit2: Manually formatting /dev/sdd with ext4 did not help the csi-plugin with mounting, but I was able to mount is manually. This does not seem to be recognized by K8S though.

Hi,

On further investigation I found out that this directory shortly appears and disappears (for roughly 1s) during this log entry

Actually, this directory  /var/snap/microk8s/common/var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-d1e722ba-35e7-4222-a797-1e66eb40c755/globalmount never appears during NodeStageVolume. It's weird because this directory should be created by kubernetes before the CSI going to do NodeStageVolume.
Before format and mount, the CSI would check if staging_target_path was mount or not, but in your case, it couldn't find the path. So the error you encountered might not be caused by mounting, but the mount point checking:
https://github.com/SynologyOpenSource/synology-csi/blob/dc05a795b79b911ec5882c3c837a7779cf3576a8/pkg/driver/nodeserver.go#L172
I'm not sure if these can help for further debugging:

check the status of the pod you created, using kubectl describe
check the logs of csi-attacher and other containers in csi-controller

Did you get this working? I am facing the same issue with microk8s.

Hi!
Try to change the value of the kubelet-dir mountPath from /var/lib/kubelet to /var/snap/microk8s/common/var/lib/kubelet, and reinstall the csi driver again (./scripts/uninstall.sh; ./scripts/deploy.sh install -b).
https://github.com/SynologyOpenSource/synology-csi/blob/fc3359223fe51a13bcfa5a7cabbf59611bbeb901/deploy/kubernetes/v1.20/node.yml#L103-L106
We're still working on providing an easier configuration method to make CSI compatible with more Kubernetes or other container orchestrations.

This is my working node.yml file:
--- kind: DaemonSet apiVersion: apps/v1 metadata:   name: synology-csi-node   namespace: synology-csi spec:   selector:     matchLabels:       app: synology-csi-node   template:     metadata:       labels:         app: synology-csi-node     spec:       serviceAccount: csi-node-sa       hostNetwork: true       containers:         - name: csi-driver-registrar           securityContext:             privileged: true           imagePullPolicy: Always           image: k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0           args:             - --v=5             - --csi-address=$(ADDRESS)                         # the csi socket path inside the pod             - --kubelet-registration-path=$(REGISTRATION_PATH) # the csi socket path on the host node           env:             - name: ADDRESS               value: /csi/csi.sock             - name: REGISTRATION_PATH               value: **/var/snap/microk8s/common/var/lib/kubelet/plugins/csi.synology.com/csi.sock**             - name: KUBE_NODE_NAME               valueFrom:                 fieldRef:                   fieldPath: spec.nodeName           volumeMounts:             - name: plugin-dir               mountPath: /csi             - name: registration-dir               mountPath: /registration         - name: csi-plugin           securityContext:             privileged: true           imagePullPolicy: IfNotPresent           image: synology/synology-csi:v1.1.0           args:             - --nodeid=$(KUBE_NODE_NAME)             - --endpoint=$(CSI_ENDPOINT)             - --client-info             - /etc/synology/client-info.yml             - --log-level=info           env:             - name: CSI_ENDPOINT               value: unix://csi/csi.sock             - name: KUBE_NODE_NAME               valueFrom:                 fieldRef:                   fieldPath: spec.nodeName           volumeMounts:             - name: kubelet-dir               mountPath: **/var/snap/microk8s/common/var/lib/kubelet**               mountPropagation: "Bidirectional"             - name: plugin-dir               mountPath: /csi             - name: client-info               mountPath: /etc/synology               readOnly: true             - name: host-root               mountPath: /host             - name: device-dir               mountPath: /dev       volumes:         - name: kubelet-dir           hostPath:             path: **/var/snap/microk8s/common/var/lib/kubelet**             type: Directory         - name: plugin-dir           hostPath:             path: **/var/snap/microk8s/common/var/lib/kubelet/plugins/csi.synology.com/**             type: DirectoryOrCreate         - name: registration-dir           hostPath:             path: **/var/snap/microk8s/common/var/lib/kubelet/plugins_registry**             type: Directory         - name: client-info           secret:             secretName: client-info-secret         - name: host-root           hostPath:             path: /             type: Directory         - name: device-dir           hostPath:             path: /dev             type: Directory

I'm having a similar problem with k0s, because it also does not have a standard /var/lib/kubelet root folder.  Instead, theirs are set to /var/lib/k0s/kubelet which I have both symlinked from /var/lib/kubelet and also tried changing the hostPath declarations to work either way.  For some reason, this did not solve my problem with mounting the volume.
2024-07-01T19:03:30Z [ERROR] [driver/utils.go:108] GRPC error: rpc error: code = Internal desc = stat /var/lib/k0s/kubelet/plugins/kubernetes.io/csi/csi.san.synology.com/5ff8af875f7f2e4d721e952230420933db1c42ee5f43c50484fc7119175cbff2/globalmount: no such file or directory

I have verified that the PVC created the iscsi target, have manually mounted (to /mnt/test not the proper location) and formatted and created a file on that volume on the same node that is running this pod.  So I know the file system formatter and mounting should work.  But... this is the only error I get from the csi-plugin pod.  For what it's worth, I have also done a find searching all the folders for this volume being mounted somewhere else... and it isn't.
I've been at this all day.  Anyone know what I should look at next?

Ahh... looking at my yaml and the one posted above, it's not just the hostPath but also the mountPath that need to have the full host path folder updated.  Working now.


Allow models not in models.json to be used by scivision

Related to (and could be solved by solution to) #76
Currently scivision can only use models that are added to scivision/catalog/data/models.json.
Can we make it so that models not already included in models.json can be loaded into scivision by simply including a scivision.yml in their repo? For an example of scivision.yml - see https://github.com/quantumjot/scivision-test-plugin/blob/main/.scivision-config_imagenet.yaml <- note this one is currently named differently

Looks like I was mistaken here: load_pretrained_model already works with a repo containing a model scivision.yml


Replace srcdeps-maven-plugin with srcdeps core extension

@pilhuhn or whoever else, could you please review and eventually merge?

@pilhuhn not responding, could @Jiri-Kremser review maybe?

bf4cc5b replaces 49baab1 fixing the mvnw path in https://github.com/hawkular/hawkular-services/pull/104/commits/ddd0394a49cd6200c566926e6d67ee15534fe7d4#diff-5922539fc070ae984a1f0132c80e2e17R31
Is this good to merge now?

Oh, I wasn't aware we need to install our special maven in travis.
Hmm, if |mvn -N io.takari:maven:wrapper| downloads the |mvnw| shell
script, so why don't we just have something like this:
#!/bin/bash
[ -f ./mvnw ] || mvn -N io.takari:maven:wrapper
./mvnw $@
in a file called |build.sh|.

Wrapping a wrapper :D !!! Well, to run the above script or mvn -N  io.takari:maven:wrapper you need mvn installed, while you do not need
to have mvn installed to run mvnw. I think that's important in many
cases, esp. in CI. Second, your script will run on unix like systems
only. There is mvnw.cmd for Windows OOTB.

ok, you convinced me. LGTM


build: Update to header 1.3.214

Update known-good
Generate source

CI Vulkan-Tools build # 725 running.


Satellite power systems example?

@whoburg said: Looking for a new GP application? Satellite power systems: https://stellar.mit.edu/S/course/16/fa14/16.851/courseMaterial/topics/topic3/resource/rauschenback-solar-array-design/rauschenback-solar-array-design.pdf

Should this be in the Model library repository?

+1


Avoid --skip-refresh on local charts

All the dependencies get correctly installed when dealing with remote charts.
If there's a local chart that depends on remote dependencies then those don't get automatically installed. See #526. They end up with this error:
Error: no cached repository for helm-manager-b6cf96b91af4f01317d185adfbe32610179e5246214be9646a52cb0b86032272 found. (try 'helm repo update'): open /root/.cache/helm/repository/helm-manager-b6cf96b91af4f01317d185adfbe32610179e5246214be9646a52cb0b86032272-index.yaml: no such file or directory

One workaround for that would be to add the repositories from the local charts. Something like this:
cd local-chart/ && helm dependency list $dir 2> /dev/null | tail +2 | head -n -1 | awk '{ print "helm repo add " $1 " " $3 }' | while read cmd; do $cmd; done

This however is not trivial to parse and implement.
An easier fix which I did here is just to not allow doing --skip-refresh for local repositories.
Fixes #526

@indrekj please rebase your code. then the unit test will be ok.

@indrekj is there another method that does not add a func arg?

@indrekj please rebase your code. then the unit test will be ok.

I did a rebase against origin main but it still fails.

@indrekj is there another method that does not add a func arg?

Not sure. I need to know if we're dealing with a local chart and then using that we can skip the refresh. I'm not very familiar with Go. In other languages I would use keyword arguments instead of a boolean argument though. I don't think we can just skip an argument if we want to use this approach though.

@indrekj please try to fix unit test. Thanks very much.

There's still one test failing which I'm having trouble fixing:
    --- FAIL: TestHelmfileTemplateWithBuildCommand/oci_need (6.08s)

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1,2 +1,7 @@
        	            	 Building dependency release=foo, chart=$WD/temp1/foo
        	            	+Hang tight while we grab the latest from your chart repositories...
        	            	+...Unable to get an update from the "myrepo" chart repository (http://localhost:18080/):
        	            	+	Get "http://localhost:18080/index.yaml": dial tcp [::1]:18080: connect: connection refused
        	            	+...Successfully got an update from the "istio" chart repository
        	            	+Update Complete. ⎈Happy Helming!⎈
        	            	 Saving 1 charts
        	Test:       	TestHelmfileTemplateWithBuildCommand/oci_need

That test does not have anything to do with 18080 and istio. So it seems that tests are not being run completely isolated from other tests. I suspect there's some Helm cache lingering and this is causing this issue. Do you have any recommendations on what to do in this case?

Interesting- But let me rerun the test anyway, assuming it might be a flake.

Apparently it's not a flake 🤔
I remember Helmfile occasionally run helm repo up to re-fetch indices for all the local and remote chart repositories registered to the local helm installation. We might be running helm repo add istio https://... through other e2e test cases and that might be a test that looks not related to istio seems to have resulted in fetching the index for the istio charts repo.
What's uncertain for me is why it's failing now.
Could it be that the changes made in this pull request resulted in an additional helm repo up all in some code paths and revelated that the our local chart repository (that is brought up/down around the helmfile e2e test run) is broken? 🤔

Could it be that the changes made in this pull request

That is likely. Previously we had --skip-refresh. The refresh seems to affect the repositories.

@indrekj @mumoshu I think the key is trying to clean up the helm repo on each iteration.
see: https://github.com/helmfile/helmfile/blob/b76f1d37d73de67f38a9ed511243b55d67957de3/test/e2e/template/helmfile/snapshot_test.go#L55

@mumoshu @itscaro all is ok. Please review.

@indrekj could you rebase main branch?

I think you already did, at least I don't see any new changes in the main branch.
By the way, thank you for taking care of this. I have been swamped, and looking at the code, you did it much better than I would have.


win32 visual studio build errors

hi !
i can't build baresip under windows(ver 7, 10) using suggested in readme visual studio project (baresip.sln) under mk/win32 folder.
The problem is VS project missing some codec dependencies, which included in code:
....\modules\avcodec\h264.c: No such file or directory baresip-win32 in c1
libavcodec/avcodec.h: No such file or directory baresip-win32 in h263.c
libavcodec/avcodec.h: No such file or directory baresip-win32 in encode.c
libavcodec/avcodec.h: No such file or directory baresip-win32 in decode.c
libavcodec/avcodec.h: No such file or directory baresip-win32 in avcodec.c
it seems that baresip-win32 requires ffmpeg headers to build properly, but there are none in src path
Are some folders missing from project ?  Or may be i do something wrong (but all i do is run solution and press Build) ? Or may be visual studio project which shipped with source code is out of date?
Any thoughts appreciated, thanks!
PS full specifications:
os: windows 10
visual studio 2015 ver 14 update 3
latest baresip src from this git repo
latest libre src from git repo
latest librem src from svn repo

I think the VC project file is out of date.
could you please create a clean VC project file and then add all .c files under src/* ?
if it works you can continue by adding modules one at a time,
such as menu, g711 etc.

thanks for reply
i succeded with building in VS after recreating project from empty one like you suggested.
PS but it wasnt that fun and fast so i cant advise to use VS as a build tool for baresip, especially on modern windows (10).

would you be interested in submitting a PR for this VC project that works?
this can benefit many people so that they dont have to experience the same
problems as you did :)

i dont consider myself a skilful C developer, so i dont think that my results are good enough to be published as "best practice example" via pull request. But if i become more confident i will publish it surely.


Refactor of setup.py

This pr updates project names & other metadata throughout the repo
It also cleans up setup.py ( following some best practices )
I'd like to move the test logic to setup.py based commands as well. Anyone thoughts on that?
Additionally we might want to consider using some format like Pipfile or setup.cfg to store the metadata, this seems to be a cleaner way to go about this.

Not sure why the precompile check is in here also, but it should be in the external calls module anyway


Unstable formatting on for loops with lots of loop variables

Operating system: Ubuntu 18.04
Python version: 3.6.5
Black version: 18.5b0
Does also happen on master: yes
Input:
import socket

for addr_family, addr_type, addr_proto, addr_canonname, addr_sockaddr in socket.getaddrinfo('google.com', 'http'):
    print(addr_family, addr_type, addr_proto, addr_canonname, addr_sockaddr)

Output:
$ black /tmp/bug.py
error: cannot format /tmp/bug.py: INTERNAL ERROR: Black produced different code on the second pass of the formatter.  Please report a bug on https://github.com/ambv/black/issues.  This diff might be helpful: /tmp/blk_z38v399t.log

Log:
--- source
+++ first pass
@@ -1,5 +1,13 @@
 import socket

-for addr_family, addr_type, addr_proto, addr_canonname, addr_sockaddr in socket.getaddrinfo('google.com', 'http'):
+for (
+    addr_family,
+    addr_type,
+    addr_proto,
+    addr_canonname,
+    addr_sockaddr,
+) in socket.getaddrinfo(
+    "google.com", "http"
+):
     print(addr_family, addr_type, addr_proto, addr_canonname, addr_sockaddr)

--- first pass
+++ second pass
@@ -4,10 +4,8 @@
     addr_family,
     addr_type,
     addr_proto,
     addr_canonname,
     addr_sockaddr,
-) in socket.getaddrinfo(
-    "google.com", "http"
-):
+) in socket.getaddrinfo("google.com", "http"):
     print(addr_family, addr_type, addr_proto, addr_canonname, addr_sockaddr)

Already tried with master (fd9bd07fe551c88f0c1e2d6f411f48b73f3083fc), tried again, same result.

Sorry, you're right, I confused this with another error I already fixed on master. Will get right on it!

@andersk @ambv I experienced the same issue, then my coworker just asked me to specify the -l flag (with a larger length) and then Black just worked! ✨ 🍰 ✨


gimli.units v0.3.1

Prepare for v0.3.1.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls


Lack of market stratgy

The people in charge of this package lack market strategy...Asper zerooo..your market sense is zero...how can you make such changes in this package like this....do you know how big my project is...I'm switching to flutter bloc or redux as soon as possible ...wtf so I can't use context.read any more so now I have to always wrap in ConsumerWidget what is I want to do context.read(a).state?...:...does that need a consumer wiget????
You guys are good developers, I totally agree... but your business sense is Zero , I assure you if you keep making these kind of drastic changes people will stop using this package..Even bloggers are tired of updating their blogs anytime you guys make update ....common buckle up..my project had 3k+ errors on updating package ...do you know how discouraging that looks....bye bye
..BloC is the way!!!!!!

@Somtobro To be fair, you are judging a situation that I don't feel is true.
Remi always stated it was an experimental package as an alternative to provider. You chose to use such package on your project.
Regarding breaking changes, that's the nature of software development, even more when it's in active development. RFCs issues have been opened to gather feedback from the community before going ahead with such changes, and even a migration tool has been written to make those breaking changes automatically.

@davidmartos96 Bro, I get where you can coming from...I totally understand, but what you don't know is that most people who use flutter use it for scale projects and most times they are self taught developers....These people ,including myself, do not follow news update, they just want to come and see the package fine and good to go..therefore the company should at least think the users of the package...We don't really appreciate having to use migration tools and stuff like that... I can't really explain what in trying to say...but the point is they should think like the users more...consumers don't care about what is going on...I know it's selfish but thats how users are....Again I can't really explain this point but just be open minded about it and you should get what I'm trying to say
..

I just want to wish easy migration to Bloc 🙃

@Somtobro I understand, breaking changes are always a pain, but they are unavoidable. The difference here is that those changes have been made months after the initial experimental release of riverpod. Certain features planned for the future wouldn't really work with the BuildContext approach, and many people were confused with the different ways to read a provider.
Not doing a breaking change, could actually harm the future progress of the package. So better make those changes before a stable release.
And remember that even Bloc or the Flutter framework have breaking changes every once in a while

That's the risk of using libraries, that are not yet considered fully stable or experimental, my friend. Either you wait for its stable release or you live with eventually appearing breaking changes.

Looks like you missed this -> Is it safe to use Riverpod in production
Upcoming new syntax for flutter bloc 8 -> This is a must read for those planning to upgrade to bloc v8.0.0
To make your big project depend on third part packages is your choice and you cant avoid changes.

Pro tip: Always handle local state with setState and for global prefer ValueNotifier or ChangeNotifier. All other state managers use only with more complicated situations.

@rrousselGit okay cool...will try that out

If you want to be in full control of package upgrades and breaking changes, build everything yourself from scratch.
Building OSS is not easy. Have some respect.

We should probably only stick to really stable things with a proven track record of zero carrying cost, like I don't know COBOL.
Oh wait https://en.wikipedia.org/wiki/COBOL#Compatibility_issues
Nope, no escape. Awesome there's a command line migration tool.

At least python 2 to 3 was easy.


refactor: remove obsolete host-component-properties mixin (WIP)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@374d7b7). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2574   +/-   ##
=======================================
  Coverage        ?   93.21%
=======================================
  Files           ?      314
  Lines           ?    25497
  Branches        ?     2062
=======================================
  Hits            ?    23768
  Misses          ?     1696
  Partials        ?       33

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add support to GPUs in TaskChain spec

Fixes #10400
Status
not-tested
Description
As a follow up of: https://github.com/dmwm/WMCore/pull/10799
this PR enabled GPU support in the TaskChain spec, thus, supporting it inside each Task definition as well.
Note that for TaskChain workflows, there is the same default values as those for top level, thus:

RequiresGPU : forbidden
GPUParams: json.dumps(None)
and the top level arguments will have
RequiresGPU: None

Is it backward compatible (if not, which system it affects?)
YES (new arguments were made optional)
Related PRs
Complement to: https://github.com/dmwm/WMCore/pull/10799
External dependencies / deployment changes
None

Basic tests went fine in my VM. @todor-ivanov feel free to leave any questions and/or your review. I will tackle the StepChain use case tomorrow, so I can fix whatever is left from this one. Thanks!


Nodes got same port assigned

Description
In tonight's LC BF6 run node 3 and 7 got port 53771 assigned:
{"node": 3, "address": "0x6ebf9FC71796e9Fe1D4D3F3f2e6F1A72E08eD248", "port": "53771", "event": "Starting node", "logger": "scenario_player.node_support", "level": "info", "timestamp": "2020-11-17 01:21:27.660391"}
...
{"node": 7, "address": "0xf52e13611563d071E0b3f671364210A98FA73062", "port": "53771", "event": "Starting node", "logger": "scenario_player.node_support", "level": "info", "timestamp": "2020-11-17 01:21:27.764930"}

Expected Behavior
Each node should get a unique port.

@ulope Is this a race condition?
If so I'd retry as long a s there are duplicates in the list of nodes!?

Yes looks that way.
This is the function we use to get a free port number:
https://github.com/raiden-network/scenario-player/blob/a3665f4d8784cfb561fdeb908c198886f6ec3863/scenario_player/node_support.py#L235-L245
This has a race in so far as that a port that has not been connected to can immediately be reused by the kernel.
In the Raiden tests we used to have the same problem and solved it with this (which for some reason is only used on macOS at the moment):
https://github.com/raiden-network/raiden/blob/c1ab0e6ea6289c5853247700d066f1dcc9e1cf87/raiden/network/utils.py#L35-L71


Project Proposal

Complete the Project Proposal by Feb 24th

Expected inputs and outputs
Topic, problem to be investigated
Team members
What you are going to deliver


Error on importing ANYTHING from this lib

I just did
$ npm install --save react-toolbox
and
import { Button } from 'react-toolbox';
Now I keep getting the below error from my webpack! What gives?!
Failed to compile.

Error in ./~/react-toolbox/lib/button/theme.css
Module build failed: Error: composition is only allowed when selector is single :local class name not in ".raised", ".raised" is weird
    at Array.map (native)
 @ ./~/react-toolbox/lib/button/theme.css 4:14-120 13:2-17:4 14:20-126

Im trying to include this in the app generated by create-react-app if that makes a difference...

If you'd be a little more patient, you should have already found the answer https://github.com/react-toolbox/react-toolbox/issues/1054#issuecomment-267910222

@liangchunn Sorry if I came off as impatient and aggressive, not sleeping for 36 hours will do that to a person.
Will go through the link you posted in my free time. Thanks a bunch!

Thank you @liangchunn 😊


Updates to samples and documenation (SlcTerms)

June 2022 updates

Couple of minor changes, looks good otherwise!


hello GDGoenka university

add new comments as you asked

@ashishmangla0 Are you sure that the email domain which you wish to add is gdgu.gdgu.org ? Double "gdgu"? Which webpage proves that your school recognizes it as a domain for students?
I am sorry, the comments have NOT to be in the file, the comments are what you reply to the email from GitHub, or what you answer on the webpage of your request in the "Conversation" section.

@philipto  yes. i am sure.  want to mention they have multiple domains like http://gdgoenka.ac.in/ only for emails. and for student/ teacher logins they are using "gdgu.org" only for emails.
https://user-images.githubusercontent.com/24789070/43310556-7f04b99c-91a5-11e8-8192-f18c3b8489bc.png

@philipto it not mentioned such as on any webpage. but I mention a  link on which it says "gdgu.org" owned by "Anjani Kumar Goenka"

@ashishmangla0 Thank you. Actually, this page proves that this domain is owned by the university: http://www.gdgoenkauniversity.com/iclass2018/conference-venue/
However, I will have to close this request without merging, because it has wrong filename. Please rename lib/domains/org/gdgu/gdgu.txt to lib/domains/org/gdgu.txt , because the domain is gdgu.org, not gdgu.gdgu.org. There is extra gdgu directory in the filename now, it is not necessary. Thank you.

@philipto thanks for confirming this.

@ashishmangla0 Pull request merged. Thank you!


@oclif/screen is deprecated

The subdependency @oclif/screen, which @oclif/core v1 uses, is deprecated
Updating @oclif/core to v2 should fix it (breaking changes)

I think this was fixed. should we close?

@oclif/core is still being used at 1.x 🤷♀ did anything change that fixes it?

just updated dotenv-vault to the latest version and it's still an issue

My bad I misread. Sorry!


AllowBlindTrading configurable

Thanks for this great piece of sotware!
Is it possible to make AllowBlindTrading configurable (without manuell config.ini) in one of the next versions?

included on commit<PHONE_NUMBER>1861da7ec9655f9cd8c9a46b20d1fa


Added type declarations for BLIK payment.

Summary & motivation
Added type declarations for confirmBlikPayment (https://stripe.com/docs/js/payment_intents/confirm_blik_payment).
Testing & documentation
Added unit tests similar to other payment methods.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Support macOS

I was able to make a hacky version, but should try to automate it properly with correct install_name_tool / rpath stuff.

MacOS support added.


Pinging specific iface does not work: Fix broken parentheses in setsockopt call (IDFGH-5676)

The call to setsockopt has the parentheses in a wrong way, which causes the whole functionality of pinging a specific netif instance to fail.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.imarkov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for your contribution.

Just remind that v4.3 also needs the fix.

Hi @igrr @Alvin1Zhang
This one is a classic case of one-line-fix which fixes a real bug.
I'm wondering if espressif has some standard process to speed up merging such fix.
I asked this because it may take very long time to apply to impacted branches.
Below is another example of such one-line-fix which fixes a real bug.
https://github.com/espressif/esp-idf/issues/7047 (And people are waiting, e.g. https://github.com/espressif/esp-idf/issues/7047#issuecomment-862181856 )
19 May 2021  Issue reported
7 Jun  2021  Commit to master
30 Jun 2021  Commit to release/v4.3
And sync to github time is slightly longer than the commited time.
PS. I'm not asking to take special care of this PR. (@suda-morris  did very quick response on this PR)
I'm asking if you have some standard process to speed up merging such fix.

@AxelLin Thank you for the suggestion. There is no existing special process for one-liner fixes compared to all other PRs. The basic process is: 1) the PR is assigned to a developer, 2) if the PR doesn't need additional work, the developer will create an internal merge request, adding release notes and any required tests, 3) code owners review the merge request, 4) once the merge request is approved it can be merged, 5) backport merge requests are created and handled in a similar way. Indeed PR handling gets stuck at different points, for example this PR is stuck at step 2, since the developer who is assigned happens to be on leave now. We are looking at options to automate more steps in this process to make the handling of PRs more efficient.
Regarding this specific bug, I don't necessarily agree with you that there is a need to speed up merging into release branches, unless the PR author specifically requests the bug to be fixed on a particular release. For bugs that result in random failures or unreliable behavior, we do need to backport them quickly, since users might encounter this issue without even changing much in their applications that are already deployed. On the other hand, for bugs that result in a certain use case being completely broken, we could argue that if noone has reported such issue for a release branch, the feature (or use case) is simply not used. Of course, we do need to fix the issue in release branches eventually. But due to lower impact, I would classify the urgency of backporting as "normal" rather than "high".

well, this is indeed not a regression because it actually never work.
However the API is there and if you call ping with specific interface
it will run into Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.

Changes have been merged with https://github.com/espressif/esp-idf/commit/ee531c748a83212312eba7390534a70fe6e88445, thanks for your contribution again.

Would you apply this fix for v4.3?


Update machine-requirements

Update VS preview version and mention Podman as supported alternative to Docker Desktop.
Microsoft Reviewers: Open in CodeFlow

this file covers (is linked from) "using daily build" and "contributing". But as of GA, there's a 3rd scenario -- "using supported build". Eg. , for the latter, we presumably put the latest version of 17.X that is GA'd whatever that is.
I guess when we get to GA in 2 weeks, we should update to add that info.


Fix for auto creation of CHW group participant when enrolling newborn

https://github.com/Gizra/ihangane/issues/3150

Trivial change. Merging.


[Deployment]: [Configure expiry for File Store Service]

Describe the bug
Configure expiry for File Store Service.

There's a setting in the filestore service. That can be configured via Helm charts.
Above info from Subhashini, we can set it as 15 minutes.

@suresh12 .
Found this in application.properties of filestore:
presigned.url.expiry.time.in.secs=86400 (this vaule is enabled by default)
Reference: https://github.com/egovernments/Digit-Core/blob/2.9-LTS/core-services/egov-filestore/src/main/resources/application.properties


sql bug

I use where clauss
".where("sex").eq("1") .whereOr().whereAnd.where("id").eq("11").where("name").eq("tom").endAnd.where("code").eq("code1").endOr". The sql should be express as “ sex=1 and ((id=11 and name=tom)  or code=code1)。but actually is “sex=1 and (id=11 and name=tom  or code=code1)”。 Is it a bug?

but the root predicater of cb's where manager seems right.

The predicate you're seeing is correct. Hibernate ORM simplifies parenthesis. Since and binds stronger than or there is no need to put parenthesis around the id=11 and name=tom part.


[enhancement] Support TCP Keep-Alive on MySQL connections

The default behavior of Options.KEEP_ALIVE is typically disabled, meaning that TCP keep-alive is not enabled by default. This means that if you do not explicitly enable it, the connection will not send keep-alive probes when idle.

run buildall


After restoring ACM (in an already installed ACM) OperatorHub is in FAIL state

After restoring ACM (in an alrady installed ACM) OperatorHub is in FAIL state:Saying  "CatalogSource was removed"
FYI @cdoan1

Catalog Sources to look at:
openshift-marketplace   certified-operators   Certified Operators   grpc   Red Hat     4d14h
openshift-marketplace   community-operators   Community Operators   grpc   Red Hat     4d14h
openshift-marketplace   redhat-marketplace    Red Hat Marketplace   grpc   Red Hat     4d14h
openshift-marketplace   redhat-operators      Red Hat Operators     grpc   Red Hat     4d14h

so this error implies that we don't have some dependent resources backed up?
downstream install, we deploy our out catalog source, I'll keep my eye on what happens.


Add environment variables for database.

@PadawanTony Do you mind if I add environment variables for the database? I need this when developing locally.

@rdok Sure go ahead. Maybe use .env?

Resolved by #24


Minimal major configuration overhaul

Description
Part of the RFC: https://github.com/hyperledger/iroha/issues/2585
After making semi-minor changes to the config and CLI, I think it is possible to make a major step in Configuration Overhaul. In this issue I describe how I see this next major step.
At the very least it should match with the configuration reference (https://github.com/hyperledger/iroha-2-docs/pull/397), which I will enhance at the same time.
Planned changes

Drop JSON/JSON5 support for the configuration. Use TOML exclusively.
Rename and restructure parameters, re-think ENV variables
Support extends mechanism for easy configuration composition
Move all parsing and validation logic into iroha_config, clearly distinguishing user-provided config from the parsed one
Implement configuration tracing mechanism
Move chain-wide parameters into a separate section until it is moved from the config entirely: https://github.com/hyperledger/iroha/issues/4028
Perhaps, remove complex JSON values from ENV entirely: leave this space for primitives only
Perhaps, use miette for comprehensive error reports

Goals in mind
Since there will be a lot of boilerplate, it makes sense to continue development of project soukousei which will provide a generic way to work with configuration. However, I think it would be too costly to bother about it right now. Instead I want to re-write iroha_config fully manually. Although there will be a lot of boilerplate, the process will be streamlined and focused on the final result from the start. Moreover, after manual implementation it will be clearer how to design soukousei.
Therefore:

Re-write iroha_config fully manually, despite having a lot of boilerplate
Write code while keeping in mind that boilerplate will be moved to the library
Prioritise errors handling quality: collect as much info as possible, build comprehensive reports

re: miette: might also want to consider ariadne, which is focused solely on formatting the output nicely without trying to cover the use-cases of thiserror which might or might not be meaningful.
What would also be nice to see diagnostics-wise is emission of all validation errors in one go, so that the user would not have to re-try launching iroha after fixing errors one-by-one and could instead see all (or, at least, most) of the validation problems right away. This can be achieved by using a error accumulator pattern, like was done in iroha macros (the emit! macro doesn't fail the validation right away, allowing the execution to proceed and collect some more possible errors)

might also want to consider ariadne

Thanks, will consider

What would also be nice to see diagnostics-wise is emission of all validation errors in one go

For sure! It is one of the main points of the RFC.

Closed by #4239


Corrected the redirect link.

Description
This PR fixes the error when redirecting to home from navbar in index.html and chapter.html

Thanks @Aarav238 , we will review and merge it soon!

thanks @akshathar-navada


Fix typo - E4_SendSmsChallenge is an activity trigger

@scottmckenzie : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good @scottmckenzie Thanks


Wenxh/fp8 on a100 v1 pr

simplify fp8 cast asm

Tasks
Version
Filter
n-shot
Metric
Value

Stderr

gsm8k
3
strict-match
5
exact_match
0.8173
±
0.0106

flexible-extract
5
exact_match
0.8196
±
0.0106


Typescript types bug

Version
V2.6.1
Reproduction link
https://github.com/orblazer/gestion-tmp
Steps to reproduce

Clone my version of vue-toasted (https://github.com/orblazer/vue-toasted/tree/patch-1) and link that (ex: yarn link)
Clone my version of @nuxtjs/toast (https://github.com/nuxt-community/modules/pull/272) and link that (ex: yarn link)
Install the reproduction git
Try run with yarn dev

What is expected ?
That run perfectly (without error)
What is actually happening?
This is run with error on nuxt but not have error in Visual Studio Code.
The error : https://imgur.com/DQmlHyP

This bug report is available on Nuxt community (#c9026)

@orblazer The error explictly said that $toast type is not defined as part of a Vue instance, which doesn't allow you to do this.$toast.  If you don't have the error in VSCode, I guess you probably get autocompletion on it ? I think it's a TS configuration issue and not a Nuxt issue but I don't have any clue for now on what's going on, did you have the chance to search further ?

@kevinmarrec Hello, i have fix my problem with useTypescriptIncrementalApi: true in build.typescript.typeCheck

Alright ! @orblazer, feels free to close your issue then 😃


Implementation in TypeScript

I did an implementation for this proposal just for fun.
https://github.com/Jack-Works/TypeScript/tree/await.ops

[x] Syntax: Basic support
[x] Type: Basic support
[x] Transpile: Downlevel to ES2020
[x] Type: Support concrete tuple type
[x] Type: Check if Promise.{*} exists
[ ] Syntax: Require a space after the operator? (Current impl await.all[array] is valid)
[ ] Service: Auto complete after await.
[ ] Service: Syntax highlight
[ ] Service: Refactor suggestion
[ ] Service: Hover quickinfo?
[x] Type: Unique type error message

Screenshots:

In TypeScript, Promise.all has 10 generic signatures. If the array has more than 10 items in it, it will fail. The new syntax does not have this limitation.

Downgraded to ES2020, they are the same.

Support iterables

Playground: https://www.typescriptlang.org/play/index.html?ts=4.0.0-pr-39224-4&ssl=1&ssc=1&pln=5&pc=2#code/IYZwngdgxgBAZgV2gFwJYHsIwLbFRACgEoYBvAKBipmAHc9kA6YAGxZgAZLqpMRkYAbQAeAXRgBeGvVRNWLQQAUATumyoQAU0bLNIdCwBumggCYAzOaKjuVYY2ToAosIAOmTRDSti5AL5AA


HHH-11838 : Added tests for getting the ID from a proxy for an entity…

… that does not exist
https://hibernate.atlassian.net/browse/HHH-11838
I don't think the fix is consistent with JPA.
Documentation for EntityNotFoundException says:
"The EntityNotFoundException is thrown by the persistence provider when an entity
reference obtained by getReference is accessed but the entity does not exist. ...
The current transaction, if one is active and the persistence context has been joined to
it, will be marked for rollback.
I've added a test that follows what is defined by JPA. It fails with the current fix. After reverting the commit, the test will pass (after resolving conflicts).

I'm trying to understand the concern here.  Is your concern, Gail, that calling the identifier getter on a proxy does not trigger that rest of the proxy state to be loaded?

After discussing with @dreab8 I see that that is indeed the concern.  And while I get where you get that idea from, I do not agree with the behavior you propose because it is a regression from what we had always done.  In that regard HHH-11838 is simply reporting a regression.  I am not aware of when that original behavior was changed, but it should not have.
Aside from being an obvious performance question and a regression behavior, I think it a logical assumption that calling #getId on a thing i just got by id does not need to "do anything" to be able to return the id value.
To me, this is all correct - as long as accessing other state on the proxy leads to the EntityNotFoundException.
@dreab8 says he asked @vladmihalcea to amend his commit to add a setting to control this.  I can definitely see value in that, mainly in case the TCK ever decides to try to add a test for this[1].  However that setting's default should absolutely be to not trigger the query when accessing the id.
[1] However I am pretty sure it does not and will not because other providers make this same assumption.

@sebersole @gbadner @dreab8 After analyzing the issue, I came to the same conclusion as Steve.
I remembered that Hibernate was not supposed to trigger a Proxy initialization when calling the id getter. What I didn't remember was that this behavior has been working when using property-based access.
The HHH-11838 issue has actually done the same for field-based access, so now, they behave in the very same way.
Therefore, even if we reak the JPA spec, I think it's the spec that's broken since we've been having this behavior for a very long time now, and I don't think that any user will complain about not initializing the Proxy when calling the identifier getter.
To be JPA compliant, I'll create a new issue which will combine Gail's test and a new one that proves that we've been having this issue for property-based access even before we fixed HHH-11838.

@gbadner @sebersole @dreab8 I created HHH-12034 and pushed a commit which demonstrates that we have this issue for both field-based and property-based access.
It's better to address both using a new issue instead of reopening HHH-11838.


Link to Discord stays in English even if selected another language

Describe the bug
The discord link at the bottom stays in English instead of changing to the selected language.
To Reproduce
Steps to reproduce the behavior:

Change the website language at the bottom using the dropdown
See the error

Expected behavior
The Discord text should change to the selected language.
Example:
In dutch, discord should be "onenigheid"
Video Showcase / Proof
Imgur Link
What device are you on?
I'm on the Brave browser in Windows 10.
Brave Browser Version: V1.21.74

Fix submitted as suggested in 'Expected Behavior'.

Now, I think I might have jumped the gun on this. I apologise.

Now, I think I might have jumped the gun on this. I apologise.

All fine, I decided to also get into some code contribution so I did the translations myself and then pushed a PR. Just waiting for it to be merged,

Isn't this expected behavior? Discord is a brand name, they don't translate it on their own website.

Isn't this expected behavior? Discord is a brand name, they don't translate it on their own website.

Yes, exactly.

Reminder that #742 that "fixed" this issue got merged


Compatibility of TileDataset with Dataloder

The following code
ds = PadoDataset('../../../../pathdrive-pado-tggates/local_dataset/', 'r')
ds = ds.filter(filter_local)

  tile_ds = TileDataset(
      ds,
      tiling_strategy=FastGridTiling(
          tile_size=(512, 512),
          target_mpp=MPP(1, 1),
          overlap=0,
          min_chunk_size=0.5,
          normalize_chunk_sizes=True,
      )
  )

  dl = DataLoader(tile_ds, batch_size=2)
  for batch in dl:
      print(batch)
      break

gives the following error
TypeError: default_collate: batch must contain tensors, numpy arrays, numbers, dicts or lists; found <class 'NoneType'>
I assume it's because some of the metadata is None
ImageId('acetamide', 'Kidney', '65440.svs', sit...     713         1              1     acetamide  Kidney  ftp://ftp.biosciencedbc.jp/archive/open-tggate...        1/1     Rat             Repeat  ...         345600.0   0.0      mg/kg     None       None         None            None       None   None
Iterating directly over the TileDataset works fine though, the issue seems to come from when I feed the TileDataset to the Dataloader.

If I pass explicitly the collate_fn defined in TileDataset
    it = zip(PadoTileItem._fields, map(list, zip(*batch)))
    # noinspection PyArgumentList
    dct = CollatedPadoTileItems(it)  # type: ignore
    tile = dct["tile"]
    # collate tiles
    if tile:
        if isinstance(tile[0], np.ndarray):
            dct["tile"] = np.stack(tile)
        else:
            dct["tile"] = stack(tile)
    return dct

as follows
dl = DataLoader(tile_ds, batch_size=2, collate_fn=collate_fn)
everything works. I would expect DataLoader to call the internal collate_fn automatically?

This is by design. Check here to see how the dataset's collate_fn method is passed to the DataLoader constructor:
https://github.com/Bayer-Group/pado/blob/635d7b8b57e527254d6302730100a6dab5a2095f/pado/itertools.py#L621-L637
We could check if since this was written, pytorch made changes that allow a dataset to provide these methods via inspection.

Works as suggested!


<EMAIL_ADDRESS>could not be found

Code worked yesterday, but today not anymore. Didn't change a thing. This occured to me multiple times.
I get the following error. Couldnt reliably fix it yet.

error: bundling: Error<EMAIL_ADDRESS>could not be found, because 'node_modules/react-native/Libraries/CustomComponents/NavigationExperimental/assets' is not a subdirectory of any of the roots  ('/home/sirhennihau/Workspace/next')
at /home/sirhennihau/Workspace/next/node_modules/react-native/packager/src/AssetServer/index.js:181:13
Bundling index.android.js  100.0% (432/432), failed.
Error<EMAIL_ADDRESS>could not be found, because 'node_modules/react-native/Libraries/CustomComponents/NavigationExperimental/assets' is not a subdirectory of any of the roots  ('/home/sirhennihau/Workspace/next')
at /home/sirhennihau/Workspace/next/node_modules/react-native/packager/src/AssetServer/index.js:181:13
Error<EMAIL_ADDRESS>could not be found, because 'node_modules/react-native/Libraries/CustomComponents/NavigationExperimental/assets' is not a subdirectory of any of the roots  ('/home/sirhennihau/Workspace/next')
at /home/sirhennihau/Workspace/next/node_modules/react-native/packager/src/AssetServer/index.js:181:13

I run code for a static userinterface mockup. Uses compressed media data in the views.
"dependencies": {
"react": "16.0.0-alpha.6",
"react-native": "0.43.3",
"react-native-video": "^1.0.0"
}
Run on an Android
Ubuntu 15
Atom, Android SDK, node.js, React-Native-Video.
Any suggestions?

 render() {
    return (
      <ScrollView>
        <Text>RnB</Text>
        <ScrollView horizontal={true}>

          <Video
          style={{ flex: 1 }}
          source={require('./app/media/compressed/Chrisbrown-1.mp4')}
          style={{ width: 150, height: 150 }}
          ref={(ref) => {
            this.player = ref
          }}
          muted={true} />

          <Video
          style={{ flex: 1 }}
          source={require('./app/media/compressed/Freestylekendrick-1.mp4')}
          style={{ width: 150, height: 150 }}
          ref={(ref) => {
            this.player = ref
          }}
          muted={true} />
          ...
        {/*
        //Multiple ScrollViews follow here, containing videos and images
        */}
          ...`

you can set a long REACT_NATIVE_FSOP_TIMEOUT, the default value is 15000ms, but if toooooo mutch files if may not enough, but it give a confused error msg...
btw, you can change it in /node_modules/react-native/packager/src/AssetServer/index.js

Thanks @saubcy! This solved the issue for us because we have ~600MB of assets in the packager.

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


AutoMapper 5 IsSourceValueNull

The IsSourceValueNull method used in the Mapping classes has been removed as of AutoMapper 5.
Updating to AutoMapper 5 will break any projects using IdentityServer3.EntityFramework.

@jbogard

IsSourceValueNull "source == null".

Should I just open a PR here?

If you don't mind
Sent from my iPhone

On 30.06.2016, at 15:23, Jimmy Bogard<EMAIL_ADDRESS>wrote:
Should I just open a PR here?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

#113 and waiting for the CLA email. Or is that CYA...


Update eslint-plugin-jest-dom and fix issues

Summary
There have been changes to their recommended ruleset, so this PR runs npm run lint:fix on everything.
Relevant Technical Choices

To-do

User-facing changes

Testing Instructions

Fixes #

There seems to be 8 test fails here. Can you take a look and request review again.


reMarkable Paper Pro

Unfortunatelly the latest reMarkable is not supported, lined pages don't show lines.

No idea, lines are showing up in the PDF on the PC though…7. 9. 2024 v 13:33, Brian Schwabauer @.***>:
Interesting. I don't have a reMarkable Pro so this is going to be hard for me to diagnose. Are the lines showing up in the PDF, but not on the device? Any ideas on what might be happening?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

hi
Using RM2 pro and works great.
only issue is that year view aprox 30% of the page does not show on right side of page

Would you mind making a new PDF and changing the line/border color to something darker? I'm wondering if the reMarkable Pro needs more contrast to see the lines.
You can change the color under the Design section in the Advanced Settings:

This does work, but the lines come out quite thick (I assume because they're scaled up on the RMPP?). Also the other grey colours used in the planner, such as the sidebar and the highlights of day etc. don't quite show on the RMPP. And finally, the toolbar is covering parts of the page (I assume it was hardcoded to the toolbar width on the RM2?).

If you could add an option to support the RPP resolution, that alone would be fantastic.


Fresh Laravel v8.12 install, node.js - TypeError: commandConvert is not a function

cross-env version:7.0
node version: 15.2.0
npmversion: 7.0.8

What you did:
I created a fresh laravel installation, then ran npm install && npm run dev
What happened:
After a successful npm install, I get an error whilst running npm run dev:
TypeError: commandConvert is not a function
/var/www/x/node_modules/cross-env/src/index.js:15
commandConvert(command, env, true),
^
TypeError: commandConvert is not a function
at crossEnv (/var/www/x/node_modules/cross-env/src/index.js:15:7)
at Object. (/var/www/x/node_modules/cross-env/src/bin/cross-env.js:5:1)
at Module._compile (node:internal/modules/cjs/loader:1102:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1131:10)
at Module.load (node:internal/modules/cjs/loader:967:32)
at Function.Module._load (node:internal/modules/cjs/loader:807:14)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:12)
at node:internal/main/run_main_module:17:47
Reproduction repository:
Laravel v8.12

https://github.com/kentcdodds/cross-env/issues/257


Add Select Options for Break Time Increments Up to 1 Hour

Description
Overview
This pull request introduces a significant update to the break time selection feature in tw+. Previously, the break time was inputted as a text field, which was less intuitive and prone to user input errors. With this update, we have transitioned the break time input to a more user-friendly select dropdown, offering predefined options in 5-minute increments, ranging from 5 minutes to a maximum of 1 hour.
Changes
Replaced the text input field for break time with a select dropdown (#break-time).
Implemented a JavaScript function handleTimeInputs() to dynamically populate the select dropdown with time options, in 5-minute increments, up to 1 hour (00:05 to 01:00).
Adjusted the HTML structure to accommodate the new select element.
Removed the old text input handling logic that was associated with the break time field.

Thank you very much for your contribution, @carloshendvpm. However, it would be interesting to migrate these improvements to the branch twp-v2 where we are implementing v2 of TWO+ as you can see in PR #41.
Furthermore, regarding its implementation, I believe it would be welcome if we increase this time to be longer than just 1 hour. Depending on the user and their schedule flexibility, it is possible to have an accumulated interval between their points of more than one hour. But your idea is good and improves usability.
Please consider contributing to this v2 by moving these changes to the current framework we are working on.
Thanks!


Use slots in ArtifactManifestEntry

Fixes
Fixes WB-NNNN
Fixes #NNNN
Description
What does the PR do?
Testing
How was this PR tested?
Checklist

[ ] Include reference to internal ticket "Fixes WB-NNNN" and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Ensure PR title compliance with the conventional commits standards

copilot:poem

Current dependencies on/for this PR:

main

PR #5512   👈

This comment was auto-generated by Graphite.