Fixed Dockerfile syntax highlighting

PR Summary
The f in Dockerfile is not uppercase, this breaks syntax highlighting for vscode on my client

PR Context
DockerFile breaks syntax highlighting as mentioned and described above.

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[x] Add [feature] to your commit messages if the change is significant or affects feature tests

This affects our release build.  I'll need to clone the branch into our release build system and verify this does not cause an issue.  It will take some time to validate.  Please be patient

Not a problem.


enterprise/compliance needs?

Is this issue related to an issue?.
Apologies if I've missed it, but there doesn't seem to be any support for a range of features often needed in high governance environments.
There is 'Enterprise features
Custom authentication, ubiquitous access control, history, etc.' in the roadmap, but it isn't clear what the timeframe for that is.
The specific features I'm interested in are
a) those that prevent the (ab)use of a single compromised browser session (or laptop) from affecting a change to production, or exfiltrating a secret. For instance mandatory peer review before application, and before any dry run which might read-out secret material.
b) dealing with a fleet of similar infrastructure - we have many instances of a single basic infrastructure with some minor variance between them. This is currently managed in terraform by parameterising a root module with a unique state file + parameters that encompass the variation.  Its also not clear whether this is (or isn't) on the roadmap today - it seems to be a different dimension of scale to me - one of managing complexity at a higher level than the component model; but perhaps components are the intended solution here?
Describe the outcome you'd like from us
For the governance question, just knowing if it is short-term, medium, or 'eventually' would be great!
For the other one, its more of a discussion, but discussions aren't turned on in Github, and discord isn't indexed, so no-one can learn from the discussion, so I guess we'll see if you'll take it here :).
Describe alternatives you've considered
Not having the feature isn't viable unfortunately. Maybe in a world with no threat actors.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Additional context
No response

Hi @rbtcollins
Thanks for opening the issue here - my apologies it has taken us a while to get back to you. We have already started the work to have mandatory peer reviews - https://www.systeminit.com/blog/opportunity-rebac
The work for #2 is underway as well - https://www.systeminit.com/blog/opportunity-management-functions
We expect these pieces of work to be available at the end of October - the blog posts note the specific details of what they will enable
Hope this helps
Paul

Hi @rbtcollins
I'd like to follow up here to point out that our approval workflows are now live - https://www.systeminit.com/blog/announcing-approval-workflows
We are also very close to being able to deliver the management functions work - more on that next week (after the thanksgiving break!)
Paul

Hi folks, I am delighted to say we have closed these features out and we have turned them on for everyone!
https://docs.systeminit.com/reference/asset/function#management-functions
We also switched on an audit-logs page on the application for a user workspace


Only PRs (not issues) arrive to IRC.

I don't know what's needed to tweak this, but I hope it should be straight-forward.
I don't think I have access to do it, maybe @jdm or @larsbergstrom can?

I'm not really sure how that happens, tbh. The settings are nearly identical for the IRC integration between this one and servo/servo (which does have the issues notifications), except that the Servo one only tracks changes to the master branch. Maybe those notifications are coming in via another service (e.g., highfive)? Hard to know, as the ghservo irc nic doesn't have a password, so it could be anything that's hooked up to the servo/servo webhooks.

I've noticed that the IRC webhook doesn't appear to work properly for repositories that were transfered from some user to the servo organization. This is the same problem that happens for highfive and webrender, among others.

Closing issues seems to work now, I think opening them too.


TouchableOpacity in Custom Marker doesn't work on Android

I created a custom marker view with a button in it, it works well on iOS, but it's no touch event triggers on Android.

@shieer android will have limitations here. Android renders the markers and the callout as bitmaps directly, and they don't have interactivity.
The best you can really do here is capture the onPress event and use the position property of the event to calculate where the user pressed.
Unfortunate, I know... but currently there are no maps implementations on android that don't implement markers and callouts as bitmaps.
It might be possible though to implement callouts ourselves and not use the gmaps implementation. I'd love some help for this, but if there is enough demand I might take a crack at it myself.

@lelandrichardson  Thanks for your answer, that helps.

MapView.Marker onCalloutPress works with the native built-in Android map callout
   <MapView.Marker key={m.id} coordinate={m.coordinate} title={m.title} description={m.description}
      onCalloutPress={() => {this._onAnnotationPress(m.id)}}>
    </MapView.Marker>

Wouldn't it be possible to support that for custom callouts too? So that at least we can have click events on the whole callout?

@gunters63 yes, we could potentially have click events on the entire rendered view, just not on specific components, and handling <Touchable*> properly is probably never going to be possible (without additional support from the maps library itself).
The onMarkerPress event should work for you here. That works right now on android IIRC.

This had the equivalent effect on user interaction through android and ios. You just need to put the onPress on the <Map.Marker>  and put whatever you want that marker to look like inside of the Marker.
  return Platform.OS === 'ios' ? (
        <MapView.Marker
          key={ `${location.id}${Date.now()}` }
          coordinate={{latitude, longitude }}>
            <View >
            <TouchableOpacity
            style={ activeId === locationId ? Styles.markerPressed : Styles.marker }
            >
              <SearchMapCallout
                setChosen={this.props.setChosen}
                navigate={navigate}
                location={location}
                locations={this.props.locations}
                onPress={this.calloutPress} />
              </TouchableOpacity>
            </View>
        </MapView.Marker>
    ) :

    <MapView.Marker
      onPress={this.calloutPress.bind(this, location)}
      style={{zIndex: 10}}
      // onPress={() => this.forceUpdate()}
      key={ `${location.id}${Date.now()}` }
      coordinate={{latitude, longitude }}>
        <View style={[activeId === locationId ? Styles.markerPressed : Styles.marker]}>
          <Text style={Styles.price}>${location.price_with_extent}</Text>
        </View>
      </MapView.Marker>
  }

Hope that helps!

@shieer The MapView component contains a property called onMarkerPress. This property works on both platforms.
Ex: <MapView onMarkerPress={() => function } />

onMarkerPress is wokring fine for me

@SHIEER The MapView component contains a property called onMarkerPress. This property works on both platforms.
Ex: <MapView onMarkerPress={() => function } />

This solves my issue. Thanks!


getItem($key) - shouldn't you be trimming whitespace from the key as well as forward slashes?

eg.: trim($key, '/ ') Line: 107
Because you can't trust the developer to do that every time when the library is expecting a certain type of string.
$key = " some/key"; would be considered an malformed string going through that method, though it's not always easily caught.

I agree with spaces but not forward slashes.

@design1online the reason I said forward slashes because of how Stash deals with forward slashes and automatically grouping arrays. There's really no reason for a cache key to start or end with a forward slash as well.
I've never see someone write keys like this:

user/1/
/user/1/
/user/1

There's no reason to write cache keys in stash like that at all. If you can give me a use case i'd be glad for you to give me a use case where it's appropriate to write any cache keys like that especially when the next line is an explode:
$key = explode('/', $keyString);

I use keys like that because I create keys based on the classname.

@design1online I don't think people should be using class names as cache keys, but to each their own


[Android, LogLevel] Ability to set log level printings in Android

The amount of prints produced by otaliastudios transcoder is enormous and makes it difficulty to find other prints, which are not produced by that library.
The suggested change allows to control the log level of that library.

Is this function updated in plug-in?

Yes, you can use it

Yes, you can use it

default level is 3?
How many steps do you have and the greater the number the more verbose is??


Disable checker in Java 11 builds

This works around kelloggm/checkerframework-gradle-plugin#117 in which the checker framework is misconfigured due to a confluence of factors, most notably the JVM that Gradle is running under being version 8 and the source level of the project being Java 8. Other factors and fix TBD but since checker is just a source level analysis we do not need to run it redundantly in Java 11 builds.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @tysonjh
CC: @jayendra13

Wrong branch


feat(sms.compose.receivers): if invalid receivers, display error message

Ref : UXCT-160

ping @Steffy29

Hello @Steffy29,
Your pull request is now closed due to inactivity.
Feel free to re-open it if you have any update.
Anna Bot for OVH UX <3

227 commits, I think we have a history issue ^^
Available to help you if needed, but we should clean this before merging it :)

@jleveugle  code rebase is done.

No pluralization necessary, only one receiver allowed

CDS Report telecom-dashboard#3565.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report freefax#3565.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report telecom-task#3565.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report pci#3565.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

For the update of lodash version(4.17.11), I looked for the SMS directory code and there isn't "import _ from 'lodash'" in the code.


[pooling layer] global pooling layer doesn't need kernel_size

pool10 = mx.symbol.Pooling(name='pool10', data=relu_conv10 , global_pool=True, pool_type='avg')

Traceback (most recent call last):
  File "convert_model.py", line 116, in <module>
    main()
  File "convert_model.py", line 37, in main
    prob, input_dim = proto2symbol(args.caffe_prototxt)
  File "/home/lsy/mxnet-1/tools/caffe_converter/convert_symbol.py", line 188, in proto2symbol
    exec(sym)
  File "<string>", line 67, in <module>
  File "/home/lsy/anaconda2/lib/python2.7/site-packages/mxnet-0.7.0-py2.7.egg/mxnet/symbol.py", line 1062, in creator
    ctypes.byref(sym_handle)))
  File "/home/lsy/anaconda2/lib/python2.7/site-packages/mxnet-0.7.0-py2.7.egg/mxnet/base.py", line 77, in check_call
    raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: Required parameter kernel of Shape(tuple) is not presented

 DMLC_DECLARE_PARAMETER(PoolingParam) {
    DMLC_DECLARE_FIELD(global_pool).set_default(false)
    .describe("Ignore kernel size, do global pooling based on current input feature map. "
              "This is useful for input with different shape");

    DMLC_DECLARE_FIELD(kernel)
    .set_expect_ndim(2).enforce_nonzero()
    .describe("pooling kernel size: (y, x)");

    DMLC_DECLARE_FIELD(pool_type)
    .add_enum("max", pool_enum::kMaxPooling)
    .add_enum("avg", pool_enum::kAvgPooling)
    .add_enum("sum", pool_enum::kSumPooling)
    .describe("Pooling type to be applied.");

    int stride_shape[] = {1, 1};
    DMLC_DECLARE_FIELD(stride).set_default(TShape(stride_shape, stride_shape + 2))
    .set_expect_ndim(2).enforce_nonzero()
    .describe("stride: for pooling (y, x)");

    int pad_shape[] = {0, 0};
    DMLC_DECLARE_FIELD(pad).set_default(TShape(pad_shape, pad_shape + 2))
    .set_expect_ndim(2)
    .describe("pad for pooling: (y, x)");
  }
};

    .set_expect_ndim(2).enforce_nonzero()

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


tonemap.glsl: Ensure color parameter of tonemap_reinhard() is positive

PR opened in response to https://github.com/godotengine/godot/issues/41901
The problem here is that there are indeed negative values in the color parameter of tonemap_reinhard()
The division in the forumla causes the negative signs to cancel out so the clamp() in the return statement doesn't fix this.
The changes here add checks that ensure the color values are positive before applying the formula.
The test scene now looks like this:

This issue also happens in master. I'll make a separate PR there after this one reaches approval and is merged.

Thanks!

Thanks for getting this merged ! :)


Responsibility Section Parser

Add in a responsibility section parser that utilizes the section parsing logic for DoD section parsing (https://github.com/dod-advana/gamechanger-data/tree/section-parse-dod) and generates an xlsx spreadsheet containing the input for the Responsibility explorer model.
To Run/Test:

A CLI tool has been added  in gamechanger-data/common/document_parser/lib/responsibility_parse/cli/responsibility_parser_cli.py and can be used to parse a directory of JSONs (that have been parsed via the DoD section parsing code) via:

python3 common/document_parser/lib/responsibility_parse/cli/responsibility_parser_cli.py -i "/path/to/gc_dod_jsons" -s "/directory/to/save/responsibility_results.xlsx"

Unit tests can be found/run via gamechanger-data/common/document_parser/lib/responsibility_parse/tests/unit/test_parse_responsibilities.py

@mishoe Great use of comments throughout the code!
I pushed a commit with some minor fixes (typos, unused imports, etc).
I got an error when running the unit tests:

Hey Olive, I added openpyxl as a requirement and made a fix here https://github.com/dod-advana/gamechanger-data/pull/252/commits/371ec092ff1df275f61986aaa05b8e6916a5fbb3 which should have everything working now. As far as I can tell, using openpyxl should inherently support xls and xlsx files without issue - let me know if your run into anything on your side


To display the Segments correctly, we need a terminal capable of displaying 256 colors

I had some Issues getting the right colors on my linux machine. After a while I figured out, that I was using TERM=xterm, wich can only display 8 colors. After changing that to xterm-256colors, the template worked as expected.
I am not 100% sure about this fix, as you can have xterm-256colors not installed because you use some other terminal editor (UXTerm, etc.). But it should do it in most cases. Unfortunately I didn't find a reliable way of determine whether xterm is installed or not..
What do you think?

Uhm. Maybe it's better to rely on this plugin...
I'm still unsure. Think it's better to keep the Template clean from OMZ-Plugins..

Yeah, I don't think we should automatically define that in the environment, as it will impact other terminal applications (ViM, emacs, etc.,), and may muck with users' applications. This is probably something we should instead make note of in the README.


[Docker] Gitea not running when data directory is mounted externally from VM

Gitea version (or commit ref): 1.14
Git version:
Operating system: Ubuntu 20.0.4 - gitea using official docker image. Running docker-compose from here: https://docs.gitea.io/en-us/install-with-docker/#mysql-database

Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No

Log gist:

Description

I tried spinning up a docker container based on the official documentation, but I kept getting the error in logs (see Logs), in the Mariadb mysql container.
For further context, my docker host is a VM, with some volumes mounted to the host.
If you need more details of my hypervisor and volume drivers, let me know, but I think the issue here may be in gitea's code as I am able to run many applications on this set up.
Let /srv/ be the directory in the VM itself, and let /srvmnt/ be the directory where the external volume is mounted into the VM.
Here are my findings from testing:

data
mysql
Works?

srv
srv
ok

srv
srvmnt
ok

srvmnt
srv
error

srvmnt
srvmnt
error

"data" refers to the docker mounted directory for the gitea web app based on the docker-compose.yml file below
"mysql" refers to the docker mounted directory for the mysql container
Where it says "ok", everything works fine, as intended.
Where it says "error", what happened was when I spun up the container, navigated to the web host and port, gitea greeted me with the installation. When the installation is completed (using default settings), it crashes and I can't visit the same url anymore. 404. Upon inspecting the docker logs, you'll see what is shown in Logs below. Looks normal for the Gitea container, but the mariadb instance is throwing the error [Warning] Aborted connection 11 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
However, as shown in my table above, it is not an error when mounting the mariadb instance on the external drive. Error occurs when mounting the gitea data directory externally.
docker-compose.yml:
version: '2'
services:
  web:
    container_name: gitea
    image: gitea/gitea:1.14
    volumes:
      - /[srv or srvmnt]/gitea/data:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    ports:
      - "3000:3000"
      - "222:22"
    environment:
      - USER_UID=1000
      - USER_GID=1000
      - GITEA__database__TYPE=mysql
      - GITEA__database__HOST=db:3306
      - GITEA__database__NAME=gitea
      - GITEA__database__USER=gitea
      - GITEA__database__PASSWD=gitea
    depends_on:
      - db
    restart: unless-stopped
  db:
    container_name: gitea_db
    image: mariadb:10.4
    restart: unless-stopped
    environment:
      - MYSQL_ROOT_PASSWORD=gitea
      - MYSQL_DATABASE=gitea
      - MYSQL_USER=gitea
      - MYSQL_PASSWORD=gitea
    volumes:
      - /[srv or srvmnt]/gitea/mysql:/var/lib/mysql

Logs:

Mysql (Mariadb) Logs

2021-04-13 12:32:26+00:00 [Note] [Entrypoint]: Database files initialized,
2021-04-13 12:32:26+00:00 [Note] [Entrypoint]: Starting temporary server,
2021-04-13 12:32:26+00:00 [Note] [Entrypoint]: Waiting for server startup,
2021-04-13 12:32:26 0 [Note] mysqld (mysqld 10.4.14-MariaDB-1:10.4.14+maria~focal) starting as process 121 ...,
2021-04-13 12:32:26 0 [Note] InnoDB: Using Linux native AIO,
2021-04-13 12:32:26 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins,
2021-04-13 12:32:26 0 [Note] InnoDB: Uses event mutexes,
2021-04-13 12:32:26 0 [Note] InnoDB: Compressed tables use zlib 1.2.11,
2021-04-13 12:32:26 0 [Note] InnoDB: Number of pools: 1,
2021-04-13 12:32:26 0 [Note] InnoDB: Using generic crc32 instructions,
2021-04-13 12:32:26 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts),
2021-04-13 12:32:26 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M,
2021-04-13 12:32:26 0 [Note] InnoDB: Completed initialization of buffer pool,
2021-04-13 12:32:26 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().,
2021-04-13 12:32:26 0 [Note] InnoDB: 128 out of 128 rollback segments are active.,
2021-04-13 12:32:26 0 [Note] InnoDB: Creating shared tablespace for temporary tables,
2021-04-13 12:32:26 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...,
2021-04-13 12:32:26 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.,
2021-04-13 12:32:26 0 [Note] InnoDB: Waiting for purge to start,
2021-04-13 12:32:26 0 [Note] InnoDB: 10.4.14 started; log sequence number 60967; transaction id 21,
2021-04-13 12:32:26 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool,
2021-04-13 12:32:26 0 [Note] Plugin 'FEEDBACK' is disabled.,
2021-04-13 12:32:26 0 [Note] InnoDB: Buffer pool(s) load completed at 210413 12:32:26,
2021-04-13 12:32:26 0 [Warning] 'user' entry 'root@cc32671f015f' ignored in --skip-name-resolve mode.,
2021-04-13 12:32:26 0 [Warning] 'user' entry '@cc32671f015f' ignored in --skip-name-resolve mode.,
2021-04-13 12:32:26 0 [Warning] 'proxies_priv' entry '@% root@cc32671f015f' ignored in --skip-name-resolve mode.,
2021-04-13 12:32:26 0 [Note] Reading of all Master_info entries succeeded,
2021-04-13 12:32:26 0 [Note] Added new Master_info '' to hash table,
2021-04-13 12:32:26 0 [Note] mysqld: ready for connections.,
Version: '10.4.14-MariaDB-1:10.4.14+maria~focal'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution,
2021-04-13 12:32:27+00:00 [Note] [Entrypoint]: Temporary server started.,
Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.,
Warning: Unable to load '/usr/share/zoneinfo/leapseconds' as time zone. Skipping it.,
Warning: Unable to load '/usr/share/zoneinfo/tzdata.zi' as time zone. Skipping it.,
2021-04-13 12:32:28 10 [Warning] 'proxies_priv' entry '@% root@cc32671f015f' ignored in --skip-name-resolve mode.,
2021-04-13 12:32:28+00:00 [Note] [Entrypoint]: Creating database gitea,
2021-04-13 12:32:28+00:00 [Note] [Entrypoint]: Creating user gitea,
2021-04-13 12:32:28+00:00 [Note] [Entrypoint]: Giving user gitea access to schema gitea,
2021-04-13 12:32:28 14 [Warning] 'proxies_priv' entry '@% root@cc32671f015f' ignored in --skip-name-resolve mode.,
,
2021-04-13 12:32:28+00:00 [Note] [Entrypoint]: Stopping temporary server,
2021-04-13 12:32:28 0 [Note] mysqld (initiated by: root[root] @ localhost []): Normal shutdown,
2021-04-13 12:32:28 0 [Note] Event Scheduler: Purging the queue. 0 events,
2021-04-13 12:32:28 0 [Note] InnoDB: FTS optimize thread exiting.,
2021-04-13 12:32:28 0 [Note] InnoDB: Starting shutdown...,
2021-04-13 12:32:28 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool,
2021-04-13 12:32:28 0 [Note] InnoDB: Buffer pool(s) dump completed at 210413 12:32:28,
2021-04-13 12:32:30 0 [Note] InnoDB: Shutdown completed; log sequence number 60976; transaction id 24,
2021-04-13 12:32:30 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1",
2021-04-13 12:32:30 0 [Note] mysqld: Shutdown complete,
,
2021-04-13 12:32:30+00:00 [Note] [Entrypoint]: Temporary server stopped,
,
2021-04-13 12:32:30+00:00 [Note] [Entrypoint]: MySQL init process done. Ready for start up.,
,
2021-04-13 12:32:30 0 [Note] mysqld (mysqld 10.4.14-MariaDB-1:10.4.14+maria~focal) starting as process 1 ...,
2021-04-13 12:32:30 0 [Note] InnoDB: Using Linux native AIO,
2021-04-13 12:32:30 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins,
2021-04-13 12:32:30 0 [Note] InnoDB: Uses event mutexes,
2021-04-13 12:32:30 0 [Note] InnoDB: Compressed tables use zlib 1.2.11,
2021-04-13 12:32:30 0 [Note] InnoDB: Number of pools: 1,
2021-04-13 12:32:30 0 [Note] InnoDB: Using generic crc32 instructions,
2021-04-13 12:32:30 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts),
2021-04-13 12:32:30 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M,
2021-04-13 12:32:30 0 [Note] InnoDB: Completed initialization of buffer pool,
2021-04-13 12:32:30 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().,
2021-04-13 12:32:30 0 [Note] InnoDB: 128 out of 128 rollback segments are active.,
2021-04-13 12:32:30 0 [Note] InnoDB: Creating shared tablespace for temporary tables,
2021-04-13 12:32:30 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...,
2021-04-13 12:32:30 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.,
2021-04-13 12:32:30 0 [Note] InnoDB: Waiting for purge to start,
2021-04-13 12:32:30 0 [Note] InnoDB: 10.4.14 started; log sequence number 60976; transaction id 21,
2021-04-13 12:32:30 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool,
2021-04-13 12:32:30 0 [Note] Plugin 'FEEDBACK' is disabled.,
2021-04-13 12:32:30 0 [Note] Server socket created on IP: '::'.,
2021-04-13 12:32:30 0 [Warning] 'proxies_priv' entry '@% root@cc32671f015f' ignored in --skip-name-resolve mode.,
2021-04-13 12:32:30 0 [Note] InnoDB: Buffer pool(s) load completed at 210413 12:32:30,
2021-04-13 12:32:30 0 [Note] Reading of all Master_info entries succeeded,
2021-04-13 12:32:30 0 [Note] Added new Master_info '' to hash table,
2021-04-13 12:32:30 0 [Note] mysqld: ready for connections.,
Version: '10.4.14-MariaDB-1:10.4.14+maria~focal'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution,
2021-04-13 12:33:08 11 [Warning] Aborted connection 11 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:08 10 [Warning] Aborted connection 10 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:08 9 [Warning] Aborted connection 9 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:09 15 [Warning] Aborted connection 15 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:09 16 [Warning] Aborted connection 16 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:10 20 [Warning] Aborted connection 20 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:10 19 [Warning] Aborted connection 19 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:12 24 [Warning] Aborted connection 24 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:12 22 [Warning] Aborted connection 22 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:13 29 [Warning] Aborted connection 29 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:13 26 [Warning] Aborted connection 26 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:16 33 [Warning] Aborted connection 33 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:16 31 [Warning] Aborted connection 31 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:20 37 [Warning] Aborted connection 37 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:20 35 [Warning] Aborted connection 35 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:27 39 [Warning] Aborted connection 39 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:27 38 [Warning] Aborted connection 38 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:41 45 [Warning] Aborted connection 45 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),
2021-04-13 12:33:41 43 [Warning] Aborted connection 43 to db: 'gitea' user: 'gitea' host: '<IP_ADDRESS>' (Got an error reading communication packets),

Gitea Logs
2021/04/13 20:47:10 routers/init.go:135:GlobalInit() [T] AppWorkPath: /app/gitea,
2021/04/13 20:47:10 routers/init.go:136:GlobalInit() [T] Custom path: /data/gitea,
2021/04/13 20:47:10 routers/init.go:137:GlobalInit() [T] Log path: /data/gitea/log,
2021/04/13 20:47:10 routers/init.go:49:checkRunMode() [I] Run Mode: Prod,
2021/04/13 20:47:10 ...dules/setting/log.go:287:newLogService() [I] Gitea v1.14.0 built with GNU Make 4.3, go1.16.3 : bindata, timetzdata, sqlite, sqlite_unlock_notify,
2021/04/13 20:47:10 ...dules/setting/log.go:333:newLogService() [I] Gitea Log Mode: Console(Console:info),
2021/04/13 20:47:10 ...dules/setting/log.go:250:generateNamedLogger() [I] Router Log: Console(console:info),
2021/04/13 20:47:10 ...les/setting/cache.go:73:newCacheService() [I] Cache Service Enabled,
2021/04/13 20:47:10 ...les/setting/cache.go:88:newCacheService() [I] Last Commit Cache Service Enabled,
2021/04/13 20:47:10 ...s/setting/session.go:77:newSessionService() [I] Session Service Enabled,
2021/04/13 20:47:10 ...s/storage/storage.go:158:initAttachments() [I] Initialising Attachment storage with type: ,
2021/04/13 20:47:10 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/attachments,
2021/04/13 20:47:10 ...s/storage/storage.go:152:initAvatars() [I] Initialising Avatar storage with type: ,
2021/04/13 20:47:10 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/avatars,
2021/04/13 20:47:10 ...s/storage/storage.go:170:initRepoAvatars() [I] Initialising Repository Avatar storage with type: ,
2021/04/13 20:47:10 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/repo-avatars,
2021/04/13 20:47:10 ...s/storage/storage.go:164:initLFS() [I] Initialising LFS storage with type: ,
2021/04/13 20:47:10 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/git/lfs,
2021/04/13 20:47:10 routers/init.go:150:GlobalInit() [I] SQLite3 Supported,
2021/04/13 20:47:10 routers/init.go:68:initDBEngine() [I] Beginning ORM engine initialization.,
2021/04/13 20:47:10 routers/init.go:75:initDBEngine() [I] ORM engine initialization attempt #1/10...,
2021/04/13 20:47:10 ...om/urfave/cli/app.go:524:HandleAction() [I] PING DATABASE mysql,
2021/04/13 20:47:10 routers/init.go:155:GlobalInit() [I] ORM engine initialization successful!,
2021/04/13 20:47:10 ...er/issues/indexer.go:142:func2() [I] PID 15: Initializing Issue Indexer: bleve,
2021/04/13 20:47:10 ...er/issues/indexer.go:159:func2() [F] Unable to initialize Bleve Issue Indexer at path: /data/gitea/indexers/issues.bleve Error: invalid argument,
Received signal 15; terminating.
,
Could not load host certificate "/data/ssh/ssh_host_ed25519_cert": No such file or directory
,
Could not load host certificate "/data/ssh/ssh_host_rsa_cert": No such file or directory
,
Could not load host certificate "/data/ssh/ssh_host_ecdsa_cert": No such file or directory
,
Could not load host certificate "/data/ssh/ssh_host_dsa_cert": No such file or directory
,
Server listening on :: port 22.
,
Server listening on <IP_ADDRESS> port 22.
,
2021/04/13 20:48:11 cmd/web.go:82:runWeb() [I] Starting Gitea on PID: 17,
2021/04/13 20:48:11 ...dules/setting/git.go:101:newGit() [I] Git Version: 2.30.2, Wire Protocol Version 2 Enabled,
2021/04/13 20:48:11 cmd/web.go:126:runWeb() [I] Global init,
2021/04/13 20:48:11 ...dules/setting/git.go:101:newGit() [I] Git Version: 2.30.2, Wire Protocol Version 2 Enabled,
2021/04/13 20:48:11 routers/init.go:134:GlobalInit() [T] AppPath: /app/gitea/gitea,
2021/04/13 20:48:11 routers/init.go:135:GlobalInit() [T] AppWorkPath: /app/gitea,
2021/04/13 20:48:11 routers/init.go:136:GlobalInit() [T] Custom path: /data/gitea,
2021/04/13 20:48:11 routers/init.go:137:GlobalInit() [T] Log path: /data/gitea/log,
2021/04/13 20:48:11 routers/init.go:49:checkRunMode() [I] Run Mode: Prod,
2021/04/13 20:48:11 ...dules/setting/log.go:287:newLogService() [I] Gitea v1.14.0 built with GNU Make 4.3, go1.16.3 : bindata, timetzdata, sqlite, sqlite_unlock_notify,
2021/04/13 20:48:11 ...dules/setting/log.go:333:newLogService() [I] Gitea Log Mode: Console(Console:info),
2021/04/13 20:48:11 ...dules/setting/log.go:250:generateNamedLogger() [I] Router Log: Console(console:info),
2021/04/13 20:48:11 ...les/setting/cache.go:73:newCacheService() [I] Cache Service Enabled,
2021/04/13 20:48:11 ...les/setting/cache.go:88:newCacheService() [I] Last Commit Cache Service Enabled,
2021/04/13 20:48:11 ...s/setting/session.go:77:newSessionService() [I] Session Service Enabled,
2021/04/13 20:48:11 ...s/storage/storage.go:158:initAttachments() [I] Initialising Attachment storage with type: ,
2021/04/13 20:48:11 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/attachments,
2021/04/13 20:48:11 ...s/storage/storage.go:152:initAvatars() [I] Initialising Avatar storage with type: ,
2021/04/13 20:48:11 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/avatars,
2021/04/13 20:48:11 ...s/storage/storage.go:170:initRepoAvatars() [I] Initialising Repository Avatar storage with type: ,
2021/04/13 20:48:11 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/repo-avatars,
2021/04/13 20:48:11 ...s/storage/storage.go:164:initLFS() [I] Initialising LFS storage with type: ,
2021/04/13 20:48:11 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/git/lfs,
2021/04/13 20:48:11 routers/init.go:150:GlobalInit() [I] SQLite3 Supported,
2021/04/13 20:48:11 routers/init.go:68:initDBEngine() [I] Beginning ORM engine initialization.,
2021/04/13 20:48:11 routers/init.go:75:initDBEngine() [I] ORM engine initialization attempt #1/10...,
2021/04/13 20:48:11 ...om/urfave/cli/app.go:524:HandleAction() [I] PING DATABASE mysql,
2021/04/13 20:48:11 routers/init.go:155:GlobalInit() [I] ORM engine initialization successful!,
2021/04/13 20:48:11 ...er/issues/indexer.go:142:func2() [I] PID 17: Initializing Issue Indexer: bleve,
2021/04/13 20:48:11 ...er/issues/indexer.go:159:func2() [F] Unable to initialize Bleve Issue Indexer at path: /data/gitea/indexers/issues.bleve Error: invalid argument,
Received signal 15; terminating.
,
Could not load host certificate "/data/ssh/ssh_host_ed25519_cert": No such file or directory
,
Could not load host certificate "/data/ssh/ssh_host_rsa_cert": No such file or directory
,
Could not load host certificate "/data/ssh/ssh_host_ecdsa_cert": No such file or directory
,
Could not load host certificate "/data/ssh/ssh_host_dsa_cert": No such file or directory
,
Server listening on :: port 22.
,
Server listening on <IP_ADDRESS> port 22.
,
2021/04/13 20:49:12 cmd/web.go:82:runWeb() [I] Starting Gitea on PID: 16,
2021/04/13 20:49:12 ...dules/setting/git.go:101:newGit() [I] Git Version: 2.30.2, Wire Protocol Version 2 Enabled,
2021/04/13 20:49:12 cmd/web.go:126:runWeb() [I] Global init,
2021/04/13 20:49:12 ...dules/setting/git.go:101:newGit() [I] Git Version: 2.30.2, Wire Protocol Version 2 Enabled,
2021/04/13 20:49:12 routers/init.go:134:GlobalInit() [T] AppPath: /app/gitea/gitea,
2021/04/13 20:49:12 routers/init.go:135:GlobalInit() [T] AppWorkPath: /app/gitea,
2021/04/13 20:49:12 routers/init.go:136:GlobalInit() [T] Custom path: /data/gitea,
2021/04/13 20:49:12 routers/init.go:137:GlobalInit() [T] Log path: /data/gitea/log,
2021/04/13 20:49:12 routers/init.go:49:checkRunMode() [I] Run Mode: Prod,
2021/04/13 20:49:12 ...dules/setting/log.go:287:newLogService() [I] Gitea v1.14.0 built with GNU Make 4.3, go1.16.3 : bindata, timetzdata, sqlite, sqlite_unlock_notify,
2021/04/13 20:49:12 ...dules/setting/log.go:333:newLogService() [I] Gitea Log Mode: Console(Console:info),
2021/04/13 20:49:12 ...dules/setting/log.go:250:generateNamedLogger() [I] Router Log: Console(console:info),
2021/04/13 20:49:12 ...les/setting/cache.go:73:newCacheService() [I] Cache Service Enabled,
2021/04/13 20:49:12 ...les/setting/cache.go:88:newCacheService() [I] Last Commit Cache Service Enabled,
2021/04/13 20:49:12 ...s/setting/session.go:77:newSessionService() [I] Session Service Enabled,
2021/04/13 20:49:12 ...s/storage/storage.go:158:initAttachments() [I] Initialising Attachment storage with type: ,
2021/04/13 20:49:12 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/attachments,
2021/04/13 20:49:12 ...s/storage/storage.go:152:initAvatars() [I] Initialising Avatar storage with type: ,
2021/04/13 20:49:12 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/avatars,
2021/04/13 20:49:12 ...s/storage/storage.go:170:initRepoAvatars() [I] Initialising Repository Avatar storage with type: ,
2021/04/13 20:49:12 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/repo-avatars,
2021/04/13 20:49:12 ...s/storage/storage.go:164:initLFS() [I] Initialising LFS storage with type: ,
2021/04/13 20:49:12 ...les/storage/local.go:47:NewLocalStorage() [I] Creating new Local Storage at /data/git/lfs,
2021/04/13 20:49:12 routers/init.go:150:GlobalInit() [I] SQLite3 Supported,
2021/04/13 20:49:12 routers/init.go:68:initDBEngine() [I] Beginning ORM engine initialization.,
2021/04/13 20:49:12 routers/init.go:75:initDBEngine() [I] ORM engine initialization attempt #1/10...,
2021/04/13 20:49:12 ...om/urfave/cli/app.go:524:HandleAction() [I] PING DATABASE mysql,
2021/04/13 20:49:12 routers/init.go:155:GlobalInit() [I] ORM engine initialization successful!,
2021/04/13 20:49:12 ...er/issues/indexer.go:142:func2() [I] PID 16: Initializing Issue Indexer: bleve,
2021/04/13 20:49:12 ...er/issues/indexer.go:159:func2() [F] Unable to initialize Bleve Issue Indexer at path: /data/gitea/indexers/issues.bleve Error: invalid argument,
Received signal 15; terminating.
,

Is any file written to the mounted volumes? Does uid 1000 have permission to read/write in the mounted volumes?

@johanvdw , yup, those bases are covered. I've just had some time to test it on one other VM host, with exactly the same configuration, and somehow it works. Will investigate further and report back. Have you ever seen this error before? Any common problems and solutions I should look at first? Google didn't yield anything useful for me.

I still have no idea why. I am using the same two ubuntu 20.0.4 VM to run my docker containers. One of them works, and the other doesn't. They are configured identically.
Nevertheless, I kept searching and found similar issues for posterity:
https://discourse.gitea.io/t/gitea-stopped-running-due-to-database-error-got-an-error-reading-communication-packets/594
https://github.com/go-sql-driver/mysql/issues/556

Reporting back to say that it actually doesn't work on the other VM either, for the same reason. It worked because I mistakenly used SQLite on the second host. With MariaDB or MySQL, the same error shows.
This, then, is highly likely due to the go-sql-driver error I mentioned above.

Look at the logs, in particular the log line marked [F] for Fatal that keeps repeating before gitea restarts:
2021/04/13 20:48:11 ...er/issues/indexer.go:159:func2() [F] Unable to initialize Bleve Issue Indexer at path: /data/gitea/indexers/issues.bleve Error: invalid argument,
Received signal 15; terminating.

The problem is that Bleve cannot lock the file.
You will need to either switch to a filesystem that bleve can support or change the indexer type:
[indexer]
ISSUE_INDEXER_TYPE=db ; or use elasticsearch if you have one

@zeripath Thanks! I really wasn't sure what to make of that. The storage is on ZFS. Elasticsearch has always had the same problem for me with ZFS too.
Anyway, I will ask on bleve's repo about this. Up to mods if they decide this to be closed or remain open here. Cheers!

After reading the issue in the upstream repo, I think it seems not a bug, neither Gitea side nor Bleve/ZFS side.


Specify groupname when search in non-stream to send query to few nodes

If you know that your search will touch few buckets, then only the nodes containing them will be contacted, lowering network hops.

Due to a mixture of historical and technical reasons, the pipelines that are aware of the cross-node bucket distribution and executing non-streaming search queries are today completely separate. Streaming searches go through the full content layer, while indexed search queries take a massive shortcut through the search dispatch layer. So routing indexed search queries based on document location (number, group) is not currently feasible.
However, if a location is specified as part of the query, it should be easy for a search node to perform node-local early-out filtering to see if it has any buckets at all that could possibly contain documents for the given location. This would still be a full query fan-out within a given group, but the query would be a no-op for most nodes (assuming most individual locations are small enough not to be split across many nodes).


chore(main): release 1.2.0

:robot: I have created a release beep boop
1.2.0 (2024-04-29)
Features

add log函数 (3963469)
add test.dart (8c11757)
add wawa (5a578ec)
add zzzz (66d17a2)
添加didi函数 (45616c4)
添加hihi函数 (1e18b06)

Bug Fixes

fix demo (3cc0641)
fix zzzz (8b2cc4b)
release-please.yml add target-branch (432b6e0)
release-please.yml push branches main->dev (62054b6)
update release-please.yml (eed7b73)
修复demo函数 (0dc2dba)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/luoyi58624/luoyi_dart_test/releases/tag/v1.2.0 :sunflower:


[BUG]: document is not defined in a Deno+remix project

What happened?
Attempting to import Stripe into a Remix application running on Deno results in a document is not defined error on the server. This is because Deno defines a global window object (node does not) and the stripe loader uses the presence of window in deciding to attempt loading stripe or short circuit and return null this line
Can this be changed to something that evaluates to false in both Deno and node environments?
Example Remix route code below, adapted directly from this example
import { Elements } from "https://esm.sh/<EMAIL_ADDRESS>import { Stripe, loadStripe } from 'https://esm.sh/<EMAIL_ADDRESS>import { Outlet, useLoaderData } from '@remix-run/react'
import { createPaymentIntent } from './payments.ts'

export const loader = async () => {
  return await createPaymentIntent()
}

export default function Payments() {
  let stripePromise = loadStripe('pk_test_4VxNf7EgW0gWs9WkTlqxXqT9')

  const paymentIntent = useLoaderData()
  const options = {
    // passing the client secret obtained from the server
    clientSecret: paymentIntent.client_secret,
  }

  return (
    <div style={{ padding: '20px' }}>
      <Elements stripe={stripePromise} options={options}>
        <Outlet />
      </Elements>
    </div>
  )
}```

Since during initialization we always call document.querySelectorAll which will crash if document is not present, I see not problem in extending the null returning line, from
    if (typeof window === 'undefined') {

too
    if (typeof window === 'undefined' || typeof document === 'undefined') {

Would you be able to make a PR for this change?

The fix has been released.


Add notifications to sign in / register

incorporate notification messages for success and errors on  sign in, sign out and register.

You can assign this to me. I have been refactoring signin and register to use preact setState instead of how it was doing it before (old fashioned getElementById). I have also tweaked the profile page to get user info and display their name and a success message if they are coming from register or sign in.

@seckboy that's great,
Thank you!


Added spicedb client to repository, generated config and added wire c…

…onfig.
PR Template:
Describe your changes

...

Ticket reference (if applicable)
Fixes #
Checklist

[ ] Are the agreed upon acceptance criteria fulfilled?

[ ] Was the 4-eye-principle applied? (async PR review, pairing, ensembling)

[ ] Do your changes have passing automated tests and sufficient observability?

[ ] Are the work steps you introduced repeatable by others, either through automation or documentation?

[ ] If automation is possible but not done due to other constraints, a ticket to the tech debt sprint is added
[ ] An SOP (Standard Operating Procedure) was created

[ ] The Changes were automatically built, tested, and  - if needed, behind a feature flag - deployed to our production environment. (Please check this when the new deployment is done and you could verify it.)

[ ] Are the agreed upon coding/architectural practices applied?

[ ] Are security needs fullfilled? (e.g. no internal URL)

[ ] Is the corresponding Ticket in the right state? (should be on "review" now, put to done when this change made it to production)

[ ] For changes to the public API / code dependencies: Was the whole team (or a sufficient amount of ppl) able to review?

@merlante can you mark this as "WIP" , thanks!


HTML JS slides

always wanted to do some, now it might be the right time :)

Łukasz Jarosz poleca reveal.js, jest też impress.js

anteq.github.io/eestec-beacon-workshops
known also as branch gh-pages :)


Add Kermack-McKendrick model/age of infection

See https://en.wikipedia.org/wiki/Kermack%E2%80%93McKendrick_theory
Some work on this using NeuralPDE.jl can be found here although it's very slow.
MethodOfLines.jl doesn't (yet) support integrals.
Fowler and Hollingsworth generate some simulations, and I have some Fortran code that I could port.

See also https://www.medrxiv.org/content/10.1101/2<IP_ADDRESS>54385v1.full

There is also https://arxiv.org/abs/2010.10955 which gives a straightforward discretization scheme, though the structure of the model isn't exactly KM.


Polish KafkaTemplate.executeInTransaction()

This PR polishes KafkaTemplate.executeInTransaction().

Can we have more explanation for the reason of change?
Thanks

Can you explain the rationale for this?
With this change, we'll no longer close the producer or remove it from this.producers.

@artembilan @garyrussell Thanks for the quick feedback! I just collapsed the finally clause for brevity as I thought it's equivalent with the current implementation. Am I missing something?

The abortTransaction after an exception needs to be in a try/catch too.

Doh - I see - the finally handles it.


sass imported styles are null on server, but correct on client

Hi,
we are thinking about using your package in one of our projects and we usually really like to use sass with css-modules on every component for styling.
We tried to implement it the way, we always do, but there seems to be a problem with the serverside rendering part.
We import the styles with
import * as styles from './STYLEFILE.scss

Then we want to access the different style Classnames like

The problem now is, that we end up getting undefined as the className, but if we change something and use hotreload (so it rerenders on the client side only), it works and shows the className correctly.
Also console.logging the className gives the correct result.
Here is our example DemoComponent:
import * as React from "react";
import { GetHackerNewsTopStoriesQuery } from "@/graphql";
import * as styles from './DemoListing.scss';

interface IDemoListingPropType {
  data?: GetHackerNewsTopStoriesQuery,
}

export class DemoListing extends React.PureComponent<IDemoListingPropType> {
  public render() {
    const { data } = this.props;

    console.log('Check it here: ', styles.List);

    return (

        {data!.hn!.topStories!.map(story => (

              {story!.title}

        ))}

    );
  }
}

And here is our DemoListing.scss file:
.List {
  list-style-type:none;
  margin:0;
  padding:0;

  li {
    display:block;
    border-bottom:1px solid #e7e7e7;
    padding:10px 0;
    font-size:12px;
  }
}

Btw: I also get the following error in my console:
react-dom.development.js:507 Warning: Prop `className` did not match. Server: "la undefined" Client: "la List-25PR_C19jEn_aOuzjpgfiz"

the same here. Any news?


Add Email Setting

I propose to add the email setting.
This add into the gitlab.yml the parameters below:
    email_from<EMAIL_ADDRESS>    email_display_name: GitLab
    email_reply_to<EMAIL_ADDRESS>
See official documentation :
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example#L66-72
Note: I added the PR #30 in order to avoid the issue #29 .

I did rebase against the new master without the /password/new commit 4aeaec0.


Subparsers with aliases are duplicated in the action column

[x] OS: Windows 10
[x] Python Version: 3.6
[x] Gooey Version: 1.0.3
[x] Thorough description of problem

[x] Expected Behavior: list subparsers without duplicates for aliases
[x] Actual Behavior: a subparser with one or more aliases gets displayed twice in the action column: once with its name, and a second time with the name of the package and its name. Example: pause and aria2p pause.

[x] A minimal code example -- preferably copy/pastable in the issue itself (less time figuring out how to run your code == more time debugging!)

import argparse
from gooey import Gooey

@Gooey
def main():
    parser = argparse.ArgumentParser(prog="aria2p")
    subparsers = parser.add_subparsers(dest="subcommand", metavar="", prog="aria2p")
    subcommand_help = "Show this help message and exit."

    def subparser(command, text, **kwargs):
        sub = subparsers.add_parser(command, add_help=False, help=text, description=text, **kwargs)
        sub.add_argument("-h", "--help", action="help", help=subcommand_help)
        return sub

    pause_parser = subparser("pause", "Pause downloads.", aliases=["stop"])

[x] Screenshot (if visual quirk)

As you can see in the screenshot, every subparser with one or more aliases is duplicated.

[x] Anything else you may think will be helpful

I think your code sample got cut off. Could you update with a complete example that demos the problem?
Thanks!

Well, I'm having trouble writing a minimum reproducible example. You can see the complete code at https://github.com/pawamoy/aria2p/blob/master/src/aria2p/cli.py#L134

Closing. Feel free to reopen if you can create a runnable example.


Add another test case into top_k_elements_test. Minor addition on col…

Add another test case into top_k_elements_test. Minor addition on column_stats_test.
Convert the value in void Add(type::Value& value) in top_k_elements.h according to their actual type, instead of an arbitrary decision of string.

@vanryan :ship:


remove duplicate import

What does this PR change?
Does this PR rely on any other PRs?

How does this PR impact users? (This is the kind of thing that goes in release notes!)
Links to Issues or ZD tickets this PR addresses or fixes

How was this PR tested?
Have you made an update to documentation?

Looks like the build is still failing on this, probably related to a recently-merged PR?

Looks like there is actually another failing test going to just add that to this PR


rename afterRender hook -> onMount

agree Vue's hooks names are the best so far so standardizing on that feels right @mandx

going to do some work that will depend on this, so eager merging and happy to followup with additional PRs to address feedbaack

going to do some work that will depend on this, so eager merging and happy to followup with additional PRs to address feedbaack


Error C2-12828-1 when start

Thanks for this repository that can play h3 in psvita!
I tried to install it and success, but failed when start game with error C2-12828-1, the detail info please see below.
Can you give some suggestion for how to fix it? Thanks again.

Error C2-12828-1 screenshot:

Dump core file: psp2core-1703327707-0x00001526b9-eboot.bin.psp2dmp.zip

HOMM3.vpk version is v1.2.2

System version of psvita is 3.60 (HENkaku-11)

All plugin files are put in ur0:/tai, and the contents of ur0:/tai/config.txt is:

# For users plugins, you must refresh taiHEN from HENkaku Settings for
# changes to take place.
# For kernel plugins, you must reboot for changes to take place.
*KERNEL
ur0:tai/gamesd.skprx
ur0:tai/nonpdrm_v1.2.skprx
ur0:tai/repatch_v3.0.skprx
ur0:tai/0syscall6_v1.3.skprx
ur0:tai/ioplus_v0.1.skprx
ur0:tai/kubridge_v0.1.skprx
*ALL
ur0:tai/VitaGrafix_v5.0.2.skprx
# henkaku.skprx is hard-coded to load and is not listed here
*main
# main is a special titleid for SceShell
ur0:tai/henkaku.suprx
ur0:tai/shellbat_r10.suprx
ur0:tai/LowMemMode_v1.2.suprx
ur0:tai/NoTrpDrm_v1.1.suprx
*NPXS10015
# this is for modifying the version string
ur0:tai/henkaku.suprx
*NPXS10016
# this is for modifying the version string in settings widget
ur0:tai/henkaku.suprx

Can you give this version a try?
https://github.com/Northfear/homm3hd-vita/releases/tag/v1.1.0
Also what's your game data version?

Reinstall with HOMM3_v1.1.0.vpk and it works fine, Thanks!

Whoa! It's not fine =)
Performance of 1.1.0 is pretty bad during big battles. Can you contact me on Discord (username: northfear), so we could investigate this further?

of course, already add you in Discord (Cering)

The problem was caused by missing libshacccg.suprx
After following the guide everything worked as expected


Stylize keyboard shortcut tip

Enhancement
Adds more styling to the keyboard shortcut info to be more readable.
Used css styles from here

@shahimclt : Don't work on this. The Spell change was a 'quick fix'. A better UI is on it's way.
Closing without Merging.

Ok sure. :+1:


[memaccess] Change AccessedStorage::hasIdenticalBase() to use accesso…

…rs to access state instead of accessing state directly.
Currently this is the only place in the code base where AccessedStorage's
underlying value is not accessed via an accessor (an invariant of
AccessedStorage). Despite breaking that invariant, the code today is technically
correct, but with some changes that @jckarter is working on will break this code
since we want to look through the begin_borrow on a class in the accessor
instead of in the AccessedStorage's constructor. So accessing the value directly
in that case will return the begin_borrow instead of the operand of the
begin_borrow like the accessor would.

@swift-ci smoke test and merge

@gottesmm I think closing it just stops the merge, the other thing we be to repush the same branch . No worries if it goes in :)

= ).


The recess callback passes an instances array now not a simple object.

This commit fixes issue #113.

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

We are no longer maintaining this project and as such are arching all PRs.


Upgrading Blazor language service from 0.6 to 0.7 installs windows SDK

Upgrading Visual studio extension from 0.6 to 0.7 installs multiple versions of Windows SDK.
Is this intended?

@ctyar This is not intended, and personally I have never experienced it, might be a bug in VS

I think this is specific to the configuration of your VS instance. It doesn't happen on mine. Perhaps the VS installer has determined that you have an out-of-date Windows SDK so it wants to update it.


About the role of gamma loss

Hi ! Thanks for sharing your great work. I could not understand the role of the gamma loss when using 3 channels illumination （polychromatic light）since you said from your work that the gamma loss is to ensure a nearly monochromatic light. I would really appreciate it if you could give me some information about it. Thanks.

Hi, in the original paper we directly set all 3 channels of light to be identical.
Later we found that this setting would lead to some artifacts in face textures given input images with abnormal lightings. Therefore, we replace the monochromatic light setting with polychromatic light to alleviate this problem. But we still want the light to be nearly monochromatic to avoid its compensation for face texture. So we add the gamma loss to constrain it.

Thank you so much : )


[2.6.6] Only check cattle-system for existing plans

Rancher was checking all namespaces for plans, and trying to update ones not currently managed by rancher in order to force rancher to manage them. By reusing the same client (created using metav1.NamespaceAll, the generated client (wrangler uses the kubernetes client generator) uses the namespace of the client in the API request, which is always empty so the object cannot be updated. Realistically, rancher should not be updating any plans except those in the cattle-system namespace, as these are the only plans we have control over, and disabling those not controlled by rancher in cattle-system is done to prevent anything from unintentionally running when system-upgrade-controller is deployed.
Related Issue: https://github.com/rancher/rancher/issues/36607

@jakefhyde  Have you got this issue reproduced?

@jiaqiluo Yes, it looks like trying to use the same client created with "" to specify all namespaces will succeed with getting and listing, but fail with other CRUD commands due to how the kubernetes api request gets generated, and this appears to be the expected behavior, but as far as I can tell, there is no really need for us to disable all plans in other namespaces on upgrade.

@jakefhyde  OK, that sounds good to me. I just want to confirm we have steps to reproduce the bug for QA.
If possible, could you update the description to follow the PR template?


[nrf fromtree] doc: Add reference labels in getting started doc

Add reference labels in getting_started/index.rst
Signed-off-by: Uma Praseeda<EMAIL_ADDRESS>(cherry picked from commit 90577ee5d8b5ac6eea891134e16aad7b69e239dc)

@umapraseeda update SHA on your PR once this is merged


Not Tile varnish (not Decals)

In SS13, the way coloring tiles is handled is via an individual tile type for each variant.
For example, on /tg/, the tiles that line the halls of each department have a line of tiles on the edge colored by that department's color. Each variant needed is an extra tile type, which is unwieldy.
Alongside that, there are a lot of these variants, as there's a lot of different ways map makers may want to color tiles.
In SS14, it's fully possible to both make it even easier for map makers to decorate the map, and to greatly cut down on the number of tile texture variants that need to exist, and the way I propose to do this is via a tile painting/varnishing functionality.
I propose attaching a 4x4px 255+1 color (255 colors and full transparency/no color) texture to each tile. This is pretty cheap, 4KiB per 16x16 chunk of tiles, and has the ability to be quite performant (blit the tile color data into a texture in VRAM, overlay that texture at some transparency level with the tile map. No entity overhead, no overhead from a large number of small textures in VRAM)
Even extremely large maps aren't particularly big with this idea. A 512x512 map that fills every single chunk with data would need 4MiB of tile varnish data in total.
Oh, yea, someone assign this to me.
Difference from decals: Decals are 32x32 textures you slap over the tiles, and they're pre-fabbed.
This is basically setting tints for the underlying tile with an extremely low resolution texture (4x4px, 256 colors), it doesn't let you add, say, caution stripes over a tile, it tints the tile it's on top of.

Is this still something that would be useful, or do the decals (#5183 & #6548 ) just make this issue redundant?

They make it redundant.


fixes issue #492

For rect series one of the scales can get adjusted, just like for bar series, even though the user has control on both sides of the rectangle.
For instance (as highlighted in issue 492) for vertical bar series, x scale gets adjusted, even though user can control the position of the left and right edge of each mark.
(likewise for horizontal rect series, y scale could get adjusted.)

Wait i take it back, it looks like i already wrote tests to that effect. make the tests pass and itll be fine


Core Files missing

Core Files for Elysium Remastered not available for download at Mega.
61,75 - Unable to download Elysium Remastered - Core Files.7z
(MegaDownloader+State|https://mega.nz/file/5ZVxDKaQ#Is83DnNFJtQdi3hih5VQI7hFbxlDxH_YO8h3Sn8amlc)
61,75 - Cannot continue, was unable to download one or more archives
61,75 - File hash check (-42) 6196e3143253eedf6c627b66645f3e40847bbff9815306518b065ad5f058b46f
61,75 - Encountered error, can't continue - System.Exception: Cannot continue, was unable to download one or more archives
   at Wabbajack.Lib.AInstaller.Error(String msg) in C:\Wabbajack\splitwork\wabbajack\Wabbajack.Lib\AInstaller.cs:line 71
   at Wabbajack.Lib.MO2Installer._Begin(CancellationToken cancel) in C:\Wabbajack\splitwork\wabbajack\Wabbajack.Lib\MO2Installer.cs:line 161
   at Wabbajack.Lib.ABatchProcessor.<Begin>b__66_0() in C:\Wabbajack\splitwork\wabbajack\Wabbajack.Lib\ABatchProcessor.cs:line 177
   at Wabbajack.MO2InstallerVM.<>c__DisplayClass31_0.<<Install>b__0>d.MoveNext() in C:\Wabbajack\splitwork\wabbajack\Wabbajack\View Models\Installers\MO2InstallerVM.cs:line 181
--- End of stack trace from previous location ---
   at Wabbajack.MO2InstallerVM.Install() in C:\Wabbajack\splitwork\wabbajack\Wabbajack\View Models\Installers\MO2InstallerVM.cs:line 175
   at Wabbajack.InstallerVM.<>c__DisplayClass88_0.<<-ctor>b__78>d.MoveNext() in C:\Wabbajack\splitwork\wabbajack\Wabbajack\View Models\Installers\InstallerVM.cs:line 391
62,11 - File hash check (-42) 6196e3143253eedf6c627b66645f3e40847bbff9815306518b065ad5f058b46f

I am getting same error

Why is this marked as completed? not seeing a solution???


Running Evaluations without merging

Hello,
Is there a way to run evaluations on just 1 model without merging anything?
For example, Flan-T5 + some LoRA model? I understand that can be specified in the modelpool but what should the method be? technically, it works to use simple averaging (with 1 model only) but is there a more, straight forward way to run the eval?
Thanks!

The dummy method simply returns the first model from the model pool.


Add back tooltip for Participants and Organizations Fix #149

remove tooltip except for Participants, Organizations and Reactions

Thanks @leocaseiro! LGTM :+1:

Thanks @leocaseiro!


Bug:  Pager-duty-issue-calculator script fails to notify missing mandatory fields when creating PagerDuty Issues

📜 Description
The script fails silently without notifying users when mandatory fields are not filled during the creation of a PagerDuty issue, leaving users unaware of the reason for the failure.
👟 Reproduction steps
N/A
👍 Expected behavior
N/A
👎 Actual Behavior
N/A
☸ Kubernetes version
1.2
Cloud provider

🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#10049

PTAL @abhibhaw

@YashasviDevtron @satyampsoni Is this still valid?

Waiting for input from prod-engg!


Acesslog dateformat enhancemnet

What is the purpose of the change
AcceLogFilter message creation and last and current check was performing by each time simple date formate object creation. In this version of code I have use the ThreadLocal for each thread wise to create simple date format object instead of each call
https://github.com/apache/incubator-dubbo/issues/3026
Previous PR I have closed as it was too old and due to recent major StringUtils changes 500+ files were showing as modified files and around 8000+ line of code changes, which will may create some confusion. To avoid this confusion have raised new PR.
In previous PR there was request change was asked by @zonghaishang , which (not thread safe)I beleive I have adrressed.
In this PR

I have moved the access log creation and writing to file into a single thread and instead of each time creating a SimpleDateFormat using FastDateFormat formatter with new created DateUtil.
Refactored code to separate our and group related task in separate method and have enhance the readability by using
- Method renaming
- Reducing big methods to small.
- DateUtil utility using FastDateFormat

This PR is a resurrection of old PR

3027 (https://github.com/apache/incubator-dubbo/pull/3027) PR
3080 (https://github.com/apache/incubator-dubbo/pull/3080)
3.https://github.com/apache/incubator-dubbo/pull/3090
Sorry for the inconvenience

Brief changelog
XXXXX
Verifying this change
Runnig UT and verifying generated access log.
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a [GITHUB_issue] (https://github.com/apache/incubator-dubbo/issues/3026) field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

@beiwei30  I have merged ur PR in branch to this branch. Could you please look into this. Thanks for your support.

@satansk could you review, as you requested for changes.


Update aseprite to 1.1.13

After making all changes to the cask:

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

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


Attach proto-images to works in the transformer

https://github.com/wellcometrust/catalogue/pull/392


Store the workspace in the DRb front object

This is necessary to access the user that started the Automation
Request. The user is stored in the workspace. Each DRb request
runs in a separate thread and the workspace and user should be
accessible from these threads.
These changes were pulled out from the RBAC PR #6395 to help with PR #10922

@kbrock @lfu
Please review

Lol, I was expecting this to be a bit biger

@mkanoor @kbrock @gmcculloug This did not make it into Euwe branch.  Please label euwe/yes or euwe/no, as appropriate.

I defer.

@chessbyte This is needed for euwe, I have labelled it

Euwe Backport details:
$ git log
commit 850bc40eca306a4e49b303e1bb1db0dc37748694
Author: Keenan Brock<EMAIL_ADDRESS>Date:   Wed Sep 21 23:21:22 2016 -0400

    Merge pull request #11434 from mkanoor/workspace_in_drb_front

    Store the workspace in the DRb front object
    (cherry picked from commit b47179ba1f9dee12884d84f59423686475d4d0e8)


Table of Contents support

First, a great thank you for your work on porting the theme to Astro. Now is there any chance we can have the Table of Contents (TOC) just like the original theme as well?

First, a great thank you for your work on porting the theme to Astro. Now is there any chance we can have the Table of Contents (TOC) just like the original theme as well?

Thank you very much for your use. This template has top navigation and podcast categories for you to use. If it doesn't meet your needs, you can migrate your original functional code to a new project.


Crossfade on pattern change

Currently, switching patterns has a hard cut with silent loading time.
Buffering then crossfading once the new pattern is ready would be awesome for random play, as well as use in live-play ambient music setups (e.g. TTRPGs).

Related: Would be also nice to crossfade to silence on stop.
The "click" from lack of crossfade is surprisingly jarring.

It would be even better if the crossfade is not based on the traditional fade-out mechanisms of music players, but instead based on the last few musical notes on the previous piece being retro-fitted into the patterns of the next piece.


How to support windows & android?

How to support windows & android?

Use your ip,remote id,PSK to connect it

how to do that? cloud you give me an instruction？thanks

@fgcui1204 这个只介绍了 iOS 的配置，我是用 Android ，用的是 配置 IKEv2 VPN: Windows 和 Android 这个。
IKEv2 连接速度感觉比  IPsec快点，也更稳定，值得拥有。

I'd made a fork of this project to add support for windows clients (closed PR #27)
https://github.com/tsl0922/docker-ikev2-vpn-server/commit/513ceeedc96fbd00415feb2753f38d5b47e76d34

I was able to connect using TheGreenBow VPN Client. It creates virtual network adapter. Was not able to use standard Windows VPN. It supports IKEv2,  but not with a shared key.


Sql Server connection

Question
We use v0.17 and we wanted to connect to sql server instead of mysql or postgress. We saw in the code that devlake uses gorm. We were wondering if devlake supports such connection. Thanks in advance.

Supporting SQL Server is not in our roadmap so far. If you are interested in it, we can provide some help.


Deprecate Inventory in favor of Rs2Inventory

I'll be rewriting the Inventory class itself, so this will be redudant.


feat(peturb): allow peturb to template pod names, IPs and host IPs

Allows the use of ##IP, ##NAME and ##HIP to template pod IPs, name and host IPs into a challenge.txt.
Also update the docs to reflect this new functionality.

Won't moving copy_challenge_and_task affect run_kubectl_yaml ?

No. copy_challenge_and_task literally only does that. None of the other functions interact with the task.yaml or challenge.txt.
If there's something in the code I've missed please highlight it as I cannot see any reason for these to conflict at all.

Fixes #89


Naming rule violations

You may want to fix the "Naming rule violations".
Also, do you know of a stand-alone that would go through all my projects and update to the Naming convention?
Thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5154904d-b7d9-3eaa-7d2e-5ca8308f1f48
Version Independent ID: 8b82f235-ec9c-5c72-d001-b761b491d400
Content: Handling Events (Visual Basic)
Content Source: docs/visual-basic/programming-guide/language-features/events/walkthrough-handling-events.md
Product: dotnet-visualbasic
GitHub Login: @KathleenDollard
Microsoft Alias: kdollard

Thank you for opening this issue. I'll add it to the backlog. You can always submit the fix yourself by editing the original article. Click on the Content Source link at the bottom of your original comment. To learn how to edit, see the Editing files in a repository article from GitHub.
The source code used by this file is at https://github.com/dotnet/samples/tree/master/snippets/visualbasic/VS_Snippets_VBCSharp/VbVbcnWalkthroughDeclaringAndRaisingEvents/VB/
Regarding applying all code styles, I think there is some basic stuff in Visual Studio if you right-click on the project and find something like Analyze and apply fixes and other plugins like resharper has this capability too.
Thanks again!

Thanks.
From: Andy De George<EMAIL_ADDRESS>Sent: Tuesday, June 11, 2019 2:09 PM
To: dotnet/docs<EMAIL_ADDRESS>Cc: RichEme<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [dotnet/docs] Naming rule violations (#12746)
Thank you for opening this issue. I'll add it to the backlog. You can always submit the fix yourself by editing the original article. Click on the Content Source link at the bottom of your original comment. To learn how to edit, see the Editing files in a repository https://help.github.com/articles/editing-files-in-your-repository  article from GitHub.
The source code used by this file is at https://github.com/dotnet/samples/tree/master/snippets/visualbasic/VS_Snippets_VBCSharp/VbVbcnWalkthroughDeclaringAndRaisingEvents/VB/
Regarding applying all code styles, I think there is some basic stuff in Visual Studio if you right-click on the project and find something like Analyze and apply fixes and other plugins like resharper has this capability too.
Thanks again!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/dotnet/docs/issues/12746?email_source=notifications&email_token=ALBEHTUH2EGYN5GX3TX7L2LPZ7Z4NA5CNFSM4HWJY6M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXOF5DA#issuecomment-500981388 , or mute the thread https://github.com/notifications/unsubscribe-auth/ALBEHTR7DJB7TDUYDP2A5PLPZ7Z4NANCNFSM4HWJY6MQ .  https://github.com/notifications/beacon/ALBEHTUCOSTDL7VA5JVXJ2LPZ7Z4NA5CNFSM4HWJY6M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXOF5DA.gif


Login page - determine host and port automatically

Currently defaults are localhost and 57772. They should be determined automatically based on current UI url (user still should have an ability to edit them if he so wishes)

And hide this advanced settings.

And add them to remote.html page
On Wed, Dec 28, 2016 at 2:23 PM, Eduard<EMAIL_ADDRESS>wrote:

And hide this advanced settings.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/intersystems-ru/RESTFormsUI/issues/19#issuecomment-269446558,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpyP3-0MBBjtZHAs_fzhAHM-H1M1_XYks5rMiOGgaJpZM4LWavA
.

Maybe location.hostname and location.port??? @eduard93
https://www.w3schools.com/js/js_window_location.asp


remove slash from labels in rational_expectations.rst

@arnavs @jlperla Ipynb translator does not acknowledge this special character in labels

Thanks @arnavs


concurrent tests

here's what i think we can do to implement concurrent tests
// in *-test.js file

parallelTest('long network request #1', () => {
  return makeRequest().then(response => expect(response).toEqual({success: true}));
});

parallelTest('long network reques #2t', () => {
  return makeRequest().then(response => expect(response).toEqual({success: true}));
});

// implementation

const parallelTest = (title, fn) => {
  let promise;
  try {
    // first run the test
    promise = fn();
  } catch (error) {
    promise = Promise.reject(error);
  }

  // then register a test with existing (already running) promise
  it(title, () => promise);
};

downside:

will break if any variables are shared between tests
can't use snapshots (it depends on global values like currently running test)

@cpojer @kittens

We should add test.concurrent to Jest with your implementation. This seems pretty sweet as an optional mode for things that do make network requests where people know about the downsides (we should document it as such). What do you say?

i agree, we should add it. It is a pretty dangerous construction, but i assume people will know what they're doing if they use it :)

It's not that dangerous actually if you exclusively use inline requires! We are in a really good position to provide a safe version of this:
test.concurrent('foo', () => {
  jest.resetModules();
  const React = require('react');
  const MyComponent = require('MyComponent');
  …
});

this way every concurrent test will have its own copy of the module registry, as long as they are all required immediately before scheduling async work.

@cpojer Any plans to include this in the docs? Came across test.concurrent() in the Yarn source and it was the first I'd heard of it.

This seems pretty sweet as an optional mode for things that do make network requests where people know about the downsides (we should document it as such

@cpojer @aaronabramov
What are the other downsides aside from what @aaronabramov already mentioned in his comment above?


Cleaning up the CSV based on recent changes

This consists of a series of commits, each of which cleans up typos, obsolete content, workarounds etc with explanation in the commit description.

/retest

/retest

/test ocs-operator-e2e-aws


go2entry

Trying to migrate a dictionary from an old installation, I came upon a go2entry global javascript function that does not work anymore. Is there a replacement?

It was apparently implemented in local js files, closing.

So, it turns out, I have no idea how to make this work. The implementation used to be this:
function go2entry(title) {   window.location =  "../?txt="+encodeURIComponent(title); }
But that triggers a

Blocked loading mixed active content "http://lexonomy.cjvt.si/furniture/public.css"

I saw, that screenful makes an api request to "../../../:dictID/entryread.json" with correct entry id. This request renders the xml using xslt on the backend and then just inserts the resulting html via $.html() inside the iframe. Should I just try and replicate this behaviour inside entry editor javascript?

The go2entry() function existed in an old beta version of Lexonomy. It took a string and caused Lexonomy to navigate to the first entry it could find that had that string as a headword.
In this version of Lexonomy you can create similar behaviour by making your XSL output this kind of HTML:
blabla

Any  elements in the HTML output of your XSL, which have the xref class, will be converted into clickable links which, when the user clicks them, will cause Lexonomy to do a search for the string in the data-text attribute.

Thanks, that worked.


conflict with sbt-coursier

steps
Use sbt-coursier
problem
There's been multiple reports on sbt 1.3.0 not working with sbt-coursier such as https://twitter.com/jaceklaskowski/status/1169296407733444609.
expectation
We use the shaded version of Coursier specifically so that we can coexist with sbt-coursier or any plugin that pulls in Coursier.

We're using shaded version of Coursier internal, so I am not sure what more we can do on sbt's end.

I confirm that sbt-coursier can't be used as is with sbt 1.3.x, because sbt ships with lm-coursier-shaded, and sbt-coursier relies on lm-coursier, that has the same API as lm-coursier-shaded, but exposes more internal stuff (that sbt-coursier uses, and that end up being shaded in lm-coursier-shaded).
As a workaround, people can rely on the coursier-based sbt launcher, that can be launched conveniently via a custom sbt-extras script. The coursier-based launcher detects that sbt-coursier is being used, and replaces lm-coursier-shaded by lm-coursier in that case.
But with sbt 1.3.x coursier support out-of-the-box, sbt-coursier doesn't bring much now. It can probably be dropped for most users.
That said, it can be interesting if users really want to test the very last coursier version. In that case, sbt-lm-coursier can be used instead of sbt-coursier, like
addSbtPlugin("io.get-coursier" % "sbt-lm-coursier" % "2.0.0-RC4")

@alexarchambault with coursier-2.x, instead of using sbt-extras script, it will be great if we could say coursier install sbt and it installs coursier-based sbt launcher. That will be very cool.

I'm very interested in coursier's most recent version for the fine grained version reconciliation. I've tried using sbt-lm-coursier for that as suggested by @alexarchambault and, though that does not cause errors, it does not provide the fine grained reconciliation. Specifically, while using sbt-lm-coursier I get this when adding a rule which shouldn't cause a failure:
lmcoursier.internal.shaded.coursier.error.conflict.StrictRule: Rule Strict(Set(ModuleMatcher(io.atomix:*)),Set(),true,true) ...

And using sbt-coursier I get no failure with that rule, but this with one that should cause failure:
coursier.error.conflict.StrictRule: Rule Strict(Set(ModuleMatcher(com.olegpy:*)),Set(),false,true,false) ...

Besides the obvious difference in number of parameters, one of these booleans, includeByDefault, is set to true in the first case, which causes all modules to be considered, except the ones excluded.

@LeonardMeyer Yes, downgrading the coursier plugin to 1.0.3 worked for me with Sbt 1.3.6. I added project/plugins.sbt with the following content:
addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.3")


Badge is Squished when viewed in PyPi

Describe the bug
Viewing the black package page on PyPi shows the Pypi badge squeezed; One would be unable to view contents of the badge.

Expected behavior
While on Github, it shows well:

To Reproduce
Visit:
Black PyPi
Black Github

It looks like the issue is that the version it's attempting to render the url https://black.readthedocs.io/en/stable/_static/pypi.svg, which currently has the version 19.10b1.dev0+g6bedb5c.d20191029, which just doesn't fit in the badge no matter where it's rendered:

I'm not sure why it's doing this but I don't think it's an issue with PyPI.


chore: Input morphing

Summary by CodeRabbit

New Features

Added new input widgets: Email, Password, Number, and Multiline.
Enhanced configuration options for phone and currency inputs.

Bug Fixes

Improved type handling for input properties, ensuring better validation and reliability.

Documentation

Updated widget exports for better modularity and usage across the application.

Chores

Introduced new constants to support the latest input widget types in the application.

[!WARNING]
Tests have not run on the HEAD a5c4b41eb615a6c655439f977fc0442cf0e0a237 yet
Mon, 26 Aug 2024 08:09:08 UTC

@jsartisan Please add unit test case if possible.

/build-deploy-preview skip-tests=true

Created the ticket - https://github.com/appsmithorg/appsmith/issues/35894


added entrymap, pixelstreaming, client server functions

For this I didn't make any changes with RapyutaSimulationPlugins, these changes were only on the turtlebot project side


Bump GPG key

Hi!
I'm using the fabulous nikolaik/python-nodejs:python3.8-nodejs16 docker image and am getting expired GPG key errors on a apt-get update command. Looks like this has happened before (more recently https://github.com/nikolaik/docker-python-nodejs/issues/18). Could we trigger a rebuilt by any chance? Thanks!

Stay fabulous! 🍸
I see the same thing
❯ docker run -it nikolaik/python-nodejs:python3.8-nodejs16 apt update
(...)
Err:5 https://dl.yarnpkg.com/debian stable InRelease
  The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging<EMAIL_ADDRESS>Reading package lists... Done
W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging<EMAIL_ADDRESS>E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.
(...)

The yarn repo needs new keys
❯ docker run -it nikolaik/python-nodejs:python3.8-nodejs16 bash
root@790b6012ca6a:/# wget -qO- https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
OK
root@790b6012ca6a:/# apt update
Get:1 http://deb.debian.org/debian buster InRelease [122 kB]
Get:2 http://deb.debian.org/debian-security buster/updates InRelease [34.8 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]
Get:4 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
Get:5 http://deb.debian.org/debian buster/main amd64 Packages [7909 kB]
Get:6 http://deb.debian.org/debian-security buster/updates/main amd64 Packages [425 kB]
Get:7 http://deb.debian.org/debian buster-updates/main amd64 Packages [8788 B]
Get:8 https://deb.nodesource.com/node_16.x bullseye InRelease [4586 B]
Get:9 https://dl.yarnpkg.com/debian stable/main amd64 Packages [10.9 kB]
Get:10 https://dl.yarnpkg.com/debian stable/main all Packages [10.9 kB]
Get:11 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages [773 B]
Fetched 8600 kB in 7s (1167 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
13 packages can be upgraded. Run 'apt list --upgradable' to see them.

 Done
Building dependency tree
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.

Thanks for reporting, this should be fixed now with the fresh rebuild. Pull the images or update your image digests accordingly 😊

I'm seeing this on nikolaik/python-nodejs:python3.6-nodejs12 as well


(WIP) Fixed a problem not to be able to parse input value which is type of dict in array in some YAQL operators.

Abstract
This fixes a problem not to be able to parse data which is typed dict(etc) in array in some YAQL operators by converting input data-structure from unhashable value to hashable one. (c.f. #176)
Problem
Orquesta couldn't handle dict in array typed value in some yqal operators (e.g. distinct) as below.
username@host:~$ cd st2
username@host:~/st2$ source virtualenv/bin/activate; python

>>> from orquesta.expressions import base as expr_base
>>>
>>> data = {'val': [{'a': 1}, {'b': 2}, {'a': 1}]}
>>>
>>> expr_base.evaluate("<% ctx(val) %>", data)
[{'a': 1}, {'b': 2}, {'a': 1}]
>>> expr_base.evaluate("<% ctx(val).distinct() %>", data)
(TypeError exception will be occurred)

Execution Result

Cause & Measure
In some YAQL operators (e.g. distinct) refer to hash value of input data to identify it. And the openstack/YAQL library that Orquesta uses wraps those input value using utils.convert_output_data to prevent TypeError exception when these operator's implementation try to refer to input hash value. Thus, we can handle these value in the distinct operator like following. And this PR applies it to the Orquesta.
(c.f.  https://github.com/openstack/yaql/commit/67d58bc17fcbba532764091dec0a68a4c9dbb180)
username@host:~$ cd st2
username@host:~/st2$ source virtualenv/bin/activate; python

>>> import yaql
>>>
>>> engine = yaql.language.factory.YaqlFactory().create()
>>>
>>> data = {'val': [{'a': 1}, {'b': 2}, {'a': 1}]}
>>>
>>> engine('$.val').evaluate(data=data)
[{'a': 1}, {'b': 2}, {'a': 1}]
>>> engine('$.val.distinct()').evaluate(data=data)
[{'a': 1}, {'b': 2}]
>>>

Execution Result

I realized some other problems (other than #193) have to be cared so I amended title as WIP.

Thank you very much for your review and I appreciate your clear instructions!

Codecov Report

Merging #191 into master will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #191      +/-   ##
==========================================
- Coverage   94.04%   94.02%   -0.02%
==========================================
  Files          41       41
  Lines        2739     2730       -9
  Branches      542      540       -2
==========================================
- Hits         2576     2567       -9
  Misses        100      100
  Partials       63       63

Impacted Files
Coverage Δ

orquesta/expressions/functions/workflow.py
95.83% <100.00%> (+0.05%)
:arrow_up:

orquesta/expressions/yql.py
90.09% <100.00%> (+0.09%)
:arrow_up:

orquesta/specs/native/v1/models.py
97.95% <0.00%> (-0.07%)
:arrow_down:

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 419a4a9...24063c5. Read the comment docs.


Fix portage provider to support version with character

I ran into an issue where chef 12 installs openssl 1.0.2d even if it's already installed. It doesn't support the character on the version, d.
According to man 5 ebuild

Versions  are  normally made up of two or three numbers separated by periods, such as 1.2 or 4.5.2.  This string may be followed by a character such as 1.2a or 4.5.2z.  Note that this letter is not meant to indicate alpha,  beta,  etc...  status.   For  that,  use  the  optional  suffix;  either  _alpha,  _beta,  _pre (pre-release),  _rc  (release candidate), or _p (patch).
I added a test which failed before I added the fix. bundle exec rspec spec/unit/provider/package/portage_spec.rb  shows passing tests.
This is my first PR on chef so let me know if I need to change anything.

@chef/client-core needs review

👍

👍

👍


chore: croc-hunter-jenkinsx to 0.0.80

chore: Promote croc-hunter-jenkinsx to version 0.0.80

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

Needs approval from an approver in each of these files:

OWNERS

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


[release-1.5] Fix the webhook integration tests in postsubmit

Fixes #21574
Still running the tests against the helm charts locally, waiting for result.. If they pass, will remove the hold

Tests pass locally against helm charts, removing hold


clean up unused distributed sampler logic in trainer

What does this PR do?
Follow up to #5743
The kwargs needed for the distributed sampler are provided by the parallel plugins. The unused logic in the trainer is obsolete.
We keep the property in the trainer for backward compatibility and ease of access internally, and reference the property in the training type plugin.
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified
[x] Check that target branch and milestone match!

Did you have fun?
Make sure you had fun coding 🙃

Deleted code is the best code 💃

https://twitter.com/fishnets88/status/1360865122969923584?s=19


CLOUDSTACK-9005: Modifying tearDown function

Modifying tearDown function to check if data volume is in detached state before deleting the volume

LGTM  Based on code understanding
One line change  if attribute is there then proceed to cleanup  if hasattr(self, "data_volume_created"):

2 lgtm but no test report, will execute

Test Result:
Storage and Snapshot Limit ...
Ran 1 test in 970.317s
OK

LGTM

@remibergsma can you please merge this in?  thanks, Raja