text:
[FEATURE] Expiry time adjustable on lower than a day granularlity

Enhancement Proposal
This enhancement is for testing purposes.
Currently if we would like to verify TLS certificates workflows, we need to manually tweak in the code to get a fast return.
This gets even worse when aiming for automated tests.
Our charm (Opensearch) is offering multiple certificates-rotatinons related operations (seamlessly) to clients. We would really like to have a solid testing around that.
May there be a way to help us out on this...? (Like a "secret environment variable" or so...?)
Thank you.

The problem has two components:

The library needs to support smaller unit of times than days. This has been addressed in #240 where the validity can be set to any timedelta.
The TLS certificates providers need to leverage this feature and expose it via juju configuration options. We are actively working on this for self-signed certificates in this series of PR's

https://github.com/canonical/self-signed-certificates-operator/pull/242: Fixing issues with CA certificate renewal
https://github.com/canonical/self-signed-certificates-operator/pull/236: Allowing the user to set any time delta with config options: ex. 5m or 365d.

Closing as this was implemented in self-signed-certificates. For more information, read the charm's configuration options descriptions.

authors: gruyaume juditnovak

repo: canonical/tls-certificates-interface


text:
Stopped schedule

This morning all of my agents stopped following schedules. Various agents run on different schedules from every minute, 5,10, 30, 1 hour, 12 hours etc. I also have several Scheduling agent as well following schedules.
The queue is empty and I have restarted my server several times but still not working. How can I check what is wrong?

Updated to latest huginn and its working.

source: gharchive/issue

repo: cantino/huginn

license: mit

license_type: permissive

license_source: bigquery


text:
OIDC Callback Url is not conform to RFC3986

Describe the bug
The OIDC authorisation code flow callback url does not conform to rfc3986.
For example a callback url used by zitadel can look like this: https://openidconnect.net/callback?code=c-<some-secret-chars>&state=<state>. <some-secret-chars> looks like base64-encoded bytes incl. padding, but the padding is not encoded correctly (<some-secret-chars> often ends with == which does not conform to rfc3986 section2.2). There are oidc certified client libraries which cannot handle this (ex. IdentityModel.OidcClient).
To Reproduce

Setup a project and an application (native, authorisation code, auth method none) in zitadel
Whitelist https://openidconnect.net/callback as a callback url
Go to https://openidconnect.net/
Click configuration and enter the details provided by zitadel
Open the chrome devtools network tab and set the Preserve log flag
Click START
Authenticate using zitadel
Check the network logs for a request url starting with https://openidconnect.net/callback. This callback url is not conform to RFC3986.

Expected behavior
The callback url should conform to RFC3986 and oidc certified client libraries should be able to handle it correctly.
Additional context
It could be sufficient to switch from base64 (rfc4648 section 4) to base64url encoding (rfc4648 section 5).

Thx for reporting this.
Opinions @livio-a

@latonz thanks for reporting
https://github.com/caos/zitadel/issues/1588 will close this issue
will be deployed to Production tomorrow along with Version 1.0

authors: fforootd latonz livio-a

repo: caos/zitadel

license_source: github-api


text:
How to import and export encrypted database - Capacitor Sqlite Plugin?

Hello developers,
I am using the capacitor sqlite plugin with vue.js and developing the native mobile apps.  The issue I am facing is, after encrypting the database the exportToJson function does not provide the valid json that could be imported later. This is generating some expData object having base64 encoded string.
My question is how could I import this base64 encoded string by using importFromJson method? Currently its showing invalid json all the time.
Please help as soon as possible.
Thanks and keep the good work up.

Is it not possible to import data when expData contains a base64 string? Is there an alternative solution? Could we potentially utilize an encrypted database for simultaneous import and export?
@patdx  @cosentino  @oscarfonts  @gion-andri

@sadamameer Can you share your code or a simple repro of your code in github so i see what is wrong to help fixing as i have a code which works well.

@jepiqueau  Thanks for the response. I am sharing the code snippets that I am using to export and import the encrypted database.
EXPORT TO JSON METHOD
var db: SQLiteDBConnection;

db = await this.$sqlite.createConnection("databse_name");

await db.open();

await db.exportToJson("full")
.then((data) => {
  // data is the a json string with the format like this:
  // {
  //   expData : base64 string
  // }
});

IMPORT FROM JSON METHOD
`backup is the exported json string with the format :`

// {
//   expData : base64 string
// }

const jsonstring = JSON.stringify(backup);
await CapacitorSQLite.isJsonValid({ jsonstring });
await CapacitorSQLite.deleteDatabase({ database : "databse_name" });
await CapacitorSQLite.importFromJson({ jsonstring });

The encrypted database is working perfectly fine.
The exporting part is also perfect.
Getting error in importing function "Must provide a valid json object"

Please help me out in this situation. Your quick support will be appreciated.
Thanks!

@sadamameer if i look at this
db = await this.$sqlite.createConnection("databse_name");

means to your database is not encrypted meaning that the export full must not be encrypted meaning that there is no expData
the correct code should be something like

        let jsonObj: any = await db.exportToJson('full');
        console.log(`returned JSONObject: ${JSON.stringify(jsonObj.export)};
        const isValid = (await CapacitorSQLite.isJsonValid({ jsonstring: JSON.stringify(jsonObj.export) })).result;
        if (isValid) {
            await CapacitorSQLite.deleteDatabase({ database : "databse_name" });
            await CapacitorSQLite.importFromJson({ jsonstring: JSON.stringify(jsonObj.export)});
       }

@jepiqueau
I appreciate your assistance. The previous problem has been resolved, but I've encountered a new and puzzling error.
When I generate a debug build, the database and SQLite plugin function correctly. However, when I create a release build, I consistently encounter an error message that states: "Capacitor SQLite Plugin is not implemented on Android."
I kindly request your help in resolving this issue. Your assistance would be greatly appreciated.

@sadamameer can you describe the procedure used to create the release build

@jepiqueau I adhere to a straightforward process where I enable resource minification and shrinking, followed by generating the release build or signed APK. If I omit the resource minification and shrinking, the release build functions correctly, but the code remains readable if someone were to decompile the APK. Consequently, I employ ProGuard to perform code minification, shrinking, and obfuscation. While this procedure works seamlessly for most Capacitor plugins, such as camera and geolocation, it encounters issues with the Capacitor SQLite plugin.

@sadamameer did you look at docs/AndroidMinify.md which has been added with the last release of the plugin

Yes, I already did the same, and added these 2 statements in the Proguard Rules.

-keep class net.sqlcipher.** { ; }
-keepclassmembers class net.sqlcipher.* { *; }

but still, its showing the same error.

@sadamameer @muuvmuuv Marvin, can you help on this as you went through all the process

What is the log output? Guess its some func that gets mangeled

@sadamameer any progress on this as i do not have any feedback i close the issue

authors: jepiqueau muuvmuuv sadamameer

repo: capacitor-community/sqlite

license: MIT


text:
Long numbers

I'm having Bad request using this number:
+345906566798696
Is it too long?

Hello!
According to the information available on Wikipedia, the maximum length of a telephone number in Spain, including the country code, is 11 digits. The number you've provided, +345906566798696, exceeds this limit and therefore appears to be incorrect.
If you are confident that the number is correct, could you please provide any additional information about this phone number's format? Sometimes, phone numbers may include extra digits for various reasons, such as extensions or calling through certain carriers, but these are typically not part of the standard phone number.
Please double-check the number and ensure that it adheres to the standard format.
Thanks!

The number is correct.
It's from a m2m simcard from this provider.
It's working in Spain, if you send a message to that number it receives.

Hello!
I've been thinking about the situation with the non-standard phone numbers you're dealing with. What I can do is add an option to the API that allows you to disable phone number validation. This way you can bypass the check. But just a heads up, with validation turned off, you'll need to make sure the numbers are clean, starting with a + and followed only by digits, in line with the E.164 format.
It'll take a little bit of time for me to update both the client and server parts of the app to make this happen. I'll definitely let you know as soon as the updates are up and ready for you to use.
Thanks!

Hello Aleksander,
Thank you very much, if I can help with a PR please let me know.

Hello!
I've implemented the feature to disable phone number validation that we discussed. A test version is now available for you to try out. You can download it from the following link: https://github.com/capcom6/android-sms-gateway/releases/tag/v1.6.1
To disable phone number validation, please append the query parameter skipPhoneValidation=true to your API requests. For example, POST /3rdparty/v1/message?skipPhoneValidation=true.
I would appreciate it if you could test this new feature and let me know if it works as you expected.
Thanks!


text:
Parsing crashes on game with {...} indicating incomplete move log

The following PGN appears in the http://chessgames.com archive of games played in 2014:
[Event "Bunratty Masters"]
[Site "Bunratty Co. Clare, Ireland"]
[Date "2014.02.08"]
[EventDate "2014.??.??"]
[Round "3"]
[Result "1-0"]
[White "Drahoslav Stejskal"]
[Black "Brendan Lyons"]
[ECO "B01"]
[WhiteElo "2129"]
[BlackElo "1888"]
[PlyCount "60"]

1. e4 d5 2. exd5 Nf6 3. Bb5+ Bd7 4. Be2 Bf5 5. Nf3 Nxd5 6. c3
e6 7. d4 Bd6 8. Bg5 f6 9. Be3 Nf4 10. Bxf4 Bxf4 11. Nh4 Be4
12. Bc4 Qd6 13. Qg4 Nd7 14. Qxe6+ Qxe6 15. Bxe6 Bc6 16. a4
O-O-O 17. O-O Bg5 18. Nf3 Bxf3 19. gxf3 Rhe8 20. Bc4 Nb6
21. Bd3 g6 22. Na3 c5 23. Nb5 Re7 24. dxc5 Nd7 25. Bc4 Nxc5
26. Rad1 Bf4 27. b4 Nd7 28. Nd6+ Kc7 29. Ne4 f5 30. Ng3 {...}
1-0

Trying to parse this with PGN raises the following error:
Whittle::UnconsumedInputError: Unmatched input "{...}\n1-0" on line 19
    from /Users/greg/.rvm/gems/ruby-1.9.3-p362/gems/whittle-0.0.8/lib/whittle/parser.rb:251:in `block in lex'
    from /Users/greg/.rvm/gems/ruby-1.9.3-p362/gems/whittle-0.0.8/lib/whittle/parser.rb:250:in `tap'
    from /Users/greg/.rvm/gems/ruby-1.9.3-p362/gems/whittle-0.0.8/lib/whittle/parser.rb:250:in `lex'
    from /Users/greg/.rvm/gems/ruby-1.9.3-p362/gems/whittle-0.0.8/lib/whittle/parser.rb:204:in `parse'
    from /Users/greg/.rvm/gems/ruby-1.9.3-p362/gems/pgn-0.0.6/lib/pgn.rb:23:in `parse'
    from (irb):5
    from /Users/greg/.rvm/rubies/ruby-1.9.3-p362/bin/irb:16:in `<main>'

I think that "{...}" is meant to indicate an incomplete move log. Even though it doesn't appear in any PGN documentation that I can find. Not sure what the best policy in parsing is here, however the current result where I'm PGN crashes midway through parsing this archive of ~10,000 games and forces me to write code that splits up the games myself with a regex and iterates over the resulting strings in order to pass them one-by-one into PGN to rescue just the one that crashes is probably not the optimal situation.

Merged & released https://rubygems.org/gems/pgn/versions/0.1.0
Thanks for reporting this. Sorry about the wait!

authors: atduskgreg capicue

repo: capicue/pgn


text:
Wrong usage of application symbol

Originally came from https://github.com/xuwupeng2000/capsitrano-scm-gitcopy/issues/33.
I'm not sure if this is NOT a Capistrano issue. But since everything used to work fine in staging before implementing scm-gitcopy into production I will post it here.
In my deploy.rb my application symbol is set to:
set :application, 'Semcoglas'
set :deploy_to, '/var/www/semcoweb'

I always regarded application as App name.
When I run cap production deploy everything works fine so far. All paths are used correctly based on the deploy_to symbol.
But then, when Composer is supposed to run, the path suddenly changes to /var/www/Semcoglas <- name of the :application symbol.
Of course I get a Could not open file: /var/www/Semcoglas/shared/composer.phar error.
I tried without defining :application and indeed the wrong path will become /var/www/shared/....
Any idea what is happening here?

For instance I had to set :application separately in my staging deploy files to make composer get the correct shared path:
# staging.rb

set :application, 'semcoglas'
set :deploy_to, '/var/www/semcoglas'
set :scm, :git

set :composer_install_flags, '--no-dev --no-interaction --optimize-autoloader'

SSHKit.config.command_map[:composer] = "php #{shared_path.join("composer.phar")}"

# production.rb

set :application, 'semcoweb'
set :deploy_to, '/var/www/semcoweb'
set :scm, :git_copy

set :composer_install_flags, '--no-dev --no-interaction --optimize-autoloader'

SSHKit.config.command_map[:composer] = "php #{shared_path.join("composer.phar")}"

I just saw that this is related to issue https://github.com/capistrano/composer/issues/39 by @gagarine.
@swalkinshaw closed that one as not an issue.

repo: capistrano/composer


text:
Added link to sonar home dashboard in sonar widget

This PR adds a link to the Sonar instance for the project as determined by the collector.

The 'View All' link can be found on the widget near the header for the scan results.
Link does not go to sonar page until data is loaded into the widget, since data has not been populated yet it would not know where to go.
Tried to achieve same look and feel for links as in other places in application.

Resolves #1122

@brennanananan  - As we enable the link in Sonar widget "View All", can we do a check on underlying url in DefaultSonarClient.java -> currentCodeQuality()
if(project.getInstanceUrl().endsWith("/")){
codeQuality.setUrl(project.getInstanceUrl() + "dashboard/index/" + project.getProjectId());
}else{
codeQuality.setUrl(project.getInstanceUrl() + "/dashboard/index/" + project.getProjectId());
}
Eg:
http://localhost:9000/dashboard/index/1 ----> (valid url)
http://localhost:9000//dashboard/index/1 ----> (invalid url)

@nireeshT I have added the features as suggested. Thank you for the feedback.

@tabladrum  LGTM

@brennanananan Thanks for the contribution.

@brennanananan @tabladrum LGTM

source: gharchive/pull-request

authors: brennanananan nireeshT satishc1

repo: capitalone/Hygieia


text:
Some documentation updates

Just a couple minor updates to the getting started documentation.

remove need for executing package goal in Maven since it already executes at an earlier phase.
fix the XML rendering for the Maven proxy configuration docs.

P.S. I've signed the contributor agreement.

LGTM

LGTM

authors: amaltson satishc1 tabladrum


text:
AMI actions: Remove permissions

We operate a "hub and spoke" VPC that builds AMIs for other accounts to use.  Rather than deregistering AMIs I would like to revoke permissions on the AMI.
Another use case: enforce that AMIs are not being shared with other accounts.

both sounds good,
so an action like
policies:
   - name: yank-old-ami-access
     resources: ami
     filters:
        - image-age: 90
     actions:
        - remove-launch-permissions

with additional customization options re removing additional account access by id.

this was added in 0.8.19.5

authors: eisenhowerj kapilt

repo: capitalone/cloud-custodian


text:
Add 'rds-snapshot' resource.

Add resource and associated age filter and delete action
Add documentation
Add ebs-snapshot documentation
Add test and Placebo data
Fixes #173

There was no skew resource type for RDS DB Snapshots so I used the old-school ResourceManager base class.

Coverage increased (+0.03%) to 82.549% when pulling 87f0040fef5a98e12f223d14ddf9824bbc8fa322 on ewbankkit:rds-snapshot into 4803885f576b283bc72f645a7b8a8bc5c535a628 on capitalone:master.

ugh.. just merged something which invalidated this, re skew base, its really easy to roll your own, see the bottom of vpc.py for a custom one.

will do.

OK, modified as requested

Coverage increased (+0.04%) to 82.559% when pulling 6eaa6f5d22168abb465df0eaa9538212dc869e50 on ewbankkit:rds-snapshot into c7345e896e1b3b3253901de14117fed30ab958e8 on capitalone:master.

Coverage increased (+0.08%) to 82.599% when pulling d2f7563024493c00aaf9d64175c6af2821169810 on ewbankkit:rds-snapshot into c7345e896e1b3b3253901de14117fed30ab958e8 on capitalone:master.

lgtm

authors: coveralls ewbankkit kapilt


text:
removing requirements.txt

We don't really need a specific requirements.txt since developers can just pip install -e .[dev]

@NikhilJArora @ak-gupta ping 😄

I think we need to remove the ref to requirements.txt in this workflow with this change. https://github.com/capitalone/datacompy/blob/1de2f37f75064422be5f82cd8f35a0859f0fb8a0/.github/workflows/publish-package.yml#L23

Closing in favour of #229

authors: NikhilJArora fdosani

repo: capitalone/datacompy


text:
Fix Requirements to match dataprofiler - scipy>=1.10.0

Closes
https://github.com/capitalone/synthetic-data/issues/280
https://github.com/capitalone/synthetic-data/issues/340
Synced requirements between dataprofiler and synthetic-data
Rationale for choosing dataprofiler>=0.10.3 was based on trying to sync on scipy>=1.10.0
https://github.com/capitalone/DataProfiler/blob/0.10.3/requirements.txt#L13
dataprofiler 0.10.3 - increased compatibility to scipy>=1.10.0 ;
Please review and let me know if you require any changes.
Thanks & regards.

@taylorfturner I was not able to understand the error - Do you know what I missed here .
`pyupgrade................................................................Failed

hook id: pyupgrade
exit code: 1
files were modified by this hook`

@rxm7706 approved the checks run -- will take a look later in the day to ensure everything is looking good. Thanks for the contribution! CC @tazitoo

checks are looking good -- will need an update branch #343 merged @rxm7706. Thanks!

@taylorfturner Thank you ! please review - updated branch.

Hi @taylorfturner is this stuck -  or did I miss something here, anything for me to do. Thank you.

oh thanks for the ping @rxm7706. oddly the mend license check isn't passing... I'd recommend an empty commit --allow-empty to trigger a check re-run and we'll see if that resolves. Thanks!

oh thanks for the ping @rxm7706. oddly the mend license check isn't passing... I'd recommend an empty commit --allow-empty to trigger a check re-run and we'll see if that resolves. Thanks!

Done - Waiting Approval ! @taylorfturner

oh thanks for the ping @rxm7706. oddly the mend license check isn't passing... I'd recommend an empty commit --allow-empty to trigger a check re-run and we'll see if that resolves. Thanks!

Done - Waiting Approval ! @taylorfturner

If it doesn't pass the check, we can do some more research as to the cause.

reopening to re-trigger checks

repo: capitalone/synthetic-data


text:
Page misalignment

This is a weird new bug that seems to be a side effect of 46e302c4fb99b7c5957295ccff4ebf2fc5022907. The page is somehow misaligned in my reader. The text is properly aligned at the start of each chapter, then it slowly moves to the left with the next page shifting out from the right, the farther away you move from the chapter start.
It's hard to explain so I took some screenshots instead :

I don't understand why this would even happen in the epub reader since the reader is just supposed to render text.
Hopefully, it makes sense to you.

It kinda does. I've set a global style on body for margin, which I think is getting re-applied on every page.
Can you try a rebuild after removing the following 3 lines from style.css:

https://github.com/captn3m0/cosmere-books/blob/46e302c4fb99b7c5957295ccff4ebf2fc5022907/style.css#L41
https://github.com/captn3m0/cosmere-books/blob/46e302c4fb99b7c5957295ccff4ebf2fc5022907/style.css#L113-L114

And see if it fixes the issue? I'll try installing Icecreame over wine to see if I can figure this out better.

Tried it, no change unfortunately.

Try removing the entire body section: https://github.com/captn3m0/cosmere-books/blob/46e302c4fb99b7c5957295ccff4ebf2fc5022907/style.css#L36-L42
If that doesn't work, it has to be the text-align: justify, which will get us back to the center aligned text. Will see if I can find an epub css template.

Nope, I removed the body and the text-align and it broke the justification but the page overlap remained. I then removed the stylesheet argument and it fixed it (but justify broke of course).
https://github.com/captn3m0/cosmere-books/blob/46e302c4fb99b7c5957295ccff4ebf2fc5022907/methods.rb#L44
Then I started to progressively delete anything I saw in the css (I don't understand any of it) until it worked.. I had to do a lot of tests before I realized that if I don't delete the ebook from the reader, then empty the trash, then close the app before opening the file, then it would somehow load a cached version of it...
Anyways, I found the faulty line : https://github.com/captn3m0/cosmere-books/blob/46e302c4fb99b7c5957295ccff4ebf2fc5022907/style.css#L108
Just delete that line (which ironically says "increasingly indent" ) and it will fix it!

Thanks for the debug, will commit the fix. (I don't think this should affect the PDF version, but have to confirm)

license: WTFPL


text:
feat: Add support for deployment labels

Modification

Add extraLabels to values and to deployment template.

Checklist

[x] Chart version bumped
[x] README.md updated

Hey folks, can I get a review here?

Checking

repo: caraml-dev/helm-charts


text:
Please include how to cite your repository

Describe the change
Please include instructions in the repository that show how to properly cite your repository in case someone uses it for their own projects. This is primarily an academic requirement, so I understand if the maintainers don't have the time to see this through.

@APratham please feel free to open a PR that adds the CITATION documentation for Carbon.

repo: carbon-app/carbon


text:
[ValueCard] Default FontSize changed from 42 to 18 to prevent truncation of text

What package is this for?

[x] React
[ ] Angular

Describe the bug
ValueCard's default size is currently 42 which is quite large and leads to truncation of text. Customers can change the size of the font in the advance settings, but some have hundreds of cards on a dashboard. This would be an annoyance to the customer to have to change the font size of hundreds of cards just to be able to see the text in the value card.
To Reproduce
Steps to reproduce the behavior:

Go to https://carbon-addons-iot-react.com/?path=/story/1-watson-iot-valuecard--small-long-no-units
ValueCard text is truncated after 10 letters for a size small card

Please create a reduced test case in CodeSandbox:
https://codesandbox.io/s/github/carbon-design-system/carbon-addons-iot-react/tree/next/packages/react/examples/codesandbox

Expected behavior
Default font size of Value Card should be 18.
Environment/versions:

OS: MacOS
Browser:chrome
carbon-addons-iot-react version: v2.147.0-next.43

Additional context
If applicable, add screenshots to help explain your problem.
Add any other context about the problem here.
Specific timeline issues / requests
Do you want this work within a specific time period? Is it related to an
upcoming release?
NB: The core contributors will try to work with your timeline, but it's not
guaranteed. The earlier you make a request in advance of a desired delivery
date, the better!

@dianatran18 I believe this is working as designed? My assumption is that small value cards do not have smaller type, and should not be used with large strings.

Yes, you're correct @JordanWSmith15. Value cards are generally used display KPIs or metrics as a summary, and not large strings of text. The reason why we have one set size for the value is to not have varying sizes of text all over the page, especially if the value cards are adjacent to each other.
For numeric values, we have guidance on how to abbreviate large numbers is space is limited, with the full value displaying in a tooltip:
https://pages.github.ibm.com/ai-applications/design/content-guide/abbreviations-symbols/overview#abbreviating-words-related-to-numbers

@eosineye1 I am going to invalidate this work item, as working-as-designed. However, keep in mind that there is an override property that allows you to change the type size to 18

.


text:
[Table] callback issues when single select with Radio buttons props are set

What package is this for?

[x] React
[ ] Angular

Describe the bug
There are two defects surrounding the single select behavior with radio buttons.

On line 252 of TableBodyRow.jsx we are calling onRowSelected inside an onChange event for the TableCell. We are also calling the onRowSelected when the RadioButto element is clicked on line 265. We should only be calling this once.
You can see this in our storybook here. Make sure options.hasRowSelection is set to 'single' and the options.useRadioButtonSingleSelect options is clicked in the 'Selections and actions' knob tab. Then open the actions panel and click on the radio button. You will see the callback fired twice.
With the same story and knobs active try clicking on the row in an area outside of the radio button cell with the actions tab open. You will see that an onRowSelected and an onRowClicked callback are fired. Notice that the radio button does not show a selected state. This most likely stems to when we added the radio buttons for single selection. Previously, a user could click anywhere and it would select the row. @JordanWSmith15 @dianatran18 can you chime in with whether we should continue to allow the clicking on a row to fire the onRowSelected and update the radio button accordingly or  disallow row clicks to fire the onRowSelected when we are using radio buttons?

@JordanWSmith15 This is related to the defect being worked by Tom for Graphite.
To Reproduce
Steps to reproduce the behavior:

Go to this story
Got to the 'Selections and actions' knob tab in the knob pannel.
Make sure options.hasRowSelection is set to 'single' and the options.useRadioButtonSingleSelect options is clicked
Open the actions panel
Click on the radio button in the table
See the action firing twice.
Click anywhere in the row and see the onRowSelected callback being fired.

We will want to make sure that our behavior for single select without the radio buttons and the multi-select functionality is preserved.

I would follow what Carbon's radio button selection does, and only have it on the radio button, not the full row.
I feel like selecting the full row can conflict with other potential actions on the row too, like inline row actions, links, etc.
Also, note that Carbon's also has a selected row state but ours does not. Was that intentional? For consistency with other selected state use cases, we should add that back in. I actually realized we don't have selected states for the checkbox variant too. We have that in our designs along with Carbon, so we'll need to align on that too.


text:
[PageTitleBar] update style to match new spec

Closes #1661
Summary

As part of the new DashboardEditor, a new design spec has been created for the header (PageTitleBar). This PR updates the styling to match those new specs

Change List (commits, features, bugs, etc)

Updated styles to match spec
Updated story to match a common DashboardEditor header
Changed a deprecated icon in the TileGallery stories to a similar valid icon to remove warning in console

Acceptance Test (how to verify the PR)

Go to each PageTitleBar story and ensure they match the specified design seen in the above issue

@sstone2423 is there an internal pal issue for this to document the source of the spec outlined in https://github.com/carbon-design-system/carbon-addons-iot-react/issues/1661?

@dianatran18 @lukefirth could you take a look and validate this from a design perspective? Here's a link to the PageTitleBar stories in the deploy preview

@tay1orjones I've added the internal link to the issue and commenting it here: https://github.ibm.com/wiotp/monitoring-dashboard/issues/1363
That issue is mainly about the DashboardEditor, where the PageTitleBar updates are a side effect

This is good to go on the design side, until we make further changes to the overall page header.
Thanks!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
Component > Content Switcher > #a11y contrast issue

http://carbondesignsystem.com/components/content-switcher/code
The hover color does not meet AA contrast requirements with the light blue background and white text.
In Firefox 56.0 on a PC a black dotted outline is appearing within the buttons as I tab through them. moz-focus-inner may help remove that.
Your choice of light blue border does not have significant contrast. You might consider using a similar treatment to your Buttons with an inner border. You are underlining the text on focus so technically you still have a highly visible focus indicator with that.

Hey @arbydev , thanks for your comment!
We are doing a large hover audit on each component as a future task item, so we will keep this in mind. Could you point us to some helpful guidelines on :hover color contrast states? Based on the W3C guidelines, I wasn't seeing anything specifically on :hover.
For the :focus states, what tool are you using to check for "significant contrast"? I'd like to better understand what tests this component is passing or failing.

Closing this issue due to lack of response from issue creator. Please feel free to re-open if needed.

authors: arbydev bsonefeld marijohannessen

repo: carbon-design-system/carbon-components


text:
feat(project): enable gatsby feature flags

This PR takes the opportunity to enable some feature flags to also update some dependencies on react, gatsby, and other related packages in the ecosystem.
Changelog
New
Changed

Update dependencies for the project, namely react and gatsby
Update gatsby-config.js with feature flags to help speed up initial dev server and incremental rebuilds

Removed

Note for content reviewers: seems like the files got formatted with prettier 👀

@joshblack is this still something we need to merge or not anymore?

authors: andreancardona joshblack

repo: carbon-design-system/carbon-website


text:
feat(tabs): add experimental tabs

Closes #440
New
Adds experimental tabs to website
Bugs
Styling on website is changing for tabs component.

padding in between the tab lines disappears
in the responsive view, the arrow is inverted (i.e. starts right side up)

I don't think the carbon-components repo has these 2 bugs. Still need to figure out what the problem is. Also should we have less tab examples so that the tabs don't come off the example container?

@jnm2377 you might have to add some styles in component-overrides.scss to fix the style overrides. We've had to do this with a few components on the website.


text:
refactor(ComboButton): convert to typescript

Contributes to #4256 and https://github.com/carbon-design-system/ibm-products/issues/4257
Adds TypeScript types to ComboButton component.
What did you change?
packages/ibm-products-styles/src/components/ComboButton/_combo-button.scss
packages/ibm-products/src/components/ComboButton/ComboButton.js
packages/ibm-products/src/components/ComboButton/ComboButton.tsx
packages/ibm-products/src/components/ComboButton/ComboButtonItem/index.tsx

How did you test and verify your work?
Storybook

Ah yes! I'll update it

Ran snapshot update and it doesn't update anything, I think because ComboButton isn't released so it won't trigger a snapshot update.

repo: carbon-design-system/ibm-products


text:
Android SDK scan credit card but does not produce output.

I am using card io Android SDK library (version 5.0.0) in Eclipse. The application opens the scan page and it scans the credit card but does not produce output ( showing credit card information).
Please see the image URL of the screen short (scanning credit card): http://i.imgur.com/GFV3IKG.png
Please help me on find out my mistake. I have tested my application on Samsung S4,Moto E, Sony xperia Z and Samsung S3.
My credit  card number provider is "ICICI Bank" and number starts with 4.
Note:
I have created Android project in Eclipse and please see the following link how I used processor libraries in my project (it may has problem) : http://i.imgur.com/iicjKjm.png

The mobile phone does not vibrated when scan the credit card. what you mean by pattern here (I assumed its card type supported, listed in the http://card-io.github.io/card.io-Android-SDK/io/card/payment/CardType.html page.   am I right?). My credit card is powered by VISA. currently we do not have iOS.

Yes, my card starts with 4 and its 16 digits long.

I have checked in iOS with same card. its works but it takes long time to recognize and shows the output and some time does not recognize even if hold for a long time. In Android case it does not work. please help me.

hello you all.
I faced the same problem. I 've tested on Note 3(Android 4.4) and Nexus 7 running Android 5.0.1.
Do you guys have found out how to resolve the problem here ? Please help me.

hi @braebot ,
Thank for your quick response.
But I 've just pulled the latest source last nigh.
At the beginning tested with the sample code here
https://github.com/card-io/card.io-Android-SDK (tested with Android studio, have this line in gradle compile 'io.card:android-sdk:5.0.0') , but it did not work then I pulled the libs from https://github.com/card-io/card.io-Android-source then built the sample app. But I got the same problem too.
Any suggestion, I think I made some mistaken :(

Hi,
I have tested the sample application yesterday, but it never scan my credit
cards. I am sure. I have placed library files correctly in libs folder as
shown in your Paypal example (only difference is, I have used cardio.jar
file which got from extracting ".AAR" file and renamed classes.jar into
cardio.jar). Please help me and let me know if your want to see my sample
application.
With thanks and regards,
M.A.Murali
Mobile : +91-9043959321 , +91-7639539122
Email:    murali6060.android@gmail.com
On Thu, Apr 23, 2015 at 7:55 AM, Minh Nguyen notifications@github.com
wrote:

hi @braebot https://github.com/braebot ,
Thank for your quick response.
But I 've just pulled the latest source last nigh.
At the beginning tested with the sample code here
https://github.com/card-io/card.io-Android-SDK (tested with Android
studio, have this line in gradle compile 'io.card:android-sdk:5.0.0') , but
it did not work then I pulled the libs from
https://github.com/card-io/card.io-Android-source then built the sample
app. But I got the same problem too.
Any suggestion, I think I made some mistaken :(
—
Reply to this email directly or view it on GitHub
https://github.com/card-io/card.io-Android-SDK/issues/55#issuecomment-95395703
.

hi @braebot ,
Here is the project as your request : https://github.com/roscrazy/TemporaryCard.ioSample
I only downloaded your sample project and trying to test it.
I tested the card with iOS and it can read. But for Android, there are no signal ...
Please help me take a look. If you can read the cards, please send me a sample APK which I can test on my credit card.
Sincerely.

hi @braebot ,
So sorry, I got the app working now. I tested with the other cards, and it work (but It take long time to recognize).
Maybe because my device's camera and the card( the card that I mention before)  does not work well together.
Thank you very much for your supporting.

am using card.io to scan credit and debit cards.scanning screen opens but not producing result even my device not vibrate

@maha1010 : are you scanning embossed card? AFAIK we can scan only embossed cards using card.io.

can any one guide me to scan all debit and credit cards please

I have the same problem , did anyone solve it ?

+1

hey! Did anyone solve this problem?

authors: Donik96 MinaMedhatKamel maha1010 muraliandroid neiljaywarner pravin-mindstix roscrazy


text:
🛑 mainnet - API is down

In 2c393ef, mainnet - API (https://api.beta.explorer.cardano.org/api/v1/epochs) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mainnet - API is back up in ca834d7 after 14 minutes.

repo: cardano-foundation/cf-explorer-status


text:
Running the realm-server fails with Fastboot TypeError

After pulling the latest GitHub source now the pnpm start:all inside /realm-server fails with the following  error:
"There was an error running your app in fastboot. More info about the error:
TypeError: (0 , cardstack_runtime_common_code_ref__WEBPACK_IMPORTED_MODULE_8_.isBaseDef) is not a function"

Did you start/build the host application first?

Did you start/build the host application first?
Yes

A clean installation works for me.

authors: backspace vimalaad

repo: cardstack/boxel


text:
Question about training dataset

Hi,
I was digging into your code recently. Nice work!
Just had question about your CULane training dataset. It seems that you didnt use txt which contains axis for lanes in the given dataset.
Could your give a little hint why this would work?
Thanks!

We just use the final lane annotations to train our models. Detailed instruction can just be found in SCNN.

@cardwing I am interested in saving lane coordinates of each lane instance separately in a JSON file so that finally I can use this official tusimple evaluation script: https://github.com/TuSimple/tusimple-benchmark/blob/master/evaluate/lane.py but the problem is I am doing semantic segmentation, not the instance. What to do?

authors: akshatbhutra cardwing jyang68qq

repo: cardwing/Codes-for-Lane-Detection


text:
LiDAR horizontal Field of View parameter missing

Many Autonomous Vehicles along with Velodyne (360 FOV) uses multiple Ibeo lidars (145 FOV) link  usually mounted in the bottom of the vehicle.
Current lidar sensor implementation in Carla doesn't have the parameter to set horizontal FOV. I believe it would be very helpful for many if the support for Ibeo like lidars (with FOV less then 360 degrees) is added.

Hey man have you figured it out. I met the same problem and want solutions......

authors: DatKartoffel anshulpaigwar

repo: carla-simulator/carla


text:
vehicle.set_light_state() only allows one type of light state to be set at a time [feature request]

First of all thanks for tackling this issue! It is exciting to have access to the vehicle lights with the release of 0.9.8!
Playing around with it, I noticed that I can't set multiple lights on at the same time, with the exception of All. For example, I cannot have the low beams on and also turn on a turn signal, it is strictly one or the other. Without the ability to pick and choose, it is unlikely we'll be able to use the vehicle lights in a meaningful way, as it is pretty rare that only one light is needed at a time throughout an entire scenario.
System:
Ubuntu 18.04
Python 3.5
Carla 0.9.8 (release version)
Unreal 4.22

You can set multiple lights at the same time like this:
vehicle.set_light_state(carla.VehicleLightState(carla.VehicleLightState.RightBlinker | carla.VehicleLightState.LowBeam))

Ideally, from Python 3.6 onwards, the enum would become a flag so you would be able to write:
vehicle.set_light_state(carla.VehicleLightState.RightBlinker | carla.VehicleLightState.LowBeam)

Thank you for that answer! This wasn't clear from the documentation.


text:
Images import

If I have image in adoc file, it results to  tag with original src. And of course there are no image at this source after bundle.

Hi @Djaler, can you provide a concrete example or point me to the repo where you are using it?
I am using an image here: https://raw.githubusercontent.com/carlosvin/carlosvin.github.io/site/static/posts/cpp-pragma-pack.en.adoc
And here is the result: https://carlosvin.github.io/posts/cpp-pragma-pack/en

That's because you're using absolute path to image, not relative. I'll provide an example soon

I understand. How would you suggest this plugin should behave when there is a relative image link?

Currently, in webpack I have this config:
config.module
        .rule('adoc')
        .test(/\.adoc$/)
        .use('html-loader')
        .loader('html-loader')
        .end()
        .use('adoc-loader')
        .loader(path.resolve('./webpack/adoc-loader.js'));

Where adoc-loader.js is:
const asciidoctor = require('asciidoctor')();

module.exports = function asciidoctorLoader(content) {
    this.cacheable();

    return asciidoctor.convert(content, {
        safe: 'unsafe',
        base_dir: this.context,
    });
};

As you can see, asciidoctorLoader just converts adoc-files to html, and then html-loader doing all the rest like rewriting images paths, etc

This plugin is not generating html, it is generating a javascript string that contains the converted html.
I've modified the previous example to use relative paths and it still works: https://carlosvin.github.io/posts/cpp-pragma-pack/en/
Can you point me to an example to help me understand what you are trying to achieve?

https://github.com/Djaler/vite-adoc-image-import-error check this, please

I see the problem, but I don't know how to solve it yet.
Here it is a sample of what rollup-plugin-asciidoc  is generating:
{
  meta: {
    title: "Post title",
    date: "2019-11-11"
  },
  html: "
Such a post!
"
}

This is pure Javascript code and it doesn't know anything about the content of the generated html, because it is an string. Rollup bundler doesn't know anything about the html var content for the same reason, so none of them can parse the html content to construct the correct paths and to move the images to the assets folder in the case of vite.
I could modify the plugin to generate html, but then I will lost the meta information variable.
Any idea how to solve this issue is very welcome!

Just as an idea about meta - it could be imported separetely, like import adocMeta from './post.adoc?meta

I didn't know about the question mark in the import, can you elaborate your idea a little bit more?

This is just a way to point your import to the same file, but provide additional params to webpack loader, rollup plugin, etc (https://vitejs.dev/guide/features.html#static-assets)

Also, more about how it works now in webpack with html-loader: https://webpack.js.org/loaders/html-loader/#sources

By default every loadable attributes (for example - ) is imported (const img = require('./image.png') or import img from "./image.png")

This is just a way to point your import to the same file, but provide an additional params to webpack loader, rollup plugin, etc.(for example https://vitejs.dev/guide/features.html#static-assets)
Sadly this won't solve the issue of loading assets from generated HTML.

I am trying to figure out how to parse handle assets from plugins, so once we have the HTML generated, we parse it again to extract the assets, but  I've found an open issue in Rollup to allow to handle assets from plugins: https://github.com/rollup/rollup/issues/2872
For now I can provide a couple of workarounds:
Workaround 1: If you add :data-uri: true in the test.adoc it will work by embedding the image in the generated html.
Workaround 2:
Manually save the images in an assets folder, they won't be copied by the plugin. Something similar to what I've shown at https://github.com/carlosvin/rollup-plugin-asciidoc/issues/4#issuecomment-782600239

I am working now on a plugin/function to process html like in html-loader

Feel free to create a PR o let me know how I can help.

If anyone interested in such feature, it is implemented in my plugin https://github.com/Djaler/vite-plugin-asciidoc

authors: Djaler carlosvin

repo: carlosvin/rollup-plugin-asciidoc


text:
Testing theme from a branch

The README now includes instructions on how to [test changes to the theme locally](how to test theme if we make changes on a branch) by replacing the theme on GH with a local path.
Is it possible to also use a branch other than main on GH?

You mean from the GitHub website? I can't say.

@AdamChlan Yes, that's what I was wondering about. When I use this theme in a project like here, it looks like it always uses the main branch.  Is it possible to test a build from another branch?

Removing "Ready for Review" label, noting my question above.

@AdamChlan @regisphilibert If either of you know this easily, please let me know. Otherwise we can close this issue.

I'm sure it's possible but do not know how.

authors: maneesha regisphilibert

repo: carpentries/carpentries-hugo-theme


text:
feat: add run casdoor through docker

Signed-off-by: killer 1533063601@qq.com

@hsluoyz If there is no problem in this part, I will do the docker installation of casnode.

@Kininaru @ErikQQY plz review.

@hsluoyz Is there still any problem? If there is no problem, I will write casnode's dockerfile

@hsluoyz Is have any question?

@hsluoyz already solved

@oranges-eating put the docs to: https://casdoor.org/

authors: hsluoyz oranges-eating

repo: casbin/casdoor


text:
added Groups in Permission struct

Hello,
I just started to use casdoor, it is a great work, thank you ! I was testing the different possibilities when I figured out that the "Groups" were missing from the Permission struct.
I just tested to add it, it works on my system, I added it to test, test is passing, I think it is ok.
Tell me whether if this PR is ok for you :)
Thank you !

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

authors: CLAassistant tsaquet

repo: casdoor/casdoor-go-sdk


text:
Consider an initial period on mainnet where nothing is guaranteed

I'm not sure about this, but something like an explicit 3-6 month period where, due to bugs in the protocol, we might have to change things in a way that nukes runes.

Call it the genesis period, and any runes that survive it has that attribute tied to it lol. Even more speculation during the transient period haha.

authors: casey summraznboi

repo: casey/runestone


text:
Integration on start.spring.io

Quoting metalhead-001 from reddit, who asked about this in the jte 3 comments.

I really wish the Spring project would adopt this as one of the supported Spring Boot templating engines that show up on start.spring.io like Thyemeaf, Freemarker, etc. do. Have you considered attempting to get jte brought into Spring like the others?

As far as getting it integrated into start.spring.io, I think you would just have to open a pull request into the Spring project and include your starter with it...basically follow the same pattern as the Thymeleaf and Freemarker, etc. integrations.

I bet if you got that going they would be willing to accept it as they have accepted the other templating engines. There is also a bit of documentation that would have to be provided. Look at the documentation on the Thymeleaf integration here. Search for Thymeleaf on this 'one page' documentation and you can see everywhere it's documented. Similar documentation would have to be provided for jte.

https://docs.spring.io/spring-boot/docs/3.1.0/reference/htmlsingle/
@atomfrede do you think we should give this a try?

Why not. It seems there is some kind of proposal process, so maybe we should start with creating such a proposal. But I could imagine it is easier as jte is "just" a template engine and not backed by a company like this proposal https://github.com/spring-io/start.spring.io/issues/1114

Oh yes, the proposal you linked looks frightening. I'm unsure if we are ready to commit to this.

Should we try to create a proposal here together? At jcon a lot of people knew and asked Thomas and me about jte vs thymeleaf for example. So I would say there is some interest

That would be awesome! What would be the best way to collaborate on a document like this? Best thing I could think of would be a branch with a markdown file in it?
Also, really cool to hear that people where asking about jte 😊

@casid
Yea I currently support 2 libraries in my library, and JTE is definitely the better option, for using with Spring ViewComponent. Thymeleaf has a lot of Spring Magic, that you don't really need with server-side components.
I just need to get going on my compile time checker because then it would be completly type safe and null safe, cause currently JTE throws an error at runtime if a property that is declared as an parameter is not available in the model.
btw did you see my Spring I/O Talk? I also talked a bit about JTE there: https://youtu.be/DPAtQU-erM4?t=749

@tschuehly great talk, thanks for sharing the video!
As for type-safety of params, maybe the new jte-models extension could be helpful?

@casid, if it’s okay with you, I would like to add support for JTE templates in Generator Genie. I’ve already started the process but ran into this issue, which I posted on StackOverflow. Once this issue is resolved, I plan to add support for JTE templates.

Welcome @nicholasnet
Sure thing, go for it, that's very much appreciated!
Can you post a stacktrace of the error you run into in production?

Sure here is the repo link I think that will be easier. As you see this is plain vanilla Spring Boot MVC app.
https://github.com/nicholasnet/jte-spring-gradle
Here if you do just ./gradlew bootRun
Then go to http://localhost:8080 it works.
However, if you do
./gradlew bootBuildImage
Then run the image docker run -it --rm -p '8080:8080' -e 'SPRING_PROFILES_ACTIVE=prod' jte:0.0.1-SNAPSHOT
Then go to http://localhost:8080 it does not work.

I've just submitted an issue for integrating it into start.spring.io: https://github.com/spring-io/start.spring.io/issues/1560

Hey @casid, Moritz waits for feedback from you. Would be awesome if you could approve the integration!

authors: atomfrede casid nicholasnet tschuehly

repo: casid/jte


text:
Outdated cask: praat

Outdated cask: praat.
Info:

version: 6.0.12.
appcast url: https://github.com/praat/praat/releases.atom.

Full appcast:
<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" xml:lang="en-US">
  <id>tag:github.com,2008:https://github.com/praat/praat/releases</id>
  <link type="text/html" rel="alternate" href="https://github.com/praat/praat/releases"/>
  <link type="application/atom+xml" rel="self" href="https://github.com/praat/praat/releases.atom"/>
  <title>Release notes from praat</title>
  <updated>2016-01-31T21:20:40Z</updated>
  <entry>
<id>tag:github.com,2008:Repository/18684635/v6.0.13</id>
<updated>2016-01-31T22:02:42Z</updated>
<link rel="alternate" type="text/html" href="/praat/praat/releases/tag/v6.0.13"/>
<title>version 6.0.13, January 31, 2016</title>
<content type="html">

Windows: corrected a bug that could cause Praat to crash when closing a script window.

Mac 64-bit: progress bars with movies.

</content>
<author>
  <name>PaulBoersma</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/3752591?v=3&s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/18684635/v6.0.12</id>
<updated>2016-01-24T13:50:10Z</updated>
<link rel="alternate" type="text/html" href="/praat/praat/releases/tag/v6.0.12"/>
<title>version 6.0.12, January 24, 2016</title>
<content type="html">

Windows 32-bit: corrected a bug that could cause Praat to crash when closing the Sound window after popping up dialog boxes.

Mac 64-bit: better demoShow().

Mac 64-bit: working Matrix movies and articulatory synthesizer movies.

</content>
<author>
  <name>PaulBoersma</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/3752591?v=3&s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/18684635/v6.0.11</id>
<updated>2016-01-18T16:06:46Z</updated>
<link rel="alternate" type="text/html" href="/praat/praat/releases/tag/v6.0.11"/>
<title>version 6.0.11, January 18, 2016</title>
<content type="html">

Corrected a bug that could cause Praat to crash when drawing a Spectrum with undefined values.

Mac 64-bit: corrected a bug by which some text in the Sound window would sometimes not be drawn.

Mac 64-bit demo window: improved the working of demoShow().

</content>
<author>
  <name>PaulBoersma</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/3752591?v=3&s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/18684635/v6.0.10</id>
<updated>2016-01-10T18:34:10Z</updated>
<link rel="alternate" type="text/html" href="/praat/praat/releases/tag/v6.0.10"/>
<title>version 6.0.10, January 8, 2016</title>
<content type="html">

Corrected a bug that would cause Praat to crash when starting an ExperimentMFC window.

Mac 64-bit: corrected a bug that would cause black selections in the Sound window.

</content>
<author>
  <name>PaulBoersma</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/3752591?v=3&s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/18684635/v6.0.09</id>
<updated>2016-01-01T18:51:32Z</updated>
<link rel="alternate" type="text/html" href="/praat/praat/releases/tag/v6.0.09"/>
<title>version 6.0.09, January 1, 2016</title>
<content type="html">

Windows 64-bit: corrected a bug that could cause Praat to crash when closing the Sound window after popping up dialog boxes.

</content>
<author>
  <name>PaulBoersma</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/3752591?v=3&s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/18684635/v6.0.08</id>
<updated>2015-12-07T22:00:36Z</updated>
<link rel="alternate" type="text/html" href="/praat/praat/releases/tag/v6.0.08"/>
<title>version 6.0.08, December 5, 2015</title>
<content type="html">

Windows command line: the --a option can be used when redirecting the output to pipes and files.

Linux command line: the --run option is not needed in the Terminal when directing output (unless you redirect standard output, standard input and standard error).

</content>
<author>
  <name>PaulBoersma</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/3752591?v=3&s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/18684635/v6.0.07</id>
<updated>2015-11-30T22:28:38Z</updated>
<link rel="alternate" type="text/html" href="/praat/praat/releases/tag/v6.0.07"/>
<title>version 6.0.07, November 30, 2015</title>
<content type="html">

Mac 64-bit: repaired dragging selections (which got broken in the El Capitan fix in 6.0.06).

</content>
<author>
  <name>PaulBoersma</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/3752591?v=3&s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/18684635/v6.0.06</id>
<updated>2015-11-29T21:37:29Z</updated>
<link rel="alternate" type="text/html" href="/praat/praat/releases/tag/v6.0.06"/>
<title>version 6.0.06, November 29, 2015</title>
<content type="html">

Mac: correct early Info window updates and demoShow() in El Capitan.

Manual updates.

Corrected some small memory leaks.

</content>
<author>
  <name>PaulBoersma</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/3752591?v=3&s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/18684635/v6.0.05</id>
<updated>2015-11-08T17:54:34Z</updated>
<link rel="alternate" type="text/html" href="/praat/praat/releases/tag/v6.0.05"/>
<title>version 6.0.05, November 8, 2015</title>
<content type="html">

A manual page that describes TextGrid file formats.

Corrected a bug that prevented some KlattGrid tiers from being edited.

32-bit Linux: correct use of PulseAudio (note: 6.0.04 on Debian already had this correct).

</content>
<author>
  <name>PaulBoersma</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/3752591?v=3&s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/18684635/v6.0.04</id>
<updated>2015-11-01T15:23:10Z</updated>
<link rel="alternate" type="text/html" href="/praat/praat/releases/tag/v6.0.04"/>
<title>version 6.0.04, November 1, 2015</title>
<content type="html">

Corrected a bug that caused an incorrect number in FFNet files; unreadable FFNet files can be sent to the Praat authors for repair.

</content>
<author>
  <name>PaulBoersma</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/3752591?v=3&s=60"/>
  </entry>
</feed>

Closing in favour of #18208.

repo: caskroom/homebrew-cask


text:
Move semulov back to using :latest

Updated version, dev appears to no longer be offering versioned dl links
See #6084

Thank you for the contribution. It was merged directly as f1cb2670d18c4f781c81163cf361c0f5d882e582 to keep commit history cleaner. Your contribution is still credited to you.

authors: Amorymeltzer vitorgalvao


text:
appcast: remove latest_version

I don’t even know/remember what the experiment was about, and how this could possibly be useful.

Added in #4847 (not really helpful)

Also https://github.com/caskroom/homebrew-cask/pull/6680.
No clue about its purpose.

I guess we could jut kill it - there's no documentation anywhere about it that I can see, either.

authors: adityadalal924 tsparber vitorgalvao


text:
Add Minikube v0.6.0

Hopefully I'm not doing any thunder-stealing with Homebrew/homebrew-binary#343 sitting out there.
Thanks to @tback for that one and to @ltiao for Homebrew/homebrew-core#2417.

Thanks!

great, thanks!

Thanks for doing this! We were going to get to it eventually in https://github.com/kubernetes/minikube/issues/450, but this looks great! We'll add this to our documentation and try to help keep it up to date.

authors: dlorenc jasisk jawshooah tback


text:
Add Karbowanec.app 1.1.9

After making all changes to the cask:

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

Additionally, if adding a new cask:

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

Refusing this as it is too obscure. Thanks for the PR nonetheless.

Rejected Casks
The Cask is too obscure (for example, a self-submitted app from a GitHub repository that is not notable enough (< 10 stars)).

I'd suggest creating your own tap.

authors: atton commitay


text:
Update quik to 2.5.2.562

After making all changes to the cask:

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

GoPro's certificate seems to be expired.
This is the reason why this ci fails.
(ref: https://community.gopro.com/t5/GoPro-Apps-for-Desktop/Installation-Developer-certificate-expired/td-p/146532)
I close this PR and will re-submit later after this issue will be fixed.
Thanks.


text:
Update font-liberationmono-nerd-font to 1.1.0

After making all changes to the cask:

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

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation (How?): {{link}}

Merged as 70e6d80588418b3944eba7dbbd6e2c011a90787c.

repo: caskroom/homebrew-fonts


text:
🛑 Baked Bean is down

In 1c52ca0, Baked Bean (https://baked-bean.co.uk) was down:

HTTP code: 403
Response time: 243 ms

Resolved: Baked Bean is back up in 09be483.


text:
Added documentation for legacy translation. Fixed removed tests. Adde…

…d more unit tests for the 2.x to 1.x translation process

left some minor comments... other than that lgtm

authors: jacek-casper zajko

repo: casper-network/casper-sidecar


text:
Discussion point: SourceDocument design

Follow up to #1047
We need to rethink the indexing pipeline re: "contents" and "raw", because there's a lot of confusion, mostly because the design has evolved over time...
In the Lucene document, we've agreed (and this is clear) that "contents" field should be the content as indexed for searching, and "raw" should be the raw source document.
What about SourceDocument then? Currently, it only has content() method, and it's underspecified as to what it should provide. The Generator is responsible for calling content() and pulling out the necessary parts to populate the Lucene "contents" field and "raw" field.
Does this design make sense? The alternative is that SourceDocument has contents() and raw() methods, i.e., it "knows" its own contents and raw form.
One argument against this is when we have one-to-many SourceDocument to Lucene Document mappings - like in COVID19 (see #1044), where we take a single SourceDocument, which may be full text, and index it at the paragraph level (i.e., multiple Lucene Documents)
@nikhilro @edwinzhng thoughts?
If we stick to the original design, then it's a matter of clarifying in documentation. If we adopted the alternative design, it's going to be a painful refactoring job...

I'm about to create a PR which could serve as an example

One argument against this is when we have one-to-many SourceDocument to Lucene Document mappings - like in COVID19 (see #1044), where we take a single SourceDocument, which may be full text, and index it at the paragraph level (i.e., multiple Lucene Documents)

This doesn't hold because the way I implemented there is one-to-one mapping

I like the separate fields too for contents and raw, allowing the SourceDocument to build it's own separation makes things more organized imo

Meat of the resolution in this comment in PR #1049: https://github.com/castorini/anserini/pull/1049#issuecomment-602228384

Okay, this will be a fairly painful refactoring to get everything in this format, so we'll punt it for later.

Actually, if we take this design to the logical conclusion, should the generator also be folded into the collection?
That is, each SourceDocument knows how to generate its own corresponding Lucene document? Or, do we like the separation between Lucene and non-Lucene code?

I don't even see the need for any refactoring because there is an implicit assumption that content == raw unless SourceDocument for that Collection specifies raw, no?

That is, each SourceDocument knows how to generate its own corresponding Lucene document? Or, do we like the separation between Lucene and non-Lucene code?
I like the separation between Lucene and non-Lucene code. It's nice and clean

I don't even see the need for any refactoring because there is an implicit assumption that content == raw unless SourceDocument for that Collection specifies raw, no?

I see, I suppose we can change SourceDocument to abstract, and make one dispatch to the other, overridable by subclasses if need be?

I see, I suppose we can change SourceDocument to abstract, and make one dispatch to the other, overridable by subclasses if need be?

I don't know Java but that sounds reasonable. cc @edwinzhng

authors: edwinzhng lintool nikhilro

repo: castorini/anserini


text:
Reproduction/Lingwei revised PR

This is the same PR from Lingwei.
I didn't fork the repo but downloaded the zip instead, so I just forced the push of the master commit where the reproduction was done (the same for pyserini reproduction...).
Sorry for starting a new PR; I spent some time to fix git issues.

Codecov Report

Merging #1707 (0e7266d) into master (30605f5) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 0e7266d differs from pull request most recent head 02ab95b. Consider uploading reports for the commit 02ab95b to get more accurate results

@@            Coverage Diff            @@
##             master    #1707   +/-   ##
=========================================
  Coverage     57.58%   57.58%
  Complexity     1032     1032
=========================================
  Files           173      173
  Lines          9781     9781
  Branches       1344     1344
=========================================
  Hits           5632     5632
  Misses         3675     3675
  Partials        474      474

Continue to review full report at Codecov.

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

Ref: #1705 - see trace for successful repo.

authors: codecov-commenter lingwei-gu lintool


text:
Docstrings for public class methods

ref: #36

thank you @AndreSlavescu very thorough documentation. I just pushed a commit after formatting with black

authors: AndreSlavescu sahel-sh


text:
"template" action of jbj does not work in documentFields for a previously created field

  "documentFields": {
    "$pmid": {
      "visible": true,
      "label": "PMID",
      "path": "content.json.AN.#text"
    },
    "$free": {
      "label": "Free",
      "noindex": true,
      "select": ".content > .json > .FREE .#text",
      "foreach": {
        "template": "Free version"
      },
      "first": true
    },

In mongo:
> db.bibliotep.findOne({"wid":"ZRajql"}).pmid
22576209
> db.bibliotep.findOne({"wid":"ZRajql"}).free
Free version

pmid is not put in free.

This behavior is due to how context is passed to foreach: its scope is limited to each element it iterates, so inside the foreach stylesheet, no pmid exists, only the content of one element of the array returned by select.
In this case, the use of foreach is a little cheat to create a value only if there is a free property in the document. Another way of doing this may be to use a (not yet existing) breakif action, which would break the flow if free was empty.

JBJ version 3.2.0 adds breakif but also assert commands.
assert seems to be more natural to use.
Version 3.2.0 is added in ad3128c6c0c10e8544fff6e066004369f4b22f49

repo: castorjs/castor-core


text:
File and Directory annotations not showing up on schema

Description
Problem 1:
PR #237 is supposed to auto infer File or Directory type of paths within source_data_schema from init, but it doesn't seem to be working.
Problem 2
This is the weirdest: after re-running the same Notebook cell, the following error track shows, apparently the type string is being changed somehow.
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-3-6d29f0927059> in <module>
----> 1 OpenEphysRecordingExtractorInterface.get_source_schema()

/media/luiz/storage/Github/nwb-conversion-tools/nwb_conversion_tools/datainterfaces/ecephys/openephys/openephysdatainterface.py in get_source_schema(cls)
     18         """Compile input schema for the RecordingExtractor."""
     19         source_schema = get_schema_from_method_signature(
---> 20             class_method=cls.__init__, exclude=["recording_id", "experiment_id", "stub_test"]
     21         )
     22         source_schema["properties"]["folder_path"]["description"] = "Path to directory containing OpenEphys files."

/media/luiz/storage/Github/nwb-conversion-tools/nwb_conversion_tools/utils/json_schema.py in get_schema_from_method_signature(class_method, exclude)
    124                     else:
    125                         raise ValueError(
--> 126                             f"No valid arguments were found in the json type mapping {arg} for parameter {param}"
    127                         )
    128                     if arg == FilePathType:

ValueError: No valid arguments were found in the json type mapping ~FolderPathType for parameter folder_path: ~FolderPathType

Steps to Reproduce
from nwb_conversion_tools import OpenEphysRecordingExtractorInterface
OpenEphysRecordingExtractorInterface.get_source_schema()

Environment
Python Executable: Conda or Python
Python Version: Python 3.7.10
Operating System: Linux
PyNWB Version: master branch

Checklist

[x] Have you ensured the feature or change was not already reported?
[x] Have you included a brief and descriptive title?
[x] Have you included a clear description of the problem you are trying to solve?
[x] Have you included a minimal code snippet that reproduces the issue you are encountering?
[x] Have you checked our Contributing document?

Update
The weird Problem 2 happens with the autoreload in Jupyter, whenever I modify anything in the code (e.g. add a print) and re-run the cell.  @CodyCBakerPhD do you have any idea what in our TypeVar usage might be causing this?

For Problem #2 can you insert a print statement into line 103 of the json_schema code and post what it looks like before and after your reload?

@CodyCBakerPhD , I'm printing arg here:

Here's a summary of what happens:

Here is it, doesn't seem to be the problem you expected:

The only problem reported online involving TypeVar and autoreload I could find hints to it being a Python version problem.
It doesn't seem to be the case here, I reproduced the error using python 3.7.10 and 3.8.11

authors: CodyCBakerPhD luiztauffer

repo: catalystneuro/nwb-conversion-tools


text:
Improve dandiset description

Their other recent publication of the visual behavior dataset is a good example of what the final product should look like: https://dandiarchive.org/dandiset/000711/0.231121.1730
But will include (a) better AllenSDK documentationc (b) working links to white papers (those supposed to be att  have been down for a while...), (c) preferably DOI's for those papers, or for others related to this project

Saskia said they would take this one; just need to remind them in follow-up email

No response


text:
EntityDescriptor Inspection

It is possible to inspect what EntityDescriptor assigned with Table,
so it should be possible to inspect below

Direct Group-Component pair to Index list
Faster and alloc-free FindGroups implementation

applied in 0.6


text:
🛑 Mas Valores is down

In 2449722, Mas Valores (https://www.masvalores.com.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mas Valores is back up in a791f32.

repo: cavalicenti/upptime


text:
Limit Iterator

The necessary component to make mid-query limit work. Acts as a limit on Next(), a passthrough on Contains(), and a limit on NextPath()

Done in #369

Merged

authors: dennwc robertmeta

repo: cayleygraph/cayley


text:
My First PR commit

PR comments

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

Needs approval from an approver in each of these files:

OWNERS

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

@cjxd-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr-build
376af8e0d18fd13849b2a96a32969f52594827b9
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


text:
chore: bdd-sbhg-1587545302 to 0.0.1

chore: Promote bdd-sbhg-1587545302 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


text:
Fix "similar-code" issue in azure-servicebus-sink-connector/src/main/java/io/cbdq/ConnectionStringParser.java

Similar blocks of code found in 2 locations. Consider refactoring.
https://codeclimate.com/github/cbdq-io/kc-connectors/azure-servicebus-sink-connector/src/main/java/io/cbdq/ConnectionStringParser.java#issue_6739b401f432bd000100002b

Fixed in #41.

repo: cbdq-io/kc-connectors


text:
Inherited test methods do not get expected group behavior

Consider the following test classes:
@Test
public abstract class ParentTest {
	public void parentTestMethod() {
	}
}

@Test(groups = "myGroup")
public class ChildTest extends ParentTest {
	public void childTestMethod() {
	}
}

When running this test (ChildTest), I would expect that both test methods (childTestMethod and parentTestMethod) belong to group 'myGroup'. Apparently this is not the actual behavior (tested with version 6.4).
I put together some code to investigate this issue:
TestNGMethodFinder testNGMethodFinder = new TestNGMethodFinder(new RunInfo(), new JDK15AnnotationFinder(new DefaultAnnotationTransformer()));
ITestNGMethod[] testMethods = testNGMethodFinder.getTestMethods(ChildTest.class, new XmlTest());
for (ITestNGMethod testMethod : testMethods) {
	String[] groups = testMethod.getGroups();
	System.out.println(testMethod + " groups:" + Arrays.toString(groups));
}

Output from running this code:
ChildTest.childTestMethod()[pri:0, instance:null] groups:[myGroup]
ParentTest.parentTestMethod()[pri:0, instance:null] groups:[]

I looked into the TestNG source code, and it appears that this behavior originates from the method org.testng.internal.BaseTestMethod#initGroups(Class<?>). To be exact, I think the following statement is the cause of this rather odd behavior:
ITestOrConfiguration classAnnotation = (ITestOrConfiguration) getAnnotationFinder().findAnnotation(getMethod().getDeclaringClass(), annotationClass);

In order to fix this issue, this statement could be modified to:
ITestOrConfiguration classAnnotation = (ITestOrConfiguration) getAnnotationFinder().findAnnotation(getInstance().getClass(), annotationClass);

but I am not sure if this would be the correct way to resolve the issue. Nor eventual implications....

I see the problem, and your suggestion doesn't quite work, unfortunately. It's a bit tricky to solve because annotations are resolved in the init phase, which means that when the parent's @Test annotation is parsed, it obviously knows nothing about the fact that the child annotation will add more groups to it...

Cedric, thank you for your prompt feedback on this issue. You say "it is a bit tricky to solve", does that mean that you do not think that this issue will have a chance of being resolved in the near future? Can you think about any possible workarounds?

What I meant was: when the group resolution is performed, no test class has been instantiated yet, so when I look at parentTestMethod(), I don't have an instance of ChildTest that would allow me to put that method in this group.
Group resolution is purely static, while the example above can only be resolved dynamically.
Does this make sense?

I created a custom method selector, that uses the groups from subclass Test annoation
/* *****************************************************************************

Copyright 2017 VMware, Inc.  All rights reserved. VMware Confidential
****************************************************************************/
package com.vmware.cloud.systemtests.util;

import java.util.Arrays;
import java.util.List;
import org.apache.commons.lang3.ArrayUtils;
import org.testng.IMethodSelector;
import org.testng.IMethodSelectorContext;
import org.testng.ITestNGMethod;
import org.testng.annotations.Test;
import org.testng.xml.XmlTest;
/**

Selector that uses groups in subclass @Test annotations to determine if methods should be included
*/
public class SubclassAwareXmlMethodsSelector implements IMethodSelector {
@Override
public boolean includeMethod(IMethodSelectorContext context, ITestNGMethod method, boolean isTestMethod) {
XmlTest xmlTest = method.getXmlTest();
if (xmlTest == null) {
return method.isAlwaysRun();
}
Class realTestClass = isTestMethod ? method.getTestClass().getRealClass() : method.getRealClass();
Test testClassAnnotation = (Test) realTestClass.getAnnotation(Test.class);
String[] classAnnotationGroups = testClassAnnotation != null ? testClassAnnotation.groups() : new String[0];
List groups = Arrays.asList(ArrayUtils.addAll(classAnnotationGroups, method.getGroups()));
 context.setStopped(true);
 if (groups.size() == 0 && xmlTest.getIncludedGroups().isEmpty()) {
     return true;
 } else if (groups.size() > 0 && xmlTest.getExcludedGroups().stream().anyMatch(groups::contains)) {
     return false;
 } else if (groups.size() > 0 && xmlTest.getIncludedGroups().stream().anyMatch(groups::contains)) {
     return true;
 } else {
     return method.isAlwaysRun();
 }

}
@Override
public void setTestMethods(List list) {
}
}

authors: cbeust damienbiggs erikgb

repo: cbeust/testng


text:
reader_dispatch doesn't yield any reader

Maybe it's just me, but when I run python benchmark_detectors.py runtime in examples/benchmark, I do not get any records, i.e. the line records = list(reader_dispatch(db_slug, data_dir)) yields an empty list. Is this caused by our recent changes in v0.4.0?

Exactly, thanks for noticing! Fixed in #68

authors: cbrnr hofaflo

repo: cbrnr/sleepecg


text:
Compact only within certain number of messages

Love the mod but there's various situations where it's not so helpful. For example if you say a few "yes" and "no" in a conversation, compacting them makes the chat log lose context.
It would be useful to be able to compact only messages that are repeated within a certain distance. For example a distance of 1 would compact only consecutive messages, which would prevent spam but not affect any proper conversations.
Alternative solutions:

Compact only within certain time
Compact only system messages (not from a user)

Good idea, I'll add an "expiry" timer.
You'll be able to select between world rejoin and a specified number of minutes.

Thank you for the feature request, @jn64!
Only compacting consecutive chat messages is now available in v1.3 of CompactChat, which you can download from Modrinth or from the releases page.

repo: cbyrneee/CompactChat


text:
Support for Euro notation

Hey! Is there a way to use the correct notation for Euro?
In Euro countries (at least for the most part of them) amounts should have commas to divide decimals from the integer part of the number and points to separate thousands (ex. € 100.000.000,00 instead of £ 100,000,000.00).
Thanks

Hi, I did not realise that was the case for Euro! But I think it should be quite simple to implement two new props for decimal separator and thousand separators. Give me a few days, and I'll see if I get the time to do it :)

That'd be great If I could choose what character to put instead of default thousand and decimal separators.

Hi @soulpaul and @umucorn, thanks for the suggestion.
I've given it a go and implemented it, but there was a bit more changes in the code than I expected, so I've published it in a beta branch for testing.
If you would like to try it out: https://www.npmjs.com/package/react-currency-input-field/v/2.2.0-beta.1#separators
npm i react-currency-input-field@2.2.0-beta.1

yarn add react-currency-input-field@2.2.0-beta.1

Feel free to raise any issues you find :)

Hi there!  FWIW, you might want to allow for passing in a locale, and outputting via Number.prototype.toLocaleString()
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/toLocaleString
Currency type is not the correct method for determining the separators, locale should be.  If I'm working in Euro, I'm still working in en-US locale, so it should read €123,456.99 .. and if someone in en-UK is working in USD, it should read $123.456,99
Of course, allowing for custom separators is also still ok, other people might have different uses. :-)

Thanks for the suggestion, @ericblade, it sounds like it should be pretty useful for dealing with different currencies. It's something I'll add to the list of potential improvements and todos.
For now I'm going to close this issue as I have made an attempt to implement the feature on the beta branch, if there are any other observations feel free to re-open this thread or raise a new issue :)

authors: cchanxzy ericblade soulpaul umucorn

repo: cchanxzy/react-currency-input-field


text:
iOS Typos

Fixed some bad references to RCTTwilioIPMessaging for iOS. See #20.

Released in 0.3.1.

repo: ccm-innovation/react-native-twilio-chat


text:
🛑 OpenEvo is down

In 0535b5d, OpenEvo (https://openevo.eva.mpg.de/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OpenEvo is back up in 82796e6 after 4 minutes.

repo: ccp-eva/uptime-monitor


text:
Add Observation mapping

This fixes #9
What changes:

Add translate.js to handle

Map old LOINC codes to new LOINC code
Map Observation.valueString to Observation.valueCodeableConcept

@yunwwang This may need to be rebased / merged with updated pilot branch now that PR: https://github.com/ccsm-cds-tools/ccsm-cds-dashboard/pull/10 is merged.

There is a test patient on Logical: Name: Testmit, Twseven, ID: 14602

repo: ccsm-cds-tools/ccsm-cds-dashboard


text:
Issue with ELF / POLY listing

It didn't purchase and crashed with this log:
[ERROR] 2021-09-08 10:00:04,145: Traceback (most recent call last):
  File "C:\py\trading-bot-new-coins-oop\bot\bot.py", line 71, in run_async
    self.process_new_ticker(new_ticker)
  File "C:\py\trading-bot-new-coins-oop\bot\bot.py", line 228, in process_new_ticker
    price = self.broker.get_current_price(new_ticker)
  File "C:\py\trading-bot-new-coins-oop\broker\broker.py", line 166, in get_current_price
    return float(self.futures_mark_price(symbol=ticker.ticker)["markPrice"])
  File "C:\Users\Bawa\AppData\Roaming\Python\Python39\site-packages\binance\client.py", line 5203, in futures_mark_price
    return self._request_futures_api('get', 'premiumIndex', data=params)
  File "C:\Users\Bawa\AppData\Roaming\Python\Python39\site-packages\binance\client.py", line 339, in _request_futures_api
    return self._request(method, uri, signed, True, **kwargs)
  File "C:\Users\Bawa\AppData\Roaming\Python\Python39\site-packages\binance\client.py", line 315, in _request
    return self._handle_response(self.response)
  File "C:\Users\Bawa\AppData\Roaming\Python\Python39\site-packages\binance\client.py", line 324, in _handle_response
    raise BinanceAPIException(response, response.status_code, response.text)
binance.exceptions.BinanceAPIException: APIError(code=-1121): Invalid symbol.

It didn't purchase and crashed with this log:
[ERROR] 2021-09-08 10:00:04,145: Traceback (most recent call last):
  File "C:\py\trading-bot-new-coins-oop\bot\bot.py", line 71, in run_async
    self.process_new_ticker(new_ticker)
  File "C:\py\trading-bot-new-coins-oop\bot\bot.py", line 228, in process_new_ticker
    price = self.broker.get_current_price(new_ticker)
  File "C:\py\trading-bot-new-coins-oop\broker\broker.py", line 166, in get_current_price
    return float(self.futures_mark_price(symbol=ticker.ticker)["markPrice"])
  File "C:\Users\Bawa\AppData\Roaming\Python\Python39\site-packages\binance\client.py", line 5203, in futures_mark_price
    return self._request_futures_api('get', 'premiumIndex', data=params)
  File "C:\Users\Bawa\AppData\Roaming\Python\Python39\site-packages\binance\client.py", line 339, in _request_futures_api
    return self._request(method, uri, signed, True, **kwargs)
  File "C:\Users\Bawa\AppData\Roaming\Python\Python39\site-packages\binance\client.py", line 315, in _request
    return self._handle_response(self.response)
  File "C:\Users\Bawa\AppData\Roaming\Python\Python39\site-packages\binance\client.py", line 324, in _handle_response
    raise BinanceAPIException(response, response.status_code, response.text)
binance.exceptions.BinanceAPIException: APIError(code=-1121): Invalid symbol.

I am also getting the same error.

Sorry for the delay on this.  I unfortunately don't have enough information to replicate the issue (I missed this sale myself) - I'm assuming there's a problem with the ticker format passed to the Binance API.  If anyone has a record of the value of the ticker processed and sent to the API  that would help.
To avoid this issue in the future, I've added a verbose logging file that saves much more information about each attempted transaction.  Please pull this new version and include the relevant information for this new log file for any other issues.  I've also added 'retries' for connection refusals which periodically occur.

Thanks, I think you are right as original repository has very simillar issue reported as well. There is json format mismatch for real trades. I will pull latest changes and keep it running and I will get back to you in case of any findings.

I just reread my code again but still haven't found anything standing out as problematic.  This script is executing quickly, I suppose it's possible the program is requesting a price from Binance before their API is even ready for it... I just added retry's to get_current_price and place_order - if either of these methods fails, they will retry 2 times each with a 3-second delay between each failure.  This should hopefully add enough time to still make the purchase without too much of a delay (if that's indeed the issue).

It looks like there was a new coin on Sept 22, did either of you happen to catch it in your logs @bwasik @easyguyme?  I'm testing a new version with notifications (dev branch) and mistakenly missed it 😔.  The verbose log should have enough information for me to fix whatever this issue is.

I have no logs logged for sept 22 only 19th

I missed two coins today, both with the "binance.exceptions.BinanceAPIException: APIError(code=-1121): Invalid symbol."
Verbose logs were:
[DEBUG] 2021-09-24 06:00:00,384: PROCESSING NEW TICKER:
{"ticker": "YGGUSDT", "base_ticker": "YGG", "quote_ticker": "USDT"}.
[DEBUG] 2021-09-24 06:00:00,384: [BINANCE]      Preparing to buy YGGUSDT.
[DEBUG] 2021-09-24 10:00:00,405: PROCESSING NEW TICKER:
{"ticker": "SYSUSDT", "base_ticker": "SYS", "quote_ticker": "USDT"}.
[DEBUG] 2021-09-24 10:00:00,405: [BINANCE]      Preparing to buy SYSUSDT.

Actual error:
[ERROR] 2021-09-24 10:00:03,912: Traceback (most recent call last):
  File "/root/trading-bot-new-coins/bot/bot.py", line 72, in run_async
    self.process_new_ticker(new_ticker)
  File "/root/trading-bot-new-coins/bot/bot.py", line 240, in process_new_ticker
    price = self.broker.get_current_price(new_ticker)
  File "/usr/local/lib/python3.6/dist-packages/decorator.py", line 232, in fun
    return caller(func, *(extras + args), **kw)
  File "/root/trading-bot-new-coins/util/decorators.py", line 113, in retry_decorator
    logger,
  File "/root/trading-bot-new-coins/util/decorators.py", line 41, in __retry_internal
    return f()
  File "/root/trading-bot-new-coins/broker/broker.py", line 229, in get_current_price
    return float(self.futures_mark_price(symbol=ticker.ticker)["markPrice"])
  File "/usr/local/lib/python3.6/dist-packages/binance/client.py", line 5203, in futures_mark_price
    return self._request_futures_api('get', 'premiumIndex', data=params)
  File "/usr/local/lib/python3.6/dist-packages/binance/client.py", line 339, in _request_futures_api
    return self._request(method, uri, signed, True, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/binance/client.py", line 315, in _request
    return self._handle_response(self.response)
  File "/usr/local/lib/python3.6/dist-packages/binance/client.py", line 324, in _handle_response
    raise BinanceAPIException(response, response.status_code, response.text)
binance.exceptions.BinanceAPIException: APIError(code=-1121): Invalid symbol.

Fixed! Thank you @jarrodjay for posting.
FYI, this new update also now has notifications - details are in the readme.  Right now I have Discord and Telegram set up, but if anyone wants another service open an issue/discussion.

Thank YOU for this fork. It's inspired me to start playing around with Python too.

authors: bwasik cdalton713 easyguyme jarrodjay


text:
add TypedDict equivalent support

It would be great if I could use TypedDict (PEP 589) equivalent for my type definition of Box.
I'm very new to python, so perhaps there is already a way to do this... I searched the Box docs, several pages of issues here, and asked in #python (they recommended I just make my own dataclasses/attrs)
but this is example TypedDict code:
from typing import TypedDict

class Movie(TypedDict):
    name: str
    year: int

def my_func(movie : Movie):
   """do some stuff"""

how to convert this so def my_func(movie: Box) works while also preserving the TypedDict Movie check?
one workaround might be:
def my_func(movie: Movie):
  movie_box = Box(movie)
  """do some stuff"""

would this be too slow to always convert it? assume the calling function already has a box so would be converting to dict from a box, only to have it convert back to a box...
if I wanted to return a TypedDict I'd also have to convert my Box to a dict on return, only to have it reconverted back to a box.
These are just internal methods to my project, so I'm not worried about making the API require a Box, I thought it would save me having to convert them constantly, as I use Box everywhere.
As #python channel mentioned another alternative is to use dataclasses/attrs, but that seems to reinvent the wheel somewhat and brings me away from the convenience of Box and TypedDict's.
If there is already a way to do this, I humbly suggest a page on how to type Box's in the wiki docs be added. I hear basic typing of Box[str, Any] should work... but it is also not specifically documented.
Thanks for the great project!

If you want your checking, use msgspec or pydantic or dataclass.

authors: ofbeaton twardoch

repo: cdgriffith/Box


text:
chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

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

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

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-27-main" workflow

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

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-k8s-25-main" workflow

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

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-26-main" workflow

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

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-27-main" workflow

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

Questions ?
Please refer to the Backport tool documentation


text:
feat: add flag to control upgrade check

Hi,
This PR intends to define a new flag on the cdk8s-cli (i.e. --check-upgrade) to control available upgrade check trigger while running the command.
Regards
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Thanks for this! My only question is how this translates into an environmental variable. I eventually got it working while not changing the command line option, like this:
.option("check-upgrade", {type: "boolean", default: true, desc: "Check for cdk8s-cli upgrade (default true)"})
Now I can set CDK8S_CHECK_UPGRADE=false as the default value in eg. a container.

@vbatoufflet  apologies for the inconvenience! We have moved this module to https://github.com/cdk8s-team/cdk8s-cli. Could you please re-submit this pull request against the new repository?

Could you please re-submit this pull request against the new repository?

@eladb sure no worries, I'll re-submit on the new repository 👍

Thanks, and apologies again for the burden.

authors: eladb rossi-fi vbatoufflet


text:
chore: update github actions dependencies

This solves "Node.js 16 actions are deprecated" warnings when running the deploy pipeline.

Tested on multistack, multistage, multiaccount pipeline. No regressions found.

repo: cdklabs/cdk-pipelines-github


text:
Search is broken

The buttons to choose the CDK type on top of the search bar don't react at all for me. Nothing happens when I click on them.
The buttons I'm referring to:

The search itself doesn't work either - when I type my query and hit Enter, the page just refreshes, but now with a /? at the end of the URL.
I'm using Firefox on Linux.

It looks like this is an outdated version of the website -- can you check if refreshing the page updates it with the latest search bar design? If that doesn't work, can you try hard refreshing (ctrl + shift + R) or clearing your browser's cache? Please let us know if either solution works.

Wow! This is an interesting bug that is definitely related to some caching troubles with the webapp we've been working on. This is a really early version of the new home page that was recently enabled. What I believe happened was

Your browser received a new config to enable the home page
The old webapp bundle was still cached and wasn't properly invalidated, so an early in-progress version of the new home page was rendered

I went to the page again today and now I see this:

Search is working again. I didn't do anything to clear the cache.

authors: Chriscbr gabewomble gshpychka

repo: cdklabs/construct-hub-webapp