Doesn't work with private github repo actions

When trying to use a private github repo for the action parameter, it does not work (we use this action daily in our workflow and it does work, just not when passed in here). I'm guessing a token/secret is not being used. I imagine this is a security feature so that actions can't see what's in your private repo so not sure if its even possible but would be great if we could get this working.
Here is the output:

Hello @mycarrysun
I've released new version v2.1.0. The action has option github_token and it is the option for downloading private actions. Please, try new version and give me a feedback.
Please, be care about the token, it should have correct access rights.


Direct import of tar files into virtual directories

See original issue on GitLab
In GitLab by [Gitlab user @jmacarthur] on Jul 27, 2018, 11:27
Background
This is an issue filed for a proposed MR !445 which currently extracts tar files to a temporary directory before importing that temporary directory. This is inefficient.
Task description

[ ] Implement direct tar file import into virtual directories

Acceptance Criteria
Direct import of tar files with functional equivalence to existing code.

In GitLab by [Gitlab user @jmacarthur] on Jul 27, 2018, 11:27
mentioned in merge request !445

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:44
marked this issue as related to #540

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:45
Do we need separate issues here for zip and deb plugins ?

In GitLab by [Gitlab user @jennis] on Aug 22, 2018, 13:00
[Gitlab user @jmacarthur] as well as being inefficient, I've faced another, more serious issue.

Issue #601.

In GitLab by [Gitlab user @jennis] on Aug 22, 2018, 13:01
marked this issue as related to #601


.env.example

Describe the feature
So everyone can easily get the secrets that are essential in the .env file.
Add ScreenShots
no
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

We are not using any .env file


MATLAB file misidentified as Mathematica

Preliminary Steps
Please confirm you have...

[x] reviewed How Linguist Works,
[x] reviewed the Troubleshooting docs,
[x] considered implementing an override,
[x] verified an issue has not already been logged for your issue (linguist issues).

Problem Description
One of my many MATLAB files is being incorrectly identified as Mathematica. (Yes, I will create a .gitattributes file to fix this, this issue is to hopefully improve your heuristics.)
The current heuristic looks for the pattern \*\)$, which identifies Mathematica. If it fails, it continues with the MATLAB pattern. This one file contains this comment, which matches the pattern:
%       LCH (or L*C*H*)

Previously, Mathematica was identified by the opening comment tag: ^\s*\(\* (see #1652). That would be an illegal sequence in a MATLAB file, as far as I know, and therefore seems to be a much better test. Is there a reason this was changed?
Is matching both the opening and the closing tag too expensive?
Otherwise, I could suggest a different strategy: if a directory contains hundreds of files with the same extension, and most of them are MATLAB, it is very likely that they are all MATLAB. To me it seems highly unlikely that a repository would have, in one directory, multiple files with the same extension that are not all the same language. Such a test could help you skip the regular expression tests on many files.
URL of the affected repository:
Repository: https://github.com/DIPlib/diplib/
The affected file is<EMAIL_ADDRESS>Last modified on:
2018-11-20
Expected language:
MATLAB
Detected language:
Mathematica

Is matching both the opening and the closing tag too expensive?

Probably not, especially if we simplify the search string for the opening comment to be (*.

@crisluengo Do you want to send a pull request to implement this change?

@pchaigno Sure, I can do this tonight or later this week.
I propose the regexp \(\*.+\*\)$. It looks like comments don't need to be at the end of a line, but this refines the current heuristic to remove false positives, it doesn't need to match every single comment in the file. I'd fear that we'd add false positives if we remove the $ from the regexp (for example to match a C expression like (*(int*)ptr)).

I was thinking we could go for
and:
- pattern: '(\*'
- pattern: '\*)$'

to avoid the costly .+ pattern, which may cause a lot of backtracking.

Sounds good.

The same happend here --> https://github.com/Christoph-Lauer/Acoustic-Camera/blob/main/acousticCamera.m

@Christoph-Lauer 🤔 Your file is being identified as Mathematica because it contains the syntax specifically identified and discussed as Mathematica in this issue... you have (* ... *) on two lines L82 and L120 so your file matches the heuristics that were implemented off the back of this issue.
From what I can find, these are valid Mathematic comments, but not MATLAB comments which uses% so it would suggest the current heuristic has correctly identified your file as Mathematica and not MATLAB.
If that really is valid MATLAB syntax, we'd be grateful for a PR to update our heuristics so this scenario can be identified correctly. Until then, you'll need to implement an override.
As an aside, this really should have been posed as a new discussion given this issue has been closed for over two years.

Hello Colin,
Thanks for the hint. I changed the comment so the file is now interpreted as Matlab.
THANKS!
--
Christoph Lauer
web:		WebPage https://christoph-lauer.github.io/
mail:		@.*** @.***>
tel.:		0159/01007198 tel:0159/01007198

Am 07.09.2021 um 17:44 schrieb Colin Seymour @.***>:
@Christoph-Lauer https://github.com/Christoph-Lauer 🤔 Your file is being identified as Mathematica because it contains the syntax specifically identified and discussed as Mathematica in this issue... you have (* ... *) on two lines L82 https://github.com/Christoph-Lauer/Acoustic-Camera/blob/75138ee0dce370362c990215851d35788e692966/acousticCamera.m#L82 and L120 https://github.com/Christoph-Lauer/Acoustic-Camera/blob/75138ee0dce370362c990215851d35788e692966/acousticCamera.m#L120 so your file matches the heuristics that were implemented off the back of this issue.
From what I can find, these are valid Mathematic comments https://reference.wolfram.com/language/guide/Syntax.html, but not MATLAB comments which uses% https://www.tutorialspoint.com/matlab/matlab_syntax.htm so it would suggest the current heuristic has correctly identified your file as Mathematica and not MATLAB.
If that really is valid MATLAB syntax, we'd be grateful for a PR to update our heuristics so this scenario can be identified correctly. Until then, you'll need to implement an override.
As an aside, this really should have been posed as a new discussion given this issue has been closed for over two years.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/github/linguist/issues/4385#issuecomment-914418989, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASVZ3MCTLHVV5CUMSYOOTZLUAYXNBANCNFSM4GQQXHXQ.


fix: Remove grid option from collections

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #5259
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 15 usd

😍 Perfect, I’ve sent the payout
💵 $15 @ 33.99 USD/KSM ~ 0.441 $KSM
🧗 Caiv9TbPz68q5dC8EcHu5xKYPRnremimGzqmEejDFNpWWLG
🔗 0xec8c57f0ab1e92eedb624245ca32314b99105ad0bfc82f028fad31f42b536df1
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Try to mark child channel writable again once the parent channel beco…

…mes writable
Motivation:
f945a071db4d499d21142d3aa321ce8070616665 decoupled the writability state from the flow controller but could lead to the situation of a lot of writability updates events were propagated to the child channels. This change ensure we only take into account if the parent channel becomes writable again before we try to set the child channels to writable.
Modifications:
Only listen for channel writability changes for if the parent channel becomes writable again.
Result:
Less writability updates.

@ejona86 this is a follow-up of f945a071db4d499d21142d3aa321ce8070616665.

alternative we could also store the channels that become unwritable in a ArrayDeque and drain it to not loop over all active channels. Not sure this is what you had in mind... let me know


Extend (and document) require clauses with functions

Currently the require clause accepts fairly simple statements. One possible extension that could be useful (particularly for my work) is to allow users to reference other NV functions from the require clause, e.g. writing something like the following:
symbolic x : int
require (f x) = (merge 0n (init 0n) (f x))
(* ... definitions of f, init and merge ... *)

This currently returns an "unbound variable f~0" on compilation.
I would also find it handy to be able to refer to the solution at a node using a function, e.g. (lab n) would give me the solution at node n.
My main use-case for this is in require clauses specifically, but it doesn't necessarily need to be a user-available feature; I can just add an SMT statement that does this internally.
Also, we don't document how to use require anywhere in the wiki. This would be useful for new users.

To respond in order:

I'm not currently aware of any restrictions on the body of a requires clause, although there certainly might be some. But it's definitely possible to use functions inside them. This example does so. You're getting an unbound variable error because you're using f before you define it. That said, I expect it would fail regardless because I don't think you can reference trans/merge/init like normal variables. Not sure, though.
Referring to the solution of a node is something we've talked about in various ways. It's likely to appear when we add in ocaml-like module syntax. We haven't really figured out how they'll work, but they're what I'm hoping to work on next. We can probably talk directly to figure out exactly what your needs are for getting the label and how it relates to partitioning.
You're right that it's not on the wiki. I don't think symbolics are on there either. I'll try to add them tonight or tomorrow.

To respond in order:

I'm not currently aware of any restrictions on the body of a requires clause, although there certainly might be some. But it's definitely possible to use functions inside them. This example does so. You're getting an unbound variable error because you're using f before you define it. That said, I expect it would fail regardless because I don't think you can reference trans/merge/init like normal variables. Not sure, though.
Referring to the solution of a node is something we've talked about in various ways. It's likely to appear when we add in ocaml-like module syntax. We haven't really figured out how they'll work, but they're what I'm hoping to work on next. We can probably talk directly to figure out exactly what your needs are for getting the label and how it relates to partitioning.
You're right that it's not on the wiki. I don't think symbolics are on there either. I'll try to add them tonight or tomorrow.

For point 1, I'm guessing this opens up into a more general question of using the definitions of trans, merge and init elsewhere in the program like they were regular functions. We can certainly emulate this behaviour by having a helper function, e.g.
let helper e x = match edge with
  | 0~1 -> x + 1
  | _ -> x

let trans e x = helper e x

let assert node x = match node with
  | 0n -> x = 0
  | 1n -> x = (helper 0~1 0)

But extending the language to allow the functions to be used elsewhere would be cleaner, and I think would also dovetail nicely with work on point 2.

I did some digging through the code and concluded that it would be a big pain to change the semantics such that merge/trans/init exist as real variables. I can do a hacky fix, but I'd rather not if we can avoid it. Probably the best thing to do is use the above workaround until we get modules more fleshed out, since they should remove this problem (if we do them right). If the workaround turns out to be a pain, let me know and I'll give you that fix.
I've also edited the NV Syntax page on the wiki to include symbolic variables and require clauses.

All right, sounds good to me. I'll close this and we can come back to it in the future if need be.


Roller shade group from ESPSomfy unavailable with HA integration v.2.1.9

I've combined two roller shades into a group using the ESPSomfy web application and integrated them into Home Assistant using the integration. All was working well in v.2.1.6. but after upgrading the integration to v.2.1.9. the group entity became unavailable.
I was running my ESPSomfy on 2.1.6 and tried upgrading to 2.1.9 but failed as I couldn't find the S2 version (the artifact was expired), so I upgraded to 2.1.10. However, this didn't change the situation.
Now I've rolled back my HA integration to v.2.1.8. and the group entity is working again.
With v.2.1.9. I see this in my device page in Home Assistant (it's the "Slaapkamer" entity). The screenshot is before the ESPSomfy upgrade, but as stated, that had no effect.

Back to v.2.1.8. shows the controls again

Also, with v.2.1.9. I tried controlling the grouped shades using my HA cover card, resulting in this error message
2023-10-17 10:44:55.595 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547918101056] Entity cover.slaapkamer does not support this service.
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 227, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1969, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2006, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 235, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 851, in entity_service_call
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Entity cover.slaapkamer does not support this service.

I'll have a look.  Are these tilt only blinds by chance?

Thanks for the quick response. These are zipscreens which only have up and down control, no tilt. They are defined as a roller shade in ESPSomfy.

Actually, HA is no longer registering the entities that are sent to the group since the latest update.  I'll dig to see what has changed.

Alright I published v2.1.10 of the integration.  The HA folks changed the attributes for the CoverGroup which essentially trashed the group.  Update to v2.1.10 and your troubles will go away.

Thanks for the quick fix! Everything is working again :)


usage issue

I downloaded the https://github.com/GHPReporter/Ghpr.NUnit.Examples
1 When I use NuGet to download the Ghpr.Console and compile the Ghpr.NUnit.Examples. It will display error that  "Console.WriteLine()" can't parsed in .cs files. I need to use System.Console.Write() in .cs files to pass the build.
So could someone update the Ghpr.Console plug-in to mitigate the build error?

For the usage
"Add relative path to Ghpr.NUnit.dll from build folder of your tests (example: addins/../../../Users/Evgeniy_Kosjakov/Documents/GitHub/Ghpr.NUnit.Examples/build/Ghpr.NUnit.dll) into nunit.bundle.addins"

In fact, there is no nunit.bundle.addins files in the package of NUnit.ConsoleRunner.3.10.0. It only has nunit.nuget.addins in tools directory of NUnit.ConsoleRunner.3.10.0.
I added below content in
../../../../build/Ghpr.NUnit.dll
So could someone update the instruction?
After I modify the Ghpr.NUnit.Settings.json to latest version and copy it to the generated build directory of Ghpr.NUnit.Examples.
Then I use nunit3-console to generate .xml file and use ghph.console to generate html format file successfully.

Hi @davesliu !
Thank you very much for detailed issue description.
Regarding your two points:

The issue is related with the name on the Console project. Basically System.Console namespace conflicts with Ghpr.Console. I'll update the repository to use different namespace.

The usage description from Ghpr.NUnit repository is related to the usage of NUnit Console which is installed locally on the machine where you are running tests. The description you've provided is related to the usage of NUnit Console downloaded as a NuGet package which is even better. I will update the usage description to use both approaches.

Thanks

@elv1s42
Thank you very much for your help :-)
BTW, another question here:
As we want to implement continuous integration for unit test with Jenkins.
So is it possible to integrate the Ghpr.NUnit to the Jenkins?

Hi @davesliu !
I've never tried it myself, but it should be possible.
You can take a look at this README section: https://github.com/GHPReporter/Ghpr.Core#how-to-publish-the-report-in-jenkins
Thank you

README updated: https://github.com/GHPReporter/Ghpr.NUnit/blob/master/README.md#with-nunit-3-consolerunner-nuget-package


Add a USB quirk rule for the Kyocera Ecosys P6130cdn (Issue #5102)

This adds the respective USB quirk entry needed to fix #5102.

Thanks!


eth: rename functions prefixed with is_

Codecov Report

Merging #182 (17d4540) into main (0cde44d) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #182   +/-   ##
=======================================
  Coverage   99.75%   99.75%
=======================================
  Files          70       70
  Lines        4068     4068
=======================================
  Hits         4058     4058
  Misses         10       10

Impacted Files
Coverage Δ

lib/eth/abi.rb
100.00% <100.00%> (ø)

lib/eth/abi/type.rb
100.00% <100.00%> (ø)

lib/eth/address.rb
100.00% <100.00%> (ø)

lib/eth/client.rb
100.00% <100.00%> (ø)

lib/eth/eip712.rb
100.00% <100.00%> (ø)

lib/eth/key.rb
100.00% <100.00%> (ø)

lib/eth/rlp/decoder.rb
95.91% <100.00%> (ø)

lib/eth/rlp/encoder.rb
93.33% <100.00%> (ø)

lib/eth/rlp/sedes.rb
100.00% <100.00%> (ø)

lib/eth/rlp/sedes/binary.rb
100.00% <100.00%> (ø)

... and 9 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Issue 91] CLI: Autofill last project if invalid project

The Pull Request is ready

[x] all github actions are passing
[x] only a single issue was worked on
[x] fixes #91
[x] the branch follows the naming schema issue-123-enable-x-does-not-disable-y
[x] the pull request has a sensible title

Intention
With this change I intend to...

Replace project strings that come in with the filler template or empty string with the last mentioned project

Review Points
Please take extra care reviewing...

Never used nestjs or this way of organizing a code base. Idk if I put stuff where they belong.

The code follows best practices

[x] duplicate code has been extracted where possible
[x] issues for follow-up tasks have been created
[x] tests have been written for any new functionality
[x] there is no any type used
[x] texts have been checked for grammar and spelling issues

Notes

@rphovley Ready for review


Refactor code into a real python module

My objectives are :

use a classic module structure (_inside the mcc/ folder) for the python, cf docs.python-guide.org
create some files and sort the function by semantics. For exemple, scoring function inside a score.py, preprocessing functions inside a preprocessing.py or the extract.py.

Did i miss something ?

There are some dependencies, for instance parsing the model characteristics and results. Make sure that the module makes it easy, for instance by providing a fluent interface.

I tried to change the functions by semantics link with new files. But there is a huge amont of code that is hard to just move. I try my best but I don't promise anything.

@saucisson I worked a lot to this issue. Could you please get a look and tell me your opinion ?

Of course, i will look at it tomorrow.


[removeparam] [uBO] 🚀  更新清單請求 (selgros.pl)

現在 FutaFilter 對他的處置是？

I found new problematic removeparam - $removeparam=/extid/i: https://github.com/FutaGuard/FutaFilter/blob/26bf4163819aea77e9d54a820d689e1075764951/removeparam.txt#L14
I can't check Polish city shop hall from I prefere see offers.
建議對此網域做出何種改變

I suppose we can again exclude few domains like:
$removeparam=/extid/i,domain=~selgros.pl
I'm still wondering if it's possible to somehow exclude this in uBO from filtering address path parameters be like:

AdGuard maybe can use @@||selgros.pl/set_hall$document or @@||selgros.pl/set_hall$genericblock but uBO don't allow these

I suppose bad is add negation regex before $ to exclude url paths.
提出更改的理由

Open this page https://www.selgros.pl/horeca

try click in any Polish city on pop-up list "wybierz halę"

or click in  red "ZMIEŃ" behind "TWOJA HALA: nie wybrano" and now click on any city from list

list break URL path like: https://www.selgros.pl/set_hall?extId=118 so can't save checked city shop hall

I hope so, but seem there's noting we can do on this.
maybe open an Feature-Request issue on uBO's repo would be better 🥳

on uBlock-issues of lack of support removeparam?

@gorhill

sorry I didn't look carefully.
In this case maybe I should made a removeparam allow list instead.
what do think ?

If possible reporduce with AG then maybe good be is add exclude 1 Polish domain.

uBo 1.36.0 property use:
@@||selgros.pl/set_hall$removeparam


scalar implementation without code duplication

I'm currently a bit confused about the purpose of xsimd::generic. My expectation was that its possible to use this architecture as a fallback or for development purposes.  For this I would assume that xsimd::batch<T, xsimd::generic> just contains a single scalar value. But this is not the case - Instead the build fails because xsimd::has_simd_register is false.
I could specialize load_* and broadcast calls and try to separate it from the rest of the implementation which then hopefully works with scalar and simd types. But it feels like this could be abstracted through implementation of the generic architecture.
Is there a reason why this is not done? Are there examples how to write simd and scalar implementations without duplicating code?

yeah, generic means "generic vector architecture". It would work with an hypothetical vector of one register, but that architecture fallback doesn't exist.
We do provide overloads for scalar values though, i.e. xsimd::cos fallsback to std::cos where it makes sense.

Instead of the "scalar" backend, which would conflict in essence with the scalar overload we provide for every operation, we could have an emulated<n> backed that would emulate a batch of n elements using scalar operations, relying on the generic implementation etc.
Is that what you have in mind? I'd happily implement that.

@serge-sans-paille Yes this is exactly what I was looking for! Using a generic n as you suggested would actually be even better than what my initial request was.


How to make kafl-ready VM snapshot?

Hi! I can't seem to understand how to launch kAFL, specifically I don't understand how to advance from "created VM with QEMU" state to "got kafl snapshot".
In README, you are referring to original README.kAFL, where I found following instructions:

Execute loader binary <...>. VM should freeze. Switch to the QEMU management console and create a snapshot:

I tried to do the same with my Windows VM and vuln_test.exe loader. VM is not freezing by default when using kAFL patched QEMU. It is freezing when launched with non-patched QEMU, as well as when I add -device kafl,reload_mode=False to kAFL QEMU.
So I used the last method, QEMU+kAFL patch, added kafl device, executed loader, and VM freezed. Next step is to make a snapshot but QEMU hangs in pause_all_vcpus().
What am I doing wrong? Can you elaborate on ways to prepare fuzzing snapshot?

Hi! I have not tested this mode in a while, most of my targets just launch with -kernel.
You definitely need the patched Qemu and Linux kernel module so that the kAFL hypercalls are understood. The lock() implementation has changed in Redqueen to perform the snapshot automatically. Have a look at handle_hypercall_kafl_lock() in pt/hypercall.c. It should still work the as described in the readme except you don't have to enter the savevm command yourself. Perhaps check if the snapshot was already created?
You can also try to replace it with the old implementation in kAFL: https://github.com/RUB-SysSec/kAFL/blob/1ece095a7a835887477393b2bba88247b1536d4f/QEMU-PT/pt/hypercall.c#L345

I suppose, the scheme is actually to put loader in VM, launch it (it will freeze and create a snapshot by using LOCK hypercall) and use this snapshot with kAFL?

Yes, you need to run the loader once manually inside the VM and snapshot it to make the image ready for use in kAFL.
A little more detail: The first hypercall in the loader (linux_x86_64/src/loader.c) is the LOCK hypercall so (1) this requires a patched Qemu + KVM and (2) you launch this once, by calling qemu directly on commandline. kAFL will only ever use this snapshot, which makes your VM start at the point of that lock (see 'loadvm' in qemu.py). The fuzzer handshake is performed and the loader will (optionally) load the actual agent executable which can be the 'info' tool or one of the examples in linux_x86_64/bin/fuzzer/.

Ok, I am following you here. I successfully created a snapshot which is accepted by kAFL, thanks. Now I have another problem which may be relevant so I don't close issue yet:
kAFL expects RELEASE+PT_TRASHED commands in __qemu_handshake but loader (targets/windows_x86_64/src/loader/loader.c) sends ACQUIRE instead which causes immediate exit. I don't quite understand QEMU snapshot loading algorithm, but I see that next hypercall after LOCK is indeed ACQUIRE. Since ACQUIRE is first hypercall in all loaders I checked, I suppose it is intended to be so.
I see that KAFL_PROTO_PT_TRASHED is sent only from synchronization_lock(), which is called only from handle_hypercall_kafl_next_payload(). which is called only on NEXT_PAYLOAD and USER_FAST_ACQUIRE hypercalls. How is this supposed to work? Can you point me in the direction of possible root cause of this problem?

The protocol is a little crazy. I think it is correct to start with ACQUIRE on the guest though. That message does not actually match the ACQUIRE expected later on by Python. You can look at Zephyr for a working sample, it has the same flow except for LOCK (it simply reboots instead of restoring from snapshot).
Before we go there, do you actually see a warning from the python frontend about an unexpected message? qemu.py is checking and printing errors in these cases. You can also set self.debug_mode=True in qemu.py to get a more detailed log of the handshake.
If it just freezes or fails later after the handshake, chances are that other parts of the agent implementation are buggy or running into a first crash already as part of initialization. I have spend a lot of time debugging the handshake when actually the guest simply crashing due to other issues.
To answer your questions, if my notes and memory serve well, the protocol works like this:

ACQUIRE from Guest to Qemu enables PT tracing (except at first time when handshake not done)
RELEASE from Guest to Qemu disables PT tracing (only on first time it sets the handshake as done instead)
NEXT_PAYLOAD from Guest to Qemu stops the VM, triggers an ACQUIRE message from Qemu to Python
RELEASE from Python to Qemu will causes the VM to resume. It is issued after the fuzzing payload has been written to shared memory and is a response to the NEXT_PAYLOAD (seen as ACQUIRE message in Python)

So the first ACQUIRE seen by qemu.py as part of qemu_handshake() is actually triggered by the first NEXT_PAYLOAD hypercall. This and any subsequent ACQUIRE messages are answered by writing the new input to the payload buffer and then sending a RELEASE command to Qemu (see set_payload/send_payload).
Qemu can insert a PT_TRASHED message to signal a problem in PT decoding. I have not actually seen this happen but PT has a bunch of Errata. The guest can also insert a range of additional hypercalls after the handshake (first ACQUIRE/RELEASE pair) to setup the CR3 filter or hook one or more PANIC/KASAN events.
Finally, the USER_FAST_ACQUIRE seems to be a shortcut to bundle hypercalls  RELEASE, NEXT_PAYLOAD (and I think also SET_CR3) into one hypercall at the end of the loop. It is used in the usermode samples in Redqueen (tests/user_bench). I don't think you get the same speedup for kernel fuzzing, never tried it.

I can show you exact places:
Snapshot is created on https://github.com/IntelLabs/kAFL/blob/master/targets/windows_x86_64/src/loader/loader.c#L168. Note that next hypercall is ACQUIRE.
Then I am trying to use it with kAFL anf get assert(False) on this line https://github.com/IntelLabs/kAFL/blob/master/kAFL-Fuzzer/common/qemu.py#L476. As you see, __qemu_handshake expects RELEASE or PT_TRASHED to be received first which contradicts (as I understand) your statement that ACQUIRE should be sent first (which is what loader is doing).
So, on this line I get Got b'R', Expected: b'DZ' and Slave has died.

Well, maybe I misunderstood the situation a bit. Here is the log with targets/windows_x86_64/src/fuzzer/hprintf_test.c:
[HPRINTF]    [+] Starting... C:\Users\ADMINI~1\AppData\Local\Temp\\fuzzing_engine.exe
[+] Allocating buffer for kAFL_payload struct
[+] Memset kAFL_payload at address 150000 (size 131072)
[+] Attempting to open vulnerable device file (\\.\testKafl)
[+] Submitting buffer address to hypervisor...
[+] Submitting current CR3 value to hypervisor...
[FATAL] Slave 0: Error in debug_recv(): Got b'R', Expected: b'DZ'
Process Slave 0:
Traceback (most recent call last):
  File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
    self.run()
  File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/home/user/kafl/kAFL-Fuzzer/fuzzer/process/slave.py", line 59, in slave_loader
    slave_process.loop()
  File "/home/user/kafl/kAFL-Fuzzer/fuzzer/process/slave.py", line 121, in loop
    if not self.q.start():
  File "/home/user/kafl/kAFL-Fuzzer/common/qemu.py", line 461, in start
    self.__qemu_handshake()
  File "/home/user/kafl/kAFL-Fuzzer/common/qemu.py", line 476, in __qemu_handshake
    self.__debug_recv_expect(qemu_protocol.RELEASE + qemu_protocol.PT_TRASHED)
  File "/home/user/kafl/kAFL-Fuzzer/common/qemu.py", line 347, in __debug_recv_expect
    assert False
AssertionError
[FATAL] Slave has died - check logs!

So it dies somewhere in this range https://github.com/IntelLabs/kAFL/blob/master/targets/windows_x86_64/src/fuzzer/hprintf_test.c#L60-L65.

Hi vient,
Please note that the ACQUIRE send by guest is not the same as the ACQUIRE seen by qemu.py. Qemu is in between those two and does not actually forward the ACQUIRE. It just causes Qemu to lock(), and wait for a RELEASE message from Python. It is the NEXT_PAYLOAD that triggers the ACQUIRE on Python side.
On your HPRINTF log, it seems that qemu.py is still in handshake mode while your guest is already executing the NEXT_PAYLOAD/ACQUIRE/RELEASE loop. The initial RELEASE from the loader (right after lock()) should have gotten you past that failing line 476. Can you check what happened to the RELEASE/ACQUIRE hypercalls from the loader?
The first NEXT_PAYLOAD inside the agent should then trigger the ACQUIRE message in line 487. It is correct to perform the ACQUIRE hypercall only after NEXT_PAYLOAD since it will simply lock the VM until Python sends a RELEASE in send_payload().

It seems that all hypercalls in the loader after LOCK are "lost" in my case. Thus, I'm returning to the "create snapshot" stage.

Also, I want to note that using -machine pc-q35-2.4 in QEMU command line leads to host hangup after loader launch. I'm using -machine pc-i440fx-2.6 as a bypass. VM OS is Windows, maybe that's why I see this problem.

Yes, I updated that recently since the UEFI target works better with q35 and also seems to launch a little faster. Perhaps try to snapshot again with -machine pc or whatever works for your target. It is probably a good idea to use the same settings on snapshot resume.

It seems that hypercall "mismatch" happens because of race between QEMU and kAFL. I patched kAFL to run QEMU under GDB so I can set breakpoint on hypercall dispatching in kvm_cpu_exec, after second break I delete the breakpoint and fuzzing continues normally. Without GDB, hypercall "mismatch" happens every time.

Can you clarify who is failing to wait on what here? Looking back at the thread, you are saying the guest is sending the RELEASE too fast for Qemu/kAFL to handle it properly? Does it help if you insert a couple msec waiting time after the LOCK?

Yes, you understand right, QEMU executes faster than kAFL, and kAFL misses some commands from QEMU. Adding
volatile unsigned long long t;
for (t = 0; t <<PHONE_NUMBER>ull; ++t) {}    // 1000*1000*1000

seems to help (it's about a 3 seconds delay on my machine). Amusingly, Sleep WinAPI does not help, maybe there is something wrong with system clock in VM. When I try to make delay smaller by removing a zero (making it ~0.3 seconds), kafl_info.py still works but kafl_fuzz.py is no more working.

Edit: host hangups seem to appear randomly

Restarting display manager helps but I still don't understand the root cause. I'm using kAFL on fully updated Ubuntu 20.04, tried to switch from gdm3+Gnome to lightdm+xfce4, nothing changed.

I can't reproduce this locally ATM, most of my targets just work with -kernel/-initrd and I managed to stay away from Windows development thus far.
I'm not sure how we are losing the initial RELEASE "char" on the control socket. AFAIK it should stay in the pipe until read by kAFL.
0013-lock-on-RELEASE.patch.gz
Perhaps it helps to make the guest wait for kAFL issuing the RELEASE command in turn. The attached patch should do that. I don't see any changes when testing with my own targets.
The host hangups are curious. The only issues I'm aware of are insufficient disk/shm space and Qemu sometimes going OOM after a couple days. Perhaps start a separate issue if you think this is related to kAFL.

Applying this patch leads to Imported payload produced no new coverage, skipping... message, with and without for-loop sleep in loader. Test cases added in runtime to imports folder also produce this message.
kafl_info.py also does not work with this patch.

Hmm, but did get you to the same point as with the busy-loop above? It seems you are getting past the handshake now.
There is no further console output beyond these startup messages and possible runtime errors/warnings. Have you tried to open kafl_gui.py on the workdir to see the status?
There is a known issue around seed import which can result in an empty queue (zero "Paths") if you supply too few seeds. In this case the GUI will show the fuzzer stuck in [waiting] or "import" stage. Supplying a couple more seeds (~3-10) in the seed directory or at runtime via imports/ will typically fix this issue.

Have you tried to open kafl_gui.py on the workdir to see the status?

Yes, it shows "importing" constantly with 1 total exec.

Supplying a couple more seeds (~3-10) in the seed directory or at runtime via imports/ will typically fix this issue.

I tried to add additional tests to imports a couple of times, nothing changed. What concerns me more btw is that kafl_info does not work too. It means that I can't obtain driver IP range to fuzz anymore.
I'll try to look into this issue a bit later but since sleeping fix works good, can't promise anything.

Ok let me know. I agree there is something fishy going on with kafl_info hanging like this. I will test it some more with a Linux image.

'sleep' issue should be fixed in 20bc950


Fix CI failures on to_timestamp() calls

Which issue does this PR close?

Closes #7939 .
Rationale for this change

What changes are included in this PR?
Fix for to_timestamp to support multiple return types depending on the input type

Are these changes tested?

Yes
Are there any user-facing changes?

@alamb please review

I took the liberty of pushing a commit to fix a typo (that I introduced 🤦 )


[Bug Report]: Topic creations doesn't seem to work with only the name

Module path
service-bus/namespace
Bicep version
0.23.1
Describe the bug
Topic creation doesn't seem to work with minimum parameters
To reproduce
Try to create topics within a service bus namespace with only the minimum parameters
Code snippet
var queues = [ 'admin.commands', 'trial.commands', 'tenant.commands', 'frontend.commands' ]
var topics = [
  {
    name: 'machin'
  }
  {
    name: 'frontend.events'
    subscriptions: [ 'frontend' ]
  }
  {
    name: 'trial.events'
    subscriptions: [ 'admin', 'trial', 'frontend' ]
  }
  {
    name: 'legacy.events'
    subscriptions: [ 'tenant', 'trial' ]
  }
  {
    name: 'tenant.events'
    subscriptions: [
      'admin'
      'tenant'
      'trial'
      'frontend'
    ]
  }
  {
    name: 'admin.events'
    subscriptions: [ 'admin', 'frontend' ]
  }
  {
    name: 'data.events'
    subscriptions: [ 'frontend' ]
  }
]
module namespace 'br/public:avm/res/service-bus/namespace:0.1.0' = {
  name: 'service-bus-namespace'
  params: {
    // Required parameters
    name: 'sb-test-dev-1'
    skuObject: {
      name: 'Standard'
    }
    // Non-required parameters
    location: location
    queues: [for queue in queues: {
      name: queue
    }]

    topics: [for topic in topics: {
      name: topic.name
    }]
  }
}

Relevant log output
SubCode=40000. Bad Request. To know more visit https://aka.ms/sbResourceMgrExceptions. . TrackingId:af0661ed-9fca-429d-8185-e17c96e3cd49_G31, SystemTracker:sb-joseph-mtm-dev-1.servicebus.windows.net:machin, Timestamp:2023-12-13T20:03:44 (Code: MessagingGatewayBadRequest)

Hey @jdaaboul ,
I just assigned @ChrisSidebotham as he is the owner of the module.
Upon first review I did not see any obvious issue, so we need to reproduce the issue for troubleshooting.

Hi @jdaaboul,
Thanks for raising this issue. I will look in to running a test with your supplied code and respond back here with my findings. Firstly I would like to draw your attention to the current configuration you have;
topic: [
 {
  {
    name: 'frontend.events'
    subscriptions: [ 'frontend' ]
  }
 }
]

subscriptions is currently not support for the current version of the service bus module and is in development which is being tracked under this issue: #722

@jdaaboul - The issue has been found within the child module for topics this is due to parameters being passed which the RP does not allow outside of premium sku. a task has been added to the issue #722 and a fix will be included in the next update


Updated remote unit hardware

Update design with fixed solar charging circuit

Schematic, parts, and footprints updated. Pending update of PCB design until other changes are confirmed.

Note power inductor C253606 has low quantity available, probably can swap with C96164, C357084, C281325, C206300

Updated design tested and working


fix(prql-elixir): fix tests to match prql-compiler update

Follow up #1644
I was not aware that the update in #1644 would cause the test to fail.
Perhaps tests for subprojects that depend on prql-compiler should also be run if the prql-compiler is updated in PRs......

Thanks!
Yes, there's a tradeoff with completeness vs latency for the PR tests. We can always add the pr-test-all label to run all tests if we suspect there might be a failure. And all tests always run on merge, so we can revert the commit if something breaks we didn't expect...

We can always add the pr-test-all label to run all tests if we suspect there might be a failure.

Wow, that's convenient! I will make use of this next time, thanks!


googleapi: Error 403: User Rate Limit Exceeded, userRateLimitExceeded

I consistently see this error when pushing from large directories (5GB with thousands of files):
googleapi: Error 403: User Rate Limit Exceeded, userRateLimitExceeded
Assuming unlimited bandwidth and a large number of files to upload, drive could implement exponential back-off as suggested by the Google Developer's guide.

Code: 403
Reason: userRateLimitExceeded
Description: Indicates that the user rate limit has been exceeded. The maximum rate limit is 10 qps per IP address. The default value set in Google Developers Console is 1 qps per IP address. You can increase this limit in the Google Developers Console to a maximum of 10 qps.
Recommended Action: Retry using exponential back-off. You need to slow down the rate at which you are sending the requests.

Related: #240

Hello there @recursionbane, thanks for reporting and welcome to drive!
So this issue is a duplicate of https://github.com/odeke-em/drive/issues/480.
Same train of thought, exponential back-off was already added in PR https://github.com/odeke-em/drive/pull/321 and PR https://github.com/odeke-em/drive/pull/318.
You can actually see the exponential backoff retries in action by setting flag --verbose e.g
$ drive push --verbose items a1 bxf

And if the max number of tries is exhausted, it fails and returns the error.
The problem manifests from two possible issues:
a) a bug with Google's backend where rate limits are improperly accounted.
b) the default credentials used in this project are used by lots of people around the world and the bug mentioned in a) gets aggravated by exhaustion.
You can try to alleviate by setting GOOGLE_API_CLIENT_ID and GOOGLE_API_CLIENT_SECRET in your env before running drive. Please see https://github.com/odeke-em/drive#configuration.

Duplicate of #480


getchat:member invalid member

in version 1.7.5
there is an error in the method
getchat sometimes works sometimes not
and method getchatmember
error code Invalid member identifier specified
in the previous version version 1.7.3 everything was normal please fix this issue thanks issue

Which exactly error did you receive for getChat?
Between, parameters of getChatMember has changed. It is
getChatMember chat_id:int53 member_id:MessageSender = ChatMember;

now.

getChatMember(chat_ids, user_ids) {
var data = {
'_': "getChatMember",
chat_id: chat_ids,
user_id: user_ids
}
return this.handle.invoke(data)
}
code error
Member identifier is not specified
and now i build td lib again td lib but getchatmember still not working?
please fix it because in the previous version it was normal

getChatMember has parameters chat_id and member_id in the latest TDLib version.

async getChatMember(chat_ids, user_id) {
    var data = {
        '_': "getChatMember",
        chat_id: chat_ids,
        member_id: user_id
    }
    var get = await this.handle.invoke(data)
    console.log(get)
    return get
}

EROR Failed to parse JSON object as TDLib request: Expected Object, got Number

getChatMember chat_id:int53 member_id:MessageSender = ChatMember;

member_id must be of the type MessageSender. See the latest scheme at https://github.com/tdlib/td/blob/master/td/generate/scheme/td_api.tl.


show errors for use of uncached functions when cached equivalents exist

get_term_link, get_page_by_path, get_page_by_title, get_term_by, get_category_by_slug, url_to_postid

@westonruter can we merge this, too? It's a more comprehensive version of my recent patch.

I missed this. Cheers.


Slice timeseries with "pro-rata" behaviour at endpoints

Hi all
Suppose I have a timeseries indexed by a PeriodIndex at day resolution, and I want to numerically integrate it over a range whose start- and end-point are known to a higher time resolution (say, to the exact second).
As the first step towards this, it'd help to take a slice of my timeseries in which the values at the start and end are computed "pro rata" according to the proportion of that calendar day Period which is included in the range.
I was looking for a way to do this with reindex, but it's not really a reindexing, more a slicing kind of operation with special-casing of the endpoints. Is there a way to do this in pandas? Seems like it could be a useful addition if not, I imagine it could be useful for various accounting applications too.
(Even better would be a way to numerically integrate a timeseries directly while specifying endpoints at higher time resolution than the index. Unfortunately this doesn't seem possible with the sample-based integrators in scipy.integrate.)
Cheers!

closing. this might involve a transformation of the series to weight by durations. but would need a concrete use case here.


Templates - Add Animations

This ticket was set with an intentionally high estimate because it needs to be broken up more.
The goal of this ticket is to add all animations to the templates. This includes going through each template page and:

Creating a ticket for the template animations
Applying animations in the animation editor /story-anim-tool
Altering it's static layout if needed to accommodate the animation
If template requires a new animation part that doesn't already exist

Create ticket for missing animation part
Add animation part
Add animation part controls to editor

We have 8 templates right now with around 8-9 pages that need to be animated per template. More likely than not each template will require several PRs to incapsulate all the animation requirements and be manageable sizes to review.

This ticket may be broken down into smaller tickets

Closing this issue because we've broken it down into 8 tickets (1 for each template):

DIY
COOKING
FITNESS
ENTERTAINMENT
TRAVEL
BEAUTY
WELLBEING
FASHION


15 USCM Chestrig

done in https://github.com/RMC-14/RMC-14/commit/b53ff663e191c48eabc16d55e4c308d1ce17e99e


helm installation instructions is missing here: https://vsecm.com/docs/installation/

Fixed by #163.


planning v0.5.0 release

I think we have reached a sufficient number of new features that it would be nice to do another release soon. Does @PyWavelets/core agree? Any suggested date to target?
Are there other things people would like to see prior to release?  If so please add to the checklist below
Since 0.4.0 we have merged:

1D continuous wavelet transforms
new discrete wavelets added (additional Debauchies and Coiflet wavelets)
new 'reflect' extension mode for discrete wavelet transforms
routines to convert multilevel DWT coefficients to and from single array
substantial refactoring/reorganization of the underlying C and Cython code

and could probably finish the existing PRs for:

faster performance for multilevel stationary wavelet transforms
axis support for multilevel DWT
(maybe?) benchmarking via ASV

TODO

[x] add documentation for CWT
[x] document new DWT coefficient reshaping routines (PR at #208)
[x] update index.rst of the docs to reflect new features  (PR at #207)
[x] update release notes (PR at #206)
[x] handful of existing PRs to review/merge #179,  (#158?)
[x] iswt and iswt2 from the last release should also be added to the API documentation
[x] fix or remove broken doctests (see issue #209)

@holgern
Are you interested in adding some brief API documentation for the CWT routines you recently contributed?  This would involve the following steps:

add an entry for cwt to doc/source/ref/index.rst
add a new cwt.rst file in doc/source/ref following the examples for the existing files in that folder.

Agreed, +1 for new release.
I have some time next week for reviewing open PRs. And I can do some of the doc writing that's still needed. Will start with iswt/iswt2 unless someone has something already in the work.

I can do the cwt documentation.
I am planing also to add denoising algorithm for dwt. (similar to matlab function wden).

Thanks @holgern
As far as wden, there may be a comparable routine, but with n-dimensional support in scikit-image (on master, not yet released).  Specifically, there is denoise_wavelet which is an n-dimensional denoising routine based on thresholding coefficients and a routine estimate_sigma that estimates Gaussian noise standard deviation.  PyWavelets will be a dependency of scikit-image as of the next release.
See here:
https://github.com/scikit-image/scikit-image/blob/682d7e68aeaf20cddfb4d6f71ded2f4e88f8a557/skimage/restoration/_denoise.py#L482

@rgommers.  I went ahead and added iswt and iswt2 docs while I was adding swtn in #229

went ahead and added iswt and iswt2 docs while I was adding swtn

thanks! you're way too fast for me, can barely keep up with reviewing:)
getting close to checking all the boxes here, a couple more open PRs....

I think we're all good to go for a last update of the release notes and setting the version number to v0.5.0. Any objections, or shall we call it good?

sounds good.  I should be able to do a release tomorrow.  If you want to go ahead and do it sooner, that is fine too.

release notes are up to date, changing version number in gh-239. Then it's just a matter of uploading some stuff according to http://pywavelets.readthedocs.io/en/latest/dev/how_to_release.html. I see that doc is still missing info on OS X binaries and the conda-forge package. I'll look at adding that tomorrow.

I will do the uploads.  I am already a maintainer on the conda-forge package, so I can do the update there as well.

@rgommers
I think I completed everything for the release except:

what is the process for OS X binaries?
updating the outdated documentation at PyPI as discussed in #215

Thanks @grlee77. I'll update the dev docs with those things now.


Shader texture has all sprites

This can make modifying sprites very hard, because the uv coordinates don't go from 0 to 1 and other textures can easily leak in.
Example

What are you trying to accomplish? The batched textured is used for performance, it should be ok as long as the uv coordinates is correct (in the example it should be texture2D(tex, uv) if you intend to render the image)


Error: org.bbop.apollo.PermissionException: User does not have permission for any organisms.

Hello-
I am trying to run “bin/prepare-refseqs.pl --fasta yourgenome.fasta --out /opt/apollo/data” to add a new organism to the panel，but the organism isn't loaded up the webapollo. and the trackList.json is right.
Thanks,
Best,
zhangw
p.s. here is the JSON file if that tells you anything:
{
"formatVersion" : 1,
"tracks" : [
{
"category" : "Reference sequence",
"chunkSize" : 20000,
"key" : "Reference sequence",
"label" : "DNA",
"seqType" : "dna",
"storeClass" : "JBrowse/Store/Sequence/StaticChunked",
"type" : "SequenceTrack",
"urlTemplate" : "seq/{refseq_dirpath}/{refseq}-"
},
{
"compress" : 0,
"key" : "tRNA",
"label" : "tRNA",
"storeClass" : "JBrowse/Store/SeqFeature/NCList",
"style" : {
"className" : "feature"
},
"trackType" : null,
"type" : "FeatureTrack",
"urlTemplate" : "tracks/tRNA/{refseq}/trackData.json"
}
]
}

Hey friend, you must be the wrong place. I guess you should pull a issue on here https://github.com/GMOD/Apollo.


yandex-disk: <IP_ADDRESS>0 -> <IP_ADDRESS>9

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/yandex-disk/versions.
meta.description for yandex-disk is: '"A free cloud file storage service"'.
meta.homepage for yandex-disk is: '"http://help.yandex.com/disk/cli-clients.xml"

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found <IP_ADDRESS>9 with grep in /nix/store/k3150wzgj6fjxkamkjy5zagjawb3psfr-yandex-disk-<IP_ADDRESS>9
directory tree listing: https://gist.github.com/adddc1e32e79670f8baca4263bd3df16
du listing: https://gist.github.com/61af7ee8fe9ef22fc2da5fae7aaccce0

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

2 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
yandex-disk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/k3150wzgj6fjxkamkjy5zagjawb3psfr-yandex-disk-<IP_ADDRESS>9 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A yandex-disk https://github.com/r-ryantm/nixpkgs/archive/6b62be5eff261073f9317243cf034e6ea8fb5d55.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/k3150wzgj6fjxkamkjy5zagjawb3psfr-yandex-disk-<IP_ADDRESS>9
ls -la /nix/store/k3150wzgj6fjxkamkjy5zagjawb3psfr-yandex-disk-<IP_ADDRESS>9/bin

cc @grwlf @jagajaga for testing.

@mmahut for which platforms did you check the build?

@markuskowa sorry, that should have been eval, misclicked. I build it on x86_64-linux.


Add auto location

It would be nice if the location updated automatically based on my current location

This is not possible due to the open-meteo weather api limitation.
Some providers have a button to detect location: https://github.com/rocksdanister/weather/issues/45
But not worth implementing automatic detection right now since it wont work with the default open-meteo provider.

okay then

Keep it open, I'll get to it when open-meteo adds support.


945 Allow contact increase for simulation of larger events

Changes and Information
Please briefly list the changes (main added features, changed items, or corrected bugs) made:

Remove the assertion for negative Damping coefficients
Now, we can model an increase of contacts which is important for the simulation of larger events

If need be, add additional information and what the reviewer should look out for in particular:

Merge Request - Guideline Checklist
Please check our git workflow. Use the draft feature if the Pull Request is not yet ready to review.
Checks by code author

[x] Every addressed issue is linked (use the "Closes #ISSUE" keyword below)
[x] New code adheres to coding guidelines
[x] No large data files have been added (files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
[x] Tests are added for new functionality and a local test run was successful (with and without OpenMP)
[x] Appropriate documentation for new functionality has been added (Doxygen in the code and Markdown files if necessary)
[x] Proper attention to licenses, especially no new third-party software with conflicting license has been added
[ ] (For ABM development) Checked benchmark results and ran and posted a local test above from before and after development to ensure performance is monitored.

Checks by code reviewer(s)

[ ] Corresponding issue(s) is/are linked and addressed
[ ] Code is clean of development artifacts (no deactivated or commented code lines, no debugging printouts, etc.)
[ ] Appropriate unit tests have been added, CI passes, code coverage and performance is acceptable (did not decrease)
[ ] No large data files added in the whole history of commits(files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
[ ] On merge, add 2-5 lines with the changes (main added features, changed items, or corrected bugs) to the merge-commit-message. This can be taken from the briefly-list-the-changes above (best case) or the separate commit messages (worst case).

@HenrZu Please see (and review) tests, example and slight default value changes.

I just added some line breaks after the std::cout calls to make the output clearer. Otherwise it is an very interesting & helpful example


Update introduction.html

I'm not sure if it was intentional, but the previous grammar didn't make sense to me.

Thanks!


date today does not change after 00:00

persianCalender don't update today date when is mobile clock or simulator clock after 00:00.
and when select date and check date with onDateChange date is one day ahead.
please check it.
thank's

Yes, I have this problem too.

yes i have same problem and i dont know how resolve this issue.

@mskarimi Can you provide more details?
A snippet of your code and Environment details

same !


Modules - new metric for duplicated packages

[x] add duplicatedPackageCount metric
[x] add list of duplicated packages to warnings
[x] add duplicate flag to packages table

Duplicate Packages Count metric

the number of packages that are duplicated

Filter packages data by duplicate

Warning for duplicate packages


Re-enable code coverage in CI

Re-enable code coverage so that I can use the CI to vet a potential fix.

Thanks, @tanviraumi !


400: Bad Request

After the 1.2.4 update, I have a "400 Bad Request" error when trying to use the start option.

Changing ID to any other number corrected issue.

Changing deviceId? It's possible you just needed to restart homebridge.

I tried relaunching and rebooting the device first. Once I changed the deviceID it worked again.

Interesting. Good to know, though, thanks.


Request: propagate variational dynamics at the same time as mass state

It is currently not possible to propagate variational dynamics when the mass of the body is propagated at the same time as its translational state. Errors like these are raised instead:
RuntimeError: Warning, dependency of central gravity on body masses not yet implemented
RuntimeError: Warning, dependency of aerodynamic acceleration on body masses not yet implemented

In particular, a (somewhat tricky) link to thrust acceleration must be made.
This feature request is low-priority.

This has been addressed and added in the thrust/rotation refactor, I've just pushed an improvement to the unit test of this to the develop branch.


UserButton bug

when trying to render user button (with nothing special, it worked before update to latest) ui send error alert

Im not able to replicate this. Would you be able to create a basic repro via stackblitz or something?

i found the issue, you need to specify a sub-component inside , i just dropped there an empty action, and it fixed.. (not the best solution cause i have an error there.
long story short you need to support the component as is without additions (in my opinion)

Whats your vue-clerk version?

latest

Kk Ill try out later today but would love a stackblitz or repo for a basic repro

Still not getting it. Even if you try the starter here - https://github.com/wobsoriano/vue-clerk-quickstart
I suggest you remove node_modules and your lockfile then reinstall again.
Feel free to reopen with a reproduction if you want!


[UI] Adopt fundamental styles - view Websockets

Target

[ ] Adopt the fundamental styles in Websockets view

Use https://github.com/dirigiblelabs/ide-next as reference

Issue cloned to https://github.com/eclipse/dirigible/issues/1520


Better replace logger support

I don't think it's safe to call
1. LogcatLogger.uninstall()
1. LogcatLogger.install(AndroidLogcatLogger())

Because another thread could call logcat { "Well intended message" } between lines 1 and 2.
It's true that uninstall sets the logger to NoLog which says nothing is loggable.  This would likely just drop any logcat{} logs that come in on the floor..  but... I was thinking that since the logcat{} calls delegate to the logger without locking on Logcat (which is an obvious choice and makes sense, you don't want to lock on that), but since we don't, I think it could be (looking at the implementation)
inline fun Any.logcat(
  priority: LogPriority = DEBUG,
  /**
   * If provided, the log will use this tag instead of the simple class name of `this` at the call
   * site.
   */
  tag: String? = null,
  message: () -> String
) {
  LogcatLogger.logger.let { logger ->

    //  IF THE LOG SWAP TO NoLog HAPPENS AFTER THIS if isLoggable LINE FIRES
    if (logger.isLoggable(priority)) {

      val tagOrCaller = tag ?: outerClassSimpleNameInternalOnlyDoNotUseKThxBye()

      // BUT BEFORE THIS logger.log LINE FIRES
      logger.log(priority, tagOrCaller, message())
    }
  }
}

Then the NoLog will throw an exception
private object NoLog : LogcatLogger {
    override fun isLoggable(priority: LogPriority) = false

    override fun log(
      priority: LogPriority,
      tag: String,
      message: String
    ) = error("Should never receive any log")
  }
}

tl;dr;
I think we should offer a replaceLogger something like..
fun replaceLogger(newLogger: LogcatLogger) {
    synchronized(this) {
        uninstall()
        install(newLogger)
    }
}

And I think we should make NoLog gentler and something like
private object NoLog : LogcatLogger {
    override fun isLoggable(priority: LogPriority) = false
    override fun log(priority: LogPriority, tag: String, message: String) = Unit
  }
}

If you need to have two logger implementations and swap these out, you can just make a logger implementation that does that within itself.
The API was never meant to be used as "uninstall(), install()" as a way to swap impls, and I'd rather not relax NoLog just for a use case that the APIs aren't meant to support and that AFAIK can be implemented with a custom logger


POL-293 Backend paging for trigger history

Depends on https://github.com/RedHatInsights/policies-ui-backend/pull/119

Codecov Report

Merging #165 into master will decrease coverage by 0.27%.
The diff coverage is 94.54%.

@@            Coverage Diff             @@
##           master     #165      +/-   ##
==========================================
- Coverage   91.79%   91.52%   -0.28%
==========================================
  Files         149      149
  Lines        2878     2857      -21
  Branches      488      485       -3
==========================================
- Hits         2642     2615      -27
- Misses        234      240       +6
  Partials        2        2

Impacted Files
Coverage Δ

src/components/Trigger/Table.tsx
86.48% <ø> (-10.82%)
:arrow_down:

src/components/Trigger/TableToolbar.tsx
100.00% <ø> (ø)

src/generated/Types.ts
100.00% <ø> (ø)

src/types/Policy/Policy.ts
100.00% <ø> (ø)

src/pages/PolicyDetail/hooks/useTriggerPage.ts
84.61% <77.77%> (-5.39%)
:arrow_down:

src/pages/PolicyDetail/hooks/useGetAllTriggers.ts
95.65% <95.65%> (ø)

src/generated/ActionCreators.ts
92.40% <100.00%> (+0.19%)
:arrow_up:

src/pages/PolicyDetail/PolicyDetail.tsx
100.00% <100.00%> (ø)

src/services/useGetPolicyTriggers.ts
100.00% <100.00%> (ø)

src/types/Page.ts
84.31% <100.00%> (-7.53%)
:arrow_down:

... and 5 more

This looks good. All the functionality I can exercise seems working. The refactor is cleaner as well. Nice. LGTM. Merging.


createkubertetesbinariesiso: Saving images in network and dashboard yaml

Description
Downloads images int the network and dashboard yaml while creating the kubernetes binaries iso
This step was skipped, so bringing up a cluster on a node that does not have access to the internet failed since the weavenet and dashboard images were not found locally
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

How Has This Been Tested?
./create-kubernetes-binaries-iso.sh ./ 1.11.4 0.7.1 1.11.1 https://github.com/weaveworks/weave/releases/download/latest_release/weave-daemonset-k8s-1.11.yaml https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.0/src/deploy/recommended/kubernetes-dashboard.yaml
..........
Downloading docker image k8s.gcr.io/kube-apiserver-amd64:v1.11.4 ---
Downloading docker image k8s.gcr.io/kube-controller-manager-amd64:v1.11.4 ---
Downloading docker image k8s.gcr.io/kube-scheduler-amd64:v1.11.4 ---
Downloading docker image k8s.gcr.io/kube-proxy-amd64:v1.11.4 ---
Downloading docker image k8s.gcr.io/pause:3.1 ---
Downloading docker image k8s.gcr.io/etcd-amd64:3.2.18 ---
Downloading docker image k8s.gcr.io/coredns:1.1.3 ---
Downloading docker image weaveworks/weave-kube:2.7.0 ---                       << Added image from network yaml
Downloading docker image weaveworks/weave-npc:2.7.0 ---                        << Added image from network yaml
Downloading docker image k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.0 ---     << Added image from dashboard yaml

Nice! Thanks @davidjumani. Will test this out

@davidjumani should this go in 4.14? And do we need to make any change in docs (added a new param for script)?

@davidjumani should this go in 4.14? And do we need to make any change in docs (added a new param for script)?

@shwstppr Don't think it's needed as it's an optional parameter and used in automated build jobs

@blueorangutan package

@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✖centos8 ✔debian. JID-2407

@blueorangutan test

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3213)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 30086 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4459-t3213-kvm-centos7.zip
Smoke tests completed. 83 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File


extraPodAnnotations doesn't apply to the migration pod

I deployed the following in a namespace that has istio injection enabled
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: dev
spec:
  config:
    datastoreEngine: postgres
    extraPodAnnotations:
      sidecar.istio.io/inject: "false"
  secretName: dev-spicedb-config

I was trying to add the annotation with extraPodAnnotations to the generated pods so that the sidecar doesn't get injected
Istio adds a sidecar to every pod created in that namespace. Because the sidecar keeps running, the pod never reaches the Completed stage, preventing the operator from progressing further (and creating the spicedb pods)
Since this migration pod is also generated by the operator, shouldn't the additional annotations apply to the migration pod as well?
I know I can either deploy the spicedb cluster to a namespace that doesn't inject sidecars, or configure the Istio operator to never inject anything in the pods that match the labels for spicedb, But it may be simpler, and perhaps more consistent, to apply the same annotations to the migration pod as well.
Another possible solution could be for the operator to only check the status of the migration container within the pod, instead of checking the pod status before moving on

Right now, extraPodLabels only applies to the deployment pods, not the jobs.
There's a PR in progress (https://github.com/authzed/spicedb-operator/pull/135) that attempts to address this generically - that would look something like:
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: dev
spec:
  config:
    datastoreEngine: postgres
  secretName: dev-spicedb-config
  patches:
    - kind: Job
      patch:
        spec:
          template:
            metadata:
              annotations:
                sidecar.istio.io/inject: "false"

Thanks for the very quick response (once again, since you did the same earlier this morning). Looking forward to it.

While the PR #135 looks exciting, until the work there has completed, consider merging PR #147.

@ecordell any plans to cut a new release with the #147 merged in?


mime/multipart: setting Content-Type in multipart part prevents it being read in go 1.10

What version of Go are you using (go version)?
1.10
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
playground
What did you do?
after upgrading to go 1.10 from 1.9 setting a Content-Type in a multipart part headers prevents the part being read
https://play.golang.org/p/ZUojNd8oREd
any other canonical header seems fine (comment out Content-Type and try other values)
What did you expect to see?
req.FormValue("hello") should print out the value of the formfield
What did you see instead?
nothing

Hello
Seems from Go 1.9 to 1.10, the behavior of mime/multipart Reader method ReadForm changes, you can see the new code here:
https://golang.org/src/mime/multipart/formdata.go#L61
the presence of a "Content-Type" header force the read interpret this part as a Form File, instead a Form Value
https://play.golang.org/p/lykpJ6Q01t5
I think it is linked to issue #19183

this seems the case when the filename is empty versus absense of filename

The data is still there, and is accessible via req.FormFile.  I don't know whether there is something to fix here or not.
CC @nilsmagnus

Since the change doesn't appear to be intentional, it seems that we should restore the old behavior (while keeping whatever fix was intended). CLs welcome.

More details in https://github.com/golang/go/issues/24060

@ianlancetaylor

Moving to 1.10.2 due to discussions about this not potentially being the right fix.

hey @andybons I'd love to help out, any chance of more details? thanks!

I'll let @ianlancetaylor chime in on that one.

My concern is simply that I don't know how to be sure that this is the right fix, and I want to be careful that we don't jerk people around in the 1.10 release cycle.  I would open to simply reverting the whole thing in 1.10.1 so that we can try again in 1.11.

Totally understand, as it stands this means upgrading to 1.10 will break codebases, I guess it depends on how many people you feel are left to update vs have already updated.
FWIW as an implementer and someone effected by this bug I wouldn't mind reverting code I wrote to work around a regression.
If we're not patching perhaps we could add a "known regressions" note to 1.10?

@gopherbot please open a 1.10 backport tracking issue. See the discussion about what to backport in #24041.

I imagine my team is not the only one holding out before upgrading to 1.10 until this is resolved. The milestone has shifted from 1.10.1 to 1.10.2 and now 1.11. Are there strong opinions against reverting to the 1.9 behaviour or is a CL/PR what is required?

I'm dowgrading to 1.8, and apparently when 2 go installed 1.10 and 1.8 this problem still arise '__')
even when go version command shows 1.8
crazy when 1 line changed in my codebase, built with my deployment server cause a problem a week later..
the finding out that this is the culprit

So, this was closed but it seems that it should not have been since we’re not clear on the fix? @ianlancetaylor

I've applied the "patch" from the backport and it seem to work form me. If it helps.

Frankly I have no idea what the right thing to do is here.  I regret approving the original CL (https://golang.org/cl/70931).
As I understand it, and I probably don't, the issue is about where we store the data associated with a part of a multipart/form-data.  We record it in either the Value field or the File field of the returned multipart.Form value.  When used with net/http, this plays into whether the code should use FormValue or FormFile.
In Go 1.9, if there was no filename, or if the filename was the empty string, we used the Value field.
In Go 1.10, this was changed (https://golang.org/cl/70931) so that we use the File field if there is a Content-Type header.  In other words, previously we used the File field if there was a filename.  In Go 1.10, we also use the File field if there a Content-Type header, even if the filename is missing.  The argument for this change (in #19183) was that RFC 2388 says that the filename is optional.  Note that the multipart.Form Value and File fields, and therefore with the http.Request FormValue and FormFile methods, the value is stored not using the filename, but using the name of the part.  So even if the filename is missing, it is still possible to look up the value.  In 1.10, looking up a value with a missing filename using File or FormFile will return a multipart.File with an empty Filename.
That change let to this issue being filed.  Basically, cases that used to be in Value are now in File, causing an unexpected change.
So in the future 1.11, the behavior was changed again, by https://golang.org/cl/96975.  Now if there is no filename, we use the Value field.  This is closer to the 1.9 behavior, but the behavior differs if there is a filename that is the empty string.  In 1.9 an empty filename used the Value field.  In 1.11, an empty filename uses the File field.  In both cases a missing filename uses the Value field.
So CL 96975 essentially undoes the argument in #19183, in that once again the filename is relevant to the choice of representation, even though the RFC says that the filename is optional.  However, it does so in a way that preserves the behavior of the test added in CL 70931, which has a filename that is the empty string.
As far as I can tell none of this matters very much.  The data is available either way.  It's just that you have to access it in different ways.  People writing new code can probably figure it out.  For existing code, we shouldn't change things.
So I think there is a solid argument to be made for reverting CL 96975, then reverting CL 70931, which will get us back to the state we were in in 1.9, then closing #19183 as "sorry," and closing this one because we've gone back to the old behavior.  And then, for 1.10.3, reverting 70931 to go back to the 1.9 state.
And then we can try to forget the whole thing.

@nilsmagnus @matiasanaya see previous comment.

I think Ian's suggestion makes sense but it looks like this did not make it into 1.10.3?

@ianlancetaylor I agree with you on reverting this change. I had no idea that this issue would cause that much trouble in the first place.

@gopherbot please backport to 1.10


Enable Discussions and Wiki for this repository

This is an amazing project.  I think adding discussions and wiki will allow the community to grow it further as we can then collaborate with each other more easily.  The wiki will allow us to share more examples, templates, etc with each other.

Howdy! Thanks for the compliment.
I didn't even think of that but I can do!
Also soon we'll have proper high availablity!

That would be so amazing!  I was just talking to my team yesterday about Wag and we are worried about losing service if our Wag server is down.  Can't wait for HA!  HA all the way!
One thing I would post to "Discussions" once you enable it is:  How do we see the transfer stats for byes sent/received?
It's not really an "Issue" but something the community can answer too so you can focus on fixing bugs and adding other cool features like HA.

To see that you'd have to just use sudo wg on the box you're on. You can open that as a feature request, as it wouldnt take much to add.
Just noting that the HA work is still on-going so you might not get a release with that for quite a while

Sweet both of those are enabled. Neither of them has content :P


How is the Deep Copy files are generated ?

I have cloned this repository, and tried to run ./hack/update-codegen.sh the script is not generating the deepcopy related files, what am i missing ?

go version go1.19.5 darwin/amd64 is the go version

Different repo but same problem:
I solved running go mod vendor in the repo, modified the script as you can see in the repo https://github.com/fulviodenza/sample-apiserver and then moving the right files in the right folders. Unfortunately this was the only method I found.


Fix link to AIOHTTP docs

@michaelyaakoby How can this change find its way to Pyctuator's PyPI page (https://pypi.org/project/pyctuator/)? Is there an automatic process which will kick in at some point?

Once we run the "publish" action, it'll publish a new version and doc.


[$250] [Advanced Approval Workflows]: Implement Sorting

Coming from this project, we have this follow-up polish issue we need to complete where we implement the ability to sort. More details here.
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01078457d0b3153dad
Upwork Job ID:<PHONE_NUMBER>827284233
Last Price Increase: 2024-08-20

Issue OwnerCurrent Issue Owner: @

cc @blazejkustra

Hey! I’m Błażej Kustra from Software Mansion, an expert agency, and I’d like to work on this issue!

Hi @blazejkustra! It's all yours!

Proposal
Please re-state the problem that we are trying to solve in this issue.
During workflow configuration, when the Approver is being selected the list of the members shown for selections is not sorted alphabetically.
What is the root cause of that problem?
There is no sorting applied to the items in the list therefore they have the default ordering from the BE.
What changes do you think we should make in order to solve the problem?
In WorkspaceWorkflowsApprovalsApproverPage.tsx we need to sort the list of the items before they are passed to the Section.
https://github.com/Expensify/App/blob/c9954ad33543c7e98807a8ea0b1e131402a7c7df/src/pages/workspace/workflows/approvals/WorkspaceWorkflowsApprovalsApproverPage.tsx#L152
Should be replaced with this:
data: OptionsListUtils.sortItemsAlphabetically(filteredApprovers)

https://github.com/Expensify/App/blob/c9954ad33543c7e98807a8ea0b1e131402a7c7df/src/pages/workspace/workflows/approvals/WorkspaceWorkflowsApprovalsApproverPage.tsx#L357
Should be replaced with this:
data: OptionsListUtils.sortItemsAlphabetically(formattedApprover)

https://github.com/Expensify/App/blob/c9954ad33543c7e98807a8ea0b1e131402a7c7df/src/pages/workspace/workflows/approvals/WorkspaceWorkflowsApprovalsApproverPage.tsx#L363
Should be replaced with this:
data: OptionsListUtils.sortItemsAlphabetically(formattedPolicyEmployeeList)

What alternative solutions did you explore? (Optional)
We could introduce sorting as a capability of the SelectionList component to have ordering built into it, so that when we pass sections to the component we can choose if the section items should be ordered ASC or DESC. That sounds like over engineering to me though.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~018cf234fc3c53341a

@dylanexpensify Please help process the payment for me. Thanks

@dylanexpensify The Upwork job is no longer available, could you create a new job and send the offer to my profile here? https://www.upwork.com/freelancers/~010c6310ab55f3d17d
Thanks

@dylanexpensify Bump on above comment

Done!


CSE APIs with content reuse

Purpose of this pull request
CSE API docs leveraging content reuse.

Select the type of change:

[x] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

@kimsauce, I added the FED URL to the cse-api-table.md file in /docs/reuse, per my comment in PR 1960.


MinMDNS client requires recursion and support for multi-answer in a single packet

Problem
MinMDNS makes some assuptions to be 'minimal' however these assuptions break especially on thread. Specifically:

It assumes that a single packet contains a single answer for a specific node. This is incorrect for "Browse" for example, where a OpenThread Border Router may answer on behalf of multiple thread devices in a single packet, resulting in separate SRV/AAAA/TXT entries in a single packet. MinMDNS will currently "Pick last entry" and assume they match, but they do not have to

It assumes that a reply containing a SRV entry would contain also TXT and A/AAAA entries. mDNS spec says that implementations SHOULD do this, but not SHALL  and specifically for OTBR we observed that we may get SRV entries without IP addresses and then Operational Discovery will fail.

MinMDNS enters a 'mode' state where it either browses or does operational discovery. Since replies are async, this is incorrect in terms of calling operational vs commissioning discovery callbacks.

Proposed Solution
Implement stateful processing of mDNS replies:

every SRV entry should be considered individually and matched with TXT and AAAA (maybe A) entries
if TXT/AAAA entries are not received, the server should explicitly query for them. Note that AAAA entries are matched by a separate host address (i.e. request has to be based off SRV content)

MDNS packet processing should not depend on a stateful logic of 'sending queries'. Sending queries should be independent from receiving results.

Recursive minmdns support added. Closing issue.


automatic evaluation of cairoVersion in Account

Motivation and Resolution
Solve account discussion from #759
Account object is able to define itself the cairoVersion variable.
Usage related changes

At Account instance creation, if the account exists in the network, the cairoVersion parameter is not necessary. It will be automatically defined.
If the account is not existing in the network, and if the cairoVersion parameter is not used, the default version is applied.
If the cairoVersion parameter is used, its value is used, whatever the status in the Network.
version by default remains with "0".

Development related changes
If the cairoVersion isn't defined by the user at the creation of the Account instance, it will be defined once, just before it is necessary in an Account method (estimateFee, execute, ...)
Checklist:

[x] Performed a self-review of the code
[x] Rebased to the last commit of the target branch (or merged it into my branch)
[x] Linked the issues which this PR resolves
[x] Documented the changes in code (API docs will be generated automatically) : updated guides
[ ] Updated the tests
[] All tests are passing

Do I take the opportunity to change default CairoVersion to "1"?

Ready for review.
default CairoVersion remains "0".


Allow specifying path for socket connections

Enhance and normalize endpoint customization via IUrlResolver.
In our scenario, we host r11s containers along with other microservices in a k8s cluster with an nginx gateway. The requirement is to use a single public endpoint and proxy all service HTTP and WS traffic through the gateway. For instance,
https://*.azure.net/api/proxy/collab/repos/{tenantId}
https://*.azure.net/api/proxy/collab/deltas/{tenantId}/{documentId}
wss://*.azure.net/api/proxy/collab/socket.io/?documentId={documentId}&tenantId={tenantId}

Currently (as of v0.30), a URL resolver is only capable of specifying endpoints for orderer, storage and delta storage services.
Where ordererUrl, in fact, can only be a base URL without a path as it's used in other places to format nested URLs, such as RouterliciousDocumentServiceFactory.
Ideal solution would be specifying a single orderer URL and let the Fluid driver infer the rest following a default convention.
Alternatively, tweak IFluidResolvedUrl to carry additional path parameter for socket connections, and fix the r11s document service factory to adhere to the same URL schema.

Happy new year! Any feedback on this issue? Thoughts or ideas?

Happy new year! Any feedback on this issue? Thoughts or ideas?

@tanviraumi what are you thoughts?

@tanviraumi what are you thoughts?

I am not sure why specifying three separate endpoints becomes an issue. We can't have just one url since storage url can be totally separate from orderer url. Delta and orderer url are also mostly disjoint. Do you want to specify any specific path to orderer url to route your socket requests?

I am not sure why specifying three separate endpoints becomes an issue. We can't have just one url since storage url can be totally separate from orderer url. Delta and orderer url are also mostly disjoint. Do you want to specify any specific path to orderer url to route your socket requests?

We need a method of specifying path in socket connection in DocumentDeltaConnection
const socket = io(
    url,
    {
        ...
        path:"/api/proxy/collab/socket.io",
        ...
    });

We need a method of specifying path in socket connection in DocumentDeltaConnection
const socket = io(
    url,
    {
        ...
        path:"/api/proxy/collab/socket.io",
        ...
    });

I think we can add an optional property to IFluidResolvedUrl. Feel free to send a PR

I think we can add an optional property to IFluidResolvedUrl. Feel free to send a PR

@alpaix - we should either find a way to propose a solution or close it, IMHO. Are you in position to raise a PR with proposal?

Will take a look

The workaround for this issue is to fork a driver that would allow customizing network endpoints and connection parameters. Will re-open if the driver approach is not sufficient.


chore: upgrade tradingview

Description

TradingView TA has been upgraded.
https://github.com/brian-the-dev/python-tradingview-ta/releases/tag/v3.2.10
Related Issue

N/A
Motivation and Context

Keep it up to date.
How Has This Been Tested?

Screenshots (if appropriate):

Codecov Report

Merging #426 (d164b2d) into master (0911946) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #426   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           80        80
  Lines         2936      2936
  Branches       546       546
=========================================
  Hits          2936      2936

Continue to review full report at Codecov.

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


add some of the podcast's feed and fix radio budio link

later will add more feeds :)

@numb95 thanks a lot :)

@SamaneYaghoobi you're welcome. I will add some more feed soon :D

@numb95 Great! thanks


[Request] LabelIf attribute

It would be nice to be able to conditionally change the name of a variable that shows on the inspector. I want to use the same variable, but show a different name under different conditions. Currently, I need to have multiple variables and use the show/hide feature to do this, but that's not optimal. Being able to change the label conditionally would be best. Thank you!

@dbrizov @IF-ACT Hopefully this feature will make it to the next update?

Little late with this, but for future googlers, feel free to check out Pull Request #358 :)


IPv6 nginx binding is preventing KubeInvaders from running in AKS

Hi I was wondering if we can remove line 8 in KubeInvaders.templ which is the IPv6 nginx binding and since Azure Kubernetes Service (AKS) does not support IPv6 it's not possible to run the image.
Le me know and I can create a PR.

Hi @cmendible please feel free to create a PR! There is no reason for to use IPv6 at moment so I will accept your change.
Thanks!


fix(elixir): Fix unused vars, chunk_every

While compiling, I had these deprecations:
Compiling 24 files (.ex)
warning: variable "reason" is unused
  lib/verk/queues_drainer.ex:49

warning: variable "shutdown_timeout" is unused
  lib/verk/queues_drainer.ex:49

warning: Enum.chunk/2 is deprecated. Use Enum.chunk_every/2 instead
  lib/verk/sorted_set.ex:82

I realize chunk is for older OTP versions. I assume the project doesn't want to deprecate until actually necessary?

Coverage increased (+0.03%) to 87.917% when pulling f8ba244aa5c25610fb626d027e045d9f5465adc3 on raksonibs:fix-outdated-elixir into 9365c712bc4062d09cf78a397bcc09aaf1b7494c on edgurgel:master.

TBH I think we will drop support to Elixir 1.4 soon so if you want to "unrevert" your last commit 😆

Done @edgurgel :)


fix: MDN link to slice removed as it is not required for the challenge

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[ ] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[ ] Tested changes locally.
[ ] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

Array.prototype.slice() is not used in the challenge "Diff Two Arrays". Removed MDN link to that.
PR for same change on production: https://github.com/freeCodeCamp/freeCodeCamp/pull/15911

@prateekgoel Please add issue number in the Checklist.

Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

MDN links are no longer used in the UI of beta and will be phased out.

Ok @BerkeleyTrue . Thanks.


Fix tx submit stuck

Codecov Report

Merging #1197 (22c7e45) into master (929c401) will increase coverage by 36.16%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #1197       +/-   ##
===========================================
+ Coverage   38.83%   75.00%   +36.16%
===========================================
  Files         422       33      -389
  Lines        9677      972     -8705
  Branches     1801      224     -1577
===========================================
- Hits         3758      729     -3029
+ Misses       5640      229     -5411
+ Partials      279       14      -265

Impacted Files
Coverage Δ

src/index.ts
100.00% <0.00%> (ø)

src/persisistentState.ts
100.00% <0.00%> (ø)

...components/common/Advice/AdviceIcon/AdviceIcon.tsx

src/app/layout/Header/TotalButton/TotalButton.tsx

src/transaction/BroadcastTx/index.ts

src/icons/Pen3.tsx

src/transaction/index.ts

src/app/layout/Home/Home.tsx

src/services/transactions/TxService.ts

src/icons/Menu.tsx

... and 381 more

Continue to review full report at Codecov.

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


Calling moment.locale(x) does not result in updated Ng2Datetime static variables

If I change the moment locale dynamically, the change is not reflected in the variables, e.g Ng2Datetime.firstDayOfWeek won't change when I switch locales.
When I switch the locale, I would like to see the calendar update accordingly.
I would expect that these moment.localeData() lookups are done lazily, but I see that they're called on import time. This way, I won't even be able to set an initial locale in my AppModule code, which is evaluated later than the ng2-datetime-picker code.
Would it not be better to use getters for these variables? You can use a setter for manual override, but if this is not used, then use the getter function.

@woutervandergraaf thanks for your suggestion. I agree with you on this matter.
Can you make an effort and create a PR for this? or else you need to wait until I have time for this implementation.

I will have time for this next week. Until then...

@woutervandergraaf this has been implemented

Wow, I was about to make time for this on Friday, but you beat me to it! Very nice. I'll be your tester then.


The test case validates for different content type in scim 1.1 api

Purpose
This test case sends checks if wrong content types are validated
Tested environment
1.ubuntu 18.04
2.java version "1.8.0_161"
3.Identity server wum updated pack wso2is-5.7.0+1543336788716.full with jdbc user store
Automation tests
The test attempts to provision a user with application/xml as the content type for scim 1.1 api and asserts the response code

closing this PR will be sending 1 PR for scim 1.1 scenarios


Help output reports wrong binary name.

What happened?
The compiled binary is named datasource. The help output assumes a binary named pomerium-datasource:
Run 'pomerium-datasource --help' for usage.

What did you expect to happen?
The help output and file name to match.

This should be fixed with :

https://github.com/pomerium/datasource/pull/50
https://github.com/pomerium/datasource/pull/51

Can you confirm @alexfornuto ?

Confirmed!


Additional test for trestle add

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[ ] All commits are signed.

hmmm... tests failing... doesn't look like the failing tests are to do trestle add. I'll have a look on Monday

hmmm... tests failing... doesn't look like the failing tests are to do trestle add. I'll have a look on Monday

Shouldn't have merged develop?


cleanup: remove old region tag (spanner_update_dml_returning)

Fixes N/A

Related to PR: https://github.com/googleapis/java-spanner/pull/2448
After cl/533584267 is merged we must merge this PR to remove the old region tag

Not required since all Golden languages except Python uses the correct region tag. So we must only update the Python samples


Set metallic property to 0

This fixes lighting bug on 1.34.2+

Are you sure this is the proper fix? This seems to be a blanket solution for all materials, but to my knowledge you only need to fix Standard, no?

Are you sure this is the proper fix? This seems to be a blanket solution for all materials, but to my knowledge you only need to fix Standard, no?

I could add a check for Standard, thats right

Are you sure this is the proper fix? This seems to be a blanket solution for all materials, but to my knowledge you only need to fix Standard, no?

I could add a check for Standard, thats right

Done!

Updated it to make the shader property change directly when instantiating the material


fix: always request openid scope from idp

Description
Changes proposed in this pull request:

busola shall always request the openid scope

Related issue(s)
#3288
Definition of done

[x] The PR's title starts with one of the following prefixes:

feat: A new feature
fix: A bug fix
docs: Documentation only changes
refactor: A code change that neither fixes a bug nor adds a feature
test: Adding tests
chore: Maintainance changes to the build process or auxiliary tools, libraries, workflows, etc.

[x] Related issues are linked. To link internal trackers, use the issue IDs like backlog#4567
[ x Explain clearly why you created the PR and what changes it introduces
[x] All necessary steps are delivered, for example, tests, documentation, merging

/test all

@mrCherry97 could you please have a look?

Closing, in favor of #3209


Create check_palindrome.cpp

Program for check the number is palindrome or not.
Description of Change

Checklist

[ ] Added description of change
[ ] Added file name matches File name guidelines
[ ] Added tests and example, test must pass
[ ] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[ ] Relevant documentation/comments is changed or added
[ ] PR title follows semantic commit guidelines
[ ] Search previous suggestions before making a new one, as yours may be a duplicate.
[ ] I acknowledge that all my contributions will be made under the project's license.

Notes:

@manjur29  palindrome is already implemented. See https://github.com/TheAlgorithms/C-Plus-Plus/blob/master/others/palindrome_of_number.cpp
You can search Directory.md for what algorithm implementation available.

Palindrome algorithm is already implemented

There can be different implementations for one algorithm;
the name needs to be changed only if it's on the same directory. 🙂

@Panquesito7 If you see the #1201

There can be different implementations for one algorithm;

Oh I see both have different implementation. Thanks!

the name needs to be changed only if it's on the same directory.

This may not be correct if you see 1211 issue. and this comment  Where we are having issue with cmake if both files have same name but different directory.

Any updates?


TypeError: createJWKSMock is not a function

Hello!
I'm using mock-jwks and nock to mock the auth0 authorization in a Node.js project but after switching to Jest 27 and enabling ES modules I get this error "TypeError: createJWKSMock is not a function". The tests were working fine before I enabled ES modules in Jest. Also, I'm not doing any kind of code transformation/compilation.
This is a screenshot with the error I'm getting:

Can anyone help me with this please?
Thank you and have a good day!

I assume you are doing the import wrong. But from this little information I cannot do much for you. I would console.log the imported variable to see what it actually is. At the moment it looks like createJWKSMock is an object, not a function, maybe the function is under the key default in the function? This seems to be an issue with module interoperability rather than this package. If you need further help, please create a demo repo in github with a minimal example to reproduce your issue. Until then I will close as wontfix.

Hi again @Levino ! Your comment helped me solve the problem. This is how I imported the package in the project: import createJWKSMock from 'mock-jwks'. You were right, createJWKSMock is an object and I had to use the default key in order to get the function (createJWKSMock(url) -> createJWKSMock.default(url)). Thank you for the package. It is very useful.
All the best and have a nice day/evening!