text:
Improve data ingestion documentation

Description

While working with prop ingestion in CARLA 0.9.10 with Unreal Engine 4.24.3, the documentation was often confusing.

Documentation has been updated adding an official CARLA video that explains data ingestion in detail
Wording around data ingestion from source was made less ambiguous (Previous documentation stated that 'JSON file would be read' with a lack of context that the make import command needed to be run first )
Note was added to the two different sections on data ingestion to make it more clear that they don't represent a  logical progression and should be used in two different cases.

Where has this been tested?

Platform(s): 0.9.10
Python version(s): 3.7.9
Unreal Engine version(s): 4.24.3

This change is

add a new map from build source , what files should  be in the input file? i put the .fbx and .xodr file in, when i execute the docker_tools.py  ,it will make errors like this:
[2022.01.10-12.48.55:235][  0]LogFileCache: Scanning file cache for directory '/home/ue4/carla/Unreal/CarlaUE4/Content/Developers/ue4/Collections/' took 0.00s
[2022.01.10-12.48.55:235][  0]LogFileCache: Scanning file cache for directory '/home/ue4/carla/Unreal/CarlaUE4/Content/Collections/' took 0.00s
1001[2022.01.10-12.48.58:728][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/Ground/SimpleRoad/CheapRoad': Can't find file.
1001[2022.01.10-12.48.58:728][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/Ground/SimpleRoad/CheapRoad': Can't find file.
1001[2022.01.10-12.48.58:729][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/Ground/SimpleRoad/CheapSideWalkCurb': Can't find file.
1001[2022.01.10-12.48.58:729][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/Ground/SimpleRoad/CheapSideWalkCurb': Can't find file.
1001[2022.01.10-12.48.58:730][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/Ground/SimpleRoad/CheapSideWalk_00': Can't find file.
1001[2022.01.10-12.48.58:730][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/Ground/SimpleRoad/CheapSideWalk_00': Can't find file.
1001[2022.01.10-12.48.58:731][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/Ground/SimpleRoad/CheapLaneMarking': Can't find file.
1001[2022.01.10-12.48.58:731][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/Ground/SimpleRoad/CheapLaneMarking': Can't find file.
1001[2022.01.10-12.48.58:732][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/WetPavement/WetPavement_Complex_Road_N2': Can't find file.
1001[2022.01.10-12.48.58:732][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/WetPavement/WetPavement_Complex_Road_N2': Can't find file.
1001[2022.01.10-12.48.58:735][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/WetPavement/WetPavement_Complex_Concrete': Can't find file.
1001[2022.01.10-12.48.58:735][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/WetPavement/WetPavement_Complex_Concrete': Can't find file.
1001[2022.01.10-12.48.58:736][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/Ground/SideWalks/SidewalkN4/WetPavement_SidewalkN4': Can't find file.
1001[2022.01.10-12.48.58:736][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/Ground/SideWalks/SidewalkN4/WetPavement_SidewalkN4': Can't find file.
1001[2022.01.10-12.48.58:737][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/LaneMarking/Lanemarking': Can't find file.
1001[2022.01.10-12.48.58:737][  0]LogLinker: Failed to load '/Game/Carla/Static/GenericMaterials/LaneMarking/Lanemarking': Can't find file.
[2022.01.10-12.48.58:737][  0]LogCarla: == CARLA Settings ==============================================================
[2022.01.10-12.48.58:737][  0]LogCarla: Last settings file loaded:
[2022.01.10-12.48.58:737][  0]LogCarla: [CARLA/Server]
[2022.01.10-12.48.58:737][  0]LogCarla: RPC Port = 2000
[2022.01.10-12.48.58:737][  0]LogCarla: Streaming Port = 2001
[2022.01.10-12.48.58:737][  0]LogCarla: Synchronous Mode = Disabled
[2022.01.10-12.48.58:737][  0]LogCarla: Rendering = Enabled
[2022.01.10-12.48.58:737][  0]LogCarla: [CARLA/QualitySettings]
[2022.01.10-12.48.58:737][  0]LogCarla: Quality Level = Low
[2022.01.10-12.48.58:737][  0]LogCarla: ================================================================================
1001[2022.01.10-12.48.58:781][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Static/TrafficLight/Streetlights_01/TrafficLightPieceStructure.uasset' failed to load '/Game/Carla/Static/TrafficSigns/Streetlights_01/SM_TLights_Leds': Can't find file.
1001[2022.01.10-12.48.58:781][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Static/TrafficLight/Streetlights_01/TrafficLightPieceStructure.uasset' failed to load '/Game/Carla/Static/TrafficSigns/Streetlights_01/SM_TLights_Leds': Can't find file.
1001[2022.01.10-12.48.58:782][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Static/TrafficLight/Streetlights_01/TrafficLightPieceStructure.uasset' failed to load '/Game/Carla/Static/TrafficSigns/Streetlights_01/T_TrafficLighSign_op': Can't find file.
1001[2022.01.10-12.48.58:782][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Static/TrafficLight/Streetlights_01/TrafficLightPieceStructure.uasset' failed to load '/Game/Carla/Static/TrafficSigns/Streetlights_01/T_TrafficLighSign_op': Can't find file.
1001[2022.01.10-12.48.58:784][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Blueprints/TrafficLight/ST_TrafficLightHead.uasset' failed to load '/Game/Carla/Static/TrafficSigns/TrafficLight/SM_TrafficLight__Light01': Can't find file.
1001[2022.01.10-12.48.58:784][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Blueprints/TrafficLight/ST_TrafficLightHead.uasset' failed to load '/Game/Carla/Static/TrafficSigns/TrafficLight/SM_TrafficLight__Light01': Can't find file.
1001[2022.01.10-12.48.58:785][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Blueprints/TrafficLight/ST_TrafficLightHead.uasset' failed to load '/Game/Carla/Static/TrafficSigns/TrafficLight/SM_TrafficLight__Light02': Can't find file.
1001[2022.01.10-12.48.58:785][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Blueprints/TrafficLight/ST_TrafficLightHead.uasset' failed to load '/Game/Carla/Static/TrafficSigns/TrafficLight/SM_TrafficLight__Light02': Can't find file.
1001[2022.01.10-12.48.58:786][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Blueprints/TrafficLight/ST_TrafficLightHead.uasset' failed to load '/Game/Carla/Static/TrafficSigns/TrafficLight/SM_TrafficLight__Light03': Can't find file.
1001[2022.01.10-12.48.58:786][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Blueprints/TrafficLight/ST_TrafficLightHead.uasset' failed to load '/Game/Carla/Static/TrafficSigns/TrafficLight/SM_TrafficLight__Light03': Can't find file.
1001[2022.01.10-12.48.58:787][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Blueprints/TrafficLight/ST_TrafficLightHead.uasset' failed to load '/Game/Carla/Static/TrafficSigns/TrafficLight/SM_TrafficLight_holster': Can't find file.
1001[2022.01.10-12.48.58:787][  0]LogLinker: While loading '../../../../carla/Unreal/CarlaUE4/Content/Carla/Blueprints/TrafficLight/ST_TrafficLightHead.uasset' failed to load '/Game/Carla/Static/TrafficSigns/TrafficLight/SM_TrafficLight_holster': Can't find file.
[2022.01.10-12.49.05:143][  0]LogAudioCaptureCore: Display: No Audio Capture implementations found. Audio input will be silent.
[2022.01.10-12.49.05:143][  0]LogAudioCaptureCore: Display: No Audio Capture implementations found. Audio input will be silent.
[2022.01.10-12.49.05:144][  0]LogAudioCaptureCore: Display: No Audio Capture implementations found. Audio input will be silent.
[2022.01.10-12.49.05:144][  0]LogAudioCaptureCore: Display: No Audio Capture implementations found. Audio input will be silent.
[2022.01.10-12.49.08:077][  0]SourceControl: Source control is disabled
[2022.01.10-12.49.08:077][  0]SourceControl: Source control is disabled
[2022.01.10-12.49.08:628][  0]SourceControl: Source control is disabled
[2022.01.10-12.49.09:811][  0]SourceControl: Source control is disabled
[2022.01.10-12.49.10:045][  0]SourceControl: Source control is disabled
[2022.01.10-12.49.10:688][  0]LogUObjectArray: 54975 objects as part of root set at end of initial load.
[2022.01.10-12.49.10:688][  0]LogUObjectAllocator: 10126952 out of 0 bytes used by permanent object pool.
[2022.01.10-12.49.10:688][  0]LogUObjectArray: CloseDisregardForGC: 0/0 objects in disregard for GC pool
[2022.01.10-12.49.10:688][  0]LogInit: Executing Class /Script/Carla.PrepareAssetsForCookingCommandlet
[2022.01.10-12.49.10:688][  0]LogInit: Initializing Editor Engine...
[2022.01.10-12.49.10:688][  0]LogEngine: Initializing Engine...
[2022.01.10-12.49.10:691][  0]LogStats: UGameplayTagsManager::InitializeManager -  0.000 s
[2022.01.10-12.49.12:851][  0]LogInit: Initializing FReadOnlyCVARCache
[2022.01.10-12.49.13:904][  0]LogAIModule: Creating AISystem for world Untitled
[2022.01.10-12.49.13:905][  0]LogNetVersion: Set ProjectVersion to 0.9.11. Version Checksum will be recalculated on next use.
[2022.01.10-12.49.14:450][  0]LogDerivedDataCache: Saved boot cache 0.55s 35MB ../../../../carla/Unreal/CarlaUE4/DerivedDataCache/Boot.ddc.
[2022.01.10-12.49.15:443][  0]LogInit: Texture streaming: Disabled
[2022.01.10-12.49.16:787][  0]LogInit: Initializing Editor Engine Completed
[2022.01.10-12.49.18:632][  0]BlueprintLog: New page: Editor Load
[2022.01.10-12.49.22:050][  0]LogTemp: Error: Package json file not found.
[2022.01.10-12.49.22:050][  0]LogTemp: Error: Package json file not found.
[2022.01.10-12.49.22:050][  0]LogFileManager: Warning: ReadFile failed: Count=0 Length=110592 Error=errno=21 (Is a directory) for file
[2022.01.10-12.49.22:050][  0]LogFileManager: Warning: ReadFile failed: Count=0 Length=110592 Error=errno=21 (Is a directory) for file
[2022.01.10-12.49.22:133][  0]LogTemp: Error: Package json file not found.
[2022.01.10-12.49.22:133][  0]LogTemp: Error: Package json file not found.
[2022.01.10-12.49.22:205][  0]LogUObjectHash: Compacting FUObjectHashTables data took  10.23ms
[2022.01.10-12.49.22:209][  0]LogFileHelpers: No new changes to save!
[2022.01.10-12.49.22:209][  0]LogCore: Engine exit requested (reason: Commandlet PrepareAssetsForCookingCommandlet_0 finished execution (result 0))
1111[2022.01.10-12.49.22:209][  0]LogInit: Display:
[2022.01.10-12.49.22:209][  0]LogInit: Display:
[2022.01.10-12.49.22:209][  0]LogInit: Display: Warning/Error Summary (Unique only)
[2022.01.10-12.49.22:209][  0]LogInit: Display: Warning/Error Summary (Unique only)
[2022.01.10-12.49.22:209][  0]LogInit: Display: -----------------------------------
[2022.01.10-12.49.22:209][  0]LogInit: Display: -----------------------------------
1001[2022.01.10-12.49.22:209][  0]LogInit: Display: LogTemp: Error: Package json file not found.
[2022.01.10-12.49.22:209][  0]LogInit: Display: LogTemp: Error: Package json file not found.
1101[2022.01.10-12.49.22:210][  0]LogInit: Display: LogConsoleManager: Warning: Setting the console variable 'r.Streaming.PoolSize' with 'SetByScalability' was ignored as it is lower priority than the previous 'SetByProjectSetting'. Value remains '4000'
[2022.01.10-12.49.22:210][  0]LogInit: Display: LogConsoleManager: Warning: Setting the console variable 'r.Streaming.PoolSize' with 'SetByScalability' was ignored as it is lower priority than the previous 'SetByProjectSetting'. Value remains '4000'
[2022.01.10-12.49.22:210][  0]LogInit: Display: LogFileManager: Warning: ReadFile failed: Count=0 Length=110592 Error=errno=21 (Is a directory) for file
[2022.01.10-12.49.22:210][  0]LogInit: Display: LogFileManager: Warning: ReadFile failed: Count=0 Length=110592 Error=errno=21 (Is a directory) for file
[2022.01.10-12.49.22:210][  0]LogInit: Display:
[2022.01.10-12.49.22:210][  0]LogInit: Display:
1001[2022.01.10-12.49.22:210][  0]LogInit: Display: Failure - 2 error(s), 3 warning(s)
[2022.01.10-12.49.22:210][  0]LogInit: Display: Failure - 2 error(s), 3 warning(s)
[2022.01.10-12.49.22:210][  0]LogInit: Display:
Execution of commandlet took:  0.24 seconds
[2022.01.10-12.49.22:210][  0]LogInit: Display:
Execution of commandlet took:  0.24 seconds
[2022.01.10-12.49.22:210][  0]LogCore: Engine exit requested (reason: EngineExit() was called; note: exit was already requested)
[2022.01.10-12.49.22:210][  0]LogExit: Preparing to exit.
[2022.01.10-12.49.22:224][  0]LogWorld: UWorld::CleanupWorld for None, bSessionEnded=true, bCleanupResources=true
[2022.01.10-12.49.22:224][  0]LogExit: Editor shut down
[2022.01.10-12.49.22:224][  0]LogDemo: Cleaned up 0 splitscreen connections with owner deletion
[2022.01.10-12.49.22:335][  0]LogExit: Object subsystem successfully closed.
[2022.01.10-12.49.22:367][  0]LogShaderCompilers: Display: Shaders left to compile 0
[2022.01.10-12.49.22:367][  0]LogShaderCompilers: Display: Shaders left to compile 0
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module WebMMediaFactory (434)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module WebMMediaEditor (432)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module MediaPlayerEditor (430)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module MediaCompositingEditor (428)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module SequenceRecorder (427)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module Persona (426)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module AdvancedPreviewScene (425)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module AnimGraph (423)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module ImgMediaFactory (418)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module ImgMediaEditor (416)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module AvfMediaFactory (414)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module AvfMediaEditor (412)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module WmfMediaFactory (410)
[2022.01.10-12.49.22:385][  0]LogModuleManager: Shutting down and abandoning module Media (409)
[2022.01.10-12.49.22:386][  0]LogModuleManager: Shutting down and abandoning module WmfMediaEditor (406)
[2022.01.10-12.49.22:386][  0]LogModuleManager: Shutting down and abandoning module MagicLeapMediaEditor (404)
[2022.01.10-12.49.22:386][  0]LogModuleManager: Shutting down and abandoning module MatineeToLevelSequence (402)
[2022.01.10-12.49.22:386][  0]LogModuleManager: Shutting down and abandoning module ActorSeque

@xiaoqingnianbudadun Hi, try generating the binary file before running docker_tools.py. While I do not have experience with map ingestion, the following link may be helpful as it shows a tutorial on how to add maps to carla.
Map Ingestion CARLA

authors: Ayaanfaraz xiaoqingnianbudadun


text:
🛑 Verifica is down

In 0fbd024, Verifica (https://verifica.ifms.edu.br/ead/5cdb04be-5f88-4b97-8528-33620a01001c) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Verifica is back up in f1d2985 after 11 minutes.

source: gharchive/issue

repo: carlitos-ifms/uptime

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 OCI VPN is down

In 2ee3b23, OCI VPN (https://vpn-2.zaffonatto.it/) was down:

HTTP code: 530
Response time: 77 ms

Resolved: OCI VPN is back up in b49a0f9 after 1 hour, 34 minutes.

repo: carloszaffonatto/upptime


text:
Pion emissivity from pp interaction

I have been battling with the formula for a bit, and I think there's a problem with $E_\pi \to E_p K_\pi$ substitution that's seemingly going on here. First of all, it holds only in $\delta$-approximation that we are abandoning at this point. Second, it leaves us with $q_\pi$ somehow expressed in terms of $E_p$ which doesn't really make sense. Third, later when this formula is used to compute $q_\gamma$, the energy in the numerator seems to be taken as $E_\pi$.
Unrelated to this, but I have a question regarding this section: what happens to $\sigma_{pp}$? It seems as if it's replaced by some constant value $\sigma_pp(E_p) \approx \sigma_0$, but this is not explicitly addressed, and it's not obvious if it can be done with generally growing (even if slowly) function.

Regarding my second questions, seems like $\sigma_0$ is a high-energy limit of $\sigma_{pp \to \pi_0 X}$ with a numerical value $\approx 140~\text{mbarn}$.

source: gharchive/pull-request


text:
Provide CellProfiler pipeline files for the datasets

YJ asked:

could kindly share the CellProfiler pipeline with me if you have the CellProfiler pipeline of the LUAD dataset which can get the CellProfiler morphological profile data?

Pipelines are at https://github.com/broadinstitute/imaging-platform-pipelines/tree/455d8ffa2a0a6cb7341868139f3f1719b9d5ea2c/

Dataset
Cell line
Pipeline set

CDRP-BBBC047-Bray
U2OS
cellpainting_u2os_20x_imagexpress_cdrp

CDRPBIO-BBBC036-Bray
U2OS
cellpainting_u2os_20x_imagexpress_cdrp

LUAD-BBBC041-Caicedo
A549
cellpainting_a549_20x_imagexpress

TA-ORF-BBBC037-Rohban
U2OS
cellpainting_u2os_20x_imagexpress_cdrp

LINCS-Pilot1
A549
cellpainting_a549_20x_phenix_bin1


text:
Include external CSS in SWC lessons

These lessons reference CSS outside of their own directories within the
website, so require spanning across hosts. Thi is limited to the lesson
site to avoid major expansions of the volume of data stored.
This is only done for Software Carpentry because it is not needed for
Data Carpentry and because DC lessons are posted to the organizations
main domain adding -H increases storage by 10x.
Co-authored-by: Virnaliz Cruz virnaliz.cruz@weecology.org

@garezana - check that this is working for you as well and then merge and let the other folks know on Slack that this is fixed.

I also just added some improvements to the lesson output so it's not just a giant wall of streaming wget information

repo: carpentriesoffline/offlinedatasci


text:
Solves #40 #41

Inserted MIT license in all swift files.
Added buildRequest(_:) to RequestParam.
Implemented SessionConfiguration protocol to set properties to URLSessionConfiguration as internal protocol.
CombinedParams is not cast over the framework anymore. Added unzip to RequestParam that will check if the self-reference is a CombinedParams type, returning the children if it is, or returning self inside an Array if it isn't.

I'm personally not a fan of putting the license in every file... Would you mind reverting that?

Alright, no problem

Codecov Report

Merging #42 (01709a3) into master (89e948d) will decrease coverage by 0.86%.
The diff coverage is 90.78%.

@@            Coverage Diff             @@
##           master      #42      +/-   ##
==========================================
- Coverage   81.25%   80.38%   -0.87%
==========================================
  Files          23       28       +5
  Lines         480      469      -11
==========================================
- Hits          390      377      -13
- Misses         90       92       +2

Impacted Files
Coverage Δ

...urces/Request/Request/RequestParams/AnyParam.swift
0.00% <0.00%> (ø)

...t/Request/RequestParams/RequestConfiguration.swift
0.00% <0.00%> (ø)

...Request/Request/RequestParams/CombinedParams.swift
66.66% <66.66%> (ø)

Sources/Request/Request/RequestBuilder.swift
80.00% <80.00%> (+1.05%)
:arrow_up:

...ces/Request/Request/RequestParams/QueryParam.swift
92.30% <90.00%> (-7.70%)
:arrow_down:

Sources/Request/Request/RequestParams/Query.swift
92.30% <92.30%> (ø)

Sources/Request/Request/Request.swift
97.95% <96.00%> (+4.77%)
:arrow_up:

Sources/Request/Request/Extra/RequestChain.swift
100.00% <100.00%> (ø)

Sources/Request/Request/RequestParams/Body.swift
100.00% <100.00%> (ø)

...ces/Request/Request/RequestParams/EmptyParam.swift
100.00% <100.00%> (ø)

... and 12 more

Continue to review full report at Codecov.

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

This looks good to me, was there anything else you needed to add/change for this PR? If not, I'll merge it now.

@carson-katri you can merge it

authors: brennobemoura carson-katri codecov-io

repo: carson-katri/swift-request


text:
🛑 API is down

In 274b366, API (https://api.cartelmatic.com/APIDisponibilites/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: API is back up in 2d5a6ed after 3 minutes.

repo: cartelmatic/upptime


text:
Compile tools statically linked to MUSL instead of GLIBC

Statically linking to MUSL instead of GLIBC would make the final binaries smaller, allowing rootfs to be more compact. Also statically linking GLIBC is not recommend, though @mpolitzer pointed this does not impact us.
To do this we would need to use a MUSL toolchain to build the tools, we could probably use Alpine toolchain or some other distro to compile them instead of creating our own toolchain, or maybe we could move our toolchain to use MUSL once we get rid of buildroot.

(For reference)
As mentioned, there are a couple of problems with the musl solution, both regarding rust.

The first is that their RISC-V is Tier-3, that is untested and not even build automatically by them (but available on alpine), and even though it seems to work fine there is an increased risk of finding bugs along the way, such as cargo update memory blowing up.
The second is that since they don't provide a nightly version, and from what I searched that is required for static compilation.

notes on glibc static compilation: https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked_programs_need_some_shared_libraries_which_is_not_acceptable_for_me.__What_can_I_do.3F

We should not forget about this, there have been some interest from others to use Alpine for example. I also have interest to make "distroless" dapps, where I would install tools into an empty filesystem and copy my dapp statically linked, the dapp rootfs would be very tiny this way.
To make this happen we need to:

Bundle busybox or toybox
Link everything statically OR link dynamically but provide a libc shared library like in libc-cartesi.so

There are plans to deprecate the rollup-http-server and remove it from this repo.
We'll have a lot more flexibility when that happens.
With only C/C++ code on the repository we'll be able to experiment with a statically compiled tools.

On the boxybox, toybox, I'd suggest taking a look at s6 ecosystem, where is provided a lot of simple versions of useful linux tools with support for musl and multicall binary just like busybox.

https://skarnet.org/software/s6-portable-utils/
https://skarnet.org/software/execline/
https://skarnet.org/software/s6-linux-utils/
https://skarnet.org/software/s6-linux-init/
https://skarnet.org/software/s6/

I've already used its s6-rc and s6-overlays on container environments, but I never used it inside cartesi-machine, but I plan to test it.

authors: edubart endersonmaia mpolitzer

repo: cartesi/machine-emulator-tools


text:
gulp release should assume --prod flag is true

With gulp release --prod, the production flag should be assumed as true.
Running gulp release with no flag should minify assets etc as expected

I think this should apply for the gulp build task, as it doesn't minify css (for example) without the flag @tawashley @bmds

@mmacartney10 Are you happy to take this feature on yourself?

@bmds I have updated this just need the pull request reviewing here #47

authors: bmds mmacartney10 tawashley

repo: cartridge/cartridge

license: mit

license_source: bigquery


text:
Don't return 200s until all services are running

The readiness check should confirm that all services are running, and if not return a non-200 code.

Missed this in refactoring services: FakeServiceModule uses Service multibindings directly. Need to fix the ReadinessCheckAction to actually obtain a list of services (or a service manager?).

authors: keeferrourke swankjesse

repo: cashapp/misk


text:
Upgrade from logback to log4j2 for logging backend

History:
2001: log4j 1.0 released.
2002: java.util.logging released (in JDK 1.4).
2006: slf4j 1.0 released. It is a frontend only.
2011: logback 1.0 released. It is a backend only.
2014: log4j2 2.0 released.
We should migrate to log4j2 as it is the newest hotness.

Switching to log4j2 will allow us to get timestamps in nanosecond precision.

This didn't age well!

authors: mightyguava swankjesse


text:
Ability to create custom tags

Can I create custom tags like @if and @for ?
The idea is to create a vue component using the tag and generate java script. The listen to event using ws. Something similar to blazor .net framework.

Welcome @adpande!
Yes, you can absolutely create custom tags. You need to put them into the tag directory within your jte root folder. For instance, you can create a jte file like this:
tag/vue/component.jte
In other templates you can then call it like this:
@tag.vue.component()
For more details, have a look at the tag syntax documentation.

Hey, thanks @casid! I will try, I think this will solve it.

@adpande thanks for the follow up! Good luck with your vue js tags, that sounds very intesting :-)
Whenever you have something to share/show, let me know, it's nice to see what other devs do with jte.

authors: adpande casid

repo: casid/jte


text:
Migrate to new Caskroom not working as expected...

Remember to follow the pre bug report guide beforehand. Failure to do so might get your issue closed.
Description of issue
I reviewed issue #21913 to move my old Casks to to the new location. It did not work as expected: the applications are still in the old Caskroom.
I tried the command mentioned towards the end of the issue:
brew cask install --force $(brew cask list)
And the new Caskroom is not even created:
mosheen:[~->]~$ ls /usr/local/Caskroom
ls: /usr/local/Caskroom: No such file or directory
Output of `brew cask  --verbose`
mosheen:[Homebrew->stable]/usr/local/Homebrew$ brew cask install --force --verbose $(brew cask list)
Warning: The default Caskroom location has moved to /usr/local/Caskroom.

Please migrate your Casks to the new location and delete /opt/homebrew-cask/Caskroom,
or if you would like to keep your Caskroom at /opt/homebrew-cask/Caskroom, add the
following to your HOMEBREW_CASK_OPTS:

  --caskroom=/opt/homebrew-cask/Caskroom

For more details on each of those options, see https://github.com/caskroom/homebrew-cask/issues/21913.
Warning: The default Caskroom location has moved to /usr/local/Caskroom.

Please migrate your Casks to the new location and delete /opt/homebrew-cask/Caskroom,
or if you would like to keep your Caskroom at /opt/homebrew-cask/Caskroom, add the
following to your HOMEBREW_CASK_OPTS:

  --caskroom=/opt/homebrew-cask/Caskroom

For more details on each of those options, see https://github.com/caskroom/homebrew-cask/issues/21913.
==> Downloading https://kits-crashlytics-com.s3.amazonaws.com/fastlane/standalone/bundle-1.7.zip
Already downloaded: /Users/yc98js1/Library/Caches/Homebrew/Cask/fastlane--1.7.zip
==> Verifying checksum for Cask fastlane
==> Running installer script /opt/homebrew-cask/Caskroom/fastlane/1.7/install
==>
==> fastlane is already installed at /Users/yc98js1/.fastlane/bin
==>
==>
==> The installer will now run the uninstall script to remove your existing fastlane bundle...
==>
==>
==> You can now remove fastlane from your search path by editing your ~/.bash_profile file.
==>
==>
==> fastlane was uninstalled successfully!
==>
==>
==> Done uninstalling, your regular installation will now commence. 🚕 💨
==>
==>
==> Installing fastlane to /Users/yc98js1/.fastlane/bin... this might take a few seconds
==>
==>
==> Successfully copied fastlane to /Users/yc98js1/.fastlane/bin
==>
==>
==>
==> Updating installed gems
==> Updating fastlane
==> Successfully installed tty-screen-0.5.0
==> Successfully installed fastlane-2.19.3
==> Gems updated: fastlane tty-screen
==> Cleaning up installed gems...
==> Attempting to uninstall fastlane-2.13.0
==> Successfully uninstalled fastlane-2.13.0
==> Clean Up Complete
==>
==> Detected shell config file at path '~/.bash_profile'
==>
==>
==> Please add the following line to your bash profile:
==>
==>
==>
==> export PATH="$HOME/.fastlane/bin:$PATH"
==>
==>
==>
==> After doing so close the terminal session and restart it to start using fastlane 🚀
==>
🍺  fastlane was successfully installed!
==> Downloading http://frim.frim.nl/GitXStable.app.zip
Already downloaded: /Users/yc98js1/Library/Caches/Homebrew/Cask/gitx--0.7.1.zip
==> Verifying checksum for Cask gitx
Warning: It seems there is already an App at '/Applications/GitX.app'; overwriting.
==> Removing App: '/Applications/GitX.app'
==> Moving App 'GitX.app' to '/Applications/GitX.app'
==> Symlinking Binary 'gitx' to '/usr/local/bin/gitx'
🍺  gitx was successfully installed!
==> Downloading https://github.com/whomwah/qlstephen/releases/download/1.4.4/QLStephen.qlgenerator.1.4.4.zip
Already downloaded: /Users/yc98js1/Library/Caches/Homebrew/Cask/qlstephen--1.4.4.zip
==> Verifying checksum for Cask qlstephen
Warning: It seems there is already a QuickLook Plugin at '/Users/yc98js1/Library/QuickLook/QLStephen.qlgenerator'; overwriting.
==> Removing QuickLook Plugin: '/Users/yc98js1/Library/QuickLook/QLStephen.qlgenerator'
==> Moving QuickLook Plugin 'QLStephen.qlgenerator' to '/Users/yc98js1/Library/QuickLook/QLStephen.qlgenerator'
🍺  qlstephen was successfully installed!

Output of `brew doctor`
mosheen:[~->]~$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  ruby

Output of `brew cask doctor`
mosheen:[~->]~$ brew cask doctor
==> Homebrew-Cask Version
Homebrew-Cask 1.1.11-23-gb38c52f93
caskroom/homebrew-cask (git revision d146; last commit 2017-03-10)
==> Homebrew-Cask Install Location
<NONE>
Warning: The default Caskroom location has moved to /usr/local/Caskroom.

Please migrate your Casks to the new location and delete /opt/homebrew-cask/Caskroom,
or if you would like to keep your Caskroom at /opt/homebrew-cask/Caskroom, add the
following to your HOMEBREW_CASK_OPTS:

  --caskroom=/opt/homebrew-cask/Caskroom

For more details on each of those options, see https://github.com/caskroom/homebrew-cask/issues/21913.
==> Homebrew-Cask Staging Location
/opt/homebrew-cask/Caskroom
==> Homebrew-Cask Cached Downloads
~/Library/Caches/Homebrew/Cask (3 files, 26.9MB)
==> Homebrew-Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask (3595 casks)
==> Contents of $LOAD_PATH
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin15
/Library/Ruby/Site/2.0.0/universal-darwin15
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin15
==> Environment Variables
LANG="en_US.UTF-8"
LANGUAGE="en_US.UTF-8"
LC_ALL="en_US.UTF-8"
PATH="~/bin:~/.rvm/gems/ruby-2.0.0-p643/bin:~/.rvm/gems/ruby-2.0.0-p643@global/bin:~/.rvm/rubies/ruby-2.0.0-p643/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Library/Java/JavaVirtualMachines/jdk1.8.0_73.jdk/Contents/Home/bin:~/Android/tools:~/Android/platform-tools:~/.rvm/bin:/usr/local/share/npm/bin:/opt/oracle/instantclient_11_2:/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/cmd:/usr/local/Homebrew/Library/Homebrew/shims/scm"
SHELL="/usr/local/bin/bash"

As long as the old Caskroom directory /opt/homebrew-cask/Caskroom exists, the new location will not be created.

Thanks... please add that comment to the bottom of #21913 or add it to the comments in brew.

authors: JESii reitermarkus

repo: caskroom/homebrew-cask


text:
Wireshark is failing to install with outdated URL

Description of issue
Wireshark URL is outdated, it seems to be downloaded from https://1.na.dl.wireshark.org/osx/Wireshark 2.4.1 Intel 64.dmg now as per the recipe defined in homebrew-core.
Output of your command with --verbose --debug
$ brew cask install wireshark --verbose --debug
==> Hbc::Installer#install
==> Printing caveats
==> Hbc::Installer#fetch
==> Satisfying dependencies
==> Downloading
==> Downloading https://www.wireshark.org/download/osx/Wireshark%202.4.1%20Intel%2064.dmg
/usr/bin/curl --show-error --user-agent Homebrew/1.3.2 (Macintosh; Intel Mac OS X 10.12.6) curl/7.54.0 --fail --location --remote-time --continue-at - --output /Users/randrade/Library/Caches/Homebrew/Cask/wireshark--2.4.1.dmg.incomplete https://www.wireshark.org/download/osx/Wireshark%202.4.1%20Intel%2064.dmg
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 503 Service Temporarily Unavailable
Error: Download failed on Cask 'wireshark' with message: Download failed: https://www.wireshark.org/download/osx/Wireshark%202.4.1%20Intel%2064.dmg
Error: Install incomplete.
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:13:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/abstract_command.rb:35:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:97:in `run_command'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:167:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:131:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
Error: Kernel.exit
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:172:in `exit'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:172:in `rescue in run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:155:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:131:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'

Output of brew cask doctor
==> Homebrew-Cask Version
Homebrew-Cask 1.3.2
caskroom/homebrew-cask (git revision 780ac; last commit 2017-09-19)
==> Homebrew-Cask Install Location
<NONE>
==> Homebrew-Cask Staging Location
/usr/local/Caskroom
==> Homebrew-Cask Cached Downloads
~/Library/Caches/Homebrew/Cask (15 files, 1GB)
==> Homebrew-Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask (3736 casks)
==> Contents of $LOAD_PATH
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin16
/Library/Ruby/Site/2.0.0/universal-darwin16
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin16
==> Environment Variables
LANG="en_US.UTF-8"
PATH="~/.nvm/versions/node/v6.11.2/bin:~/go/bin:/usr/local/Cellar/go/1.8.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/Cellar/php70/7.0.22_14/bin:/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/cmd:/usr/local/Homebrew/Library/Homebrew/shims/scm"
SHELL="/bin/bash"

brew cask audit --download wireshark
==> Downloading https://www.wireshark.org/download/osx/Wireshark%202.4.1%20Intel
######################################################################## 100.0%
==> Verifying checksum for Cask wireshark
audit for wireshark: passed

Still not working for me.
At wireshark.org/#download, the macOS download link is now https://1.na.dl.wireshark.org/osx/Wireshark 2.4.2 Intel 64.dmg
Maybe the cask should use this new/alternative download link.
$ brew cask audit --download wireshark
11:41:26
==> Downloading https://www.wireshark.org/download/osx/Wireshark 2.4.2 Intel 64.dmg
curl: (22) The requested URL returned error: 503 Service Temporarily Unavailable
audit for wireshark: failed

download not possible: Download failed on Cask 'wireshark' with message: Download failed: https://www.wireshark.org/download/osx/Wireshark 2.4.2 Intel 64.dmg

error retrieving appcast:
curl: (22) The requested URL returned error: 503 Service Temporarily Unavailable

error retrieving appcast:
curl: (22) The requested URL returned error: 503 Service Temporarily Unavailable
Error: audit failed for casks: wireshark

authors: commitay eliezio robertoandrade


text:
Update privatetunnel.rb

fix https://github.com/caskroom/homebrew-cask/issues/19823

Thank you. However, please don’t open issues if you intend to submit a PR fixing it.

authors: e-moe vitorgalvao


text:
Update slack to 2.6.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as b053c2d4070d6dd88bebf03c57c6a8c89ba946c5. Your contribution is still credited to you.

authors: commitay vitorgalvao


text:
Remove travis buddy

With the high volume of traffic we have in Caskroom combined with Casks that fail with unfixable errors make the notifications somewhat annoying.
Improving our build scripts to collect and handle errors might help but that is a separate issue that will require a reasonable amount of work.

make the notifications somewhat annoying

Do you get emails for everything?

No, web notifications.

I also use web notifications, and TravisBuddy is a net win for me. Not having to click around and waiting for Travis to load to see an error is tremendously useful.
Since we’re the ones that spend most time with the PRs, let’s see if we can get a consensus.
How does TravisBuddy make your web notifications more annoying? Because to me it’s neutral, notifications-wise. Here’s what I do:

Open https://github.com/notifications in the browser.
Run (via Alfred) a JXA script I made that will:
Check if there are unread notifications. If yes, go to 4, else jump to 5.
Go into https://github.com/notifications/participating and stop.
Grab all notifications (by this point, they’re all for things I haven’t participated in).
Ignore closed and merged issues and PRs.
Open all remaining in new browser tabs.

I leave GitHub open in a browser most of the day, so I already get a notification whenever an issue or PR is opened or commented on. Getting notifications for every build failure is annoying and makes notifications less useful to me.
Seeing the build output without having to open Travis is useful, the notification is not.
I've been preemptively commenting on builds that I know will fail with @TravisBuddy stop just so I don't get a notification a couple of minutes later.
Blocking the Travis Buddy user doesn't work so I think the the only other option would be to stop watching the repo which isn't something that I want to do.

Alright, if it’s that annoying to you, let’s get rid of it.

@commitay @vitorgalvao

I've been preemptively commenting on builds that I know will fail with @TravisBuddy stop just so I don't get a notification a couple of minutes later.

Sorry to bump this old issue, but just had an idea:
You've said that you use @TravisBuddy stop on builds since you already know it will fail - What if TravisBuddy won't comment on those builds at all? Do you think we could tag those builds somehow? Maybe using regex on build logs?
Would love to hear your thoughts on this idea :)

Sorry to bump this old issue

No problem!

What if TravisBuddy won't comment on those builds at all? Do you think we could tag those builds somehow? Maybe using regex on build logs?

Something like this could work it but it would need to be very finely tuned to a point that not be practical.  Some of the expected failures are very similar to an actual error that shouldn't be disregarded.
I think overhauling our build scripts would be the the best approach as it would allow us to handle these type of expected failures and other general build problems at the same time.

I see, thank you for sharing!
We've earned so many great features by learning from failed integrations like this one, so I really appreciate your response. :)
If you come up with an idea of how we could improve the service to better fit your needs (regardless of your in-house changes that needs to be done before trying the integration again), please let me know.

authors: bluzi commitay vitorgalvao


text:
Create font-skola-sans.rb

This is a lovely and large sans serif font family on Bechance. I use it on my personal blog and wanted to have an easy way to download it on new machines.

Didn't know that. Thanks for the heads up. Committed the change.

Thank you. Could you please squash your commits?

Squashed

Thank you.

authors: smargh vitorgalvao

repo: caskroom/homebrew-fonts


text:
Add Adobe Air Beta 26.0.

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Thank you for your contribution.

repo: caskroom/homebrew-versions


text:
Add TrackingMap to make Arc/Weaks used more robust

In some places in the node we currently shuffle Arcs and Weaks around, with manual cleanup. This functionality, if not replaced, should be replace with a tested data structure that tracks these things by itself and ideally removes the Weak on Drop, or garbage collects them when prompted.

This has been made obsolete with the addition of the new connection manager.

authors: RitaMAllenCA marc-casperlabs

repo: casper-network/casper-node


text:
GH-2604: Fix AssemblyScript ordering bug

Closes #2604
Fixes a bug where account hashes were not properly ordered.

bors r+


text:
Experiment: Extract context mutations to type level.

Problem:
Let's say you're working with a state machine with nodes a and b and context as A | B, now you know that in node a the context is always of type A and in node b the context is of type B. But the context receive in the effect will be of type A | B for both nodes and the user would have to make assertions.
xstate's solution:
The way xstate solves this is by letting the user define the relation between state and context via the "TTypestate" type parameter and "typestate" being an actual thing.
txstate's solution:
xstate has an advantage that the context is immutable, the only way to mutate it is via assign. So all mutations can be found by looking at the type of the machine and hence the typestates can be derived and the user need not write them manually. Explained in detail here
useStateMachine's solution:
Thing is right now there isn't a way to solve this because the context is fully mutable, not only it is mutable but it can be mutated many times inside an effect (you can spin up a setInterval which changes the shape of context each time)
I've opened this issue to sort of discuss if we can improve on this. My first attempt is to make effect an generator, then the user can basically emit mutations and the they will be extracted to the type as typescript can infer generators too (hover over effect) and it seems there is a lot of prior art in using generators as effects (redux-saga, fx-ts, et al). But the problem is right now effect is even capable of "reducing" the context instead of just setting it. Which basically comes in the way.
So my first question is if setContext does not take a reducer do you think there will be things user won't be able to do? Like the effect only receives a context which would be on the entry then there's no way to determine the current context, you think that'd make a big difference?
Also more important question haha - you think the problem that I point out is big enough that we even think about solving it? If not then we can close this (to mark the stance) and still keep discussing if both of us are still interested.

That's a very good question. The target audience for useStateMachine is not a hard-core State Machine user, but someone who wants to start using state machines in some parts of their app, as a consequence useStateMachine is designed to be less strict and get out of the way. So the user can, for example, call setContext multiple times in the effect - we even have an example that does that. I think that keeping this flexibility is more important than tying a relation between context and state.
That being said, I would love to have that. It's tremendously important, and if we can come up with a way to implement that that doesn't come at a cost of this current flexibility (or even if it has a cost, but one that doesn't completely shave, for example, the ability to do a timer that changes the context inside the effect), it would certainly be a great addition.

Great! It doesn't shave that ability, the change I meant was...
- setContext: (updator: (context: Context) => Context)
+ setContext: (context: Context)

Would you say this change hampers the current flexibility?

What about the timer example? Currently it looks like this:
running: {
        on: {
          PAUSE: 'paused',
        },
        effect({ setContext }) {
          const interval = setInterval(() => {
            setContext(context => ({ time: context.time + 1 }));
          }, 100);
          return () => clearInterval(interval);
        },
      },

Won't context become stale with this change?

Won't context become stale with this change?

It certainly would though the user can refactor it like this...
effect: function* ({ setContext }) {
  let time = context.time;
  while (true) {
    await new Promise(r => setTimeout(r, 100));
    yield { ...context, time }
  }
}

Of course this assumes that only one effect is mutating the context at once. If multiple effects mutate the context but different properties then we might even provide a set function and then the user would do yield set({ time }) instead. (I think redux-saga has this they call it put). And set being something like <T>(value: T) => { type: "SET", value: T }. We could even directly provide a function like increment so they'd just yield set({ time: increment() }) at intervals. The only limitation is the user can't access the current context directly and there are many ways to get around it.
There are other gaps to fill like how would on set up a clean up maybe we can have something like yield cleanup(() => {}).
And the users don't have to write while (true) etc they can also leverage things like IxJS and it'd look something like...
for await (let time of interval(100)) {
  yield set({ time })
}

Though this is all for power users, for basic stuff like waiting for a promise just a simple await would do.

authors: cassiozen devanshj

repo: cassiozen/useStateMachine


text:
Error while packaging with electron-builder

Hi,
I am running into a issue while packaging the app for distribution using electron-builder. (macOS)
While the electron-releases#v10.0.0-wvvmp-beta.25 is specified in my Dependecies in package.json:
"devDependencies": {     "electron": "https://github.com/castlabs/electron-releases#v10.0.0-wvvmp-beta.25",     "electron-builder": "^22.8.0"   }
yarn or npm is still crashing on following:
" ⨯ cannot resolve https://github.com/electron/electron/releases/download/v10.0.0-wvvmp-beta.25/electron-v10.0.0-wvvmp-beta.25-darwin-x64.zip: status code 404"
It is obviously trying to connect to the official electron GitHub repo and download the fork from there.
Any idea how to fix it ?
Best regards,
Ondrej

If you read the docs for electron-builder you should find there's a way to configure it with mirror options. It'll means specifying something like:
download: {
    mirrorOptions: {
      mirror: 'https://github.com/castlabs/electron-releases/releases/download/'
    }
}

In your config.

If you read the docs for electron-builder you should find there's a way to configure it with mirror options. It'll means specifying something like:
download: {
    mirrorOptions: {
      mirror: 'https://github.com/castlabs/electron-releases/releases/download/'
    }
}

In your config.

Yes, I have system wide variable ELECTRON_BUILDER_BINARIES_MIRROR, ELECTRON_MIRROR set to the castlabs GitHub repo, but that does not seems to do the trick.

Not sure I can add anymore, if you've got the config right then it sounds like there's a bug to raise elsewhere. I don't use electron-builder, but I'm pretty sure what I'm using delegates to the same package (and that works here), might be worth you checking then reading the usage docs: https://github.com/electron/get#usage

Not sure I can add anymore, if you've got the config right then it sounds like there's a bug to raise elsewhere. I don't use electron-builder, but I'm pretty sure what I'm using delegates to the same package (and that works here), might be worth you checking then reading the usage docs: https://github.com/electron/get#usage

Appreciate the fast reply Simon,
Can you recommend other packaging solution that is working with castlabs electron ?

I can't really exactly but I think they moved this option at some point. Anyway, you need to include it under build in your package.json and add an extra v compared to the above URL. E.g. something like this:
{
  "name": "MyApp",
  ...,
  "build": {
    "electronDownload": {
      "mirror": "https://github.com/castlabs/electron-releases/releases/download/v"
    },
    ...,
    "afterPack": "build/after-pack.js",
    "afterSign": "build/after-sign.js"
  }
}

It might work with environment variables too, but I've not tested that.

I can't remember exactly but I think they moved this option at some point. Anyway, you need to include it under build in your package.json and add an extra v compared to the above URL. E.g. something like this:
{
  "name": "MyApp",
  ...,
  "build": {
    "electronDownload": {
      "mirror": "https://github.com/castlabs/electron-releases/releases/download/v"
    },
    ...,
    "afterPack": "build/after-pack.js",
    "afterSign": "build/after-sign.js"
  }
}

It might work with environment variables too, but I've not tested that.

Emil, yet again you are absolute lifesaver. The "v" and the end of the url was the issue.

authors: khwaaj olirehacek simongregory

repo: castlabs/electron-releases


text:
Integrate EIA 860 Fuel Switching data (Schedule 3.5)

The EIA 860 contains reports information about fuel switching and multi-fuel generators, which we have not yet integrated into PUDL. We should bring it in either as a new table, or as part of generators_eia860
3_5_MultiFuelYyyyy – Contains data on fuel-switching and the use of multiple fuels by surveyed generators,

Subsumed within #1159 & #1189 for now.

repo: catalyst-cooperative/pudl


text:
Apply new naming convention to PUDL assets

Pending approval of the design doc, we should actually apply the naming convention
Scope is placeholder, to be fleshed out on design doc completion.
## Scope
- [ ] https://github.com/catalyst-cooperative/pudl/issues/2777
- [ ] https://github.com/catalyst-cooperative/pudl/issues/2788
- [ ] https://github.com/catalyst-cooperative/pudl/issues/2868
- [x] Add warnings to PudlTabl
- [ ] https://github.com/catalyst-cooperative/pudl/issues/2812
- [x] Run a full nightly build before merging into dev
- [x] Double check everything has been renamed... see #3052
- [ ] https://github.com/catalyst-cooperative/pudl/issues/3030
- [ ] Update table names in kaggle notebooks, pudl-example notebooks currently don't work so don't worry about updating them
- [ ] https://github.com/catalyst-cooperative/pudl/pull/3073

Hey @jdangerx! I was thinking about breaking up the work into two PRs off of dev:

Rename the raw and intermediate core assets
Rename the user-facing tables and documentation

I could also rename the user-facing tables in separate PRs to avoid a monster PR though the table names on dataset and s3 will follow different naming conventions during the conversion. This might be fine given the tables already follow different conventions! I could start with the output tables because we have a disclaimer that the current names are temporary and finish with the core tables which most users likely rely on. What do you think?

I think splitting this into:

raw_, _core
core
_output, output (I guess you could put the _output as a separate PR earlier in the process, since it's also hidden from users)

Makes sense to me! I'm OK with having discrepancies on datasette vs. S3 since we're pretty clear about the nightly builds being unstable.
I like doing the non-user-facing stuff first as practice for the user-facing stuff - we can see what breaks when we try to publish the data with the new names, before it breaks stuff for more important tables...
I think it's a good idea to move as much stuff from output into _output as possible, before we make output tables accessible to the public. Putting something in output is basically a promise to users that it will stay there - we can always "promote" _output tables to output. Same for core, really, though I think we have less leeway there.

Sounds good!
Based on feedback in #2503, people would prefer the changes to happen once. Here is a more detailed plan of how we can roll out these changes:

Rename raw and intermediate core assets. Merge into dev. None of these assets are persisted to the database so this will not impact users.
Rename output and core assets in a feature branch. This step will include converting some output assets that don't need to be user-facing to intermediate assets that aren't persisted in the database. We don't want to release a bunch of new tables in a tagged version and later remove them. This branch will also add a deprecation warning to PudlTabl. s3://intake.catalyst.coop should be renamed to s3://pudl.catalyst.coop #2574 prior to step 3.
Before merging the feature branch into dev, merge dev into main, tag a version pre-naming-change, and run a full build. Users can rely on this tagged version as they migrate to use the new table names and remove PudlTabl.
Merge the feature branch into dev, merge dev into main and tag a release using our desired release naming convention: vYYYY.MM.DD.
Help users migrate from depending on PudlTabl, old table names and pinning to dev to relying on the new tables in the pudl.sqlite database in the public s3 bucket.
Once core users are migrated, deprecate PudlTabl.

How does this plan sound to y'all? @zaneselvans @arengel @grgmiller @gschivley?

Ok! I think we're going to merge this thing in! Here is a todo list for rolling this out:
Release 2022 data with old names

[ ] Open a PR merging the latest commits to pass the nightly builds on dev into main.
[ ] The commits are in main. The 2022 data will be in main so we can do a data release!
[ ] Create and push a tag called v2023.12.04. This will kick off a full build.
[ ] When the build passes we'll have directory called s3://pudl.catalyst.coop/v2023.12.04
[ ] Create a manual Zenodo data release with the tagged data (not entirely sure what this entails)
[ ] Notify known users that we'll be applying the rename to dev so if they are pinned to data on datasette or pulling from the s3://pudl.catalyst.coop/dev directory, their code will break. To resolve the breakage, point your code towards the data in s3://pudl.catalyst.coop/v2023.12.04 or replace your references to PUDL tables using this sheet. Users who are still using PudlTabl and are pinned to dev will not be affected because the PudlTabl methods have not been changed though we are planning on removing PudlTabl and users should migrate to pulling the data directly from the database.

Release PUDL with new names

[ ] Merge https://github.com/catalyst-cooperative/pudl/pull/2818 into dev.
[ ] Once the nightly builds have a successful run, open a PR from dev into main.
[ ] Once the new names are in main create a tag called v2023.12.{day}, push and wait for a build to pass
[ ] Create a manual Zenodo data release once the build passes
[ ] Notify our users about the changes and fix breakages (example notebooks... tbd)

Questions

Should we do a code freeze on dev and main while we are working through these release mechanics?
How do we want to name these releases? They will likely happen on different days so the names will be different or we could use a suffix like v2023.12.04.oldnames and v2023.12.04.

Sounds like @zaneselvans and I will get cracking on the data release once #3086 is merged.

authors: bendnorman jdangerx


text:
WIF external test

I expect the google auth to fail and then we should fall back to Zenodo for everything.

Hooray! In the logs we can see that gcloud auth failed and we fell back to Zenodo!


text:
Add BaseDataInterface API docs

Including the BaseDataInterface in API docs so :py:class references link to it.

I was wondering why that link wasn't working!

authors: CodyCBakerPhD bendichter

repo: catalystneuro/neuroconv


text:
Add demo notebook

Add tutorial to showcase how to access data from the nwb files of dandiset 001170

Error from https://github.com/catalystneuro/reimer-arenkiel-lab-to-nwb/blob/2da78a1e506e2dfc2608c9366bc7422b8b0a035b/src/reimer_arenkiel_lab_to_nwb/embargo2024/tutorial/tutorial.ipynb#L105
---------------------------------------------------------------------------
Exception                                 Traceback (most recent call last)
Cell In[4], line 5
      2 import remfile
      4 # We stream the file using remfile and open it with h5py and pynwb
----> 5 file = remfile.File(s3_url)
      6 h5_file = h5py.File(file, "r")

File ~\anaconda3\envs\reimer_arenkiel_lab_to_nwb_env\Lib\site-packages\remfile\RemFile.py:77, in RemFile.__init__(self, url, verbose, disk_cache, _min_chunk_size, _max_cache_size, _chunk_increment_factor, _bytes_per_thread, _max_threads, _max_chunk_size, _impose_request_failures_for_testing, _size, _use_session)
     75     self.length = int(response.headers["Content-Length"])
     76 else:
---> 77     raise Exception(
     78         f"Error getting file length: {response.status_code} {response.reason}"
     79     )
     80 # Close the connection without reading the content to avoid downloading the whole file
     81 response.close()

Exception: Error getting file length: 403 Forbidden


text:
preg_match() expects parameter 2 to be string, array given in

function  column_push
foreach ($columns as $key => $value) { preg_match('/([a-zA-Z0-9_\\-\\.]*)\\s*\\(([a-zA-Z0-9_\\-]*)\\)/i', $value, $match); ...
my sql : where
array( 			'AND'	=> array( 				'OR'	=> array( 					'a'	=> 1, 					'b'	=> 2, 				), 				'c'	=> 3, 			) 		)
run :
[Warning] : preg_match() expects parameter 2 to be string, array given in File

Sorry, it was my operation in question

repo: catfan/Medoo


text:
change --background-darker to stay consistent with the default theme

I suspect something changed upstream with heroic, and --background-darker now effects the "Recently Played" and "All Games" headers, which are, in the default heroic theme and in the screenshots in this repo, the same color as --background.
Note - Apologies if I did something wrong with this, I'm very new to pull requests and contributing to projects in general.

Hey there, good catch, it seems that the ui has changed quite a bit. Looks much better with your changes.
Thank you very much for your contribution, I will merge the pull request and update the screenshots.

authors: DrymarchonShaun ndsboy

repo: catppuccin/heroic


text:
Welcome Screen: wrong project selection color

Theme version: 2.0.9
Hello and first of all, thanks you so much for such amazing theme. Looks like I have found incorrect color on welcome screen which uses for a single project selection/highlighting/hovering. The investigation shows that IntelliJ uses lightSelectionBackground parameter from Table object instead of some in WelcomeScreen object. To fix this issue that parameter should be defined in main.ts file. Actually, I can create the fix on my end and then create a new pull request or it could be fixed by someone else. Currently, the question is more about which color should we use for selection/highlighting/hovering. I think there are few options: selectionBackground and secondaryBackground.
Let's decide.
current color

selectionBackground color

secondaryBackground color

Hiya 👋, thanks for reporting this in such great detail!
While selectionBackground makes the most sense, I actually think secondaryBackground looks best out of the two as it doesn't clash with the grey project name as much. It is also worth mentioning that it should look nice on all flavours so we may have to resort to using isLatte() checks along with the opacity function.
It'd be great if you want to raise a PR for this. I personally can't really promise when I'll be able to do it.

Hi,
I totally agree with you about secondaryBackground color and seems it would be the best to go with. Below are examples with secondaryBackground color for that case in all four pallets. If all of them are looking fine then I will go ahead and create a PR.
Latte

Frappe

Macchiato

Mocha

I think that's fine for the time being! A PR would be greatly appreciated.

authors: darkenmay sgoudham

repo: catppuccin/jetbrains


text:
Dark theme elements showing up on frappe

With the latest update and latte, I'm seeing some bits where dark themes are sneaking through such as

and

Not sure if this is user error on my part, because I just need to wait for either spicetify or this repo to get some time to make changes, or perhaps a bug that is worth raising. Perhaps premature, but I'm raising it here just in case.

Im gonna need more info, such as spicetify config, marketplace installed tab, when you last installed/updated, etc

wow, yes, very much user error on my part. I installed maybe 6 months ago? For whatever reason I didn't use the marketplace theme and installed some other way so probably whenever I've been updating I wasn't actually updating catppuccin-spicetify. When I went to the marketplace themes tab, saw that nothing was installed, installed catpuccin and everything is lovely.
Thanks and sorry for the false alarm

wow, yes, very much user error on my part. I installed maybe 6 months ago? For whatever reason I didn't use the marketplace theme and installed some other way so probably whenever I've been updating I wasn't actually updating catppuccin-spicetify. When I went to the marketplace themes tab, saw that nothing was installed, installed catpuccin and everything is lovely.
Thanks and sorry for the false alarm

Glad you got it fixed! Simple mistake to make aha

authors: ohitstom paul-brenner

repo: catppuccin/spicetify


text:
feat(OpenMediaVault): init

🎉 Theme for OpenMediaVault 🎉
OpenMediaVault is the next generation network attached storage (NAS) solution based on Debian Linux.
💬 Additional Comments 💬
This doesn't theme the website, but rather the dashboard a user has once they have set up OpenMediaVault.
Latte was a bit difficult to get up and running, and I don't particularly enjoy it, but it's usable.
🗒 Checklist 🗒

[x] I have read and followed Catppuccin's submission guidelines.
[x] I have made a new directory underneath /styles/<name-of-website> containing the contents of the /template directory.

[x] I have ensured that the new directory is in lower-kebab-case.
[x] I have followed the template and kept the preprocessor as LESS.

[x] I have made sure to update the
userstyles.yml
file with information about the new userstyle.
[x] I have included the following files:

catppuccin.user.css - all the CSS for the userstyle, based on the
template.
assets/mocha.webp, assets/macchiato.webp, assets/frappe.webp and
assets/latte.webp - individual screenshots of the themed website, in all 4
Catppuccin flavors.
catwalk.webp - image of all individual screenshots stitched together,
generated via catwalk.

LGTM.

authors: Gandalf-the-Blue isabelroses

repo: catppuccin/userstyles


text:
Target missmatch when using "WASM_PACK_PROFILE"

Summary:  not looking for target/wasm/debug when build with dev profile.
Version:  1.2.13
Reproduce steps:

Build with dev profile, "WASM_PACK_PROFILE=dev parcel index.html"
wasm-pack successfully build with dev -> produced target/wasm/debug
Receive the error not able to find target/wasm/release:

🚨  project/crate/Cargo.toml: ENOENT: no such file or directory, open 'project/crate/target/wasm32-unknown-unknown/release/rust_parcel.d'
Error: ENOENT: no such file or directory, open 'project/crate/target/wasm32-unknown-unknown/release/rust_parcel.d'

Sorry to bother you again. It seems that although the plugin trigger wasm-pack to build with the correct profile, it still watches for compilation target with release profile.

After some investigation, I found that if build with wasm-pack release first, dev mode will work after hot-reloading.
However, if one try to build with dev profile without a release built, it will trigger the above error.

Thanks for this report.

Should be fixed in version 1.2.14

Thx, it worked without existing release build now.

authors: catsigma extraymond


text:
Build:1.5.0

Motivation and Context

Making a release to use the new RequestExtras change in other projects
Implementation Description

Any new dependencies Introduced

How Has This Been Tested?

PR Checklist:

[x] I have implemented all requirements? (see JIRA, project documentation).
[x] I am not affecting someone else's work, If I am, they are included as a reviewer.
[ ] I have added relevant tests (unit, integration or regression).
[ ] I have added comments to all the bits that are hard to follow.
[ ] I have added/updated Documentation.
[ ] I have updated the appropriate changelog with a line for my changes.

Screenshots (if appropriate):

On hold until https://github.com/causalens/dara-ui/pull/55 is released, will update and merge once a new dara-ui patch is available

repo: causalens/dara


text:
🛑 Artfos ERP is down

In ac80d07, Artfos ERP (https://intranet.artfos.com.ar/equipo/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Artfos ERP is back up in 7aa82ee.

repo: cavalicenti/upptime


text:
chore: bdd-gh-1590203638 to 0.0.1

chore: Promote bdd-gh-1590203638 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
Increase database size in resize_db test

This test crashes with an out-of-space error on my machine, so I bumped the database size, which fixes it.

Closing, since this commit was in the other PR that I merged

authors: casey cberner

repo: cberner/redb


text:
TestNG 7.0.0 with scala 2.12.8

TestNG Version

Note: only the latest version is supported

I've just upgraded my testNG project from scala 2.11.11 to 2.12.8 with testNG 7.0.0.
I have a case of @test method in a class A that implements trait B that implements trait C and both B+C have @beforemethod methods. Before the upgrade the @beforemethod methods order was C->B->A as expected
Actual behavior
After the upgrade when i execute the test the order of the @beforetest methods is now mixed and executed twice
Is the issue reproductible on runner?

[ ] Shell
[ ] Maven
[ ] Gradle
[ ] Ant
[ ] Eclipse
[x] IntelliJ
[ ] NetBeans

Test case sample

Please, share the test case (as small as possible) which shows the issue

BTW, it works just fine with testNG 6.14.3. Seems like the issue is with 7.0.0

@alexfel - Do you have a sample that can be used to simulate this issue? I am not that familiar with scala, so please feel free to add any extra information that can be used (how you are running your test etc.,)

@alexfel - Do you have a sample that can be used to simulate this issue? I am not that familiar with scala, so please feel free to add any extra information that can be used (how you are running your test etc.,)

Hi,
Thanks for your response.
So I’m basically having SBT Scala project within IntelliJ and just upgraded to Scala 2.12.8 from 2.11.11 and using testNG 6.14.3. (sbt.version=1.0.4)
I have a class A with @test method a1 that extends class B where class B extends/implement traits C and D that both extends base class E. C,D and E has @beforeMethod methods. When I try to update to testNG 7.0.0 and test a1 is executed - the @beforeMethods methods execution order is unexpected and even more, executed twice :/
Please assist

@alexfel Could you tell us if the issue comes from your scala 2.11 -> 2.12 upgrade or your testng 6.14 -> 7.0 upgrade?
It looks like the behavior you describe is similar than https://github.com/cbeust/testng/issues/2209

Closing this issue. Please check if the problem is persistent with the latest released TestNG version (7.5). If the problem persists, please share a sample that can be used to reproduce the problem.

authors: alexfel juherr krmahadevan

repo: cbeust/testng


text:
Parallel classes seems to be ignored when using groups.

So i have two tests classes and pom.xml
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <version>2.19.1</version>
    <configuration>
        <parallel>classes</parallel>
        <threadCount>30</threadCount>
        <perCoreThreadCount>false</perCoreThreadCount>
        <excludes>
            <exclude>${exclude.tests}</exclude>
        </excludes>
    </configuration>
</plugin>

which i run with
mvn clean test -Dgroups=smoke
and i get 5 threads with 4 test methods from 1st class and 1 test method from 2nd class launched concurrently, however i expect 2 test methods from different classes to be ran concurrently.
If i don't specify  -Dgroups=smoke, everything is fine and acts as expected: 2 test methods from different classes are launched.
Alternatively I have a suite
<suite name="My suite" parallel="classes" thread-count="30">
    <test name="test1">
        <groups>
            <run>
                <include name="smoke"/>
            </run>
        </groups>
        <classes>
            <class name="com.spredfast.qa.mobileauto.ios.tests.publishing.general.TestPublishMessageIOS"/>
            <class name="com.spredfast.qa.mobileauto.ios.tests.TestLoginIOS"/>
        </classes>
    </test>
</suite>

and running this suite also results in 5 threads with 4 test methods from 1st class and 1 test method from 2nd class launched. Expected result is the same: 2 test methods from different classes to be ran concurrently.
When I alter the suite as following:
<suite name="My suite" parallel="tests" thread-count="30">
    <test name="test1">
        <groups>
            <run>
                <include name="smoke"/>
            </run>
        </groups>
        <classes>
            <class name="com.spredfast.qa.mobileauto.ios.tests.TestLoginIOS"/>
        </classes>
    </test>
    <test name="test2">
        <groups>
            <run>
                <include name="smoke"/>
            </run>
        </groups>
        <classes>
            <class name="com.spredfast.qa.mobileauto.ios.tests.publishing.general.TestPublishMessageIOS"/>
        </classes>
    </test>
</suite>

the 2 test methods from different classes get launched and only test methods from the smoke group get executed.

Ok, thank, I understand now.

Any updates on this issue ?
I am facing the exact issue.
My SuiteXml File is something like this.

current stable testNg version I am using 6.14.3 and also tried on 6.9.10
Current Behaviour:
Getting few classes executed
Rest other classes gets skipped with NullPointerException

authors: ag22494 juherr sergejjkim


text:
Define Instance Variable

Redefine instance variable @profile_page_flower_list_dimensions

[Finished: #101718358]

:+1:

authors: eschlange michaelwehrley


text:
Return references instead of clones

Hey :wave:!
I saw that you wrote // FIXME perf in the sources and it seems that those are all related to cloning data. May I ask why the methods don't return references, allowing to the library's users to clone the returned data if wanted? :smiley:
Thank you :heart:!

Yes, it looks more flexible by allowing the user to clone the data if wanted. rust-protobuf offers various ways to access the data. There is an example.
It seems we could export the above methods.

Further discussion in #11


text:
Two-finger swipe for going between posts and subs is very hard to do

Since the update to gestures, anyway. I think this would be relatively straightforward to fix -- just require the two-finger swipe to fail for the 1-finger swipe to be recognized.

Unfortunately that does not fix it. There's another issue at play I believe

Oof ouch owie my project complexity

Actually I was doing it to the wrong views :P should be fixed in a sec

Not applicable anymore

authors: ccrama colejd

repo: ccrama/Slide-iOS


text:
feat: add test for controllers

make test for all controllers

Noice.
Gas lanjut ke middleware-nya, start dari middleware validation, dia gampang. Klo ada middlerwae sekiranya susah di test, di skip dulu middleware yg lain sampe 100%.

@alifaaziz coba pull dari main, ada dua function middleware yg gw buang

@alifaaziz coba pull dari main, ada dua function middleware yg gw buang

oke bang

authors: alifaaziz ccrsxx

repo: ccrsxx/plane-ticket-be


text:
喷嚏图卦的图片抓不到了

最近一段时间喷嚏图卦都抓不到图片了，就是这样的：
https://www.dapenti.com:99/dapenti/f57312f5/6275ee3c.jpg
浏览器直接打开又能看到图片，不知道哪里能看到抓取的日志。

The URL to be fetched can use any port number in the following ranges: 80-90, 440-450, 1024-65535. If the port is not mentioned in the URL, the port is implied by the scheme: http://... is port 80, https://... is port 443.
这个是GAE的端口限制，99处于这个端口范围之外，可能是因为这个原因导致抓不到图片吧
如果你有转发或反向代理，可以考虑用其他服务器转一道

3.0.0b已经发布，不再受限于GAE的资源限制，另外找VPS部署就好。
https://cdhigh.github.io/KindleEar/

repo: cdhigh/KindleEar


text:
control over image size?

It would be fantastic to be able to have some control over the size of the image. Something similar to row="1/3", like we have for cd-row would be great! This would be especially nice when there is a question with a lot of text in the answer, but a relatively unimportant graphic, or vice versa, where the graphic is detailed and important, and the answers are very small.

nod *

In the future, this will probably be rewritten to be a fair bit simple and expose more direct control over the HTML/Styling.
Keep the requests coming!

This is now possible using the .q-n-eh-picture class.

authors: iMcKelvie ivanreese

repo: cdig/q-n-eh


text:
chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2304

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 818

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2076

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2100

Questions ?
Please refer to the Backport tool documentation


text:
AttributeError: module 'torch._utils' has no attribute '_rebuild_parameter'

while implementing the line below in Jupyter notebook,
cdqa_pipeline = QAPipeline(reader='./models/bert_qa_vCPU-sklearn.joblib')
cdqa_pipeline.fit_retriever(X=df)
i get the following error:
module 'torch._utils' has no attribute '_rebuild_parameter'

Are you using the last versions of cdqa, pytorch and sklearn?
I just ran this code in local and on a Colab notebook (https://colab.research.google.com/github/cdqa-suite/cdQA/blob/master/examples/tutorial-first-steps-cdqa.ipynb) and I wasn't able to replicate this error...

The error got resolved. i actually was using older version of pytorch. so i updated it.
The problem actually got resolved by updation alone, but it was still showing the error because i hadnt restarted my Jupyter Notebook.
thanks for help

authors: andrelmfarias bhupensinghpanwar

repo: cdqa-suite/cdQA


text:
./code-server doesn't working on gcp vm

Issue description

I have installed code-server on vm of gcp

cd code-server1.1156-vsc1.33.1-linux-x64

./code-server

doesn't work...

I think it's related with port, so have got a setting VPC network > fire wall regulation
for http-8443 following the code-server/doc/admin/install/google_cloud.md
anyone help me? ;)

Related Issues

@WilliamNAM I have it running on GCP.
When you say doesn't work... what do you mean specifically?
Did you set up ports as described?
When you start ./code-server, what happens? Can you provide a log?

@WilliamNAM I have it running on GCP.
When you say doesn't work... what do you mean specifically?
Did you set up ports as described?
When you start ./code-server, what happens? Can you provide a log?

first of all, thax for your reply~ ;)
I have get a solving the issue because I didn't add a network tag!
Have use  with sudo ./code-server .. -p 8443 command~
Thanx!

authors: WilliamNAM lfx

repo: cdr/code-server


text:
setting old permissions back

Summary | Résumé
Reverting account linking IAM in NR to the original since we seem to have lost the lambda
Test instructions | Instructions pour tester la modification
TF Apply
See if api-lambda for staging exists.
Release Instructions | Instructions pour le déploiement
None.
Reviewer checklist | Liste de vérification du réviseur

[ ] This PR does not break existing functionality.
[ ] This PR does not violate GCNotify's privacy policies.
[ ] This PR does not raise new security concerns. Refer to our GC Notify Risk Register document on our Google drive.
[ ] This PR does not significantly alter performance.
[ ] Additional required documentation resulting of these changes is covered (such as the README, setup instructions, a related ADR or the technical documentation).

⚠ If boxes cannot be checked off before merging the PR, they should be moved to the "Release Instructions" section with appropriate steps required to verify before release. For example, changes to celery code may require tests on staging to verify that performance has not been affected.

it's the case of the disappearing entity.

repo: cds-snc/notification-terraform


text:
🛑 tanecni-divadlo.cz is down

In 781b48b, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in edf58eb.

repo: cebreus/upptime


text:
🛑 tanecni-divadlo.cz is down

In 6f2f1f5, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 84a8255.


text:
🛑 tanecni-divadlo.cz is down

In 0d6c54c, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in c27bcfc.


text:
🛑 tanecni-divadlo.cz is down

In 1e0b11f, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 9bd0f0e after 474 days, 14 hours, 52 minutes.


text:
🛑 tanecni-divadlo.cz is down

In 2919934, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 67a4e87.


text:
🛑 tanecni-divadlo.cz is down

In 5e3c98e, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 502
Response time: 20839 ms

Resolved: tanecni-divadlo.cz is back up in a9ff6e0.


text:
🛑 tanecni-divadlo.cz is down

In a09e5da, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in c8c142e.


text:
🛑 tanecni-divadlo.cz is down

In 989dc2d, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 17e62db.


text:
🛑 tanecni-divadlo.cz is down

In a0b8ff4, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 602b85a.


text:
🛑 tanecni-divadlo.cz is down

In 1aca200, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 9ae56a2.


text:
🛑 tanecni-divadlo.cz is down

In 81523fe, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 16a837f.


text:
🛑 tanecni-divadlo.cz is down

In a193133, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in f970ded.


text:
🛑 CDN is down

In 89d6cdd, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 522
Response time: 15310 ms

Resolved: CDN is back up in e39aa05.

repo: ceccun/status


text:
🛑 CDN is down

In e202e5b, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 522
Response time: 15704 ms

Resolved: CDN is back up in 0aa0933.


text:
🛑 CDN is down

In 1070861, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 502
Response time: 636 ms

Resolved: CDN is back up in 6a1a647.


text:
🛑 CDN is down

In 3fe64bf, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 522
Response time: 15282 ms

Resolved: CDN is back up in 1e2b13c.


text:
🛑 CDN is down

In 47675a2, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 525
Response time: 291 ms

Resolved: CDN is back up in eb87014 after 787 days, 2 hours, 11 minutes.


text:
🛑 CDN is down

In e0e7152, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 525
Response time: 270 ms

Resolved: CDN is back up in de1a6cb after 27 minutes.


text:
Tasks before the next merge from dev  to main

General Tasks
Tasks we need to do to merge the dev branch into main:

[ ] Nils: Fix incorrect placement or size of tiles that's causing lines to appear between tiles on the map (already done by Matthias)

Do not merge mouse interactions made by Matthias into main, they can stay on a separate branch until after delivery

[x] Cecilia: Separate rendering code that's currently on Rendering.cpp onto multiple files: Rendering.cpp,  Rendering_Math.cpp, Rendering_Text.cpp
[x] All: All rendering code needs to be doc commented and internally commented, see issue #83 as well, and update that one when this is completed
[x] Nils and Eimen: Memory leak in stylesheet
[x] Cecilia: Merge Rafael's work into unit test branch, then merge the unit test branch into dev, check that all tests still work, and finally pull into main

Individual Commenting
Commenting of files. Update doc comments to QDoc:

[x] Nils: Utilities.cpp and Utilities.h
[x] Cecilia: Layerstyle.cpp and TileCoord.h
[x] Eimen: Update Evaluator.cpp and VectorTiles.cpp

I am about to merge a large set of changes in to dev. These changes are just sorting out the project header include sections, so all of the functionality should remain the same. Let me know if something got lost on the way here.

[ ] Fix memory leaks
[ ] Fix top level world map not being rendered #94

repo: cecilianor/Qt-thesis


text:
Update git2_credentials

It now handle ~/.ssh/id_rsa

Waiting release 0.5.0 of git2_credentials that will include this change https://github.com/davidB/git2_credentials/issues/9

repo: cecton/cargo-git


text:
Change constructors

Just a warning today, might be an issue in the future, as per a PHP warning message, methods with the same name as their class will not be constructors in a future version of PHP; there are a bunch of these here and there, and they should probably be converted to __construct instead.
Keep it up!

Good idea, @andreg! Would you be interested in submitting a PR for this?

Absolutely!

Fixed in #59

authors: andreg bradyvercher


text:
chore(main): release 1.0.1

:robot: I have created a release beep boop
1.0.1 (2024-01-02)
Miscellaneous Chores

Add license (#2) (f624f71)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/cedricziel/mattermost-php/releases/tag/v1.0.1 :sunflower:

repo: cedricziel/mattermost-php


text:
Issue logging in to hosts management

I'm having issues logging in to host management with the default user and password, the page simply refreshes on page submission.

Issue fixed on 2.9.1.0, was using older version.

repo: cedrozor/myrtille


text:
dll's and exe's are not included in source file

Dear All,
I am using this source code.
But below listed dlls are missing form the setup project.
freerdp-client.dll
freerdp.dll
libeay32.dll
ssleay32.dll
wfreerdp.exe
winpr-tools.dll
winpr.dll
Please let me know if i am searching on wrong place.
Thank you.

Hi,
Assemblies are never commited along with source code. You have to install OpenSSL and build FreeRDP (https://github.com/cedrozor/FreeRDP) as described into the documentation.
You can also use the installer (https://github.com/cedrozor/myrtille/releases/download/v1.4.0/Myrtille_1.4.0_x86_x64_Setup.exe), which contains and installs pre-compiled DLLs and EXEs.
Regards,
Cedric

authors: cedrozor mdsajidfaizan


text:
ADR: DAS node-types aka partial nodes

Summary
Similar to the ADR for the DAS light-client, we should describe the modifications required for other DAS node-types.
Details
Some aspects are better described in separate focused ADRs. See:

Block Propagation
Block Sync
Fast Sync

Everything else that isn't already covered by these other ADRs, should still be captured in the ADR this issue is about. Including added command-line flags and config options. Non-exhaustive list of these:

boolean flag: full-body or partial body (maybe with more descriptive names)
for "partial-body": how much data / how many samples (in total?, per block?)

Other implications, like the inability to serve full block via RPC (related: #189, #195)

Thanks, @adlerjohn. I updated the title and the description. As discussed on a sync call this was coming from the perspective on how to modify the existing tendermint fullnodes and prep for DAS. My understanding (also from discussions with @musalbas e.g. here and on calls) was that this should be the immediate next priority. It is debatable if partial nodes need to "participate in consensus" (meaning running the consensus reactor that deals with these messages and basically also running the same code as validators without actively signing messages).
Here is a full overview of the reactors a regular tendermint fullnode runs: https://github.com/tendermint/tendermint/blob/de5cf42ed5ab19d93a4da48b33454f32c1c899d6/docs/architecture/adr-052-tendermint-mode.md#decision
Some of the modes (node-types) in the above ADR should also end up in the specs. Or at least their relation to our node-types IMO. I'll open an issue about this in the specs repo shortly.

closing this in favour of https://github.com/celestiaorg/lazyledger-core/issues/435

repo: celestiaorg/lazyledger-core


text:
Contract should work even with malicious relayer

Confirm that the contract is secure even if the relayer is malicious. Specifically, the relayer can duplicate and re-order signatures, but cannot change the list of validators (since that's committed to in an ordered Merkle tree).

While the relayer can duplicate and re-order signature, they can't manipulate the list of validators. This list is compared against when iterating over signatures, so a malicious relayer cannot successfully duplicate signatures.

repo: celestiaorg/quantum-gravity-bridge


text:
Gossip Fraud Proofs to P2P network after generation when needed

Overview
Gossip generated Fraud Proofs to P2P network
Closes: #552

Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

Follow up issue: #693

Codecov Report

Merging #643 (e496fc0) into main (d8679cc) will increase coverage by 0.41%.
The diff coverage is 36.76%.

@@            Coverage Diff             @@
##             main     #643      +/-   ##
==========================================
+ Coverage   54.49%   54.91%   +0.41%
==========================================
  Files          49       49
  Lines       10305     9794     -511
==========================================
- Hits         5616     5378     -238
+ Misses       3820     3607     -213
+ Partials      869      809      -60

Impacted Files
Coverage Δ

types/pb/rollmint/rollmint.pb.go
40.53% <ø> (+0.51%)
:arrow_up:

types/serialization.go
67.42% <ø> (-2.52%)
:arrow_down:

state/executor.go
65.54% <25.00%> (-3.64%)
:arrow_down:

block/manager.go
62.52% <33.33%> (-3.56%)
:arrow_down:

node/node.go
58.26% <44.44%> (-2.34%)
:arrow_down:

mocks/Application.go
35.00% <0.00%> (-4.38%)
:arrow_down:

rpc/json/ws.go
61.90% <0.00%> (+7.93%)
:arrow_up:

... and 1 more

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

authors: Manav-Aggarwal codecov-commenter

repo: celestiaorg/rollmint


text:
chore: bump versions to latest main for node and app v0.12.0-rc2

Overview

Add upd/quic-v1 to listenAddr for node's config
node latest main that contains v0.12.0-rc2 app
bumped forks of app/sdk

Ref: https://github.com/celestiaorg/celestia-node/issues/1623

Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Tested against #89 in the following experimental/deletable branch and everything works fine 👍🏻
:shipit:

repo: celestiaorg/test-infra


text:
Hyperverse Integration

Integrate Hyperverse to give smart module access to developers.

Nice suggestion; great to have on Celo Sage or Celo Examples, not on Celo Composer.
Closing issue.

authors: joenyzio nestorbonilla

repo: celo-org/celo-composer


text:
Docs: Decouple Typedoc generated docs and start new repo

Decrease engineering time to debugging Gitbook and auto-generated documentation
Definition of Done

[x]  Users can access auto-generated documents
[ ]  New docs repo is setup

weekly updates: set up the auto generated documents for all the new sdk packages, and generalized the existing script so that it can be used for any future package

repo: celo-org/celo-monorepo


text:
feat: bandwidth of attribute; resolve #69

close #69

Pull Request Test Coverage Report for Build 9078326496
Details

0 of 0   changed or added relevant lines in 0 files are covered.
28 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-1.1%) to 86.063%

Files with Coverage Reduction
New Missed Lines
%

results/multi_cpt_results.py
28
85.35%

Totals

Change from base Build 8924698846:
-1.1%

Covered Lines:
1303

Relevant Lines:
1514

💛  - Coveralls

authors: RDWimmers coveralls

repo: cemsbv/py-pilecore


text:
new hello script pull request

nice

Good

authors: cengique eMartn

license: Unlicense


text:
thirft unreachable

Please answer these questions before submitting a bug report.
What version of OpenCensus are you using?
go.opencensus.io v0.22.0
What version of Go are you using?
go 1.12
What did you do?
If possible, provide a recipe for reproducing the error.
go get -u github.com/opencensus-go
What did you expect to see?
successful go get
What did you see instead?
go: git.apache.org/thrift.git@v0.0.0-20180902110319-2566ecd5d999: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /home/foo/projekts/pkg/mod/cache/vcs/83dba939f95a790e497d565fc4418400145a1a514f955fa052f662d56e920c3e: exit status 128:
        fatal: unable to access 'https://git.apache.org/thrift.git/': Failed to connect to git.apache.org port 443: Connection timed out

Additional context
Add any other context about the problem here.

http://git.apache.org/ is downed...
but go get -u go.opencensus.io is fine.
I'm having trouble with the same problem but I don't know where the package came from...

We have same issue.
In our case, the cause was the https://github.com/opencensus-integrations/gomongowrapper repository.

Hello guys
Our all deployments are stucked by unavailable apache.org/thrift packet...  Now we can not make a build..

Note the documentation https://thrift.apache.org/lib/go tells you to get it from github.com/apache/thrift/lib/go/thrift

Apparently a redirect was added per https://issues.apache.org/jira/browse/THRIFT-4542?focusedCommentId=16428186&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16428186
But that doesn't fix the issue for Docker builds. The https://github.com/jenkins-x/jx/pull/3321/files fix seems to be the way to go if you're trying to build with Docker.
Adding replace git.apache.org/thrift.git => github.com/apache/thrift v0.0.0-20180902110319-2566ecd5d999  to go.mod fixed it for me.

Doing the replace git.apache.org/thrift.git => ... seems to only work if you don't have any other dependencies not referring to github.com/apache/thrift the proper way.  I get the error github.com/apache/thrift@v0.0.0-20180411174621-858809fad01d used for two different module paths (git.apache.org/thrift.git and github.com/apache/thrift).

The replace
replace git.apache.org/thrift.git => github.com/apache/thrift v0.0.0-20191002171323-e53d23c16c80

worked for me on go 1.12.7 but as of go1.13 I get this:
go: google.golang.org/api@v0.1.0 requires
        go.opencensus.io@v0.18.0 requires
        github.com/apache/thrift@v0.0.0-20191002171323-e53d23c16c80: invalid pseudo-version: does not match version-control timestamp (2019-02-10T18:11:46Z)

how can I generate the version for go.mod?

After fixing the timestamp to the following:
replace git.apache.org/thrift.git => github.com/apache/thrift v0.0.0-20190210181146-e53d23c16c80

I get
go: github.com/apache/thrift@v0.0.0-20190210181146-e53d23c16c80 used for two different module paths (git.apache.org/thrift.git and github.com/apache/thrift)

Apparently a redirect was added

That was over a year ago. Apparently it has now gone away.

In my case updating go.opencensus.io and cloud.google.com/go to certain versions (or newer) resolves this issue.
If you use go modules (have go.mod and go.sum),
go get -u go.opencensus.io@v0.20.1 cloud.google.com/go@v0.37.3
go mod tidy

What modules you need to update may varies. The key is finding which modules depend on git.apache.org/thrift.git. I couldn't find out a magical way to do this task, so stick following steps.

go mod tidy to remove noise from go.mod
go mod graph | grep " <module>[@version]" to know which modules are depend on certain module (and version if needed) until your main module.
googling module's github url and blaming prior change of the line of dependency in go.mod.

authors: bboreham hiroshi keitwb magicalbanana muratsplat pmalekn ryoya-fujimoto tmartinez-carecloud vvakame

repo: census-instrumentation/opencensus-go


text:
exporter/prometheus: implement one

Assigned to me by @rakyll, this issue is a placeholder for that exporter.

Thanks for this tracking bug!
I was explaining the other day what the API may look like:
package prometheus

type Exporter struct {} ...

func (e *Exporter) Handler() http.Handler {}

@rakyll I am going to close this issue since the  first version of the exporter was implemented. Any bugs that we find can be independently reported.

authors: odeke-em rakyll