cmd/link: TestDWARF failing on freebsd/arm since August 2020

The freebsd-arm-paulzhol builder has been failing since August with
--- FAIL: TestDWARF (8.89s)
    dwarf_test.go:41: cmd/link is stale - run go install cmd/link
FAIL
FAIL	cmd/link	125.383s

Unfortunately, the builder has been mostly out-to-lunch for a long time (cc @paulzhol ). The last successful run was 4489f4bc846392e85973ae30e662bd0f3cefbd9b on June 5th and the first failing run was 8acbe4c0b392840062cf882886e2424c5f07a665 on August 22nd.
@golang/osp-team , what should we do about this builder and/or the freebsd/arm port?
cc @cherrymui @jeremyfaller @thanm since it's a linker test. But the builder is effectively inaccessible, so it would be very hard to test a fix.

@aclements I've tried to debug it in https://github.com/golang/go/issues/41101 but without much success. I will gladly provide access / bring it back online. I was planning to upgrade it to FreeBSD 12.2.

I think I've seen that failure when there was non-reproducible object files. I believe that there was a bug I introduced sometime during that pass/fail window that Cherry fixed, and that test should universally pass.

Personally I don't really like that stale check. I understand that it was there to catch the situation where someone is developing the linker locally, runs go test without go installing the linker first, which will get a wrong result. But I don't think it belongs to that particular test.

it isn't useful for a builder or CI system
if we want to do that, it'd probably better be an init function or TestMain.

It is true that it is weird that the linker is reported stale there (and not earlier by cmd/dist, if it is really stale). I could try to debug. But I also want to bring up the idea that we just remove that staleness check.

As I understand it, the test is already disabled for darwin-amd64 builders by https://golang.org/cl/223925.

@cherrymui

it isn't useful for a builder or CI system (where the toolchain is always freshly built)

For the moment, at least, the staleness check is useful in CI because it helps to detect cases where the build of the toolchain is somehow incomplete, corrupted, or out of sync (such as #33598 and #35740, which have yet to be diagnosed and fixed).
It's fine to remove the check if it isn't actually verifying a property relevant to the test, but if the staleness of cmd/link actually is relevant to the test then the check should stay — if we remove it, that just papers over some underlying problem that remains for the builder.

Sorry, I'd missed that this was already reported in #41101 (I searched around but somehow didn't find that). Let's close this as a dup and move the conversation over there.


LLVM ERROR: Incomplete scavenging after 2nd pass

Describe the bug
In some projects, the capsule build --release will raise this error.
https://github.com/jordanmack/nervos-ckb-nft/commit/f38598cdb05a92e3fdca8385c418058b676be35c
Screenshots
jjy@LAPTOP-BRD86RAC:~/workspace/nervos-ckb-nft$ capsule build --name nft --release
Building contract nft
   Compiling nft v0.1.0 (/code/contracts/nft)
LLVM ERROR: Incomplete scavenging after 2nd pass
error: could not compile `nft`

To learn more, run the command again with --verbose.
error: docker container exit with code Some(101)

Additional context

capsule --version Capsule 0.4.1

Solution
This supposed to be an upstream issue, to edit the Cargo.toml lto=false can get around this in capsule projects.

Is this something we can file a report at Rust or even LLVM side?

Sure, I'll try to reproduce it with a minimal example.


Refine Smart Contracts entry

Abandoning in favor of:
https://github.com/MystenLabs/sui/pull/3319/files


In terms of joint reasoning, is there any other example besides 'Example1：Using Joint Inference Service in Helmet Detection Scenario'

If I replace the model and image of helmet detection with others, can it be combined for reasoning (Joint Inference Service).


Code Of Conduct Updates and Translation

There are some errors in the existing code of conduct. It seems to be outdated. For example, the conference staff do not use clothing from the conference so they are not easily identified.
I wonder if this is a good time to revise/update the code of conduct? CC: Founders @gcollazo @froi @jpadilla @axelrivera
Some examples we can use are: Citizen Code of Conduct and the DjangoCon Code of Conduct.
P.S. I don't seem to have push access to the repo, so I made this fork.
English translation:
Short version
Our conference is dedicated to offering a welcoming experience for everyone, regardless of their gender, sexual orientation, ability, appearance, ethnicity or religion. We do not tolerate abuses towards the participants of the conference in any form. Sexual language and/or sexualized images are not appropriate for any aspect of the conference, including talks, workshops, gatherings, Twitter or any other online medium associated to the event. Conference participants who violate these rules could be sanctioned or expelled from the conference without any reimbursement, at the discretion of the conference organizers.

We expect participants who are made aware of their abusive behavior to immediately comply and stop said behavior.
Conference sponsors are also subject to the policies against abuse. In particular, sponsors should not make use of sexual content. Conference personnel (volunteers included) should not make use of clothing/uniforms/disguises that are sexual in nature.
If a participant incurs in abusive behavior, the conference personnel reserves the right to take official action, which may include warnings as well as expulsion from the event without any reimbursement.
If you are suffering from abuse at the conference, know of anyone suffering from abuse, or feel uncomfortable in any other way, please contact any conference personnel immediately.
The conference personnel will gladly help participants in contacting the security personnel of the event location or the local authorities, provide escort out of the conference, or otherwise assist those who are the victims of abuse in any way so that they can feel comfortable during the event. We value your assistance.
We hope that participants follow these rules and regulations in the conference, workshops and any other social event related to the conference.

@rnegron thanks for the help! the translation looks good to me. I'll add it to the site.


Support multiple clusters

I can create two clusters，but cannot support. Hope to support the creation of multiple clusters just like CM.

Pull requests are not feature requests, rather code change proposals.  Ambari uses JIRA for tracking issues.  Please see https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1715/
Test FAILed.
Test FAILured.


-p option issues

I am seeing different behavior depending on the base image, so I am not sure if this is an issue in Docker or somewhere else.
To reproduce the issue, start with setting up a container
$ docker run -it -p 8888:9999 debian:wheezy
# apt-get update && apt-get install -y netcat
# netcat -l 9999

Then on the host machine
$ telnet localhost 8888
Trying <IP_ADDRESS>...
telnet: Unable to connect to remote host: Connection refused

When I set up the container with ubuntu
$ docker run -it -p 8888:9999 ubuntu:14.04
# apt-get update && apt-get install -y netcat
# netcat -l 9999

I do get a connection with telnet on the host machine
$ telnet localhost 8888
Trying <IP_ADDRESS>...
Connected to localhost.
Escape character is '^]'.

Why is this behaving differently?

I'm pretty sure this is something within the debian image/container - like a firewall.
Try running the telnet command from within each container (telnet localhost 9999). For me, the ubuntu one worked, but debian didn't.  Which would seem to indicate that its not docker issue but something within the container.

You're right, running it from within the container doesn't work either. So should I create an issue here?

well,I'm not familiar enough with debian:wheezy, but is it that something is wrong with the image or just need to find the right command to disable the firewall?  assuming it is a firewall issue.

I'm gonna close this since I don't think its a docker issue

@sgillis This explains why: http://superuser.com/questions/455875/why-is-nc-l-xxxx-not-opening-a-port


Make selector connect() non-blocking for SSL connections

Currently, for connections over SSL, the ambry selector returns an established connection after a poll even before the handshake is completed. This is not very useful as the caller will then have to repeatedly check outside of the selector poll on whether the handshake is complete, which is not ideal.
Instead, let the selector do the work as part of the poll. The selector should only return a connection after the connection is established and the handshake is complete. If the handshake does not complete for any reason, then it should be treated as a connection establishment failure. This way the callers of the selector can be agnostic to SSL, and can interact with the selector in a completely non-blocking way.

https://github.com/linkedin/ambry/pull/310


[REPO SUGGESTION] Enable discussions and/or create chat anywhere

GH Discussions are better for some questions I wanna ask, than issues
Chat.. Like anywhere, Matrix or Gitter, Discord or sth else

Sorry for previous issue on VanSwitch

Hello, thanks for the suggestion, i enabled discussions as you asked!
Have fun!

Hello, thanks for the suggestion, i enabled discussions as you asked!
Have fun!


Insufficient quota

The steps of provsions are confusing in my opinion and even after going through multiple times and hours of research, couldn't make it work. Lots of Time Lost !
InsufficientQuota: This operation require 30 new capacity in quota Tokens Per Minute (thousands) - GPT-35-Turbo, which is bigger than the current available capacity 0. The current quota usage is 1 and the quota limit is 1 for quota Tokens Per Minute (thousands) - GPT-35-Turbo

Hi, is your subscription enabled for OpenAI? You can look at the prerequisites here: https://github.com/Azure-Samples/azure-openai-rag-workshop?tab=readme-ov-file#azure-prerequisites
and fill the form linked here is needed.
This error may happen for many reasons:

Either your don't have access to Azure OpenAI (you need to fill the form)
You're trying to deploy in a region where you do not have quota. Some regions have limited capacity, in that case you can try redeploying to another location, for example eastus2


Fix manifest generation bug in Android export

Related if not a total fix for #4777.
This was a memory bug. After resizing a vector and potentially resizing it again with push_back, pointers held to data become invalid. So depending on the circumstances (release vs. debug, allocation chunk size, current size of allocated block, etc.) chars may be pointing to old memory and writes through it don't end up where they should and, moreover, they could be smashing other data or cause SEGFAULTS.
(I'm detailing the bug report with a general explanation because this may serve for future reference for someone.)

I'm not 100% sure. but this works my first attempt. 👍


Initial

closes #1

@rultor merge

@rultor merge

@l3r8yj OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@l3r8yj Done! FYI, the full log is here (took me 1min)


Carousel - function getActiveIndex() does not exists when there is only 1 slide present

Hi there, I just discovered a bug with the Carousel component of the latest version 2.0.25, at least in v4.
When the Carousel has just 1 item, I get the error "function 'getActiveIndex()' does not exists".
When I add 1 or more slides, the functions does exists again somehow.
Open the modal and click the button "Get active slide index" in the following example to see the error. https://codepen.io/anon/pen/jJMBQr

For a single slide-item I won't need the Carousel component at all.

There is a reason why I use the Carousel for single items. Besides that, this is an issue that should be fixed no matter how many items I need in the Carousel.

I disagree. The Carousel component is meant to be used with interactive content where you have 3 or more slides.
I think for this quirks alone, you should do a fork.


Trying to delete solutions

Hello there,
Yesterday, I updated both the Core Components and the Audit Logs solutions to the latest versions.  On the previous version of Core Components, I had made changes to the CLEANUP - Admin | Sync Template v2 (Power Apps User Shared With) flow.
Also, I was seeing that the data bug from #638 was not resolved in my instance.
When I updated the Core Components, I noticed that the flow still says v2 while the ones that updated say v3.  I tried to follow the steps to remove unmanaged layers as shown in https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates.  But I believe that because I'm in GCC, I cannot see that option

So I attempted to delete the Core Components solution so I could re-import it fresh (like I've done before).  It has a dependency of the Audit Log solution so it wouldn't delete.  OK, so I try to delete the Audit Log solution and it won't delete.  It has a dependency.  The "tenant" environment variable is used by the Power Platform Admin View app.  Because that app is part of a managed solution, the delete option is grayed out.

I'm stuck.  Do you have any tricks I could try that might help?
Thanks!

I'm sorry I dont have help for you here. Deleting solutions is something that doesnt work very well. You may be in a terrible state at this point and have to just start from a fresh environment.
I'm really sorry about this.
If you'd like to persue help from the product team first, you can create a ticket.
Once you get the update working, or you fresh install, if 638 still repros, please re-post and the engineer that fixed will take a look.

I'm sorry I dont have help for you here. Deleting solutions is something that doesnt work very well. You may be in a terrible state at this point and have to just start from a fresh environment.
I'm really sorry about this.
If you'd like to persue help from the product team first, you can create a ticket.
Once you get the update working, or you fresh install, if 638 still repros, please re-post and the engineer that fixed will take a look.

I was afraid of that.  I will create a ticket and reference this issue for details.
Thank you.

I was afraid of that.  I will create a ticket and reference this issue for details.
Thank you.

Of course, and I'm terribly sorry about the pain.

Of course, and I'm terribly sorry about the pain.


NIST NVD (Independent Publisher) issue

Api Name - shared_nistnationalvulnerip
Bug description - cannot see any connection in Power Automate
Is this a security bug? (Y/N) N
What is the severity of this bug? LOW
i want to use the connector with powerautomate but i dont see any connection related.

NVM i managed


New package: UlamMethod v0.1.1

Registering package: UlamMethod
Repository: https://github.com/70Gage70/UlamMethod.jl
Created by: @70Gage70
Version: v0.1.1
Commit: 961f24a92ed518d64409193038c8f6812b627ea8
Git reference: HEAD
Description: A package for discretizing trajectory data into a transition probability matrix using Ulam's method.

@JuliaRegistrator register

@JuliaRegistrator register

@JuliaRegistrator register()


Technical: General comments and corrections [2024/03/26]

Description
Some elements are missing/wrong in the technical (/documents/technical-specifications/technical-specification.md) and should be updated as soon as possible.
Severity

Critical (Severe impact)

Version
a4ad752
Expected Correction
Line 271
No approximations in the document & missing comma
Current:
However some simple statements can be written in one line, as long as it doesn't take more than 50 characters aproximately.
Expected
However, some simple statements can be written in one line, as long as it doesn't take more than 50 characters
Line 287
Awkward phrasing
Current:
### Example of a good code*
Expected:
### Expected piece of code
Line 319
Remove your comment on "this is a non-sense"
Line 321
Awkward phrasing
Current:
# 5. Software's technical specifications
Expected:
# 5. Software's technical implementation
Lines 327 to 334
General rephrasing in the overview section
Current:
We don't have access to the application, the server with which the SIM card communicates or the final hardware. And we are not supposed to use our smartphones to test the NFC or the bluetooth.
That's why the company has explicitly suggested that we only **simulate** the complex interactions with the hardware, such as Bluetooth communication or sending data over the 2G network (soon to be obsolete), by using forced values such as "bluetooth_unlock = 1 or 0 : the user has pressed the button on the application or not".
The company's request is really to improve the software by finding an effective algorithm, and not to write assembly to make components working. (It is the reason why we only had 4.5 weeks to work on, while it is usally 6 or 7.)
We will therefore focus on technical detail only on the points where we can take action. These are:
- battery management and energy consumption (sleep mode, power cut, ...)
- multi tasks to make the buzzer ringing and to send the notification at the same time, while also being able to stop the alarm at any moment.
- take the NFC into account
- movement detection (improve the way to detect a theft)

Expected:
We don't have access to the server with which SportShield communicates, thanks to the SIM card. Additionally, we don't have access to the final hardware as the product is still a prototype.
The company suggested we should assume we have access to it and could add whatever we want if we want to add additional functions on the server side.
We will therefore focus on the technical details specified in the KPIs given by the client. These are:
- Battery management and energy consumption (sleep mode, power cut, ...)
- Multi-tasking to make the buzzer ring and send notifications at the same time, while also being able to stop the alarm at any moment.
- Add NFC management to unlock SportShield.
- Improve movement detection to enhance the distinction between an accidental bump in the lock from a real theft attempt.

Lines 338 and 349
Awkward phrasing:
Current:
In this file there are :
Expected:
This file contains:
Lines 349 to 354
Enhancement of readability
Current:
In this file there are :
- **inclusion** of the different **headers** (and not the libraries -> 'definition.h')
- the '**void setup()**' where are executed only functions.
  this function contains the code which will be executed once at the beginning after a reload of the program on the board (after a power-up or reset)
- the '**void loop()**'
  this function has the role of a 'while(true)' loop : it is the main loop

Expected:
This file includes:

- Calls to the different **headers** (*.h/*.hpp files)
- The `void setup()` function: *It contains the code executed once to setup the environment after a startup or a reset of the board.*
- The `void loop()` function: *It contains the code which will be ran during the whole execution of the program. It acts as a while loop.*

Line 380
Rephrase to allow better understanding
Current:
We don't need to forecast what is in the 'void setup()' function. This is just all the initializations of the different components and libraries, and the setting of what is the initial state of the device.
Expected:
The `void setup()` function is not part of the algorithm itself. Its only purpose is to import the required libraries and headers and describe the program's initial state.

Line 382
Unacceptable comment in a document!!!
Current:
Now, the algorithm itself, the main loop of the firmware, is available in this diagram (please forgive the size !) :
Expected:
This leaves the core of the algorithm, the `void loop()` function. The following diagram describes the expected behaviour of the lock:

Lines 386 to 389
Uniformization among all the bullet points:
Current:
It allows :
- the battery consumption's management
- execute parallel tasks when a theft is detected
- to take advantage of the NFC

Expected:
It allows :
- To manage the battery consumption
- To execute parallel tasks when a theft is detected
- To take advantage of the NFC

Line 400
Approximation in a value
Current:
If the battery level is ABOVE 15%, NFC only is enabled because NFC consume like 5mA while Bluetooth Low Energy (BLE) consumes 15mA (3 times more).
Expected:
If the battery level is ABOVE 15%, NFC only as it is less energy-consuming (5mA) compared to Bluetooth Low Energy (BLE) which consumes 15mA.
Line 403
Wrong verb forms
Current:
If only one of these components are required, we turn on both D4 and D9, and a variable have to keep track of the number of devices currently used. If there is any, D9 and D4 are turned OFF to save as much energy as possible.
Expected:
If only one of these components is required, we turn on both pins D4 and D9. Concurrently, a variable has to keep track of the number of devices currently in use. If none is in use, D9 and D4 are turned OFF to save as much energy as possible.
Line 409
Missing information of library name
Current:
Also, the percentage of the battery and the management of its charge will require a specific public library called...
Expected: Add the name of the library involved
Line 411
Typo and clarification
Current:
A key feature of the battery management ids the ability to know the current capacity (%). There are 2 methods for that :
Expected:
A key feature of battery management is the ability to know the current capacity as a percentage. There are 2 methods to achieve this objective:
Line 412
Typo and rephrasing
Current:
- The ideal one but over-consuming electricity is to measure constantly the voltage and the intensity which goes out from the battery to know how much energy had beeen used or had been loaded in real-time. However it is almost impossible to imlement and this solution using though a 'coulombmeter' is reserved for very particular usages.
Expected:
- The ideal but most energy-consuming option is to measure constantly tension and intensity in the battery to know the battery level in real-time. However, in our case, this option is not convenient as it requires a coulombmeter.
Line 413
Typo and rephrasing
Current:
- The very spread solution is to just measure the current voltage and to compare the value to a set of previous measures took to define the correlation between the current capacity and the current voltage.
Expected:
- The very spread solution is to just measure the present voltage and to compare the obtained value to a set of previously measured values. We can then correlate values between the maximum and the present voltage to obtain the battery level.
Line 422
Typo and total rephrasing
Current:
Furthermore, as the temperature would be quite low, around 41°F to 23°F (as it is mainly for skis and snowboards), the discharge should avoid to eceed 80% of the total capacity. We finally get a minimum voltage (if the battery is in a cold environement) of 3.4V corresponding to a 0%. Also, we will used some standard curves of discharge to evaluate the current battery capacity based on the voltage we can get from the board itself (included function).
Expected:
Furthermore, as the temperature would be quite low, from 41°F to 23°F on average (as this product targets winter sports equipment), the discharge should avoid falling below 20% of the battery level. This limits the risk of the user device reaching the minimum voltage we can get in the battery: 3.4V, corresponding to 0% of charge, meaning the battery cannot be charged again anymore.  Complementarily, we will use some standard curves of discharge to evaluate the current battery capacity based on the voltage we can get from the board itself.
Line 424
Confusing and somewhat useless sentence
Line 435
Definition after the term which should be in the glossary. This section also lacks multiple information
Current:
As the buzzer is controlled by a MOSFET, we decided to use PWM (Pulse Wave Modulation = a high frequency square wave, where the proportion of ON/OFF time in average can be set), to make the piezzo-electric buzzer ring lower. A simple R-C circuit would have been better to smooth the output voltage to the buzzer, but as the MOSFET has a capacitance, even if the song is not the same we succeeded to get a lower noise from the buzzer.
Expected:
As the buzzer is controlled by a MOSFET, we decided to use PWM[^ref], to make the piezzo-electric buzzer ring lower. A simple R-C circuit would have been better to smooth the output voltage to the buzzer, but as the MOSFET has a capacitance, even if the song is not the same we succeeded in getting a lower noise from the buzzer.
Line 439
Sentences need to be shortened and rephrased
Current:
As the Seeed boards company released their Xiao-NRF52840 quite recently, we found on the official forum of the company website for documentation, that they said they still didn't ended to develop the NFC library of their board. The problem with this unfinished library, is that, as they have their own version of RFID microship and circuit, embedded in the board, the only solution we found to try having it working, is by coding our own library directly in assembly. That's why we probably won't develop the concrete NFC functions more than simulating input and output through the terminal.
Expected:
As the Seeed boards' company released their Xiao-NRF52840 quite recently, they still didn't end up developing the NFC library of their board, as said on their forum. This raises a major issue. As they have their proprietary version of the RFID microchip and circuit, the only workaround would be coding our library directly in assembly. That's why we probably won't develop the concrete NFC functions more than simulating input and output through the terminal.
Line 442 to 446
Empty sections that might need content addition
Expected: Addition of the missing content
Other Details
/

Typos OK 👌

LGTM 👍


Possible typo in implementing-a-concept-exercise.md

Shouldn't it be <slug>.js instead of <slug>.cs at line 93?

Is that file in this repository?

Affected file: https://github.com/exercism/javascript/blob/main/reference/implementing-a-concept-exercise.md
In the affected file at line 93, it says "<slug>.cs. the stub implementation file......". But the file tree presented in README shows <slug>.js.
Again when creating a pull request, the auto generated comment says "or the stub file <exercise>.js....". Here the file extenstion is also .js. So maybe it is a typo in the affected file.

You are correct! Would you like to submit a PR to update this file and rename .cs to .js?

Yes. Opening a PR soon.


SEO: page meta descriptions for organic SERPs

Let me know if interested in having me work on the pages in docs and writing up optimized meta descriptions for search engine discoverability.
Let me know!

Could you please elaborate with some examples? I'd like to know more about the topic anyways.

Closing due to inactivity...


Need to implement a price improvement rule...

...need to allow for the possibility that ask or bid orders might be rejected unless they improve upon the current best ask or bid limit prices.  In the literature this property is typically referred to as a price improvement or spread reduction rule.

After reading Wellman and Walsh I think we need to implement three rules...

an AscendingRule requiring that an acceptable Order be superior to existing orders
a DescndingRule requiring that an acceptable Order be inferior to existing orders
a SpreadReductionRule that imposes an AscendingRule on BidOrder and a DesendingRule on AskOrder

...all of these rules would provide implementations of the place(order: Order) method of an AuctionLike class.


The CSS in the compiler options option does not work in the production environment

Description
//vite.config.js file
export default defineConfig({
  plugins: [svelte({
    compilerOptions:{
      css:true,
    },
  })],
})

In the production not work.

I think the following line of code has an impact
https://github.com/svitejs/svite/blob/1ddc78417259d70aa7cdff49b4eaebf7d5434df8/packages/vite-plugin-svelte/src/utils/compile.ts#L32

I'll make it easier to load svelte components without having to load two files

Easier to load really depends on the usecase. But it looks like i was wrong to assume emit would fit everyone. A future version of vite-plugin-svelte is going to support emitCss: false for production builds. see linked issue above


test: cmd/cli/mesh_list.go

In cmd/cli/mesh_list.go, the osm mesh list command does not have good unit test coverage. See highlighted lines below:

It would be great to write a small test for this function that ensures that the output of osm mesh list is as expected, for example:
MESH NAME   NAMESPACE        CONTROLLER PODS                   VERSION   SMI SUPPORTED
osm         arc-osm-system   osm-controller-6d76cb8c98-wss7q   v0.8.3    Unknown

Helpful reference: osm namespace list test: https://github.com/openservicemesh/osm/blob/main/cmd/cli/namespace_list_test.go

ref #1489

Issue made on previous code coverage report. Coverage has been increased to 81% already


Keep all erlang libs private header file in Alpine

From OTP Design Principles \ 7.4  Directory Structure
http://erlang.org/doc/design_principles/applications.html#id81280
include/ - Optional. Used for public include files that must be reachable from other applications.

Ideally, all public header files for other applications should be placed in the include/ directory,
and src/ can contain *.erl source code, and private header files are ok kept under src/;
However in practice, some standard app is not following the convention,
like <ssl/src/ssl_api.hrl> is designed as a public header file, but
already referenced by many 3rd party applications (like rabbit_common)
https://github.com/erlang/otp/blob/master/lib/ssl/src/ssl_api.hrl
So the workaround is to keep all private header files, there's no
statistics how many other private header files are also used as public ones;
resolves #39

Landed in 67e6c5f resolves c0b/docker-elixir#39


Promise doesn't work

I try to using Promise but nothing works out. The following code doesn't work:
var promise = new Promise(function(resolve, reject) {
    resolve(123);
});

promise.then(function(result) {
    console.log(result);
});

This code will work fine if I execute it in a browser.

I checked the above code in JSContext without running Microservice - works fine!!
What could be the problem?

I have found another interesting thing. If I kill process process.exit(0); then the promise function resolve(123); will be executed.

I have found problem. When I start Microservice I eval the code setInterval(function(){}, 3600000);
When I changed code to setInterval(function(){}, 1000); pomises have worked.

I find it shocking that setInterval would cause other events to block!  Let me see if that is the intended behavior.


Range-Slider options don't update after _reflow

What should happen?
$('#sliderid').attr('data-options', 'display_selector: #sliderOutput2; start:5; step:0.5; end:20;');
should update data-options of range-slider after $('#sliderid').foundation('_reflow');
What happens instead?
New data-options are visible in code but are not used. Instead the slider uses the old range.
Test Case and/or Steps to Reproduce

Test Case: https://codepen.io/XSized/pen/RBNaJy
Click the button to change the data-options. Range-max should be 20 after click but stays on 12.
"Inspect Element" shows, that the options are set, but they are not used.
Context

Need to change range of different sliders at runtime.
Your Environment

Foundation version(s) used: 6.4.2 and 6.4.3
Browser(s) name and version(s): Latest Chrome
Operating System and version (desktop or mobile): Windows 10

Checklist (all required):

[x] I have read and follow the CONTRIBUTING.md document.
[x] There are no other issues similar to this one.
[x] The issue title is descriptive.
[x] The template is correctly filled.

Tried your codepen - looks identical to me.
Inspecting element shows, that the options are set but they are not used after reInit.

Hm? The button now actually triggers a change. Not sure what you mean.

Really? I trie your codepen with Chrome and Firefox. After clicking the button the slider range should be 5-20 - but it still ends at 12.

At least it moves back to 3 here in Chrome 67.

The reinit may not (yet) change the max value. We will check this.

https://codepen.io/DanielRuf/pen/NBPjdE
Yes, destroy + complete reinitalization works:
  $('#gns').foundation('destroy');
  $('#gns').foundation();

cc @ncoden don't we have already a PR about the needed change for reflow / reInit?

OK, the workaround with destroy works vor me, nice. Maybe it's not the best solution, but a solution ;)

The reinit may not (yet) change the max value. We will check this. - @DanielRuf

Afaik none of the components provide a straight way to update it's option. So far it only seems to be possible via destroy & (re)init what is suboptimal.
There's another issue regarding this: https://github.com/zurb/foundation-sites/issues/11329

Found now, that $('#gns').on('changed.zf.slider', function()
does not work anymore after destroying and reinitializing the slider.
$(document).on('changed.zf.slider', function() still works. That's crazy...

Found now, that $('#gns').on('changed.zf.slider', function()
does not work anymore after destroying and reinitializing the slider.
codepen.io/XSized/pen/djoZXd
$(document).on('changed.zf.slider', function() still works. That's crazy...

This is normal, please try $(document).on('changed.zf.slider', '#gns', function(), this is intended as the listener is reapplied and how it should be done with jQuery, this is not a bug.


security email: discourage use #760

open to suggestions - i just wanted to post something to prompt discussion.

Honestly we could just drop the email alias on the website and put it on Github only, then link more strongly to the github on the contact page?

Agree, hopefully that would solve the spamming issue, assuming those who would see it on Github won't still email it for support.
Alternatively, if dropping the email alias from the site is too destructive a change, the security disclosure bit could be left the way it currently is on the site (small and easy to miss). The stack exchange can be left in bold, as someone desperately seeking help would likely be in a rush for answers and the large community support message in this PR would catch their attention first (which is good). However, seeing another large message for security disclosure might cause them to consider that as an option for getting support as well (even despite the "not for support" message, people are just funny like that).
Regardless, I'd prefer just dropping it from the site and moving it to Github only as suggested above.

@TheBlueMatt

Honestly we could just drop the email alias on the website and put it on Github only, then link more strongly to the github on the contact page?

I'm happy to merge any changes wanted by the people on the list, but if moving the disclosure information to a different URL is something you think would work, we could just move it to a different page on the site.

Oops, to clarify, I’m not advocating moving security disclosure to GitHub issues, I’m suggesting that the only mention of the security disclosure alias be on GitHub issue default text or other similar. It’s just an idea and I’m not on that alias anymore so I can’t speak for anyone :).

On Aug 23, 2021, at 06:15, David A. Harding @.***> wrote:

@TheBlueMatt
Honestly we could just drop the email alias on the website and put it on Github only, then link more strongly to the github on the contact page?
I'm happy to merge any changes wanted by the people on the list, but if moving the disclosure information to a different URL is something you think would work, we could just move it to a different page on the site.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Concept ACK. Thank you for working on this. I think this is a good solution to further discourage use of the alias for technical support, that it's only for reporting security issues.

Alternatively, if dropping the email alias from the site is too destructive a change, the security disclosure bit could be left the way it currently is on the site (small and easy to miss).

Agree, no need to make the "responsible disclosure" part big. People who find security issues tend to be good at finding semi-hidden links too :smile:

0aeee59

ee2884d

1a12a84

197d098

dea9847

Here are a few variations to cherry-pick from...

Tested ACK dea98475b78ea9fa115bc81634218e9876115adf .  I think the current commit tip is one of the better options, and there's no need to delay this further---we can always tweak things again later.
Thanks @RandyMcMillan for working on this and for providing multiple options!


Remove NAME_KEY from addon/validations/factory.js

Resolves #626 (but resolves it on the 3.x branch)
Changes proposed:

This removes NAME_KEY  on the 3.x branch. See commit: https://github.com/offirgolan/ember-cp-validations/commit/283fc0596b2ee8a44eaa87704a56f135a69dd4ae
This lets users use ember 3.12 and ember-cp-validations without using a beta.

Tasks:
[x] Ran tests--tests passed:
1..266
tests 266
pass  266
skip  0
fail  0

Released with v3.5.6. Thanks for the PR @jbarmettler!


36.2.1 appears to ignore install_requires with extras

Travis, Appveyor, and local builds of magic-wormhole started failing about an hour ago, when 36.2.1 was released. Our setup.py has:
      install_requires=[
          "spake2==0.7", "pynacl",
          "six",
          "twisted[tls] >= 17.5.0", # 17.5.0 adds failAfterFailures=
          "autobahn[twisted] >= 0.14.1",
          "automat",
          "hkdf",
          "tqdm >= 4.13.0", # 4.13.0 fixes crash on NetBSD
          "click",
          "humanize",
          "ipaddress",
          "txtorcon >= 0.19.3",
      ],

When I run pip install -e . in a virtualenv with setuptools-36.2.0, I see Autobahn-17.7.1 installed as expected. If I have setuptools-36.2.1, then Autobahn does not get installed. (Twisted does get installed, but it's a dependency of txtorcon).

Should that be pip install -e '.[twisted]'?

Because of the extra specifiers:
setup(install_requires=["autobahn[twisted] >= 0.14.1"])

is equivalent to
setup(extras_require={'twisted': ["autobahn >= 0.14.1"]})

Previously those were ignored.

Nope, in this case, the un-extra-ed magic-wormhole installation requires both the base autobahn and autobahn's twisted support. (magic-wormhole depends upon twisted directly, but when you ask autobahn to give you its twisted support, it could conceivably depend upon something beyond just twisted, maybe some tx*foo package).
Depending upon autobahn instead of autobahn[twisted] gets you a subset of the functionality that we need.
The only extras that magic-wormhole supports are pip install magic-wormhole[dev], and a :sys_platform=="win32" that gets us some extra windows support.

Oh, what? Have I been mis-expressing this all this time?
What's the syntax to say "I want dependency X and also X's extra Y"?

No, I think I'm the one being wrong, and I have introduce a regression...

https://www.python.org/dev/peps/pep-0508/#extras

Whew, ok, good :). I looked at https://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies , and it seems to match the way magic-wormhole's setup.py is doing things.

I'm having the same problem.
$ cat setup.py
from setuptools import setup
setup(
    name="testtest",
    install_requires=['requests[security]']
)

$ pip install .
Processing /Users/bright/Playground/testtest
Installing collected packages: testtest
  Running setup.py install for testtest ... done
Successfully installed testtest-0.0.0

$ pip freeze
testtest==0.0.0

But I expected:
$ pip freeze
asn1crypto==0.22.0
certifi==2017.4.17
cffi==1.10.0
chardet==3.0.4
cryptography==2.0
enum34==1.1.6
idna==2.5
ipaddress==1.0.18
pycparser==2.18
pyOpenSSL==17.2.0
requests==2.18.1
six==1.10.0
testtest==0.0.0
urllib3==1.21.1

setup(install_requires=["autobahn[twisted] >= 0.14.1"])
is equivalent to
setup(extras_require={'twisted': ["autobahn >= 0.14.1"]})

I'm pretty sure this statement is wrong.
The former syntax says "this package depends on autobahn with its twisted extra and autobahn should be version 0.14.1 or later". The latter syntax says "this package offers an optional feature called "twisted" and if you ask for thispackage[twisted], this package will additionally depend on autobahn 0.14.1 or later."

Fix released with 36.2.2.

was reopening this intentional?

No. I'm not sure how that happened. Thanks.


Issue with display of 'Opens in new window' tooltip when viewing guidance

Please complete the following fields as applicable:
Expected behaviour:
The 'Opens in new window' tooltip is visible/readable
Actual behaviour:
If the guidance has a link at the bottom, the tooltip is obscured by the surrounding container.
Steps to reproduce:

Login
Create a new plan based on the default template (click 'no research org' and 'no funder')
Make sure that the DMPTool/DCC guidance is selected
Go to the 'Write Plan' tab
Expand the 'Selection and Preservation' section
Click on the DMPTool/DCC guidance tab of the 1st question
Expand the 'Preservation' themed guidance
Hover your mouse over the last hyperlink in the guidance

Sample of this issue from:

Brian to take a look this week.

test

Tooltips don't always display in mobile phone. Maybe use 'title' in html file instead?

Toolitp was visible and appeared over the text on which I hovered. Worked well.

Looks good to me as well

Tooltip is wrapping for me too. Closing out


spec/GetDatabase() exposes panic in datas/http_batch_store.go at user level

While attempting to resolve #2862 , I wrote the following test program:
package main

import (
  "fmt"
  "os"
  "github.com/attic-labs/noms/go/spec"
)

func main() {
  sp, err := spec.ForDatabase("http://localhost:8000")
  if err != nil {
    fmt.Fprintf(os.Stderr, "Bad database spec: %s\n", err)
    return
  }
  sp.GetDatabase()
  defer sp.Close()
  fmt.Println("Exiting cleanly!")
}

If you run this program while running a local noms server, then it exits successfully with no output.    As it stands, the workaround for the example code is to recover() from the panic:
func main() {
  sp, err := spec.ForDatabase("http://localhost:8000")
  if err != nil {
    fmt.Fprintf(os.Stderr, "Bad database spec: %s\n", err)
    return
  }
  defer func() {
    if err := recover(); err != nil {
      fmt.Fprintf(os.Stderr, "Could not connect to database '%s'\n", sp.Spec);
    }
  }()
  sp.GetDatabase()
  defer sp.Close()
  fmt.Println("Exiting cleanly!")
}

This produces the expected output...
> go run main.go
Could not connect to database 'http://localhost:8000'

... but per the guidelines on error reporting in CONTRIBUTING.md, user-level code probably shouldn't have to "catch" panics to recover in a relatively conventional use case such as the server being unavailable.  It seems like some layer of this stack should be returning an error variable instead.

From the error reporting guidelines in CONTRIBUTING.md:

For problems that might occur during correct processing, you can choose the Go-style of returned errors, or use the following to 'raise' a 'catchable' error (see go/d/try.go):
d.PanicIfError()
d.PanicIfTrue()
d.PanicIfFalse()

The code in question, having encountered an error that might occur during correct processing, used d.PanicIfError() to raise a catchable error. You should be doing this:
err := d.Try(func() {
  sp, err := spec.ForDatabase("http://localhost:8000")
  sp.GetDatabase()
  defer sp.Close()
  fmt.Println("Exiting cleanly!")
})
if err != nil {
  fmt.Fprintf(os.Stderr, "Bad database spec: %s\n", err)
}

It seems like since this is user-facing, it should use the comma-error idiom.


Branch

Before selecting the "Create pull request" button:

Enter a meaningful title above^, using a prefix if necessary and keywords "New" or "Update" indicating the nature of changes.

Describe the summary, scope, and intent of this PR:
Changed Order of new Item Azure Arc Private Link Scope

This is from: Add private Link Scope for Azure Arc #1333

Insert links(s) to any related work item(s) or supporting detail:

AFTER YOUR PR HAS BEEN CREATED, expand this section for tips and additional instructions.
These are common guidelines for contributions across the repos managed by the Cloud Architecture Content Team (CACT). Some repositories may have additional specific requirements that are not listed here.
Guidance for all contributors

Topic
Guidance

Draft PR
If your PR will be a work-in-progress for more than a day or two, select the Convert to draft link in the upper right of the page (under Reviewers) to change it to a draft. For future reference, you can also do this using the Create pull request button drop-down during PR creation.

ms.date metadata
Don't update an article's "ms.date" metadata property unless you've done a full freshness review of the content. A full freshness review includes changes required to correct or improve the full technical accuracy of the article.Don't update "ms.date" if you're doing targeted changes to improve non-technical aspects of the article, such as editorial quality, art improvements, article template alignment, etc.If you've changed any "ms.date" properties for work that wasn't part of full review for freshness, please reset them to their previous value.

Placement and linking
If you're creating a new article or articles, include updates to the related TOC.yml file to propose where the article(s) should be placed. Also consider other places within the document set where it would be beneficial to cross-reference and link to your new article(s).

PR build
After you open your PR, and for each successive commit that you push to your branch, the publishing platform will run validation on the files in your pull request. A summary of the build results for each file will be inserted inline into your pull request, which includes any build suggestions/warnings/errors. PRs cannot be merged until all build errors and most warnings are resolved.

Publishing
Following a successful merge, most repos publish to the live site at least once per (business) day, usually around 10am Pacific.

Additional resources
Learn.Microsoft.Com contributor guide

Additional guidance for private repos and internal contributors

Topic
Guidance

PR size
If your PR is more than ~5 lines of changes, or you'd like for the changes to go through editorial or larger review, open a contribution request at https://aka.ms/Contribution and include a link to the PR in response #8. Once it's processed, you'll be notified of the next steps.

PR title prefix
Select the Edit button to the right of the PR title if you need to revise it. The following prefixes are reserved for specific contribution types:[Quality Check] - maintenance work related to content quality (edit passes, art improvements, template alignment)[LinkFix] - recurring/adhoc PRs to correct link URLs[Pipeline] - new/updated contributor success pipeline content[WIP] - a work-in-progress draft requiring several days/weeks

PR preview
Following successful build of your PR, publishable files will also include Preview URL links to staged previews of your new/updated articles. Be sure to review these for verification of your intended contributions, or to send to other internal contributors for review.

PR sign-off (public repo)
If an article you own is updated in a public repo PR, you are responsible for sign-off. You will be automatically notified via email. The PR will not be merged until you've had a chance to review and sign-off.

PR sign-off (private repo)
After you've completed your proposed changes, addressed build warnings, and completed all review work, you can begin the sign-off process for review and merge:If your PR is in draft mode, remove "[WIP]" from the title and select Ready for review button at the bottom of the PR.Enter "#sign-off" in a new comment. This comment indicates that you're confident the work meets or exceeds Microsoft's standards for publication, and will trigger the review process.Your PR may be selected for initial review by the CACT. Following CACT review, you may receive questions or requests for additional changes. You should have initial feedback from CACT review within a few business days. If you have an urgent request or need to contact the team, please mention @MicrosoftDocs/cloud-architecture-content-team-pr-reviewers in your PR and someone will get back to you. After CACT review is complete, a CACT #sign-off will be added.Final review/merge is done by the PR review team. The PR team may also respond with feedback, categorized as "Blocking" (requires action from you), or "Non-blocking" (to be addressed in a future PR).

Additional resources
Learn.Microsoft.Com internal contributor guideAuthoring templates: architecture-center-pr, well-architected-prTo contact the CACT use e-mail, or @mention our GitHub team in your PR comments using: @MicrosoftDocs/cloud-architecture-content-team-pr-reviewers

@ckittel - I committed your edits.
@stephen-sumner - do you want to review?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@ckittel - take a look and LMK if that's in the right place now. thanks

@stephen-sumner  - Please review the proposed changes. If you want to move forward with the content, add a sign-off.
#label:"pending-content-team/business-approval"
cc @MicrosoftDocs/patterns-and-practices-team-pr-reviewers

still waiting for @stephen-sumner to review. will nudge him.

@Jak-MS thanks for pinging me. This looks good.
cc: @ckittel

PnP #sign-off
#remove-label:"pnp-review-in-progress"
#remove-label:"do-not-merge"
#label:"ready-to-merge"


Generation of SAML SP metadata file

Description:
When configuring an external IdP, automatic generation of the SP metadata file for WSO2 would simplify the process.  WSO2 already supports reading these files in the inbound authenticator
copied from the plugin repo as this one seems to get more attention:
https://github.com/wso2-extensions/identity-outbound-auth-samlsso/issues/55
Suggested Labels:
Component/SAML, Type/Improvement, Affected/5.4.0
Steps to reproduce:
go through the steps to connect one WSO2 instance to another via SAML, there is no apparent option to generate SP metadata in the menus involved

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


Idea: Alternative connection through FTDI/UART

Reason: BT and 2.4GHz are often jammed by frsky and other stuff. 433MHz for example will handle without a problem with much more longer distances.
Idea: Connect FTDI converter through OTG cable.
To FTDI you can connect any device like:

straight cable to arduino
433MHz (or other) modems on frequencies which are not in use by race quads.

Application: need to be changed.
Arduino side: no need - just any other device than BT module.
Hardware: For example FTDI based on CH340G (tested with library) and pair of transmiting devices which can handle 115kbps on air.
Proposed library: https://github.com/mik3y/usb-serial-for-android
I'm not so expeirenced with java but for now only FTDI library is merged.

Can 433Mhz modules handle the baud rate?

Many 433MHz data links for pixhawk/apm telemetry are able to use 250kbps air speed to maintain 115kbps inner connection for device.
Here is example of device which is working at different frequency but its able to work at 250kbps also:
http://www.banggood.com/3DR-Radio-Telemetry-915MHZ-Module-For-APM-APM2-p-73539.html
From what I've seent most of those devices are using:

USB with build in FTDI converter
transmiting modules which can be configured with AT commands.

Within end of month I'm going to replace BT module (config link) on my Pixhawk flyer. It is good oportunity to check link device for other purposes :)

Would it work with a ESP2866? Those are arduino compatible, so you could run the whole thing in one, and setup a wifi hotspot on your phone.
You could even log the results in a mqtt server or talk to the app over wifi.

ESP8266 works with 3.3v, so you would need something to provide two voltages (3,3v for ESP and i think 5v for the RX module).

If you have one of those modules with usb, like the nodemcu amica or adafruit huzzah, there is the usb/5V pin if you power it via usb. I do that to power a DHT11 temperature sensor that also needs 5V and it works.

Or maybe some logic level converter might work.


installing git-lfs and downloading large files on travis

adding a test for large files existance in the "large" test group
large files should be available for tests on travis after this pull request

Review complete -- back to @lbergelson

One additional comment: can you please update the hellbender README to mention the necessity of running git lfs pull?

@droazen Back to you.  Should be fixed.

Back to @lbergelson -- one comment then merge away


refactor: run.sh and run-ollama-docker.sh

This pull request includes a few updates to shell scripts:

Added shebang to shell scripts.
Added user prompt to run ollama in docker with or without GPU support.
Updated ollama Docker image tag to the latest version.
Update scripts with port variables.
Refactored run-ollama-docker.sh and run.sh scripts for better readability.

LGTM, Thanks!


Spelling command corrected

Thank you for fixing these @mariumfirdous 🖖
Merging ✨ 🎉
One note or the future: From what I understand, you're creating branches from other feature branches.
Like spelling-command-corrected was branched off from spelling-corrected branch. This was in turn branched off from spelling-mistake-corrected.
If your intention is to have a separate pull request for each change, you gotta create new branches from main (master) branch.


feat: sort juno first in quickstarts and frameworks

Motivation
I'm annoyed that Juno is slightly moving towards the end of the list of the tools displayed on the developer docs.
Changes

Move Juno back as the first item in the list of "Quickstarts & Frameworks" (before "Testnets" and "React").

Thanks, @jessiemongeon1, truly appreciated!


feat: add support for nameOnly option to listDatabases

NODE-1129

LGTM, with the same nitpick as your other PR. This one might be feat(listDatabases): ...


Test cluster/WalletContext always check execution result

Description
Always check transaction execution result in TestCluster and WalletContext.
For cases where we expect the transaction may fail (typically non-testing cases), we add another API explicitly for it.
Test Plan
CI

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

nit: I think it's better to call this must-succed version execute_tx_block_must_succeed and the may-fail version execute_tx_block

The must-succeed version is called significantly more often than the may-fail version (almost all except a few). My concern is that, when people are adding new test, they tend to call the default name which doesn't check

Introduced a _must_succeed version in wallet context, but also a short cut name in TestCluster


Cannot install @angular/cli

Hi,
I am trying to work on angular2 for which I have installed nodeJS. I have followed the steps given here https://github.com/angular/angular-cli#prerequisites but there seems to be an issue. Here's what I did in the Command Prompt(Admin):
`C:\WINDOWS\system32>node -v
v6.10.1
C:\WINDOWS\system32>npm -v
3.10.10
C:\WINDOWS\system32>npm install -g @angular/cli
[    ..............] / loadRequestedDeps: sill install loadAllDepsIntoIdealTree`
My command prompt is stuck at this command and shows no sign of response. I will be glad if there are any suggestions on solving this issue of mine.

Hi @VisheshSingh ,
This sounds like a npm issue you should open an issue on that project instead.
After doing a quick search on that project, it seems to be related to this one:
https://github.com/npm/npm/issues/8685

@RicardoVaranda that sounds about right, thanks for looking up the right issue on the npm tracker 👍


Add "Mass Response" mobile provider to the Austria

This adds the "670" code to the Austria file. "670" is the code for the Mass Response Provider. See this wikipedia article (sorry, only in German). Spusu is a provider that launched last year in Austria. This is their website which shows the code on the frontpage.

Thanks a lot – for the references and the code! :rocket: One thing: usually I tend to only merge if PRs contain tests. I think this was your first PR and the change was minimal, so I opted to be lenient.
Anyhow, thanks again :smile: Oh, and German is no problem at all.
Released in 2.15.18.

Thanks a lot for merging this! Sorry about the missing tests. I totally forgot to add them, since I was adding the code via the GitHub web interface while my colleagues and I were standing in a circle saying: "Look! It's easy! We just need to add it here!" :sweat_smile:

Awww :heart:


Update gcp-sa-setup.tf - string quotes no longer supported

string-quotes deprecated

checks done


Icon override on buttons jumps when we change variant

Duplicates ❌

[X] I have searched the existing issues

Libraries

[X] Vitamin Web UI Kit
[X] Vitamin Android UI Kit
[X] Vitamin iOS UI Kit
[ ] Vitamin Icons
[ ] Vitamin Assets
[ ] Vitamin Core theme (Light mode)
[ ] Vitamin Core theme (Dark mode)
[ ] Vitamin Base colors palette
[ ] Vitamin Extras kit
[ ] Not related to one Figma library

Current behavior 😯
On a medium button with left icon variant (that have been changed) when I switch to small variant the icon is going back the default one.
Expected behavior 🤔
If think this can be fixed by adding instance swap property
Context 🔦
No response
Screenshots / Videos 📸
No response

I've added swap instance component propertie on construction components.
I've checked if it's breaking on left icon it seem to not be breaking regarding this video
https://user-images.githubusercontent.com/61324309/233650449-6d2e7175-54bf-4245-ac88-6445635b4db1.mp4

And its also ok for icon alone component
https://user-images.githubusercontent.com/61324309/233652784-5b817401-1425-455a-93be-1a114593f6e1.mp4


Turn exceptions into unreachable

I want to compile with wasi-sdk a C++17 project that uses exceptions. As the wasi-sdk readme says, the proper exceptions are not supported and it refers to the exception handling proposal. However, the project I'm interested in doesn't use exceptions for control flow, so it should be safe to turn all exceptions into unreachable.
Question: is there a way to instruct wasi-sdk to compile exceptions as unreachable?
Caused by https://github.com/pocketpy/pocketpy/issues/275

The readme mentions -fno-exceptions which I think will have the effect of turning exceptions into abort() which is implemented as unreachable.

Will it? This is what I currently use but I wasn't 100% sure that it won't just remove exceptions. clang --help isn't very helpful:
-fno-exceptions         Disable support for exception handling

It looks like yes: https://stackoverflow.com/questions/7249378/disabling-c-exceptions-how-can-i-make-any-std-throw-immediately-terminate
-fno-exceptions is one of the GCC-compatibility flags that clang supports. So the GCC documentation may (or may not) be helpful: https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_exceptions.html

Thank you!


Purview Rebrand

Had to turn off Docs build - Real Time Validation from the Docs validation extension in VS Code in order to prevent YML duplicates of each MD file in the repo from being added to the branch.

Docs Build status updates of commit 67ac8ca:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-DataEncryptionPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-OMEConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-OMEMessageStatus.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/New-DataEncryptionPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/New-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/New-OMEConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/New-TransportRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Remove-OMEConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-IRMConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-OMEConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-OMEMessageRevocation.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-SmimeConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Dynamics email activities are inconsistent in different display views

Our Team is running into an issue with how email activities are displayed.
When I view an activity in the "Preview Mode" I can see all of the text within the email.
If I decide to open that same email activity, there will be text missing that I would normally see in the "Preview Mode" and instead am given an error message that is unresponsive when I try to open the full email.
Please see the screenshots below to help further identify the issue at hand as all screenshots will be showing the same email activity in different views.
"Preview Mode" view:

When "Open Record" is selected:

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

ID: 8cb0a8d4-6f48-0603-3b02-6e6c9b27018d
Version Independent ID: 7b7e5737-4735-5cd4-3c9b-bcae7bed97af
Content: Email activity entities (Developer Guide for Dynamics 365 Customer Engagement)
Content Source: ce/customerengagement/on-premises/developer/email-activity-entities.md
Service: crm-online
GitHub Login: @JimDaly
Microsoft Alias: jdaly

Recommend that this comment be set against this topic:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/email-activity-entities
@KumarVivek  Please find a new owner for this topic or remove it and point it to the CDS content


not support win7?

WriteFile(m_hDriver, (LPCVOID)&rStruct, sizeof(ReadStruct), NULL, NULL);
on windows7, this code get error code:  0xC0000005

No, I'm not supporting windows 7, but I think you can easily change the kernel interface from the usermode application. Thanks for reporting though, I will add this to the readme.

thx reply!
I will fix this on windows7

Yeah and please reply with a solution / open a pull request. I will review it and maybe publish also as a part of original code.


Swiping to both sides

Hello!
I'd like to make a feature request which would make this package THAT much more useful. Currently, it's possible to swipe to one side which is great but many apps would benefit from being able to swipe to both sides simultaneously.
My proposed API would be to have two swipe callbacks, let's say onLeftSwipe and onRightSwipe. If a given callback is given a value in the constructor, then swiping to that side would be made possible.
Of course, this would require to duplicate the other fields and constructor parameters as well - one for the left icon, another for the right one.

@ResoDev Yes we can have this feature.


Updated acidanthera projects

AppleALC 1.4.4
AppleSupport 2.1.4
Lilu 1.4.0
MacInfo 2.0.9
OpenCore 0.5.3
WhateverGreen 1.3.5

So further on we community can use pull request to keep this repository running?

Yes, when you update the link + SHA and make a pull request, it should automatically build the package ex: https://github.com/osy86/HaC-Mini/suites/344597448/artifacts/567531

I think it's better to use shikigva=160 instead of 32 for weg >=1.3.5 ?
(At lease you can hear the audio of offline drm files)

I want to try to fix the issue first before merging this.

Let's try to fix the DRM issues in a separate pull request. The updated projects don't introduce any new problems.


Fix maintenance

Fixes for #2

@JCZuurmond Thanks for taking a swing at this (after #2 sitting dormant for a long time)! Is this ready for review/merge?

it's ready to be merged yes!


[Set Audio Device] Unable to get output device list

Extension
https://raycast.com/benvp/audio-device
Raycast Version
1.83.1
macOS Version
15.0
Description
Error:
Error: Command failed with exit code 1: osascript -e
    set devices to {}

    tell application "System Preferences"
      reveal pane id "com.apple.preference.sound"
    end tell
    tell application "System Events"
      tell application process "System Preferences"
        repeat until exists tab group 1 of window "Sound"
        end repeat
        tell tab group 1 of window "Sound"
          click radio button "Output"
          tell table 1 of scroll area 1
            set selected_row to (first UI element whose selected is true)
            set currentOutput to value of text field 1 of selected_row as text

            repeat with r in rows
              try
                set deviceName to value of text field 1 of r as text
                set deviceType to value of text field 2 of r as text
                set end of devices to { deviceName, deviceType }
              end try
            end repeat
          end tell
        end tell
      end tell
    end tell

    if application "System Preferences" is running then
      tell application "System Preferences" to quit
    end if

    return [ devices, "currentOutput", currentOutput ]

64:116: execution error: “System Settings”遇到一个错误：不能获得“pane id "com.apple.preference.sound"”。 (-1728)
    at D9 (/Users/.../.config/raycast/extensions/2158713f-4712-4862-ba9a-3bce3cd07e3a/set-output-device.js:4:57)
    at /Users/.../.config/raycast/extensions/2158713f-4712-4862-ba9a-3bce3cd07e3a/set-output-device.js:4:6400
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async fa (/Users/.../.config/raycast/extensions/2158713f-4712-4862-ba9a-3bce3cd07e3a/set-output-device.js:38:6806)
    at async N0 (/Users/.../.config/raycast/extensions/2158713f-4712-4862-ba9a-3bce3cd07e3a/set-output-device.js:38:6981)

Steps To Reproduce
Just install extension and run "Set Output Device"
Current Behaviour
No response
Expected Behaviour
No response

I can't confirm if it's a problem with the MacOS system. After I restarted the computer, the plugin can be used normally. Amazing....
I will close this issue. Thanks.


fix: removed duplicated ip-restriction plugin

Currently there are two:

@guoqqqi

@juzhiyuan : )

@juzhiyuan

Hi just a friendly reminder for reviewers. Small change.


ban reasons

Add reasons to ban peers here, as you think of them, if they aren't already logging faulty_peer or have a (* TODO: punish *) next to them

The trust system is more solid and has the central registry of these ban reasons now.


Wallet users SBAT access a deep link to send CELO from the wallet

Expected Behavior
Wallet users SBAT access a deep link to send CELO from the wallet.
Something like the celo://wallet/pay that we have for cUSD
Current Behavior
Currently there is no deep link feature that allows paying with CELO. Right now, the functionality only allows for sending cUSD.

Duplicate


feat(popup): add light dismiss support

The light dismiss feature will be used in Popup as well in Select and Menu components.

Light dismiss behaviors: most popups "light dismiss", in that the following will dismiss the popup: pressing the ESC key, invoking elsewhere in the document, invoking another popup (unless it is a child of the currently opened popup).
Read more: https://open-ui.org/components/popup.research

Should be researched if the light dismiss should work also on resize / scroll.

Should be checked: https://github.com/oddbird/popup-polyfill

@yinonov There is a new version 0.0.3 for the package. They changed it's name to be popover-polyfill.
Should we also change popup's name to popover?

Member

yes. everyone else do https://carbondesignsystem.com/components/popover/usage/

just a reminder to make sure the tooltip benefits from this

Member

yes. everyone else do carbondesignsystem.com/components/popover/usage

@yinonov I see that chrome still calls it pop-up, and it had a popover attribute https://developer.chrome.com/docs/web-platform/pop-up-api/

@yinonov The popover-polyfill still doesn't support in all light-dismiss behaviours. It doesb't suppoer ESC for example..

@yinonov The popover-polyfill still doesn't support in all light-dismiss behaviours. It doesb't suppoer ESC for example..

it don't matter. it will. we don't support any of the light dismiss methods

@yinonov The popover-polyfill still doesn't support in all light-dismiss behaviours. It doesb't suppoer ESC for example..

it don't matter. it will. we don't support any of the light dismiss methods

Ok, so I think the PR is good now, I only have this linting problem

Waiting for https://github.com/oddbird/popover-polyfill/pull/49

do action-group snapshot belong in this scope?

It's not, here I created a separate PR for that: https://github.com/Vonage/vivid-3/pull/924


Explore use of pngquant

Could be a great addition to existing tools.
Found at: http://pngquant.org/

https://github.com/samastur/image-diet/pull/8

Can easily be configured in image-diet2 (https://github.com/samastur/image-diet2/) which is where further development will happen.


Removed fife installer from appveyor and use the zipped file

Needs more work because the python modul is not in the zip file!
https://ci.appveyor.com/api/buildjobs/u9kltpny74p2gulf/artifacts/libfife-dev-dbb9631-VC14.zip
Dont have the python modul in the zip file and we need python 2.7 installer

Maybe we should add the normal python 2.7 installer. Maybe it works then better and sets python path too. Then we only must set fife path.

Sorry, man. Maybe my answer was misleading. I though of repacking the python installer.

What about to take the non installer version of fife and take the zipped package and extract it with the sdk installer and set path? https://github.com/fifengine/fife-windows-sdk/issues/3#issuecomment-261790488

This change is not heading in the right direction and it's messy,
because you are mixing filenames in the download step.
The file libfife-dev-dbb9631-VC14.zip is the library bundle for C++ development.
It's not added yet to the installer, because the Python installer is more important.
Adding it, doesn't solve the Python issue.
The libfife.win32-py2.7.exe is the Python Installer for libfife, which also contains the python/swig API layer. We can solve #1 or package the python module differently: not as installer executable build by setuptools wininst, but manually packaged as zip or using another python installer builder, e.g. pyinstaller.

Maybe we could create the same installer for fife as we use for the sdk?
Use zipped version of fife engine with swig and python and add an official python2 installer?

Like i said before: PyInstaller is maybe an alternative, which produces a better installer and might support silent/scripted installs. http://pyinstaller.readthedocs.io/en/stable/usage.html


Mention transparency on website

As talked in irc, hackedu is about as open as it gets and that should be mentioned somewhere on the website so that people can watch how hackedu works.

It seems like this issue is very inactive. Closing for the time being. If anyone would like to pick it up, please reopen it!


Remove tokio to reduce the audit surface.

It was minimally used.

Does this really change much given minidump-stackwalk uses tokio? Also is really no one in the mozilla cargo-vet trust web using tokio?

Yes! We're using minidump-unwind on its own (for the minidump analyzer in crash reporting). Nothing delivered from mozilla central uses tokio, so otherwise there would need to be an audit of tokio to ensure it's safe-to-deploy.
We could actually do the audit, and we have discussed possibly trusting it ourselves. No imports in the cargo-vet registry have an audit for tokio yet. It is preferable to remove it as this is the only use in the entire dependency tree. Auditing it will be a big task; it has 500+ unsafe blocks.

Yeah I agree it's a ton of work, just a bit surprised it's managed to evade auditing this long. Makes sense, assuming the perf still behaves reasonably (I would assume so, code is generally bottlenecked on xul.dll's symbols sync downloading, async'ing just lets the other stuff get fetched at the same time).

I expect there's a lot of tokio exemptions :cry:
The new code here should be almost the same as the old code as far as perf goes. I could have written it using atomics and whatnot (actually I have an impl lying around somewhere I could copy in) but I figured it's not a high priority.


Documentation: typos in discovery, faq, security

This just fixes some typos from my reading Documentation.
Thanks,

great, thank you!

No problem. Thanks!


ARROW-9704: [Java] TestEndianness.testLittleEndian supports little- and big-endian platforms

This PR aims to take care of data layout on little- and big-endian platforms in TestEndianness.testLittleEndian

Is this mergeable now? According to the mailing list discussion:

It does not seem too invasive to support native endianness in
implementation libraries.  As long as there is appropriate performance
testing and CI infrastructure to demonstrate the changes work.

If I read this PR correctly, it's just changing the test to follow native endianness.

Thank you for your comment.
According to Micah 's comment, we may wait until he will update the document soon.
@emkornfield WDYT?
Since Java CI was merged, I rebased to run Java CI.

Opened https://github.com/apache/arrow/pull/8374 to make sure we are all on the same page, once that goes in, I think we can submit this.

@nealrichardson @emkornfield Is it ok to merge this?  I think that this failure is not related to the change of this PR.

Sounds like it. I'll merge.


'Restart kernel' and 'shutdown kernel' commands failing

Description:
Updated 'restart kernel' command doesn't properly restart the kernel. Run commands hang until kernel is restarted a second time, but only while a run command is hanging.
Second (probably related) problem: Shutdown Kernel command after Restart Kernel command triggers invalid message tracebacks.
Steps to Reproduce:
The sequence:

Restart Kernel
Run All
Restart Kernel

will properly run the program, but the sequence:

Restart Kernel
Restart Kernel
2.5 (...)
Run All

will hang.
The second problem can be reproduced as follows:

Run All
Restart Kernel
Shutdown Kernel
Run All

Produces the error message below, under Logs.
Versions:
OSX 10.12.5 (16F73)
Atom 1.17.2 x64
Hydrogen 1.16.0
(Electron: 1.3.15
Chrome  : 52.0.2743.82
Node    : 6.5.0
Jupyter : 4.1.0)
Logs:
[IPKernelApp] ERROR | Invalid Message Traceback (most recent call last): File "/Users/$USERNAME/anaconda/lib/python2.7/site-packages/ipykernel/kernelbase.py", line 199, in dispatch_shell msg = self.session.deserialize(msg, content=True, copy=False) File "/Users/$USERNAME/anaconda/lib/python2.7/site-packages/jupyter_client/session.py", line 859, in deserialize raise ValueError("Invalid Signature: %r" % signature) ValueError: Invalid Signature: 'add5a85b80d1ed8600e3188d577977d087430339bdc0e46cff9ca8971c3222cd'

I think this issue is related recently introduced faster-restart(#853).
I noticed similar issue(not same, but greatly related) while I'm working on #861(which call runAll on restart callback).

If I passed callback to  restart like restart(runAll), the issue is more happens. But % is still rare.
I can't see issue with ijavascript kernel , but I can see issue for iPython kernel.
If I launch Atom in dev-mode and open dev-tools, the issue in iPython kernel is almost always happen(means each restart-and-run-all).
This is because, hydrogen write lots of logs in dev-console which add extra delay to complete kernel-restart(my assumption).
If I add some delay by likerestart(()=> setTimeout(runAll, 1000)), issue does not happen(of course this timeout would depends on CPU of client machine).

So my impression for this issue is, the timing of calling callback passed on restart is too early.
I think we have to find the way to correctly recognize timing for "when kernel.restart complete" in fast-restart situation.

Ok this is definitely seeming like doing the restart with the old connection file is a really bad idea since we aren't capturing the full lifecycle of closing down the old kernel (and it appears to still be responding with the old signature).

Closed by #877


mini.jump (clever-f)

[x] I have read CONTRIBUTING.md
[x] I have read CODE_OF_CONDUCT.md
[x] Works in normal mode
[x] Works in visual mode
[x] Works in operator mode
[x] Accepts v:count
[x] Internal documentation
[x] Highlighting

This is a module named mini.jump, implementing the basic functionality of clever-f and a basis for the functionality of vim-sneak.
Would this fit the spirit of this project? Should I also add two-char search like vim-sneak?
(Note: the implementation is currently a bit buggy, but the basic functionality works)

Wow, that is great! Thanks!
Yes, it does fit in the spirit of this project quite nicely. I don't use any of the clever jumps plugins, so it wasn't implemented earlier. I have quite a lot of questions about particular implementations, but that can wait until you feel like this is good for review. Some general tips which I try to follow:

Use expression mappings only when they are crucially needed. Here it seems that basic mappings will be enough.
Use string.format() instead of ... It proved to be faster and more readable.
Export in module (MiniJump in this case) as little as possible. In this case both target and ask_for_target on the first glance seem like they should be in H.

Scanning through README of 'clever-f' it seems that highlighting possible jumps is pretty crucial to usability. Can this be implemented?
If you feel like adding two-char search which will have relatively simple and fast code, then sure, go for it. By the way, I've read many good things about ggandor/lightspeed.nvim. Maybe this should serve as a guide instead of vim-sneak?

I'll look into how to do the highlighting. Personally I find it more annoying than useful.
Lightspeed is an interesting concept, but I think it (and labeled jumps in general) might be too complex to fit with mini.

ask_for_target has to be in the module so that it can be modified by the autocommand. Do you have an idea how to avoid this?

I currently find using exported on_<autocmd>() quite convinient. So in this case it will be something like:
function MiniJump.on_cursormoved()
  H.ask_for_target = true
end

And then having autocmd CursorMoved * lua MiniJump.on_cursormoved(). NOTE: I am not entirely sure why this has to be in CursorMoved, but will do deeper dive when this is ready.

I am not entirely sure why this has to be in CursorMoved

The point of clever-f is that if you press f and the last movement was f, then it will repeat the movement instead of prompting for another character. So I need some way to tell if the last movement was f. I haven't looked into how clever-f does it, but the CursorMoved trick seems to work well.

It looks like search() has no way to get positions of all matches, so highlighting would need to by done my manually scanning the buffer, which could be quite complex and error-prone.

I think it's pretty much ready for review. It's just missing documentation in README and it's unclear how t should work when the match is at the beginning of a line (currently I just skip such matches, but that's probably a bad approach).

Thank you for this! I'll take a closer look along with hands-on testing this week.
What I can say right now:

I think that the main point of this plugin is to enhance behavior of jumping. So having it do nothing by default is a bit confusing. Currently I think that in terms of mappings it should be similar to 'mini.surround': have a config.mappings table defining what mappings are made. And all those mappings are applied by default.
Right now I am in the middle of figuring out a better way of introducing new modules. This will probably have a public beta-testing period inside other directory (something like 'lua/mini-dev'). I plan to soon add two modules there (almost finished). This one will go with them, once I decide on process.
I encourage you to add yourself as second copyright holder (without any obligatory burden of supporting this in the future). If you don't want that, at least mention yourself in module's documentation.
External documentation is generated locally on my machine. It is currently using tjdevries/tree-sitter-lua which is a bit of a pain to setup. I'll generate it myself after it is merged.

Here is the relevant function from clever-f:
function! clever_f#_mark_direct(forward, count) abort
    let line = getline('.')
    let [_, l, c, _] = getpos('.')

    if (a:forward && c >= len(line)) || (!a:forward && c == 1)
        " there is no matching characters
        return []
    endif

    if g:clever_f_ignore_case
        let line = tolower(line)
    endif

    let char_count = {}
    let matches = []
    let indices = a:forward ? range(c, len(line) - 1, 1) : range(c - 2, 0, -1)
    for i in indices
        let ch = line[i]
        " only matches to ASCII
        if ch !~# '^[\x00-\x7F]$' | continue | endif
        let ch_lower = tolower(ch)

        let char_count[ch] = get(char_count, ch, 0) + 1
        if g:clever_f_smart_case && ch =~# '\u'
            " uppercase characters are doubly counted
            let char_count[ch_lower] = get(char_count, ch_lower, 0) + 1
        endif

        if char_count[ch] == a:count ||
            \ (g:clever_f_smart_case && char_count[ch_lower] == a:count)
            " NOTE: should not use `matchaddpos(group, [...position])`,
            " because the maximum number of position is 8
            let m = matchaddpos('CleverFDirect', [[l, i + 1]])
            call add(matches, m)
        endif
    endfor
    return matches
endfunction

It seems to find and highlight the matches manually, which could be very error-prone, especially with Unicode characters. Also it works only on the current line.
I just got an idea on how I might be able to (ab)use syntax highlighting to do it.

Wow, that was actually very easy! Now the question is, should we highlight matches after/before the cursor, or all of them? The former may or may not be tricky.

Just curious, what modules are you adding?

I believe, having highlighting only at those places that are reachable with current command (fFtT) is more appropriate. This can be solved by either more elaborate highlighting or having commands cycle from end to beginning.
I just quickly tried this module and here are some first thoughts:

It definitely needs more careful handling of highlighting and state tracking. It doesn't disappear when going in Insert mode. Also there is some weird freeze when going into Telescope while highlighting is visible. Probably, reset_target() should be called also on InsertEnter and BufLeavePre.
Right now I can see it being useful for quick jumping to single letter, allowing till and automatic disappear of highlighting. Otherwise it seems to be quite similar to / and nN. Should think about needing multiple character support.

Just curious, what modules are you adding?

https://github.com/echasnovski/nvim/tree/master/lua/mini-dev

Right now I can see it being useful for quick jumping to single letter, allowing till and automatic disappear of highlighting. Otherwise it seems to be quite similar to / and nN. Should think about needing multiple character support.

My intent was to improve the built-in f and t commands without adding anything new. I think 2-char search should be opt-in, but I can add a way to define mappings for it. And when it comes to / and ?, it might be a good idea to somehow hijack them too.

Just wanted to say about the problem with multiple consecutive matches :)
I had quite a number of small changes (mostly cosmetic). Do you mind me pushing changes here?

No, it's your plugin after all :)

Most of the changes are cosmetic. Ones that have side effects are in commit's details.
Current thoughts and problems I found so far:

I am not sure if target should or should not be reset when using from different modes. So say I used it from operator-pending mode with dt). Should I manually supply target if I press t right after that?
Highlighting definitely needs more attention. There were some moments when it didn't disappear. Not sure right now what caused them.
I am currently getting more and more inclined to make this just an enhancement for FfTt (as you originally intended). This might get changed if we'll come up with a more user-friendly way to support multiple characters. If only FfTt-like functionality will be supported, changing a name that reflects that might be a good idea (although I really like the 'mini.jump').
There is got to be a better way to implement smart jumping and its resetting than current one. I don't have a good feeling about using CursorMoved and vim.schedule (inside smart_jump).

I didn't consider this. I think it should be reset.
The issue in clever-f links to an issue in lightspeed, which seems to be caused by feedkeys(). I don't use feedkeys() though...
It wouldn't be a problem to allow mapping something to 2-char search the same way that f is mapped to 1-char search.
It looks like clever-f uses CursorMoved. But if you can come up with something better, feel free to suggest it.

Think I solved most of the immediate issues I found while using it. It seems that most of them were because of vim.schedule() might execute its input too late. Also matchadd() works per window, so I adapted 'mini.cursorword's code here with slight change in logic of unhighlight().
I currently kind of like that after dt) I can still use jumping.
Another good idea might be to allow repeating current jump and encourage to use it with ; (via config.mappings.repeat with '' as default). This might be a better "long-term" behavior (don't need to retrain oneself from using ;) and easier for switching.
I plan to test it through everyday usage and see if there is something we missed. Adam, could you, please, do the same?

I'm definitely using the module (I have my fork installed as a Vim plugin) and it seems fine for me. But then, I don't use Telescope, so I can't find Telescope-related bugs.
The ; is a good idea for a transition period. I wouldn't encourage it because the main advantage of clever-f is freeing up the ; and , keys. (I personally have ; mapped to <cmd>w<cr> and love it.)

@xigoi, I've decided to make a quite big refactor. Didn't do it in this PR to not break your setup. Would you mind looking at this commit in my neovim config and tell me your thoughts?
After reaching an agreement regarding these changes I'll plan to merge this PR as is, move it to 'mini-dev' instead of 'mini', make those new changes, and it will be ready for a public beta-testing (hopefully in the upcoming week).

@xigoi, I'll merge this as is and make updates after. I recently after a lot of trial, error, and reading Vimscript code managed to implement fool dot-repeat in operator-pending mode. Also made a refactor to easy allow MiniJump.repeat(), but I'll wait and see about it.
Thank you very much for your ideas, enthusiasm and work!


Provide unit tests

This one is in: https://github.com/topcoder-platform/submission-processor/pull/11


Rework the ShowAst functionality

Right now a lot of the phases have changed names so a lot of Show XAst is broken. We we add capability to ask the compiler for its phases.
Additionally, Show XAst implicitly has the <Root>.main entrypoint, so often most the ast is deleted if you don't use that main name. It should really be Show XAst for Something.example (where the given function must be a valid entrypoint).

right, that makes sense. it could also be that the user presses "show ast" then the plugin asks the compiler that then shows a dropdown of the phases.
But yeah i like the solution where the user types it themselves

I have decided on the following: We change the ShowAst functionality to prompt for the phase name. Hence VSCode no longer needs to know about any phases. On the compiler side, we can use levensthein distance, such that if you type e.g. Reduc it is good enough.
@sockmaster27 Will you implement the change on VSCode
@JonathanStarup Will you improve the compiler side?

@sockmaster27 and @JonathanStarup Gentle Ping :)

@JonathanStarup You should check that it works as you would expect.


How-To: use a custom icon for our toast

Hello! Thank you for this lib, that offers more possibilities than the usual win10toast.
I tried playing it around, but however, I am not able to configure a toast to use a custom icon. I do not mean an image within the toast, but a header icon for the toast, like the yellow one here:

I do not find anything clear regarding this in the documentation. Is it possible that is possible "natively", or do we have to create a custom AUMID? (I am confused because I am still able to use custom titles, yet the documentation above mentions that "Custom AUMIDs can display user-defined titles and icons.")

Yep, you have to create a custom AUMID. If you have the Python Scripts directory in your PATH, entering register_hkey_aumid --icon "C:\path\to\image" --name "My Program" --app_id "myprogram" (replace with yours obviously) should create it.
Then, use InteractableWindowsToaster and pass your app_id argument as notifierAUMID.
toaster = InteractableWindowsToaster("Test Notif", "notiftest")
toast = ToastText1("Hello, World!")
toaster.show_toast(toast)

Excellent, thank you for the information.
I feel like that an item addressing the question of "how to set a custom icon" should be added in the "Advanced usage" section of the documentation, because I was confused at first when going through it. Something like this maybe?
Set a custom icon
----------------
To set a custom icon for your toast, you will have to register a custom AUMID. See the page [Custom AUMIDs] for more information.

And then, the page "Custom AUMIDs" could also be edited to add the example you just shown above.

I pushed https://github.com/DatGuy1/Windows-Toasts/commit/1fb3c1fcd3883fa48991284b5b530d971b64277e a bit after you made the PR. Do you think it's clearer now?

The page about AUMIDs looks a bit clearer now, but I meant more to modify the "Advanced usage" page to include a section similar to the one I wrote above. When I went in the documentation, I had no idea what an AUMID was, and how it was useful to my issue (since I was imagining that it was about an advanced thing, and that putting an icon for my toast was not something "advanced"...). So I did not have the idea to click it at first, however I looked into "Advanced usage", and could not find what I was looking for.


Regarding the GMB OAuth2

Hi,
As per the sample code in google-api-nodejs-client/samples/oauth2.js
I am using the code for Google My Business and run and enter the random code in "Enter the code here:" but I am still getting the error. Why? How am I able to get that Code?
Visit the url:  https://accounts.google.com/o/oauth2/auth?access_type=offline&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fplus.business.manage&response_type=code&client_id=XXXXXXXXXXXXXXXXXXXXXXXXXX&redirect_uri=http%3A%2F%2Fnfx.dev.canbrand.in%3A1338%2F
Enter the code here:876876
876876
An error occured [Error: No access or refresh token is set.]
Quick response is very appreciable.
Thanks In advance

Hi @prashant7july and @JesseCogolloAdvice - is this still an issue for either of you? If not, mind if I close this?

Works for me.

If this is still an issue, please let us know!


Normalize practice exercise names

We have added explicit exercise titles to the metadata.toml files in problem-specifications.
This updates the exercise names to match the values in this field.

Cleaning up very stale branches. This one still applies.


Casmpet 5771

Summary and Scope
Removed usage of deprecated, and more importantly removed in k8s 1.22 api usage with batch/v1beta1 This is in preparation for k8s 1.22.
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves CASMPET-5771
Change will also be needed in <insert branch name here>
Future work required by anything in CASMPET-5770
Documentation changes required in [issue id](issue link)
Merge with/before/after <insert PR URL here>

Testing
Validated the change manually on a 1.3 system by changing the resource manually and as per https://kubernetes.io/docs/reference/using-api/deprecation-guide/#cronjob-v125
This beta api was basically subsumed by the non beta version so no further changes are needed in the definitions of the cronjob.
Tested on:

redbull with a manual cronjob with/out the old and new api
Virtual Shasta

Test description:
Mostly validated k8s 1.21 behaves the same way with the new cronjob and the old beta. As per the deprecation docs they behave the same.

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)? no
Were continuous integration tests run? If not, why? n/a
Was upgrade tested? If not, why? n/a
Was downgrade tested? If not, why? n/a
Were new tests (or test issues/Jiras) created for this change? I added a github action to run pluto against the setup so hopefully we don't get more deprecated api usage. Though there is one more certmanager api that we likely want to change.

Risks and Mitigations
No known Risks
Pull Request Checklist

[x ] Version number(s) incremented, if applicable
[ ] Copyrights updated
[ ] License file intact
[ ] Target branch correct
[x ] CHANGELOG.md updated
[ x] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

I should note, you can manually run that github action if you have act installed by running:
act -j build

Though maybe I should change the action name to pluto...

Act is this as a note https://github.com/nektos/act

Ok now its act -j pluto as the github action name.

Bumped to 8.3.0.

I can't seem to resolve Bo's conversation even though it appears to be resolved.


Valkyrize Pals: Run migration script

Summary
After the valkyrized app has been deployed to production, we could run a script to migrate records instead of relying on lazy migrations.
"This script allows you to run a lambda on every instance of works, collections, etc in a resumable way. Very useful for migrating from Fedora to Postgres using Valkyrie." - Kiah
ref:

https://github.com/scientist-softserv/adventist_knapsack/issues/773
Instructions https://github.com/samvera/hyku/pull/2251/files
https://github.com/samvera/hyku/blob/main/lib/reprocessor.rb
https://github.com/samvera/hyku/pull/2166

See Kiah for help on with this. He performed this task for GBH.
Tasks

[ ] Run this on staging
[ ] Run this on production

NOTES
related to
~- https://github.com/scientist-softserv/hykuup_knapsack/issues/238~
~- https://github.com/scientist-softserv/hykuup_knapsack/issues/214~

BLUF:  DO NOT RUN MIGRATION SCRIPT
When saving an active fedora collection to migrate it to a valkyrie collection, the thumbnail seems to be retaining.  When uploading a new thumbnail, it has to be done now through the branding tab.  Do not run the migration, because doing each step seems to have locked one of the records we were testing.

Depends on https://github.com/scientist-softserv/adventist_knapsack/issues/773

Blocked until the imported tenant data is fixed


Rename pageflow-react to pageflow-paged-react

The pageflow-react package is tightly coupled to paged entries and should thus live in entry_types/paged.
The first commit moves it there and renames the directory to pageflow-paged-react. Then there is only packages/pageflow left in the packages directory. So the second commit, moves the pageflow package to a root level package directory instead to make it match the pageflow-scrolled package which already lives in entry_types/scrolled/package.
The PR is really big, but mostly performs these two moves, updates the build setup and documentation.
Git should handle these renames correctly, when rebasing other in progress branches that touch files in packages/pageflow.
REDMINE-17285

Coverage remained the same at ?% when pulling 363e0464382bd18a8552acd858e02f67be9f44bd on tf:pageflow-paged-react into feb59afdeca353cdcff2c8dd782ff04aeccd3ffc on codevise:master.


how to compress the extension

It reminds me when I package the extension:

This extension consists of 545 files, out of which 528 are JavaScript files. For performance reasons, you should bundle your extension: https://aka.ms/vscode-bundle-extension . You should also exclude unnecessary files by adding them to your .vscodeignore: https://aka.ms/vscode-vscodeignore

So how to compress it?

I need your help @worranhin

The website you quote seems clear. What's the problem you met? @dzylikecode
If you use webpack, maybe this tool can help.

I just write several javascript lines, but the size it builds is 1MB. That's terrible.

Is it because the dependencies?
Maybe try to split the bundle?
https://www.webpackjs.com/guides/code-splitting/