Map has missing challenges

Desktop view (chrome)

@BerkeleyTrue

does this happen with other languages? is there code to default to english if there isn't a translation for some text?
I'd like to help fix this one if it's suitable for beginners

Issue also occurs with english on staging and does NOT occur on master including with Spanish (might be due to browser cache? can anyone else reproduce the bug with english on staging?):

I'd like to work on this issue - any help would be appreciated

Here are some errors I'm getting about the props when I open the map.
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isAllCollapsed` prop on `MapHeader`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `filter` prop on `MapHeader`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `clearFilter` prop on `MapHeader`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `updateFilter` prop on `MapHeader`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `collapseAll` prop on `MapHeader`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `expandAll` prop on `MapHeader`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `title` prop on `SuperBlock`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `dashedName` prop on `SuperBlock`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `blocks` prop on `SuperBlock`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isOpen` prop on `SuperBlock`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isHidden` prop on `SuperBlock`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `message` prop on `SuperBlock`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `toggleThisPanel` prop on `SuperBlock`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `title` prop on `Block`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `dashedName` prop on `Block`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `time` prop on `Block`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isOpen` prop on `Block`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isHidden` prop on `Block`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `challenges` prop on `Block`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `toggleThisPanel` prop on `Block`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `title` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `dashedName` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `block` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isLocked` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isRequired` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isComingSoon` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isCompleted` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isDev` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `isHidden` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `challenge` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `updateCurrentChallenge` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.printWarning @ bundle.js:2631
bundle.js:2631 Warning: You are manually calling a React.PropTypes validation function for the `closeMapDrawer` prop on `Challenge`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.

okay the text reappears if I set those to isBeta: false - those four are set to isBeta: true. something is wrong with how beta challenges are rendered.

These two commits from https://github.com/FreeCodeCamp/FreeCodeCamp/pull/10654 are suspect but I'm going to bed. Will figure out why beta challenges are not displaying tomorrow.
https://github.com/FreeCodeCamp/FreeCodeCamp/pull/10654/commits/26875725db41bb084d7fdf5ca1bb52b2ad2728a0
https://github.com/FreeCodeCamp/FreeCodeCamp/pull/10654/commits/a4f1722c29b7ad68bb959ce7eba5b041ad01a7e3

here is the branch I'm using working on this. I also found a typo in utils.js
https://github.com/ashleypt/FreeCodeCamp/tree/fix/11547

Some of the Challenges being rendered in Challenge.jsx have undefined titles. These are not the only ones but for some reason they are the only ones with blank bullets. Here are the non-blank dashedNames of the challenges with this problem (if !title) console.log dashedName:
For now I am going to solve this problem by returning null if the title is undefined. In the future we need to find out WHY these titles are coming across as undefined
create-a-javascript-slot-machine
bundle.js:133062 add-your-javascript-slot-machine-slots
bundle.js:133062 bring-your-javascript-slot-machine-to-life
bundle.js:133062 give-your-javascript-slot-machine-some-stylish-images
bundle.js:133062 slice-and-splice
bundle.js:133062 learn-sass-challenges
bundle.js:133062 learn-react-challenges
bundle.js:133062 learn-d3-challenges
bundle.js:133062 learn-accessibility-challenges
bundle.js:133062 learn-agile-challenges
bundle.js:133062 learn-computer-science-challenges
bundle.js:133062 learn-data-visualization-challenges
bundle.js:133062 learn-embedded-and-internet-of-things-challenges
bundle.js:133062 learn-game-development-challenges
bundle.js:133062 learn-gamification-challenges
bundle.js:133062 learn-machine-learning-challenges
bundle.js:133062 learn-math-for-programmers-challenges
bundle.js:133062 learn-mobile-javascript-development-challenges
bundle.js:133062 learn-devops-challenges
bundle.js:133062 learn-software-engineering-principles-challenges
bundle.js:133062 learn-statistics-challenges
bundle.js:133062 learn-tools-challenges
bundle.js:133062 learn-user-experience-design-challenges
bundle.js:133062 learn-visual-design-challenges

@ashleypt apologies for the delay in responding. You may refer to https://github.com/FreeCodeCamp/FreeCodeCamp/pull/11575#issuecomment-259115693

does this happen with other languages?

I am guessing yes, and as you have already investigated for english too.

is there code to default to english if there isn't a translation for some text?

Nope. And there is an open issue that is to be addressed. Refer #11545

@Bouncey would like to guide @ashleypt further? Considering you have worked on the notification message with an open PR?

I'm unable to replicate.
@raisedadead Are you seeing the same?

@BerkeleyTrue Yes, I can reproduce this is the latest staging for me:

So what is different between our setups?

Strange, IDK to be honest, apart from the fact that I cleared the db completely.

All the learn-* challenges are referenced in #9349, and are ok.

is there code to default to english if there isn't a translation for some text?

The challenges are all in english, it is only when there is a translation that the challenge changes. See here.
@ashleypt Thank you for all your work, and I am sorry for my delay in offering help with this
@BerkeleyTrue Do we want the slot machine & slice and splice challenges on the map? If I edit the seed files to set isBeta to false, the challenge renders normally. I haven't got my head around filterComingSoonBetaFromEntities yet, but I would guess it is in that area

yeah you need to do this on the staging db to see it.
On Wed, Nov 9, 2016 at 3:58 AM Mrugesh Mohapatra<EMAIL_ADDRESS>wrote:

Strange, IDK to be honest, apart from the fact that I cleared the db
completely.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/11547#issuecomment-259242276,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOKKP6zC0iLIzyj4wZNVKT_fAy6LzwjTks5q8NR_gaJpZM4Kqhbl
.

Do we want the slot machine & slice and splice challenges on the map?

@Bouncey in dev all challenges render.

@BerkeleyTrue the bug probably doesn't occur in dev mode. marking those four challenges as isBeta: false also fixes it

the bug probably doesn't occur in dev mode.

What mode are you in?

marking those four challenges as isBeta: false also fixes it

It is an indication of where the problem may lie but it is does not fix the issue.

@BerkeleyTrue the default one. I don't change it... maybe that is dev mode?

doesnt fix issue

yeah I know... what could be causing this? I'm not really familiar with redux though ive played a bit with react

@ashleypt I'm unable to reproduce so I could not investigate
If you are able to reproduce, could you investigate? Until we find the actual cause a PR cannot be submitted.

@BerkeleyTrue sure, might take some time as im unfamiliar with the code base but I'll eventually get to the bottom of these pesky blank bullets and undefined titles :)
@Bouncey any tips or places to start in the code? I think I should watch a video on redux first...

@ashleypt this is not a redux issue, i think this is about how the challenges are filtered, look around here
If you want to see where that function is used, use the search in this repo to see where it shows up. I'd love to help more but I have to sleep .
Happy coding!

@QuincyLarson is also unable to reproduce

What are the differences in ENV?
I have recently deleted node_modules and bower_components and did a fresh install of both.
browser: chrome@latest
OS: Ubuntu 16.04
node: v6.9.1
npm: v3.10.8
mongod:
  db version v3.2.9
  git version: 22ec9e93b40c85fc7cae7d56e7d6a02fd811088c

Yes, I also did fresh runs each time with git clean -fxd.

Can I help with this Issue?

yes im a bit overwhelmed right now. feel free to take over
On Sun, Nov 20, 2016 at 2:09 AM Mridul Nagpal<EMAIL_ADDRESS>wrote:

Can I help with this Issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/11547#issuecomment-261729675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOKKPyPcNZE6F_JY8bX1W5l4jPEWwPn6ks5q_ztWgaJpZM4Kqhbl
.

@ashleypt Could you please give me a little background of the problem I couldn't make it out from the comments please.

some challenges marked isBeta, plus some not are passed with a blank title
prop in the jsx. they mention a few related functions here but my kb
batteries are out so i can't type much now (using mouse lol)
On Sun, Nov 20, 2016 at 9:22 AM Mridul Nagpal<EMAIL_ADDRESS>wrote:

@ashleypt https://github.com/ashleypt Could you please give me a little
background of the problem I couldn't make it out from the comments please.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/11547#issuecomment-261751425,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOKKPzvoKdbzeg5RnyyuGKYq7Gh-2Hcuks5q_6C5gaJpZM4Kqhbl
.

Closing, can reproduce any longer, thanks @ashleypt and others for your TA on this.


Fix issue 29184 - TabularInline read-only fields label and help text …

Providing a ModelForm for admin.TabularInline will have any Meta.labels or Meta.help_texts overrides for read-only fields ignored.

Please try to reuse existing models in the tests.

@timgraham thanks, I added two fields to an existing model, changed its admin and use it in tests.

@carltongibson thanks for your comments. I did your requested changes.


Add yaml linter to check for formatting errors

Motivation
Have encountered issues adding new GitHub Actions workflows where it's unclear why a workflow hasn't been detected.
It turns out that this is likely because the file had an invalid formatting and GitHub Actions failed to parse it.
Details
Adding yamllint to the pre-commit config so that we check formatting at commit time and in CI to ensure there are no formatting errors. And save time in future when adding or changing workflow config

Also what did you use to re-format the yaml files - did you use a tool or did you fix manually?

I used the YAML extension in  VS Code to format them. I've tried adding Prettier as a formatter here #73 which I think is the same thing the VS Code YAML formatter uses


Can't use translation file for en-US: "An i18n locale ('en-US') cannot both be a source locale and provide a translation"

🐞 bug report
I can't use a translation file for en-US:
i18n": {
    "locales": {
      "en-US": {
        "baseHref": "delete/us/en_us",
        "translation": "messages.en-us.xlf"
      }
    }
}

Description

Our app is translated into 40+ languages
We want our translation department to be responsible for all strings
We want to ignore the strings our developers have written in the HTML files
Therefore we need one build per messages.xlf file and no build for the "sourceLocale"
At the moment we are forced to manually copy the strings from the messages.en-us.xlf file back into our HTML every time our translation department makes a change to en-US

Possible solutions:

Allow "translation" as a property of "sourceLocale"

"sourceLocale": {
  "code": "en-US",
  "translation": "messages.en-us.xlf"
}

Add option to prevent the build of the source locale

🔬 Minimal Reproduction
https://github.com/MartinJaskulla/angular-issue-38316
🔥 Exception or Error

An unhandled exception occurred: An i18n locale ('en-US') cannot both be a source locale and provide a translation.

🌍  Your Environment
Angular Version:

Angular CLI: 9.0.7
Node: 12.13.1
OS: darwin x64

Angular: 9.0.7
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.900.7
@angular-devkit/build-angular     0.900.7
@angular-devkit/build-optimizer   0.900.7
@angular-devkit/build-webpack     0.900.7
@angular-devkit/core              9.0.7
@angular-devkit/schematics        9.0.7
@angular/localize                 9.1.12
@ngtools/webpack                  9.0.7
@schematics/angular               9.0.7
@schematics/update                0.900.7
rxjs                              6.5.5
typescript                        3.7.5
webpack                           4.41.2

Anything else relevant?
I know that there are several workarounds. For example we could provide a non-existent source locale "sourceLocale": "aa-aa" and delete the build afterwards. However our app is very big and we want to save the build time.
Furthermore our actual setup is more complex than the example provided above. For example the translations for the same locale e.g. my-app.com/de/en-US and my-app.com/us/en-US can be different. It would be useful for angular.json to provide some sort of nesting of the locales.

I have the same problem, and agree with the suggested solution

Allow translation as a property of sourceLocale

Hello @alan-agius4 we have the same issue mentioned above and specially this point

We want our translation department to be responsible for all strings

I was going to create a PR for that but want to make sure you agree with

Allow translation as a property of sourceLocale

Same issue here, we only have one language but would like to use i18n so we can use translation tools to have non developers change the strings we use.

We have the same problem...
It is strange to think that in a huge complex application the main source of the language will be in HTML ...

We have the same problem...
It is strange to think that in a huge complex application the main source of the language will be in HTML ...

Same issue here, we only have one language but would like to use i18n so we can use translation tools to have non developers change the strings we use.

My workaround:
Configure a fake sourceLocale in angular.json. I used zxx, which is actually a valid ISO639-2 code (https://www.loc.gov/standards/iso639-2/php/code_list.php)
Only downside is a warning during ng extract-i18n:
Warning: AngularCompilerPlugin: Unable to load the locale data file "@angular/common/locales/zxx", please check that "zxx" is a valid locale id.
If needed, you can use "registerLocaleData" manually.
That will possibly disappear when you choose a different valid locale code not used by your application

I use the same workaround as @nelisbijl with aa-AA as ISO code and it works.
But this is not a correct solution, can maintainer have a look at this ticket and give us a status ?

Any potential update on this issue? It's really annoying to manage all your text with a service like lokalise.com when you can't have the source locale as a translation target.

Private use subtags can be used to describe the unique nature of the source locale in these type of cases.  For example, the following configuration section provides for a translated de locale while also describing the content within the source code as untranslated.
“i18n”: {
	“sourceLocale”: “de-x-source”,
	“locales”: {
		“de”: “./locales/de.xliff2”,
		“en”: “./locales/en.xliff2”,
		“fr”: “./locales/fr.xliff2”
	}
}

@clydin I needed to change a few things in my extraction and upload scripts but this works well. Thank you very much :)

@clydin  Hi, I'm having the same issue here. Would like to use a default translations file for my sourceLocale. Although Im not sure how
      "i18n": {
        "sourceLocale": "nl-x-source",
        "locales": {
          "nl-x-source": {
            "baseHref": "/sa-agenda/",
            "translation": "src/locale/messages.nl.xlf"
          }
        }
      }

Now Im just running into the same issue? I;m not sure how this would work. Could you help me out please?

Hi, I'm facing a similiar issue.
I have a multilanguage app supporting many different languages.
Now aside of the other language versions I my app to have a different specific variants of en locale.
For example I will have en-US, en-GB, en-ZA, etc..
I expect that 95% of the phrases between this locales will be shared and only few percent will differ and specific to region.
Not to duplicate all the phrases and repeat the translations within multiple en files I supposed I could utilize "en" as a source locale and put there all shared words and translations and then only put the phrases with specific regional words to target translation files (en-GB, en-US,...).
However it appeared you cannot specify a translation file for a source locale and you have tu put the phrases directly into the views.
Doing this instead of using resource ID's seems like an anti pattern and a maintenance nightmare.
Is there a way I can achieve this kind of shared resource behavior now?

Bumping this issue.
Angular team, please, pay attention to it because it's seems not so hard to do but can make developer's life much easier.

Fixing Angular i18n Error
When using Angular's ng extract-i18n command, you may encounter an error message like:

An unhandled exception occurred: An i18n locale ('en-US') cannot both be a source locale and provide a translation.

This error suggests a conflict in your project configuration, particularly with the en-US locale. Here's how to resolve it:
Steps to Fix the Error

Check Project Configuration:
Open your Angular project's configuration file (usually angular.json). Look for the i18n section to review the sourceLocale and locales settings.

Modify Locale Settings:

If en-US is your source locale, ensure it's not listed under locales for translations.
If en-US is a translation target, ensure it's only listed under locales and not set as the sourceLocale.

Update Source Locale:
Change your sourceLocale if necessary, ensuring it is different from the translation locales.

Validate Configuration:
Ensure each translation locale is unique and no locale is both sourceLocale and in the locales list.

Re-run the Command:
After making the changes, try running ng extract-i18n again.

Example Configuration
Here is an example snippet from an angular.json file:
{
  ...
  "projects": {
    "your-project": {
      ...
      "i18n": {
        "sourceLocale": "en-US", // Adjust as needed
        "locales": {
          "pl-PL": "src/locale/messages.pl.xlf",
          // other locales
        }
      }
      ...
    }
  }
  ...
}

@createdbyjurand We don't need you to use ChatGPT, please don't copy paste its answer in GH issues. Furthermore, this is not a valid solution.

+1

+1

+1


Auto queue non standard game modes.

Currently we only auto queue osu standard players. We should do a (smaller) portion of other game modes as well.

i wonder if there is any statistics known out there with the ratio of standard vs other gamemode players so you can use that same ratio to auto queue, to be "fair" hahahahaha

I was wondering the same thing tbh.
On Feb 23, 2016 18:24, "Olle Kelderman"<EMAIL_ADDRESS>wrote:

i wonder if there is any statistics known out there with the ratio of
standard vs other gamemode players so you can use that same ratio to auto
queue, to be "fair" hahahahaha
—
Reply to this email directly or view it on GitHub
https://github.com/OsuCelebrity/OsuCelebrity/issues/54#issuecomment-187800256
.

how about x per gamemode? (example. 5 per standard, then 5 of taiko then 5 of ctb ecc...)

You mean rounds? x successive players per game mode?

yeah, successive players per gamemode untill somebody got voted

I think it would be better to have it randomized. Most people come to the stream for standard so if they see 5-15 players in a row not playing standard they would leave the stream.

I would like to see 15% mania, 15% taiko, 15% ctb and 70% standard. Randomized of course.

I agree.


nixos/geoclue: minor cleanups

spawn the geoclue-agent directly instead of running it via bash
document why we cannot use DynamicUser = true
have systemd create the home directory instead of using an explicit
tmpfiles.d fragment

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

For the record, the ExecStart attribute still uses the system shell (bash).


Add debug mode and tempest webhook

This patch introduces an option for test-operator that keeps the pod running even after a failure occured or after the file run_tempest.sh has reached its end (sleep infinity). It resolves the issue that oc rsh session is killed once the execution of the run_tempest.sh finishes.
Additionally, it creates tempest webhook to check workflow option is not set when debug mode is set to true. It is to avoid unwanted behavior when in debug mode.
Depends-On: https://github.com/openstack-k8s-operators/tcib/pull/163

@kstrenkova, nice progress! We're going to utilize the webhook to check whether there are available PVs on the system later. This is going to be really helpful once completed. It looks like we are really close. We just need to resolve the TLS issue.

@kstrenkova you can add
Depends-On: https://github.com/openstack-k8s-operators/tcib/pull/163  into the commit message and description of this PR

@kstrenkova can you also please add the commit that updates the documentation please?

recheck
The jobs got DEQUEUED.

Let's wait for the TCIB change to be merged first:). Also we should wait for the latest build of the openstack-tempest[-all] image that contains the @kstrenkova's change [1].
[1] https://quay.io/repository/podified-antelope-centos9/openstack-tempest-all?tab=tags

recheck

recheck


About the channel shift

class TemporalShift(nn.Module):
    def __init__(self, n_div=8):
        super(TemporalShift, self).__init__()
        self.fold_div = n_div
        print('=> Using channel shift, fold_div: {}'.format(self.fold_div))

    def forward(self, x, frame_len):
        x = self.shift(x, fold_div=self.fold_div, frame_len=frame_len)
        return x

    @staticmethod
    def shift(x, fold_div=8, frame_len=8, shape=(112,112,80)):
        B, num_heads, N, c = x.size()
        fold = c // fold_div
        feat = x
        feat = feat.view(B, frame_len, -1, num_heads, N, c)
        out = feat.clone()

        out[:, 1:, :, :, :, :fold] = feat[:, :-1, :, :, :, :fold]  # shift left
        out[:, :-1, :, :, :, fold:2 * fold] = feat[:, 1:, :, :, :, fold:2 * fold]  # shift right

        out = out.view(B, num_heads, N, c)

        return out

Why does the channel dimension in the channel shift code take the following values: fold and fold: 2 * fold, and the remaining channels(2fold:c-2fold)do not need to be shifted? I don't understand very much.

please check
https://openaccess.thecvf.com/content_ICCV_2019/papers/Lin_TSM_Temporal_Shift_Module_for_Efficient_Video_Understanding_ICCV_2019_paper.pdf
Fyw1988 @.***>于2023年2月15日 周三下午9:52写道：

class TemporalShift(nn.Module):
def init(self, n_div=8):
super(TemporalShift, self).init()
self.fold_div = n_div
print('=> Using channel shift, fold_div: {}'.format(self.fold_div))
def forward(self, x, frame_len):
    x = self.shift(x, fold_div=self.fold_div, frame_len=frame_len)
    return x

@staticmethod
def shift(x, fold_div=8, frame_len=8, shape=(112,112,80)):
    B, num_heads, N, c = x.size()
    fold = c // fold_div
    feat = x
    feat = feat.view(B, frame_len, -1, num_heads, N, c)
    out = feat.clone()

    out[:, 1:, :, :, :, :fold] = feat[:, :-1, :, :, :, :fold]  # shift left
    out[:, :-1, :, :, :, fold:2 * fold] = feat[:, 1:, :, :, :, fold:2 * fold]  # shift right

    out = out.view(B, num_heads, N, c)

    return out

Why does the channel dimension in the channel shift code take the
following values: fold and fold: 2 * fold, and the remaining channels(2
fold:c-2fold)do not need to be shifted? I don't understand very much.
—
Reply to this email directly, view it on GitHub
https://github.com/MartinXM/TPS/issues/6, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTID26AGTOMCARA2VAAZRLWXTNRTANCNFSM6AAAAAAU44B65E
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

please check https://openaccess.thecvf.com/content_ICCV_2019/papers/Lin_TSM_Temporal_Shift_Module_for_Efficient_Video_Understanding_ICCV_2019_paper.pdf Fyw1988 @.>于2023年2月15日 周三下午9:52写道：
…
class TemporalShift(nn.Module): def init(self, n_div=8): super(TemporalShift, self).init() self.fold_div = n_div print('=> Using channel shift, fold_div: {}'.format(self.fold_div)) def forward(self, x, frame_len): x = self.shift(x, fold_div=self.fold_div, frame_len=frame_len) return x @staticmethod def shift(x, fold_div=8, frame_len=8, shape=(112,112,80)): B, num_heads, N, c = x.size() fold = c // fold_div feat = x feat = feat.view(B, frame_len, -1, num_heads, N, c) out = feat.clone() out[:, 1:, :, :, :, :fold] = feat[:, :-1, :, :, :, :fold] # shift left out[:, :-1, :, :, :, fold:2 * fold] = feat[:, 1:, :, :, :, fold:2 * fold] # shift right out = out.view(B, num_heads, N, c) return out Why does the channel dimension in the channel shift code take the following values: fold and fold: 2 * fold, and the remaining channels(2 fold:c-2fold)do not need to be shifted? I don't understand very much. — Reply to this email directly, view it on GitHub <#6>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTID26AGTOMCARA2VAAZRLWXTNRTANCNFSM6AAAAAAU44B65E . You are receiving this because you are subscribed to this thread.Message ID: @.>

Thank you so much!!!


Minema crashes when I try to record : Can't export frame

Hi, I am on Windows 10 and I use Minema v3.5.4-ShaderSync but when I try to record it crashes
FFmpeg version is: 2020-12-24-git-9a0f5e412a-full_build
When I try to record with minema it tells me the following error:
java.util.concurrent.ExecutionException
java.lang.RuntimeException: Can't export frame 1
Cause:
java.lang.RuntimeException
Can't export frame 1
See log for full stacktrace
this is the log:
https://pastebin.com/v1VJNhha

Try using this build of ffmpeg.

Try using this build of ffmpeg.

It did not work, here is the complete log:
https://pastebin.com/QQSi1g2H

@shiro2505 can you provide an ffmpeg log? It should be in the Capture path folder, one of the log files.

@mchorse here is a recent log
2020-12-27_15.08.17.log

Did you edit by any chance the Encoding > Encoder arguments option? If no, try resetting it to default state (there is one of the buttons on the right that allows to reset the value), and try again.

just modify the location of ffmpeg

Hm... this is so weird... I'm not really sure what could be the problem. It's certainly not a permission error, as the log files and the fact that ffmpeg log exists shows that. What is your Frame width and Frame height in Capturing settings (maybe just send .minecraft/config/minema.cfg)?

the frame height is 1440 and frame width is 900

this is minema's configuration file
minema.zip

Everything seems fine, my last suggestion would be create a new folder within C:\ffmpeg\ and call it something like movies, and change the Capture path in Capturing option to C:\ffmpeg\movies\. Try recording afterwards.

the error continues ☹

Are you sure that the Capture path saved? I.e. you can't exit the menu by pressing Escape, you have to close it using Done button until you exit to Mods Option screen. If you did save, then I have sadly no idea... 😔
You could also try testing whether the problem is with ffmpeg, by opening Command Prompt and executing C:\ffmpeg\bin\ffmpeg.exe. If the output is something like:

ffmpeg version 4.2 Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 9.1.1 (GCC) 20190807
configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt
libavutil      56. 31.100 / 56. 31.100
libavcodec     58. 54.100 / 58. 54.100
libavformat    58. 29.100 / 58. 29.100
libavdevice    58.  8.100 / 58.  8.100
libavfilter     7. 57.100 /  7. 57.100
libswscale      5.  5.100 /  5.  5.100
libswresample   3.  5.100 /  3.  5.100
libpostproc    55.  5.100 / 55.  5.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...
Use -h to get full help or, even better, run 'man ffmpeg'

Then everything is alright.

ffmpeg version 4.3.1-2020-11-19-full_build-www.gyan.dev Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 10.2.0 (Rev5, Built by MSYS2 project)
configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable-libsnappy --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libzvbi --enable-librav1e --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
libavutil      56. 51.100 / 56. 51.100
libavcodec     58. 91.100 / 58. 91.100
libavformat    58. 45.100 / 58. 45.100
libavdevice    58. 10.100 / 58. 10.100
libavfilter     7. 85.100 /  7. 85.100
libswscale      5.  7.100 /  5.  7.100
libswresample   3.  7.100 /  3.  7.100
libpostproc    55.  7.100 / 55.  7.100
Hyper fast Audio and Video encoder

Hey so I this problem may have been awhile ago but i think i figured it out because i had the same problem.... its most likely you dont have enough space on your pc so clear some memory and it should work.

Hey so I this problem may have been awhile ago but i think i figured it out because i had the same problem.... its most likely you dont have enough space on your pc so clear some memory and it should work.

I have 2 hard disks but I cannot set the export path to D) in Minema.

Hello Guys!
I have 2 hard disks but I cannot set the export path to D) in Minema.

What do you mean by "I cannot?" Can you be more specific?


Tests run 2 times instead of 1

Describe a bug
Why the tests run 2 times in a row instead of 1?

Then it's running it for the 2nd time?

Expected behavior
Only 1 test run should be present

Details

Action version: 2.3.0
OS, where your action is running (windows, linux): Linux

      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v4
        with:
          node-version: ${{ matrix.node-version }}
      - uses<EMAIL_ADDRESS>        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}
          test-script: npm run test:ci

Additional context
In github actions I can see tests are run twice instead of just once.

I've seen the same issue in our pipelines. Looks like it's running jest twice.

@ piotrwalczak1 The process involves running a test twice to compare the coverage report between the base and feature branches. You can gauge the disparities by examining the differences in the statements, branches, lines, and function fields between the two test results.


DOC: Correct Rosenbrock function sum

Reference issue

Closes #12149 by correcting the sum from 1 to N-1 instead of 2 to N
What does this implement/fix?

Fixes sum indices in Rosenbrock function

Thanks @Bharat123rox


When animate to right side, getting bottom scroll bar

Hello,
When we use some right side animations like fadeOutRight, bounceOutRight..
getting the scroll bar in the bottom.
Thanks _/_

You've got to use overflow-x: hidden in its container or body, as the animations, literally translate the element beyond the page's width.

It helps a lot, thanks.


Enable Kindle huffdic compression

Is it considered a best practice to always have this enabled? Otherwise, it might be best to make it an option that can be passed from the commandline...perhaps something like ebook-compression=huffdic. Thoughts?

Yeah, that's actually a better fit for how asciidoc operates on the whole. We should let ebook-compression correlate to the 3 different compression modes the kindlegen bin has to offer.

Does this mean that there are no tests running for this project?
I would just like to have some tests to run to make sure I'm not breaking anything.
https://github.com/asciidoctor/asciidoctor-epub3/blob/master/Rakefile#L32

Does this mean that there are no tests running for this project?

Unfortunately, that is the case atm. It's a top priority to address this. See #11.

I also discovered that we can drastically reduce the size of the mobi by passing this undocumented flag:
-dont_append_source

This cuts the file size in half. I've enabled it on master. https://github.com/asciidoctor/asciidoctor-epub3/blob/master/lib/asciidoctor-epub3/packager.rb#L463

Superseded by #99. I implemented the 3 levels of compression, but used the ebook-compress flag instead (to align with ebook-validate and ebook-extract).


Wildcard support for code-splitting

To my current understanding, if you want to split off vendor code from application code, you have to provide an explicit list of the modules that you want in the vendor code. The trouble with this is that you must maintain an explicit list and keep it in sync with changes to your application. Webpack already discerns the information about which files are required via an entry point, so it makes quite a bit of sense to be able to specify a glob or regex to match against the bundled modules to define which ones are split into another chunk.
In other words, something like this would be very convenient, and is easy for webpack to provide but hard for a consumer to implement:
{
    entry: {
        app: __dirname + '/client/app.js',
        vendor: __dirname + '/node_modules/**'
    }
}

I believe this is what you want: link (using minChunks function parameter for CommonsChunkPlugin).
I agree that it would be nice to have a more straightforward way of setting that up. Using glob/regex for entry point doesn't seem right though; I'd expect that to just bundle all the matches it can find on the file system like require.context does.

Yeah, that solves the problem in a reasonably succinct way. I don't feel like it's on uncommon use case though, so clear support or documentation would be a bonus. Thanks!


Remove superfluous copy

Not needed anymore since https://github.com/rancher/elemental-toolkit/pull/1832

Hmm, looking at the tests we will have to do a new release of the toolkit. I can revisit this when we get there :+1:


Update main.tf

remove the count for the resource alicloud_security_group

HI @ASaiun Thanks for your feedback. Can I know why it needs to remove count?

ok ,I test it just now, It work for me now, I will close it .
but I think you need to update the readme file for the example.
another question is that this projecrt is a private project for you, Can I update it ?

HI . @ASaiun Thanks for your feedback. I have added a new vpc resource to fix this issue and please check #11 .
The new release has been cut. Please check it.
If you have any problems, please submit the pull request or issue. Thanks.


⚠ Bofrost.nl has degraded performance

In f3ad4f1, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1132 ms

Resolved: Bofrost.nl performance has improved in 24f99e3.


Can plugins be used with this package?

Is there an intended way to use Prism plugins with this package?
You can get the plugins here: http://prismjs.com/download.html

Did you find a way to use plugins? I'm interested in adding line-numbers but didn't succeed.

Nope. Line numbers though might be achievable using only the CSS :before rule though.


运行wish相关函数时http error 405

以下是完整的错误提示：
======= RESTART: /Users/ZhikunWang/Desktop/VSCode/Python/115/115_wish.py =======
Traceback (most recent call last):
File "/Users/ZhikunWang/Desktop/VSCode/Python/115/115_wish.py", line 282, in
cookie_more_5GB = {key: value for key, value in cookie_all.items() if wish_remain(key, value)[1] > 0} # 筛选出大于5GB的心愿数量的账号出大于5GB的心愿数量的账号
File "/Users/ZhikunWang/Desktop/VSCode/Python/115/115_wish.py", line 203, in wish_remain
wishes = wish_list(cookie, type=1) # 计算本次执行完成后的未完成心愿数量，以及大于5GB的心愿数量
File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/p115client/tool/xys.py", line 74, in wish_list
ls = adds = check_response(client.act_xys_my_desire(payload))["data"]["list"]
File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/p115client/client.py", line 2444, in act_xys_my_desire
return self.request(url=api, params=payload, async_=async_, **request_kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/p115client/client.py", line 2092, in request
return request(url=url, method=method, **request_kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/httpx_request/init.py", line 225, in request
return request_sync(
File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/httpx_request/init.py", line 93, in request_sync
resp.raise_for_status()
File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/httpx/_models.py", line 829, in raise_for_status
raise HTTPStatusError(message, request=request, response=self)
httpx.HTTPStatusError: Client error '405 Not Allowed' for url 'https://act.115.com/api/1.0/web/1.0/act2024xys/my_desire?type=1&start=0&page=1&limit=1000'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405

升级到最新版p115client


How can I download ScanNet-GSReg?

Dear authors:
I met a problem when downloading the dataset:

How can I fix this problem?
Thank you!

I have fixed it. Please try it again.


Deploy previewnet relay instance using Helm

Problem
We currently lack a flow to easily deploy to integration using the new Helm Chart flow.
Solution
2 phase approach
Phase 1: Provide process to pick up from a release/x.y.z branch the newly tagged branch version and deploy to previewnet with manual steps
Phase 2: Provide self service option to describe desired deployment and have automated process kick it off.
Alternatives
No response

Exists. Helm changes need to be checked into main


不支持左图右文吗

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

你好，左图右字是怎么实现的？给个思路吧，谢谢

hi @cjecky plz open a new issue


Unable to compile submodule file

Can't compile my contracts with forge compile due to solidity-stringutils submodule.
When I try to run forge build, i get this error:
Error:
Compiler run failed
error[7858]: ParserError: Expected pragma, import directive or contract/interface/library/struct/enum/constant/function/error definition.
 --> lib/foundry-huff/lib/solidity-stringutils/strings.sol:1:1:
  |
1 | ./src/strings.sol
  | ^

The reason is this file:
https://github.com/Arachnid/solidity-stringutils/blob/46983c6d9462a80229cf0d5bab8ea3b3ee31066c/strings.sol
The same happens when I follow the "Getting Started" guide in "huff-project-template" repo.
How can I fix this?
Thank you.

I reinstalled Foundry using WSL and cloned the repo using WSL, and the issue disappeared.


Improve and update ResourceQuota for 1.3

This is the updates for quota for 1.3
@pmorie @ncdc - PTAL

@ncdc - poke for a quick review pass.

@ncdc - I think I addressed all your comments.  Thanks for the review, mind applying tech-lgtm so we can get this out the door before I am on vacation next week?

This PR now added the example (with updates to show new 1.3 features for services.*) quotas.
So this is the same content from https://github.com/kubernetes/kubernetes.github.io/pull/622 but with those tweaks added in 1.3.

A few questions/comments; otherwise, LGTM. I'll apply tech-lgtm once updates are pushed.

@ncdc @johndmulhausen - updates made

One last nit and you're good from my end :) Nice work, @derekwaynecarr !

A couple of small comments/questions

@johndmulhausen - last nit addressed.

Thanks a ton, @derekwaynecarr !


[Feature Request]: Implement Service Provider Google Support Custom End Point Url

Problem Description
In the current version, the service provider Google does not support custom endpoints, unlike the service provider OpenAI, which provides a custom endpoint URL.
Solution Description
Implementing support for custom endpoints in the service provider Google could greatly enhance performance. As an example, I've been operating this repository on Kubernetes, utilizing containers such as one-api and litellm across 13 pods. This configuration has shown to be more stable compared to deployments on Vercel or other platforms.
Alternatives Considered
No response
Additional Context
No response

Additional Note

[!NOTE]
This improvement could significantly enhance performance not only for web-based applications, but also for desktop versions.

OneAPI doesnt support Google Gemini API definition, you can diectly config the enpoint in custom api. As for model providers, the progress will be tracked in issue https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/issues/4030

OneAPI doesnt support Google Gemini API definition, you can diectly config the enpoint in custom endpoint(GPT like). As for model providers, the progress will be tracked in issue #4030

it's supported

I've been testing it running on kubernetes with better configuration
(base) root@H0llyW00dzZ:/# kubectl top pods
NAME                       CPU(cores)   MEMORY(bytes)
mysql-78mv3xmb37-hpmz5     5m           402Mi
one-api-j3laxb3o30-bz0gu   0m           46Mi

To be honest, I like the one-api RESTful APIs because they are written in Go, and they also utilize Gin.

@H0llyW00dzZ the base url of gemini api should be able to configured via GOOGLE_URL, have you encountered any issue while requesting with the variable?

The reason it can't be used in the desktop version is because it needs to be recompiled again into binaries.

also another reason, rust is so slow when compiling it

GOOGLE_URL

@H0llyW00dzZ Cool! The base url of gemini api should be able to configured via GOOGLE_URL, have you encountered any issue while requesting with the variable?

no, but env variable GOOGLE_URL can't be used in desktop version
for example in this one:

also desktop version it much stable when using custom end point url, plus smoothly unlike web-based applications

They are same thing eventually, you can try switching the endpoint to one-api servoce

GOOGLE_URL

@H0llyW00dzZ Cool! The base url of gemini api should be able to configured via GOOGLE_URL, have you encountered any issue while requesting with the variable?

no, but env variable GOOGLE_URL can't be used in desktop version
for example in this one:

also desktop version it much stable when using custom end point url, plus smoothly unlike web-based applications

They are same thing eventually, you can try switching the endpoint to one-api service

No, it doesn't work that way. When using the gemini-pro model, it utilizes Google as a service provider and it's mandatory to use this service.
https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/blob/main/app/constant.ts#L14C1-L14C77

@H0llyW00dzZ When requesting gemini api server, the client will check whether the googleUrl is configured first.If not set, will fallback to the url you just mentions.
https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/blob/08fa22749aea8f497811f684bd9c7ef68d698666/app/api/google/[...path]/route.ts#L20

Oh, for native clients,  bypassing a proxy service is still necessary.

@H0llyW00dzZ have you checked the developer console in development build, it much likely the requests being block by CORS right now.

@H0llyW00dzZ have you checked the developer console in development build, it much likely the requests being block by CORS right now.

no response

I am using one-api on k8s

when using service provider openai + model open ai it work, but gemini it doesn't work

in one-api it work while testing

also I am pretty sure because of this
https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/blob/08fa22749aea8f497811f684bd9c7ef68d698666/app/client/platforms/google.ts#L121C1-L129C8


Wake on touch documentation

Not sure I got the right syntax for links to other MSDN pages.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/TOC.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/WakeOnTouch.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/screenwake.md
:white_check_mark:Succeeded

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

@saraclay Ready for review.


Request for new term [self-limited neonatal seizures ]

Label
self-limited neonatal seizures
Synonyms
SeLNE
Synonym type
exact
Definition
A neonatal/infantile epilepsy syndrome where seizures start in the neonate between day 4 and 7 of life and are often unilateral clonic events that recur and may alternate sides from seizure to seizure. Seizures can be repetitive over hours to days. Seizures remit by 4-6 months of age. A proportion of those affected may have seizures in later life. The child is expected to have normal developmental progress. This is distinguished from familial neonatal epilepsy  on the basis of family history. These entities may have similar genetic etiologies, with de novo mutations responsible for the lack of family history in self-limited neonatal seizures.
https://www.epilepsydiagnosis.org/syndrome/self-limited-neonatal-overview.html
Parent term
neonatal/infantile epilepsy syndrome
Children term(s)
No response
ORCID Identifier
https://orcid.org/0009-0008-4499-6539
Website URL
No response
Additional comments
Related to https://github.com/monarch-initiative/mondo/issues/5957

@JoyeuseMuj thanks for reporting this, I'll work on this asap


Formatter sometimes removes space after . in uncurried functions

let f = (. x) => x
let a = f(. 1)
let b = f(. [1])
let c = f(. {"a": 1})
let d = f(. list{1})

Gets formatted to this:
let f = (. x) => x
let a = f(. 1)
let b = f(.[1])
let c = f(.{"a": 1})
let d = f(.list{1})

Note the space was removed in b , c, and d but not a.
I assume that keeping the space is the preferred format, but it seems like it should be consistent either way.

@johnridesabike Thanks for the report! Looking into this.

Fixed in master!


Bug Report - Transperancy issue

Environment
Windows build number: Microsoft Windows[10.0.18922.1000]
Windows Terminal version (if applicable): 0.2.1715.0

# Description

when I am using the windows terminal there is no transparency effect.

# Expected behavior

![windows-terminal-100799928-large](https://user-images.githubusercontent.com/52347812/60396081-8dce9a00-9b5a-11e9-80d4-3141e7bafbf0.jpg)

# Actual behavior

![Screenshot (6)](https://user-images.githubusercontent.com/52347812/60396085-97f09880-9b5a-11e9-80a1-60182693dba0.png)

You need to enable it in the settings JSON file, click on the settings button and it should take you there, find the command prompt settings and set useAcrylic to true

Thank You For Solving my doubt.


initial NPM layout

This PR sets up the initial layout for #68
With this PR, you can run npx yaci-devkit and it automatically works (even if you don't have the NPM package installed on your machine)
The NPM folder has two top-level items:

yaci-devkit-linux-x64 (which should be mostly code-generated)
yaci-devkit (which aggregates all the builds)

See inline comments in this PR for more details

Great job everyone!


Use BottomSheetModalProps instead of BottomSheetProps as navigation options

Hey there, thanks for this library, it has been very useful!
I came across an issue that this PR attempts to fix. I wanted to use the stackBehavior option but it is added by BottomSheetModalProps. Since this library's BottomSheetView component does use the BottomSheetModal abstraction from @gorhom/bottom-sheet, I believe this library's props should also inherit the same props.
I think this might also fix this issue:

https://github.com/th3rdwave/react-navigation-bottom-sheet/issues/5

Thank you!

Thanks!


Download button

A button that allows the user to download the graph after generating it, fully zoomed out.

I know that the graph by itself is an image and someone can just right click on it but you know, so it would be more for convenience if anything

Already works, right-click to save or copy to clipboard.

Will add the option hinting towards that possibility in the UI


DSL errors don't report the right file position

Till PR #3 has been merged, DSL errors don't report the right file position when comments are inserted inside Xml files.

I finally rewrote from scratch the Xml DSL parser. Now everything is handled in the right way, and the node/file positions (for throwing errors) are fully reliable.

Thanks a lot! I'm so happy! :)


test1

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Creating a test PR


RDFJson parser checks for null instead of not null in the parse method for reader

Look at line https://github.com/eclipse/rdf4j/blob/master/core/rio/rdfjson/src/main/java/org/eclipse/rdf4j/rio/rdfjson/RDFJSONParser.java#L157

It looks as if three different people have now independently implemented a fix for this. Only barthanssens has actually put up a Pull Request though.


Fix function declarations with shared return type

Parsing would fail on multiple function declarations with shared return types, for example: int multiple1(), multiple2();

thanks @arbruijn  for your fix.


Issue with iPhone to iPhone to call

Hello ISBX,
Thanks for such a greate demo,
I notice one issue here, When I trying to call iPhone to iPhone Audio does not work, you can not listen voice properly. it has some issue with Audio like humming and not clear at all. But it works great From iPhone to Web Calling.
Can you please give me some fix or workaround to fix this?
Thanks,
Faizan

Did you found the solution ?


Specifying a config file moves the project root

StackMaster always expects the templates folder to be in the same directory as the stack master config.
To reproduce:
├── Gemfile
├── Gemfile.lock
├── configs
│   └── stack_master.yml
├── parameters
│   ├── mystack.yml
│   └── us-west-2
│       └── mystack.yml
└── templates
    └── mystack.json

arecker@localhost:testproject$ bundle exec stack_master diff -c configs/stack_master.yml
Executing diff on mystack in us-west-2
StackMaster::TemplateCompiler::TemplateCompilationFailed Failed to compile /Users/arecker/Desktop/testproject/configs/templates/mystack.json.
 Caused by: Errno::ENOENT No such file or directory @ rb_sysopen - /Users/arecker/Desktop/testproject/configs/templates/mystack.json

This is expected behaviour. Do you have a use case for not storing stack_master.yml in the top level?

Hey Patrick,
We're planning on keeping a lot of configs in the same repository within
a top level "configs" folder.  Cosmetics aside, shouldn't this tool use
the working directory as the project root, rather than getting it from
the path to the stack master config?  Otherwise, the "-c" option is more
like a "--specify-project-root" option.
Hope that makes sense - I haven't had any coffee yet.

Ah - now that I look at it, this is probably just another manifestation of #161.

#161 looks like it might solve your problem. I'll try and roll it out tomorrow (AEST)

Great!  You're the best - thanks.


Timer needs to have adjustable max count

Timer has fixed max count. that's not great for game

I screwed this one up, it is configurable but instead of each flipflop cascading to the next, they just feed back into themselves. Also, this doesn't even work I think oops

timer should work now hopefully


feat: partial code generation for multiple targets

Closes partially #1079
Summary of Changes
Partial code generation now works for multiple targets instead of just one.

@SmiteDeluxe You can now pass a list containing the names of your target placeholders to  services.runtime.Runner.executePipeline. Then you can just dump your additional code into the pipeline and don't need to change the existing code.


Rename use_grpc into enable in config

enable in context of [farcasterd.grpc] should be enough and maybe more intuitive.

Should do the same for auto_fund


encoding issue in hsn_hisco converter

Hi, there's an encoding issue with the hsn_hisco.py converter. The script runs fine, but virtuoso doesn't recognize the output as proper RDF.
To reproduce the error, run the script and run 'rapper -c -i turtle '. (rapper can be installed via brewer).
you'll find some trial code trying to fix the issue commented out in hsn_hisco.py

The file is likely to contain whitespace at beginning/ending of lines, which iribaker doesn't really appreciate. Thank you @LaurensRietveld ! Solved with commit


try non protected build with path changes

@sallyom's suggested sollution

something doesn't sit right with this-I'm going to go back to why it was originally failing... also, can you give the absolute path to converter? You exec-d in and found the current workdir of the base image, right?

Confirmed this works, linting and merging.


fix(es/minifier): Fix node-fetch

Description:
Related issue:

https://github.com/vercel/next.js/issues/55682

It seems like this is not a bug of the minifier. I'll try patching `node_modules a bit.

This was not a bug of SWC minfiier


enable travis for pull requests to master

For some reason travis builds are not triggered for PRs. Trying to enable them.

Is there a specific need for it to build with Travis? I'm not sure I understand the benefit to having Travis with this, at the moment.

@mindreeper2420 It runs the tests for every pull request and we can see the status in Github. So if e.g. someone forgets to update the snapshots this would catch it.

Ok, sounds good. That'd be a great thing to have in the PRs.

@mindreeper2420 Automatic tests should be working now. You can see the details by clicking on Show all checks -> Details. I also added the yarn.lock file to the repo as suggested here: https://yarnpkg.com/lang/en/docs/yarn-lock/#toc-check-into-source-control
Does that look ok to you?

@pb82 @mindreeper2420 We removed it because we where having issues on the build environments they kept getting a permission error.  If that's fix then we should go ahead and add it back.

@pb82 It was an openshift issue we where seeing when trying to build the application.  It was fixed in this PR https://github.com/integr8ly/tutorial-web-app/pull/67 .  It should be fine to check it in now.


Position bug using Fancy Zones with multiple monitors and repositioning one of the monitors

Environment
Windows build number: [Version 10.0.19041.329]
PowerToys version: 0.19.1
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

I have two monitors positioned side by side. One monitor is landscape, the other is portrait. I had previously (i.e. before booting the system and installing PowerToys) logically bottom-aligned them in Windows display settings (i.e. the portrait monitor was flush with the bottom of the landscape one and extended above the landscape one) and FancyZones operated as expected. I then logically top-aligned them in Windows Settings, and then without rebooting or logging out I tried to use FancyZones snapping on the portrait monitor with the result that the window snapped off the top of the monitor.
After rebooting FancyZones then operated as expected again.
Expected behavior

FancyZones snapping should use the current logical alignment of multiple monitors.
Actual behavior

FancyZones snapping appears to use the logical alignment from when the system was last booted.
Screenshots

@bukbukbukark
thanks for reporting the bug, we fixed it and the fix will be available in 0.19.2
Fixed by https://github.com/microsoft/PowerToys/pull/4800


Add PostgreSql to the database section.

[Enter feedback here]
This was added yesterday to the site under Databases section to the Azure portal.
Add postgresql to this list:
Databases: SQL Database, Synapse SQL Pool, Cosmos DB, Azure Database for MySQL, PostgreSql, and Azure Cache for Redis

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: cb367617-af60-4995-2c8d-43c2c1d5664b
Version Independent ID: 98db794f-0dcd-4c65-8a1d-747ef501b051
Content: Improve reliability of your business-critical applications using Azure Advisor recommendations and the reliability workbook. - Azure Advisor
Content Source: articles/advisor/advisor-how-to-improve-reliability.md
Service: advisor
GitHub Login: @ikhapova
Microsoft Alias: ikhapova

I figured out how to do the pull request so I think it should be updated already.
Thanks,
Jeff
From: ManoharLakkoju-MSFT @.>
Sent: Tuesday, November 14, 2023 10:26 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Jeff Pigott @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Add PostgreSql to the database section. (Issue #117058)
@wjpigotthttps://github.com/wjpigott
Thanks for your feedback! We will investigate and update as appropriate.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/117058#issuecomment-1810609493, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUTYXEJSQLPBDYMWGTOQO5DYEOLTJAVCNFSM6AAAAAA7K45HOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJQGYYDSNBZGM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@wjpigott - Thanks again for bringing this to our attention and updating the doc. It will be live once it's approved and merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

#reassign:jenniferlee-ms


Lights undim when video ends

How to make the lights go back to 100% when the show automatically comes to an end.

I would like to see this feature too! :)

It doesn't do that already? I have to admit that I rarely let a movie run to the very end without hitting stop at some point during the credits but I just assumed once the player reported that the video was over (ended/stopped) the plugin would turn the lights back on?

Nope, doesn't do it.
On Apr 20, 2017 3:00 PM, "hstamas"<EMAIL_ADDRESS>wrote:

It doesn't do that already? I have to admit that I rarely let a movie run
to the very end without hitting stop at some point during the credits but I
just assumed once the player reported that the video was over
(ended/stopped) the plugin would turn the lights back on?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mpolednik/script.kodi.hue.ambilight/issues/60#issuecomment-295859633,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANAsqPWBnbx1YdqTpYnyrAKTJBwYvnTSks5rx6tegaJpZM4NBGrj
.

Correct it does not. I agree that when you are watching a film, it is hardly ever left to run to the end, but when you're watching a TV show, for example, it is likely to happen.

Correct
On Apr 20, 2017 3:36 PM, "benstechtips"<EMAIL_ADDRESS>wrote:

Correct it does not. I agree that when you are watching a film, it is
hardly ever left to run to the end, but when you're watching a TV show, for
example, it is likely to happen.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mpolednik/script.kodi.hue.ambilight/issues/60#issuecomment-295873493,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANAsqIKWuzbu_v5cn6---tPAPe7cpPGvks5rx7OngaJpZM4NBGrj
.

I think this is s bug relating to the checking of the playlist length before a tv show or movie has ended
If you comment out these lines (138 and 139) of default.py which is:
    if self.playlistpos < self.playlistlen-1:
        return

then it works fine
perhaps it relates to playlistpos should that be playlistlen?

Yup, @dw20155 is right. playlistpos was added in from #18 in https://github.com/mpolednik/script.kodi.hue.ambilight/commit/c1d72cba41f667b4b24861ea31dc5e8d8d6c9a77#diff-e87f4dd869f897586689ccfd0fa643d5R92 but only partially removed by @mpolednik in https://github.com/mpolednik/script.kodi.hue.ambilight/commit/51dfb710a71e83493dc8a71b826a0a95446e91ee#diff-e87f4dd869f897586689ccfd0fa643d5L89. Given playlistpos no longer exists those two lines should just be removed.
I've created #70 to remove the broken lines.


cmake/flac: bump to version 1.3.3 and update build integration

Update flac from 1.3.2 to 1.3.3 (https://github.com/xiph/flac/releases/tag/1.3.3)
Use flac's CMakeLists.txt to simplify the build integration

Merged.


Use print mode with length in validate_sni debug

Currently, this debug message will unsafely read until a null character is detected. This is changed to use the string with length option for printing.

Ignore this and delete if possible, making new one without useless commits.


Most ergonomic way for client=custom_client to dispatch between default or custom clients?

Situation:

for some models (examples: ollama_ex.py , vllm_ex.py ), we need to specify client= in decorator
what if we would like to provide there client=my_client_dispacher, so my_client_dispacher for some values of model would return default client , and for other , one of few custom clients?
that way I could allow e.g. user to select model via dotenv (.env) or other way?

relaying on default client for most models, and for some (matching patterns), to route them to custom_defined_clients... (e.g. local or shared ollama server etc)

@gwpl
To clarify, you don't need to specify client= for ollama models if you use this code:
import ell

ell.init(verbose=True, store='./logdir')
ell.models.ollama.register(base_url="http://localhost:11434/v1")

# in terminal run ollama list to see available models
@ell.simple(model="llama3.1:latest", temperature=0.1)
def write_a_story():
    return "write me a story"

Everything else should use the default OpenAI client instance.
If you're looking to parameterize the model kwarg that is used for a particular LMP (like write_a_story), you could define a variable for the model kwarg. I believe you can also override this parameter when you invoke it with write_a_story(model="llama3.2"),

Sure!
(btw. do ell.config.register_model("foo",...) overwirte earlier resolution for "foo" https://docs.ell.so/core_concepts/models_and_api_clients.html )
Here I was thinking about more sophisticated setups,
that ofc I can make by making ollama api compatible proxy that would have resolution logic,
but I thought that maybe I could register own dispatcher (e.g. ell.config.register_providers_dispatcher( my_dispatcher(fallback=ell.config.get_current_providers_dispatcher())) )

do ell.config.register_model("foo",...) overwirte earlier resolution for "foo" https://docs.ell.so/core_concepts/models_and_api_clients.html

They should yes.
If you look at the provider and model files you can do a lot more custom stuff, maybe along the lines of what you’re describing.
I’m having a hard time seeing the end goal you want to achieve. If you could paint more of a picture for me there I may be able to help with a particular implementation that achieves it.

Setting custom dispacher, like I mentioned:
ell.config.register_providers_dispatcher( my_dispatcher(fallback=ell.config.get_current_providers_dispatcher())) )

could be good when playing on small scale with setup utilizing either load balancing, failover or just resolution of unregistered models.
However for more production setup, very likely it should use suggested by you, e.g. Ollama or just ell.config.via_proxy(...) to make everything regardless of model go via proxy and do all the magic inside the proxy.


config incoherence between sequelize and sharebandit

The SB code and example conf use:
{
  "db" : {
    "dialect": "postgres",
    "port": 5432,
    "user": "sharebandit",
    "pass": "sharebandit",
    "database": "sharebandit"
  },

but to create the db
 NODE_ENV=db sequelize db:migrate --config config/config.json
it expects
{
  "db" : {
    "dialect": "postgres",
    "port": 5432,
    "username": "sharebandit",
    "password": "sharebandit",
    "database": "sharebandit"
  },

I did duplicate so I have both user-username password-pass as a workaround
Am I missing something obvious? could we rename the keys on config to be similar with sequelize?

No, and yes. Fixed it: https://github.com/MoveOnOrg/sharebandit/pull/48


Browser caching does not work with range request set for Firefox

Dear PDF.JS contributors,
When range requests are set and http server configured to cache contents with public, max-age=31536000, immutable, browser caching does not work on Firefox but strangely it works on Chrome or Safari.
Attach (recommended) or Link to PDF file here: not file specific
Configuration:
Web browser and its version: 73.0
Operating system and its version: mac os x 10.15.3
PDF.js version: 2.2.228
Is a browser extension: no

Steps to reproduce the problem:

clear the browser cache
go to https://app.fays.io/fd7be64d-ec78-4731-9dff-7b9c8088acf9 and open the developper tool
refresh the page, the range request works fine but they are not cached on Firefox

What is the expected behavior?
On Chrome, when one refreshes the page, the range requests have been cached.

What went wrong?
On Firefox, the range requests are different and when one refreshes the page, those requests are not cached.
More surprising, Firefox performs in this example one more range request, there is a 1.2MB download.

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): https://app.fays.io/fd7be64d-ec78-4731-9dff-7b9c8088acf9
I suspect that what causes the issue is the Range header that has not the same behavior in Firefox or Chrome ?
Maybe here there is something missing
https://github.com/mozilla/pdf.js/blob/794744c3fad3411a886b697cd3c4c6cb96725880/test/unit/node_stream_spec.js#L50-L70

When opening an issue, please provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md
Furthermore, the likelihood that someone will assist you is a lot greater with a small and self-contained example (rather than a larger viewer); please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us on the IRC channel

@Snuffleupagus Of course, I have updated the description.

Also,
When disableAutoFetch is false and disableStream is false, Firefox caches correctly the request with response code 200 but not 206.. with the same file.

Given that caching is controlled by the browser itself, I'm not really sure that this is actually an actionable bug for the PDF.js library.
If anything, it sounds more like a (possibly general) bug in Firefox and I'd thus suggest reporting it in Bugzilla instead.

I found other online services where range requests are cached such that https://www.jango.com/music/Skarow for example.

Yes, this is probably best reported at Bugzilla because it seems like a browser issue that we cannot resolve. Thanks!

For follow up: https://bugzilla.mozilla.org/show_bug.cgi?id=1615698


Add Snyk scan step

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Added here #416


picture: add Vec methods

This adds some functions that exposes the inner data.
Since the inner Cow is Cow::Owned, into_owned() should be a cheap no-clone/no-allocation call.
Also, most libraries seem use bytes() or as_bytes() instead of data() but that'll break everyone's code, so, maybe not worth it.

Ah, I see.
Requested changes were made.

Thanks!


wait for scylla service to be available

wait for scylla service to be available, before update configuration and restarting it

@glommer I tested this on small servers.
Please test with bigger servers, where the "--cpuset 1-31 --smp 31" are used.
If it work, we can drop/reduce the 2 min wait in provisioning_db.yaml

Hi
Apparently it works.
All nodes are now responding to cql and exporting its metrics


Uncaught Exception: listen EADDRINUSE <IP_ADDRESS>:5672

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.2.4
Time: Fri May 27 2016 10:13:15 GMT 0200 (Vest-Europa (sommertid))
Error:
listen EADDRINUSE <IP_ADDRESS>:5672
Error: listen EADDRINUSE <IP_ADDRESS>:5672
    at Object.exports._errnoException (util.js:890:11)
    at exports._exceptionWithHostPort (util.js:913:20)
    at Server._listen2 (net.js:1234:14)
    at listen (net.js:1270:10)
    at net.js:1379:9
    at _combinedTickCallback (internal/process/next_tick.js:77:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #325


Fix create script --no-open not adding script to managed scripts

I noticed an issue where running marathon create script --no-open fails to add script.swift to managed scripts. Running marathon list shows script not listed and checking scriptManager.managedScriptPaths returns 0 elements.
Is this a bug?

This is not a bug, as Marathon has no reason to start managing a script if the user doesn't want to open it 🙂 The only reason Marathon starts managing a script is to be able to generate a package for it, and this is only needed if it should either be run, installed, or edited using Xcode.

Thank you


UPDATES... kind of 🐜

Hello!  It has been a long time since I've been here, and the reason is... wait for it... ants -
Or, to be more specific, necessity to work on other projects because of ants.  A camera enclosure I've been running had an ant infestation that not only destroyed the hardware I designed inside of the enclosure, but also destroyed the camera somehow - to the point where a fully-functional 4K camera can no longer record in 4K because of... reasons - it sees the 4K shot, it sets it up like normal, but refuses to write data for 4K (HD is fine however)... so I'm guessing something inside the memory of the camera (the buffer perhaps) is shot.  Due to that, I've spent the last few months working on a completely new system (both engineering completely new hardware, software and layout logistics) that has kind of become a white whale of a project - one that I have needed to see through to the end.  I've done it, designed an entirely new PCB, written an entirely new (and much better, honestly) daemon in C, etc. - but it's taken 2 months of complete focus that has taken me away from other projects like NeewerLite-Python.  One plus-side to that is I've had the chance to code with an ESP32, and see the kinds of things it can do (originally I had a cobbled together PCB that I designed running a ATTiny chip connected to a Pi Zero, I simplified the entire thing using just an ESP32) - so I might actually be able to port a version of NeewerLite-Python (it wouldn't be Python any more, but meh) to an ESP32 using the built-in WiFi and Bluetooth, which I think was a vision @fribse had years ago for a project like that based on a microcontroller instead of a PC.
Ha, tl;dr - I'm still here.  Haphazard, but here 😊

Here's a picture of the new board, if anyone's interested ~

Hey @taburineagle
That sounds very interesting. Yes, my though was just that as I know it the CPU usage is miniscule, so something like micropython might be able to do the trick?
Glad that you got your project on the way.
Btw. did implement any of those 'busy' signs in the files for the webbased? I was contemplating looking into updating it, if something new has appeared.

@fribse - I'll have to check into MicroPython!  I've actually never used that variant, but it looks interesting.  C would still work, I'm guessing - semantically, I'd just have to change the name for the ESP version to something else, as just "NeewerLite" has already been taken 😄  ESP-NLP... or something...
I have actually added that in a while back - it might have gotten lost in the fray of updates - I pushed a busy signal update in the latest commit to the WIP-HTTP-Server-Mods branch...

Ha ha, uh, the big change in naming.
Ahh, now I found it, ok, I'll try and fetch that and update the two files :-)
Thankyou!

I just tried the 'new' version, but I get a list "index out of range" when I replace the two files.
I tried moving the 'light_prefs' content to a backup folder, but that didn't help.
Jul 20 18:15:51 neewerlitepi systemd[1]: Started Run NeewerLite-Python HTTP Daemon as a service.
Jul 20 18:15:54 neewerlitepi python3[573]: Traceback (most recent call last):
Jul 20 18:15:54 neewerlitepi python3[573]:   File "/opt/NeewerLite-Python/NeewerLite-Python.py", line 3897, in <module>
Jul 20 18:15:54 neewerlitepi python3[573]:     loadCustomPresets() # if there's a custom mapping for presets, then load that into memory
Jul 20 18:15:54 neewerlitepi python3[573]:   File "/opt/NeewerLite-Python/NeewerLite-Python.py", line 1976, in loadCustomPresets
Jul 20 18:15:54 neewerlitepi python3[573]:     if currentParams[1] == 120: # we have a new-style list of parameters, so copy them as-is
Jul 20 18:15:54 neewerlitepi python3[573]: IndexError: list index out of range

Hmm, interesting... are you still using the older custom preset file structure?  The one from #81?  When I tested it with the old-to-new style converter, everything worked here on my end, but there may have been an eccentricity I didn't notice.  Are you saying if you have no light_prefs folder in the NeewerLite-Python folder, it still presents that error?

I just emptied the light_prefs folder.
I tried removing it entirely now, and now it starts.
I've asked it to scan for lights, and now it shows this:

However, it doesn't exit, and I can't trigger anything?
If I do a restart of the service, it restarts, and then stops again a second later

Looking at that screenshot, it looks like it just successfully connected to CE:D9:49:A3:1F:F7 (it shows this at the top), but the table still shows lights aren't completely linked yet.

Are you saying if you let it look for lights and link them, the message at the top doesn't go away if you let it run for a longer period? (the HTTP Server busy message just shows the last message received from the program when it's busy, so in the screenshot above, it's still working on connecting to the lights and isn't 100% ready for anything else yet)...


[WIP] Increasing test coverage for caveats.rb

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

@mistydemeo

Looks like there's a couple of typoes in the keg_only tests:
https://travis-ci.org/Homebrew/brew/jobs/244744936#L287 - undefined method to_receive'https://travis-ci.org/Homebrew/brew/jobs/244744936#L299 -undefined method to_receive'

There is something wrong with the build: https://travis-ci.org/Homebrew/brew/jobs/246014857#L99

@mansimarkaur Any news here?

One of the tests is failing. allow(g.sbin).to receive(:directory?).and_return(true) isn't working correctly.

🚢


rfc: anthropic cache usage

Alternative to #25644
What do we want to do with anthropic cache token counts and UsageMetadata?

do nothing for now: UsageMetadata is meant to be standard across models and we dont know what other providers will do with caching. plus the info is there is AIMessage.response_metadata. main issue here is rn cached input tokens dont show up anywhere (neither in input_tokens nor total_tokens)
just add cached input tokens to total_tokens, so at least there's some way to figure out that those tokens exist
store cache token counts as their own keys on AIMessage.usage_metadata for anthropic outputs (current implementation in this pr). easy to implement and makes this info easily accessible to user, but will this lock us into to something we can't break in the future?
add cache token counts to existing "input_tokens" key (anthropic's data.usage.input_tokens does not take into account cached tokens so this isn't double counting). not useful for estimating pricing but useful for general token counting
add something like a "cost_adjusted_input_tokens" key that counts tokens in terms of costs (1.5 * cache_creation + 1 * input + 0.1 * cache_read). useful for estimating prices, but makes it a little harder to figure out when you've got cache hits/misses. is that important?

One more thing I'm facing right now is PropmtTemplate - I can't find a way to use it with Anthropic cache 'cause it wipes out the 'cache_control' attribute from the text block.
https://github.com/langchain-ai/langchain/blob/92abf62292e10a837f1e83cd1d9b4b4ab66dc94f/libs/core/langchain_core/prompts/chat.py#L521
Here it just extracts text and throws all the rest away
Are there any ideas / workarounds?

One more thing I'm facing right now is PropmtTemplate - I can't find a way to use it with Anthropic cache 'cause it wipes out the 'cache_control' attribute from the text block.
https://github.com/langchain-ai/langchain/blob/92abf62292e10a837f1e83cd1d9b4b4ab66dc94f/libs/core/langchain_core/prompts/chat.py#L521
Here it just extracts text and throws all the rest away
Are there any ideas / workarounds?

thinking of adding support for something like this, any thoughts? https://github.com/langchain-ai/langchain/pull/25674

lgtm
so far I just made a runnable lambda that injects cache_control after template compilation. this might be a bit cleaner for me since I substitute models and e.g. groq doesn't like that sort of dict messages and I have to strip them anyway
Does that make sense to control in templates? some param to either keep dicts or flat everything down

lgtm so far I just made a runnable lambda that injects cache_control after template compilation. this might be a bit cleaner for me since I substitute models and e.g. groq doesn't like that sort of dict messages and I have to strip them anyway Does that make sense to control in templates? some param to either keep dicts or flat everything down

Hi @mrdrprofuroboros , could you share your approach with PromptTemplate? thanks :((

Oh, sorry, I missed your message
sure, here's what I came up with, rather hacky, but works for me

def to_cached(content: str | List[Dict[str, Any]]) -> List[Dict[str, Any]]:
    if isinstance(content, str):
        return [{
            "type": "text",
            "text": content,
            "cache_control": {"type": "ephemeral"},
        }]
    if isinstance(content[-1], str):
        content[-1] = {
            "type": "text",
            "text": content[-1],
            "cache_control": {"type": "ephemeral"},
        }
    else:
        content[-1]["cache_control"] = {"type": "ephemeral"}
    return content

def add_cache_control(compiled_chat: ChatPromptValue) -> ChatPromptValue:
    """
    Anthropic supports maximum 4 blocks with cache_control so we'll set
    - 1 on tools
    - 1 on the first and last system block
    - 1 on the last even 5th message
    """
    system_messages = []
    other_messages = []

    for message in compiled_chat.messages:
        if isinstance(message, SystemMessage):
            if not system_messages:
                system_messages.append(SystemMessage(to_cached(message.content)))
            else:
                system_messages[0].content.append(message.content)
        else:
            other_messages.append(deepcopy(message))

    if system_messages:
        system_messages[0].content = to_cached(system_messages[0].content)

    messages = system_messages + other_messages
    last_cached = (len(messages) - 2) // 5 * 5 # never set on the last message since it's constantly changing
    messages[last_cached].content = to_cached(messages[last_cached].content)
    return ChatPromptValue(messages=messages)

### and then

if isinstance(model, ChatAnthropic):
    model = RunnableLambda(add_cache_control) | model

Hey @baskaryan, can we add this info to the llm_output which is meant to be unreliable provider-specific info?

closing in favor of https://github.com/langchain-ai/langchain/pull/27087

Hey @baskaryan, can we merge this branch? We can explicitly warn that this data is not standardized and one could use it on their own risk of deprecation

will have a standardized format out in https://github.com/langchain-ai/langchain/pull/27087! should land and release later today

That’s great news, thank you!

That’s great news, thank you!

out in langchain-anthropic 0.2.2

That’s great news, thank you!

out in langchain-anthropic 0.2.2

Sorry 0.2.3! Had to patch so that usage_metadata['input_tokens'] was a sum of all input tokens, including cache read and cache creation tokens


HDDS-2318. Avoid proto::tostring in preconditions to save CPU cycles.

What changes were proposed in this pull request?
Avoiding proto::toString in OzoneManagerServerSideTranslatorPB.java
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-2318
How was this patch tested?
Ran TestOzoneRpcClient which executes this code path.

Thank You @arp7 and @anuengineer for the review.
I have committed this to the master.


got get impossible: https://www.fknsrs.biz SSL certificate expired

Your SSL certificate is expired and we can't go get the library. Can this be fixed please?

Fixed! Apparently I forgot to restart nginx last time I updated my certificate. Thanks for pointing it out!

That was quick, thank you!

Looks like this happened again


[G7T5-170] Lower Z-index of login button

Description
https://is212g7t5.atlassian.net/browse/G7T5-170
Login Button is no longer visible for modals.

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
NA
Checklist:

[x] I have added the appropriate labels to my PR
[x] My code follows the style guidelines of this project
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@jonathantan1425 this was your change right


Unpatched upstream vulnerabilities in mbedtls library

There are several unpatched upstream vulnerabilities in mbedtls library.

CVE-2018-9988
Brief description: Buffer over-read in ssl_parse_server_key_exchange() that could cause a crash on invalid input.
upstream patches: https://github.com/ARMmbed/mbedtls/commit/027f84c69f4ef30c0693832a6c396ef19e563ca1, https://github.com/ARMmbed/mbedtls/commit/a1098f81c252b317ad34ea978aea2bc47760b215
NVD link: https://nvd.nist.gov/vuln/detail/CVE-2018-9988

CVE-2018-9989
Brief description: Buffer over-read in ssl_parse_server_psk_hint() that could cause a crash on invalid input.
upstream patches: https://github.com/ARMmbed/mbedtls/commit/5224a7544c95552553e2e6be0b4a789956a6464e, https://github.com/ARMmbed/mbedtls/commit/740b218386083dc708ce98ccc94a63a95cd5629e
NVD link: https://nvd.nist.gov/vuln/detail/CVE-2018-9989

CVE-2018-0487
Brief description: Allows remote attackers to execute arbitrary code or cause a denial of service (buffer overflow) via a crafted certificate chain that is mishandled during RSASSA-PSS signature verification within a TLS or DTLS session
upstream patches: https://github.com/ARMmbed/mbedtls/commit/28a0c727957990ac655cbe40c7eb20b7ef01167d
NVD link: https://nvd.nist.gov/vuln/detail/CVE-2018-0487
Advisory: https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2018-01

CVE-2018-0488
Brief description: When the truncated HMAC extension and CBC are used, allows remote attackers to execute arbitrary code or cause a denial of service (heap corruption) via a crafted application packet within a TLS or DTLS session
upstream patches: https://github.com/ARMmbed/mbedtls/commit/992b6872f3ca717282ae367749a47f006d337a87, https://github.com/ARMmbed/mbedtls/commit/464147cadc694379b7717afb7b517fe05cdb323f
NVD link: https://nvd.nist.gov/vuln/detail/CVE-2018-0488
Advisory: https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2018-01

CVE-2017-18187
Brief description:  There is a bounds-check bypass through an integer overflow in PSK identity parsing in the ssl_parse_client_psk_identity() function in library/ssl_srv.c.
upstream patches: https://github.com/ARMmbed/mbedtls/commit/83c9f495ffe70c7dd280b41fdfd4881485a3bc28
NVD link: https://nvd.nist.gov/vuln/detail/CVE-2017-18187

If possible, upgrade to the latest mbedtls 2.8.0 version

Thank you for pointing this out.  Amazon FreeRTOS is currently using mbedTLS version 2.7 which is behind the latest version.  We are looking into upgrading versions.

Hello,
We have patched mbed TLS with the dot release of Amazon FreeRTOS 1.2.4.  The version of mbed TLS is no 2.8.
FOr further information, please see the change log at:
https://github.com/aws/amazon-freertos/blob/v1.2.4/change_log.txt


Do not inherit repositories in addons

An addon repository does not necessarily want the same repos or exclusions as its base, and vice versa.  For example, ELN should really not include Extras, and a lot of unwanted packages that we want to filter from Buildroot or Rawhide may still be eligible for ELN Extras.

/cc @tdawson

I think this will work.
I'll merge it.


Inner vim function for installing gounit binaries

Implemented kind of "vim-go" function for downloading gounit binaries through vim. So now you can just connect gounit-vim with your plugin manager and simply use :GoUnitInstallBinaries to download gounit into your $GOPATH. It checks if gounit is already installed and if not it is using go get underneath. (I decided to add this command and not to use auto call check of the function when plugin loads)
In the future this functionality can be simplified to use less code, but for now this should work fine.
Also fixed broken links in README file and added exta information there.

@ipriver thanks a lot for your contribution!