[SPARK-48829][BUILD] Upgrade RoaringBitmap to 1.2.1

What changes were proposed in this pull request?
The pr aims to upgrade RoaringBitmap from 1.1.0 to 1.2.1.
Why are the changes needed?

The full release notes: https://github.com/RoaringBitmap/RoaringBitmap/releases/tag/1.2.0
The latest version has brought bug fixes and some improvements:
improve: Optimize RoaringBitSet.get(int fromIndex, int toIndex) https://github.com/RoaringBitmap/RoaringBitmap/pull/727
fix: add bitmapOfRange (non-static) in https://github.com/RoaringBitmap/RoaringBitmap/pull/728

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.
Was this patch authored or co-authored using generative AI tooling?
No.

org.apache.spark.MapStatusesConvertBenchmark
JDK 17: https://github.com/panbingkun/spark/actions/runs/9832998545
JDK 21: https://github.com/panbingkun/spark/actions/runs/9833002646

ready to go?

ready to go?

Yea, ready for review, thanks!

Merged into master. Thanks @panbingkun

Thank you, @panbingkun and @LuciferYang .


step 17 - "Enable app embedding user experience"

"Enable app embedding user experience" is no longer there. Is it the same as "Optimize embedding appearance"?

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

ID: d21a753e-4f2f-941f-8ec9-40891a5ebbe6
Version Independent ID: 63740fcb-c081-6225-9fc5-8600c03125fb
Content: Pass the current row as data context with an embedded canvas app - Power Apps
Content Source: powerapps-docs/maker/model-driven-apps/pass-current-embedded-canvas-app.md
Service: powerapps
GitHub Login: @aneesmsft
Microsoft Alias: matp

@notta-thing - thank you for your feedback. The article has been updated to reflect the current UI.
Closing issue.


docs(README): v1.12.0 release announce

Coverage remained the same at 99.855% when pulling 1df77f3efed6b415107fc7d341029ac63cca9663 on release-1.12.0 into 6da0e7a608675d0d5cbe858ad929a963d67633af on master.


Thoughts on adding an environment parameter to RustIO?

This would be somewhat like ZIO. I'd be happy to take an initial stab at it if you prefer. Some notes on types and type aliases can be seen here: https://github.com/bbarker/haskell-zio

Thanks for the idea, I’m replicating step by step ZIO to explore potential and limitations of the language to express pure Functional effects systems. Add environment is a possibility that I will explore once I cover first some topics that I have pending.Enviado desde mi iPhoneEl 25 may 2023, a las 18:23, Brandon Elam Barker @.***> escribió:
This would be somewhat like ZIO. I'd be happy to take an initial stab at it if you prefer. Some notes on types and type aliases can be seen here: https://github.com/bbarker/haskell-zio
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


uniform naming of http pool in test_connectionpool test module

Thank you for this, I've been wanting to do this for some time.


Clarification on opt_in_tracking()

Hello,
I am looking at the documentation of opt_in_tracking() https://mixpanel.com/help/reference/javascript-full-api-reference#mixpanel.opt_in_tracking
Could you clarify to me if the opt_in is enabled or disabled by default? What consequence does it have on what Mixpanel tracks or not?
In the application I am working on even though I see events getting sent to Mixpanel, I do often see the DISTINCT ID changing when I go to a different page and I was wondering if having opted in or not could be related to that.
Thank you

Hey, thanks for writing in. This could probably be more clear in our documentation. The default state of the SDK instance is neither opted-in or opted-out, and no behavior of the SDK will be restricted until an opt_out_tracking call is made. opt_in_tracking simply reverses opt-out and tracks an event that can be used as a record of opt-in.
Each of opt_in_tracking opt_out_tracking sets a flag (as a cookie or localStorage entry) that marks the current user as opted in our out. If you inspect your application storage in browser devtools you'll see this flag as __mp_opt_in_out_<PROJECT_TOKEN> equal to 1 (opted-in) or 0 (opted-out). This flag is not set when the SDK is initialized, so the initial state is neither opted-in or opted-out.
The exception to this would be if you pass opt_out_tracking_by_default: true during SDK init - then an opt_out_tracking call will be made internally during init and set the opt-out flag before any data is tracked. This is documented here https://mixpanel.com/help/reference/javascript#privacy

thank you @evnp ! Clear now


[Snyk] Upgrade browser-sync from 2.26.13 to 2.27.9

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade browser-sync from 2.26.13 to 2.27.9.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 11 versions ahead of your current version.
The recommended version was released a month ago, on 2022-03-15.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Access Restriction Bypass SNYK-JS-XMLHTTPREQUESTSSL-1255647
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Arbitrary Code Injection SNYK-JS-XMLHTTPREQUESTSSL-1082936
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Denial of Service (DoS) SNYK-JS-SOCKETIOPARSER-1056752
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Denial of Service (DoS) SNYK-JS-SOCKETIOPARSER-1056752
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Denial of Service (DoS) SNYK-JS-ENGINEIO-1056749
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Regular Expression Denial of Service (ReDoS) SNYK-JS-AXIOS-1579269
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Regular Expression Denial of Service (ReDoS) SNYK-JS-WS-1296835
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Regular Expression Denial of Service (ReDoS) SNYK-JS-WS-1296835
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Insecure Defaults SNYK-JS-SOCKETIO-1024859
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Information Exposure SNYK-JS-FOLLOWREDIRECTS-2332181
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Information Exposure SNYK-JS-FOLLOWREDIRECTS-2332181
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Server-Side Request Forgery (SSRF) SNYK-JS-AXIOS-1038255
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

Information Exposure SNYK-JS-FOLLOWREDIRECTS-2396346
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
No Known Exploit

Information Exposure SNYK-JS-FOLLOWREDIRECTS-2396346
686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: browser-sync

2.27.9 - 2022-03-15What's Changed

fix(cli): Where's the command help? fixes #1929 by @ shakyShane in #1945

A bug prevented the help output from displaying - it was introduced when the CLI parser yargs was updated, and is now fixed :)
Full Changelog: v2.27.8...v2.27.9

2.27.8 - 2022-03-13This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)
PR:

58ab4ab

Resolved Issues:

#1850
#1892
#1925
#1926
#1933

Thanks to @ lachieh for the original PR, which helped me land this fix

2.27.7 - 2021-10-27v2.27.7

2.27.6 - 2021-10-26v2.27.6

2.27.5 - 2021-07-27v2.27.5

2.27.4 - 2021-07-01v2.27.4

2.27.3 - 2021-06-26v2.27.3

2.27.1 - 2021-06-24This release adds a feature to address #1882
Sometimes you don't want Browsersync to auto-inject it's connection snippet into your HTML - now you can disable it globally via either a CLI param or the new snippet option :)
browser-sync . --no-snippet
or in any Browsersync configuration
const config = {
  snippet: false,
};
the original request was related to Eleventy usage, so here's how that would look
eleventyConfig.setBrowserSyncConfig({
  snippet: false,
});

2.26.14 - 2021-01-24

2.26.14-y.2 - 2021-01-24

2.26.14-y.1 - 2021-01-24

2.26.13 - 2020-10-17

    from browser-sync GitHub release notes

Commit messages

Package name: browser-sync

c30868a v2.27.9
9b5fcdc fix(cli): Where's the command help? fixes #1929 (#1945)
8840282 v2.27.8
58ab4ab more version bumps + github actions (#1940)
6e8d2b2 Merge pull request #1936 from lachieh/socket-io-upgrade
e909447 update browser-sync-client ts version
daa8cd0 restore test setting
3c5777a Upgrade to latest version of socket.io. Fixes #1847
a7c14c8 v2.27.7
40ebbd8 fixes #1916
e557aac v2.27.6
6976fe9 v2.27.5
8ba1c17 updated lockfile format
c99273c Merge pull request #1915 from iwt-philipzeh/fix/ua-parser-version-security
6648032 security-patches
c2bc05d Merge pull request #1738 from davezuko/patch-1
b8abf44 Merge pull request #1858 from arafalov/master
3084279 v2.27.4
d0c9c4c security patches
a4fd558 v2.27.3
910a9e1 v2.27.2
ebe0962 docs: added snippet option for website generation
a4aa8eb v2.27.1
3825dc6 v2.27.0

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

👷 Deploy Preview for optimistic-mahavira-71b58e processing.

Name
Link

🔨 Latest commit
808a0f55ba0a061e8300fc910cde110adba44e48

🔍 Latest deploy log
https://app.netlify.com/sites/optimistic-mahavira-71b58e/deploys/625a7acd5f325700097bbee7


Make ChannelPool::close to accept Promise

Sometimes I have to wait until ChannelPool::close ends, but there is no way right now.
I think it would be useful if I can pass a Promise to ChannelPool::close.
@normanmaurer What do you think about it?

@fratboy actually maybe ChannelPool::close should only return once it is done ?

@normanmaurer It is but I think it would be better we can be notified when underlying channel closing is done.

@normanmaurer I'll think about it again. Thanks.


New version OnlineStatsBase: 0.12.0

Registering: OnlineStatsBase
Repository: https://github.com/joshday/OnlineStatsBase.jl
Version: v0.12.0
Commit: 6970027eb61f5c965e62d96e5981323bb9ed0e4e
Proposed by: @joshday
Reviewed by: @joshday
Reference: https://github.com/joshday/OnlineStatsBase.jl/issues/6#issuecomment-485986219

Consider enabling TagBot to make sure the release is persistent in your repo, see https://discourse.julialang.org/t/ann-tagbot-creates-tags-and-releases-for-your-julia-packages-when-theyre-registered/23084


[App]: WSL error when following Job Launch Walkthrough

Current Behavior
Following the steps given in https://docs.wandb.ai/guides/launch/walkthrough, after queuing a job successfully on the web app, the agent receives the job but errors. A section of my cmd output shows:
wandb: launch: Launching run in docker with command: docker run --rm -e WANDB_BASE_URL=https://api.wandb.ai -e WANDB_API_KEY -e WANDB_PROJECT=launch-quickstart -e WANDB_ENTITY=[REDACTED] -e WANDB_LAUNCH=True -e WANDB_RUN_ID=ljwn6ne5 -e WANDB_USERNAME=[REDACTED] -e WANDB_CONFIG='{"epochs": 10}' -e WANDB_ARTIFACTS='{"_wandb_job": "[REDACTED]/launch-quickstart/job-source-launch-quickstart-train.py:latest"}' [REDACTED]__launch-quickstart__job-source-launch-quickstart-train.py:0333b4af
<3>WSL (2912) ERROR: CreateProcessEntryCommon:577: execvpe /bin/bash failed 2
<3>WSL (2912) ERROR: CreateProcessEntryCommon:586: Create process not expected to return

Expected Behavior
The job runs successfully on my local machine
Steps To Reproduce
Follow instructions at link
Screenshots
No response
Environment
OS: Windows 10
Browsers: Chrome Version 116.0.5845.96 (Official Build) (64-bit)
Version: wandb, version 0.15.5
wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3324
Additional Context
No response

Internal GitHub User commented:
Current Behavior
Following the steps given in https://docs.wandb.ai/guides/launch/walkthrough, after queuing a job successfully on the web app, the agent receives the job but errors. A section of my cmd output shows:
wandb: launch: Launching run in docker with command: docker run --rm -e WANDB_BASE_URL=https://api.wandb.ai -e WANDB_API_KEY -e WANDB_PROJECT=launch-quickstart -e WANDB_ENTITY=[REDACTED] -e WANDB_LAUNCH=True -e WANDB_RUN_ID=ljwn6ne5 -e WANDB_USERNAME=[REDACTED] -e WANDB_CONFIG='{"epochs": 10}' -e WANDB_ARTIFACTS='{"_wandb_job": "[REDACTED]/launch-quickstart/job-source-launch-quickstart-train.py:latest"}' [REDACTED]__launch-quickstart__job-source-launch-quickstart-train.py:0333b4af
<3>WSL (2912) ERROR: CreateProcessEntryCommon:577: execvpe /bin/bash failed 2
<3>WSL (2912) ERROR: CreateProcessEntryCommon:586: Create process not expected to return

Expected Behavior
The job runs successfully on my local machine
Steps To Reproduce
Follow instructions at link
Screenshots
No response
Environment
OS: Windows 10
Browsers: Chrome Version 116.0.5845.96 (Official Build) (64-bit)
Version: wandb, version 0.15.5
wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3324
Additional Context
No response

@OfficeLlama Do you reach this same error when updating your SDK version to our latest? Additionally, did you create a Starter queue and is this where you're running into the error? I.e. does this behavior occur when you run something like:
wandb launch-agent -e <entity-name> -q <queue-name>

Uma Krishnaswamy commented:
Hi @OfficeLlama, since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!

Hi @OfficeLlama, since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!


PLT-9028: Write a constitution script that checks txFeePerByte, txFeeFixed and utxoCostPerByte

Initial version, no tests in this PR.
FIRST take a look at the README.md and then in the json files, before continuing to the validators.
Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[ ] Changelog fragments have been written (if appropriate)
[x] Relevant tickets are mentioned in commit messages
[x] Formatting, PNG optimization, etc. are updated

PR

[ ] (For external contributions) Corresponding issue exists and is linked in the description
[x] Targeting master unless this is a cherry-pick backport
[x] Self-reviewed the diff
[ ] Useful pull request description
[x] Reviewer requested

As we discussed, I think the following approach should at least be implemented, since it seems easy to implement, and even if it is not the most performant approach it is at least useful for testing.

Read the JSON file into [(ParamId, (LB, UB)], ordered by ParamId, in TH. This is the only part that needs TH.
In the script, for each (ParamId, NewValue), check the NewValue against the (LB, UB) in the previous map.

As we discussed, I think the following approach should at least be implemented, since it seems easy to implement, and even if it is not the most performant approach it is at least useful for testing.

Read the JSON file into [(ParamId, (LB, UB)], ordered by ParamId, in TH. This is the only part that needs TH.
In the script, for each (ParamId, NewValue), check the NewValue against the (LB, UB) in the previous map.

This is more or less what the Unsorted/NonStatic version does. But with the added benefit that the interpretation of minvalue and maxvalue predicates is not hardcoded (to >= and =< resp.) but is configurable in the defaultPredMeaningUnresolved mapping. Furthermore minvalue and maxvalue are  (both or individually) optional (during parsing and runtime checking) . So for example you can leave some range unbounded.

Moved

@bezirg moved where?


Refactor/transactor status

I have refactored some parts of the transactor/status class.
Also I have removed some unreferenced methods/code from the class. I removed the options on the to_xml method named 'exclude_application' and 'exclude_user' because are not referenced/set anywhere on the code and seem to be legacy options (it seems were added in commit 3424475acea289f715e7a876a6a880e3f799f464). Maybe @unleashed / @mikz that have been longer with the codebase can confirm this.
Thank you.

Regarding the use of  Nokogiri::XML::Builder, I agree with you @eguzki
The idea is to move this code out of transactor/Status.rb in another PR, in order to decouple the data representation from the model, along with trying to generalize the data representation to be compatible with other formats (like json).

bors r=@eguzki,@davidor,@mikz,@unleashed

bors r=@eguzki,@davidor,@mikz,@unleashed

last try, otherwise it is clear that some powerful, higher order entity does not want this merged, and if so better not to annoy them (a la tercera va la vencida)
bors r=@eguzki,@davidor,@mikz,@unleashed


joe-mai-avax and joe-ampl-avax

AMPL-AVAX
Vault: 0x936d1f2ECF2C911Efba16BCBB9F205184d827986
Strategy: 0xCE069a70925409DB10F5df617D947b6b4A4A4202
Want: 0x230c4aD11510360aD0DB564a889C33559A959487
MAI-AVAX
Vault: 0x41e6612044AeDDeB19102304775cA39c204Ad030
Strategy: 0xa45dd07dC52caCe34185298187E7d399717F2550
Want: 0x23dDca8de11eCcd8000263f008A92e10dC1f21e8

API still needs to be merged first

validate?

validate?

my bad, validated and then added a dumb space. works now.


Add Rocky Linux 8 and Ubuntu Focal to example images

Adding GenericCloud images would be useful too.

Adding GenericCloud images would be useful too.

True, could be a separate PR.
Ideally we'd have some CI to test these examples.


error while trying to bootstrap vcpkg

I tried the method for building with VS 2017. and I am able to complete first step of cloning the repo, but it fails in second step when I try to bootstrap. and I have the following error.  the image for error is attached. just for reference of the method I used, please see the issue #136

Hi @touseefbsb!
This error indicates that for the Windows SDK selected by Vcpkg (the latest one installed on your machine), you've probably only installed the UWP component, not the desktop windows component. This is most easily fixed by just launching the VS 2017 installer and ensuring that the optional component "Windows 10 SDK (10.x.y.z) for Desktop C++" is selected under the "Desktop development with C++" section on the right.

yeah thanks that solved the problem


Rewrite, Proxy: read configs in descending order of request path length.

This is a simple but working approach to processing longer paths before shorter ones.
Right now, caddy will not process the second rewrite config except the configuration is modified to put the /blog config first. Similar situation occurs in Proxy and possibly other middlewares. This PR will allow /blog to be processed first irrespective of the config order.
rewrite { ... }
rewrite /blog { ... }

The approach can be changed later, it is only a matter of modifying Configs.Add function.

This is a good start / PoC, but I want to explore the possibilities here a little more, since I think we'll need a more universal solution along these lines, that isn't limited to just certain middlewares (consistency will be our friend).

Yeah. I am actually gonna close this PR.

Is this PR still relevant? I just submitted the patch for proxy that does something similar.

That is fine. I'm all for a working solution, not necessary my solution. 👍

Oh, gotcha. I mean, is this fix still needed for rewrite? I did it for proxy but wasn't sure if rewrite needed it too. Anyway, if you find that it does, the solution for proxy (which was a PR) was pretty straightforward.

It is needed and definitely gonna take advantage. Thanks for the suggestion.


NullPointerException in some case

io.camunda.zeebe.spring.client.bean.MethodInfo#getParameters and io.camunda.zeebe.spring.client.bean.MethodInfo#getParametersFilteredByAnnotation methods can throw a NullPointerException when org.springframework.core.LocalVariableTableParameterNameDiscoverer#getParameterNames(java.lang.reflect.Method) returns null

Hi @wallaroo - thanks for raising the issue. Do you know in which situations this can be null? Trying to understand the root cause.

Hi @berndruecker, as mentioned by @wallaroo, the fix in #462 doesn't actually address why L71 returns a null array.  We have now had two support tickets for this issue.  Is it possible that it is not thread safe to use LocalVariableTableParameterNameDiscoverer#getParameterNames as a static class and their needs to be a synchronized block around L71?

Hi @daniel-ewing, maybe one of the support tickets is from us. We are now experiencing the same problem in the cluster. Locally there is no problem, in the AWS EKS cluster we get an incident with the following error message every time a worker is started:
java.lang.NullPointerException: Cannot load from object array because "parameterNames" is null
  at io.camunda.zeebe.spring.client.bean.MethodInfo.getParameters(MethodInfo.java:75)
  at io.camunda.zeebe.spring.client.jobhandling.JobHandlerInvokingSpringBeans.handle(JobHandlerInvokingSpringBeans.java:46)
  at io.camunda.zeebe.client.impl.worker.JobRunnableFactory.executeJob(JobRunnableFactory.java:44)
  at io.camunda.zeebe.client.impl.worker.JobRunnableFactory.lambda$create$0(JobRunnableFactory.java:39)
  at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
  at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
  at java.base/java.lang.Thread.run(Thread.java:833)

We are currently using SpringBoot 3.1.4, locally OpenJDK 20, in the cluster probably Correto, Camunda 8.2.13 and Spring-Zeebe 8.2.4.

@1nb0und can you have a look? I know you mentioned digging into SpringBoot version compatibility today.

Hi, we also encountered this issue while trying to upgrade from Spring Boot 3.1.5 to 3.2.0 and therefore from spring-boot-starter-camunda from 8.3.1 to 8.3.4. We can reproduce this issue in our process tests and it is currently preventing us from updating to Spring Boot 3.2.0.

@sam0r040 Can you put some stacktrace that you were getting?

Sure:
io.camunda.zeebe.client.job.worker       : Worker schrittJobWorker#handle failed to handle job with key<PHONE_NUMBER>685282 of type ****, sending fail command to broker
java.lang.NullPointerException: Cannot load from object array because "parameterNames" is null
	at io.camunda.zeebe.spring.client.bean.MethodInfo.getParameters(MethodInfo.java:72) ~[spring-client-zeebe-<IP_ADDRESS>.jar:<IP_ADDRESS>]
	at io.camunda.zeebe.spring.client.jobhandling.JobHandlerInvokingSpringBeans.handle(JobHandlerInvokingSpringBeans.java:48) ~[spring-client-zeebe-<IP_ADDRESS>.jar:<IP_ADDRESS>]
	at io.camunda.zeebe.client.impl.worker.JobRunnableFactoryImpl.executeJob(JobRunnableFactoryImpl.java:45) ~[zeebe-client-java-8.3.4.jar:8.3.4]
	at io.camunda.zeebe.client.impl.worker.JobRunnableFactoryImpl.lambda$create$0(JobRunnableFactoryImpl.java:40) ~[zeebe-client-java-8.3.4.jar:8.3.4]
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[na:na]
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[na:na]
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[na:na]
	at java.base/java.lang.Thread.run(Thread.java:840) ~[na:na]

The error is happening because MethodInfo.getParameters.handle is depending on StandardReflectionParameterNameDiscoverer spring bean. And this bean requires the parameter names to be left alone during compilation.
Simple workaround is to use compileArgs -parameters for javac.
tasks.named('compileJava').configure {
    options.compilerArgs = ['-parameters']
}

@backslash47 is correct. The issue can be solved by specifying of javac option "-parameters". In IntelliJ it can be done by by Settings > Build, Execution, Deployment > Compiler > Java Compiler > Additional command line parameters (as mentioned in https://stackoverflow.com/questions/39217830/how-to-use-parameters-javac-option-in-intellij).

@wallaroo

Can you confirm if this solves your issue?
What Spring Boot version were you using?

It appears we encountered this issue when Spring Boot in this project was baselined to 3.2 and here are the PRs associated with it
https://github.com/camunda-community-hub/spring-zeebe/pull/512
and the corresponding docs for the new flag has been added
Thank you @backslash47  and @janmas

I can confirm that enabling method parameters metadata via the -java-parameters flag for the Kotlin compiler fixes the issue @sam0r040 described. Thanks!

The error is happening because MethodInfo.getParameters.handle is depending on StandardReflectionParameterNameDiscoverer spring bean. And this bean requires the parameter names to be left alone during compilation.
Simple workaround is to use compileArgs -parameters for javac.
tasks.named('compileJava').configure {
    options.compilerArgs = ['-parameters']
}

where do we specify this in eclipse? anyone?
Thanks

@MMusaTR
It can be put into pom.xml if using maven.
see https://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html

@MMusaTR It can be put into pom.xml if using maven. see https://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html

I'm using gradle, I've specified following in build.gradle but still getting the NPE -
tasks.withType(JavaCompile) {     options.compilerArgs << '-parameters' }

@MMusaTR did you try following?
tasks.withType(JavaCompile) { options.compilerArgs.add("-parameters") }

I've also seen that NPE thrown in my Java client (spring-client-root v 8.4.0). It would be helpfull to detect faulty java class code ahead before it comes to NPE. That way some meanigfull error message could be thrown instead of NPE.

Fix provided in docs (add -parameters as compiler option) + error happens during init now


Undoing the PTGS additions just added

The expanded PTGS that was recently added is appreciated, but it's not ready yet. The added rows are edge cases used in only a fraction of games, but they dominate the sheet now and take up way too much space. Until they can be hidden in some way (drop downs perhaps?), I think we should stick to the original PTGS.

@LeeRhodes Pinging you for awareness.  I'm going to merge this in and revert the changes, I believe @GeneralPith is correct in their assessment of the situation, if the tracks were optional / toggle-able in some way that would be ideal.

Yep I agree. The method I was thinking of was simply have some buttons that can toggle them when needed.


error: panic: runtime error: slice bounds out of range

Describe the bug
Our core library is quite large and uses a lot of dynamic imports, but up until recently has worked well in Stackblitz, even if the build took a little bit.
Recently, during the build step, we get error similar to this in the terminal:
✘ [ERROR] panic: runtime error: slice bounds out of range [:-4294967295] (while printing<EMAIL_ADDRESS>
  linker.go:5548 +0x84

Error: Build failed with 42 errors:
error: panic: runtime error: slice bounds out of range [:-4294967295] (while printing<EMAIL_ADDRESS>error: panic: runtime error: slice bounds out of range [:-4294967295] (while printing<EMAIL_ADDRESS>error: panic: runtime error: slice bounds out of range [:-4294967295] (while printing<EMAIL_ADDRESS>error: panic: runtime error: slice bounds out of range [:-4294967295] (while printing<EMAIL_ADDRESS>error: panic: runtime error: slice bounds out of range [:-4294967295] (while printing<EMAIL_ADDRESS>...
    at failureErrorWithLog (/home/projects/github-9i57jp/node_modules/esbuild/lib/main.js:1641:15)
    at eval (/home/projects/github-9i57jp/node_modules/esbuild/lib/main.js:1049:25)
    at eval (/home/projects/github-9i57jp/node_modules/esbuild/lib/main.js:1517:9) {
  errors: [Getter/Setter],
  warnings: [Getter/Setter]

It's not always the same modules, it can vary per run.
These demo apps do work locally though.
Link to the blitz that caused the error
https://stackblitz.com/edit/github-9i57jp-83iubh?file=main.js
Steps to reproduce
Happens on build
Expected behavior
Normally a dev build on Stackblitz could take up to a minute.
Here is a sample from our previous release that worked (takes a minute or so to load): https://stackblitz.com/edit/vitejs-vite-hg4aeh?file=main.js
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform

OS: [Mac OS]
Browser: [Chrome, Firefox]
Version: [121.0.6167.85 , 122.0]

Additional context
I thought it might be Vite related since the error mentions esbuild, so  tried vite 5.1 beta, same issue. I had some luck with vite 5.0.0-beta.13, but it wasn't consistent, sometimes it worked, sometime I would get the out of bounds error.

Hey @odoe ! :wave: Thanks for the report!
This error seems to be generated by esbuild and I could not find an older version of webcontainer nor esbuild where this error wouldn't eventually appear. I did observed the same as you, which is that it sometimes worked.
I think we need to investigate more, it might still be an issue on our end.


How do I check what floating point precision the model is using?

Is there a way for me to check the precision of the weights the model is using when doing inference?
I.e., I'd like to know if the model is using FP16 weights, or bfloat16. (And if there is a way for me to force the model to maybe use bfloat16?)

Eh, but if you are using AutoGPTQ to load the quantized models for inference then they would be 8, 4, 3 or 2 bit.
If you use AutoGPTQ to quantize the settings are saved in quantize_config.json alongside the model.

Currently, if you use .from_quantized, the dtype of quantized modules are specified in quantize_config.json, others are in fp16; if you use .from_pretrained, dtype will be fp16 or bf16 that is automatically specified interally, by using torch.cuda.is_bf16_supported()


How can I get the normal from the SDK or realsense-viewer

Required Info

Camera Model
{  D435i }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) &ubuntu 16.04

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC

SDK Version
2.29

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>
Hi, I want to get the normal of each point , how can I get the normal from the SDK or realsense-viewer, could you show me an example?The export_to_ply generate the mesh file , how can I get the raw point cloud, I mean each point from the depth map ,RGB and normal information. I think it is different from the mesh. The mesh is cacluated by the some surface algrithm. Vertices dosent equal to the raw point. Am I right?
This may relate to my issue.
#4906

Upcoming release of the RealSense Viewer is going to include an option to include normals in PLY exporter, but generally speaking, I would export PLY and calculate normals externally using MeshLab.

Hi,@dorodnic
Compute normal of each point by meshlab or cloudcompare is pretty slow, especially when the point cloud is dense. I think some stereo algorithm ,like patchmatch, compute normal and depth simultaneously.  I guess the normal calculation is done by the VPU of D400. When can I get this function? Dose the development branch have include this function yet?
I find #4906 have been approved.
Thanks.

As you can see by inspecting #4906 (specifically here) normals are calculated in the viewer and not on the D400's VPU. This is why we recommend using Meshlab or similar as their code is likely more optimized for calculating vertex normals on large meshes

@lramati
Thanks

Please let us know if further assistance is needed for this topic.
Thank you.


add support for additional kwargs to the ClientError

Codecov Report

Merging #13 (6b8f71d) into master (feab003) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #13   +/-   ##
=======================================
  Coverage   94.19%   94.19%
=======================================
  Files          12       12
  Lines         947      948    +1
  Branches      169      169
=======================================
+ Hits          892      893    +1
  Misses         30       30
  Partials       25       25

Impacted Files
Coverage Δ

cnct/client/exceptions.py
85.71% <100.00%> (+1.09%)
: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 feab003...6b8f71d. Read the comment docs.

Codecov Report

Merging #13 (6b8f71d) into master (feab003) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #13   +/-   ##
=======================================
  Coverage   94.19%   94.19%
=======================================
  Files          12       12
  Lines         947      948    +1
  Branches      169      169
=======================================
+ Hits          892      893    +1
  Misses         30       30
  Partials       25       25

Impacted Files
Coverage Δ

cnct/client/exceptions.py
85.71% <100.00%> (+1.09%)
: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 feab003...6b8f71d. Read the comment docs.


Merge upstream into master

Trial PR to merge upstream/master into master branch.

Some checks failed. Please fix and resubmit.
checkpatch (informational only, not a failure)
-:323: WARNING:LEADING_SPACE: please, no spaces at the start of a line
#323: FILE: include/net/socket.h:850:
+    char ifr_name[IFNAMSIZ]; /* Interface name */$

- total: 0 errors, 1 warnings, 358 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Your patch has style problems, please review.

NOTE: Ignored message types: AVOID_EXTERNS BRACES C99_COMMENT_TOLERANCE CONFIG_EXPERIMENTAL CONST_STRUCT DATE_TIME FILE_PATH_CHANGES MINMAX NETWORKING_BLOCK_COMMENT_STYLE PREFER_KERNEL_TYPES PREFER_SECTION PRINTK_WITHOUT_KERN_LEVEL REPEATED_WORD SPDX_LICENSE_TAG SPLIT_STRING VOLATILE

NOTE: If any of the errors are false positives, please report
      them to the maintainers.

Device tree (internal test error)
module 'testdtlib' has no attribute 'run'

Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages.

Some checks failed. Please fix and resubmit.
checkpatch (informational only, not a failure)
-:323: WARNING:LEADING_SPACE: please, no spaces at the start of a line
#323: FILE: include/net/socket.h:850:
+    char ifr_name[IFNAMSIZ]; /* Interface name */$

- total: 0 errors, 1 warnings, 358 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Your patch has style problems, please review.

NOTE: Ignored message types: AVOID_EXTERNS BRACES C99_COMMENT_TOLERANCE CONFIG_EXPERIMENTAL CONST_STRUCT DATE_TIME FILE_PATH_CHANGES MINMAX NETWORKING_BLOCK_COMMENT_STYLE PREFER_KERNEL_TYPES PREFER_SECTION PRINTK_WITHOUT_KERN_LEVEL REPEATED_WORD SPDX_LICENSE_TAG SPLIT_STRING VOLATILE

NOTE: If any of the errors are false positives, please report
      them to the maintainers.

Device tree (internal test error)
module 'testdtlib' has no attribute 'run'

Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages.


About 3D-Attention-pytorch

hello，Thank you for your contribution. Is there a pytorch version?

Unfortunately, there is no version of pytorch available at the moment. Maybe there will be one in the future.


Support only Vertical tortoise

Currently, tortoise needs to have at least one Horizontal.
But, people may want to have tortoise with only Vertical.

Not yet needed actually. I'll reopen if it's really needed.

Let's add the test case for this in the controller test.


[Windows] not work in python ver 2.x.x

because of python-prompt-toolkit : https://github.com/jonathanslenders/python-prompt-toolkit/issues/86
But, It works well when using Python over 3.4.x.
You'd better change Readme.rst (https://github.com/awslabs/aws-shell#supported-python-versions).

Thanks for the catch, I'll get the README updated.

Do you guys see a problem with aws-shell on your system with Python 2.x?  The ticket referenced https://github.com/jonathanslenders/python-prompt-toolkit/issues/86 seems to indicate it's not easy to reproduce.
For aws-shell I've done a fair amount of testing on Win 10 64 bit with Python 2.7.6 32 bit and don't see any problems.
SAWS is also built on prompt_toolkit and I haven't seen any related issues logged against it.  On Windows 7 64 bit and Windows 10 64 bit I haven't seen any problems either after much testing.

When I first tried this last week, I got the traceback from https://github.com/jonathanslenders/python-prompt-toolkit/issues/86.
Today, I just tried it again and it worked (I guess that's the hard to repro part).  Windows 2012 64 bit EC2 instance using powershell.  I used  the latest python 2.7.11 and it worked for me.
I think I can improve the installation instructions for windows users but I think I'll close https://github.com/awslabs/aws-shell/pull/77

Sounds good :+1:


Add Chameleon PDA

About the PR

This PR adds the Chameleon PDA, a PDA that has Chameleon capabilities.
The Chameleon PDA is added to the Thief's Chameleon Kit and the filled Chameleon Backpack.
PDAs also no longer shows the name of the person it spawned on.
Requires https://github.com/space-wizards/RobustToolbox/pull/5324
Why / Balance

The Chameleon PDA is basically a necessity for any disguise to pass any amount of inspection, and allows for more advanced disguises for things such as ERT and CentCom. This will also allow StealthOps Nukies to much more convincingly blend in with crew instead of getting a Clown PDA or wearing the Agent ID without a PDA.
Since the Chameleon PDA does not come with an "Owner", to keep players from metagaming it that line in the UI has been removed. We already have IDs for identification, PDAs having a unique unmodifiable name set when looking at the UI is overkill.
Technical details

PdaSystem visuals have been moved over to PdaVisualizerSystem, and the state uses AppearanceData instead of a component property.
Chameleon clothes now also copies AppearanceData from the prototype it is copying.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: Added Chameleon PDA, found in the Thief & Uplink Chameleon Kit!
remove: Removed names from PDAs.

Maybe it's reasonable decision to remove name from PDA now, but i think it's better to make it like in ss13, when you can overwrite PDA owner just by inserting ID in it

Maybe it's reasonable decision to remove name from PDA now, but i think it's better to make it like in ss13, when you can overwrite PDA owner just by inserting ID in it

if you can overwrite the PDA owner by putting an ID in it then whats the point of having an owner

Maybe it's reasonable decision to remove name from PDA now, but i think it's better to make it like in ss13, when you can overwrite PDA owner just by inserting ID in it

if you can overwrite the PDA owner by putting an ID in it then whats the point of having an owner

Dunno, but in ss13 it works that way. Maybe there using in PDA chat system. They have special bomb cartridges that can be activated with PDA message.

Maybe it's reasonable decision to remove name from PDA now, but i think it's better to make it like in ss13, when you can overwrite PDA owner just by inserting ID in it

if you can overwrite the PDA owner by putting an ID in it then whats the point of having an owner

Lets say you take out your ID from the pda (for example teslaloose) and throw it away, then someone who randomly picks it up can tell who owned the PDA. Would be useful for detectives and also bringing back the PDA to the right owner.

having a button in settings to set owner to current id would be nice yes

Lets say you take out your ID from the pda (for example teslaloose) and throw it away, then someone who randomly picks it up can tell who owned the PDA. Would be useful for detectives and also bringing back the PDA to the right owner.

I have done something similar to this when playing as Detective, but it is largely one of those things that can be solved by going ";Hey, any Chef who lost their PDA?" or just turning the PDA in to HoP.
Imo the use of a named PDA without an ID is a very niche usecase and I'd hate for people to use it to metagame chameleon PDAs.

Couldn't you just make Cham. PDAs apply owner name to them? This seems like a convoluted work around to address powergaming. And if you are at a point where people can access your PDA you're kind of already screwed as a traitor.

i have personally been metagamed by a pda not having my name on it, the owner field as it is in master is just a metagaming feature. some kind of measure should be possible to change it, ideally keeping it since it does have innocent uses stated previously

Couldn't you just make Cham. PDAs apply owner name to them? This seems like a convoluted work around to address powergaming.

 Or a Syndie trying to disguise yourself as someone else?
Additionally the point of Chameleon items requiring wearing to be discovered is to make it more difficult to detect them at a surface inspection. For example if Sec does not suspect you have No-Slips or other Chameleon clothes they won't take it away from you after releasing you from the brig. Same case here.

i have personally been metagamed by a pda not having my name on it, the owner field as it is in master is just a metagaming feature. some kind of measure should be possible to change it, ideally keeping it since it does have innocent uses stated previously

While I agree that the name can be used, I also think that the impact of its removal would be minor. It's right now the go-to way to identify an ID-less PDA, but if it didn't exist I doubt people would find the addition necessary since there are other ways to return a PDA to its rightful owner.

Requiring a manual change of the PDA name (even if it is just a button press) adds an unnecessary step to a disguise, especially since 99 times out of 10 your ID will be inside the PDA anyways. Unless there is a common usecase for using the name that the ID can't fulfill, I don't see much reason to keep it around.

i think having the ID name visible on the PDA is good. It helps with identifying who it belongs to at a glance without being completely set in stone. Having it be completely fixed has obvious problems but i think that inheriting the ID name is a good solution.

i think having the ID name visible on the PDA is good. It helps with identifying who it belongs to at a glance without being completely set in stone. Having it be completely fixed has obvious problems but i think that inheriting the ID name is a good solution.

The ID name still shows as long as the ID is inserted - I really don't think that there are many instances where a PDA is found without an ID where not having the name would cause difficulties.

It is the PDA of a head or single employee job. Immediately identified.
It is the PDA of a department. Ask over the intercom if anyone is missing it. No one responds? Hand it in to HoP.
It is the PDA of a passenger. If no one responds over radio then all they'll really lose is their Notes app notes since they can get a new PDA from HoP.

in the case of some random passengers pda being lost, it should just display the last id card as the owner. no clicking needed it just automatically does it on on insertion

in the case of some random passengers pda being lost, it should just display the last id card as the owner. no clicking needed it just automatically does it on on insertion

While I find it a bit unintuitive, I can't really argue that this suggestion doesn't solve both the metagaming and finding-pda's-owner issue. I'll look into implementing it.

Deleting owner's name now maybe is solution, because PDA is now slightly useless. Now PDA is just ID card holder with crew manifest inside it, when in SS13 it's useful device when you login with your id card. In my opinion, deleting owner name won't affect gameplay in general, but the addition of the ability to imprint ID information to PDA is looks better.

in the case of some random passengers pda being lost, it should just display the last id card as the owner. no clicking needed it just automatically does it on on insertion

I think that automatic owner change is not that good as manual. I think there will be some situations where you need to hide your id in someone PDA, but you don't want to change it's name for some reason.

I think that automatic owner change is not that good as manual. I think there will be some situations where you need to hide your id in someone PDA, but you don't want to change it's name for some reason.

PDAs already show the ID info (including name) separately from the PDA owner name. You can't hide your ID in another's PDA even if the owner name is different.

I think that automatic owner change is not that good as manual. I think there will be some situations where you need to hide your id in someone PDA, but you don't want to change it's name for some reason.

PDAs already show the ID info (including name) separately from the PDA owner name. You can't hide your ID in another's PDA even if the owner name is different.

I didn't mean examine text. If i understand deltanedas correctly, he want PDA to change it's owner automatically when ID card inserted in PDA. In my opinion manual owner change is more flexible in different IC sutiatuions

New behavior: The PDA updates its owner name upon a new ID being inserted. That way it still shows it if the ID is removed, but you can overwrite it with another ID.

Added a fix that keeps Agent IDs from being turned into PDAs, and removed duplicate PDAs & IDs from the chameleon menu, and removed admin PDA/ID

Added a fix that keeps Agent IDs from being turned into PDAs, and removed duplicate PDAs & IDs from the chameleon menu, and removed admin PDA/ID

Admin ID is the only one with syndicate, centcom, and nukie access. Need it for access changes through UI.

Added a fix that keeps Agent IDs from being turned into PDAs, and removed duplicate PDAs & IDs from the chameleon menu, and removed admin PDA/ID

Admin ID is the only one with syndicate, centcom, and nukie access. Need it for access changes through UI.
Oh wait, did you mean remove it from Cham. Menu? Right, reading comprehension.

Ya sorry it was a bit unclear with how I wrote it; they're simply removed from the Chameleon menu, to prevent admin impersonation. The real PDA/ID remains as-is

is this still being worked on?

so whats stopping this from being merged, people using chameleons and not having a pda is by far the most common way to metagame chameleon outfits. we really need this


Scholarly 1.7.3 and 1.7.4 are not on PyPI

Describe the bug
Scholarly 1.7.3 and 1.7.4 are not on PyPI.

1.7.3 is on PyPI: https://pypi.org/project/scholarly/1.7.3/
1.7.4 is not, since I missed updating the setup.py
1.7.5 is now the latest release and is on PyPI: https://pypi.org/project/scholarly/1.7.5/


Feature/conditional row stacking

Note - in the example above, the stack-item elements would be arranged in a column, each at full width when the viewport is smaller than the large breakpoint

LGTM


Roll Flutter Engine from 25d773ea90c4 to cc9fc15bd53e (1 revision)

https://github.com/flutter/engine/compare/25d773ea90c4...cc9fc15bd53e
2024-04-19<EMAIL_ADDRESS>Roll Skia from ca5481ebd0fb to 7ad507eca0bd (2 revisions) (flutter/engine#52249)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jsimmons@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Configurable right nav tabs can be authored [#167679646]

Changes to hide right-nav look good.  Not sure if we also want to worry about reclaiming that extra space for the single-workspace div or other divs that might take advantage of the extra space when there are 0 tabs.

I went ahead and added code to reclaim the space for the single-workspace when there are no right-nav tabs. It won't handle the case where there are tabs defined but some of them aren't visible temporarily (e.g. only showing the My Work tab, which isn't presented to ghost users), but arguably that's the right UI. It also won't work for the comparison view, but since the right-nav tabs are the way we get to the comparison view that may not matter either. In any case, I'm going to vote that this is good enough for now. 😉

I agree!  Let's get it in!


Resolve magic on sdk

Amusing!!!! I edited your question with the answer.
Yes it is, duplicated.  The target doesn't work for restore, and so I have now removed it.
Yeah a new preview ValueTuple package will be released tomorrow more interestingly ValueTuple has been folded into System.Runtime/mscorlib on the desktop and .net standard 2.0.  And so we should probably protect against referencing it on those platforms.  It's going to have a new assembly version as well :-(
It's a bit irritating that we updated it, we should have left it alone until desktop 4.7 and netstandard 2.0 were widely adopted.


Create catch-all ACLs for transactional and idempotent producer

Q
A

Bug fix?
yes

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets
fixes #365 and #348

License
Apache 2.0

What's in this PR?
During creation of write ACLs also create two more:

cluster level ACL enabling idempotent writes
TransactionId level ACL enabling write for all transaction ids

Additional context
I don't see any harm in enabling idempotent writes in all cases. However support for transaction Ids is quite simplistic - it just allows all of them. If this is good enough or if there should be ability to enable specific transactionIds in KafkaUser CRD is something for discussion.
Checklist

[x] Implementation tested
[x] Error handling code meets the guideline

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

Thanks for your PR, We don't think it is a good idea to enable idempotent writes in all cases as user should have control whether they want to enable it or not. The same true for transaction Ids as well.
It allows specific access to Kafka which should not be granted to all producers by default. Since there is no changes made to the CRD, the users will lack the knowledge that this right is provided.
To support it properly we need to rework the complete KafkaTopic CRD. Which is not on the near future roadmap of the operator. We are happy to get a PR or discuss the ideas how to do it.
The next Supertubes release will ship advanced ACL handling that allows access to all Kafka ACLs declaratively through custom resources.

I agree about transaction ids, however I don't understand why idempotent writes need any special ACLs in the first place and what kind of possible attack scenario it allows.
As for your remark about supertube: does it mean that management of Kafka ACLs will move from KafkaUser CRD to something else handled by Supertubes? If yes, is it going to be still possible to use kafka-operator without supertubes?

We don't want to grant any right to the user automatically which is not required specifically.
To answer your second question:
No KafkaUser CRD will stay and will support all the features which are available right now in the operator. All I was saying is Supertubes will provides a more fine grained ACLs support with Kubernetes RBAC integration.


[test] Make parameters loggable in Amber and Gromacs tests

I have also aligned the implementation of the Amber library test with that of Gromacs.

Codecov Report

Merging #2449 (951f4a6) into master (050ef43) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2449   +/-   ##
=======================================
  Coverage   85.71%   85.71%
=======================================
  Files          56       56
  Lines       10536    10536
=======================================
  Hits         9031     9031
  Misses       1505     1505

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 050ef43...951f4a6. Read the comment docs.

Hello @vkarak, Thank you for updating!

In the file hpctestlib/sciapps/amber/nve.py:

Line 127:80: E501 line too long (80 > 79 characters)

Do see the ReFrame Coding Style Guide

@jenkins-cscs retry dom


Old tiles used after redrawTiles() is used

There is a bug reproduction demo on this branch.
The demo switches the TileStreamProvider implementation and then calls redrawTiles(). As the tiles are loading, it does so again. This results in the wrong tiles being displayed. I think this may be the cause for #26 too, although I am not sure.
https://user-images.githubusercontent.com/11064768/144748637-9f1120ef-04c9-45b9-bfb0-b77f326a2e8e.mp4
The number of incorrect tiles is equal to workerCount.

Well done for reproducing it. Right now I'm polishing some layers APIs and will have look at this after.
Is this issue affecting master, layers, or both?

Both.

Note for self: the internal state of the collecter should be cleared, or a new collector should be created.

This is because you are changing your TileStreamProvider, while it's concurrently accessed by worker threads. There's no synchronization on the TileStreamProvider (and there shouldn't). So nothing prevents you from altering it while the tile collector is still alive.
No matter how well the tile collector is restarted (re-created or not), the TileStreamProvider is still concurrently accessed.
One way to circumvent this issue is to re-create the MapState (yes, I know, this isn't what you want to do. But that illustrates the concurrency issue). See below. Also note, the example I give you at the end only works if you change L.101 of TileCollector to:
val i = kotlin.runCatching {
     tileStreamProvider.getTileStream(spec.row, spec.col, spec.zoom)
}.getOrNull()

My last thought is this redrawTiles API was a bad idea. For the moment, I'm considering deprecating it and favor the new API
available in layers branch : setPrimaryLayer. The idea is that a TileStreamProvider should be immutable, and we should be able to dynamically change of primary layer. Redrawing tiles would become an internal operation.
FYI, I haven't fully tested setPrimaryLayer yet.
This illustrates that there were a concurrent - and improper - access to type:
class SimpleDemoVM(application: Application) : AndroidViewModel(application) {
    private val appContext: Context by lazy {
        getApplication<Application>().applicationContext
    }
    private var type = 0  // was accessed by several threads in original example - should have been annotated @Volatile
                                    // (but wouldn't have fixed the issue)
    var state: MapState by mutableStateOf(makeMapState(type))

    init {
        viewModelScope.launch {
            while (true) {
                changeMapType()
                delay(200)
                changeMapType()
                delay(2000)
            }
        }
    }

    private fun makeMapState(type: Int): MapState {
        return MapState(
            levelCount = 1,
            fullWidth = 4352,
            fullHeight = 4096,
            workerCount = 8,
            tileStreamProvider = { row, col, zoom ->
                runBlocking {
                    getTile(col, row, type)
                }
            }
        )
    }

    private fun changeMapType() {
        state.shutdown()
        type = ((0..2) - type).random()
        state = makeMapState(type)
    }

    private suspend fun getTile(x: Int, y: Int, type: Int): InputStream? {
        delay((80L..200L).random())
        return appContext.assets?.open("tiles/test/tile_${type}_${x}_${y}.png")
    }
}

That's fair, so what is the proper way of changing the TileStreamProvider on master?

Not sure at the moment. Yeah, probably wait until layers is merged.

I've added a new demo called "Test primary layer switch". Look how a fresh new instance of TileStreamProvider is created each time, and never mutated.
If you used the same technique in your app (mutate your instance of TileStreamProvider, and invoke redrawTiles(), then if anything good came out of it, it's by happy accident. This includes the fix made in master. The problem is still there, and might show up again (under different circumstances, on another device, etc).
I like stress test like this one. Maybe we should make a "test" app, in addition to the existing demo. For instance, TestPrimaryLayerSwitch is in the demo, but it's temporary. What do you think?

In your demo the bug still happens, although now it's only once every 15-20 refreshes, not repeatable every time like it was.

See the new bug_reproduction branch, I re-added the tile loading delay so the bug has a chance to happen.

Although the visual effet looks the same, the underlying issue is this time completely different. No cancellable calls don't play nice with coroutine cancellation. Nice catch though.
I made a change which reduces the likelihood of this particular issue. I've replaced the runBlocking by a Thread.sleep, which is more representative of a real blocking call. Using runBlocking here is a bad practice and we shouldn't expect it there.
However, the problem is still there.
I believe that the proper fix is to have suspend and cancellelable TileStreamProvider. But I might find a better solution.

I've pushed another change which seems to fix the issue, for now.

The last strategy I've implemented (filtering using the last unique main layer id), seems to be more robust.

Check active state in tile collector

What's the reason for a special mainLayer? Now it fells a little hacky to have a special String prefix for it. Can't all unnamed layers just have a random UUID name?

I've thought of doing this even before this issue. It ensures uniqueness of the main layer, even after primary layer change. Otherwise, I haven't found any reliable way to distinguish old primary tiles from new ones.
And oh yes.. poor naming. I'll make names consistent.

Why are "primary tiles" special? Can't all layers be equal with no "primary layer"?

The primary layer is the only one for which opacity can't be controlled.

Also the primary layer can't be accidentally removed (the user don't know it's id).

The primary layer is the only one for which opacity can't be controlled.

Why is that limitation necessary? Although definitely less common I could see someone wanting to have a partly transparent first layer, so why limit it?

Why is that limitation necessary? Although definitely less common I could see someone wanting to have a partly transparent first layer, so why limit it?

I went for this solution initially, only to realize that it produces bad looking transitions when transitioning between levels. The current level is visible, while part of underneath other levels are visible because the primary layer isn't fully opaque.

This library has "Map" in it's name, it provides sane defaults for displaying maps.

I have a map with multiple style types, and multiple layers in each type. The total will reach over 100 different layers, with the user being able to switch between them or display multiple layers with opacity control. That's why I am wondering how the layers implementation will eventually fit in with my requirements. I don't really think of any of my layer as the "primary".

Then the primary will be the one underneath all others. I'll try to see if there's a way to make this a library concept (and not requiring the user think in terms of primary layer + other layers).

I'll try to see if there's a way to make this a library concept (and not requiring the user think in terms of primary layer + other layers).

:+1:


 Correlation ID: xxx-xxx-xxx-xxx The operation to Create a Namespace: "$namespace", failed with the following error: "namespaces is forbidden: User \"xxx-xxx-xxx-xxx\" cannot create resource \"namespaces\" in API group \"\" at the cluster scope"

The reason ist hat the feature for custom locations is not enabled - add this before the creation of the custom location:
az connectedk8s enable-features -n $clusterName -g $groupName --features cluster-connect custom-locations

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

ID: 95bceeac-dc48-471b-2d60-b7442b60ee06
Version Independent ID: a0381e86-0a67-19a3-eb35-f758ce1c2f2c
Content: Set up Azure Arc for App Service, Functions, and Logic Apps - Azure App Service
Content Source: articles/app-service/manage-create-arc-environment.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@derkoe Thanks for the feedback. We're investigating this and will get back to you shortly.

@derkoe I was able to follow through and configure my Azure Arc enabled k8s cluster to run an App Service app without running into the quoted error.
I suspect the error you saw was probably due to insufficient cluster permissions. As mentioned in the troubleshooting guide, the user connecting the cluster to Azure Arc should have cluster-admin role assigned to them on the cluster.
If the provided kubeconfig file does not have sufficient permissions to install the Azure Arc agents, the Azure CLI command will return a similar error.
Please ensure to run:
az aks get-credentials --resource-group $aksClusterGroupName --name $aksName --admin

after creating your connected cluster. The optional --admin parameter ensures that you get the cluster administrator credentials, without which the command defaults to cluster user credentials.

@derkoe Hope the above inputs help. Are there any further questions here?

@derkoe We will now proceed to close this thread as resolved, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Can I contribute proofs to theorems whose proof left for exercise?

Hi,
I am wondering if it is alright to contribute my own proofs for theorems/propositions in the book whose proof is left as exercises?

I haven't really thought about how to do that -- I suppose instructors using the text wouldn't want solutions to exercises be available on the internet. But I can collect them and put them somewhere out of sight. Email them to me at<EMAIL_ADDRESS>

Hi! I think it would be very valuable to have the solution at last for one or two problems for each section. For people that are taking the material by their own this would be the only way to ensure that they are following the contents. It is kind of discouraging to start the book alone without any solution available at all. I understand not having all the solutions, or having only the answer with no explanation, but nothing at all is kind of depressing.
Anyway, it's an amazing material, thank so much for making it public available!


Possible memory leak

Seems like whatwg-fetch has a memory leak. Tested in the browser (Google Chrome, 88). The issue is reproduced by simple script (ignore CORS errors, it behaves the same when request is resolved) which fires requests in interval:
<script>
  // Delete native fetch api to force the polyfill installation
  delete window.fetch
  delete window.Request
  delete window.Response
  delete window.Headers
</script>
<script<EMAIL_ADDRESS><script>
  setInterval(() => {
    fetch('https://www.google.com').then(console.log, console.log)
  }, 250)
</script>

After profiling around 1 minute, we can see that event listeners are constantly growing:

While they are fine with native fetch:

Did some research - looks like it's an issue with Chrome DevTools itself. Here are some links:
https://stackoverflow.com/questions/46695853/javascript-listeners-keep-increasing
https://bugs.chromium.org/p/chromium/issues/detail?id=576302

Did some research - looks like it's an issue with Chrome DevTools itself. Here are some links:
https://stackoverflow.com/questions/46695853/javascript-listeners-keep-increasing
https://bugs.chromium.org/p/chromium/issues/detail?id=576302

As you found it is a Chrome Devtools issue, shall we close this issue?

@JakeChampion Yeah, I think it can be closed, I've reproduced the same behavior in Chrome DevTools even with simple XHR requests, so it doesn't seem to be a fetch problem


Question: is there any additional Caddy configuration needed?

Hi Timo. Thank you so much for making this proxy publicly available. I used your example and it works great. I still have one general question that I could not figure out myself.
I'm not very familiar with Caddy, but in my understanding, I somehow have to configure it on my local machine to make this all work?
So I installed Caddy via brew, played around a bit, set up the neon proxy as described in your Readme and everything worked eventually. However, after a couple of hours, the npm run test fails with an error that tells me the host is not available anymore.
/Users/sk/Desktop/local-neon-http-proxy-main/node_modules/@neondatabase/serverless/index.js:1533
stringify(ye),headers:le,...D})}catch(oe){let $=new Ee(`Error connecting to data\
                                                ^
NeonDbError: Error connecting to database: fetch failed
    at execute (/Users/sk/Desktop/local-neon-http-proxy-main/node_modules/@neondatabase/serverless/index.js:1533:49)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///Users/sk/Desktop/local-neon-http-proxy-main/sample.mjs:16:18 {
  code: null,
  sourceError: TypeError: fetch failed
      at Object.fetch (node:internal/deps/undici/undici:11576:11)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async execute (/Users/sk/Desktop/local-neon-http-proxy-main/node_modules/@neondatabase/serverless/index.js:1532:43)
      at async file:///Users/sk/Desktop/local-neon-http-proxy-main/sample.mjs:16:18 {
    cause: Error: getaddrinfo ENOTFOUND db.localtest.me
        at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26) {
      errno: -3008,
      code: 'ENOTFOUND',
      syscall: 'getaddrinfo',
      hostname: 'db.localtest.me'
    }
  }
}

Node.js v18.18.1

Can you give me some basic instruction on what I have to do with my local caddy setup (like e.g. does the deamon have to run?). I also wonder why caddy is used in the first place, when the configured neon fetch endpoint is not even using https.
Sorry for asking dumb questions, I appreciate any help :)

Hi Stefan, if you are using the Dockerfile or image from the GitHub Container Registry, you shouldn't need to install Caddy manually. It's included in the container image.
The reason Caddy is used as a reverse proxy is that the neon-proxy only accepts HTTPS connections with the self-signed certificate provided during startup.
To avoid having to accept the self-signed cert on your local machine for development, Caddy trusts it and proxies the connection over a plain HTTP connection while preserving the host header for neon.
It seems like the local proxy stopps working after some time in your case. Do you get any errors in your container logs?

Thanks for your quick answer. I just retried from scratched and used the Dockerfile and the Image from the registry as well. Both now have this error (I wonder how I got this working in the first place :D)
There are indeed some errors in the logs.

Might this be a Mac/Apple Silicon issue?

Thanks for the logs. I see the same error block in my logs about invalid region but this seems to be related to some AWS S3 functionality that should not prevent the usage of the proxy. The only difference I can see is the OpenTelemetry error gives a os error 111 in my logs instead of os error 99 in your logs.
OpenTelemetry trace error occurred. error sending request for url (http://localhost:4318/): error trying to connect: tcp connect error: Connection refused (os error 111)

Unfortunately I don't have access to an ARM-based machine to test if this is the reason it's not working but it is strage that it worked partially before.
Could you maybe try to clean up the neon_control_plane schema in your Postgres DB to see if that helps?

Update: I think it all boils down to the fact that my machine cannot resolve db.localtest.me. I'm not sure how or why my machine should be able to do that because I don't understand how Caddy is working. I would naivly think, that they just point everyting to <IP_ADDRESS>.

But anyway, when I change the sample.mjs to the following the npm test works for me
import { neon, neonConfig } from '@neondatabase/serverless';

const connectionString = 'postgres://postgres:postgres@db.localtest.me:5432/main';

neonConfig.fetchEndpoint = (host) => {
  const protocol = host === 'db.localtest.me' ? 'http' : 'https';
  const port = host === 'db.localtest.me' ? 4444 : 443;
  const usedHost = host === 'db.localtest.me' ? 'localhost' : host;
  return `${protocol}://${usedHost}:${port}/sql`; // resolves to 'http://localhost:4444/sql' instead of 'http://db.localtest.me:4444/sql'
};

const sql = neon(connectionString);
const [result] = await sql`SELECT * FROM NOW()`;

console.log(result);

When I got the setup working the first time, I'm pretty sure that I hardcoded this in a similar way while I was debugging.
This is good enough for me, because it eventually works. Feel free to close this issue, except you want to investigate any further.
And again, thanks for this repo and for answering my questions so quickly!

The localtest.me domain is not related to Caddy. It's a domain that should point all wildcard entries to <IP_ADDRESS> and it is used as the cert subject. I got that from the original issue this repo is based on.
The neon proxy does some SNI stuff and doesn't accept localhost from my testing.
The caddy reverse-proxy already sets the upstream host header but unfortunately it seems to be required to use the cert domain in the connection string, otherwise the proxy returns NeonDbError: invalid hostname: Common name inferred from SNI ('localhost') is not known.
This is kind of brittle but unfortunately I haven't found a workaround so far.
I wonder what causes the DNS to fail on your setup for that domain...
By the way, I tried publishing a multi-platform image for AMD64 + ARM64. It's not going to solve this issue and I mainly did it to understand how that is done with GitHub Actions 😅 It would be very helpful if you could give that a try sometime from ghcr.io/timowilhelm/local-neon-http-proxy:mutli-platform-image and let me know if it works at all.

Thanks for clarifying. I just implied that Caddy owns that domain because it was linked on their website.
I finally got it sorted. The issue indeed was that db.localtest.me could not be resolved on my machine. My DNS was configured to be used from my router (good old FRITZ!Box), which is configured to be used from my provider (1&1). I changed it to <IP_ADDRESS> and <IP_ADDRESS> on my machine, restarted it. Everything works. The only thing I can think of is that my internet provider does not resolve all the localtest.me entries (readme.localtest.me resolves by the way...) for security reasons? I could imagine that there might be some phishing scenarios with this domain.
For anyone else having a similar issue, you want to make sure that nslookup db.localtest.me resolves to <IP_ADDRESS>.
ghcr.io/timowilhelm/local-neon-http-proxy:mutli-platform-image works like a charm ♥

Just wanted to mention that if one is using Chrome, all domains ending with .localhost tld resolves to <IP_ADDRESS>. So no need for host files etc. :)


BUG: Float64Index.get_value() for tuples.

[x] closes #13509
[x] tests added / passed
[x] passes git diff upstream/master | flake8 --diff
[x] whatsnew entry

Currently, trying to retrieve one tuple-valued entry in a Series with
a Float64Index will fail (GH 13509). This fixes that bug.

Current coverage is 85.26% (diff: 100%)

Merging #14092 into master will increase coverage by <.01%

@@             master     #14092   diff @@
==========================================
  Files           139        139
  Lines         50492      50486     -6
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits          43053      43049     -4
+ Misses         7439       7437     -2
  Partials          0          0

Powered by Codecov.


moved Mock API to NPM

PV https://www.pivotaltracker.com/story/show/143978893

@miq-bot add_label enhancement
@miq-bot add_label fine/yes

@chriskacerguis @chalettu Fine branch still has mock_api directory. Since we're moving to NPM for Fine, would you rather create an Euwe PR that also clean up those extra things?

@chalettu thoughts?

@chalettu please let me know what need to be done here.. If I should just backport this (without removing extra files no longer needed), can you still confirm this PR should be backported as is?  There has been no mock api related changes backpoted to fine branch, so I want to make sure everything will work with current fine branch + this PR.

@simaishi It should be fine to go ahead and backport this PR and 708 to Fine Branch.  Don't bother with 695 as 708 is newer.  The mock api files are fine to go ahead and leave in this branch .  They won't harm anything

@chalettu Thanks for the confirmation.

Fine backport details:
$ git log -1
commit 23fbb866fdbbd400f71cf83c966f5fac564531fd
Author: Chris Kacerguis<EMAIL_ADDRESS>Date:   Wed Apr 19 14:43:27 2017 -0500

    Merge pull request #694 from chalettu/mock-api-npm

    moved Mock API to NPM
    (cherry picked from commit 9ca3b3e4235d0975b484349546471b2458e60f0e)


TerraForged not generating correctly with BoP, the alps are almost completely flat, as are most of the BoP biomes.

Please take a look through the existing issues to see if your problem has already been reported and reply to that rather than creating a new thread :)
Description
Please describe the problem clearly and concisely
How to reproduce

Describe your setup if using anything other than the Mojang launcher or standard forge server
List any third-party mods (& their version number) that may be relevant to the issue
Provide a simple step-by-step guide to recreate the problem

Additional information
Add screenshots, world-seeds, co-ordinates, log files, links to conflicting mods

You just need to look around a bit more. It's not like vanilla gen where a given biome has the same terrain for every instance of it you find.
Also keep in mind that river networks & lakes will lower the terrain local to them creating valleys and plains (which is probably what is happening in the case of the alps biome you found).


[Bug]: Tutorial appears even if the website has already been accessed before.

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
The bug occurs because the website's tutorial is not properly tracking whether the user has already accessed the site before. As a result, the tutorial appears every time the user visits the website, regardless of whether they have seen it previously.
This issue likely arises from the lack of a mechanism to store and retrieve information about the user's previous visits or interactions with the tutorial. Without this tracking, the website treats each visit as a new session and displays the tutorial again.
Perhaps we should use cookies / localStorage to check if the website's been accessed before and hide the tutorial if that's true.
Expected behavior
I think that the tutorial must be displayed on first visit, and hidden for all subsequent sessions.
Add ScreenShots
No response
On which device are you experiencing this bug?
Android, iPhone, Linux, Chrome, Windows
Record

[X] I have read the Contributing Guidelines
[ ] I'm a GSSOC'24 contributor
[ ] I'm a SSOC'24 contributor
[X] I want to work on this issue

@LyubomirT Are you a GSSOC or SSOC contributor?

Not yet. Is that a requirement?

@LyubomirT Nopes! You can go ahead.

Okay then, thank you! I'll create a PR when I finish working on this.


Changing titlebar style should not notify to restart on macOS

After a sync:

Pretty sure this was related to title bar style as I just changed it.

I was wrong, it does things.


LL-2447

(Analytics): track screen events as pure events with same formatting as LLD
Type
Analytics
Context
LL-2447
Parts of the app affected / Test plan
All screen analytics should now be tracked as events maybe see with @aramab for details as how to test this.

we'll merge and confirm on analytics side later.


Rancher OS does not respect hostname in network configuration

Using latest rancher OS 0.4.0 on bare metal (using iPXE) and a provided cloud-config.yml does not respect the given hostname for DHCP configuration.
In the cloud-config I provide the individual hostname, which gets picked up by rancher as expected. I can see it on the login prompt and also in /etc/hostname. As I leave out the network interface configuration, rancher configures the network via DHCP.
But while issuing the DHCP query, rancher os keeps promoting the hostname "rancher" and not the configured one. I can see that in my dnsmasq logs "client provides name: rancher". So my DHCP/DNS server accepts that name and the rancher box is then only visible on the network via "rancher". You could guess that one can only have one rancher box this way.
So rancher OS must use the hostname when doing DHCP requests.
After some more investigation this is understandable:
The boot-process first starts [10/17] the "cloud-init-pre" then [11/17] the "network" and thereafter [12/17] the "cloud-init". As the hostname is in the cloud-config, but the network is configured before, the hostname can not be used in DHCP requests. If there is no reason for this boot order, one should swap step 11 and 12.
The workaround for this bug is simply to issue an sudo system-docker restart network right after booting is finished. (One could also put this into the startup script <- no you can't. The script is executed in the console container with no access to the system-docker). This is an ugly workaround as it needs another DHCP request to work, but at least it does the job.

I'm also experiencing this behavior, and it's not taking mac addresses I've assigned in cloud-config.

@mailq I can easily fix the issue in which the hostname is not set before running DHCP.
@faddat I don't believe we set the MAC address.  We use the MAC address to match the configuration.

This should be fixed in v0.4.2-rc2. @mailq @faddat Can you confirm?
I tested by booting a RancherOS v0.4.2-dev VM (on VirtualBox) on a bridged NIC on a local WiFi network and pinging it by its hostname.

This is quite old issue but facing the same in v1.5.0.
I am deploying RancherOS from Rancher vSphere provider, which sets the hostname according to node name defined in Rancher UI.
In general, the hostname gets applied correctly (I can see it on the console and it gets reported correctly by VMware Tools).
However, in the DHCP request it contains the default hostname rancher so it gets registered with this name in DNS (what is not intended).
Like mentioned in the initial issue I can use sudo system-docker restart network promote the correct hostname to DHCP after RancherOS is initialized.
But of course I don't want to run this command manually in the automated process of provisioning RancherOS with Rancher vSphere provider.

@azbpa So if we don't use the default hostname in the first dhcp request, can it fix this problem?

@niusmallnan actually not since a valid DNS name is desirable.
Actually there should be some kind of network reset or renew of the dhcp address once the hostname gets updated during cloud-config.
Or the hostname should be already set before the initial network address is requested.


error setting up stage0

I started a container and then killed it (SIGINT) while rkt was still loading it from the CAS. When I went to run it again, it failed to run, complaining run: error setting up stage0: open ...: no such file or directory.
core@apollo ~ $ rkt version
rkt Version: 1.0.0
appc Version: 0.7.4
Go Version: go1.4.3
Go OS/Arch: linux/amd64
Features: -TPM

$ rkt list
UUID    APP     IMAGE NAME      STATE   CREATED STARTED NETWORKS

core@apollo ~ $ rkt image list
ID                      NAME                                    IMPORT TIME     LAST USED       SIZE    LATEST
sha512-0472a487bcbd     coreos.com/rkt/stage1-coreos:1.0.0      4 days ago      4 days ago      134MiB  false
sha512-ee20d692cda7     strongswan                              4 days ago      4 days ago      565MiB  false

core@apollo ~ $ sudo rkt run strongswan --interactive
image: using image from local store for image name coreos.com/rkt/stage1-coreos:1.0.0
image: using image from local store for image name strongswan
^C

Woops, I forgot to override the exec flag.
core@apollo ~ $ sudo rkt run strongswan --interactive --exec /bin/bash
image: using image from local store for image name coreos.com/rkt/stage1-coreos:1.0.0
image: using image from local store for image name strongswan
run: error setting up stage0: open /var/lib/rkt/cas/tree/deps-sha512-8f4a912ea544495e0d920bbef506fac877ac0c9d22416373993485d5ad935fe6/image: no such file or directory

Here is what that directory looks like:
apollo ~ # ls /var/lib/rkt/cas/tree/deps-sha512-8f4a912ea544495e0d920bbef506fac877ac0c9d22416373993485d5ad935fe6
manifest  rootfs

The manifest looks good:
apollo ~ # cat /var/lib/rkt/cas/tree/deps-sha512-8f4a912ea544495e0d920bbef506fac877ac0c9d22416373993485d5ad935fe6/manifest
{"acKind":"ImageManifest","acVersion":"0.7.1+git","name":"strongswan","labels":[{"name":"arch","value":"amd64"},{"name":"os","value":"linux"}],"app":{"exec":["/usr/sbin/ipsec","start","--nofork","--debug"],"user":"0","group":"0"}}

And the rootfs directory looks fine (I won't include the contents here).
The directory for the stage0 look fine:
apollo ~ # ls /var/lib/rkt/cas/tree/deps-sha512-b42939d872a0645a4dcf08e33b2b99c444f2188225d0bc8290073df498a64b3c/
hash  image  manifest  rendered  rootfs

And its manifest:
apollo ~ # cat /var/lib/rkt/cas/tree/deps-sha512-b42939d872a0645a4dcf08e33b2b99c444f2188225d0bc8290073df498a64b3c/manifest
{"acKind":"ImageManifest","acVersion":"0.7.4","name":"coreos.com/rkt/stage1-coreos","labels":[{"name":"version","value":"1.0.0"},{"name":"arch","value":"amd64"},{"name":"os","value":"linux"}],"annotations":[{"name":"coreos.com/rkt/stage1/run","value":"/init"},{"name":"coreos.com/rkt/stage1/enter","value":"/enter"},{"name":"coreos.com/rkt/stage1/gc","value":"/gc"}]}

I can reproduce the bug more easily by deleting:
/var/lib/rkt/cas/tree/*/{image,rendered}

Then, I cannot start the image again.
$ sudo rkt run --debug --insecure-options=image --interactive docker://debian
image: using image from file /usr/bin/stage1-coreos.aci
image: remote fetching from URL "docker://debian"
image: fetching image from docker://debian
Downloading sha256:03e1855d4f3: [==============================] 51.4 MB/51.4 MB
Downloading sha256:a3ed95caeb0: [==============================] 32 B/32 B
stage0: Preparing stage1
run: error setting up stage0
  └─error preparing stage1
    └─error rendering tree image
      └─cannot read image file
        └─open /var/lib/rkt/cas/tree/deps-sha512-854e6556bb4f11581869e58503ac8fd2e096dbb01654a8724884903d9e771cae/image: no such file or directory

And I also cannot GC the images:
$ sudo rkt --debug  image gc --grace-period=0
gc: failed to remove unreferenced treestores
  └─cannot get referenced treestoreIDs
    └─cannot get stage1 treestoreID for pod 2351f7c7-68c0-4412-9464-c064651d7710
      └─no such file or directory

@iaguis #2242 fixed the "image gc" issue but it didn't fix everything here, did it?

is there a workaround for this?   I am getting this error with rkt 1.1

@f0 After #2258, if you get this error you should be able to re-run the image, the treestore will rebuild itself, and everything should work.

@iaguis  ok and this wil land in 1.2? and when will 1.2 released?

@f0 yes. It wll be released this week.

@iaguis   ok thank you


Child/Inner route not inheriting parent middlware(s)

Q
A

Bug?
yes

New Feature?
no

Framework
Lumen

Framework version
7.0

Package version
3.0.0

PHP version
7.2

Actual Behaviour
Dingo child/inner route middleware not "inherit" parent's middleware.
Expected Behaviour
The child routes should append middlware define from the parent as its own middlware.
Steps to Reproduce
use Dingo\Api\Routing\Router;

$api->group([
    'prefix' => 'foo',
    'middleware' => ['auth:api'],
], function (Router $api) {

    $api->get('/test', [
        'uses' => 'ExampleController@test'
    ]);

    $api->get('/bar', [
        'uses' => 'ExampleController@bar',
        'middleware' => ['employee'],
    ]);

    $api->get('/biz', [
        'uses' => 'ExampleController@biz',
        'middleware' => ['employer'],
    ]);

  ]);

/test has auth:api middlware
foo/bar has employee middlware but it should auth:api and employee
foo/biz has employee middlware but it should auth:api and employer
Possible Solutions
Currently what i'm doing is write the full middlware on every child  'middleware' => ['auth:api','employer'], or moving it outside the group.

Not really sure as I don't use Lumen, but this is definitely a very basic functionality that I have never seen not work (ie. inheriting parent middleware).
There are definitely some Lumen users here, so hopefully someone can have a look at this for you.


Better Swiftlint precomment hook

This improves the precommit hook for swiftlint, only linting the specific added/changed files. I also ran the code through the linter to fix any existing issues so we can start from a clean slate.
Fixes #1770.

          2 Warnings

:warning:
Needs testing on a Phone if change is non-trivial

:warning:
Detected some Swift building time outliers

Time | Class | Function |
| --- | ----- | ----- |239.6ms | AuctionViewController.swift | @objc dynamic func showRefineTappedAnimated(animated: Bool)
191.1ms | SwiftyJSON.swift | get {}
176.4ms | WebSocket.swift | private func processRawMessage(buffer: UnsafePointer, bufferLen: Int)
79.8ms | Observable.swift | private final func nextTokenHash() -> Int
76.6ms | LiveAuctionsAdminViewController.swift | @objc override func viewDidLoad()
72.1ms | AuctionLotMetadataStackScrollView.swift | required init(viewModel: LiveAuctionLotViewModelType, salesPerson: LiveAuctionsSalesPersonType, sideMargin: String)
63.5ms | LiveAuctionLotViewController.swift | @objc override func viewDidLoad()
63.4ms | UIViewController+BlurredStatusView.swift | func ar_presentBlurredOverlayWithTitle(title: String, subtitle: String, buttonState: BlurredStatusOverlayViewCloseButtonState = default)
61.4ms | UIViewController+BlurredStatusView.swift | (closure)
60.3ms | RefinementOptionsViewController+Private.swift | func stackView() -> ORStackView

  Generated by :no_entry_sign: danger

Aww yeah, just under the changelog loc requirement.

👍
Probably won't be too much effort to move this into a Danger plugin too

Swiftlint plugin sounds awesome. That's wrapped up, eh? Like danger new_plugin should work? I can take a stab.

Roughly, aye, IMO, clone https://github.com/dbgrandi/danger-prose and do some re-naming, there's work I've done there WRT testing that's not migrated back upstream


Tidy up some pathctx helpers

Don't duplicate the maybe case across multiple aspect-specific
functions.

Cherry-picked into 1.x. This should have been cherry-picked into 1.x sooner, since I cherry-picked things that depended on it...


Fix formatting in README

[lockit v3.0.3] Merged via Lockit CLI on 2016-12-14 15:13:04.736454697 -0800 PST


Getting correct TfsServerUrl for RM service

Incase of hosted service do not mangle the url as for RM service we should get the RM service's url.

ok

the fix is not accurate, since it's a back compat variable, i will make a fix that just copy the implementation from old windows agent.
https://github.com/Microsoft/vsts-agent/pull/606


feature: add_table() sets cell widths

In order to provide the least surprising initial behavior
As a developer using python-docx
I would like a table inserted using add_table() to be serviceable in both Word and LibreOffice without further adjustment.
Related to #75. Default table added with Document.add_table() runs off the page in LibreOffice, although it's fine in Word. Rendering differences aside, it would be better if it produced consistent results across the two clients.
The solution is to add column widths, e.g. <w:gridCol w:w="1440"/> as well as matching cell widths, e.g. <w:tcW w:w="1440" w:type="dxa"/> for each cell in each column. This is consistent with what Word does when adding a new table from the ribbon.
Column widths should be evenly distributed across the page width. For example, a 4-column table inserted into a page with 8 inches between the margins should have four columns 2 inches wide each.

Added in release v0.8.5, pushed on Feb 21, 2015.

Hi Scanny,
I've updated to 0.8.5 from 0.7.4 and now all my tables are the same width (and this is the closest issue I've found that might be the cause of it)
This is how I used to format tables (which worked fine in 0.7.4)
table = document.add_table(rows=10,cols=2,style="ColorfulList-Accent5")
table.autofit = False
table.columns[0].width = 13 * emusPerCm
table.columns[1].width = 3 * emusPerCm
However - now it does not appear to accept this. Based on your description, I presume I now need to have for loops everywhere to change all the cell widths? Is it possible that have it fallback on column width and set the cell width if cell width is not specified. There are few circumstances I can think of for varied styled cells within a table.

Hi Louis, yes, the behavior you're seeing is an artifact of the change added to address this issue with how new tables appeared in LibreOffice Writer. Now, when a table is created, the columns widths are each set to a proportional fraction of the page width, but also the width of each cell in each column is set to match the column width.
What we haven't gotten done yet is to carry this logic through to cell widths on assignment to Column.width. The reason being the logic is not trivial in the general case where one or more cells can be merged. In those cases, the cell width should be the sum of the column width of all the columns it spans.
I've added a new issue for it here #161.
In the meantime, your table creation code can be cleaner with a column width setting function that does the needful, something like this:
def set_column_width(column, width):
    for cell in column:
        cell.width = width

table = document.add_table(rows=10,cols=2,style="ColorfulList-Accent5")
set_column_width(table.columns[0], Cm(13))

If you have merged cells, you'll need to do the needful to ensure those cells get the appropriate different width.
By the way, your width setting can be a little simpler using the Cm() constructor:
from docx.shared import Cm

column.width = Cm(13)

Thanks @scanny.
I've written a function that's similar to what you've described (set_table_width rather than set_column_width) which accepts the table and a list argument. I just have to copy and paste it about 40 or 50 times. I was hoping to avoid it.
However, since it is not a trivial change and the functionality is still there - I'm not too concerned, just means I need to change my code. Compatibility with multiple processors is more important and cell merging is something I see people wanting to generate.
Did not know about Cm() function, although multiplying width by 360000 isn't too bad.
Thank you for the feature and for the speedy response - Love your work :)

def set_column_width(column, width):
    for cell in column:
        cell.width = width

set_column_width(table.columns[0], Cm(2.5))

gives an error:
TypeError: '_Column' object is not iterable

it should be for cell in column.cells:.

thanks. I use the following now:
def set_column_width(column, width):
    column.width = width
    for cell in column.cells:
        cell.width = width

any idea hot to enable the option "automatically adjust to content" when i create a table on a word docx file using python librarie docx ???

@nikosme  did you figure out how to do this? Thanks.

I'm trying to set my table to either "AutoFit to Window" or "preferred width 100 percentage", either way I just want my tables "full width"


DOC: Remove old warning from dsintro.rst

[ ] closes #xxxx
[ ] tests added / passed
[ ] passes git diff upstream/master | flake8 --diff
[ ] whatsnew entry

The warning is about something that have been fixed for almost 3 years. Every time a new user excited about pandas start reading the docs, they have to waste brain-cycles ignoring that big red warning bubble.

Yes, good idea! Thanks

actually could prob take out the Index warning as well (indexing.rst). Maybe also look for older things like this elsewhere.

Thanks for the quick merge @jorisvandenbossche . This certainly encourages me to keep sending patches like this. :)
@jreback, absolutely. This is my first touch in the code base, so I won't take on that endeavor. But if this inspires a maintainer to do it. I would be ever so glad. :)

Yes, I think we should do a general search on version notices below 0.15 or so (also for notices that something was added in eg version 0.14 -> although maybe we could leave that for the 1.0 docs to do a big cleanup)

Also removing the "experimental" tags on some sections if they're ready

Regarding experimental, there is an issue for that: https://github.com/pydata/pandas/issues/5049


Add Crystal Clipboard

Hello,
I would like to add my project to this list.
Thank you for your time 🙂

Thank you!


Dev

Pep8
Basic glossary plugin.

todo: deletion, select-by-number

AUGH.
Apologies --- github surprised me by trying to PR against the wrong master. :/


Fix integration testing config

Added rerun command and corrected trigger command
Fixed integration test image

/test integration-batch

/retest

/test integration-batch

/retest

/retest

Related to #102?

@thirteen37 No, this fixes some issues with the running of the integration test via CI. The triggering is already working as intended, although the integration test step is not properly throwing an error when the test fails. The changes made in this commit should fix that.
See the latest postsubmit-integration-test here: http://prow.feast.ai/

@zhilingc Sounds like you're saying that #102 is actually resolved then? Can we mark it as such or is there more work remaining?

@thirteen37 Not quite, I need this fix in so that it does throw an error when one occurs, otherwise the integration test (that does the building of the binaries) will always pass

Closed by #197


license for stretcher/testify

this commit removed references to stretecher/testify's license but there are still references to this go module https://github.com/apache/incubator-openwhisk-runtime-go/commit/ddd329946c1d061f256a274d6ccd23e527760e06#diff-61e0bdf7e1b43c5c93d9488b22e04170
https://github.com/apache/incubator-openwhisk-runtime-go/blob/1cbb96383502ca6df45058d966927c0796c31fbd/go.mod#L5
https://github.com/apache/incubator-openwhisk-runtime-go/blob/1cbb96383502ca6df45058d966927c0796c31fbd/openwhisk/actionProxy_test.go#L28
(there are others.)

Per https://github.com/apache/incubator-openwhisk-runtime-go/commit/ddd329946c1d061f256a274d6ccd23e527760e06?email_source=notifications&email_token=ABF25MSUK4EAGJ726O473LTPZU5GPA5CNFSM4HWJKCG2YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBAJQ33#commitcomment-33866619 we need to add the license link back.

fixing in https://github.com/apache/incubator-openwhisk-runtime-go/pull/92