documentation about ng-model

I found that with an <input date-time>, ng-model must refer to a boxed object, or its binding will not work, apparently due to datepicker's nested scope.  For example, the following does not work:
<input date-time ng-model='foo'>

While this does:
<input date-time ng-model='box.foo'>

This would be a good point to cover in the documentation.

Would you accept a pull request that added some logic like if (attrs['ng-model'].indexOf('.') === -1){return 'warning';} to make sure that people do not waste time using the library in the wrong way?

Do you have a more complete example of what you mean by boxed object? I'm having trouble understanding how to pass an existing date value to the date-time input via ng-model. I've tried converting the date to a moment object etc, but nothing seems to work :/

@AdamGerthel: boxing means that the date object must be within another object.  It can't be a direct property of $scope.  You would use code like this in your controller:
// initialize
$scope.datebox = { someDate: new Date() };

// set value
$scope.datebox.someDate = new Date("2016-01-01");

Then in your template:
<input date-time ng-model='datebox.someDate'>


Rabbit Binder retries on failed message even when max-attempts=1

From @cppwfs on September 30, 2016 18:37
null
Copied from original issue: spring-cloud/spring-cloud-stream#670

From @cppwfs on September 30, 2016 18:38
when setting spring.cloud.stream.bindings.input.consumer.maxAttempts=1, I expected that upon failure (i.e. service activator throws exception) that it would not retry the message.  However the sink continues to retry to process the message.
The workaround was to set requeue-rejected to false.

From @garyrussell on September 30, 2016 19:33
We should probably just go ahead and set it to false by default - when retry is enabled, we always "recover" the message, either by republishing it, or rejecting it without requeue. It probably never makes sense to set this to true but it won't hurt to leave it there as a setting.


Let worker ungracefully exit on memoryExceeded

This allows us to distinguish between a graceful exit (shouldRestart) and application crashes (memoryExceeded) that should trigger an autorestart according to supervisord.

Please send to 5.4 branch.


adding Authjs

Is there an easy way to add authjs to the template to protect some routes. I have a very basic knowledge, and I would appreciate some help.
#255
Thanks

Nope, no current plans to support adding protected routes.


Use custom trigger icon

Is your feature request related to a problem? Please describe.
We should offer a simple way to change the floating trigger icon in the config, instead of having to create a custom component and call openMarkprompt in JS.

Closed: https://github.com/motifland/markprompt-js/pull/222


[HUDI-7187] Fix integ test props to honor new streamer properties

Change Logs
As of now, all integ tests properties file are holding deltastreamer props. I've changed them to streamer props.
Impact
none
Risk level (write none, low medium or high below)
none
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@hudi-bot run azure

@yihua I made fixes by all your comments. Review please and merge if everything is ok.

@wombatu-kun Thanks for the contribution!  Are you interested in more code restructuring and core abstraction work?  Feel free to reach out to me on Hudi Slack.

@wombatu-kun Thanks for the contribution! Are you interested in more code restructuring and core abstraction work? Feel free to reach out to me on Hudi Slack.

@yihua Yes, i'm interested in code refactoring, restructuring and core abstraction work, that is why i'm here! Right now i'm not really familiar with all core abstractions and functionality of hudi in depth, but i'm trying hard to figure this out as soon as possible. So definitely I'll reach out to you on Slack in nearest future. Thanks!


NIFI-5122 - Add Record Writer for S2S RTs

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Reviewing...

Thanks for the feedback @mattyb149, I just pushed another commit, let me know if it's what you had in mind :)

@pvillard31 @mattyb149 Reviewed it and the changes look fine, but noticed something weird when I fired up a full build w/ it. When I'd add one of these tasks, the status would stay spinning at "validating..." until I hit start. Did either of you see that? Didn't seem to actually break anything yet.

@MikeThomsen - I know @mcgilman recently fixed something weird in the UI around CS/RT dialogs. Could you try cleaning your cache or using a private session to confirm?

Cleared the cache, and it didn't change anything. However, all three of the s2s tasks I tried (metrics, bulletin and provenance) seemed to work just fine when reporting to a second instance of NiFi. So as far as I am concerned, if you and @mattyb149  don't think the validating issue is a big deal or tied to this I'm ok with merging.

@pvillard31 @mattyb149 I'll merge today if one of you gets back to me on this.


perf(refCount): optimize the implementation of class RefCounterOperator

Description:
Since the source and the connectableObservable is the same thing in RefCountOperator, there is no need to hold the variable connectable int the RefCountOperator
Related issue (if exists):
NONE

Pull Request Test Coverage Report for Build 8388

8 of 9 (88.89%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.001%) to 96.674%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/internal/observable/ConnectableObservable.ts
0
1
0.0%

Totals

Change from base Build 8387:
-0.001%

Covered Lines:
5203

Relevant Lines:
5382

💛  - Coveralls

I'm not sure how I feel about exposing all of these properties as public. They really aren't meant to be consumed by other users.

Yeah，i gave it a second thought. This commit indeed is just removing  the unused reference of source， nothing about performance.


Validate editor.formatOnType validity using Python's test grammar

https://github.com/python/cpython/blob/master/Lib/test/test_grammar.py
We should run this file through tests at least once to make sure things work, but it's probably better to write a test for this as well to prevent regressions (we will need to make sure to update it for each new release of Python).

And if we do embed the file as a test then we will need to add the Python license appropriately.

I found another bug in the editor.formatOnType support, so doing this validation is getting important.


Fix for HHH-10631

https://hibernate.atlassian.net/browse/HHH-10631

Thanks for the PR. Did you sign the CLA?

Yeah, signed two days ago, awaiting approval yet.

Great! Your proposal is very good, so I'll just rebase and move the test into a new method so we know why we added it in the first place. Then, I'll apply it on master. Thanks for contributing.

Applied upstream on master.


Interested in using an .npmignore file?

here's the docs: https://www.npmjs.com/package/npmignore
I would create a PR, if you say this would be of interest :v:

The files key in package.json handles that.


Hosted Ubuntu agent capability

are you sure the following variables paths are for Ubuntu??? It seems like Windows paths. And this persists for months.

@dakale

Ignore those capabilities. We are in the process of updating the UI for agent pools.

Ignore those capabilities. We are in the process of updating the UI for agent pools.

But I need to get some paths on this agent, where can I get them now

close this issue since we didn't hear back from customer.
please reopen if more help is needed.


could return null

https://github.com/lim-it-ing/MultiUser-Meeting-Scheduler/blob/3f194dfafb67453152f66dbb829880a365c25371/routes/user/schedule.js#L81
There is result of null at user_times

  if (user_times.length ===0){
    res.send(time_arr);
    return;
  }

Does this could enhance this issue?

Solved.


chore(main): release 0.1.0

:robot: I have created a release beep boop
0.1.0 (2022-11-29)
Features

修改默认页面样式 (8dd3779)
新增Lua处理和conf整体配置 (7e84110)
新增workflow (e40ff8e)

Bug Fixes

修复时区和default替换为ngxway等问题 (3e02e81)
修复构建镜像和container清理顺序导致的bug (6fa7248)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/WGrape/ngxway/releases/tag/v0.1.0 :sunflower:


Account name differs from Go import URL

@andrewslotin Love your work, we use it.
However, we realized that we have an issue that was unforeseen:   Our GitHub account has a capital letter, but our Go import URLs are all lower case.
We're considering writing a version of your code at https://github.com/Senzing/github-action-go-proxy-pull, but if you are able to accommodate this requirement, we'd be happy to continue using your GitHub Action.
Essentially we are adding code like this:
PACKAGE=$(echo ${PACKAGE} | tr '[:upper:]' '[:lower:]')

for our case, but you would have to be sensitive to other conditions that your users may have.
Our special case may not lend itself well to the work you have done.  We just wanted to make you aware of what we're doing.

Hey @docktermj, thanks for the heads up and your kind words. I believe there is another way to address your issue that other users may benefit from. Currently this action assumes that import path always matches the GitHub repository name, which is not always the case, since Go allows to use custom URLs as imports path as long as they respond with an HTML doc containing <meta name="go-import"> tag that points to the actual module location. I believe this case is rather rare, yet not completely impossible.
I'm thinking of making the import path configurable via an env var and using the GitHub repo as a default, so in your case you'll need to update your workflow configuration and provide package import path as a parameter. Does this make sense?

@andrewslotin That's an excellent improvement.  Once your PR is pulled into your main branch and versioned we'll start using it and delete our https://github.com/Senzing/github-action-go-proxy-pull repository.  Thank you for your prompt attention to this.  We weren't expecting it and are delighted.   Keep up the good work!
Once you have pulled your changes into the main branch, feel free to close this issue.

@docktermj, I've just released v1.1.0 of this action on GitHub Marketplace.

@andrewslotin There may still be an issue.    Did you miss the package name at the end?

@andrewslotin That could be it.  Let me give that a try.

@andrewslotin I think you found the fix.  We're all good.  Thank you for your help.   I'll be deleting our repository.


String Theory Schools

@S1monuwu I am sorry for a delay with processing your request.
Pull request merged. Thank you!


[Bug]: Traefik dynamic setup not working

Description
I just followed docs here and it ask me for the basic auth credentials but when I enter those it throws a 404 page. I think it is not quite getting to the service api@internal or something.
Minimal Reproduction (if possible, example repository)
Enter the following *.yml file into the Dynamic Configurations for the proxy of your server. Assuming the IP of your server is <IP_ADDRESS>. Password is the same as the docs test test
http:
  routers:
    dashboard:
      rule: Host(`<IP_ADDRESS>.sslip.io`) && (PathPrefix(`/dashboard`) || PathPrefix(`/api`))
      service: api@internal
      middlewares:
        - auth
  middlewares:
    auth:
      basicAuth:
        users:
          - "test:$apr1$154ethlp$Re.R1QjCkyOyKKmgYHHYP1"

Bonus: (Not a blocker)
When entering the contents of the *.yml file the first time it throws an error about base64 encode and it enters the file as empty which then you can proceed to hit the Edit button and enter the contents of that file right there.
Exception or Error
No response
Version
v4.0.0-beta.239

Yeah happening to me in container load balancing.
After further investigation, it appears the root of my "Bad Gateway" issues is that Traefik's dynamic proxy functionality isn't working as expected. Despite configuring Traefik to dynamically route traffic based on hostnames and paths, requests aren't correctly forwarded to the intended backend services.
It seems that the challenges with Traefik's dynamic proxy not functioning correctly are linked to the recent update to version v4.0.0-beta 237 (released on March 14th).

I'm having the same difficulty, I couldn't define the "Dynamic Configurations".
When accessing the defined host, the 404 page is displayed.

This still seems to be an ongoing issue even on: v4.0.0-beta.293.
Same configuration, still error 404 page not found.

i think i am experiencing a bug related to this issue where my config is not recognized in my container. I get this error: 2024-06-04T14:12:19.408664499Z time="2024-06-04T14:12:19Z" level=error msg="the service \"forward-compute@docker\" does not exist" routerName=compute-forward-router@docker entryPointName=https

I'm wondering if my issues have the same origin. I can't access coolify which I've hosted on my on premise server from another VLAN in the same network.
It is accessible from externally.
Now, I've tried to restart the proxy and it doesn't want to start up again.

I'm wondering if my issues have the same origin. I can't access coolify which I've hosted on my on premise server from another VLAN in the same network. It is accessible from externally.
Now, I've tried to restart the proxy and it doesn't want to start up again.

I can agree on this, I had to reinstall everything a few days ago. After the proxy crashed (for unknwon reasons) it was unable to restart. I mean, it could restart but it didn't work at all and had config issues. Resetting didn't help at first, but manually deleting everything and reinstalling worked (the uninstall script wasn't enough).

I initially had the same issue of getting a 404 page when trying to access the dashboard, but I eventually got it working after doing a few things.
Firstly, my domain for the dashboard is set up in Cloudflare with strict TLS, and going to the URL showed an error page related to an invalid SSL cert. To fix it, I added the following line to the dynamic config file.
tls:
        certresolver: letsencrypt

Secondly, and this is the most important part, I ADDED A TRAILING SLASH TO MY URL. For whatever reason, it is MANDATORY. Instead of going to https://example.com/dashboard, you have to go to https://example.com/dashboard/
https://doc.traefik.io/traefik/operations/dashboard/#the-dashboard

The trailing slash / in /dashboard/ is mandatory

My dynamic configuration file is named dashboard.yaml and looks like this (edited to take out sensitive details):
http:
  routers:
    dashboard:
      rule: 'Host(`<DOMAIN>`) && (PathPrefix(`/dashboard`) || PathPrefix(`/api`))'
      service: api@internal
      tls:
        certresolver: letsencrypt
      middlewares:
        - auth
  middlewares:
    auth:
      basicAuth:
        users:
          - '<USERNAME>:<GENERATED PASSWORD HASH>'

After I applied the traefik dashboard config my coolify dashboard does not work anymore so I have to resort to troubleshooting via SSH
http:
routers:
dashboard:
rule: 'Host(traefik.mydomain.com) && (PathPrefix(/dashboard) || PathPrefix(/api))'
service: api@internal
middlewares:
- auth
middlewares:
auth:
basicAuth:
users:
- 'admin:'

I initially had the same issue of getting a 404 page when trying to access the dashboard, but I eventually got it working after doing a few things.
Firstly, my domain for the dashboard is set up in Cloudflare with strict TLS, and going to the URL showed an error page related to an invalid SSL cert. To fix it, I added the following line to the dynamic config file.
tls:
        certresolver: letsencrypt

Secondly, and this is the most important part, I ADDED A TRAILING SLASH TO MY URL. For whatever reason, it is MANDATORY. Instead of going to https://example.com/dashboard, you have to go to https://example.com/dashboard/
https://doc.traefik.io/traefik/operations/dashboard/#the-dashboard

The trailing slash / in /dashboard/ is mandatory

My dynamic configuration file is named dashboard.yaml and looks like this (edited to take out sensitive details):
http:
  routers:
    dashboard:
      rule: 'Host(`<DOMAIN>`) && (PathPrefix(`/dashboard`) || PathPrefix(`/api`))'
      service: api@internal
      tls:
        certresolver: letsencrypt
      middlewares:
        - auth
  middlewares:
    auth:
      basicAuth:
        users:
          - '<USERNAME>:<GENERATED PASSWORD HASH>'

This method works. make sure to access the dashboard using the full link provided in the docs https://traefik.yourdomian.com/dashboard/#/

After I applied the traefik dashboard config my coolify dashboard does not work anymore so I have to resort to troubleshooting via SSH

@Trubador I ran into a similar issue before, and I think I fixed it by restarting the proxy. If you ssh into the relevant server, what do you see when you run docker ps or sudo docker ps? If the proxy is running, you should see a running container with the name coolify-proxy. If Coolify itself is running, there would also be a container with the name coolify.
CONTAINER ID   IMAGE                                              COMMAND                  CREATED       STATUS                 PORTS                                                                                NAMES
6ecfa8480e8d   traefik:v2.10                                      "/entrypoint.sh --pi…"   4 weeks ago   Up 4 weeks (healthy)   <IP_ADDRESS>:80->80/tcp, :::80->80/tcp, <IP_ADDRESS>:443->443/tcp, :::443->443/tcp, <IP_ADDRESS>:8080->8080/tcp, :::8080->8080/tcp   coolify-proxy
0f4f37180bca   ghcr.io/coollabsio/coolify:4.0.0-beta.294          "/init"                  4 weeks ago   Up 4 weeks (healthy)   443/tcp, 8000/tcp, 9000/tcp, <IP_ADDRESS>:8000->80/tcp, :::8000->80/tcp                                                    coolify

I don't remember whether I found a way to start the proxy programmatically. I would have to look through the Coolify codebase to figure that out. However, I think I was able to start the proxy by doing the following steps:

On the server that should run the Coolify Dashboard, update your firewall to allow a tcp connection to port 8000 if you haven't already done so. https://coolify.io/docs/knowledge-base/server/firewall#self-hosted-version
Access the Coolify dashboard by visiting the http version through the server IP and relevant port (i.e. http://123.456.789:8000)
Go to the Servers tab
Select the server that should run the proxy
Press the "Start proxy" button.

After I applied the traefik dashboard config my coolify dashboard does not work anymore so I have to resort to troubleshooting via SSH

@Trubador I ran into a similar issue before, and I think I fixed it by restarting the proxy. If you ssh into the relevant server, what do you see when you run docker ps or sudo docker ps? If the proxy is running, you should see a running container with the name coolify-proxy. If Coolify itself is running, there would also be a container with the name coolify.
CONTAINER ID   IMAGE                                              COMMAND                  CREATED       STATUS                 PORTS                                                                                NAMES
6ecfa8480e8d   traefik:v2.10                                      "/entrypoint.sh --pi…"   4 weeks ago   Up 4 weeks (healthy)   <IP_ADDRESS>:80->80/tcp, :::80->80/tcp, <IP_ADDRESS>:443->443/tcp, :::443->443/tcp, <IP_ADDRESS>:8080->8080/tcp, :::8080->8080/tcp   coolify-proxy
0f4f37180bca   ghcr.io/coollabsio/coolify:4.0.0-beta.294          "/init"                  4 weeks ago   Up 4 weeks (healthy)   443/tcp, 8000/tcp, 9000/tcp, <IP_ADDRESS>:8000->80/tcp, :::8000->80/tcp                                                    coolify

I don't remember whether I found a way to start the proxy programmatically. I would have to look through the Coolify codebase to figure that out. However, I think I was able to start the proxy by doing the following steps:

On the server that should run the Coolify Dashboard, update your firewall to allow a tcp connection to port 8000 if you haven't already done so. https://coolify.io/docs/knowledge-base/server/firewall#self-hosted-version
Access the Coolify dashboard by visiting the http version through the server IP and relevant port (i.e. http://123.456.789:8000)
Go to the Servers tab
Select the server that should run the proxy
Press the "Start proxy" button.

Thanks this was the same approach I eventually figured out that worked. Perhaps it might be possible to start the proxy again by listing the containers that are not running using "docker ps -a" and then starting it from there. But yeah the problem arose because I tried to restart the proxy in the hope that the traefik dashboard would work so I could gain some visibility into the networking. Perhaps there is a tool to visualize the entire docker internal networking and traefik in a dependency map?

Same problem here. Using caddy or traefik, can't connect to local backend port

In my case, anytime I restart the proxy, I get a 404 when accessing the Coolify dashboard. The websites and the other services are working, though.

In my case, anytime I restart the proxy, I get a 404 when accessing the Coolify dashboard. The websites and the other services are working, though.

same issue I got - was able to start it from docker terminal on the vm

I'm on version v4.0.0-beta.360 and I'm still getting "404 page not found". I've restarted proxy but it didn't fix it.

Got the dashboard up by adding - traefik.http.routers.traefik.rule=Host(lb.example.com) to the proxy's configuration. From Traefik's dashboard, my custom domain is not listed which implies that the labels added to the docker-compose service is not been identified properly.

I've been able to resolve the error. The container with the custom domain was erroring out. Fixed it and it's working now.

I've been able to resolve the error. The container with the custom domain was erroring out. Fixed it and it's working now.

Can you quickly explain what you've done?


example fails to compile

Maybe I am doing something wrong. Here are the steps:

git clone https://github.com/web-ridge/react-native-paper-dates.git
cd react-native-paper-dates/example
yarn install
expo build:web

After the yarn install command there are some warnings:
yarn install v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "expo ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "expo > babel-preset-expo > @babel/preset-env ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "react-native-vector-icons@*".
[4/4] Building fresh packages...
Done in 15.85s.

The expo build:web command outputs:
Failed to compile.

/home/teslarenting/dev/tesla-renting/client/react-native-paper-dates/src/Date/DatePickerInput.tsx
Cannot find module: '@babel/runtime/helpers/extends'. Make sure this package is installed.

You can install this package by running: yarn add @babel/runtime/helpers/extends.

Hey That's right I'm still working on it at master maybe install the latest stable version

I still need to fix master but I stopped when I was half done with the input so you're totally right some things don't work yet on master since I was rewriting the example to expo but stopped somewhere in between

Hey That's right I'm still working on it at master maybe install the latest stable version

I tried that, too. But then I have to run yarn bugfix and that wants to make global changes on my system.
react-native-paper-dates-0.4.6/example$ yarn bugfix
yarn run v1.22.10
$ npm link ../node_modules/react --legacy-peer-deps --force
npm WARN using --force Recommended protections disabled.
npm ERR! code EACCES
npm ERR! syscall symlink
npm ERR! path ../../../home/teslarenting/Downloads/react-native-paper-dates-0.4.6/node_modules/react
npm ERR! dest /usr/lib/node_modules/react
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, symlink '../../../home/teslarenting/Downloads/react-native-paper-dates-0.4.6/node_modules/react' -> '/usr/lib/node_modules/react'
npm ERR!  [Error: EACCES: permission denied, symlink '../../../home/teslarenting/Downloads/react-native-paper-dates-0.4.6/node_modules/react' -> '/usr/lib/node_modules/react'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'symlink',
npm ERR!   path: '../../../home/teslarenting/Downloads/react-native-paper-dates-0.4.6/node_modules/react',
npm ERR!   dest: '/usr/lib/node_modules/react'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/teslarenting/.npm/_logs/2021-07-29T23_01_59_942Z-debug.log
error Command failed with exit code 243.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I don't want to mess with this command, so it really sucks, that everything I try with this library is not working. But I find the features so interesting that I am searching for other ways to make it work for my project.


more variables.less (border-width,…)

When making themes with themestrap, I often end up making new variables for a number of hardcoded things in bootstrap.
Most often these are the border-widths of a lot of elements.
How are you guys thinking about addings more variables in general, and especially in the border-width-case? I would follow up with a Pull Request if you approve.
I think I would go about like this:
@border-width-default: 1px;
@hr-border-width: @border-width-default;
[…]

Inspired by the @border-radius declarations, we could also go about it like this:
@border-width-default: 1px;
@border-width-large: 3px;
@hr-border-witdh: @border-width-default;
@btn-border-witdh: @border-width-large;
[…]

I agree with @ronlobo , I think since we have such great border control (in terms of colors) over most of the components, that having a border-width variable on the component level would indeed be pretty useful. Maybe many people aren't customizing border-width's across the project, but  this variable would be useful for adjusting certain components, and especially for removing borders themselves (instead of going in and changing each components different variation of border-color to transparent). I don't really think a default border-color would be very useful anyway, the way the colors are handled currently makes sense.
Thanks for considering


Type guards as assertions

This PR fixes several of the issues we've had around nothing types in control flows. We previously took the view that when the current control flow based type of a variable is disjoint with the type implied by a type guard, we produce type nothing. Effectively, we'd trust that the control flow based type is right and therefore conclude that the type guard must be wrong.
This PR changes the reasoning in favor of the type guard instead. We now say that if narrowing the current control flow type produces nothing, but narrowing the declared type would produce an actual type, then the type guard must be there for a reason (and consequently we must have missed something in the reasoning about the control flow). Therefore, instead of producing nothing, we revert to the declared type and narrow that. Effectively we treat the type guard as an assertion that the condition could be true and respect it if it actually could be true according to the declared type.
Things that could cause the control flow reasoning to disagree with the type guard include an invalid argument passed for a parameter or an assignment to local variable by a nested function. For example:
function foo() {
    let s: string | undefined = undefined
    function inner() {
        // Possibly assign to s
    }
    inner();
    if (s) {
        // Treat s as string instead of nothing
    }
}

Fixes #8513.
Fixes #8429.

what about the idea of not using types from nothing branches ?

@mhegazy The idea of ignoring types from nothing braches is more complicated than it first appears. When computing the control flow based type for a given variable, it isn't enough to just check if the variable is nothing before an assignment as we discussed. A branch might be dead code for other reasons (e.g. a type guard on another variable) and we'd need to analyze that separately. That possibly requires separate passes for loop constructs and creates new opportunities for circularities. Plus it wouldn't actually solve the problem shown in my initial description for this PR (the problem in #8429 which we only sort of solved in cases where variables don't have an initializer or a preceding assignment).
In aggregate I think this new approach is much better. We only produce nothing types when there is no possible way a type guard could be true. In cases where it might be true, we assume it is and do  out best to make the types work out.

I think this is generally a pretty good direction, though I'll probably need to think more on it. I still think it would be worth investigating flagging spots where a condition narrows to nothing if a user is interested.

:+1:

Yes, if a branch is inferred to be nothing, it might be dead code. Even more so if the user has added a type guard there. Since the compiler warns about dead code in other forms it would be nice to continue being able to warn about this.

Latest commits adds the "revert to declared type" behavior to the ! postfix operator to make it consistent with type guards. This is the previously suggestion option 1 from this discussion. I believe this fixes the issue that still remained in @ivogabe's code.

@ahejlsberg
This seems arbitrary:
function func(x: number | string) {
    x; // 'x' has type 'number | string' here

    if (typeof x !== "number" && typeof x !== "string") {
        x; // why does 'x' get type 'number' here?
		   // why not, say, 'string', 'number | string', or 'nothing' instead?

        return;
    }

	x; // 'x' has type 'number | string' here
}

(tested on 1.9.0-dev.20160514)

Yes, it does seem a bit arbitrary that x gets type number. The reason is that we switch back to the declared type only once we discover that a narrowing operation would produce nothing, and that doesn't happen until the second typeof test. Consider this equivalent code:
if (typeof x !== "number") {
    x;  // string (we're fine here)
    if (typeof x !== "string") {
        x;  // number (we switched back to declared type)
    }
}

The behavior above doesn't seem quite as arbitrary, but from a control flow perspective there's really no difference.
All in all, we're talking about the best possible compromise here. None of this happens as long as you're writing meaningful code and the alternative of nothing exhibits several issues that in aggregate seem worse.

First, I think one confusing part here is why you referred to number, and not number | string as the 'declared type'. So perhaps there's some non-ideal terminology here. I believe you mean something like 'origin type' or 'previous type'.
I feel that in order to get a good perspective on this I would need to observe many examples and variations or become familiar with the actual, precise logic that is being used at this point.
Anyway, I tried two more variations and compared them:
Expected:
function func1(x: number | string | boolean ) {
	x; // (1) 'x' has type 'number | string | boolean'

    if (typeof x !== "number") {
		x; // (2) 'x' has type 'string | boolean'

		if (typeof x !== "string") {
        		x; // (3) 'x' has type 'boolean'
		}
    }
}

Unexpected:
function func2(x: number | string | boolean ) {
    x = "hi";
	x; // (1) 'x' has type 'string'

    if (typeof x !== "number") {
		x; // (2) 'x' still has type 'string'

		if (typeof x !== "string") {
        		x; // (3) 'x' has type 'number | boolean'
		}
    }
}

So it seems that in the second example, the unexpected negative assertion for a string type made the compiler somehow suddenly consider number as a valid possibility for (3), unlike in the first example. This is despite the fact that a number typed value was never assigned to x and there wasn't any positive or negative guard for number aside for the one that preceded (2). It looks a bit bizarre. I'm not sure if it makes any sense.

OK, I think I got the idea, it reverts back to the 'declared type' but then applies the negative assertion. So it is more like the Declared Type - negatively asserted type.
I feel that's a very simple (simplistic?) way to approach this scenario. The original intention here seemed to have been to address cases with positive assertions, which seem much simpler. Negative assertions seem less trivial. I'm trying to think about alternative solutions, hopefully not ones that would require more complex techniques like backtracking etc. - though it may be unavoidable here, I'm not sure at this point.

I think I could isolate the issue here in the following way:
function func2(x: number | string | boolean) {
    x = "hi";
    // (1)

    if (typeof x !== "number") {
        // (2)

        if (typeof x !== "string") {
                x; // (3) 'x' has type 'number | boolean'
        }
    }
}

With the new logic, the compiler now makes the 'worst-case' assumption that the mysterious event that caused x not to be a string and eventually pass the if (typeof x !== "string") guard happened somewhere in  (2), i.e. after the negative assertion if (typeof x !== "number") was made. However that assumption isn't necessarily correct - it could have happened in (1) as well.
So after looking at like this, surprisingly I'm starting to think this is somewhat reasonable after all as a rough fallback, for these types of cases.
However the original one, there wasn't any side effect that could possibly happen between the two negative assertions, so I believe it would be better for it to fall back to either number | string or nothing here:
function func(x: number | string) {
    x; // 'x' has type 'number | string' here

    if (typeof x !== "number" && typeof x !== "string") {
        x; // why does 'x' get type 'number' here?
    }

    x; // 'x' has type 'number | string' here
}

(it would be extremely unusual if x is somehow reassigned between the two typeof predicates - anyway, that would be some serious abuse of the short-circuiting and operator)

I'll try to 'reboot' once again from a more practical perspective:
function func(x: number | string) {
	if (typeof x !== "number" && typeof x !== "string") {
		// 'x' gets type 'number' here
		//
		// However the programmer's intention was most likely to check if it was
		// null, undefined, or another type that's not 'number' or 'string'
		// ..
	}
}

func(<any> undefined); //'<any> cast not needed if non-nullability is disabled

The 'argument' for this behavior was that it is somehow consistent with nested guards and that the compiler is not 'smart' enough to differentiate between conjunct and nested guards. However, That's not really a satisfying argument. That just explains why it happens, but doesn't show why is that a reasonable outcome for this relatively common scenario - and based on relatively objective measures, it most likely isn't.

I had some initial conception of an alternative approach, that's still quite 'rough', but provides somewhat more precise 'awareness' for the soundness, or 'confidence' levels for types. I felt that I'm not in a position to evaluate how useful or suitable something like this would be to augment the current analysis, but I wanted to share it here anyway, in case it does turn out to be of some use (perhaps for even other things like literal types etc.).
Idea sketch: soundness metrics for flow analysis
What if the compiler had implicit traits for analyzed type T being either

sound T
unsound T
sound not T
unsound not T

This includes a granular trait for each individual component of a union. E.g. a union like number | string | boolean which just received a number type through a literal would be internally tracked as:
(sound number, sound not string, sound not boolean)

Some general rules:

All uninitialized or ambient variable, or parameters types start as unsound.
A variable assigned by a literal receieves a sound type.
A variable assigned by another variable receives the same type metrics as the type of the secondary variable.
Whenever a function is called, which may have side effects, all variables that could possibly be captured by the function are 'degraded' from sound to unsound (note there's no need to actually analyze every function, e.g. one can assume the worst case where all called functions may reassign all their captured variables).

Simple examples:
declare let x: number | string; // x starts as (unsound number, unsound string)

x = 1; // x is (sound number, sound not string)

function mysteriousFunction() {
	// ..
}

mysteriousFunction(); // all 'sound' types of  variables possibly captured by the
					  // function are degraded to 'unsound'

x;  // x is (unsound number, unsound not string)

if (typeof x !== "number") {
	x; // 'x' falls back to (sound not number, unsound string)
	   // which is effectively seen as 'string' for the programmer
}

Another example:
let x: number | string; // x starts as (unsound number, unsound string)

x = 1; // x is (sound number, sound not string)

if (typeof x !== "number") {
	x; // 'x' falls back to (sound not number, sound not string)
	   // which is effectively seen as 'nothing' to the programmer
}

More complex example:
function func(x: number | string | boolean) {

	// x is (unsound number, unsound string, unsound boolean)
	x = "hi";
	// x is (sound not number, sound string, sound not boolean)

	mysteriousFunction();

	// x is (unsound not number, unsound string, unsound not boolean)

	if (typeof x !== "number") {
		// type of 'x' is (sound not number, unsound string, unsound not boolean)

		if (typeof x !== "string") {
			// type of 'x' is (sound not number, sound not string, unsound not boolean)
			// the type shown to the programmer is 'boolean' - despite the fact it is negated,
			// the negation isn't considered sound so that's the only remaining option.
		}
	}
}

I cannot predict, at this point, and with my limited knowledge, if, when and how exactly these metrics would be applied, though. I guess it feels too early for that.

Just wanted to mention I'm aware of this possibility:
function example() {
	let x: number | undefined = 1;

	function imNotCalledDirectly() {
		x = undefined;
	}

	let secretBox = { secret: imNotCalledDirectly };

	callTheFunctionInTheBox(secretBox);
	// x is now undefined
}

However that's not really something that cannot be accounted for as well. Simply assume the worst possible case and consider all local variable types as unsound if there's a nested function (that's either named or anonymous, called or uncalled) that has it in scope. There are still many useful real-world cases where there are no nested functions at a particular variable's scope.


time: parseTimeZone() doesn't work for for many Zones formatted by Time.Format()

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.9.4
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/kasch/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/kasch/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build708812266=/tmp/go-build -gno-record-gcc-switches"
What did you do?
package main

import (
	"time"
)

func main() {
	loc, err := time.LoadLocation("Europe/Istanbul")
	if err != nil {
		panic("Cannot load Timezone: " + err.Error())
	}

	timeStamp := time.Date(2018, 02, 23, 0, 0, 0, 0, loc)

	layout := "2006-01-02 15:04:05 MST"
	_, err = time.Parse(layout, timeStamp.Format(layout))

	if err != nil {
		panic("Cannot Parse Time: " + err.Error())
	}
}

Example in Go Playground
some Timezones from IANA database do get parsed correctly (eg. Europe/Istanbul)
see tz database +03 is used as timezone: https://github.com/eggert/tz/blob/6df98f4244eaa5ef9af50d71020faa9364b52f09/europe#L3738
there are more Timezones using times Like this one
What did you expect to see?
no panic, as I assume that the time package should be able to read every timestamp it produces with the same layout string
What did you see instead?
panic: Cannot Parse Time: parsing time "2018-02-23 00:00:00 +03" as "2006-01-02 15:04:05 MST": cannot parse "+03" as "MST"

The timezone handling by the time package is entirely dependent on the files supplied by your operating system.  As you have shown, due to changes in the way that Turkey handles time zones, the files on your system print some dates in the Europe/Istanbul timezone using +03, but there is no timezone with that abbreviation.  As the docs for time.Parse say, using MST in the parse string only matches defined timezones, and there is no timezone named +03 on your system.
It is not a goal that time.Time.Format and time.Parse be exact reverses of each other.  In general, that is impossible, as is demonstrated by this case.
Use time.ParseInLocation instead.
Closing because there is nothing we can do.

Actually that is not completely true, as it can be matched on the system and the error is generated before trying to match it.
time.Parse calls time.ParseTimeZone() which then rejects this as it does not fit into the scheme having at least three upper case letters and a T in the end, see:
https://github.com/golang/go/blob/master/src/time/format.go#L1106-L1146
adding a third special case like:
if value[:1] == "+" || value[:1] == "-" {   return 3, true }
and packing my example into a test in that package shows that this is easily solvable.
I am also willing to fix that using a bit more sophisticated special case then shown above, if this bug gets accepted.

OK, sure, let's try that.


Fixed compatibility of full_messages for Ruby 3.0

Summary
Fixed compatibility of Discordrb::Errors::CodeError#full_message with IRB for Ruby > 3.0. Fixed #163

Added
Changed
Added unused args to #full_messages.
Deprecated
Removed
Fixed

Thanks!


Enable go linter suite (stylecheck / critic)

The golangci configuration is updated to include missing linters. Linter
warnings are resolved.
For this change, we continue to disable some linters to decrease the scope
of linter fixes. Upcoming changes will continue to increase linter scope.
Story: #205
Signed-off-by: Troy Ronda<EMAIL_ADDRESS>

Codecov Report

Merging #217 into master will not change coverage.
The diff coverage is 62.22%.

@@           Coverage Diff           @@
##           master     #217   +/-   ##
=======================================
  Coverage   86.63%   86.63%
=======================================
  Files          35       35
  Lines        1407     1407
=======================================
  Hits         1219     1219
  Misses        104      104
  Partials       84       84

Impacted Files
Coverage Δ

cmd/aries-agentd/main.go
69.23% <ø> (ø)
:arrow_up:

pkg/internal/common/logging/modlog/logtestutils.go
100% <ø> (ø)
:arrow_up:

pkg/storage/leveldb/leveldb_store.go
100% <100%> (ø)
:arrow_up:

pkg/framework/context/context.go
100% <100%> (ø)
:arrow_up:

pkg/didcomm/transport/http/inbound.go
82.85% <100%> (ø)
:arrow_up:

pkg/didcomm/crypto/jwe/authcrypt/encrypt.go
76.11% <100%> (ø)
:arrow_up:

pkg/restapi/operation/didexchange/didexchange.go
76.92% <100%> (ø)
:arrow_up:

pkg/didmethod/peer/store.go
76.74% <37.5%> (ø)
:arrow_up:

pkg/doc/did/doc.go
92.64% <50%> (ø)
:arrow_up:

pkg/didmethod/peer/resolver.go
71.42% <50%> (ø)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


String lib definition is not a subtype of indexed collections

Currently the String lib def does not implement the following interface (example):
interface IndexedCollection<T> extends Iterable<T> {
  [key: number]: T,
  length: number,
}

However, (internally?) strings are treated as such (example). A workaround could be achieved with a union but it is lossy in comparison to the IndexedCollection interface. You still have to refine string | T and a lot of the benefits of parametric polymorphism are nullified.
// 😃
function forEach1<T>(fn: T => void, value: IndexedCollection<T>): void {
  for (let i = 0; i < value.length; i++) {
    fn(value[i])
  }
}

// 😐
function forEach2<T>(fn: (string | T) => void, value: string | IndexedCollection<T>): void {
  for (let i = 0; i < value.length; i++) {
    fn(value[i])
  }
}

tldr;
Is it sound to add a [key: number]: string property to the lib def for String? If so, I would be happy to create a PR.

Huh, it's surprising to me that this doesn't work. I wonder if someone else is aware of some super type that can be used for a function to accept strings or arrays when all it wants to do is subscript them.

Huh, it's surprising to me that this doesn't work.

Likewise!
I submitted a PR that adds the indexer property to String. It seems like an easy (yet naive) solution to this problem.

Thanks for the PR! I'm really curious to see what the core team says about this. Might be just an oversight or there might be some deep reason why it can't be there.

Thanks for the PR!

Anytime!

I'm really curious to see what the core team says about this.

Likewise. I also have a feeling that there is more to this issue.


Usermin Mailbox Folders

I was parsing through Usermin this evening and notice that the "mailbox folder" tree is missing from the left panel of your theme.
Not sure if this was intentional, accidentally missing or something being worked on. However I thought I'd be bring it to your attention as this definitely needs to be addressed since most use Usermin if not for anything else but a "webmail" tool.
By folder tree I am referring to:
Inbox
Sent
Spam
Trash
etc
etc
Cheers!

Do you mean mentioned folders should be on the right? Can you please provide screenshot?

See screenshot below which shows the "folders" in the default Virtualmin Framed theme.
 I see. Will try fixing it in the next release. Thanks.

As always, your attention to these matters is greatly appreciated!
BTW, where are you located (which timezone)?
I'm from British Columbia, Canada (3:00 am PST)
We should sit down and have a discussion sometime (over Skype) as I deal with quite a few Virtualmin users.
You can read what I'm all about, and the feedback folks have left at:
http://virtualmin.com/node/25081
Drop me a line on Skype sometime, my username is: tpnsupport

Sounds good. I'm at (+0400). I will do that one day. Need to continue work on Karateka (karateka.org).
P.S. Try adding this plugin and see if it works (and let me know). You could use new script injection mechanism. https://github.com/qooob/authentic-theme#how-do-i-load-custom-scripts

What do you use as OS do you have Empathy (Fedora/Ubuntu have it)

On my desktop and laptop I run Ubuntu 14.04 and 14.10 respectively. I use Google Chrome (not Chromium) for my browser.

Can you install Empathy? I could call you using that (you would have to have Jabber IM) - free and nice alternatives to Skype/Viber and etc. If it's a problem I will install Skype on my Linux..

I'm more of a Skype guy... Don't really do voice chats very often either (not setup intentionally) as I find I can better multi-task over a "text-based" conversation.

When I jail Skype and have time, will let you know!

It turns out, I had Empathy installed all along... Lolz
Look me up by email address<EMAIL_ADDRESS>

Yes, I know! It's default for Ubuntu.

How can you don't run xmpp server?

Let's take this chat over to: http://tpnsolutions.com
In the bottom right corner, click to expand the "chat". Not sure why I didn't about this earlier. Lolz
You can even "pop out" the chat window so it appears in an IM like way allowing you to multi-task.

Woah, totally just realized what time it was... Lolz... I'm gonna hit the hay for a few hours, gotta technically be operational within an hour... argh... Likely will sleep in til closer to 9am PST (if a client doesn't call or text me before then, knock on wood).
Later!

I'm at work for another 4 hours.
Later.

This feature and complete support for all parent folders and the rest of the left menu is added in version 10.0.0, which is released within couple of days!


I Broke Pogo(Not Sure How)

My Tips/Pogo App Is Completely Unusable.. I've tried deleting the app but it just reappears after a reboot

That’s… weird. Seems like you freshly erased. If you don’t care about your data you can restore/erase in settings.
Otherwise, you can try and install TrollStore to another removable app using SSHRD_Script, then boot palera1n and install Pogo through TrollStore.


fix(List): update List usages

Summary
Type

Enhancement

Summarise concisely:
Update some list usages
The changes of this proposal:
Selectable rows :

Remove the  properties :  idKey and data which was use only for selecting allRow, instead each row selectable row register to the context
Remove the  property isSelectable, to know if we can select row, instead we detect if props selectedIds and onSelectedIdsChange are provided or not
Select/Unselect all is now disabled if there is no selectable rows

Expandable rows :

No more List.Expandable element, but a a prop expandable. It helps identify row cells content with expandable content. It also allow to remove the isExpandable prop on List.Row
Bug fix: if a row can be extended by clicking, a column is created in header to fix headerCell / bodyCell alignment
Bug fix: the last cell wasn't properly identified some type, so the last cell available space was sometime too high
Remove hideArrow, it is now implied if isExpanded (manual expanding) is not undefined
Force isHoverable if a row can be expanded

Column sorting

onClick prop column has been renamed columnId since it refers to prop id provided to a column.
onClick prop order is now newOrder and return the opposite value of the sort value provided to a column

Others

The border/separator between cells and expandable is now the same than row border (if you specify a sentiment)
Prop variant has been renamed sentiment
Updates stories to give more info about some props

There quite a lot of new code not covered by unit testing might be nice to update tests too 😄


Update free-programming-books-langs.md

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Read our contributing guidelines.
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

not free

I thought book can be free or paid and only courses should be free

you're confusing us with paid-or-free-programming-books

Sorry! So the book is paid , what can I do should I find a free book?


data: chetannada

I have added ChetanNada.json file to the data folder according to Documentation provided by you.
Thank you @eddiejaoude for the awesome App.

I have added ChetanNada.json file to the data folder

The name of your json file needs to match your GitHub username exactly (it is case sensitive).  So instead of data/ChetanNada.json please change this to data/chetannada.json

The name of your json file needs to match your GitHub username exactly (it is case sensitive). So instead of data/ChetanNada.json please change this to data/chetannada.json

Hi @SaraJaoude I made changes in JSON file as per your comment.


HHH-16844 Fix for Informix VARCHAR, NVARCHAR mappings errors

In the getSelectClauseNullString(...) method, using getRawTypeName() is not sufficient because it does not consider the castType when using CapacityDependentDdlType.
The if (descriptor == null) condition is necessary for cases like the test org.hibernate.orm.test.jpa.query.QueryWithLiteralsInSelectExpressionTest.testSelectNullLiterals, which executes the query:
SELECT cast(null as boolean), false, e.name FROM MyEntity e
Without the condition, the query would fail with a NullPointerException

https://hibernate.atlassian.net/browse/HHH-16844

Thanks. Since you work so hard on Informix compatibility, I'm wondering, are you just a user or a developer of Informix? Would be nice to have a chat about your motivation and if you want Informix to be tested more regularly. We have some guidelines for vendors that want the dialect to become part of hibernate-core.


Updated CONTRIBUTING.md

@googlebot I signed it!

@tamojit-123 thanks for the contribution! In general we don't put the $ in the code block because it can interfere with copy-paste.  I'll accept this PR because it's mostly harmless and I want you to get credit for your effort but let's not make this change on every repo!

@samtstern Thank you for picking up this, I will look into the matter.


Design support for program migration work

Program migration TDD

As an admin, I want to export a program to be able to migrate it to a different instance
As an admin, I want to import a program to save time on program creation

Requirements:

Designs should define how an admin navigates to program import and export

Program migration mock explorations
Final functionality to be confirmed after reviewing tech feasibility with Rocky

@rockycodes I believe only blocker is finalizing the different error messages/states that may occur on this page? Let me know if thats correct. I've updated the mocks to visualize what different error messaging might look like.
Let me know if you have any questions

The one other thing on my mind is if we want admin to choose if they want to override an existing program or create a new one. But my guess is that won't be a part of v1. We'll default to override which is the requested behavior.


Unable to run Slowreq

[aanm@localhost ~]$  sudo docker run -d --name powerstrip-slowreq \
            --expose 80 \
            clusterhq/powerstrip-slowreq:latest
8b5c81fbe4904e5c69463692f1cd699741b421ede051515260ab108eaaf81811
[aanm@localhost ~]$  sudo docker run -d --name powerstrip \
            -v /var/run/docker.sock:/var/run/docker.sock \
            -v $PWD/powerstrip-demo/adapters.yml:/etc/powerstrip/adapters.yml \
            --link powerstrip-slowreq:slowreq \
            -p 2375:2375 \
            clusterhq/powerstrip:latest
123b904c9917d126986b9bbfa3717172596c3d94c6e15ec48dfee32f77e30748
[aanm@localhost ~]$ sudo docker ps -a
CONTAINER ID        IMAGE                                 COMMAND                CREATED             STATUS              PORTS                    NAMES
123b904c9917        clusterhq/powerstrip:latest           "twistd -noy powerst   7 seconds ago       Up 5 seconds        <IP_ADDRESS>:2375->2375/tcp   powerstrip
8b5c81fbe490        clusterhq/powerstrip-slowreq:latest   "python slowreq.py"    20 seconds ago      Up 19 seconds       80/tcp                   powerstrip-slowreq
[aanm@localhost ~]$  time sudo docker run ubuntu echo hello
hello

real    0m0.914s
user    0m0.011s
sys     0m0.012s
[aanm@localhost ~]$ sudo docker ps -a
CONTAINER ID        IMAGE                                 COMMAND                CREATED             STATUS                     PORTS                    NAMES
fc85127fff99        ubuntu:latest                         "echo hello"           11 seconds ago      Exited (0) 9 seconds ago                            clever_mayer
123b904c9917        clusterhq/powerstrip:latest           "twistd -noy powerst   39 seconds ago      Up 37 seconds              <IP_ADDRESS>:2375->2375/tcp   powerstrip
8b5c81fbe490        clusterhq/powerstrip-slowreq:latest   "python slowreq.py"    52 seconds ago      Up 51 seconds              80/tcp                   powerstrip-slowreq
[aanm@localhost ~]$ time DOCKER_HOST=localhost:2375 docker run ubuntu echo hello
FATA[0001] Error response from daemon:
Could not connect

real    0m1.025s
user    0m0.009s
sys     0m0.004s

[aanm@localhost ~]$ sudo docker version
Client version: 1.5.0-dev
Client API version: 1.18
Go version (client): go1.4.1
Git commit (client): 2243e32
OS/Arch (client): linux/amd64
Server version: 1.5.0-dev
Server API version: 1.18
Go version (server): go1.4.1
Git commit (server): 2243e32

Thanks for detailed log output - I will take a look at this presently and try to replicate

I'm on Linux and not using boot2docker. Can you try it on a Linux environment?

Hi - so I've followed the exact same commands using the following docker version output:
Client version: 1.5.0
Client API version: 1.17
Go version (client): go1.4.1
Git commit (client): a8a31ef
OS/Arch (client): linux/amd64
Server version: 1.5.0
Server API version: 1.17
Go version (server): go1.4.1
Git commit (server): a8a31ef

output of uname -a is
Linux node1 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

When I run the final time DOCKER_HOST=localhost:2375 docker run ubuntu echo hello I don't get output but equally I don't get the error message.
This is a known issue we are fixing - if I run the same command attaching stdin:
time DOCKER_HOST=localhost:2375 docker run -i ubuntu echo hello
I get output as expected.
Can you replicate the error and then paste me the output of:

docker ps -a
docker logs powerstrip

Thanks :-)

There you go:
[aanm@localhost ~]$ sudo docker run -d --name powerstrip-slowreq \
>            --expose 80 \
>            clusterhq/powerstrip-slowreq:v0.0.1sudo docker run -d --name powerstrip-slowreq \
>            --expose 80 \
>            clusterhq/powerstrip-slowreq:v0.0.1^C
[aanm@localhost ~]$ sudo docker run -d --name powerstrip-slowreq \
>            --expose 80 \
>            clusterhq/powerstrip-slowreq:v0.0.1
9b7ceb8c51bd0a4dc902e284abaea0cc8c1639c7b893662780b1ced57a712a56
[aanm@localhost ~]$ sudo docker run -d --name powerstrip \
>            -v /var/run/docker.sock:/var/run/docker.sock \
>            -v $PWD/powerstrip-demo/adapters.yml:/etc/powerstrip/adapters.yml \
>            --link powerstrip-slowreq:slowreq \
>            -p 2375:2375 \
>            clusterhq/powerstrip:v0.0.1
3e98bb03283a8bee07be30ea1553571792d304c0416df5fb60884788c4654aef
[aanm@localhost ~]$ sudo docker ps -a
CONTAINER ID        IMAGE                                 COMMAND                CREATED             STATUS              PORTS                    NAMES
3e98bb03283a        clusterhq/powerstrip:v0.0.1           "twistd -noy powerst   6 seconds ago       Up 4 seconds        <IP_ADDRESS>:2375->2375/tcp   powerstrip
9b7ceb8c51bd        clusterhq/powerstrip-slowreq:v0.0.1   "python slowreq.py"    15 seconds ago      Up 13 seconds       80/tcp                   powerstrip-slowreq
[aanm@localhost ~]$ sudo docker logs powerstrip
export DOCKER_HOST=tcp://localhost:2375
2015-02-18 19:04:32+0000 [-] Log opened.
2015-02-18 19:04:32+0000 [-] twistd 14.0.0 (/usr/bin/python 2.7.6) starting up.
2015-02-18 19:04:32+0000 [-] reactor class: twisted.internet.epollreactor.EPollReactor.
2015-02-18 19:04:32+0000 [-] ServerProtocolFactory starting on 2375
2015-02-18 19:04:32+0000 [-] Starting factory <powerstrip.powerstrip.ServerProtocolFactory instance at 0x7f7ea44a1050>
[aanm@localhost ~]$ time sudo docker run ubuntu echo hello
hello

real    0m0.922s
user    0m0.009s
sys     0m0.015s
[aanm@localhost ~]$ time DOCKER_HOST=localhost:2375 docker run ubuntu echo hello
FATA[0001] Error response from daemon:
Could not connect

real    0m1.027s
user    0m0.011s
sys     0m0.003s
[aanm@localhost ~]$ time DOCKER_HOST=localhost:2375 docker run -i ubuntu echo hello
FATA[0001] Error response from daemon:
Could not connect

real    0m1.019s
user    0m0.009s
sys     0m0.004s
[aanm@localhost ~]$ sudo docker ps -a
CONTAINER ID        IMAGE                                 COMMAND                CREATED             STATUS                      PORTS                    NAMES
dbaa7aa6293f        ubuntu:latest                         "echo hello"           19 seconds ago      Exited (0) 18 seconds ago                            compassionate_lumiere
3e98bb03283a        clusterhq/powerstrip:v0.0.1           "twistd -noy powerst   48 seconds ago      Up 46 seconds               <IP_ADDRESS>:2375->2375/tcp   powerstrip
9b7ceb8c51bd        clusterhq/powerstrip-slowreq:v0.0.1   "python slowreq.py"    57 seconds ago      Up 55 seconds               80/tcp                   powerstrip-slowreq
[aanm@localhost ~]$ sudo docker logs powerstrip
export DOCKER_HOST=tcp://localhost:2375
2015-02-18 19:04:32+0000 [-] Log opened.
2015-02-18 19:04:32+0000 [-] twistd 14.0.0 (/usr/bin/python 2.7.6) starting up.
2015-02-18 19:04:32+0000 [-] reactor class: twisted.internet.epollreactor.EPollReactor.
2015-02-18 19:04:32+0000 [-] ServerProtocolFactory starting on 2375
2015-02-18 19:04:32+0000 [-] Starting factory <powerstrip.powerstrip.ServerProtocolFactory instance at 0x7f7ea44a1050>
2015-02-18 19:05:04+0000 [HTTPChannel,0,<IP_ADDRESS>] Starting factory <twisted.web.client._HTTP11ClientFactory instance at 0x7f7ea23e0290>
2015-02-18 19:05:05+0000 [HTTP11ClientProtocol,client] Starting factory <powerstrip.powerstrip.DockerProxyClientFactory instance at 0x7f7ea23f1ef0>
2015-02-18 19:05:05+0000 [-] "<IP_ADDRESS>" - - [18/Feb/2015:19:05:04 +0000] "POST /v1.18/containers/create HTTP/1.1" 501 26 "-" "Docker-Client/1.5.0-dev"
2015-02-18 19:05:05+0000 [-] Stopping factory <powerstrip.powerstrip.DockerProxyClientFactory instance at 0x7f7ea23f1ef0>
2015-02-18 19:05:05+0000 [HTTP11ClientProtocol,client] Stopping factory <twisted.web.client._HTTP11ClientFactory instance at 0x7f7ea23e0290>
2015-02-18 19:05:14+0000 [HTTPChannel,1,<IP_ADDRESS>] Starting factory <twisted.web.client._HTTP11ClientFactory instance at 0x7f7ea198d758>
2015-02-18 19:05:15+0000 [HTTP11ClientProtocol,client] Starting factory <powerstrip.powerstrip.DockerProxyClientFactory instance at 0x7f7ea199c7a0>
2015-02-18 19:05:15+0000 [-] "<IP_ADDRESS>" - - [18/Feb/2015:19:05:14 +0000] "POST /v1.18/containers/create HTTP/1.1" 501 26 "-" "Docker-Client/1.5.0-dev"
2015-02-18 19:05:15+0000 [-] Stopping factory <powerstrip.powerstrip.DockerProxyClientFactory instance at 0x7f7ea199c7a0>
2015-02-18 19:05:15+0000 [HTTP11ClientProtocol,client] Stopping factory <twisted.web.client._HTTP11ClientFactory instance at 0x7f7ea198d758>
[aanm@localhost ~]$ uname -a
Linux localhost.localdomain 3.18.7-200.fc21.x86_64 #1 SMP Wed Feb 11 21:53:17 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

SELinux was the problem.
After installing setroubleshoot I was able to see what the problem was.
sudo grep docker /var/log/audit/audit.log | audit2allow -M mypol
******************** IMPORTANT ***********************
To make this policy package active, execute:

semodule -i mypol.pp

After this it run perfectly
Thanks @lewq and @binocarlos

Thanks @aanm ! (I'm @lukemarsden on github)

Thanks @aanm - I was literally scratching my head at this one good work :-)


support time.sleep properly

In Pyodide doing import time; time.sleep(10) just silently does nothing right now.   See https://github.com/pyodide/pyodide/issues/2354 for their discussion.
I've seen some other python wasm shell somewhere online that just spun the cpu 100% for approx 10 seconds.
On python-wasm here it gives an oserror.
The solution for python-wasm is just to properly implement whatever select system call is required, which should be completely straightforward given our model.

~/python-wasm$ bin/python-wasm
Welcome to Node.js v16.13.0.
Type ".help" for more information.
> Python 3.11.0b3 (main, Jul 14 2022, 22:22:40) [Clang 13.0.1 (git@github.com:ziglang/zig-bootstrap.git 623481199fe17f4311cbdbbf on wasi
Type "help", "copyright", "credits" or "license" for more information.
>>> import time; time.sleep(10)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OSError: [Errno 58] Not supported

See also https://github.com/pyodide/pyodide/issues/97


Styling Fixes

Fixes: #53

Just my opinion, so take it as a grain of salt. But I personally prefer Chivo at smaller font sizes and longer texts. I agree that we can probably do away with Palanquin though.
Another issue that's more blocking is please remember to revise the list of imported fonts, here:
https://github.com/uclaacm/hoth.uclaacm.com/blob/becb3a6b71e45256e32f1ba54aaa605751281ef3/src/components/layout.js#L52-L53

How about we edit the figma to use Chivo for paragraphs or blocks of smaller text?
I'd like the website to reflect the design in the figma, which currently is almost completely Poppins.
After we fix the figma, we can edit this PR to include those changes as well.

How about we edit the figma to use Chivo for paragraphs or blocks of smaller text?
I'd like the website to reflect the design in the figma, which currently is almost completely Poppins.
After we fix the figma, we can edit this PR to include those changes as well.
Edit: I changed some of the fonts in the figma. Comparing this preview with the current live site, I agree that Chivo is nicer for the readability of blocks of text. I think it's a good idea to add the body1 override back into the theme, and we may also want to edit the schedule page to have the workshop descriptions have variant='body1', too.

I agree that the Figma should be consistent with our design. If we want to use Chivo, that's perfectly fine. I'm down for changing body1 to use Chivo by default.


Add stream output for pruning

Resolves #396
Not sure if we need to update this? https://github.com/gabrieldemarmiesse/python-on-whales/issues/499

added function overloading for pruning
added relevant tests to check the streaming logs/output

Will complete the overloading for other pruning, such as for Docker Image, Network, Buildx, etc. when this one gets approved.

Will complete the overloading for other pruning, such as for Docker Image, Network, Buildx, etc. when this one gets approved.

Indeed this seems like a good idea, we'll have a consistent api :)


fix(AoTPlugin): don't override context module deps

Thanks to @clydin for a much cleaner solution!
Fix #2496
Fix #3079

sweet, need to wait or the next NPM build to test this?
regards

@born2net after it is accepted, yes. You can also use master if you want.

tx man appreciate the efforts

LGTM, looks much better!


operator project-quay (3.9.0-nightly.20230609)

Add 3.9.0-nightly.20230609 to community operators

/merge possible

/merge possible


WL-5177 Append @ox.ac.uk for some LTI tools.

Thie needs to be merged after WL-5160 as it depends on that.

@wl-jenkins rebuild


New feature: "Absolute URLs"

In #22, @nateabele pointed out a feature of UI-Router that I'm currently not comparing: whether a nested route can have an absolute URL.

Done


Add beep package for rt-thread.

添加了针对有源或无源蜂鸣器的鸣叫控制软件包。

外层的 peripherals/Kconfig 也要记得修改下

好的，重写一下，谢谢了!还有，pull requests怎么close不掉？发自手机-------- 原始邮件 --------主题：Re: [RT-Thread/packages] Add beep package for rt-thread. (#584)发件人：朱天龙 收件人：RT-Thread/packages 抄送：Sunwancn ,Author
@armink commented on this pull request.
In peripherals/beep/Kconfig:

@@ -0,0 +1,82 @@

+menuconfig PKG_USING_BEEP

bool "beep: Buzzer beep package on rt-thread."

如果实在想不到更好的，就这样也行
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/RT-Thread/packages/pull/584#discussion_r394094328",
"url": "https://github.com/RT-Thread/packages/pull/584#discussion_r394094328",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

底部有个 close 按钮，另外，简单写个一句话的简介就行，想不好就先算了


New version: ApproxFunFourier v0.3.0

Registering package: ApproxFunFourier
Repository: https://github.com/JuliaApproximation/ApproxFunFourier.jl
Created by: @jishnub
Version: v0.3.0
Commit: 1cc65c453bc6332a34a685897b4b0e18588f0c2c
Reviewed by: @jishnub
Reference: https://github.com/JuliaApproximation/ApproxFunFourier.jl/commit/1cc65c453bc6332a34a685897b4b0e18588f0c2c#commitcomment-81675431
Description: Support for Fourier-based spaces in ApproxFun

don't merge


Change line breaks to unix style ("\n" instead of "\r\n")

Change line breaks to unix style for code output ("\n" instead of "\r\n") as it makes for easier comparison across files

Code output already does this? If it doesn't output unix newlines then that's probably a bug, somehow.

Any confirmation that this actually exists?

I compared them in WinMerge and it says that this is the case.

Are you sure? I'm checking my output and the files are definitely using unix newlines. Are the files you're comparing against using Windows newlines?


GeoJson is very slow with MultiPolygon

Summary
When trying to use a GeoJson component even with just 4 MultiPolygon, the maps go frozen. The JS and UI frame rate goes to 0 for a good minute or so before coming back normal. Is there any workaround we can do to achieve a better performance?
I am already using trackViewChanges as false but that has no impact on the rendering performance.
Reproducible sample code
<Geojson
          key={'territories'}
          tracksViewChanges={false}
          geojson={props.territories}
        />

Steps to reproduce

Add GeoJson to your MapView
Try to render 3-4 MultiPolygon at US state level
Map freezes and won't respond

Expected result
The performance shouldn't be impacted
Actual result
The maps freeze and won't respond for a minute or so, once the polygons are rendered then the maps performs smoothly.
React Native Maps Version
1.7.1
What platforms are you seeing the problem on?
Android, iOS (Google Maps)
React Native Version
0.69.0
What version of Expo are you using?
Not using Expo
Device(s)
iPhone 13, Galaxy Tab A8
Additional information
No response

Still relevant


fix(pkg/chartutil): include values.schema.json in packaged chart

When playing around with new Helm 3 features, we noticed that values.yaml is not validated when running helm install, even though the docs say it should be:

Validation occurs when any of the following commands are invoked:

helm install
helm upgrade
helm lint
helm template

The reason is that values.schema.json is not included in the tarball created by helm package, so helm lint cannot lint the tarball properly, even if it can lint the chart directory:
$ helm lint my-chart            # Finds errors in values.yaml
$ helm package my-chart
$ helm lint my-chart-1.0.0.tgz  # Does not find errors in values.yaml

Good catch. Thank you for the PR! Would you mind writing some unit tests under save_test.go to ensure this file is indeed packaged? Thanks!

We would actually mind a little bit. Unless we have missed it, there seems to be no unit test for any of the other required files that are packaged (e.g., Chart.yaml), it would require some effort to implement it. Since we are new to the project, it would be a lot of trial-and error before we could get the tests in place. Maybe it's better to create a new PR after this one, that implements the entire suite of tests needed for the files?

It shouldn't be too hard to add a Schema object here and then check if .Schema hasn't changed, similar to how we check the .Files object here. That should be enough to cover the code introduced in this change.

A test case for saving invalid JSON would also help capture the validation check.

It shouldn't be too hard to add a Schema object here and then check if .Schema hasn't changed after it's been loaded, similar to how we check the .Files object. That should be enough to cover the code introduced in this change.

I absolutely agree.

A test case for saving invalid JSON would also help capture the validation check.
https://github.com/helm/helm/pull/6519/files#diff-9ea0c476e7eb107c6b0f198af1a49caaR163

I'm not entirely sure about this, because as far as we can tell, an error returned from writeTarContents doesn't "propagate" to the user. Ergo, if I run helm package and something goes wrong such that any of the return err statements in writeTarContents is reached, then no tarball is created, but helm package still prints a success message:
$ helm package my-chart
Successfully packaged chart and saved it to: /[...]/my-chart-1.0.0.tgz
$ ls my-chart-1.0.0.tgz
ls: cannot access 'my-chart-1.0.0.tgz': No such file or directory

But that seems to us like a separate issue.
(We may not have time to work on this during the weekend, but hopefully on Monday.)

I've added the requested test cases now, @bacongobbler. There was a particular confusing aspect of the code – namely, how the name err was used – that took me several hours to figure out, but I think that's gonna be a separate PR.

Hi again, @bacongobbler. I rebased and force-pushed my commits because conflicts had arisen due to #5498.

Would you mind rebasing this PR? Once that's done I can merge this. Thanks.


bug: extra parameters in url are lost when data comes

Bug Definition
I just clicked on the link while reviewing an issue. There was an id parameter in this link and the url was updated when the data came from the api. id value removed from url.
-- Please add discord contact information
** discord username: @ss.ibrahimbas#4990 **
## Bug environment
Describe the environment produces the bug. For example:
Both:

rc.afetharita.com
afetharita.com

Describe how you are producing the bug step by step

Go to 'this link'
look the url
&id field is going

Expected Behaviour
id field is should stay in the url
Screen shots
If possible, add screenshots to describe your bug.
Desktop Information

Operating System: [Windows 11]
Browser [chrome]
Version [for example 22]

Additional Context
Not have additional context

The problem has been resolved. Even if the page is refreshed, the id is displayed.thanks

Out of curiosity, where was the problem? I was looking at the issues and this thing which would interest me @buraktuzlutas

When you refresh the page from the link https://afetharita.com/en?lng=36.570053100585945&lat=36.936358468543396&zoom=12&id=756628, the id information was corrected, while https://rc.afetharita.com/, the id information disappeared when the page was refreshed. @cemiluzunhasan

I was asking about the implementation but np anyway if it has been solved. Thanks @buraktuzlutas

I see the problem persists in rc and production. It hasn't made it to rc yet or could it be an overlooked point? @buraktuzlutas

Hi.
Issue #760 is vise versa of this issue so which path should we follow on this. should id stay on URL or not

the id stay's in URL until you move the map or refresh the page as expected. but if you want to copy and paste URL to share the marker the id vanishes from URL

expected behaviour. closd this issue.

me and @cemiluzunhasan are right now in this issue pr wip

Solved and created the related PR


RAD Studio 11.1.5

http://altd.embarcadero.com/download/radstudio/11.0/RADStudio_11_1_5_esd_10253.iso
when?

Well I Just give up on Alcinoe lib, non-commercial libraries rarely have a future unless their backed by big companies, It's a same such a good project is dying, I should been better to pay for it 350 ou 400 euros, and 200 for renew, that way I would have neved died.

if you respect your users, then explain whether it is worth waiting for the library update, and if so, then at least approximately the time frame? and it'll be a year soon...


[Minor]Re-export array::builder::make_builder to make it available for downstream

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Re-export array::builder::make_builder with pub use.
Are there any user-facing changes?

Codecov Report

Merging #1235 (d54186d) into master (66e029e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1235   +/-   ##
=======================================
  Coverage   82.70%   82.70%
=======================================
  Files         175      175
  Lines       51712    51712
=======================================
  Hits        42770    42770
  Misses       8942     8942

Impacted Files
Coverage Δ

arrow/src/array/mod.rs
100.00% <ø> (ø)

parquet_derive/src/parquet_field.rs
65.75% <0.00%> (-0.46%)
:arrow_down:

arrow/src/datatypes/datatype.rs
66.38% <0.00%> (-0.43%)
:arrow_down:

parquet/src/encodings/encoding.rs
93.71% <0.00%> (+0.19%)
:arrow_up:

arrow/src/array/transform/mod.rs
85.69% <0.00%> (+0.26%)
:arrow_up:

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 66e029e...d54186d. Read the comment docs.


tests in docker

fixes #31
figure out that the page crashes were due to:
https://code.google.com/p/chromium/issues/detail?id=519952
moved the logic to run these test in docker containers right into the
code so we can run exactly what runs in travis by simply doing
TEST_MODE=docker gulp test instead of having to use the scripts under
test/scripts/ manually to set things up.
this will also be the building blocks for running docker containers to
verify that npm installation of juttle-engine works as expected before
releasing

@juttle/developers I figured out the page crashes and also decided to make it easier for everyone to run the tests the same we do in travis using the docker images. Once this is in I can work on figuring out how to:

record screenshots or videos of the tests as they run (the selenium ones) and then artifact them somewhere for when failures occur in travis only
start using the docker containers to easily run npm tests to verify npm local and global installs work as expected before we release the code into the wild

Merging on green as this really fixes the issue with the chrome crashes that are plaguing our juttle-engine branch runs and definitely affecting others productivity. Any comments will be followed up with another PR to correct anything found.


Triton_server

Hello. I'm trying to deploy my trained streaming model, which I exported to the ONNX format, on TRTorch, and I'm encountering the following error.

The error should be a bit above what you copy pasted.

Have you tried our official recipe first? https://github.com/k2-fsa/sherpa/blob/master/triton/scripts/build_librispeech_pruned_transducer_stateless3_streaming.sh and https://github.com/k2-fsa/sherpa/blob/master/triton/scripts/build_wenetspeech_pruned_transducer_stateless5_streaming.sh. We currently support reworked conformer streaming ASR for en and zh.

thank you for answering, i haved tried for zipformer_streaming. do you support this?

Not yet. We will try to support this in a month. Or you're welcome to contribute a script or a model_repo to support it e.g. build_librispeech_zipformer2_streaming.sh

thank you. sorry i didnt have work with triton.


add St Dominc Savio High School

adding St Dominic Savio High School located in Austin Texas
https://www.saviochs.org/

@toli-belo First stage of verification passed, official domain is saviochs.org as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.


initWalletServices should not use a querier

https://github.com/penumbra-zone/web/blob/d705c7019a5cbac17804d2233d1faac547121a1d/packages/services/src/index.ts#L65-L66

closing as this was refactored when we decoupled service / rpc init


[BUG]: Can not put shortcut in shelf anymore

I usually put the gt-tools feature as a shortcut in maya shelf, but now it does not work anymore.

Hey @thegreenpuppet,
Do you get any errors?
Can you list the steps you went through so I can try to replicate the issue?
I opened the drop-down menu here, then "Ctrl + Shift + RMB" on a tool and it was added to the current shelf without any issues.
If you're refering to copying and pasting the content of the script into a shelf button. That won't work anymore because the tools are now refering code that exists inside other scripts.
For example, multiple tools will make use of utilities, so they all import form utilities (instead of repeating code)
If you don't want to install the script package, you can use the "Run-Only" option.
Installing will just create a copy in your "Documents/maya" folder, so it would be easier.

In case your goal is to have shelf buttons, but no menu. You'll be able to do this in future versions.
I'm planning to include preferences, so you can tweak the package behaviour. For example, not creating a menu even when installed.

I think I managed to replicate the issue.
If a call function for a tool is added to the shelf and then maya is restarted, the partial function address changes.
I fixed it in the development branch, I'll release an update with a complete fix for it soon 👍

I'll close this issue. Feel free to re-open or open a new one in case what I mention didn't clarify the issue 👍


Gnome 3.20

With Gnome 3.20 the function panel_applet_set_background_widget no longer exists, so the applet can't draw itself on the panel.  I have been searching for an alternative, but I can't find one so far.

Similar issue with libmatepanelapplet-4.0


Transforming timestamp to date should produce date

The output type of transforming a timestamp to a date Transforms.day(Types.TimestampType.withZone() is an integer, but should be a date. That way, it will be formatted as a date in metadata tables.
When this is updated, we need to validate backward compatibility with existing tables.

Should day also not support the date type, since that would be an identity transform?

You're probably right, although there shouldn't be a difference between the two in practice, once strict projection for dates is added.

What are suggested ways to validate backward compatibility?

Hi @rdblue, I am new to iceberg, really appreciate your guidance in advance!
Regarding "The output type of transforming a timestamp to a date Transforms.day(Types.TimestampType.withZone() is an integer, but should be a date", when you say "date", do you refer to "java.util.Date"?
Do you expect Transforms.day(Types.TimestampType.withZone()) returns Transform<T, Date> instead of Transform<T, Integer> ?

Hi @rdblue please correct me if I am wrong:
I am not sure if Transforms.day() is the function to transfer timestamps to date, it is to produce Dates.DAY or Timestamp.DAY (either is Transform) from Types.DateType or Types.TimestampType. By this issue, are you proposing a new method in Transforms which returns Transform<T, java.util.Date> from Types.DateType or Types.TimestampType?

Use java.time.LocalDate. The older java.util.Date actually represents an instant.

@waterlx, the day transform reports that its return type is IntegerType.get(), but it should be DateType.get(). Both are stored as integers but the transform actually produces the internal value that represents a date: the number of days from the unix epoch.
Changing the return type to date should be safe and would cause engines that support the metadata tables to format the values correctly as dates instead of as integers.
@timmylicheng, the compatibility checks just need to verify that older tables that are partitioned by day can still be read. It's just a matter of writing a table with the current master, making this change and reading with the new library. We don't expect any exceptions while reading or filtering after the update.

@rdblue if Im not missing, in this case
org.apache.iceberg.transforms.Timestamps will implement Transform<Long, Date> and org.apache.iceberg.transforms.Dates will implement Transform<Integer, Date>.
and internally these classes will use Date object for various transformation like apply , toHumanString.
@waterlx are you working on this issue ?

@manishmalhotrawork, only the day transform should return a date. Years, months, and hours should continue returning ordinals like before.

@rdblue

@manishmalhotrawork, only the day transform should return a date. Years, months, and hours should continue returning ordinals like before.

so you mean that we are supposed to keep org.apache.iceberg.transforms.Timestamps as it is (as Transform<Long, Integer>) and keep org.apache.iceberg.transforms.Dates as it is (as Transform<Integer, Integer>, but only change the output of Transforms.day() to Transform<T, Date>? Do I get it right?
@manishmalhotrawork yes, I am working on this issue. But please feel free to go ahead to share your thoughts or upload patches, I am new to iceberg

Sorry for the confusion. I'm talking about the Iceberg date type, Types.DateType.get(). The transform implementation is still going to return a Java Integer because that's how dates are represented in Iceberg metadata: the number of days from the Unix epoch.
This change would primarily just update getResultType and return DateType.get() when the granularity is ChronoUnit.DAYS. That will cause the partition tuple's field type to be a date, which should also cause the metadata table to display formatted dates instead of the day ordinal in Spark.

@rdblue

This change would primarily just update getResultType and return DateType.get() when the granularity is ChronoUnit.DAYS.

this is bit more clear now. thanks  !
so this will change ( if granularity is Days)

Dates.getResultType

public Type getResultType(Type sourceType) {
    return Types.IntegerType.get();
  }

and what about Timestamps.getResultType , does it also needs to return Types.DateType.get() , as that can also be needed to print datetime in metadata table. ?

Yes, I think both should return DateType

Thanks for the clarification, Ryan! I am drafting the patch.

@rdblue thanks for the answer.
Just saw messages, before that I also drafted the patch, waiting for internal approval.
@waterlx I can push, and then you can also review? Or otherwise please let me know.

@rdblue quick questions.

while validating my changes,  didn't see that transfor.getResultType is being used apart from PartitionSpec.partitionType().
can you point me to any other test-case or code path, where its being used can be verified.

( though Im adding test-cases to validate Days.getResultType() and Timestamps.getResultType())

If we are returning DateType.get for Days why not for Month/Year as well. As for those types as well it will return Integer/day ordinal?

That will cause the partition tuple's field type to be a date, which should also cause the metadata table to display formatted dates instead of the day ordinal in Spark.

I believe metadata table referenced here is related to #252? Anything specific I need to test/validate if this change impacts the metadata tables?

can you point me to any other test-case or code path, where [getResultType] is being used can be verified.

There might not be one. Thanks for adding tests!

If we are returning DateType.get for Days why not for Month/Year as well

The values for those aren't stored as dates. For example, 1990 is stored as 20.

Anything specific I need to test/validate if this change impacts the metadata tables?

Existing tests should cover it. The change should automatically update the Spark representation as well. Just fix any test failures, if there are any.

@rdblue , wondering if this issue is resolved by the #424 ?

Yep. Thank you!

Hi @rdblue , I am not sure if the table of "partition transforms" on the doc needs to update to reflect this change. The row of "day" of the table. Would you please advice? Thanks!

@waterlx, I think you're right. We should update that line. Do you want to open a PR?

Hi @rdblue , would you please review PR #447 at your most convenience?


Lambda controller should not attempt to update a Function that is in a pending state

Describe the bug
Currently, the lambda controller e2e tests are failing for Function resources. The reason is that controller tries update a Function that just got created.
logs
E           kubernetes.client.exceptions.ApiException: (409)
E           Reason: Conflict
E           HTTP response headers: HTTPHeaderDict({'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'Date': 'Tue, 14 Dec 2021 15:50:12 GMT', 'Content-Length': '400'})
E           HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Operation cannot be fulfilled on functions.lambda.services.k8s.aws \"lambda-function-2iq6fsrm\": the object has been modified; please apply your changes to the latest version and try again","reason":"Conflict","details":{"name":"lambda-function-2iq6fsrm","group":"lambda.services.k8s.aws","kind":"functions"},"code":409}

/usr/local/lib/python3.8/site-packages/kubernetes/client/rest.py:233: ApiException

/assign

Perhaps some fields on the Function resource need late_initialize: {} in the generator.yaml config file?

Perhaps some fields on the Function resource need late_initialize: {} in the generator.yaml config file?

What's weird is that tests used to pass before. Trying to fix with late_initializers and some custom code

Fixed in aws-controllers-k8s/lambda-controller#15


Sc-lstm training is not working

Dear,
I tried to train the sc-lstm module and it didn't work, please find the log below.
What could be the error?
mrc@marco-instance-0:~/ConvLab/convlab/modules/nlg/multiwoz/sc_lstm$ PYTHONPATH=../../../../.. python3 run_woz.py  --mode=train --model_path=sclstm.pt --n_layer=1 --lr=0.005 > sclstm.log
Processing data...
# of turns
Train: 26414
Valid: 3171
Test: 3154
# of batches: Train 103 Valid 12 Test 12
Using deep version with 1 layer
Start training
Epoch 0 (n_layer 1)
Traceback (most recent call last):
  File "run_woz.py", line 382, in <module>
    train(config, args)
  File "run_woz.py", line 226, in train
    train_epoch(config, dataset, model)
  File "run_woz.py", line 144, in train_epoch
    _ = model(input_var, dataset, feats_var)
  File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 532, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/mrc/ConvLab/convlab/modules/nlg/multiwoz/sc_lstm/model/lm_deep.py", line 50, in forward
    gen=gen, sample_size=sample_size)
  File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 532, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/mrc/ConvLab/convlab/modules/nlg/multiwoz/sc_lstm/model/layers/decoder_deep.py", line 155, in forward
    output, last_hidden, last_cell, last_dt = self.rnn_step(vocab_t, last_hidden, last_cell, last_dt, gen=gen)
  File "/home/mrc/ConvLab/convlab/modules/nlg/multiwoz/sc_lstm/model/layers/decoder_deep.py", line 111, in rnn_step
    _hidden, _cell, _dt = self._step(input_t, last_hidden, last_cell[i], last_dt[i], i)
  File "/home/mrc/ConvLab/convlab/modules/nlg/multiwoz/sc_lstm/model/layers/decoder_deep.py", line 69, in _step
    w2h = self.w2h[layer_idx](input_t) # (batch_size, hidden_size*4)
  File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 532, in __call__
    result = self.forward(*input, **kwargs)
  File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/linear.py", line 87, in forward
    return F.linear(input, self.weight, self.bias)
  File "/opt/conda/lib/python3.7/site-packages/torch/nn/functional.py", line 1370, in linear
    ret = torch.addmm(bias, input, weight.t())
RuntimeError: Expected object of device type cuda but got device type cpu for argument #2 'mat1' in call to _th_addmm

@mrcmoresi We only support SC-LSTM training with CPU for now. You can refer to the source code for training with GPU. We will support it in the coming Convlab-2. Sorry for the inconvenience.


Cycle through popular photos

There should be more of them (copied from my spreadsheet) and they should rotate day-to-day, to keep showing new content on the site.

Closed by https://github.com/oldnyc/oldnyc.github.io/commit/8128ed343de808330c0aaa54ffbcebed10c4f648


Break long exports into multiple lines.

Ref #19.
Currently this PR (https://github.com/jlongster/prettier/pull/104/commits/244c810bd0ef7a41fb76624fb9352652fcfae32c) is based on #101, so you might have to merge that in first, otherwise there has to be a lot of rebasing :|

@demoneaux Any chance you could convert this to use group instead?

Superseded by https://github.com/jlongster/prettier/pull/156, I went ahead and made those changes so I can get it in. Thanks for starting the work!

Thanks for providing advice and accepting my fixes! Looking forward to contributing more to this project.


add changes to test

Pipelines as Code CIchanges/news-demo has failed.PipelineRun has no taskruns

Pipelines as Code CIchanges/news-demo has failed.PipelineRun has no taskruns

Pipelines as Code CIchangesoooooooiiiii/news-demo has failed.PipelineRun has no taskruns


'Connect to Data Lake Storage Gen1… ' is not localized

Storage Explorer Version: 1.10.1
Build: 20190926.4
Branch: master
Platform/OS: Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
Architecture: ia32/x64
Language: Chinese (zh-TW) / Chinese (zh-CN)
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer using the command 'StorageExplorer.exe --lang=zh-CN'.
Right click 'Data Lake Storage Gen1 (Preview)' node.
Check its context menu.

Expect Experience:
'Connect to Data Lake Storage Gen1… ' is localized.
Actual Experience:
'Connect to Data Lake Storage Gen1… ' is not localized.

More Info:
This issue also reproduces for one Cosmos DB account.

Not occurs in localizable  resources for now.
https://devdiv.visualstudio.com/DevDiv/_git/CloudExplorer?path=%2Fsrc%2FCloudHub%2Fts%2FProviders%2FAzure%2FConfig%2FAzureDocumentDBAccountResourceTypeConfig.ts&version=GBmaster
                displayName: {
                    value: "Connect to Cosmos DB..." // Localize
                },
                icon: AzureConstants.imagePaths.DocumentDBAccountsIcon,
                themeSrc: AzureConstants.imageThemeSrc.DocumentDBAccountsIcon,
                isDefault: false,
                visible: {
                    value: Utilities.isRunningOnElectron()
                },
                namespace: "Azure.Actions.DocumentDB.connectAccount"
            },
            {
                displayName: {
                    value: "Connect to Cosmos DB Emulator..." // Localize
                },
                icon: AzureConstants.imagePaths.DocumentDBAccountsIcon,
                themeSrc: AzureConstants.imageThemeSrc.DocumentDBAccountsIcon,
                isDefault: false,
                visible: {
                    value: Utilities.isRunningOnElectron()
                },


Key Binding Conflict with Select Word

There is a keybinding conflict with Ctrl-Shift-W with word selection in Atom's core atom-text-editor selector.
I think the key bindings rbox uses are way too broad:
'atom-text-editor:not([mini])':
  'ctrl-shift-W': 'hydrogen:add-watch'
'.platform-darwin, .atom-workspace':
  'ctrl-shift-W': 'hydrogen:add-watch'
'.platform-darwin, .atom-text-editor':
  'ctrl-shift-W': 'hydrogen:add-watch'

So broad in fact that custom keybindings, even when setting unset!, do not resolve the conflict.
'atom-text-editor:not([mini])':
  'ctrl-shift-W': 'unset!'

'.platform-darwin, atom-text-editor':
  'ctrl-shift-W': 'unset!'

Why? Because if these are unset!, to remove rbox's bindings, they also actually unset the core Ctrl-Shift-W keybinding. I tried multiple combinations and it wouldn't work; either all are unset and nothing works, or leaving the atom-text-editor selector set activate rbox's keybinding, overriding the core atom-text-editor selector. Maybe I am mistaken, so any suggestions?
The only option was uninstalling/deleting rbox, and restarting Atom. Core key binding worked. So for now, this will be the case for me. Unless there is a different way to use the custom keybinding and I am mistaken somewhere.

Now use ctrl-alt-w,
https://github.com/saeidamiri1/rbox/wiki/Use-under-macOS.