Make CodeGenerator aware of CodegenTraits

The code generator produces some IR that is prone to changes for architectural differences. An example problem is CodeGenerator::codegenHoistedConstantsLoads bit casting a buffer of literals that has a different address space in L0 path case.

Fixed by #219


NavigationView appears blurry temporarily at 125% scaling for WPF XAML Islands

Describe the bug

If the system is set to 125% scaling a NavigationView initially appears blurry and after a short duration (less than a second) renders normally for WPF Xaml Island projects. The bug can be reproduced on PowerToys.  https://github.com/microsoft/PowerToys/issues/6592 is the tracking issue on our repo.
Steps to reproduce the bug

WPF Xaml Islands project with NavigationView of the form:
        <winui:NavigationView
        x:Name="navigationView"
        IsBackButtonVisible="Collapsed"
        IsBackEnabled="{x:Bind ViewModel.IsBackEnabled, Mode=OneWay}"
        SelectedItem="{x:Bind ViewModel.Selected, Mode=OneWay}"
        IsSettingsVisible="False"
        OpenPaneLength="296"
        CompactModeThresholdWidth="0"
        Background="{ThemeResource SystemControlBackgroundAltHighBrush}">

Steps to reproduce the behavior:

Launch the UI (For PowerToys, start PowerToys and click PowerToys from the sys tray to launch the Settings app (WPF Xaml Island with NavView)

Expected behavior

NavigationView should render normally.
Screenshots

On launch:

After a short duration:

Version Info

NuGet package version:

Microsoft.UI.Xaml 2.5.0-prerelease.200923002

Windows app type:

UWP
Win32

Yes

Xaml Island on WPF

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

May 2020 Update (19041)
Yes

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context

Source for the page with NavigationView https://github.com/microsoft/PowerToys/blob/master/src/core/Microsoft.PowerToys.Settings.UI/Views/ShellPage.xaml

any updates here?

Is this still an issue?

We're not planning on taking a fix for this on WinUI2. Closing this bug. Note that there is an issue tracking blurry text in WinUI3 here - https://github.com/microsoft/microsoft-ui-xaml/issues/2278
If you have a similar repro in WinUI3, please reactivate.


landscape button produce Null check operator error

After click on Freeform click on landscape button makes error "Null check operator used on a null value" happens
(from aspectRatioOriginal! image_editor_plus/image_editor_plus.dart:1180:60)

fixed in v0.2.2


AzurePipelinesCredential doc updates

Summary of changes

Switching to an aka.ms link, as the service team may be changing the target doc
Drive traffic from AzurePipelinesCredential API ref page to usage instructions

API change check
API changes are not detected in this pull request.


Multi token support

Same as #28, but opening PR with branch on origin for testing with token.

[ ] I have updated the CHANGELOG file according to the conventions in keepachangelog.com
[ ] This PR contains changes that do not require a mention in the CHANGELOG file

@kyrcha added also you to have a look at the test here.

@smacker @kyrcha fixed both issues, already squashed as they were little changes. I'm merging once CI is done.


Cloud Regime Error Metric (CREM, recipe_williams09climdyn_CREM.yml)

There are still some codacy issues that I could not fix. @bouweandela could you please take a look?

I simplified the code a little bit as suggested by @bouweandela but I am hesitant to apply more simplifications as this would basically require a recoding of the whole diagnostic. In general, I think that the rules checked by codacy are too strict for scientific code. For example, I do not think that every function must have less than 50 lines, less than 5 arguments and less than 15 local variables. Most scientific code is not written like this and would basically require rewriting everything. I don't think this would be helpful now as we are trying to release v2.0 with as many diagnostics from v1.1.0 as possible as soon as possible. No time for perfectionism now in my opinion, that would be something for later.

We had this discussion some time ago and I was expecting this kind of problem showing up sooner or later.
I think @axel-lauer has a point: as the tool is growing and we acquire more and more diagnostics, it will be hard to support code rewriting and cleaning. We cannot expect scientists to provide perfectly written code and we do not have the resources to do the cleaning ourselves, at least not beyond some basic cleaning.
We have to be pragmatic and accept that some diagnostic code will not fully adhere to our standards.

@axel-lauer @mattiarighi I fully understand that it can be too time consuming to rewrite all legacy diagnostic code, so there can be situations where we need to merge PRs that break the standards.
However, I think that setting a good standard is a good idea, because it will:

Encourage people to write better code when they're doing new development work.
Make it visible on Codacy what diagnostic code is likely to be buggy because it is written in a way that makes it very difficult to read the code.

@axel-lauer Please note that these standards have been developed by a large community of very experienced software engineers from every field. These standards may seem pedantic at first, but years of experience and discussion have shown that this are conventions that work best for most people. Indeed, rewriting old code to adhere to new standards can be be a very time consuming task, that you do not have the time for. However, writing new code that adheres to these standards is probably less work than writing new code that doesn't, especially when taking longer term maintainance into account. Of course that means you need to invest about 1 hour or so to read PEP8 and use either the prospector or the pylint tool to remind you during development, but I think that should be doable and will actually help you with your development (I find that it regularly catches bugs in code I write myself).

Both @bouweandela and @axel-lauer have good arguments here, but we need to find a compromise solution to move things forward.
My proposal is the following:

for the preprocessor and other core routines of the tool, we continue to strictly conform to the Codacy standards
for new diagnostic code contributed by the users, we ask the users to conform to the Codacy standard and help them adapting their code (as it happened for example with the first set of ocean diagnostics contributed by @ledm). This will maybe annoy or demotivate some users, but I'm confident that most of them will recognize the importance of well-written ocde in the long term
for existing diagnostic code (ported from v1) or external packages, we need to be pragmatic and accept the fact that it does not comply to the standards. This is especially true for external packages (like the CVDP package), which need to be implemented as they are. We could open an issue with a list of to-be-improved diagnostics to keep track of them and try to address them in the long term.

@axel-lauer please merge this.
I will then open an issue with the list of to-be-improved routines, as mentioned above.


'GitHub.copilot' CANNOT use API proposal: terminalDataWriteEvent.

Azure Data Studio Version: Insiders
OS Version: Windows 11

Console error captured on startup:
Error: Extension 'GitHub.copilot' CANNOT use API proposal: terminalDataWriteEvent.
Its package.json#enabledApiProposals-property declares: inlineCompletionsAdditions but NOT terminalDataWriteEvent.
 The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api GitHub.copilot

Ohk, didn't realize there's similar open issue.. I'll close it as duplicate then. Thanks!

@Charles-Gagnon, yeah, it's because of that. The extension needs to be pushed up to the gallery.

Even after the extension is pushed up to the gallery we may still see this. I noticed it in VS Code, and Karl's recommendation was to copy over the proposed API's as they appear in the product json for VS Code release 1.79.2.

@lewis-sanchez Please verify whether this is an issue that needs to be fixed for July, or whether this is expected behavior

@cheenamalhotra and @Charles-Gagnon, I'm seeing the same error in VS Code 1.79.2, which is the same VS Code version powering Azure Data Studio after our most recent merge.

Sounds good, thanks. I'd still probably let Jordan know to make sure there aren't any issues they're aware of, but we can probably close this as completed for now then.

@lewis-sanchez can you please move this issue out of the July milestone or close it if this is expected behavior for the July release?

im using arch linux with vscode insiders and i was able to solve this issue by downloading an AUR package called code-features-insiders
yay -S code-features-insiders


New opsim baseline

The OpSim team have come up with a new baseline.  We were using enigma_1189, but the new baseline is kraken_1042.  Should we change?
Apparently, enigma_1189 was never actually a baseline and the kraken_1042 is.  Technically we should probably change, but I know enigma_1189 works and I'm slightly worried about breaking things.
enigma_1189
Page listing kraken_1042

I vote for changing.  We haven't yet produced any simulated images that would be considered "production" so we might as well use an actual baseline.  Also, if switching to kraken_1042 breaks anything, then we have definitely done something wrong and should fix it.

I vote for changing.
I am aware that I am voting for spending other people's time...
Are we at the point where testing if kraken_1042 works is a low investment of human dev time?

It should be very low investment.  The only reason I mentioned any breakage is that in a conversation in the hall, Scott Daniel mentioned that the schema may have changed in the newest baseline databases.  That would prompt a change in CatSim.  I'll check with him to see what the status is.

I vote for change too: it's important to be able to adapt to things like
this, so we might as well get into the habit early. BTW Lynne Jones seems
to think that minion_1016 is the run to use now, not kraken_1042.
What's the difference?

@drphilmarshall they are two realizations of the current baseline cadence.  They were produced on different machines with the same input parameters (but are different because of know non-deterministic behavior in phosim).  The "official" baseline is kraken_1042 according to the web page linked in the issue.
As a side note, the schema did change.  This requires an update to the CatSim code.  I have a in to them about how hard this is to fix.

Where is are these runs documented?  We should take the opportunity to use Twinkles to lay out a clear provenance chain as well.

Wait, why are the outputs of opSim runs dependent on phoSim behavior?  I think I must not understand all of the things OpSim is doing.

Wait, why are the outputs of opSim runs dependent on phoSim behavior? I think I must not understand all of the things OpSim is doing.

Sorry, I miss typed.  I meant non-deterministic behavior in OpSim.

Where is are these runs documented? We should take the opportunity to use Twinkles to lay out a clear provenance chain as well.

These are documented at the link in the issue: https://confluence.lsstcorp.org/display/SIM/Operations+Simulator+Benchmark+Surveys
Unfortunately, the documentation for the previous set of baseline runs was overwritten to make this page, so you need to use the history button to look at those.  For the record, I think that's a bad idea since people will always be using the N-1 version of the baseline because that's what they started their analysis with.

I think we setlled on kraken_1042! Closing.


markdown.js: Fix inconsistent user mention on new line.

The user mention regex was checking for multiple lines,
so it broke when the user mention was on a new line.
This changes the regex AND adds a couple tests to
test inline markdown regexes.
(I will close the independent issues when this gets merged.)

Nice find debugging this!  I posted one comment on a related issue we should also fix :)

@timabbott I think you should just merge this when tests pass. stream is still buggy even taking out the m, so it's going to take some debugging. (I'm almost 100% sure it has to do with marked.js thinking # is a header and splits it as a paragraph.)

OK, sounds good.  The test failures are 5488ab4225e8ed1b7f53d702d8789d7bf5894330, so merged, thanks @lonerz!


[feat] Enable Priority Route functionality

Is your feature request related to a problem? Please describe.
Heal Network doesn't make the nodes take the shortest route they actually can, in fact I've tried several and they have set very inefficient routes (my controller is positioned such that nothing more than 2 hops should be necessary with my current setup except for one node, yet it refuses to update node connections to reflect this).
Describe the solution you'd like
The ability to set Application Priority Routes to effectively minimize the number of hops.
Describe alternatives you've considered
Currently there are no alternatives
Additional context
https://i.imgur.com/mKcKaZi.png
This is my current network map. However, from north to south, the order of node placement is actually
Front Door Light/Mailbox Door -> R Bedroom Light -> Kitchen Extender -> Scene Controller -> Controller -> Garden Extender -> Quail Light Dimmer. This was after I moved the controller from my room to a central location and healed the network twice. Garden Extender should be connected directly to the Controller and the Mailbox Door should be connected to the Front Door Light. This network map doesn't make any sense.

First things first: I'm not against implementing that functionality.

This network map doesn't make any sense.

Just to be clear: This map only indicates neighbors, not which routes will be taken.
I'm not yet sure why but I've seen tons of examples where neighbors are also missing from that map, so don't put too much weight into it. Maybe the routes haven't settled yet - there's a ton of magic happening we don't have influence over. Unless you have actual connectivity issues and/or have verified the incorrect routes with a Zniffer, I'd avoid premature optimization.
I do have a theory you could help me test: Which stick are you using? Which firmware (should be visible in the driver log on startup, "serial API version")?

https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/generating-logs?id=driver-logs - make sure to set the loglevel to debug

Yep, 7.15 seems correct. Did you include all devices on that version or did you do any firmware updates meanwhile?
Silabs seem to have fixed something very recently in 7.16, which could explain weird neighbor information, but I'm still trying to get a bigger picture.

Yeah, the stick was brand new like 2 weeks ago, so everything has been added since then.

Ok that could support my theory:
Firmware 7.16 fixes a bug where inclusion is done with a too high TX power. Normally the power is reduced, so nodes at the brink of connectivity don't include on direct range if they can't communicate reliably and are instead forced to mesh. Now if they were barely included but later don't see their neighbors, this could explain the weird neighbor situation you're having.
That doesn't help you though 😅


Explore whether using pointers to const data as arg to CUDA kernels improves performance

Currently, CUDA kernels get passed const structs like LuDecomposeParam which include pointers to arrays of indices. However, the array element types are not const. Explore whether creating something like a ConstLuDecomposeParam struct that has data member pointers to const data, and then having this type be used as the argument to CUDA kernels (with appropriate assignment operator overloads) will result in better pre-fetching of data in memory during the execution of the kernel.
Possible definition of new struct:
struct ConstLuDecomposeParam
{
  const std::pair<const std::size_t, const std::size_t>* niLU_;
  const char* const do_aik_;
  const std::size_t* const aik_;
  const std::pair<const std::size_t, const std::size_t>* uik_nkj_;
  const std::pair<const std::size_t, const std::size_t>* lij_ujk_;
  const char* do_aki_;
  const std::size_t* aki_;
  const std::pair<const std::size_t, const std::size_t>* lki_nkj_;
  const std::pair<const std::size_t, const std::size_t>* lkj_uji_;
  const std::size_t* uii_;
  std::size_t niLU_size_;
  std::size_t do_aik_size_;
  std::size_t aik_size_;
  std::size_t uik_nkj_size_;
  std::size_t lij_ujk_size_;
  std::size_t do_aki_size_;
  std::size_t aki_size_;
  std::size_t lki_nkj_size_;
  std::size_t lkj_uji_size_;
  std::size_t uii_size_;

  ConstLuDecomposeParam(const LuDecomposeParam& other) :
    niLU_(other.niLU_),
    ...
    {}
};

or we can change the existing LuDecomposeParam struct with the new one above (without the initializer) and see if it works too.

I and Matt tested it quickly on Derecho's A100 GPU. No significant difference is observed for the GPU performance.

@mattldawson My bad! After adding the const qualifier to all the CUDA kernels, the time of unit tests for CUDA is significantly faster. Thus I think it is helpful to add it here.


Create two section for widget events and property changed events

Problem description
With Widgets/NativeObjects it is sometimes not easy to see what specific events are available on an object in the docs side bar. The mix of specific and "property changed" events creates a cluttered list

Expected behavior
Create two section for Events and Property events or Property changed events.
Environment

Tabris.js version: 2.5

The docs now show more structures events.


Threat: Ability to deference and access uninitialized pointers

Due to the lack of flow state analysis the compiler currently does not check the initialisation state of a variable before it interacts with it. Hence you can dereference and attempt to read the value of an uninitialized pointer which results in a segfault due to out of bounds memory access

This will be fixed later once flow state analysis is implemented


Need to be able to handle dev and prod seperation at top level

We add tasks / modify existing tasks such that we can choose between building for development or production.
Currently, the build task does not package both the client and server sides of the project together, which it should for production.
The only real difference between dev and prod here is that, during development, the server listens on port 4567 (rather than port 80) and redirects the / route to localhost:9000 (the client side dev. server).  Database configuration should also be generalized, but that might not be necessary immediately.
Alternatively: The build can always be a "production" build, but we can have different means of starting the server. (command line flags such as "start --prod" or "start --dev")

After today's meeting, I think the plan is as follows:

We will use environment variables to specify what the build environment is, e.g., ENVIRONMENT=production
We will then have a config directory in the project that will have things like production.properties in it.
If the environment specified in ENVIRONMENT doesn't have a corresponding file in config, we'll use default.properties.
We'll provide a default.properties and a development.properties files, _and then have everything else in that directory in .gitignore so people don't inadvertently commit things with authentication tokens.

Does this sound right, @devshawn and @joethe and @kklamberty ?

The "big picture" idea made sense at the meeting yesterday, but when I got into it I realize that I'm a bit fuzzy on some of the important details. I'm also rusty on gradle, so I'm going to try to outline what I think is going on here so people can yell at me when I get something wrong. (Looking at you, @joethe and @devshawn 😛 )
My immediate question is what needs to be specified in the config/properties files? Some things I can think of:

Where the DB is (hostname and port)
DB credentials as needed
Location of all the (generated) static web files (HTML, CSS, JS)

What happens here in DEV mode? The Spark server doesn't serve this content there, right, so it just shouldn't do anything about that in DEV mode?

I feel like there is/should be more, but I'm not sure what it is.


Cleanup - squid:S1312 - Loggers should be "private static final" and …

This pull request is focused on resolving occurrences of Sonar rule squid:S1312 - Loggers should be "private static final" and should share a naming convention
You can find more information about the issue here: https://dev.eclipse.org/sonar/coding_rules#q=squid:S1312
Please let me know if you have any questions.
M-Ezzat

Thanks, but I prefer log to LOGGER. I agree with the static though.


Hotfix/package versions

Objective
What: Upgrade packages to avoid conflicts and security alerts
Why: As above
How: yarn upgrade --latest
Usage: As normal
Type
NA
Tested
Localhost
Documented
NA

👏


sharp-cxx11 flag doesn't get picked up from npm command line

I'm trying to build sharp for use with a package manager installed vips library. When I build it as described in the docs (install.md) with npm install --sharp-cxx=1 the resulting binary sharp.node is not built with the CXX11 ABI. However, if I change line 54 of binding.gyp to read 'sharp-cxx11%': '1',, I get a CXX11 ABI binary, as expected. I'm not too familiar with gyp files -- any idea why this might not be getting connected?

It looks like the dash in the variable name prevents it getting passed from npm to node-gyp, at least on . Changing it to sharp_cxx11 works as expected.
https://github.com/npm/npm/blob/master/node_modules/node-gyp/lib/configure.js#L147
@kapouer Any problem if we change this to use a underscore instead?

Oh, that explains everything :+1:

Commit 7689fbe is your friend. Thanks for reporting this Matt.

Thanks for the quick fix!

Commit https://github.com/lovell/sharp/commit/07d66da57b7829fca938d7e3c5c4b47a981b1d17 should fully automate this, and therefore removes the sharp-cxx11 flag.


bpf, nodeport: fix CT GC race where syn/ack reply gets dropped locally

While testing BPF nodeport with local backend under stress, I've noticed that
once in every several thousand cases the SYN/ACK is 'stuck' and not being pushed
back to the remote node.
'Odd' case seen:
[...]
<- stack flow 0x65f91604 identity 0->0 state new ifindex eno1 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:58490 -> <IP_ADDRESS>:30000 tcp SYN
<- host flow 0x65f91604 identity 2->0 state new ifindex eno1 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:58490 -> <IP_ADDRESS>:80 tcp SYN
-> endpoint 893 flow 0x65f91604 identity 2->16777217 state established ifindex lxc962bf03db31a orig-ip <IP_ADDRESS>: <IP_ADDRESS>:58490 -> <IP_ADDRESS>:80 tcp SYN
<- endpoint 893 flow 0xed432cf identity 16777217->0 state new ifindex 0 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:80 -> <IP_ADDRESS>:58490 tcp SYN, ACK
-> stack flow 0xed432cf identity 16777217->2 state reply ifindex 0 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:80 -> <IP_ADDRESS>:58490 tcp SYN, ACK  <---- BUGGY
[...]
'Regular' case:
[...]
<- stack flow 0xe5afda01 identity 0->0 state new ifindex eno1 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:58470 -> <IP_ADDRESS>:30000 tcp SYN
<- host flow 0xe5afda01 identity 2->0 state new ifindex eno1 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:58470 -> <IP_ADDRESS>:80 tcp SYN
-> endpoint 893 flow 0xe5afda01 identity 2->16777217 state established ifindex lxc962bf03db31a orig-ip <IP_ADDRESS>: <IP_ADDRESS>:58470 -> <IP_ADDRESS>:80 tcp SYN
<- endpoint 893 flow 0xdb0f605a identity 16777217->0 state new ifindex 0 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:80 -> <IP_ADDRESS>:58470 tcp SYN, ACK
<- stack flow 0xe5afda01 identity 0->0 state new ifindex eno1 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:58470 -> <IP_ADDRESS>:30000 tcp ACK  <---- OK
<- stack flow 0xe5afda01 identity 0->0 state new ifindex eno1 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:58470 -> <IP_ADDRESS>:30000 tcp ACK
<- host flow 0xe5afda01 identity 2->0 state new ifindex eno1 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:58470 -> <IP_ADDRESS>:80 tcp ACK
[...]
In the 'odd' case, the SYN/ACK is wrongly being pushed back into the local
stack where it is later dropped:
[...]
0.63%     0.63%  skbaddr=0xffff92ded3c8b700 protocol=2048 location=0xffffffff90c7915b
|
---ret_from_fork
kthread
smpboot_thread_fn
run_ksoftirqd
__do_softirq
net_rx_action
process_backlog
__netif_receive_skb
__netif_receive_skb_one_core
ip_rcv
ip_rcv_finish
ip_local_deliver
ip_local_deliver_finish
ip_protocol_deliver_rcu
tcp_v4_rcv
kfree_skb
kfree_skb
[...]
After further debugging, turns out that we have a CT GC race, meaning, for
the local backend case we always create 2 separate CT entries in nodeport_lb*(),
the second one is for the purpose of reverse NAT for replies. The race turns
out to be triggered when the GC runs in parallel and evicts the second CT
entry before it hits the CT lookup in ipv4_policy(). Latter will then return
CT_NEW and creates a new entry but without the nodeport status bit set. This
causes to miss the CILIUM_CALL_IPV*_NODEPORT_REVNAT tail call in handle_ipv4_from_lxc()
and results in mentioned push-to-stack behavior. Now, if the first entry would
have been evicted by the GC first, then this would not have been an issue since
we'd have recreated the second entry once again.
As a fix, bump the lifetime of the second entry upon lookup of the first to
keep it alive, or, if already evicted by the GC, recreate the second entry before
it's being pushed into the pod.
Fixes: #9663
Signed-off-by: Daniel Borkmann<EMAIL_ADDRESS>

This change is

test-me-please

Coverage increased (+0.005%) to 46.07% when pulling 9271db078fcdc92ec856b3fa3337f1b7e982d857 on pr/bpf-nodeport-fix into f694b3ba28ac2936c413fddec7771ef14a2c8808 on master.

test-me-please


[vcpkg baseline][vcpkg_configure_make] Fix arm64-windows

Describe the pull request
Since https://github.com/microsoft/vcpkg/commit/af3c99bc65d46e77900ae4e826866f134dc903ae various ports have been failing on arm64-windows.
Investigation yielded the cause: objdump is failing to deal with arm64 arch libraries:
usr/bin/objdump: installed\arm64-windows\lib\iconv.lib(iconv-2.dll): unrecognised machine type (0xaa64) in Import Library Format archive

@Neumann-A Suggested that the best option, for now, is to add a workaround with a comment (reverting af3c99bc65d46e77900ae4e826866f134dc903ae would have its own issues) - so that's what this PR does.

What does your PR fix? Fixes #15737

Which triplets are supported/not supported? Have you updated the CI baseline?

arm64 Windows triplet(s) are impacted.

Does your PR follow the maintainer guide?

cc @Neumann-A

cc @Neumann-A

Seems this PR doesn't fix the arm regression:
/cygdrive/c/a/1/s/scripts/buildsystems/make_wrapper/windres-rc: line 62: RCFLAGS: command not found

Seems this PR doesn't fix the arm regression:
/cygdrive/c/a/1/s/scripts/buildsystems/make_wrapper/windres-rc: line 62: RCFLAGS: command not found

Seems this PR doesn't fix the arm regression

Correct - it just fixes the arm64-windows regression. (I have not had a chance to investigate the arm-uwp triplet.)

Seems this PR doesn't fix the arm regression

Correct - it just fixes the arm64-windows regression. (I have not had a chance to investigate the arm-uwp triplet.)

@Neumann-A What do you think about the arm regression?

@Neumann-A What do you think about the arm regression?

The arm regression appears to be the same, but there is information that isn't contained in the logs (the exact output of running objdump on arm libraries) that I'd like to verify before implementing the same change for arm as well. I may have a chance to test this tomorrow.

The arm regression appears to be the same, but there is information that isn't contained in the logs (the exact output of running objdump on arm libraries) that I'd like to verify before implementing the same change for arm as well. I may have a chance to test this tomorrow.

@JackBoosY Everything fine. This was discussed in the vcpkg discord.

@JackBoosY Everything fine. This was discussed in the vcpkg discord.

spatialite-tools regression will be resolved in #15746 or other PR, I hope this PR can solve arm and arm64 regression issues.

spatialite-tools regression will be resolved in #15746 or other PR, I hope this PR can solve arm and arm64 regression issues.

I can confirm on arm-uwp that objdump yields a similar issue:
vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll): unrecognised machine type (0x1c4) in Import Library Format archive

(same error message with a different machine type)
@JackBoosY: I've implemented the same fix for arm on Windows.

I can confirm on arm-uwp that objdump yields a similar issue:
vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll): unrecognised machine type (0x1c4) in Import Library Format archive

(same error message with a different machine type)
@JackBoosY: I've implemented the same fix for arm on Windows.

@past-due Do you have by any chance llvm-objdump installed? Would like to know if it has the same problems.

@past-due Do you have by any chance llvm-objdump installed? Would like to know if it has the same problems.

@past-due Do you have by any chance llvm-objdump installed? Would like to know if it has the same problems.

Just installed it (through Visual Studio's LLVM / Clang package).
Results for arm .lib

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>llvm-objdump -f C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-ARM

architecture: thumb
start address: 0x00000000

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-ARM

architecture: thumb
start address: 0x00000000

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-ARM

architecture: thumb
start address: 0x00000000

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

Results for arm64 .lib:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>llvm-objdump -f C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-ARM64

architecture: aarch64
start address: 0x0000000000000000

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-ARM64

architecture: aarch64
start address: 0x0000000000000000

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-ARM64

architecture: aarch64
start address: 0x0000000000000000

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

Also tested DUMPBIN.EXE:
Results for arm .lib:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>dumpbin.exe /NOLOGO /HEADERS C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib

Dump of file C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib

File Type: LIBRARY

FILE HEADER VALUES
             1C4 machine (ARM)
               3 number of sections
        CAC54605 time date stamp
             10B file pointer to symbol table
               8 number of symbols
               0 size of optional header
             100 characteristics
                   32 bit word machine

SECTION HEADER #1
[... removed many, many lines ...]

Results for arm64 .lib:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>dumpbin.exe /NOLOGO /HEADERS C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib

Dump of file C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib

File Type: LIBRARY

FILE HEADER VALUES
            AA64 machine (ARM64)
               3 number of sections
        C5E1F4A1 time date stamp
             10B file pointer to symbol table
               8 number of symbols
               0 size of optional header
               0 characteristics

SECTION HEADER #1
[... removed many, many lines ...]

@past-due Do you have by any chance llvm-objdump installed? Would like to know if it has the same problems.

Just installed it (through Visual Studio's LLVM / Clang package).
Results for arm .lib

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>llvm-objdump -f C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-ARM

architecture: thumb
start address: 0x00000000

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-ARM

architecture: thumb
start address: 0x00000000

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-ARM

architecture: thumb
start address: 0x00000000

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib(iconv-2.dll):        file format COFF-import-file

Results for arm64 .lib:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>llvm-objdump -f C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-ARM64

architecture: aarch64
start address: 0x0000000000000000

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-ARM64

architecture: aarch64
start address: 0x0000000000000000

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-ARM64

architecture: aarch64
start address: 0x0000000000000000

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib(iconv-2.dll):  file format COFF-import-file

Also tested DUMPBIN.EXE:
Results for arm .lib:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>dumpbin.exe /NOLOGO /HEADERS C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib

Dump of file C:\Users\pastdue\src\vcpkg\installed\arm-uwp\lib\iconv.lib

File Type: LIBRARY

FILE HEADER VALUES
             1C4 machine (ARM)
               3 number of sections
        CAC54605 time date stamp
             10B file pointer to symbol table
               8 number of symbols
               0 size of optional header
             100 characteristics
                   32 bit word machine

SECTION HEADER #1
[... removed many, many lines ...]

Results for arm64 .lib:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>dumpbin.exe /NOLOGO /HEADERS C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib

Dump of file C:\Users\pastdue\src\vcpkg\installed\arm64-windows\lib\iconv.lib

File Type: LIBRARY

FILE HEADER VALUES
            AA64 machine (ARM64)
               3 number of sections
        C5E1F4A1 time date stamp
             10B file pointer to symbol table
               8 number of symbols
               0 size of optional header
               0 characteristics

SECTION HEADER #1
[... removed many, many lines ...]

LGTM.

LGTM.

Thanks for the discussions and fix!

Thanks for the discussions and fix!


Should we define which countries are eligible to become a “country” on Govdirectory?

Description
The reason for this question is: The focus country for week 32 is Bermuda. But technically it is not a country at all (or at least not a sovereign country) it is a British Overseas Territory.
I realize that the concept of whether or not it is a country is a sensitive subject. There are plenty of examples of countries not recognizing a country.
Hence defining a country.
related issue: #368

That's a good question, and not with an easy, obvious answer. At least the overarching question, about what should be seen on the top level.  There is something about the practicality, and helping the people find their government, that is important here, as it is the purpose for Govdirectory. For example, I think that most people in Taiwan would not expect to find the Taiwanese agencies under China. So I think we should have some sort of de facto approach rather than a de jure approach. If there is a functioning and organized state with bodies, that should be reflected on Govdirectory.
With that said, for Bermuda, I am still unsure. It is possible that we perhaps just should acknowledge it is an error and that we should put it under the UK, but it is also one of the participants in the Olympics, and perhaps they wouldn't expect to go to gov.uk to find info about their agencies.

We could say only the countries that are sovereign (https://w.wiki/AuJZ) or member states of the UN .

With that said, for Bermuda, I am still unsure. It is possible that we perhaps just should acknowledge it is an error and that we should put it under the UK, but it is also one of the participants in the Olympics, and perhaps they wouldn't expect to go to gov.uk to find info about their agencies.

Well, countries don't participate in the Olympic Games, but National Olympic Committees do. 😉
We will never find a solution that is good for everyone. Or we have to change the content based on geolocation/politics (like Google Maps does). But that is a whole different ball game.


[docs][gym] Add info on passing plist into export_options on gym

Checklist

[X] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[X] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[X] I've read the Contribution Guidelines
[X] I've updated the documentation if necessary.

Motivation and Context
Fixes #16327
Description
There's this small part in the source code of build_app:
if Actions.lane_context[SharedValues::MATCH_PROVISIONING_PROFILE_MAPPING]
          # Since Xcode 9 you need to explicitly provide the provisioning profile per app target
          # If the user is smart and uses match and gym together with fastlane, we can do all
          # the heavy lifting for them
          values[:export_options] ||= {}
          # It's not always a hash, because the user might have passed a string path to a ready plist file
          # If that's the case, we won't set the provisioning profiles
          # see https://github.com/fastlane/fastlane/issues/9490
          if values[:export_options].kind_of?(Hash)

Well, using a plist correctly overrides the options match passes, but this should be more apparent in documentation. For example, in https://docs.fastlane.tools/actions/gym/ there's the sentence:

Note: If you use fastlane with match you don't need to provide those values manually.

This should be changed to:

Note: If you use fastlane with match you don't need to provide those values manually, unless you pass a plist file into export_options

@googlebot I signed it!


ComplexMethod should ignore mappers, long when statements

Expected Behavior of the rule
As the name implies I would expect this check to look into the number of arguments, and the operations performed within the method.
Context
In a case of a simple mapper, or a longer when statement within a function/extension function with 1 or 2 arguments I wouldn't expect this rule to fire as the complexity is linear.

Thanks for providing feedback!
The ComplexMethod rule by default uses the MCCabe metric to determine, whether a method is complex or not.
Do you have a reference that your code shall be ignored by the MCCabe metric?
May I ask you a few more questions in order to further help you on this matter?
Can you please provide a code snippet for the mentioned case? Which configuration do you use for the ComplexMethod rule?

Thx for answering so fast.
Yeah sure I. can give an example that is not super confidential. So we want to map some values from the backend API to some DB values, and for this we have a when statement that looks like this(data has been renamed on purpose):
internal fun ApiValue.toDBValue() = when (this) {
    is FooValue -> DBValue(ENABLED.name, timeStamp, boolValue = isEnabled)
    is BlaValue -> DBValue(KILOMETERS.name, timeStamp, intValue = kilometers)
    is SooValue -> DBValue(PERCENT.name, timeStamp, intValue = percent)
    is AhaValue -> DBValue(MINUTES.name, timeStamp, intValue = minutes)
    is MoreValue -> DBValue(DAYS.name, timeStamp, intValue = days)
    from here 7 more mappings
}

Thanks for providing the code snippet?
Which rule configuration (yaml) do you have in use. There are options covering exactly this case. Those options are called ** ignoreSingleWhenExpression** and ** ignoreSimpleWhenEntries**.

Thanks for providing the code snippet.
Which rule configuration (yaml) do you have in use that flags this code?
Anyways, there exist options covering exactly this case. Those options are called ignoreSingleWhenExpression and ignoreSimpleWhenEntries.

I use the generated rule set with slight modifications.
Awesome, didn't know this existed. Will try it out , thx.

Glad that I could help!


Improve Book Appointment 0

Need to improve this component on Book appointment component/src/book-appointment-0.html
Improvements required :

As discussed need to remove Pink Border
Use SeamLess UI Form components instead of the ones used.
Make It responsive for Mobile Screens.

Any reference image?

You can checkout this one for better understanding.
Use these components to improve it

@Rajdip019 Please assign this to me

Done #745


Pkcs12 support

Adds support for generating JWK for client based on pkcs12 files

There was no need for that code to remain so I removed it.


Example Usage

Per the review criteria:

Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).

As is right now, the documentation is really focused on the base layer and the ability to define a new measure, but the documentation is missing a more extensive (practical) use-case. In the "Why" of the package its necessity in "Bayesian modeling" is pointed out, such example could really enhance the documentation, and make the package much more accessible to new users.

Ok to close this @ludgerpaehler ?

Sure!


feat(test): introduce a base class for all TransferProcessStore

What this PR changes/adds
Add a common base test class for TransferProcessStore which all implementors should extends
Why it does that
To provide a "least common denominator" for tests, i.e. a minimum subset of test scenarios for each TransferProcessStore.
Further notes
A fix has been added to BaseSqlDialectStatements fo transferprocess  store.
In the method  getProcessIdForTransferIdTemplate()  the filtered column has been changed from getProcessIdColumn to getDataRequestIdColumn which seems to be the same as InMemory and Cosmos implementations
Linked Issue(s)
Closes #1942
Checklist

[x] added appropriate tests?
[x] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #1982 (3531cb5) into main (36d8452) will increase coverage by 0.04%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1982      +/-   ##
==========================================
+ Coverage   62.98%   63.02%   +0.04%
==========================================
  Files         784      784
  Lines       16671    16685      +14
  Branches     1085     1087       +2
==========================================
+ Hits        10500    10516      +16
+ Misses       5718     5716       -2
  Partials      453      453

Impacted Files
Coverage Δ

...nsfer/store/cosmos/CosmosTransferProcessStore.java
0.00% <0.00%> (ø)

...re/cosmos/CosmosTransferProcessStoreExtension.java
0.00% <0.00%> (ø)

...process/store/schema/BaseSqlDialectStatements.java
10.00% <0.00%> (ø)

...sferprocessstore/InMemoryTransferProcessStore.java
85.00% <0.00%> (-10.00%)
:arrow_down:

...ataplane/flow/DataPlaneTransferFlowController.java
90.90% <0.00%> (+0.43%)
:arrow_up:

...spaceconnector/core/security/azure/AzureVault.java
26.56% <0.00%> (+26.56%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[7.x] Escape attributes automatically in some situations

https://blog.laravel.com/security-laravel-712-released
https://github.com/laravel/framework/releases/tag/v7.1.2

@perifer @taylorotwell @GrahamCampbell is there any way to disable this sanitizing if I do want to pass in a class with a __toString() method, and have it available as a PHP object (not a string) inside my component?


GUI : Header menu automation

[ ] Verify   the functionality of the “Log out” button” at the first top header row of the   GUI. The OpenBMC GUI web page should be able to logout.

[ ] Verify the logo of the OpenBMC GUI web page at the top second   row.

[ ] Verify the displaying of system name and IP address at top   second row of the web page menu

[x] Click on “Server health” button at the top   second row of the GUI and execute all the TC’s   from 9.2.4 section “Test case variation matrix” table in this document

[x] Click on “Server power” button at the top second row of the GUI   and execute all the TC’s from 9.5.4 section “Test case variation matrix”   table in this document

[ ] Verify the text label “Data last refreshed” at the top second   row of the GUI

[ ] Verify the content of the text label “Data last refreshed” by   clicking on “Refresh” button at top second row of the GUI. It should display   latest last refreshed time, date, month and year in the format of “h:m:ss Mmm   dd yyyy”

Code In Review/Merged
https://github.com/openbmc/openbmc-test-automation/issues/1663

Code In review - https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/18685/


Move custom footer config to db

:tada: This issue has been resolved in version 0.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Attachments

Thank you for spending the time and effort to develop this project.
I would like to be able to create and access autotask ticket attachments using atws. Is this currently possible?
Trying to execute the following:
query = atws.Query('Attachment')
query.WHERE('id', query.GreaterThan, 0)
attachment = at.query(query).fetch_one()

gave the following error.
'Autotask API has returned an error.
Please process the response attribute in this exception to detirmine
 the extent of this failure.
 '[Unable to cast object of type 'autotask.web.services.API.Attachment' to type 'autotask.web.services.API.ExternalVbApiEntity'., '<queryxml
><entity>Attachment</entity><query><field>id<expression op="GreaterThan">0</expression></field></query></queryxml>']

I don't think Attachment is an entity type that they allow you to get.  That error message sure is an interesting disclosure from their webservice though.
AttachmentInfo is all we can query.
The API specifies other specific calls relating to Attachment API Calls.  The last thing they want to you to be able to do is download 500 attachments at a time.
I'm sorry it took me so long to get to this message but hope the above helps.  I'll be doing some attachment work this week, so I may get a chance to create an example for them in the docs.


Update timeout for .github/workflows/main.yml

This is an automated pull request to update default timeouts for all jobs in .github/workflows/main.yml that do not currently contain a default timeout property.
Please review these changes closely to ensure that all jobs have sufficient time to run. If a job needs more time, please add a timeout property to that job to override the organization default.
Additionally, please be attentive to unintended changes to the workflow YAML file, as the parser is not perfect.
Lastly, note that it is up to the reviewer to merge this pull request and delete the PR branch once they are satisfied with the changes.

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


fix(jobs): load data lazily

When loading data for the jobs table, do not load all data at once, but
only once the specific tab is being open.
This prevents the issue with getting time out on the API endpoint.
Signed-off-by: Matej Focko<EMAIL_ADDRESS>Fixes #186
Fixes PACKIT-2484

RELEASE NOTES BEGIN
RELEASE NOTES END

Let's hope this builds, cause they're, once again, ***** something by switching SSL2 to SSL3. And workaround I have found is definitely not working for me /o\

Seems to be working locally in podman :tada: merging

https://dashboard.stg.packit.dev/jobs seems faster now, thanks!

https://dashboard.stg.packit.dev/jobs seems faster now, thanks!

@jpopelka I'm still surprised that those 5 tables loading at the same time (in Jobs) got timed out and pipelines view does not have any issue (so far), even though it does »much more« work on the API side IMO

Nice! That's much faster!!


795 granular to works with in sets

Description
Granular to constraints were not being checked against inSet constraints. i.e. previously, granular to 1 and in Set [1.2] would generate 1.2. This PR changes this so that no contradicting data is generated.
Changes

Added isCorrectScale method to granularToRestrcitions to check the scale of a numeric value from a set is correct
Unignored cucumber scenarios relating to issues

Additional notes
Found new bug related to granular to, #824
Issue
Resolves #795
Resolves #677

Codecov Report

Merging #825 into master will decrease coverage by 0.03%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #825      +/-   ##
============================================
- Coverage     65.97%   65.94%   -0.04%
- Complexity     1710     1714       +4
============================================
  Files           281      281
  Lines          6008     6011       +3
  Branches        695      697       +2
============================================
  Hits           3964     3964
- Misses         1795     1796       +1
- Partials        249      251       +2

Impacted Files
Coverage Δ
Complexity Δ

...enerator/restrictions/GranularityRestrictions.java
73.68% <100%> (+3.09%)
9 <2> (+2)
:arrow_up:

...ator/fieldspecs/SetRestrictionsMergeOperation.java
97.14% <100%> (+0.08%)
31 <18> (+4)
:arrow_up:

.../com/scottlogic/deg/generator/utils/IsinUtils.java
83.33% <0%> (-3.71%)
25% <0%> (-1%)

...g/generator/restrictions/DataTypeRestrictions.java
62.85% <0%> (-2.86%)
13% <0%> (-1%)

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 5a9f58c...44ce05f. Read the comment docs.


Server and Client Code bundling

Short Description
The ability to be able to combine server-side and client-side federated modules.
Longer Description
Often when shipping a feature new versions of the Frontend and Backend need to be shipped. This could be done independently or together as one holistic feature. Given that microservices and micro-frontends are frequently used together it would make sense to have federated remotes for both the server side and Frontend to be shipped together.
Business Value
New functionality rollouts are less likely to cause downtime due to both the Frontend and the Backend being able to be federated and available simultaneously.

Moved to discussion instead of an issue #447


Translate #1079: Mention support for Bot API 7.5

Translations for #1079.
https://core.telegram.org/bots/api#june-18-2024

umm, @KnorpelSenf. After I merged the main branch, the English files disappeared.

umm, @KnorpelSenf. After merging the main branch, the English files disappeared.

That's because English was already merged much earlier so that the front page displays the right compatibility. The changes can still be viewed in #1079.

Also, is this pull request already transtalable?

IMO yes. @roj1512 has very limited time these days, that's why the label wasn't added yet.


Out of scope strategy documentation

Is the out of scope strategy documented somewhere? I seem to have read something about randomly generated utterances for the None class but it would be great to have some details.

Hi @elyase, you are right, it is not well documented at the moment.
The IntentClassifierDataAugmentationConfig is responsible for configuring how data is augmented before training the intent classifier. More specifically, it contains this attribute:
        noise_factor (int, optional): Defines the size of the noise to
            generate to train the implicit *None* intent, as a multiplier of
            the average size of the other intents. Default is 5.

We then generate None utterances, by randomly sampling words from text files such as this one. The words in these files have been samples based on their global frequency in the corresponding language. Hence, it approximates the words distribution for the language.
This solution is probably not the best one overall, but it has been good enough so far.
Generating utterances for the None intent is inherently tricky as it consists in modelling a very large and not well defined corpus: everything which does not correspond to one of the declared intents.
I'm currently working on improving the documentation, and will include this in it.
I hope this help.
Cheers

yes, that is very helpful. thanks!


behnaz / Signup crowdin

Changes:

...

Type of change

[ ] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

task done by another pr https://github.com/binary-com/deriv-com/pull/2846


Sharing images in iOS 12

Hi,
Have you guys managed to make this work for images in iOS 12 (text and url's are working at least inside the simulator)? It does work for me on lower iOS versions.
Thanks :)

None of the types (image, vidoe, url, text) works for me on simulator (12, 11 OS).  No error either.
Do you get any errors at loadItemForTypeIdentifier ?

Sorry for the late reply. It does not give me any errors too.
Hmm, have you tried checking the provisioning profiles?
PS: I'll get back to you on loadItemForTypeIdentifier.


Add HTML  tag to core components

What is the expected behaviour?
Add the HTML <code> tag, as specified here: https://www.w3schools.com/tags/tag_code.asp

Closed via #213


Instrument substream with metrics

As a nice benefit, wrapping the original Negotiated<yamux::Stream>
makes the API of libp2p-xtra more contained by not exposing details
about yamux.

I love this idea and how quickly you implemented it!

Thanks! I am quite stoked myself about what we can do with this data :)

Note to self: Include dialer/listener role in metric.

bors r+


Inconsistent behavior using PERCENTILE_CONT function

Been trying to write some tests using the bigquery-emulator and so far so good! Until we ran into some strange behavior. Please see the cases from using the bq cli tool, but the results are the same querying via the bigquery API:
Working cases:

The zetasqlite/GCP documentation PERCENTILE_CONT test case

Simple 0-100 test case

bq --api http://<IP_ADDRESS>:9050 query --project_id=bq-test "WITH cte AS
    (SELECT 0 as age UNION ALL SELECT 50 as age UNION ALL SELECT 100 as age)
SELECT
    PERCENTILE_CONT(age, 0) OVER() min,
    PERCENTILE_CONT(age, 0.01) OVER() percentile1,
    PERCENTILE_CONT(age, 0.5) OVER() median,
    PERCENTILE_CONT(age, 0.99) OVER() percentile99,
    PERCENTILE_CONT(age, 1) OVER() max,
FROM cte LIMIT 1"
+-----+-------------+--------+--------------+-----+
| min | percentile1 | median | percentile99 | max |
+-----+-------------+--------+--------------+-----+
|   0 |           1 |     50 |           99 | 100 |
+-----+-------------+--------+--------------+-----+

Broken cases:
- Given 20, 30, and 40
Expected:
+-----+-------------+--------+--------------+-----+
| min | percentile1 | median | percentile99 | max |
+-----+-------------+--------+--------------+-----+
|20.0 | 20.2        | 30.0   | 39.8         | 40.0|
+-----+-------------+--------+--------------+-----+

Actual
bq --api http://<IP_ADDRESS>:9050 query --project_id=bq-test "WITH cte AS
    (SELECT 20 as age UNION ALL SELECT 30 as age UNION ALL SELECT 40 as age)
SELECT
    PERCENTILE_CONT(age, 0) OVER() min,
    PERCENTILE_CONT(age, 0.01) OVER() percentile1,
    PERCENTILE_CONT(age, 0.5) OVER() median,
    PERCENTILE_CONT(age, 0.99) OVER() percentile99,
    PERCENTILE_CONT(age, 1) OVER() max,
FROM cte LIMIT 1"
+-----+-------------+--------+--------------+-----+
| min | percentile1 | median | percentile99 | max |
+-----+-------------+--------+--------------+-----+
|   0 |         0.2 |     10 |         19.8 |  20 |
+-----+-------------+--------+--------------+-----+

- Given 500, 50, and 100
Expected:
+-----+-------------+--------+--------------+-----+
| min | percentile1 | median | percentile99 | max |
+-----+-------------+--------+--------------+-----+
|50.0 | 51.0        | 100.0  | 492.0        |500.0|
+-----+-------------+--------+--------------+-----+

Actual:
bq --api http://<IP_ADDRESS>:9050 query --project_id=bq-test "WITH cte AS
    (SELECT 500 as age UNION ALL SELECT 50 as age UNION ALL SELECT 100 as age)
SELECT
    PERCENTILE_CONT(age, 0) OVER() min,
    PERCENTILE_CONT(age, 0.01) OVER() percentile1,
    PERCENTILE_CONT(age, 0.5) OVER() median,
    PERCENTILE_CONT(age, 0.99) OVER() percentile99,
    PERCENTILE_CONT(age, 1) OVER() max,
FROM cte LIMIT 1"
+-----+-------------+--------+--------------+-----+
| min | percentile1 | median | percentile99 | max |
+-----+-------------+--------+--------------+-----+
|   0 |         4.5 |    225 |        445.5 | 450 |
+-----+-------------+--------+--------------+-----+

It appears the percentiles are being calculated using the range (max - min) multiplied by the percentile.
And the working cases conveniently work because they have a min value of 0?

@heyweswu can this be closed? Did your PR fix the issue?


install mode for vEOS?

Hi users,
it seems it wouldn't hurt to implement installation step for vEOS, since it warns about ZTP being used when you log in (witnessed on 4.24)
❯ ssh admin@clab-veos-veos
Warning: Permanently added 'clab-veos-veos,<IP_ADDRESS>' (ECDSA) to the list of known hosts.
No startup-config was found.

The device is in Zero Touch Provisioning mode and is attempting to
download the startup-config from a remote system. The device will not
be fully functional until either a valid startup-config is downloaded
from a remote system or Zero Touch Provisioning is cancelled.

To cancel Zero Touch Provisioning, login as admin and type
'zerotouch cancel' at the CLI. Alternatively, to disable Zero Touch
Provisioning permanently, type 'zerotouch disable' at the CLI.
Note: The device will reload when these commands are issued.

There is a file that you can change on guest VM to disable ZTP from being started, that will be quicker than booting the vm and issuing the console command

I've solved it with guesfish command that runs as a pre-build step
https://github.com/hellt/vrnetlab/pull/33/commits/e5821c10a97cd63aab9727f5f693520abc75bbe0


Console Warning, Require cycle: src\navigation\index.tsx -> src\navigation\root-navigator.tsx -> src\screens\index.tsx -> src\screens\onboarding\index.tsx -> src\screens\onboarding\onboarding.tsx -> src\navigation\index.tsx

Summary:
Just pulled down the latest version: npx create-obytes-app@latest MyApp
Now when I run pnpm android I get the below error immediately:
Require cycle: src\navigation\index.tsx -> src\navigation\root-navigator.tsx -> src\screens\index.tsx -> src\screens\onboarding\index.tsx -> src\screens\onboarding\onboarding.tsx -> src\navigation\index.tsx
Steps to reproduce:
Running on Windows 10
npx create-obytes-app@latest MyApp
code .
pnpm android
Expected behavior:
Run the app without issues and warnings

Thank you, @theknr, for reporting this issue. The issue has been fixed. Please check the Fix PR if you would like to apply it to your project.


Expose fields of Termios struct

I have need of directly manipulating the fields within the Termios struct. Right now that's impossible because the Termios struct just hides the underlying libc::termios::termios struct. Given the existence of OutputFlags and friends it seems like adding a control_flags() getter and set_control_flags() setter were originally planned?

Should be resolved by #527.

This was fixed by e3529352 and part of the 0.9 release.


⚠ Bofrost.nl has degraded performance

In 951b1d2, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 873 ms

Resolved: Bofrost.nl performance has improved in 95b27ae after 6 minutes.


Fhempy Server not starting anymore

Hi, Since latest update fhempy server didn't start anymore.
fhempy_local: Can't connect to ws:<IP_ADDRESS>:15733: Operation now in progress
fhempy_local: Can't connect to ws:<IP_ADDRESS>:15733: <IP_ADDRESS>: Verbindungsaufbau abgelehnt (111)
BindingsIo (fhempy_local): ERROR during connection setup: <IP_ADDRESS>: Verbindungsaufbau abgelehnt (111)
Any idea how to fix?

i have the same problem.
please help

Please post content from the fhempy log file.

-- Logs begin at Wed 2023-05-24 21:21:54 CEST. --
Dez 15 22:19:56 srvfhem systemd[1]: Started fhempy.
Dez 15 22:19:56 srvfhem systemd[54348]: fhempy.service: Failed to determine user credentials: No such process
Dez 15 22:19:56 srvfhem systemd[54348]: fhempy.service: Failed at step USER spawning /home/pi/.fhempy/fhempy_venv/bin/fhempy: No such process
Dez 15 22:19:56 srvfhem systemd[1]: fhempy.service: Main process exited, code=exited, status=217/USER
Dez 15 22:19:56 srvfhem systemd[1]: fhempy.service: Failed with result 'exit-code'.
Dez 15 22:19:56 srvfhem systemd[1]: fhempy.service: Scheduled restart job, restart counter is at 5.
Dez 15 22:19:56 srvfhem systemd[1]: Stopped fhempy.
Dez 15 22:19:56 srvfhem systemd[1]: fhempy.service: Start request repeated too quickly.
Dez 15 22:19:56 srvfhem systemd[1]: fhempy.service: Failed with result 'exit-code'.
Dez 15 22:19:56 srvfhem systemd[1]: Failed to start fhempy.

It seems you are running fhempy on a peer. Can you please let me know how you updated it?
The issue is, that the virtual environment is missing.
Try
python -m venv .fhempy/fhempy_venv
source .fhempy/fhempy_venv/bin/activate
pip3 install fhempy

Unfortunately it didn'twork for me.
In fhempy log
Activating virtual environment...FHEM/bindings/python/bin/fhempy: Zeile 47: .fhempy/fhempy_venv/bin/activate: Datei oder Verzeichnis nicht gefunden
OK
No Python virtual environment available. Exit.
(fhempy_venv) 1:~$ python -m venv .fhempy/fhempy_venv
(fhempy_venv) 1:~$ source .fhempy/fhempy_venv/bin/activate
(fhempy_venv) 1:~$ pip3 install fhempy
Requirement already satisfied: fhempy in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (0.1.684)
Requirement already satisfied: aiohttp==3.8.6 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiohttp[speedups]==3.8.6->fhempy) (3.8.6)
Requirement already satisfied: async-upnp-client==0.31.2 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from fhempy) (0.31.2)
Requirement already satisfied: importlib_metadata==6.1.0 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from fhempy) (6.1.0)
Requirement already satisfied: markdown2==2.4.10 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from fhempy) (2.4.10)
Requirement already satisfied: packaging==23.2 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from fhempy) (23.2)
Requirement already satisfied: pycryptodomex==3.18.0 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from fhempy) (3.18.0)
Requirement already satisfied: requests==2.31.0 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from fhempy) (2.31.0)
Requirement already satisfied: websockets==11.0.3 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from fhempy) (11.0.3)
Requirement already satisfied: zeroconf==0.64.1 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from fhempy) (0.64.1)
Requirement already satisfied: attrs>=17.3.0 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiohttp==3.8.6->aiohttp[speedups]==3.8.6->fhempy) (23.1.0)
Requirement already satisfied: charset-normalizer<4.0,>=2.0 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiohttp==3.8.6->aiohttp[speedups]==3.8.6->fhempy) (3.3.2)
Requirement already satisfied: multidict<7.0,>=4.5 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiohttp==3.8.6->aiohttp[speedups]==3.8.6->fhempy) (6.0.4)
Requirement already satisfied: async-timeout<5.0,>=4.0.0a3 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiohttp==3.8.6->aiohttp[speedups]==3.8.6->fhempy) (4.0.3)
Requirement already satisfied: yarl<2.0,>=1.0 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiohttp==3.8.6->aiohttp[speedups]==3.8.6->fhempy) (1.9.4)
Requirement already satisfied: frozenlist>=1.1.1 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiohttp==3.8.6->aiohttp[speedups]==3.8.6->fhempy) (1.4.1)
Requirement already satisfied: aiosignal>=1.1.2 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiohttp==3.8.6->aiohttp[speedups]==3.8.6->fhempy) (1.3.1)
Requirement already satisfied: aiodns in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiohttp[speedups]==3.8.6->fhempy) (3.1.1)
Requirement already satisfied: Brotli in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiohttp[speedups]==3.8.6->fhempy) (1.1.0)
Requirement already satisfied: voluptuous>=0.12.1 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from async-upnp-client==0.31.2->fhempy) (0.14.1)
Requirement already satisfied: python-didl-lite~=1.3.2 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from async-upnp-client==0.31.2->fhempy) (1.3.2)
Requirement already satisfied: defusedxml>=0.6.0 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from async-upnp-client==0.31.2->fhempy) (0.7.1)
Requirement already satisfied: zipp>=0.5 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from importlib_metadata==6.1.0->fhempy) (3.17.0)
Requirement already satisfied: idna<4,>=2.5 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from requests==2.31.0->fhempy) (3.6)
Requirement already satisfied: urllib3<3,>=1.21.1 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from requests==2.31.0->fhempy) (2.1.0)
Requirement already satisfied: certifi>=2017.4.17 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from requests==2.31.0->fhempy) (2023.11.17)
Requirement already satisfied: ifaddr>=0.1.7 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from zeroconf==0.64.1->fhempy) (0.2.0)
Requirement already satisfied: pycares>=4.0.0 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from aiodns->aiohttp[speedups]==3.8.6->fhempy) (4.4.0)
Requirement already satisfied: cffi>=1.5.0 in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from pycares>=4.0.0->aiodns->aiohttp[speedups]==3.8.6->fhempy) (1.16.0)
Requirement already satisfied: pycparser in ./.fhempy/fhempy_venv/lib/python3.10/site-packages (from cffi>=1.5.0->pycares>=4.0.0->aiodns->aiohttp[speedups]==3.8.6->fhempy) (2.21)

Are you running fhempy on the same machine as FHEM is running?

Yes. Same machine. A NUC

You shouldn't run fhempy from systemd in that case. Please remove the systemd fhempy service.
Please delete /opt/fhem/.fhempy/fhempy_venv and execute sudo apt install python3-venv. After that restart FHEM.

It fixed it. Anyway what is strange that this setup works for almost a year now. However, many thanks for support and patience

I think the missing python3-vemv package was the issue. I added bookworm support the last days which requires venv. Looks like I should add a check if the package is installed.
Thanks for reporting!
@tasisale does that work for you as well?

no, sorry i have the error again.

here is the detail for python from my install.
sudo apt install python3-venv
[sudo] Passwort für fhemadmin:
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
python3-venv ist schon die neueste Version (3.8.2-0ubuntu2).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
fhemadmin@srvfhem:~$ python3
Python 3.8.10
regards
simon

ok, i have delete the folder "/opt/fhem/.fhempy/fhempy_venv" again and restart the nuc.
Now it installed the Update -> 0.1.686 and its green again.
Now i will hope my skoda Connection will go.

Please reopen if fhempy doesn't work. Please create a new issue if the skodaconnection isn't working. Thx!


Update nodegit dependency

The nodegit dependency previously used did not work with the latest
nodejs. Updating to the latest available nodegit fixes relevant errors.
Fixes "Error: Cannot find module '../build/Debug/nodegit.node'"
Closes #15
I've tested git-hours on node v5.5.0 and everything seems to work ok.

So, this was supposed to be a quick fix to support newer node versions since git-hours stopped working on my machine, and turned into a fun debugging session once Travis decided that my builds weren't passing.
This PR should fix the Travis build (check the commits for details) and the program now also checks if the current repository is a shallow clone (which cannot be processed). There are also no errors if the repository is currently in detached HEAD state (such as what happens when Travis clones a repository).

Amazing work! Thanks :) i'll try to release this asap.

All this work is now released in https://github.com/kimmobrunfeldt/git-hours/releases/tag/1.2.0

Thanks!


Coverity CID #1374941 Logically dead code

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/476/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/486/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/474/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/600/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/2169/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/2065/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/729/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/479/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/488/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/476/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/2171/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/2067/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/602/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/731/


[Release/1.6] vendor: golang.org/x/net v0.17.0

backport of https://github.com/containerd/containerd/pull/9250

vendor: golang.org/x/sys v0.13.0
full diff: https://github.com/golang/sys/compare/v0.10.0...v0.13.0
vendor: golang.org/x/text v0.13.0
full diff: https://github.com/golang/text/compare/v0.11.0...v0.13.0
vendor: golang.org/x/net v0.17.0
full diff: https://github.com/golang/net/compare/v0.13.0...v0.17.0
This fixes the same CVE as go1.21.3 and go1.20.10;

net/http: rapid stream resets can cause excessive work
A malicious HTTP/2 client which rapidly creates requests and
immediately resets them can cause excessive server resource consumption.
While the total number of requests is bounded to the
http2.Server.MaxConcurrentStreams setting, resetting an in-progress
request allows the attacker to create a new request while the existing
one is still executing.
HTTP/2 servers now bound the number of simultaneously executing
handler goroutines to the stream concurrency limit. New requests
arriving when at the limit (which can only happen after the client
has reset an existing, in-flight request) will be queued until a
handler exits. If the request queue grows too large, the server
will terminate the connection.
This issue is also fixed in golang.org/x/net/http2 v0.17.0,
for users manually configuring HTTP/2.
The default stream concurrency limit is 250 streams (requests)
per HTTP/2 connection. This value may be adjusted using the
golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams
setting and the ConfigureServer function.
This is https://github.com/advisories/GHSA-4374-p667-p6c8 and Go issue https://go.dev/issue/63417.
This is also tracked by https://github.com/advisories/GHSA-qppj-fm5r-hxr3.

I tried to mimic https://github.com/containerd/containerd/pull/9276.
I did the cherry pick for the commit context, but checked out everything other than the go.mod. I then fixed the conflicts and reran go mody tidy and make vendor. I'm guessing that's how it was done for 1.7 as well, but I'm not entirely sure how else to cherry-pick such a change.

I tried to mimic #9276.
I did the cherry pick for the commit context, but checked out everything other than the go.mod. I then fixed the conflicts and reran go mody tidy and make vendor. I'm guessing that's how it was done for 1.7 as well, but I'm not entirely sure how else to cherry-pick such a change.

Thanks! Yes, preserving the commit message for these can be useful to provide context 👍 ❤


log unexpected http HOST header

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (3d70cfb) 74.18% compared to head (57a59a3) 74.18%.

:exclamation: Current head 57a59a3 differs from pull request most recent head ca2caab. Consider uploading reports for the commit ca2caab to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #315   +/-   ##
=======================================
  Coverage   74.18%   74.18%
=======================================
  Files          43       43
  Lines        4861     4861
=======================================
  Hits         3606     3606
  Misses       1008     1008
  Partials      247      247

Impacted Files
Coverage Δ

middleware/redirect.go
90.32% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[breaking change] 🎉 graphql-eslint v3

fixes https://github.com/dotansimha/graphql-eslint/issues/62 https://github.com/dotansimha/graphql-eslint/issues/664
There are breaking changes because options are changed.
This needs to be merged on the next major release, I can write also a migration guide to new options API.
Also, I saw that rules avoid-operation-name-prefix and no-operation-name-suffix rules we can remove in the next major release because we can validate the same things with naming-convention rule
Recommended config for naming-convention rule now looks like:
{
  types: 'PascalCase',
  fields: 'camelCase',
  overrides: {
    EnumValueDefinition: 'UPPER_CASE',
    OperationDefinition: {
      style: 'PascalCase',
      forbiddenPrefixes: ['Query', 'Mutation', 'Subscription', 'Get'],
      forbiddenSuffixes: ['Query', 'Mutation', 'Subscription'],
    },
    FragmentDefinition: {
      style: 'PascalCase',
      forbiddenPrefixes: ['Fragment'],
      forbiddenSuffixes: ['Fragment'],
    },
    'FieldDefinition[parent.name.value=Query]': {
      forbiddenPrefixes: ['query', 'get'],
      forbiddenSuffixes: ['Query'],
    },
    'FieldDefinition[parent.name.value=Mutation]': {
      forbiddenPrefixes: ['mutation'],
      forbiddenSuffixes: ['Mutation'],
    },
    'FieldDefinition[parent.name.value=Subscription]': {
      forbiddenPrefixes: ['subscription'],
      forbiddenSuffixes: ['Subscription'],
    },
  },
}

@JustinTRoss thanks a lot for the review and suggestions. You can test the next major version by installing alpha version 3.0.0-alpha-4613dfe.0. Any feedback is welcome 😜

@JustinTRoss thanks a lot for the review and suggestions. You can test the next major version by installing alpha version 3.0.0-alpha-4613dfe.0. Any feedback is welcome 😜

Thank you for doing all the hard work! 💪 🧠
Working on getting upgraded to that alpha version presently 😀

@JustinTRoss do you have a twitter account?

@JustinTRoss do you have a twitter account?
@JustinOfRoss


SO CONFUSING! "Tour of C#" needs update for .NET Core tools

I can't make it past building the .dll because I keep getting an error that the csc command is no longer supported. And the note that instructs to use dotnet commands isn't helpful without context. When I do try "dotnet run," I get a build error because there's no Main method.  I'll admit that I've been confused throughout the process of trying to teach myself C# (so far, I've only gone through Quickstarts), but I'm not sure if these guides are for beginners or people who've worked with programming before. A lot is vague, a lot is unexplained, and it's hard to retain the information without being challenged to use it proactively as opposed to copying code.

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

ID: 20935a57-1ba9-a5b8-0a30-cc68dac2e4e1
Version Independent ID: 7c81da48-bf33-8c1a-f9fe-d02e056b2a07
Content: C# Program Structure - A Tour of the C# Language
Content Source: docs/csharp/tour-of-csharp/program-structure.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

@malchikgey I agree that these articles don't look friendly for newcomers, lets wait for @BillWagner so he can approve/triage any changes to these sections in order to improve the barrier to entry.
Until that, let me try to help you with the issue occurred.
If you are on Windows and have Visual Studio 2017 installed, then csc.exe (also known as Roslyn) compiler should be located at "C:\Program Files (x86)\Microsoft Visual Studio\2017\{Community/Professional/Enterprise}\MSBuild\15\bin\Roslyn\".
Navigate to that folder and run csc /t:library {path_to_souce.cs}.  See how to set PATH variable on Windows.
Also, dotnet run does not work because the given example isn't tended to be an executable, it is rather a class library which doesn't have an entry point and thus can't be executed via dotnet run. If you want to build it with dotnet tools please see dotnet build command

@BillWagner please assign this to me, I'll take care about dotnet-tools section.

@d-dizhevsky I just added you as a collaborator. Can you go here and accept the invite: https://github.com/dotnet/docs/invitations  Then, I can assign this to you.
Thanks for all the contributions, and your continued interest.

And assigned. Thanks.

That did the trick! It's still giving me error cs2012, but it created the .dll file.

Started working on this issue and noticed that the tutorial already have an !IMPORTANT section which describes how to use .NET Core build tools and provides a link for tutorial.
====
The examples above use csc as the command line C# compiler. This compiler is a Windows executable. To use C# across other platforms, you should use the tools for .NET Core. The .NET Core ecosystem uses the dotnet CLI to manage command line builds. This includes managing dependencies, and invoking the C# compiler. See this tutorial for a full description of those tools on the platforms supported by .NET Core.
====
@BillWagner  I assume this can be closed? Or there some changes you would like me to do anyways?

"If you've done development before, but are new to C#, read the tour of the C# language." I understand it fine and it actually fills in a lot of cracks for me. This article wasn't made for new comers

Removed assignment from myself because, unfortunately, I have no time to work on that at the moment.

@BillWagner, Should the article shows the project creation from the beginning using .NET Core CLI ?

@Youssef1313
This article really needs a complete rewrite. The content is taken from the C# 1.0 Language Specification. It's had minimal updates since then. The tooling has changed, and the features to highlight in the language are very different than when this was written.
One part of that is to use the .NET Core CLI. But that is only one small part.

@BillWagner, Can you point to the parts to consider when rewriting it ?
I may give it a try.

@Youssef1313 I haven't flushed out the full outline, but a top level overview of what this should cover is in this gist
Now that C# 8 has shipped, the tour should include an overview of pattern matching, and non-OO techniques.  The first step would be to flush out the outline for all the sections that have the wrench icon in that gist.
I think that means most of this section will be rewritten.

I couldn't figure out how to get it running either until I added the Path variable for the C# compiler to my user Path environment variable. I naively assumed that because Visual Studio 2017 was installed that the Path variable would have been set already so I could just use it from the command line. I found the compiler under "C:\Windows\Microsoft.NET\Framework64\v4.0.30319" and added that to my path variable, but was still unable to compile as it is apparently an outdated compiler. I found that the Visual Studio compiler that supports newer language features is located at "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Roslyn" as someone else already mentioned here. To add that to your Path on Windows 10, press windows key+pause, click Advanced System Settings > Environment Variables, then under User Variables for , click Path, then Edit..., click New and paste in the path of the Visual Studio compiler. The path may be slightly different if you are on a different version.


fix(frontend): pending ck conversions displayed under incorrect token

Motivation
It was reported that pending ck conversions were displayed under the wrong token. e.g. one user converted LINK to ckLINK and then browsed ckUSDC and the frontend was displaying "Pending USDC to ckUSDC". This seems to happens because the pending transactions resolved with logs are not filtered for the selected token.
To solve it, we refine the logs topic including the ERC20 contract address among the parameters.
We can see a practical example here.

@peterpeterparker please review

Looks good to me @AntonioVentilii-DFINITY with a TODO. Given that I started the PR, it's up-to-you to approve.
Approved from my side.

Thanks!


Remove ChannelInboundHandler

Motivation:
We merged inbound / outbound handler methods into ChannelHandler in the past and removed the extra interfaces. While doing so we missed to remove the ChannelInboundHandler interface
Modifications:
Remove interface that is not needed anymore
Result:
Cleanup

Attributes are also deprecated in ChannelHanderContext. Should I open PR to remove it?


Trying to put greykite to Docker

Hi team, can you suggest some basic docker image to put Kite into
I am trying to install everything to: continuumio/miniconda3, but
when I am running: conda install -c msys2 libpython m2w64-toolchain- it fails

Hi @Misha123457 Sorry it looks like this question is out of our skill set to help. Maybe you could ask the questions in some Docker forums?

Hi @martinmenchon
Try putting the following at the top of your docker file.
RUN apt update -y &&
apt install build-essential -y &&
apt-get install manpages-dev
RUN pip install --upgrade setuptools &&
pip install --upgrade pip wheel &&
pip install --ignore-installed \   #add all pip install packages on next line.
Hope this helps!

Thanks!
ср, 20 окт. 2021 г., 21:34 McKenzie Quinn @.***>:

Hi @martinmenchon https://github.com/martinmenchon
Try putting the following at the top of your docker file.
RUN apt update -y &&
apt install build-essential -y &&
apt-get install manpages-dev
RUN pip install --upgrade setuptools &&
pip install --upgrade pip wheel &&
pip install --ignore-installed \ #add all pip install packages on next
line.
Hope this helps!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/linkedin/greykite/issues/40#issuecomment-947975573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKRM6AU63XYLADKOO35NVW3UH4KT5ANCNFSM5CKFN2BA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


[Event Request] Table 37 OnBeforeTestStatusOpen

Please extend the following publisher:
OnBeforeTestStatusOpen(var SalesLine: Record "Sales Line"; var SalesHeader: Record "Sales Header"; var IsHandled: Boolean)
with additional parameters:
OnBeforeTestStatusOpen(var SalesLine: Record "Sales Line"; xSalesLine: Record "Sales Line"; var SalesHeader: Record "Sales Header"; FieldNumber: Integer; var IsHandled: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


#819: describe mismatch in AbstractHmTextBody

For #819 I've changed AbstractHmTextBody to properly describe mismatches, added corresponding test and removed todo.

Job #867 is now in scope, role is REV

This pull request #867 is assigned to @g4s8/z, here is why; the budget is 15 minutes, see §4; please, read §27 and when you decide to accept the changes, inform @paulodamaso/z (the architect) right in this ticket; if you decide that this PR should not be accepted ever, also inform the architect; this blog post will help you understand what is expected from a code reviewer; there will be a monetary reward for this job

Codecov Report

Merging #867 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #867      +/-   ##
============================================
+ Coverage     75.28%   75.32%   +0.03%
- Complexity      972      973       +1
============================================
  Files           220      220
  Lines          4710     4713       +3
  Branches        368      368
============================================
+ Hits           3546     3550       +4
+ Misses         1010     1008       -2
- Partials        154      155       +1

Impacted Files
Coverage Δ
Complexity Δ

.../org/takes/facets/hamcrest/AbstractHmTextBody.java
86.36% <100%> (+12.67%)
6 <3> (+2)
:arrow_up:

src/main/java/org/takes/http/MainRemote.java
53.33% <0%> (-1.67%)
6% <0%> (-1%)

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 87f8ee3...5adae2e. Read the comment docs.

@g4s8 thanks, fixed

@rultor merge

@rultor merge

@g4s8 Thanks for your request. @yegor256 Please confirm this.

@rultor merge

@rultor merge

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

@rultor merge

@paulodamaso Done! FYI, the full log is here (took me 20min)

@ypshenychka/z please review this job completed by @g4s8/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

Code review was too long (13 days), architects (@paulodamaso) were penalized, see §55

The job #867 is now out of scope

Payment to ARC for a closed pull request, as in §28: +10 point(s) just awarded to @paulodamaso/z

@0crat quality good

Order was finished, quality is "good": +20 point(s) just awarded to @g4s8/z

Quality review completed: +8 point(s) just awarded to @ypshenychka/z


fix signedness so a build with -Wall -Werror is ok

not sure why github is still saying "Changes requested" when I've marked all conversations as resolved... but please review again!