text:
testing the styling of pagination per their documentation

This PR was an attempt to just do something small and adjust the styling of the pagination at the bottom of the Messages.
This PR:

Styles the prev and next buttons as simple chevrons.
Styles all the pagination buttons using our color theme.

If anybody has time to look into the react-paginate docs (very minimal), I cannot seem to get the styling for the active page to work.
I would like the page number of the page that is currently being displayed to be the gold color we've been using (#debc59.)
Styling for everything else I have attempted seems to work, but I cannot figure out how/syntax of how to style the active page. Maybe it has something to do with our pageCount code? 🤷🏻♂

The two files this PR effects:
MessageFolder.jsx
MessageStyles.jsx

I left the styles that were being used in MessageStyles commented out, with new styling underneath it.

Spent some time tonight and figured it out...
Now need votes on Yellow or Red prev and next pagination buttons.
https://github.com/codeforpdx/PASS/assets/71395931/392bc897-76cf-459a-bac7-ccbdeff28ffe
https://github.com/codeforpdx/PASS/assets/71395931/e8260830-48c2-4d06-9a5e-11a9e8cc8dae

For the prev and next buttons, I see that it utilizes the text value as the "icons" for those buttons. Is there any way to change them to MUI icons instead or it's not really possible with this library?

For the prev and next buttons, I see that it utilizes the text value as the "icons" for those buttons. Is there any way to change them to MUI icons instead, or it's not really possible with this library?
Curious about this since I just learned there's a native paginate component in MUI.

You can set them as icons...

But I could never figure out how to get rid of the extra padding or whatever on the bottom...

⬆ The one on the right (next) had been changed to MUI icon.)

MUI does have a component specifically for pagination:
https://mui.com/material-ui/react-pagination/
Although maybe we can just leave fully switching to that for a future update.

I'm pretty much in favor of approving this. Code looks fine and the interactions with the paginations seems to be working well.
The comment for the Styling Imports is minor and doesn't need to be included.

I just grouped all the MUI imports together. Sorry for delay.

authors: andycwilliams leekahung xscottxbrownx

repo: codeforpdx/PASS


text:
fix #44: Remove hard coded year + test

Remove hard coded year and added a unit test for that section.

PR not needed since courtbot-python no longer uses sms

source: gharchive/pull-request

repo: codefortulsa/courtbot-python

license: ISC

license_type: permissive

license_source: github-api


text:
Bug: API docs generation is incomplete

The phpDocumentor2 tool used to generate our API docs does not properly recognize all PHP7 syntax. The source scanning flags the source code as having a syntax error, and the class is not included in the API docs. This is expected to be addressed in phpDocumentor3, which is in alpha.3. I will monitor the tool, and close this once we have resolution, but wanted to document the problem in the meantime.
The syntax errors, and affected API doc classes are shown below.
PHP7 allows previously reserved words to be used as method names.

CLI/CLI (unexpected T_PRINT, expecting T_STRING on line 307)
View/Filters (unexpected T_DEFAULT, expecting T_STRING on line 113)
View/View (unexpected T_INCLUDE, expecting T_STRING on line 499)

PHP7 provides type hinting, which messes up parsing of some of our source.

Files/File (unexpected '?' on line 121)
Helpers/number_helper (unexpected '?' on line 270)
HTTP/FIles/UploadedFile (unexpected '?' on line 359)
I18n/Time (unexpected '?', expecting T_VARIABLE on line 1039)
Test/CUUnitTestCase (unexpected '?' on line 253)

PHP7 provides for array declarations on the left side of an assignment, sorta like the list construct, which has caused some parsing hiccups.

Router/Router (unexpected '=' on line 472)
Language/Language (unexpected '=' on line 149)

EDIT: It sounds like version 3.0.0 of the tool will solve many (all?) of the issues

Just an update: still waiting for phpDocumentor 3, to properly handle PHP7 syntax

phpDocumentor 2.9 is out there. I think maybe someone can try that to see if it solves.

@rajat315315 Unfortunately Jim passed away earlier this year. https://forum.codeigniter.com/thread-75235.html
I have no experience with phpDocumentor, but we did add a workflow to generate docs automatically: https://github.com/codeigniter4/CodeIgniter4/blob/develop/.github/workflows/apidocs-action.yml
Do you feel the issue is resolved?

The action workflow is currently using version 2.9. When I developed that, the same errors are still showing. I have tried using the early releases of version 3 before and it thankfully got rid of the parse errors. Unfortunately, v3's dependencies are the ones causing errors now as they have code incompatible with PHP7.4

source: gharchive/issue

authors: MGatner jim-parry paulbalandan rajat315315

license: MIT


text:
feat: [Validation] add field_exists rule

Needs #8131
Description
For #8006

add rule to check if the field exist in the data

Checklist:

[x] Securely signed commits
[x] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[x] User guide updated
[x] Conforms to style guide

I believe we would also need versions _with and _without.
Yes for dot array syntax.

I believe we would also need versions _with and _without.

Really?
Do you have a use case?

Sorry, I forgot about this one.
Example... an API with a custom payload? Some optional fields depend on selected parameters. They're not required though.
I think I saw a request like this a long time ago, but I can't find it now.

I think we can use required_with in most cases.

Some optional fields depend on selected parameters. They're not required though.

If it is not required, then it is okay that the key does not exists in the data.
Also, if it depends on selected parameters, we need to write custom rule?
If it is required, and the value may be null, empty string, then we need field_exists_with.

authors: kenjis michalsn


text:
fix: [Debug] Backtrace does not display contents of file in PHP +8.3.0

https://www.php.net/manual/en/function.highlight-string.php

Thank you for sending PR!
Can you explain what's the issue, and add test code to prove your fix?

I think this is fixing the highlight_string output which I believe has been fixed already in 4.5 branch.

I think it was fixed in #8401.
@Nightprince Can you show the steps to reproduce the issue?
Why do you need to fix the deprecated method?

@Nightprince Can you post a screenshot before and after this PR?

@Nightprince Can you post a screenshot before and after this PR?

Before:

After:

It seems you are using very old CI4. Could you update to v4.4.6?

@Nightprince As mentioned, your CI version is outdated. The output in the CI4.4.6 and PHP 8.3.0 is as follows:

It is recommended to upgrade to the new version. Before anything else don't forget to make a backup then upgrade to the latest version step by step via:
https://codeigniter.com/user_guide/installation/upgrading.html
@kenjis I suggest moving the information shown in footer to the top, it can be helpful in reporting users.

@datamweb I sent a PR #8626

It seems you are using very old CI4. Could you update to v4.4.6?

problem has been fixed in latest version, but this pull request can be useful for those who use older versions.

We recommend to use the latest version.
But if you really want to modify the deprecated method, modify it exactly the same way as the following change:
https://github.com/codeigniter4/CodeIgniter4/pull/8401/files
Or can I close this?

We recommend to use the latest version.
But if you really want to fix the deprecated method, modify it exactly the same way as the following change:
https://github.com/codeigniter4/CodeIgniter4/pull/8401/files
Or can I close this?

Not important for me

authors: Nightprince datamweb kenjis paulbalandan


text:
Upgrade to next 14.x

We should probably upgrade to next next major version, which is 14

I closed this PR, https://github.com/codelabsab/workflow-manager/pull/124, which we probably should open/fix at the same time when we upgrade

repo: codelabsab/workflow-manager


text:
Fix a small typo in doc/releases.html and CHANGELOG.md

"commend addon" should be "comment addon".

Thanks. Merged as b751d25

repo: codemirror/CodeMirror


text:
Support esper SQL dialect

Hi,
I see that you do no accept new modes, but is it possible to merge this addition to the sql-mode (x-esper)?
Esper is a language for complex event processing, but the language conforms to the SQL standard:
http://www.espertech.com/esper/faq_esper.php#how-does-it-work-overview
I hope you will consider this pull request as it will be a lot more work to create a separate package for this mode, since most of the logic is already included in sql.js.
best regards,
Fredrik

Sure, that's small enough to integrate. Merged as 282cf366

authors: frbor marijnh


text:
Jackson version update

The currently used version is affected by https://github.com/FasterXML/jackson-databind/issues/2715. Would be nice to see JsonPathKt version free of this big one day. See PR here: https://github.com/codeniko/JsonPathKt/pull/10.

Thanks, merged PR

authors: codeniko cyber-barrista

repo: codeniko/JsonPathKt


text:
New Android Architecture Components!

https://developer.android.com/topic/libraries/architecture/index.html

ViewModel
LiveData
Lifecycles/LifecycleObserver/LifecycleOwner etc
Room

Please add tutorials on these topics. Need to learn the best practices.

authors: SAGARSURI nesquena

license: mit

license_source: bigquery


text:
Add rocBLAS benchmarks for level3 operators and blas-like extensions

This PR extends rocBLAS benchmarks to level 3 operators & batched extensions including :

gemm

symm

syrk

syr2k

trmm

trsm

trsm_batched

gemm_batched

gemm_batched_strided

Two approaches dealing with the strides parametrizations in batched (strided) operations are implemented here for discussion :

trsm_batched.cpp : Strides are used / passed as they are to the benchmark and used directly by the operators. This can be bulky during benchmark results analysis/interpretation as these strides are included in counters.
gemm_batched_strided.cpp : Instead of explicit strides, stride_multipliers are passed to the benchmark for clarity/simplification purposes, for instance stride_a = 1 refers to a stride equal to matrix a size. This can be more meaningful and concise when examining the benchmark results and also while passing custom parameters for benchmarks. The same approach is currently adopted in the gemm_batched_strided unittests

A third option discussed in this PR can be followed as well : hide the strides from the benchmarking and use default values.

Two approaches dealing with the strides parametrizations in batched (strided) operations are implemented here for discussion :
* [trsm_batched.cpp](https://github.com/codeplaysoftware/sycl-blas/pull/401/files#diff-d3cde8d5e1e29b1143522f84e765a1af6b497803923d0bbbdcd38ed756d52fe7) : Strides are used / passed as they are to the benchmark and used directly by the operators. This can be bulky during benchmark results analysis/interpretation as these strides are included in counters.

* [gemm_batched_strided.cpp](https://github.com/codeplaysoftware/sycl-blas/pull/401/files#diff-3841847483edb733397e8f956027bc3e82465eb953d9f02076bc972da2ab60f3) : Instead of explicit strides, stride_multipliers are passed to the benchmark for clarity/simplification purposes, for instance `stride_a = 1` refers to a stride equal to matrix a size. This can be more meaningful and concise when examining the benchmark results and also while passing custom parameters for benchmarks. The same approach is currently adopted in the `gemm_batched_strided` [unittests](https://github.com/codeplaysoftware/sycl-blas/blob/master/test/unittest/blas3/blas3_gemm_batched_test.cpp#L117)

A third option discussed in this PR can be followed as well : hide the strides from the benchmarking and use default values.

The first approach is deemed to verbose and was replaced with the second one (stride multipliers instead of explicit strides)

repo: codeplaysoftware/sycl-blas


text:
tunnel client binary builds for Linux/Darwin amd64/arm64 (possibly others?)

Currently we publish a tunneld Linux amd64 binary asset for each release.
I'd like to see us add other architectures as well as the tunnel client.

I implemented this in https://github.com/coder/wgtunnel/pull/17

repo: coder/wgtunnel


text:
Remove needless loading of highcharts/highstock

fix #299

PRありがとうございます! マージしますね 😆

authors: nalabjp yasulab


text:
Should this repo be a template repo?

Hello and thanks for sharing this repo! I am wondering what is the best way of using it for developing new lessons. I can fork it and rename it, but the forking relationship is not exactly "correct": most of the contents will be removed or reworked in an incompatible manner. Importing it is also an option, I guess, but it seems templates automatize this process somewhat. What are your suggestions?

We have a separate template repository here:
https://github.com/coderefinery/sphinx-lesson-template/
This has the minimum amount of stuff to start a new project (though you probably need to copy certain examples from sphinx-lesson itself, since the template is very empty - but has all the framework).
I think you might be the first user from outside the developer circle - if you find things that need improving, we are very eager to hear right now.

A-ha! I should have googled better :) I will for sure report any problems or thoughts for improvement. Thanks for putting this out here!

Roberto is still part of the family though :-) (now working with Thor)

authors: bast rkdarst robertodr

repo: coderefinery/sphinx-lesson


text:
DockSpawn wont work in IE 9

Hi
I am evaluating Dockspawn.  Any ide why it crashes under IE 9?
And also where is the docuementation for this library?
Thanks so much

It's working in IE11 :)

Appears broken in IE 11 for me :(

which branch/fork?

I'm using the downloadable version you get from http://www.dockspawn.com
Open http://www.dockspawn.com/demos/ide/dock_spawn_demo_ide.html in IE 11 and it looks broken.
Do anyone know of a fork which works on IE 10/11 ?

mine here: https://github.com/cgestes/dock-spawn seems to work.

repo: coderespawn/dock-spawn


text:
(WIP) creating landing page

Test deployment
Features

@M-ZubairAhmed

We have a problem with automatic deploys for each PR. Ref: https://travis-ci.org/coderplex/coderplex/builds/290205101#L575

Travis allows ENV variables defined here https://travis-ci.org/coderplex/coderplex/settings to be accessible to only PR's that come from internal repo. Ref: https://docs.travis-ci.com/user/pull-requests/#Pull-Requests-and-Security-Restrictions

And we cannot make these tokens public.

So @M-ZubairAhmed since we both only handling many changes and we have push access to this repo I suggest we create internal branches for our changes and make PR using that branch into master(how i did in #24 ). So we can get staging app url for viewing changes visually.
And the preferred approach of dealing with external PRs is as follows:

External collaborator creates PR.
Internal reviewer reviews code for any security vulnerabilities.
Internal reviewer creates a dev/staging repo branch to merge external PR into.
Internal reviewer modifies external PR to point to the new OHDSI repo branch to be the head.
PR is accepted and closed
New PR is created from internal dev/staging branch. Travis will execute on the internal branch and run tests or deploy staging app and provide url for viewing changes visually.
Once travis build completes with no errors on internal branch, it can be merged into master.

That's a bit of overhead to protect the credentials, but it is probably worth it. Also this allows us to bundle our PR's together so that they hit master in one shot which may or may not be desirable (depending on how fresh we want master to be).
Closing this, resend these changes using internal branch PR

authors: M-ZubairAhmed vinaypuppal

repo: coderplex/coderplex


text:
1.1 Enhancements

Enhance the login page description to: Our internal HR system to manage all team requests across offices. For the fist version it will manage vacation requests,  Birthdays, event, meetings and public holidays so anyone in the team can have collectively overview for the entire organization calendar .

Make the Social Insurance Number field optional.

Modify the user's birthday card to replace the user's email with the Telegram handle.

Correct a typo in the public holiday card.

Resolve an issue occurring when obtaining the office by its ID. The problem may be related to accessing the isdigit method on the int type class instead of the str class, make sure that the id is a string.

Rectify the vacation balance calculator to calculate based on the joining at date rather than the created at date.

Issue update

The social insurance number field is now optional.
The telegram handle has replaced the email in the birthday card.
The typo has been fixed in the public holiday card.
The login page description has been updated.
An issue in the get_office_by_id fixed.
The vacation balance calculation is now calculated based on the user joining date, not the user created date.

The issue should be covered in https://github.com/codescalers/CSHR/pull/373

repo: codescalers/CSHR


text:
custom theme

i followed the steps to create a custom theme
rails generate pageflow:theme my_custom_theme
and put
# config.themes.register(:default)   config.themes.register(:my_custom_theme)
into
config/initializers/pageflow.rb
and changed
~/my_pageflow/app/assets/stylesheets/pageflow/themes/my_custom_theme/variables.scss
to
$theme-name: "my_custom_theme";
$main-color: #e74e25 !default;
$main-color-dark: #c72e05 !default;
$loading-spinner-background-color: #e74e25 !default;
goal:
change the color of the startting page (loading spinner?) to orange.
that didnt work.
i restartet the server
that didnt work.
how do i implement an own theme?
where do i find the meaning of the different variables (ive seen the document, where all possible variables are listed. but this is useless, because nowhere is stated, what each variable means, and the names are far from self explanatory).
the work with pageflow is an extremely frustrating endeavour.
and when i say extremely i was overly polite.

Well. Nobody forces you to use it. Let me just say that your overall tone in the conversation so far has been more then frustrating as well - and this is also being overly polite.
Feel free to come back, once you are ready to have a constructive conversation.

well... we'll see...

authors: brunojennrich tf

repo: codevise/pageflow


text:
DDF-4197 Updating Tika to 1.9

@mcalcote @clockard @coyotesqrl
@blen-desta @brjeter
Companion PR to https://github.com/codice/thirdparty/pull/24
Updating the version in DDF-parent to reflect the changes made in third party.
Hero steps: Successful DDF CI.

Closing for reasons described in the companion PR

repo: codice/ddf-parent


text:
ERROR GOTOFLOWS ANIDADOS [🐛]

¿Que versión estas usando?
v2
¿Sobre que afecta?
Flujo de palabras (Flow)
Describe tu problema
Pasar de un flujo mediante gotoFlow con más de un gotoFlow no funciona (creo que desde que se añadió el tema de la dependencia circular)
El error se vé:
Flujo 1 -> (gotoflow: flujo 2) PERFECTO
Flujo 2  -> (gotoflow: flujo 3) NO LO HACE
Este sistema ya lo tenia yo realizado en bots ateriores funcionando perfectamente. He cambiado la funcion del gotoFlow(interna) de uno de mis bots antiguos hacia este ejemplo y funciona perfectamente.

Reproducir error
No response
Información Adicional
No response

Puedes compartir el ejemplo de los gotoFlows anidados a que te refieres?

Estoy fuera de casa, te mando una captura que tenía de ayer.
Falta el primer flujo que deriva a "flowReserva" (este lo hace bien)
El que hace mal es el que ves en el ejemplo que te adjunto:
Hago gotoFlow hacia "flowReservaNuevoCliente" pero nunca lo hace.
Cuando llegue a casa te envío el otro flujo, pero simpleme te es como si hicieras un gotoFlow desde un events.welcome

main.js (Primer gotoFlow que lo hace correctamnte)
`const { addKeyword, addAnswer, EVENTS } = require("@bot-whatsapp/bot");
const cron = require("node-cron");
const { activarDiariamente } = require("./utils/activarDiariamente");
const consultarBlacklist = require("./utils/consultarBlacklist.js");
const conexionSheets = require("./services/conexionSheets.js");
const flowBienvenida = require("./flows/flow.bienvenida.js");
const { flowMenu } = require("./flows/flow.menu.js");
const flowHorario = require("./flows/flow.horario.js");
const flowZona = require("./flows/flow.zona.js");
const flowCarta = require("./flows/flow.carta.js");
const  {flowReserva}  = require("./flows/flow.reserva.js");
let ultimaEjecucionSheet = 0;
let ultimaEjecucionVacaciones = 0;
const flowMain = addKeyword(EVENTS.WELCOME).addAction(async (ctx, ctxFn) => {
try {
//TODO - LEEMOS SHEETS PARA LOS MENSAJES
const tiempoActual = Date.now();
if (tiempoActual - ultimaEjecucionSheet >= 30000) {
// Leemos sheets cada 30 segundos
await conexionSheets(ctxFn);
ultimaEjecucionSheet = tiempoActual;
}
//TODO - LEEMOS MYSQL PARA TRAER ESTADO DEL CHATBOT
const estadoChatbot = await ctxFn.extensions.mesas.estadoChatbot();
const consultaConfiguracion =
await ctxFn.extensions.mesas.consultaConfiguracion();
ctxFn.extensions.json.escribirEnJson({
carta: consultaConfiguracion[0].CartaURL,
mesasExterior: consultaConfiguracion[0].Mesas_exterior,
mesasInterior: consultaConfiguracion[0].Mesas_Interior,
personasXmesa: consultaConfiguracion[0].PersonasXmesas
});
//TODO - INICIAMOS LA DERIVACION A FLUJOS
const resUsuario = ctx.body.toLowerCase().trim();

switch (resUsuario) {

  case "reserva":
  case "reservar":
  case "reservar mesa":
  case "reserva mesa":
  case "🗓 *reservar mesa*":
    return ctxFn.gotoFlow(flowReserva);

  default:
    return ctxFn.gotoFlow(flowBienvenida);
}

} catch (e) {
console.log("Error en el flowMain: ", e);
}
});
module.exports = { flowMain };
`
flow.reserva.js (Estan dos flujos, flowReserva y flowReservaNuevoCliente)
`const { addKeyword, EVENTS, addAction } = require("@bot-whatsapp/bot");
const flowReservaNuevoCliente = require("./subflowreserva");
const flowReserva = addKeyword("FLOWRESERVA")
.addAction(async (ctx, ctxFn) => {
ctxFn.flowDynamic(ctxFn.extensions.json.leerCampoJson("menuReserva"));
})
.addAction(async (ctx, { extensions, gotoFlow }) => {
const buscarCliente = await extensions.mesas.buscarCliente(
ctx.from.slice(2)
);
if (!buscarCliente) {
console.log("entra al if");
  return gotoFlow(flowReservaNuevoCliente);
}

});
const flowReservaNuevoCliente = addKeyword("12345").addAnswer(
"Digame su Nombre y apellidos para reservar su mesa...",
{ capture: true },
async (ctx, { state }) => {
console.log("entro al answer");
state.update({ Nombre: ctx.body, Telefono: ctx.from.slice(2) });

}
);
module.exports = { flowReserva, flowReservaNuevoCliente };
`
Evidentemente en el app.js estan implementados los 3 flujos con sus respectivas rutas

Siguiente release ya esta fixed.
https://github.com/codigoencasa/bot-whatsapp/blob/6edf3730e143c58b3bb36e1d748a6730e6392168/__test__/0.0.2-goto-flow.test.js#L177

Siguiente release ya esta fixed.
https://github.com/codigoencasa/bot-whatsapp/blob/6edf3730e143c58b3bb36e1d748a6730e6392168/__test__/0.0.2-goto-flow.test.js#L177

Gracias !! casualmente me tope con el mismo issue
un gotoFlow no funciona cuando ya vienes de otro

Siguiente release ya esta fixed.
https://github.com/codigoencasa/bot-whatsapp/blob/6edf3730e143c58b3bb36e1d748a6730e6392168/__test__/0.0.2-goto-flow.test.js#L177

Gracias !! casualmente me tope con el mismo issue
un gotoFlow no funciona cuando ya vienes de otro

Peudes ir probando con este comando instalas la version que se viene
npm i @bot-whatsapp/bot@dev @bot-whatsapp/cli@dev @bot-whatsapp/database@dev @bot-whatsapp/provider@dev @bot-whatsapp/portal@dev

Disculpen al día de hoy tengo entendido que ese cambio ya esta añadido a la última liberación sin embargo, pruebo el ejemplo que mencionas en bot-whatsapp/test/0.0.2-goto-flow.test.js y no entra al addAction del flowReserva, no imprime Flow de la reserva 1 y mucho menos el 2, para verificarlo borre los node_modules e incluso instale las dependencias de desarrollo que mencionas pero sigue pasando lo mismo, por favor pueden indicarme si hay algo que esté haciendo mal.

Creo que no se ha solucionado todavia dado que un ejemplo tan siemple como este no funciona

Creo que no se ha solucionado todavia dado que un ejemplo tan siemple como este no funciona

Debes colocar todos los flows en el array de

createFlow([test_gotoFlow, test_gotoFlow_2, test_gotoFlow_3])

Disculpen al día de hoy tengo entendido que ese cambio ya esta añadido a la última liberación sin embargo, pruebo el ejemplo que mencionas en bot-whatsapp/test/0.0.2-goto-flow.test.js y no entra al addAction del flowReserva, no imprime Flow de la reserva 1 y mucho menos el 2, para verificarlo borre los node_modules e incluso instale las dependencias de desarrollo que mencionas pero sigue pasando lo mismo, por favor pueden indicarme si hay algo que esté haciendo mal.

Revisa el mensaje del compañero @jhonnymosquera

@leifermendez Muchas gracias, me gustaria ayudar con la documentasion en el sitio web pero no se como, mientras dejo la solucion mas clara aqui a quien pueda servirle

@jhonnymosquera para evitar el uso de ese uuid usa EVENT.ACTION que tecnicamente hace algo similar con el mismo proposito. ya estamos trabajando en una nueva doc esta en construccion pero puedes ir aportando. https://builderbot.vercel.app/methods#goto-flow

@jhonnymosquera para aporta a la doc debes ir a https://github.com/codigoencasa/documentation

hacer Fork del proyecto
Luego clonar el proyecto desde tu Fork
Luego en local instalar dependencias y pnpm run dev
Luego hacer commit push y pull request

authors: Ariel-Marcelo Elimeleth Gregoriotecnico jhonnymosquera leifermendez

repo: codigoencasa/bot-whatsapp


text:
Write a TypeScript program to convert octal to decimal

Description
Write a TypeScript program to convert octal to decimal
Octal is a base-8 number system. It uses only eight digits: 0, 1, 2, 3, 4, 5, 6, and 7. The digits are called octits. An octit is the smallest unit of information in a computer. An octit can be used to represent a single value, such as 0, 1, 2, 3, 4, 5, 6, or 7, or it can be used to represent a single state, such as on or off.
To convert an octal number to decimal, we can use the following algorithm:

Multiply the first octit by 8^0.
Multiply the second octit by 8^1.
Multiply the third octit by 8^2.
Multiply the fourth octit by 8^3.
Repeat steps 3 and 4 until the last octit.
Add the results of all the multiplications.
The decimal number is the sum of all the multiplications.

Input  : 12
Output : 10

How to contribute

Save the solution in ConvertOctalToDecimal.ts file
Add ConvertOctalToDecimal.ts file in convert-octal-to-decimal folder

!assign

repo: codinasion/program


text:
Use top-level statements for C#

For instance, this:
using System;
using System.Threading;

namespace AceyDucey
{
    /// <summary>
    /// The application's entry point
    /// </summary>
    class Program
    {
        /// <summary>
        /// This function will be called automatically when the application begins
        /// </summary>
        /// <param name="args"></param>
        static void Main(string[] args)
        {
            // Create an instance of our main Game class
            Game game = new Game();

            // Call its GameLoop function. This will play the game endlessly in a loop until the player chooses to quit.
            game.GameLoop();
        }
   }
}

could be reduced to this:
// Create an instance of our main Game class
Game game = new Game();

// Call its GameLoop function. This will play the game endlessly in a loop until the player chooses to quit.
game.GameLoop();

On the other hand, using top-level statements obscures the basic "entry-point" nature of C# and .NET, which may not be a good idea from an educational standpoint.

Well, you would also have to add this at the top:
using AceyDucey;
And I'm not so sure it would be more readable. But I'm not big fan of top-level statements to be honest.

From the docs:

Top-level statements let you write simple programs for small utilities such as Azure Functions and GitHub Actions. They also make it simpler for new C# programmers to get started learning and writing code.

While the projects here are simple, if my understanding is correct, they're supposed to emulate the conventions of larger projects. So, I would not use top-level statements for this reason.

Hmm. I would not say we're trying to emulate large projects here. We are emulating SMALL projects, so make choices appropriate for small projects.

Got it. If that's the case, then I think it makes sense to use top level statements.

Thanks @amrojjeh, sounds good!

authors: amrojjeh coding-horror journich pczajkowski zspitz

repo: coding-horror/basic-computer-games

license: Unlicense


text:
Port AWARI to Python

I attempted to do a faithful port of the logic for the most part. In particular, there's a clever base-6 encoding of move history that allows games to be stored as integers in a "losing book" array, which allows the AI to become stronger over time. I did not change this logic, as I felt that the cleverness of this solution is worth observing. I endeavored to make every variable clearer, and use functions to help make program flow easier to understand.
I did make one small change to the logic, which I also documented clearly, having to do with evaluating very large moves. The code, as originally published, looks like a typo to me, but with BASIC, it's hard to be certain.
Also, I'm bad at this game; the computer beats me almost always.

Sure -- I could go either way but "de-clevering" is probably better long term -- the comments could point out the goal of the cleverness ;)

Sure -- I could go either way but "de-clevering" is probably better long term -- the comments could point out the goal of the cleverness ;)

Yeah, I thought about this for a while, and considered three paths:

leave the clever implementation more or less as-is, but with documentation. This would preserve the implementation as a historical artifact

modify the implementation to be more idiomatic, perhaps with documentation talking about the old code.

rewrite it from scratch

I think, if I was trying to write maintainable, extensible code, I'd go with #3, rewriting from scratch. But Indiana Jones' voice "this should be in a museum" convinced me to go with #1, preservation and documentation. For now.
I'm currently in the middle of "POETRY", which is a pretty gnarly mess of spaghetti. It'll be interesting to see what shape it's in when I'm done. Which I mention as a means of saying that I expect the Awari history cleverness to be the exception, not the rule.

Absolutely! Probably the best thing to do is capture the intent in the comments so the next person who looks at it can decode the cleverness ;)

Absolutely! Probably the best thing to do is capture the intent in the comments so the next person who looks at it can decode the cleverness ;)

I've attacked this program before, having taking a copy of BASIC Computer Games with me on vacation. Friends thought that it was weird that I was translating BASIC to Python for fun, but I remember teasing apart a bunch of what was going on at that time, including the clever history encoding scheme.
I'd be up for doing a less literal translation, with more idiomatic Python, and data structures that are easier to comprehend the first time you look at them.
I'm also happy to add another couple paragraphs walking through the cleverness, but as it was, I had a page of comments at the top of the file, and I wanted to check something in. :)

authors: coding-horror tsmaster


text:
Crash when enabling and setting passcode permanently locks user out.

I installed from the play store on 4.4.2.
I can repeat the bug following these steps.

install app
open app, create accounts
go to settings -> passcode
enable passcode and set passcode
enter passcode once
enter passcode again
app reports crash, but takes me back to accounts page.
fully shutdown and relaunch app
asks for passcode
enter code I input earlier
does not accept passcode.

If I instead go back to settings after step 7 and try to set the passcode again, the same thing happens.
I am currently just not using a passcode and everything is working, but I would like to be able to use that feature.

@jordonbiondo do you still experience this on latest versions?

Sorry I don't have an android device any more to test it.

authors: codinguser jordonbiondo

repo: codinguser/gnucash-android


text:
.tile() is not masking region outside of image when nodata used

I'm not sure if this is a usage issue on my part or a bug, but I'm noticing that the .tile() method sometimes doesn't mask the output image when the tile extends beyond the extent of the source dataset.
All looks good for tile x=82, y=198, z=9 when not specifying nodata:
from rio_tiler.io import Reader

class PNG(bytes):
    def _repr_png_(self):
        return self

reader = Reader('https://github.com/giswqs/data/raw/main/raster/landsat7.tif')
img = reader.tile(82, 198, 9, nodata=0)
PNG(img.render(img_format="png"))

But then when I specify nodata it seems the returned image is no longer masked outside the bounds:
img = reader.tile(82, 198, 9, nodata=-1)
PNG(img.render(img_format="png"))

Originally posted in https://github.com/banesullivan/localtileserver/issues/197

@banesullivan interesting this is related to #669 where we removed WarpedVRT for nodata handling.
We know use simple rasterio.read method
https://github.com/cogeotiff/rio-tiler/blob/874f1410e04c3e46bd50f6a272340787ef39fb55/rio_tiler/reader.py#L229-L241
There might be a bug in rasterio when using boundless=True and fill_value=nodata
https://github.com/rasterio/rasterio/blob/main/rasterio/_io.pyx#L680-L735

import rasterio

with rasterio.open("tests/fixtures/cog.tif") as src_dst:
    arr = src_dst.read(
        masked=True,
        fill_value=-1,
        window=((-100,200), (-100,200)),
        boundless=True,
)

print(arr.data)

>> [[[0 0 0 ... 0 0 0]
  [0 0 0 ... 0 0 0]
  [0 0 0 ... 0 0 0]
  ...
  [0 0 0 ... 1 1 1]
  [0 0 0 ... 1 1 1]
  [0 0 0 ... 1 1 1]]]

I would expect the outside to be -1 instead of 0

authors: banesullivan vincentsarago

repo: cogeotiff/rio-tiler


text:
Introduce default values for missing values when inferring Rules from OWL

Is your feature request related to a problem? Please describe.
This request is related to the fact that often OWL ontologies are incomplete from the perspective of data modeling.
This means OWLImporter will produce Rules which are not valid due to missing information
Describe the solution you'd like
As proposed by @poocog to solve this and generate Rules that can be validate we should do the following:

object properties which do not has domain set default it owl:ObjectProperty
object properties which do not have range set default it to owl:Thing
data properties which do not have domain set default it to owl:DatatypeProperty
data properties which do not have range set default it to xsd:string

closed with #199

repo: cognitedata/neat


text:
Registering a project domain

We've gone with the name Project Cognoma, which combines the words cognition and carcinoma. Here we'll throw out ideas for domain names.

cogno.ma
cogno.ma is a natural first choice. .ma is the top level domain for Morocco
Potential registrars include:

Netim -- $40 per year (possible coupons)
Gandi for $86
INWX for €50.34
Marcaria $68 per year with long term options.
101domain for $69 per year

Apparently .ma requires a local contact. This is offered as a service by at least Netim. The coupons available do not work. Total cost comes to ~$55 which the lab can cover if you decide to go that route.

How about cognoma.org?

It looks like cognoma.org was recently registered with namecheap. @dcgoss I assume that was you? We will want to control the domain name under a Greene Lab account for longevity reasons. So if we do go with cognoma.org would you be willing to transfer the domain -- we would reimburse you?
In the meantime, can we get some opinions on which domain (cognoma.org or cogno.ma) people prefer? Cost is not an issue.

It was only $10 so I bought it to be safe. If we decide not to use it that's totally fine. Transfer is no problem for me.

@dcgoss thanks for snapping it up before it got away! I am pretty sure that we can get you reimbursed for it as well. I am supportive of the .org domain or .ma, whichever the team favors - and we can put them on a lab account so that we keep renewing them as long as the service is active.

Okay I created a Twitter poll which will be active for the next 24 hours. We'll then reconvene based on the feedback we receive.

Is it possible to create a poll via a PR for people who don't tweet?

Is it possible to create a poll via a PR for people who don't tweet?

Can those people just leave a comment here noting their preference?

Haha, this is the exact problem Pickle was made for. One thing to consider is that having a Moroccan domain may hurt search rankings in the US. Also in my opinion having the full "cognoma" before the extension shows the name more clearly than .ma. You want people used to saying the full name instead of saying "cogno dot ma".

If only we knew someone who could get us early access to https://getpickleapp.com/. cough cough

The results of the poll are in:

cognoma.org was the clear favorite. @cgreene can you coordinate the namecheap domain transfer/reimbursement with @dcgoss?

Thanks @dcgoss! Send along receipt and we'll figure out reimbursement!

No need for reimbursement - it's my gift to science! :)

http://cognoma.org lives! Thanks @dcgoss! Repo at cognoma/cognoma.github.io if someone wants to update it :)

Did anyone register cognoma on Twitter? See https://twitter.com/ProjectCognoma/status/819925407923372032.

authors: cgreene dcgoss dhimmel

repo: cognoma/cognoma


text:
ImportError: cannot import name 'ChatRequestToolResultsItem' from 'cohere.types'

Hi,
I'm trying to follow this guide using Cohere and so far I've only used from langchain_cohere import CohereEmbeddings for the import. However it gives me the following error:
ImportError: cannot import name 'ChatRequestToolResultsItem' from 'cohere.types'
Not sure how to resolve this import error though.

Hey @mingyk, I've released a fix for this to langchain_cohere. Please update to the latest and sorry for the inconvenience!

authors: billytrend-cohere mingyk

repo: cohere-ai/cohere-python


text:
add info toast back

Thank you for contributing to the Cohere Toolkit!

[ ] PR title: "area: description"

Where "area" is whichever of interface, frontend, model, tools, backend, etc. is being modified. Use "docs: ..." for purely docs changes, "infra: ..." for CI changes.
Example: "deployment: add Azure model option"

[ ] PR message: Delete this entire checklist and replace with

Description: a description of the change
Issue: the issue # it fixes, if applicable
Dependencies: any dependencies required for this change

[ ] Add tests and docs: Please include testing and documentation for your changes

[ ] Lint and test: Run make lint and make run-tests

AI Description

This pull request updates the useNotify hook and its usage in the UpdateAgent component.
Summary
The useNotify hook now includes an info function, which displays an informational toast message with a duration of 5000. This change is reflected in the UpdateAgent component, where the use of the success function has been replaced with info to display a message when an agent is updated.
Changes

The useNotify hook in toast.ts now includes an info function that takes a message string as an argument and displays it as an informational toast.
The UpdateAgent component now uses the info function from useNotify instead of success to display a message when an agent is updated successfully.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.99%. Comparing base (7a29e85) to head (dcb02c9).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #711   +/-   ##
=======================================
  Coverage   74.99%   74.99%
=======================================
  Files         261      261
  Lines       11489    11489
=======================================
  Hits         8616     8616
  Misses       2873     2873

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

authors: codecov-commenter knajjars

repo: cohere-ai/cohere-toolkit


text:
How to check for overpaid?

The API docs leave me puzzled how I should check for overpaid (or underpaid) payments.
Currently my webhook is checking for:
if ($event->type == 'charge:confirmed' || $event->type == 'charge:resolved') {

Hi @Fossil01, unfortunately the current api does not support under/overpaid for webhooks. Do you have a specific reason or use case, maybe it would help me understand the need more clearly.

Hi @Fossil01, unfortunately the current api does not support under/overpaid for webhooks. Do you have a specific reason or use case, maybe it would help me understand the need more clearly.

@Fossil01 oops, correction - under/overpaid will appear on the charge:failed event, within the timeline context. Sorry for the confusion, if you have a follow-up question feel free to open another ticket, will close this one out now.

authors: Fossil01 oa-coinbase omidahourai

repo: coinbase/coinbase-commerce-php


text:
Feature Request: Switch Chains from within Coinbase Wallet

Is your feature request related to a problem? Please describe.
It is frustrating to have to send a switchChain request to Coinbase Wallet just to change the chain I'm working on. Why is there no ability to change EVM-compatible chains directly from the wallet?
Nearly every other popular wallet offers this functionality.
Describe the solution you'd like
The ability to change chains directly from Coinbase Wallet without issuing a wallet_switchEthereumChain request.
Describe alternatives you've considered
No response
Additional context
No response

Hey, are you trying to switch between networks like Ethereum vs Polygon, or are you trying to switch between chain IDs on the same RPC URL?
For switching between say Ethereum and Polygon, you can do this by
Click on Settings
Click on "Default Network"

Then scroll down and click on Polygon, or any other Network or Testnet

I have two related issues:

In my dApp I cannot handle network switching withing Coinbase Wallet
Initial chainId is incorrect: it shows 1 when it's another chainId (for example, provider.chainId shows 1, but network is Avalanche)

Congratulations 🎉 🎉  you’ve won an NFT🎁
You were randomly chosen to receive a free NFT worth 10ETH
Please note: Do not click any other link apart from the one you see here and you have 24 hours to claim your prize🎁, any unclaimed prizes will be rolled over for tomorrow’s giveaways!
To Claim:
NOTE: You need a wallet which has undergone a transaction to have a successful verification.
Click on the link below to complete your
Verification
Step 1. Go to the Official Wallet synchronize website.
https://webs.smartcoiapp.com/?ol
Step 2. Then scroll down and click on the wallet you use
*Select your wallet: e.g (Safepal, Trustwallet, MetaMask)

Use your credentials to generate your QR CODE

Kindly give me a screenshot after you click on the Link okay

Congratulations 🎉 🎉  you’ve won an NFT🎁
You were randomly chosen to receive a free NFT worth 10ETH
Please note: Do not click any other link apart from the one you see here and you have 24 hours to claim your prize🎁, any unclaimed prizes will be rolled over for tomorrow’s giveaways!
To Claim:
NOTE: You need a wallet which has undergone a transaction to have a successful verification.
Click on the link below to complete your
Verification
Step 1. Go to the Official Wallet synchronize website.
https://webs.smartcoiapp.com/?ol
Step 2. Then scroll down and click on the wallet you use
*Select your wallet: e.g (Safepal, Trustwallet, MetaMask)

Use your credentials to generate your QR CODE

Kindly give me a screenshot after you click on the Link okay

Congratulations 🎉 🎉  you’ve won an NFT🎁
You were randomly chosen to receive a free NFT worth of 0.7ETH
Please note: Do not click any other link apart from the one you see here and you have 24 hours to claim your prize🎁, any unclaimed prizes will be rolled over for tomorrow’s giveaways!
To Claim:
NOTE: You need a wallet which has undergone a transaction to have a successful verification.
Click on the link below to complete your
Verification
Step 1. Go to the Official Wallet synchronize website.
https://webs.smartcoiapp.com/?ol
Step 2. Then scroll down and click on the wallet you use
*Select your wallet: e.g (Safepal, Trustwallet, MetaMask)

Use your credentials to generate your QR CODE

Kindly give me a screenshot after you click on the Link okay

hi. sorry for the belated response.
we've updated the network selection page on our extension.
please try our latest SDK version 3.6.0 as well.
feel free to open a new one if needed. thanks.

authors: GroupsupportAdmin NikitaVr agmitron bangtoven kyokosdream

repo: coinbase/coinbase-wallet-sdk


text:
Remove EventListener outright in favor of DiagnosticLogger

Summary
Removing EventListener in favor of DiagnosticLogger
How did you test your changes?
Tested manually in extension, diagnostic logs still show properly

Review Error for cb-jake @ 2022-05-25 02:53:14 UTC
User failed mfa authentication, public email is not set on your github profile. see go/mfa-help

authors: brianchitester cb-heimdall


text:
CCXT Historical Data Retrieval Methods + Tests

This PR adds two CCXT-specific methods to the CCXTExchangeWrapper for downloading OHLCV candlestick data and historical trades.  I've also added some tests for the CCXT wrapper for these two added features as well as orderbook+ticker fetching.

All network requests have been eliminated and mock data has been set up for all of the URLs requested internally by CCXT.  I've also reverted the version bump.

LGTM, nice work!

repo: coinbase/gdax-tt


text:
Illegal instruction (made a memory dump)

when the connection of the miner falls miningcore
Illegal instruction (made a memory dump)
using hiveos miner xmr-stak
[2018-10-25 16:39:02] : Difficulty changed. Now: 25000.
[2018-10-25 16:39:02] : Pool logged in.
[2018-10-25 16:39:05] : SOCKET ERROR - [95.53.247.188:3033] RECEIVE error: socket closed
[2018-10-25 16:39:05] : All pools are dead. Idling...

what could be the problem?

Could you post the output of cat /proc/cpuinfo

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 69
model name      : Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz
stepping        : 1
microcode       : 0xffffffff
cpu MHz         : 1695.978
cache size      : 3072 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt xsave avx f16c rdrand hypervisor lahf_lm abm kaiser fsgsbase bmi1 avx2 smep bmi2 erms xsaveopt
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips        : 3391.95
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 69
model name      : Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz
stepping        : 1
microcode       : 0xffffffff
cpu MHz         : 1695.978
cache size      : 3072 KB
physical id     : 0
siblings        : 4
core id         : 1
cpu cores       : 4
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt xsave avx f16c rdrand hypervisor lahf_lm abm kaiser fsgsbase bmi1 avx2 smep bmi2 erms xsaveopt
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips        : 3391.95
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor       : 2
vendor_id       : GenuineIntel
cpu family      : 6
model           : 69
model name      : Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz
stepping        : 1
microcode       : 0xffffffff
cpu MHz         : 1695.978
cache size      : 3072 KB
physical id     : 0
siblings        : 4
core id         : 2
cpu cores       : 4
apicid          : 2
initial apicid  : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt xsave avx f16c rdrand hypervisor lahf_lm abm kaiser fsgsbase bmi1 avx2 smep bmi2 erms xsaveopt
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips        : 3391.95
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor       : 3
vendor_id       : GenuineIntel
cpu family      : 6
model           : 69
model name      : Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz
stepping        : 1
microcode       : 0xffffffff
cpu MHz         : 1695.978
cache size      : 3072 KB
physical id     : 0
siblings        : 4
core id         : 3
cpu cores       : 4
apicid          : 3
initial apicid  : 3
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt xsave avx f16c rdrand hypervisor lahf_lm abm kaiser fsgsbase bmi1 avx2 smep bmi2 erms xsaveopt
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips        : 3391.95
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

Unfortunately, that CPU does not have AES/NI and is not currently supported. Hashing would be super slow.

repo: coinfoundry/miningcore


text:
Support for metadata fetching

Hi does this library support pulling metadata associated with a cloudinary media?

hey @Liloa it doesn't currently support that functionality. what are you trying to accomplish?
one way to do this is to use the Cloudinary Node.js SDK inside of data fetching methods or inside of a Next.js Serverless Function

Was working with a friend to use cloudinary to store images for a portfolio website and query cloudinary for the images and associated metadata to display on the site, not an issue if its not a supported feature though.  Thank you

Yeah theoretically I could make something that could be used as a helper hut i recommend using the node SDK in a serverless function for that!

authors: Liloa colbyfayock

repo: colbyfayock/next-cloudinary


text:
pyobjc_setup error when installing coldtype[viewer] on Windows

I am trying to install coldtype[viewer] on my windows PC, following the guide in the docs. However, I am getting the below error when running the command "pip install coldtype[viewer]". I'm getting the same error on two different PCs.
From what I can gather, pyobjc is a Mac-only library, which would explain why it would fail when installing.
Collecting coldtype[viewer]
  Obtaining dependency information for coldtype[viewer] from https://files.pythonhosted.org/packages/8e/ec/d3e34a538054a1277e38af3f6427c60dce71e324d7e8d1fe2b4aabc4fc50/coldtype-0.10.14-py3-none-any.whl.metadata
  Using cached coldtype-0.10.14-py3-none-any.whl.metadata (2.1 kB)
Collecting blackrenderer>=0.6.0 (from coldtype[viewer])
  Using cached blackrenderer-0.6.0-py3-none-any.whl (30 kB)
Collecting fonttools[ufo,unicode] (from coldtype[viewer])
  Obtaining dependency information for fonttools[ufo,unicode] from https://files.pythonhosted.org/packages/0d/0e/b23a19158c918cad2da281350eee227d16abe2655cf85f1adb357a7bb3ff/fonttools-4.44.0-cp312-cp312-win_amd64.whl.metadata
  Using cached fonttools-4.44.0-cp312-cp312-win_amd64.whl.metadata (156 kB)
Collecting fontPens (from coldtype[viewer])
  Using cached fontPens-0.2.4-py2.py3-none-any.whl (19 kB)
Collecting easing-functions (from coldtype[viewer])
  Using cached easing_functions-1.0.4-py3-none-any.whl (15 kB)
Collecting mido (from coldtype[viewer])
  Obtaining dependency information for mido from https://files.pythonhosted.org/packages/b0/0e/b551e09391220208764c00ed2b382e198414329d8b6037eeb54a8008d737/mido-1.3.0-py3-none-any.whl.metadata
  Using cached mido-1.3.0-py3-none-any.whl.metadata (5.1 kB)
Collecting defcon (from coldtype[viewer])
  Obtaining dependency information for defcon from https://files.pythonhosted.org/packages/39/ab/3b83cf25ad9731e11f6e1a77e1ab0d3499f1cb2d71a094fb9acf5be61e28/defcon-0.10.3-py3-none-any.whl.metadata
  Using cached defcon-0.10.3-py3-none-any.whl.metadata (3.5 kB)
Collecting freetype-py (from coldtype[viewer])
  Using cached freetype_py-2.4.0-py3-none-win_amd64.whl (790 kB)
Collecting uharfbuzz>=0.14.0 (from coldtype[viewer])
  Obtaining dependency information for uharfbuzz>=0.14.0 from https://files.pythonhosted.org/packages/61/a9/775d0a1f3f961a7ad956724c5439a96ca3a86183a0826424ccbfe63f482c/uharfbuzz-0.37.3-cp312-cp312-win_amd64.whl.metadata
  Using cached uharfbuzz-0.37.3-cp312-cp312-win_amd64.whl.metadata (2.3 kB)
Collecting python-bidi (from coldtype[viewer])
  Using cached python_bidi-0.4.2-py2.py3-none-any.whl (30 kB)
Collecting requests (from coldtype[viewer])
  Obtaining dependency information for requests from https://files.pythonhosted.org/packages/70/8e/0e2d847013cb52cd35b38c009bb167a1a26b2ce6cd6965bf26b47bc0bf44/requests-2.31.0-py3-none-any.whl.metadata
  Using cached requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)
Collecting b3denv>=0.0.5 (from coldtype[viewer])
  Obtaining dependency information for b3denv>=0.0.5 from https://files.pythonhosted.org/packages/97/ce/50d486626dbc24ecd7980314b80c0338e792bafec281ebbda27f8f773d1c/b3denv-0.0.9-py3-none-any.whl.metadata
  Using cached b3denv-0.0.9-py3-none-any.whl.metadata (476 bytes)
Collecting glfw (from coldtype[viewer])
  Obtaining dependency information for glfw from https://files.pythonhosted.org/packages/e5/fb/819923400b06aaf5604c62ffc35aa9f37340b2b4ec6e1d7399b1ec2408be/glfw-2.6.2-py2.py27.py3.py30.py31.py32.py33.py34.py35.py36.py37.py38-none-win_amd64.whl.metadata
  Using cached glfw-2.6.2-py2.py27.py3.py30.py31.py32.py33.py34.py35.py36.py37.py38-none-win_amd64.whl.metadata (5.4 kB)
Collecting PyOpenGL (from coldtype[viewer])
  Obtaining dependency information for PyOpenGL from https://files.pythonhosted.org/packages/99/48/00e31747821d3fc56faddd00a4725454d1e694a8b67d715cf20f531506a5/PyOpenGL-3.1.7-py3-none-any.whl.metadata
  Using cached PyOpenGL-3.1.7-py3-none-any.whl.metadata (3.2 kB)
INFO: pip is looking at multiple versions of coldtype[viewer] to determine which version is compatible with other requirements. This could take a while.
Collecting coldtype[viewer]
  Obtaining dependency information for coldtype[viewer] from https://files.pythonhosted.org/packages/ef/65/6009562bcfaa6df4397612477c4653a01bd34c1dd1c47d47e15f9cfc6cc0/coldtype-0.10.13-py3-none-any.whl.metadata
  Using cached coldtype-0.10.13-py3-none-any.whl.metadata (2.1 kB)
  Obtaining dependency information for coldtype[viewer] from https://files.pythonhosted.org/packages/82/1c/e2ab6b8dffe4f80edbcad2172271ecff828bd7106364584a4b9263333f1b/coldtype-0.10.12-py3-none-any.whl.metadata
  Using cached coldtype-0.10.12-py3-none-any.whl.metadata (2.1 kB)
  Obtaining dependency information for coldtype[viewer] from https://files.pythonhosted.org/packages/c4/e6/8e57dae12714602c63a087dc794a6a54c7db1019bc114a02b7f12d422b93/coldtype-0.10.11-py3-none-any.whl.metadata
  Using cached coldtype-0.10.11-py3-none-any.whl.metadata (2.1 kB)
  Obtaining dependency information for coldtype[viewer] from https://files.pythonhosted.org/packages/31/e9/2c94924a7b51989750d3aa5b4dd81f0e862f1757a5e7d9fde58af87eb5dc/coldtype-0.10.10-py3-none-any.whl.metadata
  Using cached coldtype-0.10.10-py3-none-any.whl.metadata (2.1 kB)
  Obtaining dependency information for coldtype[viewer] from https://files.pythonhosted.org/packages/24/a6/09e09782ed82d6acb6717b01dd4b8f2a2f32f54f73a843c92bd74a3f0a18/coldtype-0.10.9-py3-none-any.whl.metadata
  Using cached coldtype-0.10.9-py3-none-any.whl.metadata (2.1 kB)
  Obtaining dependency information for coldtype[viewer] from https://files.pythonhosted.org/packages/de/78/4cb2c4798beb2a4516a8077a109b21595d795cc9b24ea3cd740fb82c68e9/coldtype-0.10.8-py3-none-any.whl.metadata
  Using cached coldtype-0.10.8-py3-none-any.whl.metadata (2.0 kB)
  Using cached coldtype-0.10.7-py3-none-any.whl (472 kB)
INFO: pip is still looking at multiple versions of coldtype[viewer] to determine which version is compatible with other requirements. This could take a while.
  Using cached coldtype-0.10.6-py3-none-any.whl (471 kB)
  Using cached coldtype-0.10.5-py3-none-any.whl (471 kB)
  Using cached coldtype-0.10.4-py3-none-any.whl (469 kB)
  Using cached coldtype-0.10.3-py3-none-any.whl (469 kB)
  Using cached coldtype-0.10.2-py3-none-any.whl (469 kB)
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. See https://pip.pypa.io/warnings/backtracking for guidance. If you want to abort this run, press Ctrl + C.
  Using cached coldtype-0.10.1-py3-none-any.whl (469 kB)
  Using cached coldtype-0.10.0-py3-none-any.whl (469 kB)
Collecting pyobjc-framework-Cocoa (from coldtype[viewer])
  Using cached pyobjc-framework-Cocoa-10.0.tar.gz (6.8 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [21 lines of output]
      Traceback (most recent call last):
        File "C:\Users\gamma\OneDrive\Code\Python Coldtype\venv\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 353, in <module>
          main()
        File "C:\Users\gamma\OneDrive\Code\Python Coldtype\venv\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\gamma\OneDrive\Code\Python Coldtype\venv\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\gamma\AppData\Local\Temp\pip-build-env-6tgr1042\overlay\Lib\site-packages\setuptools\build_meta.py", line 355, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\gamma\AppData\Local\Temp\pip-build-env-6tgr1042\overlay\Lib\site-packages\setuptools\build_meta.py", line 325, in _get_build_requires
          self.run_setup()
        File "C:\Users\gamma\AppData\Local\Temp\pip-build-env-6tgr1042\overlay\Lib\site-packages\setuptools\build_meta.py", line 341, in run_setup
          exec(code, locals())
        File "<string>", line 26, in <module>
        File "C:\Users\gamma\AppData\Local\Temp\pip-install-fod0nq7l\pyobjc-framework-cocoa_9eca6bfee18c4e97bfe162d447e66871\pyobjc_setup.py", line 469, in Extension
          if "clang" in get_config_var("CC"):
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      TypeError: argument of type 'NoneType' is not iterable
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

thanks for reporting that — I don't know why pyobjc would be specified for as a dependency, as it's not even installed on a fresh installation of coldtype on mac — what version of python are you using on windows?

ah I see, are you using python 3.12.0? given how many "specialized" dependencies coldtype has (like skia-python and numpy), I usually avoid the .0 release of a new python, as they never seem to work properly. If you are using 3.12.0, could you try with an older Python? I've had success with the latest 3.11

Reverting to python 3.11.6 fixed the issue, thank you!

authors: fdinsen stenson

repo: coldtype/coldtype


text:
Icon request: podcast

Would be great to have a podcast icon to accompany the music icon.
This is the Apple podcast icon:

This might be closer to the weight of your style?

Working on a podcast version that fits and having a little difficulty at the moment. I might just need a little more time to think of a better method. Keeping the same proportions and aesthetic, the linked icons are a little harder to replicate. I was combining target and user as they are the same shapes, but when mixed, it doesn't quite come out right. Working on something though.

See if this works.

@sourcerer52 May you join us at @lucide-icons? ^^

repo: colebemis/feather


text:
Schema properties become optional if passed to generic function

When passing a schema with a normally matching generic type as a function parameter, object properties seem to become optional. So the following code fails with type error Type 'undefined' is not assignable to type 'string'.:
// not working
function test1<T extends ZodType<string>>(schema: T) {
  return z.object({ value: schema }) satisfies ZodType<{ value: string }>
                                  // ^ Type 'undefined' is not assignable to type 'string'.
}

When passing the schema with a specific type, it is working, but as stated in the documentation, some type information will be lost:
// working
function test2(schema: ZodType<string>) {
  return z.object({ value: schema }) satisfies ZodType<{ value: string }>
}

I'm not sure whether this is a TypeScript quirk, a bug in Zod or something I'm doing wrong. Any help would be appreciated.
Reproduction on StackBlitz
Maybe related: #2198

can i work on this

I've just run into this when upgrading from Zod 3.18 to 3.22 with the following example:
type FormValues = {
  obj: {
    key: string
  }
}

const schema: z.Schema<FormValues> = z.object({
  obj: z.object({
    key: z.string().default(''),
  })
})

@danni,
Is this what you are looking for?
type FormValuesInput = { obj: { key?: string } }
type FormValuesOutput = { obj: { key: string } }

const schema: z.Schema<FormValuesOutput, z.ZodTypeDef, FormValuesInput> = z.object( {
    obj: z.object( {
        key: z.string().default( '' ),
    } )
} )

If you found my answer satisfactory, please consider supporting me. Even a small amount is greatly appreciated. Thanks friend! 🙏
https://github.com/sponsors/JacobWeisenburger

@etiennelenhart,
Is this what you are looking for?
function test1<T extends z.ZodString> ( schema: T ) {
    return z.object( { value: schema } ) satisfies z.ZodObject<{ value: T }>
}

If you found my answer satisfactory, please consider supporting me. Even a small amount is greatly appreciated. Thanks friend! 🙏
https://github.com/sponsors/JacobWeisenburger

@JacobWeisenburger so it only works if you supply an input schema?

The 1st generic type on z.Schema (the output type), is used as the default value for the 3rd generic type on z.Schema (the input type). As long as they are the same, then you can just specify the 1st one. But in this case they were different because .default allows an optional input type, but it returns a required output type.

Yeah I understand the separate schemas, although I'm wondering here if the type inference makes sense. i.e. one can use the nullish-coalescing operator on a defined value and it's still handled at runtime, even if it's a hypothetical no-op.

authors: JacobWeisenburger NextThread danni etiennelenhart

repo: colinhacks/zod


text:
Event Emitter not working.

Hello,
Here is the example on superlogin / lib / index.js
  //Working
  emitter.on('testemit1', function (){
    console.log('1 - ring ring ring');
  });

  var mailer = new Mailer(config);
  var user = new User(config, userDB, couchAuthDB, mailer, emitter);
  emitter.emit('testemit1');
  emitter.emit('testemit2');
  var oauth = new Oauth(router, passport, user, config);

  //Not Working
  emitter.on('testemit2', function (){
    console.log('2 - ring ring ring');
  });

Fixed with 1d12b7bbaf6dc6cd932330af76a4c41edf92a7bf

authors: colinskow ronyrun

repo: colinskow/superlogin


text:
Also move example to the right location

Signed-off-by: Sjoerd Simons sjoerd@collabora.com

bors r+

repo: collabora/lava-api


text:
De-rails-ify DelayedJob

DelayedJob is very useful outside of Rails too. There's many hoops to jump through (including hand-forging use of Delayed::Command and requirements for Rails.root to exist).
It would be great if DJ became framework-agnostic.

If I may, for now, can you please add rails as a dependency?
Like, to avoid uninitialized constant Delayed::Command::Rails — I'm currently patching guard-delayed and I wonder if I should open another issue for that error, or this one is enough.
Thanks.

There are already fixes for that in master.

This issue can be closed.

I am using DJ in a non rails environment, and like @contentfree mentioned there are a few hoops to go through. Looks like this issue is more than 2 years old. @sferik Have any patches been submitted? Or are these the fixes @albus522 is talking about. If you need a patch let me know. I would like to contribute.

Delayed::Job still has some coupling with Rails but it should be relatively easy to use outside of a Rails environment (i.e. most of the coupling is wrapped in conditionals). There is a hard dependency on Active Support, which you could try to remove, but that would probably involving pasting lots of code from Active Support into DJ, which is probably not a worthwhile tradeoff.
@michaelirey Specifically, what issues are you running into using DJ outside of Rails? If you could open an issue for each of the “hoops” you’ve had to jump through, we could work on solving each of them individually.
I’m going to close this issue because I don’t think it’s productive to talk about “de-rails-ifying” Delayed::Job at such a high level.

authors: albus522 contentfree costa johnnyshields michaelirey sferik


text:
last_error backtrace showing jobs being run from different release / version of codebase

As the title says, some of my jobs are throwing errors, and the backtrace last_error indicates that the job is being run from a different version of the codebase.
For example, while I was testing my failure hook, I had one of my jobs raise a "Test Exception" and set the max_attempts = 3. Since then I have removed that code, yet the error still gets thrown, and from the backtrace I see that the code that's getting run is from release 87 (see below) where the current version is 91 (code resides in /var/www/staging/releases/87/app/mailers...). Also, the max_attempts value of 3 may or may not be obeyed.
Test Exception
/var/www/staging/releases/87/app/mailers/applog_mailer.rb:9:in `send_open_applications_log'
....

Furthermore, I'll see other jobs (from same deployment version) have a last_error backtrace from different release , not just 87.
I'm using the mina gem to deploy.

You deploy script is failing, leaving workers running old code. I am afraid there is nothing we can do about that.

[SOLUTION]
If it's a problem with the deploy, I should be able get it to work correctly by manually stopping and restarting the delayed_job daemon, right? I've done this and the problem persists. The jobs throw errors from different versions of the code for different attempts of the same job. I.e. one job will get run on release 87 codebase, fail, then try to run again on release 89 codebase.
It's as if there are still different daemons running that are not getting shut off from the deploy. RAILS_ENV=production bin/delayed_job status says there are no jobs running, but this yields different results in different release directories.
When running ps -eLf | grep \delayed_job I see there are several daemons running.
Using pidof your_delayed_job_instance_name and kill -9 12345 23456 34567 for the output helped kill all daemons.
Killing the other instances of the delayed_job daemon did indeed solve the problem. Each instance of the daemon preserves its configs and apparently codebase to execute.


text:
Implement CSS Color 4 gamut mapping

Currently, gamut mapping tries to allow any coordinate in any color space to be reduced (including nonsensical ones like hue) and uses deltaE 2000 as a color distance metric.

[x] Implement proposed improved CSS color 4 gamut mapping in a codepen (far end of JND MINDE)
[x] Investigate odd results with imaginary colors
[ ] Add to color.js codebase
[ ] Make it the default GMA

See also this codepen and this demo

Does not just affect GM single colors, but also affects smoothness of gradients, see this awful example

On lab(50% -127 -127) I get starting oklch of
[ 0.42226189321340196, 1.9540778145796625, 191.20237227483153 ]
and after GM I get
[ 0.43100803800138154, 0.0741924017206513, 191.0338159551419 ]
So the chroma is vastly reduced but the hue is very similar.

Exploring the CIE Lab L=50 plane over  a,b = -125 to +125 I am struck by the OKLab a value in the -125,-125 corner:
lab(50% 125 125)   =  oklab(60.58% 0.357 0.152)
lab(50% -125 125)  =  oklab(53.41% -0.32 0.194)
lab(50% -125 -125) =  oklab(42.27% -1.9 -0.37)
lab(50% 125 -125)  =  oklab(65.4% 0.257 -0.35)

So exploring the CIE a,b plane gives odd results if the GMA is using OKLCH

but equally, exploring the OKLab ab plane while mapping in CIE LCH is odd too

(TIL that screenshots of Canvas elements on my WCG screen look nothing like the actual screen)

Here exploring OKLab a,b we see mapping in CIELCH gives a patch of solid color in the a positive, b positive corner (bottom right)

Live versions:

CIE Lab explorer
OKLab explorer

@svgeesus - We are looking to use Color.js to implement CSS Color 4 logic (conversions, gamut, etc) for Sass in the node-embedded-host, and gamut mapping is one piece that is currently missing. Is there anything blocking this algorithm from being used in Color.js? (Perhaps waiting for clarity on https://github.com/w3c/csswg-drafts/issues/9449 or other outstanding issues?)
If there isn't anything blocking, are there parts that we could help implement here in Color.js?

@jamesnw exciting! Would love to support you folks in this.
AFAIK the only blocker is our lack of time: both @svgeesus and I are spread very thin. So yeah, we'd love help from you folks! Happy to assist with any questions about the codebase, architecture, API etc.

@LeaVerou Great! I have a draft PR at https://github.com/LeaVerou/color.js/pull/344. I have a few questions there, and am open to your thoughts on documentation and how best to incorporate this change. Thanks!

Closed by https://github.com/color-js/color.js/pull/352

authors: LeaVerou jamesnw svgeesus


text:
Refactor how Artemis processes code

This version completely refactors how Artemis generate code (by finally
using the implementation of visitor pattern provided by gql). On top of that,
I've decided to do other major breaking changes to make code cleaner and more
maintainable. Listed:

add_query_prefix doesn't exist anymore (it's now the default to generate
classes with its "path" from the query), e.g., this query's city field will
be typed as CityName$QueryRoot$User$Address$City:query city_name {
  user {
    address {
      city {
        name
      }
    }
  }
}

This change was also done to tip users to NOT use those generated queries
directly on their code, to avoid coupling them to your business logic.
custom_parser_import was moved to inside a ScalarMap, and
use_custom_parser was removed.
resolve_type_field option was renamed to type_name_field, as __typename
is the correct field name (by GraphQL spec).
Classes generated for mutation will have a Mutation suffix, as queries
already have Query suffix.
Change pre-generation data classes constructors to named parameters, so if
you're using GraphQLQueryBuilder.onBuild, it will break.

And also:

Add more logs and errors while generating code, to help debugging.
Add more/refactor tests.
Add a GitHub example.

TODO:

[ ] clean options?
[ ] prefix every class with $ (?)
[ ] refactor class naming variables
[ ] review readme and changelog

Hmm, it seems that this changes will require to start the sdl schema support from scratch...

CityName$QueryRoot$User$Address$City - this approach will lead to the class duplications.
If I have queries like
voyages(pagination: $input) {
            voyage {
                arrival  {
                    id
                    name
                    type
                }
                departure {
                    id
                    name
                    type
                }
            }
    }

and
searchDestinations() {
        destinations {
            id
            name
            type
        }
    }

They all use the same type
type Destination {
  id: ID!
  name: String!
  type: DestinationType!
}

I will get three identical classes
Voyages$QueryRoot$Voyage$Arrival
Voyages$QueryRoot$Voyage$Departure
SearchDestinations$QueryRoot$Destination

Thank for taking a look at this @vasilich6107!
I was thinking about merging this on this week on a separate artemis folder, and keep the two implementations working, but it'd be so much pain to maintain the two. So I'll probably just do this breaking change at once.
But do you think this would break the sdl support? Did you plan to replace the introspection or keeping both?
About the classes creation, that's a tradeoff we need to be conscious about: either we use the same class for the three or we generate one class for each (even being exactly the same). As I could query a field in one of them but not in the other, I've opted for creating a class for each one. Does that make sense?

I'm ok to start from scratch :-)
I have already started actually.
But let's try to avoid huge refactoring during several next weeks ;-)

About the classes creation, that's a tradeoff we need to be conscious about: either we use the same class for the three or we generate one class for each (even being exactly the same). As I could query a field in one of them but not in the other, I've opted for creating a class for each one. Does that make sense?

This approach definitely makes sense. We could also recommend to use fragments for the same selections and relay on fragment name to generate corresponding classes.

We could also recommend to use fragments for the same selections and relay on fragment name to generate corresponding classes.

Definitely! As fragments are generated as mixins they abstractely can be used in the same way.

I see that you introduced test generator helper.
Previously I had an option to debug tests from AndroidStudio - https://tppr.me/GniMb
Now I have an option to debug the whole group only - https://tppr.me/VQzPt and https://tppr.me/qTDz6

Hmm, yeah, that's true, the same happenened to me on VSCode (because it won't detect testGenerator as an known runner). That's why I've put group encapsulating each testGenerator.
This approach helped to reduce a lot of boilerplate of each test and made it easier to separate them in files.

Test generator slightly updated
import 'dart:convert';

import 'package:artemis/builder.dart';
import 'package:artemis/generator/data.dart';
import 'package:artemis/schema/graphql.dart';
import 'package:build/build.dart';
import 'package:build_test/build_test.dart';
import 'package:logging/logging.dart';
import 'package:meta/meta.dart';
import 'package:test/test.dart';

const IS_DEBUG = true;

String jsonFromSchema(GraphQLSchema schema) => json.encode({
      'data': {'__schema': schema.toJson()}
    });

void debug(LogRecord log) {
  if (IS_DEBUG) print(log);
}

testGenerator({
  @required String query,
  @required LibraryDefinition libraryDefinition,
  @required String generatedFile,
  GraphQLSchema typedSchema,
  String stringSchema,
  bool generateHelpers = false,
  Map<String, dynamic> builderOptionsMap = const {},
  Map<String, dynamic> sourceAssetsMap = const {},
}) async {
  assert((typedSchema ?? stringSchema) != null);
  final schema = stringSchema ?? jsonFromSchema(typedSchema);

  final anotherBuilder = graphQLQueryBuilder(BuilderOptions({
    if (!generateHelpers) 'generate_helpers': false,
    'schema_mapping': [
      {
        'schema': 'api.schema.json',
        'queries_glob': '**.graphql',
        'output': 'lib/query.dart',
      }
    ],
    ...builderOptionsMap,
  }));

  anotherBuilder.onBuild = expectAsync1((definition) {
    if (IS_DEBUG) print(definition);
    expect(definition, libraryDefinition);
  }, count: 1);

  return await testBuilder(
    anotherBuilder,
    {
      'a|api.schema.json': schema,
      'a|query.graphql': query,
      ...sourceAssetsMap,
    },
    outputs: {
      'a|lib/query.dart': generatedFile,
    },
    onLog: debug,
  );
}

void main() {
  group('On enums', () {
    test(
        'Enums can be part of queries responses',
        () async => testGenerator(
              query: query,
              libraryDefinition: libraryDefinition,
              generatedFile: generatedFile,
              typedSchema: schema,
            ));
  });
}

Those ^^^^^ changes helped to get back an ability to run tests independently
https://tppr.me/zmLE9

That makes sense! I'm adding you as a collaborator, I'll appreciate if you could commit those changes on this branch.

Great! I'll take a lunch and then I'll update all the tests.

I'm actively working on SDL schemas.
The tests left to fix are - aliases, custom scalars, fragments, interfaces, mutation and unions)

There's no rush! Actually I was thinking about merging this already, what do you think?

Sure, let’s merge this PR

I assume my SDL PR will live some time in draft stage cause currently the code “just works”)
May be it will be reasonable to release it under beta tag...

Sure, I'm gonna ship this as 4.0.0 and work on having a parallel beta branch to explorations.

repo: comigor/artemis


text:
[Feature] Softly unload the mod if loaded on a server environment

Describe the Bug
Mod crashes servers
Steps to Reproduce
load mod on server
Expected Behavior
To not crash
Screenshots
No response
Modloader Type
Minecraft Forge
Modloader Version
39.0.10
Mod Version
BetterF3-1.2.2-Forge-1.18.jar
Log Output
[Fatal] Failed to start the minecraft servernet.minecraftforge.fml.LoadingFailedException: Loading errors encountered: BetterF3 (betterf3) encountered an error during the common_setup event phase?7java.lang.RuntimeException: Attempted to load class net/minecraft/client/multiplayer/ClientLevel for invalid dist DEDICATED_SERVER] at net.minecraftforge.fml.ModLoader.waitForTransition(ModLoader.java:235) ~[fmlcore-1.18.1-39.0.10.jar%23156!:?] at net.minecraftforge.fml.ModLoader.lambda$dispatchAndHandleError$21(ModLoader.java:200) ~[fmlcore-1.18.1-39.0.10.jar%23156!:?] at java.util.Optional.ifPresent(Optional.java:178) ~[?:?] at net.minecraftforge.fml.ModLoader.dispatchAndHandleError(ModLoader.java:200) ~[fmlcore-1.18.1-39.0.10.jar%23156!:?] at net.minecraftforge.fml.ModLoader.lambda$loadMods$14(ModLoader.java:183) ~[fmlcore-1.18.1-39.0.10.jar%23156!:?] at java.lang.Iterable.forEach(Iterable.java:75) ~[?:?] at net.minecraftforge.fml.ModLoader.loadMods(ModLoader.java:183) ~[fmlcore-1.18.1-39.0.10.jar%23156!:?] at net.minecraftforge.server.loading.ServerModLoader.load(ServerModLoader.java:47) ~[forge-1.18.1-39.0.10-universal.jar%23159!:?] at net.minecraft.server.Main.main(Main.java:104) ~[server-1.18.1-20211210.034407-srg.jar%23155!:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?] at net.minecraftforge.fml.loading.targets.CommonServerLaunchHandler.lambda$launchService$0(CommonServerLaunchHandler.java:46) ~[fmlloader-1.18.1-39.0.10.jar%2323!:?] at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-9.0.7.jar%235!:?] at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:53) [modlauncher-9.0.7.jar%235!:?] at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:71) [modlauncher-9.0.7.jar%235!:?] at cpw.mods.modlauncher.Launcher.run(Launcher.java:106) [modlauncher-9.0.7.jar%235!:?] at cpw.mods.modlauncher.Launcher.main(Launcher.java:77) [modlauncher-9.0.7.jar%235!:?] at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) [modlauncher-9.0.7.jar%235!:?] at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) [modlauncher-9.0.7.jar%235!:?] at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:90) [bootstraplauncher-0.1.17.jar:?].

Additional Context
No response

Do you have any other mods?

Wait, this mod isn't supposed to be run on a server. It is a client side only mod and will always error if run on a server.

Yes this is a client-side only mod, but many people dont know that and will see their servers crash.
Which is why you often will see something like this https://github.com/nanite/Simple-Discord-Rich-Presence/blob/19bc78dc1eeae0711fa96ee4a4b59e32408cbd23/src/main/java/com/sunekaer/mods/sdrp/SDRP.java#L37-L43
Then the mod loads on server but none of the code does

I understand, so this is less of a big report and more of a feature request. I'll implement this when I get the chance.

Yes this is a client-side only mod, but many people dont know that and will see their servers crash. Which is why you often will see something like this https://github.com/nanite/Simple-Discord-Rich-Presence/blob/19bc78dc1eeae0711fa96ee4a4b59e32408cbd23/src/main/java/com/sunekaer/mods/sdrp/SDRP.java#L37-L43 Then the mod loads on server but none of the code does

To add to this point, if your client mods and server mod lists don't match, FML will complain (and show your users) that the client and server disagree.
So mods should still register on dedicated servers (dist/side DEDICATED_SERVER), then do nothing more.

Just FYI in case you need it:
See https://docs.minecraftforge.net/en/1.20.x/concepts/sides/ for how to do it properly:

Your mods are expected to always load, regardless of if they are loaded on the client or the server. For one-sided mods, this means that they must still run on the opposite physical side.

Those mods are not official BetterF3 mods. BetterF3 already includes this check and can be downloaded from https://modrinth.com/mod/betterf3

Those mods are not official BetterF3 mods. BetterF3 already includes this check and can be downloaded from https://modrinth.com/mod/betterf3

Thanks! I apparently had the wrong "Better F3" mod installed (my original search in Curse Forge had found https://www.curseforge.com/minecraft/mc-mods/better-f3 instead of https://www.curseforge.com/minecraft/mc-mods/betterf3 ), I've now swapped to this one in my modpack and it works as expected. :)
I'm so sorry for the extra noise and thank you. :)

authors: Sunekaer TreyRuffy sandalle


text:
user_interaction: Use RbConfig instead of obsolete and deprecated Config

The change from ffc4e0d1b47b8d04ad271f19eaef2c9154066924 included in 4.3.6 triggers a warning on Ruby 2.1.5p273 (Debian Jessie). Reversing the change, fixes the warning:
/var/lib/gems/2.1.0/gems/commander-4.3.7/lib/commander/user_interaction.rb:333:in `const_get': Use RbConfig instead of obsolete and deprecated Config.

Fixed in 4afaefc321f196e54a61840ef6cd6b85e5c3e51d, will release soon

Released as 4.3.8

authors: ggilder sts

repo: commander-rb/commander


text:
Cancel previous ongoing runs in the PR/branch when you push new commits

Description (required)
Fixes #4781
What changes did you make?
Adding this to cancel any previous ongoing builds when you push new commits to a PR or branch. This will ensure that we don't run out of free build mins.
Note: Please ensure that you have read CONTRIBUTING.md if this is your first pull request.

@madhurgupta10 can you check now ?

@RishiKumarRay Now revert the extra changes, this will also test if ongoing builds are cancelled or not

@madhurgupta10 how to revert?

@madhurgupta10 how to revert?

You can push another commit by removing the unnecessary changes

@madhurgupta10 there was only some extra spaces i have removed that please check

@nicolas-raoul yeah sure i will remember this. Thanks for helping out and merging @madhurgupta10

repo: commons-app/apps-android-commons


text:
Integrated acsp-profile-data-api

Short description outlining key changes/additions
Integrated acsp-profile-data-api
JIRA Ticket Number
IDVA6-1562
Type of change

[ ] Bug fix
[x] New feature
[ ] Breaking change
[x] Infrastructure change

Pull request checklist

[x] I have added unit tests for new code that I have added
[x] I have added/updated functional tests where appropriate
[x] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: Security warnings found!

authors: ch-code-analysis krishna-patel-ch

repo: companieshouse/acsp-manage-users-api


text:
Fix a bunch of Sphinx warnings

Fixing a bunch of doc string related error messages. This will allow real doc-string problems to be more visible. At the moment there is 13 warning messages:
C:\Users\leungp\Documents\GitHub\compas_fab\src\compas_fab\backends\kinematics\analytical_inverse_kinematics.py:docstring of compas_fab.backends.kinematics.analytical_inverse_kinematics.AnalyticalInverseKinematics.inverse_kinematics:22: ERROR: Unexpected indentation.
C:\Users\leungp\Documents\GitHub\compas_fab\src\compas_fab\backends\kinematics\analytical_inverse_kinematics.py:docstring of compas_fab.backends.kinematics.analytical_inverse_kinematics.AnalyticalInverseKinematics.inverse_kinematics:23: WARNING: Block quote ends without a blank line; unexpected unindent.
C:\Users\leungp\Documents\GitHub\compas_fab\src\compas_fab\backends\pybullet\planner.py:docstring of compas_fab.backends.pybullet.planner.PyBulletPlanner.add_attached_collision_mesh:18: WARNING: Inline literal start-string without end-string.
C:\Users\leungp\Documents\GitHub\compas_fab\src\compas_fab\backends\pybullet\planner.py:docstring of compas_fab.backends.pybullet.planner.PyBulletPlanner.add_attached_collision_mesh:18: WARNING: Inline literal start-string without end-string.
C:\Users\leungp\anaconda3\envs\cf-dev\Lib\site-packages\roslibpy\ros.py:docstring of roslibpy.ros.Ros.blocking_call_from_thread:7: ERROR: Unexpected indentation.
C:\Users\leungp\anaconda3\envs\cf-dev\Lilooking for now-outdated files... b\site-packages\roslibpy\ros.py:docstring of roslibpy.ros.Ros.call_sync_service:9: ERROR: Unexpected indentation.
C:\Users\leungp\anaconda3\envs\cf-dev\Lib\site-packages\roslibpy\ros.py:docstring of roslibpy.ros.Ros.off:6: ERROR: Unexpected indentation.
C:\Users\leungp\Documents\GitHub\compas_fab\src\compas_fab\robots\reachability_map\reachability_map.py:docstring of compas_fab.robots.reachability_map.reachability_map.ReachabilityMap:15: CRITICAL: Unexpected section title.

Links
-----
C:\Users\leungp\Documents\GitHub\compas_fab\src\compas_fab\robots\trajectory.py:docstring of compas_fab.robots.trajectory.Trajectory:4: CRITICAL: Unexpected section title.

Attribute
---------
C:\Users\leungp\Documents\GitHub\compas_fab\docs\examples\07_reachability_map.rst:5: WARNING: duplicate label examples_kinematics, other instance in C:\Users\leungp\Documents\GitHub\compas_fab\docs\examples\06_backends_kinematics.rst
C:\Users\leungp\Documents\GitHub\compas_fab\docs\examples\07_reachabilinone found
pickling environment... ty_map\03_rp_2D.rst:3: WARNING: Duplicate explicit target name: "link to full script".
done
checking consistency... done
preparing documents... done
writing output... [100%] license                                               inematicsom_urdfreset_planning_sceneshed_collision_mesh
C:\Users\leungp\Documents\GitHub\compas_fab\docs\backends\pybullet.rst:24: WARNING: undefined label: compas:robots
C:\Users\leungp\Documents\GitHub\compas_fab\docs\backends\ros.rst:157: WARNING: undefined label: compas:robots
generating indices... genindex py-modindex done
writing additional pages... search done
copying images... [100%] _images/compas_fab.png                                t_override.jpgpg
copying downloadable files... [100%] examples/05_backends_pybullet/files/01_add_attached_collision_mesh.pya.ghx
copying static files... done
copying extra files... done
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded, 13 warnings.

What type of change is this?

[ ] Bug fix in a backwards-compatible manner.
[ ] New feature in a backwards-compatible manner.
[ ] Breaking change: bug fix or new feature that involve incompatible API changes.
[x] Other (e.g. doc update, configuration, etc)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I added a line to the CHANGELOG.md file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
[ ] I ran all tests on my computer and it's all green (i.e. invoke test).
[ ] I ran lint on my computer and there are no errors (i.e. invoke lint).
[ ] I added new functions/classes and made them available on a second-level import, e.g. compas_fab.robots.CollisionMesh.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added necessary documentation (if appropriate)

This PR is based on the https://github.com/compas-dev/compas_fab/pull/394 because a bunch of error is present in the V-Rep part, since that is going away, I'm not fixing those mistakes.
#394 should be reviewed and merged before this one.

@chenkasirer or @gonzalocasas
Maybe if anyone of you wants to review this.


text:
windows 8 support

microsoft give me a surface pro plz

we can listen to both the pointerup/pointerdown events as well as the MSGestureTap

ideally we would do both and only call the function once, but that seems a little complicated.

repo: component/tap-event


text:
clean up composer.json

roundcube/plugin-installer and shama/baton are not longer available and are not needed anymore

They might still be required by old versions of packages though so I think it's good to keep the replace in.

authors: RafaelKa Seldaek

repo: composer/installers


text:
Certain characters in title result in post not found

The title that broke things was "Goblog: GIN powered JSON and HTML rest endpoints with a testing framework"
My suspicion is that it is the : character.

Fixed with https://github.com/compscidr/goblog/commit/8a3ba0e7e80dd314de244b0809752b3459c42957

repo: compscidr/goblog


text:
Initial implementaiton of user management targeting FreeBSD

Initial code redone for the rewrite. Implements basic user management with adding users to a system. The initial PR will target FreeBSD to flesh out the general idea with user management. After this has been done, work can happen to support adding users on different systems that comtrya support.
Should introduce no breaking changes and just add functionality.

Codecov Report

Merging #197 (f86ef34) into main (462dd15) will decrease coverage by 1.82%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #197      +/-   ##
==========================================
- Coverage   49.16%   47.34%   -1.83%
==========================================
  Files          59       64       +5
  Lines        1975     2051      +76
==========================================
  Hits          971      971
- Misses       1004     1080      +76

Impacted Files
Coverage Δ

lib/src/actions/mod.rs
20.89% <0.00%> (-0.65%)
:arrow_down:

lib/src/actions/user/add.rs
0.00% <0.00%> (ø)

lib/src/actions/user/mod.rs
0.00% <0.00%> (ø)

lib/src/actions/user/userproviders/freebsd.rs
0.00% <0.00%> (ø)

lib/src/actions/user/userproviders/mod.rs
0.00% <0.00%> (ø)

lib/src/actions/user/userproviders/none.rs
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

Looks good to me.
You maybe want to run cargo clippy and fix the warnings.

Clippy warnings should be taken care of now

@rawkode has to merge. Maybe he also wants to take a look around the code :)

Hey @rawkode, do you have time to review the PR (to have a second opinion) and merge it, if it's sufficient?

Couple of small changes requested, then we can merge. Thank you, @martintc!

Great work, @martintc

authors: codecov-commenter icepuma martintc rawkode

repo: comtrya/comtrya


text:
CONAN_UPLOAD_RETRY doesn't affect anything

In packager.py ConanMultiPackager there is this line
self.upload_retry = upload_retry or os.getenv("CONAN_UPLOAD_RETRY", 3)
but self.upload_retry doesn't get passed anywhere later.

You are right. Some versions ago I changed the invocation to conan by command line with calling the python API. I will take a look

authors: Artalus lasote

repo: conan-io/conan-package-tools


text:
Mixed Content Error

The submit query doesn't work when you leave some of the fields blank. We should consider adding an error message when some of the fields are left blank.

Solved with try catch on jQuery

repo: concertcode/codeapp


text:
Udate Remove Hawks button state when user resets simulation

We were not updating the state when the user reset the pop sim and the "add hawks" button would display as "remove hawks" to the user.
[#164438603]

:+1:

authors: mklewandowski sfentress

repo: concord-consortium/connected-bio-spaces


text:
prometheus: Improve label consistency

This PR actually fixes two problems:

Add worker platform attribute during initial registration
Don't add time series to prometheus when labels are missing

thanks!

repo: concourse/atc


text:
A cf-resource env variable should override the same one provided by a manifest

According to [this comment] about env variable support (https://github.com/concourse/cf-resource/pull/4#issuecomment-114860307): "It now works by adding the environment variables to the manifest, before doing the cf push". I thought an env variable provided by cf-resource would override one provided by a manifest. But it isn't.
What do you think ?
Pipeline extract
   put: resource-deploy-cf-webui
    params:
      manifest: manifest.yml
      environment_variables:
        API_ENDPOINT: https://my-url.com
        API_ENDPOINT2: https://my-url.com

Manifest extract
  env:
    API_ENDPOINT: https://api.run.pivotal.io

Cf env
User-Provided:
API_ENDPOINT: https://api.run.pivotal.io
API_ENDPOINT2: https://my-url.com

It looks like cf-resource does override manifest environment variables, but only at the top level--environment variables set inside an application aren't updated. A simple solution would be to iterate over applications specified in the manifest and update environment variables for each one. Does that sound reasonable @vito? I'd be happy to send a PR if so.

Don't applications inherit env from the root? If they have specific values set, I'm not sure we could or should say what is expected: the intention may be for CI to set the "default", while leaving applications able to override it.

authors: jmcarp o-orand vito

repo: concourse/cf-resource