Rewrite matching incorrect asset instances

Noticed the rewrite is replacing an instance of "style.css" where it shouldn't.
It happens with this piece of code:
(it's a dependency of my project, prosemirror-view)
function iosHacks(dom) {
  if (dom.nodeName == "UL" || dom.nodeName == "OL") {
    var oldCSS = dom.style.cssText; // <- just this line
    dom.style.cssText = oldCSS + "; list-style: square !important";
    window.getComputedStyle(dom).listStyle;
    dom.style.cssText = oldCSS;
  }
}

In the pointed line, looks like the "style.css" part of the string is being matched and replaced with the fingerprinted one, ending up looking like this:
(for some reason, the other lines are not being matched and stay as they should)
var oldCSS = dom.style-0d55b35826f83b7acaf51324d2f32623.cssText;

This not only changes the purpose of the code (it's a subtraction now) but also breaks the terser because it's bad js syntax (variable starts with a number) and get this error:
Build Error (TerserWriter)

Invalid syntax: 0d55b35826f83b7acaf51324d2f32623

Update: this seems to be happening after code minification. This is the same function as above but after:
function(e){if("UL"==e.nodeName||"OL"==e.nodeName){var n=e.style.cssText;e.style.cssText=n+"; list-style: square !important",window.getComputedStyle(e).listStyle,e.style.cssText=n}}

The matcher here for assetPath="style.css" seems to be matching with this part e.style.cssText;e.style.cs and then replaces the "style.css" part with "style-THEHASH.css"
Any workaround for this? I have no idea how all of this works this is the first time I dig this deep into broccoli and the ember build process.

Replying to myself in case anyone stumbles with the same issue.
Excluding the file from fingerprinting solves the issue (altho the css won't be fingerprinted)
// ember-cli-build.js
let app = new EmberAddon(defaults, {
  fingerprint: {
    exclude: [
      'style'
    ]
  },
  // ...

Maybe another solution would be to just change the file name to something less chashing, but would need to explore how to do that.


Issue with testsuite: terraform-docs is not installed

I noticed some issues with the terraform-docs part of the "security" section with your github action:
https://github.com/JamesWoolfenden/terraform-aws-budget/runs/5138356361?check_suite_focus=true
Can you please make sure terraform-docs is installed? Unfortunately, I don't have any experience with github-actions at all...

Ha you were right, shows how i never use the PR on my own repos! Fixed!


Updated to dart 2.12 and null-safety

Hello, Dmitry.
Thanks for your work.
I will accept your changes tonight.

Hello, Dmitry.
Thank you for your work.
All done.
Now you can test your work in real conditions.


Implement review screen design

Hey team! Please add your planning poker estimate with ZenHub @Fattimo @joe-lazzarini


last_seen: provide links to stored json and log data

Resulting CSV looks like this:
timestamp,test,conf,branch,status,count,runs_on,url,job_json,job_log,run_json
2022-06-22 16:23:18+00:00,app-luatest/gh_5747_crash_multiple_args_test.l>,,master,transient fail,38,graviton,https://github.com/tarantool/tarantool/runs/7008228471?check_suite_focus=true,https://multivac.hb.bizmrg.com/tarantool/tarantool/workflow_run_jobs/7008228471.json,https://multivac.hb.bizmrg.com/tarantool/tarantool/workflow_run_jobs/7008228471.log,https://multivac.hb.bizmrg.com/tarantool/tarantool/workflow_runs/2543635332.json
2022-06-22 16:14:02+00:00,replication/box_set_replication_stress.test.lua,vinyl,master,fail,20,macos-10.15,https://github.com/tarantool/tarantool/runs/7008230119?check_suite_focus=true,https://multivac.hb.bizmrg.com/tarantool/tarantool/workflow_run_jobs/7008230119.json,https://multivac.hb.bizmrg.com/tarantool/tarantool/workflow_run_jobs/7008230119.log,https://multivac.hb.bizmrg.com/tarantool/tarantool/workflow_runs/2543635352.json
2022-06-22 16:14:00+00:00,replication/box_set_replication_stress.test.lua,vinyl,master,fail,7,macos-11,https://github.com/tarantool/tarantool/runs/7008229745?check_suite_focus=true,https://multivac.hb.bizmrg.com/tarantool/tarantool/workflow_run_jobs/7008229745.json,https://multivac.hb.bizmrg.com/tarantool/tarantool/workflow_run_jobs/7008229745.log,https://multivac.hb.bizmrg.com/tarantool/tarantool/workflow_runs/2543635329.json

I didn't dig into the changes in the code much, but Nick asked me to look on the idea.
Re code
We have the HTML report type aside of the CSV one and it would be good to keep both reports with similar functionality. Or drop one that we don't use and don't want to support.
In my head, the ideal solution is to keep both, but enhance the HTML report with JS interactive convenience features that we have now on the deployed instance. Now the JS features are enabled externally on top of the CSV report, but we can add the JS file as a resource and copy into the output directory, just like we do for the CSS file. This way everything will be in one place (in the repository).
I think that it is good to keep the CSV report, because sometimes it is convenient to import data into a spreadsheet editor and calculate some numbers. We can generate both reports and give a link to the CSV file from the HTML report.
Re idea
I like this idea. I would like if the files will be sent from the storage with application/text (or application/json) MIME type, not octet-stream, so one can look on them from a Web browser.
I think it would be good to store artifacts from GitHub Actions as well, because they expire too, but sometimes useful for investigation (in the artifacts we store logs from tarantool instance, extra logs from test-run and core dumps in case of a fail).
If the columns json files will bloat the output too much, it is okay for keep only logs (and artifacts if you'll add them).
Further thougts
I would also like to see the historical data: each test has its own history of fails and sometimes we want to analyze more than the last fail. It seems, however, it is out of scope of this task. We need to generate a per test Web page and link it from the main report.
What else is interesting for me: if we store all data, it would be good to archive snapshots and provide a page with the list of them. So one can download the real data and experiment with its own sensor/report for multivac. Initially I think about this project as about collaborative effort toward data analysis.
Say, I see a bad situation: too long repository metadata update or specific test failure. However it may be hard to reproduce and I want to track the problem during some period. I'll download the snapshot, white a sensor and, maybe, a report and send a pull request. Once it is accepted, my problem is tracked.
I also think that the old decision to collect only long term branches (exclude developer branches and pull requests) is bad. We can collect everything, but generate reports only for long term branches. If we'll have the order of magnitude more data to analyze (even if it is not an ideal data), it may be quite useful for tracking rare problems. Nothing will be worse, if we'll start to collect all available data.
(TBH, I created the fetch.py script before we shift to pull requests from personal forks, so collecting pull request data may require some effort, at least verification.)
If you like my ideas around reporting, you also may be interested about thoughts on storing data.


Add labels to CRD YAML files

Type of question

General operator-related help

Question
Hi,
how can I add labels to a CRD YAML file
What did you do?
I tried to add this code in the kustomization.yaml file but it didn't help (it worked with role.yaml):
patchesStrategicMerge:
- patches/labels_patch.yaml

There is something that I can do to do it?
thanks
Environment
Operator type:

language go

Kubernetes cluster type:

$ operator-sdk version
operator-sdk version: "v1.9.0-11-gad645e4b", commit: "ad645e4bc6d6ae85fa5f0bffcad3bc871690608c", kubernetes version: "v1.20.2", go version: "go1.15", GOOS: "linux", GOARCH: "amd64"

$ go version (if language is Go)
go version go1.15.14 linux/amd64

@matancarmeli7 this issue looks upstream related... this question is better handled within the kustomize community.  Closing for now... but please re-open if there is a operator sdk specific concern to address.  thanks again!


Screen Share

Thanks for this it is really helpful! I wanna ask; is it possible screen share with tubertc ? Or anybody any way for screen sharing?

Unfortunately, screen sharing is currently not possible with tubertc.


Create a simple guide for starting out

The current docs are fairly good but generic. However, I think a more straightforward guide to "how to run your first cubos sample" or something would be interesting (for both windows and linux)

Duplicate of #1010.


Displaying Gregorian calendar date along with Hijri Date

Hi,
Is the any way we can display Gregorian Calendar date along with the Hijri date?
regards,
Mohammed

i think you can modify DayView.java to take two calendars Gregorian calendar and Hijri calendar.
but, it's need to change a lot of things also like MonthView.java and of course it's Adapter and  MaterialHijriCalendarView.java
i wish you Happy coding (:

Hi Ahmad, Thanks for your reply.
Yes, I have made some changes to reflect the Gregorian calendar. It's working but the performance is hit very badly. I will post the modifications anyway.

please share with me your modifications we can work on it together (:

Hi Ahmad, I am extremely sorry to have missed your comments and didn't reply to you as well. Please let me know if you still need it. I will share the zip file.


Problem with getting dotnet-monitor to execute configured actions on trigger

Description
Hi dotnet-monitor team, I set up dotnet-monitor 6 in a sidecar pattern on Kubernetes for an application I'm surveilling. To get gcdumps automatically without triggering the API, I wanted to add triggers and actions that should execute periodically. However, I was not able to get a trigger to execute during a PoC.
I was following the examples on the configuration documentation and set up a simple trigger that should execute if the CPU threshold exceeds a limit. The following logs are all I can see on my sidecar. Now, I'm not sure if the trigger is even firing as nothing happens.

Configuration
I have one sample application that is almost the same as the regular ASP.NET sample app for .NET 6 from Microsoft with the following environment variables
        env:
        - name: ASPNETCORE_URLS
          value: http://+:80
        - name: DOTNET_DiagnosticPorts
          value: /diag/port.sock
        volumeMounts:
        - mountPath: /diag
          name: diagvol
        - mountPath: /dumps
          name: dumpsvol

Dotnet-monitor runs as sidecar alongside it with a shared volume "/diag" for communication and a persistent volume claim "/dumps" to save application dumps and egress data persistently.
      - name: monitor
        image: mcr.microsoft.com/dotnet/monitor:6
        imagePullPolicy: Always
        args: ["--no-auth", "--urls", "http://*:52323"]
        ports:
        - containerPort: 52323
        env:
        - name: DotnetMonitor_DiagnosticPort__ConnectionMode
          value: 'Listen'
        - name: DotnetMonitor_DiagnosticPort__EndpointName
          value: /diag/port.sock
        - name: DotnetMonitor_Storage__DumpTempFolder
          value: /dumps
        - name: DotnetMonitor_Logging__Console__FormatterName
          value: simple
        volumeMounts:
        - mountPath: "/diag"
          name: diagvol
        - mountPath: /dumps
          name: dumpsvol
        - mountPath: /etc/dotnet-monitor
          name: dm-config
      volumes:
      - name: dumpsvol
        persistentVolumeClaim:
          claimName: diagvol-pv-claim
      - name: diagvol
        emptyDir: {}
      - name: dm-config
        configMap:
          name: dotnet-monitor-triggers

The following is my dotnet-monitor configuration. As you can see I'm trying to use the /dumps folder for egressing and use a simple rule that should trigger if my CPU usage exceeds 1 to collect a gcdump and traces. I've been trying slight adjustment and other actions like CollectDump without success.
apiVersion: v1
kind: ConfigMap
metadata:
  name: dotnet-monitor-triggers
data:
  settings.json: |-
    {
        "Egress": {
            "FileSystem": {
                "monitorFile": {
                    "directoryPath": "/dumps"
                }
            }
        },
        "CollectionRules": {
            "HighCpuRule": {
                "Trigger": {
                    "Type": "EventCounter",
                    "Settings": {
                        "ProviderName": "System.Runtime",
                        "CounterName": "cpu-usage",
                        "GreaterThan": 1,
                        "SlidingWindowDuration": "00:01:00"
                    }
                },
                "Actions": [
                    {
                        "Type": "CollectGCDump",
                        "Settings": {
                            "Egress": "monitorFile"
                        }
                    },
                    {
                        "Type": "CollectTrace",
                        "Settings": {
                            "Profile": "Cpu",
                            "Duration": "00:01:00",
                            "Egress": "monitorFile"
                        }
                    }
                ]
            }
        }
    }

Regression?
So far I haven't been able to get a trigger/action to save something once. The API runs fine if loaded manually. I can get gcdumps, traces and so on. If I trigger the dump API it saves a minidump to /dumps as expected.
I hope you can help me here as I'm not sure if it's a bug or something I've overlooked. Many thanks.

You have the SlidingWindowDuration set to 1 minute on the trigger. That means the application must be suing non-zero CPU every moment for an entire minute. If it happens to hit zero even briefly during the sliding window, it will not trigger.
Additionally, you logs show that the collection rules were started 5:36:42 PM and then you changed configuration (which will stop and restart collection rules, which will reset any tracking and conditions for the triggers) at 5:37:52 PM; that's only 1 minute and 10 seconds. It's unlikely that you were able to trigger the rule within that time window.

Hi Justin,
thanks, for your quick response. You were right with the CPU dropping to 0. I've lowered the cpu-usage parameter to 0 and the SlidingWindowDuration to 00:00:05 and now I'm able to get dumps and traces. Thank you very much, this has really kept me busy for some time.
About the configuration change I'm still in the dark. My container has been running for about an hour and I got the "Collection rule configuration changed." message every 2 minutes without doing anything. Do you have an idea what could cause this?

I'm closing this issue since the core questions were answered. Please feel free to open a discussion for asking how to accomplish something or what behavior is expected or open an issue if you've encountered a bug.


admin: include ReplicaAssignment in ListTopics()

Follow-on from #1155 / #1178 include the replica assignment information that we got back in the ListTopics() TopicDetail responses

@varun06 thanks for the approval, were you waiting for another reviewer before merge?

It is simple enough and I will merge it after another look today. In the mean time, if someone else want to review, that's great.


Avoid explicit references to AccessDeniedException in tests

For PCT compatibility with https://github.com/jenkinsci/jenkins/pull/4848.

Looks like @daniel-beck is the sole maintainer.

Trying to trigger Incrementals deployment…

JEP-227 actually 😭


[python/viewer] Add backend-independent interface to add and update primitive geometries.

Currently, it is possible to add hppfcl primitive geometries to both Meshcat and Geopetto-Gui, yet it is not possible to update there properties using the same principal. Moreover, their respective API to do so is quite bad. One way to get around this limitation would be to delete and create a new geometry systematically, but it is likely to perform poorly.

Fixed by #340. Only Panda3D is supported for now.


1.20.4

update dependencys, gradle and cape textures
Trying to fix issue #15 but could also still not fix it.
Didn't test the fix, since AE didn't have an version for 1.20.4 fabric ready

Right, thanks for submitting this PR. I'll see if i can test it asap.

Everything seems to work just fine. I was also not able to reproduce #18 so this probably fixes it.

Also, i think im going to stick with a default branch and  give support for the latest version.


Scss encountered an error while converting 'assets/css/style.scss'

Hey,
I'm getting an error with my build, what am I doing wrong?
Configuration file: /builds/benisameme/test-project/_config.yml        Deprecation: The 'gems' configuration option has been renamed to 'plugins'. Please update your config file accordingly.             Source: /builds/benisameme/test-project        Destination: public  Incremental build: disabled. Enable with --incremental       Generating...    Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/style.scss':                     Invalid US-ASCII character "\xE2" on line 5 jekyll 3.5.2 | Error:  Invalid US-ASCII character "\xE2" on line 5
Full log: https://gitlab.com/benisameme/test-project/-/jobs/34394548
Repo: https://gitlab.com/benisameme/test-project/tree/master
assets/css/main.scss: https://gitlab.com/benisameme/test-project/blob/master/assets/css/main.scss

Looks like an encoding issue. Probably has more to do with how you have your Ruby environment setup than anything related to the theme's files.
Give this thread on jekyll/jekyll a look.

Alright, Thanks!
(sorry for the late reply)

I encountered the same issue and solved to create style.scss file filled below content in assets/css folder.
---
---

@charset "UTF-8";

I'm seeing the same error and am unsure on how to resolve it.
I've tried adding '@charset "UTF-8";' and it didn't seem to help.
I have also complete purged and reinstalled ruby/dev.
Is anyone else having this issue?

Same problem here with a post-receive hook which had ever worked fine. I reported some details on Stackoverflow.
I solved by adding at the top of my hook.
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

Not sure it is the best option.


OpenAQ API Version 2: Plans to update?

OpenAQ recently released version 2 of their API to incorporate low cost sensor data. Is anyone planning to update this wrapper to work with the new version?

Sorry for taking (way) too long to respond to this. My understanding is that OpenAQ is working on its own API Wrapper for Python and so I haven't put any effort into this as it will likely be deprecated. If that's not the case, I can put some time into this.
I just posted an issue here and will check back.


fmt: correct fmt doc for hexadecimal notation

This PR will be imported into Gerrit with the title and first
comment (this text) used to generate the subject and body of
the Gerrit change.

This is wrong pull request


Remove double text

Removed a copy/pasted double Note comment.
I choose the second version, it adds one word ("update") in the sentence:

[...] there might be up to a one-hour delay before the RBAC group update takes effect. [...]

Learn Build status updates of commit 335009c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/aks/cluster-container-registry-integration.md
:white_check_mark:Succeeded

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

@mgoedtel
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#please-close due to redundant requested change that was already approved in PR https://github.com/MicrosoftDocs/azure-docs/pull/103896/files.


[KOGITO-4583] Revert lint to version v1.37.1

Signed-off-by: Karel Suta<EMAIL_ADDRESS>https://issues.redhat.com/browse/KOGITO-4583
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

/jenkins test


Lazy load of candles

Hi, and apologies in advance if question was already done.
Has anyone already implemented a lazy loading / progressive rendering of candles?
I'm able to show 100000 candles, for example, but it's very aggressive in terms of CPU and time, and it's not useful to do it all together, we can render or load progressively.
Thanks a lot for this amazing tool.

Hey, most likely that's an app-level problem. There is a basic example: https://github.com/tvjsx/trading-vue-js/blob/master/test/tests/DataHelper.vue . Obviously the full solution will be sightly more complicated.


support mismatch between DateTime (as medatata) and column type

Is your feature request related to a problem? Please describe.
If something went wrong (usually due to crate dynamic columns) in the column typing w.r.t. the actual metadata type DateTime defined for a column, QL bombs.
Describe the solution you'd like
It would be better to just print out the value and raise a warning.
Describe alternatives you've considered
Fixing manually the columns.

closed by #387


No Catalog Appearing in quinteros-2.2

I have configured a standalone ManageIQ quinteros-2.2 server setup with internal DB and messaging server. I have deployed the same on AWS EC2.
I do not see any error in evm service log. Any idea if I missed something?
This is what I see when I navigate to Services -> Catalogs

Looks like it is not an issue. Closing!


fix data migrate for juicefs enterprise

Ⅰ. Describe what this PR does
fix data migrate for juicefs enterprise
Ⅱ. Does this pull request fix one issue?

Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/test fluid-e2e


Enabled field in the ADLSE Table not working as expected

Hi,
I've just run a test with a container empty and setup with 3 tables. Only one table had the Enabled column ticked.
When I run the Export I'm expecting that only dat from one table (the one marked as Enabled) will be exported. The Message says "3 our of 3 tables will be exported" and  actually 3 tables have been exported.
I suppose that the code for exporting should filter for Enabled = true in order to exclude the table not set as Enabled.
In previous versions there was a button to set On Hold that probably has beedn replaced with this Enabled column.
Please let me know
Thank you
Eclipses

Indeed @eclipses. This is not the expected behavior.
I have created a new pull request: https://github.com/microsoft/bc2adls/pull/97
Please sync from main and then try out the above pull request- hopefully it shall resolve the issue.
Best regards,
The bc2adls team.

Thnak you.
Let me test it

@DuttaSoumya fix deployed and tested. Seems working properly now. Thank you for the quick fix. I think you can complete the PR and close this issue.


Updating conenector values and fixing Tactics

Fixes #
Proposed Changes

Updating connector values to match with other ASIM files in same folder
updating Tactics to standard values to align with others

@ashwin-patil - let's get an update on this.

@ashwin-patil - let's get an update on this.

Updated. resolved conflicts, reverting ASIM connector changes


Adjusting the wavefield

Description of the bug
I am trying to make adjustments to the wavefield to test some things about the dynamics of my vessel. Adjustments I try to make are expanding the waves and reducing or increasing the size of the wavefield.
To turn off the waves I set the gain and amplitude to 0 in the sydney_regatta.sdf, see first image below. This results in the vessel no longer moving up and down as expected, but the visuals of the waves are not stopped.
I'm trying to change the size of the wavefield by adding a 'size' parameter to the sydney_regatta.sdf, see first image below. The design of this is based on how this is read by the Wavefield.cc file: {params["size"].vector3d_value().x(), params["size"].vector3d_value().y()}.
The adjusted values are also published correctly to the /vrx/wavefield/parameters topic as shown in the second image.
Reproduction

Modify sydney_regatta.sdf according to the image above.
Build, source and run the environment as you are used to:
colcon build --merge-install
source install/setup.bash
ros2 launch ros2 launch vrx_gz competition.launch.py
Check the changes:
- Use to component inspector in gazebo to check if the pose of the vessel is stationary in the z direction.
- Use the visuals in gazebo to check if the waves are not moving up and down anymore.
- Use the visuals in gazebo to check if the size of the entire wavefield changed accordingly.

System Configuration:

OS: PopOS 22.04
ROS Version: ROS2 Humble
Gazebo Version: Gazebo 7.6.0
Graphics Card:  NVIDIA GeForce RTX 3050
Are you using VRX or VRX Classic? VRX

Screenshots

I met similar problem as dscherrenburg described, that Wave Visual doesn't change with the parameter topic.
In the end I found out that the wave parameter only apply on wave visual once at start up, which are described in /src/vrx/vrx_gz/src/WaveVisual.cc, inside the member function WaveVisualPrivate::OnUpdate()  and control by the paramsSet boolean.
So I tried these temporary solutions to change wave parameters of wave visual:
1.Let parametset become false when receive call back from parameter topic.
Or more violence but simpler way :
2. Change the default wave parameter values in Wavefield.cc and compile it again.
3. remove if (!this->paramsSet) { } block at line 304 of WaveVisual.cc, let params update every render cycle.
Wave visual will change its parameters through these ways.
But I found out another issue that the wave visual and the buoyancy apply on the wamv or buoy are not synchronized, there are tiny phase difference between them. This behavior will more significant when using larger wave amplitude (gain).

You can see the wamv doesn't move with wave visuals and "fly" out above the water line.

Same in buoy.
The wave parameter in this case is
public: WavefieldPrivate():
    size({6000, 6000}),
    cellCount({300, 300}),
    model("PMS"),
    number(3),
    scale(1.1),
    angle(0.3),
    steepness(0.0),
    amplitude(0.0),
    period(10),
    phase(0.0),
    direction(0.0),
    angularFrequency(2.0*M_PI),
    wavelength(2 * M_PI / this->DeepWaterDispersionToWavenumber(2.0 * M_PI)),
    wavenumber(this->DeepWaterDispersionToWavenumber(2.0 * M_PI)),
    tau(2.0),
    gain(5.0)
```.
I change params by modifying the Wavefield.cc default value and removing parameter publisher plugin block in sydney_regatta.sdf.

I guess this might cause by renderer? Or the coast_wave glsl program?


create last-child selector section

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason:  The article https://guide.freecodecamp.org/css/tutorials/css-selectors-cheat-sheet/ already contains information about the last-child selector.
Thank you and happy coding.


Minor documentation update for #277.

Minor documentation fixes for #277. It additionally fixes all other broken links reported (I had to guess a bit where the 'advanced c code' link was supposed to go - please let me know if not to the pragma injector section.).
Fixes #277.

Ready for next review.


ci: reduce number of presubmit kind clusters

There has been a noticable reducation in stability of the kind presubmits. This is an attempt to try to improve stability.

/lgtm

/wip


Create a DateTime value object that allows to control time for tests

Also removed a lot death code only used for testing?

As far as I could see, the dead code you removed was not yet in use. And was simply copy/pasted from Stepup-Middleware. Removing it seems the right choice here.


add other uuid functions (v1, v3, v5, v6, v7, v8) to String module

There are plenty of uuid versions:
Version 1: UUIDs using a timestamp and monotonic counter.
Version 3: UUIDs based on the MD5 hash of some data.
Version 4: UUIDs with random data.
Version 5: UUIDs based on the SHA1 hash of some data.
Version 6: UUIDs using a timestamp and monotonic counter (sortable).
Version 7: UUIDs using a Unix timestamp (sortable).
Version 8: UUIDs using user-defined data.

We currently have only generating v4, maybe we can add more of them.
It can be done as an extension to existing method by some enum param version.
You don't have to implement all of them, you can pick any.

I want to use an enum, then a switch case, and make the default use V4, is that good?


chore: fabric8 client v6.3.1

Please close #1656, then. Also note that this probably shouldn't be merged until Quarkus provides a public version that uses the same Fabric8 client.

Re-target to next branch. OK to merge there so that we can have a snapshot with it for downstream consumption.


Service Provision times out for the powervs

Version used: oparin
Service Provision Error: Server [EVM] Service [centos-stream-8-small-20230326-024055] Step [checkprovisioned] Status [Error Creating Service] Message [Error: timed out after<PHONE_NUMBER>48 seconds. Timeout threshold [600]]
Service Provision Error: Server [EVM] Service [centos-stream-8-small-20230326-024055] Step [checkprovisioned] Status [Error Creating Service] Message [Error: timed out after<PHONE_NUMBER>48 seconds. Timeout threshold [600]]
VM Provision Error: [EVM] VM [centos-stream-8-small0009] Step [CheckProvisioned] Status [Error Creating VM] Message [Error: timed out after<PHONE_NUMBER>48 seconds. Timeout threshold [600]]

seen above notifications in the service UI

but vm is created in the backend

Post this it never updates the service with vm mapping and remains in the following state forever, I don't see any recover steps.. if any please let me know..

@jaywcarman Can you please take a look at this one?

I haven't been able to recreate this in my environment.
Since the user won't have access to the service after the failed request, the admin will probably just manually delete it. @agrare suggested that we should be able to at least automate this clean-up after fail in our provisioning state-machine.
Maybe we could also increase the timeout - would be interesting to know exactly how long the VM takes to build. Our definition of "finished building" is a state of ACTIVE and a non-zero processor and memory value (source).

@jaywcarman today it failed with following error:

This one also got deployed in the backend.

Now run ./collect_current_logs.sh or ./collect_archive_logs.sh depending on if you want the latest or all logs.

Everything is running in the openshift environment, hence above instructions may not really work, let me try the steps mentioned here and send you offline.

@jaywcarman These are the pods, please suggest from what all containers we need to collect logs?
[0] % oc get pods -n manageiq
NAME                                                              READY   STATUS      RESTARTS        AGE
1-ems-metrics-processor-6b84f786bf-7nlck                          1/1     Running     0               2d13h
1-ems-metrics-processor-6b84f786bf-zsqpw                          1/1     Running     0               2d13h
1-event-handler-867d45f79b-zv7lx                                  1/1     Running     0               2d13h
1-generic-75d744cfcc-6957s                                        1/1     Running     0               2d13h
1-generic-75d744cfcc-98dpv                                        1/1     Running     0               2d13h
1-ibm-cloud-power-virtual-servers-cloud-event-catcher-2-85c7j5l   1/1     Running     1 (8h ago)      8h
1-ibm-cloud-power-virtual-servers-cloud-refresh-2-9dc77b8bdzmxx   1/1     Running     0               8h
1-priority-7bb54577df-6rcxk                                       1/1     Running     1 (3h34m ago)   2d13h
1-priority-7bb54577df-l97jq                                       1/1     Running     0               2d13h
1-remote-console-85898456d6-q9jn9                                 1/1     Running     0               2d13h
1-reporting-74dc89887f-5l9vr                                      1/1     Running     0               2d13h
1-reporting-74dc89887f-htvn8                                      1/1     Running     0               2d13h
1-schedule-5bf9cdddb7-vnh4h                                       1/1     Running     0               2d13h
1-ui-6d755f46dd-frgfq                                             1/1     Running     1 (3h34m ago)   2d13h
1-ui-6d755f46dd-pn2qm                                             1/1     Running     0               2d13h
1-web-service-7c474cdd58-qk94b                                    1/1     Running     0               2d13h
1-web-service-7c474cdd58-vfrgt                                    1/1     Running     0               2d13h
httpd-69cfb556fd-82q5p                                            1/1     Running     0               51d
manageiq-operator-59666dfb7b-d5lmv                                1/1     Running     2 (10d ago)     51d
memcached-6d4985dc9c-7tlpx                                        1/1     Running     0               51d
orchestrator-68d5d6584-6dzvd                                      1/1     Running     6 (2d13h ago)   51d

Try the generic pods: oc logs -l name=1-generic

Maybe something like this could work:

Assign users to a role with Access Restriction = Only User Owned
Create a service catalog item to use as a template from which to make copies
For each user, create a copy of the service catalog item with ownership set to the user (instead of group)

If you have too many users to manage this through the GUI, perhaps we could script automation through the Service Management API

@mkumatag thanks for providing logs privately.
I see a bunch of ems_auth_errors along with the log for the message in your screenshot above:
{
  "@timestamp": "2023-04-28T03:04:39.534744",
  "hostname": "1-generic-75d744cfcc-6957s",
  "pid": 8,
  "tid": "94c0",
  "service": "evm",
  "level": "warning",
  "message": "MIQ(ManageIQ::Providers::IbmCloud::PowerVirtualServers::CloudManager#authentication_check_no_validation) type: [\"default\"] for [2] [provider-powervs-1] Validation failed: error, 859: unexpected token at 'upstream request timeout'"
}

Looks like authentication_check_no_validation calls powervs verify_credentials which raised an exception we didn't anticipate.

I'm assuming the auth error is intermittent... but you could force a Re-check Authentication Status from the provider summary page. Wait a few minutes are verify the Default Credentials are still Valid:

I see the issue one more time now, happens when you keep running the stack for the longer time, more than couple of hours don't see the vm relationship but in the backend vm is created.

@jaywcarman sent the logs in private channel.

I found a bug that would cause this, though I would have expected it to always fail... not occur intermittently.
https://github.com/ManageIQ/manageiq-providers-ibm_cloud/pull/455

@mkumatag Can you verify whether this fix fixes your case?  I'm going to close this issue for now, since we think it's fixed and if it's still an issue, please reopen.


Looks like adding device other than Sonoff Basic breaks the whole component

Initially had a single Sonoff Basic, things were working well.
Added a Sonoff 4Ch pro, now don't see even the sonoff basic.
Error in Log:
Error while setting up platform sonoff
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 128, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/config/custom_components/switch/sonoff.py", line 23, in async_setup_platform
    entity = SonoffSwitch(hass, device)
  File "/config/custom_components/switch/sonoff.py", line 36, in __init__
    SonoffDevice.__init__(self, hass, device)
  File "/config/custom_components/sonoff.py", line 333, in __init__
    self._state         = device['params']['switch'] == 'on'
KeyError: 'switch'

Read my "Credits" section 😆
Will be fixed but I needed to see the output for myself before l blindly commit and ask for you to test.

Please check other issue, have added the json there.

Some new Progress here. @peterbuga is the man! Should be able to get this working!

it works now, thanks for debugging assistance @2016for!
closing.


bug: Conference app crashes after one week on iOS device

Bug Report
Ionic version:

[x] 5.0.2
Current behavior:

The ionic conference app crashes after being installed on an iPhone 8 Plus (iOS version: 12.3.2). App runs fine for one week before the crash happens.
**Video of the behaviour: **https://youtu.be/3MuIB666U-Y
Expected behavior:

App should load and run instead of crashing.
Steps to reproduce:

Create a new project using the ionic CLI and select the conference app
Follow the steps listed here: https://ionicframework.com/docs/building/ios
Open the Xcode project, sign the app and deploy it to the device.
Let it be installed on the device for one week.

Related code:

insert short code snippets here

Other information:

Ionic info:

insert the output from ionic info here

Ionic:
Ionic CLI : 5.0.2
Utility:
cordova-res : not installed
native-run  : not installed
System:
NodeJS : v11.5.0
npm    : 6.9.0
OS     : macOS Mojave

Hi, @santhoshraje please try below
ionic cordova platform rm ios
ionic cordova platform add ios

@ranjeetmca Hi! Thanks for the advice. I will try removing and adding the platform and testing it on my device for one week again. Will update here after my testing.

@ranjeetmca thanks for the suggestion. Unfortunately this did not work.
Quick update: I tried factory resetting both my iPhone and development environment and reinstalling ionic and the app (just the basic blank app this time), but the same thing happened.
Giving up on ionic for now. Will be trying Flutter next.

It took a really long time but I figured it out. iOS apps stop working on the device after 7 days if you are using a free developer account. Looks like it was not a problem with ionic after all.
https://stackoverflow.com/questions/38307356/iphone-app-under-test-crashes-after-a-few-days


Compilation failed for vadd after installation

After installing tapa I tried to build vadd by source run_tapa.sh
But I encounter these errors
I0316 04:40:40.180 tapa.util:184] logging level set to INFO
I0316 04:40:40.180 tapa.tapac:407] Executing all steps of tapac
W0316 04:40:40.180 tapa.tapac:429] The floorplan option is automatically enabled because a floorplan output file is provided
I0316 04:40:40.180 tapa.tapac:521] running translated command: `tapa --work-dir=run analyze --input=vadd.cpp --top=VecAdd synth --part-num=xcu250-figd2104-2L-e --clock-period=3.33 optimize-floorplan --connectivity=link_config.ini link --floorplan-output=run/VecAdd_floorplan.tcl pack --output=run/VecAdd.xo --bitstream-script=run/VecAdd_generate_bitstream.sh`
I0316 04:40:40.181 tapa.util:184] logging level set to INFO
I0316 04:40:40.181 tapa.tapa:54] tapa version: 0.0.20240301.1
I0316 04:40:40.181 tapa.tapa:58] Python recursion limit set to 3000
I0316 04:40:40.242 tapa.steps.analyze:248] Running tapacc command: /usr/local/bin/tapacc run/flatten/flatten-5322dfa0-vadd.cpp -top VecAdd -- -std=c++17 -I /home/zhenyu/.local/lib/python3.8/site-packages/tapa/../../../src -stdlib=libc++ -isystem /usr/lib/llvm-17/include/c++/v1/ -isystem /usr/include/clang/17/include/ -isystem /usr/lib/clang/17/include/
<scratch space>:45:1: error: expected unqualified-id
   45 |
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:14:
In file included from /usr/include/c++/v1/__compare/compare_three_way.h:13:
In file included from /usr/include/c++/v1/__compare/three_way_comparable.h:14:
In file included from /usr/include/c++/v1/__concepts/common_reference_with.h:12:
In file included from /usr/include/c++/v1/__concepts/convertible_to.h:13:
In file included from /usr/include/c++/v1/__type_traits/is_convertible.h:14:
/usr/include/c++/v1/__type_traits/is_array.h:40:22: error: reference to unresolved using declaration
   40 | template <class _Tp, size_t _Np>
      |                      ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:22:
/usr/include/c++/v1/__iterator/access.h:22:22: error: reference to unresolved using declaration
   22 | template <class _Tp, size_t _Np>
      |                      ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:22:
/usr/include/c++/v1/__iterator/access.h:27:22: error: reference to unresolved using declaration
   27 | template <class _Tp, size_t _Np>
      |                      ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:24:
In file included from /usr/include/c++/v1/__memory/allocation_guard.h:15:
In file included from /usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /usr/include/c++/v1/__memory/construct_at.h:23:
/usr/include/c++/v1/new:182:26: error: reference to unresolved using declaration
  182 | enum class align_val_t : size_t {};
      |                          ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:24:
In file included from /usr/include/c++/v1/__memory/allocation_guard.h:15:
In file included from /usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /usr/include/c++/v1/__memory/construct_at.h:23:
/usr/include/c++/v1/new:207:84: error: reference to unresolved using declaration
  207 | _LIBCPP_NODISCARD_AFTER_CXX17 _LIBCPP_OVERRIDABLE_FUNC_VIS void* operator new(std::size_t __sz) _THROW_BAD_ALLOC;
      |                                                                                ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:24:
In file included from /usr/include/c++/v1/__memory/allocation_guard.h:15:
In file included from /usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /usr/include/c++/v1/__memory/construct_at.h:23:
/usr/include/c++/v1/new:207:66: error: 'operator new' takes type size_t ('unsigned long') as first parameter
  207 | _LIBCPP_NODISCARD_AFTER_CXX17 _LIBCPP_OVERRIDABLE_FUNC_VIS void* operator new(std::size_t __sz) _THROW_BAD_ALLOC;
      |                                                                  ^
/usr/include/c++/v1/new:209:19: error: reference to unresolved using declaration
  209 | operator new(std::size_t __sz, const std::nothrow_t&) _NOEXCEPT _LIBCPP_NOALIAS;
      |                   ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:24:
In file included from /usr/include/c++/v1/__memory/allocation_guard.h:15:
In file included from /usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /usr/include/c++/v1/__memory/construct_at.h:23:
/usr/include/c++/v1/new:209:1: error: 'operator new' takes type size_t ('unsigned long') as first parameter
  209 | operator new(std::size_t __sz, const std::nothrow_t&) _NOEXCEPT _LIBCPP_NOALIAS;
      | ^
/usr/include/c++/v1/new:213:67: error: reference to unresolved using declaration
  213 | _LIBCPP_OVERRIDABLE_FUNC_VIS void operator delete(void* __p, std::size_t __sz) _NOEXCEPT;
      |                                                                   ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:24:
In file included from /usr/include/c++/v1/__memory/allocation_guard.h:15:
In file included from /usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /usr/include/c++/v1/__memory/construct_at.h:23:
/usr/include/c++/v1/new:216:86: error: reference to unresolved using declaration
  216 | _LIBCPP_NODISCARD_AFTER_CXX17 _LIBCPP_OVERRIDABLE_FUNC_VIS void* operator new[](std::size_t __sz) _THROW_BAD_ALLOC;
      |                                                                                ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:24:
In file included from /usr/include/c++/v1/__memory/allocation_guard.h:15:
In file included from /usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /usr/include/c++/v1/__memory/construct_at.h:23:
/usr/include/c++/v1/new:216:66: error: 'operator new[]' takes type size_t ('unsigned long') as first parameter
  216 | _LIBCPP_NODISCARD_AFTER_CXX17 _LIBCPP_OVERRIDABLE_FUNC_VIS void* operator new[](std::size_t __sz) _THROW_BAD_ALLOC;
      |                                                                  ^
/usr/include/c++/v1/new:218:21: error: reference to unresolved using declaration
  218 | operator new[](std::size_t __sz, const std::nothrow_t&) _NOEXCEPT _LIBCPP_NOALIAS;
      |                     ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:24:
In file included from /usr/include/c++/v1/__memory/allocation_guard.h:15:
In file included from /usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /usr/include/c++/v1/__memory/construct_at.h:23:
/usr/include/c++/v1/new:218:1: error: 'operator new[]' takes type size_t ('unsigned long') as first parameter
  218 | operator new[](std::size_t __sz, const std::nothrow_t&) _NOEXCEPT _LIBCPP_NOALIAS;
      | ^
/usr/include/c++/v1/new:222:69: error: reference to unresolved using declaration
  222 | _LIBCPP_OVERRIDABLE_FUNC_VIS void operator delete[](void* __p, std::size_t __sz) _NOEXCEPT;
      |                                                                     ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:24:
In file included from /usr/include/c++/v1/__memory/allocation_guard.h:15:
In file included from /usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /usr/include/c++/v1/__memory/construct_at.h:23:
/usr/include/c++/v1/new:227:19: error: reference to unresolved using declaration
  227 | operator new(std::size_t __sz, std::align_val_t) _THROW_BAD_ALLOC;
      |                   ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:24:
In file included from /usr/include/c++/v1/__memory/allocation_guard.h:15:
In file included from /usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /usr/include/c++/v1/__memory/construct_at.h:23:
/usr/include/c++/v1/new:227:1: error: 'operator new' takes type size_t ('unsigned long') as first parameter
  227 | operator new(std::size_t __sz, std::align_val_t) _THROW_BAD_ALLOC;
      | ^
/usr/include/c++/v1/new:229:19: error: reference to unresolved using declaration
  229 | operator new(std::size_t __sz, std::align_val_t, const std::nothrow_t&) _NOEXCEPT _LIBCPP_NOALIAS;
      |                   ^
/usr/include/c++/v1/cstddef:61:1: note: using declaration annotated with 'using_if_exists' here
   61 | using ::size_t _LIBCPP_USING_IF_EXISTS;
      | ^
In file included from /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp:5:
In file included from /usr/local/include/tapa.h:6:
In file included from /usr/local/include/tapa/host/tapa.h:4:
In file included from /usr/local/include/tapa/base/tapa.h:6:
In file included from /usr/local/include/tapa/base/util.h:7:
In file included from /usr/include/c++/v1/ostream:179:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:24:
In file included from /usr/include/c++/v1/__memory/allocation_guard.h:15:
In file included from /usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /usr/include/c++/v1/__memory/construct_at.h:23:
/usr/include/c++/v1/new:229:1: error: 'operator new' takes type size_t ('unsigned long') as first parameter
  229 | operator new(std::size_t __sz, std::align_val_t, const std::nothrow_t&) _NOEXCEPT _LIBCPP_NOALIAS;
      | ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
Error while processing /home/zhenyu/tapa/apps/vadd/run/flatten/flatten-5322dfa0-vadd.cpp.
E0316 04:40:41.632 tapa.steps.analyze:179] command ('/usr/local/bin/tapacc', 'run/flatten/flatten-5322dfa0-vadd.cpp', '-top', 'VecAdd', '--', '-std=c++17', '-I', '/home/zhenyu/.local/lib/python3.8/site-packages/tapa/../../../src', '-stdlib=libc++', '-isystem', '/usr/lib/llvm-17/include/c++/v1/', '-isystem', '/usr/include/clang/17/include/', '-isystem', '/usr/lib/clang/17/include/') failed with exit code 1

How can I solve it?

How did you install TAPA? Since your tapacc is installed under /usr/local/bin/, I think you might be installing from source and need to install Clang 17 manually (sudo bash -c "$(wget -O - https://apt.llvm.org/llvm.sh)" 17 all).

How did you install TAPA? Since your tapacc is installed under /usr/local/bin/, I think you might be installing from source and need to install Clang 17 manually (sudo bash -c "$(wget -O - https://apt.llvm.org/llvm.sh)" 17 all).

I already installed Clang 17

OK I was able to reproduce this problem after installing from source. The problem is indeed with Clang 17 installation; sudo bash -c "$(wget -O - https://apt.llvm.org/llvm.sh)" 17 all is actually install Clang 18 instead of Clang 17 now☹.
@KevinLikesDringCoffe Could you try if sudo bash -c "$(wget -O - https://apt.llvm.org/llvm.sh)" bash 17 all fixes the issue?

The most current TAPA version should have resolved this issue. Please try to install it and see if the problem persists. Note that the tapac interface has been replaced with tapa compile. Most options remain the same. Please refer to the documentation for details.
I am closing this issue now. Please feel free to reopen if the problem still exists in the new versions.


Support for querying Kotling model from custom distribution

Thanks, @donat. For convenience I've submitted my comments as code changes.

Thanks @rodrigo for cleaning up my code and merging the changes!


Hello, does your game engine use react?

nothing

You can take a look at the code for the game here:
https://github.com/mluogh/grontown
It uses React for the UI elements, and Phaser to render sprites/tiles/etc.


Choices not being translated

The choices of selectboxes are currently not being translated.
example:
http://puu.sh/nAgCU/65931864ce.png
while the label for the selectbox gets wrapped in , the options within the selectbox are not being translated.

This should now be fixed, I've done it in a way that does not really depend on this extension, but we rather ship a form_theme with it that can be used for translating boltforms.


Update node.yml

Codecov Report
Patch and project coverage have no change.

Comparison is base (c860fdf) 84.61% compared to head (7c0b9df) 84.61%.
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #29   +/-   ##
=======================================
  Coverage   84.61%   84.61%
=======================================
  Files           2        2
  Lines          52       52
  Branches        7        7
=======================================
  Hits           44       44
  Misses          8        8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Followup to rdar://29684330 to include expected-error comment.

Address thinko in most recent PR #7088 wherein I left out an expected-error comment (and swift-ci let it through because it was an ios-only test, which isn't caught on smoke tests).

@switft-ci please test and merge

@swift-ci please test and merge


RequestOptions.extract has wrong function type.

Hi, @spacejack
In mithril.d.ts#1.0.2 RequestOptions.extract has function which return type seems to be not correct:
extract?: (xhr: XMLHttpRequest, options: RequestOptions<T>) => string;
according to mithril's documentation example it can be not only a string but an object as well:
extract: function(xhr) {return {status: xhr.status, body: xhr.responseText}}
Cheers,
Babur

Doing some additional testing with mithril's request API, it looks like it follows these rules:
If you provide a deserialize callback, you will get the xhr.responseText string and can deserialize it manually.
If you provide an extract callback, you get the XHR object and can do whatever with that. As you say, mithril will not attempt to deserialize the result of that callback.
If you provide extract, then only extract will be used and deserialize will be skipped whether you provide it or not.
So I think this means we can type the result of both deserialize and extract as T rather than any. (If you want any then you can do m.request<any>)(...

Here's a jsbin if you want to experiment.

I've pushed up fixes for this.

cool @spacejack, thanks.


refactor(stories): change import of lucide icons

Closes #3401
Description
I have updated icon imports to fix the deprecated imports.
Current behavior (updates)
It was importing icons as Ghost instead of GhostIcon.
New behavior
It will import using the new names.
Is this a breaking change (Yes/No):
No
Additional Information
N/A

@hirotomoyamada I have resolved conflict, please review again.


Git repo with on-premise TFS

I've set up the xplat agent on a Mac Mini server and succesfully connected it to my on-premise TFS. However, when I run a build that is using a Git repo (TFS hosted Git that is) I'm getting the following output:
preparing Workspace
cwd: /Users/Shared/BuildAgents/Agent1/_work/build/8f606dfb41c4926101422d0198a9c955169bafb520042a138beeaec27c5ce25f
srcVersion: 8ed6808d0ef4b950182ffb3c6513dbd87fc2c1df
srcBranch: refs/heads/master
selectedRef: 8ed6808d0ef4b950182ffb3c6513dbd87fc2c1df
Using auth scheme: OAuth
Repo: http://zeustfs02:8080/tfs/DefaultCollection/WMS%20Git/_git/DeVries.WMS.Analytics
Repo path: /Users/Shared/BuildAgents/Agent1/_work/build/8f606dfb41c4926101422d0198a9c955169bafb520042a138beeaec27c5ce25f/repo
Using ref: 8ed6808d0ef4b950182ffb3c6513dbd87fc2c1df
repo location:http://zeustfs02:8080/tfs/DefaultCollection/WMS%20Git/_git/DeVries.WMS.Analytics
cwd: /Users/Shared/BuildAgents/Agent1/_work/build/8f606dfb41c4926101422d0198a9c955169bafb520042a138beeaec27c5ce25f
running: git --version
git version 2.3.2 (Apple Git-55)

+++++++Git clone http://zeustfs02:8080/tfs/DefaultCollection/WMS%20Git/_git/DeVries.WMS.Analytics
Cloning into folder: repo
running: git clone --progress http://zeustfs02:8080/tfs/DefaultCollection/WMS%20Git/_git/DeVries.WMS.Analytics repo
Cloning into 'repo'...
fatal: Authentication failed for 'http://zeustfs02:8080/tfs/DefaultCollection/WMS%20Git/_git/DeVries.WMS.Analytics/'

Seems that it is unable to authenticate to my TFS server. Is this unsupported?

I've managed to get this to work by manually cloning the repository on the build agent and making sure that git stored the credentials in the OSX keychain. I guess that's good enough for now, but it would be nice it it could just use the credentials I've already provided when I ran the agent.

This is a general issue we are working on with respect to OSX. Apple includes the osxkeychain cred helper with their git implementation and it always gets called regardless of what we pass on the command line.

We actually do implement a cred helper (and askpass) and do supply the creds passed down from the server.  But, apple (and some others) put a plug-in in git-core directory so it's always run and runs ahead of asking us.

but it would be nice it it could just use the credentials I've already provided when I ran the agent.

Note that when this gets worked out, it's not your creds - those are just creds to connect to the queue.  Our build server generates an oauth token on demand that's time bombed and passed down with the job request to the agent.  This is how the scope on the general tab works.  And this is the problem with the keychain caching and getting in front of us - it's cached and it may be an expired token when it runs again.
We're working on a solution where we always use the oauth token when working with the server (clone, push, etc...)

This is fixed.  the latest 0.2.26 agent and beyond uses the OAuth generated token regardless of what your run the agent as


I want to use starrocks manager, but I don't know where to download it

General Question

hi,I want to use starrocks manager, but I don't know where to download it

https://docs.starrocks.io/en-us/2.4/administration/stargo


fix(issue-reports): Remove encoded solution

Pre-Submission Checklist

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

Type of Change

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

Checklist:

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

Description

This commit removes the encoded solution from the URI to make issue submission cleaner.

@systimotic nope, that's a different topic. It relates to how challenge solutions are encoded and evaluated in browsers.
My PR addresses the GitHub Issue requests that are created from the Report Bug button, often campers reporting from the interface end up with issues that have huge URL in the description making it messy for everyone to understand.
This is not required because the code from the editor is taken into the body anyway.
My PR removes the same from the URL to the challenge. Hopefuly making it cleaner.

Fair enough. My reasoning was that if the code is removed from the URL in general, we can send the full URL again.
I do quite like the way it is right now, but I could see why you would want to remove it, as it breaks often, which is really annoying.
On Tue, Nov 29, 2016 at 11:23 PM +0100, "Mrugesh Mohapatra" <notifications<EMAIL_ADDRESS>wrote:
@systimotichttps://github.com/systimotic nope, that's a different topic. It relates to how challenge solutions are encoded and evaluated in browsers.
My PR addresses the GitHub Issue requests that are created from the Report Bug button, often campers reporting from the interface end up with issues that have huge URL in the description making it messy for everyone to understand.
This is not required because the code from the editor is taken into the body anyway.
My PR removes the same from the URL to the challenge. Hopefuly making it cleaner.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/FreeCodeCamp/FreeCodeCamp/pull/11863#issuecomment-263718906, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG7PV0-zc0qutMAY30-Pxj8frIWdApr7ks5rDKW2gaJpZM4K_WZJ.

There is no encoded solution in the URI now with react.
This is the output for the issue template from staging

Challenge [say-hello-to-html-elements](http://localhost:3000/en/challenges/html5-and-css/say-hello-to-html-elements) has an issue.

There is no encoded solution in the URI now with react.

Agreed, but this does not count already constructed URLs in the Camper's profiles. Although really rare if someone would report after visiting a solution, yet this is a safety and the former logic of using href is not needed any longer.
my two cents.

Closing this request in favor of pushing this against backup/master. We are getting very frequent issues with URLs that aren't parsed by GitHub correctly.


New help window

This PR replaces the help window with links pointing to the repository and online documentation.
While it was nice to have a documentation built into CACE, the online documentation has many benefits:

It's easier to navigate
You can have multiple tabs open at once
The documentation can fully utilize Markdown
We don't have to sync offline and online documentation anymore
Less code to maintain
Also possible to host offline

Note: Merge #45 first, then I will rebase this PR Rebased.

This is what the Help Window looks like now:

It contains the version string, a short description and links to the repository and the documentation.


Make jump.js a11y option available in config

Hello.
I wanted to access the a11y option in jump.js from within your react component. I've set it to false as default.
Could you take a look whenever you get some time, see if it's something you want to include?
Thanks
Dave

Sorry for the delay. So, I prefer not to add the a11y option. I think accessibility is great, but I'm not a big fan of the a11y functionality implemented in jump.js. Adding tabIndex = -1 to an arbitrary element can mess up the tab order of the page elements. It makes sense if adding to something like a . However, if someone adds it to an already focusable element, the result can be bad for accessibility. Therefore, I'd rather keep a11y concerns separate and up to the person implementing the page.
Let me know if I'm misunderstanding something that you have a better handle on. I'm no expert in a11y.


docs(angular.injector): improved clarity of docs

Thanks for the PR!I added a note how this could be improved slightly. We also need you to sign the CLA before we can merge.


Algolia Search Toggle Issue

[ ] This is a question about using the theme.
[ ] This is a feature request or enhancement.
[x] I believe this to be a bug with the theme.
[x] I am using the latest version of the theme.
[x] I have updated all gems with bundle update.
[x] I have tested locally with bundle exec jekyll build.

Environment informations

Minimal Mistakes version:  4.10.1
Jekyll version: latest -pulled from docker
GitHub Pages hosted: no
Operating system: Windows 10

Expected behavior
When I click on search button, I expect the algolia search box to display AND the focus to be on the textbox to allow typing. The issue is no focus is set on Algolia search. I'm not sure what I could have included that would change this behavior as your demo page works and sets focus correctly.
Steps to reproduce the behavior
Production Site with Search enabled
I've tested a local updated build just now and the same behavior is happening.

You sure you have the latest version of the theme and its assets (JS, CSS, etc.)? This was fixed in https://github.com/mmistakes/minimal-mistakes/commit/356c1eb0937ab514bda35662afb656e3c06fdeca
Hitting the search icon toggles the Algolia search box and focuses on it for the demo site... which is using the latest version of the theme.

Closing as you haven't upgraded to the latest version of the theme. Your main.min.js is still using 4.9.0...
Update that to latest.

Thank you I converted over to the ruby gem approach and thought I had cleared out all contents required. I'll remove those culprits. Thanks for the quick help.

@mmistakes if you get a sec would you mind telling me if I'm doing some obviously wrong with this again? It's not working and I've spent hours trying to fix.
I've verified my

main.min.js is up to date
my theme is up to date
algolia is running the latest
the index was built
no console errors noted
the javascript files seem to be loaded when examining in chrome dev tools

Not sure why the button won't click! It's like I messed up something with the javascript, though I searched my entire repo (using remote gem) and couldn't find any code for search or algolia that might be in there.
If you have any ideas I'd appreciate it as I've sunk a lot of time in it, and I'm guessing it's something very simple I'm just clueless on.

Whatever you modified, you also removed main.min.js from being included in the page. You need to load that script.
Without it, it's not going to toggle the search bar when you click the icon. That's why it's not doing anything for you.

I can see the divs that have the search input and they work. If you can sort out adding back in the theme's main.min.js script to toggle them, search works fine.

Thank you so much! I will figure out why it's missing. That's the help I needed. Much appreciated

I'm using remote theme and in your documentation I think it points towards this being included in the remote theme. Any tip on why I would be having an issue when I'm not providing that file in the first place? I thought I saw the reference as a resource in the header.

Found it!
Could you consider making the documentation put WARNING notice on the following content:

Site scripts
Add scripts to the  or closing  elements by assigning paths to either head_scripts and/or footer_scripts.
For example, to add a CDN version of jQuery to page’s head along with a custom script you’d do the following:
https://mmistakes.github.io/minimal-mistakes/docs/configuration/#site-scripts

Per the following content I found in: https://github.com/mmistakes/minimal-mistakes/blob/22a9c523d6be13becc6fe0ed38b065e3489e498f/docs/_docs/17-javascript.md

Note: If you assign footer_scripts the theme's /assets/js/main.min.js file will be deactivated. This script includes jQuery and various other plugins that you'll need to find replacements for and include separately. {: .notice--warning}

I used that section as a reference and only now in searching the repo found out that the footer deactivates the main.min.js
Thanks again! Glad I finally have the solution after all this troubleshooting.


Package proposal: jd-gui.vm

Package Name
jd-gui
Tool Name
jd-gui
Package type
GITHUB_REPO
Is the tool a console application?
false
Tool's version number
1.6.6
Category
Disassemblers
Tool's authors
java-decompiler
Tool's description
JD-GUI, a standalone graphical utility that displays Java sources from CLASS files.
Download URL
https://github.com/java-decompiler/jd-gui/releases/download/v1.6.6/jd-gui-windows-1.6.6.zip
Download SHA256 Hash
79c231399d3d39d14fce7607728336acb47a6e02e9e1c5f2fa16e2450c0c46cb
Why is this tool a good addition?
for Commando

Note that we already have a bytecodeviewer package which includes the jd-gui decompiler.

@mr-tz my bad. Thanks for pointing this out.


feedback form add

made changes and created the feedback form again using modal class.
now i have encapsulated the entire js into one single function to avoid any kind of conflict.
please tell if you want any modifications.
thankyou.

issue #148


The signature problem on Integrating with Ceramic

Description
I'm trying to approve for Lit Protocol and Ceramic with just one signature. I've managed to do so, but there might be some issues with my solution. I'll describe my problems here and discuss if there's a better approach, or whether it's possible to optimize the code of Lit or Ceramic to better address these issues.
Technical Information
My approach is as follows: first, I call Ceramic's authorization, with the code as below:
const accountId = await getAccountId(ethProvider, address)

const authMethod = await getAuthMethod(ethProvider, accountId)
console.log("[AuthCeramic] Authorize", authMethod)

session = await DIDSession.authorize(authMethod, {resources: ["ceramic://*"]})

After the user signs, they get a session as a login credential.
In Lit Protocol, similar to session, there's a data structure called AuthSig as a login credential. The structure of AuthSig is as follows:
interface AuthSig {
    sig: any; // Data after signing
    derivedVia: string; // Generally "web3.eth.personal.sign"
    signedMessage: string; // Data before signing
    address: string; // Signing address
}

Actually, session and AuthSig are somewhat interchangeable to a certain extent. Below is my conversion code:
async function getAuthSig(session, chainId = TargetChainId) {
  const {p, s} = session.cacao;
  const address = p.iss.split(":").pop();

  const message = new SiweMessage({
    domain: p.domain, address,
    statement: p.statement,
    uri: p.aud,
    version: p.version,
    nonce: p.nonce,
    issuedAt: p.iat,
    expirationTime: p.exp,
    chainId: chainId.toString(),
    resources: p.resources,
  })

  return {
    address, derivedVia: "web3.eth.personal.sign",
    sig: s.s, signedMessage: message.toMessage(),
  } as AuthSig
}

Therefore, we can convert the session obtained after authorizing Ceramic into AuthSig and set it in LocalStorage, to authorize Lit:
const LitAuthSigKey = "lit-auth-signature"
const LitProviderKey = "lit-web3-provider"
const LitDefaultProvider = "metamask"

if (authSig) { // Set the default authSig in advance to avoid reconnecting and re-signing
  setLocalStorage(LitProviderKey, LitDefaultProvider)
  setLocalStorage(LitAuthSigKey, authSig)
}
authSig = await LitJsSdk.checkAndSignAuthMessage({
  chain: Chain
});

// Do some encryption/decryptions ....
const res = await LitJsSdk.decryptToString({
  authSig, chain: Chain, ...
}, lit)

This is my approach.
Solution Problem
There's a problem with the above solution, which is the issue of case sensitivity in the address in the signature information.
In the signature information of Ceramic, the address is converted to lowercase, here's an example:
localhost wants you to sign in with your Ethereum account:
0x66d369e52b1a7ee16.......f84025

Give this application access to some of your data on Ceramic

URI: did:key:z6Mkofcp......pnsDJ26j
Version: 1
Chain ID: 1
Nonce: 1CjSZZjMv2
Issued At: 2023-11-15T08:13:19.690Z
Expiration Time: 2023-11-22T08:13:19.690Z
Resources:
- ceramic://*

However, when we convert this signature into AuthSig and authenticate it in Lit, it says that the address does not conform to the EIP-55 format:

And this is the request data:

Therefore, I have to insert the following statement in the first section of the code to ensure that the address in the signature information is in EIP-55 format:
const accountId = await getAccountId(ethProvider, address)
accountId.address = address // Prevent the lowercase address

Only then can I successfully authorize Lit.
But after converting to EIP-55, the generated PKH-DID looks like this: did:pkh:eip155:1:0x66d369E52b1A7ee16D65e6a052745561C1f84025, which contains case sensitivity, and that's the problem:

If I keep the address lowercase, the generated DID is normal and conforms to the rules, but Lit cannot be successfully authorized.
If I retain the case sensitivity, I can successfully authorize Lit, but the generated DID will also retain the case sensitivity, but it seems to be able to be used normally in Ceramic.

Therefore, I wonder if there is a better solution, or whether it's possible to make some modifications to Ceramic or Lit to solve this problem?
I have also opened the same issue in Ceramic: https://github.com/ceramicnetwork/js-did/issues/173

for anyone who finds this in the future. check out the above linked thread on the Ceramic repo for our discussion about this issue


go.mod: update "x/crypto" to support latest acme API

Let's encrypt doesn't work with the old acme API anymore. The latest version of "x/crypto" fixes that.
Error messages:
acme/autocert: missing certificate
403 urn:acme:error:unauthorized: Error creating new authz :: Validations for new domains are disabled in the V1 API (https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430)

See:https://go-review.googlesource.com/c/crypto/+/200638
I ran go get -u golang.org/x/crypto to update the module. Tests pass with devcam and my server got Let's Encrypt working again.

Thanks!

I notice this PR got merged even though it does not update the vendor directory. Are we giving up on keeping the go.mod and the vendor directory in sync?


Duplicate discover not working

Hello,
I use function noble.startScanning([],true) to discover peripherals with duplicate option, but it call the discover callback only first time, also disconnect the connected peripheral
This function works on my computer but doesnt work on my friend computer, both have Ubuntu 14.04 installed. My Raspberry Pi with Raspbian also doesnt work.

@duyhotan2000 does sudo hcitool lescan --duplicates work?
Are you both using the same USB Bluetooth 4.0 adapter? What about kernel version?

On my computer and my friend's both installed Ubuntu 14.04 with Linux 3.12 kernel.
My computer works fine on built-in Atheros bluetooth adapter, and my friend's adapter is built-in Broadcom chipset
On the Raspberry Pi I use iBuffalo adapter with Cambridge Silicon Radio chipset with latest 3.18 kernel. When I run 'sudo hcitool lescan --duplicates' and without '--duplicates', it has the same output (definitely print out the device, my SensorTag). But on my computer with Atheros and Ubuntu, it prints only 1 time (without '--duplicates')

Please help me!

@duyhotan2000 have you tried an alternative Bluetooth 4.0 USB adapter? Have you tried the CSR on your Ubuntu computer?
This looks more like a kernel/driver/hardware issue than a noble issue, as hcitool is producing the same behaviour.

WIth build-in adapter on my computer, when I use kernel 3.13 it's work well, but not with newer kernel
On my RPi, it looks like a issue with my CSR adapter, which dont work with my Ubuntu computer
Thanks for your answer!

@duyhotan2000 no problem. I'm closing as it's not an issue with noble ...

Is noble tested with Raspbian and can you tell me the kernel version and bluez you used?

@duyhotan2000 Rasbian, BlueZ 4.99.
pi@raspberrypi ~ $ uname -a
Linux raspberrypi 3.18.11+ #781 PREEMPT Tue Apr 21 18:02:18 BST 2015 armv6l GNU/Linux

pi@raspberrypi ~ $ lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 005: ID 0a5c:21e8 Broadcom Corp.

Thank you so much! I gotta buy a Broadcom chipset adapter (Pluggable BT4LE)
Noble is a great module. I used it for my graduate thesis.

@duyhotan2000 sounds good! You can also try out these adapters: https://github.com/sandeepmistry/noble/wiki/Compatible-devices#linux
Is your graduate thesis online? I'd love to take a look at it if it is ...

I have just uploaded my project to github https://github.com/duyhotan2000/BLEGateway
You can run it by command "node main-server.js" and browse "localhost:8081" with user: admin, pass: admin

@sandeepmistry I have bought a Plugable dongle and it works well on Raspberry Pi with 3.13 kernel, but not with latest 3.18 kernel. It can only connect to one peripheral at a time. Please help me!

@duyhotan2000 I'm away from home currently, but I believe no issues with the 3.18 kernel and multiple connections.
Please open a new issue for this, as it is unrelated to the original topic. Also, the results for scanning via hcitool while attempting to connect to multiple devices manually using gatttool just to rule out noble vs the kernel.


Fail to run master/agent under gcc 7.1.0 in centos 7

By following the instruction of DtCraft Distributed Mode (Single Host),
I tried to run bin/master and bin/agent, however, it crashed.
$ ./master
terminate called after throwing an instance of 'std::system_error'
what():  unshare failed: Invalid argument
Abort (core dumped)

Could you use uname -r to check  the Linux kernel version of your machine?

Linux 3.10.0-514.21.1.el7.x86_64, is this kernel too old? I can run examples without any problems.

To run under distributed mode, the required Linux kernel version should be at least 3.8 or higher.

I guess my kernel version is higher than 3.8?

I'll manually enable user namespace and see if this solve this problem.

Problem solve using
$ grubby --args="user_namespace.enable=1" --update-kernel="$(grubby --default-kernel)"
$ reboot
In centos 7, user namespace is a technology preview feature.

This is due to the setup of Linux container in DtCraft. We require "user namespace" to be enabled by your OS.


runtime: signal handling: runtime bypasses TSAN/MSAN sigaction interceptors

go version devel +09bb643 Wed Nov 2 20:49:58 2016 +0000 linux/amd64
What did you do?
$ cat tsan8.go

package main

/*
#cgo CFLAGS: -fsanitize=thread
#cgo LDFLAGS: -fsanitize=thread

#include <signal.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>

struct sigaction prev_sa;

void forwardSignal(int signo, siginfo_t *info, void *context) {
	// One of sa_sigaction and/or sa_handler
	if ((prev_sa.sa_flags&SA_SIGINFO) != 0) {
		prev_sa.sa_sigaction(signo, info, context);
		return;
	}
	if (prev_sa.sa_handler != SIG_IGN && prev_sa.sa_handler != SIG_DFL) {
		prev_sa.sa_handler(signo);
		return;
	}

	fprintf(stderr, "No Go handler to forward to!\n");
	abort();
}

void registerSegvFowarder() {
	struct sigaction sa;
	memset(&sa, 0, sizeof(sa));
	sigemptyset(&sa.sa_mask);
	sa.sa_flags = SA_SIGINFO | SA_ONSTACK;
	sa.sa_sigaction = forwardSignal;

	if (sigaction(SIGSEGV, &sa, &prev_sa) != 0) {
		perror("failed to register SEGV forwarder");
		exit(EXIT_FAILURE);
	}
}
*/
import "C"

func main() {
	C.registerSegvFowarder()

	defer func() {
		recover()
	}()
	var nilp *int
	*nilp = 42
}

$ CC=/usr/lib/llvm-3.8/bin/clang go run tsan8.go

What did you expect to see?
The test should pass (as it does without the -fsanitize=thread flags).
What did you see instead?
$ CC=/usr/lib/llvm-3.8/bin/clang go run tsan8.go
No Go handler to forward to!
SIGABRT: abort
PC=0x7f4b364cfc37 m=0

goroutine 1 [running]:

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
        /usr/lib/google-golang/src/runtime/asm_amd64.s:2086 +0x1

rax    0x0
rbx    0x0
rcx    0xffffffffffffffff
rdx    0x6
rdi    0x7436
rsi    0x7436
rbp    0xb
rsp    0xc420009948
r8     0x7f4b375a1440
r9     0x524e23
r10    0x8
r11    0x206
r12    0xc
r13    0x7f4b375387c0
r14    0xc420009bc0
r15    0xc420009cf0
rip    0x7f4b364cfc37
rflags 0x206
cs     0x33
fs     0x0
gs     0x0
exit status 2

It appears that TSAN and MSAN replace the libc sigaction function with their own versions, and when sigaction is called they return the remembered struct sigaction previously passed to the libc function rather than calling all the way down to the OS.
One possible fix would be to make TSAN and MSAN make a real sigaction syscall to verify the actual handler before returning the cached one.
Another would be to make the Go runtime use the libc sigaction function (instead of making the system call directly from Go) when the sanitizers are in use (e.g. as we do today for mmap via x_cgo_mmap).

@ianlancetaylor @dvyukov

Thinking about this some more, I think the right fix is to do something along the lines of x_cgo_mmap so that the Go runtime calls through the *SAN clib interceptors when they're present.
Here's my reasoning: I expect that a lot of Go users have more control over which Go version they're using than over their C compiler, and it's easier to build a fresh-from-source Go toolchain than a fresh-from-source C toolchain if they're in an environment that tends to significantly lag upstream releases.  Hooking the runtime potentially fixes it across all C toolchains in a way that Go users can control more easily.

Sounds good to me.

I agree that routing through the C library sigaction is probably correct for cgo programs.
Note: on GNU/Linux the sigaction library function fails with EINVAL for any attempt to do anything with signals 32 and 33.  I think we mostly ignore the return value of sigaction anyhow so that may not matter.

I'm wondering about the general question of how many syscalls should
a cgo program uses the libc version and not calling the syscall directly.
for example, I remember there is (was) an issue about making transparent
socks proxy work by using libc socket functions rather than issuing syscall
directly.
Where should we draw the line?

@minux One point to draw the line would be between "bug" and "feature".  The sigaction libc call is needed to avoid crashes in otherwise-correct programs compiled with -fsanitize=thread, whereas the socket functions only enable a feature (SOCKS proxying) that can be obtained in other ways.

Is someone going to work on this for Go 1.8?
If not let's move it to the Go 1.9 milestone.
Thanks.

I've got a change pending, but I've hit a couple snags during testing.  (I may need some help sorting out a bad interaction between systemstack, //go:nosplit, and anonymous functions.)


SNBT Boolean Keywords

I guess I forgot to mention this is moreso related to #37, so this is specific to that. I think I was starting to get tired when I added these to the repo last night.


Does this library work with Access Point only

If I have no internet connection or router, just a smart plug connected to an ESP32 configured as AP only, will this code detect correctly smart plug?

I never tried but it should work if you connect the KASA smart plug to ESP32  AP.


add the debug flag and the local url string

you can merge.

Merging now to reduce latency/blockage.


Calling get_formatters() returns empty table if load_associations_async() isn't done yet

Hi, thank you for this really useful plugin.
I did find a small bug: If load_associations_async is not done by the time get_formatters is called, you get an empty table, which is probably due to cached_associations not being set yet.
I worked around this by creating a blocking variant load_associations. IMHO it would be nice to let get_formatters block until a result is available (no idea how to do that), or to just add a configuration option.

Thank you for your feedback! I've pushed an updated to a new branch called fix_async where it waits for the cached_associations to load before it returns anything. Could you check if that solves your issues?

Yes! Thank you!


Feature Request: Mechanism to refer this as a library from our Rust codebase and call as part of cargo test

Since this is written in Rust, I believe the internal modules could be decoupled to be called by this CLI and be used from a Rust codebase as an integration testing framework.
That way we can write tests in our Rust codebase and co-located with our application code but with a #[cfg(test)] so that tests get run within their own binary like how native Rust tests are supposed to run and then our application code gets only compiled to wasm canisters as intended.
@chenyan-dfinity @chenyan2002 Thoughts?

Sure. But if you want to run canister tests in Rust, I recommend you to try the ic-state-machine-tests, which is much faster than ic-repl. See this example: https://github.com/dfinity/cdk-rs/blob/main/e2e-tests/tests/e2e.rs


DirectDeque supports constant time access to any element in the structure

This is starting to look much better.
I'd suggest extending Traversable and adding a foreach method. Then the tests can have assertions like assert (deque == Seq (1, 2, 3))

extends Traversable[M]
....
def foreach[U](f: M => U) {
for (i <- 0 to size-1) {
f(get(i))
}
}
I had to add the override modifier to size and isEmpty.
Now when I run assert (deque == Seq(1)) it complains that DirectDeque(1) did not equal List(1)

Of course. It should be deque.toSeq == Seq (1).

Also, to test get, you could do something like:
assert (Seq.tabulate (deque.size) (deque.get (_)) == Seq (...))

In fact, that may be a better approach than extending Traversable.

with this approach can I check two things while I'm tabulating? I want to check both the get sequence and that the size does not change for every get. But this may not actually be necessary to check. I could just do a final assert at the end to check no size change.

actually if size was changing then it would not correctly produce Seq (....) so I think that check is enough


⚠ Bofrost.hr has degraded performance

In 764fe09, Bofrost.hr (https://www.bofrost.hr) experienced degraded performance:

HTTP code: 200
Response time: 4289 ms

Resolved: Bofrost.hr performance has improved in d424b7b after 1 day, 9 minutes.


feat: create svg css sprites

supersedes #235

We'll need to move a few dependencies to dev dependencies to inline cac, colorette, consola and  unconfig, I guess it is fine.
I'll try to test both packages using pnpm pack  and install utils and  utils-cli via file: protocol.

Converting to draft, adding tests...

Closing this PR, see https://github.com/unocss/unocss/pull/2675#issuecomment-1683721033


hands-on evaluation of updated AAD MS Authenticator settings in Authentication Methods

💡 Summary
Microsoft has updated the MS Authenticator security settings available in the Azure AD Authentication Methods page #295. The baseline must be updated to align with the revised settings and ScubaGear must be aligned as well. The scope of this issue is to perform a hands-on evaluation of the revised features to understand their impacts to the baseline and ensure we provide accurate, relevant instructions/policies.
Implementation notes

[x] In the AAD portal, set the value for the three new MS Authenticator context features to Enabled (see list below).
[x] Login to the tenant as a test user that is registered with an MS Authenticator device for Push notifications. Document notes on any impact to the baseline.
[x] Repeat the previous step but test Passwordless.
[x] Ensure that the Number Matching feature is on by default and verify that it cannot be turned off. This can be tested after May 8 when Microsoft stated it will be turned on for all tenants.
[x] Test these steps on G5, E5, G3, GCCHigh

The three new context features are:

Show application name in push and passwordless notifications
Show geographic location in push and passwordless notifications
Microsoft Authenticator on companion applications

Screenshots

Test results
I tested the new Microsoft Authenticator "context" features when performing Passwordless MFA (aka phone sign-in) with the mobile app. Here are my results.
The tenant was configured to "Show application name in push and passwordless notifications" and "Show geographic location in push and passwordless notifications" - both set to Enabled. "Require number matching for push notifications" was disabled.

The authenticator app required number matching even though I had it disabled. This confirms that Microsoft has now made this a standard and it cannot be turned off.
The application name and geographic location context features worked as expected. These features make it even harder to perform MFA fatigue attacks.

I will open a separate issue to inquire if CISA wants to include these features as new policies to help secure Microsoft Authenticator implementations.

Technical implementation ScubaGear
To get the authentication configuration data on MS Authenticator from the tenant, use the Cmdlet below. This would be a new policy in the baseline and ScubaGear.
(Get-MgPolicyAuthenticationMethodPolicy).AuthenticationMethodConfigurations | ConvertTo-Json -Depth 5 > ted.json


Release 0.2.0

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.77%. Comparing base (0dc29fb) to head (51816a5).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #22   +/-   ##
=======================================
  Coverage   98.77%   98.77%
=======================================
  Files           8        8
  Lines        3605     3605
=======================================
  Hits         3561     3561
  Misses         44       44

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Custom samplingPeriod doesn't work on Android

Platform
Android 13
Plugin
sensors_plus
Version
4.0.1
Flutter SDK
3.16.1
Steps to reproduce
Hi,
In a simple flutter app, just run the code sample.
It works fine on IOS, the message "Event received" is logged every 4 seconds.
On Android however, it seems like the samplingPeriod is always blocked at ~0.5 second (approximately).
Regards,
Code Sample
accelerometerEventStream(samplingPeriod: const Duration(seconds: 4))
            .listen((event) {
          print("Event received");
        });

Logs
No exceptions/errors were logged.

Flutter Doctor
[✓] Flutter (Channel stable, 3.16.1, on macOS 14.1.2 23B92 darwin-arm64, locale en-FR)
    • Flutter version 3.16.1 on channel stable at /Users/clem/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7f20e5d18c (11 days ago), 2023-11-27 09:47:30 -0800
    • Engine revision 22b600f240
    • Dart version 3.2.1
    • DevTools version 2.28.3

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/clementpalfroy/Library/Android/sdk/
    • Platform android-33, build-tools 33.0.0
    • ANDROID_HOME = /Users/clem/Library/Android/sdk/
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.84.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.78.0

[✓] Connected device (3 available)
    • iPhone de Clément (mobile) • 00008030-000259AA0E01802E • ios            • iOS 17.1.2 21B101
    • macOS (desktop)            • macos                     • darwin-arm64   • macOS 14.1.2 23B92 darwin-arm64
    • Chrome (web)               • chrome                    • web-javascript • Google Chrome 120.0.6099.71

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Checklist before submitting a bug

[X] I searched issues in this repository and couldn't find such bug/problem
[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I'm using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

Please read the documentation first. It is explicitly mentioned there that it is not guaranteed on Android that the specified sampling rate will be applied. It is considered by the Android OS as a recommendation.
https://plus.fluttercommunity.dev/docs/sensors_plus/usage
So it is really up to a device that you use as during testing of this feature I noticed that on some Samsung devices sampling rate behaved differently compared to Pixel devices.

My bad, it was properly highlighted and I should not have missed it.
Thanks @vbuberen!

Thanks to you as well. I will add this note to README as well for better visibility as your case showed that having on website only is not enough.