text:
Shiny odds increase mod?

Would it be possible to implement a mod that either let's you fully customize the the shiny odds or hard set them at 1/512? I'm a shiny hunter, but I don't want to spend literally all day hunting for one singular pokemon.

Shiny odds are entirely in exefs and would complicate the modding process a lot more as a specific version would have to be selected

So does that mean it most likely won't be possible?

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Dynamic number of signing keys?

This is perhaps more of a Rust question, but I'm trying to generate an account with a dynamic number of signing keys depending on some configuration. An example code snippet is as follows:
let account_kp = KeyPair::new_account();
let mut account_token = Token::new_account(account_kp.public_key()).name(account.name);

for workload in account.workloads {
    let workload_kp = KeyPair::new_account();
    account_token.add_signing_key(workload_kp.public_key());
}

Obviously this doesn't work, as we get the following error:
46 |               let mut account_token = Token::new_account(account_kp.public_key())
   |  _________________-----------------___-
   | |                 |
   | |                 move occurs because `account_token` has type `Token<nats_jwt::Account>`, which does not implement the `Copy` trait
47 | |                 .name(account.name);
   | |___________________________________- this reinitialization might get skipped
48 |
49 |               for workload in account.workloads {
   |               --------------------------------- inside of this loop
50 |                   let workload_kp = KeyPair::new_account();
51 |                   account_token.add_signing_key(workload_kp.public_key());
   |                   ^^^^^^^^^^^^^ value moved here, in previous iteration of loop

How would I go about doing this properly? Any help is greatly appreciated.

Oops. Turns out I'm still a noob.
Figured it out with a simple re-assignment of account_token in the loop after reading the docs closer.

repo: AircastDev/nats-jwt


text:
Update Virtual Leds

Make a link from the multistrip page to the advanced/ddp page and move text to there
Update the advanced/ddp page: combine text and add settings image

Something went terrible wrong here.
Only wanted to push the changes made in the virtual-leds branch but all changes made on mm.kno.wled.ge are pushed.
So please delete this PR
And maybe somebody knows how to only push the changes made in a branch???

Follow the instructions for opening a PR on WLED wiki.
You can close this PR yourself (@ewoudwijma ).

source: gharchive/pull-request

authors: MoonModules blazoncek ewoudwijma

repo: Aircoookie/WLED-Docs


text:
feat(coral) - View Environments: Add tab navigation for environments page

About this change - What it does

Adds tab navigation
Adds data fetching to render environments count in badges

Note
The new endpoints are currently not available as staging is a little behind on deployments. You may see the full implementation by building the API locally:
https://github.com/Aiven-Open/klaw/assets/20607294/3c845138-d475-4f93-bdf3-1d78bd61c650
Resolves: #1706

For transparency and documentation (since we continued the conversation in Slack):
We found out that:
we do
      getPaginatedEnvironmentsForTopicAndAclSpy.mockReturnValue(
        manualKafka.promise
      );

for every render.
BUT that mocks the spy function, not the api call.
manualKafka.resolve(mockedKafkaTotalEnvs); is what actual mocks the api call.  And we don't do that for every render.
When we don't resolve or reject e.g. manualKafka the promise remains pending. So if we add a console.log to the api call itself (which is what I tried to see if it shows up), it will not show up, since the test finished before the promise is resolved. This is why neither the console error nor the correct error show up locally.
So when we do:
describe("Tab badges", () => {
    let manualKafka: Deferred<EnvironmentPaginatedApiResponse>;

    beforeAll(() => {
      manualKafka = new Deferred();

     customRender(
        <EnvironmentsTabs currentTab={EnvironmentsTabEnum.KAFKA} />,
        {
          queryClient: true,
          memoryRouter: true,
        }
      );
    });

    afterAll(() => {
      cleanup();
    });

    describe("while environment count requests are in flight", () => {
      it("renders a tab for Kafka", () => {
        screen.getByRole("tab", { name: "Kafka" });
      });
      ...
    });
 });

we have a pending request. To test this state properly, we should do something like:
      it("renders a tab for Kafka", () => {
        screen.getByRole("tab", { name: "Kafka" });
        manualKafka.resolve(mockedKafkaTotalEnvs);

        await screen.findByRole("tab", {
            name: "Kafka, 1 environment",
          });
      });

to make sure we actually resolve the pending promise.
We decided that testing that in-between state is not actually important from a user perspective anyway and will update the tests accordingly.
We also have to check other usages of this kind of deferred mocking, since they can cause this memory leak and there's no guarantee that they show up in jest in a useful way.

For reference, the issue was actually that the test for src/app/pages/configuration/environments/index.tsx needed to mock the API calls as well. I think all other theries should be discarded as wrong.

authors: mathieu-anderson programmiri

repo: Aiven-Open/klaw


text:
Setup scene

Added Game Scene files for VS1 with some assets to showcase artists models and also fixed a bugg where the engine crashed if there was no Player object when opening the Debug Mode.

Removed the entire Library folder, including some files that were pushed by mistake a few months ago.

repo: AkitaInteractive/Hachiko-Engine


text:
Is it possible to use MiDas V3 ONNX

Is it possible to convert MiDas v3 to ONNX format?
Also is possible to convert AI Model found on this link https://github.com/yu-li/TCMonoDepth to ONNX?

Since both are implemented in PyTorch, you can export the model in ONNX format just by calling torch.onnx.export.
See official doc for the details.

I have no understanding of converting the Pytorch format into ONNX, I tried but without luck. Is it possible to convert this model with temporal consistency to ONNX?

https://github.com/Akiya-Research-Institute/Monocular-Depth-Estimation-on-UE4/releases/tag/v1.4

authors: KenjiAsaba PinkMediaGroup


text:
In Home page, price field is not restricted with numeric values

Test Environment: Firefox Web browser
Test OS: Windows
Test steps

Open Site
Under Unterkünfte/Accommodations, click Angebote (is auto selected)
Choose Zimmer/Haus (is auto selected)
Type in “Bis Preis” field
Click to Search/Search button

Pre-condition: Advertisement is already created with given price
Post result/expected result: Published advertisements displayed in Alphabetic order. Typing false Search result appears
Test Fail
Screenshot after typing in "Bis Preis" field:

Anupama/ Test fail/ Test document updated on 19.01.2023

Test Enviornment: Google Chrome
Test OS: Windows
Precondition:
TC_01
Test_Steps:
Web main landing page is open and "Angebot" is selected.

Select "Zimmer" in the search criteria.
Click in the searchfield "Bis Preis".
Enter a positive integer of the max price.
Click on the button "SUCHE".
Check the accommodation displayed below for the price.

Result: Test passed 13.02.2023 - 09:26 Uhr
All rooms that are cheaper or match the price in the search criteria are displayed.
TC_02
Test_Steps:

Click in the searchfield "Bis Preis".
Try to enter a letter in the search field.
Check whether the letters can be entered in the search field.

Result: Test passed 13.02.2023 - 09:27 Uhr
It not possible to enter letters in the field "Bis Preis"
TC_03
Test_Steps:

Click in the searchfield "Bis Preis".
Try to enter a decimal number in the search field.
Check whether the decimal number can be entered in the search field.

Result: Test passed 13.02.2023 - 09:30 Uhr
It not possible to enter decimal numbers in the field "Bis Preis"
TC_04
Test-Steps:

Click in the searchfield "Bis Preis".
Try to enter a negativ number in the search field.
Check whether the negativ number can be entered in the search field.

Result: Test passed 13.02.2023 - 09:30 Uhr
It not possible to enter negativ decimal numbers in the field "Bis Preis"

authors: Dummylearners thuead

repo: AkrosAG/Akros-Marketplace


text:
Can't seem to initialize data

  data () {
    return {
      me: {
        name: null
      }
    }
  },

  apollo: {
    me: gql`{
        me {
          name
        }
      }`
  }

name remains null after the query. I can access the data but only with $data.$apolloData.data.me.name  which seems like the wrong way.
If I remove the me {} property from data() then I get the following error:
TypeError: Cannot read property 'hasOwnProperty' of undefined
    at _loop (vue-apollo.esm.js?ebd5:3924)
    at VueComponent.launch (vue-apollo.esm.js?ebd5:3938)
    at callHook (vue.runtime.esm.js?ff9b:2917)
    at VueComponent.Vue._init (vue.runtime.esm.js?ff9b:4626)
    at new VueComponent (vue.runtime.esm.js?ff9b:4794)
    at createComponentInstanceForVnode (vue.runtime.esm.js?ff9b:4306)
    at init (vue.runtime.esm.js?ff9b:4127)
    at createComponent (vue.runtime.esm.js?ff9b:5604)
    at createElm (vue.runtime.esm.js?ff9b:5551)
    at VueComponent.patch [as __patch__] (vue.runtime.esm.js?ff9b:6087)

I just started this project with vue-cli 3 and added apollo with vue-cli.
I've disabled subscriptions.

This seems to be a regression of the latest version. Will fix it tomorrow. In the meantime, you can remove your data () { ... } option.

@maziarz
It seems like a simple work around, until the issue is fixed, is to employ the result callback and set your data manually.
export default {
  data () {
    return {
      me: {
        name: null
      }
    }
  },

  apollo: {
    me: {
      query: gql`{
        me {
          name
        }
      }`,
      result({ data, loading, networkStatus }) {
        this.me = data.me
      },

      error(err) {
        // handle your error
      }
    }
  }
}

At least, that's what I did, and it seems to be working so far.
Hope it helps,
~ Ayiga

Thanks @Ayiga, that did the trick :-)

Same issue here, @Akryum can you fix that?

I don't think it's the correct way to use result to pass data in the vm but it's a good way before the fix. Maybe is better to downgrade to beta 5.

Maybe is better to downgrade to beta 5.
This. 🐈

Using for the first time (through @nuxtjs/apollo) been trying to figure it out all day until i came across this.
Downgrading has fixed the issue for now.

@binzcodes same here, as soon as there is a release, the nuxt module should be updated

beta 10 is released already 🐈

@Akryum excellent! Thanks 🥇

great thanks @Akryum 👍

authors: Akryum Ayiga Christilut binzcodes dohomi maziarz pSchaub romain-web

repo: Akryum/vue-apollo


text:
How do i add lots of catching chanels

How to add lots of catching chanels

adds multiple channels IDs in index.js allowedchannels array

authors: ANADHEER AkshatOP

repo: AkshatOP/Poketwo-Autocatcher


text:
[Feat]  : We can add map and some static contact information

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
@Akshatchaube01
we can add map and some static informtiaon like toll-free number, email etc for contact
Describe the solution you'd like
A clear and concise description of what you want to happen.

we can add google map for location and add some information

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
What problem is this feature trying to solve?

it help user to reaching out us

How do we know when the feature is complete?

you can check it on contact us form

@Akshatchaube01
Thank you :)


text:
Instance can't start after update to TrueNAS-12.0-U2

Hello, its looks like the main programmer of this adapter speaks German, so I wrote this issue in German. If needed I can translate it to English, but for better communication I prefer the German language.
Moin, ich habe letzte Woche meine FreeNAS von Version 11.3-U5 auf TrueNAS-12.0-U2 aktualisiert. Das Jail mit ioBroker ist noch nicht aktualisiert und läuft mit Version 11.3-RELEASE-p11. Eigentlich hat sich am Jail also nichts geändert, doch nach dem update starten 2 von ca. 30 Instanzen nicht mehr. Eine davon war eine hm-rpc Instanz. Diese konnte ich wieder normal starten, nachdem ich die "Adapter Adresse" von "[IPv4] 0.0.0.0 - Auf alle IPs hören" auf "[IPv4] 192.168.0.21 - epair0b" umgestellt habe. Den tradfri Adapter konnte ich bis jetzt leider nicht wieder zum Leben erwecken. Womöglich hat sich etwas an den Netzwerkadaptern geändert, was jetzt Probleme verursacht. Aus dem Logging kann ich nur erkennen, dass die Tradfri Instanz auch die Adresse 0.0.0.0 verwendet. Vermutlich hat der Adapter somit das gleiche Problem wie der hm-rpc Adapter, nur das ich es für Tradfri nicht umstellen kann. Leider habe ich auch keinen Ansatz, wo ich auf der TrueNAS nach dem Fehler suchen könnte. Vielleicht hat noch jemand eine Idee für mich. Ansonsten wäre wohl womöglich die einfachste Lösung den Tradfri Adapter auch auf die eigene IP umzustellen.
ioBroker log:
tradfri.0 | 2021-02-17 21:32:48.157 | error | at processTicksAndRejections (internal/process/task_queues.js:97:5)
tradfri.0 | 2021-02-17 21:32:48.157 | error | at /opt/iobroker/node_modules/mdns-server/index.js:71:17
tradfri.0 | 2021-02-17 21:32:48.157 | error | at processInterface (/opt/iobroker/node_modules/mdns-server/index.js:61:22)
tradfri.0 | 2021-02-17 21:32:48.157 | error | (11074) Error: No sockets created.
tradfri.0 | 2021-02-17 21:32:48.156 | error | (11074) unhandled promise rejection: No sockets created.
tradfri.0 | 2021-02-17 21:32:48.156 | info | (11074) Terminated (ADAPTER_REQUESTED_TERMINATION): unhandled promise rejection
tradfri.0 | 2021-02-17 21:32:48.155 | error | at processTicksAndRejections (internal/process/task_queues.js:97:5)
tradfri.0 | 2021-02-17 21:32:48.155 | error | at /opt/iobroker/node_modules/mdns-server/index.js:71:17
tradfri.0 | 2021-02-17 21:32:48.155 | error | at processInterface (/opt/iobroker/node_modules/mdns-server/index.js:61:22)
tradfri.0 | 2021-02-17 21:32:48.155 | error | > stack: Error: No sockets created.
tradfri.0 | 2021-02-17 21:32:48.155 | error | (11074) unhandled promise rejection:No sockets created.
tradfri.0 | 2021-02-17 21:32:48.147 | info | (11074) Discovering the gateway automatically...
tradfri.0 | 2021-02-17 21:32:48.015 | info | (11074) starting. Version 2.6.5 in /opt/iobroker/node_modules/iobroker.tradfri, node: v12.16.1, js-controller: 3.1.6
tradfri.0 | 2021-02-17 21:32:47.301 | debug | (11074) statesDB connected
tradfri.0 | 2021-02-17 21:32:47.300 | debug | (11074) States connected to redis: 0.0.0.0:9000
tradfri.0 | 2021-02-17 21:32:47.293 | debug | (11074) States create System PubSub Client
tradfri.0 | 2021-02-17 21:32:47.291 | debug | (11074) States create User PubSub Client
tradfri.0 | 2021-02-17 21:32:47.285 | debug | (11074) Redis States: Use Redis connection: 0.0.0.0:9000
tradfri.0 | 2021-02-17 21:32:47.284 | debug | (11074) objectDB connected
tradfri.0 | 2021-02-17 21:32:47.279 | debug | (11074) Objects connected to redis: 0.0.0.0:9001
tradfri.0 | 2021-02-17 21:32:47.265 | debug | (11074) Objects client initialize lua scripts
tradfri.0 | 2021-02-17 21:32:47.264 | debug | (11074) Objects create User PubSub Client
tradfri.0 | 2021-02-17 21:32:47.263 | debug | (11074) Objects create System PubSub Client
tradfri.0 | 2021-02-17 21:32:47.261 | debug | (11074) Objects client ready ... initialize now
tradfri.0 | 2021-02-17 21:32:47.238 | debug | (11074) Redis Objects: Use Redis connection: 0.0.0.0:9001

Ich fürchte das geht nicht ganz so einfach, da Tradfri unter der Haube mDNS nutzt, um das Gateway zu finden. Du könntest statt der automatischen Suche festlegen, unter welcher Adresse das Gateway erreichbar ist.

Das hatte ich auch schon getestet, aber scheinbar hat sich leider ein Tippfehler in die IP-Adresse eingeschlichen. Ein Zeichen zu wenig in der IP, hat mich jetzt schon wieder einen ganzen Tag gekostet. Ach, ist das doch immer wieder schön :)
Aber trotzdem sehr merkwürdig warum die automatische Erkennung auf einmal nicht mehr funktioniert.
Vielen Dank für den Hinweis, der Adapter funktioniert jetzt erstmal wieder.
Hast du noch eine Idee in welche Richtung der Fehler gehen könnte? Stört mich schon zu wissen das irgendetwas auf meinem Host nicht stimmt. Ansonsten hoffe ich einfach auf die nächsten Updates von TrueNAS.

Ich kann mir nur vorstellen, dass Ports nicht mehr freigegeben sind, oder ein anderer DNS-Dienst läuft, der mDNS blockiert, etc...

Ok, vielen Dank für die Hilfe. Ich werde mal in die Richtung weiter forschen.

authors: AlCalzone Herakus


text:
Optimize aur-srcver using git ls-remote

This is how aur-srcver would look like when using git ls-remote.
As I shared in #286, aur-out-of-date doesn't produce good results for me, that's why I went for looking into this approach.
For my packages, the runtime of aur-srcver decreases from 18s to 8s.
How this works:

Read source out of PKGBUILD (e.g. source = alacritty::git+https://github.com/jwilm/alacritty.git#branch=master)
Remove custom name (e.g. alacritty::)
Remove all but the last protocol (e.g. git+) - do we need to keep it?
Detect branch name, if it is specified
Run git ls-remote on the source to get their last commit hash

Big problems:

This approach doesn't work for non-vcs packages, and I'm not sure how to make it work. Should we somehow detect non-vcs packages in the input and for them fallback to aur-rpc?

This now reports version as <pkg-name>    <commit-hash>, so it's not compatible with aur-vercmp anymore. This breaks #283 😞

Do you have some ideas how to overcome these issues?

So why are you removing makepkg completely? As it stands this would only work with git packages, and not with the plethora of other VCS packages.

This now reports version as  , so it's not compatible with aur-vercmp anymore

I was about to ask what you'd do with the commit hash in the first place. yay stores the commit hash for built packages in some configuration file and compares with it later, which I suppose is functional but doesn't work outside yay or whatever program decides to implement such mechanism.

So why are you removing makepkg completely?

This is more of a prototype anyway, to test the performance and general approach, but I realized too late that there isn't really much I could do with git hashes. Because I don't see any way what to do with hashes (besides doing what yay does and store them in a file, but I don't really like that approach), I think it is safe to conclude that this approach will not work for us.
With aur-out-of-date approach we would keep makepkg call for all packages that are giving the UNKNOWN state, I only wish there were fewer UNKNOWN results... I'll make an issue in their upstream, will see what the author says about that.

authors: AladW maximbaz

repo: AladW/aurutils

license: isc

license_source: bigquery


text:
RFC update Task engine

Jobs and Tasks handle/store expections. An event in a job will be raised if an exception was thrown
Job and Tasks accept and CancellationToken
Added Parallel Job executer + synchronized task. (Usefull for e.g. download multiple files parallel and wait individually for installing them)

IO Tasks are now implemented as a Synchronized task, so depending (parallel) tasks can wait for them.
The App now listens to Ctrl+C which triggers an cancellation token.

@AnakinSklavenwalker before you push too many things in one huge PR and work on too many things that go against the intended functionality which, admittedly, we never made public but mostly discussed in private, I'll just quickly run down the things you've done so far according to what little things @SvenMarcus and I "discussed" during the day:

Jobs and Tasks handle/store expections. An event in a job will be raised if an exception was thrown
We hadn't yet settled how we wanted to do reporting beyond jobs exiting with designated exit codes and configruably verbose logging, so we'll have to look at and discuss that part.

Job and Tasks accept and CancellationToken

Added Parallel Job executer + synchronized task. (Usefull for e.g. download multiple files parallel and wait individually for installing them)
IO Tasks are now implemented as a Synchronized task, so depending (parallel) tasks can wait for them.

We actively decided against running jobs and tasks in parallel, to avoid complex dependency chains and queueing that we'd have to reflect in the configuration file in some way, making the configuration error prone and complex. So in short mot of those changes won't be needed for the MVP release.

The App now listens to Ctrl+C which triggers an cancellation token.

That's a nice to have, although generally the application's run was never meant to be cancellable by the user.
For the future it would probably be better if you either discuss things with us on Discord beforehand, or via an issue/feature request here on GitHub, just so that everyone is on one page about where things are meant to be going.

authors: AnakinSklavenwalker gruenwaldlk

repo: AlamoEngine-Tools/eaw-ci


text:
request URLString bug

//target: Alamofire.swift line 97
// MARK: - Convenience

func URLRequest(
    method: Method,
    _ URLString: URLStringConvertible,
    headers: [String: String]? = nil)
    -> NSMutableURLRequest
{
    let mutableURLRequest: NSMutableURLRequest

    if URLString.dynamicType == NSMutableURLRequest.self {
        mutableURLRequest = URLString as! NSMutableURLRequest
    } else if URLString.dynamicType == NSURLRequest.self {
        mutableURLRequest = (URLString as! NSURLRequest).URLRequest
    } else {
        mutableURLRequest = NSMutableURLRequest(URL: NSURL(string: URLString.URLString)!)
    }

    mutableURLRequest.HTTPMethod = method.rawValue

    if let headers = headers {
        for (headerField, headerValue) in headers {
            mutableURLRequest.setValue(headerValue, forHTTPHeaderField: headerField)
        }
    }

    return mutableURLRequest
}

in your code URLString fix some " spage not good example:

https://bibleverse-d0859.firebaseio.com/v/1/books.json?orderBy="version_code"&equalTo="ASV"
(lldb) po URLString
"https://bibleverse-d0859.firebaseio.com/v/1/books.json?>orderBy="version_code"&equalTo="ASV""

(lldb) po URLString.URLString
"https://bibleverse-d0859.firebaseio.com/v/1/books.json?>orderBy="version_code"&equalTo="ASV""

and your code NSURL(string: URLString.URLString)!view error  please not !
my english not good , hope you can understand

Hiya- its not really clear, can you share an example/ simple project to demo the issue?

@XueChenChen This code has changed in Alamofire 4, I suggest you update. There's also better error handling around request generation as well in that version.

authors: XueChenChen grantkemp jshier

repo: Alamofire/Alamofire


text:
docs: add new demo example for highlight menu

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: #169
Summary:

Set the highlight menu option using selected attribute in auro-menuoptions

Type of change:

[x] Other (demo update)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

Hi @jordanjones243,
I will to rebuild docs now, thank you for your information.

The work for the ticket attached to this will now be handled by this PR:

https://github.com/AlaskaAirlines/auro-menu/pull/195

repo: AlaskaAirlines/auro-menu


text:
oceanicnext scheme error

when i try to set oceanicnext scheme, i get stack of errors, first of them is
Error compiling Less stylesheet: /home/mjrev/.atom/packages/base16-syntax/index.less
Line number: 2
'schemes/oceanicNext.less' wasn't found

original file is named oceanicnext.less (lowercase n).
renaming file fixes the problem, but i don't know how would be better by default - changing name of file in schemes folder or in base16-settings.coffee file - it's up to you

Thank you for reporting this. It's due to a bad assumption on my part in the normalization method. With the addition of the new schemes it is no longer the case that capital letters only occur at word boundaries. I'm on a case insensitive system so I didn't catch it beforehand, a fix should be out shortly.

authors: Alchiadus mjrev


text:
Failed to install plugin!

Notices said:
Installing "Google Bard Assistant" ...

Failed to install "Google Bard Assistant

Obsidian Version 1.4.5 on Windows 10

I had it previously installed on MacOS, I was going to update it and it does not. I thought there was a problem in my vault, so I uninstalled it and tried to reinstall it, and I've got this same problem.

Same native story here

Also the same with me. I also disabled all my plugins... the same issue. Then I restarted Obsidian... the same problem. Then I downloaded the .zip and installed it from here. It loaded, but failed to activate with the message "Failed to load plugin google-bard-assistant".

The project seems frozen. Or the developer departed ...

... to a parallel universe where debugging is considered an extreme sport and semicolons are an endangered species.

authors: Ken9969 fabioscarsi miztizm stefandanzl taghoter warfishe

repo: Aldhanekaa/GoogleBardObsidian


text:
177 error boundaries

Closes Error Boundaries #177

Feature

Create ErrorBoundary component

Changelog

Create folder ErrorBoundary in components folder with it's tests, stories, types and the component itself.

Visual evidences :framed_picture:

Checklist

[x] Issue linked
[x] Build working correctly
[x] Tests created

Additional info

The tips in the mirio about git is just perfect! Thanks for who wrote this.

teu pr tem que apontar pra branch master não?

authors: Sherlockzen hxsggsz

repo: Alecell/octopost


text:
[Feature] Add open_testing method to the storage traits.

This PR,

adds the open_testing method to the storage traits, feature guarding them under the "testing" feature flag.
updates the RockDB::open_testing to cache DB handles (better for benchmarks)

What's the point of Option<PathBuf> instead of PathBuf?

This was the interface that was requested during in-person discussion.

Closing as #2060 will change this design.

repo: AleoHQ/snarkVM


text:
Automatic model download doesn't work

mp_rank_00_model_states.pt ends up containing:
<!DOCTYPE html><title>Google Drive - Virus scan warning</title><meta http-equiv="content-type" content="text/html; charset=utf-8"/><link rel="icon" href="null"/>

Google Drive can't scan this file for viruses.

mp_rank_00_model_states.pt (12G) is too large for Google to scan for viruses. Would you still like to download this file?
<form id="downloadForm" action="https://drive.google.com/uc?id=1EiAY3IcKWmGADaLDzdG25ykQghUwza6L&export=download&confirm=t" method="post"><input type="submit" id="uc-download-link" class="goog-inline-block jfk-button jfk-button-action" value="Download anyway"/></form>

causing:
Traceback (most recent call last):
  File "/home/ubuntu/magma/example_inference.py", line 4, in <module>
    model = Magma.from_checkpoint(
  File "/home/ubuntu/magma/magma/magma.py", line 292, in from_checkpoint
    sd = torch.load(checkpoint_path, map_location=torch.device("cpu"))
  File "/usr/local/share/miniconda/lib/python3.9/site-packages/torch/serialization.py", line 593, in load
    return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
  File "/usr/local/share/miniconda/lib/python3.9/site-packages/torch/serialization.py", line 762, in _legacy_load
    magic_number = pickle_module.load(f, **pickle_load_args)
_pickle.UnpicklingError: invalid load key, '<'.

Possibly related to https://github.com/wkentaro/gdown/issues/26

Hey guys,
I think another good option would be to also host the model(s) on Hugging Face model hub.
They also provide huggingface_hub library that can be used as a nice client to get the model download integrated into magma.
We have been using this in Flair library and also hosting some of our models on the model hub.

Yes, i hope this will end up soon in hugginface. We are also setting up hosting on our infrastructure to allow for more bandwidth/ quota. Sorry for the hick-ups.

Google Drive link is also rejecting due to too many people downloading. Happy to setup a file server if we collect some VM & traffic money to a mug.

Diese Datei kann zurzeit nicht angezeigt oder heruntergeladen werden.

Diese Datei wurde in letzter Zeit von zu vielen Nutzern angezeigt oder heruntergeladen. Versuchen Sie später noch einmal, auf die Datei zuzugreifen. Falls die Datei besonders groß ist oder viele Nutzer darauf zugreifen können, kann es bis zu 24 Stunden dauern, bis Sie sie anzeigen oder herunterladen können. Sollten Sie nach 24 Stunden immer noch keinen Zugriff haben, wenden Sie sich an Ihren Domainadministrator.

Hey all, I'm Omar from HF :hugs:
We would love to support having your models in the Hub.  One thing that you might find useful is that model cards have metadata that allow reporting things such as the dataset, metrics, tags, etc. This can help with discoverability, which would be much better than through Google Drive links.
The model could live within an organization for Aleph Alpha for additional visibility, and we have a lightweight Python library called huggingface_hub that would allow users to download/cache the model locally. Would you be interested in this?
Adding the model is relatively simple, here are some instructions for it -> https://huggingface.co/docs/hub/adding-a-model. I actually have one copy here which we could transfer to your org and add a nice model card.

repo: Aleph-Alpha/magma


text:
#57 Predict raises TypeError

#57 Using predict even with rudimentary datasets and both default inputs as well as explicit ones raises TypeError

Issue was arising from the interval dependency. Seems the corrent dependency pyinterval got swaped accidentaly during development. Note both of these packages are poorly maintained

repo: AlexRodis/bayesian-models


text:
🛑 Nyam is down

In 8d7175b, Nyam ($SECRET_URL_NYAM) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nyam is back up in 030e03b.

repo: AlexanderKlimashevskiy/upptime


text:
Owner type

Le type d'owner est "bar" : conflit avec le type de bâtiment ou erreur ?

Rouvrir en cas de bug, aucun conflit détecté

repo: Alexiscomete/A-Discord-Adventure


text:
which xxx.sh not work

I don't know if this is by mintty or msys2, so I post one here too. If not relevent, feel free to close it :).
In linux:
# which virtualenvwrapper.sh
/usr/local/bin/virtualenvwrapper.sh

But on mintty(msys2, git-bash):
$ which virtualenvwrapper.sh
which: no virtualenvwrapper.sh in (/d/Python27:/d/Python27/Scripts:/d/Go/bin:/d/Go/gopath/bin:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files/TortoiseGit/bin:/d/phantomjs-2.1.1-windows/bin:/c/ProgramData/chocolatey/bin:/c/Program Files (x86)/vim/vim80:/d/Windows Kits/8.1/Windows Performance Toolkit:/d/nodejs:/usr/bin:/c/Program Files/Git/cmd:/c/Program Files/Git/mingw64/bin:/c/Program Files/Git/usr/bin)

$ ls /d/Python27/Scripts|grep virtualenvwrapper.sh
virtualenvwrapper.sh

Just can not find this .sh file,  looks like which only searching for xxx.exe file.

Seems relate to x permission, it is weird how they add x to virtualenvwrapper_lazy.sh while chmod not work...
-rwxr-xr-x 1 yuyan 197121 89428 Dec 16 09:22 virtualenv.exe*
-rw-r--r-- 1 yuyan 197121 41384 Aug 19 09:27 virtualenvwrapper.sh
-rwxr-xr-x 1 yuyan 197121  2210 Aug 20 23:16 virtualenvwrapper_lazy.sh*
-rw-r--r-- 1 yuyan 197121   183 Dec 16 09:23 whereis.bat
-rw-r--r-- 1 yuyan 197121  1492 Dec 16 09:23 workon.bat
-rwxr-xr-x 1 yuyan 197121   400 Dec 30 12:56 wsgidav-script.py*
-rwxr-xr-x 1 yuyan 197121 65536 Dec 30 12:56 wsgidav.exe*
-rw-r--r-- 1 yuyan 197121   642 Dec 30 12:56 wsgidav.exe.manifest
-rwxr-xr-x 1 yuyan 197121 89430 Dec 20 08:53 yapf.exe*


text:
Add openbsd-netcat

Sorry for my so many tries. ><
I love using openbsd-netcat more than gnu-netcat because it's more powerful.
So I try a day to make it complied on msys2!
Hope it can be merged!

Maintainer field has to be fixed and Contributor field removed.

The status says this is merged, but it doesn't show up when I pacman -Ss netcat. Do I just need to wait longer? I did a fresh install today and ran pacman -Syu already.


text:
Use metadata to get individual run info

This PR updates the nextflow workflows to work from the metadata files that we have created to track sample information.
Closes #28
The general procedure is to read in the metadata file and use the nextflow function .splitCsv() to process that file into fields that we can then access when creating the channel which will be used by the rest of the workflow.
I also added a workflow (in checks) that can be used to check the md5 hashes of uploaded files. It currently checks all files from all runs in the metadata file. This seems reasonable, as long as we don't run it often. I think it is safe to assume that integrity checks from S3 are sufficient for most usage, and this can be used just to verify that the files we have are the ones that we expect to have been sent.
For reviewers:
I would recommend starting with check-md5.nf, as in many ways that is the simplest workflow here, and because it is new, the whole file is easily visible in the github interface.
While the code is not long, there are a number of things going on here that may be unfamiliar to new nextflow users. One is the use of operator chaining (the .function() syntax in the workflow) which is very much like piping. Another is the use of closures { } for functions like map. There is also at least one place where a variable appears to be used before it is defined.
All of this means that I fully expect questions on how things are actually working. Don't hesitate to ask!

LGTM and equally or possibly more importantly, what's in this PR makes a whole lot more sense to me! 🎉

That is the goal! At some point, you may have to edit or write one of these super-strange workflows!

repo: AlexsLemonade/alsf-scpca


text:
Client multiplexed computed file changes

Issue Number
#676
Purpose/Implementation Notes

removes references of multiplexed as a modality in download options logic
adds new checkbox and warning for multiplexed samples
breaks up merged objects help link
updates default computed file to support a filter (for suggesting project with multiplexed data)
some house cleaning
removes Single-cell data as Single-cell Experiment (R) from multiplexed samples
adds anndata warning to samples table on multiplexed projects

Types of changes

Bugfix (non-breaking change which fixes an issue)
Refactor (addresses code organization and design mentioned in corresponding issue)
New feature (non-breaking change which adds functionality)

Functional tests
N/A
Checklist

[x] Lint and unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Screenshots
N/A

@dvenprasad ready for another look

repo: AlexsLemonade/scpca-portal


text:
Unable to Display Timestamp Overlay in Go2RTC Streams

Summary:
I'm experiencing difficulties adding a timestamp overlay to the video streams in Go2RTC. The goal is to have the timestamp overlay displayed in the video streams generated by Go2RTC so that I can reuse the streams in Frigate and other applications.
I have reviewed: https://github.com/AlexxIT/go2rtc/issues/402, https://github.com/AlexxIT/go2rtc/issues/127, https://github.com/AlexxIT/go2rtc/issues/487
Configuration:

    go2rtc:
      streams:
        front: "ffmpeg:http://192.168.1.1:8080#video=h264"
        back: "ffmpeg:http://192.168.1.2:8080#video=h264"

What I have tried
List of the attempts made to add the timestamp overlay to the Go2RTC streams:
1. Directly within ffmpeg configuration block:
Added drawtext filter directly within the ffmpeg configuration block in Go2RTC, using timestamp_back and timestamp_front flags.

    ffmpeg:
      timestamp_back: -vf "drawtext=text='%{localtime}':x=w/25:y=(h-th)-h/25:fontsize=h/25:fontcolor=white:shadowx=2:shadowy=2"
      timestamp_front: -vf "drawtext=text='%{localtime}':x=w/25:y=(h-th)-h/25:fontsize=h/25:fontcolor=white:shadowx=2:shadowy=2"

2. Directly in stream configuration:
Attempted to add drawtext filter directly in the stream configuration for the front camera using extra_args or appending the filter directly to the ffmpeg command.
    go2rtc:
      streams:
        front:
          ffmpeg: "ffmpeg:http://192.168.1.1:8080#video=h264"
          extra_args: "-vf drawtext=text='DEBUG_TEXT':x=10:y=10:fontsize=24:fontcolor=white:shadowx=2:shadowy=2"

3. Using separate timestamp flags in stream configuration:
Attempted to add separate timestamp_back and timestamp_front flags directly in the stream configuration.
    go2rtc:
      streams:
        front: "ffmpeg:http://192.168.1.1:8080#video=h264#{timestamp_front}"
        back: "ffmpeg:http://192.168.1.2:8080#video=h264#{timestamp_back}"

4. Directly within stream configuration with drawtext filter:
Tried to directly include the drawtext filter within the stream configuration for the front camera.
        go2rtc:
          streams:
            front: "ffmpeg:http://192.168.1.1:8080#video=h264#-vf drawtext=text='DEBUG_TEXT':x=10:y=10:fontsize=24:fontcolor=white:shadowx=2:shadowy=2"
            back: "ffmpeg:http://192.168.1.2:8080#video=h264"

Despite these attempts, the timestamp overlay did not appear on the video streams generated by Go2RTC. The issue persists, and additional assistance or suggestions would be greatly appreciated.
Observe that the camera footage is displayed correctly, but attempts to add a timestamp overlay using ffmpeg flags or other methods have been unsuccessful.
Expected Behavior:
The timestamp overlay should be displayed on the video streams generated by Go2RTC, allowing for easy reuse of the streams in Frigate and other applications.
Actual Behavior:
Despite various attempts to add the timestamp overlay using different methods, including direct ffmpeg flags and additional configuration options, the timestamp overlay does not appear on the video streams.
Additional Information:
I've tried adding the drawtext filter directly in the ffmpeg command within the Go2RTC configuration, but it didn't work.
I've also attempted to apply the drawtext filter directly in the stream configuration for the front camera, but the issue persists.
The error logs from Go2RTC indicate "unknown error" when attempting to apply additional ffmpeg arguments or filters.

Environment:
Go2RTC version: 1.8.4

Logs:
2024-05-10 16:16:58.172208034  [INFO] Preparing new go2rtc config...
2024-05-10 16:16:58.576585406  [INFO] Starting go2rtc...
2024-05-10 16:16:58.670841556  16:16:58.670 INF go2rtc version 1.8.4 linux/arm64
2024-05-10 16:16:58.671604017  16:16:58.671 INF [api] listen addr=:1984
2024-05-10 16:16:58.671608498  16:16:58.671 INF [rtsp] listen addr=:8554
2024-05-10 16:16:58.671909312  16:16:58.671 INF [webrtc] listen addr=:8555
2024-05-10 16:17:08.021380886  [INFO] Starting go2rtc healthcheck service...

Note: Any assistance in resolving this issue and successfully displaying the timestamp overlay on the Go2RTC streams would be greatly appreciated.

Solved by this clear thread that I missed earlier: https://github.com/AlexxIT/go2rtc/issues/741


text:
Dahua vto 2wayaudio and audio settings

I am using the 2wayaudio function on my VTO dahua 2202F with satisfaction. The problem is that to make it work I had to set the correct bitrate with the happy onvif program, otherwise it doesn't work. In the vto web page I don't have any audio configuration to set. Everything works fine for a few days, after which the audio settings go back to the default settings and nothing works anymore and I have to set it again. Is there a definitive procedure to prevent this? The vto is updated to the latest firmware.

Yes, there is:

This you can do: https://github.com/AlexxIT/go2rtc/issues/49#issuecomment-1288196783
Maybe go2rtc will also support this in the future: https://github.com/AlexxIT/go2rtc/issues/105

So, I'd suggest you close this issue.

#49

authors: AlexxIT felipecrs morpheus8888


text:
Add FAQ page to Decapodes

This PR adds the FAQ page requested in #289.

@lukem12345 Would you mind looking at question 5 in issue #289 for me? I'm not familiar with what "artificial diffusion" is.


text:
Swift 4

Just asking, when do you think OHHTTPStubs/Swift will be compatible with Swift 4?
Thanks for your amazing job.

Hi @Jerem42,
I have to admit that I did not try to use OHHTTPStubs with Swift 4 yet.
Can you give us some details on the issues you have when using OHHTTPStubs with Swift 4?
Thanks!

Sure, here's the error when I try to import OHHTTPStubs:
Module compiled with swift 3.1 cannot be imported in Swift 4.0
The same happen if the Swift language version in the Settings is 3.2.

Can you provide some details about the integration tool you are using and follow the issue template and provide the informations it contains, please? 😊
I suspect that you are using Carthage here and I am afraid that we may not be able to support every swift version in this case 😞

Carthage is based on the idea of downloading the pre-compiled binary framework of each library you put in your Cartfile if available. Which is not a good idea until Swift is ABI stable (and discouraged by Apple for this exact reason) because then every time the compiler changes the Swift version then every binary framework is incompatible.
If you're in this situation (using Carthage to integrate OHHTTPStubs) then OHHTTPStubs will not be the only framework you'll have this issue with (every library providing a precompiled version will have the same issue). You'll have to use the --no-use-binaries flag of Carthage to about this issue with OHHTTPStubs and all other libraries you use in your Cartfile. You can find more info in Carthage's own documentation & issues.

You'll have to use the --no-use-binaries flag of Carthage to solve this issue with all other libraries you use in your Cartfile. You can find more info in Carthage's own documentation & issues.

FYI Carthage now falls back to build checked out projects if prebuilt binaries was built with different Swift version from local Swift version, so normally you will not need to add --no-use-binaries option.

Just so we know if there's still work to do on that issue: has anybody had time to test OHHTTPStubs with Xcode 9 & Swift 4 and saw any compilation issue with it or code that would need modification for it to be adapted to Swift 4?

I am using OHHTTPStubs in a Swift 4 project (installed via Carthage) and I haven't experienced any issues using Xcode beta 4. I didn't install the latest beta yet.

Cool, thanks @gonzalezreal for the feedback!
I'm gonna close this one then.
We could still reopen it in case a later beta creates issues but I doubt it since the biggest risk was with the changes in the String API and the string manipulations we do in the matchers but we'd have seen errors by now if we were affected.

authors: AliSoftware Jerem42 Liquidsoul gonzalezreal ikesyo

repo: AliSoftware/OHHTTPStubs


text:
deep animate is not recognized

'deep_animate' is not recognized as an internal or external command,
operable program or batch file.
did it not download correctly?

ok, I think I accidentally canceled downloading and started again, how can I tell it is done?

repo: AliaksandrSiarohin/first-order-model


text:
Wappalyzer breach

Hi Elbert,
I have been receiving multiple emails like these, indicating the breach of  wappalyzer data along with users emails.

I have also forwarded the same to elbert@...
--
Regards,
@bugbaba

Hi @bugbaba,
You should have received the following message a few days ago. I'm sorry for what happened here.

We respect the privacy of your personal information, which is why we are writing to advise you of an event that resulted in the possible disclosure of your personal data.
On 20 January 2020 our database was compromised due to a misconfiguration. No financial information or passwords were included in the breach.
The issue has been resolved and our website is working normally. There is no action you need to take.
If you requested a quote from our website before this date, your email address may have been included in the stolen data.
If you placed an order on our website before this date, your billing address may also have been included in the stolen data.
Some of our customers received an email from the perpetrator offering to sell stolen datasets. This data does not include personal information. If you receive such an email, mark it as spam and do not reply or click any links as it's likely a scam.
We're very sorry for the inconvenience and concern this has caused. We want to assure you we're doing everything we can to safeguard your personal information and will continue to monitor to investigate.

authors: AliasIO bugbaba

repo: AliasIO/wappalyzer

license: mit


text:
不能输出stdout日志

rancher中起了一个 tomcat 将日志输出到ES。
但只是自动创建access 索引，stdout 要输出的catalina索引没有创建。
下面是我的搭建和日志信息：
pilot：
`pilot:
image: registry.cn-hangzhou.aliyuncs.com/acs-sample/log-pilot:latest
environment:
ELASTICSEARCH_HOST: 1.1.1.1
ELASTICSEARCH_PORT: '9200'
ELASTICSEARCH_USER: user
ELASTICSEARCH_PASSWORD: pw
FLUENTD_OUTPUT: elasticsearch
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /:/host
labels:
aliyun.global: 'true'
/etc/fluentd/conf.d 里面也有catalina的。

@type record_transformer
enable_ruby true

host "#{Socket.gethostname}"
index catalina
topic catalina
@target catalina-${time.strftime('%Y.%m.%d')}
docker_container r-app-myweb-1-8636c928

      **tomcat:**

Volumes:   /usr/local/tomcat/logs
labels:    aliyun.logs.catalina=stdout
aliyun.logs.access=/usr/local/tomcat/logs/localhost_access_log.*.txt`
pilot log：
log1:
2018/6/14 下午5:10:37
2018/6/14 下午5:10:37      time_key @timestamp
2018/6/14 下午5:10:37
2018/6/14 下午5:10:37
2018/6/14 下午5:10:37
2018/6/14 下午5:10:37    @type record_transformer
2018/6/14 下午5:10:37    enable_ruby true
2018/6/14 下午5:10:37
2018/6/14 下午5:10:37      host 43434cb2984b
2018/6/14 下午5:10:37      index catalina
2018/6/14 下午5:10:37      topic catalina
2018/6/14 下午5:10:37      @target catalina-${time.strftime('%Y.%m.%d')}
2018/6/14 下午5:10:37      docker_container r-app-myweb-1-8636o928
2018/6/14 下午5:10:37
2018/6/14 下午5:10:37
2018/6/14 下午5:10:37  <match docker.**>
2018/6/14 下午5:10:37    @type elasticsearch
2018/6/14 下午5:10:37    hosts "1.1.1.1:9200"
2018/6/14 下午5:10:37    reconnect_on_error true
2018/6/14 下午5:10:37    user "user"
2018/6/14 下午5:10:37    password xxxxxx
2018/6/14 下午5:10:37    target_index_key "@target"
2018/6/14 下午5:10:37    type_name "fluentd"
2018/6/14 下午5:10:37
2018/6/14 下午5:10:37
Erro log:
P1:
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:692:in readpartial' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:692:in block in on_notify'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:751:in with_io' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:685:in on_notify'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:534:in on_notify' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:507:in attach'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:264:in setup_watcher' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:292:in block in start_watchers'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:278:in each' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:278:in start_watchers'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:258:in refresh_watchers' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/plugin/in_tail.rb:193:in start'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/root_agent.rb:165:in block in start' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/root_agent.rb:154:in block (2 levels) in lifecycle'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/root_agent.rb:153:in each' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/root_agent.rb:153:in block in lifecycle'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/root_agent.rb:140:in each' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/root_agent.rb:140:in lifecycle'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/root_agent.rb:164:in start' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/engine.rb:274:in start'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/engine.rb:219:in run' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/supervisor.rb:774:in run_engine'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/supervisor.rb:523:in block in run_worker' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/supervisor.rb:699:in main_process'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/supervisor.rb:518:in run_worker' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/lib/fluent/command/fluentd.rb:316:in <top (required)>'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/lib/ruby/gems/2.3.0/gems/fluentd-1.0.2/bin/fluentd:8:in <top (required)>' 2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/bin/fluentd:22:in load'
2018/6/14 下午5:10:37  2018-06-14 09:10:37 +0000 [error]: #0 /usr/bin/fluentd:22:in `'
P2:
2018/6/14 下午5:09:182018-06-14 09:09:18 +0000 [error]: #0 Is a directory @ io_getpartial - /host/.
2018/6/14 下午5:09:18  2018-06-14 09:09:18 +0000 [error]: #0 suppressed same stacktrace
2018/6/14 下午5:09:192018-06-14 09:09:19 +0000 [error]: #0 Is a directory @ io_getpartial - /host/.
2018/6/14 下午5:09:19  2018-06-14 09:09:19 +0000 [error]: #0 suppressed same stacktrace
2018/6/14 下午5:09:202018-06-14 09:09:20 +0000 [error]: #0 Is a directory @ io_getpartial - /host/.
2018/6/14 下午5:09:20  2018-06-14 09:09:20 +0000 [error]: #0 suppressed same stacktrace
2018/6/14 下午5:09:212018-06-14 09:09:21 +0000 [error]: #0 Is a directory @ io_getpartial - /host/.
2018/6/14 下午5:09:21  2018-06-14 09:09:21 +0000 [error]: #0 suppressed same stacktrace

@yixiua 使用registry.cn-hangzhou.aliyuncs.com/acs-sample/log-pilot:0.9.3-filebeat这个image看看

参考： https://helpcdn.aliyun.com/document_detail/68264.html?spm=a2c4g.11186623.6.643.LhFBJ6 这个里面的配置，   能够收集到access的日志， 但是stdout的日志也收集不到。
镜像替换成：registry.cn-hangzhou.aliyuncs.com/acs-sample/log-pilot:0.9.3-filebeat 后也是同样的问题。

log-pilot中的配置容器采集配置如下：
/etc/filebeat/prospectors.d # cat 75f71f957d2f28537ba52423a1e80a354bac42b42541fa08a2d22a267b4c8169.yml

type: log
enabled: true
paths:
- /host/var/lib/kubelet/pods/edd712d3-8cd7-11e8-b04f-005056861d76/volumes/kubernetes.io~empty-dir/accesslogs/localhost_access_log.*.txt
scan_frequency: 10s
fields_under_root: true
fields:
index: access

topic: access

docker_container: k8s_cuckoo-web_cuckoo-web-589466c59f-kcjtg_vsit_edd712d3-8cd7-11e8-b04f-005056861d76_0

k8s_container_name: cuckoo-web

k8s_pod: cuckoo-web-589466c59f-kcjtg

k8s_pod_namespace: vsit

tail_files: false
close_inactive: 2h
close_eof: false
close_removed: true
clean_removed: true
close_renamed: false

type: log
enabled: true
paths:
- /host/.*
scan_frequency: 10s
fields_under_root: true
docker-json: true
fields:
index: catalina

topic: catalina

docker_container: k8s_cuckoo-web_cuckoo-web-589466c59f-kcjtg_vsit_edd712d3-8cd7-11e8-b04f-005056861d76_0

k8s_container_name: cuckoo-web

k8s_pod: cuckoo-web-589466c59f-kcjtg

k8s_pod_namespace: vsit

tail_files: false
close_inactive: 2h
close_eof: false
close_removed: true
clean_removed: true
close_renamed: false

上述问题已解决：
目前集群中的docker版本：1.13.1 ， 他默认使用的log driver是“journald” 因此无法采集stdout日志。
参考：https://segmentfault.com/a/1190000014559152 中的方法，将log driver 修改为 json-file
如果 systemctl restart docker 报错， 可将  /var/run/docker.sock 文件（夹）删除后再重启

authors: chenqz1987 tangxy yixiua

repo: AliyunContainerService/log-pilot


text:
Release 0.9.8

End-user friendly description of the problem this fixes or functionality that this introduces

[ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

Release 0.9.8

Give a summary of what the PR does, explaining any non-trivial design decisions

Link of any specific issues this addresses

@mamoodi - I may have missed it, changes to docs with the new version number come afterwards?

Release process:

Commit is tagged
PR for upping all versions is opened and merged
Publish PyPi Package workflow is run
Release is created on the release page

authors: mamoodi tobitege

repo: All-Hands-AI/OpenHands


text:
Decoration didn't reload after observable object changed

@State var observed: String = "star.fill"

CalendarView()
  .decorating(datesToDecorate) { dateComponents in
    if dateComponents.day == specialDay {
      return .customView {
        Image(systemName: observed) // won't trigger decoration reload after observed changed
          .foregroundColor(.yellow)
      }
    }

    return .default(color: .green, size: .small)
  }

Button {
  observed = "star"
} label: {
  Text("Change decoration")
}

Workaround
      return .customView {
        Decoration(observed: observed) // here!
      }

struct Decoration: View {
  @Bindable var observed: String
  var body: some View {
    Image(systemName: observed)
          .foregroundColor(.yellow)
  }
}

repo: AllanJuenemann/CalendarView


text:
add screen to calibrate touch

https://github.com/user-attachments/assets/2015b0c2-660f-4255-8eae-1f0d26a2682e

:tada: This PR is included in version 0.13.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
Add new harp treadmill device to workflow

[x] Write interface
[ ] Add the device to aind-data-schema
[ ] Integrate in workflow (replace the current wheel)
[ ] Integrate break in the task logic

https://github.com/AllenNeuralDynamics/harp.device.treadmill

Interface tested and deployed!


text:
Session metadata error – very low success rate

Related to those issues on individual errors:
https://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/490
https://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/491
https://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/493
I have been handing/uploading all data acquired between 20240528-yesterday, that should have rig and session metadata, and realized that session.json generation failure rate seems very high (86/393 >20%). I think this should be fix with high priority.
@XX-Yin @alexpiet are you two working on this?
As I'm working on back-filling rig+session for old data (2024 early and 2023 late) (see this issue: https://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/482), I will test if those "failed" session can be easily rescued by similar back-filling operation.
adding @rachelstephlee , who told me that she is happy to help to be familiar with data structure etc.

@XX-Yin said he will take care of the session metadata errors.

I can make updates.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Alex Piet @.>
Sent: Monday, July 1, 2024 8:59:58 AM
To: AllenNeuralDynamics/dynamic-foraging-task @.>
Cc: Xinxin Yin @.>; Mention @.>
Subject: Re: [AllenNeuralDynamics/dynamic-foraging-task] Session metadata error – very low success rate (Issue #569)
@XX-Yinhttps://github.com/XX-Yin said he will take care of the session metadata errors.
—
Reply to this email directly, view it on GitHubhttps://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/569#issuecomment-2200528585, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2CTX5Q54K3QAYPDYQSWD6LZKF4H5AVCNFSM6AAAAABKDBAB6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGUZDQNJYGU.
You are receiving this because you were mentioned.Message ID: @.***>

@alexpiet @hagikent
Started working on backfiling session.json for session that failed to generate metadata.
Could you point me to example dialog_metadata_file? What exactly am I supposed to provide in addition to the main json_file to generate_metadata?

I will be out of office in the remaining days of this week. It’s very straightforward and I can show you next week. I will try to make updates on session metadata on weekends if I am still energetic, otherwise will update it next week.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Kenta M. Hagihara @.>
Sent: Wednesday, July 3, 2024 12:56:44 AM
To: AllenNeuralDynamics/dynamic-foraging-task @.>
Cc: Xinxin Yin @.>; Mention @.>
Subject: Re: [AllenNeuralDynamics/dynamic-foraging-task] Session metadata error – very low success rate (Issue #569)
@alexpiethttps://github.com/alexpiet @hagikenthttps://github.com/hagikent
Started working on backfiling session.json for session that failed to generate metadata.
Could you point me to example dialog_metadata_file? What exactly am I supposed to provide in addition to the main json_file to generate_metadata?
—
Reply to this email directly, view it on GitHubhttps://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/569#issuecomment-2205339711, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2CTX5SC73CX2IW4P25HKBDZKOVDZAVCNFSM6AAAAABKDBAB6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBVGMZTSNZRGE.
You are receiving this because you were mentioned.Message ID: @.***>

The code to generate the metadata is confusing. @XX-Yin should be able to help.
The main code generates the metadata by this call:
foraging_gui.generate_metadata(Obj=Obj)
So all of the information should be in that dictionary. Which should have a key meta_data_dialog, which gets populated by this call: self.Metadata_dialog.meta_data
You can see the fields that should be there by looking for that key in a saved session:

Which is also the fields of the metadata popup window

Let me know if you need more help

[like]  Xinxin Yin reacted to your message:

From: Kenta M. Hagihara @.>
Sent: Wednesday, July 3, 2024 6:13:53 PM
To: AllenNeuralDynamics/dynamic-foraging-task @.>
Cc: Xinxin Yin @.>; Mention @.>
Subject: Re: [AllenNeuralDynamics/dynamic-foraging-task] Session metadata error – very low success rate (Issue #569)
Thanks both. I see both straightforward and confusing 😂
I think I sort of got high-level concept now. I was using/calling foraging_gui.generate_metadata as a standalone script (not as a function) and was confused why info to be ingested into metadata have to be separately fed from two json files. Understandable that most of them are ephys specific.
@XX-Yinhttps://github.com/XX-Yin
I will try this later this week and get back to you if I cannot fully figure out by next week. Have a good 7/4 week.
—
Reply to this email directly, view it on GitHubhttps://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/569#issuecomment-2206931227, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2CTX5VFUO2KLYA7Y7O5YILZKQ5ODAVCNFSM6AAAAABKDBAB6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBWHEZTCMRSG4.
You are receiving this because you were mentioned.Message ID: @.***>

@hagikent
To backfill the session metadata, you can follow steps below. Please let me know if it works.

fill out the session metadata dialog.

save the session metadata dialog by clicking the save button in the dialog. The data will be saved to C:\Users\user_name\Documents\ForagingSettings\metadata_dialog.
run generate_metadata. And you need to provide the behavior json file, dialog_metadata_file saved in the step 2 and the output_folder. One example is shown below:
generate_metadata(json_file=r'Y:\715083\behavior_715083_2024-04-26_17-12-15\behavior\715083_2024-04-26_17-12-15.json', dialog_metadata_file=r'C:\Users\xinxin.yin\Documents\ForagingSettings\metadata_dialog\323_EPHYS3_2024-05-13_12-38-51_metadata_dialog.json', output_folder=r'F:\Test\Metadata')

thanks @XX-Yin
I'm trying NOT to use the GUI; I need to reduce manual steps.
The number of sessions missing session.json after 240528- is not so much and manually patching one-by-one is likely fine.
However, I need to backfill metadata for data from late2023 and early2024 and I cannot do this manual steps for all of them.
Let me try differently and get back to you if need some help/clarification.

thanks @XX-Yin I'm trying NOT to use the GUI; I need to reduce manual steps.
The number of sessions missing session.json after 240528- is not so much and manually patching one-by-one is likely fine. However, I need to backfill metadata for data from late2023 and early2024 and I cannot do this manual steps for all of them.
Let me try differently and get back to you if need some help/clarification.

You don't need to fill out all fields in the session metadata dialog. Probes, Left lick sprout reference positions, Stick microscopes  and Protocols.io ID are optional.

I made it work without using the GUI to generate the metadata_dialog file.
I sort of agree with @alexpiet saying that this is confusing – information to be ingested into rig.json and sessions.json are intermingled/spread around in both dialog.json and the main-json (nnnnnn_YYMMDDTTTTTjson). And most confusing part to me was that the main-json has Metada_dialog key; very intertwined. I suppose this is because of
some historical/development-trajectory reasons but not very straightforward for those who didn't know the history.
Longer-term, this should be refactored by incorporating AIND-mapper.
For now, I made a minimal generic dialog.json stab, and a snippet to generate only session.json. By this, you only need to feed the main-json to produce sessions.json, most practical converter function for the backfilling purpose.
Will execute the backfilling process and upload remaining data (2023late, 2024early, session-missing-after20240528) by the end of this week.

@hagikent
Glad to see that you can backfill some old sessions. Can you explain a little more how do you make it?
I can image you only need to provide fields highlighted below to generate the session metadata, and don't need to care about the ephys part. These fields should be consistent if you don't change the rig metadata, which means you only need to do once.

I understand that the code is a little complex that is determined by the complex nature of session metadata itself. During the design process, modularity was considered as a major requirement. The behavior json, rig metadata, and metadata dialog are largely independent in the code. However, they need share information to generate the session metadata. For example, the session metadata requires a lot of fields from the behavior json; the ephys part, laser parts, daqs etc of the session metadata require rig metadata to keep naming consistent; the metadata dialog requires the rig metadata to parse the probes and the stick microscope. Their integration is inevitable and necessary to automate the entire process and reduce human intervention.
However, please keep in mind that you can use the independent class GenerateMetadata to flexibly integrate them. The metadata dialog is designed to capture fields not directly provided by the behavior json. So, you only need to provide metadata dialog and behavior json to GenerateMetadata to generate the session metadata. The metadata dialog (if provided) is saved to the behavior json (just one dictionary called meta_data_dialog), which has multiple advantages. 1) We can visualize these metadata fields when we load a behavior json. 2) Behavior json and metadata dialog can communicate with each other through a shared data format. 3) If we want to regenerate the session metadata when we update the code, we only need the behavior json as it contains all information (If we add some fields that are not contained in the behavior json, we need to add this field to the metadata dialog).
Please let me know if you need help to generate the session metadata, or if you find specific parts that are confusing so we can make updates.

By the way, my understanding is AIND-mapper is more for the rig metadata than the session metadata. The exact form of AIND-mapper is not clear. I've been advocating for standardizing "rig metadata", but it seems challenging (one discussion is here https://github.com/AllenNeuralDynamics/dynamic-foraging-task/discussions/460).

https://github.com/AllenNeuralDynamics/aind-metadata-mapper
No, mapper is for both session and rig.

It's a collection from many projects. Not sure if we have a general framework to make session metadata reusable across projects
Get Outlook for iOShttps://aka.ms/o0ukef

From: Kenta M. Hagihara @.>
Sent: Tuesday, July 9, 2024 11:50:39 PM
To: AllenNeuralDynamics/dynamic-foraging-task @.>
Cc: Xinxin Yin @.>; Mention @.>
Subject: Re: [AllenNeuralDynamics/dynamic-foraging-task] Session metadata error – very low success rate (Issue #569)
https://github.com/AllenNeuralDynamics/aind-metadata-mapper
No, mapper is for both session and rig.
—
Reply to this email directly, view it on GitHubhttps://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/569#issuecomment-2219695077, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2CTX5UXJHISR5QYELXJV3TZLTKT7AVCNFSM6AAAAABKDBAB6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJZGY4TKMBXG4.
You are receiving this because you were mentioned.Message ID: @.***>

That's not the point... the idea of externalizing the mapper function is to catch up with the evolving metadata scheme versions. Our current metadata generation functions are based on a fixed version that is already old and will soon get very obsolete.
Anyway, backfilling is done. You can close this thread if the session metadata failure problem is solved.

How does the mapper handle the version of the schema? Some changes of the schema require change the code for generating session metadata (For example, they changed the folder structure in the schema and the code in the session metadata needed to be changed accordingly).
Still working on other parts.

authors: XX-Yin alexpiet hagikent


text:
Darkened Corner on Images

Environment

Camera:  ZWO  ASI678MC
OS: Bullseye
Allsky version: v2023.05.01
Pi 3 Model B Revision 1.2 1GB

Bug Description
All images have the upper left 1/4 frame (exactly 1/4) significantly darkened (about 25%) relative to the remainder of the frame.  I tried turning off all the annotations (also in the top left corner) and it had no effect.  Shooting images with other software does not show the effect.  This problem has existed since I installed this camera.  It did not occur with a previous ASI120MC.
Richard

Can you post an image that more clearly shows the problem?  The image above looks fine to me.
Also, please attach your ~/allsky/config/config.sh file.

I have enhanced the contrast across the difference in sky background in the attached.  The dark area shows much more visibly in the timelapse as it remains stationary while the stars (and clouds, sigh) move.

And here is my config.sh.
config.txt

I see it now.  My first guess would have been a hardware problem, but it works on other software so that's not likely to be the reason.
What other software does it work on?
Is that on the Pi or a PC?

@RLWagner, any update?

@RLWagner, any update?

Sorry it's been so long to reply - the weather here has been awful and unsuitable to open the observatory to get a usable daytime image.  The darkened corner does not appear in daytime allsky images, and does not appear in images taken with other software on either RPi or Windows PCs.  It seems to be a problem only with nighttime images from allsky.

That's real strange.  Try setting Overlay Method to "Legacy" to rule out the overlay module.  It's possible you have a rectangle or image in your Overlay that is partially transparent and only shows up on dark images.

Had a similar issue. I had moved to the ASI178 after utilizing the ASI224. It appeared to be an issue with the software knowing the sensor size. A re-install of allsky with the new camera attached fixed the issue. ~ Clear Skies

@H-who, when you first started using the ASI178 did you select Refresh from the Camera Type field in the WebUI?  That causes Allsky to poll the attached camera to get its sensor size and other capabilities.  That's what installing Allsky does.

I did, I was on version 3.  Tried rebooting as well. When moving between the overly editors on my 2nd allsky with another 224 on board you could also see an additional variable field on the image that was at the bottom of the smaller square in the image. That suggested to me the software was not reading the image sensor size correctly. I messed around for a bit but besides refreshing the camera I decided to re-flash. In doing so I moved to allsky v4 (did not want to leave that out).

@H-who, what is the "smaller square in the image"?
When you switch camera models of the same camera brand, Allsky currently uses the same configuration  file which will likely have incorrect screen resolutions.
We need to change this to have different overlay configurations for each camera model, like we do for the allsky settings.

In the provided images above by OP, you can see a quarter of the image (top left) is essentially a smaller square within the larger image.  Unlike theirs, I also had an overlay variable of $CameraModel (similar) at the bottom of that inlayed smaller square. That is what tipped me off to something in config being screwy. Yes, on the different camera model/resolutions recommendation. I figured it pulled the sensor size information on original install and just was not updating even with the refresh and reboot.

@Alex-developer,
If a user had a low-resolution camera and replaced it with a higher resolution one but didn't Refresh the Camera Type in the WebUI, what impact would that have on the Overlay Editor?
Would they see something like the second screenshot above where there is a darker rectangle whose size is that of the old camera?

@H-who,
By default the Camera Type and Model are on the overlay at the bottom left, down 1070 pixels for ZWO cameras.  We need to change that since the ASI120, and possibly other cameras, have a resolution smaller than that.
For discussion sake, assume that appeared at the bottom of your images.  When you installed a higher resolution camera those fields would still be 1070 pixels from the top, but would now be above the bottom - the higher resolution the higher they would be.
This is what you saw.  It's an artifact of using pixels for locations rather than, for example, percents or some other unit that scales with the resolution.

authors: EricClaeys H-who RLWagner

repo: AllskyTeam/allsky


text:
Add ability to evict blocks of open files to lower storage tiers

Is your feature request related to a problem? Please describe.
Currently if you load a single file that is larger than your T0 cluster capacity (for example: 70GB, 10GB per worker, 7 workers), then the write will never end (eventually timing out) and the workers will loop with the same error in #9796.
SpaceReserver failed to free $(workerMEMCapacity*lowWaterMarkRatio) bytes on tier MEM for high watermarks: Failed to find an eviction plan to free $(workerMEMCapacity*lowWaterMarkRatio) bytes space at location MEM

This also happens if your blocks aren't distributed evenly across the cluster and one of your workers reach 100% MEM capacity.
A workaround is to split your large files into smaller parts and work with them individually (open bigfile-part1, do what you need to do, close bigfile-part1, open bigfile-part2, etc)
Describe the solution you'd like
Have the ability to evict blocks that are a part of an open file from T0 to T1.
This would lead to inconsistent R/W speeds when specific blocks are being R/W and a lot of swapping between T0 and T1, but at least your entire Alluxio stack won't fall over.
Describe alternatives you've considered
Splitting bigfile into bigfile-part1, bigfile-part2, bigfile-partN is a possible workaround.
Urgency
Not very urgent. Would be a nice feature (or config flag that can be set)

This also happens if you use alluxio.user.file.write.tier.default=1 and then try to read bigfile from Alluxio.
The blocks from bigfile will be CACHE_PROMOTED from T1 to T0 before it is served, if bigfile is too big (>maxT0Capacity), then the same as above will happen.

repo: Alluxio/alluxio


text:
Update version to 2.6.3-SNAPSHOT for branch-2.6

Alluxio Version:
2.6.2
Describe the bug
Since 2.6.2 has been released, need to update version to 2.6.3-SNAPSHOT for branch-2.6
To Reproduce
Expected behavior
Urgency
Trivial
Additional context
No

Branch-2.6 doesn't updates its numbers with OS releases per our release protocol. I'm closing this issue for now. If you see the necessity, feel free to reopen or raise new issue to discuss this. Thank you for your contribution!


text:
Fix S3 API ListStatus return value

What changes are proposed in this pull request?
S3 doesn't have dir concept so it will return size 0 for all non-object content with delimiter /.
Why are the changes needed?
make return value correct, tested as follows:
aws s3api list-objects-v2 --bucket shouwei-test
{
    "Contents": [
        {
            "LastModified": "2021-11-04T01:33:07.000Z",
            "ETag": "\"d41d8cd98f00b204e9800998ecf8427e\"",
            "StorageClass": "STANDARD",
            "Key": "alluxio/",
            "Size": 0
        },
        {
            "LastModified": "2021-11-04T01:33:08.000Z",
            "ETag": "\"d41d8cd98f00b204e9800998ecf8427e\"",
            "StorageClass": "STANDARD",
            "Key": "alluxio/special_backups/",
            "Size": 0
        },
        {
            "LastModified": "2021-11-04T01:33:08.000Z",
            "ETag": "\"4a6b70de44d18dffbd94860a7d60f9e2\"",
            "StorageClass": "STANDARD",
            "Key": "alluxio/special_backups/alluxio-backup-2021-11-04-1635989588831.gz",
            "Size": 190
        }
    ]
}
aws s3api list-objects-v2 --endpoint-url http://localhost:39999/api/v1/s3 --bucket shouwei-test
{
    "Contents": [
        {
            "LastModified": "2021-11-18T20:04:04.068Z",
            "Key": "alluxio/",
            "Size": 0
        },
        {
            "LastModified": "2021-11-18T20:04:04.068Z",
            "Key": "alluxio/special_backups/",
            "Size": 0
        },
        {
            "LastModified": "2021-11-03T18:33:08.000Z",
            "Key": "alluxio/special_backups/alluxio-backup-2021-11-04-1635989588831.gz",
            "Size": 190
        }
    ]
}

Does this PR introduce any user facing changes?
s3 API change.

Codecov Report

Merging #14558 (f19d180) into master (f7b7558) will increase coverage by 8.89%.
The diff coverage is 0.00%.

:exclamation: Current head f19d180 differs from pull request most recent head 270e718. Consider uploading reports for the commit 270e718 to get more accurate results

@@             Coverage Diff              @@
##             master   #14558      +/-   ##
============================================
+ Coverage     29.55%   38.44%   +8.89%
- Complexity     5951     8533    +2582
============================================
  Files          1494     1494
  Lines         87681    87696      +15
  Branches      10452    10453       +1
============================================
+ Hits          25910    33719    +7809
+ Misses        59668    51463    -8205
- Partials       2103     2514     +411

Impacted Files
Coverage Δ

...c/main/java/alluxio/proxy/s3/ListBucketResult.java
0.00% <0.00%> (ø)

...in/java/alluxio/proxy/s3/S3RestServiceHandler.java
2.51% <0.00%> (+2.51%)
:arrow_up:

...n/java/alluxio/underfs/s3a/S3AUnderFileSystem.java
16.97% <0.00%> (+16.97%)
:arrow_up:

...mmon/src/main/java/alluxio/metrics/MetricInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...roxy/src/main/java/alluxio/proxy/ProxyProcess.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...roxy/src/main/java/alluxio/web/ProxyWebServer.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...main/java/alluxio/file/options/DescendantType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...er/src/main/java/alluxio/worker/WorkerProcess.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/src/main/java/alluxio/master/MasterRegistry.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/src/main/java/alluxio/worker/WorkerRegistry.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 581 more

Continue to review full report at Codecov.

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

FYI @jffree

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.7 please

authors: HelloHorizon codecov-commenter


text:
Fix aws s3 cp with source object having special characters in it

What changes are proposed in this pull request?

Fixed the issue of unable to do aws s3 cp when the source objects has special characters in it. The source object are specified in the header x-amz-copy-source which is url encoded, it should be decoded to give the correct source object name.
Add access log to display req http verb / path / query / http body content length / time for processing the request. As well in the debug mode the request and response headers will be displayed.
Fixed when the uploadId is not found in multipart upload, it should return NoSuchUpload error code instead of NoSuchKey.

Why are the changes needed?
To fix incorrect behavior in aws cp and multipart upload APIs.
Does this PR introduce any user facing changes?
No.

error from checkstyle/findbugs build:
2022-10-11T03:44:41.7178960Z 03:44:41.714 [INFO] --- spotbugs-maven-plugin:4.0.4:check (default) @ alluxio-core-server-proxy ---
2022-10-11T03:44:41.7307867Z 03:44:41.719 [INFO] BugInstance size is 2
2022-10-11T03:44:41.7370181Z 03:44:41.730 [INFO] Error size is 0
2022-10-11T03:44:41.7490897Z 03:44:41.745 [INFO] Total bugs: 2
2022-10-11T03:44:41.8175107Z 03:44:41.807 [ERROR] Medium: Format string should use %n rather than \n in alluxio.web.ProxyWebServer.logAccess(HttpServletRequest, HttpServletResponse, Stopwatch) [alluxio.web.ProxyWebServer] At ProxyWebServer.java:[line 155] VA_FORMAT_STRING_USES_NEWLINE
2022-10-11T03:44:41.8176705Z 03:44:41.815 [ERROR] Low: Unchecked/unconfirmed cast from javax.servlet.ServletResponse to javax.servlet.http.HttpServletResponse in alluxio.web.ProxyWebServer$1.service(ServletRequest, ServletResponse) [alluxio.web.ProxyWebServer$1] At ProxyWebServer.java:[line 110] BC_UNCONFIRMED_CAST

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.8 please


text:
Split BlockStoreEventListener.onCommitBlock()

What changes are proposed in this pull request?
listener.onCommitBlock() cannot reflect the state difference between commitBlockToLocal and commitBlockToMaster, so some times when commitBlockToMaster failed the listener.onCommitBlock() will still be called. This PR separated  the listener.onCommitBlock() to onCommitBlockToLocal() and onCommitBlockToMaster(), and added corresponding UT to PagedBlockStore and MonoBlockStore.
Why are the changes needed?
Please clarify why the changes are needed. For instance,

listener.onCommitBlock() cannot reflect the state difference between commitBlockToLocal and commitBlockToMaster, so some times when commitBlockToMaster failed the listener.onCommitBlock() will still be called. The separation of the listener.onCommitBlock() can eliminate this inconsistency.

Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including
No user-facing changes
previous conversation is here since I select incorrect base repo the first time I create this PR...

alluxio-bot, merge this please


text:
[SMALLFIX] Disable delegation by default

Since delegation is being introduced in this version, turn it off by default. Also updates the ufs read buffer size to be equal to our remote read buffer size.

LGTM

LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10242/
Test PASSed.

Merged build finished. Test PASSed.

LGTM


text:
NoIPCFile thrown when discord is not running

This exception should probably be handled instead of the IDE poping up with an alert
Unhandled exception in [StandaloneCoroutine{Cancelling}@1636fcbd, Dispatchers.Default]

dev.cbyrne.kdiscordipc.core.error.ConnectionError$NoIPCFile: Failed to find an IPC file. Is Discord open? Is this application allowed to access temporary files?
	at dev.cbyrne.kdiscordipc.core.error.ConnectionError$NoIPCFile.<clinit>(ConnectionError.kt)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:95)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:99)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:99)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:99)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:99)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:99)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:99)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:99)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:99)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:99)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.findIPCFile(SocketHandler.kt:99)
	at dev.cbyrne.kdiscordipc.core.socket.handler.SocketHandler.connect(SocketHandler.kt:59)
	at dev.cbyrne.kdiscordipc.KDiscordIPC.connect(KDiscordIPC.kt:83)
	at dev.cbyrne.kdiscordipc.KDiscordIPC.connect$default(KDiscordIPC.kt:76)
	at com.almightyalpaca.jetbrains.plugins.discord.plugin.rpc.connection.DiscordIpcConnection$connect$2.invokeSuspend(DiscordIpcConnection.kt:59)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)

Bump. This issue seems strange to have. Getting an error every time I open my IDE is annoying lowering my attention to IDE exceptions in general, which is not particularly good. :slightly_smiling_face:

This is occurring for me even with Discord running.
System: Pop!_OS 22.04 LTS
I reinstalled Webstorm using JetBrains Toolbox instead of via Flatpak, no change.
My solution: After switching Discord from Flatpak to their direct .deb distribution, Discord Integration began working again.


text:
Support alignment in votes tally

Making a fully functional spreadsheet to support 5 gangs at once might end up with a bit of combinatorial hell or at least overly long expressions, so I'd rather generate the battle of gangs spreadsheet from the tally tool instead.

I think I made it in time? What do you mean the GMC Jam 51 results are already out?

repo: Alphish/game-jam-tools


text:
Fix cypress tests which are failing in github actions

Tasks

[x] Fix alle API-delegering og Idporten failing tests
[ ] Check how it appears in GitHub Actions after the pull request has been merged into the main branch.

API-delegering testene fortsatt feiler da skal jeg utvikle de testene i playwright instedenfor å fikse de i cypress.


text:
Fix bugs in List component

Description

Removes dataModelBinding validation that asserts that you can only use bindings from table headers. This check was broken when initially added, but fixed in #2108. It turns out that several apps in prod used dataModelBindings for mapping columns that were not shown in tableHeaders, so fixing this dataModelBinding validation was a breaking change.
Removing filteredRows from ListComponent. This would filter out values that should not be shown in mobile view if tableHeadersMobile was set. The only problem is that the filteredRows object was also used for setting formData, so if you scaled down your browser window, some fields may no longer get saved when you click the row. Added unit tests for this.
Table was using the raw data-list row when mapping cells in the table body. This does not preserve the column ordering specified in table-headers, and if not all columns in the data-list were used in table headers it would add more columns to the table body than the header has (see image below). Now using tableHeaders as the source of truth for what goes where.

Related Issue(s)

https://digdir.slack.com/archives/C0760NPT2BE/p1729059789947969

Verification/QA

Manual functionality testing

[x] I have tested these changes manually
[ ] Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
[ ] No testing done/necessary

Automated tests

[x] Unit test(s) have been added/updated
[ ] Cypress E2E test(s) have been added/updated
[ ] No automatic tests are needed here (no functional changes/additions)
[ ] I want someone to help me make some tests

UU/WCAG (follow these guidelines until we have our own)

[ ] I have tested with a screen reader/keyboard navigation/automated wcag validator
[x] No testing done/necessary (no DOM/visual changes)
[ ] I want someone to help me perform accessibility testing

User documentation @ altinn-studio-docs

[ ] Has been added/updated

[x] No functionality has been changed/added, so no documentation is needed
[ ] I will do that later/have created an issue

Support in Altinn Studio

[ ] Issue(s) created for support in Studio

[x] This change/feature does not require any changes to Altinn Studio

Sprint board

[x] The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
[ ] I don't have permissions to do that, please help me out

Labels

[x] I have added a kind/* label to this PR for proper release notes grouping
[ ] I don't have permissions to add labels, please help me out

Code looks good to me! 👍
Found a couple of issues through accessability testing, though they were probably there earlier as well.
One is that the selected value of the list is read as the stringified json object of the row, which is not that user friendly:

The other is just an empty header reported by WAVE:

This could probably be solved by using a visually hidden text that describes the action; "Velg/Select" or something.

though they were probably there earlier as well.

Indeed, pretty sure its been like this since day one of the List-component

Does this not have a wcag issue?

I only found this: #1850
But it does not mention the issues i found.
We could update that issue with the ones i found i guess 😊

authors: Magnusrm bjosttveit

repo: Altinn/app-frontend-react


text:
Первая страничка-пример с использование tymeleaf

resolve #2

repo: Amaralus/no-code-qa-platform


text:
return this from cacheElements

By doing so, it will allow easier chaining
of additional method calls after render()

Pinging @AmpersandJS/core-team let's use this or lose this.

@wraithgar I'm fine with returning this but I don't want to change the examples/docs to show that you should do return this.cacheElements

+1 on @HenrikJoreteg's points

Merged w/o readme updates.

published as v7.3.0

authors: HenrikJoreteg lukekarrys nathanstitt wraithgar

repo: AmpersandJS/ampersand-view


text:
[BUG] Sendgrid API key is used even when empty

Describe the bug
If I do not provide SENDGRID_API_KEY I see the following error message in my container logs: API key does not start with "SG."
This seems to be coming from here: https://github.com/AmruthPillai/Reactive-Resume/blob/main/server/src/mail/mail.service.ts#L10
Looks like we're initialising the mail service even if SendGrid tokens aren't available/are empty?
It would be nice if we only set the API Key if it's not an empty string/null.
Product Flavor

[ ] Managed (https://rxresu.me)
[X] Self Hosted

Got it, will fix this in an upcoming commit.

authors: AmruthPillai michael-robbins

repo: AmruthPillai/Reactive-Resume


text:
🐛 [BUG] - TypeError unsupported operand type(s) for *=: 'NoneType' and 'int'

Description
Problem Description
The error message is telling us that there's an unsupported operand type for the *= operation.
The issue is happening in the song_sync_continuation_score function in the file result/score.py on line 71. There, the line previous_result.score *= -1 is trying to multiply a None value with an integer. I'm not sure if the previous result's score should always be defined or that we should perhaps initialise it when it doesn't exist and we cannot multiply.
See also https://uva-aml.sentry.io/issues/5413868492/?project=4506353897570304&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=7d&stream_index=3
Screenshots
Sentry

Session results on Acceptance
As it tries to get the previous result with the key "recognize", we can see that result is not always there (whether that's intentional or not), so that probably results into previous_result = result.session.get_previous_result(['recognize']) resolve into None. And from that you can obviously not read the score property.

Reproduction URL
http://illc-aml-mu-prd.science.uva.nl/server/result/score/
Reproduction steps
n/a

Logs
https://uva-aml.sentry.io/issues/5413868492/?project=4506353897570304&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=7d&stream_index=3

Browsers
No response
OS
No response
Additional context
No response

This probably happens due to the race condition that is fixed in #1043, but the questions is: should we handle a scenario like this or should we always assume that previous score is defined?

Most likely fixed by #1043 - the issue doesn't seem to appear anymore after of 2024-05-31

repo: Amsterdam-Music-Lab/MUSCLE


text:
chore(Examples, PeriphDrivers): MAX32655: test examples on Rev. B production silicon

This PR includes the changes related to testing, debugging, and updating each of the non-BLE examples for the MAX32655 Rev. B production parts. The Flash and I2C_Playback examples each have minor bug fixes and the changes for the rest of the examples are mainly just README updates.

Also, I recommend merging the latest changes from main so you have the auto-labeler updates.

authors: Jacob-Scheiffler sihyung-maxim

repo: Analog-Devices-MSDK/msdk


text:
Extend Sytling to allow check for existing of a property

Currenlty you have to make sure a property exists if you use it in Cesium3DTileStyle. But if you have a generic UI sometimes you don't know if a Tileset as has property, because its depend on conent of each tile.
So following code can cause a crash if MYPORPERTY does not exists:
    var tileset = new Cesium3DTileset({url : 'data'});
    tileset.style = new Cesium3DTileStyle({
        "color" : {
            "conditions" : [
                ["(${MYPORPERTY} === 0)", "rgb(196, 196, 196)"],
                ["(${MYPORPERTY} === 1)", "rgb(128, 128, 128)"],
                ["true", "rgb(255, 255, 255)"],
            ]
        }
    });

So it would be nice if you could write something like this:
    var tileset = new Cesium3DTileset({url : 'data'});
    tileset.style = new Cesium3DTileStyle({
        "color" : {
            "conditions" : [
                ["(defined(${MYPORPERTY}) && ${MYPORPERTY} === 0)", "rgb(196, 196, 196)"],
                ["(defined(${MYPORPERTY}) && ${MYPORPERTY} === 1)", "rgb(128, 128, 128)"],
                ["true", "rgb(255, 255, 255)"],
            ]
        }
    });

In case this is to complex another suggestion would be to extent it to
var tileset = new Cesium3DTileset({url : 'data'});
tileset.style = new Cesium3DTileStyle({
	"color" : [
		{
			"required_properties" : [
				"MYPORPERTY", "MYPORPERTY2",
			],
			"conditions" : [
				["(${MYPORPERTY} === 0 && ${MYPORPERTY2} === 0)", "rgb(196, 196, 196)"],
				["(${MYPORPERTY} === 0 && ${MYPORPERTY2} === 1)", "rgb(164, 164, 164)"],
				["(${MYPORPERTY} === 1 && ${MYPORPERTY2} === 0)", "rgb(128, 128, 128)"],
				["(${MYPORPERTY} === 1 && ${MYPORPERTY2} === 1)", "rgb(92, 92, 92)"],
				["true", "rgb(255, 255, 255)"],
			],
		},
		{
			"required_properties" : [
				"MYPORPERTY"
			],
			"conditions" : [
				["(${MYPORPERTY} === 0)", "rgb(196, 196, 196)"],
				["(${MYPORPERTY} === 1)", "rgb(128, 128, 128)"],
				["true", "rgb(255, 255, 255)"],
			],
		},
		{
			"rgb(255, 255, 255)"
		}
	}
});

Yes this is a good point for the point cloud styling engine, which won't work if a style references a non-existent property. We should be smarter about detecting non-existent properties ahead of time.
Adding defined may not be needed since {MYPORPERTY} !== undefined is valid. It might be a good idea though.

CC #3241
Also added link from https://github.com/AnalyticalGraphicsInc/3d-tiles/issues/140 where it is suggested that undefined may be able to evaluate to 0 or false with the GLSL backend.

So what is the solution for this case?

Before applying how can I check with undefined?

authors: SunBlack VolodKu lilleyse pjcozzi

repo: AnalyticalGraphicsInc/cesium


text:
Optional result parameter to Color.fromHsl and Color.fromCssColorString

Added optional result parameter to Color.fromHsl and Color.fromCssColorString and added tests to check the result is modified.

Could you also update Color.fromRgba?  For an example of how to test these, see https://github.com/ggetz/cesium/blob/color-result-parameters/Specs/Core/Cartesian3Spec.js#L50-L55

Updated.

@lilleyse do you want us to wait until after the 1.19 release to merge this?  Doesn't matter to me, there is no rush here.

It's fine to merge this.

:+1:

authors: ggetz lilleyse pjcozzi