Some advice as to how to use this bucket, please

Say I install a np program in the normal way in scoop. Windows 10 Pro.
I then have two folders under scoop/apps: one with the version number, the other "current".
Each contains a setup.exe file.

Do I run the .exe (as administrator) as I would if I had downloaded a program outside scoop?

Which do I open? Current? The version-number one?

Where will the app be installed? Program Files? Programs Files (x86)?

When the app is installed after running the .exe file, should I/ can I (to save space) delete the .exe file(s)? Which? Both?

How does scoop then (when I run "scoop update-all") work out when the app is updated?

If it does get updated, do I have to run an .exe file again?

Sorry for these utterly n00b questions.
Any help would be appreciated!

Scoop should install the applications automatically. Which app are you trying to install?

To elaborate, applications in this bucket are often installed to the Program Files or Program Files (x86) directory, but it depends on the installer for each application, and some will be installed in the designated Scoop directory. scoop update * will automatically update all installed applications. current is simply a directory junction to the latest version, so it doesn't really matter which one you enter, but current always points to the latest version.

Thanks. It was logitech-gaming-software-np, which admittedly was already installed in Program Files by a non-scoop method - and I failed to uninstall it first, before going the scoop way.
(Fairly new to this!)
There's my point 4 above: what to do with the two setup.exe files, in version-number and current? Leave them? Delete? (I'm manic about housekeeping of unnecessary biggish files, but maybe these need to stay?)
Thanks!

They're there so Scoop can uninstall the applications easily. They'll be downloaded again once an update is released, so it's up to you.

Thanks indeed. Happy for you to close this off now!


[Bug]: Create a new ODP sharding mysql data source entrance is not closed

ODC version
4.2.2
OB version
all
What happened?

What did you expect to happen?
Create a new ODP sharding mysql data source entrance is closed
How can we reproduce it (as minimally and precisely as possible)?
Click on creating new Data Source
Anything else we need to know?
No response
Cloud
No response

done

pass


Developing eval_utils module

Because
As a reformat task, and for future development of more evaluations, it should be considered if a common evaluation utilities module should be created.
-[ ] where should that module reside? Should it be a subsection of the clams_utils?
That module could contain commonly used code such as:

goldretriever
data extraction/preprocessing from golds and preds
guid/file matching between golds and preds.
common accuracy metrics
etc

Note, not every evaluation will be similar, and thus some may use different metrics. As such, its likely that printing is unlikely to be universal enough for modulization.
The environment for CLAMS so far seems to require:
clams-python
mmif-python
and now
clams_utils for goldretriever, which is used in each eval, and in the annotation for NEL. The goldretriever code seems to be commonly used.
Is it better to place certain codes in utilities? What is the organizational method?
Done when
No response
Additional context
No response

Also related to #41, I think the most straightforward way of doing this will be providing a PyPI distro (clams-aapb-eval package hereinafter, working name for now) that includes all the utility modules and Evaluator superclass (ABC), so that evaluator developers can just pip-install and start writing. Then, conveniently, since I already set up clams-utils repo for daily PyPI release, I'm very tempted to use that to hold an additional clams-aapb-eval package . But there could be some issues with that approach, namely;

there's no inherit linkage between this repo and clams-utils repo, so we need a very clear documentation for this arbitrary use of separate repositories. As I stated also in https://github.com/clamsproject/clams-python/issues/147, I don't like this arbitrariness / segregation of clearly related components.
I'm not seeing a big chance that parts of clams-aapb-eval package is commonly used in other part of the whole clamsproject. Hence ,no need to "factorize" the eval package.
clams-utils is auto-released every day. If there's any problem in, for example, the clams.utils.aapb.eval package, even if it's a very minor bug, it will take time to do the fix and propagate the fix over PyPI.

Combining the above reasons, I firmly believe the package should reside in this repository. This will imply

we put a aapb_eval package in the project root
all other evaluator subdirectories should now be python packages (__init__.py)
all invocations of the evalute.pys should now through python -m subdir.evaluate <more> <flags> <as> <defined>
when evaluator developer found an issue with the superclass, they can directly mend and push the fix

Conversation of where this repo is to be placed had two different outcomes,
can the comments above this be reviewed and updated plus any other details
of this development?
On Mon, Jan 29, 2024 at 11:51 AM Keigh Rim @.***> wrote:

Assigned #42 https://github.com/clamsproject/aapb-evaluations/issues/42
to @jarumihooi https://github.com/jarumihooi.
—
Reply to this email directly, view it on GitHub
https://github.com/clamsproject/aapb-evaluations/issues/42#event-11630563773,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHUBDVULEDP6DHK3GO6253YQ7HRPAVCNFSM6AAAAABA7L244CVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGYZTANJWGM3TOMY
.
You are receiving this because you were assigned.Message ID:
@.***
com>

Conversation of where this repo is to be placed had two different outcomes,

I don't think I follow this. This repo doesn't go anywhere else...?


Conceptualize and propose key harvesting operation steps: Propose top 3 workflow management systems to evaluate

Team discussed on 4/11 that we will plan to evaluate: Airflow, Temporal, and AWS Step. This evaluation will take place during the next sprint (Sprint 12) and will be balanced and ranked against our requirements.


[Serverless Mini Agent] Add Azure App Service Span Tags

What does this PR do?
Adds aas.* span tags to all spans submitted from Azure Functions.
Motivation
https://datadoghq.atlassian.net/browse/SVLS-4920
Allows for proper billing of Azure Functions and for traces to be correlated for the app on the Azure tab of the Serverless page.
Additional Notes

Reused azure_app_services in ddcommon to build these span tags

Changes are backwards compatible with the profiling package that currently uses azure_app_services by creating get_function_metadata which has Azure Function specific logic. get_metadata expects the DD_AZURE_APP_SERVICES environment variable to be set to true, which only occurs when the Datadog Extension for Windows is installed

https://github.com/DataDog/libdatadog/blob/ebe9a6a502a03b32d06b108b19cb3048c339b85a/profiling/src/exporter/mod.rs#L18

Operating system now falls back to std::env::consts::OS.to_string() if WEBSITE_OS environment variable is not set
Resource group now falls back to being parsed from the WEBSITE_ONWER_NAME environment variable if WEBSITE_RESOURCE_GROUP is not set (Azure Functions on Consumption plans only)
Added mini_agent_version property to mini agent config to surface in a span tag

Value from CARGO_PKG_VERSION environment variable

How to test the change?

Build mini agent locally
Deploy Azure Function with mini agent binary in root path
Set DD_MINI_AGENT_PATH to /home/site/wwwroot/datadog-serverless-trace-mini-agent

Codecov Report
Attention: Patch coverage is 66.66667% with 26 lines in your changes are missing coverage. Please review.

Project coverage is 68.53%. Comparing base (de8d3b6) to head (e86275f).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #463      +/-   ##
==========================================
- Coverage   68.56%   68.53%   -0.04%
==========================================
  Files         193      193
  Lines       25086    25148      +62
==========================================
+ Hits        17201    17235      +34
- Misses       7885     7913      +28

Components
Coverage Δ

crashtracker
19.34% <ø> (ø)

datadog-alloc
98.76% <ø> (ø)

data-pipeline
51.45% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
85.28% <93.02%> (+0.03%)
:arrow_up:

ddcommon-ffi
74.15% <ø> (-0.79%)
:arrow_down:

ddtelemetry
56.09% <ø> (ø)

ipc
81.69% <ø> (ø)

profiling
77.97% <ø> (-0.01%)
:arrow_down:

profiling-ffi
60.00% <ø> (-0.06%)
:arrow_down:

serverless
0.00% <ø> (ø)

sidecar
37.75% <ø> (-0.15%)
:arrow_down:

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
54.98% <ø> (ø)

trace-mini-agent
69.33% <100.00%> (+0.21%)
:arrow_up:

trace-normalization
97.79% <ø> (ø)

trace-obfuscation
95.74% <ø> (ø)

trace-protobuf
30.76% <ø> (ø)

trace-utils
88.29% <14.81%> (-1.71%)
:arrow_down:


Added alert labels cannot be used in annotation

What did you do?
When I add a label in an alert via LABELS I would like to be able to use it immediately in the annotation, however that doesn't seem to be possible.
ALERT InstanceDemo
  IF up == 1
  FOR 10s
  LABELS {
    where = "{{ .Labels.instance | toUpper }}",
    severity = "demo" ,
  }
  ANNOTATIONS {
    summary = "Instance {{ $labels.where }} down",
    description = "{{ $labels.where }} of job {{ $labels.job }} has been down for more than 5 minutes.",
  }

What did you expect to see?
I would expect $labels.where in the annotation description to be replaced with the value I just set in the LABELS section.
What did you see instead? Under which circumstances?
It gets replaced with an empty string.
You can see "where" in the list of labels in the output of curl -sg '<prom-url>/api/v1/query?query=ALERTS, but the contents posted in the Slack channel is "Instance  down".
Environment

System information:
Linux 4.4.0-83-generic x86_64

Prometheus version:

prometheus, version 1.6.3 (branch: master, revision: c580b60c67f2c5f6b638c3322161bcdf6d68d7fc)
  build user:       root@a6410e65f5c7
  build date:       20170522-09:15:06
  go version:       go1.8.1

Alertmanager version

alertmanager, version 0.6.2 (branch: master, revision: b011c0a32ce887c1a10f7d34d52fd8cce485c1cf)
  build user:       root@e3ca4de32142
  build date:       20170509-08:56:14
  go version:       go1.8.1

Prometheus configuration file:

global:
  scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
  evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
  # scrape_timeout is set to the global default (10s).

  external_labels:
      monitor: 'demo-2454'

rule_files:
  - "alert-demo-2454.rules"

scrape_configs:
  - job_name: 'prometheus'
    static_configs:
      - targets: ['localhost:9091']

alerting:
  alertmanagers:
    - static_configs:
        - targets:
            - localhost:9094

Alertmanager configuration file:

global:
  slack_api_url: https://hooks.slack.com/services/XXXX/YYYY

route:
  receiver: demo-2454

  group_by: ['alertname', 'origin']

  group_wait: 10s

  group_interval: 30s

  # If an alert has successfully been sent, wait 'repeat_interval' to
  # resend them.
  repeat_interval: 1m

receivers:

  - name: demo-2454
    slack_configs:
      - channel: 'alert-testing'
        text: |
          {{ range .Alerts }}
            *Alert:* {{ .Annotations.summary }} - `{{ .Labels.severity }}`
            *Description:* {{ .Annotations.description }}
            *Details:*
            {{ range .Labels.SortedPairs }} • *{{ .Name }}:* `{{ .Value }}`
            {{ end }}
          {{ end }}

This is not supported, nor is it required in this case. You can use .Labels.instance | toUpper  as needed, though I'd recommend sticking with the unmodified instance label.

That's not the minimal case to reproduce, in case that wasn't obvious. The real case is more complicated, but is beside the point here, which is that it would be very useful to use in ANNOTATIONS values that were set in LABELS. Based on the documentation, which says that both can be templated, it was surprising to me that they're totally independent.

This has been discussed previously and there's no way to do it that won't cause confusion. The same argument can be made the other way around, and I don't think we want to try and build a partial ordering across annotations and labels.
If you share your actual use case we may be able to make suggestions/improvements.

Now you say it's been discussed previously, but when I tried to add a point to #2454 you said there that the report is actually about a different use case.
Firstly, the semantics doesn't have to be complicated, or involve partial ordering. E.g., labels are fully defined before annotations are added, and all values defined in LABELS are added at once at the end, so that they are not available except in ANNOTATIONS. (Just like variables defined by let in Lisps.)
The use case in mind is having a phrase constructed from several labels of the original alert, and use it in summary and description annotation. Before you say that these should be added by Prometheus as part of the target label:

sometimes it's really useful to have this alert-related labelling kept as part of the alert rule rather than a job
the templating available to define alert labels is far richer than what can programmatically be done with target labels (where you only have regex rewriting)
creating this more complicated phrase once and attaching it to LABEL means I can just reference it in every other annotation directly as $label.whatever, instead of having to duplicate the templating expression.

labels are fully defined before annotations are added, and all values defined in LABELS are added at once at the end, so that they are not available except in ANNOTATIONS

If we added that we'd just get complaints that it didn't work the other way. And that it was all done at once. No matter what we do here, someone is going to be unhappy.

The use case in mind is having a phrase constructed from several labels of the original alert, and use it in summary and description annotation.

Can you be more specific about your use case? There's several directions something like this can be approached from, and I need more detail to know if none of them apply.

Without further information about your use case I'll have to presume there's some other better way to resolve your use case.


Site header component: Do we need 2 header examples?

Assigning to @jaredwyee for decision

@xjensen Based on this morning's conversation, alerting you to another example of where we may have more demo than we need.

We could use the oft-neglected Use Cases tab to show different uses of a component.
I think we definitely need to show both examples (with and without a logo). We're already supporting that in production between Drought and Cannabis.

You're right--we definitely want those use cases. I could keep the demo as is or move one (I'd recommend the no logo version) to the use case tab. That might be a strategic decision, so I'm interested in @jaredwyee 's thoughts.

pinging @jaredwyee for a decision

@yesenia-gtz I think that this is a you decision now instead of Jared. My recommendation is to close this issue. We do need both header examples and probably don't want to put the development work into creating a use case tab for the page at this point. (But others correct me if I'm wrong!)


scrollToOffset/index in horizontal direction with paging is wrong

Current behavior
I am having a long list of items rendered in a Horizontal direction. On a button press, I want to scroll to a certain item in the list. The problem is that the "scrollToOffset" and "scrollToIndex" are not scrolling me to the middle of the item as it is shown on the screenshot. The first few items are centered but if I try to scroll to a 15. item, for example, then it gets it wrong.

My code:
<FlashList
    ref={flatListRef}
    data={data}
    renderItem={renderItem}
    horizontal
    pagingEnabled
    showsHorizontalScrollIndicator={false}
    estimatedItemSize={400}
    viewabilityConfigCallbackPairs={viewabilityConfigCallbackPairs.current}
  />

The render item wrapper has a width equal to the width of the device screen.
This is how I am trying to scroll to the item.
flatListRef?.current?.scrollToOffset({
    offset: width * index,
    animated: true,
  });

Expected behavior

This is how it looks when I scroll to the first five items, and this is how it should be for the all items on the list.

To Reproduce

Platform:

[x] iOS
[ ] Android

Environment

1.1.0

Can you create an expo snack for this? I can take a look

I have tried to recreate the problem, that I have, on the Expo Snack and everything worked fine. So, I started digging more into the problem on my side and discovered that my custom hook created this problem. I think the problem is that the hook is rerendering the item at the same time when the scrollToOffset is working.
Here is an example on the snack: https://snack.expo.dev/@sega93/upbeat-strawberries
(Run it on iOS or Android mode)

@fkranenburg check your estimatedItemSize prop.
It should have the correct measurements of the item's width/height.
I have resolved the problem by updating it to estimatedItemSize={Dimensions.get("window").width}


⚠ Bofrost.es has degraded performance

In eeb366f, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1491 ms

Resolved: Bofrost.es performance has improved in 30709ad after 6 minutes.


backport.statistics in requirements.txt should have Python version range

... because it is only needed for Python up to 3.3

I've taken it out :)


Screen not registered for screen handler wands:wand_menu!

Trying out the wands for the first time but currently unable to open the wand menu. Here are some details that'll hopefully help to debug it, and let me know if you need anything else from me.
Versions

Java 1.17.1
Fabric 0.11.6
Building Wands 2.2.5
Quite a few other mods

Issue

Press the wand menu key and nothing happens in game
Check the logs and each time the key is pressed the following is output

[09:06:19] [Render thread/ERROR]: ########## GL ERROR ##########
[09:06:19] [Render thread/ERROR]: @ Render
[09:06:19] [Render thread/ERROR]: 65539: Invalid key -1
[09:06:20] [Render thread/WARN]: Screen not registered for screen handler wands:wand_menu!

Okay, I have removed each of these mods one by one to see what happens, and I've ruled out the following as potential culprits: Cloth Config API (at least the standalone file), Data Attributes, Carpet Mod, and Patchouli.
So we're left with Dawn API, Impersonate, Industrial Revolution, Megane, Mod Menu, Player Ability Lib, Pehkui, Somnus, Trinkets, and Yung's API. Architectury, Fabric API, Fabric Language Kotlin, and WTHIT also have to be in there as dependencies, but they don't break anything.

it's weired, if I remove all the other mods but trinkets, Building Wands, and deps), then it works ok. it must be trinkets+other mod.

Removing any one of the mods I listed fixes it for me, but I'm really at a loss as to why. I'm going through the .jars looking for access wideners and mixins they seem to share, since it's my understanding those are common culprits in compatibility issues.


Missing Declared license

Type: Incomplete
Summary:
Missing Declared license
Details:
This one has some inconsistencies. 4 licenses are listed here: https://mvnrepository.com/artifact/com.github.jnr/jnr-posix/3.0.45. Note it says EPL 1.0.
Resolution:
However, on the code header it says "The contents of this file are subject to the Eclipse Public
License Version 2.0 (the "License")" but then the link it gives for the license goes to the CPL 1.0.  So, I didn't curate EPL 1.0 and wasn't sure to curate CPL 1.0 AND EPL 2.0?
Affected definitions:

jnr-posix 3.0.45

See file header:
/***** BEGIN LICENSE BLOCK *****

Version: EPL 2.0/GPL 2.0/LGPL 2.1

The contents of this file are subject to the Eclipse Public
License Version 2.0 (the "License"); you may not use this file
except in compliance with the License. You may obtain a copy of
the License at http://www.eclipse.org/legal/cpl-v10.html

Software distributed under the License is distributed on an "AS
IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
implied. See the License for the specific language governing
rights and limitations under the License.

Alternatively, the contents of this file may be used under the terms of
either of the GNU General Public License Version 2 or later (the "GPL"),
or the GNU Lesser General Public License Version 2.1 or later (the "LGPL"),
in which case the provisions of the GPL or the LGPL are applicable instead
of those above. If you wish to allow use of your version of this file only
under the terms of either the GPL or the LGPL, and not to allow others to
use your version of this file under the terms of the CPL, indicate your
decision by deleting the provisions above and replace them with the notice
and other provisions required by the GPL or the LGPL. If you do not delete
the provisions above, a recipient may use your version of this file under
the terms of any one of the CPL, the GPL or the LGPL.
***** END LICENSE BLOCK *****/

@fossygirl @bduranc @royaljust Please take a look at this curation and provide your input. Thank you.

I also encountered this same license when curating a version of JRuby:
https://github.com/jruby/jruby/blob/8a269e34ff3d242ec90fb08061f79c2757a5e157/lib/ruby/stdlib/ffi/union.rb
It seems to me like at some point they moved from the CPL over to the EPL as this was quite common, but forgot to change all the text.
I'm interested also to see what the others think.

Thanks, @bduranc.  In this instance, I curated what I did from the view point that we should not be interpreting what someone meant to be the license.  However, I looked at two instances yesterday where there were inconsistencies between the package licensing metadata and the licensing info in the source.  That happened here as well, as I ignored the reference to EPL 1.0 in the package metadata (the license tags here: https://mvnrepository.com/artifact/com.github.jnr/jnr-posix/3.0.45), because EPL 1.0 wasn't mentioned in the source for this version. And then here as well, it does look like the mismatch between the license name given for EPL 2.0 and the license link (for CPL 1.0) was an oversight.  When curating,It would be good to decide what to do when we have evidence that supports a licensing 'error.'

Interesting issue.  I don't think we should be curating based on suspicion of error, even when the error seems pretty clear.  In this case, I would treat the declared license as what the Maven repo says and note the discovered EPL 2.0 in the source.  Any thoughts on this @pombredanne?

@ariel11 Did we agree as a group to Declare EPL 1.0 and EPL 2.0 would be a discovered license?

@AE49 - My understanding from @royaljust is that because there is not a "license" file in the jar, we will carry through what the metadata says for the maven package.  And that we are not going to use the license block on some of the files to curate the 'declared' field.  So, my understanding is the curation for the 'declared' field becomes the (4) licenses tagged at the top here: https://mvnrepository.com/artifact/com.github.jnr/jnr-posix/3.0.45. An open question for me then is whether we carry through the "or later" for GPL/LGPL because that info was found on some of the files and not in a canonical location for the overall project.

@ariel11 Yes, I remember we were going with the four licenses. My question is specific to the EPL license. We can discuss your last question with @royaljust as we need to make a decision.


typo CONFIG_NO_MOUSE_CURSOR_CHARGE remains in pyglet integration

Looks like CI didn't catch this; https://github.com/pyimgui/pyimgui/blob/9e97c2489fc7f424d7df63fd9a13df770ceacffe/imgui/integrations/pyglet.py#L108 (current master) still has the typo. This breaks pyglet-based pyimgui apps.
Originally posted by @connorjak in https://github.com/pyimgui/pyimgui/issues/216#issuecomment-956383441

Good catch, thanks!
I fixed it in commit https://github.com/pyimgui/pyimgui/commit/a5edd386ee50ab6dd515256cca542223fdf2d0bd. I did a search in all files to be sure. I'll wait until the end of the week to wait if any other issues with the latest release occurs and I'll push a minor release with all fixes (1.4.1).

I fixed it locally in my site_packages and verified it worked.
Also, ideally, we would have a test in the CI that would have caught this. Not this particular issue, but it would "exercise" the pyglet integration and see if anything failed.


[stable/oauth2-proxy] Breaking change: upgrade to v4.0.0

Also add desaintmartin as maintainer.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @Miouge1

Up?

/ok-to-test
/lgtm


SC lesion comparison between M0 and M12

In this issue, we investigate the patient's differences between M0 and M12.
To do so, we first listed all the patients which had to be excluded, which are :

patients with poor PSIR or STIR data quality
patients with impossibility to label vertebral levels
patients which are not present and either M0 or M12
patients which have the same images at M0 and M12 (issue 39 for ref

The following file contains all the subjects to be excluded : exclude_M0_M12_comparison.yml
TO DO:

[x] Run inference on M12 subjects
[x] Generate dataframe for M0 subjects
[x] Generate dataframe for M12 subjects
[x] Compare dataframes

Inference was run on M12 time points with both the 2d and 3d nnUNet (trained on STIR and multiplied by -1 PSIR) → inference was performed on 290 subjects.
Inference results are available at :

duke.neuro.polymtl.ca/temp/plben/inference_results_555_2d_BIDS
duke.neuro.polymtl.ca/temp/plben/inference_results_555_3d_BIDS

The dataframes were generated for M0 and for M12 3d and M12 2d. They include every subject in the CanProCo except from those in exclude_M0_M12_comparison.yml They are available at :

duke.neuro.polymtl.ca/temp/plben/dataframe_M0
duke.neuro.polymtl.ca/temp/plben/dataframe_M12_2d
duke.neuro.polymtl.ca/temp/plben/dataframe_M12_3d

→ Currently working on dataframe comparison

The analysis of M0 and M12 dataframes was performed.
→ figure to be used for abstracts ?
However, I noticed, that the total volume of lesion segmented is greater with the 2d nnUNet inference then with the 3d nnUNet inference.

→ figure to be used for abstracts ?

for ismrm definitely (not possible for ACTRIMS AFAIK)


[CWS] fix scrubbing of variables of type []string during serialization

What does this PR do?
Currently []string values variables are serialized by only including the last scrubbed value of the slice which is quite surprising. This PR fixes the issue by ensuring we scrub each element of the slice and serialize the scrubbed array.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


⚠ Samsung has degraded performance

In 3d2fe72, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2605 ms

Resolved: Samsung performance has improved in 774c927.


[excel] (Performance) Correcting range limit text

This is based on clarification from the production team:

Range size limitation (five million cells) is for get operations (not set operations). It applies to all platforms.
Payload size limit is kind of platform limitation, it is online only and it applies to all APIs (not only range API).

Docs Build status updates of commit 57e806f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/excel/excel-add-ins-core-concepts.md
:warning:Warning

Details

docs/develop/common-coding-issues.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-core-concepts.md

Line 209: [Warning] Invalid link: 'Excel Range limits'. The file develop/common-coding-issues.md doesn't contain a bookmark named 'excel-range-limits'.

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

Docs Build status updates of commit f47276e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/common-coding-issues.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-core-concepts.md
:white_check_mark:Succeeded

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


Owned Entities behave in a manner modified to Owned Attributes And Upgrade to .Net 6.0

I removed the code in Composed Type Mapper and added an AnnotationHandler for Owned Entities instead.
It also makes sense to move away from .netStandard and upgrade the project to .Net 6.0 since .netStandard is deprecated.
.Net 6.0 is still compatible to other operating systems like MacOS or Linux.
@leonardoporro I ask for quick feedback and fast release on Nuget.

mmm.. didn't have enough time to check everything, but have some feedback from my end...
as far as I remember, owned entities doesn't really exist, they are mapped to table fields whose name follows a pattern like Table_OwnedEntity_FieldName.. so Detached should copy them as is.. no [Composition] or [Aggregation] should be needed.. it is something similar to a Primitive,
please push the test and the solution in different PRs, so we can work toghether in finding the best approach, any change in the contrib folder will be approved inmediately
if some bug is fixed using your own TypeMapper / Annotation, you don't need to add it to this repo inmediately
MapperOptions provides public AnnotationHandlers, TypeMapperFactories, etc. properties and you can inject your own OwnedEntityTypeMapperFactory that resides in your solution.
I tried to follow SOLID.. closed to modification, open to extension..
(let me know if this is not well explained)
Another possibility for quick nuget release.. you may fork the repo, and install a local feed using BaGet
I know there are few people using this library and you are one of the most important! but I can't introduce breaking changes in a hurry. othewise, the few people that is using it will drop it soon
as far as I remember, moving from netstandard to net6 breaks NetFiddler examples, and it might break other people projects too.
I will pull this branch and review bug 17 tomorrow afternoon, will keep you up to date

I will now create 2 PRs and close this one


turbo:after-stream-render event

We've got turbo:before-stream-render but it would also be helpful to have an event fire after the rendering has occurred as well.
My use-case is that the new DOM element is rendered into a scrollable window, so I'd like to scroll the new element into view after it's been rendered. It doesn't appear as though there is any event I can currently hook into that will let me perform this action after the DOM update has occurred.

Is this a duplicate of https://github.com/hotwired/turbo/issues/92 and https://discuss.hotwired.dev/t/event-to-know-a-turbo-stream-has-been-rendered/1554/6?

Apologies, I did search but nothing came up.

It helped me https://github.com/hotwired/turbo/pull/20#issue-773325276. Didn't found any drawbacks yet.


Proxy by "startwith" request_path

Hi,
Can Kong support route by "startwith" request_path?
For example 1, /order.* routes to http://order.myapi.com with strip_request_path.

http://mykong.com/order.retail('id') routes to http://order.myapi.com/order.retail('id')
http://mykong.com/order.xsp('id') routes to http://order.myapi.com/order.xsp('id')

Example 2, /accounts.* routes to http://account.myapi.com, but the accounts.account('id').email routes to http://email.myapi.com

http://mykong.com/accounts.account('id') routes to http://account.myapi.com/accounts.account('id')
http://mykong.com/accounts.account('id').email routes to http://email.myapi.com/accounts.account('id').email

thanks,
Kalin

@kalinchih not at the moment, but we plan to support it. Related to #369, so closing this as a duplicate.


Release v2.4.0

Since v2.3.0, an outline of the new features and changes is given below:

Include all Dockerfiles in the project and switch to GitHub Actions and Packages (GH-84)
Scan and Search queries (GH-83, GH-85, GH-89 and GH-92)
Additional Float and String aggregators (GH-86)
Support for Druid SQL (GH-90 and GH-91)
Use requestInterceptor in health checks (GH-93 and GH-94)
Use com.typesafe.scala-logging instead of using slf4j directly (GH-95)
Expand "tests" section in README file (GH-96)

Is it possible to proceed with a new release of Scruid library (v2.4.0)?
:)

If it were released as-is I would be okay with that, but there are a couple of things I would like to fix before the release:

I can see in the build output that I've somehow managed to log the stack trace with health check failures, despite my intention not to. Probably a difference between raw SLF4J and Typesafe-Logging that I overlooked. I think the logging is too noisy there.
I am a little bit bothered by the "upstream failed / abrupt termination" warnings in the unit test suite. If we can do a clean stop in the tearDown handler, there won't be that "boy who cried wolf effect" if we ever introduce a real warning

I'll create a PR with some pre release housekeeping

Pull request ready for review. Resolving those Akka shutdown warnings turns out not to be really feasibly. There are tons of issues mentioning them, which are unresolved since 2015 or so. That suggests it's a tough one.

Indeed it's a an old and unresolved issue regarding the Akka shutdown error message. The error message in Scruid is fired from the logging of cachedHostConnectionPool Flow. When, for example, comment out the .log("scruid-load-balancer", _ => s"Sending query to ${queryHost.host}:${queryHost.port}") part in DruidAdvancedHttpClient.scala then the error message is not exposed.
I think it is safe leave it unchanged. Perhaps in a future release of Akka it may be resolved.

Hi Anastasios, we expect to complete release 2.4.0 before the end of this week.
best regards, Marcus Martina

released :)


bugfix: fix TextMatchFilterOptimizer boolean grouping

Previously the text_match filter optimizer didn't properly push down grouping. For example (tm = text_match):
tm(a) AND (tm(b) OR tm(c))and (tm(a) AND tm(b)) OR tm(c) both were optimized to tm(a AND b OR c)
This PR corrects the behavior to maintain the grouping, e.g.
tm(a) AND (tm(b) OR tm(c)) -> tm(a AND (b OR c))
(tm(a) AND tm(b)) OR tm(c) ->  tm((a AND b) OR c)
tag: bugfix

Codecov Report
Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 0.00%. Comparing base (59551e4) to head (6a02e1c).
Report is 368 commits behind head on master.

Files
Patch %
Lines

...ery/optimizer/filter/TextMatchFilterOptimizer.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #13009       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2427        -9
  Lines        133233   132942      -291
  Branches      20636    20595       -41
=============================================
- Hits          82274        0    -82274
- Misses        44911   132942    +88031
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <0.00%> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <0.00%> (ø)

java-11
?

java-21
0.00% <0.00%> (-61.63%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
0.00% <0.00%> (-27.73%)
:arrow_down:

temurin
0.00% <0.00%> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


RFI: Deprecation of send()

Changeset as listed in #170 highlights that Browser::send() has been deprecated.  #170 also makes reference to #56, #154, #162, #167, and #168; all of which revolve around API updates and test suite improvements.
As per a DM with @clue I am submitting this "issue" as an RFI for technical reasons behind deprecation of send().
It feels odd that a "PSR-7 HTTP client" (shamelessly copied from README.md) does not (or rather will not) have a publicly available method that sends a previously created PSR-7 request.
The transactional methods (get, put, head, post, etc, etc) all proxy through requestMayBeStreaming() which generates a PSR-7 request which in turn is used in Transaction::send().
Is the intent to shift away from PSR-7 as the browser moves forward (under react/http)?
send() made it easier to move from Guzzle to a React based application.  My most common use case is that the browser is wrapped in a middleware type architecture where the request type is not necessarily known (or cared about) and specific actions are added onto the promise chain based on specific criteria.

$handler = function (RequestInterface $request, array $options) use ($browser) : PromiseInterface {
    // configure browser if required based on $options.

    // send the request
    return $browser->send($request);
};

$middleware = function (RequestInterface $request, array $options) use ($handler) : PromiseInterface {
    $promise = $handler($request, $options);
    if ($request meets some condition) {
        $promise->then(function(ResponseInterface $response) {
            // do some things;
         });
    }
    return $promise;
};

@shaunbramley Thanks for bringing this up, I think it's an excellent question!
The send() method has been deprecated via #170, but it continues to work as-is. You can keep using it until you update to react/http as per #177.
The main motivation for this is that the previous options have been replaced with dedicated methods to configure the Browser. In particular, the new request() and requestStreaming() methods are believed to provide a much cleaner interface to sending arbitrary requests.
The send() method requires an explicit RequestInterface object, which in most cases means that consumers also need an explicit dependency on a PSR-7 implementation (which isn't exposed by this project, i.e. there's no public Request class). It's too easy to have state attached to this request object which should not leak through to the network layer. For instance, most PSR-7 implementations default to creating requests with the HTTP/1.1 protocol version. With #162, this decision is left up to the Browser, i.e. if we start supporting HTTP/2 in the future (https://github.com/reactphp/http/issues/99), we would have to stick to older protocol versions in many cases or disregard the caller arguments. Likewise, a PSR-7 implementation may default to HTTP/2 right now and we would not be able to fulfill this request due to lack of protocol support. Additionally, most PSR-7 implementations will not support passing a streaming request body using the ReadableStreamInterface, which is easy to support in the request()/requestStreaming() methods.

Is the intent to shift away from PSR-7 as the browser moves forward (under react/http)?

Not at all. I think PSR-7 message abstractions are an excellent choice for this library (and react/http).
I think we can still discussing having (i.e. re-introducing) a send() method if the above points are taken care of. Additionally, we may also have to implement another way to send a request that receives a streaming response à la requestStreaming(). A new sendStreaming() could be the answer, but I feel this API name is misleading as it is more about receiving a streaming response body rather than sending a streaming request body. Sending a streaming request body is already supported by using a ReadableStreamInterface for either of the request methods.
At the moment, I think the cons outweigh the pros and using this below logic seems like a good compromise:
// old
$browser->send($request);

// new
$browser->request(
    $request->getMethod(),
    (string) $request->getUri(),
    $request->getHeaders(),
    (string) $request->getBody()
);

It's not perfect, but it gets the job done. I'm happy to hear your thoughts on this :+1:

I believe this has been answered, so I'm closing this for now. Please come back with more details if this questions persists and we can reopen this :+1:


.setnick doesn't take user as argument

Bot version: 2.17.3
OS: Ubuntu 16.04
Short description: The bot doesn't accept the user as an argument.
Steps to reproduce:

Make sure your bot version is 2.17.3.
Make sure the bot has Change Nickname permission.
Use .setnick @UserMention NewNickname.
Expected result: The user's nickname should change.
Actual result: The bot changes it's own nickname to <@IDOfTheUserYouMentionedEarlier> NewNickname`.

Not able to replicate this on 2.17.3. Relevant logs:

Also, make sure the bot has Manage Nicknames (not just the Change Nickname) perm.

Bot has the Administrator permission, although the command still doesn't work properly.

Not sure, I'm unable to replicate. Does this happen for any user/bot you try to change the nick for? Are you using the desktop client?

Only other thing I can see is that you need to make sure you have Manage Nick permissions.

I am an admin. Yes, I am using desktop Discord client. Not a role hierarchy issue since the bot is almost at the top and Active role is under the bot's role.

Update:
Happens only on my personal server. Works fine on others.

Means bot can't find that user. Make sure the user is online and bot can see it. Checked the code, its' fine.

And make sure the bot has manage nick permissions.

As I mentioned before, bot has Administrator permission. I doubt that the bot is unable to change my as well as any other members' nick.


Provide helm in update-deps image

Some of the update-deps jobs require helm to be installed (e.g. eventing or eventing-kafka-broker).
See: https://github.com/knative-extensions/knobots/actions/runs/7482975295/job/20367497039 or https://github.com/knative/eventing/blob/bc89d285177775c5e287aea32e86a502eddac80e/hack/update-cert-manager.sh#L14-L17
This PR addresses it and installs the latest helm 3 version into the update-deps image.

/cc @pierDipi

Why not just curl the release yamls?
https://github.com/knative-extensions/net-certmanager/blob/main/third_party/cert-manager-latest/download-cert-manager.sh

Because we need trust-manager too, which is AFAIK currently only available via helm: https://cert-manager.io/docs/trust/trust-manager/#manual-installation


how to generate cityflow  trainval dir?

hi xiangyu：
to train reCam model，how to generate below dir ？

Hello, I am sorry to bother you.
have you got the .txt file?

Hello, I have the same question

hi， tranval is a partition of full training set, I forgot to upload this scripts. You can partial it yourself, in my case  I select the pid<97 in trainset as validation.

Thank you very much. Moreover,  what information is included in the txt files?

Hi, do train.txt contain the name of the images?
Thank you

@Martafdez18 train.txt just contains name of images in row.

However, the function _process_dir try to get pid, camid, trackid and  image_name from the txt.  Is it an error?
def _process_dir(self, dir_path, list_path, relabel=False):
    dataset = []
    with open(list_path, 'r') as f:
        lines = f.readlines()

    for line in lines:
        line = line.strip()
        pid, camid, trackid, image_name = line.split('_')
        pid = int(pid)
        camid = int(camid[1:])
        img_path = osp.join(dir_path, image_name)
        #dataset.append((img_path, pid, camid))
        dataset.append((img_path, camid, pid))
    if relabel: dataset = self.relabel(dataset)

    return dataset

@Martafdez18 Well，I renamed the file  from  "003931.jpg" to “0053_c001_t0115_003931.jpg”, which stands for 'pid_camid_trackid_image_name"


feat: support checkly test on private locations

I hereby confirm that I followed the code guidelines found at engineering guidelines
Notes for the reviewer
Relates to https://github.com/checkly/checkly-cli/issues/352 and https://github.com/checkly/checkly-cli/issues/386
This PR adds support for running checks on private locations for checkly test. The PR adds a --private-location flag that can be used to pass the slug name of a private location.
Error handling
Passing both --location and --private-location:
$ npx checkly test --location eu-central-1 --private-location test
 ›   Error: The following error occurred:
 ›     --location=eu-central-1 cannot also be provided when using --private-location
 ›   See more help with --help

Passing an invalid private location (gives non-zero status code)
$ npx checkly test --private-location test
 ›   Error: The specified private location test was not found on account<EMAIL_ADDRESS>$ echo $?
1

Sorry for the duplicate review request. I've updated the README to include the new flag.


Possible error - 3rd Ed. - Page 84

Pg. 84, second to last line:
... using the `logical_or` function ....

should probably be
... using the `logical_xor` function ....

Thanks, you are right! Added this to the errata.


[NT-2108] Migrating UnwatchProjectMutation to Apollo

📲 What
In a previous PR we successfully handled the migration of the WatchProjectMutation for use with our Apollo GraphQL client. This PR will handle the counterpart to that very mutation -- UnwatchProjectMutation.
Both mutations essentially handle the same functionality but have different mutation signatures, which is why they are separated. This PR introduces the template for the mutation and the various adapters required for interoperability with our codebase.
🤔 Why
This is another addition to our GraphQL migration from our legacy DSL to Apollo. There is nothing unusual occurring in this PR that did not occur in all the others so it is becoming quite familiar/boilerplate-ish.
🛠 How

Created a new file, UnwatchProject.graphql to create the template of the mutation.
Updated the Service.swift method for unwatching a project to perform the mutation with our Apollo GraphQL object.
Created an adapter to make the GraphAPI.UnwatchProjectInput from a WatchProjectInput object. This is required because we use the WatchProjectInput for both mutations but Graph distinguishes these inputs as two separate ones.
Created an adapter to return the WatchProjectResponseEnvelope from a GraphAPI.UnwatchProjectMutation.Data object. This is functionally the same work required for watching a project but, again, GraphQL distinguishes these as separate mutations/data.
Included some tests.

✅ Acceptance criteria

[ ] Run Charles proxy to monitor when the unwatch project mutation is called.
[ ] Unwatch a project from your Profile and verify that the mutation is called without regression.

Good to go, I experienced strange responses from Charles when testing this PR on a simulator (like this mutation returning a user backing object) but then again staging wasn't loading pages for me half the time. Confirmed with yourself it was an issue on my local.


Deprecate S3PrefixSensor and S3KeySizeSensor in favor of S3KeySensor

Refer to https://github.com/apache/airflow/pull/22737 and make changes to async versions wherever applicable

Look for the Latest release in OSS and Deprecate in Astronomer Provider repo as well

Went through this PR  #22737 , some changes has to be done in the S3KeySensorAsync, because the S3KeySensor sync version has the combination of S3PrefixSensor and S3KeySensor. Its not only deprecating the S3PrefixSensorAsync and S3KeySizeSensor, but also we need to incorporate the changes what is in sync version. so changing the story estimation point.

Need to add async decorator function which will be used in current changes

Deprecated S3PrefixSensor and S3KeySensor. Made changes to the S3KeySensorAsync need test it

Added PR: https://github.com/astronomer/astronomer-providers/pull/577


[FLINK-19448][connector/common] Synchronize fetchers.isEmpty status to SourceReaderBase using elementsQueue.notifyAvailable()

What is the purpose of the change
Synchronize fetchers.isEmpty status to SourceReaderBase using elementsQueue.notifyAvailable().
Brief change log

Add test case to fail empty queue assumption in SourceReaderBase.finishedOrAvailableLater.
Correct empty queue assumption by returning InputStatus.MORE_AVAILABLE if not empty.
Synchronize fetchers.isEmpty status to SourceReaderBase using elementsQueue.notifyAvailable().

Verifying this change
This change is already covered by existing tests, such as:

CoordinatedSourceITCase.testEnumeratorReaderCommunication.

This change added tests and can be verified as follows:

SourceReaderBaseTest.testMultipleSplitsWithSeparatedFinishedRecord

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

@flinkbot attention @StephanEwen @becketqin

@flinkbot run travis
Rerun test ci due to probably unrelated failure.


Add install/usage instructions

Found it on npm first, and then came here but didn't see anything pointing to the name (package.json only) so decided to add these simple instructions.

Excellent addition, thanks!

Published in 1.1.13.

Sweet.
Unrelated question, any idea if there is a way to hide the marker?


Issues don't show up in project

Description
I tried Gitea using www.gitea.com not try.gitea.com. I created a repo and a project and some issues but the issues don't show up: https://gitea.com/treyerl/Test-Repo/projects/1823

Gitea Version
1.22.0+dev-219-gb2f828db5
Can you reproduce the bug on the Gitea demo site?
Didn't try
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
www.gitea.com
Database
None

https://github.com/go-gitea/gitea/pull/27720 need someone to approve

closed with #27720

closed with #27720

closed with #27720


How to use a 64-bit address to load hanfnium?

When I modify the  configuration in BUILD.gn as follows:
origin_address = "0x880000000"
I encounter the build error:
FAILED: secure_aem_v8a_fvp_clang/hafnium.elf
ld.lld -pie --gc-sections --defsym=ORIGIN_ADDRESS=0x880000000 -O2 --icf=all --fatal-warnings --color-diagnostics -T /home/yuye/hafnium/Hafnium/build/image/image.ld -o secure_aem_v8a_fvp_clang/hafnium.elf --start-group @secure_aem_v8a_fvp_clang/hafnium.elf.rsp --end-group
ld.lld: error: secure_aem_v8a_fvp_clang/obj/src/arch/aarch64/entry.entry.o:(.init.entry+0xC8): relocation R_AARCH64_ABS32 out of range:<PHONE_NUMBER>6 is not in [-2147483648,<PHONE_NUMBER>]; references ORIGIN_ADDRESS
>>> defined in -defsym:1
ninja: build stopped: subcommand failed.
Makefile:70: recipe for target 'all' failed
make: *** [all] Error 1
+ cp out/reference/secure_aem_v8a_fvp_clang/hafnium.bin ../../V2/Ali_M1_Public/Nonosi/Platform/Ali/M1/Bin/
cp: cannot stat 'out/reference/secure_aem_v8a_fvp_clang/hafnium.bin': No such file or directory

This is better discussed on the Hafnium mailing list. In this case, it seems that the new address causes some relative addressing to reach too far. This can be fixed in the assembly code if you're able to identify the instruction causing the problem. That said, I guess you're doing something that isn't supported by Hafnium so you may run into other problems after this is sorted.

Ok, I will try it first according to your suggestion. Thank you!


[Question]: Error on createSupabaseClient(), Function not found

General info

[X] I checked the troubleshooting page for similar problems

What is your question?
I have scoured the internet, Supabase Docs, this GitHub repo and all the issues.
I am not able to find the import dependency for createSupabaseClient()
val supabase = createSupabaseClient(
supabaseUrl = "https://xyzcompany.supabase.co",
supabaseKey = "your_public_anon_key"
) {
install(Postgrest)
}
If I try to do "import io.github.jan-tennert.", I get error on "github"
Relevant log output (optional)
No response

YouTube Video (Official Guide) : https://www.youtube.com/watch?v=P_jZMDmodG4&t=330s
Tyler Shukert right click and does an import on createSupabaseClient function which is not available to me,
this happens when the dependencies in the files are not imported and the required class functions are not available

The package should be io.github.jan.tennert.supabase.
How did you add the Supabase dependencies?

build.gradle.kts (app)
// Supabase Dependencies
implementation(libs.bom)
implementation(libs.postgrest.kt)
implementation(libs.gotrue.kt)
implementation(libs.ktor.client.android)
libs.version.toml
bom = "2.1.3"
ktorClientAndroid = "2.3.8"
bom = { module = "io.github.jan-tennert.supabase:bom", version.ref = "bom" }
gotrue-kt = { module = "io.github.jan-tennert.supabase:gotrue-kt" }
ktor-client-android = { module = "io.ktor:ktor-client-android", version.ref = "ktorClientAndroid" }
postgrest-kt = { module = "io.github.jan-tennert.supabase:postgrest-kt" }

Two things I can see there:

You are using an old version of supabase-kt
BOMs don't work like that. If you are using a version catalog anyway, just add version.ref = "bom" to gotrue and postgrest and remove the bom dependency.

I mean that's how it is on the YouTube guide.
Shall I use
supabase-kt bom : 2.6.0
ktor : 2.3.12
?

Shall I use

Yes

I mean that's how it is on the YouTube guide.

The video guides didn't use a gradle version catalog, but both approaches work.

Quick update
supabasebom = "2.1.3"
bom = { module = "io.github.jan-tennert.supabase:bom", version.ref = "supabasebom" }
gotrue-kt = { module = "io.github.jan-tennert.supabase:gotrue-kt", version.ref = "supabasebom" }
postgrest-kt = { module = "io.github.jan-tennert.supabase:postgrest-kt", version.ref = "supabasebom" }
import io.github.jan.supabase.createSupabaseClient
import io.github.jan.supabase.gotrue.Auth
import io.github.jan.supabase.postgrest.Postgrest
This has fixed my issue,
Thanks,
Once I have my code working as intended, I will update the dependencies to the latest versions


Refactor OpExecutionModeTest and apply it on v1.1.

Previously v1.1 testing was dead.
@antiagainst @AWoloszyn @dneto0 @Qining PTAL.

LGTM


Check for Registered Directories always fails

The check if a Directory is already registered to the server always fails, because the token is missing. Test-TargetRessource needs a token to ask for the already registered directories...

@shailesh91
Unfortunately it does not work.
on the one hand it might get the token twice or at least the log-file indicates so.
on the other Hand, even if the test is correct it goes to set the Directory again.
Please see the logfile:
[1060-303]: LCM:  [ Start  Test     ]  [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories]
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] Fully Qualified Domain Name :- 1060-303.gis.lab
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] Getting the Token for site 'http://1060-303.gis.lab:6080'
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] Getting the Token for site 'http://1060-303.gis.lab:6080'
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] POST http://1060-303.gis.lab:6080/arcgis/admin/system/directories with 78-byte payload
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] received 3897-byte response of content type text/plain;charset=UTF-8
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] Testing for Directory basemapcache
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] Directory basemapcache already registered
[1060-303]: LCM:  [ End    Test     ]  [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories]  in 1.4190 seconds.
[1060-303]: LCM:  [ Start  Set      ]  [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories]
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] Fully Qualified Domain Name :- 1060-303.gis.lab
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] Waiting for Server 'http://1060-303.gis.lab:6080/arcgis/admin' to initialize
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] Getting the Token for site 'http://1060-303.gis.lab:6080'
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] POST http://1060-303.gis.lab:6080/arcgis/admin/system/directories with 78-byte payload
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] received 3897-byte response of content type text/plain;charset=UTF-8
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] Testing for Directory basemapcache
[1060-303]:                            [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories] Directory basemapcache already registered > no Action required
[1060-303]: LCM:  [ End    Set      ]  [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories]  in 2.9570 seconds.
[1060-303]: LCM:  [ End    Resource ]  [[ArcGIS_Server_RegisterDirectories]Server1060-303.gis.labRegisterDirectories]

@spitzerr Getting the token twice is it just printing it twice. Nothing more. I have found the result variable was not initialized correctly.

#70

@shailesh91 Works perfectly. Thanks


Bad link on AppScope download page for "Quick Start Guide"

On the AppScope download page (https://cribl.io/download/)
When clicking on Quick Start Guide button, it tries to forward to docs, but breaks.
Button Clicked:

Resulting page when forwarded:

Thanks. We'll correct the dead link, and this whole iframe, by the palindromic 12/21/2021.

The iframe will change to this, and the left button's corrected target will be https://appscope.dev/docs/downloading:


Add common logic for buffering / reordering live points

Add common logic for buffering / reordering live points (see twitter adapter).
For live points, each adapter maintains a moving time-window, accepts arriving points with timestamps inside of it, and drops the rest. The points arriving within the window are sorted by timestamp, then periodically emitted. This is intended to maintain the  'monotonically increasing timestamp' invariant for points arriving out of order.
As this logic will be common to all our adapters, it should be added to the source base class.
The PR #20 implements the module that the base class should eventually use.

@dmehra I updated the comment - is the description clear?

Looks clear to me.


💡[FEATURE] Design Blog Home Page

Description
I want to design a blog home page which will have cards with images,title description
When blog data is available it can be put in these cards
Screenshots

Checklist

[X] I have checked the existing issues.
[X] I have read the Contributing Guidelines
[X] I have read the Code Of Conduct
[X] The changes don't break the code

Hey I am closing this issue, as this is already been added in the project. Actually the deployed link is old. Please check the website after cloning, it is there.


Slower string manipulation performance than CPython

Feature request
After investigating Numba usage and internals, I want to popularize the usage of Numba in my work group.
However, our existing Python bussiness code is often related with user-defined-functions using Pandas DataFrame and string manipulation.
I know Numba is excellent at numeric manipulation, not good at string stuff.
I look into Numba internals, it already has Python unicode type support, but with much slower speed than CPython.
I wonder:

whether Numba will enhance string performance in recent future?
if I dive into modifying numba source code for string speed on the current basis of Numba unicode support by myself, is there a theoretical upper limit for performance? Specifically, I think if I decide to do it by myself, I have to optimize each string operation (e.g., CPython string find() implementation contains many "short cut", bloom, KMP algorithm and so on; numba just implements a brute-force _finder() to overload string find()), and what's more? Adding specific compilation optimization pass for string manipulation?
or for much better performance, such as ~10x speed up than CPython, I have to rewrite all unicode code already in Numba?
or recommand some existing numba extensions/tools with better string support?
Besides, I know Intel SDC project is developing, are there other numba extensions with Pandas DataFrame support?

For example, I tested a small snippet of code:

Thank you for your interest in Numba. Currently, the unicode support in Numba is primitive and it's not performing well for application relying on string manipulation. IIRC, it is particularly bad on code that requires processing on individual characters such as the text_distance() code. Unfortunately, we don't have any immediate plans to optimize the string support.
As for the performance limitation, i think the reference counting operations are preventing optimizations. In CPython, many of the implementation can access the underlying buffer directly and bypass any reference counted operations.  Numba needs a similar direct access to the chars.
Lastly, beside Intel SDC, I only know of bodo for pandas support. (ping @ehsantn)

@sklam ,  @ehsantn , thanks.
Recently, I saw SDC gives a str_ext implementation, the core idea is like below:
@overload_method(types.UnicodeType, 'replace')
def str_replace_overload(in_str, old, new, count=-1):

    def _str_replace_impl(in_str, old, new, count=-1):
        with numba.objmode(out='unicode_type'):
            out = in_str.replace(old, new, count)
        return out

    return _str_replace_impl

It seems sdc uses with objmode to callback to python interpreter code.
But I don't know whether this kind of operations will unbox python unicode type to numba UnicodeType, and box back when call replace or other str operations. Can this boost string performance, e.g., achieve similar performance like CPython? It really confuses me, haha.
I also find some c.pyapi usage in numba source code, does this call into ctypes.pythonapi or sth like this? If totally calling back to Python C API, can we boost Numba String Performance?
Any comments are welcome, or any numba discussion group can let me in, haha. thanks.

close this. I think no many users will care for string operation performance when using numba, we more focus on numeric computing. Feel free to reopen it.


Firebase auth crashes the app with: [GTMSessionFetcher setFetcher:forTask:]: unrecognized selector sent to instance

Describe your environment

Xcode version: 10.1
Firebase SDK version: 5.15.0
Firebase Component: Auth
Component version: 5.15.0

Describe the problem
the app crashes when using signInWithCustomToken. the error log is: Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[GTMSessionFetcher setFetcher:forTask:]: unrecognized selector sent to instance.
It seems there is a collision beetween firebase sdk and Trustkit (https://github.com/datatheorem/TrustKit).
Steps to reproduce:
Run the example app in this repository (react native, although it does not seem related...):
https://github.com/eyalevy/trustkit-firebase-sample

This doesn't seem like it's caused by any collision with TrustKit. Can you share the stack trace of the crash?

This is my linker flags:  https://github.com/eyalevy/trustkit-firebase-sample/blob/e048d3d4ae630b3e97c814bcf2b1c42449d3a85d/ios/trustkitfirebasesample.xcodeproj/project.pbxproj#L1228
Am I missing something?
Also this is the stack trace:
(
	0   CoreFoundation                      0x000000010bd971bb __exceptionPreprocess + 331
	1   libobjc.A.dylib                     0x0000000109dc3735 objc_exception_throw + 48
	2   CoreFoundation                      0x000000010bdb5f44 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132
	3   CoreFoundation                      0x000000010bd9bed6 ___forwarding___ + 1446
	4   CoreFoundation                      0x000000010bd9dda8 _CF_forwarding_prep_0 + 120
	5   trustkitfirebasesample              0x0000000107536372 -[GTMSessionFetcherService fetcherDidBeginFetching:] + 402
	6   trustkitfirebasesample              0x000000010751102b -[GTMSessionFetcher beginFetchMayDelay:mayAuthorize:] + 11099
	7   trustkitfirebasesample              0x000000010750d419 -[GTMSessionFetcher beginFetchWithCompletionHandler:] + 329
	8   trustkitfirebasesample              0x00000001073ec14f -[FIRAuthBackendRPCIssuerImplementation asyncPostToURLWithRequestConfiguration:URL:body:contentType:completionHandler:] + 1023
	9   trustkitfirebasesample              0x00000001073ef9ff -[FIRAuthBackendRPCImplementation postWithRequest:response:callback:] + 1087
	10  trustkitfirebasesample              0x00000001073ed33b -[FIRAuthBackendRPCImplementation verifyCustomToken:callback:] + 299
	11  trustkitfirebasesample              0x00000001073eb34b +[FIRAuthBackend verifyCustomToken:callback:] + 123
	12  trustkitfirebasesample              0x00000001073df93e -[FIRAuth internalSignInAndRetrieveDataWithCustomToken:completion:] + 286
	13  trustkitfirebasesample              0x00000001073d7c97 __44-[FIRAuth signInWithCustomToken:completion:]_block_invoke + 183
	14  libdispatch.dylib                   0x000000010dfa6595 _dispatch_call_block_and_release + 12
	15  libdispatch.dylib                   0x000000010dfa7602 _dispatch_client_callout + 8
	16  libdispatch.dylib                   0x000000010dfaeb0b _dispatch_lane_serial_drain + 791
	17  libdispatch.dylib                   0x000000010dfaf784 _dispatch_lane_invoke + 428
	18  libdispatch.dylib                   0x000000010dfb989a _dispatch_workloop_worker_thread + 733
	19  libsystem_pthread.dylib             0x000000010e378fd2 _pthread_wqthread + 980
	20  libsystem_pthread.dylib             0x000000010e378be9 start_wqthread + 13
)

Linker flags look fine to me. @renkelvin can you take a look?

Hi all, I believe it's not an issue with the Auth SDK. GTMSessionFetcher is our main entry point talking to backend. All requests would fail if GTMSessionFetcher is not properly linked. Could you try other apis to see if it's the same issue?

@eyalevy Please share the Podfile and Podfile.lock so we can check if there's something strange about the versions being used.

Sure, the links for Podfile and Podfile.lock:

Podfile : https://github.com/eyalevy/trustkit-firebase-sample/blob/e048d3d4ae/ios/Podfile
Podfile.lock - https://github.com/eyalevy/trustkit-firebase-sample/blob/e048d3d4ae/ios/Podfile.lock

I want to add that this issue happened when we upgrade Firebase SDK version from version 4.9 to version 5.15. when I downgrade Firebase SDK to version 4.9 the app is not crashing.

@renkelvin I tried to use firebase storage for getting a file and I succeed to read it.

@renkelvin @paulb777  did any of you experience this error?

@eyalevy I wonder, if you can reproduce the crash if you remove pod 'TrustKit'. From the first glance, TrustKit does method swizzling on NSURLSessionDelegate which could be a reason of the issue.
If we know this we may narrow down the issue search area. Thanks.

@maksymmalyhin when I disable swizzling or remove TrustKit completely the issue doesn't reproduce.
I want to add that we did not add TrustKit recently. The last change we did is to upgrade Firebase SDK from version 4.9 to version 5.15. With Firebase SDK v4.9 and TrustKit the issue doesn't reproduce as well.

@eyalevy Thank you for the quick response. We will investigate how we can fix it.

It looks like the google/gtm-session-fetcher#130 creator stopped responding to the reviewer's questions months ago, so the discussion would need to be revived.

I commented in google/gtm-session-fetcher#130.
I hope the fix will be merged soon

This should be fixed with https://github.com/google/gtm-session-fetcher/pull/142. Please comment here if you run into the issue again.

I am experiencing this issue.
How can I fix this issue?
I am using Firebase and Trustkit

@morganchen12 Thanks for replying. These are my env and logs.
--- Podfile ---
pod 'Firebase/Auth', '~> 6.2.0'
pod 'Firebase/Core', '~> 6.2.0'
pod 'Firebase/Messaging', '~> 6.2.0'
pod 'TrustKit', '~> 1.6.2'
--- Podfile.lock ---

Fabric (1.10.2)
Firebase/Auth (6.2.0):

Firebase/CoreOnly
FirebaseAuth (~> 6.1.1)

Firebase/Core (6.2.0):

Firebase/CoreOnly
FirebaseAnalytics (= 6.0.1)

Firebase/CoreOnly (6.2.0):

FirebaseCore (= 6.0.2)

Firebase/Messaging (6.2.0):

Firebase/CoreOnly
FirebaseMessaging (~> 4.0.2)

FirebaseAnalytics (6.0.1):

FirebaseCore (~> 6.0)
FirebaseInstanceID (~> 4.1)
GoogleAppMeasurement (= 6.0.1)
GoogleUtilities/AppDelegateSwizzler (~> 6.0)
GoogleUtilities/MethodSwizzler (~> 6.0)
GoogleUtilities/Network (~> 6.0)
"GoogleUtilities/NSData+zlib (~> 6.0)"
nanopb (~> 0.3)

FirebaseAnalyticsInterop (1.4.0)
FirebaseAuth (6.1.2):

FirebaseAuthInterop (~> 1.0)
FirebaseCore (~> 6.0)
GoogleUtilities/AppDelegateSwizzler (~> 6.2)
GoogleUtilities/Environment (~> 6.2)
GTMSessionFetcher/Core (~> 1.1)

FirebaseAuthInterop (1.0.0)
FirebaseCore (6.0.2):

GoogleUtilities/Environment (~> 6.0)
GoogleUtilities/Logger (~> 6.0)

FirebaseInstanceID (4.2.3):

FirebaseCore (~> 6.0)
GoogleUtilities/Environment (~> 6.0)
GoogleUtilities/UserDefaults (~> 6.0)

FirebaseMessaging (4.0.2):

FirebaseAnalyticsInterop (~> 1.1)
FirebaseCore (~> 6.0)
FirebaseInstanceID (~> 4.1)
GoogleUtilities/AppDelegateSwizzler (~> 6.2)
GoogleUtilities/Environment (~> 6.2)
GoogleUtilities/Reachability (~> 6.2)
GoogleUtilities/UserDefaults (~> 6.2)
Protobuf (~> 3.1)

--- Error Logs ---
2019-08-27 10:12:59.773214+0800 PAB[19389:4469184] === TrustKit: Proxy-ing NSURLSessionDelegate: GTMSessionFetcher
2019-08-27 10:12:59.773320+0800 PAB[19389:4469184] Fetcher delegate class: TSKNSURLSessionDelegateProxy
2019-08-27 10:12:59.773424+0800 PAB[19389:4469184] Fetcher made an extra session: GTMSessionFetcher 0x104c68b20 (https://www.googleapis.com/identitytoolkit/v3/relyingparty/sendVerificationCode?key=AIzaSyDOYUzUrIfsdJG92KwrPNTYdJWp6MrVF-U)
2019-08-27 10:12:59.773456+0800 PAB[19389:4469184] Couldn't assign delegate.
2019-08-27 10:12:59.773764+0800 PAB[19389:4469184] Fetcher delegate class: TSKNSURLSessionDelegateProxy
2019-08-27 10:12:59.773823+0800 PAB[19389:4469184] -[GTMSessionFetcher setFetcher:forTask:]: unrecognized selector sent to instance 0x104c68b20
2019-08-27 10:12:59.773998+0800 PAB[19389:4469184] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[GTMSessionFetcher setFetcher:forTask:]: unrecognized selector sent to instance 0x104c68b20'
*** First throw call stack:
(0x193e5a98c 0x1930339f8 0x193d771c8 0x193e601d4 0x193e61e6c 0x1023ac4d4 0x10238a20c 0x102386a48 0x102277b20 0x10227a7e8 0x1022797bc 0x102277284 0x10229b428 0x10229b960 0x10229af74 0x10229ab88 0x102285650 0x1022852dc 0x10226e520 0x104868c78 0x104877480 0x10226e444 0x10226dfec 0x193e62010 0x193d43be0 0x1023e06b4 0x1023de918 0x193d463c8 0x1023de720 0x1023e0500 0x102284ff0 0x1048676f4 0x104868c78 0x1048766fc 0x193dec32c 0x193de7264 0x193de67c0 0x195fe779c 0x1c08e5c38 0x102246418 0x1938aa8e0)
libc++abi.dylib: terminating with uncaught exception of type NSException
--- Stacktrace ---

thread #1, queue = 'com.google.firebase.auth.globalWorkQueue', stop reason = signal SIGABRT
frame #0: 0x00000001939f70dc libsystem_kernel.dylib__pthread_kill + 8   frame #1: 0x0000000193a749b0 libsystem_pthread.dylibpthread_kill$VARIANT$armv81 + 296
frame #2: 0x000000019394fea8 libsystem_c.dylibabort + 140   frame #3: 0x000000019301c788 libc++abi.dylibabort_message + 132
frame #4: 0x000000019301c934 libc++abi.dylibdefault_terminate_handler() + 308   frame #5: 0x0000000193033e00 libobjc.A.dylib_objc_terminate() + 124
frame #6: 0x0000000193028838 libc++abi.dylibstd::__terminate(void (*)()) + 16   frame #7: 0x00000001930288c4 libc++abi.dylibstd::terminate() + 84
frame #8: 0x0000000193033d5c libobjc.A.dylibobjc_terminate + 12   frame #9: 0x000000010627cc8c libdispatch.dylib_dispatch_client_callout + 36
frame #10: 0x000000010628b480 libdispatch.dylib`_dispatch_lane_barrier_sync_invoke_and_complete + 124

frame #11: 0x00000001041d2278 PAB-[FIRAuth setAPNSToken:type:](self=0x0000000283a1d680, _cmd="setAPNSToken:type:", token=32 bytes, type=FIRAuthAPNSTokenTypeUnknown) at FIRAuth.m:1371:3 frame #12: 0x00000001041d1d50 PAB-[FIRAuth application:didRegisterForRemoteNotificationsWithDeviceToken:](self=0x0000000283a1d680, _cmd="application:didRegisterForRemoteNotificationsWithDeviceToken:", application=0x0000000106b07f90, deviceToken=32 bytes) at FIRAuth.m:1336:3
frame #13: 0x0000000193e62010 CoreFoundation__invoking___ + 144 frame #14: 0x0000000193d43be0 CoreFoundation-[NSInvocation invoke] + 292
frame #15: 0x0000000104343cbc PAB__93-[GULAppDelegateSwizzler application:donor_didRegisterForRemoteNotificationsWithDeviceToken:]_block_invoke(.block_descriptor=0x000000016bc5a780, interceptor=0x0000000283a1d680) at GULAppDelegateSwizzler.m:849:37 frame #16: 0x0000000104342918 PAB__72+[GULAppDelegateSwizzler notifyInterceptorsWithMethodSelector:callback:]_block_invoke(.block_descriptor=0x000000016bc5a6e0, key=@"GUL_0x283a1d680", obj=0x0000000280910e00, stop=NO) at GULAppDelegateSwizzler.m:680:7
frame #17: 0x0000000193d463c8 CoreFoundation-[__NSFrozenDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 176 frame #18: 0x0000000104342720 PAB+[GULAppDelegateSwizzler notifyInterceptorsWithMethodSelector:callback:](self=GULAppDelegateSwizzler, _cmd="notifyInterceptorsWithMethodSelector:callback:", methodSelector="application:didRegisterForRemoteNotificationsWithDeviceToken:", callback=0x0000000104343b9c) at GULAppDelegateSwizzler.m:667:3
frame #19: 0x0000000104343b08 PAB-[GULAppDelegateSwizzler application:donor_didRegisterForRemoteNotificationsWithDeviceToken:](self=0x0000000280b006c0, _cmd="application:didRegisterForRemoteNotificationsWithDeviceToken:", application=0x0000000106b07f90, deviceToken=32 bytes) at GULAppDelegateSwizzler.m:840:3 frame #20: 0x000000010627b6f4 libdispatch.dylib_dispatch_call_block_and_release + 24
frame #21: 0x000000010627cc78 libdispatch.dylib_dispatch_client_callout + 16 frame #22: 0x000000010628a6fc libdispatch.dylib_dispatch_main_queue_callback_4CF + 1360
frame #23: 0x0000000193dec32c CoreFoundation__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 frame #24: 0x0000000193de7264 CoreFoundation__CFRunLoopRun + 1924
frame #25: 0x0000000193de67c0 CoreFoundationCFRunLoopRunSpecific + 436 frame #26: 0x0000000195fe779c GraphicsServicesGSEventRunModal + 104
frame #27: 0x00000001c08e5c38 UIKitCoreUIApplicationMain + 212 frame #28: 0x00000001041aa418 PABmain(argc=2, argv=0x000000016bc5b7d8) at main.m:14:13
frame #29: 0x00000001938aa8e0 libdyld.dylib`start + 4


Sonarqube improvements

This improves on the previous template using some lessons learned from client engagements. This template in conjunction with changes to the Docker build for SonarQube will allow for more reliable configuration of LDAP/Active Directory integration.

@InfoSec812  - I have not used SonarQube but this req has been hanging around a while so Im going to take the executive decision to merge it in.
fingers crossed  👍

@springdo I'm all for you merging stuff, but please run the CI job first and make sure there are no regressions


Check command name on pid check for pid confliction after OS restart

On unexpected OS restart, there happens that different process uses the same pid as mackerel-agent before restart. We should start the mackerel-agent, when it finds a process matching the old pid file but is not mackerel-agent.

Thank you.


Create Detection Simulator which uses Platforms/Sensors

Create a simulator, which takes in ground truth of targets, and detection simulator which has one/multiple platforms with one/multiple sensors, producing detections.

I believe with the sensors measure method, this would be fairly easy to implement, using current detection simulator as an initial guide.


Feat: Improvement of UI in contact us page

Describe the feature
Currently the UI of contact-us page looks like this

We can improve its UI and make it better
Add ScreenShots

Record

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

Hi @SUGAM-ARORA i have done some work on this issue
and it is looking like this

@upsaurav12 Kindlhy don't change the ui of contact page. It looks better before


Ability to read private immutables

Component
Forge
Describe the feature you would like
It is currently impossible to read private immutable variables in Foundry because of how they work.
Immutables are, similarly to constants, inlined in the bytecode directly and PUSHed where they are needed.
The issue is that immutables are, as opposed to constants, not known before the contract construction.
This makes them, even more tricky to read if private. Because that would imply reading the code and parsing what's of interest, making it not scalable as the code change, or optimizations.
Example:
contract HardToRead {
    uint256 private immutable val;

    constructor(uint256 _val) {
        val = _val;
    }
}

My proposition would be to add a cheatcode to read immutables, and constants directly from the code called codeLoad (very open to propositions).
It would work by using the solc output, probably the bytecode to source code mapping in order to generate bindings for the immutables and constants that are defined in the contract and expose them through the cheatcode.
Additional context
No response

I'm happy to take this one

Did you take it? :D

Nope @spaceh3ad !

Do we currently have a way to do that from cast?
Otherwise what choice do we have for private or internal var?

@Ethnical you can use cast storage or load storage slot with vm.load()

@spaceh3ad How this is possible since this is not inside the storage as this is inside the bytecode directly?

+1 to this feature!


.summary() does not report number of parameters correctly when model.trainable=False

For the example below, .summary() reports the same number of parameters for the first two calls.  I  believe the second and third calls should both report total params as 0.
vgg = keras.applications.vgg16.VGG16(include_top=False)
vgg.summary()  # First call, total params 14714688
vgg.trainable=False
vgg.summary()  # Second call,  total params 14714688
for k in vgg.layers:
     k.trainable=False
vgg.summary()  #third call, total params 0

@fchollet Was this fixed?  I can't find it in the commits?

Fixed.


update get_preamble

updated a syntax fix , otherwise it is returning empty

First and last commit are now obsolete and were already fixed in the master.  "updated print_module" commit was cherry-picked and is now in master.  This push request is now closed.


Feature Request: Refer to the current fava filters (time, account, filter) in link field

as per above, is that possible to refer to the fava's current filters, including time, account and filter?
Thanks

hi @ileodo, yes that's possible, take a look at the example dashboard:
https://github.com/andreasgerstmayr/fava-dashboards/blob/4d6340babb69ce77722cdcafbb17262d25a08fea/example/dashboards.yaml#L592
You can access the account and filter in the same way.

thanks @andreasgerstmayr, it would be great to just support a special variable name in the link filed which will be replaced with the time instead of manually do it in js.

I'd like to keep the extension as simple as possible, and don't plan to support this for now.

@ileodo: Related to this, just wanted to share this snippet of code that makes the above request pretty easy to implement within the new utils configuration:
# dashboards.yml

utils:
  inline: |
    const linkReplacer = () => {
      const windowUrl = new URL(window.location.href);
      window.document.querySelectorAll('h2 a').forEach(function (el) {
        const linkUrl = new URL(el.href);
        linkUrl.searchParams.set('time', windowUrl.searchParams.get('time'));
        linkUrl.searchParams.set('conversion', windowUrl.searchParams.get('conversion'));
        el.href = linkUrl;
      });
    }

    linkReplacer();

This JS snippet runs after each page load, loops through all the dashboard's panel headlines, and updates their href with the current page's time and conversion parameters. It's easy to extend with other dynamic parts as well.

@mattmattmatt thanks for the snippet!
I've added a generic way to copy Fava's filter parameters to all links in #41.


⚠ Contemporanea B2B has degraded performance

In 5ec520c, Contemporanea B2B ($SITE_CNTMB) experienced degraded performance:

HTTP code: 200
Response time: 11592 ms

Resolved: Contemporanea B2B performance has improved in 5afe009.


Add var to merra2

This PR adds support for the variable "Root-Zone Soil Moisture"  in the CMORization script for the dataset MERRA-2.

Tasks

[x] Give this pull request a descriptive title that can be used as a one line summary in a changelog
[x] Circle/CI tests pass. Status can be seen below your pull request. If the tests are failing, click the link to find out why.
[x] Preferably Codacy code quality checks pass, however a few remaining hard to solve Codacy issues are still acceptable. Status can be seen below your pull request. If there is an error, click the link to find out why. If you suspect Codacy may be wrong, please ask by commenting.
[x] Please use yamllint to check that your YAML files do not contain mistakes
[x] No new dependencies.

Modified data reformatting script

[x] Test the CMORized data using recipes/example/recipe_check_obs.yml, to make sure the CMOR checks pass without errors
[x] Tag @remi-kazeroni in this pull request, so that the updated dataset can be added to the OBS data pool at DKRZ and synchronized with CEDA-Jasmin

I will take on this after #1657 is merged

looks good to me from a technical standpoint - apart from the comment about not mixing shell scripts in source code, all's fine. Could you please merge the latest master in here so we have the latest functionality?


No image for thumbnail (Ender 3 v3 KE)

Integration version - 1.1.1
There are similar closed issues, however for my Creality Ender 3 v3 KE it does not work
The printer used is Creality Ender 3 v3 KE with Klipper and Fluidd firmware installed according to the official manual on GitHub (https://github.com/CrealityOfficial/Ender-3_V3_KE_Annex)
The fingerprint thumbnail does not appear in my settings, I am attaching the debug log files and a screenshot of the problem

home-assistant_moonraker_2024-03-25T19-18-05.387Z.log

What is your slicer?

What is your slicer?

Latest Ultimaker Cura (5.6.0)
In settings enabled "Upload" > "Format" > "UFP with thumbnail"

In the Fluidd interface, the thumbnail link looks like this in my case
http://<IP_ADDRESS>:4408/server/files/gcodes/.thumbs/CE3V3KE_Core Tile_PETG_SP.png

I have the same printer and had the same issue. You have to disable the Creality server to get the thumbnail to show.
Follow the instructions for installing the script here
Once I removed the Creality server the thumbnail started to display.

I have the same printer and had the same issue. You have to disable the Creality server to get the thumbnail to show.
Follow the instructions for installing the script here
Once I removed the Creality server the thumbnail started to display.

I installed the script and reinstalled moonraker + fluidd, what do you mean by Creality Server? Deactivating the Creality Web Interface setting in the Customization section?

I installed the script and reinstalled moonraker + fluidd, what do you mean by Creality Server? Deactivating the Creality Web Interface setting in the Customization section?

Yes, deactivate the Creality Web Interface. Sorry, I forgot what it was called. Will take a few seconds but the thumbnail will then appear in HA as long as you use a slicer that adds them to the Gcode. I've used the Creality one, Cura and Orca and all those proved thumbnails.

I confirm that it is necessary to do as described:

https://guilouz .github.io/Creality-K1-Series/helper-script/helper-script-installation/
After reinstalling moonraker and fluidd, you must deactivate the Creality Web Interface
Success

Link to Instructions for disabling the web interface after installing the script:
https://guilouz.github.io/Creality-K1-Series/helper-script/remove-and-restore-creality-web-interface/


enable overlap_comm in deepspeed

The training process does not converge with DeepSpeed v0.15.0 ?
Back line is PPO with overlap_comm = True


Bump go-sdk api to latest version - model 4.4.18

The problem
New api-model is available, we should upgrade the go-sdk to allow new features. Some will be needed later for terraform and OCP IPI.
https://gerrit.ovirt.org/#/c/111373/

@imjoey looks like you did the versions bumps before. Are you still maintaining it?

@emesika

Most probably there will be api-model 4.4.19 next week, so please consider if it's worth to release this week


Add notification key to login

Description:
Add ability to set a notificaiton_key to the login.  This is based on discovery documented here: https://github.com/fronzbot/blinkpy/discussions/770
Related issue (if applicable): fixes #
Checklist:

[x] Local tests with tox run successfully PR cannot be meged unless tests pass
[x] Changes tested locally to ensure platform still works as intended
[x] Tests added to verify new code works

I think we are ready for a release (at least of the other PR's that were added).  I would like try to get it into the next HA release.


No such file go-bindata

Was able to run until bootstrap, but when trying to make build, got an error saying that there is No such file or directory.  I also got the same error when executing as individual lines:
go run ./tools/config_gen ./config_templates/config . -- ran successfully
go-bindata -ignore secrets\.yml -ignore config/config.go -modtime<PHONE_NUMBER> -o config/config.go -pkg config config/.. -- failed
Error message:
make: go-bindata: No such file or directory
make: *** [config] Error 1

My guess is go-bindata is not where it's supposed to be?

Also having this problem

Please try to run the scripts/bootstrap.sh

resolved


Repeat Bot Messages Reply On Message Event

Describe the bug
The "message" event suppose to reply one time but the bot is replying two times even the (!message.author.bot) condition is checked still it replies two times.
To Reproduce
Steps to reproduce the behavior:

Setup the "message" event
send a message

Expected behavior
The bot should reply one time only instead of repeating twice.
Screenshots

Try this or provide a minimal repository for replay
@Injectable()
export class BotGateway {
  @On({event: 'message'})
  async onMessage(message: Message): Promise<void> {
    if (!message.author.bot) {
      await message.reply('I\'m watching you');
    }
  }
}

This work for me

only difference is I am using @Controller() annotation instead of @Injectable else all code is same. I was trying this example only. The doc mention we can use any of annotation right

Yes, it works too

Really not sure wts wrong with mine way of doing can you see.

it's like this replying two times.

Sorry it's just not this everything is coming two times...that ready event also firing two times...

This is possible only if you have announced twice a subscription to the "message" or "ready" event.
Like this:

Check your code pls

Ok sorry, It was a problem with my code. I was declaring the bot controller in controller too causing it to run two times. We can close the issue. Thanks


Access Functions

While I'm trying to get familiar with developing in Python for Unreal, I realised that I didn't know how to access funtions. Currently we have access to properties (.get_property, .set_property, .properties) and they work fine but how about functions? I saw that in the UEPyModule.cpp there are a few related functions (.find_function and .call_function") but I can't make them work. I assume that I'm doint something wrong.
That's a simple example of how I was trying access Actor's GetLevel() function:

Scripts\test.py
def fun():
    selected_actors = ue.editor_get_selected_actors()
    for actor in selected_actors:
        fn = actor.find_function("GetLevel")
        ue.log(str(fn))

This prints "None". What am I doing wrong?

Only the function marked (in the docs) as UFunction (the ones with the 'u' logo) can be called via reflection:
life = actor.GetLifeSpan()

"private" functions must be exposed natively.
By the way the rule is that if a function is availabel to blueprint, you can call it in python via reflection

Can we close it ? Or do you prefer do add support for GetLevel() natively ?

Hi @rdeioris, sorry for the late reply. I'm assigned to another project the past couple of weeks but I expect to get back on Unreal later down the line. I think you should close it, yeah. Thanks.


fix(payment): continue payment if it is not internal

Context

fixes #

Changes

Why is this change needed?

@raducristianpopa Transactions were not working on rafiki.money at all on friday and I think this is the fix....
@dragosp1011 correct me if I am wrong :D


BundleTracker Tests

This includes most of the tests for BundleTracker API methods in BundleTrackerMethodTest.cpp and tests using 2 out of the 4 user customization workflows in BundleTrackerCustomCallbackTest.cpp.

Codecov Report

Merging #7 (37e1e24) into bundle-tracker (495e94f) will increase coverage by 0.37%.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           bundle-tracker       #7      +/-   ##
==================================================
+ Coverage           89.83%   90.20%   +0.37%
==================================================
  Files                 225      238      +13
  Lines               12212    12808     +596
==================================================
+ Hits                10971    11554     +583
- Misses               1241     1254      +13

Impacted Files
Coverage Δ

util/include/cppmicroservices/util/String.h
50.00% <0.00%> (-50.00%)
:arrow_down:

...include/cppmicroservices/BundleTrackerCustomizer.h
71.42% <0.00%> (-28.58%)
:arrow_down:

util/src/Error.cpp
70.83% <0.00%> (-19.17%)
:arrow_down:

util/include/cppmicroservices/util/MappedFile.h
83.33% <0.00%> (-4.91%)
:arrow_down:

...mework/include/cppmicroservices/ServiceReference.h
96.00% <0.00%> (-4.00%)
:arrow_down:

...ork/include/cppmicroservices/detail/CounterLatch.h
93.54% <0.00%> (-3.23%)
:arrow_down:

framework/include/cppmicroservices/detail/Log.h
97.14% <0.00%> (-2.86%)
:arrow_down:

.../cppmicroservices/detail/ServiceTrackerPrivate.tpp
82.85% <0.00%> (-2.15%)
:arrow_down:

framework/include/cppmicroservices/Any.h
92.72% <0.00%> (-1.48%)
:arrow_down:

...mework/include/cppmicroservices/ServiceInterface.h
95.83% <0.00%> (-0.84%)
:arrow_down:

... and 86 more


Page loaded but waitload/waitidle reach generates an error => No XHR in outputs

Current Behavior:
I'm currently crawling a headless site in order to detect as many XHR requests as possible.
While debugging, I noticed that some pages are well loaded in the browser and are stable. However, katana doesn't see them that way. The code waits for the timeout to be reached before returning the error.

The error is linked with this code:

The context exceeds because the timeout is reached, rendering the DOM inaccessible and causing the error.

However, in the browser, the page seems to be fully loaded.

According to the code, the page should have been closed and the reply processed, but this is not the case. The code is waiting for the timeout.
The problem is that XHR and other requests detected before the timeout are not written to the output because of the error.
Expected Behavior:
I'd like to understand why the page is considered unstable and yet appears to be so when viewed in the browser.
Steps To Reproduce:

Run Katana in headless mode
Choose web page endpoint with XHR and other requests starting from the page
Open browser for debugging
Check that a page is fully loaded but does not close in the browser, meaning that it is about to reach the defined timeout.

Anything else:
It could also be a performance problem with my computer. However, I'm on a MAC OS:

2.6 GHz Intel Core i7 6 cores
16 Go 2667 MHz DDR4
And I also had the same problem on another PC.

Have a nice day !

katana can try use rod's Page.waitStable or waitDOMStable method instead of idle


Commit closes active file

Whenever I do a commit (I usually do CTRL+A A to add all and commit), after I save the commit message both the commit file and my previously active file are closed.
This has always happened to me since I've used this package (since the beginning of the year I think) but only know did I think of reporting it. Currently I am on windows 8 and atom 0.209.0, but it also happened in windows 7 and across all versions of atom.

Has this been happening in the most recent versions of the package?

It seems to only happen sometimes. Right now, I had 3 files opened, first file active, did add all and commit, entered message and save. Message and previously active tab were closed.
Afterwards I had only one tab open, same sequence of events, but it did not close.

I have the same issue

I am running into the same issue.

I am also having this issue.

This bug has disappeared for me after updating atom to the latest version (1.0.3).

@filipesilva Is this still an issue for anyone?

I just got it myself. Let me get back to you in a few days of usage to make sure it wasn't a fluke.

Ok after a few days working with it, I can verify the problems still happen (double commits windows, closing current window) roughly with the same frequency.
This is on a clean install on a win10 machine now.

Confirming that saving a commit message window closes active file tab. Issue still exists.

I confirm also on Atom version 1.0.5 . The bug where it closed the active tab had disappeared until this version.

Can someone share with me a video or gif so I can get the context around this? I think it'd be really helpful

Oh man this is great! Thanks :D


Publish 8.5-20231110012027+0000

Publish 8.5-20231110012027+0000

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


[Bug]: Tensorflow docs are not working

Bug Description
The tensor flow docs cannot be queried. Using the keyword tf results in an error
Relevant Screenshot
No response
To Reproduce
No response
Debugging Log
[11:24:52.553] Logging Started...
[11:24:54.625] Search ALL the docs![Script Filter] Queuing argument '(null)'
[11:24:55.223] Search ALL the docs![Script Filter] Script with argv '(null)' finished
[11:24:55.230] ERROR: Search ALL the docs![Script Filter] Code 1: /Users/tim/Library/Application Support/Alfred/Alfred.alfredpreferences/workflows/user.workflow.062E4F52-4BC7-4ED9-A63D-6509B86D527A/devdocs/dev-docs-search.js: execution error: Error: SyntaxError: JSON Parse error: Unexpected EOF (-2700)

Workflow Configuration

Checklist

[X] I have updated to the latest version of this workflow.
[X] I am using Alfred 5. (Older versions are not supported anymore.)

Looks like a cache file wasn't updated in time for whatever reason.
Delete the file ~/Library/Caches/com.runningwithcrayons.Alfred/Workflow Data/de.chris-grieser.doc-searches/keyword-slug-map.json and it should work. The problem should not occur again after that


Fix fighter bay names

most of the fighter bays were defined as fighter instead of Fighter
because its case sensitive as of the categories update

Interesting, seems I forgot to push a local change once again. Thanks for mentioning.


There are some problems building the image

Describe the bug
I try to use the command buildx build -t wws:0938 -f image/Dockerfile , but I have a problem:

So I tried to modify the image to rust:1.66.0-slim and tried to build again. But again I got an error, seems to be missing openssl：

So I tried to modify the image again and changed it to rust:1.66.0, To my surprise, the build was successful.
Reproduction steps
I tried to run it using the built image, but I encountered a problem and I don't know how to solve it.

Expected behavior
run successfully
Additional context
No response

Thank you for this report @dierbei! I have opened https://github.com/vmware-labs/wasm-workers-server/pull/184 to address all the issues.

@dierbei Everything should be fine now, please reopen if any of the mentioned issues persist.


DB misses some values when queried immediately after start

I investigated this report by @nipuntalukdar: https://github.com/prometheus/tsdb/pull/211#issuecomment-347174740
And heres what happens, we init head, then run the compaction loop. Now before we compact the head, we set the head.minTime to be the min-time of the current block range: https://github.com/prometheus/tsdb/blob/master/head.go#L368
Which means there are values that are ONLY in head but no visible to the querier for a short time before the first compaction. Not sure if this is worth fixing, though. @fabxc
@nipuntalukdar Also, the solution there is not really a good one and might allow duplicate values from both head and compacted blocks.

@gouthamve do you know if this is fixed?

ping @gouthamve