text:
Providing a minified mjs bundle

It's recommended to use preact.min.js instead of preact.js in production builds due to the file size reduction from the property mangling: https://github.com/developit/preact/blob/87a4ebe99dc068eaeb8503644c60ffe8ad735771/config/properties.json#L1-L27
This works well if you are using a regular script to pull preact from the CDN and relying on the preact global or if you are bundling with webpack. However, it doesn't work if you are importing preact as a native ES module.
In that case, you can successfully import the unminified preact.mjs bundle, as seen here:
http://jsfiddle.net/tpck6Lf4/
But since preact.min.js is not a native ES module, you cannot change it like this:
- import { Component, h, render } from 'https://npmcdn.com/preact@8.4.2/dist/preact.mjs'
+ import { Component, h, render } from 'https://npmcdn.com/preact@8.4.2/dist/preact.min.js'

(you'd get SyntaxError: The requested module 'https://npmcdn.com/preact@8.4.2/dist/preact.min.js' does not provide an export named 'h')
It'd be awesome if there was a corresponding preact.min.mjs that we could import from in production builds to take advantage of the reduced file size.
One way to do this might be to switch from uglify to terser where the minifier can understand ES2015 syntax. Alternatively perhaps we can minify the code with export stripped out, and then add it back. Thoughts?

We published an alpha version for Preact X just a few hours ago. It's available on npm via the preact@next tag and ships with a minified mjs bundle 💯

authors: marvinhagemeister rmacklin

repo: developit/preact


text:
Mark event to Daily / Weekly / Monthly / Yearly

Hello,
i have create event on 1st September, 2013 for weekly intervals. so my mark date are 1, 8, 15, 22, 29.... so how can i implement this thing using this library. i am stuck at this point. which method of your library help me to resolve this issue. please help me as soon as possible.
Thank you so much in advance.....

yea the same question http://stackoverflow.com/users/587415/matrosov-alexander )

source: gharchive/issue

repo: devinross/tapkulibrary

license: mit

license_type: permissive

license_source: bigquery


text:
Update README to use current version

The current released version says it's in 4.0.1 so I just updated the version in the installation.

Pull Request Test Coverage Report for Build 244

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.423%

Totals

Change from base Build 236:
0.0%

Covered Lines:
186

Relevant Lines:
208

💛  - Coveralls

Fixed in 5.0.

source: gharchive/pull-request

authors: corroded coveralls devinus

repo: devinus/poison

license_source: github-api


text:
zu1k's docker image got removed

the docker image is gone. i see your app is running fine. would you help to restore or provide the exported .tar file of that image?

How can I help with that?

found the release here.

Should I/you close this issue or is there anything to be done?

It's alive again now.

repo: devockr/deeplx

license: MIT


text:
Enable h2-console for debug purposes

I have tricked sec config to make h2-console work.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@maciejmalecki could you please sign the CLA in order to contriubte to devonfw?

authors: CLAassistant hohwille maciejmalecki

repo: devonfw-forge/keywi


text:
Update 정상동기.md

각 챌린지 미션을 완료 할때 마다 PR을 생성해 주세요.

팀이름

팀이름, 자신의 GitHub ID를 남겨주세요.

팀 이름: 정상동기
GitHub ID: justinyoo

완료된 챌린지

완료된 챌린지의 내용을 선택 한 후,  해당 정보를 알려주시면 됩니다.

[x] 애저 정적 웹 앱 챌린지 완료
[ ] 깃헙 액션 챌린지 완료
[ ] 소셜미디어 인증샷 챌린지 완료
[ ] 애저 정적 웹 앱 리포지토리 제출 챌린지 완료
[ ] 애저 정적 웹 앱 URL 제출 챌린지 완료
[ ] 블로그 후기 URL 제출 챌린지 완료

/aswasignoff

/aswasignoff

repo: devrel-kr/HackaLearn


text:
Bug: Paradise lost is breaking some leaf textures from other mods due to christmas ornaments.

What happened?
A bug happened!
To replicate:

Install paradise lost & BYG (Or any mod that adds leaves)
Some leaves will not have textures.

Mod Version
Beta 1.6.9 1.18.2
Fabric API Version
0.67.0
Relevant log output
https://gist.github.com/FluffyBumblebees/3862e4b0fff36bc84c82630e7c72ff42

Other mods
BYG
Additional Information
No response

It seem that i was able to replicate this bug by installing sodium with byg and lost paradise, when i remove sodium both lost paradise and byg leaf's start to have texture
For me:

BYG + Paradies  Lost (no sodium) = load
BYG + Sodium = load
Paradies  Lost + Sodium = does not load
BYG + Paradies  Lost + Sodium = does not load

Mod ### Version
Release 1.4.7 1.18.2
Fabric API ### Version
0.67.0

Ah its a sodium incompat. Kinda annoying that there isnt a config to atleast turn this off until there's a fix.

I am currently using these 3 mods with my friend in a modded server, from his point of view the BYG and paradise lost leaf does load, but chest from paradise lost does not load

We actually don't have christmas textures for the chests that's why they're untextured. I believe the leaf problems are fixed in the 1.19.x versions however, but I will make a not of both.

1.19.2 Modpack MedievalMC users have reported this exact issue as well. Most notably, leaf textures from BYG are missing and are replaced with the purple/black texture.

This is fixed in my PR.

authors: FluffyBumblebees Frontear MBatt1 aeaver

repo: devs-immortal/Paradise-Lost


text:
修复无法杀死自定义容器的问题

修复 https://github.com/devsapp/fc3/issues/15

最好签署一下 DCO

已签


text:
chore: restructure into a monorepo using pnpm

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] The title of the PR states what changed and the related issues number (used for the release note).
[ ] Does this PR require documentation updates?
[ ] I've updated documentation as required by this PR.
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas

Remove linter.py, sentry.sh
Common out custom.d.ts
vite-env

repo: devtron-labs/dashboard


text:
ERROR in BusyModule is not an NgModule

I get this error when I import BusyModule. Or this library only works on Angular 2.0.0?
"dependencies": {
"@angular/common": "^2.3.1",
"@angular/compiler": "^2.3.1",
"@angular/core": "^2.3.1",
"@angular/forms": "^2.3.1",
"@angular/http": "^2.3.1",
"@angular/platform-browser": "^2.3.1",
"@angular/platform-browser-dynamic": "^2.3.1",
"@angular/router": "^3.3.1",
"angular2-busy": "^1.0.2",
"angularfire2": "^2.0.0-beta.7",
"bootstrap": "^3.3.7",
"core-js": "^2.4.1",
"firebase": "^3.6.8",
"ng2-bootstrap": "^1.3.2",
"rxjs": "^5.0.1",
"ts-helpers": "^1.1.1",
"zone.js": "^0.7.2"
},
"devDependencies": {
"@angular/compiler-cli": "^2.3.1",
"@types/jasmine": "2.5.38",
"@types/node": "^6.0.42",
"angular-cli": "1.0.0-beta.26",
"codelyzer": "~2.0.0-beta.1",
"jasmine-core": "2.5.2",
"jasmine-spec-reporter": "2.5.0",
"karma": "1.2.0",
"karma-chrome-launcher": "^2.0.0",
"karma-cli": "^1.0.1",
"karma-jasmine": "^1.0.2",
"karma-remap-istanbul": "^0.2.1",
"protractor": "~4.0.13",
"ts-node": "1.2.1",
"tslint": "^4.3.0",
"typescript": "~2.0.3"
}

same issue

same issue

same issue

I have the same problem.

same issue

Same

same

Has anyone fixed this bug?

Same error for me with:
"@angular/compiler-cli": "^2.3.1",
"angular-cli": "1.0.0-beta.24",
"typescript": "~2.0.3"

same

Any idea how to fix this?

same issue!!

same issue. any idea how to fix?

same! any idea?

the same issue.  any idea when it will be fixed?

Same error for me with:
"@angular/compiler-cli": "^2.4.8",
"angular-cli": "1.0.0-beta.32.3",

Same issues
"@angular/compiler-cli": "^2.3.1",
"angular-cli": "1.0.0-beta.28.3",

Same issue here after upgrading to @angular/cli@latest - is there a fix in the works?
@angular/cli: 1.0.0-beta.32.3
node: 7.3.0
os: win32 x64
@angular/cli: 1.0.0-beta.32.3
@angular/common: 2.4.8
@angular/compiler: 2.4.8
@angular/compiler-cli: 2.4.8
@angular/core: 2.4.8
@angular/forms: 2.4.8
@angular/http: 2.4.8
@angular/platform-browser: 2.4.8
@angular/platform-browser-dynamic: 2.4.8
@angular/router: 3.4.8

+1

A possible workaround, until it is patched, is to comment out
imports: [ ...
//,BusyModule
...]
Then ng build -w or whatever you prefer.  Once it is built remove the comments.  It just throws a fit during the build but it still works fine.

+1

same issue

yep! same issue...

same here

Same here

Changing the order in app.module.ts from
@NgModule({
  imports: [
    ...
    BusyModule,

  ],
  declarations: [
   ...

  ],

  ...
}

to
@NgModule({
  declarations: [
   ...

  ],
  imports: [
    ...
    BusyModule,

  ],
  ...
}

worked for me

same here :(

@devyumao , you can take a look at this issue: https://github.com/angular/angular-cli/issues/3426#issuecomment-269673735 maybe it will be able to help.
Do you plan to keep the library updated or it is abandoned currently?

I have fixed this error. Please use this until the official module is fixed.
https://github.com/dinusuresh/angular2-busy

Thank you @dinusuresh ! The solution you provided works on my side too! 👍
Why don't you consider to issue a pull request to https://github.com/devyumao/angular2-busy ? I bet this would help @devyumao deal with this issue faster.

Yay!  Works great!  Thanks, Dinesh!
From: Dinesh [mailto:notifications@github.com]
Sent: Friday, March 10, 2017 5:43 AM
To: devyumao/angular2-busy
Cc: Hatfield, R. Scott; Comment
Subject: Re: [devyumao/angular2-busy] ERROR in BusyModule is not an NgModule (#33)
I have fixed this error. Please use this until the official module is fixed.
https://github.com/dinusuresh/angular2-busy
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/devyumao/angular2-busy/issues/33#issuecomment-285636933, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABDSfemQtnuFzG9iunR8soclrhBApxCxks5rkSk4gaJpZM4L02hA.

Thanks a lot @dinusuresh 👍  your fixed also worked for me.

Thanks  @dinusuresh  its works for me too!!!
I updated "ts-metadata-helper" and "angular2-dynamic-component" packages in my projetc too...

Glad I could help 😄
@superKalo I have created a pull request but considering the author is not active ATM I do not know if and when it will be accepted.

Can anyone please explain me how to solve this problem? I didn't understand what I have to change :)

@M4NC1O Sure. If you are looking to just get it working, then
In you package.json file amke sure the angular2-busy line is like this:
"angular2-busy": "https://github.com/dinusuresh/angular2-busy.git"

It works!
thank you!

Thank you !

It works well..thanks

When I build --aot I lose the spinner and the label "Loading..".. does anyone have the same issue?

@dinusuresh: started getting error "DynamicComponentModule is not an NgModule"..

@Niraj-Sharma Please can you post your package.json ?
It is working good on my end, the only warning is the rxjs version 5.0.2 which is used by angular2-dynamic-component
@M4NC1O I will look into it and let you know.

@Niraj-Sharma https://github.com/devyumao/angular2-busy/issues/39

Now the module has been fixed.
Thanks, @dinusuresh ! Your solution is great. 👍
Also thank @superKalo . The issue you mentioned is very helpful.
Sorry for the late reply. The library will be keeping updated :)

@Niraj-Sharma Now the module does not rely on angular2-dynamic-component any more. Please update to the latest version.

@devyumao Thank you

Hello,
I followed solution by dinusuresh, but it's not working. Please provide solution.
& also wanted to ask that It will create separate instance for different component if we add in diff component.
Currently, I am using loader with observables but problem is loader gets activated for any request to Server it's just because of service we are using.
Please provide solution.

@dinusuresh

authors: GuiFSimoes M4NC1O Niraj-Sharma PatilPritam SerhiiTsybulskyi SimoneMSR Trenrod arianul bashoogzaad bgaillard calvingferrando18 chintharr danilocubo devyumao dinusuresh emidel flexkiran gepisolo hambardzumyan-mane justicewebtech kthomas80 marciomsm michalzfania nolafs oslanier qcnguyen rshatf slesarevns smainz stanciupaul superKalo tim-hoffmann tmwnni trueflywood


text:
Dexie is sometimes hard to debug because of missing context in error event object

I'm using window.addEventListener('unhandledrejection', callback) for global error handling of Dexie.js. My Problem is I often find myself in a situation where it's hard to debug my code because the error event object does not give enough meaningful information of where the error occurred in my code. Here is a very distilled example of a type of error which I had a hard time debugging:
window.addEventListener('unhandledrejection', function(e) {
  // The output of the error object does not give any meaningful information where the error occured
  console.log(e);
});

var db = new Dexie("TestDuplicateKey");
db.version(1).stores({ test: 'id' });

db.open().then(function() {
  return db.test.add({ id: 1 });
}).then(function() {
  return db.test.add({ id: 1 });
});

Fiddle: https://jsfiddle.net/1ksfk1hv/
Here is all information I get from the error event object in the console output:

message: "Key already exists in the object store."
name: "ConstraintError"
stack: "Error
at getErrorWithStack (https://unpkg.com/dexie@2.0.1/dist/dexie.js:322:12)
at new DexieError (https://unpkg.com/dexie@2.0.1/dist/dexie.js:451:19)
at mapError (https://unpkg.com/dexie@2.0.1/dist/dexie.js:481:14)
at handleRejection (https://unpkg.com/dexie@2.0.1/dist/dexie.js:965:14)
at IDBRequest. (https://unpkg.com/dexie@2.0.1/dist/dexie.js:4220:9)
at IDBRequest. (https://unpkg.com/dexie@2.0.1/dist/dexie.js:1178:23)"

I'm not sure if I should do something differently, this is a limitation I have to live with or if this is something which could be improved in Dexie.js.

Yes, you can set Dexie.debug to true to enable long call stacks:
Dexie.debug = true;

I updated the fiddle accordingly and after running it, the log will tell you the exact line where the error occurred, see screenshot:

Note: Dexie.debug will be default true when served from localhost.
http://dexie.org/docs/Dexie/Dexie.debug

Thank you - this helps a lot! I'm running my tests in a Jasmine suite and therefore Dexie.debug has been set to false by default.

authors: dasboe dfahlander


text:
parameters information (wcbench)

Hi Daniel,
I'd like to find out more  about "cbench_max, cbench_min, cbench_avg, one_min_load, five_min_load, fifteen_min_load" parameters?
What are exactly this parameters? How are they calculated??
Thanks :)

With these parameters:

I don't understand these values:

and the average responses/sec (817.41),  are the answers that "switches" riceve by "controller"?

What are exactly this parameters?

They are described in detail in the WCBench Results section of the README.

How are they calculated??

This array contains most of the commands used to gather system stats, including all of the *_load ones you asked about. The CBench min/max/avg values are parsed from CBench's result output. Here's the relevant code.

are the answers that "switches" riceve by "controller"?

I don't think I understand what you mean by this - can you restate it more clearly?
You can find general information about system load from many places, including this wiki article.

Daniel excuse me,
I wouldn't be wrong;
"CBench is a somewhat classic SDN controller benchmark tool. It blasts a controller with OpenFlow packet-in messages and counts the rate of flow mod messages returned."
Is "cbench_avg" parameter calculated according to these messages returned?

Is "cbench_avg" parameter calculated according to these messages returned?

Yes, it's the average packet_ins/flow_mods per second.
My slides from LinuxCon provide a pretty good overview of CBench's algorithm.

Perfect ;)
Thanks you !!


text:
MEF exports with IODataEndpoint or IODataEndpointData must support Version information

Currently MEF endpoints that are loaded via the IODataEndpoint interface do not specify their version. When using these endpoints more intensively it will become difficult to manage or detect their versions.
Therefore it is suggested to either implement a static property on IODataEndpointData which specifies the version of the assembly/plugin or to add a method/property to IODataEndpoint that returns the version.
The disadvantage of having the version information supplied in IODataEndpointData is that it is static, but it is then very obvious (within the data annotation) which version the plugin is supposed to have.
If the version information was supplied via IODataEndpoint then it could be read from the assembly or somewhere else (which could lead to a more consistent version scheme and could be detectable from the outside via file information).
Both of these suggested changes are breaking changes!

@rufer7 what do you think of this?
The downside is, that we have that IODataEndpoint inside the utilities package so everyone upgrading this package for other reasons will run into that breaking change.
I know that breaking changes are not the way to go, but this is very early in the dev process of that component, so I think we should go for it.

@dfch Seems to be a good point providing the version in IODataEndpoint. Another option could be reading the assembly version itself. The disadvantage is, that with this apptoach the version gets increased with every build. Exposing the version by a method or field seems to be more flexible. I would suggest taking the approach you suggested. Breaking changes in early development state should not be the reason for not doing it.


text:
not saving correctly

this is the part of my script that exports the data to excel
foreach($tedserver in $tedservers) {
$kbtenables | Where-Object {$.'dns name' -match $tedserver} | Export-Excel -Path 'D:\Powershell Scripts\Data\WindowsUpdates\Tenable.xlsx' -WorksheetName Ted-KB -Append -AutoSize
$othertenables | Where-Object {$.'dns name' -match $tedserver} | Export-Excel -Path 'D:\Powershell Scripts\Data\WindowsUpdates\Tenable.xlsx' -WorksheetName Ted-Other -Append -AutoSize
}
i have the same thing about 6 times, one for each tech. when i run one loop everything works but doing 2 or more i get this error message
MethodInvocationException: C:\Users\my user\Documents\PowerShell\Modules\ImportExcel\7.4.1\Public\Export-Excel.ps1:679:20
Line |
679 |              else { $pkg.Save() }
|                     ~~~~~~~~~~~
| Exception calling "Save" with "0" argument(s): "Error saving file D:\Powershell Scripts\Data\WindowsUpdates\Tenable.xlsx"
what i end up with is a spreadsheet with 2 sheets which is from the last loop instead of all sheets for all techs
Thank you

i went back to this the next day, closed code and reran the script and everything works

Sometimes it only works every other Thursday ;-)

authors: computechrr dfinke

repo: dfinke/ImportExcel


text:
Draft: Galactic-Devel (Help wanted)

Hi there,
I have started porting this package to ROS2 galactic a while ago. It was a lot of effort so far and there is still heaps to do. I wanted to get further in the development before opening a PR but because of the lack of time I am guessing it would be easiest to all work together (hopefully) on this one to move along. And finally be able to use ROS2 for all the MiR platforms.
It is still pretty rudimentary, but the simulation and driver work together with our MiR100 platform and it is great to be able to use ROS2 package once the driver connection is up and running.
Overview:

mir description: ported
mir_driver: supports the laser_scans, cmd_vel, odom and tf so far. Since I didn't need the other topics, I have commented them out. (ROS1 to ROS2 msg require some dict filter, but that shouldn't be a big effort to implement for most topics) This was the biggest chunk to be solved, I ended up porting rospy_msg_converter to ROS2 (rclpy_msg_converter) as well. Will link the PR here shortly.
mir_gazebo: simulation is up and running
mir_navigation: mapping + navigation ported using slam_toolbox and nav2 (which is great) but there is still a lot of parameter tuning to be done (mostly waiting on 1.0.8 release right now)

Some issues to point out:

Separate laserscans: The laserscans are the most important part in mapping, localization and mapping and we have two separate scans (front and back). In comparison to ROS1 the slam and nav nodes require the scan to be merged and not only be passed alternately to the same topic. So I needed to merge those (using another package I ported) from laserscan to pointcloud then merge the clouds and then convert it back to a single laserscan. At that time I could not find a better solution, if somebody else can point out anything, I'd be happy to review that.
Known Bug: Gazebo simulated Laserscans drift away from time to time (before merging in a pointcloud). This seems to be an issue in the urdf configuration, but I haven't had the time to track it down. https://github.com/relffok/mir_robot/issues/1
Missing namespace support: While porting I missed to drag the namespace everywhere (I also felt like there is an ongoing discussion about namespaces in lots of ros2 pkg), but this will also be added some time soon https://github.com/relffok/mir_robot/issues/2

To sum up, it is useable for a few tasks, but there is still lots of things to do and bugs to remove. Help wanted and appreciated!

Thanks a lot for all this work! I'll review it as soon as possible (I'm pretty swamped with work right now). Just a quick comment on one of your points:

Separate laserscans: The laserscans are the most important part in mapping, localization and mapping and we have two separate scans (front and back). In comparison to ROS1 the slam and nav nodes require the scan to be merged and not only be passed alternately to the same topic. So I needed to merge those (using another package I ported) from laserscan to pointcloud then merge the clouds and then convert it back to a single laserscan. At that time I could not find a better solution, if somebody else can point out anything, I'd be happy to review that.

This is really unfortunate. The problem with merging the laserscans like that is that you lose the information which frame a particular point was recorded from. At least in mapping and navigation there's some ray tracing going on between the sensor frame and the point (to determine free space), so that'll probably be a problem. Perhaps for pure localization it's going to work.
I remember having to do the same hack because gmapping in ROS1 also doesn't support multiple laser scanners, but it didn't produce good results, so I switched to hector_mapping instead (which supports multiple laser scanners).

Thanks a lot for all this work! I'll review it as soon as possible (I'm pretty swamped with work right now).

Thank you. I'm looking forward to get this one fully ported!

This is really unfortunate. The problem with merging the laserscans like that is that you lose the information which frame a particular point was recorded from. At least in mapping and navigation there's some ray tracing going on between the sensor frame and the point (to determine free space), so that'll probably be a problem. Perhaps for pure localization it's going to work.

I used it on MiR for mapping and navigation and also SLAM with a what I called virtual_laser_link (which I placed in the middle of the robot platform) and I didn't run into any issues. But maybe I am overlooking something here and you'll find something explicit to show me once you tested it.

@ros-pull-request-builder retest this please

That doesn't seem to have worked. Closing and reopening to trigger retesting.

authors: mintar relffok


text:
Migrate the FromRequest things into a sub-package with some more flexible features

The original ParseFromRequest method was just a helper I inserted based on how I was using this library. It is useful as an example, but far more specific than I'm comfortable with for this library.  It's also hard to change it's behavior without introducing risk to users of the library.
I'd like to migrate, for version 3.0, all the request parsing behavior into a sub-package.  In doing so, we should also modify it to be flexible, but have well defined behavior.  Adding functionality should not introduce unexpected behavior for existing users.

Now's a good time to talk about a desired set of functionality.  I'll go through the PRs and Issues and see what people have asked for in the past as a jumping off point.  If anyone has any other thoughts, please post here.

repo: dgrijalva/jwt-go


text:
touch.rb:54: Add support for search over multiple branches (.locations)

The puzzle 567-859269e5 from #567 has to be resolved:
https://github.com/dgroup/lazylead/blob/cab193ac3d5bedcf8f8c6ad487e898fc03f5d864/lib/lazylead/task/svn/touch.rb#L54-L54
The puzzle was created by rultor on 02-Feb-22.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 567-859269e5 has disappeared from the source code, that's why I closed this issue.

repo: dgroup/lazylead


text:
Start DaprPlacementContainer automatically when DaprContainer is started

Currently, DaprPlacementContainer and DaprContainer should be started manually. This commit adds DaprPlacementContainer as a dependency when DaprContainer is started.

/cc @ThomasVitale

This is great! Thanks a lot @eddumelendez!

authors: ThomasVitale eddumelendez

repo: diagridio/testcontainers-dapr


text:
How to handle list/carousel selection events ?

I have made a carousel following this example,
link
How can I handle the selection event for this ?

Hi,
Your link does not work for me.
I got it to work for me on a project i did earlier using
actions_intent_OPTION as an EVENT TRIGGER on a followup intent to the intent containing the carousel.
To extract the value in a parameter use #actions_intent_option.OPTION

@karanvs Your link is broken, can you post the code you have so far and be more specific?

List selection events are Action on Google specific events and are not supported by this library.  If you are building on Dialogflow with only Actions on Google in mind please use the Actions on Google client library . If you are building for Actions on Google and other platforms please see the Dialogflow fulfillment & Actions on Google client library sample.

authors: karanvs matthewayne sarahdwyer syedatifakhtar


text:
SSL error when trying to run example

Environment details

OS: Windows 10
Node.js version: 10.1.0
npm version: 5.0.3
dialogflow version: 0.4.0

Steps to reproduce

Follow the QuickStart steps on https://github.com/dialogflow/dialogflow-nodejs-client-v2
Create a file using the code on https://github.com/dialogflow/dialogflow-nodejs-client-v2#using-the-client-library
Change the project ID as intended.
Run node filename.js

After struggling with the grpc installation, I followed the steps for Windows users here.
Now I have the following error when trying to run the code, as well as with any sample on the /samples directory:
Auth error:Error: write EPROTO 21584:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:openssl\ssl\record\ssl3_record.c:252:
ERROR: { Error: 14 UNAVAILABLE: Getting metadata from plugin failed with error: write EPROTO
21584:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:openssl\ssl\record\ssl3_record.c:252:
at Object.exports.createStatusError (C:\Users\foo\Desktop\dialogflow\samples\node_modules\grpc\src\common.js:87:15)
at Object.onReceiveStatus (C:\Users\foo\Desktop\dialogflow\samples\node_modules\grpc\src\client_interceptors.js:1214:28)
at InterceptingListener._callNext (C:\Users\foo\Desktop\dialogflow\samples\node_modules\grpc\src\client_interceptors.js:590:42)
at InterceptingListener.onReceiveStatus (C:\Users\foo\Desktop\dialogflow\samples\node_modules\grpc\src\client_interceptors.js:640:8)
at callback (C:\Users\foo\Desktop\dialogflow\samples\node_modules\grpc\src\client_interceptors.js:867:24)
code: 14,
metadata: Metadata { _internal_repr: {} },
details: 'Getting metadata from plugin failed with error: write EPROTO 21584:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:openssl\\ssl\\record\\ssl3_record.c:252:\n' }

I searched for problems with SSL relating to both grpc and Google cloud projects, but didn't find any clue on what to do.
For me it seems to be related to the installation issues involving openssl and Windows as cited on the grpc installation page, so I'm considering test the same steps on some Linux platform and see if the same problem occurs.
Could anyone help?
Update:
Running on an Ubuntu VM with
Node.js: 8.11.2
npm: 5.6.0
I got a similar error, here tried to run detect.js from /samples:
ubuntu@ubuntu-VirtualBox:~/dialogflow-nodejs-client-v2/samples$ node detect.js text -q "hi"
Sending query "hi"
E0523 16:58:36.419127299   10093 ssl_transport_security.cc:989] Handshake failed with fatal error SSL_ERROR_SSL: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number.
E0523 16:58:36.774246703   10093 ssl_transport_security.cc:989] Handshake failed with fatal error SSL_ERROR_SSL: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number.
E0523 16:58:37.124691019   10093 ssl_transport_security.cc:989] Handshake failed with fatal error SSL_ERROR_SSL: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number.
E0523 16:58:37.471887273   10093 ssl_transport_security.cc:989] Handshake failed with fatal error SSL_ERROR_SSL: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number.
E0523 16:58:38.195687058   10093 ssl_transport_security.cc:989] Handshake failed with fatal error SSL_ERROR_SSL: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number.
E0523 16:58:38.542390862   10093 ssl_transport_security.cc:989] Handshake failed with fatal error SSL_ERROR_SSL: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number.

Also I'm pretty sure the problem isn't with my credentials, because they work perfectly fine with the Python SDK.

I found out that the problem was my proxy, when I tried to use in a network without the proxy I forgot to deactivate the proxy configurations temporarily.

This is not an issue with the proxy from what I can tell.  This issue appears to be with the node.js library itself.  The TLS handshake needs to be initiated with an HTTP CONNECT message to the proxy so the destination server (google) can receive the TLS handshake initiation instead of your proxy.  Otherwise you get a 400 or other error from your proxy server, which is invalid TLS protocol with respect to your client, resulting in the error.  If the node.js grpc implementation really did send the CONNECT message to the proxy, then this all should work.

Greetings!  We're tracking proxy support over in #20.

authors: JustinBeckwith mephicide pbragaalves


text:
Fix rethrowing errors

🎁

reject was not defined here 😄. I could use return Promise.reject(e) but opted for simpler throw.

repo: dialohq/inline-test-ppx


text:
feat(avatar): extract initials from full name

Feat (Avatar): Extract initials from full name
:hammer_and_wrench: Type Of Change

[ ] Fix
[x] Feature
[ ] Refactoring
[ ] Documentation

:book: Description

Refactored Avatar to remove slot based usage in favor of prop based
Added iconSize property to be able to resize the avatar's icon
Removed slot related documentation
Migrated avatar's usage on components that were using DtAvatar
Changed imported images to public path to improve Percy visual tests stability with images
Included changes from #1097 and #1098

:bulb: Context
We we're having a lot of issues maintaining avatar's as it was created slot based initially to make it more customizable.
:pencil: Checklist

[x] I have reviewed my changes
[x] I have added tests
[x] I have added all relevant documentation
[ ] I have validated components with a screen reader
[ ] I have validated components keyboard navigation
[ ] I have considered the performance impact of my change
[ ] I have checked that my change did not significantly increase bundle size
[ ] I am exporting any new components or constants in the index.js in the component directory
[ ] I am exporting any new components or constants in the index.js in the root

:crystal_ball: Next Steps
Migrate usages of DtAvatar, DtRecipeFeedItemRow, DtRecipeContactRow and DtRecipeContactInfo components on product.
:camera: Screenshots / GIFs

Seems like visual tests are running even the PR is not approved yet, I'll take a look into that.

repo: dialpad/dialtone-vue


text:
Separate static checks from pytest

I want to separate the static code checks (black, mypy, ruff) so that they don't run as part of pytest. Instead they should run either as part of pre-commit, or as their own standalone tox environments. We only need to run these checks once, not for every Python version as we do with pytest, and besides the dependencies needed to run these tests as part of pytest are breaking compatibility with Python 3.6.

From what I've figured out so far, I think this should be done together with, or after, #20. Anyway I'm working on both.

repo: diazona/setuptools-pyproject-migration


text:
Can't logout

npm logout
Results in
13:48:16 Fennec@VERGIL testpublish: npm logout
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "logout"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.2
npm ERR! code E404

npm ERR! 404 Not found : -/user/token/191c8da2-07c5-43de-ac98-c8704cd915cd

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Fennec/testpublish/npm-debug.log

Is this api just not supported?

not at the moment, feel free to submit a PR though, should be pretty simple

authors: Roam-Cooper dickeyxxx

repo: dickeyxxx/npm-register

license: isc


text:
Suffix v1/chat/completions added to custom server endpoint

Plugin Version

1.0.0-231

Actual Behaviour
I use a custom endpoint in the server settings https://ete-openai-experiments.openai.azure.com/openai/deployments/gpt-4/chat/completions?api-version=2024-02-15-preview and this worked fine until the latest version of the plugin.
Now it fails with the message
404 Not Found from POST https://ete-openai-experiments.openai.azure.com/openai/deployments/gpt-4/chat/completions/v1/chat/completions
Please notice the v1/chat/completions suffix that seems to be added.
Expected Behaviour
If I add a URL in the server settings configuration it gets applied as it is

Azure OpenAI services have got a separate configuration in the latest version of the plugin. Please go to Settings | Tools | ChatGPT Integration | Azure OpenAI and provide your endpoint configuration there: API Key, API Endpoint and Deployment Name.
And if you are not using previous endpoints for GPT-4 and GPT-3.5-Turbo you may also disable them to not show them in a tool window.
I hope this helps.

Great - thanks 👍 That resolved my issues. Thanks for this nice plugin.

authors: didalgolab pgebert

repo: didalgolab/chatgpt-intellij-plugin


text:
iOS、web端为什么没有弱网模拟

想全面推进团队使用DoKit
但是不知道为什么只有Android端有弱网模拟，iOS和web没有是因为技术问题吗？

Android 和iOS都是支持弱网模拟的，如果没有找到升级最新版本试试。

authors: RealOnlyone protectedMan

repo: didi/DoKit


text:
Feat locale

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow DiDi's contributing guide.
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

Codecov Report

Merging #302 into dev will decrease coverage by 0.04%.
The diff coverage is 91.52%.

@@            Coverage Diff             @@
##              dev     #302      +/-   ##
==========================================
- Coverage   92.89%   92.84%   -0.05%
==========================================
  Files         131      134       +3
  Lines        2801     2853      +52
  Branches      418      427       +9
==========================================
+ Hits         2602     2649      +47
- Misses        105      110       +5
  Partials       94       94

Impacted Files
Coverage Δ

src/components/picker/picker.vue
82.45% <ø> (ø)
:arrow_up:

src/components/cascade-picker/cascade-picker.vue
81.81% <ø> (ø)
:arrow_up:

src/components/date-picker/date-picker.vue
98.73% <ø> (ø)
:arrow_up:

src/modules/locale/index.js
100% <100%> (ø)

src/modules/time-picker/index.js
100% <100%> (ø)
:arrow_up:

src/components/time-picker/time-picker.vue
89.41% <100%> (+0.52%)
:arrow_up:

src/modules/date-picker/index.js
100% <100%> (ø)
:arrow_up:

src/components/action-sheet/action-sheet.vue
90% <100%> (+1.11%)
:arrow_up:

src/modules/select/index.js
100% <100%> (ø)
:arrow_up:

src/components/dialog/dialog.vue
96.66% <100%> (+0.11%)
:arrow_up:

... and 13 more

Continue to review full report at Codecov.

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

Hey @theniceangel,
Something went wrong with the build.
TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
View build log
TravisBuddy Request Identifier: 0c3648f0-cd1d-11e8-9706-8d7bf71fb7b5

authors: TravisBuddy codecov-io theniceangel

repo: didi/cube-ui


text:
[language] remove unused diem-types dependency from disassembler

This removes the (unused) diem-types dependency from crate disassembler.

/land

@bmwill :exclamation: Unable to run the provided command on a closed PR

/land

@vgao1996 :exclamation: Unable to run the provided command on a closed PR

Unable to run the provided command on a closed PR
@bmwill this doesn't look quite right

Let me try to close and then reopen this

/land

Looks like it works. Hmm... maybe bors didn't add this to In Review in the first place?

:broken_heart: Test Failed - ci-test-success

/land

authors: bmwill bors-libra vgao1996

repo: diem/diem


text:
afd-blocker blockiert afd.de nicht

Geht mal so gar nicht

[Witzig]

schwach

Fixed in #21

authors: KennyTV RaisingAgent dieparteidiepartei fzakfeld

repo: dieparteidiepartei/afd-blocker-plugin

license: ISC


text:
Support for order by random()

Setup
Versions

Rust: 1.18
Diesel: 0.14.0
Database: SQLite
Operating System Windows

Feature Flags

diesel: sqlite
diesel_codegen: sqlite

Problem Description
There is no way to randomly sort the results of a select statement.
What are you trying to accomplish?
Returning a random subset of rows from a table. (ie. SELECT * FROM my_table LIMIT 20 ORDER BY RANDOM())
I know it's possible to work around this with my_table.order(sql::<types::Bool>("RANDOM()")).load(connection) but this seems like a useful feature to support in a safe manner.
Checklist

[x] I have already looked over the issue tracker for similar issues.

You can use sql_function! or no_arg_sql_function! for this. Generally we want to avoid exporting every possible function in SQL from Diesel, since it's trivial to declare the ones that you want.

Thanks!

It took me too long to figure this out so this is the code required:
no_arg_sql_function!(RANDOM, (), "Represents the sql RANDOM() function");

// Usage, using the post schema from the getting started guide.
let results = posts
    .order(RANDOM)
    .limit(5)
    .load::<Post>(&*connection)
    .expect("unable to load posts");

Which will generate the following query:
SELECT * ORDER BY RANDOM()

@agersant How do you solve this problem? (The version I am using now is 1.4.2)

no_arg_sql_function!(
	random,
	sql_types::Integer,
	"Represents the SQL RANDOM() function"
);

let results = table
		.limit(10)
		.order(random)
		.load(connection);

I used this code in version 1.4.2, but it still reports an error.
pub fn query_by_random_order_by_id_desc(conn: &MysqlConnection, category_id_data: i32, limit_num: i64) -> Result<Vec<Self>, Error> {
        no_arg_sql_function!(random, sql_types::Integer,"Represents the SQL RANDOM() function");

        albums::table
            .order(random)
            .filter(category_id.eq(category_id_data))
            .filter(status.eq(1))
            .limit(limit_num)
            .load::<Self>(conn)
    }

@tingfeng-key Our issue tracker is used to track bugs and feature request. For asking questions please use our gitter channel

authors: Thomasdezeeuw agersant sgrif tingfeng-key weiznich

repo: diesel-rs/diesel


text:
Opprette spdx:algorithm

#52
"Range: spdx:checksumAlgorithm_sha1 Cardinality: 1..1 This property identifies the algorithm used to
produce the subject Checksum. Currently, SHA-1 is the only supported algorithm. It is anticipated that other algorithms will be supported at a later time."

Gjelder versjon 1.1

authors: Elianne oystein-asnes

repo: difi/dcat-ap-no


text:
feat: add "all organisations" to global menu

When the option "all organisations" in party dropdown (situated left for filters) is chosen,  this is not reflected in the global menu (cf. picture). It is also not possible to choose "all organisations" from the global menu.
Missing design?

Legges på is inntil detaljert videre. Fjernes fra PartyDropdown.

repo: digdir/dialogporten-frontend


text:
Question: Only sending specific errors to Sentry

Hello,
We have a module that collects and deals with lots of personal information (including payment data).
For our staging site, all data is obfuscated or test data, so there's no issue in sending every error to Sentry.
However, for the production site, we would only want to send specific errors (either like an includedExceptions array or the ability to only manually throw an error when we want e.g. MyCustomSentryError. This is because we cannot guarantee that personal data isn't contained within the error until we go through a scrubbing process and it's a large code base.
Is something like this possible with this plugin? I note that the craft-sentry plugin seems to support this when writing module code, as it explicitly needs the Sentry error to be thrown.
Any ideas welcome!
Thanks.

Hello @lukew-cogapp,
I believe you can achieve the desired result with the categories parameter. This parameter is empty by default, which means all exception categories are sent to Sentry. If you specify classes in this parameter, only the mentioned exception categories will be sent to Sentry.
https://github.com/diginov/craft-sentry-logger?tab=readme-ov-file#categories
Since this plugin is a direct extension of a Yii Log Target, you can use all the base parameters.
https://www.yiiframework.com/doc/api/2.0/yii-log-target

authors: lukew-cogapp martinleveille

repo: diginov/craft-sentry-logger


text:
Use IIIF terminology

For the training it is useful if things are referred to as canvas and manifest etc. This might be at odds to making the tool universally accessible especially to those that are less familiar with IIIF but for the training its useful if the terms mentioned in the tool are the ones we've already taught them from the specifications.

In v1 this was configurable, so some users could see terms appropriate for making an exhibit, and others would see the IIIF terms.
I think this is related to 118n but not quite the same - a French training course would use localised text but not translate "Canvas", for example.
So formal model terms maybe should have separate config.

Would it not just be easier to ensure that all terms and titles can be controlled by the 118n process - with the default being the standard English IIIF terms - if a use case requires simplified or domain specific terms then a single config file can be created to control it. This provides consistency or programming and administration.

TODO - decide what this looks like in https://github.com/digirati-co-uk/iiif-manifest-editor/wiki/Configuration
The UI strings can be included in Language Maps; there should be a special flag to indicate where a string is a label for an actual property value, e.g., requiredStatement, so they can be left intact if needed.
Different Apps can have their own overriding strings. E.g., a bespoke slide show editor.

There is a new sub-package of the Manifest Editor that specifically tries to match the IIIF specification with a static definition that can be read in applications.
https://codesandbox.io/s/iiif-meta-27v3q9?file=/index.html
Contains things like:

Required/recommended properties per resource
Valid rights statements + descriptions of each
Link + summary of each property (from IIIF specification)

This can be used to show contextual information inline and relate it back to the specification. Labels will be in the i18n configuration as previously mentioned.

authors: glenrobson jpadfield stephenwf tomcrane

repo: digirati-co-uk/iiif-manifest-editor


text:
Update the game over message

Update the game over message so people know how to play again!

done!


text:
Add google analytics tag

@bame-da asked me to do this
thanks @anthonylusardi-da for the help!

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: andreolf-da digitalasset-cla

repo: digital-asset/daml-cheat-sheet


text:
Edit package.json config

Hi.
Can you change the main file in package.json from grunfile.js to src/jquery.maskedinput.js. It needs to built bundle using webpack.

:+1:
It would be useful if we can build a bundle using the webpack.

Please fix this. Anyone hoping to use this with a module bundler is out of luck.

In Browserify, you can just require the file directly until there's a fix.
require('jquery.maskedinput/src/jquery.maskedinput.js');

authors: Forshortmrmeth jonscottclark maximal


text:
Updated spacing to match designs

There were a couple of spacing issues that have been fixed to match the original designs.
Adobe XD Designs - https://xd.adobe.com/view/6f1463ae-cefd-4b5e-8641-474ab7880353-3a47

Before
After

Which screens, while not matching the designs, I'm not sure the
implemented looked bad...
Brandon
On Tue, Feb 1, 2022 at 3:07 AM Seth Duffin @.***> wrote:

There were a couple of spacing issues that have been fixed to match the
original designs.
Adobe XD Designs -
https://xd.adobe.com/view/6f1463ae-cefd-4b5e-8641-474ab7880353-3a47
You can view, comment on, or merge this pull request online at:
https://github.com/digitalcredentials/learner-credential-wallet/pull/120
Commit Summary

790b303
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/commits/790b303265a5d5672892cf4ef11f3893882df138
Updated spacing to match designs

File Changes
(9 files
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/files
)

M app/components/CredentialItem/CredentialItem.styles.tsx
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/files#diff-783ec984564e6476e607a66f54e4b11cc2184aff86982c7ef60193ef60774391
(17)
M app/screens/AddScreen/AddScreen.styles.tsx
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/files#diff-8575a9bd35f15872fe3ff3385978610bf16f2aa2b5a1e1e0c3943877c2488af8
(2)
M
app/screens/ApproveCredentialsScreen/ApproveCredentialsScreen.styles.ts
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/files#diff-01504ed743d49bb4661beaf2b716e1f1fe707c25cce6b1b6095767e097d386aa
(6)
M app/screens/ApproveCredentialsScreen/ApproveCredentialsScreen.tsx
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/files#diff-c155cd019318e5ff514b34192b1f3b99eaab8828cae55ee00638a59f10f8aa10
(9)
M app/screens/HomeScreen/HomeScreen.styles.tsx
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/files#diff-80ea8b3e615dbe45d84b09fa9e0a32f138c5b78cb1a79df42c5885465ab6fbc1
(5)
M app/screens/HomeScreen/HomeScreen.tsx
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/files#diff-869377616d47d4f9c3f66acdb1b2534686f1c5ef38d665394fa6b60d924d0f53
(2)
M app/screens/ShareHomeScreen/ShareHomeScreen.styles.ts
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/files#diff-d9cfeb678c385dee4e22edbe78597ab10dc13568d173302531bbbb41fbae2c5f
(10)
M app/screens/ShareHomeScreen/ShareHomeScreen.tsx
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/files#diff-0c0fd255ffa680da0b656558bfc2c604619c5346266bdffcc63e3381f9314417
(1)
M app/styles/mixins.ts
https://github.com/digitalcredentials/learner-credential-wallet/pull/120/files#diff-8a22920ed8ef9464931083f26f71fe02bb7df9943feaae9228fb5c35e23de441
(5)

Patch Links:

https://github.com/digitalcredentials/learner-credential-wallet/pull/120.patch
https://github.com/digitalcredentials/learner-credential-wallet/pull/120.diff
—
Reply to this email directly, view it on GitHub
https://github.com/digitalcredentials/learner-credential-wallet/pull/120,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFXVRQHQK2OSBHHGPTB62LUY6IENANCNFSM5NINN7GA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@bmuramatsu There were a couple of small padding issues that Brandon Findlay had pointed out to me. These were quick fixes that took no longer than 5 min.

👍
On Wed, Feb 2, 2022 at 1:42 PM Seth Duffin @.***> wrote:

@bmuramatsu https://github.com/bmuramatsu There were a couple of small
padding issues that Brandon Findlay had pointed out to me. These were quick
fixes that took no longer than 5 min.
—
Reply to this email directly, view it on GitHub
https://github.com/digitalcredentials/learner-credential-wallet/pull/120#issuecomment-1028243162,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFXVRQKZQIG4EOPN6RK2XLUZF3H7ANCNFSM5NINN7GA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***
com>

authors: bmuramatsu sethduffin


text:
feat: Required logos added in the supported by section

Pull Request Details
Description
Rwquired logos added in the supported by section
Fixes
#989 solved
Type of PR

[x] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Refactoring
[ ] Other (specify): _______________

Summary
[Summarize the changes made in this PR.]
Screenshots (if applicable)

Additional Notes
[Include any additional information or context that might be helpful for reviewers.]
Checklist

[x] I have read and followed the Pull Requests and Issues guidelines.
[x] The code has been properly linted and formatted using npm run lint:fix and npm run format:fix.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
[x] I have not borrowed code without disclosing it, if applicable.
[x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
[x] I have tested these changes locally.
[x] My code follows the project's style guidelines.
[x] I have updated the documentation accordingly.
[x] This PR has a corresponding issue in the issue tracker.

Summary by CodeRabbit

New Features

Added new partner logos to the Home section with direct links to Netlify, Google Cloud, and Holopin websites.

@pranshugupta54 LGTM 💥

repo: digitomize/digitomize


text:
Merge commcare hq deploy

Sorry for the long diff here. To review this PR

Consider your thoughts about merging commcare-hq-deploy into commcarehq-ansible/fab
Then skip down all the way to the bottom and review the commits starting with https://github.com/dimagi/commcarehq-ansible/pull/1179/commits/09cb79714574556f51dc2c0782c7ebcd4dd48293.
See whether you think https://github.com/dimagi/commcare-hq/pull/18959 is an okay bridge for easing the change.

When this is merged, people will be able to log into the control machine and (assuming they've already run the 2 steps to set it up) can run
update-code

and then (and every time they log in thereafter) they can run all our fab commands like we always have (without changing directories or anything).
Locally the change is going to be a little less automated but it's basically
workon ansible
cd commcarehq-ansible
git pull
pip install -r fab/requirements.txt
./control/check_install.sh
cd fab

and then you can run the fab command. Thereafter to run fab commands you must workon ansible and choose one of three options:

enter the fab directory:cd commcarehq-ansible/fab
fab production deploy

use the -f option on fabfab -f ~/.commcare-cloud/repo/fab/fabfile.py production deploy

put an alias in your bash profileecho "alias fab=fab -f ~/.commcare-cloud/fab/fabfile.py" >> ~/.bash_profile
# forever after, from any directory:
fab production deploy

I prefer the third one, which is what's done on control machines, and I suggest that in https://github.com/dimagi/commcare-hq/pull/18959/files

👍 from me. I think this makes a lot of sense. I've been think about making it a submodule for a while but I think this is better

This also breaks ground on getting the services deploy out of HQ deploy. I could also see us breaking the environments.yml file up and putting it with the other env vars files.

Yes! Exactly. Glad to hear we're on the same page. Those were also two of the top things on my wish-list related to this change.

It just occurred to me that we could possibly do this in two steps, where we merge this one first, and then merge the commcare-hq counterpart of this a week or two later. That way we can make sure fab is working in commcarehq-ansible for a number of people before pulling out the rug.
The only thing we'd have to do is to remember to make all changes in the interim to the current commcare-hq-deploy submodule and then I could make sure they get more or less continuously merged into this repo. Not sure it's worth the effort, but just wanted to throw that out there and highlight that merging this would initially be a very quiet change (but would mean committing to a louder change within a couple weeks).

your rollout plan seems good. I doubt much will change in the next few days

just tested this on icds-new and it worked fine:
(ansible) skelly@kafka0:~/commcarehq-ansible/fab$ fab icds-new restart_services

@dannyroberts FYI there are some commits in commcare-hq-deploy that need to be merged in here.

Looked at https://github.com/dimagi/commcare-hq-deploy/commits/master (latest commit on Dec. 21) and it's all been merged in; must have done that last week after you wrote this but before I read it.

authors: dannyroberts snopoke

repo: dimagi/commcarehq-ansible


text:
OTD stopped working

looks like i'm not the only one. about 7pm PST, stopped loading the columns.

I see your on it. thanks.

repo: dimdenGD/OldTweetDeck


text:
API routes fail with Debugbar enabled

I've just installed barryvdh/laravel-debugbar and attempting to load a page with an API named route now fails with a 'Route not defined' error.
I'm filing the bug here and with the debugbar (https://github.com/barryvdh/laravel-debugbar/issues/290) since I'm not sure which project is doing something funky.

Sample code? Works fine here mate.

maybe try to load api first.
		'Dingo\Api\Provider\ApiServiceProvider',
		'Barryvdh\Debugbar\ServiceProvider',

I've created a minimal test case laravel install that shows the issue
https://github.com/EspadaV8/dingo-debugbar/tree/develop

All good I'll give this a run when I can. Cheers.

I'm no longer supporting Laravel 4.x. Try this in either Lumen or Laravel 5 and report back if there's still issues. Cheers mate.

authors: EspadaV8 devmark jasonlewis

repo: dingo/api


text:
Limn(of:) an URL causes an EXC_BAD_ACCESS

In Limn+Objc.swift line 10.
Test:
Limn(of: URL(string: "http://foo.com")).dump()

Not sure what's so evil about reading the _urlString ivar, but it doesn't work.

Nice, thank you!

repo: diogopribeiro/Limn


text:
[log] merge-only option

Problem, approach
See https://github.com/dirk-thomas/vcstool/issues/174
Example operation and out put
# git checkout 0.1.27
# vcs-log --merge-only
=== . (git) ===
commit d82cb6ec3be31533dc90979e083072c6440c68d3
Merge: dcee1a0 c174cd8
Author: Dirk Thomas <dirk-thomas@users.noreply.github.com>

    Merge pull request #61 from dirk-thomas/use_pytest

commit 68a2451d33c4f4de6f148de57439f08f0330d898
Merge: f7f008a 93eb8c6
Author: Dirk Thomas <dirk-thomas@users.noreply.github.com>

    Merge pull request #58 from dirk-thomas/support_nested_repos

commit f7f008a1279dce9b213c9cfc9e72a2f1fbf73c33
Merge: 3d98c90 3d8d011
Author: Dirk Thomas <dirk-thomas@users.noreply.github.com>

    Merge pull request #59 from dirk-thomas/flake8

Open question

This PR at the time of writing just adds a simple wrapper for underlining vcs tool, without new advantage. The design with custom verb to delegate commands to each vcs tool seems to be a right approach. I can agree to close this PR if a simple change like what's in this PR is undesirable.

What I envisioned originally was to take advantage of vcstool's unique functionality and run a command against multiple local repos. Something like this (Obviously the argument oneline doesn't yet exist so the command failed):# vcs-log --merge-only --oneline
usage: vcs log [-h] [-l N] [--limit-tag TAG | --limit-untagged] [--merge-only] [--verbose] [--debug] [-s] [-n] [-w N] [--repos] [paths [paths ...]]
vcs log: error: unrecognized arguments: --oneline

Then I found custom verb lets you easily achieve what I wanted.# vcs-custom --git --args log --oneline --merges -n 10
...
=== ./ros_tutorials (git) ===
f40abd5 Merge pull request #31 from JavaJeremy/ThetaBugfix
626a3e5 Merge pull request #35 from jproft/kinetic-devel
f21c4d2 Merge pull request #29 from ros/fix_compiler_warnings_jade
d6d11f3 Merge pull request #27 from gusmonod/patch-1
36715e2 Merge pull request #23 from adamheins/jade-devel
9a1f606 Merge pull request #22 from ros/jade-devel-add-turtle
:
=== ./vcstool (git) ===
d82cb6e Merge pull request #61 from dirk-thomas/use_pytest
68a2451 Merge pull request #58 from dirk-thomas/support_nested_repos
f7f008a Merge pull request #59 from dirk-thomas/flake8
3d98c90 Merge pull request #55 from dirk-thomas/style
3a687d2 Merge pull request #54 from dirk-thomas/convert_version_to_string
:

OP updated:

Problem, approach
See https://github.com/dirk-thomas/vcstool/issues/174
Example operation and out put
# git checkout 0.1.27
# vcs-log --merge-only
=== . (git) ===
commit d82cb6ec3be31533dc90979e083072c6440c68d3
Merge: dcee1a0 c174cd8
Author: Dirk Thomas <dirk-thomas@users.noreply.github.com>

    Merge pull request #61 from dirk-thomas/use_pytest

commit 68a2451d33c4f4de6f148de57439f08f0330d898
Merge: f7f008a 93eb8c6
Author: Dirk Thomas <dirk-thomas@users.noreply.github.com>

    Merge pull request #58 from dirk-thomas/support_nested_repos

commit f7f008a1279dce9b213c9cfc9e72a2f1fbf73c33
Merge: 3d98c90 3d8d011
Author: Dirk Thomas <dirk-thomas@users.noreply.github.com>

    Merge pull request #59 from dirk-thomas/flake8

Open question

This PR at the time of writing just adds a simple wrapper for underlining vcs tool, without new advantage. The design with custom verb to delegate commands to each vcs tool seems to be a right approach. I can agree to close this PR if a simple change like what's in this PR is undesirable.

What I envisioned originally was to take advantage of vcstool's unique functionality and run a command against multiple local repos. Something like this (Obviously the argument oneline doesn't yet exist so the command failed):# vcs-log --merge-only --oneline
usage: vcs log [-h] [-l N] [--limit-tag TAG | --limit-untagged] [--merge-only] [--verbose] [--debug] [-s] [-n] [-w N] [--repos] [paths [paths ...]]
vcs log: error: unrecognized arguments: --oneline

Then I found custom verb lets you easily achieve what I wanted.# vcs-custom --git --args log --oneline --merges -n 10
...
=== ./ros_tutorials (git) ===
f40abd5 Merge pull request #31 from JavaJeremy/ThetaBugfix
626a3e5 Merge pull request #35 from jproft/kinetic-devel
f21c4d2 Merge pull request #29 from ros/fix_compiler_warnings_jade
d6d11f3 Merge pull request #27 from gusmonod/patch-1
36715e2 Merge pull request #23 from adamheins/jade-devel
9a1f606 Merge pull request #22 from ros/jade-devel-add-turtle
:
=== ./vcstool (git) ===
d82cb6e Merge pull request #61 from dirk-thomas/use_pytest
68a2451 Merge pull request #58 from dirk-thomas/support_nested_repos
f7f008a Merge pull request #59 from dirk-thomas/flake8
3d98c90 Merge pull request #55 from dirk-thomas/style
3a687d2 Merge pull request #54 from dirk-thomas/convert_version_to_string
:

Thanks for the patch and apologies for the late merge.

repo: dirk-thomas/vcstool


text:
screen sharing DO NOT WORK in WAYLAND !

This is somehow and old issue for me but it has not been fixed yet !!
It's been some time that Modern linux systems moved from X to Wayland protocols . but Still I'm not able to share my screen in wayland !
people have to use firefox/chrome web app version of discord so they can share screen, show teammate/friends something and then again get back to desktop version ! :)
That's kinda terrible experience for users ...

This repo is not for tracking client issues, and you're in the wrong place.

authors: ArMot junetried

repo: discordlinux/feedback


text:
.NET Core Support Possible?

I know you stated that you will not update the library, so I am not asking whether you will do it, I am asking how hard would it be. As if it is easy enough I should be able to do it myself and possibly fork this one but if it is hard or near impossible without a complete rewrite, I will not attempt, because I would most likely fail tbh,
Thanks

Currently, MonoGame relies on WinForms implementations of .NET Framework or Mono for desktop GUI rendering. .NET Core 2.1 (latest as of this post) does not support WinForms, making it impossible to support it.
However, .NET Core 3.0 will introduce WinForms support for Windows platform. If MonoGame decides to support it, I'd be more than happy to move this code base over to .NET Core. Main benefits would be faster runtime and vastly improved .csproj format to simplify code.

Wait, if I understand correctly, your saying that MonoGame itself cannot currently run on .NET Core?

Okay, not to argue with you, but I am running a .NET Core MonoGame game on Linux right next to me, and MonoGame download links list Linux as well link

It's cool to see that there's working third party effort for .NET Core support!
The Linux download link on the official page is the Mono version of MonoGame.
It's hard to tell what problems may rise during the port. I'm mostly worried about the content pipeline, as Penumbra needs to compile custom shaders for each supported platform.

If it is any help, when I attempted to build Penumbra in .NET Core it compiled successfully, don't know if that included the shaders or not though.

Well, keep us updated, whether you plan to port or not!

Personally, I will wait for official support in MonoGame 3.8 before dabbling into it. The whole .NET Core story around MonoGame is still unclear for me.

Well what.
Did you bloody know.
If you install nuGet package Penumbra.DesktopGL it works out of the box.
Just like that, no nothing needed.
Your thing does work for .NET Core.
You're a bloody genius.

After some testing, I have concluded, that it works reliably, had 0 problems

Well what.
Did you bloody know.
If you install nuGet package Penumbra.DesktopGL it works out of the box.
Just like that, no nothing needed.
Your thing does work with .NET Core.
You're a bloody genius.
Edit: Tested on HelloPenumbra, saw shadow thing rotating, the whole window was slightly blue, I suppose that's what it is supposed to do
Edit2: Well someone is definitely a genius, don't actually know if specifically you.

How are you run monogame on .net core?

Install MonoGame like you normally would
Create new project
Add Penumbra.DesktopGL nuGet package

Should work now

Penumbra.DesktopGL is not working with Monogame UWP Core project:
System.TypeLoadException: 'Could not load type 'MonoGame.Framework.GameFrameworkViewSource`1' from assembly 'MonoGame.Framework, Version=3.8.0.1641, Culture=neutral, PublicKeyToken=null'.'

Penumbra.DesktopGL is not working with Monogame UWP Core project:
System.TypeLoadException: 'Could not load type 'MonoGame.Framework.GameFrameworkViewSource`1' from assembly 'MonoGame.Framework, Version=3.8.0.1641, Culture=neutral, PublicKeyToken=null'.'

Closing as supported already for awhile.

authors: discosultan meowxiik nanodesu88 richard-hajek romanov

repo: discosultan/penumbra


text:
Minimum required PHP version

README.rst mentions PHP 5.3 as the minimum required version but from a quick code analysis with this neat little tool, it's actually 5.2 and just for json_decode().
For all the rest you only need PHP 5.1. Could you please confirm this and, if correct, change the docs accordingly?
Thanks! :)

5.3 might have actually been a guess. Will try to review and confirm.
Neat tool :)

Thanks for looking into it :)
I forgot to mention this but since you provide an alternative json implementation, the minimum required version is effectively 5.1.
I also went through the code manually to confirm the tool's result and I think it's right, I don't see anything that requires PHP over 5.1 (or 5.3 for json_decode()).

authors: borfast dcramer

repo: disqus/disqus-php


text:
update to go1.19.9

Added back minor versions in these, so that we have a somewhat more
reproducible state in the repository when tagging releases.

Codecov Report
Patch and project coverage have no change.

Comparison is base (8900e90) 56.76% compared to head (b320abd) 56.76%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3905   +/-   ##
=======================================
  Coverage   56.76%   56.76%
=======================================
  Files         106      106
  Lines       10681    10681
=======================================
  Hits         6063     6063
  Misses       3944     3944
  Partials      674      674

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

We'll probably need an updated golangci-lint;
 > [stage-2 1/1] RUN --mount=type=bind,target=.     --mount=type=cache,target=/root/.cache     --mount=from=golangci-lint,source=/usr/bin/golangci-lint,target=/usr/bin/golangci-lint       golangci-lint run:
#17 10.70 panic: load embedded ruleguard rules: rules/rules.go:13: can't load fmt
#17 10.70
#17 10.70 goroutine 1 [running]:
#17 10.70 github.com/go-critic/go-critic/checkers.init.22()
#17 10.70 	github.com/go-critic/go-critic@v0.6.2/checkers/embedded_rules.go:46 +0x4b4

temporarily rebased on top of https://github.com/distribution/distribution/pull/3906 to see if things are looking good after that

(I'll rebase this one once the other PR is merged to remove the golangci-lint update commits)

authors: codecov-commenter thaJeztah

repo: distribution/distribution


text:
Coderef using keyref also prints temporary file name

Expected Behavior

I am using a codeblock with coderef to a C# file pointed to by a keyref.
Only the file content is listed in the codeblock.
Following snapshot shows output using direct href path to the same file.

Actual Behavior

After the codeblock, the file name of the temporary file is printed.

Environment

DITA-OT version: 3.2.1 out-of the box, no external plugins
Operating system and version: Windows 10
How did you run DITA-OT? calling dita.bat
Transformation type:  PDF, using FOP

My bookmap project used:
coderef-test.zip

Reproduced in 3.3.4 with both HTML and PDF.
In HTML output, the last line of the code block includes the full path name of the snippet:
}snippets/csharp-regions-simple.cs

Same in DITA-OT version 3.4.1
Do you have any plans to fix this?

Reproduced in 3.3.4 with both HTML and PDF.
In HTML output, the last line of the code block includes the full path name of the snippet:
}snippets/csharp-regions-simple.cs

Same in DITA-OT version 3.4.1
Do you have any plans to fix this?

Unable to reproce with 3.5. @robander, how about your?

authors: jelovirt masofcon qvrijt robander

repo: dita-ot/dita-ot


text:
Add support for configuring tm scope in PDF #1245

Add mode to control whether trademark symbol is created.

:+1:

authors: jelovirt robander


text:
Graph Dfs Application

Title - Count the number of islands in a grid
what will change - Code will be added
Type of Issue - Application of DFS
Please add/delete options that are not relevant.

[x] Adding New Code
[x] Improving Code
[x] Improving Documentation
[x] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[] Python
[x] C++
[] Java
[] C
[] Go
[] Other language

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

please assign me @div-bargali @jai2dev  for this task, this is an interview question and a nice application of DFS

Can I solve this issue?

I would also like to add some variations in this question, please assign me this so that I can add more relevant material here.


text:
Documentation for 3.2 features...

This should include apphooks_reload in core, content creation wizards, etc. (see: https://github.com/divio/django-cms/pull/4563)
Also, replace any references of "click" et al, in the docs to something more touch-friendly.
Finally, review this closed PR for text changes: https://github.com/divio/django-cms/pull/4551

done by @evildmp

authors: FinalAngel mkoistinen

repo: divio/django-cms


text:
Make note of need for migrations in plugin tutorial

Just a suggestion from a user working to develop a new CMS plugin that uses a model -- it may seem intuitive to some django programmers but you might want to add a line in the http://docs.django-cms.org/en/release-3.3.x/how_to/custom_plugins.html#storing-configuration tutorial noting that you should run manage.py makemigrations and manage.py migrate following your model creation to properly set up the configuration fields -  it tripped me up a little before I realized what was the issue when I went to remove or save the newly created plugin.

Thanks, fixed in https://github.com/divio/django-cms/pull/5566.

authors: evildmp pdbethke


text:
GitSavvy doesn't work after updated

After installed GitGutter my Sublime can't use GitSavvy anymore. It was not found on my command palette. So, I tried to remove GitGutter and reinstall GitSavvy but it still doesn't work.
Please help me as soon as possible, GitSavvy is a part of my life now.

Same issue here, GitSavvy is totally absent from the command palette since the last update :disappointed:

There is some major bug now, I am working on fixing it now.

@bank32 @rmnbrd, I just pushed out an update that will disable the offending code as a temporary work-around.  Syntax highlighting will disabled in inline-diff views, but we'll address that regression separately.  If you see this in the next few minutes, it would be super helpful if you could pull down master and confirm that things are working for you.  Sorry for the bad update!

fixed it. Thanks a lot.

@divmain I have another question. now I fixed it by less simple method but I wanna know when we can install latest version via Sublime package control ?

@bank32 it should be going out now.  You may need to either 1) restart Sublime, or 2) run Package Control: Upgrade Package in the command palette.  There is a delay between when I push a new tag in my Git repo and when packagecontrol.io picks up that changes and starts pushing it out to clients.

It's working like a charm now.
Thank you guys for your great reactivity! You rock! :+1:

authors: bank32 divmain rmnbrd stoivo

repo: divmain/GitSavvy


text:
Is it possible to revert from gitsavvy?

I didn't find a way..  I'd guess it  could be done from the graph window.

I don't believe we support it, and I don't use it personally.
However this is a nice feature request, to add a git: revert command, should be easy to implement if you want to give it a go and submit a Pull Request we'll be happy to assist.
Meanwhile, as a workaround I can suggest using custom commands.

authors: asfaltboy hanoii


text:
🛑 ArtChart is down

In 24fef4f, ArtChart (https://artchart.net/en) was down:

HTTP code: 504
Response time: 15646 ms

Resolved: ArtChart is back up in 01a2984 after 7 minutes.

repo: divtiply/artupptime


text:
Cyrillic-based keyboards not selectable on Mac

On Mac 12.5.1, I have had Erzya (myv) and Moksha (mdf) keyboards as well as several Latin-based keyboards Apurinã (apu), Lushootseed (lut), Tenino (tqn), Võro (vro).
After restarting my mac today, 2022-12-08, I have been unable to select a Cyrillic-based keyboard (a) from the keyboard, (b) manually attempting to select the language from the drop-down menu.
Upon adding a Mac Russian keyboard, both Erzya and Moksha mysteriously disappeared.
The same issue affects the keyboards: Mansi (mns), Kildin Saami, Khanty (kca)

I can confirm the behaviour reported: Today I installed the Mansi (mns) cyrillic-based keyboard, with the same result:
I installed the Mansi keyboard, and after restart the Divvun installer claims it to be installed, as excpected. The keyboard, however, is nowhere to be found  in the System menu for adding keyboards. DI lists the keyboard as installed ("No updates"), but to no avail. Latin-based keyboards (e.g. fao, rmn) work well, the problem seems to be the cyrillic-based one.
The issue is somewhat acute, since we work on mns this week, but it is of course a problem also genarally speaking.

Further confirmed by me using Mansi as a test case. @zoomix could you have someone look at this?
Details:

macOS 13.3.1 (a)
bundle properly installed as /Library/Keyboard\ Layouts/no.uit.giella.keyboards.mns.keyboardlayout.mns.bundle using Divvun Manager
not listed or visible at all in System Preferences (System Preferences > Keyboards > Input sources)

@dylanhand @SteffenErn — sorry, I forgot one step: you need to switch to the nightly channel in the app settings. After that the All repositories view will show Mansi near the bottom (it is written in Cyrillic, and the Cyrillic entries are towards the bottom - the actual packages are written in Latin, so should be no problem finding it).

We found the issue.
This occurs when the .keylayout file contains a self-closing  tag, such as:
<actions />`

The .keylayout file can be found in /Library/Keyboard\ Layouts/<your language>.bundle/Contents/Resources
The problem doesn't occur if this tag is either omitted or re-written as:
<actions></actions>

Our current plan to fix is to fork https://github.com/bbqsrc/xmlem and add an option to disable self-closing tags.

Our current plan fix is to fork https://github.com/bbqsrc/xmlem and add an option to disable self-closing tags.

Feel free to make a pull request and i can publish the fixes on cargo.

So, what next? I understand the pull request is now done.
From my perspective I would then like to have a working Mansi keyboard on PC (Mac and Windows), my coworkers are typing in hex codes. Does the code in keyboard-xxx (here: keyboard-mns) need any changes, and if so, what changes?

@bbqsrc the option to disable self-closing tags ended up causing other issues. MacOS being persnickety 😄
The fix was instead to remove the <actions \> tag altogether if it contained no children when generating MacOS layouts.
@Trondtr changes to keyboard-xxx repos should not be required for this fix to work on MacOS. I'm not sure about Windows though - are you having issue there too? If so please create an issue with details.
Next step is to merge this and then have kbdgen re-generate MacOS layouts so they're available in the nightly channel. Hopefully the merge will trigger that. Still learning the tool chain. Will merge (if no objections) and investigate how to deploy the layouts to nightly after lunch 😄

Please do merge.

@dylanhand rebuild of the keyboards do not happen automatically yet (cross-repo build deps have been planned, but not yet implemented). I will trigger new builds of the most critical keyboards as soon as the fix is merged and kbdgen has been rebuilt.

@snomos thanks for the info.
Just merged, so feel free to trigger new builds of the keyboards.

I was able to download and install Mns (Mansi) keyboard on my Mac M2 13.0.1
It seems to work fine in the command line, so I am happy.
The keyboards for mhr (Meadow & Eastern Mari), mrj (Hill Mari aka Western Mari), myv (Erzya), mdf (Moksha), kpv (Komi-Zyrian), yrk (Nenets), did not show up as possible keyboards to install.

@rueter all the mentioned keyboards have now been rebuilt to fix the issue. They also have a new version number. They should be available in Divvun Manager as updates.
For keyboards with a Sámi flag as menu item icon, it has been replaced with a best effort alternative. Feel free to suggest other flags or icons 😊

@snomos
The Cyrillic keyboards presently working are: myv, mdf, kpv
The mrj (Hill Mari aka Western Mari) keyboard is only partial. It contains none of the extras required for mrj, so we will have to work on that.
The mhr (Eastern & Meadow Mari) keyboard does not appear on my Ventura as a selectable, even after down loading it.
The udm keyboard, has a Saami flag and is, in fact, a Latin letter content. More work for us;)

Thanks for the feedback, I will look into the various points. Further discussion should take place in new issues specific for the relevant keyboards, if needed.
This issue is now fixed, thanks for reporting it 😊

authors: Trondtr bbqsrc dylanhand rueter snomos

repo: divvun/kbdgen


text:
🛑 Dixneuf19 website is down

In 2b5a889, Dixneuf19 website (https://www.dixneuf19.me) was down:

HTTP code: 504
Response time: 15459 ms

Resolved: Dixneuf19 website is back up in ed769af.


text:
🛑 Dixneuf19 website is down

In 1532138, Dixneuf19 website (https://www.dixneuf19.me) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dixneuf19 website is back up in 2bb701b after 8 minutes.


text:
Update About button (about.html)  to show the user profile

Can I work on this @diyajaiswal11

Can I work on this @diyajaiswal11

Similar issue has been raised in #13 . Go through it.


text:
Plugin does not appear on session start. Only appears after serialization-interval time.

Describe the bug
After updating to Zellij 0.39.1, the status line is not initially displayed after a session is started. After some time, the statusbar displays as normal.
To Reproduce
Steps to reproduce the behavior:

Update to Zellij 0.39.1
Start a zellij session using this plugin

It appears that the amount of time it takes for the status bar to appear is the same as Zellij's session serialization frequency. Starting a session with just zellij, it will take 60 seconds for  the status line to appear. 60 seconds is the new default session serialization frequency in 0.39.1. It was previously 1 second. Running zellij with zellij --serialization-interval 5, the statusline will appear after 5 seconds. With zellij --serialization-interval 20, it will appear after 20 seconds.
Expected behavior
Plugin should load immediately as it did on Zellij 0.39.0.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: 6.5.6-arch2-1
Zellij version: v0.39.1
Version: v0.9.0

Layout
How does the layout look like? Please copy it into a code block.
layout {
    pane split_direction="vertical" {
        pane
    }

    pane size=1 borderless=true {
        plugin location="file:/home/mike/.config/zellij/plugins/zjstatus.wasm" {
            format_left  "{mode}#[fg=#1a1c23,bg=#4fa6ed,bold]{session}#[fg=#4fa6ed,bg=#1a1c23]{tabs}"
            format_right "#[fg=#1a1c23,bg=#4fa6ed,bold]{datetime}"
            format_space "#[bg=#1a1c23]"

            border_enabled  "false"

            hide_frame_for_single_pane "true"

            tab_normal              "#[fg=#000000,bg=#4C4C59] {index}  {name} #[fg=#4C4C59,bg=#1a1c23]"
            tab_normal_fullscreen   "#[fg=#000000,bg=#4C4C59] {index}  {name} Z #[fg=#4C4C59,bg=#1a1c23]"
            tab_normal_sync         "#[fg=#000000,bg=#4C4C59] {index}  {name} S #[fg=#4C4C59,bg=#1a1c23]"
            tab_active              "#[fg=#1a1c23,bg=#ffffff,bold] {index}  {name} #[fg=#ffffff,bg=#1a1c23]"
            tab_active_fullscreen   "#[fg=#1a1c23,bg=#ffffff,bold] {index}  {name} Z #[fg=#ffffff,bg=#1a1c23]"
            tab_active_sync         "#[fg=#1a1c23,bg=#ffffff,bold] {index}  {name} S #[fg=#ffffff,bg=#1a1c23]"

            datetime        "#[fg=#1a1c23,bg=#4fa6ed,bold] {format} "
            datetime_format "%A, %Y%m%d %H%M"
            datetime_timezone "America/Los_Angeles"

            mode_normal        "#[fg=#1a1c23,bg=#4fa6ed,bold]  NORMAL "
            mode_locked        "#[fg=#1a1c23,bg=#e55561,bold]  LOCKED "
            mode_resize        "#[fg=#1a1c23,bg=#e2b86b,bold]  RESIZE "
            mode_pane          "#[fg=#1a1c23,bg=#e2b86b,bold]   PANE  "
            mode_tab           "#[fg=#1a1c23,bg=#e2b86b,bold]   TAB   "
            mode_scroll        "#[fg=#1a1c23,bg=#e2b86b,bold]  SCROLL "
            mode_enter_search  "#[fg=#1a1c23,bg=#e2b86b,bold] ENTER SEARCH "
            mode_search        "#[fg=#1a1c23,bg=#e2b86b,bold]  SEARCH "
            mode_rename_tab    "#[fg=#1a1c23,bg=#e2b86b,bold] RENAME TAB "
            mode_rename_pane   "#[fg=#1a1c23,bg=#e2b86b,bold] RENAME PANE "
            mode_session       "#[fg=#1a1c23,bg=#e2b86b,bold] SESSION "
            mode_move          "#[fg=#1a1c23,bg=#e2b86b,bold]   MOVE  "
            mode_prompt        "#[fg=#1a1c23,bg=#e2b86b,bold]  PROMPT "
            mode_tmux          "#[fg=#1a1c23,bg=#8ebd6b,bold]   TMUX  "
        }
    }
}

Awesome thanks for the quick fix

Hey,
the fix is available with the new release (0.9.1). Seems to work on my side. Hope this resolves the issue.


text:
Add more customizable blocks in import.html

Problem
Fields detail and definition cannot easily be overriden in import.html unless you overrite the whole import_form block.
Solution
This PR adds sub-blocks in import_form block to allow overide forms parts more easily.

Thanks, feel free to add your name to AUTHORS

Done, thank you!

Thanks - we had an issue with an upstream lib which caused the build to fail.  I've fixed that.  I'd be grateful if you could merge the main branch and re-push your change.

Done.

authors: christophehenry matthewhegarty


text:
Get more info on tasks

Hello,
Is there a way to know the cluster / machine used by a task ?
I guess I could add it in the result for the successful ones but how would it be done for failures / queued ones (maybe the most important ones)
Thanks,

Couldn't get this through the Q_CLUSTER_NAME environment variable?

Yes, actually the cluster name can be found. For the machine I guess I'll have to save it as a variable (as few clusters can have the same name across different machines)

authors: GDay ThomasDeudon


text:
Removed unnecessary line in OrderBy.as_sql().

The first line of as_sql (https://github.com/django/django/blob/ed0cc52dc3b0dfebba8a38c12b6157a007309900/django/db/models/expressions.py#L1213) is a duplicate of this line that's being removed, meaning that in this function template is already defined in the same manner, making this line a noop.

@davidjb Thanks :+1: Good catch :dart:

authors: davidjb felixxm

repo: django/django


text:
Fixed #29026 -- Added --scriptable option to makemigrations.

ticket-29026 desires to separate logging from a simple list of filepaths created in makemigrations.

Today, there is logging to both stdout and stderr (for errors), but no real "program output": the filenames are bolded and indented to flow between other log messages.
This PR creates a new option --scriptable that will 1. divert all current logging to stderr and 2. log only the filepaths of created migration files to stdout, one per line (without leading spaces and styling)
--noinput mode is still necessary to suppress input completely, otherwise interactive prompts go to stderr when --scriptable is used

EDIT: moved ticket-29470 solution to #14805
All of this logging can be silenced with --verbosity 0: no changes in this respect.

The thing with structured is that text lines aren't that structured. To me that sounds more like json.

Very reasonable--I'll think about a name for this option.

It seems like the user-facing option should be more about whether logging should go to stderr. Then the non-logging ("output") lines would continue to go to stdout as is.

My thought process was this: merely switching the output to stderr is achievable today: you simply subclass the command and set self.stdout to whatever you want, sys.stderr, or whatever. I'm not sure we would add complexity if that were the only thing we were achieving. I think the reason for this PR is that we don't have any "non-logging/output" lines today, since this is not really nonlogging (leading spaces, hyphen, colors):
\x1b[1m/var/folders/6q/jljmh5xs27v8_7557q3rgtfw0000gn/T/django_klnxitjw/tmpwiefzufk/tmp82ptgwlr/migrations/0001_initial.py\x1b[0m\n

My thoughts would be to add an initial commit that adds a log() method and makes all stderr / stdout output go through that.

So I'm a little hesitant to do to this, because then we're making makemigrations more special than the other commands. This ticket is asking to make makemigrations more special by producing different kinds of output, so I guess we're already starting down that path.

Also, in the case that logging is going to stderr, I think you'd still want to log the output lines using log() as a message, so that info would be available both in the diagnostic stderr logs, as well as the output.

Agreed, I made sure this was the case.

Any thoughts on the ticket-29470 stuff? If we have design questions about ticket-29026 I could ask the fellows to re-triage 29470 and move it to a separate PR to keep it moving.

btw, thanks for the review, @cjerdonek! And it looks like I need to liberalize one of the tests to pass on Windows.

Maybe --separatelogs?
Everything but the last line going to stderr, last line to stdout:
Migrations for 'migrations':
  /var/folders/6q/jljmh5xs27v8_7557q3rgtfw0000gn/T/django_e_o35bow/tmpso0994dn/tmp7ogni0kc/migrations/0001_initial.py
    - Create model ModelWithCustomBase
    - Create model SillyModel
    - Create model UnmigratedModel
/var/folders/6q/jljmh5xs27v8_7557q3rgtfw0000gn/T/django_e_o35bow/tmpso0994dn/tmp7ogni0kc/migrations/0001_initial.py

you simply subclass the command

This didn't feel right when I wrote it, and indeed--it's easier than that, there's call_command(stdout=), see: https://docs.djangoproject.com/en/3.2/ref/django-admin/#output-redirection
The drift of my earlier comment was that I would be hesitant to rework the documented API we have for that. I see the issue as more defining wanting separate logs, period.

To respond to one point now:

My thoughts would be to add an initial commit that adds a log() method and makes all stderr / stdout output go through that.

So I'm a little hesitant to do to this, because then we're making makemigrations more special than the other commands.

I think making log() a method that is passed a message is more natural and has advantages over making it an attribute with a write() method. For example, it would give people a way to use a Python logger instead of writing to a stream. This is the approach taken in this commit for ticket #14150. Also, the word "log" is more commonly used in Python as the verb / method name rather than the stream (see e.g. Logger.log() in Python's logging module). It would also make the calling sites simpler / cleaner. Finally, if this pattern is found useful, it could be moved to BaseCommand so makemigrations.py wouldn't be so special.

Also, the word "log" is more commonly used in Python as the verb / method name rather than the stream (see e.g. Logger.log() in Python's logging module).

I have to admit, this did occur to me when I was writing it, and if you also noticed it, lots of folks will. :-O

For example, it would give people a way to use a Python logger instead of writing to a stream. This is the approach taken in this commit for ticket #14150.

That's a good reason.

Finally, if this pattern is found useful, it could be moved to BaseCommand so makemigrations.py wouldn't be so special.

I guess I wasn't looking at it that way. 👍🏻    Thanks for the quick feedback, and I'll have a look at implementing a log() method.

Maybe --separatelogs?

Maybe --scriptable or --scriptmode? The option seems like a higher-level mode as it does two things: it changes logging to go to stderr, and it adds additional info to stdout.

Maybe --scriptable or --scriptmode?

At a glance, I would be a bit worried it implies setting --noinput can be skipped when using in a script.

At a glance, I would be a bit worried it implies setting --noinput can be skipped when using in a script.

I think there's an argument the mode should imply --noinput. The reason is that, when programmatically consuming the stdout (e.g. piping it to a file), you wouldn't see the prompt anyways. (It would show up to the user as a hang.) This is because the command's questioner uses Python's input() built-in, which writes to stdout. So it seems incompatible with consuming stdout for programmatic use. Maybe you could write a prompt to stderr, but that seems non-standard.
Either way, I think you'd want to document in the help whether --noinput is implied, which should eliminate any worries.

Reading and thinking more about Python's input() and how --noinput behaves, I think the scriptable mode option we're discussing in this PR shouldn't default to --noinput, and when it's used, the questioner should write its prompt to stderr instead of stdout (and not use log()). There are a couple reasons for the latter. First, there is a very old Python ticket to change input() to use stderr, so it wouldn't actually be non-standard to use stderr like I suggested in my comment above. Secondly, if the mode didn't use stderr, then there would be no way to use scriptable mode while capturing the output stream (one of its intended use cases) when answers are required that differ from the default answers when --noinput is used. Lastly, I said "not use log()" because if someone, say, changed log() to log to a file, you would still want the prompt to go to stderr so the user could provide interactive feedback.
Also, on this question:

Any thoughts on the ticket-29470 stuff?

After reading and thinking about it, I think it should be re-opened and handled separately. I can go ahead and add a comment to the ticket.

Hello @francoisfreitag -- I noticed you have a WIP branch for ticket-21429 implementing logging for each of the management commands. As you can see above, Chris is making the good case that to move this PR forward, I should do something similar for makemigrations. Are you still interested in contributing your work? If #13853 is the only blocker, we can see about getting it into the review queue. Let me know if I can be helpful in any respect. 👍🏻

@jacobtylerwalls By the way, regarding the log() method I was suggesting you add above, the collectstatic management command is another class that already has a method like that: https://github.com/django/django/blob/8208381ba6a3d1613bb746617062ccf1a6a28591/django/contrib/staticfiles/management/commands/collectstatic.py#L207-L212
It will be of help here independent of that ticket.

Hi @cjerdonek,
Thanks for the ping! Fixing ticket-21429 is pretty time consuming and personal life has been busy (and will be for at least a few months). My employer is not interested in sponsoring the work for now, so it’s all on my personal time.
Basically, my todo list includes:

rebasing on main (last rebase was probably 9 months ago)
a readthrough, making sure:

assertNoLogs and assertLogRecords are used where possible
reviewing uses of io, StringIO, stdout and stderr in test code
code polish (e.g. grouping context managers, preferring single quotes, f-strings, etc)

consider introducing flake8-logging-format
installing my branch on an existing project shows unexpected line returns if I don’t change the existing project config. Needs investigation.
Completing the documentation
Testing against all DBs. I tried to use exact assertions for the logging output as much as possible, but different DB engines or configuration may cause messages to change slightly.

#13853 is just a very early step, introducing tools I would like to use for the logging PR. I’m afraid there are weeks of work remaining before my branch can be put up for review, and I am not able to commit to a timeline.

Thanks for the update. I certainly wouldn't ask you to commit to a timeline! I was just merely curious if I should try to conform to any likely pending changes. I think I have enough to go on for now. Good luck with everything, and be well. --Jacob

Thanks for the design guidance @cjerdonek , that was very helpful. I haven't squashed/reordered commits yet, and I am still thinking about https://github.com/django/django/pull/14751#discussion_r684664382, but I wanted to ask if you thought these changes were looking right-track to you. I'd be grateful if you had time for a re-review.
I didn't as of yet tackle a refactor of how verbosity is tracked. There's enough going on (and I feel like this PR is already two or so.) Speaking of which, thanks for commenting on ticket-29470.

The first one I'd recommend is a refactoring PR that just adds a log() method, and in particular doesn't make any reference to scriptable, etc. The next step PR can be discussed after that.

Done! :tada:
https://github.com/django/django/pull/14936

Summary:
Adds --scriptable flag to makemigrations, causing:

log() method to divert output to self.stderr (agreement on this here: "whether log() uses stderr or stdout could be controlled centrally in that method")
Interactive questioner to divert prompts to self.stderr (agreement here)
an additional line of "clean output" (no styling or indentation) written to self.stdout (original case from ticket)

That's all the diff does, it's just bloated because the interactive questioner was using print() statements, which had to be rewritten. I can move that to another commit (or PR?) if folks like.
Could also be good to rebase after #15212.

@jacobtylerwalls Thanks :+1:
I added writing a path of generated migration file to the --merge option (with tests) and pushed small edits.

@felixxm Thanks for the updates and the additional test!

authors: cjerdonek felixxm francoisfreitag jacobtylerwalls


text:
Added username in AbstractBaseUser as a index

I changed this

from this

Q Why I did this
A This field is used for login user and find user to most of time, as the number of user increases applications get slow in finding users by usernames. So I thought to add this in that. Every time I have to create a custom user field and I think most of developers does too. I think this will help for beginners too.

db_index is unnecessary as this field is already marked as unique.