heroku addons --resource X gives an error: Unexpected flag: --resource

I believe this is just a documentation issue. The example given when you type heroku help addons says:
$ heroku help addons
Usage: heroku addons [{--all,--app APP_NAME,--resource ADDON_NAME}]

 list installed add-ons

 NOTE: --all is the default unless in an application repository directory, in
 which case --all is inferred.

 --all                  # list add-ons across all apps in account
 --app APP_NAME         # list add-ons associated with a given app
 --resource ADDON_NAME  # view details about add-on and all of its attachments

Examples:

 $ heroku addons --all
 $ heroku addons --app acme-inc-website
 $ heroku addons --resource @acme-inc-database

Additional commands, type "heroku help COMMAND" for more details:

  addons:_create                                  #
  addons:attach ADDON_NAME                        #  attach add-on resource to an app
  addons:create                                   #
  addons:destroy ADDON_NAME [ADDON_NAME ...]      #  destroy add-on resources
  addons:detach ATTACHMENT_NAME                   #  detach add-on resource from an app
  addons:docs ADDON_NAME                          #  open an add-on's documentation in your browser
  addons:downgrade ADDON_NAME ADDON_SERVICE:PLAN  #  downgrade an existing add-on resource to PLAN
  addons:info ADDON                               #  Show info about an add-on and its attachments.
  addons:open ADDON_NAME                          #  open an add-on's dashboard in your browser
  addons:plans SERVICE                            #  list all available plans for an add-on service
  addons:services                                 #  list all available add-on services
  addons:upgrade ADDON_NAME ADDON_SERVICE:PLAN    #  upgrade an existing add-on resource to PLAN

But using the --resource flag doesn't appear to work.

yeah it was a bug with help, can you update and try again?


[79, 67, 72] Home landing page

What Github issue does this PR relate to?
Changes proposed in this pull request:

Close #79
Close #67
Close #72

Because we're requesting the requestsData, menteesData, mentorshipsData and applicationsData objects asynchronously in pages/index.js, these objects are not defined when we execute the logic to decide the path. This means that the default path is always loaded. We could either simplify the logic to always load the default path, or refactor to wait for all of the requests? Something like the below could work:
import useSWR from "swr";
import { useRouter } from 'next/router'

const fetcher = url => fetch(url).then(response => response.json())

const multipleURLfetcher = (urls) => {

  const urlArray = Object.keys(urls);

  return Promise.all(urlArray.map(urlKey => fetcher(urlKey))).then((responses) => responses.reduce((returnObj, currentResponse, index) => {
    // get the response label using the array of URLs passed to Promise.all function
    // and the original urls object
    const responseLabel = urls[urlArray[index]]

    // assign the response to the r
    returnObj[responseLabel] = currentResponse
    return returnObj
  }, {}))
}

export default function Home({ mode }) {
  const router = useRouter();

  const { data, isValidating } = useSWR({
    "/api/requestsCount": "requestsData",
    "/api/menteesCount": "menteesData",
    "/api/profile": "profile",
    "/api/applicationsCount": "applicationsData",
    "/api/mentorshipsCount": "mentorshipsData"
  }, multipleURLfetcher)

  if (!isValidating) {
    const { requestsData, menteesData, profile, applicationsData, mentorshipsData } = data

    let homePath = '/profile';
    if (mode === "mentor") {
      const requestsCount = requestsData?.count || 0;
      const menteesCount = menteesData?.count || 0;

      if (profile && !profile?.mentor?.calendly) {
        // will go to the profile to let the mentor set their calendar link
        homePath = '/preferences';
      } else if (requestsCount) {
        homePath = '/requests';
      } else if (menteesCount) {
        homePath = '/mentees';
      }
    } if (mode === "mentee") {
      const applicationsCount = applicationsData?.count || 0;
      const mentorshipsCount = mentorshipsData?.count || 0;

      if (mentorshipsCount) {
        homePath = '/mentorships';
      } else if (applicationsCount) {
        homePath = '/applications';
      } else {
        homePath = '/mentors';
      }
    }

    router.push(homePath);
    return <></>;
  }

  return <>Loading...</>
}

WDYT?

agree, on the preview seems to work, even though it should not.
I created a followup ticket here #119
I will merge this and let's discuss later about it and see what's best!

thanks @raluka and @maranta1 for reviewing this! I will merge now.


Notifications popup in member menu isn't aligned correctly sometimes

https://www.boonex.com/forums/topic/Notifications-problem-2015-08-03.htm

It happens when a new notification received. On first click it doesn't appear in its place but if you click again, it will be in its place.


Unicode support: Bold Fractur not rendered

When rendering 𝕬^2 katex throws the error Font metrics not found for font: .

However 𝔄^2 renders fine

Note that MathJax renders both expressions fine

I'll need some help with this one.
Character 𝕬 is is bold Fraktur character, Unicode code point U+1D56C. KaTeX does have a glyph for this character, in KaTeX_Fraktur-Bold font. The trouble is in the KaTeX font metrics file. It includes metrics for Fraktur, but not bold Fraktur.
If someone else will update the KaTeX font metrics to address bold Fraktur, I can do the rest. My part is a simple matter of editing
https://github.com/KaTeX/KaTeX/blob/a624918e14f4b8e2f591df63e96d22d175f6028e/src/wide-character.js#L48
and another line in symbols.js.

update the KaTeX font metrics

How can I help? Do you mean to find the font out there and hand it to you? As this font is available in MathJax is there an easy way to retrieve it from there?

First, some background: KaTeX keeps a careful accounting of heights and vertical alignments as it generates math. It can do this in advance of any browser rendering because KaTeX has detailed metrics for every glyph in the KaTeX fonts. Or to be more accurate, nearly every glyph in the fonts. You've uncovered a gap where bold Fraktur has been omitted.
The KaTeX file fontMetricsData.js is created by a script at KaTeX/submodules/katex-fonts/buildMetrics.sh. I am not competent in bash, Python, or Perl, so I am not going to revise that script or its dependencies. Someone who has that competency needs to perform a revision so that it includes bold Fraktur when it generates font metrics.


[ANDROID] Allow using a custom RNCWebView in New Architecture

What does this PR do?
Adds a createViewInstance override to RNCWebViewManager in new architecture, to allow using a custom RNCWebView, in accordance with the official guide for Android Customization.
Usage
With this change, the official guide will still be relevant:
@ReactModule(name = CustomWebViewManager.REACT_CLASS)
public class CustomWebViewManager extends RNCWebViewManager {
  /* This name must match what we're referring to in JS */
  protected static final String REACT_CLASS = "RCTCustomWebView";

  protected static class CustomWebViewClient extends RNCWebViewClient { }

  protected static class CustomWebView extends RNCWebView {
    public CustomWebView(ThemedReactContext reactContext) {
      super(reactContext);
    }
  }

  // This is currently not possible in New Architecture
  @Override
  protected RNCWebView createViewInstance(ThemedReactContext reactContext) {
    return super.createViewInstance(reactContext, new CustomWebView(reactContext));
  }

  @Override
  public String getName() {
    return REACT_CLASS;
  }

  @Override
  protected void addEventEmitters(ThemedReactContext reactContext, RNCWebViewWrapper view) {
    view.getWebView().setWebViewClient(new CustomWebViewClient());
  }
}

⬆ Friendly bump :)


Download flags

URL flags to force various download strategies for mobile testing.

What do the flags do?

downloadWindowOpen uses window.open to try to generate a download
downloadProtocol provides custom protocols


Should we introduce keys of any type in map/record/dictionary in AskScript?

Following this comment, let's discuss whether we should allow arbitrary type of keys in AskScript associative types and whether we should extend the current type (map) or rather introduce a new type (record, dict or whatever other name).

I think yes, Map already allows that in JavaScript

Fine. How would we support creating non-string keys with {} syntax?
{ [ <expression> ]: <value> }?


How do I apply aspect to multiple TS modules?

All aspect.js usages examples I managed to find seem to only apply aspect in scope of single TS module: example. Is it for sake of simplicity or is it a technical restriction?
In my case, I wanted to apply an aspect to multiple classes, but I didn't manage to make it work without adding:
import {LoggingAspect} from "./logging.aspect";
LoggingAspect;

to every module. Here's my illustration:

My aspect: https://github.com/loki2302/angularjs-experiment/blob/master/angular2-experiment/src/logging.aspect.ts
My Angular module: https://github.com/loki2302/angularjs-experiment/blob/master/angular2-experiment/src/app.module.ts
A component I want to apply it to: https://github.com/loki2302/angularjs-experiment/blob/master/angular2-experiment/src/calculator.component.ts
A service I want to apply it to: https://github.com/loki2302/angularjs-experiment/blob/master/angular2-experiment/src/calculator.service.ts

How do I avoid these funny references? I would appreciate any hints.

You can do the following:
import './logging.aspect';

It is similar to importing Rx.js operators which produce some side-effect. The aspects do not have access to the ElementInjector, in order to get access to it you can use the Angular bindings for aspect.js. Notice that the code won't work with AoT because it is woven runtime, instead of compile time.

@mgechev thank you a lot!

Removing my imports and adding import './logging.aspect' into app.module.ts indeed did the trick.
And indeed DI doesn't seem to work with this approach. I unfortunately didn't manage to make things work with aspect.js-angular. After replacing aspect.js's @Wove() with aspect.js-angular's @Wove, it now says:

EXCEPTION: Uncaught (in promise): Error: Error in ./result class result_Host -
inline template:0:0 caused by: Class constructor CalculatorService cannot be
invoked without 'new'

Would you share a snippet which demonstrates your use case?

I've prepared a minimal example to demonstrate the issue: https://github.com/loki2302/aspectjs-angular-experiment - please feel free to:

git clone https://github.com/loki2302/aspectjs-angular-experiment.git
npm i
npm run-script run
Go to http://localhost:8080
Open JS console in dev tools
Click the "Increment" button and see how it says BEFORE, INSIDE, AFTER in console.
Then update https://github.com/loki2302/aspectjs-angular-experiment/blob/master/src/app.module.ts#L6 - replace aspect.js import with aspect.js-angular import.
Reload the page

In my case the page is empty and in console it shows the error I've mentioned above.

Thanks. I'll take a look and tell you once I do.

Opened a PR here.


Inceptionev/add assembly instructions

Adding electrical and mechanical assembly instructions and BOM updates for electrical components and improved gasket material

adding assembly instructions and moving file locations to release candidate folder.


uid is missing from the docs

Known existing prior art: https://youtu.be/p0wDUK0Z5Nw?t=454

Also https://11ty.rocks/posts/understanding-webc-features-and-concepts/

One note - when you document this, please explain the rules of the random string. For example, will it be safe to use as IDs for DOM elements. (If not, let me know and I'll file an issue for that. ;)


Chinese fonts cannot be displayed in typst

I try to define font file.  Place the downloaded ttf file in the folder.  But when I edit the typst file preview, it doesn't show up.

Did you follow this comment?: https://github.com/typst/typst/issues/416#issuecomment-1487995026

Did you follow this comment?: typst/typst#416 (comment)

Yes I have seen that.  But it doesn't seem to work

Hm, have you tried capitalizing the w or maybe wenkai.ttf? Also could you share the file with me so I can try?

嗯，您尝试过将 w 或 wenkai.ttf 大写吗？另外您可以与我分享该文件以便我尝试吗？
Okay, thank you。

wenkai.zip

Hm, oddly, it seems that the capability to use custom fonts is completely broken?

Hm, oddly, it seems that the capability to use custom fonts is completely broken?

I do not know why either.  I changed several fonts but still can't preview properly.


Rogue paragraph in migration guides

It seems one of the paragraph escaped its section and is roaming free in the vast steppes of white space. It is mildly amusing, though still probably needs to be shoved back.

They have been herded back to safety 🤠

They have been herded back to safety 🤠


Note_Off is displayed as Note_On

Hi,
How to identify the start time and duration of note played from mid file ?
as i went through the mido read me time in message refers to wait time from previous event. is this the start time of the note ? also i don't see a "note_off message".
Below is a midi file printed using mido. In this file, the key c4 is pressed and released 10 times.
Kindly help in understanding

start of each key press in seconds ?
time duration / end of each key press ?
time gap between two key press ( start of second key - end of first key)

MidiFile(type=1, ticks_per_beat=24, tracks=[
MidiTrack([
MetaMessage('set_tempo', tempo=500000, time=0),
MetaMessage('time_signature', numerator=4, denominator=4, clocks_per_click=24, notated_32nd_notes_per_beat=8, time=0),
MetaMessage('key_signature', key='C', time=0),
MetaMessage('end_of_track', time=0)]),
MidiTrack([
Message('program_change', channel=0, program=4, time=0),
Message('note_on', channel=0, note=60, velocity=46, time=54),
Message('note_on', channel=0, note=60, velocity=0, time=30),
Message('note_on', channel=0, note=60, velocity=40, time=30),
Message('note_on', channel=0, note=60, velocity=0, time=36),
Message('note_on', channel=0, note=60, velocity=33, time=36),
Message('note_on', channel=0, note=60, velocity=0, time=36),
Message('note_on', channel=0, note=60, velocity=38, time=36),
Message('note_on', channel=0, note=60, velocity=0, time=36),
Message('note_on', channel=0, note=60, velocity=34, time=36),
Message('note_on', channel=0, note=60, velocity=0, time=42),
Message('note_on', channel=0, note=60, velocity=40, time=36),
Message('note_on', channel=0, note=60, velocity=0, time=36),
Message('note_on', channel=0, note=60, velocity=45, time=36),
Message('note_on', channel=0, note=60, velocity=0, time=42),
Message('note_on', channel=0, note=60, velocity=48, time=48),
Message('note_on', channel=0, note=60, velocity=0, time=42),
Message('note_on', channel=0, note=60, velocity=51, time=36),
Message('note_on', channel=0, note=60, velocity=0, time=42),
Message('note_on', channel=0, note=60, velocity=28, time=24),
Message('note_on', channel=0, note=60, velocity=0, time=42),
MetaMessage('end_of_track', time=0)])

According to the MIDI 1.0 specification, page 73, a MIDI note-on event (9n) with a velocity of 0 is considered a note-off. In your example, every note_on event is immediately followed with another one with a velocity=0, functioning as the note-off event.
This means assuming an uninterrupted stream of note-on and note-off event, a space-conscious implementation may take advantage of the running status, which is likely why such an optimization was introduced in the standard.
I haven't looked at the mido code, but this seems to be a MIDI-related thing, not one of this project, which appears to be completely in-spec.


Use Postman Public Workspace for API docs and collections

Postman recently launced Public Workspaces, with loads of features. Binance can leverage it to keep track of the APIs and the docs, meanwhile general public can test out those collections by forking it in their personal workspace. Do take a look at it. Felt it will be useful for you guys.
Blog Post: https://blog.postman.com/introducing-postman-public-workspaces/
Sample Workspace:https://www.postman.com/postman/workspace/postman-public-workspace/overview

thank you for the suggestion.
Because the collection requires API key/secret, which is extreme important to our users, we don't want to host it or have any dependency on other services.  For now, all collections are write in plain json file and fully open sourced, so it's easy to review by checking the commit history. Also the json files can be easily imported into other similar tools.
We are happy with current solution and will not have any change at this moment.
Thanks again.

thank you for the suggestion.
Because the collection requires API key/secret, which is extreme important to our users, we don't want to host it or have any dependency on other services.  For now, all collections are write in plain json file and fully open sourced, so it's easy to review by checking the commit history. Also the json files can be easily imported into other similar tools.
We are happy with current solution and will not have any change at this moment.
Thanks again.


Fix fetchBaseQuery: Throw when invalid

I'm just going to leave this here. Error handling doesn't work anything like I'd expect it to. If I get a chance later, I'll write up what I think should happen -- if not, tomorrow. As of right now, the thrown error doesn't make it into the rejected payload, and due to how createAsyncThunk works, you can't catch it. This might be an idea, but not sure if you're going to merge it: https://github.com/reduxjs/redux-toolkit/pull/812

but I'd be curious as to if refetch should be able to be handled as a promise in a component instead of being void? Maybe this is offbase either way though - curious to hear thoughts.

Thing is: if a query for that serializedArgs is already running, that refetch would immediately return with a rejection. And syncing that up so it waits for that already-running query would require quite a rework of the middleware concept. So I'm putting that off for now.


Feature/n2 140 tabs advanced page

Uses Bootstrap library to give Gloss Advanced edit page clickable tabs.
The tabs are:
Edit - the familiar edit page with the Enable/Disable Edit button.
Public View - to house the view of the Gloss on the Signbank Dictionary site if it is published there.
Revision History - to house the Revision History of the gloss, including comments.
The Public View and Revision History tabs have their own Jira tickets which have details to help developers get started.
Each of those tabs breaks out to a new stub html file which has been created.
https://user-images.githubusercontent.com/82071930/176383723-e463195f-b32d-41fe-a449-faa6ed762bbf.mp4

https://user-images.githubusercontent.com/82071930/176383991-ecdc4ab4-2a13-4196-bbac-b337437e02fd.mp4


Revert "scan Adjust parallel scanners num  (#38430)"

This reverts commit 11b332fd90eadeff78d120db2b51abc6b7b44d35.
Proposed changes
Issue Number: close #xxx

run buildall


Publish Stage

What is the purpose of the change

Fixes including CL pools in router

ClickUp Task
ClickUp Task URL
Brief Changelog

Testing and Verifying

Documentation and Release Note

I think this contains additional commits since the last publish was squashed


Is there an easy way to disable the requirement for an uploaded resume?

I would like to disable the validation against requiring an uploaded resume prior to submit.
Reason being; I would like to use the career portal to capture quick contact information on a tablet during a recruitment event.

Hey, @tazplay—
It would be fairly easy to remove the validation logic for a resume in the modal.controller.js, but removing that poses a risk: our REST API needs some form of resume in order to process an application. So changing that logic could backfire if there was no LinkedIn application and no uploaded application.
I hope this helps you as you extend this app!


Prepare 10.0.0-beta07 release

Story: https://app.shortcut.com/smileid/story/xxx
Summary
Prepare 10.0.0-beta07 release
Known Issues
Any shortcomings in your work. This may include corner cases not correctly handled or issues related
to but not within the scope of your PR. Design compromises should be discussed here if they were not
already discussed above.
Test Instructions
Concise test instructions on how to verify that your feature works as intended. This should include
changes to the development environment (if applicable) and all commands needed to run your work.
Screenshot
If applicable (e.g. UI changes), add screenshots to help explain your work.

Merge after #26


Unnecessary diff on ods-start-builds job

The order of the fields is out of sync and it would be nice to not show the diff, even though it doesn't make a difference in the end.
Currently updating looks like this:
- # Source: ods-pipeline/charts/images/templates/job-start-builds.yaml
  apiVersion: batch/v1
  kind: Job
  metadata:
-   name: ods-start-builds
    annotations:
-     "helm.sh/hook": post-install,post-upgrade
-     "helm.sh/hook-weight": "1"
-     "helm.sh/hook-delete-policy": hook-succeeded,hook-failed
+     helm.sh/hook: post-install,post-upgrade
+     helm.sh/hook-delete-policy: hook-succeeded,hook-failed
+     helm.sh/hook-weight: "1"
+   name: ods-start-builds
+   namespace: foo-cd
  spec:
    template:
      spec:
-       serviceAccountName: pipeline
-       restartPolicy: Never
        containers:
-       - name: post-upgrade-job
-         image: 'quay.io/openshift/origin-cli:4.10'
-         command: ["/bin/sh","-c"]
-         args: ["set -e; oc get bc -l=app.kubernetes.io/name=ods-pipeline -o=name | xargs -I % sh -c 'oc start-build %'"]
+       - args:
+         - set -e; oc get bc -l=app.kubernetes.io/name=ods-pipeline -o=name | xargs
+           -I % sh -c 'oc start-build %'
+         command:
+         - /bin/sh
+         - -c
+         image: quay.io/openshift/origin-cli:4.10
+         name: post-upgrade-job
+       restartPolicy: Never
+       serviceAccountName: pipeline

https://github.com/databus23/helm-diff/issues/348

After discussion with @kuebler and @ManuelFeller, we agreed this should also be applied to the Helm execution in the ods-deploy-helm task.


testing in hw

sometimes device go to state when no transactions in IIC bus, probably this problem in iic_bridge


⚠ Bofrost.es has degraded performance

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

HTTP code: 200
Response time: 3667 ms

Resolved: Bofrost.es performance has improved in 0b4b419.


CB-10015: Fixed the browse online link for the issues mailing list

@dblotsky please review

LGTM.


Runtime Config - Use Waiter instead of While

Per Victor - I still suggest you switch to waiter instead of computing nodecount yourself. Then you can rely on DM doing the polling in a sustained manner.
https://cloud.google.com/deployment-manager/runtime-configurator/creating-a-waiter

I simplied the runtime config, so this isn't really relevant anymore.  We have a better async approach instead.


Add support for line breaks (line continuations)?

C-style languages use the ; to say that this is where a statement ends, because in C-style, pretty much all white-space is arbitrary and optional - it's just a good convention.
It sort of looks like rockstar is going down the Python route where one line = one statement, however even python gives you the option to break up long lines using the  \ thingy.
My proposal is that to be a bit like a piece of prose, rockstar could use  - (whitespace then hyphen) to break a line. Alternatively (and god forbid) if you break up an actual word, maybe a - (just a hyphen) could be used to line split, because this is how its done in English-style languages.
Take it to the top.

Maybe it should be the semi-colon?  A semi-colon at the end of a line could signify that the line is continued on the next line.  It's a bit more "prose" like.

My concern with semicolon is that it would have the exact opposite meaning that it has in most industry languages (i.e. confusing readability), and also that in prose you read a; hyphen as a line continuation - but if you just drop semicolons around you end up with; weird pauses.

I agree with @callumfrance, I think we should stay away from the semi colon. I would be okay with the hyphen idea.
Would it be possible to implement something that would implicitly continue a line? Or would that be too hard (too much ambiguity).

I think it would be too hard for a compiler to be able to tell. It would be a bit like reading a paragraph with no full stops.

Fair enough, my vote remains for hyphen.

Combining with #77- maybe use 'Baby', 'Yeah', 'Oooh, and/or 'Whoa' as the line continuation marker at the beginning of a line.
I'm torn on what to do in a poetic declaration. On one hand I don't want to take words away, but on the other, you could do something like this which would be cool:
My dreams were ice.
Yeah, A life unfulfilled;
Baby, wakin' everybody up,
Oooh, taking booze and pills


fix: check for workspace folder capability

Fix logic for checking initializeParams.capabilities.workspace.workspaceFolders to be true before requesting workspace capabilities. Noticed this when investigating #356, althought that behaviour won't change since neovim's client sends true anyways.

Codecov Report

Merging #375 (72d874b) into development (b06993a) will decrease coverage by 0.05%.
The diff coverage is n/a.

:exclamation: Current head 72d874b differs from pull request most recent head 56b3434. Consider uploading reports for the commit 56b3434 to get more accurate results

@@               Coverage Diff               @@
##           development     #375      +/-   ##
===============================================
- Coverage        57.08%   57.03%   -0.05%
===============================================
  Files              176      176
  Lines             4364     4364
  Branches           711      711
===============================================
- Hits              2491     2489       -2
- Misses            1640     1641       +1
- Partials           233      234       +1

Impacted Files
Coverage Δ

src/utils/index.ts
80.00% <0.00%> (-6.67%)
:arrow_down:

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


Enabling the toggle button and it is showing required message.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
master
Issue Description
Enabling the toggle button and it is showing the required message. Getting the same issue in the configuration-> sales shipping/payment methods tabs.
Preconditions

Admin should be logged in.

Steps to reproduce

Go to 'Admin panel'
Click on 'Edit content/shipping/payment method' inside the Configuration
Enable the toggle button
See the error

Expected Result
The required message should not be shown.
Actual Result
it shows the required message. Here
Screenshots
No response
Additional context
No response

Now, this issue is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.


⚠ GitLab Server has degraded performance

In fa612b6, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 9392 ms

Resolved: GitLab Server performance has improved in 036ad46.


Fixed typo (cange)

Docs Build status updates of commit 5f1e8e3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/core/installing-certificates-for-the-wcf-adapters.md
:white_check_mark:Succeeded
View

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


Not able to add default value in schema once the schema is saved.

Create a schema with some fields E.g.

{
 "type": "record",
 "name": "test",
 "namespace": "com.hortonworks.registries",
 "fields": [
  {
   "name": "business_id",
   "type": "string"
  }
 ]
}

Save

Click edit and now change the definition of field as

  {
   "name": "business_id",
   "type": "string",
    "default": "x"
  }

Enter some description
Save

UI throws a message saying "Schema version already present" and does not save the changes.

Verified from the UI, on making POST request, backend returns back the original(previously saved) schema's ID and is not creating new and so UI throws a warning message.
@satishd can you look at it, please?

Currently avro schema normalization does not take care of default attributes. I started a discussion in avro user/dev lists explaining the issue.

It seems there is a bug AVRO-2002 already raised but given why it behaves so.

Doug Cutting added a comment - 16/Feb/17 17:55
I believe you have misunderstood the semantics of fingerprints. Identical fingerprints mean that one schema can read output of the other without schema resolution, not that both can read a third using schema resolution.
Schema resolution permits interoperability (in some cases) between a pair of schemas whose fingerprints do not match. The SchemaCompatiblity class can determine whether a pair of schemas can, through resolution, interoperate.

I will address this issue extending avro schema normalization.


Scheduled notification events

I think we should add an event dispatched before and after a notification is sent.
It would allow the application to do some checks before the notification is sent (ie, ensure that the user is still active, etc) and after (record that x email was sent)

Could we handle this with just having a method on the notification class like shouldStillSend() to check to see if sending is still required? You can already log that a notification was sent in the toArray() method of the notification class.
I'm going to create a PR for the should still send check, and we can discuss events down the road if there's a more concrete example.

I was actually thinking of doing it that way, but didn't have a chance to get it implemented yet :)
Thanks for doing the PR, will check it out now :)
I think it's probably still worth firing an event on sent (at least)

Is this implemented?

@LeonAlvarez
Yep:
https://github.com/thomasjohnkane/snooze/blob/master/src/Models/ScheduledNotification.php#L77


VOICE-->CAR for PQ Discover Media SW0480 converted USA->EU with HMI ZR from MQB

Make sure you've ran one of the remap-functions BEFORE you open up a new issue. This is mandatory for the files you need for this issue
Describe your desired behaviour / problem:
What button do you want to remap and what new function should be available?
PQ Discover Media SW0480
configurationmanager.zip
converted USA->EU with HMI ZR from MQB
VOICE-->CAR
Attach a picture of your screen, including the buttons beside it (IDs must be readable / shown!):
Drag and drop a picture here and wait for the upload to be finished!

Attach the configurationmanager.res file out of the /backup/buttons folder:
Drag and drop the mentioned file here and wait for the upload to be finished!

Done in https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter minuaru for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.minuaru
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E254] Version "2.0.0-beta" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.

WARNINGS:

[ ] :eyes: [W168] "common.keywords" should not contain "iobroker, adapter, smart home" io-package.json
[ ] :eyes: [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
[ ] :eyes: [W252] Version of package.json (2.0.0-beta) doesn't match latest version on NPM (1.1.0)

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
or
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Sat, 26 Oct 2024 04:13:40 GMT based on commit 1d5e455f9889387f23394a9c2752d60d60a1bca1
ioBroker.repochecker 3.1.3

@iobroker-bot recheck

@ioBroker-Bot recreate


tools/osbuild-depsolve-dnf: enable loading of filelists

This is required when using newer versions of libdnf with old repositories or packages that specify dependencies on files.  For example, depsolving against RHEL 9.3 repos on Fedora 40 fails to resolve platform-python with the message
nothing provides /usr/libexec/platform-python needed by platform-python-...

The same option is already enabled in the dnf5 solver.
Further reading:

https://libdnf.readthedocs.io/en/stable/tutorial-py/#case-for-loading-the-filelists
https://github.com/rpm-software-management/dnf/releases/tag/4.19.0
https://dnf.readthedocs.io/en/stable/user_faq.html#starting-with-fedora-40-i-noticed-repository-metadata-is-synchronized-much-faster-what-happened

Here's a small depsolve request that demonstrates the issue:
{
  "command": "depsolve",
  "arch": "x86_64",
  "module_platform_id": "platform:el9",
  "releasever": "9",
  "cachedir": "/tmp/rpmmd.cache",
  "arguments": {
    "repos": [
      {
        "id": "baseos",
        "name": "baseos",
        "baseurl": "https://rpmrepo.osbuild.org/v2/mirror/rhvpn/el9/el9-x86_64-baseos-n9.3-20230808",
        "check_gpg": false
      },
      {
        "id": "appstream",
        "name": "appstream",
        "baseurl": "https://rpmrepo.osbuild.org/v2/mirror/rhvpn/el9/el9-x86_64-appstream-n9.3-20230808",
        "check_gpg": false
      }
    ],
    "transactions": [
      {
        "package-specs": [
          "insights-client"
        ]
      }
    ]
  }
}

$ rpm -qa "*dnf*"
dnf-data-4.19.2-1.fc40.noarch
libdnf-0.73.1-1.fc40.x86_64
python3-libdnf-0.73.1-1.fc40.x86_64
python3-dnf-4.19.2-1.fc40.noarch
dnf-4.19.2-1.fc40.noarch

$ ./osbuild-depsolve-dnf < ./depsolve.json
error depsolve
DepsolveError: There was a problem depsolving insights-client:
 Problem: conflicting requests
  - nothing provides /usr/libexec/platform-python needed by insights-client-3.2.0-1.el9.noarch from appstream
{"kind": "DepsolveError", "reason": "There was a problem depsolving insights-client: \n Problem: conflicting requests\n  - nothing provides /usr/libexec/platform-python needed by insights-client-3.2.0-1.el9.noarch from appstream"}

Make sure the cache directory is empty before testing.

Maybe this would be better as an option on the depsolve request so that we can get the speed and efficiency of depsolving without downloading filelists when we know we don't need them and still be able to depsolve older distro versions when we need to.

I think that's the best option, maybe even a generic option to control what metadata is needed, set by the distro definition. I wouldn't want to unnecessarily download them when they aren't needed -- I don't actually remember why I set it in the dnf5 version, it was likely just a side effect of trying to get things working with the current repos.

Converted to draft to signal this is a WIP.  I'll have to come back to this next week.

Made it an option for both dnf and dnf5.  This is a change in the default behaviour for the dnf5 depsolver, but I think that's okay given we don't use it in prod yet.
Discussions on the name of the option are welcome.
Should we make it a list of strings that the caller can enable instead?
{
  "command": "depsolve",
  "arch": "...",
  "module_platform_id": "...",
  "cachedir": "...",
  "optional-metadata": ["comps", "filelists"],
  "arguments": {
    "repos": [ ... ],
    "transactions": [ ... ]
  }
}

I like the example above, optional-metadata seems fine, or extra-metadata maybe? Either one does a good job describing that it's adding, not overriding anything.

I went with optional-metadata to match the dnf option name and moved it to the arguments part of the request.
{
  "command": "depsolve",
  "arch": "...",
  "module_platform_id": "...",
  "cachedir": "...",
  "arguments": {
    "repos": [ ... ],
    "optional-metadata": ["comps", "filelists"],
    "transactions": [ ... ]
  }
}

Moving it to the arguments makes more sense since it is an option that is only relevant for the depsolve command.

Looks good. Schutzbot not happy though, not really sure why.

Happy now.

This looks nice! How much extra work would it be if the existing test_depsolve.py be extended to include the "optional-metadata" in the files and the test?

Not sure.  I think it might be as simple as enabling the option (or not) and checking if the local cache includes any files called *filelists* (or not) after the depsolve.
Let me poke at it a bit and see.

I added a test, but there's one small issue.  It doesn't do any check for libdnf version.  If this test runs using an older libdnf, it will fail.

I added a test but there's a small issue.  The test doesn't check for the version of dnf, so if it's run with a version older than 4.19.0, it will fail.  It's also tricky to check which version we're testing against because in out GitHub tests we use tox, which sets up venvs, so if we import dnf to check its version, we'll be checking the version in the venv, but the test is actually run against the system dnf version because we shell out to osbuild-depsolve-dnf, which runs in the system-wide env.

I added a test but there's a small issue. The test doesn't check for the version of dnf, so if it's run with a version older than 4.19.0, it will fail. It's also tricky to check which version we're testing against because in out GitHub tests we use tox, which sets up venvs, so if we import dnf to check its version, we'll be checking the version in the venv, but the test is actually run against the system dnf version because we shell out to osbuild-depsolve-dnf, which runs in the system-wide env.

Now that I think about it, this might be an issue with release testing in EL9...


Extra jmh options: testonly, runtime_deps

Description

Adding 2 options to JMH rules:

testonly to allow marking JMH as testonly and consuming testonly dependencies, which allows re-using various test-kits and test helpers.
runtime_deps, which might (and is in our case) required for benchmark dependencies

Both are optional, so should be fully backwards-compatible.

Motivation

We have many test-kits and test helpers marked with testonly, because we're using them for testing mainly and testonly protects us from getting them into production. They are very useful for benchmarks as well, which is why we need this flag.

I don't have permissions to merge the PR - is there anything else needed from me, or should I just wait?

We need @simuons approval


Installation guide for Helix

There is a space between the list items, because the <details>-Tag has a bottom margin of 16px in the Github CSS. I tried overriding it with style="margin-bottom: 0", but Github is sanitizing that information.

Any idea?

There is a space between the list items

i think you might have to put a space between the closing backticks and the closing html tag


invokeMethod for External Calls

Expected Behavior
HTTPEndpoint in dapr for making external call needs to support application/xml content type.
Actual Behavior
As of now we get following exception
"msg":"Inside handleException - Dapr exception encountered - "
"exception":"io.dapr.exceptions.DaprException: UNKNOWN: HTTP status code: 415
This is suported in invokeBinding so need to have support in HTTPEndpoint as well.

Today the recommended approach is to use a standard httpClient instead of DaprClient instance. There are no content type restrictions for http client and the use of invokeClient is deprecated.


Add capability to check if it's currently snowing at player's position

origins:in_rain exists, however it returns false if the player is in snow. (1.19.2, Origins v1.7.1)

This has now been added in Origins 1.11.x


Add documentation for CREATE USER gonymizer for testing and mapping

Add to instructions to create user for Postgresql for the application.

We need
ALTER USER gonymizer WITH SUPERUSER;

since we need to instantiate the UUID plugin.

Going to skip this. Right now the tests run as the local user running the test. Keep it this way for now.


Decide what datasets to include in ACME v1.0, and what parameters to use for the degs.

Current thoughts are:
piano-midi is a must.
PPD should go in as well, but decision on monophonic vs polyphonic.
Maestro would be nice, but probably best to leave it for future work.

Using all 3 datasets is sensible, and I think default settings is fine initially.
I've added into the paper that we intend to investigate different settings in future work. It's very possible that different settings (like align_onset, etc) might make the tasks more difficult, but they seem to be difficult enough already...
We should probably set min_pitch and max_pitch to 21, 108 to match the pianoroll defaults, but nothing else. And I'd suggest just using those values as deg defaults anyways, for simplicity in writing the paper.


AI Prompt and API Design

Write an OpenAI prompt that accepts the text from a job description and assesses if it meets our conditions.

1-3 years
probably other things as well (TBD)

wrong repo


Highlight color on current active buffer?

Hey,
first of all: thanks for the work you put into this plugin!
I wanted to know, is it possible to change the color of the currently active buffer?
 LightlineModified()
  if &filetype == "help"
    return ""
  elseif &modified
    return "+"
  elseif &modifiable
    return ""
  else
    return ""
  endif
endfunction

function! LightlineReadonly()
  if &filetype == "help"
    return ""
  elseif &readonly
    return "\ue0a2"
  else
    return ""
  endif
endfunction

function! LightlineFugitive()
  if exists("*fugitive#head")
    let branch = fugitive#head()
    return branch !=# "" ? "\ue0a0 ".branch : ""
  endif
  return ''
endfunction

function! LightlineFilename()
  return ('' != LightlineReadonly() ? LightlineReadonly() . ' ' : '') .
       \ ('' != expand('%:t') ? expand('%:t') : '[No Name]') .
       \ ('' != LightlineModified() ? ' ' . LightlineModified() : '')
endfunction
" }}}

"Lightline-Buffer settings
set showtabline=2   " always show tabline
" remap arrow keys
nnoremap <Left> :bprev<CR>
nnoremap <Right> :bnext<CR>

" lightline-buffer settings
let g:lightline_buffer_logo = ' '
let g:lightline_buffer_readonly_icon = ''
let g:lightline_buffer_modified_icon = '✭'
let g:lightline_buffer_git_icon = ' '
let g:lightline_buffer_ellipsis_icon = '..'
let g:lightline_buffer_expand_left_icon = '◀ '
let g:lightline_buffer_expand_right_icon = ' ▶'
let g:lightline_buffer_active_buffer_left_icon = ''
let g:lightline_buffer_active_buffer_right_icon = ''
let g:lightline_buffer_separator_icon = ' '

let g:lightline_buffer_show_bufnr = 1
let g:lightline_buffer_rotate = 0
let g:lightline_buffer_fname_mod = ':t'
let g:lightline_buffer_excludes = ['vimfiler']

let g:lightline_buffer_maxflen = 30
let g:lightline_buffer_maxfextlen = 3
let g:lightline_buffer_minflen = 16
let g:lightline_buffer_minfextlen = 3
let g:lightline_buffer_reservelen = 20

What would I have to add to the vimrc to enable colors?

Hi,
The easiest way is modifying the color theme file.
For example, if you are using the 'wombat' color theme, you can modify ~/.config/nvim/bundle/repos/github.com/itchyny/lightline.vim/autoload/lightline/colorscheme/wombat.vim and change the line let s:p.tabline.tabsel = [ [ s:base3, s:base03 ] ].
The way I am more recommended is writing your own customized color theme as a lightline plugin. You can clone my lightline-solarized as a staring point and modify it. Then modify ~/.config/nvim/bundle/repos/github.com/taohex/lightline-solarized/autoload/lightline/colorscheme/lightline_solarized_dark.vim.
More comments are welcome!
Thank you!

Hey,
thanks for your response.
I tried changing the tabline.tabsel-line in the colorscheme but it had no effect.
Just to make sure I was in the right file I tried changing different values, for example tabline.left/midde/right, and I could observe visual changes in the colorscheme. But for some reason the currently active buffer still looks the same.
By the way I also tried this your lightline-solarized theme and it didn't work either.
Maybe there is an option that needs to be activated to enable this feature of styling the active buffer? But I'm just shooting in the dark here to be honest... ;)

OK, I will look into this later. Thank you!

Hi,
I had the same problem, the tabline does not highlight the current buffer
Thanks,
A

Hi @pwntester ,
Which of the following do you mean?

You want to modify the color in the color scheme.
All buffers have the same color, so you can't determine which is the current buffer.
Thanks!

Hi,
The second one, all buffers have the same color.

Thanks,
A

Which color scheme are you using?

I use OSX with iTerm2 and Solarized dark theme. For vim, I use GertjanReynaert/cobalt2-vim-theme. I dont have a color scheme set up for lightline.
I just tried using Solarized for everything: iterm2, vim and lightline and got the same issue, active buffer is not highlighted

@taohex As I said in my comment earlier, I also tried your suggestion with your very own "lightline-solarized" theme that you mentioned earlier and it didn't work.

I'm also facing that issue, regardless of the vim/lightline/terminal color scheme I use, all I see is two "|" surrounding the active buffer name.

great plugin btw!

I checked the code and saw that you are basically creating the before, current and after strings and concatenating them in the same lightline subcomponent, which should always be rendered with the same syntax highlight.
I ended up writing a simple component function that uses the lightline tab components to show the buffer line reusing the lightline components and styles. You may want to use this approach for your plugin since my function is quite simple but it works fine and easy. The function is described here

Hi all,
Finally I figure out the problem. I missed the below line in README.
    \ 'component_type': {
        \ 'buffercurrent': 'tabsel',
        \ },

Please add it, and I have updated the README. Thank you very much for your feedback!

Great, that fixed it for me :) Thanks!

It works!


Handle Figma "Auto" line-height value

fix(tokens): handle Figma "Auto" line-height value

makeLineHeightTokens will return the CSS keyword: "normal" in such case.
makeLineHeightTokens no longer throw errors when token cannot be calculated.
It will be ignored instead (while the others will still be emited)

I could not get precise specifications for this non-CSS value, I sent a message to Figma on their contact form, will follow-up on that if they answer.
Meanwhile, "Auto" will result in the CSS "normal" keyword, hope that is okay.
From a design-system perspective, it is probably better if the value is set, to avoid browser-specific differences, but the tokens will always be there with the explained fallback.
Fix #82

Let me know what you think about the try/catch approach as well?
(I can generalize this behavior to other tokens if you want to follow the same pattern)

Let me know what you think about the try/catch approach as well?
(I can generalize this behavior to other tokens if you want to follow the same pattern)


[docs] Info on Chart.yaml indents some properties wrongly

I may be confused about YAML syntax, but https://helm.sh/docs/topics/charts/#the-chart-yaml-file , I see the following:

I haven't tried to find anything like a schema, but I have a feeling that the only properties in each dependency are "name", "version", and "repository".  At least that's what the detailed docs mention.  The properties that come after that at the same indent level, like "condition", "tags", "enabled", "import-values", and "alias" most likely apply to the entire chart, not a specific dependency, so they should be de-indented one level.

It appears that "alias" is allowed both in a dependency and the main chart, but I have a feeling the "alias" in this picture was supposed to refer to the main chart, not the dependency.

And now I see that "tags", "condition", and "import-values" can also apply to a dependency.  It appears that only "enabled" is definitely wrong indented here, but reading the comments on those other properties in this image makes me think those other properties were intended to refer to the main chart, not the dependency.

The properties like condition, tags, enabled, etc are per dependency. This is the same for both Helm 2 and 3. For example, the wordpress chart in the stable charts repository has:
dependencies:
- name: mariadb
  version: 7.x.x
  repository: https://kubernetes-charts.storage.googleapis.com/
  condition: mariadb.enabled
  tags:
    - wordpress-database

In the values.yaml file there is a section that has:
mariadb:
  ## Whether to deploy a mariadb server to satisfy the applications database requirements. To use an external database set this to false and configure the externalDatabase parameters
  enabled: true

When mariadb.enabled is set to false the dependency is not installed.

I don't think there is any Helm bug here, though there is possibly a documentation error that should be filed in the docs project: https://github.com/helm/helm-www/issues


Another Proposal to fix blast aoe preview.

Another approach to fixing the aoe preview not matching the hit calculation.
This PR just changes the rendering preview and does not touch any other code.

This commit leaves the hit calculation as is and uses actor.distance() to determine the hit.
The shape does match the preview, but the hit calculation does not take into account tile transparency.
Basically it would just be the fov calculation without any of the additional masking for the view followed by a check if the entity is in the aoe_tile array.

This is at least more accurate than the previous version.  I can try figure out the rest when I get to this part in my refactoring.

If you still want to add to this then convert it to a draft.  Otherwise I'll merge it sometime after the tests pass.

I am fine with it as-is.  It's close enough for now and is better than before.  Adding the FOV code to the hit detection would really only allow entities the ability to have cover behind walls or around corners.  Since the tutorial does not have irregular shaped rooms or barriers inside of rooms, it's an edge case.
If you want to refine it you can address it whenever you get to part 9.


bencrypt.py file ready

The New File bencrypt is ready with strong encryption methods
dependencies

enrocrypt

Ok

Done With Case


Do not include null value for non required fields

When a not required field is not set, a null value for that field is included in the request. In order to make the request smaller, we can skip that by adding an annotation in the generated code

Event though i partially agree with @fjtirado imho i think this feature should be configurable and we shouldnt force the users to skip serialization of null fields since there is a standard way how to do it in quarkus:
https://quarkus.io/guides/all-config#quarkus-jackson_quarkus-jackson-serialization-inclusion
@hbelmiro could you please share your thoughts on this

@ricardozanini maybe you have a time to think about my comment hm?

Leaving my opinion here, I think it should be configurable

This affects the payload that is sent by the generated code to the REST server.
Since we are using POJOs to generate the request and most optional fields are never set by users, the request was essentially a lot of unneeded properties set to null, which kills the purpose of the optional flag.
So not sending them seems the right thing to do
Is there any use case where the payload should include an optional field set to null? I can only think of some servers where setting a value to null has semantic value (for example deleting an array when the request include a null for that array property). For those ones, I think that, rather than configuration, we should look at if the field is described as nullable in the OPen file. See nullable section here. If it is nullable, then null should not be skipped for that property.

@fjtirado I agree that optional fields should not be forced to null. Otherwise, it smells anti-pattern.
On the other hand, I remember someone in this community raising a concern that a server won't accept a request if an optional field wasn't sent as part of the request (of course, again, a case where the server was badly implemented).
That being said, what should be optional, as in a configuration option, is the ability to force set to null non-required fields to address these edge cases. So this PR can be as is, but we should add a property to revert to the original behavior.

For those cases, they added nullable to the open api spec. I think we need another PR to handle nullable. And if the openapi spec file does not match the server behaviour (does not have the nullable and the server behave as it was there), then, as it is probably done in other cases, the file should be edited locally to adjust it to the server behaviour (which is kind of equivalent to add a local property to enforce sending optional fields set to null, with the different that the null will be sent only for the nullable fields)

Nevertheless, a new PR can address this case. @michalsomora have you faced such problems on your end since you first raised this concern?

Yes, I encountered the issue on the client side (post-backend upgrade), where it did not handle missing null fields correctly. This issue definitely needs to be resolved on the client side. However, I wanted to discuss whether it is necessary to enforce non-null serialization at the DTO level when users can configure it globally using:
quarkus.jackson.serialization-inclusion=non-null
In my opinion, the debate about why someone might need to serialize nulls is not relevant. Why does the library prevent configuring serialization as needed? Should we introduce a new option to change this? I would argue against it, as we already have a global configuration that perfectly addresses this requirement.

@michalsomora  quarkus.jackson.serialization-inclusion will affect all json payloads, however the idea was to remove nulls only for optional fields. Thats why annotations are included for individual properties, becuase not all properties follows the same policy. Null for mandatory fields are still included as part of the payload.
As explained before, I think we need a new issue to handle nullable. If nullable is present for an optional field, optional field set to null should be sent.


Align performance test config with regular e2e

Resolves #2957
What is being addressed
Performance E2E tests had environment settings used exclusivly by them.
How is this addressed

Remove performance tests environment variables and align with the TEST* ones used by other E2Es.

/test-force-approve
performance tests aren't checked


Angular, Meteor - Wont import Mongo Database

Just updated Meteor with:

meteor update

and it throws me a server error.
'meteor list' results:
 meteor list
accounts-base            1.2.2  A user account system
accounts-password        1.1.4  Password support for accounts
barbatus:ng2-pagination  0.1.0  Angular2 Pagination Components
es5-shim                 4.1.14  Shims and polyfills to improve ECMAScript 5 ...
jquery                   1.11.4  Manipulate the DOM using CSS selectors
less                     2.5.1  Leaner CSS language
meteor-base              1.0.1  Packages that every Meteor app needs
meteorhacks:npm          1.5.0  Use npm modules with your Meteor App
mobile-experience        1.0.1  Packages for a great mobile user experience
mongo                    1.1.3  Adaptor for using MongoDB and Minimongo over DDP
npm-container            1.2.0+ Contains all your npm dependencies
reactive-var             1.0.6  Reactive variable
session                  1.1.1  Session variable
standard-minifiers       1.0.2  Standard minifiers used with Meteor apps by d...
tmeasday:publish-counts  0.7.3  Publish the count of a cursor, in real time
tracker                  1.0.9  Dependency tracker to allow reactive callbacks
twbs:bootstrap           3.3.6  The most popular front-end framework for deve...
urigo:angular2-meteor    0.3.7  Angular2 and Meteor integration

+ These packages are built locally from source.

Here's my code:
/// <reference path = '../typings/angular2-meteor.d.ts' />
/// <reference path = '../resources/database.ts' />
/// <reference path = '../typings/meteor-accounts.d.ts' />

import {IPs} from 'resources/database'

console.log(IPs)

the code
console.log(IPs)

Is giving me as 'undefined'  and throws a server error
TypeError: Cannot call method 'find' of undefined

when i actually define it in '../resources/database.ts' as it follows:
/// <reference path = "../typings/angular2-meteor.d.ts" />

export var IPs = new Mongo.Collection("ips")

You seem to be using /// <reference  sugar still. Please read on the usage of tsconfig.json [here] (http://www.angular-meteor.com/tutorials/socially/angular2/folder-structure) and check if it works after.
If  it doesn't then I'll need a repo to investigate. Absolute paths like collections/parties work well in the demo app (check out examples/parties), I see no reason why it shouldn't work in your case.

You're right. I'm still using old-school reference path. Thanks!


Upgrade to embedded-hal 1.0.0-rc.1

Thanks for your crate!
It look like the embedded-hal 1.0 release is scheduled for 12/28/2023 and the rc.1 release should have the same API unless something goes off the rails.
Is there any work that needs to be done to upgrade?

Hi @clintfred
Thanks for letting me know about the future release of v1.0. Looks like it's really happening soon 😄
I think there will be some small changes needed to pca9535 lib, but it should not be too drastic as far as I saw. We removed the IO-Pin trait in #1 which I'd like to get back in. But looks like this is not in 1.0 so it can be skipped for now.
I might need to make a few adjustments to the hardware testing, but rppal seems to support v1.0 rc2 already, so I only might need to patch shared-bus to v1.0 rc2 for now.
In case you need pca9535 to support v1.0 rc2 I can create a release candidate for you, otherwise I plan to release v2.0.0 of pca9535 once v1.0 of embedded-hal is released.

Thank you for your response. I can wait for the 2.0 release; no worries.
FYI: I am using your crate with linux-embedded-hal.
If you need any support or feedback, I will try to help, just lmk.

Ok, so I will wait for the official release. The update is now merged into master.
I'm always happy for any feedback regarding the library usage. In case there's something that is hard to achieve or does not work.
It's always nice to have people using the library in combination with other hardware and providing feedback in case anything does not work correctly. I myself only use it in combination with rppal on a Raspberry Pi 4 which is also used for the hardware based tests in this lib.


Fixed broken link to Content Types

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Wrong assertion in EqualsHashCodeContractAssert

Hi,
I read the class EqualsHashCodeContractAssert, and since equals returns a boolean, i think
public static void assertIsNotEqualToNull(Object obj) {
    assertThat(obj.equals(null)).isNull();
}

should be
public static void assertIsNotEqualToNull(Object obj) {
    assertThat(obj.equals(null)).isFalse();
}

If you didn't spot the bug, i guess this is dead code.
Regards

By the way, did you consider expose those assertions in the public API to check the equals contract?

Good catch! The code is dead code indeed, it was written in Fest Assert which AssertJ is a fork of.
I think it is better to use https://jqno.nl/equalsverifier/ to test equals and hashcode, no plan in the roadmap to support this.

Ok, thanks for the pointer.


added no. of items in system on view stocked.

Nice! Great idea.
I assume you tested this out? My MC world has probably succumbed to rot by now, so not able to do so myself.

Yes, this works.


Documentation for all supported commands

Documentation for all commands supported by the ci-bot for easy usability by the user.

@edisonxiang , @pavan187 @swx457056 , Can we quickly come up with a document of all commands supported by ci-bot. Very glad that the bot is working on kubeedge repo now. Thanks All.
cc @m1093782566

Yeah, sushantha just talked to me that CNI-Genie want to use ci-bot as well.

@swx457056 , @pavan187 , Any update on this ? Need a document


It showing at all

 Issue by usw21
Friday Mar 03, 2017 at 05:48 GMT
Originally opened as https://github.com/Sticktron/LockGlyphX/issues/44

I tried uninstalling all tweaks that could have interfered with lock screen yet the glyph still would not appear. It simply doesn't work?!?

@usw21 Please provide a tweak list and iOS version


Tests should run without network access and be consistent in PyPi

Is your feature request related to a problem? Please describe.
I package various Azure SDK components in Fedora Linux for use with azure-cli, and one of my frustrations is around running tests. During RPM builds, no network access is allowed. However, many of the SDK tests require network access or they have a VCR cassette that is outdated. This prevents me from running tests.
I've reviewed how Arch and Debian packagers are handling this challenge and many of them are disabling many tests or simply not testing at all. To make matters worse, some of the PyPi packages for certain SDK components contain tests, and some do not. Some of them contain the VCR recordings for tests, and others do not. This requires me to get the source code from the git repository so I can be sure I have all of the tests and recordings. However, I must download the entire repository (> 100MB) just to get the 1-2MB of code that I really care about.
Some tests, such as the ones for azure-mgmt-network, require me to run docker during tests, which includes downloading a remote container.
Describe the solution you'd like
I'd like to see:

SDK tests run without network dependencies
Tests and VCR recordings either included or excluded consistently in PyPi packages

Describe alternatives you've considered
Sometimes I have to disable some or all of the tests for a particular part of the SDK. For some, such as azure-mgmt-network, I must disable all of the tests to build the package successfully. This creates issues later when I get bugs from users or when I package azure-cli and its tests break when importing command modules.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.12790225,Network - Virtual Network:0.11832973,Search:0.029103864'

Hi @major, thank you for your feedback.
According to your issue description:
If you want SDK tests run without network dependencies, you can set the environment variable AZURE_TEST_RUN_LIVE to "false". See link for detailed explanation.
Currently SDK tests are run in docker

If you want SDK tests run without network dependencies, you can set the environment variable AZURE_TEST_RUN_LIVE to "false". See link for detailed explanation.

I'm using that environment variable now in my package builds, but the challenge there is that packages are published inconsistently to PyPi:

Some packages have no tests
Some packages have tests, but VCR recordings are missing
Some packages have both tests and VCR recordings, but they still try to make connections across the internet

My expectation would be that:

Every package has tests/recordings published to PyPi consistently
No package requires network connectivity to run tests

Currently SDK tests are run in docker. https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/mgmt/tests.md#writing-management-plane-test

Again, this requires network access (to download container images) and the ability to run a container for the test. Neither of these are available to OS packagers when they build their packages.

Hi @major ,
There is two parts to your question:

Get tests in sdist
Run tests without docker

For the first part, I agree with you, we should package the tests in the sdist, including recordings.
For the second part, we are moving away from vcrpy as a dependency, and we moved to a system that requires an actual mock server to run to replay the tests. This means either Docker (or Podman work as well and don't require a daemon) or to run the server manually with the dotnet cli.
I do recognize that running a mock server might be challenging, and we're working on a set of pytest fixtures to allow you to run unittests only, and skip recorded tests.
Would that solve your issues?
Thanks!

For the first part, I agree with you, we should package the tests in the sdist, including recordings.

That would be super helpful! I've made some PRs in the past to get this working in the templates, but azure-cli still calls for very old versions of some azure-sdk-for-python packages.

For the second part, we are moving away from vcrpy as a dependency, and we moved to a system that requires an actual mock server to run to replay the tests. This means either Docker (or Podman work as well and don't require a daemon) or to run the server manually with the dotnet cli.
I do recognize that running a mock server might be challenging, and we're working on a set of pytest fixtures to allow you to run unittests only, and skip recorded tests.
Would that solve your issues? Thanks!

Honestly, it might be easier for me to get some of the dotnet cli working in a test than it would be for something running in docker/podman. Either way the pytest fixtures (or perhaps marks?) would help me at least run some tests to ensure everything is packaged properly.
Are there any SDK packages where I could give this a try today? Or, is this all future planned work?
Thanks!

We do include tests in sdist but recording files are not included since current recording files are .json files after migration to testproxy. We will update the template to ensure the recording files are included in sdist.


Fix cyclic deps error (contrib,world,shared)

CMake Error: The inter-target dependency graph contains the following strongly connected component (cycle):
  "opencv_world" of type SHARED_LIBRARY
    depends on "opencv_xfeatures2d" (weak)
  "opencv_xfeatures2d" of type SHARED_LIBRARY
    depends on "opencv_world" (weak)
At least one of these targets is not a STATIC_LIBRARY.  Cyclic dependencies are allowed only among static libraries.

Problem is in deps of stitching module.

:+1:


custom image

add custom image and also change the status online to idle and do not DISTURB

Duplicate of #1

Setting status is not the what this app do.


Jagged indexing doesn't work for ChunkedArrays

This is somewhat similar to the problem #180. The problem here is that a ChunkedArray made out of JaggedArrays cannot be indexed by JaggedArrays:
>>> import awkward
>>> j = awkward.fromiter([[1]])
>>> j
<JaggedArray [[1]] at 0x7f68a3d71f60>
>>> c = awkward.ChunkedArray([j])
>>> c
<ChunkedArray [[1]] at 0x7f68b14497f0>
>>> mask = c.ones_like().astype(bool)
>>> mask
<ChunkedArray [[True]] at 0x7f68a3c85550>
>>> c[mask]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/mproffit/anaconda3/lib/python3.7/site-packages/awkward/array/chunked.py", line 480, in __getitem__
    raise TypeError("cannot interpret shape {0}, dtype {1} as a fancy index or mask".format(head.shape, head.dtype))
TypeError: cannot interpret shape (1, 1), dtype object as a fancy index or mask

This of course works just fine for standard JaggedArrays. I run into this problem with uproot because it's much more convenient to use lazyarrays() (which returns ChunkedArrays), but I can't use them with this problem.

+1 I would like to support this request

That's understandable, but I'm in a bit of a bind: I can either fix bugs on this version of awkward-array or make progress on the version that will replace it. Notice that all of the open issues that aren't enhancements involve ChunkedArray: this is a difficult one to get right in the present framework.
The redesign represented by awkward-1.0 is directly addressing this—the "layout" (e.g. JaggedArray vs IndexedArray of JaggedArray vs ChunkedArray of JaggedArray) will become an implementation detail inside a general Array class that abstracts over different layouts providing the same "high-level type" (e.g. jagged vs not-jagged). Specifically for this case, __getitem__ won't be asking whether the object in square brackets is a JaggedArray or a ChunkedArray of JaggedArray or a ChunkedArray of ChunkedArray of JaggedArray (there's an infinite set of possibilities); it will be asking if the high-level type is jagged. When ChunkedArrays report their type, they report the type of their contents.
Any work that I do to fix this version is a temporary patch, like fixing Python 2.7 in the era of Python 3 (except that I'm a team of one). Given that this would be a temporary solution anyway, could you do something like
array = awkward.concatenate(array.chunks)

to turn your ChunkedArray into a non-chunked array? Or do you run out of memory because it's a ChunkedArray of VirtualArray (i.e. a "lazy" array) and you really need the laziness? In uproot, iterate is a more explicit way of walking over chunks than lazyarray.
(Again, I understand that you have an immediate physics problem to solve and can't wait for pie-in-the-sky future developments; I'm just trying to find the best trade-offs. Sometimes you have to give up on some things in the present to reduce technical debt in the future.)

From my side this is for development / testing of a future fwk so it is not needed immediately and I can wait.  Do you have an idea of the timeline for the new version to be ready to use?

P.s My use case is with lazyarrays  (ChunkedArray of VirtualArray) since only lazy array has a profile method to pass in your own filling; iterate doesn't have this.  Would it make sense to add this profile method to iterate?

In that case, it would be better to wait because you don't want to develop a framework around something that will change this much.
When I started a month ago, I said I expected it to take 6 months, and that still seems like a reasonable estimate for physics users. I was also trying to get a minimally testable product out in one month, and I'm close to what I meant by that, though a potential user would have to ask, "What is meant by minimal?"
What I expect to finish in a week is:

awkward1.layout.NumpyArray, awkward1.layout.ListArray, awkward1.layout.ListOffsetsArray (which together represent jagged arrays), and awkward1.layout.TensorArray (which represents a regularly "shaped" array object, but not necessarily a Numpy array), with __iter__ and __getitem__ only (and only Numpy-like semantics; no jagged arrays in the square brackets yet).

This is the minimum set of layout classes that are needed to implement __getitem__ with Numpy-like semantics (beyond only NumpyArray, which wouldn't be interesting in itself because it just reproduces what Numpy can already do). I don't foresee wrapping these in a user-friendly awkward1.Array soon, though that is how they will eventually be used.
After that, I have to make a decision:

Update the Numba wrappers, to keep Numba and C++ development in sync, ensuring that I don't make any C++ designs that would be hard to carry over to Numba?
Implement awkward1.fromiter, since this is useful for making tests and demonstrating what awkward-array is good for.

Beyond those two, I'll be addressing RecordArray (the new name for Table). ChunkedArrays are quite a bit further down the list.

P.s My use case is with lazyarrays (ChunkedArray of VirtualArray) since only lazy array has a profile method to pass in your own filling; iterate doesn't have this. Would it make sense to add this profile method to iterate?

Oh! That's different—you're not interested in ChunkedArrays at all. You should be able to do the awkward.concatenate(array.chunks) trick to turn the lazy array into an eager array with no chunks.
Also, yes, there should be a profile option for eager arrays in uproot (tree.array, tree.arrays, tree.iterate, uproot.iterate...). In fact, that would be simpler to implement because it wouldn't involve all the indirection of trying to keep VirtualArrays from being prematurely materialized. It's just a matter of changing names and using IndexedArray to point to associated collections (e.g. jets associated with a muon). The biggest conceptual difficulty with that is that a user can ask for subsets of arrays, which might or might not include the associated collections you want to link across.
Maybe that shouldn't be something that uproot provides (because the eager-array uproot functions all have an interface that lets the user choose which arrays to read) but a renaming facility that happens afterward. That is, a function that looks at a dict of arrays and says, "If there are any named "Muon_(.*)", then JaggedArray.zip them into a collection named "muons" with "\1" as subnames," and "If "Muons_JetIdx" and "Jets_(.*)" are both present, then make the IndexedArray to associate one with the other." That's what the lazy-array profile is doing, except that all arrays are always available in VirtualArray form, and they have to be turned into new VirtualArrays that do this renaming on the fly. A separate function would just be a suite of if-thens that connect and rename arrays.

Thanks for the info.  I am only starting to play with this and this sounds interesting indeed.  I want to make essentially a class-like table of event.muons.variable etc, like you do for the CMS nanoAOD but for an ATLAS format.  Ideally, at the moment I think that on the "event" I want to be able to select events using the muons.variables etc but on the "muons" I also want to be able to select muons using muons.variables to make skimmed collections of muons, if that makes sense.  I am going to PyHEP so maybe I will talk to you there about this some more.  In the meantime I might have a go at such a function and any pointers as to how this should look (since I am not yet so familiar) would be useful.

That sounds great! Check into the coffea project, which has a kind of "DataFrame" for awkward-arrays, and it's not supposed to be exclusively CMS. You might find it an easier place to start generalizing.
An ATLAS profile would be very welcome, though as you can see we need better ChunkedArrays for the lazy profiles to be useful. Fortunately, the idea of this renaming can be separated from the idea of laziness.
However, do you know if you can read ATLAS data files in uproot? I had a lot of trouble trying to parse xAOD and DxAOD samples sent to me from Attila. Even the most understandable branches had types like std::vector<std::vector<X>>, which are not serialized by ROOT in a Numpy-friendly way (no way in Python to deserialize them without a for loop).
But we can definitely talk at PyHEP. See you there!

Thanks.
I should be clear this is more as a personal project and aimed at a further derived dataset from the DxAOD.

@masonproffitt Here's a better example, though your example works, too:
import awkward

j = awkward.fromiter([[1, 2, 3], [], [4, 5]])  # ensure that the array is really jagged
c = awkward.ChunkedArray([j, j])               # let's have more than one chunk
mask = (c % 2 == 0)                            # a mask that isn't all True
mask
# → <ChunkedArray [[False True False] [] [True False] [False True False] [] [True False]]>

c[mask]
# → ChunkedArray [[2] [] [4] [2] [] [4]]>

PR #193, will be part of 0.12.11.


Possibility to change URL of tool

It would be nice to be able to customize the URL of the Tool to something different than "nova-filemanager" ✌

Hello @marcreichel. Thanks for the suggestion but we’re not thinking to change for now.
Regards.


calendar integration

calendar integration so schedule can appear as a widget and can be imported to other planning apps. since pausd doesn’t even have a google calendar with the schedule

Can there be a fxn that generates a .cal file from the schedule and allow a download, so people can manually upload it to google cal.
Or alternatively, there could be a calendar link?


Group authors for references.

Codecov Report

Merging #588 into master will increase coverage by 0.05%.
The diff coverage is 90.62%.

@@            Coverage Diff             @@
##           master     #588      +/-   ##
==========================================
+ Coverage   53.86%   53.92%   +0.05%
==========================================
  Files         211      211
  Lines        5272     5285      +13
==========================================
+ Hits         2840     2850      +10
- Misses       2432     2435       +3

Impacted Files
Coverage Δ

src/entities/EntityDatabase.js
84.37% <ø> (ø)
:arrow_up:

src/article/converter/j2r/NormalizeContribGroup.js
87.5% <100%> (-12.5%)
:arrow_down:

src/entities/entityRenderers.js
82.24% <100%> (+0.26%)
:arrow_up:

src/article/converter/r2t/EntityConverters.js
94.97% <88.46%> (-0.76%)
:arrow_down:

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 a3b6348...38c2b8f. Read the comment docs.


ARROW-13655: [C++][Parquet] Disable Thrift message size protections

In Thrift 0.14+, the maximum message size is capped by default and attempts to read larger messages will error out.
The maximum message size doesn't really make sense in our case since we read the whole message buffer in memory anyway.
Also, it produces regressions on files with large metadata, which can be found in the real world.

With this PR, the reproducer in ARROW-13655 can be read with both Thrift 0.13 and 0.14:
<pyarrow._parquet.FileMetaData object at 0x7fc260dc5290>
  created_by: parquet-cpp-arrow version 6.0.0-SNAPSHOT
  num_columns: 1000
  num_rows: 40010
  num_row_groups: 4001
  format_version: 1.0
  serialized_size: 391441580

Since the reproducer file takes some time to read, I'm not sure how to integrate it into the CI checks.

Hmm, perhaps a more straightforward approach would be to use the Thrift version that's detected by CMake...

Since the reproducer file takes some time to generate and read (and the file is huge), I'm not sure how to integrate it into the CI checks.

Mark it as large_memory? Or is it still too large for that?
(although in practice we might not be running those tests ..)

Ah, we may mark it large_memory and use in-memory files indeed.

(although in practice we might not be running those tests ..)

Indeed. But at least they exist for later reproduction :-S

@github-actions crossbow submit -g cpp

I still need to read the information in https://nvd.nist.gov/vuln/detail/CVE-2020-13949 to make sure it is ok to disable the limit (it sounds like it should...).

The added test looks good. On the CVE issue, I can't add much insight, hopefully we get some response on the JIRA/mailing list.

I'm now reasonably convinced that this fix is correct (see the message I posted on https://issues.apache.org/jira/browse/THRIFT-5237?focusedCommentId=17416197&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17416197 ). I'd rather have a confirmation from the Thrift community, but if that doesn't arrive within a week or so, we may want to move forward with this fix.

Also cc @emkornfield

I am going to rebase and then merge if CI passes.

@github-actions crossbow submit -g cpp


move clearing of media query cache

resolve https://github.com/zurb/foundation-apps/issues/759

fix has been made in https://github.com/base-apps/angular-base-apps


Serial::setTimeout should accept param by const reference

It's misleading (and inconsistent with the constructor version of the same API) to accept this parameter by non-const reference as it indicates to me the user that it is being "captured" by reference and that I should therefore keep the timeout object I provide it around for at least as long as I have the Serial object itself, or that the object will be modified by the function itself. Neither of these do I believe to be true after closer inspection of the code.
If there is data being changed in Timeout (I followed the pimpl implementation through to unix.cc:702) it should be advertised more clearly in the documentation.
Thanks!

I agree, the setTimeout method should take a const Timeout &. The constructor should probably do the same. I just need to test how the default argument works out in that case.
I'll do this when I get some time, but it would go quicker with a pull request. Also, I'll need to consider how this breaks the ABI/API and then figure out what future release it should be included into.

I submitted PR 102 to hopefully make this go a little faster.  I hope it is acceptable.
Thanks for your attention @wjwwood !


chore: prepare for new release

Necessary tasks to prepare for the new release of charts to 2.1.2

I would include this PR as well: https://github.com/nautobot/helm-charts/pull/391


Can createDocumentFragment be used directly?

Can be used directly, no need to pass through VanJS proxy constructor?
let fragment =  document.createDocumentFragment()
    fragment.appendChild( div(input()) )

What do you mean by "VanJS proxy constructor"?
The code you pasted seems to be valid VanJS code.

I mean by "VanJS proxy constructor" a function that adds a proxy to an object.

The code you pasted seems to be valid VanJS code.

Yes, that is right.

In my large project I tried to use createDocumentFragment. I encountered the problem that the resulting DOM has no bindings with the reactive store.
let line = document.createDocumentFragment();
line.appendChild(el1); // el1 = extern func: return div(....
line.appendChild(el2); // el2 = extern func: return div(....
return line;

This breaks the bindings to the reactive store and as a result van.derive does not work in the extern func of creating the DOM.
So instead of return line; I use an extra div  return div(el1, el2);
Unfortunately, I have not yet been able to make a short example to repeat the error. Sorry.

I managed to write some code to test it. It has to do with vanX.list. If in vanX.list return createDocumentFragment then the bindings break.
    let state = vanX.reactive({test: [{id:0, name:'MSB'}, {id:1, name:'LSB'}]});
    let elFn1 = (obj, key) => {
        let el1 = div({view:()=>obj[key]}, 'click' );
        van.derive(()=>{
            el1.innerText = obj[key]+'(click)';
            console.log(obj[key]);
        });
        el1.onclick = evt=>{
            obj[key] += 100;
        }
        return el1;
    }
    let list = vanX.list(div, state.test, (objItem, deleter, key) =>{
        objItem = objItem.val;
        let el1 = div( {}, 'start line: ');
        let el2 = div( span('new '+objItem.name), elFn1(objItem, 'id') );
        let line = document.createDocumentFragment();
        line.appendChild(el1)
        line.appendChild(el2)
        // return div(div(el1), div(el2)); // it works
        return line; // it doesn't work
    });
    return list;

DocumentFragment cannot be treated as a DOM node for state binding. This is because in the DOM implementation, it's not represented as a standalone node, rather its children are just fused into its parent element.


Update for future versions

Hello!
I Would like to update the server to the new update 1.17.0 but it seems is too recent.
There is any way to identify when a new version comes out and then download it?
Thank you!

On container startup it pulls the latest, which worked fine for me just now:
> docker run -it --rm -e EULA=TRUE itzg/minecraft-bedrock-server

DEBU[0000] Using /data to match uid and gid
DEBU[0000] Resolved UID=0 from match path
DEBU[0000] Resolved GID=0 from match path
DEBU[0000] Forwarding signal                             signal="window changed"
Downloading Bedrock server version <IP_ADDRESS> ...
Starting Bedrock server...
NO LOG FILE! - setting up server logging...
[2021-06-09 17:54:52 INFO] Starting Server
[2021-06-09 17:54:52 INFO] Version <IP_ADDRESS>
[2021-06-09 17:54:52 INFO] Session ID d2316770-de22-4fc2-b4c2-669ab4b2de1f
[2021-06-09 17:54:52 INFO] Level Name: Bedrock level
[2021-06-09 17:54:52 INFO] Game mode: 0 Survival
[2021-06-09 17:54:52 INFO] Difficulty: 1 EASY
[INFO] opening worlds/Bedrock level/db
[INFO] IPv4 supported, port: 19132
[INFO] IPv6 not supported
[INFO] IPv4 supported, port: 41465
[INFO] IPv6 not supported
[INFO] Server started.

...as far as detecting a new version and auto-restarting the container (if that's what you're asking), then that's beyond the scope of this image. It would be great if someone would implement a sidecar image/utility that could automate that.

Thank you very much!
That solved the problem, I'll try to replicate an internal CICD to try something out


Implement pc regression with jax

Original source:
https://github.com/theislab/scib/blob/main/scib/metrics/pcr.py
See the manuscript for a description (search principal component regression):
https://www.nature.com/articles/s41592-021-01336-8#Sec11

For the api of this package, see the other metrics implemented. For now we are going with no anndata, just straight numpy ndarrays

LinearRegression and PCA should use jax implementation as the data will be a low-dimensional embedding


Drive Name Assigned or Empty

I was trying to the GUI working - but I noticed I can't even enter the drive name (For reference). Whatever I type, it tells me that it has been assigned or empty.

@ankushdas9, was this resolved?

I met same problem too


🏆 Ranklist and Certificate Info (Top 11 - 20) Part -2

As there is a limit to the number of contributors that can be tagged in one comment.
So, I am breaking the list in 3 parts -
Top 1 - 10, Top 11 - 20 (Part - 1) Top 11 - 20 (Part -2)

Hi enthusiastic contributors,
Congratulations🎉 and Thank you for contributing and making the Hacktoberfest a success for you and for us.
Time for celebration 🥳:
Please take a moment to share your achievements and the dedication you've displayed throughout the month of October. Showcase your accomplishments on LinkedIn, allowing your network to appreciate the positive impact you've made. 📈
Be sure to mention the repository - SarthakKeshari/calc_for_everything (github.com) 📚, highlighting the specific features you've skillfully integrated into it.
I'd be honored to extend my personal congratulations, so if you wish to include me in your celebration 🎊, do not hesitate to tag me in your posts on LinkedIn - Sarthak Keshari | LinkedIn

Contribution Certificate
All the contributors are requested to fill the Google form. Form will be active till 10th of November, 2023.
https://forms.gle/oQ5NPE2KP3fkQDwn6

Ranklist

Rank
Githib Handle
Points Scored

15
@vendhan-ds
5

15
@tmsagarofficial
5

15
@TANYA03GUPTA
5

15
@srronaksingh
5

15
@Musak2
5

15
@Heramb4270
5

15
@atharvsawant2003
5

15
@abhijithhegde
5

15
@Ahasasjain
5

15
@XronTrix10
5

15
@shivanshhgit
5

15
@real-varshney
5

15
@DapaoK
5

15
@Alfred-hhy
5

15
@Upkar0904
5

15
@wuyu-wy
5

15
@M111ku
5

15
@WaterCubeGod
5

15
@Shantanu-Tiwari
5

Thanks and Regards,
@SarthakKeshari

Hi all,
This repository will remain active and will launch as a website. So, I invite you all to be an active contributor and contribute features and fix bugs.
See you all in the pull requests... 👋🏻

Hi all,
Certificates we be given out from 12th November, 2023 (00:00:00 IST) to 14th November, 2023 (23:59:59 IST).
Comment here and keep a check on my reply, if you don't receive your certificate latest by 14th November, 2023 (23:59:59 IST).

No certificates will be given out after 17th November, 2023 (23:59:59 IST).

Heramb Sachin Bhoodhar
Certificate Not Received
On Sat, 11 Nov 2023, 4:52 pm Sarthak Keshari, @.***>
wrote:

Hi all,
Certificates we be given out from 12th November, 2023 (00:00:00 IST) to
14th November, 2023 (23:59:59 IST).
Comment here and keep a check on my reply, if you don't receive your
certificate latest by 14th November, 2023 (23:59:59 IST).
No certificates will be given out after 17th November, 2023 (23:59:59 IST).
—
Reply to this email directly, view it on GitHub
https://github.com/SarthakKeshari/calc_for_everything/issues/644#issuecomment-1806788877,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUD72LJ35QIEB4Y7B6KRSITYD5NWFAVCNFSM6AAAAAA62H624GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBWG44DQOBXG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

TANYA03GUPTA   Tanya Gupta c ertificate not recieved @SarthakKeshari

Upkar Chaudhary certificate not received @SarthakKeshari

Dear Contributors,,
I am pleased to announce that all certificates have been successfully distributed.
Kindly Note - Certificates have been issued exclusively to contributors whose names appear in the rank list and have completed the requisite step of filling out the google form at https://forms.gle/oQ5NPE2KP3fkQDwn6.
No certificates will be given out after 17th November, 2023 (23:59:59 IST).
Should you have any queries or concerns, please do not hesitate to reach out.
Thanks and Regards,
Sarthak Keshari


Can't clear breakpoint condition

It doesn't seem to be possible to clear a breakpoint condition. There's no clear button, no clear context menu action and I can't input an empty value (that just seems like a no-op).

The empty value should not be a no-op. Will fix next week


Dev server proxy doesn't handle blob: protocol

Describe the bug
Dev server doesn't handle blob: protocol, so I can't load images from my local S3 storage, example url:
blob:http://localhost:3000/s3/my-image
I just get ERR_FILE_NOT_FOUND
Reproduction
https://stackblitz.com/edit/vitejs-vite-psxg4p?file=main.js
Steps to reproduce
npm i && npm run dev
System Info
stackblitz

Used Package Manager
npm
Logs
No logs, because it doesn't get triggered
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Oops, devtools confused me! blobs can be only created in memory.