filters short-circuit in an unexpected fashion

Consider the following mirror filters:

aptly mirror create -filter='Name (~ python)' ...
aptly mirror create -filter='Name (~ python), !Name (= libpython2.7) ...
aptly mirror create -filter='!Name (= libpython2.7), Name (~ python) ...

Expected results:

contains all packages with python in the name
contains all packages with python in the name, except for libpython2.7
contains all packages with python in the name, except for libpython2.7

Actual results:

contains all packages with python in the name
contains all packages with python in the name
contains all packages with python in the name, except for libpython2.7

Based on these outcomes, it appears that filtering on packages short-circuits after the first clause that evaluates to true, which is incorrect behavior for a logical AND.
--
~ % aptly version
aptly version: 0.9.1

@Commod0re I'm not able to reproduce that (neither in tests nor reproducing your scenario):
$ aptly mirror create -architectures=amd64 -filter='Name (~ python)' wheezy http://mirror.yandex.ru/debian wheezy
$ aptly mirror update wheezy
...
$ aptly mirror edit -filter='Name (~ python), !Name (= libpython2.7)' wheezy
$ aptly mirror update wheezy
$ aptly mirror show -with-packages wheezy | grep libpython
Filter: Name (~ python), !Name (= libpython2.7)
  libpython2.6_2.6.8-1.1_amd64
  libpython3.2_3.2.3-7_amd64
  libpythonqt2-dev_2.0.1-1.1_amd64
  libpythonqt2.0_2.0.1-1.1_amd64

$ aptly mirror edit -filter='!Name (= libpython2.7), Name (~ python)' wheezy
$ aptly mirror update wheezy
$ aptly mirror show -with-packages wheezy | grep libpython
Filter: !Name (= libpython2.7), Name (~ python)
  libpython2.6_2.6.8-1.1_amd64
  libpython3.2_3.2.3-7_amd64
  libpythonqt2-dev_2.0.1-1.1_amd64
  libpythonqt2.0_2.0.1-1.1_amd64

That is interesting. I had no problems reproducing the issue yesterday. Let me see if I can narrow this down a little more.

Aha, I figured it out. The problem is not necessarily the filter by itself, but it seems to show up at times when filtering along with dependency resolution.
This example shows a reproduction of unexpected filtering results with aptly snapshot filter:
% aptly -architectures=i386 mirror create -filter='Name (~ python)' test http://archive.ubuntu.com/ubuntu precise
% aptly mirror update test
...
% aptly snapshot create test from mirror test

Snapshot test successfully created.
You can run 'aptly publish snapshot test' to publish snapshot as Debian repository.
% aptly snapshot filter test tf1 -with-deps 'Name (~ python), !Name (= libpython2.7)'
Loading packages (1995)...
Building indexes...

Snapshot tf1 successfully filtered.
You can run 'aptly publish snapshot tf1' to publish snapshot as Debian repository.
magreene@HAL ~ % aptly snapshot show -with-packages tf1 | grep libpython
Description: Filtered 'test', query was: '-with-deps Name (~ python), !Name (= libpython2.7)'
 libpython3.2_3.2.3-0ubuntu1_i386
 libpythonqt2-dev_2.0.1-1ubuntu1_i386
 libpythonqt2.0_2.0.1-1ubuntu1_i386
% aptly snapshot show -with-packages tf2 | grep libpython
Description: Filtered 'test', query was: '!Name (= libpython2.7), Name (~ python)'
 libpython2.7_2.7.3-0ubuntu3_i386
 libpython3.2_3.2.3-0ubuntu1_i386
 libpythonqt2-dev_2.0.1-1ubuntu1_i386
 libpythonqt2.0_2.0.1-1ubuntu1_i386

It is a little odd to me that doing it this way produces the opposite results of what I was seeing last night, but it does at least show that the behavior can change based on the filter order.

That makes sense: first aptly does filtering, then dependency resolution. As dependency resolution algorithm isn't perfect, it may produce different result on slightly different package order.

Is this related to aptly not looking at dependencies of dependencies?
Example:  I filter openjdk-7-jre-headless, which depends on libpulse0, which depends on libasyncns0 and others. The dependencies for libpulse0 don't get pulled in with -filter-with-deps


Patch 90

What does this PR do?
Added sololearn Courses, Sorted the Courses section
Description
Why is this valuable (or not)?
It is valuable since a user can find the courses easily after searching through a sorted list. And Sololearn courses are really great for beginners
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

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

Follow-up

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

please add to the correct list


test Explorer tree view not show case iteam

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:  1.86
OS Version:  macos 12.4

Steps to Reproduce:

open test Explorer in python pytest
see like this tree view

Possibly in several versions ago
can show  test_get_proxy, test_post_porxy case tree view iteam

and use other plugin can show

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

yes my version now is 1.86.2 problem is  also

Hi! To confirm you are expecting a "test_get_proxy" node with then the multiple parameterized tests under it right?

你好！為了確認您期望一個“test_get_proxy”節點，然後在其下進行多個參數化測試，對嗎？

yes, like   test_get_proxy
--data0
--data1
--data2

understood yes- this is a reporting problem which is being tracked here: https://github.com/microsoft/vscode-python/issues/22870


Issue 358 enhancement enable relative paths for chaining

Using url.substring(0, url.indexOf("/oauth2/auth")) and contains("/oauth2/auth") leads to weird things e.g. when https://example.predic8.de/oauth2/userInfo?ignore=/oauth2/auth is requested.
Both patterns have therefore been replaced in 355293e1 by exact variants using url.startsWith(basePath + "/oauth2/auth") and basePath where basepath is retrieved from the surrounding <serviceProxy>.
The construction
<serviceProxy port="80">
  <path>/abc</path>
  <oauth2AuthorizationServer ...>

therefore now works. In d0727c052, a test was added verifying exactly that.


"Convert.py" Error

Hello,
The DeeplabV2 has two caffemodels. one named init.caffemodel and the second named train_iter_20000.caffemodel
I tried both but I get this error:
Check failed: target_blobs.size() == source_layer.blobs_size() (5 vs. 3) Incompatible number of blobs for layer bn_conv1
*** Check failure stack trace: ***
Aborted (core dumped)

Please consider this, or upload the Tensorflow weights somewhere. Thanks.

The link to the converted weights is provided. Please read Readme carefully
before asking questions/opening new issues.
As for your error, it might be because of your caffe version.
On 24 Apr 2017 6:20 pm, "Hesam Moshiri"<EMAIL_ADDRESS>wrote:

Hello,
The DeeplabV2 has two caffemodels. one named init.caffemodel and the
second named train_iter_20000.caffemodel
I tried both but I get this error:
Check failed: target_blobs.size() == source_layer.blobs_size() (5 vs. 3) Incompatible number of blobs for layer bn_conv1
*** Check failure stack trace: ***
Aborted (core dumped)
Please consider this, or upload the Tensorflow weights somewhere. Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DrSleep/tensorflow-deeplab-resnet/issues/73, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHemmHu_mBmPzwqVSbRPngGQwv7CxTx8ks5rzL3DgaJpZM4NGUNv
.

Hh sorry yes, you are right. I just missed that download link
But anyway before closing this issue, may I ask you what is the difference between the resnet_init weights resnet?

Init is the model pretrained on COCO (not on Pascal). Resnet is the init
model trained on Pascal
On 24 Apr 2017 6:56 pm, "Hesam Moshiri"<EMAIL_ADDRESS>wrote:

Hh sorry yes, you are right. I just missed that download link
But anyway before closing this issue, may I ask you what is the difference
between the resnet_init weights resnet?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DrSleep/tensorflow-deeplab-resnet/issues/73#issuecomment-296717451,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHemmF5jBeRBtmQQp-iBmQ9w3UckpcU8ks5rzMY7gaJpZM4NGUNv
.


[SPARK-9949] [SQL] Fix TakeOrderedAndProject's output.

https://issues.apache.org/jira/browse/SPARK-9949

Merged build triggered.

Merged build started.

Test build #40815 has started for   PR 8179 at commit 0ac595e.

Test build #1582 has started for   PR 8179 at commit 0ac595e.

Test build #1582 has finished for   PR 8179 at commit 0ac595e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KMeans(JavaEstimator, HasFeaturesCol, HasPredictionCol, HasMaxIter, HasTol, HasSeed):

Test build #40815 has finished for   PR 8179 at commit 0ac595e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait Identifiable
case class QRDecomposition[QType, RType](Q: QType, R: RType)
class VectorUDT extends UserDefinedType[Vector]
class KMeans(JavaEstimator, HasFeaturesCol, HasPredictionCol, HasMaxIter, HasTol, HasSeed):

Merged build finished. Test FAILed.

Test build #1585 has started for   PR 8179 at commit 0ac595e.

Test build #1586 has started for   PR 8179 at commit 0ac595e.

Test build #1588 has started for   PR 8179 at commit 0ac595e.

Test build #1585 has finished for   PR 8179 at commit 0ac595e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1586 has finished for   PR 8179 at commit 0ac595e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1588 has finished for   PR 8179 at commit 0ac595e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

This no longer merges cleanly ...

Merged build triggered.

Merged build started.

Test build #40849 has started for   PR 8179 at commit d7da496.

Test build #40849 has finished for   PR 8179 at commit d7da496.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
 implicit class StringToColumn(val sc: StringContext)

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40917/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40915/
Test FAILed.

Test build #1606 has started for   PR 8179 at commit a8a59e2.

Test build #1606 has finished for   PR 8179 at commit a8a59e2.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1610 has started for   PR 8179 at commit a8a59e2.

Test build #1610 has finished for   PR 8179 at commit a8a59e2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Thanks - merging this in.


[FX-2259] Tracking for Artist Series

The type of this PR is: Feature
This PR resolves FX-2259.
Description
This PR adds the following events from the spreadsheet:
Artist Series View

Screenview

followedArtist

unfollowedArtist

tappedArtistSeriesGroup

Artwork View

tappedArtworkGroup (on an individual artwork)

tappedArtworkGroup (on the header-- to view the series)

tappedArtistSeriesGroup

Artist View

tappedArtistSeriesGroup

All Artist Series View

Screenview

tappedArtistSeriesGroup

PR Checklist (tick all before merging)

[X] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[X] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[X] I have documented any follow-up work that this PR will require, or it does not require any.
[X] I have added an app state migration, or my changes do not require one. (What are migrations?)

Thank you @pvinis !
Curious what @ashfurrow and @ds300 think as well. 😄
Since tracking often involves passing in relay data directly, it feels like a lot of indirection to create a separate function (that then needs arguments for all that data) just to construct the payload. This is not a strong opinion, by any means! We have a bunch of different patterns for tracking in the app, so if there's a new agreed-upon approach I'm happy to adjust. 🙏

I'm not personally tied to either option – and while I like consistency I'm not sure of the trade-offs in this case. Having it in the same file (and not separating out everything, like we did with query renderers until recently) feels good enough, but it could be that my use of VSCode is different in a way that makes consistency less important. So in that sense, I agree with Sarah that minimizing indirection would be more impactful than maintaining consistency. Just my 2¢, happy to follow-up!

I'm going to merge this in but am happy to follow up with any changes if need-be! Feel free to keep commenting.


latest supported cert-manager version with cert-manager-istio-csr?

we are looking to upgrade cert-manager and one of the questions we have it's what is the latest support cert-manager version with cert-manager-istio-csr 0.3.0?

Hi @smarunich, all tests successfully pass against cert-manager v1.7


optionally allow \n

I found here that \n is wrong char for string parsed by JSON.parse()
But some servers send it.
To avoid this I have to do
var  s=NSString(data: data!, encoding: NSUTF8StringEncoding)!
s=s.stringByReplacingOccurrencesOfString("\n",withString: "")
let json2 = JSON.parse(s as String)

instead of short (data: data)
So is it possible to optionally turn on possibility to allow \n in parsed string/data?

@djdance Sorry for the delay on this. It seems that the latest version of SwiftyJSON parses new lines correctly:
let json = JSON.parse("{\n    \"a\":\"b\"}")
print(json["a"].stringValue) // Prints "b"

Do you have an example of code that fails to parse correctly? Thank you

@ldiqual I have the same issue. I'm using 3.1.4 of SwiftyJSON. Here is my JSON from server
"{ \"code\":0,  \"info\":\"OK\",  \"result\":{\"tariffs\":[{\"tariff_id\":106, \"tariff_name\":\"dsa\",\"tariff_info\":\"here\r\nerror\" },{\"tariff_id\":108, \"tariff_name\":\"asd\",\"tariff_info\":\"dsa\" }]}}\r\n"
when i remove \r\n characters from "tariff_info":"here\r\nerror" is works fine.
I checked this JSON on http://www.freeformatter.com/json-validator.html and result is

The JSON input is valid according to RFC 4627 (JSON specfication).


Add hierarchical dispatch

Currently, every dispatch rule in Cowboy is dispatched from the root URL, i.e. /. The dispatch table is thus "flat" and does not really reflect the hierarchical nature of the Web. I would like to be able to write the dispatch rules as a tree instead of a simple list, with nodes and leaves.
See the following dispatch rules:
{'_', [
	{[<<"foo">>, <<"bar">>], ohai, []},
	{[<<"foo">>, <<"qux">>], ohai, []},
	{[<<"foo">>, <<"blah">>, <<"blah">>], ohai, []},
	{'_', kthx, []}
]}

Compare with:
{'_', [
	{[<<"foo">>], [
		{[<<"bar">>], ohai, []},
		{[<<"qux">>], ohai, []},
		{[<<"blah">>, <<"blah">>], ohai, []}
	]},
	{'_', kthx, []}
]}

Of course, this would serve no purpose if it was just a way to save a few keystrokes. I also want this to change the way the returned #req records are built.
A request to /foo/bar currently returns a #req record where path equals to [<<"foo">>, <<"bar">>] and raw_path to something like <<"/foo/bar">>. But what if ohai is a file-oriented handler which files are to be served from <<"/path/to/files">>? Let's add this path as a option to the handler in the dispatch rules:
{'_', [
	{[<<"foo">>, <<"bar">>], ohai, [{root, <<"/path/to/files">>}]},
	{[<<"foo">>, <<"qux">>], ohai, [{root, <<"/path/to/files">>}]},
	{[<<"foo">>, <<"blah">>, <<"blah">>], ohai, [{root, <<"/path/to/files">>}]},
	{'_', kthx, []}
]}

So the handler is now correctly configured, but the path field is still [<<"foo">>, <<"bar">>], naively ohai will try to serve <<"/path/to/files/foo/bar">> instead of <<"/path/to/files/bar">>. What can be done to strip this initial token? Yet another prefix option could be introduced:
{'_', [
	{[<<"foo">>, <<"bar">>], ohai, [{root, <<"/path/to/files">>}, {prefix, [<<"foo">>]}]},
	{[<<"foo">>, <<"qux">>], ohai, [{root, <<"/path/to/files">>}, {prefix, [<<"foo">>]}]},
	{[<<"foo">>, <<"blah">>, <<"blah">>], ohai, [{root, <<"/path/to/files">>}, {prefix, [<<"foo">>]}]},
	{'_', kthx, []}
]}

In my opinion this is not the right way to go: there is now a lot of redundant information in the dispatch rules and nobody can guarantee every handler writer will use the same option name. What I would like to see is a hierarchical dispatch tree where only the matched segments from the tree leaves would end up in the path field of the #req record passed to the handler.
Given the following tree:
{'_', [
	{[<<"foo">>], [
		{[<<"bar">>], ohai, [{root, <<"/path/to/files">>}]},
		{[<<"qux">>], ohai, [{root, <<"/path/to/files">>}]},
		{[<<"blah">>, <<"blah">>], ohai, [{root, <<"/path/to/files">>}]}
	]},
	{'_', kthx, []}
]}

A request to /foo/bar would return a #req record with a path field to [<<"bar">>] and a raw_path field left unchanged w.r.t. the former flat dispatch rules, thus making ohai correctly try to serve <<"/path/to/files/bar">>.
This change would ease configuration of my own fcgi handler and I think it would also simplify @klaar's cowboy_static handler while not breaking anything currently in use. The nodes could also have another element to set common options found in its children, like root in my example but this is not relevant to my case.
Dunno if I explained myself correctly, feel free to ask me any question you have.

Take a look at this:
https://github.com/erlyvideo/http_router/blob/master/priv/routes.conf
perhaps you will find some interesting ideas.

+1 I am doing this by hand right now, would be a great win if it could be part of cowboy :)


Module not showing up in module settings so can't be used.

Just like the title says, the module is not showing up in module settings and so it can't be used.

same :(


"Cocorăștii Mislii" is listed in the drop-down menu

Description:
When user writes "Cocorăștii Mislii" the location appears in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Cocorăștii Mislii"
Expected results
The location appears in the drop-down menu as "Comuna Cocorăștii Mislii, PRAHOVA"


Move outline to glsl

I've moved the outline rendering from the canvas to WebGL with modifications to the fragment shader.

It seems I've broken the rendering of the pie-chart centroids (OR-mode).
I'll try to resolve that before marking as ready for review.

It seems I've broken the rendering of the pie-chart centroids (OR-mode). I'll try to resolve that before marking as ready for review.

Ah, it seems centroids are broken before my changes:
// Retrieve color (FIXME - need to integrate into viewer manager)

I've filed the OR-mode bug as a separate issue. I'll see if switching centroid mode to WebGL solves that problem.

I've marked this PR as ready for review... I can handle the centroid rendering in another PR.

renders very fast.
currently draws whole cells:

Could it draw outlines? This would be important to see the underlying image data.
Getting error:
gl not defined when changing color and color mapping slider on the left channel panel:

adding a this solves it:
const size_2fv = [this.gl.canvas.height, this.gl.canvas.width];

I've moved more of the logic to the shaders... there's one more rendering optimization I'd like to make before reviewing for the merge.

I've moved more of the logic to the shaders... there's one more rendering optimization I'd like to make before reviewing for the merge.

I've solved the pie chart issue for 4+ markers... there is still an optimization on the ordering of selection kesy.


Multiple portfolios support

Are there any plans to have multiple portfolio functionality similar to program one?

Not currently. If you'd like, you can customize the Accelerator to include a custom Portfolios table and add the UI in the Power App.

I'm thinking about that. But the question is do I need a dataverse license to create a custom Portfolio table?

I have been modifying the app with just a Project Plan 3 license.  So far I have added a decision log and lessons learned log along side the current risks, issues, changes and status.

@hmbouk I dont suppose its possible to share that somehow? export that solution? I would like to add a decision and lessons learned but if you have already built that would save considerable work

@hmbouk I dont suppose its possible to share that somehow? export that solution? I would like to add a decision and lessons learned but if you have already built that would save considerable work

Yes.  I am working on two solutions that layer on top of the base project accelerator.  One solution adds the decision log and lessons learned logs.  The other I am using to modify any drop downs in the project accelerator so that I have drop down values that make sense for my clients.
I am implementing this with two clients and need to be able to add functionality that I feel is missing but also quickly customize things like business units, departments, etc for each client.  I have also modified the PftW Accelerator report to add report tabs for the decision log and lessons learned.  It is rough and still needs work but am happy to share.
To be clear, I'm not trying to fork the project accelerator, I have created solutions that add to the solution from this repository.  My changes my conflict with future functionality or maybe not.

That sounds good, I'm happy to enhance it etc. but having a start will certainly save duplicate effort

It is great to see this kind of collaboration in the community!
@hmbouk, nice use of best practices (additional solution layers) to add scenarios to the Accelerator.

It is great to see this kind of collaboration in the community!
@hmbouk, nice use of best practices (additional solution layers) to add scenarios to the Accelerator.

Any suggestions on the most appropriate way to share my solution and updated PBI report with the community?  Create a repository for my solution(s)?

@hmbouk, yes, creating a new GitHub repo and sharing it there is a good approach.


Fix build of 2.7 with MBEDTLS_CERTS_C disabled in config (fixes #4206)

Fixes #4206
Description
Build of the 2.7 branch fails when MBEDTLS_CERTS_C is disabled.
This only happens with the 2.7 LTS versions. Not affected: 2.16.6 LTS, 2.25.0, development and master, as far as I tested.
Reason: Caused by wrongfully placed closing brackets between #ifdef's, copy & paste hell unleashed ;-)
Origin: The bug was introduced in PR #2498
Status
READY
Requires Backporting
NO / This problem only applies to the mbedtls-2.7 branch.
Migrations
NO

And thanks for reporting the bug, by the way.

Glad I could help :)
Thanks for adding the changelog entry, I didn't want to interfere with this process.
Merging is blocked for me, so please feel free to merge once you are ready.


Adapt to Coq PR #14846: references to inductive types in the type of constructors are directly Ind rather than Rel nodes

We insert a translation function which emulates the previous behavior.
This is to be merged synchronously with coq/coq#14846.

Please merge now

Hmm, I guess we should do that in metacoq itself rather than the quoting functions, but that's minor.


'aiida_optimize.engines._result_mapping' is not imported exception

Hi @zooks97 , I got the following exception when I running the convergence test. Do you have any idea how this happened?
I just paste part of the traceback, ask me for more information if it is needed.
....
  File "/data/CONDA_ENV/aiida-production/lib/python3.7/site-packages/yaml/constructor.py", line 593, in construct_python_object
    instance = self.make_python_instance(suffix, node, newobj=True)
  File "/data/CONDA_ENV/aiida-production/lib/python3.7/site-packages/yaml/constructor.py", line 566, in make_python_instance
    cls = self.find_python_name(suffix, node.start_mark)  File "/data/CONDA_ENV/aiida-production/lib/python3.7/site-packages/yaml/constructor.py", line 593, in construct_python_object
    instance = self.make_python_instance(suffix, node, newobj=True)
  File "/data/CONDA_ENV/aiida-production/lib/python3.7/site-packages/yaml/constructor.py", line 566, in make_python_instance
    cls = self.find_python_name(suffix, node.start_mark)
  File "/data/CONDA_ENV/aiida-production/lib/python3.7/site-packages/yaml/constructor.py", line 538, in find_python_name
    "module %r is not imported" % module_name, mark)
yaml.constructor.ConstructorError: while constructing a Python object
module 'aiida_optimize.engines._result_mapping' is not imported
  in "<unicode string>", line 49, column 10:
          0: !!python/object:aiida_optimize.e ...
  File "/data/CONDA_ENV/aiida-production/lib/python3.7/site-packages/yaml/constructor.py", line 538, in find_python_name
    "module %r is not imported" % module_name, mark)
yaml.constructor.ConstructorError: while constructing a Python object
module 'aiida_optimize.engines._result_mapping' is not imported
  in "<unicode string>", line 49, column 10:
          0: !!python/object:aiida_optimize.e ...

Here is the example file I changed a little on top of your demo https://gist.github.com/unkcpz/87d8564560ecb8066b390dea09ef80d5

Seems related to https://github.com/aiidateam/aiida-core/issues/3709, although I don't quite understand why this showed up here (and not in our tests).
In this branch I changed the __init__.py's to import all submodules directly - can you check whether that might work as a work-around?

Hi @greschd the import_everything branch still not working and raise the same exception once I restart the daemon :pensive:
the version of yaml is:
aspy.yaml==1.3.0
ruamel.yaml==0.16.12
ruamel.yaml.clib==0.2.2

still not working and raise the same exception once I restart the daemon 😔

Well, that was a bit of a long shot, didn't really expect that to work.
Hm, there should be a version of pyyaml installed, from this requirement: https://github.com/aiidateam/aiida-core/blob/develop/setup.json#L48. Maybe you need to grep with -i, because it's listed as PyYAML.

To confirm this is is related to https://github.com/aiidateam/aiida-core/issues/3709, you could apply the following patch to aiida-core and check if the problem is still present.
Note that this is unsafe in the following sense: If you import an AiiDA archive from an untrusted source that contains maliciously crafted "checkpoints", it can execute arbitrary code. The proposed solution in https://github.com/aiidateam/aiida-core/issues/3709 is to remove all checkpoints when importing.
If you never load untrusted archives however, the patch below is sufficient.
diff --git a/aiida/orm/utils/serialize.py b/aiida/orm/utils/serialize.py
index 23aa68348..70fc09070 100644
--- a/aiida/orm/utils/serialize.py
+++ b/aiida/orm/utils/serialize.py
@@ -176,7 +176,7 @@ class AiiDADumper(yaml.Dumper):
         return super().represent_data(data)

-class AiiDALoader(yaml.FullLoader):
+class AiiDALoader(yaml.UnsafeLoader):
     """AiiDA specific yaml loader

     .. note:: we subclass the `FullLoader` which is the one that since `pyyaml>=5.1` is the loader that prevents

@greschd , my pyyaml version is 5.1.2. For the time being, I'll use the workaround, thanks!


Callsign too big "hides" colon delimiter

When spotter callsign is too big, colon delimiter :  will not show and the parser will fail to parse the dx string correctly.

Mistake issue number in commit :/


Grad-Cam with Inceptionv3. TypeError: unhashable type: 'Dimension'.

Hi, I'm trying to follow the GradCam code but I got an error: TypeError: unhashable type: 'Dimension'.
Here is my model:
cnn_vec3 = InceptionV3(input_shape = (224,224,3), include_top = False, weights = 'imagenet', input_tensor=None)
x = cnn_vec3.output
x = GlobalAveragePooling2D()(x)
x = Dropout(0.2)(x)
inp1 = cnn_vec3.input
dense_layer = Dense(1024, activation = 'relu')(x)
dense_layer = Dropout(0.3)(dense_layer)
dense_layer = Dense(1024,activation='relu')(dense_layer)
dense_layer = Dropout(0.3)(dense_layer)
output_layer = Dense(1, activation = 'linear', name ='predict')(dense_layer) # linear is what 16bit did
model = Model(inputs=inp1,outputs=output_layer)

here is the error:
Traceback (most recent call last):

  File "<ipython-input-18-8ae3fe8aeecf>", line 2, in <module>
    x = bone_age_model.get_layer(layer_name)(x)

  File "C:\Users\Cong\Anaconda3\envs\py36_2\lib\site-packages\keras\engine\base_layer.py", line 434, in __call__
    self.assert_input_compatibility(inputs)

  File "C:\Users\Cong\Anaconda3\envs\py36_2\lib\site-packages\keras\engine\base_layer.py", line 339, in assert_input_compatibility
    x_shape[int(axis)] not in {value, None}):

TypeError: unhashable type: 'Dimension'

Is there any suggestion?

I can't reproduce your error, can you share a minimal example raising this error?

Hi @Luca1236a ,
I have tried replicating the error with the provided code snippet. The error can't be reproducible now. Either this is resolved in latest versions or the code snippet is not enough to replicate it.
Could you please check the attached gist and let us know if it resolved already.If not please submit a reproducible code snippet. Thanks!


CI not running clean

🌈  CI seems to be not running clean because of:

spec/parser/options_spec.rb:119  #777
ruby 3.0+ failures with specs expecting intracoversion between final hash argument and keyword args #779
coveralls SSL error (seems to be same as https://github.com/lemurheavy/coveralls-ruby/issues/163 - maybe replace with coveralls-reborn?) #778

There's a combination PR #780 if you prefer a simple one-shot to get to green.

I think the combo PR looks fine! @rafaelfranca


Load site interface translation by default

Since v8, user can translate site interface by default. Why don't we enable loading site interface translation by default?
Note: Please merge this PR after merging #5073.

Whoops: I forgot about this PR and added the same patch to https://github.com/concrete5/concrete5/pull/5010


Suggest Record labels and Union cases

I this "Replace with" suffix is not needed.

How is C# doing this? The text is from earlier commit. But we can change it.

ready for review

Hmmm.  Not sure I like surfacing the possibility of something completely unrelated, like GetHashCode when we're specifically trying to fix a Record label or DU case.  That's likely going to result in quite a few people logging bugs with the feedback tool.

The GetHashCode can probably be filtered out here since it's not a static method.

Okay.  I think if we can filter out non-static members on types then all the suggestions should seem relevant.

just took a quick look. this is not easy to determine at this location since we don't know if we are invoked in static or member position. So since this PR only improves the current situation it should still be merged. I have an idea for the filtering and will apply that later.

Sounds good.

Ok need to fix couple of tests tomorrow

Ok all tests fixed

@cartermp since I saw your list on twitter. This pr is not for the analyzer. It's actually just the error message improvement.
But since the code fix stuff is already merged this error message is automatically used in the analyzer. Ionide will profit as well automatically when this got merged to FCS.

Good to know!


#12, it's now possible to configure various timeouts, scheduling is

now also configurable

Hi, we integrated your changes in our pull request(#14) because merging would be hard.

#14 had everything needed, thanks @bomgar


On the web the tooltip and trigger component is rendered in the wrong place

When I run this on the web I have this issue

code:
(im using nativewind so thats why I'm using classes)
 const [isVisible, toggle] = useReducer((state) => !state, false);

    const renderContent = useCallback(() => {
      return (
        <TouchableOpacity
          className="bg-surface-default px-4 py-2 rounded-2xl shadow-md"
          onPress={toggle}
        >
          <Text>Welcome to React Native Tooltiplize 🥳</Text>
        </TouchableOpacity>
      );
    }, []);

    return (
      <View className="flex-1 justify-center items-center">
        <Tooltip
          position="right"
          offset={8}
          renderContent={renderContent}
          isVisible={isVisible}
          withOverlay
          onDismiss={toggle}
          pointerStyle={{ width: 16, height: 8 }}
          pointerColor="white"
        >
          <Button onPress={toggle} text="Press Me"></Button>
        </Tooltip>
      </View>
    );
  },

works nicely on android and ios

I think its related to the styling of the outer container and I was able to find a way around it by just changing some of that so I'll close this. An outer container had padding that I guess threw off the calculation.


fix(Suffix): Suffix will be broken from now on

Leo testing if Travis catch error on my test

Worked perfectly!


When Extending Theme It gets duplicated multiple times

Describe the bug
When extending the theme to overwrite it duplicates all the elements multiple times. This is with DSpace 7.6.
So what I did was copy the dspace theme, made it called "theme1" and made my normal changes there. I then created theme2 and want to apply it to specific collections to add additional metadata fields to some of the views.
It looks like it's rendering the original version, and the extended theme? See the photo below

To Reproduce
Steps to reproduce the behavior:

Create custom theme by copying the dspace theme (theme1)
Enable your new theme1
Create a new theme (theme2) that you want to change only src/themes/theme2/app/item-page/simple/item-types/untyped-item/untyped-item.component.html in
Enable themes in config.yml

themes:
  - name: theme2
    extends: theme1
    uuid: '6d684812-6d29-4564-8b51-f5670957936b'

  # default theme, based on DSpace
  - name: theme1

Expected behavior
I would it to only change the elements defined in

I made the repo public https://github.com/kstatelibrariesit/dspace-angular/tree/etdr-theme/src/themes/etdr, in case it might make it easier to find what I might have messed up, if it's a user error.

We are experiencing the same bug, and I have some additional info.  If I select a themed community, for example, via it's handle (/handle/12345/3434), the themed page renders correctly even though the url reverts to its /communities/uuid form.  I can even refresh the page successfully.  This is regardless of whether I use the handle or the uuid as the theme selector.  If I select a page via its uuid, I experience the duplication of page elements as described above.

I would like to claim this issue

Atmire would like to claim this issue

@alexandrevryghem : Sounds great! Thanks, I'll assign this to you for your team to work on.

For those following this issue, it now has a possible fix in #2395  Testers are welcome/encouraged! (The fix is also rather small, so it looks like you could copy it into your 7.6 instance if you are impacted)

I forgot to circle back that #2395 does fix the duplication issue I was seeing! Thank you @alexandrevryghem!


ENH: support for circular input

What does this implement/fix?

This implements support for circular input in spatial.SphericalVoronoi. The current implementation supports geodesic input, but not other types of rank-deficient input in 3D.

Random aside, but I think the email address used for your git commits is missing a character, so that GitHub isn't automatically associating your commits/contributions back to your identity the way it typically does.

Thanks for spotting that! I have updated my commit email address.

Looks good now, merging, thanks @pmla

I drafted a short release note, feel free to edit it: https://github.com/scipy/scipy/wiki/Release-note-entries-for-SciPy-1.5.0#scipyspatial-improvements

Thanks Tyler. The release note looks good too.


getting error on npm run dev [BUG]

Add more details such as your version of Node.

getting these 2 errors after creating a hydrogen app.
hope this helps,
node version : v16.8.0
using ubuntu on wsl,
WIndows 10
Steps
npx create-hydrogen-app
npm install --legacy-peer-deps
npm run dev

followed by

getting these 2 errors after creating a hydrogen app.
hope this helps,
node version : v16.8.0
using ubuntu on wsl,
WIndows 10
Steps
npx create-hydrogen-app
npm install --legacy-peer-deps
npm run dev

followed by


localhost:8000 and how to share that?

local ip:8000       not work
i tryed myip:8000 and nothing
portforward 8000      not work
please help me.

this runs on 5000 man

localhost:8000 that work
localhost:5000 not work
mayebe run on 8000 port :d

@daproject85 Are you sure it runs on port 5000? According to my netstat Python is hosting something on port 8000...

I'm running mine bro , I didn't mod anything , straight OOTB

On Jul 24, 2016, at 10:12 AM, DyonR<EMAIL_ADDRESS>wrote:
@daproject85 Are you sure it runs on port 5000? According to my netstat Python is hosting something on port 8000...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Correctly set page color metadata for symbol pages

Bug/issue #, if applicable: rdar://107962126
Summary
Fixes a bug where the @PageColor metadata directive was ignored when used on symbol pages.
Testing
Add:
@Metadata {
   @PageColor(purple)
}

to a symbol page and confirm that the page renders as expected.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

@swift-ci please test

@swift-ci please test


When will the Radeon RX 5700 XT support ROCm

I purchased the RX 5700 XT and was planning to use it in my ML projects. But I realized that the card has not yet received ROCm support. Is there a scheduled release date? If not, I will return the card back to the store. Hopefully, it will be answered quickly and precisely.

AFAIK the most accurate statement currently available is this comment. My interpretation of the comment is that nobody official is willing to give a hint when it will be released. In principle it could even take years before it is supported.
Between the lines it looks like as if they intend to eventually support Navi. But personally I wouldn't buy a Navi card if I want to do ML within the next months.

Thank you for your reply. I'm sorry to hear that. I am going to return my card.

I am going to return my card.
@omerferhatt
so why can't you code the kernels of your ML projects with OpenCL ?

Why returning, use plaidML with Keras. It works like charm.


findProxyFromEnvironment is not picking up environment variables defined by flutter run --dart-define=...

Hi,
I'm using the following code to create a HttpClient and make a request (Flutter 3.13.9, Dart 3.1.5, macOS, iOS Simulator):
print(const String.fromEnvironment('HTTPS_PROXY');
final httpClient = HttpClient()
      ..idleTimeout = const Duration(seconds: 3)
      ..findProxy = HttpClient.findProxyFromEnvironment;

    await httpClient.getUrl(Uri.parse('https://my-example-api.com/foobar'));

I run this piece of code via flutter run --dart-define=HTTPS_PROXY=localhost:8888.
As expected from the print, I get whatever I've set in --dart-define, in this case it prints localhost:8888 to the console.
However, I can see, that findProxyFromEnviroment is not using the proxy.
Then, I've tried this here:
print(const String.fromEnvironment('HTTPS_PROXY');
final httpClient = HttpClient()
      ..idleTimeout = const Duration(seconds: 3)
      ..findProxy = (final uri) => 'PROXY ${const String.fromEnvironment('HTTPS_PROXY')}';

    await httpClient.getUrl(Uri.parse('https://my-example-api.com/foobar'));

And suddenly, the proxy is working as expected.
According to the documentation of findProxyFromEnviroment, it should pick it up from HTTPS_PROXY, but it does not.
// Edit
If I do the following:
class ProxyOverrides extends HttpOverrides {
  @override
  String findProxyFromEnvironment(final Uri url, final Map<String, String>? environment) =>
      super.findProxyFromEnvironment(url, {
        // ignore: do_not_use_environment
        'HTTP_PROXY': const String.fromEnvironment('HTTP_PROXY'),
        // ignore: do_not_use_environment
        'HTTPS_PROXY': const String.fromEnvironment('HTTPS_PROXY'),
      });
}

// in main:
HttpOverrides.global = ProxyOverrides();

then it works also as expected. No sure, if this is the real solution, or if the documentation is wrong for Flutter, or if the implementation has a bug.

You are being confused by poor choice of naming in dart core libraries.
There are two different things which are called almost the same:

OS environment variables: things you can define in your shell by doing export HTTPS_PROXY=...;
Dart's environment declarations: compile time values passed via --dart-define and -D flags.

findProxyFromEnviroment is looking at OS environment variables.
@lrhn should we maybe deprecate int.fromEnvironment and friends and provide a more aptly named int.fromDartDefine?

You are being confused by poor choice of naming in dart core libraries.
There are two different things which are called almost the same:

OS environment variables: things you can define in your shell by doing export HTTPS_PROXY=...;
Dart's environment declarations: compile time values passed via --dart-define and -D flags.

findProxyFromEnviroment is looking at OS environment variables, not at Dart's environment declarations.
@lrhn should we maybe deprecate int.fromEnvironment and friends and provide a more aptly named int.fromDartDefine?

Gotcha.
so my "workaround" I've edited is the solution for the issue because it now looks at the dart environment declarations. Ok, it would be nice if the wording would be more precise in the future because, according to the documentation, I'm in the flutter documentation, so I was kind of expecting it to work.


Difference in page element structure relevance to CSS selectors

Following the discussion in #306 I attempted to set a native obsidian "cssclasses" property on the web. Here I wanted to override the overflow-x: auto style property on certain  elements so I could display the full width of some wide tables without the need to scroll.
The class was set with this property section:
---
cssclass: "wide-tables"
---

This sets the class wide-tables on the main element, but there were div elements in the HTML that contain a style="overflow-x: auto;" property, which I needed to override. I didn't find a smart way to select these.
In obsidian the following css worked.
div.wide-tables > div > div {
	overflow-x:visible!important;
}

However after export the structure of the webpage changed so I needed to change my selector to the following:
div.wide-tables > div > div > div > div {
	overflow-x:visible!important;
}

I am thinking the style="overflow-x: auto;" property is unfortunate in the Obsidian html, so the best course of action might be to ask Obsidian to change this to a CSS controlled class with a variable.
The good news is that cssclasses itself worked without any problems.

Hmm, I think for the moment your work around is probably what I will stick with. I doubt the obsidian team will want to move those css declarations into classes because, like you said, they are not applied to any specific type of element that's easily selectable. And adding a class rule just for a single overflow declaration is a little bit weird. Additionally, this is only a problem for my plugin so they don't have much incentive to change it. I'll look into ways I could improve this though.

@hberge A better solution here would be to use an attribute selector which filters out only the elements having this style. You can do:
div.wide-tables div[style='overflow-x: auto;']
{
	overflow-x: visible !important;
}

Which will work in both obsidian and the website.

That is an excellent solution! Why didn't I think about that? Thank you so much. I think this can be closed for now, as long as there are no-one else having difficulties with the structural difference, so doing that. :)


Slack Commands - "In Channel" vs Ephemeral

Hi,
I couldn't see how to have the bot respond with "in channel" message when using botman to answer slack commands. Did I miss something?
...deon

Hi,
what do you mean by "in channel" messages?

https://api.slack.com/slash-commands#responding_to_a_command
See the section "In Channel" vs "Ephemeral" responses
IE: When the bot replies to a slack slash command, the response is only visible to the person who instigated the command. It is possible for the response to be visible to everybody in the channel, hence "in channel" response type.

You can pass additional parameters to the response.
For example:
$botman->hears('your command', function($bot) {
    $bot->reply('respond in channel', [
        'response_type' => 'in_channel'
    ]);
});

Sorry, this is not working.
It would appear that slash commands are defaulted to a "text" response SlackDriver::reply().
If I change it to a JSON response (calling SlackDriver::respondJSON()) and forcing content-type to application/json then it works.
It might be desirable to default slash command responses to be json responses so that more advanced responses could be returned (e.g.: with attachments, pretext, etc).


Needlessly architecture-specific build system

Describe the bug
The build system is needlessly architecture-specific: for example, all Unix platforms are assumed to be x86, and all Android platforms are assumed to be armv7. The main issue this causes is that the installation directory on Linux is always /usr/lib/x86_64-linux-gnu, which is not in the library path on non-x86 systems (like the Raspberry Pi).
To Reproduce
Steps to reproduce the behavior:

Build and install on Raspberry Pi (tested with 5 under the recommended official RPi OS image, others should behave similarly); build should succeed.
Program cannot be started because /usr/bin/qlcplus: error while loading shared libraries: libqlcpluswebaccess.so: cannot open shared object file: No such file. However, this file exists and was installed to its intended directory according to make install.

Expected behavior
As far as no architecture-specific code exists in QLC, everything should just build on aarch64, RISC-V, and other platforms.

Where are these references you're talking about?
Only appimage and coverage builds have hardcoded x86_64-linux-gnu paths.

Where are these references you're talking about? Only appimage and coverage builds have hardcoded x86_64-linux-gnu paths.

These are in the install paths. As I say, the build succeeds without issues. For instance, to make a basic QLC+ work under Raspberry Pi 5, I quickly hacked:
diff --git a/variables.cmake b/variables.cmake
index 3a89857f8..6950ab16e 100644
--- a/variables.cmake
+++ b/variables.cmake
@@ -89,7 +89,7 @@ if (WIN32)
 elseif (APPLE)
     set(LIBSDIR "Frameworks")
 elseif (UNIX)
-    set(LIBSDIR "lib/x86_64-linux-gnu")
+    set(LIBSDIR "lib/aarch64-linux-gnu")
 endif ()

 if (ANDROID)

If you're building with qmake or not following the wiki instructions then this report is invalid

As I should have said more clearly, I am building exactly according to the wiki instructions, using a different CMake path to account for the different Qt5 CMake file. I have tested this issue with both the Ninja and Make generators of CMake, so they do not play a role (I prefer to build with ninja but am aware that it causes issues sometimes; this is not one of them).

You're not building the latest sources
https://github.com/mcallegari/qlcplus/blob/master/variables.cmake#L92
This has been fixed months ago.

Then why is this not fixed on the last 5.0 beta? I prefer to build relatively stable tags instead of the main branch.

Check the dates
4.13.1 - May 31st 2024
5.0.0 beta3 - December 30th 2023
So how can a fix from November 2024 can be included in one of the above?
If you can't live without a one-line fix that you can apply to 4.13.1, then you need to wait for the next release.

Hm. I don't understand the release policy of QLC in comparison to other open-source projects. (And in either case, I don't even know with the branching setup whether it applies to the last 4.x patch release, I hope you have checked that)


Mandragora - if using Pomander of Alteration

Mob Id
5041 - Pygmaioi
Content Type
DeepDungeon
What threat level sould the mob have
Easy
What agro type does the mob have
None
Vulnerabilities for the enemy

[ ] Stun
[ ] Heavy
[ ] Slow
[ ] Sleep
[ ] Bind
[ ] Undead

Additional mob text guide
No response

Seems to be related to #203 as it has the data in the files.


[WIP] SkiaSharp 2.88

What does the pull request do?
Update SkiaSharp to a 2.88.0 preview build
What is the current behavior?
SkiaSharp 2.80.2 is currently used.
What is the updated/expected behavior with this PR?
Hopefully no changes other than more available SkiaSharp APIs.

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

I opened this PR mainly to see if the CI pipeline succeeds and get some unstable nuget-packages to play around with. Hope this is ok.

superseded by https://github.com/AvaloniaUI/Avalonia/pull/6902


(INF): add Rust annotator

At the moment it only highlights attributes
@Atsky please review.
I'm not sure, where Colors should go, there is a similar class in RustHighlighter.

Better to extract all Colors to separate class


aerogear/update tempalte dir

Changes

updating some author company etc to aerogear
updating path to template file after repo change

@PhilipGough

@laurafitzgerald AeroGear is usually written with capital A and G. Other than this - LGTM.

@matskiv aerogear -> AeroGear done. merging.


ROSSCO-Apollo steering PID controller questions

While looking at the code of rossco_apollo, I noticed the usage of a "PID" controller for a closed-loop control of steering commands.
However, in each call of closedLoopControl, a new local variable state is initialized using createPIDState which always re-initializes the integral and pre_error terms to 0. The controller doesn't seem to keep track of its previous states.
This means that every call to pidController will compute an integral term equal to the error and a derivative term equal to the error as well. Eventually, this means that the PID controller of parameters Kp, Ki, Kd is equivalent to a P controller of parameter (Kp+Ki+Kd).
My questions are:

Why would we need a PID controller on the first place? Wouldn't Apollo's control module be enough to generate smooth steering commands?
Am I missing something in the logic of this code? If not, why is the PID controller equivalent to a P controller ?
I understand that this is a code example but Apollo's ControlCommand variables also come with a "steering_rate" command that is currently ignored by roscco_apollo. What would be the best way to use OSCC to take into account the steering rate ?

You are right, the current version of the controller work as a P controller and not as a PID. Thank you for noticing that. We will make sure to correct that for the next release.
DriveKit/OSCC expects a torque command for the steering. Apollo only provides steering angle and rate commands. The controller role is to evaluate a torque command to feed to DriveKit/OSCC from Apollo's steering angle command. Yes, we could also use the steering rate command to complete/improve the controller.

Hi, @bbidault2, @FlorentRevest,
Would you share with me, if you have any updates specifically on how to convert a steering angle command (from Apollo, Autoware, etc) to a steering torque command (to roscco in DriveKit)?
Thanks in advance!

In the end I just ended up using the angle control command of the DriveKit. It is not part of oscc but is an additional feature of the drivekit that does the control for you and I found it worked well enough

@FlorentRevest, thanks for your reply. If you don't mind, would you please tell me a little bit more about that additional feature of DriveKit? Is it described in your github repo or somewhere else? I think I have to follow the way you walked through. Thanks in advance!

This feature was documented as part of the DriveKit.
You can find my Apollo implementation here
https://github.com/nap-lab/apollo/blob/v3.0/modules/canbus/vehicle/niro/protocol/steering_angle_command_b8.cc

@FlorentRevest, thanks for your sharing! :)


upgrade beacon package to 1.0.2

Anything to add in the description or readme of beacon package??
@ThierryThevenet @hawkbee1

Just need to add thanks to Tezos foundation and AltMe as exemple of this package usage.


Added toastify notification on submit and copy button

Fixes Issue
Solves Issue #2
Description

Added pop-up notification to Submit button and Copy button.
On successful/wrong submission message is displayed accordingly.
The copy button changes to a green tick for 2 seconds on successful text copy.

Tech Stack Used

Used React - Toastify library of ReactJS to implement appropriate notifications.

Additional changes

Set the default color of the copy button to red so that it looks good when it changes to green tick.

Screenshots

@PranabKumarSahoo kindly go through the changes made and accept the PR if found alright

Hi @Anubhab-03,
Excellent work on adding the Toastify notification feature to the Submit and Copy buttons for all sections! 👏
That looks great but If the Tostify Notification could be shown in Top Right corner, It'd be more seamless user experience. Right!!
After changes, You can raise the PR. Then I'll merge it. No issues.
#Good Luck! ✌

Good job @Anubhab-03,
I'm merging the PR. Thanks for the contribution. ⭐

Feel free to create/work on more issues.
#Good luck! ✌

Thanks a lot, @PranabKumarSahoo for merging the PR. I enjoyed contributing to your project!!

Just a query, any idea how will the points be awarded and where to check the leaderboard

I guess the scores will be counted as per the Quine DevRank Points & for the Leaderboard, there might be released after the end of the program i think.
For clarification, You can ask our mentors in the Discord project channel.


LKA error on 2018 RAV4 at around 1:10 min after the car started

Describe the bug
Device: Comma 3
Car: 2018 rav4
Openpilot version: 0.9.6
(Also tried latest sunnypilot and frogpilot, with same problem)
Issues:
Comma Device show:
LKA failure, restart car to re-engage openpilot
RAV4 display show:  front camera failure & lane keep assist failure (something like that, I forgot the exact wording)
Reproduce the issue:
After the car started about 1 hr 10min.  This error show up.  It will show up with openpilot, sunny pilot, frogpilot (latest version). It will also have issues regardless of the cruse control is engaged or not.
Extra test that I did to eliminate it was the car problem.  I unplug the USB on the comma 3 and driven the car for 2 hours with cruise control engaged, disengaged and turn on and off the LKA button without any error.
Hope this report help to locate the bug.  I think the 1:10 after car start error play a big part on this bug hunting.
Provide a route where the issue occurs
64de1f0143663494
openpilot version
0.9.6
Additional info
I cannot locate the route that is long enough. But it will be on Mar29, 24 between 1600 - 2300 PST.
And Mar31, 24 between 1300 - 2000 PST.
I have to make multiple stop to restart the car to re-engage the open pilot.

This is an issue with your 3rd party SDSU hardware.


Running last version of react-scripts will cause to launch the app in both Browser and Electron window

Hi,
i was updating the app to the latest versions of the packages- Everything was fine until i updated the react-scripts package to the last version (2.1.3).
Now running yarn dev will cause to launch the app in the browser and lately in the electron window.
Any idea on how to fix it?

I have a fix for this. In package.json  under scripts change  "start": "react-scripts start", to  "start": "SET BROWSER=none&&react-scripts start", . That's what worked for me.

As per this comment, you can also create a .env file in the root of your project with BROWSER=none as the contents - this works perfectly and is a little bit nicer than setting the BROWSER variable in the start script! 😄


Swapping sw-toolbox and sw-precache for workbox-sw and workbox-build

@jeffposnick @Garbee
What do people think of this?
The fiddling between dev and prod makes this a bit messy, so very open to alternative approaches.
I was thinking of adding dev and prod to app/third_party/ and then just switching the import script at run time but the version number is still going to be tricky.

I think there's actually value in us completing this PR and changing over WSK to just be a reference of a modern build process.
Between Matt's PR here, our docs and the PWA codelabs I've been able to migrate more of my older WSK-based apps to Workbox and found enough value here that it might be worth adjusting for the feedback and landing. Two cents :)

No idea what the npm run test is doing. The build is fine but somewhere between git status and grep, something is borked.
gulp && git status | grep 'working directory clean' >/dev/null || (echo 'Please commit all changes generated by building'; exit 1)


Disallow importing while operations are in progress

This can be done client-side.

Implemented in 3.2.0.


add: inject ip address and node name into tags

Needed ability to inject node name and ip address into tags of the instance.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hello, thanks for your suggestion. I reworked your code a little bit so that it will be easier to support more sequences in the future. Please look at the version I just committed, and I am open to your feedback. Note that I renamed the sequence %n by {node_name}, and %i by {ip_address}. Is that OK for you?

Hello, I have not heard from you. I hope that the changes I made to the code are aligned with your initial requirements. I'll close the pull request, but please let me know if you have question or feedback. Nicolas


Auto Layout Issue

Hi,
I'm using Storyboard. I've created 2 container views, a couple of toolbars, etc, and when I present it with MZFormSheet, I get the following auto layout issues:

If I take out MZFormSheet, and present it regularly, it works just fine. I tried doing the symbolic breakpoint to maybe pinpoint it in this library, but it only breaks somewhere in creating the storyboard.
Code:
+ (MZFormSheetPresentationViewController *)orderSummaryController:(Order *)order
{

    OrderCheckoutController *controller = [[UIStoryboard storyboardWithName:@"OrderCheckoutStoryboard" bundle:nil] instantiateViewControllerWithIdentifier:@"checkout"];

    controller.order = order;

    MZFormSheetContentSizingNavigationController *navigationController = [[MZFormSheetContentSizingNavigationController alloc] initWithRootViewController:controller];

    MZFormSheetPresentationViewController *formSheetController = [[MZFormSheetPresentationViewController alloc] initWithContentViewController:navigationController];

    formSheetController.presentationController.shouldDismissOnBackgroundViewTap = NO;
    formSheetController.presentationController.movementActionWhenKeyboardAppears = MZFormSheetActionWhenKeyboardAppearsMoveToTop;
    formSheetController.presentationController.contentViewSize = controller.preferredContentSize;
    formSheetController.contentViewControllerTransitionStyle = MZFormSheetPresentationTransitionStyleSlideFromBottom;

    return formSheetController;
}

And in my content controller:
- (BOOL)shouldUseContentViewFrameForPresentationController:(MZFormSheetPresentationController *)presentationController
{
    return YES;
}

- (CGRect)contentViewFrameForPresentationController:(MZFormSheetPresentationController *)presentationController currentFrame:(CGRect)currentFrame
{
    CGFloat preferredHeight = self.preferredContentSize.height;
    CGFloat height;

    if (self.paymentStepController.addPaymentController.creditCardController.shouldShowCardIOView) {
        height = preferredHeight + 240;
    } else {
        height = preferredHeight;
    }

    currentFrame.size.height = height;

    return currentFrame;
}

You are setting wrong contraints if you are using resizing between them ther are exists until transition is finished so you must be carefound with constraints sticked to the bottom. This is not issue in library but how it works and constraints when resizing

Hi, thanks for the reply. I'm using pretty standard constraints - and the interface builder is not complaining. What do you see wrong with this? I love this library (seems very well made) and prefer it over the standard FormSheet due to the movement to the top when the keyboard appears. Hopefully I can get it to work.

Check how the constraints are set in example project when there is resizing animation between view controllers.

Perfect, it's working now. Thank you

Cool :)


Updated comparison of Prometheus vs Sensu Go

Hi there @juliusv @brian-brazil  :wave: first time contributor to Prometheus here, with hopefully more contributions to come (we're using Prometheus a fair bit at Sensu, including standardizing on Prometheus for instrumenting the Sensu platform).
We have wanted to update the "Prometheus vs Sensu" content in the Prom docs for a long time, but never got around to it until now. We'd like to be a good citizen in the Prom community, so please let me know if there are any changes I ought to make to the content here and I'll be happy to adjust it accordingly.
#monitoringlove
Signed-off-by: Caleb Hailey<EMAIL_ADDRESS>

Thanks for your PR, I understand Sensu has changed a bit since this was first written so could probably do with some freshening up. A lot of the proposed text comes across as marketing copy, whereas this is intended to be an impartial high-level technical comparison. Can you try to adjust this to make it more like the others, and stick within the categories?

Thanks from me as well! I agree with the general sentiment that it would be great to update the Sensu section (and others as well), but parts of the wording also seem a bit too much like marketing copy to me. Generally the suggestions by @SuperQ seem to go in the right direction.

Thanks, @brian-brazil, @juliusv, and @SuperQ :+1:
We'll take another stab (starting with @SuperQ's suggestions) and come back with a fresh revision.
Cheers! 🍻

@brian-brazil @juliusv @SuperQ we updated the content per your requests/recommendations. Let me know if this works.
Cheers 🍻

Thanks for your feedback, @brian-brazil I hope you had a nice holiday and that your 2021 is off to an excellent start!
All of your comments have been very helpful so far – much appreciated! I generally agree with your suggestions to trim our edits, and I think our most recent update will address most of that feedback. The only bit of constructive criticism I'm confused about is the comment regarding the "architecture" section. Even if we avoid anything that remotely resembles "marketing", I would expect that the most technically accurate way to describe Sensu's architecture is to list all of the moving parts and their high level roles/functions (tl;dr: backends provide api/scheduler; agents connect to the backend via pub/sub transport; backends can be clustered for HA and federated configurations are supported, as needed); but your comment suggests that the architecture subheading "is to talk about clustering/HA" and "the rest is not relevant".
I'm assuming the non-relevant parts were not technical enough and smelled too much like marketing (a fair criticism), for example: "Sensu is a primarily agent-based monitoring solution (agentless applications are also supported)"?? I've rewritten this section to just list the components and their technical role/function. I hope this works, but I'll be happy to strip away everything that's not just about clustering/HA, as needed. Like I explained above, I'm not trying to work around your recommendations here, I just didn't understand this one bit of feedback.
I also reworked the summary section in a similar style as the InfluxDB section to (hopefully) highlight the few similarities between Sensu and Prometheus, as well as the use cases (which are quite different IMO). I think this is a better framework for the summary, but let me know if you want me to change it.
Cheers 🍻 #monitoringlove

Thanks for your feedback, @brian-brazil I hope you had a nice holiday and that your 2021 is off to an excellent start!
All of your comments have been very helpful so far – much appreciated! I generally agree with your suggestions to trim our edits, and I think our most recent update will address most of that feedback. The only bit of constructive criticism I'm confused about is the comment regarding the "architecture" section. Even if we avoid anything that remotely resembles "marketing", I would expect that the most technically accurate way to describe Sensu's architecture is to list all of the moving parts and their high level roles/functions (tl;dr: backends provide api/scheduler; agents connect to the backend via pub/sub transport; backends can be clustered for HA and federated configurations are supported, as needed); but your comment suggests that the architecture subheading "is to talk about clustering/HA" and "the rest is not relevant".
I'm assuming the non-relevant parts were not technical enough and smelled too much like marketing (a fair criticism), for example: "Sensu is a primarily agent-based monitoring solution (agentless applications are also supported)"?? I've rewritten this section to just list the components and their technical role/function. I hope this works, but I'll be happy to strip away everything that's not just about clustering/HA, as needed. Like I explained above, I'm not trying to work around your recommendations here, I just didn't understand this one bit of feedback.
I also reworked the summary section in a similar style as the InfluxDB section to (hopefully) highlight the few similarities between Sensu and Prometheus, as well as the use cases (which are quite different IMO). I think this is a better framework for the summary, but let me know if you want me to change it.
Cheers 🍻 #monitoringlove

@SuperQ @brian-brazil I don't want to presumptively press the "resolve conversation" buttons on your suggestions, but I believe all of them have been addressed and are ready for a fresh round of feedback.

@SuperQ @brian-brazil I don't want to presumptively press the "resolve conversation" buttons on your suggestions, but I believe all of them have been addressed and are ready for a fresh round of feedback.

@brian-brazil thanks again for the feedback. I have completed another round of changes in between my morning of meetings. I think 🤞  I have made all of your recommended changes, less one. I updated the description of Sensu's federation feature as it is part of our clustering/HA story (it's literally a technique to cluster Sensu clusters), but if you still don't think it fits I'll go ahead and remove it.
Let me know if I missed anything else.
Cheers 🍻

@brian-brazil thanks again for the feedback. I have completed another round of changes in between my morning of meetings. I think 🤞  I have made all of your recommended changes, less one. I updated the description of Sensu's federation feature as it is part of our clustering/HA story (it's literally a technique to cluster Sensu clusters), but if you still don't think it fits I'll go ahead and remove it.
Let me know if I missed anything else.
Cheers 🍻

Thanks again, @brian-brazil. Sorry for the slow follow-up here. You were being very responsive last week, but then I got derailed by the political news last week...
Cheers 🍻

Thanks again, @brian-brazil. Sorry for the slow follow-up here. You were being very responsive last week, but then I got derailed by the political news last week...
Cheers 🍻

Thanks!

You were being very responsive last week, but then I got derailed by the political news...

I think we're all still a bit off-kilter from that even on this side of the ocean, no need to apologise.

Thanks!

You were being very responsive last week, but then I got derailed by the political news...

I think we're all still a bit off-kilter from that even on this side of the ocean, no need to apologise.

🎉

🎉


Why you use wasm here?

Hey
I noticed lots of info about Sealevel but here you use wasm, why?

@askucher solana is written in Rust and so wasm allows us to compile our rust code and run it in the browser


Installer fails to download binaries due to broken links

The url to wix-binaries.zip periodically changes due to new releases of WiX. This currently breaks the installer build. I've contacted Rob Mensching (project lead) and asked about stable urls. If that cannot happen, we'll need to figure out some way to get the latest url.

I had a look around, and while WiX now seems to be on Github (https://github.com/wixtoolset/wix3) they don't provide binaries there.
They do provide binaries on their homepage, and exposed in this feed:
http://wixtoolset.org/releases/feed/v3.10
http://wixtoolset.org/downloads/v<IP_ADDRESS>07/wix310.exe
This doesn't seem to be packaged the same as the zip archive provided on codeplex though

Yes, Microsoft is closing down CodePlex, so everything is moving to Github. This is probably a work in progress, so let's wait a short while and see if they get their CI working with Github as well.

This was fixed by #84! :cake:


Framework tree closed on SkiaGold diff

See: https://ci.chromium.org/ui/p/flutter/builders/prod/Windows framework_tests_libraries/9200/overview
https://flutter-gold.skia.org/detail?test=material.flexible_space_bar_stretch_mode.blur_background&digest=682f7daddc094a52ba1d2ee688b6ee9e
The diffs are occurring on an engine roll that appears unrelated, and there were no diffs flagged in presubmit.

Looks like another case of https://bugs.chromium.org/p/skia/issues/detail?id=14048 I updated the issue for the Gold team
The tree is currently green

result-state.json: No result file found.
What happened to that file? (created from goldctl auth and init)

I am not sure, it may not be where we think it is. We check to make sure it exists though, and the contents are apparently empty:
https://github.com/flutter/flutter/blob/72f9cf54871a97a857d69873ffe6da0a884dd4b5/packages/flutter_goldens_client/lib/skia_client.dart#L221


Change the font of profile page to Poppins

Description
The font of website is Poppins but it is missing in the profile section on name and email which doesn't look so good. So, please assign this issue to me under GSSOC'23 to change its font.
Steps to reproduce
Go to profile page and see the name and email on it.
Screenshots

Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional information
No response

Yes please help maintain consistencies in fonts, it's a great UI fix. Also please check if other section also dont have the same issue


XCHammerd / Project watcher script

We currently generate projects during the build if needed. In addition, it'd be awesome to have a program that watches for changes in files, and updates projects for me.

It would be cool to leverage existing watcher tools for this rather than building another daemon if possible.
watchman is pretty popular and also there is ibazel which I think is unsupported from google but is designed to watch if the deps of a target change


Welcome messages

Add the following messages when channel is created. Send as system messages.

"Hi first name 👋, we are so glad you are here!"
"Ours is a better way to communicate online and we want to show a few ways how we do that."
"First is to a set a time each day that you are most ready to READ/RESPOND to messages. We call this a "ritual". Every message anyone sends you will be displayed in your feed during this time. You can always access any message, but the idea here is to help you not be distracted through out your day."
"You may have noticed there isn't a send button! 😱 That's intentional. Simply swipe up on your message in order to send it. If you need to move the cursor, simply hold down on the spacebar. This gesture is to help reduce the number of accidental sends by adding a touch of intentionality 🤗. "
"All messages are set to READ manually. This ensures that you know when a message is actually read, not just scrolled too 🧐. Simply tap a message, you want to set, or pull up on the last message in the conversation."
"Hit us up in Feeback if you have issues or suggestions. Enjoy! 🥳 "

Send all these messages together, right?

Send all these messages together, right?


Deno permissions flags required to use ddc after updating deno/installing for the first time

Problems summary
The latest version of deno (1.29.2) requires the following --allow flags for ddc.vim to work after updating deno or installing deno for the first time (I installed deno with mamba install deno):
let g:denops#server#deno_args = ['--allow-env', '--allow-net', '--allow-read', '--allow-write']

Perhaps this is specific to the deno version I installed. But if not, it might be a good idea to add some notice to the documentation / at the top of your readme. Or, you could even include these flags by default when ddc starts the server?
Expected
The ddc plugin works like normal / without errors on startup.
Actual
The ddc plugin throws many many different errors without the above init.vim setting.
Environment Information

ddc.vim version (SHA1):

Shougo/ddc.vim@8905e6d52b4d2ffb5d446996561ca9df304db5e6

denops.vim version (SHA1):

vim-denops/denops.vim@8f3899de3d3add07105221262dca90a31c4c2d4c

deno version(deno -V output):

deno 1.29.2 (release, x86_64-apple-darwin)
v8 <IP_ADDRESS>
typescript 4.9.4

OS (sw_vers output):

ProductName:		macOS
ProductVersion:		13.2.1
BuildVersion:		22D68

neovim/Vim :version output:

VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Oct 28 2022 21:23:20)
macOS version - x86_64
Included patches: 1-814
Compiled by<EMAIL_ADDRESS>

Huge version without GUI.
" Your minimal init.vim/vimrc
set runtimepath+=~/path/to/ddc.vim/
call ddc#enable()
" Uncomment to fix the errors:
" let g:denops#server#deno_args = ['--allow-env', '--allow-net', '--allow-read', '--allow-write']

How to reproduce the problem from neovim/Vim startup (Required!)
Simply start vim with ddc enabled and the versions listed above.
Upload the log messages by :redir and :message (if errored)

Without the flags, after installing / updating deno, deno emits many many error messages indicating that the above flags are required.
With the flags, when starting vim for the first time, deno emits messages indicating that different components are being downloaded / installed.
After this step, when starting vim again, the above g:denops#server#deno_args setting is no longer required for ddc to work like normal.

I can no longer get the specific error messages, but hopefully you can still reproduce. Thanks for the great package.

The latest version of deno (1.29.2) requires the following --allow flags for ddc.vim to work after updating deno or installing deno for the first time (I installed deno with mamba install deno):

Please use the latest version of deno.  Because 1.29.2 is not the latest.
% deno upgrade
Looking up latest version
Local deno version 1.32.1 is the most recent release


Field not found in a Match table

So I was pushing a local updated schema and unfortunately failed to give this information
? Are you sure you want to continue? Yes
🛑 user2ID is not a field in Match
This is the code and the error I got

and here I the scheme I created was amplify

any help please?

Hey @gmako6 👋, Please try changing the field name from ["user2ID"] to ["User2ID"] in graphql schema (line number 10).

Wow ....work misspelling. Thank you, everyone


Get zipcode, Country params

Hi, Thanks for support this library.
I have a question regarding get data to parse zipcode and country.
Are there any ref or doc to get/parse zipcode, country strings?
Thanks.

I have the same question, but I need to get Country, State, City and zip code. Can I do that?

I need this also

yes i also need to get just state

I need this to

I need this too

Check out the available options in Place autocomplete
[https://developers.google.com/places/web-service/autocomplete#place_types]here
geocode instructs the Place Autocomplete service to return only geocoding results, rather than business results. Generally, you use this request to disambiguate results where the location specified may be indeterminate.
address instructs the Place Autocomplete service to return only geocoding results with a precise address. Generally, you use this request when you know the user will be looking for a fully specified address.
establishment instructs the Place Autocomplete service to return only business results.
the (regions) type collection instructs the Places service to return any result matching the following types:
    locality
    sublocality
    postal_code
    country
    administrative_area_level_1
    administrative_area_level_2
the (cities) type collection instructs the Places service to return results that match locality or administrative_area_level_3.

Hi there, I also need to include the zip code in the address on both places, in the list, and in the textinput when one item is selected. I do get the complete addres, including zip code from  details.formatted_address on onPress. But the row parameter in renderDescription does not include formatted_address, and row.description does not show zip code. Is it possible to tell renderDescription to show formatted_address? Thanks!

how to get the zip code ? Any update ?

Here is solution.
Don't forget to add fetchDetails prop on your <GooglePlacesAutocomplete/> component. Then in onPress will be provided details where you can find address_components and postal_code will be here.
Address components:
[
  {
    "long_name": "4511",
    "short_name": "4511",
    "types": [
      "street_number"
    ]
  },
  {
    "long_name": "GlencoeAvenue",
    "short_name": "GlencoeAve",
    "types": [
      "route"
    ]
  },
  {
    "long_name": "MarinadelRey",
    "short_name": "MarinaDelRey",
    "types": [
      "locality",
      "political"
    ]
  },
  {
    "long_name": "LosAngelesCounty",
    "short_name": "LosAngelesCounty",
    "types": [
      "administrative_area_level_2",
      "political"
    ]
  },
  {
    "long_name": "California",
    "short_name": "CA",
    "types": [
      "administrative_area_level_1",
      "political"
    ]
  },
  {
    "long_name": "UnitedStates",
    "short_name": "US",
    "types": [
      "country",
      "political"
    ]
  },
  {
    "long_name": "90292",
    "short_name": "90292",
    "types": [
      "postal_code"
    ]

My example:
<GooglePlacesAutocomplete fetchDetails onPress={(data, details = null) => {
        // 'details' is provided when fetchDetails = true

        const { address_components } = details;
        if (address_components.length === 0) {
          return;
        }
      ...
      }}
...

To solve this problem, I used the following solution:

@bell-steven you are closing the issue without providing any solution

you are closing the issue without providing any solution
I beg to differ. There are multiple solutions posted here.

It's really hard to track issues and solutions
Not really sure what you mean here.

you are closing the issue without providing any solution

I beg to differ. There are multiple solutions posted here.

It's really hard to track issues and solutions

Not really sure what you mean here.

Since the details address_components array can be different lengths depending on the address input, this is a more reliable way to get zip code
<GooglePlacesAutocomplete
  fetchDetails={true}
  onPress={(data, details) => {
    const zipCode = details?.address_components.find((addressComponent) =>
      addressComponent.types.includes('postal_code'),
    )?.short_name;
  }}
  query={{
    key: 'YOUR_GOOGLE_KEY_HERE',
    language: 'en',
    types: 'address',
  }}
/>;

Since the details address_components array can be different lengths depending on the address input, this is a more reliable way to get zip code
<GooglePlacesAutocomplete
  fetchDetails={true}
  onPress={(data, details) => {
    const zipCode = details?.address_components.find((addressComponent) =>
      addressComponent.types.includes('postal_code'),
    )?.short_name;
  }}
  query={{
    key: 'YOUR_GOOGLE_KEY_HERE',
    language: 'en',
    types: 'address',
  }}
/>;

Since the details address_components array can be different lengths depending on the address input, this is a more reliable way to get zip code
<GooglePlacesAutocomplete
  fetchDetails={true}
  onPress={(data, details) => {
    const zipCode = details?.address_components.find((addressComponent) =>
      addressComponent.types.includes('postal_code'),
    )?.short_name;
  }}
  query={{
    key: 'YOUR_GOOGLE_KEY_HERE',
    language: 'en',
    types: 'address',
  }}
/>;

This works! Thank you!

Since the details address_components array can be different lengths depending on the address input, this is a more reliable way to get zip code
<GooglePlacesAutocomplete
  fetchDetails={true}
  onPress={(data, details) => {
    const zipCode = details?.address_components.find((addressComponent) =>
      addressComponent.types.includes('postal_code'),
    )?.short_name;
  }}
  query={{
    key: 'YOUR_GOOGLE_KEY_HERE',
    language: 'en',
    types: 'address',
  }}
/>;

This works! Thank you!

Check this - https://github.com/FaridSafi/react-native-google-places-autocomplete/issues/835#issuecomment-1438041017


Update terra.go to use the proper terra 2 endpoint

Current endpoint refers to Terra Classic
Also changed from fcd to LCD (current fcd endpoints is just proxied to LCD anyway)

Thanks for the contribution @etienne-napoleone !!


[SPARK-16660][SQL] CreateViewCommand should not take CatalogTable

What changes were proposed in this pull request?
CreateViewCommand only needs some information of a CatalogTable, but not all of them. We have some tricks(e.g. we need to check the table type is VIEW, we need to make CatalogColumn.dataType nullable) to allow it to take a CatalogTable.
This PR cleans it up and only pass in necessary information to CreateViewCommand.
How was this patch tested?
existing tests.

cc @yhuai @liancheng

Test build #62661 has started for PR 14297 at commit 26312b9.

Test build #62661 has finished for PR 14297 at commit 26312b9.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62661/
Test FAILed.

Merged build finished. Test FAILed.

Test build #62663 has started for PR 14297 at commit 7e516ff.

Test build #62663 has finished for PR 14297 at commit 7e516ff.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62663/
Test FAILed.

Test build #62671 has started for PR 14297 at commit 3e22096.

Test build #62671 has finished for PR 14297 at commit 3e22096.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62671/
Test PASSed.

Merged build finished. Test PASSed.

Test build #62701 has started for PR 14297 at commit 5072959.

Test build #62701 has finished for PR 14297 at commit 5072959.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62701/
Test PASSed.

Merged build finished. Test PASSed.

retest this please

Test build #62775 has started for PR 14297 at commit 5072959.

Test build #62775 has finished for PR 14297 at commit 5072959.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62775/
Test PASSed.

Merged build finished. Test PASSed.

Test build #62786 has started for PR 14297 at commit a5cf2b3.

Test build #62786 has finished for PR 14297 at commit a5cf2b3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62786/
Test PASSed.

LGTM except for one minor issue.

Test build #62818 has started for PR 14297 at commit 7b78e20.

Test build #62818 has finished for PR 14297 at commit 7b78e20.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62818/
Test PASSed.

Merging to master, thanks!


[API] Update C-API @open sesame 06/08 13:02

Update C-API and corresponding code changes
Major Changes:

ml_nnmodel_compile_with_conf() replaced with ml_nnmodel_construct_with_conf().
This new function loads the model from the config file but does not initialize.
ml_nnmodel_compile() should be called after ml_nnmodel_construct_with_conf() before training.

ml_nnmodel_compile() does not take optimizer as an input.
Rather, use ml_nnmodel_set_optimizer() to set the optimizer for the model.

init() from neuralnet has been updated to loadFromConfig() and does not initialize the model anymore.
Rather call init() after loadFromConfig() to initialize.
This also allows updating the model config after loading model with loadFromConfig().

init(optimizer, args_list) has been replaced with init()
Rather call setOptimizer(optimizer) to set the optimizer and
setProperty(args_list) to set the properties before calling init().

Bug fixes in checkValidation()

Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #273. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/273-202007071822240.40795588493347-f8aa7fce4fcee3aa1037a8cda3d26d3f9faa100e/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/273-202007081302010.38129806518555-f8aa7fce4fcee3aa1037a8cda3d26d3f9faa100e/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/273-202007081353450.56621503829956-25254f6451cb712314aeee492610a5a0ede06a28/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

FYI) #277 need merge to pass CI clang checker

V2:
Restrict the properties which can be set for the network after the compilation of the model has been done

code (line 631~640) is repeated. how about making some func or macro?
        TensorDim def_init_dim;
        if (def_init_dim == layers[i]->getInputDimension()) {
          layers[i]->setInputDimension(previous_dim);
        } else if (previous_dim != layers[i]->getInputDimension()) {
          status = ML_ERROR_INVALID_PARAMETER;
          ml_loge("Dimension mismatch between layers.");
          NN_RETURN_STATUS();
        }
      }

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

code (line 631~640) is repeated. how about making some func or macro?

Done.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.


Create an ARMCC base file for cross-compilation

ARMCC example
$ cat armcc.txt
# This file assumes that path to the arm compiler toolchain is added
# to the environment(PATH) variable, so that Meson can find
# the armcc, armlink and armar while building.
[binaries]
c = 'armcc'
cpp = 'armcc'
ar = 'armar'
strip = 'armar'

[properties]
# The '--cpu' option with the appropriate target type should be mentioned
# to cross compile c/c++ code with armcc,.
c_args      = ['--cpu=Cortex-M0plus']
cpp_args    = ['--cpu=Cortex-M0plus']

[host_machine]
system = 'bare metal'      # Update with your system name - bare metal/OS.
cpu_family = 'arm'
cpu = 'Cortex-M0+'
endian = 'little

Completed in monorepo


compiler: switch to token replacement instead of format strings

This allows the use of regular { and } tokens in the C file instead of the escaping required for every scope and control flow structure. It should be a QOL improvement while developing the C file, compared to the cost of a few string allocations while compiling to C ?
Also a couple of drive-by changes:

removes some, I believe unused, cranelift crates: hvm will be faster to build
some automated rustfmt, and println simplifications

(I haven't fully tested this, only on one example, which seemed to work. Hopefully CI will soon be able to test this PR)

(I haven't fully tested this, only on one example, which seemed to work. Hopefully CI will soon be able to test this PR)

Ah, unfortunately the CI doesn't yet run automated tests, sorry. It should be added when #31 gets merged though. We also don't have extensive unit tests yet, so I'm not sure if it'll be able to catch a lot of errors either when it does. I think I might try integrating some property testing with the proptest crate to improve this.

I was indeed thinking of your PR being able to test this PR soon. Even basic smoke tests will be able to catch an intended change here.

Conflicts on runtime.c are super likely since it's an heavily modified file. If that happens, I'll rebase when/if people find this technique interesting.

Since we are still loading the template on compile time, I think this is better. Let's see what Maia thinks.
I just wish there was a function that would do all the replacements concurrently.

Or you could search the template and split it per token "hole", write each static section directly to the output file without doing interpolation and the String allocation & concatenation. In any case, this is easy to improve when/if you see that generating the C file becomes the bottleneck of the compiler, which seems unlikely to be the case today ?

This looks good. I won't be updating the code a lot tomorrow, so that's a good window to merge

Rebased.
I've left the tokens independent, so that you can change them individually. It will be easy to make the template a valid C file to ease development by turning into valid commented expressions to replace.

@lqd Ideally, you should run crate2nix generate if you're able to install crate2nix (or if you have Nix, you can access it from the dev shell) since your PR changes Cargo.lock. But don't worry though, I've included the required changes in my CI PR instead so you don't have to do that.

@nothingnesses thank you for doing that, I don't use nix.

I guess to make
#define MAX_WORKERS (/* GENERATED_NUM_THREADS_CONTENT */)

we could do something like
/* GENERATED_NUM_THREADS_CONTENT */
#ifndef MAX_WORKERS
#define MAX_WORKERS (1)
#endif

/* GENERATED_NUM_THREADS_CONTENT */ <- #define MAX_WORKERS ({num_threads})
etc
?

Sure, or variations of int value = /* START */ 0 /* END */; expressions where it is important, and replace both tokens and the content they box.


Add CausalPy logo and restructure docs contents

Removes the img folder from the root of the repo. Also slightly restructures the docs folder so that now, image resources are in docs/source/_static. This closes #183
Adds the CausalPy logo to the README and the docs homepage. This advances #27

It seems like the GitHub servers are a bit glitchy today. Similar thing happening on a PR for PyMC-Marketing. Am attempting to re-run failed tests.


MYNEWT-543 Keep settings not set in syscfg variable

The current newt target set target-name syscfg variable saves the settings in a new target syscfg.yml file. Settings from the current target syscfg.yml that are not specified in the syscfg  variable are deleted. While setting a variable with only the values specified in the command is consistent with how other variables are set, the syscfg variable is a bit different because of multiple configuration settings.  A user might want to only override some settings but keep the values for the other settings in the target syscfg.yml.
This commit adds support to keep the values of the settings that are not specified in the set syscfg variable and to add or override the values in the target syscfg.yml for the settings specified for the variable. The code change converts the setting/value pair from the current syscfg.yml in to a KV String, and appends the KV String from command to it before it processes and saves the setting values. This way, an old setting value is either saved, or overridden if it is specified in the  syscfg variable.
A user who only wants to create a new target syscfg.yml with the settings specified in the syscfg variable can set  syscfg="" before it sets syscfg with the setting names and values. Example:
newt target set target_name syscfg="" syscfg=settingname1=settingvalue1:settingname2=settingvalue2 ...

Chris, Aditi and I discussed this further and have decided to keep setting the syscfg variable behavior consistent with the other variables: setting a variable overwrites the current variable values.  We are looking into a feature enhancement, post release 1.0, that will support "appending" variable values.
Closing this PR without code change.  The  newt target set documentation will be updated to let user know that the command will overwrite the current variable settings.


how to run the code?

i run python main.py (in before_finetuned/magnetization1_4mT) , but i got this error:
Total steps 200000
Total learning steps per simulation 2000
Traceback (most recent call last):
File "/home/tianyu/code/msr/RL-for-MSRs/Code and Models/before_finetuned/magnetization1_4mT/main.py", line 47, in
observation = env.reset()
File "/home/tianyu/code/msr/RL-for-MSRs/Code and Models/before_finetuned/magnetization1_4mT/set_environment.py", line 132, in reset
self.shearable_rod = CosseratRod.straight_rod(
File "/home/tianyu/anaconda3/envs/msr/lib/python3.9/site-packages/elastica/rod/cosserat_rod.py", line 297, in straight_rod
raise ValueError(
ValueError: The option to set damping coefficient (nu) for the rod during rod
initialisation is now deprecated. Instead, for adding damping to rods,
please derive your simulation class from the add-on Damping mixin class.
For reference see the class elastica.dissipation.AnalyticalLinearDamper(),
and for usage check examples/axial_stretching.py

But i can run axial_strectching.py successfully:

Hi SHITIANYU-hue, thank you for your question. It seems that you have installed a newer version of PyElastica, which may not be compatible with the initialization of straight_rod in my code. Sorry for the trouble but maybe you should try older version of PyElastica. If I remember it correctly, you may need to install v0.1.0.post2 release.

Hello, Thanks for your help, yes, it works now, by the way, it has another issue with the device, it should have a device here:

Hello, Thanks for your help, yes, it works now, by the way, it has another issue with the device, it should have a device here:

Thanks. I will get it fixed soon.