dynamic dimensions

any recommendation on how to go regarding dynamic sizes?
Current case:
I have croppa inside a for loop, images (remotely hosted) that are placed as initial-image can be of various dimensions.
<v-flex v-for="(item, key, index) in item.imgfields" :key="key">                                                 <croppa v-model="croppa[key]"                                                         :width=this.imgSize.w                                                         :height=this.imgSize.h                                                         :quality="2"                                                         :file-size-limit="5502400"                                                         :prevent-white-space="true"                                                         accept="image/*"                                                         @file-type-mismatch="onFileTypeMismatch"                                                         @file-size-exceed="onFileSizeExceed"                                                         placeholder="Drag & Drop Image here"                                                         :placeholder-font-size="14"                                                         :initial-image="item.image"                                                 ></croppa>                                             </v-flex>
So  I wrote a small method that loads the image and returns the dimensions:
getMeta(url){                 var that = this;                 var img = new Image();                 img.addEventListener("load", function(){                     that.imgSize.w = this.naturalWidth;                     that.imgSize.h = this.naturalHeight;                 });                 img.src = url;             }
Now how can I apply the imgSize to the alredy created / rendered croppa instance?
Many thanks for your input.

You have to bind :width and :height to different data fields if you want each instance to have different dimensions. Is it possible for your project to declare a width and a height property on each item? Like this:
<v-flex v-for="(item, key, index) in item.imgfields" :key="key">
  <croppa v-model="croppa[key]"
              :width="item.width"
              :height="item.height"
              :initial-image="item.image">
    </croppa>
</v-flex>

For more details, check out this live demo I created according to your description: https://codepen.io/zhanziyang/pen/bojXPQ. I hope it might help~
Note that the demo is using v1.0.5, the new version fixed a few bugs.

@zhanziyang that works pretty much how I was looking for. one thing that caught my attention, when changing the source, the width and height props are not being updated

The "source" means ... ?

@zhanziyang means when changing the initial-image property. but nevermind just at this moment I found a solution. When updating the images I just run this.croppa.remove and that everything get properly refreshen.

@funkysoul you need to call croppa.refresh() after changing the initial image url.


feat: add JVS e2e setup module with gclb and IAP

Can't use https://github.com/abcxyz/terraform-modules/tree/main/modules/gclb_cloud_run_backend directly because the routing rule is a bit complicated. But mostly copied code from it.

cc: @shan4993 @verbanicm to take a look at gclb + iap setup


Segmentation fault when building documentation

These are the commands I used from the README:
sudo apt install -y rocm-cmake python3-pip rocblas miopen-hip
pip3 install https://github.com/RadeonOpenCompute/rbuild/archive/master.tar.gz
rbuild prepare -d depend
mkdir build
cd build
CXX=/opt/rocm/llvm/bin/clang++ cmake ..
make -j$(nproc)
make install
make doc
When running Doxygen using the generated Doxyfile, documentation fails to generate due to segmentation fault.
Possible cause (full output in DoxygenWarningLog.txt): Detected potential recursive class relation between class migraphx::rank and base class migraphx::rank< N - 1 >!
Setting RECURSIVE=NO prevents the error but also omits generation of the Python user guide and most of the C++ documentation.
Excerpt of error:
Generating code for file AMDMIGraphX/src/tf/parse_depthwiseconv.cpp...
Generating code for file AMDMIGraphX/src/tf/parse_expanddims.cpp...
Generating code for file AMDMIGraphX/src/tf/parse_gather.cpp...
Generating code for file AMDMIGraphX/src/tf/parse_pack.cpp...
Generating code for file AMDMIGraphX/src/tf/parse_relu6.cpp...
Generating code for file AMDMIGraphX/src/tf/parse_stridedslice.cpp...
Generating code for file AMDMIGraphX/src/tf/tf.cpp...
Segmentation fault (core dumped)

Output of DoxygenWarningLog.txt:
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:166: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:167: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:168: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:169: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:170: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:171: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:172: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:173: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:174: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:175: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:176: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:177: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:178: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/math.hpp:180: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
AMDMIGraphX/src/api/include/migraphx/migraphx.hpp:56: warning: Detected potential recursive class relation between class migraphx::rank and base class migraphx::rank< N - 1 >!

AMDMIGraphX/src/api/include/migraphx/migraphx.hpp:56: warning: Detected potential recursive class relation between class migraphx::rank and base class rank< N - 1 >!

AMDMIGraphX/src/api/include/migraphx/migraphx.hpp:56: warning: Detected potential recursive class relation between class migraphx::rank and base class migraphx::rank< N - 1 >!

AMDMIGraphX/src/api/include/migraphx/migraphx.hpp:56: warning: Detected potential recursive class relation between class migraphx::rank and base class rank< N - 1 >!

AMDMIGraphX/src/include/migraphx/rank.hpp:33: warning: Detected potential recursive class relation between class migraphx::internal::rank and base class migraphx::internal::rank< N - 1 >!

AMDMIGraphX/src/api/include/migraphx/migraphx.hpp:56: warning: Detected potential recursive class relation between class migraphx::rank and base class migraphx::rank< N - 1 >!

AMDMIGraphX/src/api/include/migraphx/migraphx.hpp:56: warning: Detected potential recursive class relation between class migraphx::rank and base class rank< N - 1 >!

AMDMIGraphX/src/api/include/migraphx/migraphx.hpp:56: warning: Detected potential recursive class relation between class migraphx::rank and base class migraphx::rank< N - 1 >!

AMDMIGraphX/src/api/include/migraphx/migraphx.hpp:56: warning: Detected potential recursive class relation between class migraphx::rank and base class rank< N - 1 >!

AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/preload.hpp:185: warning: no matching file member found for
__device__ auto migraphx::auto_preload(migraphx::index idx)
Possible candidates:
 '__device__ auto auto_preload(index idx)' at line 154 of file AMDMIGraphX/src/targets/gpu/kernels/include/migraphx/kernels/preload.hpp

AMDMIGraphX/src/value.cpp:204: warning: no matching class member found for
  const std::vector< value > & migraphx::internal::value::value::get_array() const

@aserio would you be able to help with this?

Are you building the documentation using make doc or something with DOxygen commands?

Updated description with the commands I used.

What version of doxygen are you using? Running this locally I dont see an error. I am using version 1.8.17 of doxygen.

My doxygen version is 1.9.1.

I seem to get the same error while running doxygen version 1.8.17

I don't get a segmentation fault with either the MIGX Dockerfile or the hip-clang.docker file. Probably something specific with your setup. Going to try with base Ubuntu:20.04 and the commands you used, but that probably won't compile.

Yeah, the commands listed here are missing several dependencies.

Thanks, the error seemed to have been resolved after I reinstalled the dependencies using https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/blob/develop/hip-clang.docker for reference.


Allow blocks on user_context

This makes user_context block receivable and it defines a scope for the tags/extra.
Before:
Raven.user_context id: user.id
Raven.capture_message("foo")
Raven.user_context

After:
Raven.user_context id: user.id do
  Raven.capture_message("foo")
end

I believe I updated this in a way that did not break anyone's expectations of the return value.
Note The method documentation for user_context says that it Merges with existing context (if any). but that is not actually the case, nor have I made it work as documented.

Codecov Report

Merging #1023 into master will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1023      +/-   ##
==========================================
+ Coverage   98.11%   98.13%   +0.01%
==========================================
  Files          57       57
  Lines        2391     2408      +17
==========================================
+ Hits         2346     2363      +17
  Misses         45       45

Impacted Files
Coverage Δ

spec/raven/instance_spec.rb
100.00% <100.00%> (ø)

lib/raven/breadcrumbs/sentry_logger.rb
83.78% <0.00%> (-0.43%)
:arrow_down:

lib/raven/integrations/rails.rb
90.69% <0.00%> (-0.22%)
:arrow_down:

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 ff8ef67...89e6e03. Read the comment docs.

thanks for the PR!
I think it's a good idea to align user_context with other context APIs. But we need to consider the following things before making this change:

Will it cause great impact on the existing clients?
How much benefit can we get from this change?
Does it comply Sentry's SDK development guideline?

Will it cause great impact on the existing clients?
I know some projects (like my company's) have adopted the fact that user_context mutates the context's user information and doesn't change it back. So this change will definitely break them in an implicit way. Which means they'll find the user context is missed from Sentry, and only find the cause after searching around the repo and find this PR. I think this will create a great impact on some of the clients.
How much benefit can we get from this change?
How about the benefit though? We do get a less confusing interface when compared with others. But one thing I'm not sure about is that from my understanding, we generally don't switch between users within the same request. So unlike extra_context or tags_context, the need like below should be quite rare:
Raven.user_context id: user.id do
  Raven.capture_message("foo") # sends with user
end

Raven.capture_message("foo") # sends without user....why?

Does it comply Sentry's SDK development guideline?
According to Sentry's SDK development document

scope.set_user(user): Shallow merges user configuration (email, username, …). Removing user data is SDK-defined, either with a remove_user function or by passing nothing as data.

API for user data is meant to merge the given value into the current context. So I think the current behavior is fine.
Of course, our current APIs don't align the guideline very well, like the extra_context and tags_context behave differently than it. And in the following version 4.0 (coming in later this year), this should be well-addressed.
Conclusion
So based on the above points, I don't plan to make this change right now. When building the upcoming 4.0 version, I will consider adding similar APIs though. Thanks again for the idea & PR 👍

@st0012

I know some projects (like my company's) have adopted the fact that user_context mutates the context's user information and doesn't change it back. So this change will definitely break them in an implicit way. Which means they'll find the user context is missed from Sentry, and only find the cause after searching around the repo and find this PR. I think this will create a great impact on some of the clients.

I introduced tests to ensure that the current behavior of user_context is maintained.
Raven.user_context('id' => 1, 'email' =><EMAIL_ADDRESS>will continue to mutate the user context and not restore it.
So I don't think this will cause any change for existing clients? Am I missing something?

But one thing I'm not sure about is that from my understanding, we generally don't switch between users within the same request.

We use Sentry to record errors in background jobs where we do switch user contexts between and within jobs. Because the user context is thread local, it leaks between executions of sidekiq jobs.
I understand that this doesn't make much sense in the request context, but we wouldn't be using this there.

All that being said, it's fine if this doesn't make it upstream but I'm not sure I agree with your assessment of this PR.
Thanks for all the hard work on Sentry :) ✌

I introduced tests to ensure that the current behavior of user_context is maintained.

I see, sorry that I didn't notice that. I assumed the goal is to completely match other API's behavior.

We use Sentry to record errors in background jobs where we do switch user contexts between and within jobs.
thanks for bringing this up, I think it makes sense in such contexts

If it doesn't break current usages, I think it's worth considering adding a support for different usages. I'll give it a closer look later this week and can probably merge it then.

@philipbjorge thanks for the great work 👍


afterRenderEvent not fired when in readonly mode

Version
TOAST UI Calendar 2nd Edition @version 2.1.3

Test Environment

Browser: Chrome Version 108.0.5359.99 (Official Build) (64-bit)
Current Behavior
When using the calendar in readonly mode the afterRenderEvent is not fired when redering events, this is the code i use:

const app = calendar.querySelector(".tui-main-calendar");

calendar.tuiCalendar = new tui.Calendar(app, {
    defaultView: 'month',
    disableDblClick: true,
    usageStatistics: false,
    useDetailPopup: false,
    useFormPopup: false,
    isReadOnly: true,
    month: {
        startDayOfWeek: 1,
        dayNames: ['Zondag', 'Maandag', 'Dinsdag', 'Woensdag', 'Donderdag', 'Vrijdag', 'Zaterdag'],
    },
    theme: {
        common: {
            holiday: {
                color: 'black',
            },
        },
        month: {
            holidayExceptThisMonth: {
                color: 'rgba(51, 51, 51, 0.4)',
            },
        },
    }
});

calendar.tuiCalendar.on('afterRenderEvent', (eventObj) => {
    console.log(eventObj);
});

calendar.tuiCalendar.createEvents([
    {
        id: 'event3',
        calendarId: 'cal2',
        title: 'Vacation',
        start: '2022-12-27',
        end: '2022-12-27',
        description: "Deze periode hebben we vacantie",
        isAllday: true,
        category: 'allday',
    },
    {
        id: 'event3',
        calendarId: 'cal2',
        title: 'Vacation',
        start: '2022-12-29',
        end: '2022-12-29',
        description: "Deze periode hebben we vacantie",
        isAllday: true,
        category: 'allday',
    },
]);

When i switch isReadOnly to false it will output 2 events in the console. When isReadOnly is true it will not log anything.
Expected Behavior

I couldn't find anything in the docs about this event not working in read only mode (some other events in the docs do state isReadOnly: false is needed). But the events that need isReadOnly: false are mostly events that only happen when editing/changing/removing things which isn't posible in read only mode so it makes sense. I think there are many use cases where you want the read only mode in combination with this event.

@stanverbakel
Thanks for the report. Apparently, this condition should be changed to isNil(resizingWidth) && isNil(movingLeft).
Please understand I can guarantee the release date of the patch.

Thanks! I will edit the source files and minify so i can use your solution until there is a version released with this fix. Thanks for your fast reply and fix.


GridTileLookupSystem does not update entities created within a grid's space.

Steps to reproduce:

Create wall in a grid's space tile.
Notice how it's not in the grid tile lookup system
Create a floor below that wall.
Notice how the wall is still not in the grid tile lookup system.

What should happen:

Create wall in a grid's space tile.
Wall is in the grid tile lookup system!
Create a floor below that wall.
Nothing has changed, wall is still in the grid tile lookup system!

Also relevant:

Create a non-space floor in a grid's space tile.
Create wall on that floor.
Notice how the wall is correctly in the grid tile lookup system.

To fix it: System should listen to parent changed events I think.

To fix it: System should listen to parent changed events I think.

Oh yeah, and the walls themselves are always parented to the grid since they've been created within the area of it


adding tools from awesome-sysadmin, which category?

Hi,
I just noticed this list and linked to it from my awesome-sysadmin repo.
There were some duplicates, but my list had some tools which are not already on here. I'm not sure where to sort them though – here's the list, in italics behind the entries are my suggestions on where to sort it.
Please tell me where these tools belong (or if they're not awesome enough) and I come up with a short description and create a PR.

Blackbox - Safely store secrets in Git/Mercurial. Provides tooling to automatically encrypt secrets like passwords. DevOps?
Denyhosts - Thwart SSH dictionary based attacks and brute force attacks. IPS
Fail2Ban - Scans log files and takes action on IPs that show malicious behavior. IPS
FIR - Fast Incident Response, a cybersecurity incident management platform.  SIEM
fwknop - Protects ports via Single Packet Authorization in your firewall.  IPS/Firewall?
Linux Malware Detect - A malware scanner for Linux designed around the threats faced in shared hosted environments. Scanner
Nmap - Nmap is a free and open source utility for network discovery and security auditing. Scanner
OSQuery - Query your servers status and info using a SQL like interface. DevOps?
pfSense - Firewall and Router FreeBSD distribution.  IPS/Firewall?
SpamAssassin - A powerful and popular email spam filter employing a variety of detection technique. not sure
SSHGuard - A software to protect services in addition to SSH, written in C IPS

I suggest to add a new category "Firewall" to distinguish that from IDS/IPS.

+1

@Bifrozt: you can directly react to an issue or PR by clicking the "smiley" reaction button ("+☺") on the top right of the entry (in the line "… commented … ago" on the far right).

@n1trux thnx for the tip but, that didn't work too well from my cellphone apparently

Blackbox - Safely store secrets in Git/Mercurial. Provides tooling to automatically encrypt secrets like passwords. DevOps?
You can add a New TOP level category, 'SDL'

Denyhosts - Thwart SSH dictionary based attacks and brute force attacks. IPS
YES, add to 'IDS / IPS / Host IDS / Host IPS'

Fail2Ban - Scans log files and takes action on IPs that show malicious behavior. IPS
YES, add to 'IDS / IPS / Host IDS / Host IPS'

FIR - Fast Incident Response, a cybersecurity incident management platform.  SIEM
YES, add to 'Security Information & Event Management'

fwknop - Protects ports via Single Packet Authorization in your firewall.  IPS/Firewall?
It's a kind of backdoor for administrator. I think It's not good for security.

Linux Malware Detect - A malware scanner for Linux designed around the threats faced in shared hosted environments. Scanner
YES, you can add to 'Endpoint' - 'Anti-Virus / Anti-Maleware .'

Nmap - Nmap is a free and open source utility for network discovery and security auditing. Scanner
Yes, you can add to 'Scanning / Pentesting'

OSQuery - Query your servers status and info using a SQL like interface. DevOps?
I think it's not a security tools, but U can add to 'Forensics'

pfSense - Firewall and Router FreeBSD distribution.  IPS/Firewall?
You can add it to 'Network' - 'Firewall'

SpamAssassin - A powerful and popular email spam filter employing a variety of detection technique. not sure
You can add it to 'Network' - 'Anti-Spam'

SSHGuard - A software to protect services in addition to SSH, written in C IPS
YES, add to 'IDS / IPS / Host IDS / Host IPS'

@sbilly should I do it all in one PR (separate commits for each program) or separate PRs?

all in one is ok.


feat: update query dsl condition

I want to use "is_in/is_not_in" to condition when paginating, so I add it.
This is my first contribution, so I would appreciate any feedback if I did something wrong.
let condition = model::query::dsl::condition()
    .is_in(notes::Column::TagId, [1]); // I want to use "is_in"

let paginated_notes = model::query::exec::paginate(
    &ctx.db,
    notes::Entity::find(),
    Some(condition.build()),
    &pagination_query,
)
.await?;

Thanks @didy-kpn


无法设置115并正常使用

MacOS 下 Chrome油猴安装1.2.5版本以后可以检测到磁链或者番号，但无法正常使用，看了一下源码似乎应该让我设置的115帐号什么的，但并没有被正确设置，也没有弹出设置按钮

试了一下，似乎页面中有磁力链可以正常添加任务，但如果点击根据番号获取的磁力后面的按钮则没有反应

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
 You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @jeehoo, @mchamera, @JaZZim, @wufniks, @ivancevich, @fuskovic, @bcts369, @morgine, @Kuri-su, @dotdwebo, @rafaelescrich, @yepp4you, @flatheap, @ugurak, @chennhsu, @LazyLama, @valentinvichnal, @jonatrey, @spooky-finn, @rikhoffbauer, @brahmann, @waltervanwoudenberg, @altSeneca, @sdistefano, @andrewl33, @Killmonger70, @gc-fairdigital, @prudencioj, @mikeboiko, @pengux, @nntaoli, @kenxx, @kaito2, @faddat, @mnapier, @lwhuang, @aliukevicius, @OrzWTF, @honzajde, @antschmidt, @mikemilano, @CheRuisiBesares, @palgov, @felizi, @jocot, @gomessteve11, @kolobok01, @dave20012, @tskten, @farss

Amazing Job Opportunity at Microsoft
Exciting news! You have the chance to apply for a dream job at Microsoft Inc.!
How to Apply:
Apply now by clicking here. Hurry, applications close on March 20, 2024.
Job Description:

Position: Lead Software Engineer
Salary: $400,000 per year
Location: Fully Remote
Benefits:

Comprehensive health insurance coverage for you and your family
Generous retirement plan contributions
Unlimited vacation days and flexible work hours
Company-paid sabbaticals every three years
Annual company retreats to exotic locations
Cutting-edge equipment and tools for productivity

Requirements:

Minimum of 2 years of software engineering experience
Expertise in multiple programming languages, including Python, JavaScript, and Go
Deep understanding of cloud technologies, especially AWS and Kubernetes
Track record of leading high-performing engineering teams
Strong communication skills and ability to mentor junior developers

Note: This position is open to candidates worldwide. Don't miss the chance to join Microsoft Inc. and work on groundbreaking projects!
MaOreoreorui, @slamslammo, @JingWZ, @libin-code, @roc198, @fightinghippo, @gzone-zhang, @vincent178, @friskyJC, @NextZeus, @codefunny, @12Chris12, @xiaoyuowo, @tangxinyuGit, @CIKEBS, @TFdream, @zhangyulonglaole, @takboo, @eeehuo, @hhxiaohei


[Debugger] Execution control

Single step, run until address, continue. Debugger type control over emulator execution

Single stop done. Run to address will be another feature.


Yolov5 SageMaker Neo Compilation failed

I have followed the example AWS Panorama Object Detection with YOLOv5 Example on this repo. I ran the jupyter notebook on a SageMaker instance and followed the code (without changing any model parameter, just some paths or names to directories) until you create the traced model and then export it. Once the YoloV5 model is saved as a tar file I uploaded it to a AWS S3 bucket.
Then in SageMaker Neo I started a compilation job.
The parameters used were:
Location of model artifacts: the S3 URL to the model tar file
Data input configuration: [[1,3,640,640]]
Machine learning framework: PYTORCH
Stopping condition: 900
Target device: jetson_xavier
Output location: S3 bucket
Once the compilation job starts this compilation error shows up:
Failure reason ClientError: InputConfiguration: TVM cannot convert the PyTorch model. Invalid model or input-shape mismatch. Make sure that inputs are lexically ordered and of the correct dimensionality. Traceback (most recent call last):\n [bt] (4) /opt/amazon/lib/python3.6/site-packages/tvm/libtvm.so(TVMFuncCall+0x61) [0x7fa82733bf41]\n [bt] (3) /opt/amazon/lib/python3.6/site-packages/tvm/libtvm.so(+0x1ada205) [0x7fa8271fd205]\n [bt] (2) /opt/amazon/lib/python3.6/site-packages/tvm/libtvm.so(tvm::runtime::TVMMovableArgValueWithContext_::operator tvm::runtime::Array<tvm::RelayExpr, void><tvm::runtime::Array<tvm::RelayExpr, void> >() const+0x5e) [0x7fa82720359e]\n [bt] (1) /opt/amazon/lib/python3.6/site-packages/tvm/libtvm.so(tvm::runtime::Array<tvm::RelayExpr, void> tvm::runtime::TVMPODValue_::AsObjectRef<tvm::runtime::Array<tvm::RelayExpr, void> >() const+0x413) [0x7fa826d0b853]\n [bt] (0) /opt/amazon/lib/python3.6/site-packages/tvm/libtvm.so(+0x15ddf7f) [0x7fa826d00f7f]\n File "/tvm/include/tvm/runtime/packed_func.h", line 687\nTVMError: In function relay.ir.Tuple: error while converting argument 0: [13:24:41] /tvm/include/tvm/runtime/packed_func.h:1564: \n---------------------------------------------------------------\nAn internal invariant was violated during the execution of TVM.\nPlease read TVM\'s error reporting guidelines.\nMore details can be found here: https://discuss.tvm.ai/t/error-reporting/7793.\n---------------------------------------------------------------\n Check failed: !checked_type.defined() == false: Expected Array[RelayExpr], but got Array[index 1: Array]\n

What parameters did you use to convert the model? You should try to use --train parameter, because TVM in SM Neo cannot convert NMS from PyTorch.


[Messung] Layout - Calculated Values

Put those calculated values below their labels; there should be enough vertical space. We save some horizontal space that can be used to give the left part of that measure-tab a bit more space.

The measurements are now under the labels


Require block reward in every block?

Currently it is up to block producers whether they want to include a block reward or not. I think faithfully implementing the economics whitepaper demands that block producers not have the power to stop inflation independently of on-chain governance. I think it also weakens consensus? I believe that if the main chain inflates slower than adversarial side chains can, the side chain stake distribution might become favorable (although I don't see how to execute this attack without triggering the epoch density comparison).

Have the proposer refuse to propose a block if it can't (doesn't?) include the block reward?

@bkase  to write script to monitor blks produced w/o coinbase

Ran the script during our meeting but didn't post updates on this issue.
~50 out of 400 blocks recorded had no coinbase when I check 11 days ago.


[REQUEST] Splash Screen

Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Would like to see a splash screen similar to Discord; a logo in the center a text with some data or curiosity right below.
This would be used mainly on the launcher initiation, but could be reused for other trouleshoot/updating/loading screens.

Describe alternatives you've considered
No response
Additional context
No response

It was done in #466


Show rule and spacing between CJK punctuations

Description
Thanks for the great work!
If I use show rule for CJK text, CJK typesetting go wrong.
In the code below, I think the first line and the second line of the output should be the same except for the color, but the actual result is not.
#[日」]#[「日]

#show regex(".+"): set text(fill: blue)

#[日」]#[「日]

Thanks.
Reproduction URL
No response
Operating system
macOS
Typst version

[X] I am using the latest version of Typst

i think it's a known bug. Also, IMHO, in terms of language design, regex show rule is a very bad idea.

@Enter-tainer

i think it's a known bug.

I searched for known issues but I couldn't find. Could you tell me the issue number?

regex show rule is a very bad idea.

In composition of CJK and western mixed texts, sometimes I want to use different fonts and font sizes for CJK texts and western texts. I use regex show rule for this purpose.
But I agree that this is not a good idea. If there are another method, I'll use it.

I searched for known issues but I couldn't find. Could you tell me the issue number?

i havent find it either. it is the current limitation of text regex show rules.

In composition of CJK and western mixed texts, sometimes I want to use different fonts and font sizes for CJK texts and western texts. I use regex show rule for this purpose.
But I agree that this is not a good idea. If there are another method, I'll use it.

https://github.com/typst/typst/issues/3331

https://github.com/typst/typst/issues/3331

This is what I wanted to. Thanks so much!
Limitation of regex show rule is also commented there.

Also, IMHO, in terms of language design, regex show rule is a very bad idea.

@Enter-tainer on some days I agree with this take, on others I see yet another thing that would not have been possible without regex show rules (e.g. today: some special highlighting of a specific word in a raw block).


Throw same exception as Cake when request is for missing action

Codecov Report

Merging #11 into master will increase coverage by 0.55%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master      #11      +/-   ##
============================================
+ Coverage     91.66%   92.22%   +0.55%
- Complexity       41       43       +2
============================================
  Files             8        8
  Lines            84       90       +6
============================================
+ Hits             77       83       +6
  Misses            7        7

Impacted Files
Coverage Δ
Complexity Δ

src/ParamConverterManager.php
97.14% <100%> (+0.59%)
17 <0> (+2)
: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 f545965...3ed042c. Read the comment docs.


help use

Good morning,
I tested the plugin and I can't understand how to add a label for example
MyUi = new UI("Overlay", (mainPanel,player) =>
{
  mainPanel.CursorEnabled = true;
  mainPanel.Image.Color = "1 1 1 0.5";
  mainPanel.Bounds.MinX = 0.1;
  mainPanel.Bounds.MaxX = 0.9;
  mainPanel.Bounds.MinY = 0.2;
  mainPanel.Bounds.MaxY = 0.8;

  mainPanel.AddLabel((label) => {
    label.Text = "test";
  });

//error Error while compiling te: A readonly field cannot be assigned to (except in a constructor or init-only setter of the type in which the field is defined or a variable initializer) | Line: 30, Pos: 21

Error while compiling te: Property or indexer 'UiBuilderLibrary.LabelElement.Instance.Text' cannot be assigned to -- it is read only | Line: 29, Pos: 9

You'll want to use label.Text.Text = "test" instead of label.Text = "test".
Here's a more full example:
mainPanel.AddLabel((label) =>
{
  label.Text.Text = "test";
  label.Text.Align = TextAnchor.LowerCenter;
  label.Text.FontSize = 65;
  label.Text.Color = ".9 .5 .1 1";
  label.Bounds.MinX = 0;
  label.Bounds.MinY = 0;
  label.Bounds.MaxX = 1;
  label.Bounds.MaxY = 1;

  return false;
});

thank you it works I have another question
I am making a grid and how I can return the cell id or Rows Columns position in the following example the label is always equal to 22 and I would like each cell to be a distinct id
Thank you for your help
subPanel2.AddGrid((grid) =>
{
grid.Rows = 2;
grid.Columns = 11;
grid.Bounds.MinX = 0;
grid.Bounds.MaxX = 1;
grid.Bounds.MinY = 0;
grid.Bounds.MaxY = 1;
for (var i = 0; i < grid.Rows * grid.Columns; i++)
{
    grid.AddCell((cell) =>
    {

        cell.AddLabel((label) =>
        {
            label.Text.Text = i; // all return 22
            label.Text.FontSize = 28;
            label.Text.Color = "0.27 0.33 0.42 1.00";
            return true;
        });
        return true;
    });
}

So this issue is caused by there only being a single reference to the variable i, and by the time the callback of adding a label is called, the for loop has already finished, thus i is at its max value.
To solve this, each iteration of the loop needs its own variable to store the current iteration number in so each callback call is only referencing the variable for its iteration in the loop.
for (var i = 0; i < grid.Rows * grid.Columns; i++)
{
    var index = i; // Store a scoped value of i - using this var instead of i in the rest of loop.
}


use pull_request_target to allow access to secrets

What this PR does / why we need it:
Allows the "add-to-project" github action to work for PRs from non-contributors. GitHub seems to allow access to secrets from these actions when they come from people with certain privileges, but will fail from other users.
https://securitylab.github.com/research/github-actions-preventing-pwn-requests/

LGTM


Fixing buffer in picodisplay micropython example: Issue #9

Not ready to merge straight away, fixes the picodisplay micropython example issue.
The Ball class is still an issue though, will have a crack at it tomorrow...
Signed-off-by: James Sutton<EMAIL_ADDRESS>

Related to Issue #9

Related to Issue #9


Missing install_requires for toml(i)

It looks like black_nbconvert uses toml, but the setup.py doesn't specify it in install_requires. Thus, an install in a clean venv fails:
$ black_nbconvert Untitled.ipynb
Traceback (most recent call last):
  File "/home/florian/tmp/.venv/bin/black_nbconvert", line 5, in <module>
    from black_nbconvert import main
  File "/home/florian/tmp/.venv/lib/python3.9/site-packages/black_nbconvert.py", line 10, in <module>
    import toml
ModuleNotFoundError: No module named 'toml'

Yes - this was changed in v21.7b0 of black and was fixed moments ago in v0.3.0 of black_nbconvert.


Pipe from request

Cool library. It works fine with files, but I can't get it to work with requests:
const request = require('request');
const unzip   = require('unzip2');

const run = () => {
  let stream = request.get(SDK_URL).pipe(unzip.Parse()).on('entry', entry => {
    entry.autodrain();
  });

  return new Promise((resolve, reject) => {
    stream.on('finish', resolve);
    stream.on('error', reject);
  });
};

This gives me:

{ Error: invalid distance too far back
at Zlib._handle.onerror (zlib.js:355:17) errno: -3, code: 'Z_DATA_ERROR' }

Any ideas?

I'm getting similar errors @RWOverdijk. I'd like to debug. Are you able to provide a file (or URL) to test this with that shows the error?

@mtharrison I was using this to download the google chromecast sdk. I worked around it by simply downloading the file first, and then creating a read stream from disk.

Do you know the URL for that? I tried https://developers.google.com/cast/downloads/GoogleCastSDK-Public-3.4.0-Release-ios.zip and it works with the above code. May I ask what OS you're on?

https://developers.google.com/cast/downloads/GoogleCastSDK-Public-3.1.1-Release-ios.zip for instance. (old, I know)
Mac os

Thanks, I'm also on Mac OSX. I tried to run your code above and it's executing just fine with that URL:
const SDK_URL = 'https://developers.google.com/cast/downloads/GoogleCastSDK-Public-3.1.1-Release-ios.zip';

const request = require('request');
const unzip   = require('unzip2');

const stream = request.get(SDK_URL).pipe(unzip.Parse()).on('entry', entry => {

  console.log(entry.path);
  entry.autodrain();
});

stream.on('finish', () => console.log('finished'));
stream.on('error', (err) => console.error(err));

Are you able to confirm that running the above gives you an error? Can I ask what versions of Node/Unzip2/Request that you're using?


DOI Provider: The VersionedDOIIdentifierProvider will check if the item level versioning is enabled

Is your feature request related to a problem? Please describe.
The VersionedDOIIdentifierProvider defined in identifier-service.xml does not check whether item level versioning is enabled.
Describe the solution you'd like
If the VersionedDOIIdentifierProvider is enabled, but the item level versioning is disabled, an exception will be thrown at startup.

Sounds like a bug. It sounds like it can be solved by correct configuration, but I agree this should result in exceptions at startup if possible.  Needs a volunteer


pull request for e2e test at 01/04/2017 23:26:13

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


deployed the handler successfully, but nothing happens just write staring execution and execution took ...

Hi I have recently updated the EKS to 1.19 and updated the AMI to 1.19 version in the autoscaling group which uses launch template and deployed the handler successfully, but after checking the logs nothing happens it just writes staring execution and execution took ...
Please advice. Here is my configuration file:
apiVersion: v1
kind: ServiceAccount
metadata:
  name: aws-eks-asg-rolling-update-handler
  namespace: kube-system
  labels:
    k8s-app: aws-eks-asg-rolling-update-handler
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: aws-eks-asg-rolling-update-handler
  labels:
    k8s-app: aws-eks-asg-rolling-update-handler
rules:
  - apiGroups:
      - "*"
    resources:
      - "*"
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - "*"
    resources:
      - nodes
    verbs:
      - get
      - list
      - watch
      - update
      - patch
  - apiGroups:
      - "*"
    resources:
      - pods/eviction
    verbs:
      - get
      - list
      - create
  - apiGroups:
      - "*"
    resources:
      - pods
    verbs:
      - get
      - list
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: aws-eks-asg-rolling-update-handler
  labels:
    k8s-app: aws-eks-asg-rolling-update-handler
roleRef:
  kind: ClusterRole
  name: aws-eks-asg-rolling-update-handler
  apiGroup: rbac.authorization.k8s.io
subjects:
  - kind: ServiceAccount
    name: aws-eks-asg-rolling-update-handler
    namespace: kube-system
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: aws-eks-asg-rolling-update-handler
  namespace: kube-system
  labels:
    k8s-app: aws-eks-asg-rolling-update-handler
spec:
  replicas: 1
  template:
    metadata:
      labels:
        k8s-app: aws-eks-asg-rolling-update-handler
    spec:
      automountServiceAccountToken: true
      serviceAccountName: aws-eks-asg-rolling-update-handler
      restartPolicy: Always
      dnsPolicy: Default
      containers:
        - name: aws-eks-asg-rolling-update-handler
          image: twinproduction/aws-eks-asg-rolling-update-handler
          imagePullPolicy: Always
          env:
            - name: AUTO_SCALING_GROUP_NAMES
              value: "asg-name"
            - name: CLUSTER_NAME
              value: some-name
            - name: AWS_REGION
              value: some-region
  selector:
    matchLabels:
      k8s-app: aws-eks-asg-rolling-update-handler

logs:
2021/09/23 08:06:06 Starting execution
2021/09/23 08:06:09 Execution took 3267ms, sleeping for 20s
2021/09/23 08:06:29 Starting execution
2021/09/23 08:06:29 Execution took 103ms, sleeping for 20s
2021/09/23 08:06:49 Starting execution
2021/09/23 08:06:49 Execution took 73ms, sleeping for 20s
2021/09/23 08:07:09 Starting execution
2021/09/23 08:07:09 Execution took 95ms, sleeping for 20s
2021/09/23 08:07:29 Starting execution
2021/09/23 08:07:29 Execution took 87ms, sleeping for 20s
2021/09/23 08:07:49 Starting execution
2021/09/23 08:07:50 Execution took 80ms, sleeping for 20s
2021/09/23 08:08:10 Starting execution
2021/09/23 08:08:10 Execution took 128ms, sleeping for 20s

no worries thanks for your update.
sure i will try it during my next EKS upgrade which will be in few days.

its working fine your answer.


python3Packages.xdis: ensure tests target the current Python version

Description of changes
ZHF: #199919
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

2 packages failed to build:

python39Packages.xdis
unrpa

1 package built:

python310Packages.xdis

Hm, bummer. Was looking for a quick fix of the build for ZHF and suspected the build was failing because our Python version is different now. Can’t say much about it otherwise I’m afraid.


 This is due to https://github.com/tapjs/signal-exit/issues/71.
1$ # terminal 1: debug server
1$ cat index.js  # very simple script
console.log("a");

1$ node --inspect-brk index.js

2$ # terminal 2: debug client
2$ node inspect --port=9229
connecting to <IP_ADDRESS>:9229 ... ok
Break on start in index.js:1
> 1 console.log("a");
  2
debug>

# terminal1
Debugger attached.
^C
1$ # killed with Ctrl-C

When proper-lockfile is used:
1$ cat index.js
const lockfile = require("proper-lockfile");
console.log("a");

1$ node --inspect-brk index.js

2$ node inspect --port=9229
connecting to <IP_ADDRESS>:9229 ... ok
Break on start in index.js:1
> 1 const lockfile = require("proper-lockfile");
  2 console.log("a");
  3
debug> n
break in index.js:2
  1 const lockfile = require("proper-lockfile");
> 2 console.log("a");
  3

# now we can't kill the server!

# terminal1
Debugger attached.
^C^C^C^C^C

Tested environment:

Ubuntu 20.04 amd64
Linux kernel 5.15.39+
Node.js v16.18.1

I think we should wait for https://github.com/tapjs/signal-exit/issues/71 to be responded in the meantime.


Upgrade dfx, base library and CI scripts.

My best guess is that something is going wrong with serialization of the result (?)
It's hard to say without diving deeper into the compiled Wasm, or its behavior, I fear.

My best guess is that something is going wrong with serialization of the result (?)
It's hard to say without diving deeper into the compiled Wasm, or its behavior, I fear.

@chenyan-dfinity There's something new happening with the latest moc and dfx.
Compiling and installing is fine, but during the more complex test, the compiled Wasm seems to hang right when it is supposed to return the (complex) result rendering.
Strangely, my other projects that use this same serialized type does not seems to have this issue -- e.g., this Alice-Bob chat example still works with the dfx version I am trying to use here (0.6.16).
What should I do to debug this further, I wonder?

@chenyan-dfinity There's something new happening with the latest moc and dfx.
Compiling and installing is fine, but during the more complex test, the compiled Wasm seems to hang right when it is supposed to return the (complex) result rendering.
Strangely, my other projects that use this same serialized type does not seems to have this issue -- e.g., this Alice-Bob chat example still works with the dfx version I am trying to use here (0.6.16).
What should I do to debug this further, I wonder?

Memo to future self: Remember Yan's advice: https://github.com/matthewhammer/motoko-adapton/pull/16#discussion_r551540736
(try doing dfx canister call --output raw to avoid the slow pretty-printer)

Memo to future self: Remember Yan's advice: https://github.com/matthewhammer/motoko-adapton/pull/16#discussion_r551540736
(try doing dfx canister call --output raw to avoid the slow pretty-printer)


Add files via upload

Your checklist for this pull request
Heaven Hobson
Author:
<!- GodlyAngel1613
About your game
What is your game about?
Avoid the poodles and endermen, they will kill you! and your goal Is to get the box In the goal without being killed by the poodle or trapped by the endermen!
WASD to move double K to start the game double J to reset the level and if you pressed the  J, to start the game again press K
Code
Check off the items that are true.

[x ] The game was made using the Sprig editor.
[ x] The game is placed in the in the /games directory.
[x ] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x ] The game runs without errors.
[x ] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x ] The game name is not the same as the others from gallery

Image (If an image is used)

[x ] The image is in the /games/img directory.
[x ] The name of the image matches the name of your file.

Thanks for your PR!

Hey there, do you need any help? I'm @alex (p variant) on the Hack Club slack if you want to DM me.


Fix getting container names of versions in openshift namespace; popd; done

This PR fixes problem when version in openshift namespace  is not the lesser one (example of s2i-python-container). In this case, NAMESPACE variable is not set back to openshift/ and created versions have wrong name.
@hhorak @bparees Same as sclorg/s2i-python-container#148. Please merge.

[test]
@hhorak Please merge.


Set vertical alignment on tabs

Fix #4214

@tomasantunes  Is this still desired? If so, it needs to be rebased on the latest master branch. Also, the above feedback should be addressed. Also, since this PR is a feature proposal, consider opening a proposal which explains example use cases and how this approach will solve the problem.
Otherwise, abandoned pull requests will be closed in the future as announced here.

Superseded by https://github.com/godotengine/godot/pull/44420. Thanks for the contribution nonetheless!


ObsHistID selection for Run 3

Are we doing all obshistID with fieldID = 1427 and propID = 56 from Minion 1016?  I should

[x] change the selection criteria in the phosim instance catalog generation script
[x] If it is not a single propID, I should drop duplicates

Good questions, thanks Rahul. We need to be able to investigate light
curves with both the WFD cadence and the DDF cadence, so I think we need
both these proposals (just like in real life, no?). I don't know what you
mean by "duplicates" - does each visit not have a unique proposal ID? Or do
some visits get labelled with both IDs, to make it easier to do things like
"select all visits at position x,y"?

Yes, combined would be closest to real life I think.

I don't know what you
mean by "duplicates" - does each visit not have a unique proposal ID? Or do
some visits get labelled with both IDs, to make it easier to do things like
"select all visits at position x,y"?

It is an OpSim thing: there are multiple records that are identical (including obsHist), except for proposalID (ie. the visit serves the purposes of two different proposals). We deal with that routinely, so I just need to remember to do it.

Great, thanks! I noticed a while back that the string "kraken" appears a
lot in our code. Can you confirm that minion_1016 is exactly the same as
kraken_1042 (3?) please? I'm pretty sure it is, but it's important
because when we write about this project, we need to quote minion_1016
(because only this one is the official baseline cadence).
On Thu, Sep 29, 2016 at 9:13 AM, rbiswas4<EMAIL_ADDRESS>wrote:

Yes, combined would be closest to real life I think.
I don't know what you
mean by "duplicates" - does each visit not have a unique proposal ID? Or do
some visits get labelled with both IDs, to make it easier to do things like
"select all visits at position x,y"?
It is an OpSim thing: there are multiple records that are identical
(including obsHist), except for proposalID (ie. the visit serves the
purposes of two different proposals). We deal with that routinely, so I
just need to remember to do it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DarkEnergyScienceCollaboration/Twinkles/issues/329#issuecomment-250514171,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AArY99JSfKbPoWIccBo7ewy8yDFaNBouks5qu-OagaJpZM4KJpQV
.

I noticed a while back that the string "kraken" appears a
lot in our code.
That should change. If you see kraken (except in the names of tables, please let me know). I would prefer we actually use minion if we write we are using minion.

Can you confirm that minion_1016 is exactly the same as
kraken_1042

I am going to ping @danielsf and @yoachim for the exact slight differences.

There are very minor differences between the two, despite having identical inputs.
I think this was an issue where things were stored in python dictionaries, so order of items was not guaranteed to be the same.

Thanks Peter. minion_1016 it is then!

@drphilmarshall I thought this was done and (had set it to autoclose when the setups pull request was accepted). What are you wanting us to do here?

I am taking this as closed, please reopen if something else is wanted.


Upgrade pallet atomic swap

Converts the atomic swap pallet to the new pallet attribute macro
Part of #7882.
Upgrade guidelines used.
:warning: Breaking Change :warning:
From https://crates.parity.io/frame_support/attr.pallet.html#checking-upgrade-guidelines

storages now use PalletInfo for module_prefix instead of the one given to decl_storage: use of this pallet in construct_runtime! needs careful updating of the name in order to not break storage or to upgrade storage (moreover for instantiable pallet). If pallet is published, make sure to warn about this breaking change.

So users of the atomic swap pallet must be careful about the name they used in construct_runtime!. Hence the runtime-migration label, which might not be needed depending on the configuration of the atomic swap pallet.
For polkadot and kusama atomic swap is not used, thus no migration needed there.

bot merge


Dynamic loading of language support

Don't link statically to tree-sitter-json and future languages. Investigate how https://github.com/helix-editor/helix does it.

See #595 for a discussion on also pulling the queries from upstream.

Are there any plans to address this in the near future? Thanks!

No, you're right. This issue can be closed.


Specific Energy calculation from DFN model

Does DFN model solution give specific energy calculation for each data points in PyBamm?

What do you mean by "data points" here?

@tinosulzer , I think he is asking about the specific energy calculation of the  cell at every voltage data points, i.e
de/dt = v * i(applied), for the specific time window.
@soumyadeeproy12 , Kindly correct if I am wrong

Fixed by #1969

Hey
I've done the model = pybamm.lithium_ion.DFN("calculate discharge energy" =='true') . Now I want to see the data of discharge, I meant data for the simulated model.


Switch loggo for logrus for more enterprise friendly licensing

Hey, I'm not sure if you were aware but loggo is LGPL'd which is causing it to get flagged in the CNCF's license scanning tool: https://app.fossa.io
You only used loggo in one test for configuring customer loggers. Logrus, which is MIT licensed, meets the necessary interfaces so this PR switches loggo for logrus to resolve the licensing issue.
@xizhao can provide more context on licensing and why we're trying to avoid (L)GPL.

Test failures seem the same as previous merged PRs that were failing. The specific test that was updated appears to be passing.

It is pretty silly. Removing this altogether.


Double check that build-sync updated the image stream

/hold

On hold because we're not sure what the heck really happened.
This is related to https://issues.redhat.com/browse/ART-1656

https://saml.buildvm.openshift.eng.bos.redhat.com:8888/job/hack/job/tbielawa-aos-cd-jobs/job/build%252Fbuild-sync/73/

Need to copy those changes into this branch

/hold cancel


Only require chewy railtie when Rails::Railtie is defined

When using ActiveSupport's inflector in a standalone
circumstance, the Rails module will be defined, but
Rails::Railtie will not; this causes Chewy to break bootstrapping
during bundling

The stack trace of this issue looks roughly like this ...
Bundler::GemRequireError: There was an error while trying to load the gem 'chewy'.
Gem Load Error is: uninitialized constant Rails::Railtie
Backtrace for gem load error is:
/usr/local/rvm/gems/ruby-2.1.9/gems/chewy-0.7.0/lib/chewy/railtie.rb:2:in `<module:Chewy>'
/usr/local/rvm/gems/ruby-2.1.9/gems/chewy-0.7.0/lib/chewy/railtie.rb:1:in `<top (required)>'
/usr/local/rvm/gems/ruby-2.1.9/gems/chewy-0.7.0/lib/chewy.rb:38:in `<top (required)>'
/usr/local/rvm/gems/ruby-2.1.9@global/gems/bundler-1.12.5/lib/bundler/runtime.rb:86:in `require'
/usr/local/rvm/gems/ruby-2.1.9@global/gems/bundler-1.12.5/lib/bundler/runtime.rb:86:in `block (2 levels) in require'
/usr/local/rvm/gems/ruby-2.1.9@global/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `each'
/usr/local/rvm/gems/ruby-2.1.9@global/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `block in require'
/usr/local/rvm/gems/ruby-2.1.9@global/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `each'
/usr/local/rvm/gems/ruby-2.1.9@global/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `require'
/usr/local/rvm/gems/ruby-2.1.9@global/gems/bundler-1.12.5/lib/bundler.rb:102:in `require'

Hey, just update it to be mergable please.

Will do.
Sent from my iPhone

On Aug 3, 2016, at 4:13 PM, Arkadiy Zabazhanov<EMAIL_ADDRESS>wrote:
Hey, just update it to be mergable please.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey! I've backported it to master


#84 Fixes of Schools are not plotted in map in streamlit app

Fixes #84

While Filtering data , schools will also shown in map in different color than center when we apply both (school/center) filter .

Using school list like in your first commit is a better idea as school-center-distance has a much larger row count.
Also instead of re-reading from tsv can we use dataframe in tab3? and build a dict[scode , (lat,long)] from from it so that we dont have to traverse school list multiple times

Using school list like in your first commit is a better idea as school-center-distance has a much larger row count.
Also instead of re-reading from tsv can we use dataframe in tab3? and build a dict[scode , (lat,long)] from from it so that we dont have to traverse school list multiple times

@sapradhan Completed these changes please review again.

thank you @nirmala-sharma
One more request. is it possible to add legend somewhere. Blue marker = school, Red marker = center


aws-sso-util console should just work if AWS_PROFILE is set to an SSO-enabled profile

Right now --account-id and --role-name as well as --sso-start-url and --sso-region, and --region are all required when  using aws-sso-util console launch or aws-sso-util get-token-config and at least in my common case those can generally all be inferred from the config settings in ~/.aws/config if AWS_PROFILE env var is set. Similarly I would expect AWS_DEFAULT_REGION env var to take priority if not specific on cli.
I'd then be able to run aws-sso-util console launch with no arguments!

Funny, I opened up the issues area to see if anybody else had said the same thing. Given all the other profile-centered goodness of aws-sso-util it's odd to have to recapitulate so many data elements that are already present (potentially, anyway) in a profile. This would be a nice enhancement.

This is the same as #61. In general, the idea behind aws-sso-util console is not to be an all-purpose web console launcher (which should work as long as there are valid credentials available), but rather to leverage the unique capabilities that AWS SSO provides, which is that you can have a specification of what identity to use without having actual credentials for that identity. That's what is contained in a config token.
Wouldn't it be confusing if aws-sso-util console launch "just worked" if you had AWS_PROFILE set to a profile that contained AWS SSO config, but didn't work if that profile contained, for example, a credential process? Or didn't work if credentials were set in environment variables?
Is what you're looking for a generic console launcher? As in, you don't have a use for the saveable/shareable config token functionality provided by aws-sso-util console, and you don't have a standalone tool that can accomplish console launching for you?

https://github.com/aws/aws-cli/issues/4642 is what I want, but it doesn't exist so I was hoping this tool would provide it and the AWS_PROFILE variable that I already have set (it's the right way to use AWS SSO) provides you all the info you need to generate the args required by aws-sso-util console launch.

You could check out granted... It offers assume -c <profile> to launch a console with a given profile, it works for all types of profiles, and it will manage the login to Identity Center also.

That's basically what I'm saying, there are tools out there to do this in a comprehensive way. aws-sso-util console is meant to explore packaging up console launching information in a saveable/shareable way.
The only difference I'd draw with existing tools if I was making a general-purpose launcher is that I wouldn't aim to fully manage the credentials; granted, awsume, etc. do things like stash the login token in the keychain and inject credentials through environment variables, but then breaks assumptions like the SDKs being able to refresh credentials themselves. I usually build things as thinly on top of AWS-provided tooling as possible.

Thankfully granted recently implemented a credential_process option, so now I use that. That way, the profile works fine with pretty much every SDK these days, and it doesn't clutter the env.


ipsec: fix stale keys reclaim logic

The current logic used to reclaim stale IPSec keys is incorrect. In
fact, whenever a new key is added we just spawn a new goroutine which
after linux_defaults.IPsecKeyDeleteDelay time will delete all keys
different than the one just added.
The issue with this approach is that if a new key is added while one of
these goroutine is still running, this goroutine will end up deleting
the new key.
This commit fixes this by introducing a single new goroutine that
periodically removes any stale key (XFRM state and XFRM policy template)
after enough time has passed since the current key has been added.
Fixes: https://github.com/cilium/cilium/pull/19814

I think we also need to clear stale XFRM policies, no?

Let me double check, but before this change the goroutine we spawned after a key becomes stale would only delete the XFRM state :thinking:
https://github.com/cilium/cilium/blob/0b58178dd5d8d9fac123c1cd7bb1c66e7c42c97f/pkg/datapath/linux/ipsec/ipsec_linux.go#L639-L645
https://github.com/cilium/cilium/blob/0b58178dd5d8d9fac123c1cd7bb1c66e7c42c97f/pkg/datapath/linux/ipsec/ipsec_linux.go#L263-L281

/test

/test

Two minor comments below.

Thanks for the review :pray:
New changes with this iteration:

defined a new constant for that shift value
introduced a couple of helpers to set and get the SPI from a XFRM mark
move the loop for deleting policies outside the state one

/test

/test

Updated to only take into account OUT XFRM policies when deleting stale ones

/test

/test

/test

/test

/test

/test

Since the last review I updated the PR with an additional call to NodeValidateImplementation() in keyfileWatcher():
https://github.com/cilium/cilium/blob/76a5bb907c2418050598fde28046fb4396507f9d/pkg/datapath/linux/ipsec/ipsec_linux.go#L729-L733
This should ensure that whenever a key is rotated the relevant XFRM states and policy are updated immediately rather than waiting on the backgroundSync() method of the node/manager package to eventually update the configuration

Latest iteration, taking @julianwiedmann feedback into account.
We don't want to assume that a user is always rotating keys less frequently than the linux_defaults.IPsecKeyDeleteDelay interval, and the current approach based on XFRM state timestamp is not going to work here as we need the time a key was deleted rather than the one it was added.
This new approach reintroduces the ipSecKeysRemovalTime local state to keep track of removal timestamps, and if an SPI is not in that map we assume it was just deleted and wait IPsecKeyDeleteDelay before removing it (in this way we manage also the case where the agent gets restarted while stale keys are still present, as after enough time has passed since the )

/test

/test-1.16-4.9

/test

/test-1.16-4.9

/test-1.24-net-next

/test-1.16-4.9

Latest iteration, taking @julianwiedmann feedback into account.
This new approach reintroduces the ipSecKeysRemovalTime local state to keep track of removal timestamps, and if an SPI is not in that map we assume it was just deleted and wait IPsecKeyDeleteDelay before removing it (in this way we manage also the case where the agent gets restarted while stale keys are still present, as after enough time has passed since the )

There's another reason why this is needed. If doReclaimStaleKeys() hits the time window just right so that only deleteStaleXfrmPolicies() reclaims a SPI, then we need to give deleteStaleXfrmStates() a second chance for this SPI when the reclaimer runs again.
If we can't avoid this scenario (ie. have a smart approach where we evaluate ipSecSPICanBeReclaimed() just once for each SPI), then we should at least adjust the comment in ipSecSPICanBeReclaimed().

Been trying to poke holes into the reclaim logic, but I think this should work :+1:. The agent-restart scenarios are certainly ... interesting. With the async filewatcher and reclaimer, I hope we still ensure that all the config happens in the right order.
Note that the commit msg for ipsec: fix stale keys reclaim logic might also need an update:

...
This commit fixes this by introducing a single new goroutine that
periodically removes any stale key (XFRM state and XFRM policy) after
enough time has passed since the current key has been added.
linux_defaults.IPsecKeyDeleteDelay has passed since this key was replaced.

If we can't avoid this scenario (ie. have a smart approach where we evaluate ipSecSPICanBeReclaimed() just once for each SPI), then we should at least adjust the comment in ipSecSPICanBeReclaimed().

Nice catch! What complicates things a bit is the fact that there are multiple states (4) and policies (2) for any given SPI, so we may as well end up with only half of the states removed :thinking:
I don't think an approach based on precalculating the list of SPIs (i.e .evaluate ipSecSPICanBeReclaimed() just once) could work:

we cannot assume that all states and policies for a given SPI are either all present or all removed (thinking about the case where the agent is restarted right before starting deleting old policies)
because of this we would still have to build the list of SPIs that need to be reclaimed by looking both at states and policies, going back to the original problem

Given that the issue is ipSecSPICanBeReclaimed() being dependent on the time it is called, what about getting that out of the equation and making that function take a timestamp (which then would be the timestamp of the  doReclaimStaleKeys() invocation?)

If we can't avoid this scenario (ie. have a smart approach where we evaluate ipSecSPICanBeReclaimed() just once for each SPI), then we should at least adjust the comment in ipSecSPICanBeReclaimed().

Nice catch! What complicates things a bit is the fact that there are multiple states (4) and policies (2) for any given SPI, so we may as well end up with only half of the states removed thinking
I don't think an approach based on precalculating the list of SPIs (i.e .evaluate ipSecSPICanBeReclaimed() just once) could work:
* we cannot assume that all states and policies for a given SPI are either all present or all removed (thinking about the case where the agent is restarted right before starting deleting old policies)

* because of this we would still have to build the list of SPIs that need to be reclaimed by looking both at states and policies, going back to the original problem

Agree, there's a lot of complexity there.

Given that the issue is ipSecSPICanBeReclaimed() being dependent on the time it is called, what about getting that out of the equation and making that function take a timestamp (which then would be the timestamp of the doReclaimStaleKeys() invocation?)

Sounds good!

/test-1.24-net-next


JS not working past Hugo v76.5

Is this a BUG REPORT or FEATURE REQUEST?:
bug
What happened:
Updating Hugo past v76.5 gives webpack_require error, and all the JS breaks. This looks like a known issue, so I won't go into it more.
What you expected to happen:
JS working
How to reproduce it (as minimally and precisely as possible):
Update Hugo past v76.5
Anything else we need to know?:
I want to update Hugo for some of their features to update my website. It seems like this is a longstanding issue with Syna, (I don't mind looking for a fix myself). Are there any leads that you have on fixing this issue so I don't have to start from ground 0? I will report back if I find a fix. Thanks!
Environment:

Syna Theme version:
Hugo version:
Others:

Known issue and PRs are welcome :)
For now using Hugo v76.5 is the solution, if asset compilation is necessary. Pages without asset compilation should work with later versions as well.

A bit more information here: https://github.com/okkur/syna/issues/847
As far as I could track it down until I ran into not having enough time was it being related with the difference between webpack 4 and 5. But couldn't pin it down to a specific thing.

Looking into it and will update here how far I got.

Great. Thank you.

Should have a few more specifics tomorrow I reckon.

Small update: Got it working with the latest Hugo version and think I know the culprit. Want to be sure on the whole issue before pushing it. Traveling next week, but afterwards should have a bit of time to finalize it.

That's excellent news!

A few things came up 😅, but have it on my list for next week. 🤞

Super! I really appreciate this project and the work you're putting in.

Had quite a few urgent refugee projects take up our time. We or I will get back to this as soon as possible.

Subscribing to this one as well.

I found out that disbaling JS minification works around the issue:
[minify]
disableJS = true

Thus, I think this issue came up with the bump of tdewolff/minify in Hugo 0.77.0.


add OptImportRoaring=true

update test - we only get 4 fields now because the exists field is hidden
one test is still failing because of how Range queries are generated in go-pilosa
fixes #117

Could you use RowRange instead of Range ? That should fix the failing test.

OK, fixed that


fractal-next: enable gstreamer-good support

gstreamer-good is in the legacy fractal package, seems to have been overlooked in the fractal-next port. providing this enables fractal to play inline video -- else the following output is observed for messages containing video:
ERROR fractal::components::video_player::imp: Error playing video: Error from element /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0: Your GStreamer installation is missing a plug-in.
Your GStreamer installation is missing a plug-in.
../gst/playback/gsturidecodebin.c(1049): no_more_pads_full (): /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0:
no suitable plugins found:
../gst/playback/gstdecodebin2.c(4704): gst_decode_bin_expose (): /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0:
no suitable plugins found:
Missing decoder: Quicktime (video/quicktime, variant=(string)iso)

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@uninsane, Could you please check if you can still build fractal-next, based on the latest master?
The build timeouts in CI and also when I run nixpkgs-review locally. It seems it's not caused by this PR, as this problem is already present in master.

The build times were about 30 minutes, or at least very long, before the timeouts happened, I think

fractal-next builds for me on master. as mentioned, it's lengthy: about 2 hours on a mid-range desktop, because rustc uses only a single core when linking it. you can rebuild it in about 5 minutes using an overlay like this:
nixpkgs.overlays = [(self: super: {
  fractal-next = super.fractal-next.override (upstream:
    nativeBuildInputs = upstream.nativeBuildInputs ++ [
      git  # only necessary when profile is development or hack
    ];

    mesonFlags = upstream.mesonFlags ++ [
      # profile: default, beta, development, hack.
      # - default causes a 2hr+ build, 98% of that being `rustc fractal` using a single core
      # - development has the same problem
      # - hack brings the build down to ~5 minutes, because it doesn't pass --release to cargo
      #   - it still has rustc using only ~4 cores typical
      "-Dprofile=hack"
    ];
  );
})]

Can you rebase this to after e9ca6038eb5f4398fc57feb4084b7df4afaa6d7d?

Can you rebase this to after e9ca603?

that was merged into staging. ping me again once it's merged into master?
in the meantime i rebased to f1818b1041cea87a8d7ecc969eed692d0688eb9f & it still builds cleanly, at least.

Sorry for not approving earlier, but Fractal 5 has now been merged. Feel free to use this diff to update (GitHub wouldn’t let me upload it as a file)
diff --git a/pkgs/applications/networking/instant-messengers/fractal/default.nix b/pkgs/applications/networking/instant-messengers/fractal/default.nix
index d0723653e159..fd96316a0943 100644
--- a/pkgs/applications/networking/instant-messengers/fractal/default.nix
+++ b/pkgs/applications/networking/instant-messengers/fractal/default.nix
@@ -72,6 +72,7 @@ stdenv.mkDerivation rec {
     gstreamer
     gst-plugins-base
     gst-plugins-bad
+    gst-plugins-good
   ]);

   passthru = {

rebased for fractal 5


feature: I have some processes to should be executed before loading lazy nvim

Did you check the docs?

[X] I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.
I have a piece of code that activates the python virtual environment, and it should be done before loading the lsp configs (which is done by lazy.nvim)
Describe the solution you'd like
As described
Describe alternatives you've considered
Not yet
Additional context
No response

init from lspconfig?
or just put the code before the lazy setup

Oh yeah, at first I thought lazy was async because I put vim.schedule in my code. It is fixed now, thanks !


Cleanup script for CI testing

We're currently deploying but for CI testing it would be great to have a quick way to remove and return to a pristine environment without redeployment

done


fid

Dear author, I have a question: Regarding calculating the Fid index, even generating 5000 samples to calculate Fid would take a long time, such as one day. What is the reason for this? It takes 30 seconds to generate a batch of 8 for the graph.
Looking forward to your reply,Thanks

As shown in Table 7 of the paper, for RCG-L, generating one image using one V100 takes around 0.45 seconds. Therefore it should take less than 4 seconds for a batch of 8 images. What type of GPU do you use? Different GPUs can have totally different running time.

As shown in Table 7 of the paper, for RCG-L, generating one image using one V100 GPU takes around 0.45 seconds. Therefore it should take less than 4 seconds for a batch of 8 images. What type of GPU do you use? Different GPUs can have completely different generation speed.
Thank you for your reply. The GPU model I am using is 3090 and the graphics memory is 20GB


Fixing Button text ignores breakline (\n) #2967

After a long review of the code, the discussion on the issue #2967 page and the other merged issues (#4327 and #21334), I present a solution proposal.
In this comment, @StraToN say :

line breaks in Buttons' captions won't work for the moment. I will leave this apart.

And that's what I did. I fix the tabs in the Buttons' captions, Labels text and Control tooltips and fix the line breaks in the Label text and Control tooltip.
Before

Break Line (\n)
Tab (\t)

Inspector
Label
prints the characters
prints the characters

Tooltip
prints the characters
prints the characters

Button
prints the characters
prints the characters

GDScript
Label
It works
discards the characters

Tooltip
It works
discards the characters

Button
discards the characters
discards the characters

After

Break Line (\n)
Tab (\t)

Inspector
Label
it works
it works

Tooltip
it works
it works

Button
prints the characters
it works

GDScript
Label
It works
it works

Tooltip
It works
it works

Button
discards the characters
it works

Fix  #2967

@cesarpinho Please fix the conflicts.

Requesting rebase.

@cesarpinho The merges you pushed aren't the same as a rebase. Godot requires contributors to make their PRs have good Git history in order to be accepted.
Please see this article for more information: https://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html

@cesarpinho Requesting rebase and squash.

This PR has not been in a good state for over a year, closing.


C# Support for null response messages

What version of gRPC and what language are you using?
1.19.1, C#
What operating system (Linux, Windows,...) and version?
Windows 10
What runtime / compiler are you using (e.g. python version or version of gcc)
.NET Framework 4.7.2
What did you do?
We recently tried to upgrade form 1.16.0 to 1.19.1, but encountered a new error.
We use a custom serializer (based on protobuf-net instead of Google.ProtoBuf), which can produce null byte arrays as response messages. Returning a null as the serialized byte[] worked in 1.16.0, but in 1.17.0+ it throws the following exception on the client side:
Status(StatusCode=Internal, Detail="Failed to deserialize response message.")
The actual (unfortunately swallowed) inner exception is thrown here:
https://github.com/grpc/grpc/blob/5344c81f3c7701a6b1864faa2da91041c1e29e03/src/csharp/Grpc.Core/Internal/DefaultDeserializationContext.cs#L49
This check was introduced with https://github.com/grpc/grpc/pull/17167/commits/5344c81f3c7701a6b1864faa2da91041c1e29e03
What did you expect to see?
I understand that supporting a null byte[] as response is probably not a design goal as the default tooling with Google.ProtoBuf does not allow it anyway, but would it be possible to support this in the SerializationContext?
I have also considered a workaround, namely sending an empty byte[] and setting a flag in the response trailers, something like "IsResponseNull". This would then allow the client to distinguish between null and an empty byte[]. Unfortunately this only works for async calls, not for sync calls (which we also need). This is because the response trailers are only available via the AsyncCall class and this is only returned for the async methods in CallInvoker, but not for CallInvoker.BlockingUnaryCall (which returns just the response).https://github.com/grpc/grpc/blob/af283b3183eca452733e5eb7ac767cb17242199d/src/csharp/Grpc.Core/CallInvoker.cs#L33
Is there another way to get the response trailers for successful sync calls? Or would it be possible to add a variant of BlockingUnaryCall that returns an AsyncUnaryCall (or something similar, that particular name combination would be a bit strange)?

Returning null as a response message was always meant to me illegal, we just started enforcing that more strictly. The problem with null messages is that grpc as a protocol actually doesn't support them.
It is of course possible to send a zero-length message, which translates to a byte buffer of length zero, but a "null" message is illegal (see https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md). It seems like it's something that just happened to work in your case, but it's not a supported use case, so I'd strongly recommend to stop trying to use "null" payloads (
and use "empty" messages that serialize to a zero-length byte array instead).
The workaround you're suggesting seems fragile - if you really need to support null responses, why don't you just wrap the response in another layer of protobuf message that allows a nested message to be null, but will never be null itself?
message NullableResponse
{
    MyResponse myResponse = 1;
}

Btw, because of the way the proto binary format works, if myResponse = null, the message will still serialize as an empty byte array (= you won't waste any bandwidth).


"Vite requires Node.js version 14.18+, "

Documentation is

[ ] Missing
[X] Outdated
[ ] Confusing
[ ] Not sure?

Explain in Detail
Please drop support for versions of Node that are not currently maintained by the Node.js project.
Your Suggestion for Changes
Please see the Node supported versions document and do not reference any older versions in documentation.

Why
I am now three days into setting up "Hello World" with Vite + Vue + TS + Prettier + Yarn Berry + ESLint + Prettier plugins.
And I already reached the OpenAI limit for how many o1-preview tokens I can use getting help.
Seeing a mention of "Node 14" in the documentation does not demonstrate that the documentation is up-to-date.
When something is that hard to install just to get started, and your energy level or emotion level is anything less than "I am willing to spend 40+ hours to get hello world running" then any quality sniff like that does not demonstrate an actively maintained and useful project.
Reproduction
No response
Steps to reproduce
No response

Please see the Node supported versions document and do not reference any older versions in documentation.

Can you point out where did we reference that?

Sorry about that, that was on the old v3 documentation page
https://v3.vitejs.dev/guide/

So I think that info is correct, and this this issue is wrong. Closing.

In separate news: https://github.com/vitejs/vite/issues/18420


Working code sample for S3?  Document how to construct S3Client with auth and config?

The blog post sample does not set a configuration or authentication provider for the S3 client.  The headers do not document how to construct one.  The test harness offers clues but not an example that I can copy.
According to the headers, I can use this:
S3Client(const Auth::AWSCredentials& credentials, const Client::ClientConfiguration& clientConfiguration = Client::ClientConfiguration());

But that requires me to successfully create those objects.  I poked around the core headers and found this:
AWSCredentials(const Aws::String& accessKeyId, const Aws::String& secretKey, const Aws::String& sessionToken = ""

But the code below will not compile -- "incomplete type not permitted"
const char* secret_id = "foo";
const char* secret_key = "bar";
Aws::Auth::AWSCredentials creds(secret_id, secret_key);

I'm guessing I need to do something with < > and AWS::foo but guessing that without documentation or samples is going to be difficult.

I'd recommend against manually constructing credentials. The default constructor will use the default credentials provider chain. This will first check your environment, then your profile config file (~/.aws/credentials), and then check the ec2 metadata service (if you are on ec2 and have an instance profile attached.
Anyways, for explicitly what you are trying to do, you need to #include <aws/core/auth/AWSCredentialsProvider.h>  and then it should work.
We cover this in the video listed in the readme.md

Thanks, and d'oh! I should have thought of the include file but I assumed it was pulled in automatically from the other includes.

We cover this in the video listed in the readme.md

D'oh! again, I don't normally watch videos to learn an API, I assumed it would be too high-level of an introduction to include details like this.  My bad, I'll Watch The Friendly Manual  :)

No problem. For more context, we try to always forward declare everything to help with build times. Most of the time, you'll have to hunt down a header file if we are only using the type as a reference, return value, or pointer.


mac-10 lost external connection from phone device.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
mac-10 lost external connection from phone device.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Rebooting phone device to restore connection.


No message confirming item deletion [CRUD items page]

After deleting an item there should be displayed an info popup as when adding or removing items.

it also concerns the "Documents" page. After deleting a document there is no confirming message.


Unable to update eslint due to resulting configuration errors

Issue
In the process of keeping react-native-macos up to date with the upstream repo, we've run into issues where we can't upgrade eslint (and dependencies related to eslint) without causing a bunch of errors.
For example, if we try to upgrade eslint to 6.8.0 as per a4757d28235617b6448ea962b66e2ee0c88ca331 and add any other devDependencies as needed, everything under packages/eslint-plugin-react-native-community fails yarn test with errors such as this one:
: Configuration error:

Could not locate module ~/react-native-macos/node_modules/babel-eslint/lib/index.js mapped as:
~/react-native-macos/$1.

Please check your configuration for these entries:
{
  "moduleNameMapper": {
    "/react-native(.*)/": "~/react-native-macos/$1"
  },
  "resolver": undefined
}

Similar issues come up when we try merging in 0b68f3cf77cb96df18535764b68f40b3fa89ed37, which is why #802 skipped over that commit. (Notice that babel-eslint was still kept at version 10.0.1 instead of being bumped up to 10.1.0 as a result of this pull request.)
Thankfully, this only affects the Javascript validation process, and any Javascript we're bringing in should already be validated when it was committed upstream, so this shouldn't be a big showstopper for us. That being said, it would still be nice to get to the bottom of these configuration errors so we can more properly keep everything up to date.

After investigating another bug attempting to merge upstream commit a77f2c40d1044da63426078f356cfc7c1284a79e into react-native-macos, I found that our jest.config.js file was being a bit too lenient on this key-value pair of moduleNameMapper:
'react-native(.*)': '<rootDir>$1'
This replacement appears to solve the problem:
'^react-native(.*)': '<rootDir>$1'
It will be included in the next upstream merge after #822 gets pulled in.


Add an option to visualize audio being played

What do you mean about visualize audio been played?

To be able to get the heights of the currently playing audio, something like this:

(in the middle is the current position)

I think you mean then to get the amplitude of the sound wave in each time? So that you can plot this chart using something else? I'm not sure how easy is to extract that information from the files, it might require complex calculations that might be better suited for a separated library. I'm not an expert either, so maybe someone here can help us out?

try this https://github.com/iamSahdeep/FlutterVisualizers but it need to get audio session id

try this https://github.com/iamSahdeep/FlutterVisualizers but it need to get audio session id

This does not support what I want, but its author is willing to add it in the future.

I think you mean then to get the amplitude of the sound wave in each time? So that you can plot this chart using something else? I'm not sure how easy is to extract that information from the files, it might require complex calculations that might be better suited for a separated library. I'm not an expert either, so maybe someone here can help us out?

Yeah, I think you are right.

@dvorapa does supports https://github.com/iamSahdeep/FlutterVisualizers  what you need? You said that it need an audio session id, is this? https://developer.android.com/reference/android/media/MediaPlayer#getAudioSessionId()

No, FlutterVisualizers does not support what I need, see https://github.com/iamSahdeep/FlutterVisualizers/issues/1#issuecomment-510914715

Okay, if it got implemented, and you need to get the session id, we could see the possibility to implement a getter for that on this package. But since this is a different issue, I will close this. Feel free to open a new one for the audio session id.

Okay, if it got implemented, and you need to get the session id, we could see the possibility to implement a getter for that on this package. But since this is a different issue, I will close this. Feel free to open a new one for the audio session id.

Okay, so audioplayers will not support amplitudes and sound waves for songs being played?

I'm not sure how easy is to extract that information from the files, it might require complex calculations that might be better suited for a separated library.

Maybe you are right, separate library would do. But it requires someone who knows well internals of native Android audio player and is also more an audio expert

I don't think so, this package is focused on playing audio, which already is quite complicated given all the available options, configurations, since this is a visual thing, I guess it out of the scope of this package, and since there is already a lib focused on that, I don't this kind of stuff been implemented here.
But we would gladly implemente a way to fetch the audio session id, so you can use audioplayers alongside a specialized lib for visualizing audio waves.

This is more like analyzing audio file statically than using current session id.


copy task issue

Short description of the problem:
I added a new entry to the copy dictionary to get some node_modules file copied to the build folder. Unfortunately the file doesn't get copied.
What behavior are you expecting?
node_modules/file copied to www/build folder
Steps to reproduce:

Add a custom copy.config.js in your ionic 2 app

"config": {
    "ionic_copy": "./config/copy.config.js"
  }

Add a new entry to the copy dictionary in ./config/copy.config.js

copySW_Toolbox: {
    src: ['{{ROOT}}/node_modules/sw-toolbox/sw-toolbox.js'],
    dest: '{{BUILD}}'
  }

Run ionic serve

Which @ionic/app-scripts version are you using?
0.0.45
Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Maybe this issue is related to https://github.com/driftyco/ionic-app-scripts/issues/448#issuecomment-264735182.
And other people are experiencing the same problem (https://github.com/driftyco/ionic/issues/9035) also.

This should be resolved in 0.0.47.
Thanks,
Dan


Replace GetFiles with EnumerateFiles

Tracking issue.
GetDirectories and GetFiles are implemented using Linq ToArray and an internal method IEnumerable<string> InternalEnumeratePaths, so there is no gain in avoiding the EnumerateDirectories/EnumerateFiles methods.

@xtqqczze Can we close the tracking issue?