[Issue]: Action Server does not handle timeouts

Target library

[X] Action Server
[ ] robocorp-actions
[ ] robocorp-browser
[ ] robocorp-tasks
[ ] robocorp-vault
[ ] robocorp-windows
[ ] robocorp-workitems

What happened?
Current Status
Current Action Server @action has limitless time to be executed. AI clients and internet services in general have timeouts for http requests. These range from 30 seconds up. OpenAI GPT seems to currently have Action timeout around 45 seconds.
This means that actions that take long enough will always fail from the callers (clients) point of view.
Based on experiments LLM clients such as OpenAI GPT easily can work with actions that give a separate callback url to check the results later on.
How should it work
I propose that Action Server internally switches to callback mode if action takes long enough. For example 20 seconds.
This would mean the following:

Action that takes 20 seconds or less => return result directly
Action that takes over 20 seconds => return callback url and status

calling callback url before action has finished => return callback url and status
calling callback url after action has finished => return action result

This method has been tested against OpenAI GPT and it works.
System Info

0.0.13 * Python 3.11.5 * OSX *

Seems reasonable.
Can you give a concrete example of what'd be the callback message? Would an LLM make sense of something as:
The message has not completed and in processing in the background. Please call `/get-async-result/<generated-uuid>` later to see if it completed. If it has not completed this same message will be repeated, otherwise the actual result will be provided.

And then /get-async-result/309uhsoenu]3stnp2-ue3 would be called at a later time and would return either the same message or the result.

Also, is it a problem if the return in this case is a string even if the original schema could've been marked to return an integer?

Ok, so, we'd have a /callback url path which would accept an id for the callback as a post. And then we'd return something with a 202 status asking to call that callback later.
Is that it?
Now, I'm not sure I follow:
I would first separate @action decorated functions signature from the matching http endpoint signatures. So they can differ.
What exactly do you mean by that?
As a note, internally the action-server manages everything, the @action is already executed in a different process and is managed by the action-server (so, in theory it's kind of decoupled already -- although there are definitely some internal reorganizations needed to return early while still keeping on executing the action).

What exactly do you mean by that?

I think what you have written is what I was after. Nothing else.

Is there anyway where the GPT side would provide the callback url?
Would this be essentially make it so that the GPT side becomes a poller that needs to figure out all kinds of error cases.
GPT side is developing fast, is there anything in the pipelines for this problem?

This realates also to async Actions discussed in #177. The AI app frameworks are developing fast, so this should be not a top priority just yet.
For now, we should have good design principles indicating that there are limits like request timeout and max response size that the developer needs to consider, and they vary per AI App framework.

This issue has been moved here, under Sema4AI/actions repository.


game command only accepts 1 argument

Accidentally only had the moe game command take the first argument. Need to update so it takes all remaining arguments.

Some issues with games starting with 'moe'


Rule "Read environment variable from /proc files Only" Applies Only to Containers

Describe the bug
Hi,
Not sure if this is a bug or not but I think it is.
While look at the rulesets, I noticed the following rule in falco-incubating_rules.yaml only applies to containers:
- rule: Read environment variable from /proc files
  desc: >
    An attempt to read process environment variables from /proc files. The consequences are akin to accessing traditional
    sensitive files, as sensitive data, including secrets, might be stored in environment variables. Understanding your
    environment, such as identifying critical namespaces, and incorporating extra filtering statements to alert exclusively
    for those, can enhance the rule's effectiveness.
  condition: >
    open_read
    and container
    and (fd.name glob /proc/*/environ)
    and not proc.name in (known_binaries_to_read_environment_variables_from_proc_files)
  output: Environment variables were retrieved from /proc files (file=%fd.name gparent=%proc.aname[2] ggparent=%proc.aname[3] gggparent=%proc.aname[4] evt_type=%evt.type user=%user.name user_uid=%user.uid user_loginuid=%user.loginuid process=%proc.name proc_exepath=%proc.exepath parent=%proc.pname command=%proc.cmdline terminal=%proc.tty exe_flags=%evt.arg.flags %container.info)
  priority: WARNING
  tags: [maturity_incubating, container, filesystem, process, mitre_discovery, T1083]

I think this rule should be applicable to both containers and the host. Is there any reason that the rule author decided to only apply it containers? Thanks
How to reproduce it

Expected behaviour

Screenshots

Environment

Falco version:

System info:

Cloud provider or hardware configuration:
OS:

Kernel:

Installation method:

Additional context

I suspect it was deemed potentially too noisy. Have you tried this rule without the container statement in production?
CC @darryk10

Hi,
I'm afraid it might get really noisy, especially sing open_read and without filtering by any proc.name.
This rule would require some time to get well tuner and usable for users. I can test it out and see how it goes just to see it in action.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Merge/merge datasets from swb byob

Issue #, if available:
Description of changes:
Checklist:

[ ] Have you successfully deployed to an AWS account with your changes?
[ ] Have you written new tests for your core changes, as applicable?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@bhudnell , is it supposed to be byob -> dev?

Yes, need these changes in develop so we can put our integ tests for datasets into develop


feat(hackathon): Sensor profiling CI step

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
TODO(replace-me)
Use this space to explain how you validated that your change functions exactly how you expect it.
Feel free to attach JSON snippets, curl commands, screenshots, etc. Apply a simple benchmark: would the information you
provided convince any reviewer or any external reader that you did enough to validate your change.
It is acceptable to assume trust and keep this section light, e.g. as a bullet-point list.
It is acceptable to skip testing in cases when CI is sufficient, or it's a markdown or code comment change only.
It is also acceptable to skip testing for changes that are too taxing to test before merging. In such case you are
responsible for the change after it gets merged which includes reverting, fixing, etc. Make sure you validate the change
ASAP after it gets merged or explain in PR when the validation will be performed.
Explain here why you skipped testing in case you did so.
Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/?

/test ?

/test gke-scale-tests

/test ?

/test ?

/test ocp-4-13-sensor-profiling

/test ocp-4-13-sensor-profiling

/test ocp-4-13-sensor-profiling

/test ocp-4-13-sensor-profiling

/test ocp-4-13-sensor-profiling

/test ocp-4-13-sensor-profiling

/test ocp-4-13-sensor-profiling

/test ocp-4-14-sensor-profiling


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

Thank you for contribution!!!

@IsseiAoki  please check https://github.com/IsseiAoki/SimpleCropView/issues/107 it may be simple for you but giving me sleepless nights currently..
Atleast do look at it. :-)

@corientdev
Hi,
Sorry, this library not support detailed initial crop frame position for now, but I will manage it for next version. (will release some time soon)

Hey Thanks for looking into it. Cheers!


slow performance while loading files

try >1000 line file
if you change DiffTextsSideBySide to add all the lines to stringbuilder then call AppendRow once - then the performance is fast.

I'll look into this - thanks 👍

Thanks for bringing this to the next decade! Fix at commit 5249714, also released a NuGet package. 🥳

Fixed


fix: comic 2622 coloring

Partially fixing #305, by adding comic 2622 as a special case.

Before
After

Of course, this does not solve the general problem of some comics being incorrectly inverted. I think one solution might be to check each pixel color, but I'm not sure whether that would perform well enough.  Should I open a new issue about possible solutions?

Thanks!
Sure, feel free to open a new issue if you have ideas on how to improve this - Bur I'm not sure if checking every pixel is worth it though, our current solution of (ab)using Palette.from(bitmap).generate().vibrantSwatch seems to work well enough for most comics.
Note that sometimes we may want to invert an image even though it contains color, for example some comics are black and white except for some red text added for emphasis, in which case it's ok (and better IMO) to invert the colors anyway.
Maybe the best course of action would be to just go through https://www.explainxkcd.com/wiki/index.php/Category:Comics_with_color and add more special cases for where our heuristic fails.


InitialState for nested states doesnt seem to work

Given the following state machine
When I transition to a nested state
Then transition to this state's initial state
In reality it the statemachine is currently ignoring the initial state and it just transitions to the root of the nested state.
Example:
Given the following statemachine:
  final machine = StateMachine.create(
    (g) => g
      ..initialState<Start>()
      ..state<Start>((g) => g..on<OnKickStart, Main>())
      ..state<Main>(
        (g) => g
          ..on<OnTickFirst, First>()
          ..on<OnTickSecond, Second>()
          ..coregion<First>(
            (g) => g
              ..initialState<One>()
              ..state<One>((g) => g..on<OnToggle, Two>())
              ..state<Two>((g) => g..on<OnToggle, One>()),
          )
          ..coregion<Second>(
            (g) => g
              ..initialState<Three>()
              ..state<Three>((g) => g..on<OnToggle, Four>())
              ..state<Four>((g) => g..on<OnToggle, Three>()),
          ),
      ),
  );

When: applying a OnKickStart event
Reality: the statemachine transitions to Main->VirtualRoot"
Expected: the statemachine transitions to Main->First->One->VirtualRoot and Main->Second->Three->VirtualRoot.
In this XState visualizer you can see that by triggering "Kickstart" the machine transitions to all initial states of the parallel machines.
In this PR you can see a failing test for this scenario.

I'm back at working with FSM2 (now in the real project and not in an hackathon), and I'm now stuck at this stage again.
I updated the issue to provide more clarity on what I'm facing.

Hi, it seems we're hitting the same issue with nested states (no coregions defined). This GH issue suggests it's a bug in fsm2, can you confirm?

I think the problem is the transition attempts to transition to a parent state which isn't allowed. You need to transition or fork to one or more leaf states.
The validator should probably flag the state machine definition as being in error.

A mobile app can be in the foreground or in the background.
When it is in the foreground there are a number of activities allowed/possible.
During one of these activities, the end user may press the home button, moving the app to the background.
On such occasion we may want to gracefully pause or cancel ongoing activities.
I believe an FSM can help.
For example:
final fsm = StateMachine.create((b) => b
  ..initialState<Foreground>()
  ..state<Foreground>((b) => b
    ..initialState<Idle>()
    ..state<Idle>((b) => b
      ..on<StartActivity1, DoingActivity1>()
    )
    ..state<DoingActivity1>((b) => b
      ..on<EndActivity1, Idle>()
    )
    ..on<GoToBackground, Backgrounded>()
  )
  ..state<Backgrounded>((b) => b) # are you saying this is not allowed? how would you do it?
);

the on<GoToBackground... is fine as it targets a leaf state Background.
However, I don't think I would model it that way.
Instead, I would have two (or more) states for each activity. The activities would switch between states based on GoToBackground, GotoForeground events.
.state((b) => b
..initialState()
..state((b) => b
.. on<OnForeground, Running>
..state((b) => b
.. on<OnBackground, Idle>
You may also want to consider having a separate state machine for each activity as it can make the model easier to understand.
Alternatively, have a look at the doco example of the human life cycle. The living/dead states are closer to your original idea.

Following is an updated state machine where the Backgrounded state contains nest state. I assume that's no longer what you call a "leaf state".
There, you're saying that the ..on<GoToBackground, Backgrounded>() line is no longer valid?
That example is quite close to our app's behaviour. Are you suggesting that we should migrate this fsm design to one where we have "two (or more) states for each activity"?
final fsm = StateMachine.create((b) => b
  ..initialState<Foreground>()
  ..state<Foreground>((b) => b
    ..initialState<Idle>()
    ..state<Idle>((b) => b
      ..on<StartActivity1, DoingActivity1>()
    )
    ..state<DoingActivity1>((b) => b
      ..on<EndActivity1, Idle>()
    )
    ..on<GoToBackground, Backgrounded>()
  )
  ..state<Backgrounded>((b) => b
    ..initialState<GracefulShutdown>()
    ..state<GracefulShutdown>((b) => b
      ..onEnter(...)
      ..on<GracefulShutdownComplete, Terminated>()
    )
    ..state<Terminated>((b) => b)
  )
);

Also, you wrote earlier:

I think the problem is the transition attempts to transition to a parent state which isn't allowed.

It sounds arbitrary and I can't justify it, could you explain why?
I've seen it too in xstate and they created "final states" which, when transitioned to, transition to their parent state. I haven't found the equivalent in fsm2.

close and stale.
The equivalent of 'final states' (as I understand it) is leaf states.  You can only transition to a leaf state, the tree of parent states is then implied by the path to the leaf state.


Propagate the request id to nomis API

Stores the request id coming from X-Request-Id header and uses for request
logging and to pass it through to the Nomis API.

Similar to https://github.com/ministryofjustice/prison-visits-public/pull/27

Looks good, albeit with the same niggle as the other PR.

@alan LGTM.  I'll refactor it after the fashion of whatever gets done on the refactor referenced in ministryofjustice/prison-visits-public/pull/27.


Manually set loading page transition?

Is there a way to manually set the loading page transition to use the same animation in other cases that are not route changes?

You can use something like this:
            async login() {

                this.$root.$loading.start();

                try {
                    // ...
                } catch (e) {
                    console.log(e.message);
                }

                this.$root.$loading.finish();
            }

Thanks that works awesome.

This works on the client side in the mounted life cycle method.  But when I refresh the page, I get Vue warn]: Error in mounted hook: "TypeError: this.$root.$loading.start is not a function" in my client-side console.  Is my component being mounted before that function is available?  Is there any way around this?  Thanks!

Did you try to use
if (process.browser) {
  // code to run only in browser
}

(or process.BROWSER_BUILD if version < 1.0.0-rc3)

@sbefort  please create a reproduction example or using glitch

Here is a glitch:
https://sturdy-wave.glitch.me/
https://glitch.com/edit/#!/sturdy-wave

I have a similar issue at the moment using the apollo-module. As I want the animation/loading spinner to wait till my graph-ql query is finished I would like to throttle the animation. Is there any way doing this?

Will be fixed in the next release. I'm closing it, but feel free to comment it in the future.

@alexchopin same here with window.$nuxt.$root.$loading.start() or this.$root.$loading.start(). Will it be fixed in version 1? thank you!!!!

I also have the problem in the "mounted"

also need manual trigging loading actions

I've noted that the code in https://glitch.com/edit/#!/sturdy-wave is still giving the "this.$root.$loading.start is not a function" error. Was this resolved?
nextTick doesn't seem to work for me. I get two errors:
unknown action type: orders/fetchOrders
and
TypeError: Cannot read property 'then' of undefined
Help?

Hey Team - has there been any movement on this issue? Would really appreciate getting an update on current status.

@jkd77 Use this.$nuxt.$loading (docs: https://nuxtjs.org/api/configuration-loading#the-loading-property). If you still have issues, please create a new one.


foxmail: Add version <IP_ADDRESS> with new checkver

Closes #XXXX

Relates to #XXXX

[x] I have read the Contributing Guide.

Foxmail is Tencent's free email client.
/verify

/verify
Foxmail is Tencent's free email client.

Closes #10685

Closes #10685

Closes #10685
@Zliced13 Thank you.


Packs don't download fully on slow connections.

Describe the bug
When you try to download packs on a slow connection, the download stops part way through and a new download starts (if there are anymore queued).
To Reproduce
Steps to reproduce the behavior:

Go to the pack downloader on a slow connection.

Expected behavior
The download to complete before moving to the next item.
Screenshots

Desktop (please complete the following information):

OS: Windows 7 x64 SP1
0.63.0 x64

Additional context
N/A

Are you on wifi? My guess is this is due to an unstable connection rather than a slow connection (though the two aren't mutually exclusive)

No, I'm connected to my router via Ethernet.

Open a command prompt and run ping east.stepmania-online.com -n 100, and let it go until it's finished, then paste the summary at the end, which looks something like this:
Ping statistics for <IP_ADDRESS>:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 31ms, Average = 30ms

The mirror did work better, thanks for the help. Perhaps the mirror should be an option for first time installations.

bundle download options for new installs always using non-mirror links is an oversight on our part
good observation

Accomplished by https://github.com/etternagame/etterna/commit/49bcaa357d3e96f3c7a853efc3ceb05c5850d454


Integrate v0.12.1 fork choice tests

Description
Had to revert https://github.com/PegaSysEng/teku/pull/2154 on the 0.12.1-integration branch because those are the 0.11.1 fork choice tests.  We need to get the v0.12 fork choice tests and integrate them.
Need to also fix the way they're integrated as they're being run as a separate test, not actually picked up by the reference test runner because they're under src/test/java instead of src/test/resources with the rest of the reference tests.

After offline discussion with @ericsson49, we're waiting for the v0.12.2 release in order to update the tests and later incorporate them back into Teku tests.


Impact of fixing start and stop codons

Hi. I used the fix_start_stop flag on an annotated genome; however, after fixing the codons, none of the other metrics changed? I was wondering if you can please explain why that is? Thanks!

Hi @tarunaaggarwal  - I believe that the fix_start_stop codons is just annotating the start and stop in your GFF output, so it doesn't filter out gene models that don't have appropriate start and stops.   @bruab will need to confirm.

Hi @tarunaaggarwal! What @nextgenusfs says is correct -- all the --fix_start_stop option does is inspect CDS boundaries and create start/stop codon features where appropriate. Are you looking to do something more elaborate?

No not necessarily. It was just worrisome when after fixing the start and stop codons, none of the other metrics changed since they depend on where these codons are. For instance, shouldn't the CDS total length change if start and stop codons shift?

Perhaps the name (--fix_start_stop) is throwing you off - it is only annotating start and stop codons and is thus not changing your gene models at all, so the metrics shouldn't change.

Oh I see. Alright. Well, thanks a bunch for your help and explanation!

@nextgenusfs Thanks!


Defocus/focus in video call

Hey there,
I'm facing an autofocus (defocus/focus) issue with the rear camera in a video call, scenarios is when I move and stop then the camera tries to focus/defocus irrespective of the distance between the object and camera, can someone help me to disable this
Thanks
Sachin

is system camera work?

you can try this function. but the default param is false.
https://docs.agora.io/en/Interactive Broadcast/API Reference/react_native/classes/rtcengine.html#setcameraautofocusfacemodeenabled

Yes, the Device camera works, I have a focus/defocus problem with Agora video calling with rear camera, I'll check out that link
Thanks

Update +,
I figured out the reason for defocus/focus, if i set below configuration only then its happening and that too only on iOS
await this._engine?.setVideoEncoderConfiguration({
dimensions: { width: 1280, height: 720 },
frameRate: 30,
bitrate: 1710,
});

sorry for the late reply, is this problem remain?

you can reopen this issue if it still exists.


empty sitemap since 4.1.0

I'm using @nuxtjs/sitemap@6, and since updating @nuxtjs/robots to 4.1.0 the sitemap.xml returns empty.
see: https://stackblitz.com/edit/nuxt-starter-uk5gcm

Thank you for reporting this, I've pushed up a fix in v4.1.1.

Thanks for the quick response! I've updated to v4.1.1 but I'm still experiencing the issue. production build or order of modules does not affect it. do I need to enable it somehow?
https://stackblitz.com/edit/nuxt-starter-uk5gcm

Same problem here. Example stacktrace : https://github.com/Skyost/MesCoursDeMaths/actions/runs/10469819778/job/28993654625#step:6:3427.

Same problem here, downgrading to 4.0.2 fixed it:
Works using<EMAIL_ADDRESS>in combination with downgraded<EMAIL_ADDRESS>

I'm very sorry about this, it seems like I was missing test coverage on the robot meta tag in production. I've pushed up a fix in v4.1.2 and will release a Nuxt SEO release with this patch now as well.

No Problem, thanks for the quick fix!

Is the bug fixed for you @felixranesberger ? I have the same problem, even with v4.1.2...

Just tried out the new version of<EMAIL_ADDRESS>which uses<EMAIL_ADDRESS>and everything seems to work.
sitemap.xml is filled with entries, also robots.txt and robots-meta-tag seems to work just fine, so no issues on my side.

Thanks for confirming @felixranesberger.
I've tested using Stackblitz to also confirm the issue is solved: https://stackblitz.com/edit/nuxt-starter-kjedrj?file=package.json
Again sorry for the issue, I was moving house yesterday so thought I could just quickly push up a fix but I missed the case of not having any robot rules. Test cases now cover this properly.


Corrected style of WIP balloons

Before:

After:

@AlexandreDeCarli where condition for user when used server jira?
I look on you picture, and see interface the cloud jira only....
You need take this into account in your decision

I see @pavelpower... I have only the cloud jira instance to test.
What is your suggestion to correct or solve this issue?

yep, you right
this the problem have only on cloud jira
check, please, after publish version 2.16.0


[Snyk] Upgrade org.bouncycastle:bcprov-jdk18on from 1.72 to 1.74

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade org.bouncycastle:bcprov-jdk18on from 1.72 to 1.74.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released 23 days ago, on 2023-06-15.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Fixed in https://github.com/swedenconnect/credentials-support/pull/42


Redesign and rewrite

Description
Signature validator rewritten.

Users now enter API URL directly. This allows them to call any URL they choose.
If api.gov.sg API is used, .i and .e subdomains are automatically added and displayed
Implementation for generating base strings and signatures are now in line with node-apex-security
Flow and UI redesigned
Rewrite of signature validator and testservice. All redundant code removed

How Has This Been Tested?
Manually

Some conflicts on the package files to be resolved

More commits coming, just wanted to create this first
On Fri, Sep 28, 2018, 11:37 Robin Cher<EMAIL_ADDRESS>wrote:

Some conflicts on the package files to be resolved
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GovTechSG/apex-signature-validator/pull/11#issuecomment-425311081,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH-bzpuU2Axbtp_-YWZbhgR5zxHqwPE_ks5ufZlqgaJpZM4W9y3m
.


wolkennacht

Did you read the instructions?

[X] I have read the README, including the known-limitations section.

The problem
Encountered the following in log file
What version of this integration has the issue?
1.3.3
What version of Home Assistant Core has the issue?
HA 2022.11.3
Home Assistant log
This error originated from a custom integration.

Logger: homeassistant
Source: custom_components/knmi/weather.py:103
Integration: KNMI (documentation, issues)
First occurred: 04:14:57 (480 occurrences)
Last logged: 08:14:28

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 813, in _update_entity_states
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 532, in async_update_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 583, in _async_write_ha_state
    state = self._stringify_state(available)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 551, in _stringify_state
    if (state := self.state) is None:
  File "/usr/src/homeassistant/homeassistant/components/weather/__init__.py", line 832, in state
    return self.condition
  File "/config/custom_components/knmi/weather.py", line 103, in condition
    return CONDITIONS_MAP[self.coordinator.get_value("image")]
KeyError: 'wolkennacht'

Diagnostics
No response
Additional information
No response

I'm getting a little confused, I've recently removed wolkennacht as it's not documented on the website: https://weerlive.nl/delen.php
I'll restore it for now and contact the supplier in the mean time.

This has been fixed in 1.3.4, similar issues will be handled better, now with an error log instead of a error trace:
2022-11-20 07:27:39.875 ERROR (MainThread) [custom_components.knmi] Weather condition wolkennacht (for image) is unknown, please raise a bug

I wonder if I could close this issue?

I want to keep this until I've heard from the supplier. I've sent them a reminder mail today

Still no reply. Will close this now


fix: make devimint backup & restore test backwards-compatible

Fixes #4106
Includes commit from https://github.com/fedimint/fedimint/pull/4136 to verify CI passes. Will rebase once merged.

Flakey code coverage, force pushing to start CI again.
Backwards-compatibility completed and everything passed 🎉
Backwards-compatibility tests summary:
fed_version  client_version  gateway_version  exit_code
v0.2.1       v0.2.1          current          0
v0.2.1       current         v0.2.1           0
v0.2.1       current         current          0
current      v0.2.1          v0.2.1           0
current      v0.2.1          current          0
current      current         v0.2.1           0

(manually re-ran CI b/c a bunch of stuff seemed stuck)


Standardize See also sections

In docs/build directory

@corob-msft - Could you review the proposed changes? Thanks.


Span attribute count limit doesn't work by the specification

Please answer these questions before submitting a bug report.
What version of OpenTelemetry are you using?
"@opentelemetry/api": "^1.0.3",
"@opentelemetry/sdk-trace-base": "^1.0.1"
What version of Node are you using?
v16.13.0
Please provide the code you used to setup the OpenTelemetry SDK
// index.js
const opentelemetry = require('@opentelemetry/api');
const { BasicTracerProvider } = require('@opentelemetry/sdk-trace-base');

new BasicTracerProvider().register();

const span = opentelemetry.trace.getTracer('default').startSpan('foo');

span.setAttribute('key', 'value');
span.setAttribute('foo', 'bar');
span.setAttribute('mirko', 'slavko');
// the span has 1 attribute even though it's been run with OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT=128 and OTEL_ATTRIBUTE_COUNT_LIMIT=1

span.end();

What did you do?
I started the script with OTEL_ATTRIBUTE_COUNT_LIMIT set to 1 and OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT set to 128
env OTEL_ATTRIBUTE_COUNT_LIMIT=1 OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT=128 node index.js
What did you expect to see?
I expected it works by the specification:

If both a general and a model-specific limit are implemented, then the SDK MUST first attempt to use the model-specific limit, if it isn't set, then the SDK MUST attempt to use the general limit

What did you see instead?
The general limit is used instead the model-specific. So the limit is set to 1 not 128
Additional context
Add any other context about the problem here.

Hi @dyladan, could you assign this to me? I'm already working on it


fix(app): Refactor launcher

Codecov Report

Merging #93 into master will increase coverage by 0.04%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master      #93      +/-   ##
==========================================
+ Coverage   91.32%   91.37%   +0.04%
==========================================
  Files           5        5
  Lines         173      174       +1
  Branches       22       22
==========================================
+ Hits          158      159       +1
  Misses         15       15

Impacted Files
Coverage Δ

lib/utils.js
94% <66.66%> (-1.75%)
:arrow_down:

lib/build.js
89.01% <85.71%> (+0.83%)
:arrow_up:

Continue to review full report at Codecov.

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


[PNOR] Software version Management

Support PNOR check in the test FW version
Follow up task from
https://gerrit.openbmc-project.xyz/#/c/2355/

could you pls add estimate. Thank you.

The changes has not yet came.. Gunnar will let me know once its up from developement

This is valid with the new PNOR, will start off coding a bit

This test code is already in place


core.memory: get the page size from sysconf

The page size is hardcoded to 4K, which is a problem on systems which
define different value for it. Use sysconf(_SC_PAGESIZE) to determine
the actual page size.
base_page_size is removed from memory.lua since is not used.

What systems are these? See also #712.

The system in question is AArch64 compiled with CONFIG_ARM64_64K_PAGES.
But this is also valid for PowerPC which can have 16K, 64K and even 256K page size.
This patch does not support those platforms, it just uses a more portable. POSIX compliant and non-hardcoded way to determine the page size value.

The master branch does not accept this kind of change. There need to be separate posix, arm, ppc branches where somebody is maintaining ports. If ports work well and have users then we can plan for merging them onto master.
There could also be a branch for collecting general portability patches but again this is not master.
More on #712.

As far as I can tell, this isn't entirely irrelevant even on x86_64: https://en.wikipedia.org/wiki/X86-64#Page_table_structure
I think this patch is worth merging, for what it might be worth.

I don't think that replacing 4096 with sysconf(_SC_PAGESIZE) is architecture specific.
It's just a more generic way to determine the value.
It is also a better programming style than having arbitrary and unexplained numbers all over the code.
I understand #712, but this is not porting, although the patch makes this particular part of the code a little bit more portable. If this is not suitable for master then so be it.

I agree that the magic number is bad and it would be better to avoid that.
I am not wild about using a GCC extension to do this though. I want to rewrite as much of the C code we have as possible in Lua based on ljsyscall and adding new C code that is potentially hard to rewrite seems like a step in the opposite direction.

@nnikolaev-virtualopensystems Thank you for your understanding :). I hope that we will have a portability branch in the future for collecting these changes (and that once ports are working well we could also merge them onto master).
In the short term I'd like to come up with a tagging scheme on Github to make these portability fixes easy to find for the day when somebody decides to collect and integrate them on a branch. There have been about half a dozen such changes submitted to master. Working this out on #725.

I think this patch is worth merging, for what it might be worth.

@kbara My beef about merging this as an improvement for x86-64 is: shouldn't we rewrite this C code in Lua? I want to use C very conservatively so that Snabb hackers need only basic C skills. So I am not enthusiastic with replacing a magic number (okay, lame) with a new GCC trick that I don't really understand using an advanced compiler feature that I have never seen before.

@kbara Historical context is that most of the C code in Snabb Switch should never have been written: we should have written it in Lua with ljsyscall. Unfortunately, we didn't use ljsyscall back in the beginning so every function that made non-trivial use of system calls or the standard C library had to be written in C and called via FFI. This C code then has a natural tendency to spread e.g. because an extension is needed and it is inconvenient to do in Lua because of the FFI barrier so we add it to C instead.
I really want to weed out this code. I don't feel that there is a place in Snabb Switch for C code that could have been written in Lua. I dislike the way the smattering of C code that we have is consuming brain cycles on talking about POSIX compliance and so on. I'd much prefer to work with tools that don't require such a level of language-lawyering to use effectively.

I will close this as it doesn't seem to be going anywhere. Please reference this PR in case an ljsyscall based alternative is found.


Use new resolve API to support TypeDoc v0.24

Close https://github.com/Gerrit0/typedoc-plugin-mdn-links/issues/7

Switch from app.renderer.addUnknownSymbolResolver to app.converter.addUnknownSymbolResolver. I'm not sure if I use the new API correctly, but it works fine in my project.
Updated peerDependencies to use typedoc versions that support the new app.converter.addUnknownSymbolResolver API.
Updated tsconfig.json and added esModuleInterop to fix some build errors.

Thanks!


Add spark-master configuration & PySpark1xJob support for --jars

LGTM!

Thanks @jthi3rry! Can you please also fix @berkerpeksag's comment in a new PR? :)


SLF4j warnings when running with gradle 5.3

Using gradle 5.3.1 and spotbugs gradle plugin 1.7.1. Every time i run my build i get the following warnings.
Others have reported this on closed ticket https://github.com/spotbugs/spotbugs/issues/823
> Task :web:spotbugsMain
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

> Task :wsclient:spotbugsMain
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

Looks like a duplicate of https://github.com/spotbugs/spotbugs-gradle-plugin/issues/133

Still a problem in Gradle 5.4.1 w/Spotbugs 4.0.0-beta2.

the problem is that plugin adds slf4-simple dependency with fixed version 1.8.0-beta4 https://github.com/spotbugs/spotbugs-gradle-plugin/blob/master/build.gradle#L28 when Spring Boot uses dependency management plugin to import slf4 version from Spring Boot Parent pom (spring-boot-starter-parent) which is 1.7.30 (as for version 2.2.6.RELEASE). So the result classpath of spotbugs looks like this:
~/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-simple/1.8.0-beta4/1531950ac50afd70a4d02f10b6aaf6d6a6a7669e/slf4j-simple-1.8.0-beta4.jar
~/.gradle/caches/modules-2/files-2.1/com.github.spotbugs/spotbugs/3.1.12/f44d1e64d96d683cc930622f1cc23b87a0bcd299/spotbugs-3.1.12.jar
~/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-api/1.7.30/b5a4b6d16ab13e34a88fae84c35cd5d68cac922c/slf4j-api-1.7.30.jar
~/.m2/repository/org/ow2/asm/asm-commons/7.0/asm-commons-7.0.jar
~/.gradle/caches/modules-2/files-2.1/org.ow2.asm/asm-util/7.0/18d4d07010c24405129a6dbb0e92057f8779fb9d/asm-util-7.0.jar
~/.m2/repository/org/ow2/asm/asm-analysis/7.0/asm-analysis-7.0.jar
~/.m2/repository/org/ow2/asm/asm-tree/7.0/asm-tree-7.0.jar
~/.m2/repository/org/ow2/asm/asm/7.0/asm-7.0.jar
~/.gradle/caches/modules-2/files-2.1/org.apache.bcel/bcel/6.3/ab01e21304edb070aa840b856a4b26f17f901479/bcel-6.3.jar
~/.m2/repository/net/jcip/jcip-annotations/1.0/jcip-annotations-1.0.jar
~/.m2/repository/org/dom4j/dom4j/2.1.1/dom4j-2.1.1.jar
~/.gradle/caches/modules-2/files-2.1/jaxen/jaxen/1.2.0/c10535a925bd35129a4329bc75065cc6b5293f2c/jaxen-1.2.0.jar
~/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar
~/.gradle/caches/modules-2/files-2.1/com.github.spotbugs/spotbugs-annotations/3.1.12/ba2c77a05091820668987292f245f3b089387bfa/spotbugs-annotations-3.1.12.jar
~/.m2/repository/com/google/code/findbugs/jsr305/3.0.2/jsr305-3.0.2.jar

slf4j-simple-1.8.0-beta4.jar is not compatible with slf4j-api-1.7.30.jar that causes warning.
The possible workaround is to configure gradle dependency management plugin (https://plugins.gradle.org/plugin/io.spring.dependency-management) to use slf4j version 1.8.0-beta4 or manually override spotbugs classpath by using afterEvaluate hook for spotbugs gradle plugin:
afterEvaluate {
  val spotbugs = configurations.getByName("spotbugs")
  dependencies {
    spotbugs("org.slf4j:slf4j-nop:1.7.30") // or org.slf4j:slf4j-simple:1.7.30
    spotbugs("com.github.spotbugs:spotbugs:3.1.12")
  }
}

It is also possible to use spotbugsSlf4j configuration, then we can change the dependency for SLF4J provider:
dependencies {
  spotbugsSlf4j  "org.slf4j:slf4j-simple:1.7.30"
}

@madorb is this still an issue?

does not appear to be an issue anymore, no warnings using latest gradle

FYI, this issue is back with Gradle 7.3.1  and Spotbugs Gradle Plugin 5.0.3.
> Task :spotbugsMain
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

> Task :spotbugsTest
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

@martmagi this repo itself meets the condition you pointed but no warning was reported.
https://github.com/spotbugs/spotbugs-gradle-plugin/runs/4544294283
Try to make a mcve project, and create a new issue with it.


Move to GitHub Actions

Travis no longer provides free plan for OSS.
It should be based on https://github.com/chalk/chalk/blob/main/.github/workflows/main.yml, but made to work with Atom.

Plenty of examples e.g. https://github.com/bus-stop/x-terminal/tree/master/.github/workflows minimal adpation required obviously to suit this project

Atom's official sunset date is on December 15th, so between then and now, there's a slim chance of porting our tests to GitHub Actions… especially since Atom's package registry is constantly unavailable due to DDoS attacks from spam-bots publishing bullshit "packages". Which, in other words, means that the test-environment can't even be setup properly (since APM needs to make requests through Atom.io's APIs).
(FWIW, I already did port the package's test-runner to GitHub Actions in Atom-CI…)

@Alhadis for reference on our https://github.com/bus-stop/x-terminal project we have no such issues publishing/pushing updates, any of our releases continue to trigger updates within atom irrespective of any failures.


HDDS-4873. Re-replication failure throws NPE

What changes were proposed in this pull request?
Increase the log that helps users to use.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4873
How was this patch tested?
No test.

@jojochuang Can you review this PR for me?Thank you.

what Attila said. Thanks for the review!


[ENHANCEMENT] v1.2.1 upgrade related enhancements

Is your enhancement related to a problem? Please describe.

Summarize all v1.2.1 upgrade related enhancements.
Describe the solution you'd like

(1) Upgrade stuck in Upgrading System Service
Issue:
4519 [BUG] Upgrade to Harvester 1.2.0 fails in fleet-agent due to customer provided SSL certificate without IP SAN
4517 [BUG] Upgrade from 1.1.2 to 1.2.0 stuck 50% through the "Upgrading System Service"
Fix:

[x] fix fleet-agent;  rollback server-url sync in mcm settings handler https://github.com/harvester/harvester/pull/4543
[ ] fix fleet-controller;  msg="error syncing 'fleet-local/local': handler import-cluster: missing apiServerURL in fleet config for cluster auto registration, requeuing"
[ ] check self-signed certs; https://github.com/harvester/upgrade-helpers/pull/10

(2)  Upgrade stuck with first node in Post-draining state
Issue:
4526 [BUG] Upgrade stuck with first node in Post-draining state
https://github.com/rancher/elemental-toolkit/issues/1827
Fix:

[x] (Harvester workaround) upgrade: cleanup the incomplete state file
#4566
[x] (Elemental-toolkit) https://github.com/rancher/elemental-toolkit/pull/1836

(3) Upgrade request denied - rancher-monitoring is not ready
Issue:
4537 [BUG] Harvester 1.1.2 to 1.2.0 upgrade request denied - rancher-monitoring is not ready
An derived issue https://github.com/harvester/harvester/issues/4581 is adde.
Workaround:
In v1.1.2, the lost cluster-repo deployment was re-added.
In v1.2.0, the failed deployed rancher-monitoring addon was recovered manually.
Fix:

[ ] deployment harvester-cluster-repo was gone, re-created manualy;  reason unknown
[ ] doc enhancement: when rancher-monitoring addon is not deployed during v120 upgrade, how to manually fix it after the upgrade

Describe alternatives you've considered

Additional context

@w13915984028 are we good to close this epic? since all children issues are done

Finished.


refactor: implement Valuer/Scanner to read/write to SQL databases

This PR implements the following interfaces using a simple Go template:

driver.Valuer (from database/sql/driver)
sql.Scanner (from database/sql)

This is to enable storing protobom wire format messages as raw bytes in a SQL database, needed by protobom/storage#29 as a more efficient storage format.
More info here.
Other changes

bump protoc version to 28.2
bump protoc-gen-go version to v1.34.2
bump golangci-lint version in workflow to v1.61, address new findings

@cpanato had to push a small change, mind approving again?


adding month only

Even though it states:

Please enter a date (DD).(MM).YYYY
It is not possible to enter

07.1991
or
Juli 1991
`

@martinantonmueller  is this still valid after introducing the new solution using <>?

Nope!


Quickstart.md not working for me

I'm a bit new to laravel, so please forgive me for asking stupid questions :) I'm using laravel 5.3.
I followed the quickstart readme. Using Adldap::auth()->attempt($username, $password); with a correct password and username works for me. And I can retrieve lists of users etc. However the login form doesn't work. I get the error of wrong credentials.
I think my login controller is still looking for the credentials in the current user model. My login controller currently is the basic laravel login controller
Could someone add the instructions / help me with getting this to work?

Hi @martijnimhoff, no problem at all, I'd be glad to help you out! :)
Can you post your config/adldap_auth.php file?

Thank you. this is my adldap_auth.php

return [

    'connection' => env('ADLDAP_CONNECTION', 'default'),

    'username_attribute' => ['username' => 'samaccountname'],

    'limitation_filter' => env('ADLDAP_LIMITATION_FILTER', ''),

    'login_fallback' => env('ADLDAP_LOGIN_FALLBACK', false),

    'password_key' => env('ADLDAP_PASSWORD_KEY', 'password'),

    'password_sync' => env('ADLDAP_PASSWORD_SYNC', true),

    'login_attribute' => env('ADLDAP_LOGIN_ATTRIBUTE', 'samaccountname'),

    'windows_auth_attribute' => ['samaccountname' => 'AUTH_USER'],

    'bind_user_to_model' => env('ADLDAP_BIND_USER_TO_MODEL', false),

    'sync_attributes' => [

        'name' => 'cn',

    ],

    'select_attributes' => [

        //

    ],

];

And in my .env I've set ADLDAP_PASSWORD_SYNC=true.

Looks like you're using a username instead of an email to authenticate:
    'username_attribute' => ['username' => 'samaccountname'],

Did you update your create_users_table migration to create a username column instead of email?
You'll also need to update your controller as specified in the quick start doc (below):
If you require logging in by another attribute, such as a username instead of email follow the process below for your Laravel version. Otherwise ignore this step.
Laravel <= 5.2:
Inside the generated app/Http/Controllers/Auth/AuthController.php, you'll need to add the protected $username property if you're logging in users by username.
class AuthController extends Controller
{
    protected $username = 'username';

Laravel > 5.3:
Inside the generated app/Http/Controllers/Auth/LoginController.php, you'll need to add the public method username():
public function username()
{
    return 'username';
}

Thanks for your reply! It works now. I added the username() method, updated the fields in the login.blade.php and changed the create_users_table
What was confusing for me is that the LoginController.php is actually a basic laravel file. So it's not generated.

Great! Glad you've resolved the issue :).


cmd/go: go mod -sync removes a module from go.mod but not go.sum

What version of Go are you using (go version)?
Does this issue reproduce with the latest release?
go version devel +6f96cf2 Fri Jul 13 22:29:48 2018 +0000 linux/amd64

What did you do?
$ mkdir /tmp/foo && cd /tmp/foo
$ echo 'package foo // import "foo"' > main.go
$ go mod -init
$ go get github.com/lib/pq
$ cat go.sum
github.com/lib/pq v0.0.0-20180523175426-90697d60dd84/go.mod h1:5WUZQaWbwv1U+lTReE5YruASi9Al49XbQIvNi/34Woo=
$ go mod -sync
$ cat go.sum

What did you expect to see?
Nothing.
What did you see instead?
github.com/lib/pq v0.0.0-20180523175426-90697d60dd84/go.mod h1:5WUZQaWbwv1U+lTReE5YruASi9Al49XbQIvNi/34Woo=

Files in go.sum are never intended to be removed. It keeps a list of all modules seen.

That approach (if indeed the defined behaviour) is (1) badly documented, (2) probably wouldn't scale very well, (3) raises questions.
Regarding (1) here is what go help modules had to say about go.sum:

The go command maintains, in the main module's root directory alongside
go.mod, a file named go.sum containing the expected cryptographic checksums
of the content of specific module versions. Each time a dependency is
used, its checksum is added to go.sum if missing or else required to match
the existing entry in go.sum.

I added the emphasis. My assumptions from reading this section are:

"Maintaining" means adding that is used and removing what is unused
A dependency is "used" when one of packages in the module imports it.

By (2) I mean that when we consider a project like Hugo, with hundreds of dependencies being added, removed, and updated daily in several branches. go.sum would accumulate trash very quickly. (Ideally, go mod -sync would remove any line that is not a hash of a used package, so that resolving git conflicts is as easy as fixing go.mod and running go mod -sync.)
By (3) I simply mean that the "Go 1.11 Modules Experiment" comes with a number of tools to support modules in a project. So why not include a tool to maintain go.sum? Don't get me wrong, I can write an awk script to do that, but why, if almost any project will need something like that?

/cc @rsc @bcmills for confirmation of the intended semantics here.

I appreciate the fact that go.sum is append only. It secures the case of reintroducing a dependency and improves future cross-pollination experiments where hashes are learned from other repositories.
One way to look at this is that go.sum is just a way (currently, the only one) to check package integrity, not really bound to go.mod. In the future we might have system-wide go.sum, or remote auditable services instead.
For projects so big it becomes a problem, there can be an external tool to trim go.sum.


Cannot add sass-loader to a new project

Version
3.2.26
Reproduction link
sfc.vuejs.org/
Steps to reproduce
vue create project
# select Default (Vue 3)
cd project
npm install -D sass-loader

What is expected?
sass-loader installed
What is actually happening?
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/webpack
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@intervolga/optimize-cssnano-plugin
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@vue/cli-service
npm ERR!       peer<EMAIL_ADDRESS>|| ^4.0.0-0" from<EMAIL_ADDRESS>npm ERR!       node_modules/@vue/cli-plugin-babel
npm ERR!         dev<EMAIL_ADDRESS>from the root project
npm ERR!       4 more (@vue/cli-plugin-eslint, @vue/cli-plugin-router, ...)
npm ERR!   peer<EMAIL_ADDRESS>|| ^5.0.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/@soda/friendly-errors-webpack-plugin
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@vue/cli-service
npm ERR!       peer<EMAIL_ADDRESS>|| ^4.0.0-0" from<EMAIL_ADDRESS>npm ERR!       node_modules/@vue/cli-plugin-babel
npm ERR!         dev<EMAIL_ADDRESS>from the root project
npm ERR!       4 more (@vue/cli-plugin-eslint, @vue/cli-plugin-router, ...)
npm ERR!   19 more (@vue/cli-plugin-babel, @vue/cli-plugin-eslint, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev sass-loader@"*" from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/webpack
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/sass-loader
npm ERR!     dev sass-loader@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/user1/.npm/eresolve-report.txt for a full report.

npm ERR!      /Users/user1/.npm/_logs/2021-12-25T11_35_19_562Z-debug.log

I cannot provide a link to SFC playground as reproduction steps require running npm install

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.

@posva this is a bug report

@builder555 Try yarn add sass-loader --save, maybe it could help you.

@ygj6 yup, tried using yarn as well - same error.

i'm still not sure why this bug report is marked as closed? was it fixed?

This obviously not a bug.

@caozhong1996  if you try installing sass from one of the predefined settings (no manual npm install steps), the same error happens.


Add question for email/sms preference on cutgroup.org sign-up form

We want to ask testers if they sign up via web if they prefer to receive text message notifications or email notifications when new tests are announced.
Tasks associated with this:

[x] Add a question on the wufoo form on this webpage: http://www.cutgroup.org/
[x] Tag testers appropriately as SMS or Email preferred in Patterns

@shua123 API ID is 273 on this form https://smartchicago2012.wufoo.com/forms/smart-chicago-cutgroup-signup/

Closing this issue since it is completed.


Don't use custom Bundler path

It was made because of macOS in #172
There is Brew and a bit another installation. I wanted to unify it.
Also I had similar in some repos, but without macOS, for example: https://github.com/r18n/sinatra-r18n/blob/master/.cirrus.yml
Are you sure about these changes?

Especially in this PR I see:

Cache miss for bundle-65e14e12f77284fd0ba506bc37e3792cf1d2a2661895ec59e97182055fb06ee4! No script to populate with.

https://cirrus-ci.com/task/6467993317146624?command=bundle#L54

Skipping change detection for bundle cache!

https://cirrus-ci.com/task/6467993317146624?command=Upload 'bundle' cache#L0
WTF? 😅

This is not WTF. This is coming from macOS where is can't write to /usr/local/bundle https://cirrus-ci.com/task/6467993317146624?command=bundle#L50

This is not WTF. This is coming from macOS where is can't write to /usr/local/bundle https://cirrus-ci.com/task/6467993317146624?command=bundle#L50

OK, thank you, so… maybe we should use relative custom path for which we have permissions to write and read?


Fix/input type hint

I think the type hint of predict and predict_proba is not correct.
It's python, so it doesn't cause errors, but it might confuse readers, so made this PR.
The reasons for this PR are as follows
Regarding inputs:

SentenceTransformer.encode accept Union[List[str], str], not torch.Tensor as you can see here
If the type of x_test is str, errors occur since the size of embedding is different from the size expected by the model head.
From type these reason, the type of x_test should be   List[str]

As for the output, the reason is clear, so I will omit it.

Ah, there's some conflicts from previous PRs getting merged - would you mind resolving them and pushing again @Yongtae723 ?

Absolutely no problem

@lewtun
Hi lewtun
I resolved it. please merge it if there are no problems.
thank you
Yongtae

Thanks for the fix @Yongtae723!


Remove postscribe dependency

We'd like to identify why the postscribe dependency exists, and if possible, remove it for either web or all of PUC depending on the genesis.

We need someone to document what actually is postscribe. Ideally, we should also at least try to hypothesize why it might have been added to the PUC.

To answer: why was it added in the first place? was it for performance reasons on mobile webviews?


Doesn't work with mod_mime_magic

If mod_mime_magic is enabled on an Apache server (it's enabled by default on RedHat based systems) then the pf_meta file fails to load.
Looking deeper into this, it appears as if the magic module is detecting the files are already gzip'd and so added a Content-Encoding: x-gzip header to the response.   This appears to tell the browser to automatically gunzip the data because gzs() is being passed the uncompressed data.  This, naturally then fails the "is this compressed" test and causes the load to fail.
The simple solution is to disable this module on the server (which may be worth adding to the documentation).  But maybe having some way of detecting if the browser has automatically uncompressed the data before the javascript gets to see it (e.g. add a simple 3-byte signature to each file; if that gets seen instead of the gzip header then return the raw datastream).

Aha, interesting, I've never seen that behavior but good to know! I'll add the signature strategy to the next release, so that we don't have a pitfall waiting anyone on RedHat 🙂

Hi @sweharris 👋
Support for server-handled gzip has been released in Pagefind v0.5.0 🎉


Configuration directory different than /etc/rancher/

Is your feature request related to a problem? Please describe.

I run k3s server on a system with volatile root where only specific paths are persisted across reboots. The inability of changing the configuration directory to something other than /etc/rancher and k3s not following directory symlinks at /etc/rancher make it very hard for me to persist the content of /etc/rancher. Unfortunately, mounts also don't work for me in combination with systemd-confext.
Describe the solution you'd like

My problem would be solved if I could point k3s to another configuration directory. Is this already possible and I'm missing something here? I didn't find a way to set it to another path, please let me know if this is already possible.
Describe alternatives you've considered

It would be also ok if k3s would follow symlinks, currently it errors with file exists when a symlink exists at /etc/rancher.
Additional context

Is there anything speaking against making this configurable? If not, I could try to contribute a PR for it.

Hmm, the error when it's a symlink is unexpected, we can look at that.
Have you tried symlinking /etc/rancher/node and /etc/rancher/k3s individually? Do you get the same behavior?

Have you tried symlinking /etc/rancher/node and /etc/rancher/k3s individually?

I just tried this but it results in the same error
level=error msg="Failed to generate kubeconfig: mkdir /etc/rancher/k3s: file exists"

For reference, this is the error I get when only symlinking /etc/rancher/
level=error msg="Failed to generate kubeconfig: mkdir /etc/rancher: file exists"

I tried with v1.30.6+k3s1 and v1.31.2+k3s1 but the error is the same. It seems to fail when calling WriteToFile() in WriteClientKubeConfig().

The problem was the target of the symlink at /etc/rancher didn't exist. os.MkDirAll() doesn't create a directory at the target location if it doesn't exist and I guess that is expected. It works if I create the directory to which /etc/rancher points.
Sorry for the noise, I had the wrong idea of how a symlink is treated in this case.

It works if I create the directory to which /etc/rancher points.

Well yeah, that seems important.


Understanding self type in CB

If the editing context opr is an access operator with an identifier on the left side, and this identifier is an existing local variable available in our method, then the qualified pattern of the resulting filter should not be defined, and self type should be the type of such local.

Actually, the algorithm described in the initial description does not work well, because "Local" entries in the suggestion database have usually "Any" type.
And it makes sense, because their type may be decided only during runtime. Technically, the type of given local may vary depending on the execution context.
The proper solution would be then relying not on suggestion database, but on the expression updates we receive. But we need alias analysis first to know where identifiers we use are defined.

Two parts:

[ ] Find the expression of the identifier on the left side of . in the current method using alias analysis.
[ ] Also analyze the CB input to find out if the identifier isn't introduced inside, e.g. by being a lambda argument.


Override request.url/body/method only when init values are defined

Fixed #51 .
In some cases,  URL/Method and body return by getRequests() are 'undefined' due to init values that are 'undefined'.  I propose to override these values only when a value is defined.
@chmanie, please review my PR .
I need this bug fix, because currently, I can't use expectRequest feature.

Closed in favour of #58

Published v3.0.3 which incorporates this fix. Thanks again!


Variables in Kotlin: Android Basics with Compose

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-variables?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-1-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-variables#4
In which task and step of the codelab can this issue be found?
fun main() {
val trip1 = 3.20
val trip2 = 4.10
val trip3 = 1.72
val totalTripLength = trip1 + trip2 + trip3
println("$totalTripLength miles left to destination")
}
Describe the problem
Codlab tutorial says that "Run your code again to ensure that your code still compiles. The output should be the same, but now your code is simpler!" which means output should be the same. Which works fine in Kotline Playground.
But. When I slightly modify the code :
fun main() {
val trip1 = 2.03
val trip2 = 3.04
val trip3 = 5.06
val totalTrip = trip1 + trip2 + trip3
println("Total length : $totalTrip")
}
The Output is
Total length : 10.129999999999999
Which I think is incorrect. Because totalTrip variable should have been stored as a Double.
Steps to reproduce?
Here is the code
https://pl.kotl.in/YGF4Z0f8W

Additional information
Screenshot is attached.

Hi @uttammanher
Thank you for writing in.
Double can have multiple numbers after the decimal. It is not limited to two.
https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-double/
Hope this helps.
Regards.


"export:310: not valid in this context: --bind" error when

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[ ] Linux
[x ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce
DISCLAIMER, I searched the manual but did not read the whole thing. Search on the web turned up nothing with my exact error.
Notes: rg and fzf have are installed and updated via brew.
Following the example in the README, copy and paste the following for integration with rg:
INITIAL_QUERY=""
RG_PREFIX="rg --column --line-number --no-heading --color=always --smart-case "
FZF_DEFAULT_COMMAND="$RG_PREFIX '$INITIAL_QUERY'" \
  fzf --bind "change:reload:$RG_PREFIX {q} || true" \
      --ansi --disabled --query "$INITIAL_QUERY" \
      --height=50% --layout=reverse

When the shell is reloaded, I get the following error:
.zshrc:export:310: not valid in this context: --bind

I forgot to mention that i'm using ohymyz.sh with the fzf plugin. And per the instructions in the plugin README file, I have placed the keyword export in front of FZF_DEFUALT_COMMAND. I tried removing export but then fzf with rg doesn't work at all.

OK, I don't think this is a problem with fzf but with my zsh config. I'm going to close.

Reopening because there is a similar issue in the queue at #2481. I updated the patched files (shell/completion.zsh and shell/key-bindings.sh) and ran the install.sh script and reloaded zsh but I still get the same error:
.zshrc:export:310: not valid in this context: --bind
Not sure what else to do at this point.

OK, the command were not designed to go into the shell's config file. Putting them in a separate script solved the problem.


Correct tree height generation for arrays of size 32^n

"Fixes" #176 by making initialize and fromList generate trees of the same height for the same amount of elements. This fixes the eq problem by making sure that the way trees are generated (in terms of height and leafing) is consistent between the two functions.
Doesn't fix the issue of equality checking on arrays with different heights yet the same elements, however.

Fix for equality is better done a different way. Overall fix for Array is better done with the Elm rewrite that is in progress.


Trying to sign in

dosent work, always get that error:
ERROR while attempting sign in: "name='csrftoken', domain=None, path=None"

Hi @5p4ce thanks for the feedback. It appears Instagram have changed their backend so I'll have to update the login function. I'll let you know when it's fixed.

Hey Friends, i use this instabot and works fine:
https://github.com/instabot-py/instabot.py
@nickpettican can fix your instbot reading it?

@nickpettican You learn python on free course ? i want learning more to help us

The login issue is fixed, yet sometimes you may get the checkpoint error. If you do, just follow this https://www.gramto.com/article/how-to-bypass-instagram-checkpoint/

@LopesX I learned through online course at first, and then by profession and side projects. I highly encourage you to keep going :)


renderToStaticNodeStream

Page: https://id.react.dev/reference/react-dom/server/renderToStaticNodeStream
Assignee: @rimamei

Hello, I’m interested in translating. Can you assign me to this issue? cc @zainfathoni @resir014

By raising a Draft PR, we can assume that you're assigned to it automatically.
Therefore, please raise a Draft PR with a very minimum change (one-line change is enough) at your earliest convenience. 😁

Thank you for the explanation. So, this is my PR and it's ready to review https://github.com/reactjs/id.react.dev/pull/476


Add symlink in kodata 🔗

Changes

This allows ko to be less noisy. This replicates what knative does
in serving and elsewhere.
Not sure if we wanna go through with it or not but here it is.
Related to #2028
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>/cc @steveodonovan @ImJasonH @afrittoli @mattmoor
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Describe any user facing changes here, or delete this block.

Examples of user facing changes:
- API changes
- Bug fixes
- Any changes in behavior

/lgtm
That supposed to go in the image, right ?
(we build our own image with ko)

@chmouel yeah :sweat_smile:

/lgtm

/approve

/lgtm

/test pull-tekton-pipeline-build-tests

/test pull-tekton-pipeline-build-tests


ParameterAccessContext: add a missing virtual destructor

@tcahuzax @krocard please review (I need this to be delivered in v3.2.2).

[x]   General Comment
<img border=0 src='https://avatars.githubusercontent.com/u/8655789?v=3' height=16 width=16'> ## [Current coverage][1] is 78.80%

Merging #347 into master will not affect coverage as of [e43c859][3]

@@            master   #347   diff @@
=====================================
Files          210    210
Stmts         7157   7159     +2
Branches         0      0
Methods          0      0
=====================================
+ Hit           5640   5642     +2
Partial          0      0
Missed        1517   1517

Review entire [Coverage Diff][4] as of [e43c859][3]
[1]: https://codecov.io/github/01org/parameter-framework?ref=e43c8596d551915aece9a11b1e11688674b6ca8f
[2]: https://codecov.io/github/01org/parameter-framework/features/suggestions?ref=e43c8596d551915aece9a11b1e11688674b6ca8f
[3]: https://codecov.io/github/01org/parameter-framework/commit/e43c8596d551915aece9a11b1e11688674b6ca8f
[4]: https://codecov.io/github/01org/parameter-framework/compare/88d1d136eeb4d8d1d86e4acff230be9a809351d2...e43c8596d551915aece9a11b1e11688674b6ca8f
Powered by Codecov. Updated on successful CI builds.

This pull request is now managed with CodeReviewHub. Refresh.

Current coverage is 78.80%

Merging #347 into master will not affect coverage as of e43c859

@@            master   #347   diff @@
=====================================
  Files          210    210
  Stmts         7157   7159     +2
  Branches         0      0
  Methods          0      0
=====================================
+ Hit           5640   5642     +2
  Partial          0      0
  Missed        1517   1517

Review entire Coverage Diff as of e43c859

Powered by Codecov. Updated on successful CI builds.

:+1:

:shipit:


React Native 0.68~0.69.  A problem occurred configuring project ':react-native-gradle-plugin'.

Description

What went wrong:
A problem occurred configuring project ':react-native-gradle-plugin'.

Could not create service of type OutputFilesRepository using ExecutionGradleServices.createOutputFilesRepository().
Timeout waiting to lock Build Output Cleanup Cache (/Volumes/HPP500/project/ReactNative/Cmpanda/node_modules/react-native-gradle-plugin/.gradle/buildOutputCleanup). It is currently in use by this Gradle process.Owner Operation: unknown
Our operation:
Lock file: /Volumes/HPP500/project/ReactNative/Cmpanda/node_modules/react-native-gradle-plugin/.gradle/buildOutputCleanup/buildOutputCleanup.lock

Version
ex. 0.69.2
Output of npx react-native info
System:
OS: macOS 12.4
CPU: (8) x64 Intel(R) Core(TM) i7-8557U CPU @ 1.70GHz
Memory: 56.42 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.13.1 - /usr/local/bin/node
Yarn: Not Found
npm: 8.1.2 - /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8609683
Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild
Languages:
Java: 11.0.15 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
npm run android
Snack, code example, screenshot, or link to a repository

rootProject.name = 'Cmpanda'
apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesSettingsGradle(settings)
include ':app'
includeBuild('../node_modules/react-native-gradle-plugin')
if (settings.hasProperty("newArchEnabled") && settings.newArchEnabled == "true") {
include(":ReactAndroid")
project(":ReactAndroid").projectDir = file('../node_modules/react-native/ReactAndroid')
include(":ReactAndroid:hermes-engine")
project(":ReactAndroid:hermes-engine").projectDir = file('../node_modules/react-native/ReactAndroid/hermes-engine')
}

This is unrelated to React Native but rather a problem with Gradle: https://github.com/gradle/gradle/issues/8750
I would try to delete the .lock file mentioned and rebuilt. Please reopen if the issue persists

Do sudo before any command. example: sudo ./gradlew assembleRelease

All errors can be due to different reasons, always in a permissions or gradle context.
In my personal case, updating through Android Studio the gradle version solved my problem, it is automatically given by gradle when starting Android Studio.
Also, you could modify the general permissions in your macOS or through the terminal using chmod -R 777 or chmod -R 755 with the specific path of your project.
Cheer up!
PS: Sorry for my English, I'm perfecting it, I'm from Chile


Initial testing with pr branch

Adding in a second email to notify a user when their contentful changes have begun deployment
Additional amendments made to prevent concourse from queueing up builds on the contentful pipeline sequentially, every 5 minutes if there are changes it will now instead queue up a single build from latest

DEPLOY_URL=https://d3g8soeloqwu4y.cloudfront.net/
cloudfront_id=E3T8QO317ZWSEJ

DEPLOY_URL=https://d3g8soeloqwu4y.cloudfront.net/
cloudfront_id=E3T8QO317ZWSEJ


Add code for finding the median of two sorted arrays.

Description
Add code for finding the median of two sorted arrays.
Expected logarithmic time complexity.

I am adding the code for this one very soon.

Assigning it to you @itskeffect


The newsout app provided nextcloud sever is unreachable 10/15

Newsout provided Nextcloud server is currently unreachable. Is this a temporary problem, or has the provided server been retired/discontinued?

The provider permanently changed the url. I will fix and reupload a version to the stores asap. Thanks

I just released an update (v.1.2.2) to the Play Store and F-Droid store. It might take a few hours until it's available to download.


A bug in documentation $itemMatcher = \Knp\Menu\Matcher\Matcher(); missing new

Threre is a bug in documentation: https://github.com/KnpLabs/KnpMenu/blob/master/doc/04-Iterators.md
$itemMatcher = \Knp\Menu\Matcher\Matcher();
should be
$itemMatcher = new \Knp\Menu\Matcher\Matcher();

Can you send a pull request fixing the doc ? this way, you would get authorship on the fix.

I'm sorry, I'm a newbie to github workflow, so by now I can't.

Well, for such a small documentation change, you can do it in the github interface directly (click on the edit button when looking at this file)

Ok, done.


Compiling problem psychsource

Describe your bug here.
Hi i just wanted to compile the source and than after tiping lime test windows this appeared "C:\Users\Admin\Downloads\FNF-PsychEngine-main\FNF-PsychEngine-main>lime test windows
source/psychlua/HScript.hx:317: characters 89-96 : Type not found : TeaCall" HOW DO I SOLVE THIS?
Command Prompt/Terminal logs (if existing)
C:\Users\Admin\Downloads\FNF-PsychEngine-main\FNF-PsychEngine-main>lime test windows
source/psychlua/HScript.hx:317: characters 89-96 : Type not found : TeaCall

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No i did not.

replace all instances of TeaCall to Tea

replace all instances of TeaCall to Tea

thx


add f03gl and PLplot

Submitting 2 graphics libraries to the registry. I couldn't find the PR template for this. Do we have any?

Submitting 2 graphics libraries to the registry. I couldn't find the PR template for this. Do we have any?

No PR template yet

#build_preview

Preview doesn't seem to work.

Preview doesn't seem to work.

Working for me:

It does for me as well now.

Regarding versions: f03gl indeed didn't have a version and we don't want to show a version none badge. However, PLplot does (5.15.0, I forgot to include it). Why wouldn't we show version for non-GH projects that have one?

Sorry I didn't mean for all non-github repos, just those without explicit versions

Here is what we have to go over: https://github.com/fortran-lang/fortran-lang.org/blob/8f74576faef57a6da975195ffda8da85402b1ba9/PACKAGES.md

@certik I did, feel free to check it as well.

Here is what we have to go over: https://github.com/fortran-lang/fortran-lang.org/blob/8f74576faef57a6da975195ffda8da85402b1ba9/PACKAGES.md

I'm happy these packages meet all the criteria discussed :+1:

Have you tried installing the packages and do they work? I haven't checked the "Maturity" section.
I am hoping that fpm will help with libraries like these, to make them easy to install, part of the wide Fortran ecosystem and also have usage statistic at the registry webpage, and so on.

Have you tried installing the packages and do they work? I haven't checked the "Maturity" section.

Yes for f03gl, no for PLplot.
Have you looked at PLplot? This may be among the most mature libraries in the registry (contributions go back to 1992): https://www.openhub.net/p/plplot/contributors/summary

Thank you both, merging.

#delete_preview


Delete Item(s) on Wishlist

As a customer
I need to be able to delete items from my wishlist
So that I can keep track of my changing wants and needs while shopping online
Details and Assumptions

Customers can delete only one item at a time from their wishlist

Acceptance Criteria
Given that the service is running
When I delete an item from my wishlist
Then that item should disappear from the wishlist and be removed from the database

03/07 - Submitted initial pull request, but realized that my code was missing code from test_routes.py, so need to go back and incorporate

03/20 - Test is dependent on creation of read request


KeyMapping Works only on one monitor

Microsoft PowerToys version
0.86
Installation method
GitHub
Running as admin
None
Area(s) with issue?
Keyboard Manager
Steps to reproduce
i want to remap the volume mute key to nothing.
remapping a key ( volume mute ) to disabled on one monitor works as long as I'm in focus in that monitor but if i click on the 2nd monitor its functioning again as normal (not being disabled)
--Monitor 1--
Changing the volume mute to disabled
testing the key
its disabled and it wont mute
Now Hovering to 2nd Monitor
--Monitor 2--
making the windows focus on 2nd monitor ( any random click anywhere )
testing the key
it mutes the volume
if i bring the program it self (PowerToys) to the 2nd monitor it disables the key
testing the key
its disabled and doesn't mute
Now Hovering to 1nd Monitor
--Monitor 1--
making the windows focus on 1st monitor ( any random click anywhere )
testing the key
it mutes the volume
...................................................
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

/bugreport

PowerToysReport_2024-12-20-03-42-14.zip


Addition of LazyTableResource for resource that are imported at runtime

A few minor non-breaking changes to how the expected_file_extension argument is used

I do not love Lazy here but neither Mike nor I could find anything better. @nawatts would be great if you want to take a look at this PR and/or suggest a better name!

The use-case for this is that we have a bunch of resources that are quite small that we typically do not want to necessarily import and write as HT as it is overkill. Yet it'd be great to include them in a streamlined interface.

Alternatively, we could merge this into the base TableResource: add the import_func parameter to TableResource and default it to hl.read_table(self.path).

hmmm, maybe I'll drop the Protocol thing. Although it looks like the right way to do this seems like typing_extensions needs installation, which might be overkill

digesting that last suggestion...

Alternatively, we could merge this into the base TableResource: add the import_func parameter to TableResource and default it to hl.read_table(self.path).

Yes, I think I like this after all

def ht():
    if not self._ht:
        if self.import_function:
            self._ht = self.import_function(self.import_sources)
        else:
            self._ht = hl.read_table(self.path)

    return self._ht

we need to think what to do with path though

Maybe we could even store the import functionalities for all resources in there then instead of in https://macarthur-lab.github.io/gnomad_hail/api_reference/resources/grch38/reference_data_import.html

and ht() would do read if resources exists, else import

OK @nawatts , @mike-w-wilson , I've folded the import logic into TableResource. Take a look and comment. When we agree I'll apply the same logic to MatrixTableResource.
A note is that after some consideration I chose not to try read_table and default to import otherwise because the Hail always returns a HailError when reading doesn't work and it sometimes contains useful information. I also thought of checking if the file exists, and importing if not, but this also causes troubles because it's hard to make it independent of the storage used.

I added a tentative force_import argument that could be used if a user wanted to re-import a resource.
I suppose another avenue would be an argument that specifies what to do in case of a read error.

A note is that after some consideration I chose not to try read_table and default to import otherwise because the Hail always returns a HailError when reading doesn't work and it sometimes contains useful information.

👍If a consumer wants to import on failure, then they have the option of catching the error from from ht and calling it again with force_import=True.

I also thought of checking if the file exists, and importing if not, but this also causes troubles because it's hard to make it independent of the storage used.

👍Checking if files exist at self.path doesn't provide any guarantee anyway. The table files could still be deleted between the check and the read or while the read is in progress. Also, expecting the read to work is more idiomatic Python.

When we agree I'll apply the same logic to MatrixTableResource.

I think the changes to __init__ to add import_func should be applied to the base resource class instead of duplicated in TableResource, MatrixTableResource, etc.

@nawatts @mike-w-wilson I've just pushed a suggestion for import_resource for all resource types. Would be great to have feedback. Once we settle on an implementation, I'll update the import scripts.

Thanks @nawatts for the comments! I'll let @mike-w-wilson weigh in on the overwrite and Pedigree discussion.

Thanks for adding all the class docstrings. They are super clear.


How to use?

Why do I need to reply?
Op wo 3 feb. 2021 om 21:38 schreef Shentikai<EMAIL_ADDRESS>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/voxell-tech/SmartAssistant/issues/19, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASI4HALAKKJCCTPEE7X3MLLS5GX5XANCNFSM4XBRB73A
.

Hi, I know that everything is quite not working yet especially the UI part, but you can use the python version without the UI first. It's under PythonAPI folder. Follow the setup part and you should be fine. I will be making a video on this proj to demonstrate it XD.


Freminet Constellation Incorrect

Current Behavior
Freminet C3 is incorrectly labeled as +3 Burst, when it is actually +3 Normal Attack.
As a result, the scanner fails to export the character at burst levels below 4, and inaccurately export at level 4+
  "freminet": {     "GOOD": "Freminet",     "ConstellationName": [       "Automaton"     ],     "ConstellationOrder": [       "burst",       "skill"     ],     "Element": [       "cryo"     ],     "WeaponType": 1   },
Expected Behavior
The scanner exports the data
Reproducing a Behavior
Scan a C3+ Freminet with an unleveled burst talent. During export the scanner will adjust the talent level to -2 (invalid).
Device OS
Windows 11
Genshin Impact Version
4.4
Inventory Kamera Version
1.3.14
Screen resolution, screen mode, and UI scale
1920x1080, borderless, normal scale
Additional notes and remarks
No response
Evidence
InventoryKamera.log

Preflight Checklist

[X] I have checked for similar issues in the issue page, and I have not found any similar to mine.
[X] I am using the latest version of the scanner.
[X] I tried setting the scanning delay to maximum, and it still doesn't work.
[ ] I have attached the video recording to the bug report.
[X] I have attached the error log to the bug report.
[X] I am available to later explains the issue.
[X] I have disabled (or documented) all screen filtering software, plugins, and enhancements while scanning.
[X] I use default in-game keybindings or have configured keybindings for the scanner.

This is not unique to Freminet. The characters.json file is wrong for all C3 Normal Attack Constellations.
This includes Arlecchino, Freminet, Lyney, Neuvillette, Sethos and Wriothesley.


WARN when using "docker-compose image -q"

When using the command:
docker-compose images -q
I get following warning:
WARN[0000] The "D" variable is not set. Defaulting to a blank string.
Could not find the D variable anywhere. Is this a bug or how could I mitigate this warning?

I'm going to have a wild stab in the dark here and guess that a value in your docker compose file includes "$D" which docker compose thinks is a variable. If so, you can escape it by replacing it with "$$D".

oh I see. there was a password in my docker-compose with "$D" in it. Thank you for the insight.


Wrong wsdl file is returned

Dear castle-mock team,
I think that I found an issue.
I have a project with multiple ports. Each port was created with its own wsdl file.
If I try to access the wsdl of port x,a,z or w via the supported link, I'll receive the wsdl of port y every time.
That seems a little bit strange to me
Please see the attached files for further information
Best Regards
HaloSkyDG
getNotification.txt
productCatalog.txt

Hi @HaloSkyDG.
Thank you for raising this issue. I will look into this issue shortly, but it should be fairly simply to resolve.
I will keep you posted!
Once again, thank you very much.
Best regards,
Karl Dahlgren

I think mainly the issue here is that the SoapResouce is associated with the SoapProject.
To fix it, we need to associate the SoapResouce with SoapPort.
I think this change will affect all layers starting from web to repository layer.

@karldahlgren
I did a quick analysis of this issue, and I found here's a purposed solution:

reference the port Ids inside the resource object.
when deleting a resource before creating (cleanup process).. search not only by project id  but also by project id and port id (already saved in step 1).
when saving a port, do reference the resource id that belongs to it.
modify the get-wsdl method to return the wsdl not only related to the project, but also related to the port. (can we consider port-uri as unique or we need to change the wsdl URL to contains the port id instead/with -the currently used- the port uri?)

I think this is not a major issue, I mean it does not affect the mock responses from return correctly, correct?

Actually the client always retrieves the wsdl prior to making calls to any service. This makes a multi-port project completely useless. I have a set of ports I could group under the same project to make it easier to import / export, but I just can't because of this bug.

Hi @mhewedy ,
Any update on this ?

(can we consider port-uri as unique or we need to change the wsdl URL to contains the port id instead/with -the currently used- the port uri?)

IMO yes we can consider port-uri as unique. Having multiple ports in one project is useful to have one base server and multiple custom URIs (one per port). If you can't choose the URI and it is generated using the port ID, then I see no advantage in using one project with multiple ports rather than multiple projects.

Is there a workaround for this issue? We have a project with two ports with different wsdl files.

Is there a workaround for this issue? We have a project with two ports with different wsdl files.

Can this please be fixed or at least prevented that one can upload another wsdl without telling you that the previous port will be broken afterwards?

Can this please be fixed or at least prevented that one can upload another wsdl without telling you that the previous port will be broken afterwards?


Add jmh to sql module + some pre-exec benchmarks

@dobe please review

Current coverage is 81.05% (diff: 100%)

Merging #4492 into master will decrease coverage by 0.16%

@@             master      #4492   diff @@
==========================================
  Files          1297       1297
  Lines         44096      44096
  Methods           0          0
  Messages          0          0
  Branches       7003       7003
==========================================
- Hits          35813      35742    -71
- Misses         5604       5665    +61
- Partials       2679       2689    +10

Powered by Codecov. Last update 3ec50b0...aaf5a04


Direct calculation is incorrect.

Unless I'm mistaken, in file dev_direct_gravity.cu, function dev_direct_gravity:
int numTiles = n / p;
should be
int numTiles = (n + p - 1) / p;
Otherwise forces from the last, non-full, tile are not processed.

And, the kernel is also incorrect since it returns at the start if the index is out of range. However, these all the threads in the block are needed to load the data into shared memory. Instead the code should just mask those operations that have side effects such as loading data and storing the result.

Thanks for reporting this issue. I fixed it in this commit: faa46de0b3373870ef8831c5f9793d23800d4bba
Notice though that this feature is just for testing/comparing the performance difference between an O(N*N) algorithm and the O(NlogN) and should not be used for production simulations.


[ci] Build and publish bitstream artifacts on earlgrey_es

Update the azure-pipelines.yml to refer to the earlgrey_es branch.

Since this doesn't get tested until it is merged, I'd be okay with skipping the rest of the CI run. Then we'll have time to back it out this afternoon, if necessary.


Add ability to serve Whitehall-specific assets from Asset Manager

[x] Add Whitehall-specific Asset Manager API endpoint for creating assets
[x] Add ability to serve Whitehall-specific assets from Asset Manager

[x] Image placeholder - serve from Asset Manager using a Rails asset pipeline
[x] HTML placeholder - continue to serve from Whitehall
[x] Cache-Control headers for Whitehall assets and placeholders

This has been implemented in:

#199
https://github.com/alphagov/govuk-app-deployment/pull/183
https://github.com/alphagov/govuk-puppet/pull/6502
#210

However, I'm not going to close it until we've tested that it's working in at least integration.

I've verified that this functionality is working correctly in integration by SSH-ing onto a backend box and running the following commands. Note that I've had to make the final "public" request to the asset-manager.integration.publishing.service.gov.uk host rather than assets-origin.integration.publishing.service.gov.uk, because we haven't yet put in place the Nginx changes described in #214.
jamesmead@integration-backend-1:~$ echo `date` > tmp.txt

jamesmead@integration-backend-1:~$ cat tmp.txt
Wed Sep 20 14:42:54 UTC 2017

jamesmead@integration-backend-1:~$ curl \
  -H"Authorization: Bearer <redacted>" \
  -H"Accept: application/json" \
  https://asset-manager.integration.publishing.service.gov.uk/whitehall_assets \
  --form<EMAIL_ADDRESS>\
  --form "asset[legacy_url_path]=/government/uploads/tmp.txt"
{
  "_response_info":{"status":"created"},
  "id":"https://asset-manager.integration.publishing.service.gov.uk/assets/59c282e2e5274a598a083a92",
  "name":"tmp.txt",
  "content_type":"text/plain",
  "file_url":"https://assets-origin.integration.publishing.service.gov.uk/government/uploads/tmp.txt",
  "state":"unscanned"
}

jamesmead@integration-backend-1:~$ curl \
  -H"Authorization: Bearer  <redacted>" \
  -H"Accept: application/json" \
  https://asset-manager.integration.publishing.service.gov.uk/assets/59c282e2e5274a598a083a92
{
  "_response_info":{"status":"ok"},
  "id":"https://asset-manager.integration.publishing.service.gov.uk/assets/59c282e2e5274a598a083a92",
  "name":"tmp.txt",
  "content_type":"text/plain",
  "file_url":"https://assets-origin.integration.publishing.service.gov.uk/government/uploads/tmp.txt",
  "state":"clean"
}

jamesmead@integration-backend-1:~$ curl -v https://asset-manager.integration.publishing.service.gov.uk/government/uploads/tmp.txt
Wed Sep 20 14:42:54 UTC 2017

Doing this I did notice one flaw which I've captured in #218, but otherwise I think this looks good.

I can't think of a way to test that this functionality is working in staging/production until we have Whitehall saving assets to Asset Manager in #212. However, having tested it in integration, I'm pretty happy that it's working OK. So I'm going to close this issue on the assumption that we'll discover any problems when we test #212.
@chrisroos, @chrislo: Feel free to re-open if you disagree.

I've just chatted to @chrisroos about this and we've agreed that we'll leave this open for now until we've made some progress on #212 and have worked out what functionality we need in Asset Manager to support replacement/updating of Whitehall assets.


Write manual test cases for "AuvergneRhoneAlpesPage"

Please write a manual test case for the following pages manual test which involves breaking down the functionality of the webpage into specific steps that can be tested.
AuvergneRhoneAlpesPage:
https://prayersconnect.com/mosques/search/Saint-%25C3%2589tienne%252C%2520Auvergne-Rhone-Alpes%252C%2520France/45.44941%2C4.39832/45.44941%2C4.39832
Please use this Google doc for your test cases.
https://docs.google.com/spreadsheets/d/1v4pXXdrtDnI1bMoTChw2GMhktxPvWBu5ayLzeNaXiFk/edit?usp=sharing

Is this done?

yes Bhaiya, long time before i did it .


clips: 6.4.1 -> 6.40

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/clips/versions.
meta.description for clips is: Tool for Building Expert Systems
meta.homepage for clips is: http://www.clipsrules.net/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.40 with grep in /nix/store/ja2zckgmgdj3783dafgkkpy9rymm4gpw-clips-6.40
found 6.40 in filename of file in /nix/store/ja2zckgmgdj3783dafgkkpy9rymm4gpw-clips-6.40

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

clips

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ja2zckgmgdj3783dafgkkpy9rymm4gpw-clips-6.40 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A clips https://github.com/r-ryantm/nixpkgs/archive/222f6e376b43b443ffb393504a3117ba02828c6b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/222f6e376b43b443ffb393504a3117ba02828c6b#clips

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ja2zckgmgdj3783dafgkkpy9rymm4gpw-clips-6.40
ls -la /nix/store/ja2zckgmgdj3783dafgkkpy9rymm4gpw-clips-6.40/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

clips

Maintainer pings
cc @league for testing.

See also, the prior bot submission PR #318436 to downgrade and the human-led PR #316628 to upgrade.


Start to execute AWS healthchecks prior to syncing state

Resolves #616

Coverage remained the same at 25.288% when pulling 5fae11d2aae23e2507e222cb375a514682aa696a on 616-run-healthchecks-at-init into c3632cc9b4b7f9e581828f814a33e21cb435d803 on master.

/lgtm

/lgtm
/approve


feat(chain): Implement DB migration

This adds a MigrateDB function that converts a DB from one version to the next. Accordingly, the per-block and per-state versions have been removed.
I've tested this against walletd v0.8.0, though not exhaustively.
Currently there is no live feedback during migration. We could add logging or some other form of callback. We also discussed calling MigrateDB inside NewDBStore; I'm open to that, but it would require changing the function signature if we want logs as well, so we'd need to update a lot of callsites.

Ok, new approach. Every key is suffixed with a version. (Prefix would also work fine, and might be better for sorting...hmm)
When we migrate, we check the version byte on every key to determine whether it needs updating.
The old DB keys don't have a version byte at all, though, so instead we check the key length. This is feasible because all the keys have a fixed length, unlike values which can vary in size. This is also why the version is on the key, not the value: if it was on the value, then migrating the old DB (which lacks version bytes) would be ambiguous: you wouldn't be able to tell if the byte was actually a version byte, or part of an old DB value.
I tested this manually by migrating a consensus.db, loading it, and reading from it. When I migrate it again, it's a no-op. When migration is interrupted and resumed, the already-migrated keys are skipped as intended.