text:
[Uncaught in Promise] Invalid Basetexture

I was playing with the cover calculation and once finished I removed the player token from the canvas, moved monster tokens back to their rooms and then reset fog of war. Everytime I open the scene now I get these errors:

Oh an I just noticed that one of the monster tokens isn't accessible anymore. Looks like part of the backdrop.
I can't even select it. o.O
Disabling 5ehelper didn't resolve the issue either. It still tries to load that image.

Ok - I was able to open the scene in another browser (Firefox was broken, Chrome worked). The token has this cover status indicator:

I believe this is addressed by #176 . Please re-open if you still experience issues related to this.

authors: tagnullde trioderegion


text:
What is the use of macro CHECK in below code?

Hi,
When I look at the tensorRT inference code (csrc/detect/normal/include/yolov8.hpp), in many places CHECK has been called to look for some errors. For example, see below
CHECK(cudaMemcpyAsync(
        this->device_ptrs[0], nchw.ptr<float>(), nchw.total() * nchw.elemSize(), cudaMemcpyHostToDevice, this->stream));

I am not understanding the use of CHECK. What it is doing and is it mandatory to have CHECK?
CHECK expands as below.
#define CHECK(call)
    do {
        const cudaError_t error_code = call;
        if (error_code != cudaSuccess) {
            printf("CUDA Error:\n");
            printf("    File:       %s\n", __FILE__);
            printf("    Line:       %d\n", __LINE__);
            printf("    Error code: %d\n", error_code);
            printf("    Error text: %s\n", cudaGetErrorString(error_code));
            exit(1);
        }
    } while (0)

Just for checking cuda api return error.
Here https://docs.nvidia.com/cuda/cuda-runtime-api/group__CUDART__ERROR.html

Hi @triple-Mu
Sorry for delayed reply. I was off from work.
So, basically, if I comment out CHECK, meaning if I run the code like below, that means I will not catch the error. Is my understanding right?
cudaMemcpyAsync(
        this->device_ptrs[0], nchw.ptr<float>(), nchw.total() * nchw.elemSize(), cudaMemcpyHostToDevice, this->stream);

The reason I am asking is,
We are integrating your code in Gstreamer/Deepstream platform. If we run single instance of your code, we are not getting any error in cudaMemcpyAsync line, however, if we run 2 (two) instances of your code parallelly, we get error at cudaMemcpyAsync line.
Do you think it is something related to synchronization?

Hi @triple-Mu Sorry for delayed reply. I was off from work. Thank you for your reply.
So, basically, if I comment out CHECK, meaning if I run the code like below, I will not catch the error which might occur during cudaMemcpyAsync. Is my understanding right?
cudaMemcpyAsync(
        this->device_ptrs[0], nchw.ptr<float>(), nchw.total() * nchw.elemSize(), cudaMemcpyHostToDevice, this->stream);

The reason I am asking is, We are integrating your code in Gstreamer/Deepstream platform. If we run single instance of your code, we are not getting any error in cudaMemcpyAsync line, however, if we run 2 (two) instances of your code parallelly, we get error at cudaMemcpyAsync line. Do you think it is something related to synchronization? or race-condition?

Do you mean two process?
I think it doesn't matter if you open two process.

Thanks @triple-Mu

source: gharchive/issue

authors: aravindchakravarti triple-Mu

license: MIT

license_type: permissive

license_source: github-api


text:
Sc-4687 : fix form legal validation in certificate flow && Minor fixes

This PR contains other stories fixes :

fixed legal form validation certificate flow sc-4687
Added spaces between vasp categories sc-4693
Fixed the establishment misspelling sc-4696
Fixed error in legal person review component

Codecov Report

Merging #465 (6c67fbe) into main (7d199b6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #465   +/-   ##
=======================================
  Coverage   46.94%   46.94%
=======================================
  Files         233      233
  Lines       11673    11673
  Branches      608      608
=======================================
  Hits         5480     5480
  Misses       5234     5234
  Partials      959      959

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 7d199b6...6c67fbe. Read the comment docs.

source: gharchive/pull-request

authors: codecov-commenter masskoder

repo: trisacrypto/directory


text:
Support for 204/205 response HTTP status code?

The default AlamoFire response handlers don't error out when encountering an empty response body and a 204 (or 205 status code). Does AlamofireObjectMapper handle this differently for some reason (it seems to error out with 'ObjectMapper failed to serialize response.')? Here is an Issue that touches on how they handle it:
https://github.com/Alamofire/Alamofire/issues/1813

Another Issue touching on it here:
https://github.com/Alamofire/Alamofire/issues/1673
"The reason the 204 status call works is that the responseJSON handler has logic to handle a 204 or 205 gracefully without failing. They are special HTTP status codes that do not return data so we have special logic in Alamofire to handle them in the default response handlers."

Hi, Is there any update or way of doing this in "AlamofireObjectMapper"?

authors: chadpod philipborbon

repo: tristanhimmelman/AlamofireObjectMapper

license: mit

license_source: bigquery


text:
How to undo changes executed while trying youtube-viewer?

How do I roll-back the command 'perl -pi -ne 's{DEVEL = 0}{DEVEL = 1}' {gtk2-,gtk3-,}youtube-viewer'?
I followed the instructions to try youtube-viewer without installing.  Afterwards, I want to roll back any changes to my system but I cannot figure out how to undo the above perl command.  The perl man pages are no help whatsoever.  I do not want to leave those changes to my system.  I don't usually run commands that I don't understand prior to running them but I made an exception this time, now I want to undo those changes.

After trying youtube-viewer without installing it, youtube-viewer creates its configuration folder on ~/.config/youtube-viewer, which can be removed with the following command:
rm -r ~/.config/youtube-viewer

If LWP::UserAgent::Cached is installed, then some files may be cached in ~/.cache/youtube-viewer, which can be removed with:
rm -r ~/.cache/youtube-viewer

This are the only changes made by youtube-viewer to your system.
The command (see also perl -h):
perl -pi -ne 's{DEVEL = 0}{DEVEL = 1}' {gtk2-,gtk3-,}youtube-viewer

just changes DEVEL = 0 to DEVEL = 1 inside the temporary files in /tmp/youtube-viewer-master/bin/.
To remove the /tmp/youtube-viewer-master directory, execute:
rm -r /tmp/youtube-viewer-master

(although the temporary files in /tmp/ are automatically removed after a reboot)

authors: Amandaville trizen

repo: trizen/youtube-viewer


text:
Reapply next-prev post links

前後記事へのリンクを復活させます

LGTM

本番にデプロイしたらルーティングしてたので、restoreする

authors: miyaoka trkw

repo: trkw/trkw


text:
Minus Scores

Issue

Currently answering a question wrong with timeLeft <15 results in a negative (sub-0) score.

Solution

Set if in JS.

Fixed in #14

repo: trnigg/mc-coding-quiz


text:
Fixing problem with .pdb files in Debug version

replacing the default /Zi in MSVC with /Z7, so that the debugging information ends up embedded in the .lib file rather than separate .pdb files.
forcing cmake to override the default cache

Hi @ThibaultDECO - while my understanding of cmake is limited, do you still remember why you thought it was a good idea to have debug symbols included in the library binary? If MSVC offers to have debug information in separate files, why not make use of that?

Hi @aral-matrix
Unfortunately, I don't remember, it was too long time ago

Thanks for getting back to me / responding here anyways. Would you be okay to close (or for me to close) the pull request then?
I believe that your pull request implements something that was very specific to your use case, and even you yourself only needed it for debugging - so without really understanding the consequences or being able to properly test it, I would prefer to not accept this.

authors: ThibaultDECO aral-matrix

repo: troldal/OpenXLSX


text:
json-ld: Don't render fields in the output if they're not in the json mapping file

In some types we've added specific relations in order to generate filter queries for them:
https://github.com/trompamusic/ce-api/blob/24270a1f4d65bd3cc34a12b8dca0b9372454b34a/src/schema/type/MusicComposition.graphql#L176-L179
These fields are useful only for graphql, and shouldn't be rendered in the jsonld.
A good way to do this would be to remove these fields from the matching json file that contains the field->type mappings. If a field doesn't exist in this file it shouldn't be rendered

This functionality already exists, these fields were present in MusicComposition.json. I removed them and they're no longer in the output.

repo: trompamusic/ce-api


text:
🛑 Plex is down

In d3bc063, Plex (https://tronflix.app/plex/web/index.html) was down:

HTTP code: 520
Response time: 157 ms

Resolved: Plex is back up in 9b344e4.

repo: tronyx/upptime


text:
🛑 Radarr is down

In d4e4dfc, Radarr (https://tronflix.app/radarr/activity/queue/) was down:

HTTP code: 520
Response time: 122 ms

Resolved: Radarr is back up in e316d3f.


text:
Invariant Violation Error

I got the below mentioned error when application build and run.
I am using the following versions:
magento: 2.3
react-native-cli: 2.0.1
react-native: 0.59.10
OS : windows10
IMAGE SCREENSHOT FOR ERROR REFERENCE:

@Insha-Siddiquii have you done https://github.com/troublediehard/magento-react-native/wiki/Setup#2-setup-new-cms-block-in-magento-admin-which-will-be-used-in-homepage ? It looks like something wrong with your homepage config.

yeah i followed all setup guide and there was no problem in that. I inspected the problem , this was actually with react native that does not allow my store url to fetch data and initialize magento. Problem solved when i changed my store url  from http://localhost/xxxxx to http://ip-address:port/xxxx.

Happy to hear you solved it.

authors: Insha-Siddiquii troublediehard

repo: troublediehard/magento-react-native


text:
Test PR to test PR Labeler

Fixes

Reverting removes label

trying sync-labels=true

PR Labeler with
#         sync-labels: true

removes labels as well

repo: trsvchn/ignite


text:
Avoid using the "**" pattern

This was introduced in https://github.com/truckersmp-cli/truckersmp-cli/pull/287 and seems to be a plausible cause of #345
@Synthron Since you seem versatile in python, may I ask you to give this a try?
fix #345

I am actually quite new to python but I can try out the new routine and maybe find a bug or two.
my suggestion also would be to make a check whether the --without-wine-discord-ipc-bridge flag is used or not. If someone doesn't want to use the bridge, there is in my eyes no need to look for one in the first place
also may I suggest further debugging info in the terminal by adding to gamestarter.py something like
logging.info("Looking for wine-discord-ipc-bridge. If this takes too long, try starting with the '--without-wine-discord-ipc-bridge' option.")

came around testing it, game now starts perfectly.
Even without the --without-wine-discord-ipc-bridge it works, no critical errors in the logs as far as I can see
a log dump from the game start here just for completeness:
command: truckersmp-cli start ets2mp -vv --native-steam-dir /home/marco/.steam/
output:
** INFO **  Platform is Linux, using Proton
** INFO **  Log file: <empty> (Default)
** INFO **  Game directory: /home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/data (Default)
** INFO **  Prefix directory: /home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/prefix (Default)
** INFO **  Game options: -nointro -64bit (Default)
** INFO **  TruckersMP MOD directory: /home/marco/.local/share/truckersmp-cli/TruckersMP (Default)
** INFO **  Whether to disable Steam Runtime (deprecated): False (Default)
** INFO **  Whether to disable Steam Runtime: False (Default)
** INFO **  Whether to use Flatpak version of Steam: False (Default)
** INFO **  Whether to disable Steam Overlay: False (Default)
** INFO **  Proton directory: /home/marco/.local/share/truckersmp-cli/Proton (Default)
** INFO **  Steam Runtime directory: /home/marco/.local/share/truckersmp-cli/SteamRuntime (Default)
** INFO **  Rendering backend: gl (Default)
** INFO **  AppID/GameID: 227300 (ets2)
** DEBUG **  Updating mod files
** DEBUG **  Creating directory /home/marco/.local/share/truckersmp-cli/TruckersMP if it doesn't exist
** DEBUG **  No files to download
** INFO **  Proton version is (major=8, minor=0)
** INFO **  Using Steam Runtime container
** DEBUG **  Steam is running
** INFO **  Steam installation directory: /home/marco/.steam/
** DEBUG **  Shared paths: ['/home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/data', '/home/marco/.local/share/truckersmp-cli/Proton', '/home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/prefix', '/home/marco/.local/share/truckersmp-cli', '/home/marco/.local/share/truckersmp-cli/TruckersMP', '/home/marco/.local/lib/python3.10/site-packages/truckersmp_cli', '/run/user/1000/discord-ipc-0', '/run/user/1000/discord-ipc-1']
** DEBUG **  Created starter for Proton
** INFO **  Starting game
** DEBUG **  Creating directory /home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/prefix if it doesn't exist
** DEBUG **  Whether to setup native d3dcompiler_47: False
** INFO **  Running Steam Runtime helper:
  SteamAppId=227300
  SteamGameId=227300
  LD_PRELOAD=/home/marco/.steam/ubuntu12_64/gameoverlayrenderer.so
  PROTON_USE_WINED3D=0
  STEAM_COMPAT_CLIENT_INSTALL_PATH=/home/marco/.steam/
  STEAM_COMPAT_DATA_PATH=/home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/prefix
  python3
    /home/marco/.local/share/truckersmp-cli/Proton/proton
    run
    /home/marco/.local/lib/python3.10/site-packages/truckersmp_cli/truckersmp-cli.exe
    /home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/data
    /home/marco/.local/share/truckersmp-cli/TruckersMP
      -rdevice gl -nointro -64bit
** DEBUG **  winediscordipcbridge.exe is present, MD5 is OK.
** DEBUG **  Helper arguments: ['/home/marco/.local/share/truckersmp-cli/SteamRuntime/run', '--filesystem', '/home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/data', '--filesystem', '/home/marco/.local/share/truckersmp-cli/Proton', '--filesystem', '/home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/prefix', '--filesystem', '/home/marco/.local/share/truckersmp-cli', '--filesystem', '/home/marco/.local/share/truckersmp-cli/TruckersMP', '--filesystem', '/home/marco/.local/lib/python3.10/site-packages/truckersmp_cli', '--filesystem', '/run/user/1000/discord-ipc-0', '--filesystem', '/run/user/1000/discord-ipc-1', '--', 'python3', '/home/marco/.local/lib/python3.10/site-packages/truckersmp_cli/steamruntime_helper.py', '--early-executable', '/home/marco/.local/share/truckersmp-cli/wine-discord-ipc-bridge/winediscordipcbridge.exe', '--early-wait-before-start', '5', '--wait-before-start', '0', '-vv', '--', 'python3', '/home/marco/.local/share/truckersmp-cli/Proton/proton', 'run', '/home/marco/.local/lib/python3.10/site-packages/truckersmp_cli/truckersmp-cli.exe', '/home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/data', '/home/marco/.local/share/truckersmp-cli/TruckersMP', '-rdevice', 'gl', '-nointro', '-64bit']
ERROR: ld.so: object '/home/marco/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/home/marco/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/home/marco/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/home/marco/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
x86_64-linux-gnu-capsule-capture-libs: warning: Dependencies of libnvidia-pkcs11.so.535.171.04 not found, ignoring: Missing dependencies: Could not find "libcrypto.so.1.1" in LD_LIBRARY_PATH (unset), ld.so.cache, DT_RUNPATH or fallback /lib:/usr/lib
ERROR: ld.so: object '/tmp/pressure-vessel-libs-4LQEN2/${LIB}/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Setting breakpad minidump AppID = 227300
Steam_SetMinidumpSteamID:  Caching Steam ID:  <redacted> [API loaded no]
Executables (early): ['/home/marco/.local/share/truckersmp-cli/wine-discord-ipc-bridge/winediscordipcbridge.exe']
Executables: None
Game Arguments: ['python3', '/home/marco/.local/share/truckersmp-cli/Proton/proton', 'run', '/home/marco/.local/lib/python3.10/site-packages/truckersmp_cli/truckersmp-cli.exe', '/home/marco/.local/share/truckersmp-cli/Euro Truck Simulator 2/data', '/home/marco/.local/share/truckersmp-cli/TruckersMP', '-rdevice', 'gl', '-nointro', '-64bit']
Waiting time (early): 5
Waiting time: 0
Proton output:
ERROR: ld.so: object '/tmp/pressure-vessel-libs-4LQEN2/${LIB}/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/tmp/pressure-vessel-libs-4LQEN2/${LIB}/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/tmp/pressure-vessel-libs-4LQEN2/${LIB}/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/tmp/pressure-vessel-libs-4LQEN2/${LIB}/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/tmp/pressure-vessel-libs-4LQEN2/${LIB}/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Setting breakpad minidump AppID = 227300
Steam_SetMinidumpSteamID:  Caching Steam ID:  <redacted> [API loaded no]
ERROR: ld.so: object '/tmp/pressure-vessel-libs-4LQEN2/${LIB}/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/tmp/pressure-vessel-libs-4LQEN2/${LIB}/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/tmp/pressure-vessel-libs-4LQEN2/${LIB}/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

not sure what causes the ld.so errors, but game starts and runs smooth

my suggestion also would be to make a check whether the --without-wine-discord-ipc-bridge flag is used or not. If someone doesn't want to use the bridge, there is in my eyes no need to look for one in the first place

While this looks like the easier fix, this still leaves the same problem when using the bridge.
The way I've done it should fix both use-cases, it's just a simple file finding after all.

While this looks like the easier fix, this still leaves the same problem when using the bridge.

true, but I was more referencing the fact that it is looking for something that will never be used if the flag is set.
but with the fix it now starts repeatedly and quickly, so yay :)

authors: Lucki Synthron

repo: truckersmp-cli/truckersmp-cli


text:
Update README.md

Small phrasing changes.

@gaspard thank you :)

authors: gaspard trueadm

repo: trueadm/inferno


text:
Throw error for children passed in as Components not templates.

May not be the best way to handle this, but at least provides a nice error message back to the source for this.
Added informative error message when children contain Components.
Added test for error thrown when children contain Components.

More of a future consideration -- but should checks/errors like this only happen in when NODE_ENV=development?

More of a future consideration -- but should checks/errors like this only happen in when NODE_ENV=development?

@tejacques I idea to think about!

@tejacques I idea to think about!

authors: Kflash Svjard tejacques


text:
Vue3 Inertia - Failed to resolve component: inertia-link

Fresh Laravel installation now uses different Register.vue template.
Running vendor:publish will nowdays overwrite template to old one causing warning in console.

Pull request which will fix the issue for new installations requested. #5
New implementation of Register.vue with this package to copy/paste also here: https://github.com/lukasirsak/jetstream-team-invites/blob/main/src/resources/js/Pages/Auth/Register.vue

Pull request which will fix the issue for new installations requested. #5
New implementation of Register.vue with this package to copy/paste also here: https://github.com/lukasirsak/jetstream-team-invites/blob/main/src/resources/js/Pages/Auth/Register.vue

Thanks @lukasirsak — We'll count this as the solution for now!

authors: kevnk lukasirsak

repo: truefrontier/jetstream-team-invites


text:
Lumina start menu icon at top left, menu items in the right-hand half of the screen with an expanse of grey to their left

Bugging an admin account that I rarely use, this shot was taken on 2016-11-06:

I can't tell when the bug began, nor can I imagine how it might be made reproducible … sorry.

Afterthought, maybe worth mentioning: this is on an HP EliteBook 850G2 notebook where TrueOS Desktop never drives the display that's integral to the notebook. It drives:

at home, a VGA display at DP-2 with a resolution of 1,366x768 pixels
at work, when docked, two displays on DisplayPort and one of the two is much larger (maybe 1,900x1,200).

I thought the menu size thing should be fixed now.  Do you know what version of Lumina you are running on that machine?

Since you've updated Lumina, are you still having this problem?

Yes, with 1.1.2 (Git Revision: d5a55a0).
With the customised panel at the top, the problem persisted, so I added a panel at the bottom.
The panel at the top unexpectedly disappeared, that's probably another symptom of #304.
A shot of start menu in the new, default panel 1 at the bottom:

With a different user 'test', on the same computer, the symptom is not evident:

I'll review the display preferences for the original user …

The start menu keeps/re-uses it's last size information the next time it is started up (~/.config/lumina-desktop/pluginsettings/desktopsettings.conf- look for the[panelPlugs]` section).
You probably just expanded the menu as large as possible when testing something out. You should be able to grab one of the menu edges and resize it smaller again as well.

No recollection of ever expanding the menu, I had no idea it was possible.

… You should be able to grab one of the menu edges and resize it smaller again as well.

Yep, I found the top left corner easiest to grab, pull down and to the right until the menu was entirely disconnected from its icon. Disconcerting, but it had the required effect after I allowed the menu disappear.
Thanks

My admin/wheel account (first created) still has this bug.
At 640x480 and 800x600 the app launcher is "double wide". At 1024x768 it works fine. This is run in
VirtualBox Version 5.1.12 r112440 with extensions on an OS X 10.11.6 host.
VBox Screenshot:

repo: trueos/lumina


text:
Fallback error handling is sketchy

See https://github.com/trufflesuite/uws-js-unofficial/blob/d91c4d02be0b1eafd156aa4b85786f5a1a21e181/src/fallback/websocket.ts#L22-L32
What cases are we missing? How can we figure it out to align them better?

Also of interest is this comment in uWebsockets about why the close code is 1006 instead of 1009.

repo: trufflesuite/uws-js-unofficial


text:
adding Sass's multi-line comment syntax to docs

I imagine using Hologram in addition to my normal Compass or SassC compiling, not in place of it.
To do this without getting errors, you need to use Sass's multi-line comments "//". but the docs only have single line: "/*".
I'm sure future developers would appreciate that in the docs, it's a bit of a nuance.

I know this issue is closed and I've seen it brought up a couple of times, but what would be nice is to allow single-line comments for those that use linting programs and have setup for single line comments.

Hmm, what change are you looking?

authors: gvinter jamierytlewski jdcantrell

repo: trulia/hologram


text:
bedrite, dibenzyl

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,d]

/trunk merge

repo: trunk-io/mergequeue-staging


text:
friend, bracketwise

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,f]

/trunk merge


text:
bantam, asianic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,b]

/trunk merge


text:
gamed, deterration

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,g]

/trunk merge


text:
faked, aeroview

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,f]

/trunk merge


text:
exhortations, browd

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,e]

/trunk merge


text:
feoffment, erosely

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[e,f]

/trunk merge


text:
frontier, beets

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,f]

/trunk merge


text:
dangs

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d]

/trunk merge


text:
cestuy, endearment

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,e]

/trunk merge


text:
barology, gingerwort

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,g]

/trunk merge


text:
gastrologer, exasperation

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[e,g]

/trunk merge


text:
butterflower, geoduck

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[b,g]

/trunk merge


text:
bedding, eristalis

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,e]

/trunk merge


text:
emulgent, aviarist

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 30
deps=[a,e]

/trunk merge


text:
cottier, exacum

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 30
deps=[c,e]

/trunk merge


text:
extrapelvic, dovecotes

This pull request was generated by the 'mq' tool

/trunk merge


text:
gorgonacea, enaluron

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[e,g]

/trunk merge


text:
gaskings, elidible

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[e,g]

/trunk merge


text:
conjectures, aliturgical

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,c]

/trunk merge

repo: trunk-io/mergequeue


text:
connectionism, buffalos

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,c]

/trunk merge


text:
duopolies, alvus

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,d]

/trunk merge


text:
destining, granulosa

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[d,g]

/trunk merge


text:
dp

This pull request was generated by the 'mq' tool

/trunk merge


text:
corebel, gypsum

This pull request was generated by the 'mq' tool

/trunk merge


text:
colorationally, blackened

This pull request was generated by the 'mq' tool

/trunk merge


text:
elan, fenite

This pull request was generated by the 'mq' tool

/trunk merge


text:
gravels, counterprove

This pull request was generated by the 'mq' tool

/trunk merge


text:
fermentive, cinchomeronic

This pull request was generated by the 'mq' tool

/trunk merge


text:
ergocalciferol, damage

This pull request was generated by the 'mq' tool

/trunk merge


text:
gershom, costiferous

This pull request was generated by the 'mq' tool

/trunk merge


text:
fundamentalism, galimatias

This pull request was generated by the 'mq' tool

/trunk merge


text:
fadding, arshins

This pull request was generated by the 'mq' tool

/trunk merge


text:
abutted, ghbor

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,g]

/trunk merge


text:
bizcacha, attitudes

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,b]

/trunk merge


text:
geophilus

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[g]

/trunk merge


text:
ascochyta, dusenwind

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,d]

/trunk merge


text:
coracler, biplanal

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[b,c]

/trunk merge


text:
gunpowderous, eaning

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[e,g]

/trunk merge


text:
grievedly, achenial

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,g]

/trunk merge


text:
curtalax, fogus

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,f]

/trunk merge


text:
beefwood, embryoma

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[b,e]

/trunk merge


text:
functionalism, grammy

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[f,g]

/trunk merge


text:
frieda, brainwash

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[b,f]

/trunk merge


text:
blared, equipollency

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[b,e]

/trunk merge


text:
complexions, bundts

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,c]

/trunk merge


text:
caryota, footwarmers

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,f]

/trunk merge


text:
bleeding

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b]

/trunk merge


text:
germinate, euphorbiaceae

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[e,g]

/trunk merge


text:
gassings, dispending

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[d,g]

/trunk merge


text:
apathistical, geldesprung

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,g]

/trunk merge


text:
anaemic, galactin

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,g]

/trunk merge


text:
chrysamine, emblematicize

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,e]

/trunk merge


text:
gedanite, escortment

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[e,g]

/trunk merge


text:
Support skipping building for wasm32-unknown-unknown

Partially addresses https://github.com/trunk-rs/trunk/issues/830
This PR adds a new build_target config option, with 2 choices of wasm32-unknown-unknown (default) and none. The former works as it does now, the later skips the build altogether, allowing users to supply their own build commands via hook.

Thanks for the PR. I don't really see why it would be important to not build at all? As mentioned in the PR, I would assume that the user would want to provide the target explicitly. Being able to default to the project's default.

There are a lot of build configurations, and having a custom build command would allow people to use Trunk without waiting for Trunk to support them directly. It's an escape hatch for users to "do-it-yourself". Searching the GH issue list, there are a bunch waiting for official Trunk support, that could be solved by supplying custom build command.

https://github.com/trunk-rs/trunk/issues/719
https://github.com/trunk-rs/trunk/issues/670
https://github.com/trunk-rs/trunk/issues/732

In my particular case, my build command is a bit involved. It's something like cargo +nightly b --target=wasm64-unknown-unknown -Z build-std=std,panic_abort, with a whole bunch of RUSTFLAGS env vars. In addition, I already have it setup as cargo xtask build. I think there are ways to put those options into .cargo/config.toml and/or ENV variables, but honestly I don't wanna change that to fit Trunk.
Other reasons I can think of are for people using different build systems (not cargo) like buck, bazel, etc...

So what you are actually looking for is not to set the target, but to have a data-trunk-skip attribute?

So what you are actually looking for is not to set the target, but to have a data-trunk-skip attribute?

Yes, that would work for my current situation.
Looking forward I'd love to have native wasm64/wasi support from Trunk though. Would make it much easier to start new projects for those targets.

I absolutely agree that having wasm64 support would be cool. I am just not a fan of partial fixes. Having a skip attribute feels self-contained and valuable. Having full target support too.

Hmm I don't see any difference between build-target=none and data-trunk-skip. But then data-trunk-skip works for me too. I'm gonna change the PR to take that approach.

Should be released as 0.21.0-alpha.5.

authors: ctron wooden-worm

repo: trunk-rs/trunk


text:
[feat] Lock main branch while a release is in progress.

Does your feature request relate to a specific USWDS feature?
No this is related to dev flow and releasing
Is your feature request related to a problem? Please describe.
We should ensure that merges to main branch don't happen while a release is in progress.  Our single branch release flow calculates the changelog based on already merged work at that time and also determines the release version.  We don't want random changes being introduced anytime between when a release PR opens and the release is tagged on github after that release PR merges.
Describe the solution you'd like
Let's ensure our mainline branch is locked while a release is in process.  Make a  "Safe to Merge" GH action or danger check that fails when there is an open release PR to main.  Open release PRs can be identified either by their title ( chore(release)) and/or by label (release).
Describe alternatives you've considered
Using clear communication between devs can also be a way to avoid merging during releases.  However dependabot could still merge while a release is in progress.

@haworku I'm curious on a possible alternative here. Since it is possible for main to receive commits between anytime after the yarn release and before npm publish, the following process changes are easy to implement and don't involve worrying about code freezes or implementing automation. We could effectively solve this issue with just a couple of changes to our releasing docs:

Specify the "chore(release): [...]" commit when creating the tag in Github under Step 5:

Checkout the tag instead of main before running npm publish

Then our bullets for step 5 would look something like this, which should solve these problems:

Merge the PR and create a new release tag pointed at the release commit on Github. Use the same notes as release PR.

Pull down the release tag locally before publishing:

git fetch --tags
git checkout {TAG_VERSION}, e.g. git checkout 1.13.2

Publish the new package to npm: npm publish. You will be prompted for a MFA code.

You may need to npm login first.
Publishing access is limited to package owners. If you need access and don't have it, please contact @npm-admins on Truss Slack.

🏆 @brandonlenz makes sense to me!  Also good example of "Improve via marginal gains"

@haworku I tried it out with 1.14.0:

git fetch --tags
git checkout 1.14.0
npm publish

I'll make a PR to the release process docs for the deliverable for this issue

@haworku actually this doesn't quite do what I was hoping because of the way we squash commits and delete the release branch on merge. So the release commit is actually the commit on main, NOT the commit from standard-version.
Sooo I'll hold off on that PR to update the docs.

Eh, I'd vote to leave the current release process alone in that regard. Creating the tag on github does the release notes too in one step. I'd worry about someone messing something up in their command line who is new to the release process.
I really think we ultimately need to  move towards something that automates tags. I used to use semantic release  heavily (we had releases weekly for different small libraries) and liked it.  I made this issue to capture that work or alternatives to automated tagging:  https://github.com/trussworks/react-uswds/issues/326
This issue about locking main was really just about a stop gap measure until we do something better.

Closing this ticket, no longer needed because our release process has changed and we point release tags now at a specific commit hash not the main branch.

authors: brandonlenz haworku

repo: trussworks/react-uswds


text:
What's the difference between a vulnerability and an advisory?

<jcrossley3> do you have good definitions for "vulnerability" and "advisory"?
	     i conflate them, too.  [14:05]
<bobmcw> Yes!  [14:27]
<bobmcw> A vulnerability is, in our world, only/exactly a CVE from NVD.
<bobmcw> What confounds things is that NVD also generally issues an *advisory*
	 with the same name ("CVE-123") that then gives scores, what's
	 affected, which versions, etc.  [14:28]
<bobmcw> all GHSA are advisories.
<bobmcw> All RHSA are advisories
<bobmcw> our VEX/CSAF are computer-parsable advisories
<bobmcw> OSV/Snyk are neither vulnerability sources nor advisory
	 producers. They aggregate other advisories about vulnerabilities, and
	 allow you to find them via a purl/hash/whatever.  [14:29]
<bobmcw> OSV/Snyk add very little value, really.
<bobmcw> We could directly consume the same DBs that OSV does, load into our
	 $GUAC, and we can then replicate OSV.
<bobmcw> so, CVE-123 existing ("buffer overrun in a crypto library") is one
	 thing.  [14:30]
<bobmcw> CVE-123 advisory would be "CVE-123 is known to affect libopenssl.so
	 v1.2 through v1.3"
<bobmcw> GHSA/RHSA/VEX/CSAF would also be an advisory "while libopenssl.so
	 v1.2.4 is in RHEL, we have decided it's not a problem"  [14:31]
<bobmcw> Snyk/OSV -> "Hey, I see you're using RHEL, check out GHSA-ghas8f,
	 RHSA-123 and CVE-123"
<bobmcw> There *can* exist vulnerabilities outside of the CVE system, but
	 generally it'll be "INTERNAL_APPLE_VULN-97" which you only kinda get
	 a sense from when iOS has an update saying "fixed some
	 vulnerabilities"  [14:32]
<bobmcw> it may or may not be tied/related to a CVE.
<bobmcw> Applicable to folks like JPMC/Bloomberg, because they have teams of
	 folks writing internal libraries/services.
<bobmcw> "bloomberg-ticker-scroll.jar has a vulnerability known as BLOOM-2."
								        [14:33]
<bobmcw> thence they need to do their own internal workflow to locate wtf is
	 using that internal library, and an advisory as to how to
	 remediate/fix/upgrade
<bobmcw> basically crafting their own Advisory for internal usage.
<jcrossley3> we should write that down somewhere  [15:27]

I would also say that: Advisories are there to tell you about the impact of a vulnerability in some other context (like a product, or even the original component). And thus it can carry additional information in mitigating it.
Like:

Vulnerability: CVE-2030-1234: Machine learning model ABC 1.0 might identify humans as a threat
Advisory (TBRUSH-200): Electric toothbrush ABC is affected by CVE-2030-1234 … remediation: approach it carefully, try not to argue with it, ask it kindly to leave the room.
Advisory (GHSA): Machine learning model ABC 1.0 might identify humans as a threat … remediation: upgrade to version 1.1

The vulnerability is CVE-2030-1234. But depending on the context, the assessment of the impact that has, and the remediation, … might be different. It might also be that multiple advisories reference the same vulnerability.

Advisory (TBRUSH-200): Electric toothbrush ABC is affected by CVE-2030-1234 … remediation: approach it carefully, try not to argue with it, ask it kindly to leave the room.

Great example, @ctron :smile:

repo: trustification/trustification


text:
🛑 Wikipedia is down

In e27ce59, Wikipedia (https://en.wikipedia.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wikipedia is back up in 39133d5 after 1,110 days, 9 hours, 28 minutes.

repo: tryadelion/StatusTest


text:
Add support for serverless

@hdoan741 and @huytool157, i know that rpc is beta. There is my architecture feedback.
The current architecture for retool rpc doesn't support serverless architecture. Under the hood integration uses polling, which requires running server.
Our case:

In QA environment application deployed as Cloud Run (serverless container)
In prod environment application deployed as k8s pod

We have such setup for cost optimization.
From a security standpoint pull-rpc looks better than rest/graphql/grpc/etc, but we can not use it in QA environment.
Can we add the ability to call webhook from retool based on resource configuration? It should improve the Developer Experience with this resource.

Making it webhook-based would be better for serverful environments as well. I just deployed Retool RPC today and we already get a lot of false-negative errors due to random network errors when the polling happens.
It'd be nicer if it was a webhook that got called (with a debounced batch of messages in the last x milliseconds so we'd internally could leverage dataloaders etc for noisy messages)

authors: KATT galkin

repo: tryretool/retoolrpc


text:
fix(schema): fix OASv3 schema generation fails when model used in @OneOf has kind property

Closes: #2413

:tada: This PR is included in version 7.34.8 :tada:
The release is available on:

v7.34.8
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 7.35.0-beta.5 :tada:
The release is available on:

v7.35.0-beta.5
GitHub release

Your semantic-release bot :package::rocket:

repo: tsedio/tsed


text:
設定オブジェクトのリファクタリング

https://github.com/tsutaj/statements-manager/issues/49#issuecomment-1601325857
生の dict を使うのではなく、クラスを使うようにしたい

大部分に対応した
cache の部分もクラス化したいが、残件

repo: tsutaj/statements-manager


text:
关于封禁策略的估计。

我认为，我们正常浏览一般都是直接点击首页上已有的文章来浏览，而不是直接跳转到几个月前的旧闻。建议插件选取首页的链接，或模拟人通过点击菜单进行浏览。

我还用老版本，把学习窗口放大基本就可以了，没有警告了。

repo: ttglad/learning


text:
Permission denied (publickey).

On Ubuntu 16.10, i have a error. Permission problems on know_hosts ?
Thanks for your help
Instance has been created XX.XXX.XXX.XXX
Giving new instance some time to fully boot up...
XX.XXX.XXX.XXX is still booting...
XX.XXX.XXX.XXX is still booting...
Setting up VPN on XX.XXX.XXX.XXX
Warning: Permanently added 'XX.XXX.XXX.XXX' (ECDSA) to the list of known hosts.
Permission denied (publickey).
lost connection
Error code 5

If you created a new key pair you will need to use
ssh-add <key>.pem
Verify that it's in ssh-agent
ssh-add - l

I create a new key pair and...
I specify that the key is not already in AWS, on the other hand it is well created but I can not save it locally
./autovpn -G -r us-west-2
Generating new keypair for us-west-2.
Traceback (most recent call last):
  File "./scripts/keygen.py", line 37, in <module>
    generate_key()
  File "./scripts/keygen.py", line 29, in generate_key
    key.save(key_dir)
  File "/usr/local/lib/python2.7/dist-packages/boto/ec2/keypair.py", line 81, in save
    file_path = os.path.join(directory_path, '%s.pem' % self.name)
  File "/usr/lib/python2.7/posixpath.py", line 73, in join
    path += '/' + b
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 11: ordinal not in range(128)
Key already exists in AWS

Try to delete it and recreate It looks like some weird ascii encoding error.
. /autovpn -D -r us-east-2 - k us-east-2_vpnkey
Then
. /autovpn -G -r us-east-2

hum, it's the same thing.
I will look at the code

when i do in command line
python ./scripts/keygen.py "us-west-2_vpnkey" "us-west-2" "."
it's works...

sounds like its unable to write to the directory. what is the output of "pwd"?

$ pwd
/home/zil/Téléchargements/autovpn

But it's good, I managed to make it work with
python ./scripts/keygen.py "us-west-2_vpnkey" "us-west-2" "."
Thanks !


text:
Put some anchor nodes to handle no-relation in graphing

Put some anchor nodes to handle no-relation in graphing

Done.

repo: tttor/csipb-jamu-prj


text:
🛑 Webmail is down

In 49dfdf4, Webmail (https://webmail.protagonist.co.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Webmail is back up in dfbbeb0 after 11 minutes.

repo: tubul/upptime


text:
:memo: 首页说明润色

主要是标点等格式一致。另外，编程语言列表中暂时去掉了 Kotlin（因为此问题未解决）。

thanks

thanks

authors: nobodxbodon tuchg


text:
v3  bugs go/src/gopkg.in/telebot.v3/middleware/logger.go:15:7: undefined : log.Default

go/src/gopkg.in/telebot.v3/middleware/logger.go:15:7: undefined
: log.Default

try to commit log.Default() line

repo: tucnak/telebot


text:
Update BuildSettingProvider to return LD_RUNPATH_SEARCH_PATHS as Array

Part of https://github.com/tuist/tuist/pull/464.
Short description 📝
There is a small inconsistent in the representation of multi-value settings returned from BuildSettingsProvider.
GCC_PREPROCESSOR_DEFINITIONS is defined as an array of strings, whereas LD_RUNPATH_SEARCH_PATHS is a single string.
The problem appears once the project is serialized by Xcode (tested with Xcode 10.2.1). LD_RUNPATH_SEARCH_PATHS are reformatted to arrays which can result in an unexpected diff.
Solution 📦
Use Array<String> to represent LD_RUNPATH_SEARCH_PATHS setting.

Could you add a note to the CHANGELOG @marciniwanicki? We can merge afterwards.

authors: marciniwanicki pepibumur

repo: tuist/xcodeproj


text:
fail on installing pypi sync tool bandersnatch

as title
Reproduction Steps

deploy stack with latest amz linux2

Error Log

    building 'multidict._multidict' extension
    creating build/temp.linux-x86_64-3.7
    creating build/temp.linux-x86_64-3.7/multidict
    gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python3.7m -c multidict/_multidict.c -o build/temp.linux-x86_64-3.7/multidict/_multidict.o -O2 -std=c99 -Wall -Wsign-compare -Wconversion -fno-strict-aliasing -pedantic
    unable to execute 'gcc': No such file or directory
    error: command 'gcc' failed with exit status 1

    ----------------------------------------
Command "/usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-6pow3cpx/multidict/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-zmha9ian-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-6pow3cpx/multidict/
WARNING: Running pip install with root privileges is generally not a good idea. Try `pip3 install --user` instead.

Environment

CDK CLI Version:
Framework Version:
Node.js Version:
OS               :

Other

This is :bug: Bug Report

Let’s fix with below considerations,

resolving the broken install
make the user data script failure when the installation fails, which will trigger the existing CloudWatch alarm

repo: tuna/opentuna


text:
Add ⚡ as default favicon for documentation and examples (#191)

#191
Added ⚡ icon as svg favicon to documentation pages and all examples repos.

Consider rebasing since we have just merged this https://github.com/tuono-labs/tuono/pull/187

Consider rebasing since we have just merged this #187

Rebased the same commit

authors: NayanVR Valerioageno

repo: tuono-labs/tuono


text:
fix: 指定したパターンで story ファイルが存在しないと警告される

yarn dev 時以下のようなメッセージが表示されることへの対応です`
WARN No story files found for the specified pattern: stories/**/*.stories.@(js|jsx|ts|tsx)

mdx以外も対象に含める

差分としては逆で、mdx以外のパスパターンを取り除く変更ではあります

repo: tuqulore/jumpu-ui


text:
Implementation of Paul Heckel's diff algorithm

Implement Paul Heckel's diff algorithm, described in the paper "A technique for isolating differences between files".
Efficiently calculate removed, added, changed, and moved elements

Implemented in a separate library: https://github.com/turbolent/heckel-diff-items

repo: turbolent/collection-view


text:
global definitions of Database slots like mims_soil_set have incorrect, implicit range of string

Global
  mims_soil_set:
    name: mims_soil_set
    from_schema: https://github.com/turbomam/mixs-subset-examples-first/tree/main/src/mixs_subset_examples_first

Database slot_usage
      mims_soil_set:
        name: mims_soil_set
        multivalued: true
        range: MimsSoil
        inlined_as_list: true

just manually copied all of the implicit Database slot usage rows, removed the Database class mention, to get slot definition rows

need to update the generation code

repo: turbomam/mixs-subset-examples-first


text:
Give the access of this project

@tushargupta1504 Hii, i am new mentor assigned to your project can I get the access for this to make this project more beautiful

i have given you the access kindly assign the issue which are true and close the previous one same with pr

@tushargupta1504 received


text:
[HELP] Couldn't flash any Plug and how to make an dumb?

Hi, I'm running tuya-cloudcutter on an RPi3 and wanna flash an Smart Plug of LSC and Workzone (Antela F1s203-EU WiFi Smart Plug). Both has MAC-ID's of Tuya, so I think they have an Beken inside. I found an tutorial where someone flashed successfully an Workzone Plug, but he has dissambled the Plug.
So, I wanna try flashing OTA, because dissambling the Plug would destroy the case.
For LSC I found an profile in the list but it won't work and for Workzone I've tried the Antela F1s202-EU profile. Also no luck :(
I also tried to make a dumb with Cloudcutter App on my Samsung Phone but everytime I push the Button "Read Flash" I get an Error Message that the could not be readed. I've read something about LibreTuya, but I don't understand what this is for. I have an NodeMCU with ESP8266, but I found nothing how I could flash LibreTuya on it. Maybe I'm blind.
Here is the protocol of my RPi3:
[?] How do you want to choose the device?: By manufacturer/device name
 > By manufacturer/device name
   By firmware version and name
   From device-profiles (i.e. custom profile)

[?] Select the brand of your device: Antela
   AIJIA
   Alantop
   Aldi
   Amico
 > Antela
   Aoycocr
   Arlec
   Atarm
   Athom
   Atomi
   Aubess
   Avatar
   Avatto

[?] Select the article number of your device: F1s202-EU Smart Plug
   BAW534 E27 9W RGBCT Bulb
 > F1s202-EU Smart Plug

[?] Select the firmware version and name: 1.3.5 - BK7231T / oem_bk7231s_dltj
 > 1.3.5 - BK7231T / oem_bk7231s_dltj

Selected Device Slug: antela-f1s202-eu-smart-plug
Selected Profile: oem-bk7231s-dltj-1.3.5-sdk-1.0.2-40.00

================================================================================
Place your device in AP (slow blink) mode.  This can usually be accomplished by either:
Power cycling off/on - 3 times and wait for the device to fast-blink, then repeat 3 more times.  Some devices need 4 or 5 times on each side of the pause
Long press the power/reset button on the device until it starts fast-blinking, then releasing, and then holding the power/reset button again until the device starts slow-blinking.
See https://support.tuya.com/en/help/_detail/K9hut3w10nby8 for more information.
================================================================================

Scanning for open Tuya SmartLife AP
..
Found access point name: "SmartLife-86AF", trying to connect...
Device 'wlan0' successfully activated with 'a5c474e2-24d1-4c9f-a6ab-0e3c80737d0e'.
Connected to access point.
Waiting 1 sec to allow device to set itself up...
Running initial exploit toolchain...
Exploit run, saved device config too!
output=/work/configured-devices/E2RtzPsl6xKK.deviceconfig
Saved device config in /work/configured-devices/E2RtzPsl6xKK.deviceconfig

================================================================================
Power cycle and place your device in AP (slow blink) mode again.  This can usually be accomplished by either:
Power cycling off/on - 3 times and wait for the device to fast-blink, then repeat 3 more times.  Some devices need 4 or 5 times on each side of the pause
Long press the power/reset button on the device until it starts fast-blinking, then releasing, and then holding the power/reset button again until the device starts slow-blinking.
See https://support.tuya.com/en/help/_detail/K9hut3w10nby8 for more information.
================================================================================

Scanning for open Tuya SmartLife AP
..
Found access point name: "SmartLife-86AF", trying to connect...
Device 'wlan0' successfully activated with 'a5c474e2-24d1-4c9f-a6ab-0e3c80737d0e'.
Connected to access point.
================================================================================
[!] The profile you selected did not result in a successful exploit.
================================================================================

Maybe someone can help me for flashing the Plugs :)

https://github.com/tuya-cloudcutter/tuya-cloudcutter/wiki/FAQ#how-do-i-find-out-what-firmware-version-my-device-has

repo: tuya-cloudcutter/tuya-cloudcutter


text:
🛑 Recruit Connect - ES Status is down

In 399ac7a, Recruit Connect - ES Status (https://api.recruitconnect.vn/elasticsearch/check-status) was down:

HTTP code: 502
Response time: 257 ms

Resolved: Recruit Connect - ES Status is back up in 67fe1cf after 2 hours, 20 minutes.

repo: tuyencaovn/recruituptime


text:
🛑 Giaymoi.vn is down

In a1f12d8, Giaymoi.vn (https://www.giaymoi.vn) was down:

HTTP code: 403
Response time: 1200 ms

Resolved: Giaymoi.vn is back up in 40fffbe.

repo: tuyenld/monitorWebsiteUptime


text:
not able to deploy on bluemix

Received following error after upload.
Done uploading
FAILED
Error uploading application.
Server error, status code: 403, error code: 0, message:
What this could be?

Follow my procedure in this post which is the final version. This should work
http://www.ibm.com/developerworks/cloud/library/cl-watson-qaapi-app/

authors: sanvaibhav tvganesh

repo: tvganesh/WhatsupWatson


text:
Bump glob to ^5.0.3

Fixes #265.

Coverage remained the same at 100.0% when pulling ba703ba65424f0f197ca531b4b49602339d66c96 on bump-glob into 3eb0a3c4ddb524b50cbfafdeaf93211e9db04931 on master.

Coverage remained the same at 100.0% when pulling 68c916f013336af0ac7cee624478a58e2bbe362c on bump-glob into cc513dfdd4c091b9834d2d1b277cda2440f3d03b on master.

authors: coveralls cvrebert

repo: twbs/bootlint


text:
Poor contrast of standard colors (Non WCAG-compliant)

The info, success and warning colors all fail WCAG contrast guidelines. The colors in action on buttons can be seen here: http://v4-alpha.getbootstrap.com/components/buttons/

Info color (#83bddc) fails against white with an extremely poor contrast of 2.
Warning color (#dfb057) also fails with a contrast ratio of 2.
Success color ([#7fb561](http://webaim.org/resources/contrastchecker/?fcolor= 7fb561&bcolor=ffffff)) fails with a contrast ratio of 2.4.
Danger color ([#bf5e52](http://webaim.org/resources/contrastchecker/?fcolor= bf5e52&bcolor=ffffff)) passes, with a contrast of 4.4. But this is on the limit (4.5) so pretty much okay.
Primary color passes.

I suggest improving the colors so they fullfil WCAG guidelines, so that websites built on bootstrap can be used by standard can be used people with vision disabilities (and poor screens). To fulfill this goal they would need to be changed as follows:
To pass for normal text (<18px):
Warning: #a06a23
Info: #2b739a
Success: #547f3c
If we limit to large text (≥18px):
Warning: #b78323
Info: #3b97c8
Success: #619446
Related issue regarding validation colors: https://github.com/twbs/bootstrap/issues/19004

You might want to take a look at #19693

#19693 indeed duplicates this. Anticipating it being merged.

authors: Florian-R hjnilsson

repo: twbs/bootstrap


text:
glyphicons fonts

Did you remove glyphicons fonts from bootstrap 4.0.0 ?

@engrshahabuddin
Glyphicons Fonts was dropped check out the Components from the Bootstrap Link https://v4-alpha.getbootstrap.com/migration/

Yes, and it's in the migration docs. Head there if you're curious about any other changes like this.

I also saw that bootstrap is 1140px that was 1170px in 3.x
Why ?

authors: engrshahabuddin jgacuca567 mdo


text:
Bootstrap@5.0.0-beta1 color clash with active list-group + link

When list-group-item is active and contains a link (<a />) inside, the color of link and background are the same. See example for Bootstrap@5.0.0-beta1

We can't unilaterally change link colors unfortunately. if you had custom markup, even a dropdown menu, it could override that on accident. Best course here is a utility class IMO.

When active class is added, the text color is changed to white, but links are left intact - I would expect some more consistent behavior.
Using utility classes adds some additional work when trying to manage the state dynamically (it is just more to do than simply toggling one class).
But ofc, if changing this is a problem, then using .text-info for the active state would be the simplest solution.

build custom scss
.list-group-item {   &.active {     a {       color: #fff;       text-decoration: none;       &:hover {         color: #fff;         text-decoration: underline;       }     }   } }

OK, so I know how to change the default behavior.
But still he default behavior is--in my opinion--sub-optimal.
But as @mdo stated - changing the default behavior might be surprising for others.
Given that I think this ticket can be closed.
Thanks!

Closing per last comment.

Closing per last comment.

authors: aribudin mdo michalbachowski


text:
data-bs-boundary="viewport" doesn't work inside responsive tables.

Using BS5, I'm using data-bs-boundary="viewport" in my dropdown (which is inside a responsive table) and it has no effect. The dropdown still gets clipped by the table-responsive container.
How to fix?

Bug reports must include a live demo of the issue. Per our contributing guidelines, please create a reduced test case via CodePen or JS Bin and report back with your link, Bootstrap version, and specific browser and operating system details.

This is a saved reply.

authors: bastinald mdo


text:
Switch Form Layout Depending on Screen Size

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
It would be nice to be able to easily adapt forms layout depending on screen size.
Labels would be on the side of inputs on large screens:

Labels would be on top of inputs on small screens:

Current implementation
The above example, switching between those 2 layouts, has been implemented as follows:

    Role

    <select id="selectRole" class="form-select">
      <option value="admin">Admin</option>
    </select>

The problem
This way of doing things requires to use col-form-label instead of form-label on our label. This adds an extra-padding to the top of the label, breaking the spacing when the label is displayed on top of the input.
https://github.com/twbs/bootstrap/assets/5413308/b496c586-20ac-4da6-a419-a605b8f1e91f
Proposed solution
An ideal solution would be to allow the behavior of our label to change based on the screen size. Our label could behave like a form-label on vertical layouts (small screens), and behave like a col-form-label only on horizontal layouts (larger screens).
Maybe by adding a breakpoint parameter in the class name: col-md-form-label. The behavior of the label would be form-label until the md breakpoint, and col-form-label above it.
Motivation and context
Adapting forms to mobile devices.

I have written the code.
can you please guide me, how can I add those classes to my index.html to see whether it works properly?


text:
Compare tooltip right offset to viewport right offset (and not width)

Hi !
There seems to be a bug on viewport bound check.
Instead of checking that the right offset of the tooltip is not bigger than the right offset of the viewport, you check it's not bigger to the viewport size. This causes wrong offsets being applied in some conditions.
I'm willing to add a unit test if you acknowledge this issue but this will be complicated as qunit tests run in a div with a negative positionning, that will prevent the bug from happening.
Thanks

qunit tests run in a div with a negative positioning, that will prevent the bug from happening.

I think we'd be okay with the new test using an on-screen element. We already have to do something similar for iOS (see 20fb55a840f1b8ae7c3ccaa86acb10a2554b903c).

Thanks !

@twbs-savage Retry

Tests passed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: a0ef4f9bb5c56e38130dcd21ba626a9c1d29f264
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/55854960
(Please note that this is a fully automated comment.)

I tried to add a test case but did not manage to reproduce it within the js unit tests.
I think the minimality of those test prevent the bug from happening (no tooltip css for instance)
However, here's a jsfiddle demonstrating the issue : https://jsfiddle.net/gc8qkgpg/
Thanks

(no tooltip css for instance)

Yeah, generally the approach is to include a minimal amount of CSS (either simple stub CSS or actual tooltip CSS copied over from bootstrap.css) in the testcase itself via <style> tags in those sorts of cases. For examples, see

https://github.com/twbs/bootstrap/blob/93bf800e1f00861525688007ae7aaf6f3daeda47/js/tests/unit/tooltip.js#L697
https://github.com/twbs/bootstrap/blob/93bf800e1f00861525688007ae7aaf6f3daeda47/js/tests/unit/tooltip.js#L958

@Intrepidd So, can you try adding a unit test again now that I've explained the approach?

Sorry for taking so long, and thank you for reminding me about this.
I finally managed to write a spec that fails on master and passes on my branch.
The key is that it can only fail when this style (from bootstrap css) is present :
* {
  box-sizing: border-box;
}

In the tests this style was added though :
.tooltip, .tooltip *, .tooltip *:before, .tooltip *:after { box-sizing: border-box; }

I replaced the latter by the former in the specs that used it to be more consistent.

Tests failed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: BUSTED
Commit: 7f187f90c16ae4aad573d166333bb2d16f63c97f
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/59513555
(Please note that this is a fully automated comment.)

I pushed -f, it broke the build :/

Tests failed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: BUSTED
Commit: 6ce6fec465cd3f76fac158a981b40c95d52c91d2
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/59513120
(Please note that this is a fully automated comment.)

No worries, a build of your new revision is already in progress.

Tests failed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: BUSTED
Commit: 4e18806b07a311aac7c5b2fa5a0eb08dc960b462
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/59513874
(Please note that this is a fully automated comment.)

Tests passed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: 13cd2cbd58bb3d0724d8a2bd99fcd0b0793d38d2
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/59516395
(Please note that this is a fully automated comment.)

Yay !
On Wed, Apr 22, 2015 at 10:43 AM twbs-savage notifications@github.com
wrote:

Tests passed. Automated cross-browser testing via Sauce Labs and Travis
CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: 13cd2cb
https://github.com/twbs/bootstrap/commit/13cd2cbd58bb3d0724d8a2bd99fcd0b0793d38d2
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/59516395
(Please note that this is a fully automated
https://github.com/twbs/savage comment.)
—
Reply to this email directly or view it on GitHub
https://github.com/twbs/bootstrap/pull/16142#issuecomment-95078814.

Is there anything more I can to to wrap up this PR ?

Sorry for the delay; the * { box-sizing: border-box; } change gave me pause when considering merging this previously. Turns out a less drastic reset (cdb37dce3a85c07790e73b7e2c809860db6b0cad) works fine, but I had to test that out (and also squash everything into a single commit).
Thanks for your contribution!

Ok ! Thanks for your time !

authors: Intrepidd cvrebert twbs-savage


text:
[Fix #17544][V4] Update doc for tooltips and popover about dispose method

Hi,
fix for https://github.com/twbs/bootstrap/issues/17544

FYI: @fat

Thanks!

authors: Johann-S cvrebert


text:
Refactor Dashboard example.

Resolves #17816, resolves #17883, closes #18707.

<3<3<3

authors: bardiharborow mdo


text:
tweepy.error.TweepError: [{'message': 'Application cannot perform write actions. Contact Twitter Platform Operations through https://help.twitter.com/forms/platform.', 'code': 261}]

I've made a bot who is working well but after a certain amount of time I keep getting this error and I don't know why:
tweepy.error.TweepError: [{'message': 'Application cannot perform write actions. Contact Twitter Platform Operations through https://help.twitter.com/forms/platform.', 'code': 261}]
My code: https://pastebin.com/XtmEHPFZ

The most likely cause of Code 261 is:

The App that you are using with the API does not have the proper permission level set for its access token and access token secret. Please navigate to the 'Keys and tokens' tab on the Twitter Apps dashboard and check the permission levels assigned to your access token and access token secret. If it is set to anything other than 'Read, write and Direct Messages,' then you are going to have to adjust the settings under the 'Permission' tab and regenerate your access token and access token secret to apply the new settings.

https://developer.twitter.com/en/support/twitter-api/error-troubleshooting
This is likely happening when you try to update you status.

Ok I will try thanks for the answer

The most likely cause of Code 261 is:

The App that you are using with the API does not have the proper permission level set for its access token and access token secret. Please navigate to the 'Keys and tokens' tab on the Twitter Apps dashboard and check the permission levels assigned to your access token and access token secret. If it is set to anything other than 'Read, write and Direct Messages,' then you are going to have to adjust the settings under the 'Permission' tab and regenerate your access token and access token secret to apply the new settings.

https://developer.twitter.com/en/support/twitter-api/error-troubleshooting
This is likely happening when you try to update your status.

I just what you send so if I understand well I need to pay to have a better api?

Like it says, you simply need to use the proper permission level. It has nothing to do with paying.

Like it says, you simply need to use the proper permission level. It has nothing to do with paying.

Ok thanks and I have another question what is the difference between standard app and standalone app?

That's not relevant to this issue, but see https://developer.twitter.com/en/docs/apps/overview.

repo: tweepy/tweepy


text:
Program freezing after a certain amount of time

Hello I've made a twiiter bot who is working well but after a certain amount of time like 10 minutes the bot freeze and doesn't work anymore and I've to restart I don't understand why.
My code:
https://pastebin.com/phb7VY4j

This is too much code to debug for you, with a lot of unnecessary nesting and repetition, but it's likely not an issue with Tweepy.
Can you provide a reproducible example (MCVE/SSCCE) or be more specific about your issue?


text:
warning: kqueue is not supported on this platform

tweetstream-2.6.1/lib/tweetstream/client.rb:401: warning: kqueue is not supported on this platform

Just started getting this warning message in the logs, which I think has been triggered by updating eventmachine from 1.0.7 to 1.0.8. This corresponds to line 418 in the current source.
EventMachine.kqueue

I presume this is okay -- being only a warning, and all seemingly working okay -- but could you confirm.
Also, is there a way to stop the message?
Thanks.

My recollection is that these no-op but i'll check.

Yep, it's just a warning: https://github.com/eventmachine/eventmachine/blob/67fd2af021159fc8a8b72f24bd6eff6f45669bdb/ext/rubymain.cpp#L1040-L1049
I think I can suppress the message by changing tweetstream's code from EM.kqueue to EM.kqueue = true if EM.kqueue? which is actually how they use it in their tests: https://github.com/eventmachine/eventmachine/blob/36003fcf1675e8718a9d45b83e70c2054ddb7c40/tests/test_file_watch.rb#L28-L34
It does appear that this was changed recently: https://github.com/eventmachine/eventmachine/commit/9af94064e1f05b373145ba0c3cac41daa9daf369

heh, it could probably be simplified to EM.kqueue = EM.kqueue? which seems silly but ¯_(ツ)_/¯

Cool. Thanks.

authors: auxbuss stve

repo: tweetstream/tweetstream


text:
initial vagrant setup

An effort to normalize the dev environment. It's not working out of the box yet. Need to figure out why npm install doesn't complete(misses bower). Also, there are a lot of deprecated components maybe the install issue is due to this.

This is the failed logged after npm install on the vagrant box:
from vagrant box npm-debug.txt
This is the failed logged after npm install on osx.
from osx npm-debug.txt

repo: twg/wikiwash


text:
Add my pixel

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.

[x] I acknowledge that all my contributions will be made under the project's license.

@dkundel the CI system appears to be broken :)

Yeah unfortunately Danger is not doing what it's supposed to do :(

authors: dkundel stgarf

repo: twilio-labs/open-pixel-art


text:
Add support for Arduino NANO R3 with new bootloader (optiboot)

The Arduino development team has replaced the bootloader for the Arduino NANO R3 boards in early 2018.

NOTE: We have updated the NANO board with a fresh bootloader. Boards sold from us from January 2018 have this new bootloader, while boards manufactured before that date have the old bootloader. First, make sure you have the Arduino AVR Core 1.16.21 or later looking at the Board Manager. Then, to program the NEW Arduino NANO boards you need to chose Processor > "ATmega328P". To program old boards you need to choose Processor > "ATmega328P (Old Bootloader)". If you get an error while uploading or you are not sure which bootloader you have, try each type of processor 328P until your board gets properly programmed.
Source

The previous bootloader ATmegaBOOT was exchanged for Optiboot and thus also doubled the data transfer rate from 57,600 Bd to 115,200 Bd. See comparison:

Arduino Nano w/ ATmega328P
nano.menu.cpu.atmega328=ATmega328P
nano.menu.cpu.atmega328.upload.maximum_size=30720
nano.menu.cpu.atmega328.upload.maximum_data_size=2048
nano.menu.cpu.atmega328.upload.speed=115200
nano.menu.cpu.atmega328.bootloader.low_fuses=0xFF
nano.menu.cpu.atmega328.bootloader.high_fuses=0xDA
nano.menu.cpu.atmega328.bootloader.extended_fuses=0xFD
nano.menu.cpu.atmega328.bootloader.file=optiboot/optiboot_atmega328.hex
nano.menu.cpu.atmega328.build.mcu=atmega328p
Arduino Nano w/ ATmega328P (old bootloader)
nano.menu.cpu.atmega328old=ATmega328P (Old Bootloader)
nano.menu.cpu.atmega328old.upload.maximum_size=30720
nano.menu.cpu.atmega328old.upload.maximum_data_size=2048
nano.menu.cpu.atmega328old.upload.speed=57600
nano.menu.cpu.atmega328old.bootloader.low_fuses=0xFF
nano.menu.cpu.atmega328old.bootloader.high_fuses=0xDA
nano.menu.cpu.atmega328old.bootloader.extended_fuses=0xFD
nano.menu.cpu.atmega328old.bootloader.file=atmega/ATmegaBOOT_168_atmega328.hex
nano.menu.cpu.atmega328old.build.mcu=atmega328p

I think the easiest way would be to implement a new variation of the Arduino NANO in ArduinoUploader.xml and add the "new" Arduino model to the list in ArduinoModel.cs as NanoR3New just like in the Arduino IDE:

Image source

I just did some tests by modifying the library from the latest release v.3.2.0.
I got a successful result by adding the following code to ArduinoUploader.xml:
    ...
    <Arduino model="NanoR3New">
      <Mcu>AtMega328P</Mcu>
      <BaudRate>115200</BaudRate>
      <PreOpenResetBehavior>DTR;true</PreOpenResetBehavior>
      <CloseResetBehavior>DTR-RTS;250;50</CloseResetBehavior>
      <SleepAfterOpen>250</SleepAfterOpen>
      <ReadTimeout>1000</ReadTimeout>
      <WriteTimeout>1000</WriteTimeout>
      <Protocol>Stk500v1</Protocol>
    </Arduino>
    ...

Then I added the new model to the list in ArduinoModel.cs:
        ...
        NanoR3,
        NanoR3New,
        UnoR3
        ...

I have tested the code with five original Arduino NANOs with the Optiboot bootloader and got no errors. So @christophediericx could you please add this additions to your library with the next release?
Thank you.

Without taking merit from @SoftwareBySebastianLang since he points out, imho, the correct way of supporting the new chip change!
I would like to indicate a workaround that enables to use the current release v.3.2.0 with an Arduino Nano with Optiboot booloader until a new release emerges.
Since ArduinoSketchUploader only programs the device's flash one can use --model=UnoR3 in order to successfully program a Nano.
This works because, as pointed out by @SoftwareBySebastianLang, the major change with the new bootloader is the programming baudrate.
Keep up the good work!
Kind regards.
PS: @SoftwareBySebastianLang, consider doing a pull request with your changes to better help @christophediericx incorporating them ;)

Sebastian do you know how to add the support for an Atmega4808 (Thinary board) https://www.avrfreaks.net/forum/nano-every-use-atmega4808?page=all ? @SoftwareBySebastianLang

repo: twinearthsoftware/ArduinoSketchUploader


text:
small cleanup

Was trying to understand what the module does, and came across this. From what i can see runAnimation is never called with any arguments.
If I didn't miss something obvious shouldn't this be removed?

runAnimation can be called externally with a config. See the demo.

OK did miss the obvious, but what I initially noticed was that it looked like the code should call the 2 methods for stop and finish animations instead of having that code twice?
_finishAnimation() {
_stopAnimation() {

I suppose it could, but consolidating that isn't a huge priority.

Should I make a PR? and would you want a patch version increase based on it?

authors: finneganh mmussmann

repo: twitter-fabric/velocity-react


text:
2.0-wip: input/textarea with warning/error/success no longer glows on focus

As of SHA: 40e92221a616bfe4e9500bcf2b72c86844f7f03f, inputs and text areas where the control-group has the class of error/warning/success doesn't glow like it used to. I'm not sure if this change was intentional or not. I enjoyed the glow effect it used to have. You can see it in the Base CSS > Forms > Form Control States section of the docs.

Just to clarify, the shadow color now seems to be white instead of red/green/yellow.

Sorry about that, all back now!

authors: GMFlash markdotto

repo: twitter/bootstrap


text:
Suggested Spilt of files

I would like to suggest that the patterns.less file gets split up a little so that components such as buttons have there own less file.  This would make it a little more modular and allow for folks to more easily drop in there own styles  and could lead to folks providing replacement styles for the main bootstrap.

I found this ticket only after implementing the same thing (https://github.com/bryfox/bootstrap/commit/a4f6c8e8d16e760f7e4159f1db7a7d36ed2420ce). My use case: needing to pull out a few of the patterns into a modular build for a mobile-friendly site (where the resulting 27K savings in my compiled, minified css is pretty significant). Sounds like you've ruled out the many-files approach, but I thought I'd throw in my 2 cents behind it anyway.

authors: bryfox khoogheem


text:
Cannot resolve module 'hogan' in ...

package.json
"devDependencies": {
    "css-loader": "^0.28.4",
    "extract-text-webpack-plugin": "^1.0.1",
    "file-loader": "^0.11.2",
    "html-loader": "^0.4.5",
    "html-webpack-plugin": "^2.29.0",
    "style-loader": "^0.18.2",
    "url-loader": "^0.5.9",
    "webpack": "^1.15.0",
    "webpack-dev-server": "^1.16.5"
  },
  "dependencies": {
    "hogan": "^1.0.2"
  }

ma.js
'use strict';
var Hogan = require('hogan');
var conf = {
    serverHost: ''
};
//渲染html模板
    renderHtml: function(htmlTemplate, data){
        var template = Hogan.compile(htmlTemplate),
            result = template.render(data);
        return result;
    },

index.js
'use strict';

var _ma = require('util/ma.js');

var html = '<div>{{data}}</div>';
var data = {
    data: 123
}
console.log(_ma.renderHtml(html, data));

ERROR in ./src/util/ma.js
Module not found: Error: Cannot resolve module 'hogan' in /Users/Macx/Documents/mall/mall-fe/src/util
@ ./src/util/ma.js 9:12-28

已经决。
hogan新版本的引入方式:
var Hagon = require('hagon.js');
具体参见官方文档

This should actually be:
var Hogan = require('hogan.js');

and hogan.js in package.json

authors: Haroenv labike zhangbinzhbb


text:
Keycap Digit URLs different

Unicode is a little strange to me, so I could be totally off base on this, but given that the hex for keycap digit 8 is 0038 20e3, it seems like the corresponding URL should be
https://twemoji.maxcdn.com/svg/0038-20e3.svg
rather than
https://twemoji.maxcdn.com/svg/38-20e3.svg
as it currently stands. It might just be a matter of convention, but aren't all bytes usually expressed even if they're 0? FWIW, github's URL: https://assets-cdn.github.com/images/icons/emoji/unicode/0032-20e3.png

for some reason assets had no leading zero in their names and everything is based on current available assets. Hopefully not a big deal, or to look at the bright side, we save 2 bytes in the URL there: yaiiiii!

authors: WebReflection aquach

repo: twitter/twemoji


text:
Add Reference To EmojiOnRoku Project

Description
Hi, I recently discovered this project and thought it was perfect to allow some Emoji support on Roku Scenegraph applications. This is one of my first attempts at independent open source contributions so please let me know if my project looks ok and if I attributed the work correctly. This is basically a port of this project to work on Roku applications.
Technical Details
I used the same base code for transforming specific code points into a URL to retrieve for each emoji. The regex provided in the https://github.com/twitter/twemoji-parser does not work for the regex functionality on Roku, since that component has the Unicode flag enabled by default (so matching based on surrogates was not working correctly). I had to instead use another emoji regex which I attributed and found here: https://github.com/mathiasbynens/emoji-regex. That project is also open source under the MIT license.
The other work done in my project was to create a component for Roku's Scenegraph architecture that behaves roughly the same as the ordinary Label node, with the added bonus of recognizing and rendering emojis in much the same way as the DOM or string parser does in this project.
Thanks!
Thanks for the amazing project here! Again I hope this project is licensed and attributed properly, please let me know otherwise! I hope to continue to develop the project, adding multi-line support, better string truncating and adding unit tests. I think it is ready for use but could use some work as well.
Thanks again!

 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.

Thanks for building such a cool project!

Thanks for building such a cool project!

https://github.com/rosseljost/twemoji/commit/984204cf6b8d0cce500fab4255923d5d1af4fa1a

https://github.com/twitter/twemoji

language: node_js
node_js:

"8"
git:
depth: 1
branches:
only:

gh-pages
install: yarn install --frozen-lockfile
script: yarn test

language: node_js
node_js:

"8"
git:
depth: 1
branches:
only:

gh-pages
install: yarn install --frozen-lockfile
script: yarn test

authors: BROSVORN CLAassistant KasperGam jdecked


text:
Missing required parameter [code_verifier]

await authClient.requestAccessToken(code)

crashes with
error: {
  error: 'invalid_request',
  error_description: 'Missing required parameter [code_verifier].'
}

I think the problem is that #codeVerifier is undefined here 👇
https://github.com/twitterdev/twitter-api-typescript-sdk/blob/0d4954c675dbfc566c6911adc4d4178dce926ca4/src/OAuth2User.ts#L170

I am having this exact same issue. The only thing I can think is that the oAuth has a different code_verifier value than my redirect URL for the callback-->both use new auth.OAuth2User to create a client for use on either oAuth or the callback (which is slightly different than what the example code is doing in an app). This is just speculation though.

Thanks @RodionChachura, you need to call generateAuthURL to create the code_verifier. Will add a check and throw a helpful error to improve this

@wmencoder thats right, you need to use the same Auth Client that generated the authentication URL

I am having the same issue, but this solution will not work for me. Is there a way to generate an access token statelessly? My app runs in a serverless environment and I can't persist an instance of the OAuth2User class between requests. I can store any data necessary, but the code_verifier property is private and it can't be accessed from outside the class.

@jgjr I am also trying to use this SDK in a serverless environment. Could you please a minimal working code for the same?
@refarer Official example to run this SDK on serverless environment would be really appreciated.

@sasivarnan The solution was fairly simple.
In the initial call of generateAuthURL() I use code_challenge_method: 'plain' and save the code_challenge that I use. Then when the user is redirected back to my platform I call the generateAuthURL() method again with the same saved code_challenge, and then the requestAccessToken() method with the code I have received.

@sasivarnan I was able to generate a stateless client by creating a class
class OAuth2UserStateless extends auth.OAuth2User

That overloads the constructor and assigns the Token that I pass as a cookie from the client. You can theoretically do the same with the code_verifier property instead of doing void call to generateAuthURL to populate that property.
This is a hack and clearly this SDK isn't designed for statelessness at this time.

@sasivarnan The solution was fairly simple. In the initial call of generateAuthURL() I use code_challenge_method: 'plain' and save the code_challenge that I use. Then when the user is redirected back to my platform I call the generateAuthURL() method again with the same saved code_challenge, and then the requestAccessToken() method with the code I have received.

Feels crazy hacky but works

I created a PR to solve this issue, I need to work with the maintainers to get a code review and eventually this feature can be merge, the PR is here if you want to take a look:
https://github.com/twitterdev/twitter-api-typescript-sdk/pull/42

The 1.2.0 version  published 6 days ago  (thanks @refarer!) allows the token to be passed on the constructor. So, now you could do something like this:

Create the endpoint to start the authentication process: generate state and challenge and call generateAuthURL; persist these values to recreate the OAuth2User later on;
Create another endpoint for the callback: recreate the auth with state and challenge and call requestAccessToken passing the code received; store the token returned by that function;
Pass the token on the OAuth2UserOptions during user creation.

Using firebase functions, my simplified code is:
// authenticate.ts
export const authenticate = functions
  .region('southamerica-east1')
  .https.onRequest(async (req, res) => {
    res.redirect(await generateAuthURL());
  });

// authenticationHandler.ts
export const authenticationHandler = functions
  .region('southamerica-east1')
  .https.onRequest(async (req, res) => {
    const { code } = req.query;
    await handleAuthCode(code as string);
    res.send('OK');
  });

// auth.ts
let user: auth.OAuth2User | null = null;
const getUser = async () => {
  if (!user) {
    const { token } = (await getPlatformTokens()) ?? {};
    user = new auth.OAuth2User({
      client_id: <CLIENT_ID>,
      client_secret: <SECRET>,
      callback: <CALLBACK_URL>,
      scopes: ['tweet.read', 'tweet.write', 'users.read', 'offline.access'],
      token: token ? JSON.parse(token) : undefined,
    });
  }
  return user;
};

let client: Client | null = null;
const getClient = async () => {
  if (!client) client = new Client(await getUser());
  return client;
};

export const generateAuthURL = async () => {
  const state = randomBytes(12).toString('hex');
  const challenge = randomBytes(12).toString('hex');
  await updatePlatformTokens({
    state,
    challenge,
  });
  const user = await getUser();
  return user.generateAuthURL({
    state,
    code_challenge_method: 'plain',
    code_challenge: challenge,
  });
};

export const handleAuthCode = async (code: string) => {
  const user = await getUser();
  const { state, challenge } = (await getPlatformTokens()) ?? {};
  if (state && challenge) {
    user.generateAuthURL({
      state,
      code_challenge_method: 'plain',
      code_challenge: challenge,
    });
    const { token } = await user.requestAccessToken(code);
    await updatePlatformTokens({
      token: JSON.stringify(token),
    });
  }
};

@pdandradeb what is getPlatformTokens and it's type?

@apecollector
// types.ts
export interface PlatformTokens {
  token?: string;
  state?: string;
  challenge?: string;
}

// tokens.ts
export const getPlatformTokens = async () => {
  const tokens = await getFirestore()
    .collection('platform')
    .doc('tokens')
    .get();
  return tokens.data() as PlatformTokens;
};

export const updatePlatformTokens = async (tokens: Partial<PlatformTokens>) => {
  await getFirestore()
    .collection('platform')
    .doc('tokens')
    .set(tokens, { merge: true });
};

// authenticate.ts
export const authenticate = functions
  .region('southamerica-east1')
  .https.onRequest(async (req, res) => {
    res.redirect(await generateAuthURL());
  });

My implementation is almost exactly the same except using an onCall instead of on request, in hopes of limiting the ability for this function to be called from any browser.

This thread was super helpful! Got me past a few roadblocks while trying to use this sdk with nextjs and serverless api functions

This SDK is very problematic.
In particular, the inability to inject code_verifier from the outside should be fixed as soon as possible.
I'm extending it with a Service class that has a constructor that can inject the code_verifier and code_challenge from the outside.
I hope this implementation helps those who are having trouble.
Also, if there are any problems, please point them out.
https://gist.github.com/amemiya/14f1614819210b8be5d4afcbf4727ca6

authors: PMLyf RodionChachura amemiya apecollector danforero elie222 jacklynch00 jgjr mathieuhelie pdandradeb refarer sasivarnan wmencoder

repo: twitterdev/twitter-api-typescript-sdk


text:
Support building on MacOS, fix libunwind building, add basic support for Twizzler in clang

If that sounds like a lot for a PR, that's because they're all intertwined and most of the work happened in the llvm and rust repos, not this one.
Currently, macos fails to build Twizzler for two reasons:

The config.toml file that rust uses for configuring the toolchain build is static and only contains the targets for twizzler and x86_64 linux.
The build of crtbegin and crtend in llvm fails because we try to use the system compiler, which on mac produces a mach-o file, not an ELF file. As a result, we'd get this fun error:

running: "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-std=c11" "-DCRT_HAS_INITFINI_ARRAY" "-DEH_USE_FRAME_REGISTRY" "-o" "/Users/dbittman/src/test/twizzler/toolchain/src/rust/build/x86_64-unknown-twizzler/native/crt/crtbegin.o" "-c" "/Users/dbittman/src/test/twizzler/toolchain/src/rust/src/llvm-project/compiler-rt/lib/crt/crtbegin.c"
cargo:warning=/Users/dbittman/src/test/twizzler/toolchain/src/rust/src/llvm-project/compiler-rt/lib/crt/crtbegin.c:15:28: error: argument to 'section' attribute is not valid for this target: mach-o section specifier requires a segment and section separated by a comma
cargo:warning=    __attribute__((section(".eh_frame"), aligned(sizeof(void *)))) = {};

The fix for this has several components.
Fixing config.toml
Instead of just hard linking toolchain/src/config.toml to toolchain/src/rust/config.toml, we now generate toolchain/src/rust/config.toml using toolchain/src/config.toml as a template. When xtask does the bootstrapping step, it reads the template, adds the necessary targets (e.g. the current host triple) to the list of targets, and adds explicit tool paths to the twizzler target for cc, cxx, linker, and ar.
This is useful anyway, since we'll want to support building on and for arm and x86, and generating the necessary targets makes this all more flexible.
Fixing crt
The crt files are built manually by the rust bootstrap program, so we can just modify that by providing paths to the C compiler built by llvm during the bootstrapping phase (if we tell rust to not worry that those tools aren't there ahead of time). This fixes the error above because clang will make us a nice ELF file if we tell it to target twizzler.
And we're telling clang to generate code for twizzler, so we (sigh) probably should add support to clang for Twizzler as well. Our llvm fork is updated with this, mostly just copied from other targets, based off of fuchsia and linux.
This works, but it makes libunwind be compiled by the clang we build. Which is the point, but the side effect is that now we have no headers. Actually, this has always been a latent bug, that we were using system headers on linux for compiling libunwind for twizzler, but it's okay because although libunwind is not necessarily freestanding and does depend on libc, in practice we can turn almost all of that off and make it (mostly) freestanding.
However, to avoid modifying libunwind as well, we'll need to provide some basic C headers that libunwind unconditionally includes. These are mostly for memset etc and stddef.h. C sucks. Anyway, we provide the minimal files to get libunwind to compile. Maybe in the future we'll have a real C library and we can use that instead.
Alternatives
This isn't necessary, since macos is not currently a supported target. But I'd like to make it one. Or at least, make it work, even if not officially supported.
The header files are an ugly solution to get libunwind to compile, but it's better that modifying libunwind. I'd like to keep modifications to upstream toolchain software to a minimum. At least, as much as is reasonable.
Finally, clang support. This makes it harder to update llvm, since many more files are modified. But there's a good chance we'll eventually need a C compiler for twizzler anyway, so this is probably the best approach. And it makes libunwind compile "more correctly".
Future plans
I'd like to improve the way we generate the config.toml file. We'll probably want to add support for arm to that soon, so @PandaZ3D should take a look at that.
The clang support is super minimal; we'll want to expand that (adding sanitizers, etc).
Conclusion
Now my mac can compile twizzler. Still can't run it, though, since KVM doesn't work (obvs). That'll come later.

Relevant rustc repo commits:

1
2
3
4

Relevant llvm repo commits:

1
2

repo: twizzler-operating-system/twizzler


text:
don't crop thumbnails

they should be scaled down to fit (same amount in X and Y), leaving whitespace (centered).
this is for the regular metadata view.
in the featured view it should crop so the rectangle is filled.

@scottdraves how "leaving whitespace" can be achieved without actually cropping thumbnails? Also, by "leaving whitespace" do you mean we should try to detect whitespace in all images (png, jpg) and crop images automatically so they don't show it? If yes, this problem seems a bit complex to solve in general.
If we want to have fine grained control over thumbnail maybe we should add a cropping step to our image upload flow, where a user could crop the image on his own using some js lib like http://fengyuanchen.github.io/cropper/
What do you think?

i think we should keep it simple and not introduce cropping.
i am not proposing looking into the image and deducing whitespace.
just treat the uploaded image as a unit.
do not crop it!  whatever the user sent up they want to see.
to make it fit into the space on the web page, introduce whitespace around what they uploaded,
either on top & bottom or on sides.

:+1:

Fixed in: https://github.com/twosigma/bunsen/pull/1266

authors: grin scottdraves

repo: twosigma/beaker-notebook


text:
When the cell returns null it should not be rendered

It looks ugly if some custom output is used in the cell, this null pops up after it.

does this API address this issue? https://github.com/twosigma/beakerx/blob/73ac34418eeed06df280b774dc51d44857dd5730/doc/contents/showNullExecutionResult.ipynb

Thanks, it does indeed. Though I believe it should be false by default.

There is disagreement about which is better.  While our API allows switching, if you are someone who wants to always turn off showing "null" it is annoying to switch in every notebook.  Maybe there's a good way to make it a more permanent switch...

authors: altavir scottdraves

repo: twosigma/beakerx