Add comment about default service port 8080

Adds comment into ./Dockerfile just in case someone pulls the image and stuck wondering what the hell is the default service port.  (LIKE I DID!!!)

Default of WHAT? read stuff man.  There's a difference between the container running and Spring setting up the app running on port 8080 INSIDE the container.  TRUE.
But what about reaching the service (DB2Rest) that is running in that container from the OUTSIDE of the container.  Like your host PC/Mac, or from a system in another cloud or halfway around the world through the public internet?

By default, when you create or run a container using docker create or docker run, the container doesn't expose any of its ports to the outside world. Use the --publish or -p flag to make a port available to services outside of Docker. This creates a firewall rule in the host, mapping a container port to a port on the Docker host to the outside world.

https://docs.docker.com/network/#published-ports
https://docs.docker.com/reference/dockerfile/#expose

The host port can be set with -p
We can specify that in the docker documentation.
Once the app is packaged, the users cannot change the dockerfile and there is no utility of doing that either.

Also, what's interesting, is that PostgRest doesn't use a Dockerfile... they use Nix for building:

The image is built from scratch using Nix instead of a Dockerfile, which yields a higly secure and optimized image. This is also why no commands are listed in the image history. See the PostgREST respository for details on the build process and how to inspect the image.

I'm done here.

We will switch to build packs eventually.
This is just a start.
On Sat, Apr 27, 2024 at 1:23 AM Thad Guidry @.***>
wrote:

I'm done here.
—
Reply to this email directly, view it on GitHub
https://github.com/kdhrubo/db2rest/pull/509#issuecomment-2080384859, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAISPRBNVYWDZ4PZ4CENZ4LY7M77DAVCNFSM6AAAAABG2D6APCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGM4DIOBVHE
.
You are receiving this because you were assigned.Message ID:
@.***>

--
Kind Regards... Dhrubo
http://www.linkedin.com/in/dhrubo


WIP: ensure clients see their transaction_ids

Suppose

Alice has made an incremental (i.e. with pos) sliding sync.
The proxy has nothing to give to Alice right now and is waiting for a live update.
Alice /sends a message into a room using a transaction_id.
Bob is also in the room and using the proxy.
Bob's poller sees Alice's message without a transaction ID.
This message is handed off to Alice's /sync handler and sent to Alice without a transaction id.
Alice's poller later sees the message with the transaction id.
(Not sure if that txn_id ever arrives at Alice's client?)

The bold bullet is bad because it means that the client doesn't realise it has just received the event it sent, meaning that the "local echo" flickers.
We want to fix this by never notifiying a waiting sync handler about Things until its dedicated poller has seen that Thing.

I assume everything is broken because I'm now delaying certain messages for up to a second.


Temporarily remove imagebutton mapper

What does this PR do?
We have an issue at the moment with base64 where too many bitmaps are being created and recycled, resulting in excessive garbage collection. We need to turn off the feature until it can be fixed. In this PR I'm temporarily removing ImageButtonMapper from the list of mappers used in the traversal, as this is the only place where we enter the base64 logic.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1530 (ef005ea) into develop (8fbf901) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1530      +/-   ##
===========================================
- Coverage    83.43%   83.42%   -0.01%
===========================================
  Files          438      438
  Lines        14848    14846       -2
  Branches      2237     2237
===========================================
- Hits         12387    12384       -3
- Misses        1873     1879       +6
+ Partials       588      583       -5

Impacted Files
Coverage Δ

...adog/android/sessionreplay/SessionReplayPrivacy.kt
100.00% <ø> (ø)

... and 18 files with indirect coverage changes


fix(elec-pair): disable auto-pairing of "<" in `org-mode'

minemacs-after-startup load after org|markdown-mode-hook so (bound-and-true-p electric-pair-mode) will return nil because electric-pair-mode is not yet enabled

Run emacs with client will be fix

This PR make sense, I will test it later. Thanks

This error only occurs when opening org files with emacs *.org.


Server Boost page

The Server Boost page on Account settings doesnt fit into the redesigned modal

thank you for sharing this!


Switch to Google Benchmark for expression template benchmarking

This PR switches the expression template timing checks to a separate executable, meaning that the tests are no longer bogged down with timing checks.  A set of utility functions were introduced to reduce the amount of copy-pasting of initialization logic in each test.
For comparison purposes I also attempted a naive MPI implementation of the expression evaluation.
Now that Google Benchmark is enabled, we could explore benchmarking other components of serac.

LGTM


DocumentRepository::find() now handles an array of identifier values

Should it check the keys of $id are in getIdentifierFieldNames ?

I don't understand this change. Doctrine MongoDB ODM doesn't have composite primary keys, the only reason getIdentifierFieldNames() exists is for the interface. It will always return an array like array('id') and won't ever have more than 1 element.

@jwage the EntityUserProvider in Symfony uses find with an array of keys, so you get send array('id' => 'somthing') as the argument for the find method.

@henrikbjorn: I think given the revisions I suggested, we can sidestep my previous issue with UnitOfWork::tryGetById() not accepting an array.

This broke the tests. Fixed here cff550669b253a6f0082f312b5560017d2e36e14


bpf: allow prefix of /32 and /128 in RSS src CIDR

See commit desc.

test-me-please

test-me-please

retest-runtime

retest-4.9


invalid metric name with null byte crashes persistence of all metrics

Due to an error in our application we have sent a metric name with a null byte via TCP to Carbon cache. This results in following error message in log:
07/01/2015 10:03:14 :: Unhandled Error
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 484, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.6/site-packages/twisted/python/threadpool.py", line 172, in _worker
    result = context.call(ctx, function, *args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/lib64/python2.6/site-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
--- <exception caught here> ---
  File "/usr/lib/python2.6/site-packages/carbon/writer.py", line 158, in writeForever
    writeCachedDataPoints()
  File "/usr/lib/python2.6/site-packages/carbon/writer.py", line 91, in writeCachedDataPoints
    for (metric, datapoints, dbFilePath, dbFileExists) in optimalWriteOrder():
  File "/usr/lib/python2.6/site-packages/carbon/writer.py", line 54, in optimalWriteOrder
    dbFileExists = exists(dbFilePath)
  File "/usr/lib64/python2.6/genericpath.py", line 18, in exists
    st = os.stat(path)
exceptions.TypeError: stat() argument 1 must be encoded string without NULL bytes, not str

Because we could still access our statistics we didn't noticed that Carbon is not persisting incoming metrics anymore. Queue caches did increase continuously until it crashed with out of memory. We've lost all metrics within this period, because this one invalid metric did abort persistence of all further metrics.
Robustness of Carbon needs to be improved here.

We probably just need to catch that TypeError exception on the exists(dbFilePath).


Deploybot Deployments

Have not heard back from Deploybot on my support email send on Tuesday. Looks like they may have live chat but not available at the moment. Will try that today, and if not available, will send another email.

Thank you. Which deployment method are you using?

SFTP. Login based, then tried public key authentication.

I'll have a look and see if I come up with anything. brb

Looks like it was the paths. You had /theliteraryreview.org… but it needed to be /home/minpro1/theliteraryreview.org…

Ugh..thanks. Will start pushing some safe tickets.

No worries - sorry I didn't equip you with all the info you needed.


provide data both on an account's holdings as well as the participant…

…s reputation tokens and size
Added more stuff
sqlite> select * from all_participants;
              universe = 0x3d777ea1541a7dec004972b283d53af3633b7531
              marketId = 0x49e206f44268ed4e26c8912d84081ac7511130b6
                  type = initial_report
    participantAddress = 0x2432ac65710fde9297f9477bdaf3a0e8062ba3ac
                 owner = 0x913da4198e6be1d5f5e4a40d0667f70c0b5430eb
                  size =<PHONE_NUMBER>82291667
        accountBalance =<PHONE_NUMBER>82291667
       reputationToken = 0x69c95d801ba3890c7090bdedeb7e5cc8f2058586
reputationTokenBalance =<PHONE_NUMBER>82291667
              payoutId = 2
             completed = 1
        reportingState = AWAITING_FINALIZATION
               forking = 0
             disavowed = 0

              universe = 0x3d777ea1541a7dec004972b283d53af3633b7531
              marketId = 0xbcde24abef27b2e537b8ded8139c7991de308607
                  type = crowdsourcer
    participantAddress = 0x0308861267cfddb962c2664817979090d0dc6b88
                 owner = 0x913da4198e6be1d5f5e4a40d0667f70c0b5430eb
                  size =<PHONE_NUMBER>046875001
        accountBalance =<PHONE_NUMBER>046875001
       reputationToken = 0x69c95d801ba3890c7090bdedeb7e5cc8f2058586
reputationTokenBalance =<PHONE_NUMBER>070312501
              payoutId = 3
             completed = 1
        reportingState = FINALIZED
               forking = 0
             disavowed = 0

This separates the notion of the tokens that an account holds (accountBalance) from the reputation tokens the participant holds

Here's another good view into the data. payoutId 3 = winning, 4 = losing
              universe = 0x3d777ea1541a7dec004972b283d53af3633b7531
              marketId = 0xbcde24abef27b2e537b8ded8139c7991de308607
                  type = crowdsourcer
    participantAddress = 0x0782e4e784b5993a3ba08293d46f51182f2e6083
                 owner = 0x913da4198e6be1d5f5e4a40d0667f70c0b5430eb
                  size =<PHONE_NUMBER>64583334
        accountBalance =<PHONE_NUMBER>64583334
       reputationToken = 0x69c95d801ba3890c7090bdedeb7e5cc8f2058586
reputationTokenBalance = 0
              payoutId = 4
             completed = 1
        reportingState = FINALIZED
               forking = 0
             disavowed = 0

              universe = 0x3d777ea1541a7dec004972b283d53af3633b7531
              marketId = 0xbcde24abef27b2e537b8ded8139c7991de308607
                  type = crowdsourcer
    participantAddress = 0x858a983bab142aaf4fc80d3716ee5e6f33eb7672
                 owner = 0x913da4198e6be1d5f5e4a40d0667f70c0b5430eb
                  size =<PHONE_NUMBER>187500004
        accountBalance =<PHONE_NUMBER>187500004
       reputationToken = 0x69c95d801ba3890c7090bdedeb7e5cc8f2058586
reputationTokenBalance =<PHONE_NUMBER>281250006
              payoutId = 3
             completed = 1
        reportingState = FINALIZED
               forking = 0
             disavowed = 0

One of them, there is an accountBalance , but not reputationToken balance (as it has been cleaned out). In the other, there is an accountBalance of X and a reputationToken balance of 1.5X


Update .travis.yml - use latest LXML 4.5.x version

Use latest LXML 4.5.x version for testing

Build is failing due #130


[ERROR]: [Quests] This protocol does not support npc-effect: NOTE

My version of quests is 3.9.3. I get this error whenever I join in game after a server restart. I have all the default quests and I added one more quest. The error stops when there are no players in game. The plugin still works perfectly as far as I can tell but it is spamming my console and is rather annoying.

Thanks for the report. This has to do with the particle effect shown over a NPC's head when a quest is available (in this case, a Note particle). Although some particles are protocol-specific (meaning only for certain versions of Minecraft) the Note particle should work on all tested versions.
What is your Minecraft server version? Also, you can temporarily disable the "spamming" by setting npc-effects.enabled: false in your config.yml file.

My server version is 1.8.8, I do not see the npc-effect.enabled option in the properties but that might be because it is so old.

@garsh1 Thanks. Please try https://ci.codemc.io/job/PikaMug/job/Quests/113/


Alternative authentication entity name not fully supported

When running feathers generate app and not chosing the default answer (users) for ? What is the name of the user (entity) service?, the file names are adapted accordingly, but not the configuration file.
config/default.json still contains the fixed values:
...
  "authentication": {
    "entity": "user",
    "service": "users",
...

How should this be handled for the upgrade operation? There all authentication-related parameters are replaced with a fixed set again, overwriting user modifications.
Just copying authentication.entity and authentication.service from the current configuration would solve this issue, but continue to annoy anyone with local authentication modifications.


#97 Fixed deserializing of EventBridge object body

Issue #97
Description of changes: Deserialize EventBridge body if JsonValueKind.Object
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi, unit test added. (The unit test fails with the old code).


Auto-adding ssh public key to Jenkins config

Can be enabled by adding -e "add_public_key_automatically=true" to ansible-playbook command

Verified in my local vm 👍

Updated readme file + aerogear.org (https://github.com/aerogear/aerogear.org/pull/681/commits/8f61a136d406fa5e5ace540b598e1adf294e0701) and support for oauth

@psturc where does the use get the oauth token from? I had tested using Oauth in this JIRA https://issues.jboss.org/browse/AGDIGGER-222 and I thought it was necessary for the user to get the API token to do any requests.

@laurafitzgerald correct, user needs to provide OAuth token (API token) from Jenkins UI: <jenkins-url>/user/admin/configure, which means user already has to have the Jenkins instance running before running the playbook, otherwise it won't work (as mentioned in readme file).

@psturc thanks for clarification. In this case would you agree that we should add a manual step where the user is prompted to go get the oauth token and provide it to the installler? There are some JIRAs created around this in this epic. https://issues.jboss.org/browse/AGDIGGER-221 If you think there are some additional steps or the JIRA for this change falls under the epic feel free to add it.

@laurafitzgerald agreed. JIRAs under the epic LGTM

@psturc thanks. :)


Add Pendo Track Events for Weave GitOps CLI

As a user, I understand you are trying to build a product that helps me to get the job done and to do that effectively, data can be useful.  Please keep my privacy in mind and only collect what you need.  As an OSS user I want you to ask for my permission first before collecting information.  As an enterprise user I understand that you will collect this by default, but I do want to have the ability to turn it off.
As a product manager, I want to understand the most common OSS and Enterprise CLI commands that are used by our users.  It would be nice to know whether they are running the command from an OSS or Enterprise binary.  It would be nice to know which version of the CLI they are running the command.  It would be nice to be able to distinguish each user with a unique visitor ID.
New Acceptance Criteria

The name of the track event should be the command.  E.g. "beta run" or "create dashboard"
We should have this stored in a place where there is no impact if they upgrade to a new version of the CLI.  I.e. we do not have to keep asking them if we can collect info each release.
Each track event should have the following event properties "tier" which can be oss|enterprise and "version" which is the CLI version, and "app" which is "cli".
We would like to know which flags they are using and each flag should be their own track event.  Do not collect any information about each flag's value, just a simple "true|false" so we know it was used.

OLD Acceptance Criteria

We should have this stored in a place where there is no impact if they upgrade to a new version of the CLI.  I.e. we do not have to keep asking them if we can collect info each release.
Each track event should have the following event properties "tier" which can be oss|enterprise and "version" which is the CLI version, and "app" which is "cli", as well as the command after gitops such as "add cluster" or "run".
We would like to know which flags they are using.  Do not collect any information about the each flag's values they are using with each command, we just want the "key".

https://support.pendo.io/hc/en-us/articles/360032294291-Track-Events-Configuration#volume-0-5
Moved question to turn on to different ticket

FYI: @davidstauffer, @sympatheticmoose, @MostafaMegahid, and @josefaworks

@ozamosi based on the following discussion we might need to edit the acceptance criteria and the format in which the tracked command path and flags data is submitted:
https://weaveworks.slack.com/archives/C03EFTMT6P6/p1666269125478829
It should be easy to modify as soon as the updated criteria are provided.

Right now I am submitting all flags as a text string, so I just need to split it.

Good question,
I think we want the "flags" as individual event properties with "true" and "false".  This will allow us to use the data analytics features directly within Pendo.  The fact that we are now making each command a unique track event means we will be able to keep the event property count pretty low as they will be unique for each command that is run.
So in the above examples, I think this is the one we need to use:
{
    "event": "beta run",
    "properties": {
      "tier": ...,
      "version": ...,
      "timeout": true,
      "port-forward": true,
    },
}

I don't think we need to do "false" for the other flags, it should default to that...I can test it when you get a PR up.

@JamWils  sorry, one more question about, there is a minor contradiction between:

I think we want the "flags" as individual event properties with "true" and "false".
and
I don't think we need to do "false" for the other flags

Here is the list of all GitOpsRun flags (and there may be some globel flags used with it I suppose):
type RunCommandFlags struct {
	FluxVersion     string
	AllowK8sContext []string
	Components      []string
	ComponentsExtra []string
	Timeout         time.Duration
	PortForward     string // port forward specifier, e.g. "port=8080:8080,resource=svc/app"
	RootDir         string

	// Dashboard
	DashboardPort           string
	DashboardHashedPassword string

	// Session
	SessionName         string
	SessionNamespace    string
	NoSession           bool
	SkipResourceCleanup bool
	NoBootstrap         bool

	// Global flags.
	Namespace  string
	KubeConfig string

	// Flags, created by genericclioptions.
	Context string
}

So, I and not adding keys to the event properties for flags which are not used? Thus, the tracked event for the command above will not have, for example, "session-name": false  and "allow-k8s-context": false under properties?

Did you mean that each flag property should be a boolean value but that values with false value should not be submitted in the event props?

@JamWils I've updated the event properties, this is what I have right now for the following commands. Does it look right? (type, visitorId, and timestamp keys are required).
gitops beta run ./deploy/overlays/dev --timeout=3m --port-forward namespace=dev,resource=svc/backend,port=9898:9898
{
  "type": "track",
  "event": "beta run",
  "visitorId": "2fesk6Lqmi",
  "timestamp":<PHONE_NUMBER>256,
  "properties": {
    "app": "cli",
    "port_forward": true,
    "tier": "oss",
    "timeout": true,
    "version": "v0.10.2-rc.1-89-g88508ae7"
  }
}

gitops create dashboard ww-gitops --password=123
{
  "type": "track",
  "event": "create dashboard",
  "visitorId": "2fesk6Lqmi",
  "timestamp":<PHONE_NUMBER>661,
  "properties": {
    "app": "cli",
    "password": true,
    "tier": "oss",
    "version": "v0.10.2-rc.1-89-g88508ae7"
  }
}

There is a potential issue that a sanitized flag name could be the same as a hardcoded property key (app, tier, version).
What should I do about it?

Added a flag_ prefix to flags (based on @ozamosi 's suggestion), to avoid the conflict between flag names and names of hardcoded event properties. So, now the data tracked looks like:
{
  "type": "track",
  "event": "create dashboard",
  "visitorId": "hlHdSMskQE",
  "timestamp":<PHONE_NUMBER>574,
  "properties": {
    "app": "cli",
    "flag_password": true,
    "tier": "oss",
    "version": "v0.10.2-rc.1-91-g292e65b8"
  }
}

{
  "type": "track",
  "event": "beta run",
  "visitorId": "hlHdSMskQE",
  "timestamp":<PHONE_NUMBER>995,
  "properties": {
    "app": "cli",
    "flag_port_forward": true,
    "flag_timeout": true,
    "tier": "oss",
    "version": "v0.10.2-rc.1-91-g292e65b8"
  }
}

And each event property name (in total, with the prefix) cannot be longer than 32 characters.


tests: Use final and add constructor where needed

coverage: 87.309%. remained the same
when pulling 2fb75f50e175385e4362d72aee75899eda61506a on hazendaz:pom-cleanup
into 5d995de6908a722a6d3c07af99642b8699212808 on mybatis:master.


Papaya missing/weird translations (Spanish & French)

Issue
Missing translation strings in the new Admin UI and change log

"Add User" button (Spanish & French) and "Apply" button don't translate on Users Page

"Profile" next to user name in the Profile drop-down.

Bulk action secondary select box

French translations have  in place of an apostrophe

Program landing page: “Indicators missing ___”

Program landing page: “Program metrics for target periods completed to date”

Program landing page: “Change log” button

I'm running down the reports section.  Starting with IPTT:
None selected in filters (translated but showing english)
Excel (shouldn't be translated as a verb)
Change log (translated but showing english)
Change log:
Date and time (translated but showing english)
Indicator change log (translated but showing english)
Change type (translated but showing english)
Previous entry (translated but showing english)
New entry (translated but showing english)
Reason for change (translated but showing english)
Disaggregation report:
Show X entries (not translated)
No data available in table (not translated)
Showing X to X of X entries (not translated)
Previous (translated but showing english)
Next (translated but showing english)
Project report:
Project statuses (translated but showing english)
Export to CSV (translated but showing english)
All headers (translated but showing english)
Edit and View buttons (translated but showing english)
Show X entries (not translated)
Search: (translated but showing english)
Showing x to x of x entries (translated but showing english)
Previous (translated but showing english)
Next (translated but showing english)

[ ] Results modal: “This may be a badly formatted web address…”

"Program or country" isn't translated in ES in the nav bar

"No options" is inside a JS library and not translated ATM. This can be fixed by overriding it with a translated string.

The change log field names are always in english, as the translated strings call gettext during the class instantiation, instead of on a per-request basis.

[ ] Admin lite, Program page: “users” is not translated:

QA Passed:

FRENCH:

Secondary Select box FRENCH:

SPANISH:


Include static libraries in project

This PR add a static tag and libraries that allows one to build a standalone binary on Linux/Windows/macOS. Discussed in https://github.com/veandco/go-sdl2/issues/329 .

Hi @gen2brain, I have set up a repository that stores all the static libraries in https://github.com/veandco/go-sdl2-libs. I figured that since it takes about 37M, it would be better to make .go-sdl2-libs a submodule. Could you perhaps change it to submodule before I merge? That way, I think this repository will not store the files in history.
As a side note, I've also invited you to become a collaborator as well on the projects since you have done so much. Please join us! :grin:

Hi @veeableful, I changed libs to submodule. Thanks for invite! I think I can prepare some script to update SDL libs in future, and it should probably be done on some old Ubuntu, e.g. 14.04.
Also, I will see if I can update https://github.com/gen2brain/go-sdl2-android-example.

Thanks @gen2brain!


Add an @alpha annotation?

It would be really useful to have an annotation that we could use to indicate that some classes, methods, etc are experimental (@alpha, @beta, @experimental, or similar).
Some of our Dart libraries are reasonably mature and we rely on semver to indicate to consumers when breaking changes occur.  It's difficult to add experimental apis within a mature library while adhering to semver, so it would be awesome if we could annotate experimental code to indicate that the normal semver rules aren't being respected for this code (breaking changes may occur without a major semver release).
Is there a way to add an annotation for this to the meta package?

You can just create your own package with these annotations.
The annotations by themselves don't do much anyway.
Interesting would be what you want to get from these annotations.
Analyzer support? In what way?
https://github.com/dart-lang/sdk/blob/0c1e85ebadaa0680d4ff30acc1f3ac823c53756e/sdk/lib/html/html_common/metadata.dart contains similar annotations. Unifying them in a package like meta would IMHO make sense.

I'm wondering if @alpha is receiving as many tons of unintended mentions as I do every day :D.

Assigned to 'area-analyzer' since the analyzer team seems to maintain the meta package.

We generally add annotations to the meta package only when there is (or reasonably could be) tooling support associated with the annotation. I'm not sure what tooling support this would enable, so I'm not inclined to add it.

The most direct parallel for what we'd like to do with this sort of annotation is @deprecated.  Similarly, we'd like to call attention to the use of experimental code in the analysis process so that it stays front of mind for devs and we can guard against it in our CI process if desired.
At the moment, we're bastardizing @deprecated for this purpose, but it would be better if we could differentiate between code that is 'flagged' because it's deprecated vs because it's using an experimental api.

So a linter rule similar to what @deprecated does that can be enabled using .analysis_options

I suspect that this annotation wants to be a little different than deprecated.
The deprecation hint is produced for any use of a deprecated member that occurs anywhere (either inside or outside the declaring library / package) unless it is inside a deprecated member.
My guess is that we'd want to allow references to such code (we've been calling it provisional) inside the same package, because you wouldn't have added it if you didn't intend to use it in order to gain experience with it. The question is, is that enough, or do you need to be able to reference it from other packages in order to experiment with it? Can we precisely define when a hint/lint should be produced?

That sounds about right to me.  For the 'provisional' tag:

Don't hint for uses within the package it's declared in
Do hint when anything provisional has been referenced by a consumer of the package

Bump:
I'd like to see @experimental in package:meta. Rationale:

For projects using strict semver, removing any public API is a XX.##.## bump
@experimental could be used to loosen that restriction, i.e. only a ##.XX.## bump

We are considering automated tools similar to Elm that actually check your pubspec.yaml version is updated if your public interface has changed, and if we have these tools we'd need @experimental in order to get around them.
The rationale for being here versus say, package:strict_semver, is that the analyzer/IDE could give warnings to users that are using these APIs - perhaps also configurable in .analysis_options:
analyzer:
  warn_experimental_features: <true|false>

That way teams that don't have a huge migration/deprecation budget could avoid using these.

any chance of this happening?

Ah, that's what it was called. Thanks @bwilkerson

Yes, there appears to be increasing demand for it, so I think it's time. I'll start with defining the annotation, then we can hammer out the specific of analyzer support.

Thanks Brian! Let me know if you'd like to chat re: specifics after this lands.

This adds the annotation: https://codereview.chromium.org/2789843003/. Analyzer support will follow, but not immediately.

any update on analyzer support for this annotation?

No, sorry, there hasn't been any work done on this yet.

What would the analyzer support do?

As discussed earlier in this issue, produce a hint if any code outside the declaring package makes use of experimental APIs.

Do we consider this complete since @experimental is implemented?


INCBIN_EXTERN doesn't work on AppleClang <IP_ADDRESS>20039

The build error: https://travis-ci.org/andyli/incbin/builds/367773037
Undefined symbols for architecture x86_64:
  "_gLoremData", referenced from:
      _main in asserts.c.o
  "_gLoremEnd", referenced from:
      _main in asserts.c.o
  "_gLoremSize", referenced from:
      _main in asserts.c.o
  "_gOnebyteData", referenced from:
      _main in asserts.c.o
  "_gOnebyteEnd", referenced from:
      _main in asserts.c.o
  "_gOnebyteSize", referenced from:
      _main in asserts.c.o
  "_gSevenbytesData", referenced from:
      _main in asserts.c.o
  "_gSevenbytesEnd", referenced from:
      _main in asserts.c.o
  "_gSevenbytesSize", referenced from:
      _main in asserts.c.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [asserts] Error 1
make[1]: *** [CMakeFiles/asserts.dir/all] Error 2
make: *** [all] Error 2

My test code can be seen at https://github.com/andyli/incbin/commit/47c3b76c833c9d40d13d1dbf84274638db9d6911
Notice that the test passed in the Linux builds.

Looks like maybe Apple Clang uses different name mangling for symbols, can you check if it defines __USER_LABEL_PREFIX__ and maybe dump the contents of the object file's symbols with nm -g file.o.  It appears the symbols are there, maybe the linker expects one to specify symbol visibility ?

I don't know. But I found that the data.c produced by the incbin program can be used with the INCBIN_EXTERN header file. Maybe it is useful for you to look at the data.c.o object: data.c.zip

nm on both seems the same s and S are the same according to my man, this seems weird, the U ones are really interesting tho. I don't have an Apple to dig deeper into this.

Can reproduce this on Apple clang 11.0.0
I think it does have to do with symbol visibility. man nm says:

Each symbol name is preceded by its value (blanks if undefined).  Unless the -m option  is  specified,  this value  is followed by one of the following characters, representing the symbol type: U (undefined), A (absolute), T (text section symbol), D (data section symbol), B (bss section symbol), C (common symbol),  -  (for debugger symbol table entries; see -a below), S (symbol in a section other than those above), or I (indirect symbol).  If the symbol is local (non-external), the symbol's type is instead represented by the corresponding  lowercase letter.  A lower case u in a dynamic shared library indicates a undefined reference to a private external in another module in the same library.

It looks like the linker is looking for the _-prefixed symbols, but those are “local” so it's not finding them?

I found a workaround. Everything works for me if I change the definition of INCBIN_GLOBAL to:
#  define INCBIN_GLOBAL(NAME)    ".globl " INCBIN_MANGLE INCBIN_STRINGIZE(INCBIN_PREFIX) #NAME "\n"

I don't know much about assemblers so not sure if it's the right fix.

@rogual: thank you for this workaround, it just helped me to resolve a similar problem when switching from 64 bits compilation to 32 bits compilation with MingW (x86_64-8.1.0-release-win32-seh-rt_v6-rev0 vs i686-8.1.0-release-win32-dwarf-rt_v6-rev0). I've yet to confirm this workaround is still compatible with my 64 bits environment.
By the way, sometimes I'm considering switching back to my old-school bin2c approach...

I'm beginning to thing __APPLE__ case never worked. Can someone confirm if it works in any version of AppleClang without any of these changes. If not we may need to put the INCBIN_MANGLE on the front here.

Fixed


Make setting.Provider take a variadic parameters.

setting.Provider should take a variadic slice of keys, and return a map[string]Setting rather than a single setting. more info here

if a setting cannot be found then a nil map should be returned, and error stating which setting cannot be found.

setting.CachedProvider, setting.AggregateProvider, and setting.Filler will have to be refactored to take this change into account.

The fallback behaviour of setting.AggregateProvider should not change.

The lifetime of setting.ExpirableSetting should still be respected on setting.CachedProvider

Make sure all tests still pass and do not reduce coverage.

got setting.Provider and setting.Filler refactored; that includes 100% coverage;
The plan for today is do as much as I can from the rest; tomorrow's plan is to go over setting.AggregateProvider and get some help from @Connor-McGuinness


NLTK sentiment analysis returns only positive classifications

Python script
import nltk
import csv
FBdata = None
with open('Classified.csv' ,'rb') as f:
reader = csv.reader(f)
FBdata = map(tuple, reader)
with open('Classified2.csv' ,'rb') as f:
reader = csv.reader(f)
Negative = map(tuple, reader)
import random
random.shuffle(FBdata)
Negativedata = Negative
newFBdata = []  #sorting data
for row in FBdata:
statement = row[0]
sentiment = row[1]
words_filtered = [e.lower() for e in statement.split() if len(e) >= 3]
newFBdata.append((words_filtered, sentiment))
posts = newFBdata[:1000]
#Then we need to get the unique word list as the features for classification.
get the word lists of posts
def get_words_in_posts(posts):
all_words = []
for (words, sentiment) in posts:
all_words.extend(words)
return all_words
get the unique word from the word list
def get_word_features(wordlist):
wordlist = nltk.FreqDist(wordlist)
word_features = wordlist.keys()
return word_features
word_features = get_word_features(get_words_in_posts(posts))
word_features
#To create a classifier, we need to decide what features are relevant. To do that, we first need a feature extractor.
def extract_features(document):
document_words = set(document)
features = {}
if posts in word_features:
features['contains(%s)' % word] = True
return features
#Then, we can build up the training set and create the classifier:
training_set = nltk.classify.util.apply_features(extract_features, posts)
classifier = nltk.NaiveBayesClassifier.train(training_set)
#You may want to know how to define the ‘train’ method in NLTK here:
def train(labeled_featuresets, estimator=nltk.probability.ELEProbDist):
# Create the P(label) distribution
label_probdist = estimator(label_freqdist)
# Create the P(fval|label, fname) distribution
feature_probdist = {}
return NaiveBayesClassifier(label_probdist, feature_probdist)
#Now, we will classify the negativeposts and calculate the recall accuracy.
def classify_post(post):
return
classifier.classify(extract_features(post)) # nltk.word_tokenize(tweet)
total = accuracy = float(len(Negativedata))
for post in Negativedata[:100]:
if classify_post(post[0]) != post[1]:
accuracy -= 1
print('Total accuracy: %f%% (%d/20).' % (accuracy / total * 100, accuracy))
#test to see post sentiment, everyone gets positive value :(
print classifier.classify(extract_features(Negativedata[1]))
for x in range(0,100):
print classifier.classify(extract_features(Negativedata[x]))
classifier.show_most_informative_features()

@fievelk Would you have time to have a look at this?

Sure, I will check it

@josti92 I think I found the online tutorial you are using for your task; since I do not have your data, I cannot replicate your results. However, it seems that you only changed the datasets (FBdata and Negative), so the issue is probably there. You are supposed to train the classifier on both positive and negative labeled examples; testing on Negativedata instances is then supposed to give you a lot of negative classifications.
In this case, I think that your problem is not related to a NLTK bug, and it is therefore more suitable to be reported on the nltk-users forum.
I think you would also find it useful to check the first part of the NLTK Sentiment Analysis How To. Finally, we recently added several utility methods for sentiment analysis and preprocessing tasks in the sentiment/sentiment_analyzer.py and sentiment/util.py modules, so you can use them if you need more features for your classifier.

Thank you for your reply! I figured it out, I had to redo the cleaning of my data.
Best regards,
Øystein Løken
From: Pierpaolo Pantone<EMAIL_ADDRESS>Sent: 10. desember 2015 12:38
To: nltk/nltk<EMAIL_ADDRESS>Cc: josti92<EMAIL_ADDRESS>Subject: Re: [nltk] NLTK sentiment analysis returns only positive classifications (#1227)
@josti92 https://github.com/josti92  I think I found the online tutorial you are using for your task; since I do not have your data, I cannot replicate your results. However, it seems that you only changed the datasets (FBdata and Negative), so the issue is probably there. You are supposed to train the classifier on both positive and negative labeled examples; testing on Negativedata instances is then supposed to give you a lot of negative classifications.
In this case, I think that your problem is not related to a NLTK bug, and it is therefore more suitable to be reported on the nltk-users forum https://groups.google.com/forum/#!forum/nltk-users .
I think you would also find it useful to check the first part of the NLTK Sentiment Analysis How To http://www.nltk.org/howto/sentiment.html . Finally, we recently added several utility methods for sentiment analysis and preprocessing tasks in the sentiment/sentiment_analyzer.py and sentiment/util.py modules, so you can use them if you need more features for your classifier.
—
Reply to this email directly or view it on GitHub https://github.com/nltk/nltk/issues/1227#issuecomment-163585909 .  https://github.com/notifications/beacon/APdsEVGqBETGHTSYHQDLd1SPk9y8AcV6ks5pOVuegaJpZM4Gxygm.gif

Thanks, @fievelk.


Create a project before trying to decompile

If you're on the home screen after loading the editor and you select an example, it will fail to load. The error was that we were trying to decompile before a project was loaded and an exception was being thrown. It has been masked up until now because before the home screen we always had a project loaded in the editor.
Scenarios to test:

[ ] edit javascript with syntax errors, reload editor -> it should go back to JS
[ ] edit javascript correct code, reload editor -> goes back to JS
[ ] edit blocks correct code, reload editor -> goes back to blocks
[ ] edit blocks, invalid syntax (like a type error) - goes back to blocks

But does this mean when we open an example we will now decompile twice? Once for this newly created project, and the other when we actually load the project?

We don't decompile when you create a project. That being said, I am seeing it decompile twice for some reason; seems to be that we decompile when you reload the headers for a project if the new file is a blocks file. I'm investigating. The code is really weird.

@microsoftsam please take a look at the latest commit. I removed a check in app.tsx that I'm pretty sure does nothing as it was an async call in the middle of sync code. Not really sure what the original intention was.

@riknoll that bit of code is ancient so it's possible that its no longer needed however that code was added in order to make sure were were able to decompile the code at startup. This was back when some projects diverged and could no longer be converted back to blocks. We would want to open those projects in JS.
In that instance the check would first check that it can decompile the code, before opening the blocks, if we didn't do that we would end up opening the main.blocks file which is not a representation of actual project code (as that no longer decompiles).

This area is tricky, we should multiple scenarios like editing broken JavaScript, reopening and stuff. Let's do a full review tomorrow.

Scenarios to test:

edit javascript with syntax errors, reload editor -> it should go back to JS

testing

@pelikhan all those scenarios work fine.

The one scenario that might break is if the JS code somehow becomes invalid without any interaction for the user. For example, if we drop a language feature or API's change under the hood. I really don't think that's a scenario we need to handle, though, and even if we did I'm not sure going to the JS is the right response.


[Backport 0.5-nexus] Support table identifier contains dot with backticks

Description
backport 768 bug fix to 0.5-nexus

In this Spark version TableIdentifier only supports 2 parts so the catalog is implicitly taken from spark context.

Issues Resolved
https://github.com/opensearch-project/opensearch-spark/issues/767
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

CI failure unrelated


Update: Nvidia.GeForceNow v<IP_ADDRESS>

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.0 schema?

PS C:\Users\Esco> winget install -m M:\n\Nvidia\GeForceNow\<IP_ADDRESS>\
Found NVIDIA GeForce NOW [Nvidia.GeForceNow]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://download.nvidia.com/gfnpc/GeForceNOW-release.exe
  ██████████████████████████████   134 MB /  134 MB
Successfully verified installer hash
Starting package install...
Successfully installed

Microsoft Reviewers: Open in CodeFlow

How did it get passed? Mine was stuck at "You must have Nvidia GPU to install the software".


Slight improvements.

This PR provides slight improvement/shortening to a few places.
BitcoinPublicKey.swift

The idea is to use switch for data.first. Multiple comparings can be put in a single case.
data.first == nil equals data.isEmpty so both these cases can be put in default since we need to return false in case of being empty and in other unhandled cases as well.

Data+Hex.swift

The idea is to let initializers decide whether to return nil or not. Firstly we need to be able to parse UInt8 to ASCII letter. Then this ASCII letter can either be HEX digit or not.
Joining formatted strings requires less code.

Function.swift

String concatenation with comma-separator can be done more elegant.

@devsedo this is great! There is a few changes on this PR:
https://github.com/TrustWallet/trust-core/pull/29. @alejandro-isaza will take a look at this.
Thanks for contributing.

@vikmeup I was using my own git as a remote so I didn't notice that there was a commit to master before making PR :/

Codecov Report

Merging #39 into master will decrease coverage by 0.07%.
The diff coverage is 90%.

@@            Coverage Diff             @@
##           master      #39      +/-   ##
==========================================
- Coverage   83.75%   83.68%   -0.08%
==========================================
  Files          56       56
  Lines        2044     2029      -15
==========================================
- Hits         1712     1698      -14
+ Misses        332      331       -1

Impacted Files
Coverage Δ

Sources/Ethereum/Solidity/Function.swift
100% <100%> (ø)
:arrow_up:

Sources/Data+Hex.swift
66.66% <100%> (-7.25%)
:arrow_down:

Sources/Bitcoin/BitcoinPublicKey.swift
73.91% <80%> (+4.34%)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks!

@devsedo if you have some free time we always have some cool problem to work now. Feel free to ping me on telegram: @vikmeup


fisco-bcos-java-sdk 2.9.2版本，调用合约后，一切正常没有报错信息，但是疯狂的打印日志，详情看图

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
1.运行Webase导出的SDK后
2.调用合约成功
3.疯狂打印日志，相关类是EventSubscribeImp
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

OS: ubuntu 18.04
FISCO BCOS Version 2.9.2

Additional context
Add any other context about the problem here.

正常情况，普通info日志，在轮询等待事件返回


Revert "Fix EOL handling in web editor"

Reverts go-gitea/gitea#27141
close #28097

This behavior already effects end users.
If there is no quick fix (eg: in 1 or 2 days), let's revert it to old behavior. Then you have enough time to propose a new fix.

It's a trivial fix, I will provide soon. That's assuming the current behaviour can even be considered "broken", I think monaco is doing the sensible thing by defaulting to user's platform.

https://github.com/go-gitea/gitea/pull/28119

Will merge it in 1 day.

@silverwind the last call for the merge in 12h, if you still have objection, please show a real case to help understanding the "problem" you are worrying about.

I'm strongly against this because it removes editorconfig support.

But it broke many users' online editors. I was surprised when I edit a readme and only add one new line then all files were changed with no warning until I take a look at diff.

The only "necessary" revert is this line:
https://github.com/go-gitea/gitea/pull/27141/files#diff-898533f7342f43a8390c353ae398fa85578aaa93667b3ff99a5dd889c048e1c7L290
Ideally we should just convert line endings based on the new server pref.

Added server-side convertion in https://github.com/go-gitea/gitea/pull/28119/commits/e58dcc03437dca23ed8bc24c8b7434ac088e14be, this will always be correct, no matter what happens on the client side.


Performance Improvements, changed some design

Major changes -

The input file is used to eliminate duplicates. It is assumed input will be smaller than the file to append to, and hence to remove dupes, the input is read into a map. Output file is read line by line and any matches found to input map are removed. In the end, remaining elements are written to the output file.

Used struct map instead of bool map as they occupy lesser space.

Closing as breaks the desired flow


Fix potential panic for task in unknown state.

We added unknown state support for task in https://github.com/containerd/containerd/commit/101d4b78eb7fc0ef2be6dea1cfe2e5cf277df622. And task in unknown state will have empty fifos path.
However, we continue attach IO for task in unknown state https://github.com/containerd/containerd/blob/master/container.go#L386, which will potentially trigger a panic, because copyIO tries access nil stdout.
This PR:

Avoids attaching IO if task is in unknown state;
Fix io attaching helper to tolerant empty stdout fifo path.

Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

Codecov Report

Merging #3611 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3611      +/-   ##
==========================================
+ Coverage   42.38%   42.38%   +<.01%
==========================================
  Files         126      126
  Lines       13900    13901       +1
==========================================
+ Hits         5891     5892       +1
  Misses       7123     7123
  Partials      886      886

Flag
Coverage Δ

#linux
45.91% <100%> (ø)
:arrow_up:

#windows
37.2% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

cio/io_unix.go
74.41% <100%> (+0.3%)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM


Type on pagespeed recipe

In https://github.com/chef-cookbooks/chef_nginx/blob/master/recipes/pagespeed_module.rb#L29
should be package and not packages

Fixed. Thanks for noticing


Update README.md, add cyber to search engines

A decentralized alternative to Google, built with the help of IPFS, Tendermint and economic incentives

Hey, can this be merged?


Kmesh Logs Errors and Crashes After  Deploying 165 ServiceEntries

Motivation:
A limit of 165 ServiceEntries seems lower than expected. Our production use case requires support for a very large number of services, service entries and pods
Environment Details:
Kubernetes: 1.28
OS: Openeuler 23.03
Istio: 1.19
Kmesh version: release 0.5
CPU: 8
Memory: 16 Gib
Steps To Reproduce

Step 1: Make sure you have the below  service-entry.yaml file at the root of your repo. This config defines 1 endpoint per service entry.

apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: foo-service
  namespace: default
spec:
  hosts:
  - foo-service.somedomain # not used
  addresses:
  - <IP_ADDRESS>/24 # VIPs
  ports:
  - number: 27018
    name: foo-service
    protocol: HTTP
  location: MESH_INTERNAL
  resolution: STATIC
  endpoints: # 1 endpoint per service entry. Adjust depending on your test.
  - address: <IP_ADDRESS>

Step 2: Run the below command.

$ for i in $(seq 1 165); do sed "s/foo-service/foo-service-0-$(date +%s-%N)/g" service-entry.yaml | kubectl apply -f -; done

What was observed
After the number of ServiceEntries hit 165, Kmesh started logging the below error (see attachment) and crashed.
service-entry-error.txt'
Note: After trying this multiple times, sometimes the error message was different malloc(): invalid next size

cc @nlgwcy  @lec-bit

the same issue with https://github.com/kmesh-net/kmesh/issues/941
the maximum value of inner_map, 1300, so this issue occurred. When we create 163 virtualHosts in one routeConfigs, the array 163*sizeof(ptr) > 1300.
This problem can be avoided by manually adjusting the maximum value of inner_map.
kmesh.json

Maximum Endpoints and Services Supported by Kmesh
We changed the command to deploy every ServiceEntry on a separate port so that each RouteConfig would have one Virtual Host. Below are the 2 scenarios we tested.
Scenario 1: 1 endpoint (minimum possible) per ServiceEntry
Steps

Config file: The below config file will deploy endpoint per service entry.

apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: foo-service
  namespace: default
spec:
  hosts:
  - foo-service.somedomain # not used
  addresses:
  - <IP_ADDRESS>/24 # VIPs
  ports:
  - number: 27018
    name: foo-service
    protocol: HTTP
  location: MESH_INTERNAL
  resolution: STATIC
  endpoints: # 1 endpoint per service entry. Adjust depending on your test.
  - address: <IP_ADDRESS>

Command: Run the below command to deploy 1100 services, each with one endpoint

for i in $(seq 1 1100); do sed  "s/foo-service/foo-service-0-$(date +%s-%N)/g;s/27018/$i/g" service-entry-1.yaml | kubectl apply -f -; done

Results
The below errors are observed when slightly more than 1000 ServiceEntries are deployed.
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_943 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_48 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_117 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_138 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_383 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_603 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_739 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_786 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_79 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_354 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_591 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_675 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_729 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2
time="2024-11-08T18:41:39Z" level=error msg="listener <IP_ADDRESS>_816 NONE flush failed: ListenerUpdate deserial_update_elem failed" subsys=cache/v2

Why is this an issue ?
Our use case needs to support higher number of endpoints, and this is far lower than the theoretical 100,000 endpoints and 5000 services.
Scenario 2: 150 endpoints (maximum possible) per ServiceEntry
Steps

Config file: Run the same test as before, but increase the number of addresses per endpoint to 150 (last line in the config)

Command: Run the below command to deploy 600 services, each with 150 endpoints

for i in $(seq  1 600); do sed  "s/foo-service/foo-service-0-$(date +%s-%N)/g;s/27018/$i/g" service-entry-1.yaml | kubectl apply -f -; done

Results
The below errors are observed at approx 500 services (total 75000 endpoints)
error-logs-max-pods.txt
Why is this an issue ?
Our use case needs to support highter number of endpoints, and 75000 endpoints is lower than theoretical 100,000 maximum endpoints and 5000 maximum services.


[wallet] Handle ChallengeCleared event from Nitro-Protocol's ForceMove contract

Some cosmetic changes got included here.

Is this in accordance with the linter?

Is this in accordance with the linter?

The lint check passed so...yeah?

Could we split up the cosmetic changes into a separate PR?

I've made a new PR which consolidates linting: #139


deno version matrix on CI

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Fix SearchResult struct so it is compatible with cross-cluster search results

The Clusters member of the SearchResult struct is currently an array and I don't believe it should be.  This causes the following error when results of a cross-cluster search are unmarshalled:
cannot unmarshal object into Go struct field SearchResult._clusters of type []*elastic.SearchResultCluster"

The Elasticsearch documentation shows that the _clusters element is indeed not an array:
https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cross-cluster-search.html#ccs-search-remote-cluster
This PR resolves this issue.

Already fixed. See https://github.com/olivere/elastic/blob/release-branch.v7/search.go#L648.


Add DNS records for Argo Rollouts

Brad to create a DNS entry support ticket to route argorollouts.ortelius.io to our Azure Front Door instance
CNAME Entry needs to go to argorollouts.ortelius.io = ortelius.z01.azurefd.net
TXT entry _dnsauth.argorollouts.ortelius.io = hlr008b0trb78003s2xpvhclhwf5nfft
old example https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22914

Request made to linux foundation: https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23802

Hello Brad McCoy,
Johnson Nguyen changed the status of your request IT-23802 to Resolved.
Hello Brad McCoy,
Ticket Number: IT-23802
Your request has been resolved as Done.

Added routes to azure front door, now last test is to deploy argorollouts and then test that it works then i will close the ticket

tested and working closing


Wrap empty enums with a single member as constants

For example:
enum { Type = 3 };
now becomes:
enum Type { Type = 3};
Instead we'd better have:
public const int Type = 3;

:+1:

When doing this, we'll also need to cover with tests the case that the enum is in the global namespace, inside a namespace, as well as inside another type (class).


Djboss.modules.system.pkgs question

Why do we have to add the "Djboss.modules.system.pkgs" params to find the 3 jars when using Jboss ?
Why it is not necessary in Tomcat ?
Is there any difference between Tomcat and Jboss ?
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=com.navercorp.pinpoint.bootstrap,
com.navercorp.pinpoint.common,com.navercorp.pinpoint.exception"

Jboss and Tomcat are different implementation.
We do not know about Jboss internal implementation.
Ask the jboss community.


update auth.php for Hebrew

Thanks, but can you help to translate others files ?

Yeah. This was my first PR ever, I didn't wanna break anything ;p


#2643: Standardize includes of toolbar layout

Description (required)
Works on #2643
Include toolbar.xml in the same simple way everywhere - there is no need to add the id, width, height etc. in both the caller and the template - it should just be once in the template. There are a couple of unused files which I haven't updated but these should be deleted by #2641 and I don't want to create merge conflicts.
Tests performed (required)
Tested 2.10.1-debug-refactor-toolbar~9d15e177e
Beta Commons upload

Codecov Report

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

@@          Coverage Diff           @@
##           master   #2646   +/-   ##
======================================
  Coverage    2.77%   2.77%
======================================
  Files         259     259
  Lines       12373   12373
  Branches     1117    1117
======================================
  Hits          343     343
  Misses      12003   12003
  Partials       27      27

Continue to review full report at Codecov.

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

Thanks for improving the code quality @domdomegg


Improve Exchange Rates

Improve exchange rate handling to be more generic and self-contained. This work begins #1437 by adding structs which will implement the CurrencyValue and CurrencyDefinition interfaces. This uses those same structs to perform the currency conversion behavior and validate many currency usages.
Future work:

Move exchange rate handler out of (multiple) wallet implementations and into the CurrencyDictionary. Replace exchange rate interface in wallets with native currency rates as it relates to a set of reserve currencies (which will allow us to support beyond BTC as a reserve currency, if BTC is unavailable at some point later).

Coverage increased (+0.2%) to 35.077% when pulling c2c8e93bc5d4596c7e97ff5e9a75e3da38749ca5 on exchange-rate-improvements into 373e3a75f8def4eef711cd0eb53bb6b2cbdd7767 on master.


More Advanced Logging & Error Handling

This update adds more advanced logging & error handling capabilities to both the Engine and the Scaler. The Scaler modules now bubble up their errors to the Scaler function, which in turn properly forms and throws a PowerShell error. Added ERRORDATA output which can be captured by Application Insights for monitoring/alerting. Adjusted the Scaler to only dequeue a message once, so a failure won't trigger the Scaler to run 4 additional times. Finally, I cleaned up a few minors spelling/grammatical items, as well as set some nice-to-have defaults in the ARM Template.

Hey @NillsF, I was originally using the "outer" scope, but that caused some issues in how some of the dependencies worked, and the scoping of certain resources. In the future, I foresee breaking this template up into multiple smaller Linked templates to make it easier to update. For now, I believe it's better to leave the scope to "inner", but I'm happy to revisit this later and attempt using the "outer" scope once again.

Hey @NillsF, really good catch! I added some additional validations to the Scaler to make sure that setData/saveData are not Null or Empty. Much appreciated sir.


On acquiring data, a null entry causes the key to not instantiate.

I generated a testing table while learning the API for AirTable.
Essentially, this looks as below, where NULL is the absence of any data at all, rather than the textual representation:

Name
Ident
ColA

A
1
Item 1

Small
2
Item 2

Thing
3
Item 3

NULL
4
Item 4

The code is
from pyairtable import Api, Base, Table
import json
table=Table('patextXXXXXX','appXXXXXX','tblXXXXXX')
for record in table.iterate(page_size=1, max_records=1000,fields=['Name']):
  print (json.dumps(record))
While running a test to filter for "Name", the following output occurs:
[{"id": "recXXXXXXXXXXXXX", "createdTime": "2023-02-19T00:55:05.000Z", "fields": {"Name": "Thing"}}]
[{"id": "recXXXXXXXXXXXXX", "createdTime": "2023-02-19T01:01:15.000Z", "fields": {}}]
[{"id": "recXXXXXXXXXXXXX", "createdTime": "2023-02-19T00:55:05.000Z", "fields": {"Name": "A"}}]
[{"id": "recXXXXXXXXXXXXX", "createdTime": "2023-02-19T00:55:05.000Z", "fields": {"Name": "Small"}}]
Rather than generate a dict of {"Name": ""}, it incorrectly ignores that there is a Name key available with the contents of NULL, returning an empty dictionary {} instead.
As a request for a non-existent field results in an HTTP 422 error, I'd assert that a successful query for a known field (that returns nothing) should autovivify the key in the returned dictionary with an empty value.

Is it reproduced when using an actual filter rather than specifying the fields in the kargs?

What's the benefit of changing this behavior? A change of this sort would create a subtle inconsistency, because any time a developer doesn't pass fields= to the API, there will be no way for pyairtable to guess and populate null values.
So this would work fine...
>>> records = table.all(fields=["Name"])
>>> names = [record["Name"] for record in records]

...but the following would raise KeyError:
>>> records = table.all()
>>> names = [record["Name"] for record in records]

It might be safer for developers to have to always code as if every key is potentially missing, rather than having to maintain context about whether fields= was passed to the API endpoint that retrieved whatever data they're using.

I don't think we'll modify the behavior of the library here, since it would be a breaking change for existing code.


Caching pygments

Would it be a good idea to cache multiple runs of pygmentize?
You could take the checksum of the input code, see if there's a file with that name and return it. If not: run pygmentize and write a cache file.
This would make livereload lightning fast again for those who use pygments.

Is this something that would be accepted (I'll happily submit a patch)?
Can I dump the cache files into CacheDir? Any specific naming pattern to follow?

That is a splendid idea.
A PR would be welcome.
CacheDir or a subdir of that would be good place, yes. I would try to find a pattern in the 1 place we cache today. We should also try to generalize the cache logic where it make sense.

It MAY be an idea to do this on the shortcode level, and maybe turn it on/off per shortcode / all shortcodes.
The key could be calculated from the param key/vals + the inner content (if applicable).

The key could be calculated from the param key/vals + the inner content (if applicable).

Plus the shortcode definition and any other shortcodes it might call. This might be a can of worms, if you don't mind I'd like to start with the low-hanging fruit of just making pygments fast.
Most shortcodes are simple and fast anyway, so there won't be much (noticeable) gain.


Problem when runing mayavi/test_drawline.py

Hi friends,
I want to run mayavi/test_drawline.py on my remote machine via Xvnc. This is no error about OpenGL like we may meet if we use ssh-X. But there is an error said:
Xlib:  extension "XInputExtension" missing on display ":1". Segmentation fault (core dumped)
I am not familiar with the X-server series. So does anyone know how to solve it or meet the same problem?

You cannot use mayavi visualizations if you are remotely connected to your machine.
Instead of save the visualization on your machine as jpg and transfer is to your local machine with scp.
Replace this line:
l = plot3d(x, y, z, numpy.sin(mu), tube_radius=0.025, colormap='Spectral')
with:
fig = mlab.figure(figure=None, bgcolor=(0, 0, 0), fgcolor=None, engine=None, size=(1600, 1000))
mlab.plot3d(x, y, z, numpy.sin(mu), tube_radius=0.025, colormap='Spectral', figure=fig)
mlab.savefig('draw_line.jpg', figure=fig)

Thanks a lot, this provides a good solution to see what happens to point cloud on my local machine.

from mayavi import mlab
causes
sunrgbd_data.py: cannot connect to X server


dmc.Collapse - required parameter in does not work

When I try to use the undocumented Collapse component, I get the following error:
    dmc.Collapse(in=True, children=[dmc.Button()])
                 ^^
SyntaxError: invalid syntax

Same issue with Fieldset and NumberFormatter (undocumented props).

I also saw that the following components are missing: Tree, SemiCircleProgress, Dialog, ColorSwatch,

Hi @MichaelODeli
Thanks for reporting - I could replicate this issue with the in prop.
Are you interested in doing any pull requests either in the dmc-doc repo or here?

@AnnMarieW Yes, I will try to add undocumented components to dmc-docs.

The same error with Fieldset components - unexpected argument
TypeError: The `dash_mantine_components.Fieldset` component (version 0.14.4) received an unexpected keyword argument: `disabled`

But in dmc-docs with configurator.add_switch("disabled", False) param - it works fine

That's odd - but in the upstream docs, disabled is not a valid prop for Fieldset
https://mantine.dev/core/fieldset/?t=props

I think I see how to fix this.  It would be helpful if you could make a draft PR for the Fieldset component, then when the fix is done, the docs will be ready to go.  :-)

@AnnMarieW https://github.com/snehilvj/dmc-docs/pull/64

FWIW there is a way to use props masked by Python keywords, or that in some other way are invalid as kwargs:
dmc.Collapse(children=[dmc.Button()], **{"in": True})

Which is what you have to do for example to use the data-* and aria-* wildcard props in dash.html because of the hyphens.
But I agree, this pattern is tricky, ugly, and non-Pythonic so better to change it where we can.


Add A Creative Footer Section

Description
Is your feature request related to a problem? Please describe.
It's not a problem but to have a good footer makes a website look cool and easy for a user to get the details about the social media handles and many more important part from the bottom also.
Describe the solution you'd like
I have a quite good solution for your website to add a attractive and informative footer section which will consist of all the important information about the website and all the official social media handles.
Describe alternatives you've considered
It can be a better option for the user that uses the website to get information about the website form the footer section also.
I can add all the informative details in this section of your footer
Additional Information
Context

Its a very basic footer that has been uesd, but I can update it to make it appears attractive and creative
So, please assign me this issue under GSSOC'23.

I am interested to work on this issue under GSSoC 2023 as a contributor

Please assign this project to me. I will fix the issue.

pl do a fresh fetch footer was updated.


Passthrouge protoc options via --protoc-opts

Usage:
$CMD --protoc-opts --go_out=:.

I don't think this is necessary given the several flag options that protoc-all supports.
Feel free to reopen if you'd like to discuss further


hugo: 0.122.0 -> 0.123.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/gohugoio/hugo/releases.
meta.description for hugo is: A fast and modern static website engine
meta.homepage for hugo is: https://gohugo.io
meta.changelog for hugo is: https://github.com/gohugoio/hugo/releases/tag/v0.123.0
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.123.0 with grep in /nix/store/zr920k4i896sgdyki0j93aggjhziyshs-hugo-0.123.0
found 0.123.0 in filename of file in /nix/store/zr920k4i896sgdyki0j93aggjhziyshs-hugo-0.123.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
hugo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zr920k4i896sgdyki0j93aggjhziyshs-hugo-0.123.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/e00e1aba2a7016e8e85736144b7529454440c8c4#hugo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zr920k4i896sgdyki0j93aggjhziyshs-hugo-0.123.0
ls -la /nix/store/zr920k4i896sgdyki0j93aggjhziyshs-hugo-0.123.0/bin

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

1 package built:

hugo

Maintainer pings
cc @schneefux @Br1ght0ne @Frostman for testing.

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

1 package built:

hugo


float snippet hover on the wrong when opening the CocList(plugin coc.nvim)

Yes, the plugin is probably splitting the window first, then changing the buffer. We need to call update() on BufEnter autocmd.

It should work now, please re-open if it persists.

same problem again, when using 'q/' or 'q:' to open a Command-line windows


Add does_not_match field to conversion rules

This allows you to exclude certain metrics from a conversion rule by rejecting the match if the result's tag values match their do_not_match field.
Golang does not support negative lookahead in its regular expression (in order to keep them more regular, as well as to ensure O(n) matching) and therefore it can be very difficult to intentionally exclude certain metrics from being matched.
It used to be that metrics were just matched in order, so that you could exclude from one rule by matching with another. However, because of danger of this introducing subtle bugs when one rule was changed, the behavior was changed so that order must not matter, and all metrics should match at most one rule.
This change makes it possible to easily exclude metrics from a particular rule, while keeping it orthogonal to all others- so that if another rule is removed or changed, it won't suddenly start capturing everything that the old one had.
TODO: check this when reversing metrics too (this is less likely to be useful, but for completeness it's not a bad idea)

I like this feature!

@cchandler

:+1:


Fixed parsing of docker image names issue - #3820

fixes #3820
There are a few assumptions about docker image names in this fix:

Registries must contain with . or : i.e. localhost:5000, site.com or with both: <IP_ADDRESS>:1234 but not server or localhost since theres no way I could think of to differentiate between a registry and an image name. in the example server/image:tag its unknown if server is a registry or a subrepo
Image names in the system can be anything after registry i.e. aaaa/bbbb/cccc/user/example would be the image name from localhost:5000/aaaa/bbbb/cccc/user/example

@abonas @simon3z

cc @oschreib (wrt missing registries)

@Fryguy @chessbyte build looks stuck, could you please rekick it?

@simon3z, @abonas, based on comments, this looks good to go.  Is that right?

@blomquisg LGTM :+1: , we'll have to separate the digest from the tag (but not in this pr).


Configuring  a Timer Restart

Whenever an actor restarts or an application containing an Actor restarts, the reminder associated with an actor automatically restarts.
Is there anyway to configure this?
If I do not want the remainder to restart when a service restarts, how to configure this.
Can someone pls confirm whether this feature exists with Remainders or not.

It might be that the Actor Timer would better suit your needs

All timers are stopped when the actor is deactivated as part of garbage collection. No timer callbacks are invoked after that. Also, the Dapr actor runtime does not retain any information about the timers that were running before deactivation. It is up to the actor to register any timers that it needs when it is reactivated in the future.

Read about it here

@olitomlinson Any idea on the thread https://github.com/dapr/dapr/issues/5517


Win 10 - the layout of VSCode panel is out of order after Windows was upgraded to version 1703

VSCode Version: Code 1.12.1 (f6868fce3eeb16663840eb82123369dec6077a9b, 2017-05-04T21:26:50.689Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author
Version

npm-intellisense
christian-kohler
1.3.0

githistory
donjayamanne
0.2.0

jquerysnippets
donjayamanne
0.0.1

vscode-html-css
ecmel
0.1.2

auto-close-tag
formulahendry
0.3.12

auto-rename-tag
formulahendry
0.0.11

code-runner
formulahendry
0.6.16

godot-tools
geequlim
0.2.5

beautify
HookyQR
1.0.2

path-autocomplete
ionutvmi
1.4.1

vscode-colorize
kamikillerto
0.5.0

Go
lukehoban
0.6.61

editorconfiggenerator
nepaul
0.2.1

syncing
nonoroazoro
1.3.7

vscode-versionlens
pflannery
0.14.1

vscode-icons
robertohuertasm
7.6.0

text-marker
ryu1kn
0.3.0

guides
spywhere
0.7.0

JavaScriptSnippets
xabikos
1.4.0

Material-theme
zhuangtongfa
2.6.3

Steps to Reproduce:

Translation of the issue's title: the layout of VSCode panel is out of order after Windows is upgraded to version 1703

happens to me too, like this……
after sacling the window sevaral times :

winpty => @Tyriar

Duplicate https://github.com/Microsoft/vscode/issues/19665
The exception seems to happen very infrequently (been reported once before), when you get the Windows issue fixed above the problem should be resolved for you.

我和我的同事都遇到同样的问题，这个问题是在win10更新1703之后出现的，不是vscode更新出现的


warn when emmet is installed

It creates crazy performance issues in dart files. Remove the warning once emmet fix is available.
@johnmccutchan @sethladd

fixed by https://github.com/dart-atom/dartlang/pull/217


Ability to create submenus

Hi,
I am new to Hugo.
I have been reading on how to create submenus in hugo.
I came across this link in my research https://codingnconcepts.com/hugo/nested-menu-hugo/
Unfortunately I have not been able to get a result.
Does this theme support sub-menus and if not could I request this feature?
Many thanks,

Hi @Bas-Man We'll discuss and get back to you. I'm pretty sure it's not possible at the moment.

Any update on this? I'm running into the same issue.

I've been trying to follow the same instructions without success.  Is there any update on this feature?

Before I dive in and have another go at this, has anyone else managed to get a sub-menu working?

I also tried to implement sub menus without success.
Any chance that this might work in the future?

I'll second having this feature would be very helpful.
As a first step, just having two levels menus would enough for many.


connection not working for postgres backend

unable to connect to database:dial tcp <IP_ADDRESS>:5432: connect: connection refused

connection refused comes from your operating system, this means no open port on <IP_ADDRESS>:5432, please check your configuration

You struggle with the basics of container networking, inside the go-ipam container there is no one listening on localhost:5432. Instead, depending on your local docker network configuration, it will be reachable at <IP_ADDRESS>:5432.
Please read https://docs.docker.com/network/ and try with these insights.

if this is the case, let's say that I use docker run -it --rm ghcr.io/metal-stack/go-ipam postgres f for use file backend
and I only see
{"time":"2024-03-14T06:21:06.205190227Z","level":"INFO","msg":"starting go-ipam","version":{},"backend":"file"}
{"time":"2024-03-14T06:21:06.206083937Z","level":"INFO","msg":"serving metrics","at":"localhost:2112/metrics"}
and when run the docker run -it --rm --entrypoint /cli ghcr.io/metal-stack/go-ipam ip release the error is there for 9090 port, I even try to update
unavailable: dial tcp <IP_ADDRESS>:9090: connect: connection refused

Created a PR which explains the usage with docker compose, will be merged next week, but you can have a look and give feedback
https://github.com/metal-stack/go-ipam/pull/139

Yes, the docker compose is working fine with all the testings!!!!! thank you!!!!!!

Thank you!


Unrecognized type 'URuntimeBlueprintMeshBuilder'

When compiling in the editor, UnrealHeaderTool:
.../Plugins/RuntimeMeshComponent/Source/RuntimeMeshComponent/Public/RuntimeMesh.h(345)  : Error: Unrecognized type 'URuntimeBlueprintMeshBuilder' - type must be a UCLASS, USTRUCT or UENUM
this makes no sense, because URuntimeBlueprintMeshBuilder is a UCLASS and the header file is included
(Unreal Engine v4.20.1)
Visual Studio compiles it without errors

Closing as this is for an outdated version of the plugin that's no longer supported.
If you experience this or any other issues in the current version, feel free to report again!
Thanks!


Remove some debug spans

The issue is now isolated specifically to the async task that's being spawned.
I still haven't quite figured out why the trace_span in spawn_with_handle isn't enough to stop using the caller span as the parent, but a debug_span here is, so I've left in the one span for now.

bors r+


Perplexity Calculation

Thank you for providing the code base!
I am wondering if the perplexity is missing an np.exp, or is this integrated somewhere before and I am missing it maybe?

Dear Veronika, I think np.exp is just a monotonic function and it does not change the ordering of instances. You will get the same results with or without exponentiation, that is why it might be absent from the code.

Thanks! Yes, that's true. I just wanted to make sure I understand what's done in the code so that I don't miss it in case it's hidden somewhere.

If you have any other questions, we would be happy to help.


Remove typehint to allow all types of variables

Fixes #17

In #29 I made a fix which excludes the one case this happens.


Error while adding azure CLI extension 'az extension add --name azure-devops'

I have installed Azure CLI but facing issue while adding azure devops extension.
Unable to get extension index.
Please ensure you have network connection. Error detail: HTTPSConnectionPool(host='aka.ms', port=443): Max retries exceeded with url: /azure-cli-extension-index-v1 (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x060F1430>: Failed to establish a new connection: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond',))
Please provide solution.
Thank you.

any updates on this issue ?

The issue was related to proxy, either we can set proxy variable as permanent solution or use set proxy command.


Discover MQP brokers

User story
As a data user, I want to search on a portal so that I can discover the available data sources to which I can subscribe.
Acceptance criteria

[ ] data user able to access a list of all the available brokers
[ ] data user able to search for a specific broker by "publisher"

Definition of done

[ ] unit/functional tests added/updated
[ ] documentation updated
[ ] live demonstration provided

WIS 2.0 catalogue to have discovery metadata based on MQP services
each wis2node should create a discovery metadata document for its MQP service


Uncaught Error: The notify function has been called synchronously!

In browser's console log:
6game.elm:1315 Uncaught Error: The notify function has been called synchronously!
This can lead to frames being dropped.
Definitely report this to <https://github.com/elm-lang/Elm/issues>```

The translated javascript has this line referenced
```while (xs.ctor !== '[]' && n > 0)```

I added a new action (in SimpleApp terms) to the update function:

     Action.DrawCardsToHand ->
          let (deck, player) = Domain.drawCardsToHand deck player
          in { model | player = player, deck = deck }

The problem seems to be that the arguments  ```deck``` and ```player``` in the call ```Domain.drawCardsToHand deck player``` should actually be referencing ```model.player``` and ```model.deck```. It seems that creating having a let with the needed variable (```deck``` and ```player```) are enough to satisfy the compiler. They are not defined globally elsewhere; though similar let constructions are defined on other action branches (case of ...).

Yet another example of #873, which is common enough that I have that issue number memorized.
Thanks for reporting. You've correctly diagnosed the circular nature of the code. For now... just don't do that, m'kay?

Ah, that's good!

Would you mind closing the issue?


Manage imported accounts

You can import accounts but you cannot remove them

@crmn111, this feature already exists in the latest version. Thanks!


I2C slave mode support

What would be needed to support i2c slave mode? It seems like there is a lot of overlap with i2c master, but I am not sure what the structure would look like.
Register summary is in section 36.7 of the datasheet

I think the main reason we don't have it yet is mainly a lack of standardization for the interface in the embedded-hal crate (last I checked). But that's not exactly a good reason why we can't or shouldn't support it.

Now that it looks like embedded-hal-bus is going to be split off, I wonder if it will cover it better. The details about what HAL 1.0 are going to look like are unfortunately iffy at best it seems.
Err... I'm pretty new to the project, could you point me in the right direction for where to start adding something like this?

If I were to do it, I would create a slave module under the existing i2c directory https://github.com/atsamd-rs/atsamd/tree/master/hal/src/sercom/i2c

We also have a chatroom where we can discuss if you have more questions https://matrix.to/#/#atsamd-rs:matrix.org


[Bug]: Error: Could not find Chrome (ver. 127.0.6533.88).

Minimal, reproducible example
import puppeteer from 'puppeteer';
const browser = await puppeteer.launch({ headless: "true"});
const page = await browser.newPage();
page.setDefaultNavigationTimeout(0);
await page.setContent(htmlContent, { waitUntil: 'domcontentloaded' , timeout: 0 });
 const pdfBuffer = await page.pdf({
                format: 'A4',
                printBackground: true,
                margin: {
                  top: '.6in',
                  bottom: '.6in',
                  left: '.6in',
                  right: '.6in',
                },
                border: {
                  right: ".6in",
                  left: ".6in",
                  top: ".6in",
                  bottom: ".6in",
                },
                landscape: false,
              });
await page.setViewport({ width: 800, height: 600 });
await browser.close();

Background
Above code is working fine in  locally but getting issue in aws hosted server.
Expectation
In local i can generate pdf but in hosted server  i am getting below error
Reality
Error: Could not find Chrome (ver. 127.0.6533.88). This can occur if either

you did not perform an installation before running the script (e.g. npx puppeteer browsers install chrome) or
your cache path is incorrectly configured (which is: C:\Windows\system32\config\systemprofile.cache\puppeteer).

Puppeteer configuration file (if used)
No response
Puppeteer version
"puppeteer": "^22.15.0",
Node version
v20.10.0
Package manager
npm
Package manager version
10.2.3
Operating system
Windows

I am unable to reproduce.
Installing version 22.15.0 installs chrome 127.0.6533.88 correctly and run my script.
Are you skipping post-install as that is where we download the browser.
Alternatively you did you run npx puppeteer browsers install chrome as suggested in the output?

Yes i did run npx puppeteer browsers install chrome.

Did any error occur while that command was running? Did you get output that the browser was downloaded successfully?

i did not get any error. it is downloaded successfully

yup its launching the chrome

Hmm so it's issue with the set-up on AWS, you can check Running Puppeteer in the cloud, but in general it's possible that Chrome dependencies are not installed and/or other error are happening.
You can check by adding dumpio:true to the launch params, that will show any errors or info that may cause issues.

thank you for info, i could able to figure out the issue.


EventHub component delivers out of order messages (pubsub, binding)

Expected Behavior

When using Event Hubs as a pubsub or binding, messages should be delivered in the order they were posted (assume PartitionKey is set when publishing/posting to ensure ordering across partitions.)
Actual Behavior
In the pubsub case, the sidecar delivers new events before the subscriber has completed handling the last one. This causes major problems when trying to ensure order sensitive work is executed correctly (e.g. starting a workflow to process subsequent events.)
Steps to Reproduce the Problem

We're publishing to our topic like this (dotnet sdk):

await dapr.PublishEventAsync(
        WellKnownPubSubNames.Percept,
        WellKnownPubSubTopics.RecordingSessionFileEventV1,
        data,
        new Dictionary<string, string>
        {
            { "partitionKey", data.DeviceId }
        }
    );

and receiving like this:
pubsub.MapPost(
    WellKnownPubSubTopics.RecordingSessionFileEventV1,
    [Topic(WellKnownPubSubNames.Percept, WellKnownPubSubTopics.RecordingSessionFileEventV1)]
    async (
        [FromServices] ILogger<Program> logger,
        [FromServices] IRecordingSessionRepository recordingSessionRepository,
        HttpContext HttpContext,
        [FromBody] RecordingSessionFileEventV1 data
    ) => {
        try {
            var messageId = HttpContext.Request.Headers["Message-Id"];

            logger.LogInformation("Start message id: {messageId}", messageId!);

            await Task.Delay(500);

            logger.LogInformation("Stop message id: {messageId}", messageId!);

            return Results.Ok();
        }
        catch (Exception ex) {
            logger.LogError(ex);
            return Results.Problem(ex.Message);
        }
    }
);

The problem is clear when watching the logs: instead of seeing a constant start/stop/start/stop alternating sequence of log events, we're seeing start/stop/start/start/stop/stop interleaving. The sidecar should not be sending another event until the current one has completed processing, i.e. it receives a http 200 (in this case.)
The same issue likely occurs for the binding since the common code is the problem (according to @yaron2):

It appears our implementation is using goroutines for each message, which would cause out-of-order delivery: https://github.com/dapr/components-contrib/blob/main/common/component/azure/eventhubs/eventhubs.go#L293. We do have a concurrency mechanism for components, it just hasn't been applied to Event Hubs. This should be an easy change - can you please open an issue in components-contrib for this? I'll add it to the v1.15 milestone

Release Note

PubSub and Binding components using ordered delivery (with a partitionkey) would interleave event deliveries to a subscriber. Now the sidecar will wait until the handler returns before sending the next event.

RELEASE NOTE:

Triaged

Imo this is a P0 as it fundamentally breaks the underlying FIFO ordering that one would expect when processing each message individually via Dapr PubSub

Imo this is a P0 as it fundamentally breaks the underlying FIFO ordering that one would expect from EventHubs when processing each message individually via Dapr PubSub

Agree

Imo this is a P0 as it fundamentally breaks the underlying FIFO ordering that one would expect from EventHubs when processing each message individually via Dapr PubSub

And also the EH binding! They share the same code AFAICT.

Hey @olitomlinson @yaron2 - After a crash course in golang, I don't think the issue is at https://github.com/dapr/components-contrib/blob/main/common/component/azure/eventhubs/eventhubs.go?rgh-link-date=2024-10-16T14%3A11%3A56Z#L293 as this starts a goroutine for the partition which seems perfectly fine. Partitions should be handled in parallel. However, looking at
https://github.com/dapr/components-contrib/blob/4ca04dbb61c553047727ec709f37a2b4b9832159/common/component/azure/eventhubs/eventhubs.go#L398 I can see that messages within the partition are dispatched as goroutines, where I would expect here they should be blocking calls to ensure correct dispatch ordering, no?

Hey @olitomlinson @yaron2 - After a crash course in golang, I don't think the issue is at https://github.com/dapr/components-contrib/blob/main/common/component/azure/eventhubs/eventhubs.go?rgh-link-date=2024-10-16T14%3A11%3A56Z#L293 as this starts a goroutine for the partition which seems perfectly fine. Partitions should be handled in parallel. However, looking at
https://github.com/dapr/components-contrib/blob/4ca04dbb61c553047727ec709f37a2b4b9832159/common/component/azure/eventhubs/eventhubs.go#L398
I can see that messages within the partition are dispatched as goroutines, where I would expect here they should be blocking calls to ensure correct dispatch ordering, no?

That seems correct, yes

So removing the go prefix should be enough? I should probably rename handleAsync to something like handleEvents -- it's interesting to me how the method being called asynchronously and named as such has no bearing on the method's body. Quite simple!
If this really is a one line fix, would you expect unit tests? They would be entirely beyond me at this point in my golang career :D

Hey @olitomlinson @yaron2 - After a crash course in golang, I don't think the issue is at https://github.com/dapr/components-contrib/blob/main/common/component/azure/eventhubs/eventhubs.go?rgh-link-date=2024-10-16T14%3A11%3A56Z#L293 as this starts a goroutine for the partition which seems perfectly fine. Partitions should be handled in parallel. However, looking at
https://github.com/dapr/components-contrib/blob/4ca04dbb61c553047727ec709f37a2b4b9832159/common/component/azure/eventhubs/eventhubs.go#L398
I can see that messages within the partition are dispatched as goroutines, where I would expect here they should be blocking calls to ensure correct dispatch ordering, no?

This is exactly what I said in Discord :)

So removing the go prefix should be enough? I should probably rename handleAsync to something like handleEvents -- it's interesting to me how the method being called asynchronously and named as such has no bearing on the method's body. Quite simple!
If this really is a one line fix, would you expect unit tests? They would be entirely beyond me at this point in my golang career :D
Also, as a P0 bug - would this warrant making it into 1.14.5 ?

It could be as simple as a one-liner, but it needs thorough testing to makes sure that the checkpointing is done correctly after each message completes.
My one reservation on fixing this quickly is that there may be users out there in the wild with high-throughput use-cases that depend on the throughput that is currently afforded by this incorrect implementation. Until a fix is in place, its hard to quantify what that performance degradation maybe by checkpointing on each message.
The real solution here is to use Bulk Subscriptions for high throughput use-cases, but this is not Stable yet.
Idea : This could be fixed but the fix is put behind an opt-in feature-flag on the metadata so it doesn't impact people with existing expectations (from the incorrect implementation).
Then, when bulk subscriptions does graduate to Stable, the feature flag could be removed and replaced with an opt-in feature flag that reverts the behavior back to the broken implementation. And users with high-throughput expectations are encouraged to migrate to Bulk Subscriptions (or opt back in to the previous broken implementation, for a window of supported releases)

Hmm, I'm not going to be competent enough in the language to fix this in the window that my project requires. If you could collaborate with me, then I may learn enough to address my other feature requests for event hubs myself. How busy are you, lol

Good to see this was completed!  In order processing of ordered event streams is a basic requirement.  Thanks.
FYI After a deep dive into the Azure IoT realm last fall and winter consisting of lots of reading, I'd like to remind you that a very, very common use for the Azure Event Hub is the Azure IoT Hub which comes with an Event Hub attached!  Therefore, by fixing Event Hub bugs and adding new features you also improve the positioning of Dapr to service the IoT community, which has had consistent strong growth for a number of years now and is expected to continue.  This fix will really help!


[Flaky test] The scalability test TestScalability/WorkloadClasses/large  flakes

What happened:
The TestScalability/WorkloadClasses/large  failed on a non-related branch: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_kueue/2659/pull-kueue-test-scheduling-perf-main/1815372699975815168
What you expected to happen:
No random failures.

/cc @trasc @mbobrovskyi


.xe works but don´t on Comand Line

I use the exe file and I don't have problems, but when I use the command I have this error, I want to use the command, always on top, I'm pretty new on this

Use v1.10.

Thank, you, that was the problem, and that I need to use the command before open the program, there's a way to put commands when the program is already open?

No, you can't change the parameters afterwards.
Note that you can just create some file.bat in the scrcpy folder containing your command:
scrcpy --always-on-top

Then you can just double-click on it.

No, you can't change the parameters afterwards.
Note that you can just create some file.bat in the scrcpy folder containing your command:
scrcpy --always-on-top

Then you can just double-click on it.

Thanks you, I cant put 2 comands at same tame time? Something like that:
--always-on-top
--turn-screen-off
And if is possible how I put this on command line?

scrcpy --always-on-top --turn-screen-off
In one line

scrcpy --always-on-top --turn-screen-off
In one line

Ok, thank you


update kubeflow summit agenda & speakers

This PR updates the Kubeflow Summit 2023 with the final agenda.
Based on: https://docs.google.com/spreadsheets/d/11gdgKxlCzQfMLiRO-gaEYIQG91VbdzJCnARHLhG9YTQ/edit#gid=0

/lgtm


Fix that annoying "DMWM-WMCore-PR-pylint" jenkins test

Apparently it's responsible for most (if not all) of the jenkins test failures.
It seems to be getting stuck copying the artifacts back to somewhere (I assume to the upstream project "DMWM-WMCore-PR-test"...).
Example of the logs can be seen here (if not cleaned up):
https://cmssdt.cern.ch/dmwm-jenkins/job/DMWM-WMCore-PR-pylint/7355/console

Sigh... apparently same happens to "DMWM-WMCore-PR-27".
...
RefactoringTool: No files need to be modified.
Tue Jul 31 13:30:48 GMT 2018: running AnalyzePyFuture.py script
Tue Jul 31 13:30:48 GMT 2018: done with all tests and copying files over to artifacts!
~