text:
codespan-reporting and codespan-lsp compatibility

I've been using codespan and codespan-reporting for error reporting for my CLI. I'm now working on an LSP extension and want to use codespan-lsp to covert to the proper LSP types, but it seems like codespan-reporting doesn't play well.
For example, I have a custom file system abstraction that implements the Files trait but codespan-lsp utilities like byte-span-to-range expect a reference to codespan::Files. They also expect a Span but codespan-reporting's Label uses Range<usize>.
Are there plans to align the packages one way or the other, or should I just roll my own diagnostics object and have compatibility layers for codespan-reporting and codespan-lsp?

Thanks for your issue!
I've been trying hard to de-emphasise codespan, and emphasizing codespan-reporting, because I've found it rather challenging to create a one-size-fits all thing for handling files. This was part of the work I did in inverting the dependency between those two crates. Eventually I'd like to deprecate codespan, if I'm honest.
codespan-lsp currently depends on codespan though, so sadly you are tied to using codespan if you want these conversions. It would be cool if there would be some way to make those conversions easier to implement for custom file system abstractions though! I'm still not sure where they fit though…

@brendanzab would you be open to including some LSP utilities in codespan-reporting? It might make sense to have codespan_reporting::lsp to mirror the codespan_reporting::term backend. I'd be happy to help here if you're interested.

Ohhh, that is a good idea, yes! Now I have a better handle on the lsp-types version ranges this could also be helpful too - it was a constant pain to keep having to update them.

I'd definitely be open to collaborating on this! Feel free to chat on Gitter or the the #langdev channel on the rust community discord if you like!

authors: aweary brendanzab

repo: brendanzab/codespan


text:
implement remove-by-model-name. Make backups of configs

I had several hundred iBeacon devices to get rid of, all with long hex-string names, so I extended your code to do model names as well. Minimal change w/o restructuring completely. In the spirit of it being a power-user tool, but even power users can sometimes shoot themselves in the foot, I provided one level of toe-armor: it makes a backup of the three config files.

Looks good, though I haven't had occasion to use it. Does it still work for basic removal?

source: gharchive/pull-request

authors: brettonw reedstrm

repo: brettonw/Remove-Home-Assistant-Device

license: MIT

license_type: permissive

license_source: github-api


text:
PrometheusMetricsTrackerFactory should support custom registries

Prometheus collectors can typically be registered either in the default registry or in a user supplied registry. As the default registry is basically a singleton maintained in a static field of Prometheus' CollectorRegistry, using it in non-trivial class loader scenarios (like in a Java EE servers) can be problematic. Therefore, I think that providing support for custom registries is very valuable.
I'm aware of the problems discussed in #940 and #851 regarding the difficulties to maintain single instances of collectors as required by the Prometheus Client API, but I think there must be a way to fix it. If we force users to use a single MetricsTrackerFactory for each CollectorRegistry, this could actually be very simple.
There should also be a way to deregister collectors in a clean way. Something like PrometheusMetricsTrackerFactory.close(). It is important to support this especially if you create and destroy pools at runtime.
I would love to work in this and provide a pull request if you are interested. But we should merge #940 before as it already improves the overall structure of the code.

Hi @chkal !
Could you please have a look on this PR https://github.com/brettwooldridge/HikariCP/pull/1331 ?
I've introduced the ability to deregister collectors when connection pool is shutting down.

@apodkutin Thanks. I'll try to find some time in the next days to have a deeper look this. But I'm not very familiar with the details, so I may not be the best person for a review.

Now that #1331 has been merged and released, can this issue be closed?

Now that #1331 has been merged and released, can this issue be closed?

I second this. @brettwooldridge Please close this issue.

source: gharchive/issue

authors: apodkutin chkal djbehnke edysli

repo: brettwooldridge/HikariCP

license_source: bigquery


text:
Fix #224 - aliased column in function

Fixed the aliased column in function call issue. When in a function call, columns must not have alias. Added some tests as well.

Hi @brianc. More conflicts resolved. I think this one is good to merge too

:dancer:

authors: brianc edudutra

repo: brianc/node-sql

license: mit


text:
Jitter when animating via transformNode.scale

Hey!
I'm currently trying to put together a project using masking and we've run across an issue wherein setting scale on a transformNode causes a visible jitter.
This behavior seems to become worse the more nodes are added to the graph.
Essentially we are running an requestAnimationFrame loop which sets a new value using
transformNode.scale(value)
on every frame. What we observe is either stale values, or conflicting values within the transform node.
I've attached a video of the observed bug. This doesn't seem to be performance related as the page runs at a solid 60fps in the test.
I'd be happy to try to contribute a fix if you can point to me in the right direction in the source. Any help on this one is greatly appreciated as I've got a delivery coming up very soon.
jitter_capture.mp4.zip

Hey @tencircles. That's interesting. Do you have a reduced code sample you can share? Maybe a jsbin, codepen or something live like that?
Does it only happen with whatever effects you're using for masking?
Have you tried it in Firefox as well?
Does it make a difference if you change the resolution of the source image/video?

Hey @brianchirls, thanks for the response!
I've set up a test repo here
https://github.com/tencircles/seriously_mask_test
The javascript code is here:
https://github.com/tencircles/seriously_mask_test/blob/master/js/index.js
And you can find the code live here:
http://45.55.37.142/seriously_mask_test/
The jitter seems to be most prominent when using the translate method of the transform2d node.
Steps to reproduce:

Check do_translate
Set start/end_translate to any values
Click 'tween'

There seems to be an observable disparity between the numbers we send (viewable under 'translate' in the GUI), and the result on screen. You can see both the scale and translate input values on screen.
You can find a screen cap showing the disparity between input values on and on screen result here. If you step through frame by frame it's really easy to see.
http://45.55.37.142/seriously_mask_test/captures/chrome_counter.mp4
The behavior seems to be the same in firefox and in safari.
Tried changing images, didn't have any effect. Seems to be limited to the transform node, not sure if the behavior is present in other nodes.
Let me know if I can dig anything up!

Okay, first of all, this is a pretty cool-looking composition. I'm looking forward to seeing the finished product.
This is a very strange one. But there is definitely something going wrong here - you're not imagining things. ;-) I'm not able to replicate your problem on my machine, but I can see in your video that the "A" is moving backwards, which it obviously should not do. I've run CPU profiles, timeline recordings and screen captures; I even tried CPU throttling. Apart from a few janky frames, this does not appear to be a performance issue. That wouldn't explain backwards movement anyway.
I wonder if something weird might be going on with TweenMax. It's hard for me to tell for sure, because the code is minified and I'm not familiar with the API or behavior of that library. In theory, it might be possible that two requestAnimationFrame cycles are running and fighting over setting different values on the same target object. A later value might be smaller than the previous one, and the difference might be < 1/1000, in which case you would not see it show up in your scale value text. But the difference might be magnified enough to be visible in the canvas by rounding of pixel positions and/or floating point quirks. I know it sounds like a bit of a stretch, but it's all I got at the moment.
Are you sure you're cleaning up the timeline properly?
Is it possible that this only happens after you've gone through the animation at least once? Or does it happen on the first time you play through it?
Since I can't replicate, I can't do the debugging for you, but I can point you in the right direction. I suggest two things:

Set a conditional breakpoint at line 5933 of seriously.js with this code: translateX < 499 && x < translateX. If it breaks, you'll know that the incoming value is less than the one before it. (This will only work if you let the animation play all the way to the end.) You can see in the call stack where that happened. If it never breaks and you still see the A going backwards, that will tell us we need to look deeper into Seriously.

Try making a reduced test without TweenMax or even dat.gui. Write your own code in the callback passed to seriously.go() to determine the x value of the translation. If you still have the problem, then we'll know for sure the bug is in Seriously.js. If not, then it's more likely that something is going on with TweenMax.

Can you report the results back here?

Set a conditional breakpoint at line 5933 of seriously.js with this code: translateX < 499 && x < translateX. If it breaks, you'll know that the incoming value is less than the one before it. (This will only work if you let the animation play all the way to the end.) You can see in the call stack where that happened. If it never breaks and you still see the A going backwards, that will tell us we need to look deeper into Seriously.

Just tried this out, but the breakpoint doesn't trigger. You can also seek frame by frame in the video above to see the values being passed to seriously. You'll see the values on screen going up constantly, but the result rendered jumps back.
It's very difficult to see with the naked eye, so this might be occurring for you just not quite as noticeable perhaps? For me most of the time it looks like slight performance jank, but at a 60fps screen cap you can actually see it's moving backwards.

Try making a reduced test without TweenMax or even dat.gui. Write your own code in the callback passed to seriously.go() to determine the x value of the translation. If you still have the problem, then we'll know for sure the bug is in Seriously.js. If not, then it's more likely that something is going on with TweenMax.

Rather than coding the manually, I just added all values sent to seriously to an array with timestamp + value. Since all values we send are send through a single point (line 112 in the example above), we can be 100% sure that nothing else is setting values or calling methods within seriously. Checking the values sent both manually and programmatically it looks like we are sending values which steadily increase over time. If you want to have a look at the number let me know.
Any ideas on where to look within seriously to try to catch this? Stale matrix values maybe?

Just pinging this. Any clue where we could start looking?

I was only just able to replicate this. Earlier efforts, even with screen recording, didn't show the problem.
It's not jank, because that wouldn't be moving backwards. Also seems unlikely that stale matrix values would cause it to go backwards. I checked most of the matrix values of the different, and they all seem correct.
Another hunch I had is that something weird is happening with ping-ponging textures. Some effects do that, but not the ones you're using. I suppose it's possible that something weird is going on with buffering in the GPU driver, though unlikely. What machines have you tested this on?
I did notice that you're using a lot of "layer" effects that don't seem necessary, either because they only have a single source input or they have 2 sources but only one of them is in use. Maybe there's something going on there? Is there a reason for that? Maybe if you can eliminate those nodes and it fixes the problem, that might get you far enough to deliver your product and it'll give me/us a starting point to hunt down whatever bug.

Hello Brian,
We've ran some stress tests to try and see what nodes specifically could be causing the issue.
For each of these tests, we animate the letter by calling the letter transform node's translate method within the callback passed to seriously.go().
All tests have jittering when animating. The jittering is sometimes limited, sometimes erratic, seemingly without taking into account the level of complexity. The video captures in the zip have all been made on Chrome OS X, the behavior is exactly the same in Safari. On Chrome Windows, the jittering is still present but much more subtle.
We haven't been able to identify what worsens or betters the jittering as the behavior seems to be random. To clear any possible external causes, we are not updating the translate method's x position with TweenMax anymore.
To answer your question, we are using layer nodes so that we can control each layer's opacity level independently.
You can download the zip and run the directory on a local server.
Here's the routing for each of these tests, in order of complexity.
simple_test_step1_noReformat:

letter source image => letter transform node
target canvas (source: letter transform node)

simple_test_step1:

letter source image => letter reformat node => letter transform node
target canvas (source: letter transform node)

simple_test_step2_noReformat:

letter source image => letter transform node
color node
layers node (source0: color node, source1: letter transform node)
target canvas (source: layers node)

simple_test_step2:

letter source image => letter reformat node => letter transform node
color node
layers node (source0: color node, source1: letter transform node)
target canvas (source: layers node)

simple_testBug:

letter source image => letter reformat node => letter transform node
color node
layers node (source0: color node, source1: letter transform node)
starry sky source image => starry sky reformat node
gradient wipe (source: starry sky reformat node, gradient: layers node)
target canvas (source: gradient wipe)

Do you have any suggestions as to what we could do?
Thank you very much
seriously_stressTests.zip

Okay, thanks for these reduced test cases. I can work with this. I have some ideas of where to start and will dive into it as soon as I can.

@brianchirls Any way I can help out with this one? I've poked around in the source, but it's really just guesswork.

Hi Brian! Have you had any chance to look into this? Can we be of any help?

authors: brianchirls johanbelin tencircles


text:
AAD SignIns Insights

I wonder if there would be an interest for such a module. It's essentially a similar concept of what we have for analysts in the entity page available for automation and a bit of what we have in UEBA.
Takes a user and return stats such as:

Last successful logon data (timestamp + other metadata)
Last failed logon data
Usual user-agent-string data
Usual contries/IPs

If there is a cloud-logon-session present in the entities (case of an AAD Protection alert), return all the info about this particular login.
That last one maybe could be added to the AAD Risk Module instead.

I like the idea, would this be a new module or perhaps an extension to the capabilities of the AAD Risks?  It may make it too complex though if we add it... not sure off hand.
One issue, the cloud-logon-session is not passed from the incident trigger so you have to go back into SecurityAlerts to get it.... this is one of the reasons for #205 so you can use the KQL module to lookup the incident easily and work from there

Maybe also return a table of last successfull access per app?

possibilities to include:

Conditional access failures (and the policies that failed)
Named locations the user has been seen from
Device join status of the signins
password resets or other interesting admin actions on account

insights about signin hours

(although we would need to define what baseline could be used to determine out of character behaviors)

authors: briandelmsft piaudonn

repo: briandelmsft/SentinelAutomationModules


text:
publish to npm

so ppl can npm install selectize --save :+1:

Caved in and published it: https://www.npmjs.com/package/selectize

:+1: Thank you :)
On Thursday, January 29, 2015, Brian Reavis notifications@github.com
wrote:

Closed #604 https://github.com/brianreavis/selectize.js/issues/604.
—
Reply to this email directly or view it on GitHub
https://github.com/brianreavis/selectize.js/issues/604#event-227320904.

--
~ BE*Kind . kn0wledge 1s p0wer ~

authors: brianreavis gdibble


text:
Fix removed task file include

Fix bug introduced in : fb936053af1663abe4557befb4db36a845043c3a
I tested this is working on a single node install (ubuntu 17.04)

Our fixes just crossed as I just fixed this as well and made a new release.

authors: brianshumate vincent-legoll

repo: brianshumate/ansible-consul


text:
Proper save time handling

Finally resolve the TODO for reading save time

use chrono::DateTime for parsed save time
if save does not have a time, use current time when writing

Result of read_json example
{
  "version":10,
  "game_version":6781,
  "map":"Plate",
  "description":"",
  "author":{
    "name":"x",
    "id":"3f5108a0-c929-4e77-a115-21f65096887b"
  },
  "host":{
    "name":"x",
    "id":"3f5108a0-c929-4e77-a115-21f65096887b"
  },
  "save_time":"2021-07-10T22:22:49.135Z",
  ...
}

I made the chrono and uuid imports pub use so that dependent crates can use them without adding whole crates to their Cargo.toml.
Otherwise, this is great. Thanks!

authors: Kmschr voximity

repo: brickadia-community/brickadia-rs


text:
Add depth check for brace and paren to fix #297

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
This patch added a depth check for brace and paren to fix incorrect tag value parse.

Unfortunately I found that the gosec issue and failed tests also exist in the main branch. I'll try to fix them in this pr but cannot guarantee it.

I've passed the unit tests and integration tests on my machine, and I've fixed gosec issue, could we run CI for this pr please? Thanks.

Sign off, I've passed all unit tests and integration tests on my machine, and I've fixed gosec issue, could we run CI for this pr please? Thanks.

Hi @nimrodkor , would you please give this pr a review? Thanks!

Hi, I've solved the conflicts, can anyone give this pr a review? Thanks.

repo: bridgecrewio/yor


text:
Publish v6.0.3

Publishes v6.0.3

Publishes fixes for all v.6.0.3 milestone issues

ran across this when I toggled theme...is correct with the white-ish?

@jeffvg for that section it's supposed to be a random image. It's just not rendering for you for some reason so I think this is ok for now. There's no styles or anything doing that. I assume that's just what happens when an image doesn't render.

authors: daileytj jeffvg


text:
TableSortLabel should not be hidden when mouse is not hovering on it

Describe the desired behavior
When a .MuiTableSortLabel is not hovered on, the arrow should have the ~disabled color~
(edit: should be a "disabledBackground" color of Gray500@12% for light theme, and a Black200@24% for dark theme).
When it is hovered or in-use, the label should be text.secondary
Describe the current behavior
The arrow has an opacity 0 on it when not in use.

Additional Context
This will be part of the Tables effort.

2633

@huayunh Shall we close this, as PR has been merged?

authors: bkarambe huayunh

repo: brightlayer-ui/react-themes


text:
Weatherflow Hourly based Forecast: Unknown

As visible in the following screenshot, I sometimes get 'unknown' ('Inconnu' in French) as the current weather condition:

I get this for a few weeks/months now. Not sure if it was caused by a change in this plugin or if Weatherflow changed something in their API. One of the statuses is probably not mapped properly. I didn't manage to find which one at the moment. Looks also like there is no French translation in this plugin so I guess the value "Inconnu" comes from HA directly.
Looking at the code, I guess you take the value from "icon" in "current_conditions" from /better_forecast. I'll see if I can find the value reported by Weatherflow API when the problem occurs.
There is nothing in HA's logs by the way.

Duplicate. Sorry, Github had a hiccup.

repo: briis/hass-weatherflow


text:
Discord Bot

Description
Create a new Discord Server for Vike, and use/create a Discord bot to teach users about https://github.com/brillout/vite-plugin-ssr/discussions/526.
Having a cozy firechat-like place to casually chit-chat about general topics could be lovely. Example use cases:

Show us what you're building (startup, dev tool, Vike extension, etc.)
Philosophical discussions about the future of programming and/or Vike (e.g. vertical integration vs do-one-thing-do-it-well)
News
Etc.

It's paramount that users don't ask for help in that space. Therefore I think a bot is necessary to to prominently show the rules of https://github.com/brillout/vite-plugin-ssr/discussions/526 with maybe (if possible?) a checkbox "I've read the rules" that users have to check before being able to start chatting.
Contribution much welcome to point us to a Discord bot that does this, or maybe implement one? I'm unfamiliar with Discord's bot API.

I express interest in such a bot for inlang

Closing as we don't need this anymore.

authors: brillout samuelstroschein

repo: brillout/vite-plugin-ssr


text:
Show max depth or prevent drop on folders

I've got a tree that has categories and within those there are child links. I render two different trees, one that shows just the top level categories (and I want it only to ever display the root level nodes) and one that when you select a category shows the children of the selected category. Imagine it's a bit like windows explorer with 2 panes, and the left pane only ever shows the top level items.

This is all working great apart from one small thing! :)
If you drag within the top level category tree and drop onto one of the other categories, it then opens the node and shows all the sub items.

Is there a way you can tell a tree to allow drag and drop, but not to automatically open the folders if you drag something into it OR only ever show a max-depth of children (so you could set it to one for example)
I'm using a controlled tree and have my own handlers for onMove etc.
I hope that rather convoluted explanation makes sense... Thanks for any help, it's a terrific package!

I managed to get a solution and tackled it in a different way. What I do is pass a modified version of the top level node data into the left hand tree where I strip all the children from the array. That makes it behave as leaf nodes, so no folder opening!

Great! Glad you found a solution. I love seeing screenshots of people using the package. Happy coding.

authors: jameskerr theearlofsandwich

repo: brimdata/react-arborist


text:
Replace zio/parquetio with zio/arrowio and pqarrow

We can replace the Parquet reader and writer in zio/parquetio with a combination of zio/arrowio and github.com/apache/arrow/go/v11/parquet/pqarrow, and we probably should since

it'll let us remove about 750 lines from zio/parquetio,
the Arrow Parquet implementation will probably receive more attention the one we're currently using, and
it fixes #764.

Verifications of this change are in https://github.com/brimdata/zed/issues/764#issuecomment-1526667106 and https://github.com/brimdata/zed/issues/4527#issuecomment-1526671541. Thanks @nwt!

authors: nwt philrz

repo: brimdata/zed


text:
Filter based on Gaussianity

We filter targets with extreme variance, the idea being that tangent normalization did a poor job with these and our model is unreliable for them.  However, issue #378 will likely go a long way toward making this less of a concern.  One thing we don't filter on and perhaps should is not how much variance remains after tangent normalization but how Gaussian the coverage looks after tangent normalization.  Since our model assumes Gaussian copy ratio this amounts to filtering out targets for which our model is unsuitable.
We could implement this, for example, by filtering on the Anderson-Darling test statistic for each target.

Obviated by new coverage model.

authors: davidbenjamin samuelklee

repo: broadinstitute/gatk-protected


text:
github video player having issues when playing video

Describe the bug
Video keeps restarting or seizing the volume button and playing with no sound
Desktop (please complete the following information):

chrome, edge

Additional context
Suggest the video is moved to youtube and displayed in the readme

@ukpagrace  This is regular GitHub behavior 🙏

authors: Shchepotin ukpagrace

repo: brocoders/nestjs-boilerplate


text:
Honkai Star Rail Support?

With the recent launch of Honkai Star Rail, seems adding it would be really easy.
https://act.hoyolab.com/bbs/event/signin/hkrpg/index.html?act_id=e202303301540311&bbs_auth_required=true&bbs_presentation_style=fullscreen&lang=en-us&utm_source=share&utm_medium=link&utm_campaign=web

yes please, add Star Rail too

authors: Seantourage ShatteredGod

repo: brokiem/auto-hoyolab-checkin


text:
refactor gpkg_write()

[x] vector write not working properly anymore
[x] better handling of list input for naming feature / tile sets / data_null
[x] basic post-processing/validating of result
[x] tests

I am happy with the functioning of gpkg_write() and think it is now more robust and better documented. Will create a new issue for the idea of validating geopackages.

repo: brownag/gpkg


text:
License / publication on hex

Hi brpandey,
thanks for this implementation. Is there any chance of publishing this on hex? And/or, could you put an explicit license on the code?
Thanks in advance
arnomi

https://hex.pm/packages/interval_tree

authors: arnomi brpandey


text:
Test assets folder copied in public folder on production env

In previous versions, too. Today one is 1.17.20

Change the assets convention in your config to be more specific, or rename the assets dir you don't want copied.

repo: brunch/brunch


text:
Installation problem

Hi there,
I hope someone in the know could help point me in the right direction. What could I possibly be missing? Thank you!
/usr/local/lib/node_modules/gatsby-cli/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;
        ^

Error: listen EADDRINUSE: address already in use :::8000
    at Server.setupListenHandle [as _listen2] (net.js:1280:14)
    at listenInCluster (net.js:1328:12)
    at Server.listen (net.js:1415:7)
    at startDevelopProxy (/Users/adam/PROJECT/MAIONE/node_modules/gatsby/src/utils/develop-proxy.ts:86:10)
    at module.exports (/Users/adam/PROJECT/MAIONE/node_modules/gatsby/src/commands/develop.ts:124:17)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)

Oh apparently, we can't run another app at the same port :8000 (even though I have none running)

Been trying for hours, just couldn't get pass
Cannot query field "allStripeSku" on type "Query".
I've created a test data on Stripe and follow everything to a "T"
Hopefully someone is kind enough to point me in the right direction. What supposedly a 5-min installation turned in hours scratching my head
Thanks everyone.

@yansusanto Did you figure this out? You have to use the Stripe API to add SKU/quantity.

The latest version of the starter comes with Stripe fixtures, which I hope will alleviate problems others are having with getting the proper data setup in Stripe. It also moves from the Orders API (Skus) to the Prices API.
Please let me know if you have any problems with the new version of the starter!

authors: brxck thomasvaeth yansusanto

repo: brxck/gatsby-starter-stripe


text:
Quits with issue

Finally getting around to trying this again. (Thanks for #3)
I have:

[x] dayone2 cli installed
[x] iMessage journal created
[x] successfully run the app

When attempting to import (regardless of date range selected, and clearing the imported dates each time), I get an exception. Here's the full traceback
2018-09-23 20:58:30.669000-0700 iMessage Importer[20871:2537379] [default] Unable to load Info.plist exceptions (eGPUOverrides)
importing: 2017-09-23 15:00:00 +0000
=================================================================
Main Thread Checker: UI API called on a background thread: -[NSControl setStringValue:]
PID: 20871, TID: 2539520, Thread name: (none), Queue name: com.imessagesimport, QoS: 17
Backtrace:
4   iMessage Importer                   0x000000010003acf6 $S17iMessage_Importer20ImportViewControllerC36importMessagesForAllNonImportedDatesyyF + 3334
5   iMessage Importer                   0x000000010003bd64 $S17iMessage_Importer20ImportViewControllerC36importMessagesForAllNonImportedDatesyyFTo + 36
6   iMessage Importer                   0x0000000100037ad0 $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU1_ + 32
7   iMessage Importer                   0x0000000100037b2d $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU1_TA + 13
8   iMessage Importer                   0x0000000100032aad $SIeg_IeyB_TR + 45
9   libdispatch.dylib                   0x00000001010df7f3 _dispatch_client_callout + 8
10  libdispatch.dylib                   0x00000001010e35f9 _dispatch_block_invoke_direct + 291
11  iMessage Importer                   0x0000000100037c8f $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU2_ + 31
12  iMessage Importer                   0x0000000100037cac $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU2_TA + 12
13  iMessage Importer                   0x0000000100032aad $SIeg_IeyB_TR + 45
14  libdispatch.dylib                   0x00000001010de71b _dispatch_call_block_and_release + 12
15  libdispatch.dylib                   0x00000001010df7f3 _dispatch_client_callout + 8
16  libdispatch.dylib                   0x00000001010e79f7 _dispatch_lane_serial_drain + 789
17  libdispatch.dylib                   0x00000001010e88ae _dispatch_lane_invoke + 446
18  libdispatch.dylib                   0x00000001010f3f6c _dispatch_workloop_worker_thread + 691
19  libsystem_pthread.dylib             0x000000010115a058 _pthread_wqthread + 409
20  libsystem_pthread.dylib             0x0000000101159e51 start_wqthread + 13
2018-09-23 20:58:51.078156-0700 iMessage Importer[20871:2539520] [reports] Main Thread Checker: UI API called on a background thread: -[NSControl setStringValue:]
PID: 20871, TID: 2539520, Thread name: (none), Queue name: com.imessagesimport, QoS: 17
Backtrace:
4   iMessage Importer                   0x000000010003acf6 $S17iMessage_Importer20ImportViewControllerC36importMessagesForAllNonImportedDatesyyF + 3334
5   iMessage Importer                   0x000000010003bd64 $S17iMessage_Importer20ImportViewControllerC36importMessagesForAllNonImportedDatesyyFTo + 36
6   iMessage Importer                   0x0000000100037ad0 $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU1_ + 32
7   iMessage Importer                   0x0000000100037b2d $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU1_TA + 13
8   iMessage Importer                   0x0000000100032aad $SIeg_IeyB_TR + 45
9   libdispatch.dylib                   0x00000001010df7f3 _dispatch_client_callout + 8
10  libdispatch.dylib                   0x00000001010e35f9 _dispatch_block_invoke_direct + 291
11  iMessage Importer                   0x0000000100037c8f $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU2_ + 31
12  iMessage Importer                   0x0000000100037cac $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU2_TA + 12
13  iMessage Importer                   0x0000000100032aad $SIeg_IeyB_TR + 45
14  libdispatch.dylib                   0x00000001010de71b _dispatch_call_block_and_release + 12
15  libdispatch.dylib                   0x00000001010df7f3 _dispatch_client_callout + 8
16  libdispatch.dylib                   0x00000001010e79f7 _dispatch_lane_serial_drain + 789
17  libdispatch.dylib                   0x00000001010e88ae _dispatch_lane_invoke + 446
18  libdispatch.dylib                   0x00000001010f3f6c _dispatch_workloop_worker_thread + 691
19  libsystem_pthread.dylib             0x000000010115a058 _pthread_wqthread + 409
20  libsystem_pthread.dylib             0x0000000101159e51 start_wqthread + 13
2018-09-23 20:58:51.121123-0700 iMessage Importer[20871:2539520] [logging-persist] cannot open file at line 42249 of [95fbac39ba]
2018-09-23 20:58:51.121149-0700 iMessage Importer[20871:2539520] [logging-persist] os_unix.c:42249: (0) open(/Users/adambrault//Library/Messages/chat.db) - Undefined error: 0
unable to open database file (code: 14)
2018-09-23 20:58:51.128226-0700 iMessage Importer[20871:2539520] [General] An uncaught exception was raised
2018-09-23 20:58:51.128257-0700 iMessage Importer[20871:2539520] [General] NSWindow drag regions should only be invalidated on the Main Thread!
2018-09-23 20:58:51.128369-0700 iMessage Importer[20871:2539520] [General] (
	0   CoreFoundation                      0x00007fff340ba43d __exceptionPreprocess + 256
	1   libobjc.A.dylib                     0x00007fff5ffc7720 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff340d3ec1 -[NSException raise] + 9
	3   AppKit                              0x00007fff315d82a5 -[NSWindow(NSWindow_Theme) _postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 324
	4   AppKit                              0x00007fff315d568c -[NSWindow _initContent:styleMask:backing:defer:contentView:] + 1488
	5   AppKit                              0x00007fff31695edf -[NSPanel _initContent:styleMask:backing:defer:contentView:] + 50
	6   AppKit                              0x00007fff315d50b6 -[NSWindow initWithContentRect:styleMask:backing:defer:] + 45
	7   AppKit                              0x00007fff31695e94 -[NSPanel initWithContentRect:styleMask:backing:defer:] + 64
	8   AppKit                              0x00007fff315d35c7 -[NSWindowTemplate nibInstantiate] + 495
	9   AppKit                              0x00007fff3154e646 -[NSIBObjectData instantiateObject:] + 267
	10  AppKit                              0x00007fff3154d9b4 -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 579
	11  AppKit                              0x00007fff3154bbe1 loadNib + 401
	12  AppKit                              0x00007fff3154b0a9 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 696
	13  AppKit                              0x00007fff3154acee -[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:] + 204
	14  AppKit                              0x00007fff31904cc9 -[NSAlert init] + 101
	15  iMessage Importer                   0x00000001000414a3 $SSo7NSAlertCABycfcTO + 19
	16  iMessage Importer                   0x00000001000381cf $SSo7NSAlertCABycfC + 31
	17  iMessage Importer                   0x0000000100044b87 $S17iMessage_Importer0aB0C11getMessagesyyF + 9719
	18  iMessage Importer                   0x000000010003be41 $S17iMessage_Importer20ImportViewControllerC14importMessages4datey10Foundation4DateV_tF + 193
	19  iMessage Importer                   0x000000010003bea1 $S17iMessage_Importer20ImportViewControllerC14importMessages4datey10Foundation4DateV_tFTo + 65
	20  iMessage Importer                   0x000000010003afc8 $S17iMessage_Importer20ImportViewControllerC36importMessagesForAllNonImportedDatesyyF + 4056
	21  iMessage Importer                   0x000000010003bd64 $S17iMessage_Importer20ImportViewControllerC36importMessagesForAllNonImportedDatesyyFTo + 36
	22  iMessage Importer                   0x0000000100037ad0 $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU1_ + 32
	23  iMessage Importer                   0x0000000100037b2d $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU1_TA + 13
	24  iMessage Importer                   0x0000000100032aad $SIeg_IeyB_TR + 45
	25  libdispatch.dylib                   0x00000001010df7f3 _dispatch_client_callout + 8
	26  libdispatch.dylib                   0x00000001010e35f9 _dispatch_block_invoke_direct + 291
	27  iMessage Importer                   0x0000000100037c8f $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU2_ + 31
	28  iMessage Importer                   0x0000000100037cac $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU2_TA + 12
	29  iMessage Importer                   0x0000000100032aad $SIeg_IeyB_TR + 45
	30  libdispatch.dylib                   0x00000001010de71b _dispatch_call_block_and_release + 12
	31  libdispatch.dylib                   0x00000001010df7f3 _dispatch_client_callout + 8
	32  libdispatch.dylib                   0x00000001010e79f7 _dispatch_lane_serial_drain + 789
	33  libdispatch.dylib                   0x00000001010e88ae _dispatch_lane_invoke + 446
	34  libdispatch.dylib                   0x00000001010f3f6c _dispatch_workloop_worker_thread + 691
	35  libsystem_pthread.dylib             0x000000010115a058 _pthread_wqthread + 409
	36  libsystem_pthread.dylib             0x0000000101159e51 start_wqthread + 13
)
2018-09-23 20:58:51.138791-0700 iMessage Importer[20871:2539520] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'NSWindow drag regions should only be invalidated on the Main Thread!'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff340ba43d __exceptionPreprocess + 256
	1   libobjc.A.dylib                     0x00007fff5ffc7720 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff340d3ec1 -[NSException raise] + 9
	3   AppKit                              0x00007fff315d82a5 -[NSWindow(NSWindow_Theme) _postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 324
	4   AppKit                              0x00007fff315d568c -[NSWindow _initContent:styleMask:backing:defer:contentView:] + 1488
	5   AppKit                              0x00007fff31695edf -[NSPanel _initContent:styleMask:backing:defer:contentView:] + 50
	6   AppKit                              0x00007fff315d50b6 -[NSWindow initWithContentRect:styleMask:backing:defer:] + 45
	7   AppKit                              0x00007fff31695e94 -[NSPanel initWithContentRect:styleMask:backing:defer:] + 64
	8   AppKit                              0x00007fff315d35c7 -[NSWindowTemplate nibInstantiate] + 495
	9   AppKit                              0x00007fff3154e646 -[NSIBObjectData instantiateObject:] + 267
	10  AppKit                              0x00007fff3154d9b4 -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 579
	11  AppKit                              0x00007fff3154bbe1 loadNib + 401
	12  AppKit                              0x00007fff3154b0a9 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 696
	13  AppKit                              0x00007fff3154acee -[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:] + 204
	14  AppKit                              0x00007fff31904cc9 -[NSAlert init] + 101
	15  iMessage Importer                   0x00000001000414a3 $SSo7NSAlertCABycfcTO + 19
	16  iMessage Importer                   0x00000001000381cf $SSo7NSAlertCABycfC + 31
	17  iMessage Importer                   0x0000000100044b87 $S17iMessage_Importer0aB0C11getMessagesyyF + 9719
	18  iMessage Importer                   0x000000010003be41 $S17iMessage_Importer20ImportViewControllerC14importMessages4datey10Foundation4DateV_tF + 193
	19  iMessage Importer                   0x000000010003bea1 $S17iMessage_Importer20ImportViewControllerC14importMessages4datey10Foundation4DateV_tFTo + 65
	20  iMessage Importer                   0x000000010003afc8 $S17iMessage_Importer20ImportViewControllerC36importMessagesForAllNonImportedDatesyyF + 4056
	21  iMessage Importer                   0x000000010003bd64 $S17iMessage_Importer20ImportViewControllerC36importMessagesForAllNonImportedDatesyyFTo + 36
	22  iMessage Importer                   0x0000000100037ad0 $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU1_ + 32
	23  iMessage Importer                   0x0000000100037b2d $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU1_TA + 13
	24  iMessage Importer                   0x0000000100032aad $SIeg_IeyB_TR + 45
	25  libdispatch.dylib                   0x00000001010df7f3 _dispatch_client_callout + 8
	26  libdispatch.dylib                   0x00000001010e35f9 _dispatch_block_invoke_direct + 291
	27  iMessage Importer                   0x0000000100037c8f $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU2_ + 31
	28  iMessage Importer                   0x0000000100037cac $S17iMessage_Importer20ImportViewControllerC25importAllNotImportedDatesyySo8NSButtonCFyycfU2_TA + 12
	29  iMessage Importer                   0x0000000100032aad $SIeg_IeyB_TR + 45
	30  libdispatch.dylib                   0x00000001010de71b _dispatch_call_block_and_release + 12
	31  libdispatch.dylib                   0x00000001010df7f3 _dispatch_client_callout + 8
	32  libdispatch.dylib                   0x00000001010e79f7 _dispatch_lane_serial_drain + 789
	33  libdispatch.dylib                   0x00000001010e88ae _dispatch_lane_invoke + 446
	34  libdispatch.dylib                   0x00000001010f3f6c _dispatch_workloop_worker_thread + 691
	35  libsystem_pthread.dylib             0x000000010115a058 _pthread_wqthread + 409
	36  libsystem_pthread.dylib             0x0000000101159e51 start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException

I'm running Mojave—so possibly that's what's going on? (Have you run this lately?)
Such a cool tool, I truly can't wait to use it.

I"ll look into this. Looks like a label is being set from a background thread

I've just tried it on what is actually a completely new computer, as I got a new laptop between the time I had that issue and now.
I remember seeing this in the readme before:

Make sure Don't Sign Code is the selected setting in Build Settings > Code Signing Identity When code signing is enabled, it looks like some sandbox restrictions are disabling access to the iMessage DB

But in the latest version of Xcode, at least, that option doesn't seem to exist:

If I have it sign for ad hoc local use, I get a new error:

If I reset everything and run it without setting anything in that spot, then I don't have the "fatal error" business, but in the console, I basically get the same message described above:
2018-11-04 21:45:24.812172-0800 iMessage Importer[12428:2288923] [default] Unable to load Info.plist exceptions (eGPUOverrides)
[file:///Users/adambrault/Library/]

Attempting to run the import in this condition gives me an error dialog box which says:

FATAL ERROR
unable to open database file (code: 14)

Which, combined with the console output below, indicates that it's probably not accessing that DB and a different setting is needed:
2018-11-04 21:45:24.812172-0800 iMessage Importer[12428:2288923] [default] Unable to load Info.plist exceptions (eGPUOverrides)
[file:///Users/adambrault/Library/]
importing: 2018-10-28 15:00:00 +0000
[file:///Users/adambrault/Library/]
/Users/adambrault//Library/Messages/chat.db
2018-11-04 21:48:03.519350-0800 iMessage Importer[12428:2292103] [logging-persist] cannot open file at line 42249 of [95fbac39ba]
2018-11-04 21:48:03.519385-0800 iMessage Importer[12428:2292103] [logging-persist] os_unix.c:42249: (0) open(/Users/adambrault//Library/Messages/chat.db) - Undefined error: 0
unable to open database file (code: 14)
importing: 2018-10-29 15:00:00 +0000
[file:///Users/adambrault/Library/]
/Users/adambrault//Library/Messages/chat.db
2018-11-04 21:48:03.523456-0800 iMessage Importer[12428:2292103] [logging-persist] cannot open file at line 42249 of [95fbac39ba]
2018-11-04 21:48:03.523468-0800 iMessage Importer[12428:2292103] [logging-persist] os_unix.c:42249: (0) open(/Users/adambrault//Library/Messages/chat.db) - Undefined error: 0
importing: 2018-10-30 15:00:00 +0000
[file:///Users/adambrault/Library/]
/Users/adambrault//Library/Messages/chat.db
2018-11-04 21:48:03.524766-0800 iMessage Importer[12428:2292103] [logging-persist] cannot open file at line 42249 of [95fbac39ba]
2018-11-04 21:48:03.524782-0800 iMessage Importer[12428:2292103] [logging-persist] os_unix.c:42249: (0) open(/Users/adambrault//Library/Messages/chat.db) - Undefined error: 0
importing: 2018-10-31 15:00:00 +0000
[file:///Users/adambrault/Library/]
/Users/adambrault//Library/Messages/chat.db
2018-11-04 21:48:03.525691-0800 iMessage Importer[12428:2292103] [logging-persist] cannot open file at line 42249 of [95fbac39ba]
2018-11-04 21:48:03.525707-0800 iMessage Importer[12428:2292103] [logging-persist] os_unix.c:42249: (0) open(/Users/adambrault//Library/Messages/chat.db) - Undefined error: 0
importing: 2018-11-01 15:00:00 +0000
[file:///Users/adambrault/Library/]
/Users/adambrault//Library/Messages/chat.db
2018-11-04 21:48:03.526637-0800 iMessage Importer[12428:2292103] [logging-persist] cannot open file at line 42249 of [95fbac39ba]
2018-11-04 21:48:03.526652-0800 iMessage Importer[12428:2292103] [logging-persist] os_unix.c:42249: (0) open(/Users/adambrault//Library/Messages/chat.db) - Undefined error: 0
importing: 2018-11-02 15:00:00 +0000
[file:///Users/adambrault/Library/]
/Users/adambrault//Library/Messages/chat.db
2018-11-04 21:48:03.527502-0800 iMessage Importer[12428:2292103] [logging-persist] cannot open file at line 42249 of [95fbac39ba]
2018-11-04 21:48:03.527515-0800 iMessage Importer[12428:2292103] [logging-persist] os_unix.c:42249: (0) open(/Users/adambrault//Library/Messages/chat.db) - Undefined error: 0
importing: 2018-11-03 15:00:00 +0000
[file:///Users/adambrault/Library/]
/Users/adambrault//Library/Messages/chat.db
2018-11-04 21:48:03.528183-0800 iMessage Importer[12428:2292103] [logging-persist] cannot open file at line 42249 of [95fbac39ba]
2018-11-04 21:48:03.528196-0800 iMessage Importer[12428:2292103] [logging-persist] os_unix.c:42249: (0) open(/Users/adambrault//Library/Messages/chat.db) - Undefined error: 0
importing: 2018-11-04 16:00:00 +0000
[file:///Users/adambrault/Library/]
/Users/adambrault//Library/Messages/chat.db
2018-11-04 21:48:03.528894-0800 iMessage Importer[12428:2292103] [logging-persist] cannot open file at line 42249 of [95fbac39ba]
2018-11-04 21:48:03.528906-0800 iMessage Importer[12428:2292103] [logging-persist] os_unix.c:42249: (0) open(/Users/adambrault//Library/Messages/chat.db) - Undefined error: 0

Thanks again for your help @bryan1anderson :)

@adambrault Can you try these steps?
Open System Preferences > Security & Privacy > Full Disk Access
Click +
Locate iMessage Importer and add it

@adambrault the only way I can duplicate these issues is by removing disk access. Would you mind sometime trying out the steps above?

@bryan1anderson I sure appreciate you looking into this. It's on my list to test it and I'll try to do that this weekend.


text:
Allow the config_module key to be placed on any config block

Since there is now only one config item for Joken, config_module, it would probably be nice to make it so that the user can define which config block contains the key.
I propose change the config_module key to joken_module, and adding a using macro that takes an otp_app option which defines which config block to look for the joken_module key.
Something like below:

    #the config block
     config :my_app,
         joken_config: My.Config.Module

  #Next, tell Joken where to find the config block
    use Joken, otp_app: :my_app

  #then to encode and decode
      {:ok, token} = encode_token(%{username: "johndoe"})
      {:ok, decoded_payload} = decode_token(jwt)

I made a branch with the change and the only thing I could come up with is having the functions to encode and decode added to the using macro and called directly in the module using it. Since a lot of libraries use encode and decode as function names, in this branch I renamed the functions encode_token and decode_token.

This is nice! Some things I think would be useful:

Perhaps it is good to have the property name as an optional parameter. This way it would be possible to have 2 config modules: one for user login and another for system to system authentication. I don't need this use case but I think it will be desired by people who are coding microservices.
We could use a @on_load to cache the generated JOSE header for each configuration. :smiley:

Good points. I think making the name of the config property optional makes sense. Or maybe add a property that points directly to the module instead?
I had to look up @on_load :smile:. It sounds like that could work.

@cs-victor-nascimento I added a PR for this, but I haven't added the bit to customize the property itself yet.
Also I'm not sure I completely understand what should be cached using @on_load. Could you give me an idea of what to do?

The cache idea is that for each config module the first part of a JWT (which describes de algorithm and optional parameters) will always be the same. Say you choose to use HS256. Then it will always be {"alg": "HS256", "typ": "jwt"} or something.
So we can generate the JSON and Base64 representation of those once we have that information. Not sure the on_load will work with that (not 100% secure we can ensure our dependencies are all loaded when on_load function is executed) and probably it would be better to go all in and define an application module. I mentioned the on_load just to avoid adding another breaking change: people would need to add joken to their list of apps in mix.exs.
What do you think?

Actually I was thinking and I believe we should have a performance benchmark suite set before atempting any early optimization. I will open another issue for that.

The caching may work, but I will probably do a separate issue/PR for it. I can probably finish this by adding the ability to customize the config key tonight.
With all the changes going on, the next release will be a big one!

Closing this as it's no longer valid

authors: bryanjos cs-victor-nascimento

repo: bryanjos/joken


text:
Evaluate to implement other use cases from langgraph tutorial

Original langgraph tutorial contains a lot of interesting examples, I would implements others to promote langgraph4j as first citizen in langchain4j eco-system:
RAG

Agentic RAG
Corrective RAG (CRAG)
Corrective RAG (CRAG) using local LLMs
Self-RAG
Self-RAG using local LLMs
SQL Agent

Agent Architectures
Multi-Agent Systems

Collaboration
Supervision
Hierarchical Teams

Planning Agents

Plan-and-Execute
Reasoning without Observation
LLMCompiler

Reflection & Critique

Basic Reflection
Reflexion
Language Agent Tree Search
Self-Discover Agent

That's really great. When will these RAG and Agent frameworks be combined with Langchain4j for an example! I have been following langchain4j and langgraph4j all along.

Hi @243006306 thanks for interest
However Agent Executor and Adaptive RAG are already available

This project looks interesting. Currently going through the code base , please let me know if you want me to contribute on anything. Thanks

authors: 243006306 ArnWEB bsorrentino


text:
Can't load plugins into Ableton 11 or Bitwig 4.1.2

For bug reports
Operating system(s): Windows 10 64-bit 21H2
Version of Rack if using official binary, or commit hash and branch if compiling from source:  VCVRack:v2.0.5
All hardware relevant to your issue (e.g. graphic card model, audio/MIDI device): Radeon Pro WX3100, Radeon RX550, SSL 2+ ASIO
Plugins don't show up during scan, both Ableton and Bitwig refuse to let me load the .dll files manually; I get a crossed out circle icon for a mouse cursor when I try this
Both instrument and effect VCVR plugins load fine into VSThostx64, no problems
Tried restarting machine, running both as admin, still won't load. Tried deleting preferences files and cache, still wont load
Not sure what to try next. Any suggestions?
Thanks

Version of Rack if using official binary, or commit hash and branch if compiling from source: VCVRack:v2.0.5

for questions regarding VCVRack v2.0.5, please go to https://github.com/VCVRack

Sorry I'm confused, I have the standalone VCVR which works fine no problems there, I'm trying to get these plugins to work inside Bitwig and Ableton.
I think its 0.6.1? I just downloaded it a few hours ago

your post mentioned v2.0.5, that's what got me confused.
if you are indeed using VCVR (0.6.x), make sure that the entire vst2_bin/ folder is in the host plugin path.
I vaguely recall that someone once resolved a similar issue by not placing the plugin in a deeply nested folder structure (cannot remember which host required that).
I've tested VCVR in both Ableton Live and Bitwig and it worked fine (just re-tested it with the latest Live version 11.0.12).

Well I got them to work inside Bitwig. Was never able to manually drag and drop the .dlls, but after deleting the Bitwig preferences file and Index folder, then running Bitwig as admin, they were both picked up during the plugin scan.
This is the exact same procedure I tried initially; not sure what I did differently this time that made it work, but not complaining!


text:
UX Improvements

"bootstrap native" breadcrumbs
"alert" wrapper for "Advanced Considerations"
tweak text related to "advanced" sections
use some "»" chars (for "next steps" prefix and before "Advanced Considerations" in titles)
tweak margins/padding in the base layout to give a little more breathing room

Love the new style, thanks!

Love the new style, thanks!

authors: janoside mflaxman


text:
bech32: Encode accepts invalid uppercase HRP

bech32.Encode will accept an uppercase HRP and generate an invalid bech32 encoding instead of normalizing it or returning an error.
BIP 0173 is clear that mixed case encodings are invalid, and that the lowercase encoding should be used for checksum purposes. This means there are two ways to handle an uppercase HRP in Encode:

treat it as lowercase, and ideally return a lowercase encoding
return an error

Instead, this library will use the uppercase values for the checksum and return a mixed case encoding. Decode will correctly reject the mixed case encoding, and will fail the checksum of the lowercase version.
https://play.golang.org/p/h0ekj8VmiPV

I'm no longer active on this project, but for reference for the new maintainers, you guys might want to go ahead and back port the updated version from Decred at https://github.com/decred/dcrd/tree/master/bech32.  We originally based it on this implementation from the LL folks, but improved it in many ways, which includes handling what this issue raises properly.
The primary improvements made are:

Much improved efficiency in terms of memory allocations and overall encoding and decoding performance along with benchmarks
Corrected the issue being reported here by automatically converting the HRP to lowercase and improved error handling to catch other potential misuses
Added convenience functions for EncodeFromBase256 and DecodeToBase256 which automatically handles the typical case of converting to base32 with padding before encoding and back to base256 without padding when decoding
Improved the error handling to be more in line with the rest of the code base such that the errors are more descriptive and programmatically detectable
Fleshed out the test coverage to test more corner cases as well as ensure the actual errors that are produced are the expected errors versus just checking that some error happened
Updated the code and documentation to be more consistent
Created and tagged a separate Go module specifically for bech32 (github.com/decred/dcrd/bech32) and thus provide a tighter module with a smaller API surface which results in less notifications of new versions for consumers due to other things not related to bech32 changing

I've slightly modified the code provided by @FiloSottile accordingly to show the improved version works as expected:
https://play.golang.org/p/VlNZprYObxE
package main

import (
	"log"
	"strings"

	"github.com/decred/dcrd/bech32"
)

func main() {
	s, err := bech32.EncodeFromBase256("UPPERCASE", []byte("xxx"))
	if err != nil {
		log.Fatal(err)
	}
	log.Print("encoded: ", s)
	log.Print(bech32.Decode(s))
	log.Print(bech32.Decode(strings.ToUpper(s)))
}

Output:
... encoded: uppercase10pu8sss7kmp
... uppercase[15 1 28 7 16] <nil>
... uppercase[15 1 28 7 16] <nil>

authors: FiloSottile davecgh

repo: btcsuite/btcutil

license: isc


text:
Tratamento de erros na entrada do usuario

Ao tentar converter a entrada do usuário para inteiro não tem nenhum tratamento de erro o que pode levar o programa a crashar caso o usuário entre com um valor que não seja possível converter
https://github.com/btwhelena/Swift-Challenge/blob/a540f08104cd97cc8b14e196eb9360499bdf14c3/Sources/Hello/main.swift#L174-L177
O leitura do input poderia ficar dentro de um laço while e só sair quando o valor for válido:
var isInputValid = false
var input: String?

while !isInputValid {
    input = readLine()
    if let intInput = Int(input!) {
        isInputValid = true
    } else {
        print("Por favor insira um valor inteiro")
    }
}

Obrigada pela sugestão, Lais! Irei implementá-la assim que possível ✨

authors: btwhelena laisbastosbg

repo: btwhelena/Swift-Challenge


text:
如何训练可以得到77maP

想问一下如何训练可以得到您给出的在voc上77mAP的权重？可以问一下训练策略吗？我在你的代码中注释了对预训练文件的引入，直接使用原始ResNet网络进行train.py文件中100epoch的训练，得到的训练效果很差？想问怎样可以训练出和您相同的voc的结果呢？

pretrain=True可以用主干的预训练权重吧

pretrain=True可以用主干的预训练权重吧

同问，请问你解决了嘛？

想问一下如何训练可以得到您给出的在voc上77mAP的权重？可以问一下训练策略吗？我在你的代码中注释了对预训练文件的引入，直接使用原始ResNet网络进行train.py文件中100epoch的训练，得到的训练效果很差？想问怎样可以训练出和您相同的voc的结果呢？

同问，请问你解决了嘛？

想问一下如何训练可以得到您给出的在voc上77mAP的权重？可以问一下训练策略吗？我在你的代码中注释了对预训练文件的引入，直接使用原始ResNet网络进行train.py文件中100epoch的训练，得到的训练效果很差？想问怎样可以训练出和您相同的voc的结果呢？

为啥会忽略我中间的回答呢…

呃，主要是我试了你用pretrain=True也是这样30%的map

截图，训练策略也截图，loss也截图

Train

Train one epochs

Loss

Dataloader

DataLoader 和 Loss基本按照你的方式写的。训练策略稍有改动，但我感觉Loss和data都一样的情况，应该没啥问题。

你咋改了这么多…

是呀，跟着你的讲解自己又重新加了一点。

你这个改的有点多啊……我看l1_loss里面连permute都删了……我不知道具体原因。

找个我是在外面进行了permute，维度顺序是一致的，不然也没法计算。不过我想和你确认的是，你是基于resnet50 backbone的预训练权重，然后fine-tune就可以在VOC上达到77的MAP吗？那此时的val loss是多少呢？我也是采用resnet的backbone预训练权重，也没法达到这个77，而且val loss达到2.5的时候，就会反向上升（虽然我看了下原作者的repo说hm loss是正常的）。模型确实是学到东西了，直接测训练集Map是89，但验证集只有40多。很难受。。。

当然，上传前我已经测试过了，100epoch大概到76.多，之前是77多，因为之前学习率较大，现在增大epoch后也可以77。

你是我提供的数据集么， 我是freeze batch为32，unfreeze batch16

我是用voc2012的，训练集15000多张，验证集1700多张。我用同样的数据集，训练你最新的repo，上周五下载的。map只有28。。。

下次问问题说清楚情况。
VOC2012的数据集你用labelimg打开就知道，里面有些标注是不完全的，因为有一些不是拿来目标检测的。

可以，那我试试VOC2007

是07+12，我都提供了为啥不用呢

单07训练集就5000张，效果又不一样

是07+12，我都提供了为啥不用呢

你这个是自己改过标注的吗？还是整理过官方的呢

https://www.bilibili.com/read/cv10239076?spm_id_from=333.999.0.0

谢谢耐心解答，麻烦了。

你好，您的邮件我已收到。我将在近期查看，尽快给你回复。

authors: Runist ZxSnow bubbliiiing

repo: bubbliiiing/centernet-pytorch


text:
sortedlist 试两次

{ "hash": "0x39c767e230f1cc4d8fa7baa4ef8c39bc2e4add8680d09bfe086e1efdaa0d6437", "score": 290 }, // 10
{ "hash": "0x39c767e230f1cc4d8fa7baa4ef8c39bc2e4add8680d09bfe086e1efdaa0d6438", "score": 290 }, // 10

看那个先进

According to  current implementation, two items with the same score are sorted in order of insertion, from first to last. If the inserted item has the same score as the last one in list, the insertion will be considered invalid.

I updated the testcase to include insert two items which has same score. it will ranked by their insert order.

authors: fulldecent weiqiushi

repo: buckyos/DCRM


text:
code splitting and uploading all source maps

Hi,
In my react app I am using code splitting (react-loadable) to reduce the bundle size and serve them on demand whenever the respective route is loaded. Using this technique I am getting about 53 chunks and a main file (.js and .map).
How can I upload all these source maps to identify the error stack trace correctly.
regards
Aman

Hi @amanthegreatone. Are you using webpack? If so you should take a look at our webpack plugins module which can upload sourcemaps:
webpack-bugsnag-plugins (docs)
If you're not using webpack, you can make use of the underlying JS API/CLI tool:
bugsnag-sourcemaps (docs)

I see!
So create-react-app does use webpack for you but it hides the details away, and as far as I can tell doesn't let you add plugins.
Our webpack plugin would do exactly what you want – it iterates over all the chunks/maps and uploads them all. But it seems like your only option would be to "eject" from create-react-app in order to modify the webpack config yourself. But you probably don't want to do that!
Alternatively you can use bugsnag-sourcemaps, iterating over all of the generated source maps using bash or javascript. Here's a sketch of what I mean (in JS):
const { upload } = require('bugsnag-sourcemaps')
const glob = require('glob')

// find all of the map files in ./dist
glob('dist/**/*/*.map', (err, files) => {
  if (err) throw err
  // process each .map file
  Promise.all(files.map(processMap))
})

// returns a Promise which uploads the source map with accompanying sources
function processMap (sourceMap) {

  // remove .map from the file to get the js filename
  const minifiedFile = sourceMap.replace('.map', '')

  // remove the preceding absolute path to the static assets folder
  const minifiedFileRelativePath = minifiedFile.replace(`${__dirname}/dist/`, '')

  // call bugsnag-sourcemaps upload()
  return upload({
    apiKey: 'YOUR_API_KEY_HERE',
    appVersion: '1.2.3',
    minifiedUrl: `http*://your-domain.app/path/to/assets/${minifiedFileRelativePath}`,
    sourceMap,
    minifiedFile,
    projectRoot: __dirname
    uploadSources: true
  })

}

I didn't run or test this so you will undoubtably need to tweak paths/urls for your setup and play with the arguments to bugsnag-sourcemaps. This also rather crudely will fire off all the uploads concurrently. See webpack-bugsnag-plugins for an example of how to limit the concurrency of that.
Feel free to continue on this thread if you have any further questions, or alternatively email support@bugsnag.com where we can dig into your specific project and have a bit more context. We can also then share more detail than we would be able to on this public issue tracker.
Thanks!

Thanks @bengourley.
I will try your suggestions and update.

@bengourley as per your suggestion I followed the same instructions and uploaded the chunk.js.map files to bugsnag. Here is my code.
const upload = require('bugsnag-sourcemaps').upload;
const glob = require('glob');
const appVersion = require('./package.json').version;
const bugsnagKey = require('./src/config/env').bugsnagKey;
const path = require('path');

glob('source-maps/*.js.map', (err, files) => {
  if (err) throw err;
  Promise.all(files.map(processMap));
});

const processMap = sourceMap => {
  const minifiedFileName = sourceMap.split('/')[1].split('.map')[0]; //just extracting the file name.
  return upload({
    apiKey: bugsnagKey,
    appVersion: appVersion,
    minifiedUrl: `http://myAppWebsite.com/static/js/${minifiedFileName}`,
    sourceMap,
    minifiedFile: `${__dirname}/build/static/js/${minifiedFileName}`,
    projectRoot: __dirname,
    uploadSources: true,
    overwrite: true,
  });
};

The files are all uploaded and everything works. But the problem is the map and chunks are not mapped when an error is raised in the stacktrace i still get the chunk code rather than the original code.
Hoping you could point out where I am going wrong or what the error really is.
Thanks.

Hi @pavan-syook. I took a look at your account and it seems you are uploading everything correctly 👍
There is just one minor problem which you need to resolve. For your source maps, you are providing a value for appVersion (it's currently 0.1.0), but events coming in from your notifier have no appVersion. What our system does is look for an uploaded source map matching the url and app version, and since the app version is different (undefined vs. 0.1.0) it doesn't find your source map.
All you need to do is make sure the app version is set in your notifier and kept in sync with the version of your app. Then we'll be able to use the source maps you've uploaded to show the original sources. Hope this helps!

@bengourley Thanks for the quick update. will do that and let you know if I face any issues.

Hi @bengourley. we are also using code splitting in our react web application(groww.in) and in our case, the number of chunks are more than 80. all chunks source map files are uploaded on bugsnag for every app release. So my doubt is how many source map files can be uploaded on bugsnag, is there any restriction on uploading number of files?

Nope, no restriction. As many as you need.

@bengourley Thanks for the reply.

authors: Shiv-Dangi amanthegreatone bengourley pavan-syook

repo: bugsnag/bugsnag-js


text:
RNCNetInfo.getCurrentState got 3 arguments, expected 2.

Enviornment info :
System:
OS: Windows 10 10.0.17763
CPU: (8) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
Memory: 1.06 GB / 7.88 GB
Binaries:
Node: 8.16.1 - C:\Program Files\nodejs\node.EXE
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
SDKs:
Android SDK:
API Levels: 21, 22, 23, 24, 25, 26, 27, 28, 29
Build Tools: 26.0.2, 28.0.3, 29.0.2
System Images: android-24 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: Version 3.5.0.0 AI-191.8026.42.35.6010548
npmPackages:
react: ~16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz => 0.61.4
Facing this problem using expo directory.
import {AppState } from 'react-native';
import NetInfo from '@react-native-community/netinfo';
Using this two library

@mattdyoung : I have not used bugsnag-js in current project. I am using it in expo directory.
Above all information mentioned and JS code too attached.

@SanjanaTailor
You've raised this as an issue with bugsnag-js. If you're not using bugsnag-js in your project I don't think there's any issue for the maintainers of bugsnag-js to resolve here.
If you are using bugsnag-js can you provide a reproducible example of the issue bugsnag-js is causing using the latest version v6.5.1.

Please reopen, we need to know what is the correct version of @react-native-community/netinfo that can be used with sdk35 too
@react-native-community/netinfo - expected version range: ~3.2.1 - actual version installed: ^5.5.1

@react-native-community/netinfo - expected version range: ~3.2.1 - actual version installed: 4.6.2

Both crash with RNCNetInfo.getCurrentState got 3 arguments, expected 2..

Hi @lc3t35 - if you have a React Native project, we would recommend using our React Native notifier: https://github.com/bugsnag/bugsnag-react-native
Are you currently using bugsnag-js in your project? what version of bugsnag-js are you using?

I'm using expo sdk35 with "@bugsnag/expo": "6.4.1" for dev and  "bugsnag-react-native": "^2.23.2" for production.

Hey @lc3t35, the bugsnag-react-native library should not be used with Expo apps. Additionally, a fix was released that fixes an issue that sound exactly like this. This was released in v6.5.1 of our bugsnag-js library. Can you please try a version that is at least v6.5.1 to see if the issue persists?

Yes as ejected Expo app, I use bugsnag-react-native ("bugsnag-react-native": "^2.23.6",)
But for staging/dev, I would like to use https://docs.bugsnag.com/platforms/react-native/expo/ too. What do you suggest ?
I had to remove bugsnag-react-native and @bugsnag/expo, so I can work on my project, I can stay stuck ... QA is waiting for updates.... without error catching then...
I expect to update to sdk36 soon, so I'll check again.

@lc3t35 Have you confirmed that you still see this issue with the latest @bugsnag/expo which includes the fix @xander-jones refers to?
https://github.com/bugsnag/bugsnag-js/releases

installing version 3.2.1 worked for me

authors: Ashwini-ap SanjanaTailor lc3t35 mattdyoung phillipsam xander-jones


text:
Rename req.host to req.hostname

Just upgraded to Bugsnag v1.6.0, but express v4.11.2 started logging this warning:
express deprecated req.host: Use req.hostname instead node_modules/bugsnag/lib/request_info.js:6:46

This should fix this!

Original pull request broke on old versions of express. Just fixed that.

Awesome, thanks!

authors: ConradIrwin paton

repo: bugsnag/bugsnag-node


text:
Sourcemap path in case of android flavor builds

I have created flavor builds in the android side of the React Native app. Earlier there was no flavor builds
So I was uploading the source map using CI like this
- run:
          name: Upload sourcemaps to Bugsnag
          command: |
            if [[ $BUGSNAG_KEY ]]; then
              yarn generate-source-maps-android upload \
                --api-key=$BUGSNAG_KEY \
                --app-version=$CIRCLE_BUILD_NUM \
                --minifiedFile=android/app/build/generated/assets/react/release/app.bundle \
                --source-map=android/app/build/generated/sourcemaps/react/release/app.bundle.map \
                --minified-url=app.bundle \
                --upload-sources
            fi

But now the app is divided into two flavor builds (play and foss) and Bugsnag is available only in play build.
I am getting this error as the source map path needs to be updated.
 [error] Error uploading source maps: Error: Source map file does not exist (android/app/build/generated/sourcemaps/react/release/app.bundle.map)
    at /home/********/repo/node_modules/bugsnag-sourcemaps/lib/options.js:141:17

Can anyone help me in determining what will be the updated path of source map in case of multiple flavors in the app?  Thanks in advance.
PS: I Have gone through the docs but didn't find anything related to this scenario.

Hi @GOVINDDIXIT
Are you using the Hermes JS engine on Android in your React Native app? If you're not using Hermes you can just follow our standard instructions here to upload via the API without bugsnag-sourcemaps:
https://docs.bugsnag.com/platforms/react-native/react-native/showing-full-stacktraces/#uploading-source-maps-to-bugsnag
If Hermes is enabled then using bugsnag-sourcemaps is currently the only upload method we support.
Where does you flavor build output the .bundle and .bundle.map files? Have you tried manually running the build and searching for the files? Is it just the path that's wrong in your upload command?

Hi @mattdyoung
Thanks for the quick response. Yes, I have got the correct path by building source maps locally and the issue is now solved. If possible I would suggest adding a specific section for the android flavor builds in official docs.
After adding flavors the updated path for minified file and source map is
            --minifiedFile=android/app/build/generated/assets/react/play/release/app.bundle
            --source-map=android/app/build/generated/sourcemaps/react/play/release/app.bundle.map

In general
                --minifiedFile=android/app/build/generated/assets/react/{flavor_name}/release/app.bundle
                --source-map=android/app/build/generated/sourcemaps/react/{flavor_name}/release/app.bundle.map

@GOVINDDIXIT
Thanks for letting us know! We're looking into various docs improvements currently so we'll consider this clarification.

authors: GOVINDDIXIT mattdyoung

repo: bugsnag/bugsnag-react-native


text:
Use global default shell in release-tag.yml workflow

To remove the need to repeat default shell declaration in our workflow, we should set a global default so that it is available across all jobs in https://github.com/build-trust/ockam/blob/cdf925aa2adb4439061449e5ea5f9ad774833e20/.github/workflows/release-tag.yml#L1
More here https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#defaults

Closing this now. Thanks @rghdrizzle

repo: build-trust/ockam


text:
Bootstrap script doesn't fetch correctly with Git < v1.9

TL;DR: In version 2.1.5, the bootstrap script runs git fetch origin --tags to update all heads and tags. In some older versions of Git, that command will only update the tags, which can cause the subsequent checkout to fail.

We upgraded to version 2.1.5 on Ubuntu 12.04 LTS and the new bootstrap script failed. The problematic command is git fetch origin --tags. It seems to have been introduced in #243.
The relevant comment in the bootstrap script reads: "we fall back to fetching all heads and tags, hoping that the commit is included." With Git 1.9 and later, git fetch origin --tags will indeed fetch all heads and tags, assuming the remote is configured in the usual way. With Ubuntu 12.04 LTS's version of Git (v1.7.9.5), the command will run cleanly – that is, it will give a successful exit code and won't print error messages – but it will fetch only the tags. As a result, the git checkout command that follows it may fail and complain about "bad object".
We worked around this issue by adding a custom checkout hook that uses the command git fetch origin --tags +refs/heads/*:refs/remotes/origin/*.

#250 may have fixed this.

Yep, you're right, this is fixed in #250. Thanks for the report!

repo: buildkite/agent


text:
Docker images docs

I have few suggestions about docker images:

There should be the docs on the dockerhub where explicitly stated base image for tags. Or at least how to determine which base image was used.

Agent docker images should have appropriate tag naming for ubuntu and alpine, etc.. Take a look on python dockerhub.
buildkite/agent:3.1.1-ubuntu
buildkite/agent:3.1.1-alpine
buildkite/agent:3.1.1-alpine3.6
etc..
You can still say that defalut image is alpine. So buildkite/agent:3.1.1 and buildkite/agent:3.1.1-alpine are just symlinks.

IMO it's much more convinient way.
Why?
Sometimes it's useful to modify existing image (in my case I need to add envsubst to the image). And it was quite confusing for me when dockerfile dockerhub page use ubuntu:14.04 and agent:latest based on alpine.

Yup, good idea @ksanderer, we're going through a bit of a transition with how we build and manage docker images, so still trying to figure out best practice and how to work around some of the clunky aspets of docker hub.

authors: ksanderer lox


text:
Add support for other aws regions

It would be nice to launch these in e.g. us-west-2 in my case.

@mikekap @deoxxa this is now live, you can now use the stack in:

us-west-1
us-west-2
eu-west-1
eu-central-1
ap-northeast-1
ap-northeast-2
ap-southeast-1
ap-southeast-2
sa-east-1

Excellent! Thank you!

authors: deoxxa mikekap toolmantim

repo: buildkite/buildkite-aws-stack


text:
Make h3's linkable, and provide the ability for id and class overrides

Makes all the h3 elements linkable by adding an automatic id, and let's you customize the id and class.
For example, the following markdown:
## A long complicated section description
{: id="short-id"}

### Subsection 1

## Section 2

### Subsection 2

generates:

A long complicated section description

Subsection 1

Section 2

Subsection 2

This means we can now link to individual environment variables, and instead of #buildkite-environment-variables-buildkite-agent-pid we can have #bk-env-vars-buildkite-agent-pid for example.
Fixes #708

Everything here is up for grabs, so if you’ve got any preferred syntax changes or anything, let me know!

Ace! Yeah, I was hoping we could use the class/id for a bunch of things.

I'm happy with this as is, unless you fancy testing the ID clashes just converting H3 without prepending H2 to them? But it is probably not worth the time.

Yeah, I couldn’t think of a good algorithm. Would it be just adding -2, -3 etc to the end of the ids that clash? So as you progress down the page?
Also I didn’t add the hover link doohicky that h2’s have. Should we?

ooh, I didn't notice the lack of doohicky!  I reckon add it, saves from having to "view source" :-p. Please and thank you.
On the clash front, if there are a few dozen or so site wide, I'd be happy to add manual overrides to all of them, and just put up with an ID clash breaking the build for new content. What do you think?

ooh, I didn't notice the lack of doohicky! I reckon add it, saves me from having to "view source" :-p. Please and thank you.

All done!

On the clash front, if there are a few dozen or so site wide, I'd be happy to add manual overrides to all of them, and just put up with an ID clash breaking the build for new content. What do you think?

I like the idea, but I think I'm keen to stick with the current method for now — 90% because the code is mostly ready, and 10% because of getting my head around dealing with the clashes. Let's stick with the nesting method we have now, and revisit if we're not feeling it's working well.

:100:

authors: plaindocs toolmantim

repo: buildkite/docs


text:
Set individual environment variables for build

pack allows setting build-time environment variables via a file, but not
as individual values on the cli. This PR adds the ability to set one (or
more) environment variables directly as cli switches.
The same semantics are preserved from --env-file where a value can be
forwarded from the current environment if a variable name is specified
without a value. The new flags can be used to augment or override
specific values from a file.
The BuildFlags struct now includes an Env field in addition to EnvFile.
The BuildConfig struct EnvFile field has been renamed to Env for
consistency as the field contains the parsed values and not a file.
Refs buildpack/roadmap#25

A little background context.
riff currently uses a riff.toml file to pass configuration to function buildpacks. This file is generated based on values provided to the riff cli. Since this config file is not actually part of the project, it's awkward to write a file to the filesystem, do some work and then remove that file. It would be nicer to specify this config as environment variables.

Merged master and fixed a conflict with build config changes.
cc @ekcasey

@scothis I was under the impression that riff was importing github.com/buildpack/pack as a library using the pack.Build(...) function to run builds. In which case, I would imagine the correct solution for this problem is to add a map of env vars as a  param to pack.Build. In that case riff should be able to construct that map as desired (no file required).
Is riff shelling out to the pack cli? I am not opposed to supporting a --env flag but to better enable library consumers it's important to us to know where users are integrating. In the near future we plan to make everything except a deliberately exposed library internal and thus not importable.

@ekcasey yes, riff embeds pack rather than shelling out. On its own, this PR is not enough to fully solve riff's needs, but it provides a large step towards scratching that itch. I'll open another PR that takes a baby step towards creating a programatic API that exposes the same capabilities.
This PR is updated to resolve conflicts.

@scothis Thanks for the explanation. If we think cli users will value having a --env flag in addition to an --env-file, flag this is a good step. I think the only thing missing here is acceptance test coverage. If we are exposing a new flag we should add coverage in acceptance/acceptance_test.go, just like we do with --env-file.

@ekcasey added an acceptance test and manually verified that all the tests are actually passing

authors: ekcasey scothis

repo: buildpack/pack


text:
enable terse option for 'buildtest buildspec find invalid'

The two files that i edited was "tests/cli/test_buildspec.py" and "buildtest/cli/buildspec.py". I added a test to the test_buildspec.py and added some code to allow for the terse option in buildspec.py

It seems Black Formatter check is not passed.

@JeffreyFG please run buildtest style -a which will run all the style checks that should fix the black issue. Please see https://buildtest.readthedocs.io/en/devel/contributing/code_contribution_guide.html#running-stylechecks-via-buildtest-stylecheck. I would recommend you setup pre-commit with black and isort see https://buildtest.readthedocs.io/en/devel/contributing/code_contribution_guide.html#configuring-black-pre-commit-hook. This will run black and isort during git commit even if you forget to run buildtest style

@JeffreyFG I have tested this locally
This is the exception
(buildtest)  ~/Documents/github/buildtest/ [JeffreyFG-Issue-1092] buildtest bc find --terse invalid --error
The --terse flag can not be used with the --error option

This is with terse option and without header
(buildtest)  ~/Documents/github/buildtest/ [JeffreyFG-Issue-1092] buildtest bc find --terse invalid
buildspec
/Users/siddiq90/Documents/github/buildtest/tutorials/invalid_buildspec_section.yml
/Users/siddiq90/Documents/github/buildtest/tutorials/invalid_tags.yml
/Users/siddiq90/Documents/github/buildtest/tutorials/burstbuffer_datawarp_executors.yml
(buildtest)  ~/Documents/github/buildtest/ [JeffreyFG-Issue-1092] buildtest bc find --terse -n invalid
/Users/siddiq90/Documents/github/buildtest/tutorials/invalid_buildspec_section.yml
/Users/siddiq90/Documents/github/buildtest/tutorials/invalid_tags.yml
/Users/siddiq90/Documents/github/buildtest/tutorials/burstbuffer_datawarp_executors.yml

This is the table format
(buildtest)  ~/Documents/github/buildtest/ [JeffreyFG-Issue-1092] buildtest bc find invalid
                                  Invalid Buildspecs
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Buildspec                                                                          ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ /Users/siddiq90/Documents/github/buildtest/tutorials/invalid_buildspec_section.yml │
└────────────────────────────────────────────────────────────────────────────────────┘

This is the implementation of --error
(buildtest)  ~/Documents/github/buildtest/ [JeffreyFG-Issue-1092] buildtest bc find invalid --error
─────────────────────────────────────────────────────────────────────────── /Users/siddiq90/Documents/github/buildtest/tutorials/invalid_buildspec_section.yml ────────────────────────────────────────────────────────────────────────────
"'[/Users/siddiq90/Documents/github/buildtest/tutorials/invalid_buildspec_section.yml]: type badscript is not known to buildtest.'"
────────────────────────────────────────────────────────────────────────────────── /Users/siddiq90/Documents/github/buildtest/tutorials/invalid_tags.yml ──────────────────────────────────────────────────────────────────────────────────
"['network', 'network'] is not valid under any of the given schemas\n\nFailed validating 'oneOf' in schema['properties']['tags']:\n    {'oneOf': [{'type': 'string'},\n               {'$ref': '#/definitions/list_of_strings'}]}\n\nOn instance['tags']:\n    ['network', 'network']"
───────────────────────────────────────────────────────────────────────── /Users/siddiq90/Documents/github/buildtest/tutorials/burstbuffer_datawarp_executors.yml ─────────────────────────────────────────────────────────────────────────
"'create_burst_buffer_multiple_executors' is too long\n\nFailed validating 'maxLength' in schema['properties']['buildspecs']['propertyNames']:\n    {'maxLength': 32, 'pattern': '^[A-Za-z_.-][A-Za-z0-9_.-]*$'}\n\nOn instance['buildspecs']:\n    'create_burst_buffer_multiple_executors'"

authors: JeffreyFG Xiangs18 shahzebsiddiqui

repo: buildtesters/buildtest


text:
🛑 heartMap is down

In 6e1cf1e, heartMap (https://heartmap.buligadragos.work/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: heartMap is back up in 75f2a5e.

repo: buligadragos/UpTime


text:
Add CI job for testing against the starter repo

This make it so that the GitHub Actions CI pipeline will:

Checkout the starter repo. We'll look for a branch on the starter repo that matches the name of the branch being tested. If we can't find one we'll test against the main branch.
Checkout the core repo, also looking for a matching branch.
Alter the Gemfile in the starter repo to point to the local branch of jbuilder-schema and the core gems.
Run the Minitest suite of the starter repo
~Run the Super Scaffolding suite of the starter repo~ Edit: I'm not sure it's useful to run the Super Scaffolding tests, so I'm skipping it for now.

@newstler This should be good to go for running tests against the starter repo. There's one test failing on this PR related to https://github.com/bullet-train-co/jbuilder-schema/issues/74 but this doesn't change any shipped code so it should be safe to merge.

@jagthedrummer How urgent is this? I would wait when #74 is resolved if possible (we're looking for solution with @kaspth) to be able to release next versions with green tests.

@newstler not super urgent. I just figured that we should get this going sooner rather than later since we kept finding issues after a release instead of before.

@newstler looks like #74 is now resolved, so I rebased this branch and now it looks like everything is good to go.

@jagthedrummer Released this as v2.6.7 so should be good to check in BT gems without updating the minor version number.

authors: jagthedrummer newstler

repo: bullet-train-co/jbuilder-schema


text:
Menu with options

Is your feature request related to a problem? Please describe.
It isn't clear how or there isn't a component yet to make a menu that contains options that could be selected

Describe the solution you'd like
If it's already possible with the current components we could add an example for it in the Docs, If it's not possible with the current set of components we could consider adding a component that handles this use-case.

I would say SelectMenu might be what you are looking for... However, it doesn't have the ability to group sections yet...

SelectMenu acts more like an input.
I was thinking more of a menu that works with a Button like the chakra-UI Menu

Yeah true. Reakit exports a MenuItemRadio & MenuItemCheckbox component. So we could definitely make use of them. https://reakit.io/docs/menu/#menu-bar

Added in 1.2.0

repo: bumbag/bumbag-ui


text:
D3 Plugin Pattern

Use Let’s Make a (D3) Plugin pattern for consistent result

Closing - #35 duplicate


text:
Letzter Commit vor 3 Jahren

Finde ich sehr schade, dass das Repo nicht mehr verwaltet wird…
Obermenge von #54

Wenn es da im Netz noch Quellen gibt die aktuell gehalten werden, dann können wir ein Skript schreiben um sie dort Runterzuladen evtl. in md umwandeln. @UgnilJoZ Hast du eine idee?

@hhirsch Theoretisch gibt es ja noch das Repo https://github.com/bundestag/gesetze-tools, das alles mitbringen sollte, um die Gesetze halbautomatisch einzupflegen. Auch dieses wurde vor gut zwei Jahren das letzte Mal geändert, müsste aber noch gehen. Ich werd das mal ausprobieren.

Genau, grundsätzlich sollte alles noch gehen, aber vielleicht eben auch nicht. Gerne auch pull requests an das Repo. Ich gebe auch gerne jedem, der einen vernünftigen Pull Request zustande bringt, Schreibrechte geben.

Kümmert sich denn aktuell jemand darum? Das Gespräch ist ja auch schon eine Weile her... Ich habe leider nicht die Python-Kenntnisse.

Kümmert sich denn aktuell jemand darum? Das Gespräch ist ja auch schon eine Weile her... Ich habe leider nicht die Python-Kenntnisse.

Kennt jemand aktuellere Quellen als gesetzte-im-internet.de?
Dort scheint es zum Beispiel keine aktuelle Version des Bundesdatenschutzgesetz (BDSG) in der Fassung von 2018 zu geben...

@darkdragon-001 gesetze-im-internet.de ist das offizielle Portal für Gesetze. Das Bundesgesetzblatt stellt die Änderungsgesetze zeitnaher bei sich zur Verfügung, die Änderungen müssen dann aber erst (offenbar von Hand) in den Gesetzestext übertragen werden.

Wie bedauerlich, dass dieses Projekt aufgegeben wurde

Schade, wenn es nicht mehr gewartet wird, sollte der Eigentümer das Repository konsequenterweise auf archived setzen.

Es gibt wieder eine Seite, welche alle aktuellen Gesetztes-Veröffentlichungen online stellt. Die Frage ist, nur, ob diese Plattform nicht vom Dumont Verlag in Grund und Boden geklagt wird.
https://offenegesetze.de/

wolterskluwer-online bietet Verlinkungen zu Paragrafen und einen praktischen Versionsvergleich. Zumindest diese beiden Features scheinen kostenlos zu sein.

As indicated in https://github.com/bundestag/gesetze/pull/58#issuecomment-1033097288 why not run this update automatically via GitHub actions?

I can help with workflow setup if we decide we want that.

I can help with GitHub Actions workflow setup if we decide we want that.

We want that!
Please reference https://github.com/bundestag/gesetze-tools/issues/16
Consider to implement the workflow on the https://github.com/bundestag/gesetze-tools/ repo. ❤

authors: ISSTJ UgnilJoZ darkdragon-001 hhirsch keilw laulens12 mdschweda mk-pmb rugk stefanw tom-richter ulfgebhardt

repo: bundestag/gesetze

license: Unlicense


text:
gem error

Error details
Errno::EACCES: Permission denied @ rb_file_s_rename - (/var/folders/vj/dkscdd2x3wbftywhjf9d8lx80000gn/T/bundler-compact-index-20170101-53146-7cinnb/versions, /Users/pallaviaggarwal/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/versions)
  /Users/pallaviaggarwal/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/fileutils.rb:528:in `rename'
  /Users/pallaviaggarwal/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/fileutils.rb:528:in `block in mv'
  /Users/pallaviaggarwal/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/fileutils.rb:1571:in `block in fu_each_src_dest'
  /Users/pallaviaggarwal/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/fileutils.rb:1587:in `fu_each_src_dest0'
  /Users/pallaviaggarwal/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/fileutils.rb:1569:in `fu_each_src_dest'
  /Users/pallaviaggarwal/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/fileutils.rb:517:in `mv'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:55:in `block in update'
  /Users/pallaviaggarwal/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:29:in `update'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:65:in `update'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:56:in `update_and_parse_checksums!'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/fetcher/compact_index.rb:67:in `available?'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/fetcher/compact_index.rb:15:in `call'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/fetcher/compact_index.rb:15:in `block in compact_index_request'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/fetcher.rb:157:in `use_api'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/source/rubygems.rb:332:in `block in api_fetchers'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/source/rubygems.rb:332:in `select'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/source/rubygems.rb:332:in `api_fetchers'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/source/rubygems.rb:337:in `block in remote_specs'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/index.rb:10:in `build'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/source/rubygems.rb:336:in `remote_specs'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/source/rubygems.rb:83:in `specs'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/definition.rb:261:in `block (2 levels) in index'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/definition.rb:259:in `each'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/definition.rb:259:in `block in index'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/index.rb:10:in `build'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/definition.rb:256:in `index'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/definition.rb:250:in `resolve'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/definition.rb:174:in `specs'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/definition.rb:162:in `resolve_remotely!'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/installer.rb:225:in `resolve_if_need'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/installer.rb:78:in `run'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/installer.rb:24:in `install'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/cli/install.rb:71:in `run'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/cli.rb:189:in `install'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/cli.rb:20:in `dispatch'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/cli.rb:11:in `start'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/exe/bundle:34:in `block in <top (required)>'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib/bundler/friendly_errors.rb:100:in `with_friendly_errors'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/exe/bundle:26:in `<top (required)>'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/bin/bundle:22:in `load'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/bin/bundle:22:in `<main>'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/bin/ruby_executable_hooks:15:in `eval'
  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3/bin/ruby_executable_hooks:15:in `<main>'

Environment
Bundler   1.13.7
Rubygems  2.6.8
Ruby      2.3.3p222 (2016-11-21 revision 56859) [x86_64-darwin16]
GEM_HOME  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3
GEM_PATH  /Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3:/Users/pallaviaggarwal/.rvm/gems/ruby-2.3.3@global
RVM       1.28.0 (latest)
Git       2.11.0
rubygems-bundler (1.4.4)
--- TEMPLATE END ----------------------------------------------------------------

See the other Permission denied issues. A suite of permission errors have been addressed by #5007 which will release in Bundler 1.14.
Let us know if you're still having trouble and none of those solutions worked for you.

I'm closing this for now. If you're still experiencing your original issue don't be afraid to re-open this ticket.

authors: colby-swandale hmistry pallavi16

repo: bundler/bundler


text:
backport: bundle clean native extensions for gems with a git source

Cherry-pick https://github.com/bundler/bundler/pull/7059 to 1-17-stable since, as https://github.com/bundler/bundler/issues/7058 mentioned, the bug is present on 1.17.3

This test error seems unrelated to this PR
ERROR:  Error installing rubocop:
	parallel requires Ruby version >= 2.2.

Thanks for the PR. I've marked the PR this references with a backport for when we organize the next Bundler 1 release which will get cherry-picked.

authors: colby-swandale dylanahsmith