elasticsearch and Hive integration on Yarn

Hi,
I am using Apache 2.6.0 and Hive 0.13 versions. I have downloaded elasticsearch-hadoop-2.1.0.Beta3.zip and elasticsearch-1.4.4 version. while executing INSERT query in hive to insert the data into elasticsearch I am getting below error:
ERROR - Caused by: org.xml.sax.SAXParseException; systemId: file:///tmp/hadoop-root/.../job.xml; lineNumber: 665; columnNumber: 51; Character reference "&#0" is an invalid XML character.
Please help to solve the problem, am I using any wrong version of lib?
I also gone through the issue mentioned in the https://github.com/elastic/elasticsearch-hadoop/issues/359 but didn't get the solution.
Please help, thanks in advance.
Abhishek

Hi, I  gone through the #359 and changed my hive query to insert only single column. it is working fine but at the end I am getting below error:
Diagnostic Messages for this Task:
Error: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: Hive Runtime Error while processing row (tag=0) {"key":{},"value":{"_col0":"<IP_ADDRESS>"}}
at org.apache.hadoop.hive.ql.exec.mr.ExecReducer.reduce(ExecReducer.java:265)
at org.apache.hadoop.mapred.ReduceTask.runOldReducer(ReduceTask.java:444)
at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:392)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: Hive Runtime Error while processing row (tag=0) {"key":{},"value":{"_col0":"<IP_ADDRESS>"}}
at org.apache.hadoop.hive.ql.exec.mr.ExecReducer.reduce(ExecReducer.java:253)
... 7 more
Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: org.apache.hadoop.hive.ql.metadata.HiveException: org.elasticsearch.hadoop.rest.EsHadoopNoNodesLeftException: Connection error (check network and/or proxy settings)- all nodes failed; tried [[localhost:9200]]
at org.apache.hadoop.hive.ql.exec.FileSinkOperator.createBucketFiles(FileSinkOperator.java:517)
at org.apache.hadoop.hive.ql.exec.FileSinkOperator.processOp(FileSinkOperator.java:615)
at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:815)
at org.apache.hadoop.hive.ql.exec.LimitOperator.processOp(LimitOperator.java:51)
at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:815)
at org.apache.hadoop.hive.ql.exec.SelectOperator.processOp(SelectOperator.java:84)
at org.apache.hadoop.hive.ql.exec.mr.ExecReducer.reduce(ExecReducer.java:244)
... 7 more
Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: org.elasticsearch.hadoop.rest.EsHadoopNoNodesLeftException: Connection error (check network and/or proxy settings)- all nodes failed; tried [[localhost:9200]]
at org.apache.hadoop.hive.ql.io.HiveFileFormatUtils.getHiveRecordWriter(HiveFileFormatUtils.java:277)
at org.apache.hadoop.hive.ql.exec.FileSinkOperator.createBucketForFileIdx(FileSinkOperator.java:562)
at org.apache.hadoop.hive.ql.exec.FileSinkOperator.createBucketFiles(FileSinkOperator.java:506)
... 13 more
Caused by: org.elasticsearch.hadoop.rest.EsHadoopNoNodesLeftException: Connection error (check network and/or proxy settings)- all nodes failed; tried [[localhost:9200]]
at org.elasticsearch.hadoop.rest.NetworkClient.execute(NetworkClient.java:123)
at org.elasticsearch.hadoop.rest.RestClient.execute(RestClient.java:303)
at org.elasticsearch.hadoop.rest.RestClient.execute(RestClient.java:287)
at org.elasticsearch.hadoop.rest.RestClient.execute(RestClient.java:291)
at org.elasticsearch.hadoop.rest.RestClient.get(RestClient.java:118)
at org.elasticsearch.hadoop.rest.RestClient.esVersion(RestClient.java:367)
at org.elasticsearch.hadoop.rest.InitializationUtils.discoverEsVersion(InitializationUtils.java:84)
at org.elasticsearch.hadoop.hive.HiveUtils.init(HiveUtils.java:142)
at org.elasticsearch.hadoop.hive.EsHiveOutputFormat.getHiveRecordWriter(EsHiveOutputFormat.java:93)
at org.elasticsearch.hadoop.hive.EsHiveOutputFormat.getHiveRecordWriter(EsHiveOutputFormat.java:42)
at org.apache.hadoop.hive.ql.io.HiveFileFormatUtils.getRecordWriter(HiveFileFormatUtils.java:287)
at org.apache.hadoop.hive.ql.io.HiveFileFormatUtils.getHiveRecordWriter(HiveFileFormatUtils.java:274)
... 15 more
FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.mr.MapRedTask
MapReduce Jobs Launched:
Stage-Stage-0: Map: 7  Reduce: 1   Cumulative CPU: 9.22 sec   HDFS Read: 1706351 HDFS Write: 0 FAIL
Total MapReduce CPU Time Spent: 9 seconds 220 msec
please help me to solve the problem.

I would check a couple of things.

Make sure that you are using elasticsearch-hadoop-2.1.0.BUILD-20150314.023416-331.jar. There was a bug that was fixed in master
I would check you Create table statement and make sure that the 'es.nodes' is referring to the host name on which the elastic search is running

Hi Vinaypandit,
thank you very much for reply. I am not able to find the jar you said. it will be great help for me if you can share the link to download it.
Thanks & Regards
Abhishek Soni

nightly builds are here: https://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch-hadoop/

I am wondering if anyone has resolved above error. I am using Elasticsearch v1.1.2, Hive 0.12.0-cdh5.1.3. I am using most recent build elasticsearch-hadoop-2.1.0.BUILD-20150426.023656-380.jar
2015-04-26 05:39:02,081 ERROR [main] org.elasticsearch.hadoop.rest.NetworkClient: Node [Connection timed out] failed (HERE_GOES_ES_HOSTNAME:9200); no other nodes left - aborting...

@nataliaking That indicates that the nodes where the Hive script is running cannot access Elasticsearch on port 9200. Make sure the Elasticsearch nodes have the REST interface enabled and the IP used is accessible from the Hive nodes.
Note the default is localhost:9200 which is likely not going to work when deployed in a cluster.
P.S. For questions please the mailing list not the issue tracker. And please don't hijack existing reports.
Cheers,

@abhisheksoni16 @Vinaypandit  This issue has been fixed in master some time ago - see the #409 #359 issues. Note that unless the classpath is cleared, older versions without the fix might be loaded instead.
Cheers,


What makes fastForEach Faster

Hi, I was wondering what exactly makes fast for each faster than the normal for each.
I noticed in the .js you mention:
"Employing sound techniques to make a faster Knockout foreach binding."
I am not sure if these sound techniques make it faster and if so what are sound techniques?
I am wondering as I am doing a comparison of frameworks and was wondering what made this faster.

Good question. :)  There are a few things, including (and I may be forgetting things):

Updates are batched into animationFrames

It has a noIndex option that makes it O(1) in terms of computational complexity

DOM nodes are re-used for re-ordering/deletion/inserts within the same animation frame

It can re-use the Knockout Context with a noContext option

So, in other words, in the average case it'll have fewer reflows because DOM changes are batched into animation frames.  When given options noIndex it will scale to relatively huge numbers because each addition has constant-time computational complexity.
I hope that helps explain. :)

Thank you for the response! That helps a lot.

So this issue can be closed?

Yes this issue can be closed.


cargo update

The sanity tests are still running locally, but I wanted to start CI in parallel.

Based on this result I think this is merge-ready:
        PASS [ 348.903s] libtonode-tests::concrete slow::witness_clearing
------------
     Summary [1185.968s] 332 tests run: 332 passed (109 slow), 31 skipped
1731611433 || shofth nattyb dev[ ]
REDACTED: 0 $
git show -s
commit 4a37b48afe4726f9d6d3198d7140c0beb9e78c67 (HEAD -> dev, zancos/cargo_update)
Author: zancas<EMAIL_ADDRESS>Date:   Thu Nov 14 11:46:30 2024 -0700

    cargo update


dapr init does not work with nightly builds

Expected Behavior
Both of the following commands should work:
dapr init --runtime-version=nightly-2024-02-03
dapr init -k --runtime-version=nightly-2024-02-03
Actual Behavior
$ dapr init --runtime-version=nightly-2024-02-03
⌛  Making the jump to hyperspace...
ℹ  Container images will be pulled from Docker Hub
ℹ  Installing runtime version nightly-2024-02-03
❌  Downloading binaries and setting up components...
❌  error downloading daprd binary: version not found from url: https://github.com/dapr/dapr/releases/download/vnightly-2024-02-03/daprd_linux_amd64.tar.gz

Steps to Reproduce the Problem
Run the commands.
Release Note

RELEASE NOTE: ADDED support for nightly builds in dapr init

If I could set this to edge or nightly that would be extremely handy.  I think I'd do at least weekly integration tests and prevent more regressions as we go.


pull latest

Coverage increased (+3.4%) to 88.811% when pulling c5b2f2ed64483374f899804fc358684c2b74e409 on thetringuyen:master into 81be990eb59931acffa2cea70a10380061666ce8 on thequackdaddy:master.


Adopt 128 bit cycles API

https://dfinity.atlassian.net/browse/LANG-8

@nomeata do you recall: what's the current status of support wasm functions with n-ary returns at the moment? The new 128 bit cycles API returns two values, high and low 64 bits, presumably for atomicity, and I'm wondering if I'll be able to call that using our wasm lib or will need to upgrade.

That requires multi-value, see https://github.com/dfinity/motoko/pull/1459. I am surprised that this actually works in the replica, I thought rust support for multi-value is not there yet.
I see nothing in ic-hs yet. I'd wait before it's there before doing anything in Motoko (or officially give up on spec and reference implementation driven design).
Do they have test cases with plain .wat files that demonstrate that the replica really implements the specification (with multiple results), and not sure Rust-specific calling convention that uses the stack or something like that?

Yeah, I though I might be being too optimistic....  I'll have to investigate I guess...

Once https://github.com/dfinity/motoko/pull/2879 is merged we have support for this in ic-ref. Support in drun is still blocked on a working public code dump.

Long done.


Update hdinsight-restrict-public-connectivity.md

Added an additional sentence to recommend placing dependent resources with private endpoints on the cluster subnet. This was a gotcha that I encountered leveraging a different subnet on the same vnet. The diagram earlier shows this configuration, but its not obvious that a different subnet would prevent connectivity.

Thanks. I added another commit just with a missing word in the sentence.


Archive repo with the release of Crossplane 1.15

With PR https://github.com/crossplane/crossplane/pull/5275, the functionality of this binary will be merged into the Crossplane CLI.

@jbw976 I don't have permissions to this repo. Can you archive it?


Overflow menu outline expanded by dropdown in Mozilla

In Chrome:

In Firefox:

Hi there! Since this is related to the CSS of the component reference, and not the React.js bindings, moved this issue over to: https://github.com/carbon-design-system/carbon-components/issues/475
Feel free to re-open if you feel like that doesn't address your core concern!


Remove Registy trait in registry module and refactor

This PR removes the Registry  trait from the registry module - according to #89 . The following changes has been made:

Removed Registry trait and RegistryType enum from registry/mod.ts
Moved Artifactory functions that were implemented for the Registry trait into the struct implementation - added made them pub(lic)
Moved LocalRegistry functions that were implemented for the Registry trait into the struct implementation - added made them pub(lic)
Removed Registry trait references

I've been thinking about ways to test the registry interactions, and it occurred to me that even though we don't want to support multiple registry implementations, the trait might still be helpful so we can inject a local registry for use in testing.
That may still require a larger refactor though (because the current signatures don't give us a way to customise the registry choice) so I think it may still be best to get rid of the trait for now and reintroduce it later when necessary. It's definitely confusing to have it at the moment.

Thanks for the contribution!


Fedora docker daemon not running on kamal deploy

On a fresh fedora instance, and a working kamal project, I ran
kamal init

Updated config/deploy.yml to my docker hub repo / user
Set working KAMAL_REGISTRY_PASSWORD
After running
kamal setup

I get
  INFO [c8e5e6b1] Running docker pull .../...:... on my-ip
  Finished all in 252.6 seconds
Releasing the deploy lock...
  Finished all in 253.7 seconds
  ERROR (SSHKit::Command::Failed): Exception while executing on host myip: docker exit status: 1
docker stdout: Nothing written
docker stderr: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Problem: Should have started the docker daemon automatically upon install for future commands to work

 ERROR (SSHKit::Command::Failed): Exception while executing on host myip: docker exit status: 1
The error seems to be related with SSH not docker, are you able to SSH into the machine?

No ssh works fine because when I ran into the same problem again, the only way to fix it was to ssh into the server and run the systemctl commands above. Then the ssh worked fine
I believe that message means that the docker service exit with a status of 1 because the docker service wasn't running.

Ah ok I see your point. You should remember that Kamal is a deployment tool, not a system configuration. Not sure if this is the responsibility of Kamal (I'm just a regular user), because those commands are not universal in Linux, so Kamal would have to query for the OS and then run the adequate commands to enable docker daemon at startup.
In my case, I installed everything I need and secured the system and then used kamal to deploy and run the containers.

I understand that it's not a system configuration, but it says that all you need to do is point to an ip you can access over ssh, and it'll install docker and do the rest of the deployment.
When kamal installs docker (see below) on debian and ubuntu, docker will automatically start the docker daemon post install. However because fedora and rhel by default don't start the docker daemon, it would be a very simple low hanging fruit common blocker to just start the docker daemon with systemctl if it isn't started.
kamal setup
  INFO [cc2b9321] Running /usr/bin/env mkdir -p .kamal on myip
  INFO [cc2b9321] Finished in 0.817 seconds with exit status 0 (successful).
Acquiring the deploy lock...
warning: could not open directory 'db/postgres/data/': Permission denied
Ensure Docker is installed...
  INFO [29053175] Running docker -v on myip
  INFO [29053175] Finished in 0.124 seconds with exit status 127 (failed).
  INFO [b5c933cb] Running [ "${EUID:-$(id -u)}" -eq 0 ] || command -v sudo >/dev/null || command -v su >/dev/null on myip
  INFO [b5c933cb] Finished in 0.131 seconds with exit status 0 (successful).
  INFO Missing Docker on myip. Installing…
  INFO [63679fdf] Running /usr/bin/env sh -c 'curl -fsSL https://get.docker.com || wget -O - https://get.docker.com || echo "exit 1"' | sh on myip
  INFO [63679fdf] Finished in 43.739 seconds with exit status 0 (successful).


CircleCI unit-test with Go 1.13 image

To migrate CircleCI to compile with Go 1.13:

[ ] Create a new textile/builder docker image
[ ] Change .circleci/config.yaml to use it

Regarding the first checklist item:
@sanderpick , is the textile/builder Dockerfile available?
I imagine is just changing the URL tar file, rebuild, tag and upload.

Yep, the file is here: https://github.com/textileio/go-textile/blob/master/.circleci/Dockerfile
After re-building that image, you should now be able to push a new tag to docker hub

Nice. I'll let you know about any probs.


Basic Pricing Tier

Currently we say 'Workloads that require light compute and I/O performance. Examples include servers used for development or testing or small-scale infrequently used applications'
We need to augment it to say that 'Azure Standard Storages that are used in the Basic Tier servers have variable IOPS with no performance guarantees'

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

ID: 038ee2b6-8a76-a678-1069-3eb7c2808d73
Version Independent ID: cd6cb2ea-9fff-9237-2168-a39eb24f2677
Content: Pricing tiers for Azure Database for PostgreSQL
Content Source: articles/postgresql/concepts-pricing-tiers.md
Service: postgresql
GitHub Login: @jan-eng
Microsoft Alias: janeng

#please-close

Part of internal team discussions.

part of internal discussion

If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


@silent message

Summary
add support for silent messages
What is the feature request for?
Application commands
The Problem
add support for silent messages
The Ideal Solution
I think the best way would be
await interaction.response.send_message("Hello World!", silent=True)
The Current Solution
N/A
Additional Context
No response

Set suppress_notifications via flags in .send()

Set suppress_notifications via flags in .send()

Can say the same for suppress_embeds. The doc for the  flags param needs updating too.


Dockerization of KestrelHttpServer (DVSPIMP-2099)

This pull request adds the docker-compose requirements to the repo. No Other changes Or any changes to the existing code have been made.

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

What's the purpose of this change?


usbip: fix auto-attach script

The upstream script changed to a relative path based on the working directory. This patches the code to use the lookup by PATH instead.
Fix #594

wsl --import seems to be flakey unfortunately. I hope this will be better once we switch to wsl --install --from-file


Commands not working (Quests 3.7.6)

Build : Quests 3.7.6
Not a single command seems to be working. No error text ether. Just nothing
Wondering if its because i am on 1.14.4 and this isn't up to date, or the plugin is missing files?
Edit: Also the server when i go to type to commands. Shows them as commands i can use.

Working just fine for me on 1.14.4 with Quests 3.7.6 installed.
The fact that you're seeing autofill suggestions means the plugin is working. Make sure you have permissions or are /op
You could also try removing other plugins in-case they conflict.

You could also try temporarily removing other plugins in-case they conflict.

Hi! I'm an owner of the server me and @DynastyCraft run. I've updated a bunch of the plugins one of which was mystic mobs and since then the plugin is now working. Thanks for your help!


Add rich text option

Hello!
I’m going to ask a question. I don’t think this is the right place, but I don’t have matrix or other social media. So, is there a possibility that you will add in future something like “super note” in Standard Notes ( a tool that let you change font, font size, justify the text and so on) with the possibility to export in pdf ?
The reason I’m asking for this: I’m currently using Google Docs because for my personal needs is the best choice; however, I find out that super note mode in sn is great, but you can’t export in pdf. So, I thought maybe you could add something like this in you app. I hope I made myself clear.
Also, I just want to express my gratitude to your project. I think is really good! I’m not demanding anything here, I know this is a FOSS project and as such you’re probably building it in your free time without any payback. I’m just asking and the answer “I don’t have time/resources” is perfectly fine! :)

Hi, this is actually supported with Typst might wanna try it out, the docs are at https://typst.app/docs/
:)

Oh my, thank you! I just tried the function and I think is amazing. You’re really cool. :)
also, I just wanted to tell you that I just tried your new app “AppVerifier” and…wow. I searched for an application like that for a long time. I love you apps because they are so simple and yet so powerful. (Just on thing: “policy and license” seems to be set incorrectly, maybe is just my phone though (I’m using a Samsung galaxy A30s with android 11)

Thanks for the support :D. That bug might be a jetpack compose one as something similar happened before too. It happened on my Pixel 7 and other devices as well but got fixed in an update to jetpack compose.


Fail to create/change sub-indices

Hi @bggardner,
your editor seems appealing as it is web-based and therefore platform independent. I tried to create a 1010h which has at least 0x00 and 0x01 as sub-indices but I cannot create nor change any sub-index. Can you please elaborate the steps required to proceed?
This is what I got

Right now, I am using Firefox 114 on Windows 10.
Thanks in advance!

Thanks!
FYI
apparently this it the current state in Firefox

but I tried Chrome now and it works there

You may need to do a hard refresh so Firefox reloads the (changes to) JavaScript file.


Control flow graph

Cretonne's in-memory representation needs a control flow graph analysis. This would record for each EBB:

A set of predecessors, where a predecessor is an (EBB, Inst) pair identifying a basic block in an EBB.
A set of successor EBBs. This may not be worthwhile caching since it is easily derived from the branch instructions in the EBB.

The control flow graph is easily computed from the code, so we don't want to represent it in the textual IR. It would be useful if the iteration order of the predecessor set were stable so it doesn't change when saving out the IR and reloading it.

A very ugly WIP. https://github.com/mrrrgn/cretonne/commit/19ef16e508df28b916cb8a45490368dd58bfaeff
todo:

Code cleanup and restructuring (maybe the predecessors should be stored on the Function?)
Tests!
Generating prettier graphviz graphs.

A new approach which moves the CFG into its own data structure. This is tidier and easier to test IMO. Speaking of tests, writing them now. https://github.com/mrrrgn/cretonne/commit/977d11046dcb4383f59a4d3bc9e9a448dbe28c65
The graph printing is still ugly/basic. Thinking about the parser interface as I proceed with that.

https://github.com/stoklund/cretonne/pull/6
https://github.com/stoklund/cretonne/pull/7

Let's add some tests for the print-cfg command before closing this.

https://github.com/stoklund/cretonne/pull/8


Feat exportable targets

What this PR contains:
User Exportable Target
when there is a property userExportable on any target served from the Q-server at /editor/targets it shows a button for any exportable target. The object at exportableTarget looks like this:
{
  "buttonLabel": "download for print",
  "modalTitle": "shown as the titel of the modal dialog"
  "preview": {
    "target": "target_used_for_preview"
  },
  "onlyTools": ["toolThatAllowsThisExport"]
}

onlyTools is optional. If undefined, the button is shown for items of all tools.
If the button is clicked, a modal opens with a schema-editor driven by a JSON-schema served from the Q server at export-options-schema/{itemId}/{target}.json
When the user clicks download in the modal, a renderingInfo request is sent to the target with toolRuntimeConfig.exportOptions set to the data from the schema-editor. The response is then saved to disk.
loading state on buttons
The button-primary, button-secondary and button-tertiary elements bind a isLoading attribute. If it is true a q-loader element is shown instead of the icon and text.
The q-loader element is a little nicer now with a css animation instead of a gif.
different content-types in preview
The preview-container element can now handle different content-types of renderingInfo. Everything that is not returned with application/json is treated as a Blob and displayed as an image. So renderingInfo to be displayed in the preview can be a PNG for example served with image/png.
Additionally, the preview-container shows a q-loader if it is in loading state.

@manuelroth I improved the placing of the q-loader in the preview container with the last commit


[Disk Meter] View free space and total bandwidth usage on hover

On SilverAzide's Disk Meter, it is possible to view both current disk space usage as well as free disk space, which is what I miss in this Disk Meter, as here it's either option one or two.
I think a good solution to that would be to make it so that the mode switches when hovering on the disk space usage bar, so that when needed, both statistics can be viewed with ease.
Another good thing to have would be the ability to view the total bandwidth usage when hovering on bandwidth stats, similar to how it works in SilverAzide's Disk Meter.

I'll implement your suggestions. Thank you!

Implemented for v1.7.0.


Stylesheets updated

@vinitshahdeo Please review the changes made in style.css

@ananyachaudhary Sure will review.


Handle patch versions in versioning script

Description
Update the release automation script so that it can correctly handle patch version numbers like "10.4.3-LTS-Patch-3".
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Limited the regex to only match LTS Patch version.


Agent RPC IDs could theoretically collide

The server RpcClient choses a random integer between 0..2_147_483_647 as the RPC request ID:
  def request_id
    rand(2_147_483_647)
  end

The agent RpcClient has a more complicated logic where it tracks pending requests, and avoids currently in-flight request IDs:
    def request_id
      id = -1
      until id != -1 && !@requests[id]
        id = rand(2_147_483_647)
      end
      id
    end

See #1855 for some discussion about this:

https://github.com/kontena/kontena/pull/1855#discussion_r103421867
https://github.com/kontena/kontena/commit/2bdbfdbd52848643a91754ddb4ff842bf0462e28#commitcomment-21091762
https://github.com/kontena/kontena/pull/1855#issuecomment-283273890
https://github.com/kontena/kontena/pull/1855#pullrequestreview-24420682

It is possible for these request IDs to collide, if an RpcClient#request task manages to choose the same request ID as some previous request that is still in flight, waiting for the remote server to respond. Request ID collisions could lead to nasty side-effects, where RPCs requests return unexpected results.
The current stateful agent implementation will work to avoid Request ID collisions, unless it crashes with in-flight RPCs. However, the agent implementation also leaks memory on RPC request timeouts, as it can't re-use those request IDs...
The simplest approach would be to use something similar to TCP sequence numbers... initialize @request_id = rand(1 << 32) and then use @request_id = (@request_id + 1) % (1 << 32).
However, this would not work on the server, where there will be multiple proceses with independent RpcClient states initiating requests... perhaps it would make more sense to use the MongoPubsub ID for the RpcClient implementation, and then have each WebsocketBackend choose their own request IDs?

One other approach is to use Twitters snowflake pattern where the id is combined from timestamp, node/worker number and running counter. So something like:
(Time.now.to_i << 22) | (node_num << 12) | counter++

I really would like an explanation of these magic numbers ... :)

https://www.slideshare.net/davegardnerisme/unique-id-generation-in-distributed-systems
slides 23&24

Talking of magic numbers... the current rand(2_147_483_647) is only using half of the uint32 space... it should be rand(1 << 32), or rand(4294967296)?

@SpComb probably yes, but we did hit into some weird msgpack issues back in the days.. maybe msgpack updates have fixed this.


Removed unnecessary hyphen

@mufeez-amjad : Thanks for your contribution! The author, @cynthn, has been notified to review your proposed change.

#sign-off @mufeez-amjad thank you for the fix!


add comments to export old wallets

ACK

Coverage increased (+0.004%) to 93.323% when pulling a40188aec916f90b46a2d7e11c4a21ed07831069 on matiu:doc/test-comments into ff8873502121012db055554779f97f71a437893a on bitpay:master.

closed in favor of https://github.com/bitpay/bitcore-wallet-client/pull/400


NSM Provisioning Fails - missing /charts manifests

Description
Using the latest version of NSM adapter, provisioning of NSM fails. See the error below. Helm charts have moved directories.
Expected Behavior
Short-term, the provisioning of NSM can be updated to use the new path to the charts directory - https://github.com/networkservicemesh/networkservicemesh/tree/master/deployments/helm
Long-term, the NSM adapter needs to be updated to use helm; to deploy NSM in the fashion in which the NSM project defines (using networkservicemesh/helm-charts). See #53 .
Logs
ERRO[0045] render manifests error: found in requirements.yaml, but missing in charts/ directory: config
DEBU[0045] sending event: &meshes.EventsResponse{EventType:2, Summary:"Error while deploying NSM", Details:"render manifests error: found in requirements.yaml, but missing in charts/ directory: config", OperationId:"ca151287-f9f6-4e12-afba-0a134fedd94c", XXX_NoUnkeyedLiteral:struct {}{}, XXX_unrecognized:[]uint8(nil), XXX_sizecache:0}

@ivanayov, here's a relatively simple bug to fix. This issue is currently causing the NSM adapter not to function as users are not able to deploy NSM using Meshery because of it.

I think this issue is fixed. I will be closing it now.


Pivot longer minor

PR Description
Please describe the changes proposed in the pull request:

Fixes to logic in .value computation

This PR improves pivot_longer.

PR Checklist

Please ensure that you have done the following:

[x] PR in from a fork off your branch. Do not PR from <your_username>:dev, but rather from <your_username>:<feature-branch_name>.

[x] If you're not on the contributors list, add yourself to AUTHORS.rst.

[x] Add a line to CHANGELOG.rst under the latest version header (i.e. the one that is "on deck") describing the contribution.

Do use some discretion here; if there are multiple PRs that are related, keep them in a single line.

Quick Check
To do a very quick check that everything is correct, follow these steps below:

[x] Run the command make check from pyjanitor's top-level directory. This will automatically run:

black formatting
flake8 checking
running the test suite
docs build

Once done, please check off the check-box above.
If make check does not work for you, you can execute the commands listed in the Makefile individually.
Code Changes

If you are adding code changes, please ensure the following:

[x] Ensure that you have added tests.
[x] Run all tests ($ pytest .) locally on your machine.

[x] Check to ensure that test coverage covers the lines of code that you have added.
[x] Ensure that all tests pass.

Documentation Changes

If you are adding documentation changes, please ensure the following:

[ ] Build the docs locally.
[ ] View the docs to check that it renders correctly.

Relevant Reviewers

Please tag maintainers to review.

@ericmjl

@samukweku please do the honors!


[BUG]: Pipeline fails with Failed to create CoreCLR, HRESULT: 0x80004005

What happened?
All my self hosted devops pipelines are failing with Failed to create CoreCLR, HRESULT: 0x80004005  . I am not aware of any updates which have caused this. I have seen the solution here and tried it with no luck.
Versions
Ubuntu 22.04.2 LTS
Agent 3.236.1
dotnet 8.0.203
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu 22.04.2 LTS
Version controll system
git
Relevant log output
##[error]Failed to create CoreCLR, HRESULT: 0x80004005
,##[error]We stopped hearing from agent fern00. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. For more information, see: https://go.microsoft.com/fwlink/?linkid=846610

Hi @lewisoptellum thanks for reporting!
We are working on more prioritized issues at the moment, but will get back to this one soon.

Thanks a lot. Do you have any suggestions for a work around at the minute? Currently our entire CI is blocked by this issue is all.
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg

From: Maksim Petrov @.>
Sent: Monday, April 8, 2024 2:28:15 AM
To: microsoft/azure-pipelines-agent @.>
Cc: Lewis Lappin @.>; Mention @.>
Subject: Re: [microsoft/azure-pipelines-agent] [BUG]: Pipeline fails with Failed to create CoreCLR, HRESULT: 0x80004005 (Issue #4741)
CAUTION: External email
Hi @lewisoptellumhttps://github.com/lewisoptellum thanks for reporting!
We are working on more prioritized issues at the moment, but will get back to this one soon.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azure-pipelines-agent/issues/4741#issuecomment-2042044901, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAGDMIZELX6GS4UFLPKY3OTY4JBI7AVCNFSM6AAAAABFRWBV26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBSGA2DIOJQGE.
You are receiving this because you were mentioned.Message ID: @.***>
CAUTION: This email is confidential and intended for the addressees only. If you receive this email in error, please let us know and delete the email. We believe, but do not warrant, that this email and any attachments are virus free. We do not accept any liability for losses that you may sustain as a result of software viruses.

Adding the following to runsvh.sh solved the issue:
# insert anything to setup env when running as a service
export COMPlus_EnableDiagnostics=0

I am having the same intermittent issue and don't know how to debug it.
@lewisoptellum How did you figure out that solution?


aur fetch: learn to parallelize

Rewrite of aur-fetch to implement features such as

~ability to choose between git reset (default)/pull --rebase to update cached repos. (discard local commits vs trying to reapply local commits on top of the incoming changes)~ #639
~ability to choose between a git log or git diff to generate review patches.~ #640
fetch packages in parallel

Documentation still missing.

I think it makes sense to split this up to:

PR that adds --rebase and --results (added functionality over 2.3, same behavior)
PR that adds --log, --diff
PR that adds --jobs

aur-fetch/aur-sync is being reworked, and this PR would need a complete rewrite once these changes land. So I'll close this for now. We can revisit this when those code-paths are more stable.


[Task] Add new and remove old bootswatch themes

What is the task
I can do this task but I will need some form of help.
We need to update:
Paper  (screenshots no longer exist on bootswatch)
Readable (screenshots no longer exist on bootswatch)
We need to add:
Litera
Lux
Materia
Minty
Morph
Pulse
Quartz
Sketchy
Solar
Vapor
Zephyr
Additional Notes
This should be quite easy to do, i will post a comment on this issue if i need help with this.

I'll include new themes in commit when Bootstrap 5 will ready.


feat(client): rename client::Builder pool options

Renamed keep_alive_timeout to pool_idle_timeout.
Renamed max_idle_per_host to pool_max_idle_per_host.
Deprecated keep_alive(bool) due to confusing name. To disable the
connection pool, call pool_max_idle_per_host(0).

This is partly motivated by wanting to add HTTP2 keep-alive options, and the names keep_alive(bool) and keep_alive_timeout would be confusing as they have different semantics.


Pad @q values with 'doz' in certain cases

E.g., renders both the hex strings '010203' and '10203' as '~doznec-binwes', rather than the latter as '~nec-binwes'.  Note that both are considered equivalent in Hoon (i.e. =(.~doznec-binwes .~nec-binwes) is true).
(See urbit/arvo#824.)

(@Fang- I already tipped you off to this, but just FYI.)


Check led status

Led status is on (red led) when board is sleeping and using battery, this will drain battery faster.

https://www.reddit.com/r/esp32/comments/idinjr/36ma_deep_sleep_in_an_eink_ttgo_t5_v23/


Improved Exception handling Generator.java

Create a meaningful title

Improved Exception handling Generator.java
Description
Generator had some issues, about unreachable code and in theorie cases which leads to crashes.
Also some resources werent properly closed.

Correcting exception handling
Fixing invalid string.format
Autoclosing resources

Does your pull request have unit tests?

No unit test, since no new feature was implemented and should be covered by existing unit tests.

will reopen, when everything fixed.


Infrastructure to run scikit-learn tests on GPU

Changes proposed in this pull request:

The script to run scikit-learn tests with sycl context
Small fixes in patching message and execution with context
⚠ all the failed GPU tests added to deselect

/intelci: run

do you have a plan to integrate this into a private CI? or do you want to merge first?

@PetrovKP, yes, I am currently working to enable this in private CI

/intelci: restart

/intelci: run
set infra_branch=dev/smirnovm-sklearn-gpu-tests

/intelci: run
set infra_branch=dev/smirnovm-sklearn-gpu-tests

/intelci: run
set infra_branch=dev/smirnovm-sklearn-gpu-tests

CI: http://intel-ci.intel.com/eb9e0137-5deb-f1a7-b150-8cdcd4b723a1

CI: http://intel-ci.intel.com/eba35508-4c07-f10f-8b93-8cdcd4b723a1


Token group focus created

Description
POC for focus on token API
How has this been tested?

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

Changes include appropriate documentation updates.
Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
Changes do not include unsupported browser features, see CONTRIBUTING.md.
Changes were manually tested for accessibility, see accessibility guidelines.

Security

If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

Changes are covered with new/existing unit tests?
Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing this as out of scope for the initial release of the file-upload. The token-group is also used in multiselect and property-filter and there the concern is not addressed. Once file-upload is released we can have a second look and evaluate if focusing on the first token upon creation can be implemented for all component and if we need additional changes for that.


Fix RBAC for Folders (descendent of VMs)

Part of https://github.com/ManageIQ/manageiq/issues/21516
We preload to avoid N+1 in our map
But some of the relations are not associations
(i.e.: parent_blue_folders and resource_pool)
So we are only using preload for those that are associations.
This fixes:
DEPRECATION WARNING: Vm.parent_blue_folders does not exist (called from preload at manageiq/lib/miq_preloader.rb:7)

And fixes a rails 6.1 blowup

push:

fixed rubocops
added comments per LJ to make reasoning more obvious

push:

fixed rubocops. they sure are picky about the aliases. I can throw those away. they are only used in tests but they read better for me.


Cannot marshal JSON object to NSDictionary and vice versa

In Cordova one can call native APIs with JSON objects and they are converted to NSDictionary under the hood.
Consider the same behaviour for JSONArray <-> NSArray

Right now the bridge will convert an Array to an NSArray implicitly, but that's because I can recognize the Array exotic object. I can project the Map exotic object as NSDictionary the same way, but from what I gather Maps are not what you're after.
Type-coercing exotic objects is simple, but it becomes tricky to do correctly for plain JavaScript objects. I can't guess the purpose of an object - is it array-like, is it map-like, is it javascript-framework-du-jour's idea of a date, and so on. That's why there's no implicit conversion to NSDictionary today.
What I can do is convert an Object to a NSDictionary only when the target type is explicitly NSDictionary. That is to say, if a native function or method accepts CFDictionaryRef or NSDictionary. Would that work for you?

The runtime can now wrap JavaScript values in NSArray and NSDictionary instances:

When converting to id
Values of the JavaScript Array exotic object will be wrapped as NSArray
Values of the JavaScript Map exotic object will be wrapped as NSDictionary
When converting to NSArray or NSDictionary
Values of the JavaScript Array exotic object and plain JavaScript objects with a length property and indexed properties will be wrapped as NSArray
Values of the JavaScript Map exotic object and plain JavaScript objects will be wrapped as NSDictionary

Native NSArray and NSDictionary instances will still be exposed as Wrapper exotic objects to JavaScript, same as before.


Rework cursor configuration

The cursor configuration has been reworked based on the proposal made in
jwilm/alacritty#1080. This moves the custom_cursor_colors into the
culors.cursor struct, cleans up the deserialization of primary and
cursor colors and moves all other cursor configuration in a new cursor
config field.
I'm proposing this as one potential implementation to improve cursor configuration.
If there are any changes desired that haven't been stated in the RFC, I'd love to
incorporate them in this PR.
This also updates all dependencies to get back on track with clippy.
This fixes #1080.

This still needs a deprecation strategy, but I thought it might be better to add this once the solution is actually accepted over the current configuration.
However when I have the time to quickly and easily change this, I will add this asap.

The old config is now still supported, but deprecation warnings are omitted. This should allow for a smooth transition if this change is desired.

omitted or emitted?
I really like the new config!

My comments on alacritty.yml also apply to alacritty_macos.yml.

This PR initially put the hide_cursor_when_typing variable under
cursor.hide_when_typing. However this field is completely unrelated to
the cursor, but instead relates to the mouse cursor.
Since the word cursor is already used for the active cell in the grid
of a terminal emulator, all occurences of the word cursor when talking
about the mouse have been replaced with the word mouse.
The configuration option has also been moved to
mouse.hide_when_typing, to make it clear what this option is changing.


"copy path" from context menu crashes files

Description
right click on file
copy path
--> crash notice, automatic restart of Files
Steps To Reproduce
right click on file
copy path
--> crash notice, automatic restart of Files
Requirements

e.g. Fix crash that occurs when...

Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.1906
Log File
debug.log

Thanks for the report, I've added this to the project board.


add Android support

Add Android support
Motivation:
make swift-nio compatible with Android, and pass all test in Android.
Modifications:

add missed ifaddrs implementation
add missed thread related functions - CNIOLinux_pthread_getname_np, CNIOLinux_pthread_setaffinity_np and CNIOLinux_pthread_getaffinity_np
fix types incositency between Linux and Android, e.g. Epoll.swift class
make bytes counter explicitely 64bits to avoid overflow on 32bit, in PendingWritesManager.swift and PendingDatagramWritesState.swift
fix issue with Unix domain socket, first byte need to be zero in Android
several incosistency fixes between Linux and Android api.

Result:
now swift-nio works on Android. All tests passed!

wow thanks so much @albertaleksieiev! I'll have a look over the next week (sorry we were out on a conference and almost out to the next)

Thanks for your response and review  @weissi 👌Unfortunately nearest 2 weeks I will be on vacation, so I can commit changes after vacation. But I will response on your changes in a few days😇

@swift-nio-bot test this please

@weissi , @Lukasa , @normanmaurer please check my changes

thanks @albertaleksieiev this looks great and I'll approve as soon as you resolve @Lukasa 's comments. And then 🛳

Fixed! And also I fix some issues regarding the latest master branch. But unfortunately I pushed force and now all timeline is shifted 😓

@swift-nio-bot test this please

@normanmaurer ping

@albertaleksieiev oh, the PR validation failed. You'll need to add exceptions in scripts/sanity.sh for Sources/CNIOLinux/ifaddrs-android.c. Basically you'll need to add at least
-o -name ifaddrs-android.c

to the exceptions list
exceptions=( -name c_nio_http_parser.c -o -name c_nio_http_parser.h -o -name cpp_magic.h -o -name Package.s

wift -o -name c_nio_sha1.h -o -name c_nio_sha1.c)

Awesome, all green! @normanmaurer ready to merge when you are

Thanks to everyone! Swift-nio now will be compatible with Android 🤩

Hi! After a research I ended up on this issue :)
I tried to compile my test project on Android via https://github.com/vgorloff/swift-everywhere-samples
My project uses https://github.com/hummingbird-project/hummingbird (that uses swift-nio)
While compiling with Android Studio I encountered these 2 errors:
cannot find 'getifaddrs' in scope
private let sysGetifaddrs: @convention(c) (UnsafeMutablePointer<UnsafeMutablePointer<ifaddrs>?>?) -> CInt = getifaddrs

cannot find 'freeifaddrs' in scope
private let sysFreeifaddrs: @convention(c) (UnsafeMutablePointer<ifaddrs>?) -> Void = freeifaddrs

I had the impression that this issue was fixed when reading the comments.
Do you have an idea on this problem ?
Thanks! :)

Can you provide the full error output including which lines triggered the issue?

Can you also please provide information about which SwiftNIO version is present in Package.resolved?

Thanks @Lukasa for your concern!
SwiftNIO in Package.resolved:
{
        "package": "swift-nio",
        "repositoryURL": "https://github.com/apple/swift-nio.git",
        "state": {
          "branch": null,
          "revision": "3be4e0980075de10a4bc8dee07491d49175cfd7a",
          "version": "2.27.0"
}

And here is the full log of compile:
> Task :app:spm
Updating https://github.com/apple/swift-nio.git
Updating https://github.com/apple/swift-protobuf.git
Updating https://github.com/swift-server/swift-service-lifecycle.git
Updating https://github.com/apple/swift-nio-http2.git
Updating https://github.com/hummingbird-project/hummingbird
Updating https://github.com/apple/swift-metrics.git
Updating https://github.com/swift-server/async-http-client.git
Updating https://github.com/hummingbird-project/hummingbird-core.git
Updating https://github.com/apple/swift-nio-extras.git
Updating https://github.com/apple/swift-nio-transport-services.git
Updating https://github.com/apple/swift-nio-ssl.git
Updating https://github.com/apple/swift-atomics.git
Updating https://github.com/apple/swift-log.git
Fetching https://github.com/swift-server/swift-backtrace.git
Cloning https://github.com/swift-server/swift-backtrace.git
Resolving https://github.com/swift-server/swift-backtrace.git at 1.2.1
[1/21] Compiling CNIOWindows shim.c
[2/21] Compiling CNIOWindows WSAStartup.c
[3/21] Compiling CNIODarwin shim.c
[4/23] Compiling CBacktrace state.c
[5/23] Compiling _AtomicsShims.c
[6/23] Compiling CNIOLinux shim.c
[7/23] Compiling CBacktrace sort.c
[8/23] Compiling CBacktrace print.c
[9/23] Compiling CBacktrace simple.c
[10/35] Compiling CBacktrace posix.c
[11/35] Compiling CBacktrace mmapio.c
[12/35] Compiling CBacktrace mmap.c
[13/35] Compiling CBacktrace fileline.c
[14/35] Compiling CBacktrace backtrace.c
[15/35] Compiling CNIOHTTPParser c_nio_http_parser.c
[16/35] Compiling CBacktrace atomic.c
[17/35] Compiling CBacktrace elf.c
[18/35] Compiling CBacktrace dwarf.c
[19/37] Compiling Backtrace Demangle.swift
[20/37] Compiling Backtrace Backtrace.swift
[21/38] Merging module Backtrace
[22/38] Compiling Atomics AtomicOptional.swift
[23/38] Compiling Atomics AtomicRawRepresentable.swift
[24/38] Compiling Atomics AtomicLazyReference.swift
[28/38] Compiling Atomics HighLevelTypes.swift
[29/38] Compiling Atomics DoubleWord.swift
[30/38] Compiling Atomics AtomicBool.swift
[31/38] Compiling Atomics PointerConformances.swift
[32/38] Compiling Atomics AtomicStrongReference.swift
[33/38] Compiling Atomics AtomicValue.swift
[35/39] Merging module CoreMetrics
[36/40] Compiling Metrics Metrics.swift
[37/41] Merging module Metrics
[38/41] Compiling Atomics IntegerConformances.swift
[39/42] Merging module Atomics
[40/45] Compiling Lifecycle Atomics.swift
[41/45] Compiling Lifecycle Locks.swift
[42/45] Compiling c-nioatomics.c
[43/45] Compiling Lifecycle Lifecycle.swift
[44/46] Compiling c-atomics.c
[45/49] Merging module Lifecycle
[46/49] Compiling NIOConcurrencyHelpers lock.swift
[47/49] Compiling NIOConcurrencyHelpers NIOAtomic.swift
[48/49] Compiling NIOConcurrencyHelpers atomics.swift
[49/50] Merging module NIOConcurrencyHelpers
[50/122] Compiling NIO SocketOptionProvider.swift
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:103:109: error: cannot find 'getifaddrs' in scope
private let sysGetifaddrs: @convention(c) (UnsafeMutablePointer<UnsafeMutablePointer<ifaddrs>?>?) -> CInt = getifaddrs
                                                                                ^~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:105:87: error: cannot find 'freeifaddrs' in scope
private let sysFreeifaddrs: @convention(c) (UnsafeMutablePointer<ifaddrs>?) -> Void = freeifaddrs
                                                                                ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:122:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:186:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
[51/122] Compiling NIO SocketProtocols.swift
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:103:109: error: cannot find 'getifaddrs' in scope
private let sysGetifaddrs: @convention(c) (UnsafeMutablePointer<UnsafeMutablePointer<ifaddrs>?>?) -> CInt = getifaddrs
                                                                                ^~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:105:87: error: cannot find 'freeifaddrs' in scope
private let sysFreeifaddrs: @convention(c) (UnsafeMutablePointer<ifaddrs>?) -> Void = freeifaddrs
                                                                                ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:122:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:186:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
[52/122] Compiling NIO System.swift
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:103:109: error: cannot find 'getifaddrs' in scope
private let sysGetifaddrs: @convention(c) (UnsafeMutablePointer<UnsafeMutablePointer<ifaddrs>?>?) -> CInt = getifaddrs
                                                                                ^~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:105:87: error: cannot find 'freeifaddrs' in scope
private let sysFreeifaddrs: @convention(c) (UnsafeMutablePointer<ifaddrs>?) -> Void = freeifaddrs
                                                                                ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:122:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:186:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
[53/122] Compiling NIO Thread.swift
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:103:109: error: cannot find 'getifaddrs' in scope
private let sysGetifaddrs: @convention(c) (UnsafeMutablePointer<UnsafeMutablePointer<ifaddrs>?>?) -> CInt = getifaddrs
                                                                                ^~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:105:87: error: cannot find 'freeifaddrs' in scope
private let sysFreeifaddrs: @convention(c) (UnsafeMutablePointer<ifaddrs>?) -> Void = freeifaddrs
                                                                                ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:122:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:186:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
[54/122] Compiling NIO ThreadPosix.swift
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:103:109: error: cannot find 'getifaddrs' in scope
private let sysGetifaddrs: @convention(c) (UnsafeMutablePointer<UnsafeMutablePointer<ifaddrs>?>?) -> CInt = getifaddrs
                                                                                ^~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:105:87: error: cannot find 'freeifaddrs' in scope
private let sysFreeifaddrs: @convention(c) (UnsafeMutablePointer<ifaddrs>?) -> Void = freeifaddrs
                                                                                ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:122:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:186:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
[55/122] Compiling NIO ThreadWindows.swift
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:103:109: error: cannot find 'getifaddrs' in scope
private let sysGetifaddrs: @convention(c) (UnsafeMutablePointer<UnsafeMutablePointer<ifaddrs>?>?) -> CInt = getifaddrs
                                                                                ^~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:105:87: error: cannot find 'freeifaddrs' in scope
private let sysFreeifaddrs: @convention(c) (UnsafeMutablePointer<ifaddrs>?) -> Void = freeifaddrs
                                                                                ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:122:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:186:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
[56/122] Compiling NIO TypeAssistedChannelHandler.swift
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:103:109: error: cannot find 'getifaddrs' in scope
private let sysGetifaddrs: @convention(c) (UnsafeMutablePointer<UnsafeMutablePointer<ifaddrs>?>?) -> CInt = getifaddrs
                                                                                ^~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:105:87: error: cannot find 'freeifaddrs' in scope
private let sysFreeifaddrs: @convention(c) (UnsafeMutablePointer<ifaddrs>?) -> Void = freeifaddrs
                                                                                ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:122:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:186:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
[57/122] Compiling NIO UniversalBootstrapSupport.swift
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:103:109: error: cannot find 'getifaddrs' in scope
private let sysGetifaddrs: @convention(c) (UnsafeMutablePointer<UnsafeMutablePointer<ifaddrs>?>?) -> CInt = getifaddrs
                                                                                ^~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:105:87: error: cannot find 'freeifaddrs' in scope
private let sysFreeifaddrs: @convention(c) (UnsafeMutablePointer<ifaddrs>?) -> Void = freeifaddrs
                                                                                ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:122:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:186:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
[58/122] Compiling NIO Utilities.swift
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:103:109: error: cannot find 'getifaddrs' in scope
private let sysGetifaddrs: @convention(c) (UnsafeMutablePointer<UnsafeMutablePointer<ifaddrs>?>?) -> CInt = getifaddrs
                                                                                ^~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/System.swift:105:87: error: cannot find 'freeifaddrs' in scope
private let sysFreeifaddrs: @convention(c) (UnsafeMutablePointer<ifaddrs>?) -> Void = freeifaddrs
                                                                                ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:122:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
/Users/ion/Desktop/nioandroid/Package/.build/checkouts/swift-nio/Sources/NIO/Utilities.swift:186:13: error: cannot find 'freeifaddrs' in scope
            freeifaddrs(originalInterface)
            ^~~~~~~~~~~
[59/122] Compiling NIO IOData.swift
[60/122] Compiling NIO IntegerTypes.swift
[61/122] Compiling NIO Interfaces.swift
[62/122] Compiling NIO Linux.swift
[63/122] Compiling NIO LinuxCPUSet.swift
[64/122] Compiling NIO MarkedCircularBuffer.swift
[65/122] Compiling NIO MulticastChannel.swift
[66/122] Compiling NIO NIOAny.swift
[67/122] Compiling NIO NIOCloseOnErrorHandler.swift
[68/122] Compiling NIO ByteBuffer-conversions.swift
[69/122] Compiling NIO ByteBuffer-core.swift
[70/122] Compiling NIO ByteBuffer-int.swift
[71/122] Compiling NIO ByteBuffer-views.swift
[72/122] Compiling NIO Channel.swift
[73/122] Compiling NIO ChannelHandler.swift
[74/122] Compiling NIO ChannelHandlers.swift
[75/122] Compiling NIO ChannelInvoker.swift
[76/122] Compiling NIO ChannelOption.swift
[77/122] Compiling NIO NIOThreadPool.swift
[78/122] Compiling NIO NonBlockingFileIO.swift
[79/122] Compiling NIO PendingDatagramWritesManager.swift
[80/122] Compiling NIO PendingWritesManager.swift
[81/122] Compiling NIO PipeChannel.swift
[82/122] Compiling NIO PipePair.swift
[83/122] Compiling NIO PointerHelpers.swift
[84/122] Compiling NIO PriorityQueue.swift
[85/122] Compiling NIO RecvByteBufferAllocator.swift
[86/122] Compiling NIO EventLoop.swift
[87/122] Compiling NIO EventLoopFuture.swift
[88/122] Compiling NIO FileDescriptor.swift
[89/122] Compiling NIO FileHandle.swift
[90/122] Compiling NIO FileRegion.swift
[91/122] Compiling NIO GetaddrinfoResolver.swift
[92/122] Compiling NIO HappyEyeballs.swift
[93/122] Compiling NIO Heap.swift
[94/122] Compiling NIO IO.swift
[95/122] Compiling NIO AddressedEnvelope.swift
[96/122] Compiling NIO BSDSocketAPI.swift
[97/122] Compiling NIO BSDSocketAPIPosix.swift
[98/122] Compiling NIO BSDSocketAPIWindows.swift
[99/122] Compiling NIO BaseSocket.swift
[100/122] Compiling NIO BaseSocketChannel.swift
[101/122] Compiling NIO BaseStreamSocketChannel.swift
[102/122] Compiling NIO Bootstrap.swift
[103/122] Compiling NIO ByteBuffer-aux.swift
[104/122] Compiling NIO ChannelPipeline.swift
[105/122] Compiling NIO CircularBuffer.swift
[106/122] Compiling NIO Codec.swift
[107/122] Compiling NIO ControlMessage.swift
[108/122] Compiling NIO ConvenienceOptionSupport.swift
[109/122] Compiling NIO DatagramVectorReadManager.swift
[110/122] Compiling NIO DeadChannel.swift
[111/122] Compiling NIO DispatchQueue+WithFuture.swift
[112/122] Compiling NIO Embedded.swift
[113/122] Compiling NIO Resolver.swift
[114/122] Compiling NIO Selectable.swift
[115/122] Compiling NIO SelectableEventLoop.swift
[116/122] Compiling NIO Selector.swift
[117/122] Compiling NIO ServerSocket.swift
[118/122] Compiling NIO SingleStepByteToMessageDecoder.swift
[119/122] Compiling NIO Socket.swift
[120/122] Compiling NIO SocketAddresses.swift
[121/122] Compiling NIO SocketChannel.swift

> Task :app:spm FAILED

So the ifaddrs code was removed as part of #1695. This appears to add a requirement to target at least Android API Level 24 to get an NDK new enough to have getifaddrs. Can you try raising your minimum deployment target?

Hmm I don't see any change, I edited the build.gradle file
I must be missing something. I think the main reason is that I'm as iOS developer and just starting to learn Android...
I use vgorloff's https://github.com/vgorloff/swift-everywhere-toolchain to build on Android, do you use something else ?
Does the NDK version have an impact on this ? vgorloff's recommends 21.3.6528147
Here is build.gradle gilr:
apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply plugin: 'com.google.protobuf'

android {
    ndkVersion "23.0.7196353"
    compileSdkVersion 30
    defaultConfig {
        applicationId "com.home.hello_ndk"
        minSdkVersion 30
        targetSdkVersion 30
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
        /*
        ndk {
            abiFilters 'armeabi-v7a', 'arm64-v8a', 'x86', 'x86_64'
        }
        */
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
    sourceSets {
        // See:
        // - Gradle swap jniLibs resources based on build flavor - Stack Overflow: https://stackoverflow.com/questions/31687547/gradle-swap-jnilibs-resources-based-on-build-flavor
        // Disabled as sources copied to `app/src/main/jniLibs` on build.
        // main {
        //     jniLibs.srcDirs 'build/swift'
        // }
    }
    tasks.withType(JavaCompile) {
        compileTask -> compileTask.dependsOn spm
    }
    // See: Android NDK. Decrease size of APK - Stack Overflow: https://stackoverflow.com/questions/21644150/android-ndk-decrease-size-of-apk
    splits {
        abi {
            enable true
            reset()
            include 'armeabi-v7a', 'arm64-v8a', 'x86', 'x86_64'
            universalApk false
        }
    }
}

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation 'com.android.support:appcompat-v7:28.0.0'
    implementation 'com.android.support.constraint:constraint-layout:2.0.4'
    testImplementation 'junit:junit:4.13.1'
    androidTestImplementation 'com.android.support.test:runner:1.0.2'
    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
    implementation 'com.google.protobuf:protobuf-javalite:3.8.0'

    protobuf(files("$rootDir/../Models"))
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-android:1.3.0'
}

protobuf {
    protoc {
        artifact = 'com.google.protobuf:protoc:3.8.0'
    }
    generateProtoTasks {
        all().each { task ->
            task.builtins {
                java {
                    option "lite"
                }
            }
        }
    }
}

// https://stackoverflow.com/a/36730534/1418981
// https://stackoverflow.com/q/50448281/1418981
def getDeviceAbi() {
    return "adb shell getprop ro.product.cpu.abi".execute().text.trim()
}

// See: https://docs.gradle.org/current/dsl/org.gradle.api.tasks.Exec.html
task spm() {
    doLast {
        exec {
            workingDir "$rootDir"
            commandLine '/usr/bin/env', "../Package/Builder.sh", "-target", "armv7-none-linux-androideabi"
        }
        exec {
            workingDir "$rootDir"
            commandLine '/usr/bin/env', "../Package/Builder.sh", "-target", "aarch64-unknown-linux-android"
        }
        exec {
            workingDir "$rootDir"
            commandLine '/usr/bin/env', "../Package/Builder.sh", "-target", "i686-unknown-linux-android"
        }
        exec {
            workingDir "$rootDir"
            commandLine '/usr/bin/env', "../Package/Builder.sh", "-target", "x86_64-unknown-linux-android"
        }
    }
}
repositories {
    mavenCentral()
}

/*
afterEvaluate {
    if (project.hasProperty("assembleRelease")) {
        assembleRelease.dependsOn spm
    }
    if (project.hasProperty("assembleDebug")) {
        assembleDebug.dependsOn spm
    }
}
*/

/*
See: Configure Gradle to execute custom build step before starting compilation - Stack Overflow: https://stackoverflow.com/questions/27672553/configure-gradle-to-execute-custom-build-step-before-starting-compilation
gradle.projectsEvaluated {
    preBuild.dependsOn(spm)
}
*/

Hmm, I'm afraid I'm not an android developer either so I'm not well placed to identify the issue here. @buttaface made the change and may know more.

Despite your build.gradle file targeting Android API 30, the SPM toolchain you're using is passing in an earlier Android API and working at cross-purposes to what you've specified. Apparently, you can override it by passing in the Android API you want.


ACM-2647: Problems with time window links (#2446)

ACM-2647: Problems with time window links

Signed-off-by: Maggie Chen<EMAIL_ADDRESS>
use link with generate path

Signed-off-by: Maggie Chen<EMAIL_ADDRESS>
fix edit issue

Signed-off-by: Maggie Chen<EMAIL_ADDRESS>
Add test cases

Signed-off-by: Maggie Chen<EMAIL_ADDRESS>
Add more test coverage

Signed-off-by: Maggie Chen<EMAIL_ADDRESS>Signed-off-by: Maggie Chen<EMAIL_ADDRESS>

/retest

/lgtm

/cherry-pick release-2.5


feat($http): flag timed out requests

This allows differentiating a network error from a timeout.
If you guys thinks this is OK I'll write some tests and update the docs.

this looks interesting, but it needs some tests and documentation.

We've got an issue for this already (https://github.com/angular/angular.js/issues/4491) with a associated PR (#8756). Would be good to discuss pros and cons of the respective approaches. But yeh, in any case we need tests, doc updates etc.

I gave it a bit of thought and think that the status approach is better. So I'll wait for #8756 :+1:


[BUG] SpinButton doesn't allow for really compact sizes

Describe the bug
There seems to be a border on the bottom of the title and the navigation seems to not shrink down
To Reproduce
Steps to reproduce the behavior:

Get a really small font like pico8 font
Customize the theme to work on a really tiny display like 128x128 pixels
Shrink the SBSpinButton's min height down to something like 10
See there is something blocking the title and the navigation doesn't shrink down

Expected behavior

When pegination is disabled the border below the title should go away
The navigation should shrink down to the same size as the title and should position propertly

Screenshots

Desktop (please complete the following information):

OS: Kubuntu 22.04
Godot Version: v4.2.2.stable.mono.official [15073afe3]

Additional context
None

@yudinikita I can't seem how to get around this with themes


Create a jenkinsFile for pushing docker images to docker hub

Issue Title: Create Jenkinsfile for Docker Image Push to Docker Hub
Issue Overview
We need to set up a Jenkins pipeline for building and pushing Docker images to Docker Hub. This Jenkinsfile will automate the process of building the Docker image from our repository and pushing it to a Docker Hub repository.
Task Details

Objective: Create a Jenkinsfile for Docker image automation.

Requirements:

The Jenkinsfile should be designed to build the Docker image from our project's repository.
The pipeline should push the Docker image to a specific repository on Docker Hub.
Proper error handling and notifications should be implemented in the pipeline.
Securely handle Docker Hub credentials within the Jenkins pipeline.

Expected Workflow:

The pipeline should trigger automatically when changes are pushed to the repository.
It should use a Dockerfile present in the repository to build the image.
The image should be tagged and pushed to the specified Docker Hub repository.

Credentials:

Docker Hub credentials should be securely stored and retrieved in the pipeline.
Ensure that credentials are managed following best practices and securely stored in Jenkins.

Testing:

The Jenkinsfile should be tested to ensure it successfully builds and pushes the Docker image.

Documentation:

Provide documentation or comments within the Jenkinsfile to explain its purpose and usage.

Optional Enhancements:

Consider adding additional stages for testing or deploying the Docker image, depending on project requirements.

i can take this up


VaultTokenRequest noParent field serializes incorrectly in JSON

In https://github.com/spring-projects/spring-vault/blob/master/spring-vault-core/src/main/java/org/springframework/vault/support/VaultTokenRequest.java
the noParent field is missing @JsonProperty("no_parent")
Without it, it becomes noParent in the JSON, but Vault expects no_parent
https://www.vaultproject.io/api/auth/token/index.html#no_parent

--- a/spring-vault-core/src/main/java/org/springframework/vault/support/VaultTokenRequest.java
+++ b/spring-vault-core/src/main/java/org/springframework/vault/support/VaultTokenRequest.java
@@ -42,6 +42,7 @@ public class VaultTokenRequest {

        private final Map<String, String> meta;

+       @JsonProperty("no_parent")
        private final boolean noParent;

        @JsonProperty("no_default_policy")

Good catch! Care to submit a pull request?

Here is the PR https://github.com/spring-projects/spring-vault/pull/244


official set of registered voters

[ ] publish to registry
[ ] update URI in the code

@ian-bloom I'm afraid this occurs in more than one place in the code. I'm pretty sure @jimscarver knows where they are.

In today's meeting, @leithaus requested that the staff run a mock election. @ian-bloom agreed to do it on Monday, with help from @jimscarver . @jimscarver noted his availability is limited, but offered 4pm ET , if not before, as a sync point.


Issue with build

Hello,
I have an issue with build. I have installed docker windows and cloned the repositroy. When I try to build I get the following error. Docker works for the sample docker tutorial so I am sure the there is no issues with docker installation.

I found the issue alreayd solved in (https://github.com/WhatsApp/proxy/issues/64)


Error: Building for iOS Simulator-arm64 but attempting to link with file built for iOS Simulator-x86_64 (M1)

Hi, really appreciate if anyone can help me in building to M1 simulator
https://github.com/Kotlin/kmm-sample/issues/60

Hi! M1 support is in development at the moment. It will available with Kotlin 1.5.30
But you can work with project via rosetta

Hi @terrakok thank you so much for the info! I thought I have missed out something. Thanks!

Good day! When is Kotlin 1.5.30 released, or where you can download it?

Hi! M1 support is in development at the moment. It will available with Kotlin 1.5.30
But you can work with project via rosetta

Good day! When is Kotlin 1.5.30 released, or where you can download it?


Test whether this current codon-switching strategy can handle all possible sequences or if there are sequences that are impossible to fix with a silent mutation

Checked all possible sequences of the form NN******NN where N is any nucleotide and ****** is a BsaI or BsmBI restriction site. In all three possible frames for the sequences of this form, there exists at least one silent point mutation that will remove the restriction site and leave an overhang that passes the most basic compatibility tests (doesn't have GC content of 0% or 100% and doesn't interfere with basic part assembly).
We could still probably encounter a situation where there are no compatible overhangs among the possible silent mutations if multiple silent mutations must be made simultaneously. i.e. the program might fail to find a solution if it had to remove multiple very similar restriction sites.


Adding changes for the search client side of the pipeline

Code containing changes to searchers and feature extractors

Mostly looks fine, just a few minor changes.


compiler/protogen: Go name conflicts can occur for non-style compliant protobuf names

What version of protobuf and what language are you using?
// 	protoc-gen-go v1.25.0-devel
// 	protoc        v3.12.4
What did you do?
Tried to generate this file.
syntax = "proto3";
package hello;
option go_package=".;hello";

message myMessage {
  string myField = 1;
}

message my_Message {
  string my_Field = 1;
}

message my_message {
  string my_field = 1;
}

message MyMessage {
  string MyField = 1;
}

message My_Message {
  string My_Field = 1;
}

message My_message {
  string My_field = 1;
}

What did you expect to see?
Some solution on how protoc-gen-go resolves/avoids conflict in name conversion.
What did you see instead?

proto message name
go struct name

myMessage
MyMessage

MyMessage
MyMessage

my_message
MyMessage

My_message
MyMessage

my_Message
My_Message

My_Message
My_Message

Anything else we should know about your project / environment?
Twirp is trying to resolve naming convention issues in go.
Specifically, how to handle service and method names that begin with a lower case letter.
What should they do if it happens to conflict with another method or service. https://github.com/twitchtv/twirp/pull/269
I figured this project would've probably solved this issue with message names. Sadly. it does not.

The derived Go names that protoc-gen-go uses (or more specifically compiler/protogen produces) has long been known to be problematic and possibly produce conflicts. Unfortunately, there is not much we can do about it since changing the behavior will likely break the world. For that reason, the new google.golang.org/protobuf module did not fix this behavior since it's deeply ingrained into the wider use of protobufs in Go and we wanted the new module to be reasonably compatible with the older github.com/golang/protobuf to the best we can.
I should note that naming styles in most programming languages is typically an aesthetic concern. However, for protocol buffers, it's actually a semantic concern since the naming style used makes a difference in whether generated code is even valid. Therefore adherence to the style is of much greater concern beyond just personal preferences. If the protobuf style guide is properly followed, conflicts should not occur. Otherwise, all bets are off, and we can't guarantee conflict-free name generation.
If you want guaranteed conflict-free name derivation, then the following naming styles must be used for the corresponding descriptor types:

Descriptor Type
Naming Style

Enum
CamelCase

EnumValue
UPPER_SNAKE_CASE

Message
CamelCase

Field
lower_snake_case

Oneof
lower_snake_case

Extension
lower_snake_case

Service
CamelCase

Method
CamelCase

In particular:

CamelCase must match the regular expression [A-Z][a-zA-Z0-9]*, where any letters that appear after a number must be uppercase (e.g., Ext4Mount is okay, but Ext4mount is not).
UPPER_SNAKE_CASE must match the regular expression [A-Z][_A-Z0-9]* (e.g., GEO_LOCATION is okay).
lower_snake_case must match the regular expression [a-z][_a-z0-9]*, where letters must not follow any numbers (e.g., int64_value is okay, but int64value is not).

Explicit failure is better than a silent one in case there are no plans to support non-style compliant proto files.
Centralised proto-> multiple language automated builds pass right now, only to get broken on import.
Can we add an explicit failure with an error message for cases where conflicts will occur?

Explicit failure is better than a silent one in case there are no plans to support non-style compliant proto files.

There's no way we can enforce this today with breaking the world. The situation is unfortunate, but it is what it is.

If we want to support the behaviour, we can follow the convention proto2 codegen does and add an _ for the 2nd occurence of a conflicting name.

We already do this for some small set of conflicts. We consider it a grave mistake to have ever done this since it means that generated names are dependent on the order that fields are specified in a .proto file.

There's no way we can enforce this today without breaking the world.

The world already breaks when those failures happen. It just breaks when the program compiles instead of code generation.
Making at break at build time will not break any successfully running program.

The world already breaks when those failures happen. It just breaks when the program compiles instead of code generation.

The code breaks if you add another non-compliant name that results in a conflict. That's very different from breaking the code the moment if any non-style compliant name is used.
I should also note that style enforcement is not the responsibility of protoc-gen-go. Personally, I support such a notion, but this is something that should be discussed at the main protocol buffer project and be implemented in protoc.

That's very different from breaking the code the moment if any non-style compliant name is used.

I meant the examples I posted in original issue, sorry for the confusion. We can fail explicit when we know generated code will not compile.

something that should be discussed at the main protocol buffer project
Given that one officially supported major language implementation stops working in some cases, this might be a good candidate issue for discussion in v4.

We can fail explicit when we know generated code will not compile.

What's the point of building conflict detection code into protoc-gen-go if the code already doesn't compile? We'd just be re-implementing the exact same logic as the Go compiler itself. Therefore, It seems entirely appropriate to let the Go compiler be the explicit failure for this class of failures.

this might be a good candidate issue for discussion in v4.

What is v4?

What's the point of building conflict detection code into protoc-gen-go

Centralised proto-> multiple language automated builds pass right now, only to get broken on import.

We'd just be re-implementing the exact same logic as the Go compiler itself.

I believe it might not be that difficult to achieve this by leveraging public API of the go compiler.
https://github.com/golang/go/blob/23573d0ea225d4b93ccd2b946b1de121c3a6cee5/src/go/ast/resolve.go#L74
We already do something similar for formatting go code, checking for package errors will not be a lot of additional effort for better UX.

What is v4?

proto4, whenever that comes. Is there any official place to request features/fixes for the next major version or to file things for consideration when that conversation begins?

We already do something similar for formatting go code, checking for package errors will not be a lot of additional effort for better UX.

That's 100LOC to maintain for slightly better UX; I'm not convinced this is worth it. If there's anything to do here, it should be in protoc to at least print a warning that non-style compliant names are being used. The problem we're facing here is certainly not unique to Go.

proto4, whenever that comes. Is there any official place to request features/fixes for the next major version or to file things for consideration when that conversation begins?

In my opinion, the introduction of proto3 itself, give the pre-existing proto2 has been technically expensive to maintain and rollout. I'm doubtful there will ever be a proto4. Regardless, any discussion about proto4 should be at github.com/protocolbuffers/protobuf

The problem we're facing here is certainly not unique to Go.

This issue is more about how to handle conflicting cases that break go generated code. It is not about addressing all non-style-compliant code.
Case sensitivity is pretty unique to go. Almost every other language can generate service and method names as is and call it a day. They might not like the style of generated code, but it will work nevertheless.

github.com/protocolbuffers/protobuf

Thank you 😊

That's 100LOC to maintain for slightly better UX

I figured a better 2 LOC check.
conf := &types.Config{Importer: importer.Default()}
_, err = conf.Check("", fset, []*ast.File{fileAST}, nil)

Is it worth it now?

That snippet tells us that the code doesn't compile. Can you explain how that's better UX than the Go toolchain not compiling the code? To my knowledge, the go/types package doesn't return a distinguishable error for conflicting identifiers.

Codebases with multiple languages usually have a centralised step to generate code in multiple languages from proto files.
Right now, the code gen succeeds and breaks during import. Failing at build time will prevent such code from being released at all.
As an example, think of places where services are in other languages but also have generated go clients etc. They would release a new service before ever realising that the generated code will break in go.
The most common case I can think of is when people are switching from non-compliant code to compliant one.

Can you explain how that's better UX

Failing at build time and printing the error with a documentation link which explains this gotcha is much better than leaving people in the dark to discover on their own.
The crux is that a build time error would avoid a lot of work later.

I agree with @ofpiyush here. The earlier a break occurs in a complex build system, the better it is for everyone. We've been fighting with:
enum MyType {
  MY_TYPE_UNSPECIFIED = 0;
  name = 1;
  address = 2;
}

causing a name conflict between the generated const definition of:
const (
  MyType_MY_TYPE_UNSPECIFIED      MyType = 0
  MyType_name                     MyType = 1
  MyType_address                  MyType = 2
)

and the later generated definition of:
// Enum value maps for MyType.
var (
	MyType_name = map[int32]string{
		0:  "MY_TYPE_UNSPECIFIED",
		1:  "name",
		2:  "address",
	}
)

All of our .proto files are in a central repo that produces packages for several different languages, including go. The repo has pretty tight linting, but in this particular case the author of the above had a good reason for turning off UPPER_SNAKE_CASE enforcement on the MyType enum values, so the linter ignored it. The protoc build succeeded, even for go, but the generated .pb.go file contained a name conflict, which in turn broke several other project's builds. Having protoc-gen-go reject this due to the name conflict immediately would have been quite helpful.
If you're worried about "breaking the world", why not make the generation time conflict check @ofpiyush proposed a flag, perhaps  --go-opt=conflict-check=true, that defaults to off.

import the whole Go toolchain to reparse the code

We already do this to format the code.
https://github.com/golang/protobuf/blob/v1.4.3/protoc-gen-go/generator/generator.go#L21-L25
It is a 2 LOC check.

More ideally, anyone generating Golang protobuf code could just add a go test

That is not ideal, it is a very non-obvious requirement to put on one's user.
It would still somewhat be palatable it if we had precedence with saying "you need to run go fmt on generated code yourself"

The following is not meant to be a dig, just a reflection on the hilarious situation we're all in.  More to lighten the atmosphere on this thread than anything else:
Today protoc-gen-go says,

I'll give you code that you can't run, but at least it'll be formatted pretty 😅

import the whole Go toolchain to reparse the code

We already do this to format the code.
https://github.com/golang/protobuf/blob/v1.4.3/protoc-gen-go/generator/generator.go#L21-L25
It is a 2 LOC check.

More ideally, anyone generating Golang protobuf code could just add a go test

That is not ideal, it is a very non-obvious requirement to put on one's user.
It would still somewhat be palatable it if we had precedence with saying "you need to run go fmt on generated code yourself"

The following is not meant to be a dig, just a reflection on the hilarious situation we're all in.  More to lighten the atmosphere on this thread than anything else:
Today protoc-gen-go says,

I'll give you code that you can't run, but at least it'll be formatted pretty 😅

Closing as "working as intended". It's appropriate for us to the rely on the Go toolchain to reject generated code that has conflicts. In working in the protogen package recently, there a number of cases where I could perform checks that the Go toolchain itself is going to check for us. It won't be very maintainable to replicate every check that the Go toolchain itself performs in protogen.


Setup Cypress

Maybe add some small info to readme as well?

Added info to the readme. Will add more as we move forwards, I am not sure if we will use only Cypress or unit tests with an in memory DB for regression testing, it depends a bit where the functionalty to be tested is


currentinstance value is null for the bundled component

Version
3.0.0-beta.18
Reproduction link
https://github.com/anandkumarram/vue3lib
https://github.com/anandkumarram/vue3App
Steps to reproduce

in vue3lib -> run : npm run build:es -> it will generate vue3lig.esm.js (bundled using rollup-plugin-vue)
rollup.config.js : vue3lib\build\rollup.config.js
vue3lig.esm.js : vue3lib\dist\vue3lib.esm.js

in vue3App -> run : npm install --save ../vue3Lib && npm run serve.
I have used the vue3lib as a plugin in vue3App and used a component name "sample".

What is expected?
All Components loaded from bundle(vue3lib.esm.js) should have componentinstance value
What is actually happening?

currentinstance value is null in the Closure object.

runtime-core.esm-bundler.js?821d:36 [Vue warn]: onMounted is called when there is no active component instance to be associated with.
Lifecycle injection APIs can only be used during execution of setup(). If you are using async setup(),
make sure to register lifecycle hooks before the first await statement.

attached few debugged images for reference.

This is not a Vue's bug, the cause of the problem is that vue3lib installed vue itself and resolve the path to it, and vue3App also installed another vue and resolve the path to it. The currentInstance in these two Vue is not shared,
Just add the alias configuration in your vue3App/vue.config.js:
config.resolve.alias.set('vue$', resolve(__dirname, 'node_modules/vue'))

vue3lib shouldn't have vue listed as a dependency - it should be a peer dependency.

I took another look and this is because you are building it locally with linked Vue in the dependency tree, so webpack resolves vue for vue3lib based on its location. This will not happen in production if you list vue in vue3lib as a peer dep.

@HcySunYang @yyx990803 it's working now.. thanks for the suggestion..

Thank you very much... 12h trying to understand this issue. Solved!

Same issue has occurred while upgrading vue 2.6 -> 2.7.
And it has solved with this solution. Thanks a lot!
Below is my vue.config.js, hope to help to someone.
module.exports: {
    ...
    configureWebpack: {
        ...
        resolve: {
            alias: {
                ...
                vue: path.resolve('./node_modules/vue'),
            }
       }
}

my vue2.7/lib is umd , this webpack config dosn't work.
so I use props to reception vue2.7/app's this.$root.

@Nick87-xkk can you describe this more? What did you update to get this working with vue2.7?


Use CUDA unified memory for Random123 state

Description
This modifies how we allocate state variables for Random123 in GPU-enabled builds. This should simplify things, and enable use-cases like in #528 where we need to manipulate this state on the device from CPU code in ways that the existing API did not allow.
Because the state is now accessible from both CPU and GPU code, this also closes #345.
How to test this?
Build and run with/without GPU support enabled.
Test System

OS: BB5
Compiler: NVHPC 21.2
Version: master
Backend: CPU/GPU

Use certain branches for the SimulationStack CI
CI_BRANCHES:NEURON_BRANCH=master,

Codecov Report

Merging #595 (f8cc054) into master (9bd58f6) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #595      +/-   ##
==========================================
- Coverage   56.46%   56.45%   -0.02%
==========================================
  Files          99      100       +1
  Lines        8021     8030       +9
==========================================
+ Hits         4529     4533       +4
- Misses       3492     3497       +5

Impacted Files
Coverage Δ

coreneuron/utils/randoms/nrnran123.cpp
36.36% <ø> (-0.78%)
:arrow_down:

coreneuron/utils/randoms/nrnran123.h
100.00% <100.00%> (ø)

coreneuron/network/multisend_setup.cpp
81.45% <0.00%> (+0.07%)
: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 9bd58f6...f8cc054. Read the comment docs.

Retest this please

It was tested locally that channel-benchmark produces consistent results with/without --gpu in a GPU-enabled build.
Note that a bug in the NVHPC compiler version 21.3 and 21.5 means version 21.2 (or older?) or 21.7 (or hopefully newer!) must be used.

Replayed rxd-mpi tests and they passed - https://bbpgitlab.epfl.ch/hpc/coreneuron/-/jobs/38730 (in previous CI there was timeout)


'$' is not recognized as internal or external command

Quickstart > Step 4

"rnuc": "$(npm bin)/rnuc"

Any alternatives I could try?

The solution that I found:
Update from npm
Just switch package into rnuc


Titles are the wrong way round

This was opened 2 months ago by another user, but it is still wrong.
"To view the dependencies of a table" has the content switched with "To view the objects on which a table depends"

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

ID: d1d9a706-27a6-b00f-6e5b-3f7f548a2f4a
Version Independent ID: d99fd464-baea-24b8-30d7-2cbdb36981a8
Content: View the Dependencies of a Table - SQL Server
Content Source: docs/relational-databases/tables/view-the-dependencies-of-a-table.md
Product: sql
Technology: table-view-index
GitHub Login: @stevestein
Microsoft Alias: sstein

Just for further clarification - Under "To view the objects on which a table depends", there is the line of text "The following example returns the objects that depend on the table Production.Product. "  which alone shows that the titles are the wrong way round.  The text is correct for the SQL, it is just the titles that don't match.

@DenzilNewman -- thank you for your feedback.  I am looking into this article.

@stevestein -- Steve, please review private PR 14608 which will close this issue.

May I ask why this was closed.  It is really simple and definitely wrong, with only a need of an understanding of English to correct.
The title To view the objects on which a table depends
is then followed by the text
"The following example returns the objects that depend on the table Production.Product"
This has the opposite meaning of the title.
The text is correct, the title is not, some users will find this very confusing as they will be complete beginners.  I struggle to understand why it would take professionals so very long to review and correct such a glaring error.
Feel free to disregard this, however its pretty poor in my opinion as this is considered the "Official" source of information on the subject.  I can certainly see why Stack Overflow is the first port of call for most developers.

@DenzilNewman -- thank you for your feedback.  I updated the article with your suggestions, closed this issue, and the article is now live.

ah ok, had not updated when I looked.  I'll trust that its fixed now then.
Thank you.
On Tue, 26 May 2020 at 17:28, William Anton Rohm<EMAIL_ADDRESS>wrote:

@DenzilNewman https://github.com/DenzilNewman -- thank you for your
feedback. I updated the article with your suggestions, closed this issue,
and the article is now live.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/sql-docs/issues/4561#issuecomment-634133456,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGKGDZAPC7BKGKQQBRQUQTTRTPU4RANCNFSM4MIM4W3A
.


TypeError: Cannot read property 'setParent' of undefined

Describe the bug
When I'm importing a Button from proton-native, and rendering it the app crashes, with the error:
TypeError: Cannot read property 'setParent' of undefined.
To Reproduce
import { Button } from 'proton-native';

return (
    <App>
      <Window style={{ width: 700, height: 768, backgroundColor: 'white' }}>
        <View>
          <Text style={processStyle}>aksjdhahdjk</Text>
          <Button>Click</Button>
        </View>
      </Window>
    </App>
  );

Expected behavior
Button should be rendered with sucess.
Screenshots

Versions:

OS: Ubuntu
Version 19.04
Node version v12.14.1

Additional context
Add any other context about the problem here.

Also having the same problem on Arch linux and Node 12.14.1

Not sure why, but working from the examples I'm able to compile.

I'm obviously not the expert, but it looks like you may need to import { App, Button View, Text, Window } from 'proton-native' instead of just Button, to get the application running.

I'm obviously not the expert, but it looks like you may need to import { App, Button View, Text, Window } from 'proton-native' instead of just Button, to get the application running.

Thanks for the heads up, but everything is imported, it's just a snippet.

As seen here, Button takes no children. To pass the text to the button, you can use the title prop. I've added an error that should make this clearer in the future.


gci: update bugfix with two new tickets to explore

please merge.

I was wondering why they were pointing to Removing a BSP ;).

Tickets 2493 is already closed.

the tasks were already published they just never got merged into joel's gci_tasks repo.

Everything OK now?
On January 6, 2016 9:17:25 PM CST, Gedare Bloom<EMAIL_ADDRESS>wrote:

the tasks were already published they just never got merged into joel's
gci_tasks repo.
—
Reply to this email directly or view it on GitHub.

--joel

All OK now?
On January 6, 2016 8:52:28 PM CST, Aun-Ali Zaidi<EMAIL_ADDRESS>wrote:

I was wondering why they were pointing to Removing a BSP ;).
—
Reply to this email directly or view it on GitHub.

--joel


Pressing Enter in a TextEdit with prevent_default_event_handling: false inputs an "E"

Reproduction: https://github.com/aecsocket/bevy-egui-enter-bug
cargo run --target wasm32-unknown-unknown
fn main() {
    App::new()
        .add_plugins((
            DefaultPlugins.set(WindowPlugin {
                primary_window: Some(Window {
                    prevent_default_event_handling: false,
                    ..default()
                }),
                ..default()
            }),
            EguiPlugin,
        ))
        .add_systems(Update, ui)
        .run();
}
// ...
fn ui(mut egui: EguiContexts, mut text: ResMut<Text>) {
    egui::Window::new("Window").show(egui.ctx_mut(), |ui| {
        ui.add(egui::TextEdit::singleline(&mut text.0));
    });
}

This is probably a bug in an upstream dependency (maybe winit? egui?), but I'm not experienced enough with this stuff to know exactly which dependency is causing it.
https://github.com/mvlabat/bevy_egui/assets/43144841/96bbd067-6670-4234-a59a-0a4890904754

I believe this is no longer actual with the newer version of winit. But please let me know if it's still is.


fix: correct repo-id arg

Fixes: #4

This is great, I would add the --branch ${GITHUB_REF} so we also get the branch of the execution

Done!

The branch should name should be --branch ${GITHUB_REF##*/}
Otherwise, the ${GITHUB_REF} return the all path refs/heads/feature-branch-1 instead of `feature-branch-1.


Bot watches stream for drop that is impossible to get

[2022-01-20 17:49:18] [info] Found 45 pending campaigns. Watching https://www.twitch.tv/forhonorgame | Viewers: 9891 | Uptime: 1:00:00 WD Reveal Jan SC2 ██████████░░░░░░░░░░ 31 / 60 minutes
The campaign ends at 18:15

There's always a chance that the stream lasts a little longer than expected, or the campaign gets extended :)
But I guess I can add an option to not watch drops if it's not likely to be finished before the campaign ends.