Question about p_sample :)

Hi!
Always thank you for your great codes that you provide!
Anyway, there are 2 points that I can't understand.

Why do you use posterior mean and variance on reverse step? ( in p_sample function )
I expected using the equation (11) of original DDPM paper, but I think it is not on this code.
Can you explain this for me ? :)

    def p_mean_variance(self, x, t, x_self_cond = None, clip_denoised = True):
        preds = self.model_predictions(x, t, x_self_cond)
        x_start = preds.pred_x_start

        if clip_denoised:
            x_start.clamp_(-1., 1.)

        model_mean, posterior_variance, posterior_log_variance = self.q_posterior(x_start = x_start, x_t = x, t = t)
        return model_mean, posterior_variance, posterior_log_variance, x_start

    @torch.no_grad()
    def p_sample(self, x, t: int, x_self_cond = None, clip_denoised = True):
        b, *_, device = *x.shape, x.device # b: 4
        batched_times = torch.full((x.shape[0],), t, device = x.device, dtype = torch.long)
        model_mean, _, model_log_variance, x_start = self.p_mean_variance(x = x, # Isotrophic Normal Gaussian
                                                                          t = batched_times,
                                                                          x_self_cond = x_self_cond,
                                                                          clip_denoised = clip_denoised)  #  <------ This part!
        noise = torch.randn_like(x) if t > 0 else 0. # no noise if t == 0
        pred_img = model_mean + (0.5 * model_log_variance).exp() * noise
        return pred_img, x_start

Can you explain the intent of (0.5 * model_log_variance).exp() on `pred_img = model_mean + (0.5 * model_log_variance).exp() * noise in p_sample_loop?

The full code is as below:
    @torch.no_grad()
    def p_sample(self, x, t: int, x_self_cond = None, clip_denoised = True):
        b, *_, device = *x.shape, x.device
        batched_times = torch.full((x.shape[0],), t, device = x.device, dtype = torch.long)
        model_mean, _, model_log_variance, x_start = self.p_mean_variance(x = x, # Isotrophic Normal Gaussian
                                                                          t = batched_times,
                                                                          x_self_cond = x_self_cond,
                                                                          clip_denoised = clip_denoised)
        noise = torch.randn_like(x) if t > 0 else 0. # no noise if t == 0
        pred_img = model_mean + (0.5 * model_log_variance).exp() * noise  # <------------ This part!
        return pred_img, x_start

Thanks for a great job from the authors!
I got the same question for p_sample
  def predict_start_from_noise(self, x_t, t, noise):
      return (extract(self.sqrt_recip_alphas_cumprod, t, x_t.shape) * x_t -
              extract(self.sqrt_recipm1_alphas_cumprod, t, x_t.shape) * noise)

I cannot understand the equation above, could you please figure out where is it from?

I got the same question
In my mind, posterior_variance is the one that we need.
as 'pred_img = x_start + posterior_variance * noise'

1: Step 4 from Algorithm, but using equivalence from formula 9,7.
Equation 9 right side of mean_tilde_t( ... , HERE) and replacing mean_tilde_t with 7
I tested equation 11 and came across stability issues. I think that small numbers cause some floating point errors.
This also enables the clamping of the image.
2: There is a commentary somewhere "# below: log calculation clipped because the posterior variance is 0 at the beginning of the diffusion chain". I can't remember if this comment is from this repository. This is probably again a numerical fix.
Note: sqrt(posterior_variance) == exp(0.5*log(posterior_variance))
posterior_variance stores the square of σ


feat: allow function for config.tarball_url_redirect

Type: feature
The following has been addressed in the PR:

There is a related issue? https://github.com/verdaccio/monorepo/issues/250
Unit or Functional tests are included in the PR: Yes

Description:
Adds ability to optionally specify a function for config.tarball_url_redirect, as discussed here: https://github.com/verdaccio/verdaccio/pull/1688#issuecomment-619314369

Hi @gordlea, thanks for implementing the feature. I'm busy on a project, but I will get this reviewed this week.


The issues doesn't have tags

I would like to solve some issues but I'm not sure if the picked issue is a good one to fix, because no tags are provided.

This is objectively untrue - there are 15 issues labeled "good first issue", for example.


Added some basic instructions for building and running the project.

Hey, I really love your project! I needed to regenerate the auto completion for nwscript.nss so I embarked on a journey to figure out Web Languages (tm). The result is this condensed list of steps needed to build, regenerate, and package.

PS I am far from an expert, in fact my first exposure to using npm was approximately one hour ago, so I might be misunderstanding or simply missing some steps. Please feel free to correct as you see fit!


Typescript "error underlining" and "problems console" completely broken

VSCode Version: 1.6.0-insider (90dda)
OS Version: Windows 10 x64

Steps to Reproduce:

Open any .ts file
Write any type of garbage
The wriggly red underline is gone, and the "problems" console shows nothing wrong
Try to compile to .js, receive a sh*tton of errors

I'm also using Typescript@next, which is 2.1.0-dev.20160921

Can you provide me with code I can copy and paste to reproduce the problem?
Does the problem exist on TypeScript 2.0.2?

happens with either typescript@next or stable. it doesn't work with ALL .ts files, my tsconfig (didn't change it, it just stopped working):
{
  "compilerOptions": {
    "target": "es5",
    "module": "system",
    "preserveConstEnums": true,
    "lib": [
      "dom",
      "es2015",
      "es5"
    ],
    "noImplicitAny": true,
    "sourceMap": false,
    "moduleResolution": "node",
    "inlineSourceMap": false
  },
  "exclude": [
    "test",
    "system",
    "stylesheets",
    "node_modules",
    "modules",
    "keys",
    "configs",
    "bower_components",
    "blog",
    "jspm_packages",
    "application",
    "api",
    ".vscode",
    ".tscache",
    ".sass-cache"
  ]
}

tested with vscode 1.5.3, and works properly, regardless of typescript version (2.0.3 or next)

@pocesar than you for the information and for providing your settings and tsconfig.json file. Couple additional questions.

Can you try running 1.6-Insiders without any extensions? You can do that by running code with code <your folder name> --disable-extensions
Are the settings files the same between 1.5.3 and 1.6-Insiders?
Can you provide me with the typescript code I can copy and paste to reproduce the issue on my end?

@dbaeumer can I get your thoughts here? It looks like we may have introduced a breaking change between 1.5.3 and 1.6?
Op tested with 1.6-Insiders originally and saw problems when compiling. He switched back to 1.5.3 and the problems go away. He tried multiple typescript versions.

@waderyan

yes, no extensions are enabled
yes, same settings
the file is in a private repo, can I email you it?

Yes<EMAIL_ADDRESS>

sent

@pocesar @waderyan this is actually caused by the Electron update we did on 1.6 insider :-). The Electron version we use in 1.6 has a different implementation of fs.realpath which causes problems in the tsserver. I added a 'work around' on our end. However that only went in last Friday and is available this week.

@pocesar can you confirm this works for you using the Insider build?

@waderyan I'm not being able to test the insiders because of #12503

@pocesar does that happened all the time. If so can you share our workspace so that we can investigate.

@dbaeumer it's not constant, but it definitely is 9 out of 10. when I do manage to be able to load vscode, when the editor area get focus, it freezes.

latest version of vscode insiders (c94c8) is showing the wriggly lines and the "problems" tab is displaying the errors, but still randomly getting freezes

OK. Will close this one. Lets followup regarding the freezes in #12503


tests: Fix unused message_id parameter in tests.

Various backend tests use the PATCH /messages/{msg_id} endpoint. For that endpoint, the message ID is encoded in the URL path and ignored if provided as a parameter in the the query.
Verified that the tests were providing the same message ID to both the path and then removed the ignored parameter in the query.
Noticed this issue when working on next steps for implementing ignored_parameter_unsupported for json_success and JsonableError and also this recent commit that fixed a the same issue in test_message_edit.py.

Nice, merged, thanks for cleaning these up @laurynmm!  I guess I should have thought to audit other test files for this issue :)

@timabbott No problem! I'll have a few more of these as I go through the test failures from adding the ignored_parameters_unsupported to the responses. I figured it would be good, for reviewing purposes, to group them by the endpoint and parameter that's being used.

Yeah I think that makes sense; at least at the commit level (feel free to
put a few like this in a single PR).
-Tim Abbott (mobile)
On Mon, Feb 21, 2022, 09:57 Lauryn Menard @.***> wrote:

@timabbott https://github.com/timabbott No problem! I'll have a few
more of these as I go through the test failures from adding the
ignored_parameters_unsupported to the responses. I figured it would be
good, for reviewing purposes, to group them by the endpoint and parameter
that's being used.
—
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/pull/21207#issuecomment-1047118501, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAU6NWSFW7OSWDF5LXWH46TU4J4IXANCNFSM5O7A7A7A
.
You are receiving this because you were mentioned.Message ID:
@.***>


Poor Fingerprinting Due to PIDs

One of the best features of Sentry is its fingerprinting - with exceptions for example it uses the stack trace and exception to fingerprint the message so that doesn't hammer you with lots of instances of the same error. Unfortunately it seems this doesn't work so well with logger_sentry as exceptions get sent to Logger.error with the PID as part of the text message.
Do you have any strategy for dealing with this? I want to keep Logger.ErrorHandler enabled, but don't want it sending exceptions with PIDs to Sentry. If you don't have a better solution would you take a PR that optionally strips PIDs out of the beginning of the message?
This is a partial example of the kind of message I'm talking about:
(ErlangError) Erlang error: "#PID<0.9201.0> running SmartErp.Web.Endpoint (cowboy_protocol) terminated\nServer: cal.smarterp.io:80 (h

Currently, we don't have a universal solution to the problem, because the uncaught exception's error message threw by Erlang runtime varies a lot. For example, here your message has a PID info, but node info and others can also exist in other error messages. These messages are hard to classify, so we let the user to decide how to generate fingerprints according to the error message.
You can custom your fingerprints here: https://github.com/Tubitv/logger_sentry/blob/master/lib/sentry.ex#L215-L220, for example, in your case here, you can strip the PIDs and return the new whole message as a fingerprint or extract some keywords like [SmartErp.Web.Endpoint] as fingerprints.


When Using docker-compose up mysql MySQL Doesn't Start

Info:

Docker version ($ docker --version): Docker version 17.06.1-ce, build 874a737
Laradock commit ($ git rev-parse HEAD): 801ccd47d22999d087896045cdfd1d7316212174
System info (Mac, PC, Linux): Mac
System info disto/version: macOS Sierra 10.12.6 (16G29)

Issue:

When running docker-compose up mysql the container fails to start.

Expected behavior:
The loading of mysql container.

Reproduce:
After updating from the git repo my mysql failed to start. I cleared my system of volumes, containers and images. I followed https://github.com/laradock/laradock/issues/1110 that solution to no avail.

Relevant Code:
~/D/laradock ❯❯❯ docker-compose up mysql                                                                                ⏎ master ✭ ✱
Starting laradock_mysql_1 ...
Starting laradock_mysql_1 ... done
Attaching to laradock_mysql_1
mysql_1                | 2017-09-10T20:03:45.549204Z 0 [Note] Basedir set to /usr/
mysql_1                | 2017-09-10T20:03:45.549436Z 0 [Warning] The syntax '--symbolic-links/-s' is deprecated and will be removed in a future release
mysql_1                | 2017-09-10T20:03:45.549468Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
mysql_1                | 2017-09-10T20:03:45.550182Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
mysql_1                | 2017-09-10T20:03:45.550227Z 0 [Note] /usr/sbin/mysqld (mysqld 8.0.2-dmr) starting as process 1 ...
mysql_1                | 2017-09-10T20:03:45.559430Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
mysql_1                | 2017-09-10T20:03:45.563093Z 0 [Note] InnoDB: Using Linux native AIO
mysql_1                | 2017-09-10T20:03:45.563222Z 0 [Note] Plugin 'FEDERATED' is disabled.
mysql_1                | 2017-09-10T20:03:45.567395Z 1 [Note] Starting upgrade on data directory.
mysql_1                | 2017-09-10T20:03:45.568189Z 1 [Note] InnoDB: PUNCH HOLE support available
mysql_1                | 2017-09-10T20:03:45.568220Z 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_1                | 2017-09-10T20:03:45.568224Z 1 [Note] InnoDB: Uses event mutexes
mysql_1                | 2017-09-10T20:03:45.568227Z 1 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql_1                | 2017-09-10T20:03:45.568230Z 1 [Note] InnoDB: Compressed tables use zlib 1.2.3
mysql_1                | 2017-09-10T20:03:45.568449Z 1 [Note] InnoDB: Number of pools: 1
mysql_1                | 2017-09-10T20:03:45.568547Z 1 [Note] InnoDB: Using CPU crc32 instructions
mysql_1                | 2017-09-10T20:03:45.570649Z 1 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
mysql_1                | libnuma: Warning: /sys not mounted or invalid. Assuming one node: No such file or directory
mysql_1                | mbind: Operation not permitted
mysql_1                | mbind: Operation not permitted
mysql_1                | mbind: Operation not permitted
mysql_1                | mbind: Operation not permitted
mysql_1                | 2017-09-10T20:03:45.591187Z 1 [Note] InnoDB: Completed initialization of buffer pool
mysql_1                | 2017-09-10T20:03:45.593939Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql_1                | 2017-09-10T20:03:45.622880Z 1 [ERROR] InnoDB: Upgrade after a crash is not supported. This redo log was created with MySQL 5.7.17. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html
mysql_1                | 2017-09-10T20:03:45.622917Z 1 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
mysql_1                | 2017-09-10T20:03:46.232623Z 1 [ERROR] Failed to initialize DD Storage Engine
mysql_1                | 2017-09-10T20:03:46.234344Z 0 [ERROR] Data Dictionary initialization failed.
mysql_1                | 2017-09-10T20:03:46.234443Z 0 [ERROR] Aborting
mysql_1                | 2017-09-10T20:03:46.234467Z 0 [Note] Binlog end
mysql_1                | 2017-09-10T20:03:46.234810Z 0 [Note] Shutting down plugin 'InnoDB'
mysql_1                | 2017-09-10T20:03:46.234906Z 0 [Note] Shutting down plugin 'MyISAM'
mysql_1                | 2017-09-10T20:03:46.234923Z 0 [Note] Shutting down plugin 'CSV'
mysql_1                | 2017-09-10T20:03:46.238592Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
mysql_1                |
laradock_mysql_1 exited with code 1

Quick update when I drop the MySQL down to version 5.7 it builds and functions properly.
I'm not sure what step might be missing for me as the database should not exist as everything was cleared unless someone could point me in a direction regarding phantom databases in docker (just my lack of knowledge potentially).

Just for clarity, did you rebuild mysql container with docker-compose up --build or docker-compose build after upgrading to v8? Sometimes I catch myself spending hours when it's as simple at that :).

I've tried docker-compose build as well as docker-compose up --build both with no avail. Like I said above I was able to get it working, just not with MySQL 8.0.

I have the same problem, and I use docker-compose build mysql,the problem is still there.
'docker-compose down' many times, but still can't be solved.
``WARNING: Image for service mysql was built because it did not already exist. To rebuild this image you must use docker-compose build or docker-compose up --build.
Creating laradock_mysql_1 ...
Creating laradock_mysql_1 ... done
Attaching to laradock_mysql_1
mysql_1                | 2017-09-30T23:46:36.415592Z 0 [Note] Basedir set to /usr/
mysql_1                | 2017-09-30T23:46:36.415723Z 0 [Warning] The syntax '--symbolic-links/-s' is deprecated and will be removed in a future release
mysql_1                | 2017-09-30T23:46:36.415752Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They w
ill be merged with strict mode in a future release.
mysql_1                | 2017-09-30T23:46:36.419196Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
mysql_1                | 2017-09-30T23:46:36.419233Z 0 [Note] /usr/sbin/mysqld (mysqld 8.0.3-rc-log) starting as process 1 ...
mysql_1                | 2017-09-30T23:46:36.430072Z 0 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL se
rver acts as a master and has his hostname changed!! Please use '--log-bin=441b44a5a18b-bin' to avoid this problem.
mysql_1                | 2017-09-30T23:46:36.442964Z 0 [Note] InnoDB: Using Linux native AIO
mysql_1                | 2017-09-30T23:46:36.443301Z 0 [Note] Plugin 'FEDERATED' is disabled.
mysql_1                | 2017-09-30T23:46:36.445645Z 1 [ERROR] Failed to find valid data directory.
mysql_1                | 2017-09-30T23:46:36.445903Z 0 [ERROR] Data Dictionary initialization failed.
mysql_1                | 2017-09-30T23:46:36.445985Z 0 [ERROR] Aborting
mysql_1                | 2017-09-30T23:46:36.446011Z 0 [Note] Binlog end
mysql_1                | 2017-09-30T23:46:36.447956Z 0 [Note] Shutting down plugin 'InnoDB'
mysql_1                | 2017-09-30T23:46:36.448022Z 0 [Note] Shutting down plugin 'MyISAM'
mysql_1                | 2017-09-30T23:46:36.448058Z 0 [Note] Shutting down plugin 'CSV'
mysql_1                | 2017-09-30T23:46:36.450846Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
mysql_1                |
laradock_mysql_1 exited with code 1
`

Got similar issue after upgrade the laravel to 5.5, after run docker-compose start mysql:
ysql_1                | 2017-10-31T13:21:56.763281Z 0 [Note] Server socket created on IP: '<IP_ADDRESS>'.
mysql_1                | 2017-10-31T13:21:56.763329Z 0 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address
mysql_1                | 2017-10-31T13:21:56.763335Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
mysql_1                | 2017-10-31T13:21:56.763358Z 0 [ERROR] Aborting
mysql_1                | 2017-10-31T13:21:56.763456Z 0 [Note] InnoDB: FTS optimize thread exiting.
my

I solved this problem. This is because of data folder. I was running it using mysql 5.7 then abort it in the middle of building, and change the mysql to 8.0
Try this step.
Try remove the docker image. List all images using docker images then remove the mysql & laradock mysql using docker rmi imagename. Dont forget remove the docker volume using docker volume rm volumename
Also go to cd ~/.laradock/data remove the mysql folder.
Then try docker-compose up mysql for debuging. If no errors, you could try docker-compose up -d mysql

have same issue here
2019-04-16T15:18:21.991726Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-04-16T15:18:21.991796Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-04-16T15:18:21.991801Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-04-16T15:18:22.015022Z 0 [Note] mysqld (mysqld 5.7.25) starting as process 1 ...
2019-04-16T15:18:22.061018Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-04-16T15:18:22.061086Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-04-16T15:18:22.061094Z 0 [Note] InnoDB: Uses event mutexes
2019-04-16T15:18:22.061098Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-04-16T15:18:22.061101Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-04-16T15:18:22.061104Z 0 [Note] InnoDB: Using Linux native AIO
2019-04-16T15:18:22.074473Z 0 [Note] InnoDB: Number of pools: 1
2019-04-16T15:18:22.091503Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-04-16T15:18:22.102197Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-04-16T15:18:22.144845Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-16T15:18:22.155488Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-04-16T15:18:22.222946Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-04-16 15:18:22 0x7f2fe6fd7740  InnoDB: Assertion failure in thread<PHONE_NUMBER>61280 in file ut0ut.cc line 942
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:18:22 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0x56466953d81c]
mysqld(handle_fatal_signal+0x479)[0x564668e68879]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7f2fe6bb40e0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f2fe5340fff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f2fe534242a]
mysqld(+0x628efb)[0x564668e3eefb]
mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x56466970db9d]
mysqld(+0xfa4901)[0x5646697ba901]
mysqld(+0xfa4f38)[0x5646697baf38]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x5646697c40f0]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x56466977916e]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x5646697483ba]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x5646696ebd33]
mysqld(+0x62806f)[0x564668e3e06f]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x5646696b8bed]
mysqld(+0xd6e963)[0x564669584963]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x564668eb359f]
mysqld(+0xb14e16)[0x56466932ae16]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x56466932e000]
mysqld(+0x64af7e)[0x564668e60f7e]
mysqld(_Z11mysqld_mainiPPc+0xc71)[0x564668e62b41]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f2fe532e2e1]
mysqld(_start+0x2a)[0x564668e5921a]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2019-04-16T15:18:49.941818Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-04-16T15:18:49.941965Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-04-16T15:18:49.941974Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-04-16T15:18:49.948786Z 0 [Note] mysqld (mysqld 5.7.25) starting as process 1 ...
2019-04-16T15:18:49.958190Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2019-04-16T15:18:49.961586Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-04-16T15:18:49.961743Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-04-16T15:18:49.961778Z 0 [Note] InnoDB: Uses event mutexes
2019-04-16T15:18:49.961958Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-04-16T15:18:49.962119Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-04-16T15:18:49.962407Z 0 [Note] InnoDB: Using Linux native AIO
2019-04-16T15:18:49.963448Z 0 [Note] InnoDB: Number of pools: 1
2019-04-16T15:18:49.965103Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-04-16T15:18:49.968204Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-04-16T15:18:49.987656Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-16T15:18:49.991478Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-04-16T15:18:50.036842Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-04-16 15:18:50 0x7fc1c6738740  InnoDB: Assertion failure in thread<PHONE_NUMBER>75712 in file ut0ut.cc line 942
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:18:50 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0x558b0c89f81c]
mysqld(handle_fatal_signal+0x479)[0x558b0c1ca879]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7fc1c63150e0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7fc1c4aa1fff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fc1c4aa342a]
mysqld(+0x628efb)[0x558b0c1a0efb]
mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x558b0ca6fb9d]
mysqld(+0xfa4901)[0x558b0cb1c901]
mysqld(+0xfa4f38)[0x558b0cb1cf38]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x558b0cb260f0]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x558b0cadb16e]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x558b0caaa3ba]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x558b0ca4dd33]
mysqld(+0x62806f)[0x558b0c1a006f]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x558b0ca1abed]
mysqld(+0xd6e963)[0x558b0c8e6963]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x558b0c21559f]
mysqld(+0xb14e16)[0x558b0c68ce16]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x558b0c690000]
mysqld(+0x64af7e)[0x558b0c1c2f7e]
mysqld(_Z11mysqld_mainiPPc+0xc71)[0x558b0c1c4b41]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fc1c4a8f2e1]
mysqld(_start+0x2a)[0x558b0c1bb21a]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2019-04-16T15:21:03.799026Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-04-16T15:21:03.799113Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-04-16T15:21:03.799120Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-04-16T15:21:03.811033Z 0 [Note] mysqld (mysqld 5.7.25) starting as process 1 ...
2019-04-16T15:21:03.822158Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2019-04-16T15:21:03.825767Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-04-16T15:21:03.826139Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-04-16T15:21:03.826464Z 0 [Note] InnoDB: Uses event mutexes
2019-04-16T15:21:03.826690Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-04-16T15:21:03.826965Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-04-16T15:21:03.827107Z 0 [Note] InnoDB: Using Linux native AIO
2019-04-16T15:21:03.828222Z 0 [Note] InnoDB: Number of pools: 1
2019-04-16T15:21:03.829260Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-04-16T15:21:03.832726Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-04-16T15:21:03.855160Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-16T15:21:03.860606Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-04-16T15:21:03.903299Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-04-16 15:21:03 0x7fd7e5f19740  InnoDB: Assertion failure in thread<PHONE_NUMBER>11552 in file ut0ut.cc line 942
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:21:03 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0x5561ea3a981c]
mysqld(handle_fatal_signal+0x479)[0x5561e9cd4879]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7fd7e5af60e0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7fd7e4282fff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fd7e428442a]
mysqld(+0x628efb)[0x5561e9caaefb]
mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x5561ea579b9d]
mysqld(+0xfa4901)[0x5561ea626901]
mysqld(+0xfa4f38)[0x5561ea626f38]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x5561ea6300f0]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x5561ea5e516e]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x5561ea5b43ba]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x5561ea557d33]
mysqld(+0x62806f)[0x5561e9caa06f]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x5561ea524bed]
mysqld(+0xd6e963)[0x5561ea3f0963]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x5561e9d1f59f]
mysqld(+0xb14e16)[0x5561ea196e16]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x5561ea19a000]
mysqld(+0x64af7e)[0x5561e9cccf7e]
mysqld(_Z11mysqld_mainiPPc+0xc71)[0x5561e9cceb41]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fd7e42702e1]
mysqld(_start+0x2a)[0x5561e9cc521a]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

have try solutions above, but not fix my problem

I came here looking for a solution to the mysql container exiting when started. https://github.com/laradock/laradock/issues/1138#issuecomment-333332386 fixed this for me. Just leaving this here for anyone that comes here like me. This was one of the results when I literally Googled the error message.

I solved this problem. This is because of data folder. I was running it using mysql 5.7 then abort it in the middle of building, and change the mysql to 8.0. here some explanation #1138 (comment)
Try this step.
Try remove the docker image. List all images using docker images then remove the mysql & laradock mysql using docker rmi imagename. Dont forget remove the docker volume using docker volume rm volumename
Also go to cd ~/.laradock/data remove the mysql folder.
Then try docker-compose up mysql for debuging. If no errors, you could try docker-compose up -d mysql

your solution is still work until 2019

have same issue here
2019-04-16T15:18:21.991726Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-04-16T15:18:21.991796Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-04-16T15:18:21.991801Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-04-16T15:18:22.015022Z 0 [Note] mysqld (mysqld 5.7.25) starting as process 1 ...
2019-04-16T15:18:22.061018Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-04-16T15:18:22.061086Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-04-16T15:18:22.061094Z 0 [Note] InnoDB: Uses event mutexes
2019-04-16T15:18:22.061098Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-04-16T15:18:22.061101Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-04-16T15:18:22.061104Z 0 [Note] InnoDB: Using Linux native AIO
2019-04-16T15:18:22.074473Z 0 [Note] InnoDB: Number of pools: 1
2019-04-16T15:18:22.091503Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-04-16T15:18:22.102197Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-04-16T15:18:22.144845Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-16T15:18:22.155488Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-04-16T15:18:22.222946Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-04-16 15:18:22 0x7f2fe6fd7740  InnoDB: Assertion failure in thread<PHONE_NUMBER>61280 in file ut0ut.cc line 942
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:18:22 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0x56466953d81c]
mysqld(handle_fatal_signal+0x479)[0x564668e68879]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7f2fe6bb40e0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f2fe5340fff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f2fe534242a]
mysqld(+0x628efb)[0x564668e3eefb]
mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x56466970db9d]
mysqld(+0xfa4901)[0x5646697ba901]
mysqld(+0xfa4f38)[0x5646697baf38]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x5646697c40f0]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x56466977916e]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x5646697483ba]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x5646696ebd33]
mysqld(+0x62806f)[0x564668e3e06f]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x5646696b8bed]
mysqld(+0xd6e963)[0x564669584963]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x564668eb359f]
mysqld(+0xb14e16)[0x56466932ae16]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x56466932e000]
mysqld(+0x64af7e)[0x564668e60f7e]
mysqld(_Z11mysqld_mainiPPc+0xc71)[0x564668e62b41]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f2fe532e2e1]
mysqld(_start+0x2a)[0x564668e5921a]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2019-04-16T15:18:49.941818Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-04-16T15:18:49.941965Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-04-16T15:18:49.941974Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-04-16T15:18:49.948786Z 0 [Note] mysqld (mysqld 5.7.25) starting as process 1 ...
2019-04-16T15:18:49.958190Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2019-04-16T15:18:49.961586Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-04-16T15:18:49.961743Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-04-16T15:18:49.961778Z 0 [Note] InnoDB: Uses event mutexes
2019-04-16T15:18:49.961958Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-04-16T15:18:49.962119Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-04-16T15:18:49.962407Z 0 [Note] InnoDB: Using Linux native AIO
2019-04-16T15:18:49.963448Z 0 [Note] InnoDB: Number of pools: 1
2019-04-16T15:18:49.965103Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-04-16T15:18:49.968204Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-04-16T15:18:49.987656Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-16T15:18:49.991478Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-04-16T15:18:50.036842Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-04-16 15:18:50 0x7fc1c6738740  InnoDB: Assertion failure in thread<PHONE_NUMBER>75712 in file ut0ut.cc line 942
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:18:50 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0x558b0c89f81c]
mysqld(handle_fatal_signal+0x479)[0x558b0c1ca879]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7fc1c63150e0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7fc1c4aa1fff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fc1c4aa342a]
mysqld(+0x628efb)[0x558b0c1a0efb]
mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x558b0ca6fb9d]
mysqld(+0xfa4901)[0x558b0cb1c901]
mysqld(+0xfa4f38)[0x558b0cb1cf38]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x558b0cb260f0]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x558b0cadb16e]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x558b0caaa3ba]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x558b0ca4dd33]
mysqld(+0x62806f)[0x558b0c1a006f]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x558b0ca1abed]
mysqld(+0xd6e963)[0x558b0c8e6963]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x558b0c21559f]
mysqld(+0xb14e16)[0x558b0c68ce16]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x558b0c690000]
mysqld(+0x64af7e)[0x558b0c1c2f7e]
mysqld(_Z11mysqld_mainiPPc+0xc71)[0x558b0c1c4b41]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fc1c4a8f2e1]
mysqld(_start+0x2a)[0x558b0c1bb21a]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2019-04-16T15:21:03.799026Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-04-16T15:21:03.799113Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-04-16T15:21:03.799120Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-04-16T15:21:03.811033Z 0 [Note] mysqld (mysqld 5.7.25) starting as process 1 ...
2019-04-16T15:21:03.822158Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2019-04-16T15:21:03.825767Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-04-16T15:21:03.826139Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-04-16T15:21:03.826464Z 0 [Note] InnoDB: Uses event mutexes
2019-04-16T15:21:03.826690Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-04-16T15:21:03.826965Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-04-16T15:21:03.827107Z 0 [Note] InnoDB: Using Linux native AIO
2019-04-16T15:21:03.828222Z 0 [Note] InnoDB: Number of pools: 1
2019-04-16T15:21:03.829260Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-04-16T15:21:03.832726Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-04-16T15:21:03.855160Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-16T15:21:03.860606Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-04-16T15:21:03.903299Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-04-16 15:21:03 0x7fd7e5f19740  InnoDB: Assertion failure in thread<PHONE_NUMBER>11552 in file ut0ut.cc line 942
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:21:03 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0x5561ea3a981c]
mysqld(handle_fatal_signal+0x479)[0x5561e9cd4879]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7fd7e5af60e0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7fd7e4282fff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fd7e428442a]
mysqld(+0x628efb)[0x5561e9caaefb]
mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x5561ea579b9d]
mysqld(+0xfa4901)[0x5561ea626901]
mysqld(+0xfa4f38)[0x5561ea626f38]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x5561ea6300f0]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x5561ea5e516e]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x5561ea5b43ba]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x5561ea557d33]
mysqld(+0x62806f)[0x5561e9caa06f]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x5561ea524bed]
mysqld(+0xd6e963)[0x5561ea3f0963]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x5561e9d1f59f]
mysqld(+0xb14e16)[0x5561ea196e16]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x5561ea19a000]
mysqld(+0x64af7e)[0x5561e9cccf7e]
mysqld(_Z11mysqld_mainiPPc+0xc71)[0x5561e9cceb41]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fd7e42702e1]
mysqld(_start+0x2a)[0x5561e9cc521a]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

have try solutions above, but not fix my problem

What your VPS configuration ?

In my case, i crash to mariadb data in ~/.laradock/data/mariadb so solution is remove or rename data folder and restart laradock
Ref: https://devhoi.com/threads/laradock-on-mac-error-unknown-unsupported-storage-engine-innodb.28/

When we remove folder data, our data will be lost. So this is not a suitable solution

In my case, I changed the DATA_PATH_HOST environment variable in the laradock .env file to something different.
e.g.
# Before
DATA_PATH_HOST=~/.laradock/data

# After
DATA_PATH_HOST=~/.laradock/data/project_name

I suspect this happened because I started a new project with laradock when I already had another project using laradock on my machine. There was already a mysql data folder from my other project stored at ~/.laradock/data/mysql. Because I didn't change the DATA_PATH_HOST environment variable on my new project the mysql container on my new project tried to use to same data directory and because it was already used by my other project it wasn't able to initialize properly.

In my case, I changed the DATA_PATH_HOST environment variable in the laradock .env file to something different.
e.g.
# Before
DATA_PATH_HOST=~/.laradock/data

# After
DATA_PATH_HOST=~/.laradock/data/project_name

I suspect this happened because I started a new project with laradock when I already had another project using laradock on my machine. There was already a mysql data folder from my other project stored at ~/.laradock/data/mysql. Because I didn't change the DATA_PATH_HOST environment variable on my new project the mysql container on my new project tried to use to same data directory and because it was already used by my other project it wasn't able to initialize properly.

I solved this problem. This is because of data folder. I was running it using mysql 5.7 then abort it in the middle of building, and change the mysql to 8.0. here some explanation #1138 (comment)
Try this step.
Try remove the docker image. List all images using docker images then remove the mysql & laradock mysql using docker rmi imagename. Dont forget remove the docker volume using docker volume rm volumename
Also go to cd ~/.laradock/data remove the mysql folder.
Then try docker-compose up mysql for debuging. If no errors, you could try docker-compose up -d mysql

Still working in 2021 👍

this is completely related with data directory folder permissions and owners.
do not put a chown or chmod in the entrypoint.sh (or whatever) to  your scripts

I solved this problem. This is because of data folder. I was running it using mysql 5.7 then abort it in the middle of building, and change the mysql to 8.0. here some explanation #1138 (comment)
Try this step.
Try remove the docker image. List all images using docker images then remove the mysql & laradock mysql using docker rmi imagename. Dont forget remove the docker volume using docker volume rm volumename Also go to cd ~/.laradock/data remove the mysql folder.
Then try docker-compose up mysql for debuging. If no errors, you could try docker-compose up -d mysql

Still working in 2022 :D

I solved this problem. This is because of data folder. I was running it using mysql 5.7 then abort it in the middle of building, and change the mysql to 8.0. here some explanation #1138 (comment)
Try this step.
Try remove the docker image. List all images using docker images then remove the mysql & laradock mysql using docker rmi imagename. Dont forget remove the docker volume using docker volume rm volumename Also go to cd ~/.laradock/data remove the mysql folder.
Then try docker-compose up mysql for debuging. If no errors, you could try docker-compose up -d mysql

this answer saved my day after 5 years

I solved this problem. This is because of data folder. I was running it using mysql 5.7 then abort it in the middle of building, and change the mysql to 8.0. here some explanation #1138 (comment)
Try this step.
Try remove the docker image. List all images using docker images then remove the mysql & laradock mysql using docker rmi imagename. Dont forget remove the docker volume using docker volume rm volumename Also go to cd ~/.laradock/data remove the mysql folder.
Then try docker-compose up mysql for debuging. If no errors, you could try docker-compose up -d mysql

Still works. Thank you

I solved this problem. This is because of data folder. I was running it using mysql 5.7 then abort it in the middle of building, and change the mysql to 8.0. here some explanation #1138 (comment)
Try this step.
Try remove the docker image. List all images using docker images then remove the mysql & laradock mysql using docker rmi imagename. Dont forget remove the docker volume using docker volume rm volumename Also go to cd ~/.laradock/data remove the mysql folder.
Then try docker-compose up mysql for debuging. If no errors, you could try docker-compose up -d mysql

Still working 2023 - in my case it occurred after I downgraded from MySQL8 to 5.7

How can I use this without losing the data? Removing the volume name will make me lose the data, doesn't it? So, what's the approach without data losing? Thanks.

[+] Running 4/4  ✔ Network laradock_backend    Created                                                                                0.0s   ✔ Network laradock_frontend   Created                                                                                0.0s   ✔ Network laradock_default    Created                                                                                0.0s   ✔ Container laradock-mysql-1  Created                                                                                0.1s  Attaching to mysql-1 mysql-1  | 2024-05-23 01:41:46+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.37-1.el9 started. mysql-1  | 2024-05-23 01:41:46+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' mysql-1  | 2024-05-23 01:41:46+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.37-1.el9 started. mysql-1  | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock' mysql-1  | 2024-05-23T01:41:46.721033Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead. mysql-1  | 2024-05-23T01:41:46.721071Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. mysql-1  | 2024-05-23T01:41:46.724370Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead. mysql-1  | 2024-05-23T01:41:46.724404Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.37) starting as process 1 mysql-1  | 2024-05-23T01:41:46.725014Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. mysql-1  | 2024-05-23T01:41:46.726929Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive mysql-1  | 2024-05-23T01:41:46.738518Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. mysql-1  | 2024-05-23T01:41:47.045945Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with MySQL 5.7.44, and it appears logically non empty. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html mysql-1  | 2024-05-23T01:41:47.045993Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error. mysql-1  | 2024-05-23T01:41:47.046904Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine mysql-1  | 2024-05-23T01:41:47.047101Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. mysql-1  | 2024-05-23T01:41:47.047124Z 0 [ERROR] [MY-010119] [Server] Aborting mysql-1  | 2024-05-23T01:41:47.047950Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.37)  MySQL Community Server - GPL. mysql-1 exited with code 1
i have this kind of error. i already reinstall from the images to the docker


OSError：library nvvm not found

When i  run the program ,I met the question:OSError：library nvvm not found.What I can do?
thank you .

Please follow the instructions in Readme to install the numba:
A summary of installing/using numba without conda:

Install llvm-6.0
Build and install llvmlite
sudo pip3 install numba
Set environment variables, example

export LLVM_CONFIG=/usr/lib/llvm-6.0/bin/llvm-config
export NUMBAPRO_NVVM=/usr/local/cuda/nvvm/lib64/libnvvm.so
export NUMBAPRO_LIBDEVICE=/usr/local/cuda/nvvm/libdevice

Numba is required by 3-layer SO-Net and accelerated kNN search. Another method to remove the dependency of Numba is to use cuda extentions. The codes can be found in my other repository: rot-equ-net


How to screencast a url?

Any examples with screenshots or screencasting? Also does screencasting support recording with an alpha channel? (like to webm or mov format)?

Yes you can create a screen recording of loading a specific URL.
While the project's purpose is to provide a Docker setup for Webdriver.io, it also comes with integration for video recording.
You can enable video recordings in the browser configs. For Firefox it's enabled by default:
https://github.com/blueimp/wdio/blob/77b7c9518bc377334ac497e83ce0e7265c682ca9/conf/firefox.js#L18
There's in example in the test specs how to save and diff screenshots.
The package providing the screen recording and diffing integration has more usage examples:
https://github.com/blueimp/wdio-screen-commands#usage
There is no support for alpha channel screen recordings.


Tracker: RISC-V boot failure ClangBuiltLinux #1965

Tracking: https://github.com/ClangBuiltLinux/linux/issues/1965 It doesn't affect the upcoming clang-r510928 update but subsequent updates.

This has been resolved: https://github.com/llvm/llvm-project/commit/6c207ee5d20d2b054509123e6d0507df1332b376


Adding Line Of Sight Tool functionality

Hello,
I've added Line of sight functionality to this application. I've done the following:

Created an output using Line of sight tool in Arcmap 10.3.1
Shared the result from above activity, as a service on ArcGis for server.
Wrote a piece of code to consume this service and get the ouput.
I'm getting the correct output, but I'm struggling to show the output correctly. Could you please help me to show the output correctly for Line of Sight? Could you point me to some code already available?

I've searched on internet and not able to find the code specific for showing output of Line of Sight.
Thanks,
Sam

I have not done this, but it may be similar to the Vehicle Commander sample that calls a GP Tool which returns a ArcGISDynamicMapServiceLayer (which is then added to the map)
https://github.com/Esri/vehicle-commander-java/blob/master/source/VehicleCommander/src/com/esri/vehiclecommander/view/ViewshedJPanel.java#L50


Support for docker secrets

Expected Behavior
The docker container should set the docker secrets  as environment variables.
Current Behavior
The docker container does not support to set secrets as environment variables. Thus secrets has to  exposed in the compose-file.
Possible Solution
Office docker container using a docker-entrypoint.sh to achieve this. In this case in can be look like.
#!/bin/bash
set -eo pipefail
shopt -s nullglob

# logging functions
oauth_log() {
	local type="$1"; shift
	printf '%s [%s] [Entrypoint]: %s\n' "$(date --rfc-3339=seconds)" "$type" "$*"
}
oauth_note() {
	oauth_log Note "$@"
}
oauth_warn() {
	oauth_log Warn "$@" >&2
}
oauth_error() {
	oauth_log ERROR "$@" >&2
	exit 1
}

# usage: file_env VAR [DEFAULT]
#    ie: file_env 'XYZ_DB_PASSWORD' 'example'
# (will allow for "$XYZ_DB_PASSWORD_FILE" to fill in the value of
#  "$XYZ_DB_PASSWORD" from a file, especially for Docker's secrets feature)
file_env() {
	local var="$1"
	local fileVar="${var}_FILE"
	local def="${2:-}"
	if [ "${!var:-}" ] && [ "${!fileVar:-}" ]; then
		oauth_error "Both $var and $fileVar are set (but are exclusive)"
	fi
	local val="$def"
	if [ "${!var:-}" ]; then
		val="${!var}"
	elif [ "${!fileVar:-}" ]; then
		val="$(< "${!fileVar}")"
	fi
	export "$var"="$val"
	unset "$fileVar"
}

# check to see if this file is being run or sourced from another script
_is_sourced() {
	# https://unix.stackexchange.com/a/215279
	[ "${#FUNCNAME[@]}" -ge 2 ] \
		&& [ "${FUNCNAME[0]}" = '_is_sourced' ] \
		&& [ "${FUNCNAME[1]}" = 'source' ]
}

# Loads various settings that are used elsewhere in the script
# This should be called after mysql_check_config, but before any other functions
docker_setup_env() {

	# Initialize values that might be stored in a file
	file_env 'OAUTH2_PROXY_BASIC_AUTH_PASSWORD'
        file_env 'OAUTH2_PROXY_CLIENT_ID'
        file_env 'OAUTH2_PROXY_CLIENT_SECRET'
        file_env 'OAUTH2_PROXY_COOKIE_SECRET'
}

# check arguments for an option that would cause mysqld to stop
# return true if there is one
_oauth_want_help() {
	local arg
	for arg; do
		case "$arg" in
			-help|-version)
				return 0
				;;
		esac
	done
	return 1
}

_main() {
	# if command starts with an option, prepend /bin/oauth2_proxy
	if [ "${1:0:1}" = '-' ]; then
		set -- /bin/oauth2_proxy "$@"
	fi

	# skip setup if they aren't running /bin/oauth2_proxy or want an option that stops /bin/oauth2_proxy
	if [ "$1" = '/bin/oauth2_proxy' ] && ! _oauth_want_help "$@"; then
		oauth_note "Entrypoint script for Oauth2-Proxy started."

		# Load various environment variables
		docker_setup_env "$@"

	fi
	exec "$@"
}

# If we are sourced from elsewhere, don't perform any further actions
if ! _is_sourced; then
	_main "$@"
fi

The dockerfile should contain these lines:
COPY docker-entrypoint.sh /usr/local/bin/
RUN ln -s usr/local/bin/docker-entrypoint.sh / # backwards compat
ENTRYPOINT ["docker-entrypoint.sh"]
CMD ["/bin/oauth2_proxy"]

With this it is then possible to define  e.g. the environment variable OAUTH2_PROXY_CLIENT_SECRET_FILE and set it to the secrets file path.
If you agree i can prepare a merge request.

Hey @hesstobi, Could you please explain a little more about your use case here? I'm a little confused by what you're trying to achieve here so I'm not following the suggested solution. I guess my main questions are "How are you running the proxy?", "How are you storing your secret values at present?" if that helps you formulate a reply :)


Fix globbing importing path

Now rake test is 100% passed, please refer to https://travis-ci.org/jsw0528/sass-globbing

Given that 1.1.0 is causing a CPU issue with Passenger on my box and 1.1.1 is broken... this PR REALLY needs to get merged.


trilium: 0.47.3 -> 0.47.4

Motivation for this change
https://github.com/zadam/trilium/releases/tag/v0.47.4
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 125790 at 287e0f24 run on x86_64-linux 1

2 packages built successfully:

trilium-desktop
trilium-server


[Hookable(false)] vs [Wrappable(false)]

Is there any difference between  [Hookable(false)] and [Wrappable(false)]?

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

ID: 4317fdb2-b37f-550d-f229-bfd8498ab073
Version Independent ID: ecd0974c-0abc-c494-cc8c-e81e7cf096f9
Content: Class extension - Method wrapping and Chain of Command
Content Source: articles/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @ChrisGarty
Microsoft Alias: cgarty

@nagarazt, thanks for posting here! You might want to go to the Dynamics 365 community page to get help with your questions from the Dynamics community.
@ChrisGarty, please review and update the content, as necessary.

Bug 408197 has been logged to track this issue.

Thanks Irfan. I understood the concept of both Hookable vs Wrappable. But [HookableAttribute(false)] and [Wrappable(false)] both we use for the normal public or protected methods not on final methods to avoid the extensible option. My question is if both are working in similar way why do we have two properties.  I feel Hookable is deprecated concept. Correct me if I am wrong.

I will review the doc with the team as I agree it's not clear.
Hookable(false) disallows pre/post handlers and CoC. Wrappable(false) only disallows CoC (still allows handlers).
Hookable(true) can be used to allow pre/post handlers on final or protected methods (default is only on non-final public).
Wrappable(true) can be used to allow CoC on final methods (protected or public, private methods can never be wrapped).

Joris updated the doc and the new info should go live tonight.


ImportError: cannot import name 'GeminiClient' from 'gemini'

from gemini import Gemini
from gemini import GeminiClient
async def main():
cookies = {
I setup all the cookies as per the instructions in readme file
}

client = GeminiClient(cookies=cookies)
await client.async_init()

prompt = "Hello, Gemini. What's the weather like in Seoul today?"
response = client.generate_content(prompt)
print(response)

gskreddy1981
Please, try to use 1.0.4 or above!
We are currently modifying the package with a focus on extensive code refactoring and future maintainability, so errors may occur. We are also in the process of making adjustments to the returned dictionary for easier access in the future.
We appreciate your understanding. Thank you!!!
python uninstall python-gemini-api

python install python-gemini-api==1.0.4


pandas columns names starting with a number fail to be exported

Describe the bug
pandas columns names starting with a number fail to be exported with postgres when using
To Reproduce
Steps to reproduce the behavior:

Set a pandas object with a column name starting with a number ("1ereParution" is example)
Export this data to postgres with allow_reserved_words=True
We have error: UndefinedColumn: column "1ereparution" of relation "_raw_initiatives" does not exist

Expected behavior
Export should be successful
Screenshots

Desktop (please complete the following information):

OS: MacOS Ventura 13.4.1
Browser: Chrome
Version: 120.0.6099.109 (Official Build) (arm64)

Hi @csauge , Postgres column name can't start with a number.

Actually we can and it works (i have performed tests) and regarding you documentation (which is an old one v7.0): "Names containing other characters may be formed by surrounding them with double quotes (")".
Nevertheless it seems that Mage should not except with UndefinedColumn. It should either:

accept them by surrounding them with double quotes (allow_reserved_words=True)
rename them automatically by for example adding an "_" before the first number (allow_reserved_words=False)
What do you think ?

We're working on the fix for this issue.

Hi @wangxiaoyou1993 any update on this I am also facing a similar issue?
`File /usr/local/lib/python3.10/site-packages/mage_ai/io/postgres.py:393, in Postgres.upload_dataframe(self, cursor, df, db_dtypes, dtypes, full_table_name, allow_reserved_words, auto_clean_name, buffer, case_sensitive, unique_conflict_method, unique_constraints, **kwargs)
386             df_.to_csv(

387                 buffer,

388                 header=False,

389                 index=False,

390                 na_rep='',

391             )

392             buffer.seek(0)

--> 393             cursor.copy_expert(f"""
394 COPY {full_table_name} ({insert_columns}) FROM STDIN (

395     FORMAT csv

396     , DELIMITER \',\'

397     , NULL \'\'

398     , FORCE_NULL({insert_columns})

399 );

400         """, buffer)

UndefinedColumn: column "_name" of relation "items" does not exist`

Hi @wangxiaoyou1993 - is this issue resolved, I am facing a similar issue.


Exclude fuzz target code from coverage measurement

Our current line coverage measurement includes the lines from the fuzz target.
It's fairer to measure the lines from the project only, not the fuzz target, so that covering more lines in the fuzz target will not increase the code coverage.

JOB: https://pantheon.corp.google.com/kubernetes/job/us-central1-c/llm-experiment/default/ofg-pr-135-dg
REPORT: https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-03-05-135-dg-comparison/index.html
BUCKET: https://pantheon.corp.google.com/storage/browser/oss-fuzz-gcb-experiment-run-logs/Result-reports/ofg-pr/2024-03-05-135-dg-comparison
BUCKET GS: gs://oss-fuzz-gcb-experiment-run-logs/Result-reports/ofg-pr/2024-03-05-135-dg-comparison


refactored so that submit_done can be used by other python programs

the submit_done function now stands alone a bit more.
I'd like to be able to call submit_done directly from other python programs that would get the token & team from a config file and generate the message automatically based upon what the program did.
It would be interesting if a config file could be used for this CLI as it is so that the only required item would be the message and not the team and token if those are found in the config file.

The code I submitted does work, but the tests seems to be failing due to my refactoring the code. Not sure how to the tests.

This is awesome, thanks for the PR!


tests: power management: test_power_state_trans fails on nrf boards

Describe the bug
The test test_power_state_trans from tests/subsys/power/power_mgmt/ fails on-target tests (at least on nrf and reel boards)
To Reproduce
Steps to reproduce the behavior:

have nrf52840dk connected
go to your zephyr dir
call /scripts/twister -T /tests/subsys/power/power_mgmt -p nrf52840dk_nrf52840 --device-testing --device-serial /dev/ttyACM0 -v --inline-logs
See error

Expected behavior
The test passes
Impact
Not clear
Logs and console output
START - test_power_state_trans
Assertion failed at WEST_TOPDIR/zephyr/tests/subsys/power/power_mgmt/src/main.c:109: notify_pm_state_exit: (notify_app_exit == true is false)
Notification to leave suspend was not sent to the App
Assertion failed at WEST_TOPDIR/zephyr/tests/subsys/power/power_mgmt/src/main.c:112: notify_pm_state_exit: state not equal to PM_STATE_RUNTIME_IDLE
FAIL - test_power_state_trans in 0.133 seconds

Environment (please complete the following information):

OS: Ubuntu 18.04
Toolchain Zephyr SDK 0.12.2
Commit SHA or Version used: zephyr-v2.5.0-3011-gb61c23943c6f

I think the same bug is causing more power mgmt tests/samples to fail, as I see also this one failing from the same time: sample.power.ospm.dev_idle_pm

@gmarull The fail of test_power_state_trans  is gone, thanks. Do you know if sample.power.ospm.dev_idle_pm (samples/subsys/pm) is related? Should I raise a separate issue? This test is still failing with the fix (nrf52840 and nrf52832). It hangs at:
ERROR   - *** Booting Zephyr OS build zephyr-v2.5.0-3821-g41afd838aabd  ***
Device PM sample app start
open()
parent resuming..
Async wakeup request queued
child resuming..
Dummy device resumed
write()
transfer()
read()
transfer()
close()
child suspending..
Device PM sample app complete
parent suspending..

@ceolin do you know if related to any recent change?

@PerMac https://github.com/zephyrproject-rtos/zephyr/pull/35315 may fix the problem, but I haven't reviewed yet

unluckily, #35315 doesn't change the test behavior. I will create a separate issue for ease of tracking.


NAN Error In OPT-125M and LLaMA-2-7B

Could you please tell me why this numerical instability is occurring, and if I still need to go for a reproduction?

Thank you for your interest in our work. We have just pushed an update to address the numerical instability for the OPT models and we are still working on addressing the numerical instability for the LLaMA models. We would like to emphasize that our method relies on an alternating optimization scheme which is known to be sensitive to the hyperparameter values.

Thank you for your interest in our work. We have just pushed an update to address the numerical instability for the OPT models and we are still working on addressing the numerical instability for the LLaMA models. We would like to emphasize that our method relies on an alternating optimization scheme which is known to be sensitive to the hyperparameter values.


Enabling support for QuickAssist Devices

Thanks! That's good start. I'll review it later today.

@swatisehgal please also have a look at CI errors (lint and build issues)

@swatisehgal Please check this PR https://github.com/swatisehgal/intel-device-plugins-for-kubernetes/pull/1
Feel free to squash the proposed changes into your commit. But please test them with a real device before squashing.

@swatisehgal could you please squash the commits into one commit? Then I’ll merge the PR.

There are few minor things that can be fixed in separate PRs


Hollow Rhombus Pattern

Description 📜
I have prepared a documentation on:
Hollow Rhombus Pattern
A fascinating pattern which can have as many equal number of rows and columns as the user wants. 👍
Do try it and enjoy! :)
Fixes #5270

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] C/CPP

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@ikavyajain  Like syntactically its fine...
But I hope you understand that there cn be infinite amount of Pattern contributions...
Toh itna chhota PR makes it harder to do justice to the good meaningful ones
So, I hope you'll pick a nice praise-worthy topic for contribution


Problem processing avi file

I keep getting the error below when i deal with avi file and i can't seem to figure out what i'm missing. any insight into what's going on?
[AVHWDeviceContext @ 0x5599facb8080] Could not dynamically load CUDA
[mpeg4_cuvid @ 0x5599facb5da0] Error creating a CUDA device
cuvid hwaccel requested for input stream #0:0, but cannot be initialized.
[mpeg4_cuvid @ 0x5599facb5da0] ff_get_format failed: -1
Stream mapping:
Stream #0:0 -> #0:0 (mpeg4 (mpeg4_cuvid) -> h264 (libx264))
Stream #0:1 -> #0:1 (mp3 (native) -> aac (native))
Error while opening decoder for input stream #0:0 : Operation not permitted

It's an FFMpeg error because you're trying to use hardware acceleration. If you're not intending to use it feel feee to remove those options from hwaccels and hwaccel-decoders (just leave those blank)
If you're intending to use hwaccel then you gotta debug your hardware configuration.


Type and range of bucket

An integer underflow was triggered when the arkime capture module was processing a pcap file. The crafted pcap file manipulates the value of  long int lastPacketSecs, and causes the underflow of int bucket in the following processing. Also, the range of bucket ought to be limitted to avoid the out of bound reference.

Hi can you attach the pcap or slack it to me.

Hi can you attach the pcap or slack it to me.
Sure, I will slack the samples to you.

Thanks for the pcaps, looks like I still get sanitize errors with the current PR, so I'll look some more. I think the general issue is that arkime has Y2038 issues that I need to fix. :(

It really weird, as I haven't catch the entire structrue of arkime. I also wonder how this change takes effects.

it looks like libpcap has a Y2038 issue (or design choice) that I'm overriding in PR #2103, once i merge that we should retest what is needed next.

get it

So I took a different approach with #2104 although i don't know it will work if the timestamp is maxtime.

I tested different timestamp including the maxtime based on my previous pcap, and it worked fine without any error.
Impressive change :)


How to disable trackingSessionEvent?

Summary
Hi! Is there any preferred way to disable trackingSessionEvent property on Android?
I see that Android-supported initialisation method only allows to modify the existing configuration, which in turn declares trackingSessionEvent as a val.
fun Amplitude(apiKey: String, context: Context, configs: Configuration.() -> Unit): com.amplitude.android.Amplitude {
    val config = Configuration(apiKey, context)
    configs.invoke(config)
    return com.amplitude.android.Amplitude(config)
}

EDIT:
Should I just do this?
val amplitude = Amplitude(Configuration(apiKey, context))

Hi @scana, yeah, in the second way you can declare trackingSessionEvents to be false.
@liuyang1520 @justin-fiedler maybe we should turn that value in config to var to prevent future confusion.

@qingzhuozhen , do you mean this part?

@liuyang1520 yeah, that is correct.

@qingzhuozhen , I create a PR https://github.com/amplitude/Amplitude-Kotlin/pull/68 for updating this, PTAL!

Merged and released in v1.3.0.


Feature/my invitations

Allow a student to accept/reject invitations from groups

FYI I'm just blocking out functionality in this PR. I don't think I'll ever get the time to make this look more interesting than a simple data table


upload Roger EDA

adding EDA section for assignment 3.1

A few comments!

The EDA generally looks good, but I think the graph titles & axis labels should be more descriptive. For example, when you get bar plots by race, gender, etc, the y axis labels are just "Count" but it's not total count of people by race, gender, etc. The graph actually is just the count of rows, which is just # of counties in our dataset with data for those races, genders, etc.
I would rename the "val" column in the correlation heatmap to be more informative as to what it is & also indicate its the target variable for us to focus on.
How did you get the top 10 counties' names for all the graphs at the bottom of the notebook? I don't believe I saw the code for that. If possible, I think the x axis should also have the actual county names rather than the FIPS IDs if you're able to map them like you did to get the Top 10 for each category you showed.

Thanks :)


Determine DataSet

https://www.kaggle.com/datasets/jahnavipaliwal/video-game-reviews-and-ratings/data is a good candidate, but User Ratings seems to be unreliable.


cuda error

cpu_data = data.contiguous().to("cpu", non_blocking=True).pin_memory()

RuntimeError: CUDA error: operation not supported
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

I found that there will be no problem in the initial inference, but a CUDA error will be reported during subsequent inference. How can I solve this?

Hi, could you share more details about your platform and environment? Such as CUDA and PyTorch versions, and operating system.

Hi, could you share more details about your platform and environment? Such as CUDA and PyTorch versions, and operating system.

thanks for your reply :)
Driver Version: 470.199.02   CUDA Version: 12.1

torch                         2.1.0a0+b5021ba

Hi, could you share more details about your platform and environment? Such as CUDA and PyTorch versions, and operating system.

thanks for your time.
torch 2.1.0a0+b5021ba
Driver Version: 470.199.02   CUDA Version: 12.1 Ubuntu 22.04.2 LTS
I tried to use both triton==3.0.0 and torch, but still failed.(it seem like that attention is after memoryunit operations)

thanks for your time.
torch 2.1.0a0+b5021ba
Driver Version: 470.199.02 CUDA Version: 12.1 Ubuntu 22.04.2 LTS
I tried to use both triton==3.0.0 and torch, but still failed.(it seem like that attention is after memoryunit operations)

I noticed that you're using a driver version that's lower than what CUDA 12 requires.
I'm not familiar with CUDA compatibility, but I think using PyTorch compiled with CUDA 12 might lead to some operations being incompatible.
You could run a simple test code
import torch
data = torch.randn((32, 128, 128), dtype=torch.bfloat16, device='cuda')
torch.cuda.synchronize()
cpu_data = data.to("cpu")
torch.cuda.synchronize()
non_blocking_cpu_data = data.to("cpu", non_blocking=True)
torch.cuda.synchronize()
pin_data = cpu_data.pin_memory()
torch.cuda.synchronize()
non_blocking_pin_data = data.to("cpu", non_blocking=True).pin_memory()
torch.cuda.synchronize()

The issue might stem from non_blocking or pin memory not being supported.
If that's the case, modifying the code inf_llm/attention/context_manager.py could work, though it might be slower slightly .
However, I'd still recommend using a fully supported CUDA version like 11.8.

thanks for your time.
torch 2.1.0a0+b5021ba
Driver Version: 470.199.02 CUDA Version: 12.1 Ubuntu 22.04.2 LTS
I tried to use both triton==3.0.0 and torch, but still failed.(it seem like that attention is after memoryunit operations)

I noticed that you're using a driver version that's lower than what CUDA 12 requires. I'm not familiar with CUDA compatibility, but I think using PyTorch compiled with CUDA 12 might lead to some operations being incompatible. You could run a simple test code
import torch
data = torch.randn((32, 128, 128), dtype=torch.bfloat16, device='cuda')
torch.cuda.synchronize()
cpu_data = data.to("cpu")
torch.cuda.synchronize()
non_blocking_cpu_data = data.to("cpu", non_blocking=True)
torch.cuda.synchronize()
pin_data = cpu_data.pin_memory()
torch.cuda.synchronize()
non_blocking_pin_data = data.to("cpu", non_blocking=True).pin_memory()
torch.cuda.synchronize()

The issue might stem from non_blocking or pin memory not being supported. If that's the case, modifying the code inf_llm/attention/context_manager.py could work, though it might be slower slightly . However, I'd still recommend using a fully supported CUDA version like 11.8.

Unfortunately…
It is executable
And when I tried infllm, my first inference is valid, but the error will be reported from the second time.


Pass headers to the AuthN and AuthZ

Closing in favor of https://github.com/stargate/stargate/pull/581

Closing in favor of https://github.com/stargate/stargate/pull/581


fix: not showing deprecated fields on root level

Fixes #816 .
Changes proposed in this pull request:

Currently, GP doesn't show deprecated fields on root level(e.g. deprecated query or mutation). So this PR fix it and GP shows the deprecated fields.

@timsuchanek Hey, could you pls review it?


Access blob storage using Bearer token

Please document or provide an example on how to access blob storage using Bearer token.
Scenario:

SPA is authenticated with AD
SPA invoked Azure Function, bearer token is retrieved in this function
Blob is now needs to be accessed using this token

Hi @leonbrag,
How is your SPA authenticating with AAD currently?  Why would you need to use a different bearer token than the one you already acquired when you authenticated the SPA?  We generally do not recommend handling bearer tokens directly as it can be a security concern, especially when you're retrieving them from a service you've hosted in Azure.
Is it possible that you could use one of the existing credential implementations in @azure/identity to accomplish what you're trying to do?

Yes, I can use existing credential implementation and it works (other then MSI credential bug I opened here: https://github.com/Azure/azure-sdk-for-js/issues/5539)
I was just curious about Bearer token. But I think your comment “We generally do not recommend handling bearer tokens directly” is sufficient to satisfy my curiosity.
SPA authenticates against B2C using MSAL libraries. SPA is authorized via claims to invoke Function. In the function, check is made to verify that claim to invoke function is present (using MSAL again) and then email claim from bearer token in obtained  (for further processing)

Thanks @leonbrag!  It seems like the concern in this issue has been addressed so I'll close it now.  Please let me know if you have any other questions!

@sadasant Can you help with @diberry's question above?

@ramya-rao-a I believe that @diberry and I have discussed this scenario at length. This is one of the champion cases I want to present next week.
I can still answer those questions here, of course:

If I want the Function API to create resources using the signed-in user to AAD in React, how to I go from client/accessToken to server/aad credential?

The way this would work is to use the InteractiveBrowserCredential on the client, calling getToken directly, using the cleintId and tenantId of an App Registration that supports Single Page Application redirect endpoints (let’s call it “App A”), with the scope of a custom endpoint of a separate App Registration (let’s call it “App B”), then sending that token to the backend to use the OnBehalfOfCredential to gain access to services non-compatible with CORS (or services only available to “App B”).
The “easier” approach is to get the access token directly on the backend using the AuthorizationCodeCredential, but at the moment the users have to figure out by themselves how to “go” to the authentication URL to trigger the redirection.


Add a special __call__ function

Users can define a contract function named __init__ that will execute at initialization time.
Continuing with this pattern, we might consider adding a function named __call__ that runs at call time. By adding such a function, the language would be more flexible with regard to contract interfaces.
e.g.
contract Foo:
  # the __call__ function is defined with full access here. not sure if that should be required..?
  pub fn __call__(mut self, ctx: mut Context):
    # grab the calldata from the Context object
    let calldata = ctx.calldata()

    # the function is selected using the first byte in calldata
    if calldata[0] == 0:
      # pass the second byte into foo
      self.foo(calldata[1])
    else if calldata[0] == 1:
      # pass the second and third byte into bar
      self.bar(calldata[1], calldata[2])

    revert "invalid calldata"

  fn foo(self, my_byte: u8):
    # do stuff

  fn bar(self, my_byte: u8, my_extra_byte: u8):
    # do stuff

In the example above, we have defined an super simple and efficient contract interface. Writing a custom interface such as this one might be useful for people looking to reduce fees. The other benefit is that we could move the Solidity ABI decoding/encoding implementation into Fe-lang as opposed to having that code generated in the Yul gen phase.
In the future, it might be possible to change the interface of a contract using a procedural macro that writes a __call__ function for you.
e.g.
#[interface(SomeAbi)]
contract Foo:
   ...

One thing to note is that the __init__ function takes ABI encoded parameters, which does not align well with this proposal.

In the example above, how is __call__ being triggered? Does it run like a hook whenever a public function is called (the above example has none except __call__) or is it called manually like Foo.__call__()? In that case, I'd be wondering what is the special role of it since a user could have just defined it as a regular function and e.g. call Foo.dispatcher().

how is call being triggered?

The __call__ function is the only thing that would be triggered when the contract is called, so any pub labels become obsolete.
If one does not define a call function, then a __call__ that performs Solidity ABI dispatching would be added to the contract during lowering.

Also note that Foo.dispatcher() would be selected using the Solidity ABI, which means that custom dispatching has not been defined.
The idea is to provide total flexibility around contract interfaces and allow for us to define the existing interface in Fe-lang

Oh, now I understand. Genius! I like that :+1:


Unable to find published extension

firebase ext:install -i
... select the extension and get the message ...
Error: Unable to find published extension 'firestore-messagebird-send-msg'. Run firebase ext:install -i to select from the list of all available published extensions.

Hi @YouZag
Thank you for reporting.
I quickly checked the problem and from what I see it seems to me that the problem is on Firebase side.
It lists MB extension as firebase/firestore-messagebird-send-msg where the correct id of the extension should be messagebird/firestore-messagebird-send-msg.
@karayu @i14h can you guys please check why our extension is listed under firestore/?
@YouZag in the meantime you can use command with full extension name to install it:
firebase ext:install messagebird/firestore-messagebird-send-msg  --project='YOUR_PROJECT_ID'
Thanks, Oleks

@YouZag @aodinok yes this is a bug on our side and we're working on it. In the meantime please install the extension directly just as Oleksander mentioned.

@i14h @aodinok Thanks for the quick responses.  Unfortunately, the full extension is how I originally ran into this problem as it also returns unable to find.

Hmm it works for me:
i  extensions: ensuring required API firebaseextensions.googleapis.com is enabled...
✔  extensions: required API firebaseextensions.googleapis.com is enabled
i  extensions: information about 'messagebird/firestore-messagebird-send-msg@latest':
Name: Send Messages with MessageBird
Publisher: messagebird
Description: Sends messages and notifications using the MessageBird Conversations API.
License: Apache-2.0
Source code: https://github.com/messagebird/firestore-send-msg/tree/master

? Would you like to continue installing this extension? (Y/n)

Can you try again maybe the issue was already fixed by Firebase.

Hey @i14h,
Is there any update on this? I still see that MessageBird extension is listed under firebase:


Add in the ability to generate ASYNCAPI Yaml

Why do we need this improvement?
Allows for greater flexibility in use cases & better fit business needs
How will this change help?
My workplace works with yaml for describing our API's and as such we would like to have our rabbitmq protocols described using yaml
Screenshots
No response
How could it be implemented/designed?

Provide additional endpoint which returns the yaml

🚧 Breaking changes
No

This should be easy enough once asyncapi.net has replaced the models.
I am technically working on this, although currently on parental leave so i don't have time until May to finish it up

No problem, there is no urgency from me as i will have a possible workaround generate the JSON and then use the lego library to convert it.


MFA enforced but not enabled?

Any idea why a user can be MFA enforced but not enabled?

Enforced means that the user will need to set up MFA at the next login. Enabled is when MFA is actually configured by the user.


Extractor loses track of container

1. fn - lua/entities/isawc_extractor.lua:640
2. unknown - lua/ulib/shared/hook.lua:109
3. SetTeam - [C]:-1
4. PlayerJoinTeam - gamemodes/base/gamemode/player.lua:649
5. TryToChangeToTeam - gamemodes/lootwars/gamemode/init.lua:187
6. unknown - gamemodes/lootwars/gamemode/init.lua:543
7. unknown - lua/includes/modules/concommand.lua:54

Found this when I changed teams after rejoining the server

The exporter is persistent btw

Resolved via 437fb9ec632f920d85b5b13acb76658acc45c5a4


🐛 Bug Report: Notifications don't work without users in catalog

📜 Description
We are trying to use the notifications plugin with a catalog with no users. Unfortunately this is resolving a list of user entity refs to entities in the catalog before sending out notifications resulting in no notifications being sent out in our case. I was able to fix this by commenting out the check in our codebase but I think an extension point to allow for custom user resolvers may be a better solution.
👍 Expected behavior
Given a list of user entity refs, notifications should be sent out to all of them.
👎 Actual Behavior with Screenshots
No notifications are sent out.
👟 Reproduction steps

Create sign-in resolver for catalog with no users
Send out notifications

📃 Provide the context for the Bug.
We have a custom sign-in resolver for allowing users to login without a corresponding user in the catalog.
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Hi, made a fix #25781 that bypasses catalog calling for all user entity references. This would also help a bit to remove unnecessary calls to the catalog for notifications targeted directly to users.


Disable ARM tests in official builds.

Refer https://devdiv.visualstudio.com/DevDiv/_build/index?buildId=1020801&_a=summary

@ravimeda,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@dotnet-bot test NanoServer - 1. Dockerfiles please

@dotnet-bot test NanoServer - 1. Dockerfiles please

Thanks!


ml-build fails on Windows with error

Version
110.99.2
Operating System

[ ] All
[ ] Linux
[ ] macOS
[ ] Windows
[X] Other Unix

OS Version
other x64 Windows 11
Processor
Other
Component
Core system
Severity
Minor
Description of the problem
ml-build fails with the error that it cannot find XYZ_XXX_BOOTLIST. I think it might be because of either the space or the parenthesis in the default install path.
Steps to repro:

Download installer from https://smlnj.org/dist/working/110.99.2/smlnj-110.99.2.msi
Install SMLNJ to the default location: C:\Program Files (x86)\SMLNJ.
Create a file sources.cm and add the content below.
Create a file main.sml and add the content below.
Open cmd.exe or powershell and run ml-build sources.cm Main.main out.
Fix:
I think you can double quote around the %COMSPEC% command like so in ml-build.bat:
%COMSPEC% /C ""%SMLNJ_HOME%\bin\sml.bat" %flags% %setup% @CMbuild %root% %cmfile% %heap% %listfile% %linkargsfile%"

Transcript
C:\source\repos\smlnj-windows-build-repro>ml-build sources.cm Main.main out
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
Compilation failed with error.
Could Not Find C:\source\repos\smlnj-windows-build-repro\XYZ_XXX_BOOTLIST
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.

Expected Behavior
No response
Steps to Reproduce
sources.cm:
Group is
    $/basis.cm
    main.sml

main.sml:
structure Main =
struct
  fun main (name, args) =
    (print "Hello World!\n"; OS.Process.success)
end

Additional Information
No response
Email address
<EMAIL_ADDRESS>Comments from smlnj-gforge
Original smlnj-gforge bug number 301
Submitted via web form by Harry Gifford<EMAIL_ADDRESS>on 2022-01-27 at 02:18:00
Keywords: Windows, ml-build
comment by Shakil Ahmed on 2022-02-08 00:16:00 +000 UTC
I reproduced the error and then edited the %COMSPEC% command in ml-build file  as mentioned.
Then build was successful.

Fixed for 110.99.3 (as suggested above).


Meet with Debasmita

To continue from 11/18 discussion about gcc_sd

[x] Confirm issues with pulling weather forecasts
[ ] How to model error around the the mean?

Debugged the noaa_stack() function, which requires a date if doing consecutive pulls. Otherwise, it will stack all of the forecasted dates.
Also showed the native temporal SD in the gcc_90 data, which arises due to random processes. Therefore, adding weather or averaging across ensemble runs still won't improve it. Hopefully, the temporal SD in a moving window from the past can be used to adjust the across-ensemble SD and improve performance with CRPS.

Met with Debasmita and Arun to decide how to obtain the CI for the gcc/rcc predictions. Empirical methods considered, then looked at the weather forecasts and decided to use each of 30 forecasts separately. Arun also proposed a weighting for the precipitation, as it appears that gcc variability depends in part on how bright or cloudy the day was


How to implement CIL  DDPG  in Coach

I wang to implement  paper "CIRL: Controllable Imitative Reinforcement Learning for Vision-based Self-driving".
In CIL  DDPG  agent，there have multi-branches output ,how to compute the policy gradient?

https://github.com/HubFire/Muti-branch-DDPG-CARLA A tensorflow implemention


Prepare for mainlining first release devnet node

This commit is a next step towards Gevulot devnet.
Old test provers are removed. README is changed towards node-centric repository structure and specific INSTALL guide has been added.

I'll merge this now and fold the proto -> main shortly afterwards. Let's iterate & make frequent fixes when we come up with points to change. We can still discuss under this PR for a short while afterwards as well if it makes sense (i.e. there's suitable context).