text:
ferineness, dentately

This pull request was generated by the 'mq' tool

/trunk merge


text:
diastrophy, aspy

This pull request was generated by the 'mq' tool

/trunk merge

source: gharchive/pull-request

repo: trunk-io/mergequeue

license: MIT

license_type: permissive

license_source: github-api


text:
fibrobronchitis, dorsoapical

This pull request was generated by the 'mq' tool

/trunk merge


text:
autofluorescence, banago

This pull request was generated by the 'mq' tool

/trunk merge


text:
aesculapian, forkful

This pull request was generated by the 'mq' tool

/trunk merge


text:
epitaxial, alights

This pull request was generated by the 'mq' tool

/trunk merge


text:
gonal, forfeiture

This pull request was generated by the 'mq' tool

/trunk merge


text:
analogia, chuffed

This pull request was generated by the 'mq' tool

/trunk merge


text:
euthycomic, formalins

This pull request was generated by the 'mq' tool

/trunk merge


text:
forevouched, chemicking

This pull request was generated by the 'mq' tool

/trunk merge


text:
dryest, bizet

This pull request was generated by the 'mq' tool

/trunk merge


text:
cystogenous, diversifiability

This pull request was generated by the 'mq' tool

/trunk merge


text:
gutterblood, cresotic

This pull request was generated by the 'mq' tool

/trunk merge


text:
antiromanticism, bondmaid

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

/trunk merge


text:
embryomas

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

/trunk merge


text:
experimentalize, consummately

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

/trunk merge


text:
dipnoid, bullfighter

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

/trunk merge


text:
gymnolaema

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

/trunk merge


text:
gigadoid, doebird

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

/trunk merge


text:
ghillie, dinglebird

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

/trunk merge


text:
fumitories

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

/trunk merge


text:
gabarit, excubant

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

/trunk merge


text:
columboid, antityrosinase

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

/trunk merge


text:
gemmative, andropogon

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

/trunk merge


text:
bletia, forehandsel

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

/trunk merge


text:
epaulet, blanche

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

/trunk merge


text:
formalize, buttressing

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

/trunk merge


text:
cave, bilateral

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

/trunk merge


text:
Use a variable to define expiration blocks similar to transition and noncurrent_version_transition is done.

In #220 I didn't realize you couldn't set date or days and also set expired_object_delete_marker. I could change the code to do something fancy with expiration_days variable I introduced or I could simplify the logic to work like the other lifecycle policy blocks. I've chosen the latter and set the default to be what it always was, meaning a no-op for users.
From the TF Docs:

expired_object_delete_marker (Optional) On a versioned bucket (versioning-enabled or versioning-suspended bucket), you can add this element in the lifecycle configuration to direct Amazon S3 to delete expired object delete markers. This cannot be specified with Days or Date in a Lifecycle Expiration Policy.

@dynamike - Could I get a review on this? I think it solves a good problem but I'd also like to know your thoughts on it.

Sorry, I missed the ping. Can you pop an example usage in examples/? We can turn that into a terratest. This will help me grok the problem you're trying to solve and ensure it works as expected.

@dynamike - Could I get a review on this? I think it solves a good problem but I'd also like to know your thoughts on it.

I have added an example for you to look at with some notes about how it works.
I'm also using the latest terraform-docs at v0.12.1 and it auto-updated the readme. I can back those out if you want or you can roll forward, just let me know.

we can leave it in and I can follow up with the test and tf-docs update

authors: chrisgilmerproj dynamike


text:
feat(sdk): Update error handling when requesting credential from issuer

Added an error code that gets returned if credential parsing (a significant operation) fails.
Updated a potentially misleading error message that gets returned if a user PIN is not set.
Added a nil check to the request credential methods to ensure that they don't panic if the SDK user fails to pass in the options object. If not set, the method defaults to an empty object (PIN will be empty).
Updated documentation.

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.11 :tada:

Comparison is base (755beff) 90.33% compared to head (1fb6959) 90.45%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #327      +/-   ##
==========================================
+ Coverage   90.33%   90.45%   +0.11%
==========================================
  Files          55       55
  Lines        2422     2431       +9
==========================================
+ Hits         2188     2199      +11
+ Misses        160      159       -1
+ Partials       74       73       -1

Impacted Files
Coverage Δ

cmd/wallet-sdk-gomobile/openid4ci/interaction.go
78.18% <100.00%> (+4.59%)
:arrow_up:

pkg/openid4ci/openid4ci.go
90.19% <100.00%> (+0.19%)
:arrow_up:

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

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

repo: trustbloc/wallet-sdk


text:
[Tools] Kotlin API codegen

Description
Add a script for generation of KDoc Kotlin documentation using Dokka tool. Solves #2217.
How to test
Manually
Types of changes

New feature (non-breaking change which adds functionality)

Checklist

[X] Create pull request as draft initially, unless its complete.
[X] Add tests to cover changes as needed.
[X] Update documentation as needed.
[X] If there is a related Issue, mention it in the description.

Left to do: modify release scripts if needed

Some screenshots would be nice, is there a way we can easily host it on web?

Some screenshots would be nice, is there a way we can easily host it on web?

It generates an archive which inside contains an index.html, screenshot/video coming

https://user-images.githubusercontent.com/3388747/197799186-6ad22ba7-142e-4cdb-be83-aab85147a1ad.mov

Is it ready for review @miloserdow ?

Is it ready for review @miloserdow ?

Yeah, forgot to set it

authors: Milerius hewigovens miloserdow

repo: trustwallet/wallet-core


text:
Support: Use your own OpenAI API key?

Hi there,
Thanks for building Pear! I'm loving it so far. I had a question around using my own API key / models. On the pricing page the Free tier says:

Use our free trial, your own API key, or local models.

I can't find anywhere to seemingly set up my own OpenAI key or anything. I see the models outlined in ~/.pearai/config, but not sure how to set up a custom provider. I saw in the documentation for Tab Autocomplete you can drop in your own Codestral key. Is that what Intern tier is referring to? Or is there some other place where this can be set up?

Thanks for your time! - Rob

Add Model -> Other Model -> Go from there

@RobErskine

@cqdev-co Ack ok, can't believe i missed that. Thank you.

Sorry for bothering the thread,  @cqdev-co , I'm not able to find the space in the Image you've showed.
Is it from VSCode settings ?

Oh shoot!, I found it in the PearAI chat window.

source: gharchive/issue

authors: RobErskine akashp1712 cqdev-co

repo: trypear/pearai-app


text:
feat: convert circuit json to dsn

This circuit json was converted to the bottom pcb json shared which is very close to the og pcb json
Circuit Json
[
  {
    "type": "pcb_smtpad",
    "pcb_smtpad_id": "RoundRect[T]Pad_540x640_135.514_um_0.000000_0_1",
    "pcb_component_id": "Resistor_SMD:R_0402_1005Metric",
    "pcb_port_id": "RoundRect[T]Pad_540x640_135.514_um_0.000000_0_1",
    "shape": "rect",
    "x": 149.48,
    "y": 105,
    "width": 0.54,
    "height": 0.64,
    "layer": "top",
    "port_hints": [
      "1"
    ]
  },
  {
    "type": "pcb_smtpad",
    "pcb_smtpad_id": "RoundRect[T]Pad_540x640_135.514_um_0.000000_0_2",
    "pcb_component_id": "Resistor_SMD:R_0402_1005Metric",
    "pcb_port_id": "RoundRect[T]Pad_540x640_135.514_um_0.000000_0_2",
    "shape": "rect",
    "x": 150.5,
    "y": 105,
    "width": 0.54,
    "height": 0.64,
    "layer": "top",
    "port_hints": [
      "2"
    ]
  },
  {
    "type": "pcb_smtpad",
    "pcb_smtpad_id": "RoundRect[T]Pad_900x950_225.856_um_0.000000_0_1",
    "pcb_component_id": "Capacitor_SMD:C_0603_1608Metric",
    "pcb_port_id": "RoundRect[T]Pad_900x950_225.856_um_0.000000_0_1",
    "shape": "rect",
    "x": 154.245,
    "y": 105,
    "width": 0.9,
    "height": 0.95,
    "layer": "top",
    "port_hints": [
      "1"
    ]
  },
  {
    "type": "pcb_smtpad",
    "pcb_smtpad_id": "RoundRect[T]Pad_900x950_225.856_um_0.000000_0_2",
    "pcb_component_id": "Capacitor_SMD:C_0603_1608Metric",
    "pcb_port_id": "RoundRect[T]Pad_900x950_225.856_um_0.000000_0_2",
    "shape": "rect",
    "x": 155.795,
    "y": 105,
    "width": 0.9,
    "height": 0.95,
    "layer": "top",
    "port_hints": [
      "2"
    ]
  },
  {
    "type": "pcb_trace",
    "pcb_trace_id": "bff2dc94-ce6d-46ea-b3f3-c4d4a34a12f0",
    "source_trace_id": "Net-(C1-Pad1)",
    "route_thickness_mode": "constant",
    "should_round_corners": false,
    "route": [
      {
        "route_type": "wire",
        "x": 150.5,
        "y": 105,
        "width": 0.2,
        "layer": "top"
      },
      {
        "route_type": "wire",
        "x": 154.54,
        "y": 105,
        "width": 0.2,
        "layer": "top"
      }
    ]
  },
  {
    "type": "pcb_board",
    "pcb_board_id": "4db82917-cd24-45fb-bd07-830ca5b5db42",
    "outline": [
      {
        "x": 158,
        "y": 108
      },
      {
        "x": 147.5,
        "y": 108
      },
      {
        "x": 147.5,
        "y": 102
      },
      {
        "x": 158,
        "y": 102
      },
      {
        "x": 158,
        "y": 108
      }
    ]
  }
]

Pcb Json
{
  "filename": "",
  "parser": {
    "string_quote": "",
    "host_version": "",
    "space_in_quoted_tokens": "",
    "host_cad": ""
  },
  "resolution": {
    "unit": "um",
    "value": 10
  },
  "unit": "um",
  "structure": {
    "layers": [
      {
        "name": "F.Cu",
        "type": "signal",
        "property": {
          "index": 0
        }
      },
      {
        "name": "B.Cu",
        "type": "signal",
        "property": {
          "index": 1
        }
      }
    ],
    "boundary": {
      "path": {
        "layer": "pcb",
        "width": 0,
        "coordinates": [
          158000,
          -108000,
          147500,
          -108000,
          147500,
          -102000,
          158000,
          -102000,
          158000,
          -108000
        ]
      }
    },
    "via": "Via[0-1]_600:300_um",
    "rule": {
      "clearances": [
        {
          "value": 200
        },
        {
          "value": 200,
          "type": "default_smd"
        },
        {
          "value": 50,
          "type": "smd_smd"
        }
      ],
      "width": 200
    }
  },
  "placement": {
    "components": [
      {
        "name": "Resistor_SMD:R_0402_1005Metric",
        "place": {
          "refdes": "Resistor_SMD:R_0402_1005Metric",
          "PN": "Resistor_SMD:R_0402_1005Metric",
          "x": 149990,
          "y": -105000,
          "side": "front",
          "rotation": 0
        }
      },
      {
        "name": "Capacitor_SMD:C_0603_1608Metric",
        "place": {
          "refdes": "Capacitor_SMD:C_0603_1608Metric",
          "PN": "Capacitor_SMD:C_0603_1608Metric",
          "x": 155020,
          "y": -105000,
          "side": "front",
          "rotation": 0
        }
      }
    ]
  },
  "library": {
    "images": [
      {
        "name": "Resistor_SMD:R_0402_1005Metric",
        "outlines": [],
        "pins": [
          {
            "padstack_name": "RoundRect[T]Pad_540x640_135.514_um_0.000000_0",
            "pin_number": 1,
            "x": -510,
            "y": 0
          },
          {
            "padstack_name": "RoundRect[T]Pad_540x640_135.514_um_0.000000_0",
            "pin_number": 2,
            "x": 510,
            "y": 0
          }
        ]
      },
      {
        "name": "Capacitor_SMD:C_0603_1608Metric",
        "outlines": [],
        "pins": [
          {
            "padstack_name": "RoundRect[T]Pad_900x950_225.856_um_0.000000_0",
            "pin_number": 1,
            "x": -775,
            "y": 0
          },
          {
            "padstack_name": "RoundRect[T]Pad_900x950_225.856_um_0.000000_0",
            "pin_number": 2,
            "x": 775,
            "y": 0
          }
        ]
      }
    ],
    "padstacks": [
      {
        "name": "RoundRect[T]Pad_540x640_135.514_um_0.000000_0",
        "shapes": [
          {
            "shapeType": "polygon",
            "layer": "F.Cu",
            "width": 0,
            "coordinates": [
              -270,
              320,
              270,
              320,
              270,
              -320,
              -270,
              -320,
              -270,
              320
            ]
          }
        ],
        "attach": "off"
      },
      {
        "name": "RoundRect[T]Pad_900x950_225.856_um_0.000000_0",
        "shapes": [
          {
            "shapeType": "polygon",
            "layer": "F.Cu",
            "width": 0,
            "coordinates": [
              -450,
              475,
              450,
              475,
              450,
              -475,
              -450,
              -475,
              -450,
              475
            ]
          }
        ],
        "attach": "off"
      }
    ]
  },
  "network": {
    "nets": [
      {
        "name": "Net-(C1-Pad1)",
        "pins": [
          "Resistor_SMD:R_0402_1005Metric-2"
        ]
      }
    ],
    "classes": [
      {
        "name": "kicad_default",
        "description": "",
        "net_names": [
          "Net-(C1-Pad1)"
        ],
        "circuit": {
          "use_via": "Via[0-1]_600:300_um"
        },
        "rule": {
          "clearances": [
            {
              "value": 200
            }
          ],
          "width": 200
        }
      }
    ]
  },
  "wiring": {
    "wires": [
      {
        "path": {
          "layer": "F.Cu",
          "width": 200,
          "coordinates": [
            150500,
            -105000,
            154540,
            -105000
          ]
        },
        "net": "Net-(C1-Pad1)",
        "type": "route"
      }
    ]
  }
}

we should throw in a smoke test or even a quick svg snapshot test

Also instead of calling it PcbJson we should call it DsnJson, because there are many pcb json types (including KicadJson)

I was testing on my end, forgot to add the test file. Will add that

repo: tscircuit/dsn-converter


text:
Looking for testers : DVB tuners on Windows

Hi TSDuck users,
TSDuck version 3.4-20171110 is out.
Among other features and improvements, the support for DVB tuners on Windows has been partly rewritten. The previous version was written 10 years ago on XP or Vista (I cannot even remember). Since then, there have been some significant improvements in DirectShow. With version 3.4, TSDuck uses DirectShow filters which did not exist 10 years ago. This should improve the support for DVB tuners on Windows. As a start, it solved the 32-bit vs. 64-bit issue which was reported with some drivers.
However, messing with DirectShow can be tricky since different tuners come with different BDA drivers and DirectShow filters. The experience had shown (but it was a long time ago) that some proprietary drivers may require very specific forms of DirectShow graphs.
So, I would appreciate if all TSDuck users with DVB tuners on Windows could try this new version and report their feedbacks in this thread. If it works, please indicate the tuner type and characteristics so that I could include this in the documentation. If if does not work, please add the output of tslsdvb --debug.
Thanks in advance for your cooperation.
PS: @rezna11, @ggnull35, your feedback would be greatly appreciated

I briefly tried couple of tuners, all worked. I tuned in DVB-S2 or DVB-T frequency and streamed to VLC to check. Tried with the 64-bit version of TSDuck.
TT-budget S2-4100 DVBS/S2 Tuner (Windows 10, Ku-band)
TeVii DVB-S/S2 Receiver (Windows 10, Ku-band)
TBS 6284 DVBT/T2 Tuner (Windows 10, DVB-T)
TBS 6903 DVB-S/S2 (Windows 10, C-band)
TBS 5925 USB (Windows Server 2016, Ku-band)
TBS 5922 USB (Windows Server 2016, Ku-band)
DVBSky S960 USB (Windows Server 2016, Ku-band)

Thanks Jan,
This is good news. It is quite fortunate that you have so many different tuners !
Thanks again for your help.

@rezna11  I am including your test results in the TSDuck documentation. Could you please specify if the TeVii DVB-S/S2 is a S660 or S662 ?

It's actually TeVii S482, I forgot to mention that.
By the way I also tried "IT9135 BDA Filter" (DVB-T) and it tuned and streamed, but after some time the picture started pixelating. I used -P regulate -P pcrbitrate, but that didn't solve it.

repo: tsduck/tsduck


text:
MSD dataset

请问msd数据集可以开源吗？关于类别的单标签划分是如何处理的呢？

We have uploaded MSD dataset in the data folder. We use the genre of songs as the category label.

authors: DavyMorgan KennyNH

repo: tsinghua-fib-lab/DGCN


text:
Implement subdirectory / suburl

Hey,
Gotty has a feature to run the web terminal in a sub url, e.g. http://localhost:8080/ttyd.
Would it be possible to implement a command line argument like -s "ttyd" to enable suburl routing?
Best regards,
Jonas

Is there any progress on this? If not, could you instruct how I can write the related part? I will try to add this feature.

resolved by #281

Hey thanks for working on this! Guess this will be very useful in the future. Unfortunately it doesn't work for me yet.
ttyd -b "/ttyd" bash
ttyd --base-path "/ttyd" bash

But I only get 404 on http://playground.pi:7681/ttyd :,(

authors: abduramann onny tsl0922

license: mit

license_source: bigquery


text:
unrecognized option '--reconnect'

Reconnect option not working.
root@7713654067ef:/app/src# ttyd -p 5000 -a --reconnect 0 --readonly pytest
ttyd: unrecognized option '--reconnect'

As you're trying to set it to 0 (disabling re-connect as per #180) there is nothing you should need to configure.  This option was removed in 0fc275f3a3251f1839a2e59d04011f6a4e41541c (diff-b3356305).

The old reconnect option is replaced with exponential backoff now, unfortunately it can't be disabled now.

authors: brianredbeard nnocetti tsl0922


text:
html: Add Unicode 11 xterm.js addon

Add Unicode 11 addon to xterm.js to enable support for newer Unicode standards. This addon significantly improves rendering of emojis.

@tsl0922 Will need some advice on how I activated the feature. Not sure I activated it in the preferred location. Feel free to recommend any changes or improvements.
For reference this is the line I am uncertain about:
terminal.unicode.activeVersion = '11';

For reference this is the line I am uncertain about:
terminal.unicode.activeVersion = '11';

Maybe it can be a Client Option, if we want to extend it to support unicode-graphemes addon later.

I think once the unicode-graphemes addon becomes stable it would be worth switching over.
The reason I didn't make Unicode 11 an option was I can't think of why you wouldn't want this always enabled. What benefit do we gain from this being an option? Without this being set, most emoji are just rendered incorrectly.

What benefit do we gain from this being an option?

You can enable / disable this addon, or switch to unicode-graphemes later.

You can enable / disable this addon, or switch to unicode-graphemes later.

Does this mean we want something that has a value of unicode-11 or unicode-graphemes so you select which support you want?

You actually have me thinking, should we add unicode-graphemes and mark is experimental, while setting the default to unicode11. Can do all the work now and later on just switch the default.

Does this mean we want something that has a value of unicode-11 or unicode-graphemes so you select which support you want?

The value should be valid for term.unicode.activeVersion, for example: 11 / 15-graphemes  (6 if both disabled)
Ref: https://github.com/xtermjs/xterm.js/blob/1da0db435f93879a60b9badbb663852ff3223063/demo/client.ts#L659-L679

should we add unicode-graphemes and mark it experimental

No, unicode-graphemes is not published to npm yet.

So let me clarify this before I get started:

We add a new client side variable: unicodeVersion.
If unset default is 11.
Can also be set to 6 or 15-graphemes.
If set to 11 we enable the unicode11 addon.
If set to 15-graphemes we fallback to default 11 and enable unicode11 addon.
If set to 6 we do nothing (not enable the unicode11 addon).

This is slightly different to your earlier post but I think it makes more sense to have Unicode 11 as the default. Unicode 6 is just way too old and renders very differently.
Happy to adjust this logic though based on your feedback.

We add a new client side variable: unicodeVersion.
If unset or unknown value, use the default 11.
If set to 6 we do nothing (not enable any unicode addon).

Thanks for merging this! 🤞 when this is released there are no issues.


text:
"ionic run ios" build error

Under OSX attempting to run 'ionic run ios' on the master branch (commit 32651bade92b38287f8a33d27698e456a62e55c5), I get the following compile error:
ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/GeofencePlugin.swift:35:23: error: expected expression in list of expressions
            selector: #selector(GeofencePlugin.didReceiveLocalNotification(_:)),
                      ^
ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/GeofencePlugin.swift:35:23: error: expected ',' separator
            selector: #selector(GeofencePlugin.didReceiveLocalNotification(_:)),
                      ^

'ionic info' yields:
Cordova CLI: You have been opted out of telemetry. To change this, run: cordova telemetry on.
6.4.0

Ionic Framework Version: 2.0.0-beta.9
Ionic CLI Version: 2.1.4
Ionic App Lib Version: 2.1.2
ios-deploy version: 1.9.0
ios-sim version: 5.0.9
OS: Mac OS X Yosemite
Node Version: v6.9.1
Xcode version: Xcode 7.0.1 Build version 7A1001

@Yermo master version is using master version of cordova-geofence-plugin, where swift version has been upgraded to 2.3. Looks like xCode 7.0 doesn't support swift 2.3, try to upgrade your xCode version to the newest 7.x or 8 if you can.

Thank you for the reply. Sorry for the delayed response. It took quite a few hours to get my venerable Mac Mini upgraded to the point where I could install the latest Xcode.
I re-cloned the repository, master branch, and followed the instructions again.
"ionic run ios" now yields a different compiler errors:
/Users/yml/Projects/ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/SwiftData.swift:668:36: warning: extraneous duplicate parameter name; 'name' already has an argument label
    public static func createIndex(name name: String, onColumns: [String], inTable: String, isUnique: Bool = false) -> Int? {
                                   ^~~~~

/Users/yml/Projects/ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/SwiftyJson.swift:181:39: error: '=' has been replaced with ':' in attribute arguments
    @available(*, unavailable, renamed="null")
                                      ^
                                      :
/Users/yml/Projects/ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/SwiftyJson.swift:897:35: error: expected ',' joining parts of a multi-clause condition
        if let errorValue = error where errorValue.code == ErrorNotExist{
                                 ~^~~~~
                                 ,
/Users/yml/Projects/ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/SwiftData.swift:1612:21: error: 'SQLiteDB' is inaccessible due to 'private' protection level
extension SwiftData.SQLiteDB {
                    ^
/Users/yml/Projects/ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/SwiftData.swift:1036:19: note: type declared here
    private class SQLiteDB {
                  ^
/Users/yml/Projects/ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/SwiftData.swift:1831:21: error: 'SQLiteDB' is inaccessible due to 'private' protection level
extension SwiftData.SQLiteDB {
                    ^
/Users/yml/Projects/ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/SwiftData.swift:1036:19: note: type declared here
    private class SQLiteDB {
....

* BUILD FAILED **

The following build commands failed:

	CompileSwift normal x86_64 /Users/yml/Projects/ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/GeofencePlugin.swift

	CompileSwift normal x86_64 /Users/yml/Projects/ionic2-geofence/platforms/ios/Ionic2 Geofence/Plugins/cordova-plugin-geofence/SwiftData.swift

	CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler

(3 failures)

Error: Error code 65 for command: xcodebuild with args: -xcconfig,/Users/yml/Projects/ionic2-geofence/platforms/ios/cordova/build-debug.xcconfig,-workspace,Ionic2 Geofence.xcworkspace,-scheme,Ionic2 Geofence,-configuration,Debug,-sdk,iphonesimulator,-destination,platform=iOS Simulator,name=iPhone 5s,build,CONFIGURATION_BUILD_DIR=/Users/yml/Projects/ionic2-geofence/platforms/ios/build/emulator,SHARED_PRECOMPS_DIR=/Users/yml/Projects/ionic2-geofence/platforms/ios/build/sharedpch

"ionic info" yields:
Your system information:

Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-beta.9
Ionic CLI Version: 2.1.4
Ionic App Lib Version: 2.1.2
ios-deploy version: 1.9.0
ios-sim version: 5.0.9
OS: Mac OS X El Capitan
Node Version: v6.9.1
Xcode version: Xcode 8.1 Build version 8B62

@Yermo thanks for pointing out. I forgot to add a preference to use legacy swift version after upgrading the plugin. Now it should work. I don't know why, but sometimes ionic run doesn't work for the first time, only the consecutive time. I haven't been doing hybrid mobile development for a few months, so looks like things have changed a little bit.

i can confirm rm plugin and add again works, also had to run then build / emulate ios more then once

authors: Yermo rathgeber2 tsubik


text:
__forceinline をやめてMinGWでもビルド可能とする

起こっていること
MinGWでは、__forceinlineはextern __inline__ __attribute__((__always_inline__,__gnu_inline__))と展開される
x86_64-w64-mingw32\include_mingw.h
https://github.com/mirror/mingw-w64/blob/eff726c461e09f35eeaed125a3570fa5f807f02b/mingw-w64-headers/crt/_mingw.h.in#L263-L267
すると、static extern ...と展開されてしまい、以下のエラーを生じる
error: multiple storage classes in declaration specifiers

修正案
すべての__forceinlineをinlineに置き換える。
根拠

このキーワードはCの標準ではないこと(https://forums.unrealengine.com/t/what-is-forceinline-macro/438373)
この関数たちはラウンド関数で繰り返し呼び出しが多いはずなので、展開を行うか否かは最近のコンパイラの最適化に任せるほうが無難と思われること
から、妥当だと思う。

プルリクエストありがとうございました！


text:
ブランチの命名規則

dev/から始まるブランチはプルリク時に自動デプロイされる。

説明は READMEかwikiに書くことを提案します。

repo: tsumiki-works/Pyramid


text:
Task 637 rayza component badge component development

Screenshots

Task linked: TASK-637 [component Badge] Component development

authors: RayzaOliveira arantespp

repo: ttoss/ttoss


text:
Feature Request: Adjustable soft tabs

I'd like to see an option to choose the number of spaces a soft tab spaces (ie, I'd like to use two).
Thanks in advance !

Me too (2), but I'm guessing on the age and lack of commentary, that this is not going to be a high priority.

authors: ephetic pfaure

repo: ttscoff/nv


text:
select_related

I.e., we have City-Country-Continent db schema. I need to obtain continents for some cities. To do this, now I have these options:

query City with depth=2
write custom serializer class on server side

depth is not a bad option, but if you need more than one join, all these relations may become a problem.
So, the proposal is to add "select_related" option to filter() arguments.

it adds qs.select_related(*fields) to serializers queryset
it automatically created fields, named like select_related values

For example:
>>> client.filter('City', kwargs={
  'filters': {},
  'select_related': ['country__continent']
})

[{
  'id': 1,
  'name': 'Moscow',
  'country__continent': 'Eurasia'
}]

Problems found:

Django select_related() adds related objects as obj.country.continent
Thus, you need to write complex serializer method to obtain continent serialized data
if you setattr this method to GenericSerializerClass object, it doesn't become 'bound method', so some __new__ magic is needed
also, ModelSerializer need to be constructed for Continent model, and model class must be resolved before instantiation of GenericSerializerClass

Lot's of stuff to think about.

Thanks!

license: unlicense


text:
Problem receiving multiple messages quickly

Hi Tuan
I am using your ESP8266 firmware with your mqtt library on Arduino Nano.  Using a modified version of the example program (see below), I can send and receive individual messages OK.
However, when I try to receive five messages that have been sent in quick succession from another client program, only the first two are received.  Then I see the following debug message and the program hangs.
Get another published message
TCP: data received 114 bytes

Checking the messages at the same time using MQTT.fx client, I can see that all five messages are received OK.
Any idea what the cause might be?
Thanks
Ray
#include <myPushSwitch.h>

#define SWITCH_PIN                     8

PushSwitch testSwitch(SWITCH_PIN, INPUT_PULLUP, LOW, false);  // Enable internal pullup; use default debounce time; wait for double press

switchEvent sEvent;

#include<SoftwareSerial.h>
#include <espduino.h>
#include <mqtt.h>

SoftwareSerial debugPort(2, 3); // RX, TX
ESP esp(&Serial, &debugPort, 4);
MQTT mqtt(&esp);

boolean wifiConnected = false;
boolean mqttIsConnected = false;
boolean sentFirstMQTT = false;

#define BUFFER_SIZE 50
char buffer[BUFFER_SIZE];

void wifiCb(void* response)
{
  uint32_t status;
  RESPONSE res(response);

  if (res.getArgc() == 1)
  {
    res.popArgs((uint8_t*)&status, 4);
    if (status == STATION_GOT_IP)
    {
      debugPort.println(F("WIFI CONNECTED"));
      wifiConnected = true;
      mqtt.connect("hackscribble.ddns.net", 1883, false);
    }
    else
    {
      debugPort.println(F("WIFI NOT CONNECTED"));
      wifiConnected = false;
      mqtt.disconnect();
    }
  }
}

void mqttConnected(void* response)
{
  debugPort.println(F("MQTT CONNECTED"));
  mqtt.subscribe("hackscribble/controls/query");
  mqtt.subscribe("hackscribble/controls/led");
  mqtt.subscribe("hackscribble/controls/pwm");
  mqttIsConnected = true;
}

void mqttDisconnected(void* response)
{

}

void mqttData(void* response)
{
  RESPONSE res(response);

  debugPort.print(F("Received: topic="));
  String topic = res.popString();
  debugPort.println(topic);

  debugPort.print(F("data="));
  String data = res.popString();
  debugPort.println(data);

  topic.toCharArray(buffer, BUFFER_SIZE);
  if (strstr(buffer, "controls/query"))
  {
    reportSwitchState();
  }
  if (strstr(buffer, "controls/led"))
  {
    data.toCharArray(buffer, BUFFER_SIZE);
    if (strstr(buffer, "true"))
    {
      digitalWrite(13, HIGH);
    }
    else if (strstr(buffer, "false"))
    {
      digitalWrite(13, LOW);
    }
  }
}

void mqttPublished(void* response)
{

}

void reportSwitchState()
{
  if (testSwitch.read() == switchWasPressed)
  {
    mqtt.publish("hackscribble/controls/switch", "closed");
  }
  else if (testSwitch.read() == switchWasReleased)
  {
    mqtt.publish("hackscribble/controls/switch", "open");
  }
}

void setup()
{

  Serial.begin(19200);
  debugPort.begin(19200);
  debugPort.println(F("ARDUINO: running test-mqtt\r\n\n"));

  pinMode(13, OUTPUT);

  testSwitch.begin();
  sEvent = testSwitch.update();

  esp.enable();
  delay(500);
  esp.reset();
  delay(500);
  while (!esp.ready())
  {
    // empty
  }

  debugPort.println(F("ARDUINO: setting up mqtt client"));
  if (!mqtt.begin("ESP8266", "hackscribble", "hackscribble", 120, 1))
  {
    debugPort.println("ARDUINO: fail to setup mqtt");
    while (1);
  }

  debugPort.println(F("ARDUINO: setting up mqtt lwt"));
  mqtt.lwt("/lwt", "offline", 0, 0);

  /*setup mqtt events */
  mqtt.connectedCb.attach(&mqttConnected);
  mqtt.disconnectedCb.attach(&mqttDisconnected);
  mqtt.publishedCb.attach(&mqttPublished);
  mqtt.dataCb.attach(&mqttData);

  /*setup wifi*/
  debugPort.println(F("ARDUINO: setting up wifi"));
  esp.wifiCb.attach(&wifiCb);

  esp.wifiConnect("<snip>", "<snip>");

  debugPort.println(F("ARDUINO: system started"));

}

void loop()
{

  esp.process();

  if (wifiConnected)
  {
    // empty
  }

  if (mqttIsConnected)
  {
    if (!sentFirstMQTT)
    {
      mqtt.publish("hackscribble/controls/status", "ESP8266 is connected");
      sentFirstMQTT = true;
    }
  }

  sEvent = testSwitch.update();
  if ((sEvent != switchNoChange) && mqttIsConnected)
  {
    reportSwitchState();
  }

}

I too have issues with messages coming in in rapid succession. In my case, the Arduino completely freezes up. I've narrowed the down to the espduino Library (IOTW: not my code). I'm not entirely sure why it happens, but I suspect it may be related to @hackscribble's issue.

Did you try to increase receive buffer size more than 256 bytes?

Did you try to increase receive buffer size more than 256 bytes?

@tuanpmt No, I did not try that, but thank you for your reply as it led me to a solution.
I looked around in the espduino code for the default buffer size. I think I found it, and I believe it was 512 bytes (?). Which should have been sufficient for my needs.
In debugging my sketch, I found that my available memory was less than 400 bytes. I rearranged some object allocations to free up memory, and now hover around 900 bytes free. I would assume that the 512 bytes for the buffer are allocated only once. Freeing up more memory, however, DID seem to solve the problem for me.
I ran some more tests to see what happened when I sent multiple messages in rapid succession. My sketch no longer crashes. The worst result I got was a momentary freezing of the loop(), followed by an invalid CRC error. It then recovered on it's own. The messages I receive are not mission critical. It will be rare for me that many messages come in rapid succession, and if the worst I get is a random invalid CRC, so-be-it. Good enough for my needs.

Thanks @tuanpmt for the suggestions about memory.  I tried those but it did not help.  And reducing the size of my topic titles and data made no difference either.
But that go me thinking that maybe I was seeing a timing problem, not a memory problem.  The symptoms were consistent with the code not being able to keep up with the speed at which new messages arrive.
So I looked at the mqttData callback.  It had several calls to SoftwareSerial.  Also, I am running the debug version of the firmware, so that sends its own messages to SoftwareSerial.  I commented out a couple of my debug print statements and the problem has gone away.
I'll experiment with the no debug firmware and putting my print statements back in.  But I'm going to close this issue.
Many thanks.

@hackscribble Good call. I have quite a few Serial print statements in the same place, and I too am running the debug version of the firmware.

@tuanpmt , hello!
I have faced with quite a similar problem. I am sending mqtt messages from Arduino with ESP as a bridge and after successful 2-3 messages in a row connection between device and broker is lost.
I have increased time delay between messages from 1 second to 20 but same situation appeared. I have tried to clear some more space in Arduino sketch but that didn't help either.
Is there any command to clear buffer on ESP because it seems to me that the problem is on that side? Any suggestions?
Thank you!

@hackscribble @eschlenz  @tuanpmt
Was running into the same issue using a Nano and debug software. Due to the number of sensors I must support I had the hardest time getting memory consumption low. Eventually I also got the CRC error in the loop and then it would process again. Thus it would lock up intermittently and then process again. I tried the following serial buffer sizes 16,32,64,128,256,512, I also removed a lot of debug statements.
I suspect my problem was exasperated due to the amount of other libraries in my sketch.
I suspect the debug firmware and debug output statements might be causing an issue where the serial buffers are causing the arduino to wait for some end of line/end of packets this buffer keeps on getting filled and when the arduino finally get the missing eol character it does a crc check. This crc check fails but since the message is complete the arduino can then processes as per normal.
When I changed over to the production version of the firmware the problem seems to not occur. I will do some more testing.
This is all just a hunch though.

@Namphibian
I have switched to production version of firmware and increased both HardwareSerial and SoftwareSerial up to 512 as well. But the problem still occurs after 20 minutes of sending information each second.
As for me it is almost fine but however I want to see completely running device without any mistakes

I was using the ESP-01 variant for initial testing as it is just easier to connect. I have now moved to the ESP-07 variant and this problem seems to have vanished. Well based on my tests now I cannot see the system freezing when sending/receiving messages in a 1 second interval for 15 minutes there was a slow down and things got queued but nothing like the lock ups I saw before. This evidence is only anecdotal and once I have done some more testing I will confirm this.

authors: Namphibian eschlenz hackscribble hukm tuanpmt

repo: tuanpmt/espduino


text:
decoding momentum/sparkpost click tracking urls

The tools you are writing here seem to be part of a new system for engagement tracking, as described on your post https://www.sparkpost.com/blog/deploying-signals-for-on-premises-powermta-with-engagement-tracking-part-4/ .
Are there similar tools for dealing with existing momentum/sparkpost engagement tracking, such as those described in your post https://www.sparkpost.com/blog/deploying-signals-premises-momentum-integration-part-3/ ?
In particular, the engagement tracking encoding mechanism seems quite different in the two pieces of software. In your part-3 post, you have URLs such as:
http://momo.signalsdemo.trymsys.net:81/q/rCZ3YpEEJBOHGGI06Rw9OA~~/AAAAAQA~/RgRfOCDVPhdCCgAAVe1WXbth_QBSGHN0ZXZlLnR1Y2tAc3Bhcmtwb3N0LmNvbVgEAAAAAEEIAC6rdFwAAPoJUQQAAAAARwJ7fQ~~
But the example URLs for your linktool here are of the form:
http://localhost:8888/eJxUzLEOQiEMRuF3-WciGAaTTr4JwbaIUSKBMhnf_Ybxnv18P2Q2EBgOltb4gFDN-iTvraotfs8Lfxsc2nyml4AQdqJZHqqlhCDXGG9wGNw3VYbK_fT-jwAAAP__f2Mg1g==
As far as I can tell these are of a different encoding.
Do you know of software that decodes the first type of URL as above?

You're correct that the two tracking encodings (Momentum, and this project) are quite different. The Momentum encoding is not open-sourced, is more complex, and uses cryptographic methods.

Are there no open-source documentation/tools then for decoding the Momentum links? I understand that the entire Momentum project may not be open.


text:
Not working with asset-pipeline:2.1.0

The plugin is working fine with assest-pipeline:1.9.9 but when upgraded to asset-pipeline:2.1.0 it is giving the following error:
File was not sourced from the same ScanDirectory D:\Grails Projects\easygridtest2\target\work\plugins\easygrid-1.6.9\web-app\jquery.jqGrid-4.6.0\js\jquery.jqGrid.src.js scanDir: D:\Grails Projects\easygridtest2\target\work\plugins\easygrid-1.6.9\web-app\css

Should be fixed in 1.6.9.1

Thank you it is working now after I downloaded 1.6.9.1
On 8 February 2015 at 17:38, Tudor Malene notifications@github.com wrote:

Should be fixed in 1.6.9.1
—
Reply to this email directly or view it on GitHub
https://github.com/tudor-malene/Easygrid/issues/137#issuecomment-73413408
.

authors: suryazi tudor-malene

repo: tudor-malene/Easygrid


text:
Update viewer-custom.scss

Blank space is showing

this space appear in a new version of Microsoft Edge Chromium

Someone car review this PR pls? 🙏🏼

I will try to make a new release today.

also seeing this in Brave 1.17.73 (Chromium 87.0.4280.67)

also seeing this in Brave 1.17.73 (Chromium 87.0.4280.67)

apparently only affected chromium based browsers :/ but @tulios has not done a new release yet

https://github.com/marketplace/actions/chrome-extension-upload-publish
@tulios This is an action to configure a workflow to upload and publish chrome extensions

Version 0.18.1 was submitted for review and it will be automatically published once it's done.

authors: buster95 felixmosh murakilo tulios

repo: tulios/json-viewer


text:
Add in typescript declaration file.

I've added in a typescript declaration file and also updated the transactions documentation to correctly  reflect the setup process for transactional producer.

@talam thanks for the PR

This is an amazing effort. Thank you so much!

I think Azure pipelines is having some issues; I will get this build green and merge. Thanks.

Nice work!
@tulios any idea when this will be released?

@micaelmbagira I will probably bundle this change with some other issues so it might take a little while. You can try it out by using the commit number:
yarn add https://github.com/tulios/kafkajs.git#054ef5042a99cca6af97bd90e43facadcc01dd3e

authors: Nevon micaelmbagira talam tulios

repo: tulios/kafkajs


text:
Update scalafmt-core to 3.1.0

Updates org.scalameta:scalafmt-core from 3.0.8 to 3.1.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, early-semver-minor, semver-spec-minor

Superseded by #85.

repo: tulz-app/laminext


text:
博士后模板中增加合作导师

维护人员你们好！不知道能否在博士后模板中，在“专 业（二级学科）名称”的下一行，增加一个“合作导师”？
非常感谢

发现原来已经有所讨论，是官方给的模板中没有这一行。

repo: tuna/thuthesis


text:
Comparison with wasm2c + some ideas

Just performed a quick test to understand how it compares to wasm2c.
For this test I took a ~25 MB wasm (WASI) file, clang.wasm

w2c2 finishes in 5.1s, RAM usage: 193 Mb. Output: 1.3 GiB file (34.8 Mb zipped)
wasm2c finishes in 1m23s, RAM usage: 1432 Mb. Output: 301 MiB file (22 Mb zipped)

Clearly, speed and RAM usage are really good :tada: :rocket:
Wondering if file size can be reduced :scientist:
This also brings another question. C compilers are not very efficient when working with huge C files, so monsters like clang.wasm will take ages to compile. This is mentioned in my wasm2native tool: https://github.com/vshymanskyy/wasm2native#todo
One of the possible solutions is to split output into smaller chunks (which also enables parallel build).

I think I can add w2c2 as an alternative translator for wasm2native.
Now on Features comparison.
w2c2 is not yet handling some of important wasm proposals:

Sign-extension operations
Non-trapping Float-to-int Conversions
Multi-value

These are implemented in wasm2c and covered by opam-1.1.1 spec tests.
Other important proposals include:

Bulk memory operations
Exception handling
Reference types
Multiple memories
These (at the time of writing) are not available in wasm2c. Spec tests for these features are available in main branch.

Coremark 1.0 results
Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz, single-thread
GCC 10.3.0, optimization level: -O3

Native: 33305.578684
wasm2c output: 27458.936027
w2c2 output:  27469.603167

Thank you for this analysis Volodymyr!
These are great points for the README, I will detail better which features are supported and also which are not, and the trade-offs / goals of the project itself.
Performance
I had no idea clang was itself available as a WebAssembly binary, amazing! This is a great  stress-test.
My main goal is porting new software to older machines, which have only tens of MHz and memory, ideally on the host itself (no cross-compiling). This is why I looked into streaming compilation (no IR), but also took a few short-cuts.
For now I have focused on getting the test suite to pass and some small programs to compile and run. So far I have not focused on any performance optimizations, other than employing a streaming-compilation approach. It is great to see that even large programs like clang can be translated and performance is already good.
I think there are multiple opportunities to improve the performance and resource footprint  further, by improving memory allocation, improving speed by parallelizing compilation, and especially for reducing size by removing the unnecessarily generated code:

Always remove parameter names from function prototypes, they are not needed
Behind a "compact" flag:

Remove spaces for indentation
Remove braces for blocks
Remove newlines for statement of a single op (e.g. jump op is if-statement + goto statement)
Remove unnecessary labels. Streaming compilation makes this harder

Great point about compiling large C files: This is one of the reasons I started this project. SwiftWasm generates very large WebAssembly binaries, which take long to compile to C and then very long to compile to a native binary.
I am currently working on parallel compilation, where the compiler is writing function implementations into several smaller files that can be compiled independently, and also performing this code generation concurrently. This will hopefully make compiling the resulting C code more manageable and also speed up the translation process from WebAssembly to C.
Features
For now I have focused on supporting the core specification 1.0 as outlined in https://www.w3.org/TR/wasm-core-1/.
I have not looked into new approved features, like the ones you listed, mostly because I was not sure if they are needed for compiling applications and libraries written in C, C++, Rust, Swift, etc. It seems that most compilers seem to target the "MVP" specfication.
As for the concrete proposals you listed:

Sign-extension operations and non-trapping float-to-int conversions: I think this should be "just" implementing the new opcodes
Multi-value: I had a quick look, it seems like it is going to complicate the compiler quite a bit
Bulk memory operations, exception handling, reference types, multiple memories: These features all seem to add new opcodes, new types, and extend the language quite a lot. They are going to be quite a bit of work to implement

Do you know if there are certain compilers targeting WebAssembly that leverage or even require these feature?
Coremark results
Performance should be very similar to wasm2c, as the generated code pretty much the same.
I have not looked into opportunities to generate more efficient code.
wasm2native integration
This looks like a great project! I was looking for a wasi implementation for wasm2c, awesome work!
Currently the API that w2c2 provides is slightly different than wasm2c, and it produces differently mangled names (mostly they are shorter, e.g. don't include type information). I think this difference could be worked around or even removed.

Some thoughts from me (great project btw!):

Sign-extension [..] non-trapping float-to-int [..] Multi-value [..] Bulk memory operations, exception handling, reference types, multiple memories [..] Do you know if there are certain compilers targeting WebAssembly that leverage or even require these feature?

Several of those features are implemented in LLVM and are optional in the Emscripten and Rust toolchains for example. But they are not required, so projects using them could just be recompiled for wasm 1.0.
Exceptions is maybe the hardest of those. You can compile C++ exceptions and longjmp with wasm 1.0 today, but then you have to use the Emscripten EH model which requires supporting some extra imports (emscripten's wasm2c layer emits them), but also it is probably slower than wasm EH.
Overall, my guess is that compiling wasm 1.0 to C is "good enough" for most things in the C/C++/Rust/Zig/etc. world today. Exceptions maybe raise the question of compiling to C++ instead, and wasm GC maybe suggests compiling to a GC language, but maybe those features would be out of scope of this project anyhow?

Coremark results: Performance should be very similar to wasm2c, as the generated code pretty much the same. I have not looked into opportunities to generate more efficient code.

I would guess nothing is needed in w2c2 or wasm2c for performance since the C compiler does the hard work anyhow. The big question is whether there are things that wasm->C translation can optimize that a C compiler can't, but it's hard for me to think of anything...

@kripken Thank you for answering my questions, that makes a lot of sense!

Exceptions maybe raise the question of compiling to C++ instead, and wasm GC maybe suggests compiling to a GC language, but maybe those features would be out of scope of this project anyhow?

I have no immediate plans for generating other code in other languages, but even though the C code generation (in c.c) is currently writing C directly, it would be possible to abstract it away, e.g. by calling code generating functions, for different target languages.

[...] the C compiler does the hard work anyhow. The big question is whether there are things that wasm->C translation can optimize that a C compiler can't, but it's hard for me to think of anything..

I mostly focused on streaming code generation and assumed that tools like binaryen's wasm-opt can take care of optimizations and w2c2 does not need to reinvent the wheel here. It is likely that such pre-C optimizations are actually useful, as older C compilers likely do not have as advanced optimizations as modern compilers, though I have not tested this yet.

@vshymanskyy I've added support for parallel compilation in #2. Going to work on reducing the output size now

With #3 merged, the output size is now reasonable

Great news. #2 along with #3 bring clang compilation time from 20 minutes to ~3 minutes (gcc, 12 threads, -O3).
I was not able to link it yet, will take look into this later.
Overall, this is a huge improvement :tada: :tada: :tada:

@vshymanskyy That's great to hear! Linking clang.wasm will require implementing quite a few more WASI functions (e.g. file I/O, FS operations), so far I had only implemented enough to get coremark.wasm to run.
I saw you started work on a WASI implementation for wasm2c in wasm2native, great work! It would be nice to leverage this existing work and not have to re-implement the WASI spec specifically for w2c2 again. First step would be to make the API of the generated code of w2c2 match that of wasm2c. I started looking into the differences and noticed that wasm2c includes the parameter types and return types in the mangled names of the imports and exports – is this really necessary?
I also wonder what the minimum requirements for uvwasi and especially libuv are (C standard, endianness, etc.)

WASI implementation improvements are work in progress in #4

I also wonder what the minimum requirements for uvwasi and especially libuv are (C standard, endianness, etc.)

Both target C89 and run on little and big endian machines.

I was able to add w2c2 as an alternative translator for wasm2native.
Re-mapping of symbols is easy:
    #define Z_fd_prestat_getZ_iii               fdX5FprestatX5Fget
    #define Z_fd_prestat_dir_nameZ_iiii         fdX5FprestatX5FdirX5Fname
    #define Z_environ_sizes_getZ_iii            environX5FsizesX5Fget
    #define Z_environ_getZ_iii                  environX5Fget

Along with customized IMPORT_IMPL* definitions.
@turbolent When generating multiple files with -j flag, I'm getting lots of "multiple definitions" of e_X5Fstart and e_memory (defined in decls.h, then included in each c file). Fixed it by making them extern and defining in my main.c.
After that, I was able to build clang.wasm into a working clang.elf. Beware, linking takes ages :grinning:

Ok, got it working. clang.wasm was compiled and linked (using Clang 12 + LLD) in parallel mode (-j 12) in just 3m34s.
Will send a PR with my changes.

@vshymanskyy Wow, nice! It didn't even occur to me to use the pre-processor to add compatibility, great idea 👍
Also, thank you for the bug report and also the fix!
Great to hear clang builds in reasonable time 🎉  Maybe it can be sped up with -O0? (see https://maskray.me/blog/2021-12-19-why-isnt-ld.lld-faster)

@turbolent do all/any of these platforms support CMake? Do you compile on the target, or do you cross-compile?
wasm2native should conceptually support Big-Endian systems, like Wasm3 does. It needs some debugging, as testing with QEMU showed there are issues (but looks like we're almost there).

I'd like to get rid of CMake dependency for wasm2native, but libuv only supports autotools or CMake officially.

@vshymanskyy Node.js builds libuv with gyp. I'm not sure if you can use it for inspiration, but here is the gyp file.

@vshymanskyy For Mac OS X 10.4/10.5 tigerbrew provides CMake 3.6, I'm not sure if that's enough.
As for big-endian support: wasm2c and w2c2 both use "negative memory" (see the end of https://skmp.dev/blog/negative-addressing-bswap/), so access in memory mem with size size at offset off is mem + size - off. Values are in native endianness, but that also means that e.g. data (e.g. string values) is stored in "reversed order" and e.g. needs a reverse before a syscall (e.g. write). I think the first step is to add a big-endian definition for https://github.com/vshymanskyy/wasm2native/blob/afa64bee90b3483e8747f3533906a7332c588a6b/src/wasi-main.c#L16 and then add reverse operations where data is read. I wonder which of the two options I can think off are more efficient:

Two reverses in the linear memory that is pointed to
One copy of the memory that is pointed to into a temporary allocation and a single reverse of it

@vshymanskyy I now have enough of a WASI implementation that should be able to run clang.wasm, e.g. the input file is checked to be existing, but then clang just exits. A simple Rust program exercising all the functionality works as expected, so I'm wondering what I'm missing.
Do you have instructions on how you compiled/created clang.wasm? I would like to build it with assertions enabled, so I can debug it further.

@turbolent thanks for explanations on Big-Endian, will check it soon.
Just checked my clang compilation. For this test I replaced clang.wasm here in my wasm3 self compilation experiment here: https://github.com/wasm3/wasm3-self-compiling/blob/ee61ccecdf30bee73f3c640764896da8f6ca439d/Makefile#L33
It looks working well.
I didn't push my changes to wasm2native yet. I'll let you know when it's ready.

Overall, it may be a good idea to move wasi implementation into a separate project. It's rather complicated, esp. if targeting multiple OS environments.

@turbolent just pushed changes to wasm2native. You should be able to:
git clone https://github.com/vshymanskyy/wasm2native.git
cd wasm2native
export CC="clang-12"
export LDFLAGS="-fuse-ld=lld"
./build.sh path/to/clang.wasm

To run the resulting clang.elf, you can replace the compilation command in wasm3-self-compiling.
But it should work as a standalone compiler as well.

@vshymanskyy Great to see you've added support for w2c2!
I've got clang.wasm working in #4 and documented the status for all WASI syscalls in the README. There are still a few missing and I'll add them as needed, contributions are very welcome! Agreed on moving the WASI implementation to a separate repository once it is in a more complete state.
When compiling clang.wasm I noticed that inits.c is still huge (16MB), so I'll look into splitting how to split it up further, as currently I can only compile it with -O0.

@vshymanskyy Great to see you've added support for w2c2!
I've got clang.wasm working in #4 and documented the status for all WASI syscalls in the README. There are still a few missing and I'll add them as needed, contributions are very welcome! Agreed on moving the WASI implementation to a separate repository once it is in a more complete state.
When compiling clang.wasm I noticed that inits.c is still huge (16MB), so I'll look into splitting how to split it up further, as currently I can only compile it with -O0.

Awesome! 🙌

Update: The WASI implementation now has support for big-endian machines and fd_readdir.
QEMU's user mode emulation is really useful for development, but also has some issues, e.g. when using it on a 64-bit host running 32-bit executables and performing filesystem operations.

With some efforts, it should be possible to wasm2c wasm2c.wasm > wasm2c.c 😱

@turbolent , wasm3 w2c2.wasm w2c2.wasm > w2c2.c works with #7 ! 🎉 🎉 🎉

@vshymanskyy Wow, awesome! This is actually going to be really useful on platforms with bad C compilers (e.g. the SGi MIPSpro compiler on IRIX) 👍

As mentioned above, I ran into linking errors for clang on Mac OS X 10.4 on PowerPC. I assumed this was due to large static arrays that are generated for the data segments. I found some platform-specific ways of embedding the data segments directly in the binary without having to generate large array literals in the source in #8. This is generally useful, however, I am still getting linker issues for the example above, probably due to the binary being too large and jump instructions overflowing?

authors: cjihrig kripken turbolent vshymanskyy


text:
Build libsql-server images on PR

This PR adds a workflow which builds and pushes the pull request Docker image.
Note: This workflow is only triggered for internal users and the pull request body must contain a special string +build
+build

sample workflow run: https://github.com/tursodatabase/libsql/actions/runs/7478339603/job/20353093678?pr=734

@MarinPostma @LucioFranco anything preventing us from merging this?

authors: avinassh penberg

repo: tursodatabase/libsql


text:
segfault when using turso db shell

Version:
turso version v0.96.1

steps

start sqld locally
run turso db shell  ws://localhost:8080
enjoy:

 turso db shell ws://localhost:8080
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0xe8 pc=0x104a03df4]

goroutine 1 [running]:
nhooyr.io/websocket.(*Conn).SetReadLimit(...)
        /home/runner/go/pkg/mod/nhooyr.io/websocket@v1.8.10/read.go:94
github.com/tursodatabase/libsql-client-go/libsql/internal/ws.connect({0x140001aea50, 0x13}, {0x0, 0x0})
        /home/runner/go/pkg/mod/github.com/tursodatabase/libsql-client-go@v0.0.0-20240715111033-518abad12431/libsql/internal/ws/websockets.go:205 +0xe4
github.com/tursodatabase/libsql-client-go/libsql/internal/ws.Connect({0x140001aea50?, 0x140001f3b08?}, {0x0?, 0x104438f18?})
        /home/runner/go/pkg/mod/github.com/tursodatabase/libsql-client-go@v0.0.0-20240715111033-518abad12431/libsql/internal/ws/driver.go:57 +0x24
github.com/tursodatabase/libsql-client-go/libsql.wsConnector.Connect(...)
        /home/runner/go/pkg/mod/github.com/tursodatabase/libsql-client-go@v0.0.0-20240715111033-518abad12431/libsql/sql.go:191
database/sql.(*DB).conn(0x140002a0ea0, {0x104d4f700, 0x105392140}, 0x1)
        /home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.0.linux-amd64/src/database/sql/sql.go:1415 +0x824
database/sql.(*DB).exec(0x140002a0ea0, {0x104d4f700, 0x105392140}, {0x104a8919d, 0x9}, {0x0, 0x0, 0x0}, 0x20?)
        /home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.0.linux-amd64/src/database/sql/sql.go:1679 +0x40
database/sql.(*DB).ExecContext.func1(0xb8?)
        /home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.0.linux-amd64/src/database/sql/sql.go:1662 +0x54
database/sql.(*DB).retry(0x104d4f700?, 0x14000049600)
        /home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.0.linux-amd64/src/database/sql/sql.go:1566 +0x4c
database/sql.(*DB).ExecContext(0x0?, {0x104d4f700?, 0x105392140?}, {0x104a8919d?, 0x140000498e0?}, {0x0?, 0x1400029c5e0?, 0x10462bd50?})
        /home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.0.linux-amd64/src/database/sql/sql.go:1661 +0x94
database/sql.(*DB).Exec(...)
        /home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.0.linux-amd64/src/database/sql/sql.go:1675
github.com/libsql/libsql-shell-go/internal/db.(*Db).TestConnection(0x140001aea20?)
        /home/runner/go/pkg/mod/github.com/libsql/libsql-shell-go@v0.10.2/internal/db/db.go:109 +0x48
github.com/libsql/libsql-shell-go/pkg/shell.RunShell({{0x140001aea20, 0x13}, {0x0, 0x0}, {0x0, 0x0}, {0x104d4a328, 0x14000198028}, {0x104d4a308, 0x14000198030}, ...})
        /home/runner/go/pkg/mod/github.com/libsql/libsql-shell-go@v0.10.2/pkg/shell/shell.go:36 +0xb8
github.com/tursodatabase/turso-cli/internal/cmd.runShell({0x0, 0x0}, {{0x140001aea20, 0x13}, {0x0, 0x0}, {0x0, 0x0}, {0x104d4a328, 0x14000198028}, ...})
        /home/runner/work/turso-cli/turso-cli/internal/cmd/db_shell.go:233 +0x4c
github.com/tursodatabase/turso-cli/internal/cmd.init.func23(0x105314f00, {0x1400019b3a0, 0x1, 0x104a8357f?})
        /home/runner/work/turso-cli/turso-cli/internal/cmd/db_shell.go:228 +0xaf4
github.com/spf13/cobra.(*Command).execute(0x105314f00, {0x1400019b370, 0x1, 0x1})
        /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:916 +0x654
github.com/spf13/cobra.(*Command).ExecuteC(0x10531a820)
        /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044 +0x320
github.com/spf13/cobra.(*Command).Execute(...)
        /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
github.com/tursodatabase/turso-cli/internal/cmd.Execute()
        /home/runner/work/turso-cli/turso-cli/internal/cmd/root.go:25 +0x24
main.main()
        /home/runner/work/turso-cli/turso-cli/cmd/turso/main.go:6 +0x1c

additional information: it seems to be because the sever refuses the connection:
2024-07-18T12:04:02.701195Z  INFO libsql_server::connection::libsql: setting PRAGMA synchronous to relaxed
2024-07-18T12:04:02.701776Z  INFO libsql_server::connection::libsql: setting PRAGMA synchronous to relaxed
2024-07-18T12:06:20.918786Z  INFO libsql_server::hrana::ws: Received HTTP upgrade connection #0
2024-07-18T12:06:20.919870Z ERROR libsql_server::hrana::ws: HTTP upgrade connection #0 failed: Could not perform the WebSocket handshake on HTTP connection

Caused by:
    Invalid host header: `host header should be in the format <namespace>.<...>`

fixed by https://github.com/tursodatabase/libsql-client-go/pull/128

repo: tursodatabase/turso-cli


text:
ユーザー画面に問題解答画面を実装する

問題文、テキストエディタ、テスト実行機能、提出機能が含まれた画面。生徒が解答を入力し、テストを実行して結果を確認した後、最終的に提出することができる。

https://v0.dev/chat/GObOpm1ocyp

repo: tus-project-team/program-grading-system


text:
Base Path of / no longer working

Describe the bug
I updated from an older version of tusd (somewhere in the 0.13s, I think) to the latest version (v1.2.0). Having a base path of / no longer works, it just returns 404 errors. If I set base-path to anything else (/files/ or /resumable/) then it works. Just not a base-path of /.
To Reproduce
Steps to reproduce the behavior:

Run docker run --rm --name tusd -p 127.0.0.1:1080:1080 tusproject/tusd:v1.2.0  -port 1080 -max-size 10737418240 -base-path /
Use uppy on the client side to try to upload with configuration:

Uppy({autoProceed: true})
      .use(Tus, { endpoint: 'http://127.0.0.1:1080/' });

Upload fails.

Error message in browser:

[Uppy] [01:29:53] Failed to upload myFile.csv tus: unexpected response while creating upload, originated from request (response code: 404, response text: 404 page not found

Logging from tusd console:

[tusd] 2020/05/25 06:27:47 Using '/srv/tusd-data/data' as directory storage.
[tusd] 2020/05/25 06:27:47 Using 10240.00MB as maximum size.
[tusd] 2020/05/25 06:27:47 Using 0.0.0.0:1080 as address to listen.
[tusd] 2020/05/25 06:27:47 Using / as the base path.
[tusd] 2020/05/25 06:27:47 Using /metrics as the metrics path.
[tusd] 2020/05/25 06:27:47 Supported tus extensions: creation,creation-with-upload,termination,concatenation,creation-defer-length
[tusd] 2020/05/25 06:27:47 You can now upload files to: http://0.0.0.0:1080/
[tusd] 2020/05/25 06:27:49 event="RequestIncoming" method="POST" path="/" requestId=""

HTTP Response body from tusd:

404 page not found

HTTP Response headers from tusd:

Access-Control-Allow-Origin: http://localhost:8000
Access-Control-Expose-Headers: Upload-Offset, Location, Upload-Length, Tus-Version, Tus-Resumable, Tus-Max-Size, Tus-Extension, Upload-Metadata, Upload-Defer-Length, Upload-Concat
Content-Length: 19
Content-Type: text/plain; charset=utf-8
Date: Mon, 25 May 2020 06:31:47 GMT
Tus-Resumable: 1.0.0
X-Content-Type-Options: nosniff

Expected behavior
Upload is successful.
Setup details
Please provide following details, if applicable to your situation:

Operating System: macOS host but using Docker image for tusd
Used tusd version:

Version: v1.2.0
Commit: a4a733fb39186dea8337ae4579d87034b7f222c7
Date: Thu May  7 12:58:13 UTC 2020

Used tusd data storage: [e.g. disk store, AWS S3, Google Cloud Storage] Tried with AWS S3 and default
Used tusd configuration: see above command
Used tus client library: Uppy.js

Thanks for your detailed report. This should be fixed in the 1.3.0 release.

Can confirm that fixed it. Thanks for the incredibly quick response and release!

authors: Acconut seanfisher

repo: tus/tusd


text:
轮播图自定义dots样式后无法响应鼠标经过指示点切换

TuSimple/naive-ui version (版本)
2.32.2
Vue version (Vue 版本)
3.2.37
Browser and its version (浏览器及其版本)
chrome 106.0.5245.0
System and its version (系统及其版本)
Windows11 22621.382
Node version (Node 版本)
Reappearance link (重现链接)
https://codesandbox.io/s/elegant-proskuriakova-mts8ne?file=/src/App.vue
Reappearance steps (重现步骤)
自定义dots样式后设置 trigger="hover"
Expected results (期望的结果)
响应 trigger="hover" 属性
Actual results (实际的结果)
未响应 trigger="hover" 属性
Remarks (补充说明)

当自定义 dots 后，组件会将控制权交给用户，此时想实现 hover 效果，必须用户自己实现：
https://codesandbox.io/s/divine-mountain-3jcwm4?file=/src/App.vue

repo: tusen-ai/naive-ui


text:
New Template Added

name: Pull Request Template
on:
pull_request:
types:
- opened
- synchronize
jobs:
pr-template:
runs-on: ubuntu-latest
steps:
  - name: Check PR title
    run: |
      title=$(git log --pretty=format:%s origin/main..HEAD)
      if [[ $title != *"JIRA-"* ]]; then
        echo "Error: PR title must include a JIRA ticket number"
        exit 1
      fi

  - name: Check PR description
    run: |
      description=$(git log --pretty=format:%b origin/main..HEAD)
      if [[ $description != *"JIRA-"* ]]; then
        echo "Error: PR description must include a JIRA ticket number"
        exit 1
      fi

  - name: Request more information
    run: |
      echo "👋 Thank you for your contribution! To help the reviewer understand your changes better, please provide the following information:"

      echo ""
      echo "## Description"
      echo ""
      echo "<!-- Please provide a brief summary of your changes. -->"
      echo ""

      echo "## Why This PR ?"
      echo ""
      echo "<!-- Why is this change necessary? What problem does it solve? -->"
      echo ""

      echo "## How Has This Been Tested?"
      echo ""
      echo "<!-- Please describe the tests that you ran to verify your changes. -->"
      echo ""

      echo "## Screenshots (if applicable)"
      echo ""
      echo "<!-- If applicable, add screenshots to help explain your changes. -->"
      echo ""

      echo "## Related Issues"
      echo ""
      echo "<!-- If this PR is related to any issues, please mention them using the GitHub issue linking syntax (e.g., 'Fixes #123', 'Closes #456'). -->"
      echo ""

      echo "## Types of Changes"
      echo ""
      echo "<!-- What types of changes does your code introduce? Put an `x` in the boxes that apply. -->"
      echo "- [ ] Bug fix (non-breaking change which fixes an issue)"
      echo "- [ ] New feature (non-breaking change which adds functionality)"
      echo "- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)"
      echo "- [ ] Documentation update"
      echo ""

      echo "## Checklist"
      echo ""
      echo "<!-- Put an `x` in the boxes that apply. -->"
      echo "- [ ] My code adheres to the established style guidelines of this project"
      echo "- [ ] I have conducted a self-review of my code"
      echo "- [ ] I have commented my code, particularly in hard-to-understand areas"
      echo "- [ ] I have made corresponding changes to the documentation"
      echo "- [ ] My changes generate no new warnings"
      echo ""

issue no : #153
@ZapeeoSheikh please Check Let me Know Changes
I have not added image, please add it when your website become ready.

@PatilHarshh thank you for contributing. please resolve the issue so that i can merge it.

authors: PatilHarshh ZapeeoSheikh

repo: tusharzalte/tusharesume


text:
Can pydf generate from URL directly?

In the "wkhtmltopdf.py" file it has mention "Generate a pdf from either a url or a html string", how to pass in generate via URL?

Yes, just try it

is it like this ?
pdf = pydf.generate_pdf("", url="https://www.google.com")

pydf.generate_pdf('https...')

Somehow, my pdf content has the url path instead of the content in the url. Is there anything I am missing?  @samuelcolvin pydf.generate_pdf('https...')

repo: tutorcruncher/pydf


text:
Simplify string representation code using str_pad()

According to the PHP docs, str_pad is available since PHP 4.0.1, so I think it is safe to use it.
reference: https://www.php.net/manual/en/function.str-pad.php
Using str_pad simplifies the code by removing an if branch and a temporary variable, while keeping code readability.

Much better. Thanks!

You're welcome! Somehow I missed the merge notification. Thanks for the package

authors: rodrigopedra tuupola

repo: tuupola/ksuid


text:
🛑 Prometheus is down

In 822d61c, Prometheus (https://prometheus.eighty-three.me) was down:

HTTP code: 404
Response time: 431 ms

Resolved: Prometheus is back up in 9e9aca6.

repo: tuxpeople/monitoring


text:
chore: SOF-1404 bump TSR

includes the ATEM upstreamKeyerId fix https://github.com/tv2/tv-automation-state-timeline-resolver/pull/53

Codecov Report

Merging #227 (38ae761) into staging (f3b70a2) will increase coverage by 5.16%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##           staging     #227      +/-   ##
===========================================
+ Coverage    68.14%   73.30%   +5.16%
===========================================
  Files          278       93     -185
  Lines        34075    24119    -9956
  Branches      4569     2336    -2233
===========================================
- Hits         23220    17681    -5539
+ Misses       10391     6403    -3988
+ Partials       464       35     -429

see 185 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: codecov-commenter ianshade


text:
How to push new data into the graph on the client side?

Hello.
Could anyone help me to understand how to push ohlcv data into the empty chart right from browser?
There is no way from me to get data from vue server, so I want somehow to create a json in browser to push data for processing into the chart
Thank you
P.S. I want to compile tradingvue lib into pure js and use it in browser when page loads

@jokaorgua You can using datacube update real time data. View code example here https://github.com/tvjsx/trading-vue-js/blob/master/test/tests/DataHelper.vue

Thanks for the tip. Im already using tue DataCube in server vue.
I’m more interested in solution for already compiled js code. Something like chart.dc.update but from js on the page

authors: jokaorgua tamanhquyen

repo: tvjsx/trading-vue-js


text:
1.6.4 在 macOS 12.6 上频繁 crash

版本： 1.6.4
macOS： 12.6
附件中是crash log
logs.zip

方便给一个大概的复现路径不

我再观察一下看怎么复现

印象里应该是这样的操作步骤：

安装，保留默认配置，使用iCloud存储
File -> Import -> 选择一个已经存在的 md 文件进行打开 （打开以后就crash了第一次）
删除刚打开的md文件
创建一个新的文件夹，File -> Single Open -> 选择一个md文件 （这里又crash了一次）

然后从Preferences里面把存储为改成本地文件夹，没有发现有crash的问题。

辛苦重新试试这个新包
https://fl-file.oss-cn-hangzhou.aliyuncs.com/upic/iNKDsE.zip

https://github.com/tw93/MiaoYan/issues/169
归拢到这里一起讨论


text:
Form margin not exposed in LESS

https://github.com/twbs/bootstrap/issues/3737

@mdo The forms can be customized easily enough to reduce this when folks need it.

This statement is inaccurate, form control margin is not exposed in the LESS.
.form-control {
     margin-bottom: 15px
}

@mryellow The CSS you refer to no longer exists in Bootstrap v3. We don't set margin-bottom: 15px on .form-control anywhere.

It's in the current master and 3.3.2
https://github.com/twbs/bootstrap/blob/85a6595a716fa6549383356e75c2091bfdfee585/less/forms.less#L200
https://github.com/twbs/bootstrap/blob/v3.3.2/less/forms.less#L200

Your original post says .form-control, not .form-group.

Ahh too right, thanks. I had mistakenly worked around it by overloading form-control instead of form-group.

@cvrebert I can easily add a variable for this to variables LESS file, will it also require being exposed in the customizer or is it automatically loaded?

@kkirsche That's done automatically via the customizer-related Jade Grunt tasks.

Fixed by #15728.

authors: cvrebert kkirsche mryellow

repo: twbs/bootstrap


text:
Consider enabling more new ESLint rules

Refs http://eslint.org/blog/2016/02/eslint-v2.0.0-released#new-rules
Refs http://eslint.org/docs/rules/object-property-newline
Refs http://eslint.org/docs/rules/no-control-regex

CC: @XhmikosR @hnrch02 @juthilo

No new warning with the new rules so far?

Here's a specific proposal: #20076

authors: XhmikosR cvrebert


text:
Collapse prevents radio button update

When using data-toggle="collapse" and data-target on a radio button, the clicked radio button is not checked. See this minimal fiddle: https://jsfiddle.net/p0xkotyr/1/. Reproducible for me in Chrome (54.0), Safari (9.1.2) and Firefox (49.0.2) on OS X 10.11.6.
I didn't find any current open issue on this, just a couple of rather old closed ones:

https://github.com/twbs/bootstrap/issues/1060
https://github.com/twbs/bootstrap/issues/3857

Thanks for taking a look!

Yes it's due to this line : https://github.com/twbs/bootstrap/blob/v4-dev/js/src/collapse.js#L354
IMO, If you want to check the radio button, you have to listen this event show.bs.collapse and checked manually your radio button.
$('input').on('show.bs.collapse', function() {
  $(this).attr('checked', 'checked');
})
.on('hide.bs.collapse', function() {
  $(this).attr('checked', '');
});

I get that, but isn't the point of using data- attributes to avoid the need to roll your own JS? But if this is by design, perhaps it's worth a short explanation in the docs?

As it said in the documentation (See http://v4-alpha.getbootstrap.com/components/collapse/#via-data-attributes) :

Just add data-toggle="collapse" and a data-target to the element to automatically assign control of a collapsible element.

By doing this you didn't declare your Collapse in JavaScript like this $('input').collapse() that's all

The behavior comes from the call to event.preventDefault(); in the click event handler. Is the recommended option to check if the target is a radio/checkbox input, or to actually add custom code to counter the effect by adding a checked attribute manually?
Testing the type of target should not be hard, but would probably require to think about which elements should fall into this list if not just radio and checked.
I have tried @Johann-S 's suggestion but this specific event is triggered on the targeted collapsed element, not the originator. I found the click.bs.collapse.data-api event though, but whatever I tried to do the checkbox doesn't reflect it's checked property or status.

Yeah my suggestion was bad sorry for that but yes what I want to suggest is exactly what you said :

Testing the type of target should not be hard, but would probably require to think about which elements should fall into this list if not just radio and checked.

Closing as a dupe of #22049.

authors: Johann-S mdo sebastienros trusche


text:
Shim for easy upgrade from v3 to v4

This will make it very easy to still use bootstrap 3 while progressively migrating to v4.
The Font Awesome theme has a nice example of this at https://fontawesome.com/how-to-use/upgrading-from-4

Not sure if we will have time to implement that :thinking:

Not sure whether improving Bootlint in this direction wouldn't be a more reasonable (and less error-prone) approach, I am personally no friend of such client-side shims.

Sorry, but this just isn't feasible or productive—for us or folks using Bootstrap. v3 doesn't go away, and v4 is such a sweeping overall. Providing a shim would be bloated, slow, difficult to produce, etc.

OK. Thanks.

authors: Herst JahlomP Johann-S mdo


text:
Improve accessibility for anchor tag

Error Message :
Content inserted with CSS is not read by some screen readers, and not available to people  who turn off style sheets.
Not compliant to :
WCAG 2.0 A F87 Section 508 (2017) A F87
Content :
.custom-file-input:lang(en)~.custom-file-label::after{content:"Browse"}
a[href]:after {
content: " (" attr(href) ")";
}
Impact on users :
•NVDA 2018.4 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
•NVDA 2017.3 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
•NVDA 2016.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
•JAWS 2018.1811.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
•JAWS 18.0.5038 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
•JAWS 17.0.2619 IE11 Windows 10 Reading: Text inserted by CSS content property not read

While it's true that for the custom file uploads, IE11 won't announce the "Browse" ... it also doesn't announce "Browse" for regular <input type="file"> anyway, so it's not a major change in user experience for the few users still using this now rather outdated browser.
As for the a[href]:after, that's part of the print stylesheet, so irrelevant when it comes to screen reader support.


text:
Add a namespace for classes

How do you feel about adding the namespace for classes as you have done it for CSS variables?

Duplicate of #29547.
It won't happen: https://github.com/twbs/bootstrap/issues/29547#issuecomment-561025723
You will need to handle it with post-processors.

I think we can close this one?

Closing for now. Maybe in a future major release.

authors: Sir-Genius florianlacreuse mdo


text:
Add js sourcemaps to build process

fixes #16583
The cssmin task supports this as well but I figured that would be better in its own PR

Punting per my comment in #16583.


text:
Fix position: sticky

.sticky-top is deleted after compilation.

No, it's not:
https://github.com/twbs/bootstrap/blob/f7b55da4509e62b559f1e8181cf4b03e964775a4/dist/css/bootstrap.css#L7796-L7803

.sticky-top is removed, leaving the wrong css code, if you use only the scss compiler

authors: MartijnCuppens ilcomp


text:
Fix reboot for placeholder links

Fixes #28010

native: https://codepen.io/anon/pen/eqdNVZ

current: https://codepen.io/anon/pen/oKzXGG

after: https://codepen.io/anon/pen/PMGqaX

I'm not sure should backport this to v4.

Should we backport this?

Yup. I would wait for @patrickhlauke's aproval before merging this, just to be sure.

so if it's a placeholder, but it has been explicitly made focusable with tabindex="0" or any tabindex value > 0, this would suppress any focus indication? if so, not sure i'd agree...focus needs to be shown somehow.

@patrickhlauke The after behavior is:

Windows 10, Chrome 75

This needs to be manually backported to v4-dev. Can someone do it?

urgh only noticed now, should probably also amend the preceding comment in the scss that talks about tabindex...

This needs to be manually backported to v4-dev. Can someone do it in my v4-dev-xmr branch?

done https://github.com/twbs/bootstrap/pull/29162

authors: MartijnCuppens XhmikosR patrickhlauke ysds


text:
Enable OpenSSF Scorecard Github Action and Badge

Signed-off-by: Joyce Brum joycebrum@google.com
CC @XhmikosR
Description

Scorecards.yml file enables the Scorecard action to run on push to main and once a week (important for some checks like contribution check)
Readme file with badge from shields.io

Any doubts or concerns please let me know.
Motivation & Context

Closes #37343
It enables the OpenSSF Scorecard Github Action and Badge to help you to ensure the project will continue to follow the open source best practices or even improve any possible practice to avoid security risks and vulnerabilities.
Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[X] I have read the contributing guidelines
[X] My code follows the code style of the project (using npm run lint)
[X] My change introduces changes to the documentation
[X] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://github.com/joycebrum/bootstrap#status
Related issues
#37343

@mdo: What's your take on this?
I removed the link since there isn't a human readable page to link to.
Overall, the checks are OK, I mostly disagree with the Actions pinning for the reasons I mentioned above. The other things are generally considered good practices.
That being said, 7.2 is not good enough either and it's mostly caused by Actions not being pinned AFAICT.

BTW, maybe we could link to https://bestpractices.coreinfrastructure.org/en/projects/2930 and add the best practices badge? It seems @bardiharborow set this up, not sure how to get updated results or access ourselves.

About wheter the Pinned-Dependencies has a big weight in the current score, I've made some calculations:
“Critical” risk checks are weighted at 10
“High” risk checks are weighted at 7.5
“Medium” risk checks are weighted at 5
“Low” risk checks are weighted at 2.5
This we would have:
( 10 * (Dangerous-Workflow) + 7.5 * (Binary-Artifacts + Branch-Protection + Code-Review + Dependency-Update-Tool + Maintained + Signed-Releases + Token-Permissions + Vulnerabilities) + 5 * (Fuzzing + Pinned-Dependencies + Packaging + SAST + Security-Policy) + 2.5 * (CI-Tests + CII-Best-Practices + Contributors + License) ) / (10 + 60 + 20 + 10)
Then, considering the current score:
$$ (100 + 7.5*(10 + 8 + 9 + 10 + 10 + 0 + 0 + 10) + 60 + 75) + 5 * (0 + 7 + 10 + 10) + 2.5 * (10 + 2 + 10 + 10)) / 100 $$
$$ (100 + 7.5 *  57 + 5 * 27 + 2.5 * 32 ) /100 = 7.4 $$
Even if the Pinned Dependencies was a 10, the score would only go to 7.6.
According this, the best approach would be:

Signed-Releases
Token-Permissions (Quick-win)
Fuzzing
CII-Best-Practices

Working only to get this four to 10 would increase the score to 9,6

@XhmikosR it says that everyone with commit access to the repository should have access already, but if not, I can manually add user IDs to the access list.

authors: XhmikosR bardiharborow joycebrum


text:
fix  data-bs-theme="dark" on component carousel itself

Description
the description says
"Instead of adding .carousel-dark, set data-bs-theme="dark" on the root element, a parent wrapper, or the component itself. "
but it does not work on the element itself

Motivation & Context

Type of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[ ] My change introduces changes to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-{your_pr_number}--twbs-bootstrap.netlify.app/

Related issues

Thanks for this! Also noting that we may need to do this on other components.

that can be, at modal and card the text color are not taken over, in addition a workaround #38212

authors: jonnysp mdo


text:
fixup! Add changelog to the extra-source files.

I'm merging this fix w/o review, as it just fixes syntax error in cabal file.

repo: tweag/network-transport-zeromq


text:
blinking text on fast background change

I am using for this date the latest version of "mIRC v7.63" + "DCX dll v3.1-222-g4063583"
There is one problem I am facing while writing my script.
If you create a large list from a set of controls for text in a dialog,, then make it so that when you hover the mouse, the background of the text and control changes to another, and when you remove the mouse, the background color changes again, then when you quickly fast move the mouse down and up, the text in these controls starts to wink, also when stretching and resizing the dialog, which is very conspicuous and doesn't look good. The same problem is observed with other controls where there is text and the ability to change the background under the text, or when it becomes transparent, for example, when using a control for an image with a transparent style and the key (+b), as well as an picture in it with the "png" extension, then when the background color on the parent element changes, the image also starts flickering.
Is there a solution to this problem to remove flickering when changing item parameters quickly or is it a common bug in dll?
Here is a test piece of script to recreate this problem (To run the script click on "F4"):
alias F4 { newdialog }
alias newdialog {
  if ($dialog(newdialog)) { .dialog -x newdialog | halt }
  .dialog -mp newdialog newdialog
}
dialog newdialog {
  title "New Dialog"
  size 350 400 300 430
}
on *:dialog:*:init:*: {
  if ($dname == newdialog) {
    .dcx Mark $dname newdialog_work
    .xdialog -b $dname +tyz
    .xdialog -g $dname +b $rgb(20,20,27)
    newdialog_panel $dname 20
  }
}
alias newdialog_panel {
  var %nd_np 0 | var %nd_y 10 | var %nd_q 1 | while (%nd_q <= $2) {
    inc %nd_np
    .xdialog -c $1 %nd_np text 10 %nd_y $calc($dialog($1).cw -20) 20 center
    .xdid -f $1 %nd_np +ab ansi 11 Tahoma
    .xdid -C $1 %nd_np +bk $rgb(35,35,35)
    .xdid -C $1 %nd_np +t $rgb(255,199,0)
    .xdid -t $1 %nd_np DialogTextTest %nd_q
    inc %nd_q | inc %nd_y 20
  }
}
alias newdialog_work {
  if ($2 == mouseenter && $3 > 0) { .xdid -C $1 $3 +bk $rgb(50,50,50) }
  if ($2 == mouseleave && $3 > 0) { .xdid -C $1 $3 +bk $rgb(35,35,35) }
}

This does happen some times, seems to be a drawing issue/delay, try using the noformat style to speed up drawing if you arn't using mirc ctrl codes.

maybe fixed in dev57 rel, try with doublebuffer style & see.

OokEek, thanks for your reply. For testing, I specifically created 2 identical dialog boxes, only in one I left everything as it was, and in the other I added new styles. Setting the style "noformat" helped to significantly reduce the visibility of flicker, but a small fraction still remains. If, in addition to this, add the "doublebuffer" style, then visible braking and even flickering of the already black stripe begins, which, as it were, lags behind the movement of the computer mouse. In principle, this is tolerable and little noticeable, but it will be better to if possible if you can completely eliminate this flaw so that there is no flicker.
P.S. In fact, I have a lot of questions and suggestions for improving your DLL, so if I have some free time, I will leave new posts here from time to time.

authors: EpicNet OokEek

repo: twig/dcxdll


text:
feat(pixels): add pixel for wobbol

Checklist

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

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

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

I'm still here

Because it is supposed to be automatically merged. I have written an issue here
#3941 about it. I would love to fix the issue, but I haven't seen the GitHub bot code anywhere.

repo: twilio-labs/open-pixel-art


text:
akka routes not matching input with default property

I have an API where the Create operation consumes a resource without an ID field (the server generates it) and where every operation returns that same resource with an ID field.
definitions:
  TheResource:
    discriminator: type
    type: "object"
    required:
      - "type"
    properties:
      id:
        type: "string"
      type:
        type: "string"
  ...

Guardrail generates an id field of type Option[String].  If I change the id property in swagger to have a default: "" and/or add id to the list of required properties, Guardrail changes the case class accordingly (either as id: Option[String] = Option("") or id: String = ""), but the generated routes don't match requests without an ID.
I think this should be possible in swagger 2 and 3.  Is there an extra hint I should be providing to the akka server routes generator?

Hey @dsilvasc, thanks for the report! I expect this is due to the generated decoders not explicitly handling default values.
This is similar to #94, with the unfortunate workaround being (as you may already suspect) manually handling these use cases for now.
I think the fix for this is much more straightforward than read/write-only properties, as we can always fall back to a default value.
Taking a similar strategy to x-scala-empty-is-null seems like a good direction for a fix:
          implicit val decodePet = new Decoder[Pet] {
            final def apply(c: HCursor): Decoder.Result[Pet] =
              for (
                name <- c.downField("name").withFocus(j => j.asString.fold(j)(s => if (s.isEmpty) Json.Null else j)).as[Option[CustomThing]]
              ) yield Pet(name)
          }

could easily be modified with j.asString.orElse(...) without negatively impacting other functionality.

authors: blast-hardcheese dsilvasc

repo: twilio/guardrail


text:
Circular reference when creating a BYOC trunk with a sip domain as both "from" and termination domain

Issue Summary
Circular reference when creating a BYOC trunk with a sip domain as both "from" and termination domain
Steps to Reproduce

create a terraform file with the resources below

Code Snippet
resource "twilio_voice_byoc_trunks_v1" "my_byoc" {
    from_domain_sid = twilio_api_accounts_sip_domains.my_sip_domain.sid
}

resource "twilio_api_accounts_sip_domains" "my_sip_domain" {
  domain_name = "myexample.sip.twilio.com"
  byoc_trunk_sid = twilio_voice_byoc_trunks_v1.my_byoc.sid
}

Exception/Log
Error: Cycle ...

Technical details:

terraform-provider-twilio version: 0.8.12
terraform version: 1.0.11

Ran into this today, it's something that is completely possible to do from the UI but not from terraform.
I was hoping that there would be a work-around of having separate "from" and "termination" domains but this doesn't seem to be possible either at the moment which makes it afik impossible to configure the from domain with terraform

This issue has been added to our internal backlog to be prioritized. Pull requests and +1s on the issue summary will help it move up the backlog (ref: DI-1325).

authors: childish-sambino russell-wave

repo: twilio/terraform-provider-twilio


text:
Deploying server.js on production

Question
I've used server.js as a wrapper for calling my own API with my own accessToken. It's the API that acts as the token server, but i'm using this proxy so that my API token is kept secret from the frontend.
In my server.js I have:
const apiUrl = process.env.TALKED_API_URL;
const apiKey = process.env.TALKED_API_KEY;

app.get('/token', (req, res) => {
  const { identity, roomName } = req.query;

  const data = {
    identity,
    roomName,
    key: apiKey,
  };

  axios
    .post(apiUrl + '/video/token', data)
    .then(result => {
      res.send(result.data);

      console.log(`issued token for ${identity} in room ${roomName}`);
    })
    .catch(error => {
      console.log(`failed to get token for ${identity}`);

      res.status(500);
      res.send();
    });
});

The issue is when I deploy this using the command npm run deploy:twilio-cli -- --override it's clear that the server.js is running and it's using the serverless version of /token. How can I use my custom code in server.js? Do I need to split it up into serverless functions? OR can i somehow get server.js node server running on Twilio?

Thanks for the question @baj84!
The server.js file that is in this repo is for local development only. It is what is run when you run npm start. It is not the code that is deployed when you run npm run deploy:twilio-cli.
The code you are looking for is in our plugin-rtc repo. Specifically, this file.
You can configure the Twilio CLI so that it runs a local version of plugin-rtc. You can then modify the local code for plugin-rtc, so when you run npm run deploy:twilio-cli, it will run your modified code. There are some instructions in the README.
Additionally, we added a new feature to the plugin-rtc repo that you may like! First, make sure you have the newest version of the plugin installed with twilio plugins:update. Once this is finished, deploy a new video app. Once the deployment is complete, you'll see a message like this in your console:
Edit your token server at: https://www.twilio.com/console/functions/editor/ZSxxxxxxxxxxxxxxxx/environment/ZExxxxxxxxxxxxxxxx/function/ZHxxxxxxxxxxxxxxxx

Just click on that link and it will take you to our Functions Editor inside the Twilio Console. There you'll be able to edit the live token server right inside your browser.
Let me know how this works out for you! And please let me know if you have any further questions.

Thanks @timmydoza for your help. I checked out plugin-rtc into my directory and tried to link it, but I got the following error:
plugin: @twilio-labs/plugin-rtc
root: /Users/ben/code/talked/talked-video/plugin-rtc
See more details with DEBUG=*
(node:63626) Error Plugin: @twilio-labs/plugin-rtc: could not find package.json with {
  type: 'dev',
  root: '/Users/ben/code/talked/talked-video/plugin-rtc',
  name: '@oclif/plugin-help'
}

Also, once this is working and I modify the video-token-server.js with my own code will it automatically get added as a function when I do a deployment?
And one final question :) I don't have a need for this passcode validation - am I safe to remove it?
My authentication logic is essentially a token in the URL string (each party is given a unique token), that is then sent to my own API layer which validates the users token against the DB and if valid will then create the room using Twilio SID + Secret - Is this an OK way to do things?

I had the same question as the OP. Just noting that the file mentioned in @timmydoza's comment is no longer there: https://github.com/twilio-labs/plugin-rtc/blob/master/src/video-token-server.js

I had the same question as the OP. Just noting that the file mentioned in @timmydoza's comment is no longer there: https://github.com/twilio-labs/plugin-rtc/blob/master/src/video-token-server.js

authors: adamq-q baj84 timmydoza

repo: twilio/twilio-video-app-react