🐛 Bug Report: Cloudbuild doesn't work

📜 Description
Hi team, I've been trying to configure the Cloudbuild plugin, but it seems to be quite outdated, as the full integration is not working as it should.
In the component-info.yaml, it doesn't seem to recognize the annotation google.com/cloudbuild-project-slug, and when I start Backstage, the message 'No CI/CD available for this entity' appears.
Following the Roadie documentation (https://roadie.io/backstage/plugins/google-cloud-build/), the error seems to be in the configuration of EntityPage.tsx.
👍 Expected behavior
Cloudbuild should work properly
👎 Actual Behavior with Screenshots
Doesn't recognize de google.com/cloudbuild-project-slug.

👟 Reproduction steps
Just follow the Roadie documentation https://roadie.io/backstage/plugins/google-cloud-build/
📃 Provide the context for the Bug.

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, I don't have time to work on this right now

yeah it looks like the docs are a bit outdated. You should change your EntityPage.tsx as following:
+ import {
+   EntityCloudbuildContent,
+   isCloudbuildAvailable,
+ } from '@backstage/plugin-cloudbuild';

  export const cicdContent = (
    <EntitySwitch>
      <EntitySwitch.Case if={isJenkinsAvailable}>
        <EntityJenkinsContent />
      </EntitySwitch.Case>

+.    <EntitySwitch.Case if={isCloudbuildAvailable}>
+       <EntityCloudbuildContent />
+     </EntitySwitch.Case>

We should update the instructions here

It's an intering nuance too, that this plugin is in the Backstage monorepo and so it's install documentation really should be here?
https://github.com/backstage/backstage/tree/master/plugins/cloudbuild
Indeed Roadie does sometime have their own documentation, and I wonder if that switch example (which is cool btw :) ) is the way their default Roadie service handles multiple CI/CD vs. how the Backstage sample code in open source does?
Anyway, if you visit backstage.io, then click plugins, you see the Google Cloud Build plugin, and if you explore it, it takes you here to install it:
https://github.com/backstage/backstage/tree/master/plugins/cloudbuild
Which is essentially blank.  So I'd recommend from an open source perspective that page likely needs an update, too!

Add the following to EntityPage.tsx:
/packages/app/src/components/catalog/EntityPage.tsx
import { EntityCloudbuildContent, isCloudbuildAvailable } from '@backstage/plugin-cloudbuild';
Then in your cicdContent const, add the following switch case:
    <EntitySwitch.Case if={isCloudbuildAvailable}>
      <EntityCloudbuildContent />
    </EntitySwitch.Case>

E.G.
const cicdContent = (
  // This is an example of how you can implement your company's logic in entity page.
  // You can for example enforce that all components of type 'service' should use GitHubActions
  <EntitySwitch>
    <EntitySwitch.Case if={isCloudbuildAvailable}>
      <EntityCloudbuildContent />
    </EntitySwitch.Case>

    <EntitySwitch.Case if={isGithubActionsAvailable}>
      <EntityGithubActionsContent />
    </EntitySwitch.Case>

Thank you this bug/comment thread helped me.

Hi @cl-christschantz would you like to help us update the documentation? This will be greatly appreciated 🙂

Hi @cl-christschantz would you like to help us update the documentation? This will be greatly appreciated 🙂

Sure, Ill get a PR submitted.

Hi @cl-christschantz would you like to help us update the documentation? This will be greatly appreciated 🙂

Sure, Ill get a PR submitted.

Thank you so much in advance, issue assigned to you 🙌🏻

@camilaibs PR is up. #20812

Sadly, while the docs in this issue helped me get the plugin installed, I don't see any cloud build data :(   Looking at this https://github.com/backstage/backstage/blob/master/plugins/cloudbuild/src/api/CloudbuildClient.ts#L33 makes me think that this plugin supports the v1 API only, and I'm wondering if since my cloud build repo was set up using 2nd Gen if this plugin is unable to see my builds..

Sadly, while the docs in this issue helped me get the plugin installed, I don't see any cloud build data :( Looking at this https://github.com/backstage/backstage/blob/master/plugins/cloudbuild/src/api/CloudbuildClient.ts#L33 makes me think that this plugin supports the v1 API only, and I'm wondering if since my cloud build repo was set up using 2nd Gen if this plugin is unable to see my builds..

Not sure if that is the case or not. I wouldn't think it would matter since the build runs are independent from the repo. Also, there is no "projects.builds.list" Method that I can find on the v2 api.
You could try the list method manually using this page:
https://cloud.google.com/build/docs/api/reference/rest/v1/projects.builds/list
If you get results, then what you stated likely is not the case.
I assume you are properly specifying the correct project slug in your component-info.yaml file?
google.com/cloudbuild-project-slug: your-project-name

I can run it, and get a 200, and the return is an empty map {}   and  google.com/cloudbuild-project-slug: your-project-name.  Is set to set to  my GCP project name/ID (which are the same) when I view the GCP project overview.  It's the same string I used for the projectId key when I set up my k8s integration, which is working correctly. (And Cloudbuild  is currently in that same project)
Thanks for the  replies, they are really helpful! I appreciate it!

I can run it, and get a 200, and the return is an empty map {} and google.com/cloudbuild-project-slug: your-project-name. Is set to set to my GCP project name/ID (which are the same) when I view the GCP project overview. It's the same string I used for the projectId key when I set up my k8s integration, which is working correctly. (And Cloudbuild is currently in that same project)
Thanks for the replies, they are really helpful! I appreciate it!

Sounds like you may not be able to use 2nd gen repo's in cloud build and use this plugin.
Ill try to do some testing after I setup a 2nd gen repo and run a build from that repo.

I'm facing the same issue as @tfhartmann even though I'm using a 1st gen repo. Could it be possible that it only works for global scope? Is there a way to specify region?
I tried the calling the list method manually with:
> gcloud builds list
Listed 0 items.

However, when I specify the region, it works as expected:
> gcloud builds list --region us-central1
ID   CREATE_TIME                DURATION  SOURCE  IMAGES  STATUS
id1  2023-11-21T20:01:24+00:00  6M25S     -       -       SUCCESS
id2  2023-11-21T17:26:10+00:00  5M50S     -       -       SUCCESS

tfhartmann

Yes, currently its only going to return builds in the global scope.
@tfhartmann are your builds also in a specific region vs global?

@vedantthapa
Can you try the following projects.locations.builds.list method:
https://cloud.google.com/build/docs/api/reference/rest/v1/projects.locations.builds/list?
In the parent parameter, use the following: projects/your-project/locations/us-central1. Replace your-project with your actual project name (the one you would use in your project-slug annotation.

@PurseChicken Yes, that works and returns the relevant results!

@PurseChicken Yes, that works and returns the relevant results!

Awesome thanks! Could you please open a new issue and tag me? I have an open PR for some changes already to the plugin and I'll submit another based on your issue.
Thanks again!

region

Sorry for the late reply, but yes I can confirm my builds are in a specific region, and not in a global scope!

region

Sorry for the late reply, but yes I can confirm my builds are in a specific region, and not in a global scope!

Perfect. I have a PR up which will allow you to specify a region in you component-info manifest which will pull the relevant results for your backstage entity. @vedantthapa has already tested this as well.

region

Sorry for the late reply, but yes I can confirm my builds are in a specific region, and not in a global scope!

@tfhartmann. I have a PR up which will allow you to specify a region in you component-info manifest which will pull the relevant results for your backstage entity. @vedantthapa has already tested this as well.

As a follow up, I've never been able to get this working... no idea why. Works from the CLI, with gcloud --project my-project builds list --region us-east4
I totally get results from https://cloud.google.com/build/docs/api/reference/rest/v1/projects.locations.builds/list using the parent...   but when I try to get this from  backstage
    google.com/cloudbuild-project-slug: my-project
    google.com/cloudbuild-repo-name: repo-name (tried both org/reponame and just reponame)
    google.com/cloudbuild-location: us-east4

no idea why.... I checked my oauth scopes, but don't see anything missing from them... 🤷  kind of at a loss...

@tfhartmann Are you sure that the plugin is the updated version in your backstage instance?

@tfhartmann Are you sure that the plugin is the updated version in your backstage instance?

I show this when running, yarn list --pattern plugin-cloudbuild so I believe I'm at the most recent...
yarn list v1.22.19
└─<EMAIL_ADDRESS>✨  Done in 0.66s.

I do get the Google Login prompt, the CI/CD tab "things about it" then returns
"No records to display"
I do see a url in my logs  from /api/auth/google/handler/frame  which leads me to this url https://www.googleapis.com/auth/userinfo.email
That returns this message...
You are receiving this error either because your input OAuth2 scope name is invalid or it refers to a newer scope that is outside the domain of this legacy API. which made me think is was a scope in my Oauth setup on GCP, but I couldn't find any scope that changed the behavior.

This API was built at a time when the scope name format was not yet standardized. This is no longer the case and all valid scope names (both old and new) are catalogued at https://developers.google.com/identity/protocols/oauth2/scopes.

I think it's something I've misconfigured or missed...

You only need to specify repo-name if its different than the repo your component-info is in. Have you tried an annotation like the following:
 google.com/cloudbuild-project-slug: my-project   google.com/cloudbuild-location: us-east4

You only need to specify repo-name if its different than the repo your component-info is in. Have you tried an annotation like the following:
If your builds happen to be associated with a different repo-name, make sure repo-name matches what you get in your results when using gcloud --project my-project builds list --region us-east4

Ok... wild... so when I run builds list  the SOURCE field is always returned as a dash -  So I'm not seeing a repo name in that output, although when I go the the gcp console, I clearly see the SOURCE with the repo.  I do  see the correct repos when running
gcloud --project my-project builds repositories list --connection github --region us-east4

That is very strange. Have you tried using the trigger filter instead? I wonder if the plugin is not matching on repo name (since as you stated it shows blank when using builds list) so that would explain why there are no results with the plugin.

That is very strange. Have you tried using the trigger filter instead? I wonder if the plugin is not matching on repo name (since as you stated it shows blank when using builds list) so that would explain why there are no results with the plugin.

Sadly using trigger filter returns no results in backstage either. 😢


rc4 The bootnode you want to connect to at /ip4/<IP_ADDRESS>/tcp/30333 provided a different peer ID than the one you expect: `12D3KooWSVSi7jXwGcfBBB5Uq9Pj2UakNakiqVwrS1TPdUzReLE

while using the newest rc4 template following the start a private network tutorial , on start up it give's me the following error
The bootnode you want to connect to at `/ip4/<IP_ADDRESS>/tcp/30333` provided a different peer ID than the one you expect: `12D3KooWSVSi7jXwGcfBBB5Uq9Pj2UakNakiqVwrS1TPdUzReLE

while im using the correct peer id

This means the node has a different peer id. Please take a look into the log to find the correct peer id.

https://drive.google.com/drive/folders/1NvPMQisQBB5K_P0Z-CnAk5aHzTsDRRwC?usp=sharing

Why does it want to connect to all these ips? Did you changed the chain spec and added them?

No, only cloned the git repository

It tries to connect via <IP_ADDRESS>. Not sure.
Which repo did you clone?

 git clone -b v2.0.0-rc4 --depth 1 https://github.com/substrate-developer-hub/substrate-node-template

Works for me without problems. You also don't need to specify a bootnode, as MDNS should find your other node

sorry

Did you find your problem?

Im cloning the repo again to see if it works, actually my real problem is in here
https://github.com/noahsalvadordenjo/dev
produces blocks in dev mode but not in production

It works


Why calculate IoU from voxel label？

Hi.
I a new to point cloud segmentation. There are problems that have been bothering me a lot.
1). Why does PolarNet (here) calculate IoU from voxel-wise label instead of point-wise label? Even PolarNet directly saves the voxel label to the file for submission (here).
2.) As I learned from semantic-kitti-api, predictions about each point of the scan are required when submitted to the benchmark. Is my understanding correct? Or is it not necessary to predict the label of every point?
Thank you for answering me. It really bothers me very much.

1). Why does PolarNet (here) calculate IoU from voxel-wise label instead of point-wise label? Even PolarNet directly saves the voxel label to the file for submission (here).

In the validation and testing, we will project the voxel-wise label to the point-wise label (here). predict_labels is the predicted voxel-wise label, val_grid is the voxel location of each point. And there are two reasons why we use the voxel-wise label in the training: 1. it will be faster to train. 2. our experiment showed the result won't be improved if we use the point-wise label.

2.) As I learned from semantic-kitti-api, predictions about each point of the scan are required when submitted to the benchmark. Is my understanding correct? Or is it not necessary to predict the label of every point?

Yes. The submission file needs to be the label of every point. And the label needs to be in the original dataset format(here)

Thank you for your kind reply.
I mistakenly thought that it was mapping val_pt_labs to voxel. I feel much clearer.


sorting doesn't work with DT_RowIndex , it searches for a column named DT_RowIndex when sorting button is pressed.

Sorting of the column with DT_RowIndex values. screenshot of error is attached.
columns: [
		      { data: 'id', name: 'id'},
		      { data: 'DT_RowIndex', name: 'DT_RowIndex', "orderable":true, "ordeing":true, "searchable":true, "className" : "my_class"},
		     {
    	                "className":'details-control',
    	                "orderable":false,
    	                "ordeing":false,
    	                "searchable":false,
    	                "data":null,
    	                "defaultContent":''
    	            },

System details

PHP Version 7.2
Laravel Version 5.7

DT_RowIndex is a computed column, thus searching and sorting are expected not to work when using it. Unless the value was fetch from the database too.


Correct assignement for logits in classifier example

I tried to address https://github.com/huggingface/pytorch-pretrained-BERT/issues/76
should be correct, but there's likely a more efficient way.

Ok thanks, that should work for now. I simplified the output of the classes indeed (only send back loss when a label is provided) so this example broke.


Addition of "tree_map(np.asarray, value)" to "_convert_inps" function in "JAXAgent"

Hello,
I've identified a potential issue in the _convert_inps method of the JAXAgent class. When len(devices) == 1, it appears necessary to add value = tree_map(np.asarray, value). This addition could prevent exception errors when using custom programs that are compatible with the gym framework.
Here's the recommended modification:
def _convert_inps(self, value, devices):
  if len(devices) == 1:
    value = tree_map(np.asarray, value)  # Addition for gym compatibility
    value = jax.device_put(value, devices[0])
  else:
    check = tree_map(lambda x: len(x) % len(devices) == 0, value)
    if not all(jax.tree_util.tree_leaves(check)):
      shapes = tree_map(lambda x: x.shape, value)
      raise ValueError(
          f'Batch must by divisible by {len(devices)} devices: {shapes}')
    # TODO: Avoid the reshape?
    value = tree_map(
        lambda x: x.reshape((len(devices), -1) + x.shape[1:]), value)
    shards = []
    for i in range(len(devices)):
      shards.append(tree_map(lambda x: x[i], value))
    value = jax.device_put_sharded(shards, devices)
  return value

Thank you for considering this issue.
Best,

Hi, thanks for pointing that out. I would do that in an environment wrapper. The embodied framework defines the environment API to use Numpy types for everything.


Arbitrary 2d array data instead of TileMap?

Hello, I'm working on a 3d puzzle game involving blocks of different types. I'd like to setup a feature that generates a random puzzle based on predefined rules, naturally I found WFC. Most implementations though center around generating TileMap data and in looking at this project's docs it looks like you need a source and target tilemap.
Instead of building shims and translating tilemap data to data that I can use for my game logic, I'm wondering if I can simply pass in a 2d array of constraints (consisting of int values), along with target dimensions and it would solve that.
I saw that you have a sodoku solver, but my case is a bit simpler and I didn't see this specific example. Thanks!

Hi.
This addon does not require TileMap or any other specific node. Instead it uses mappers to interface between the algorithm and nodes. So if you do have some sort of map-like node in your game, you can implement a mapper for that node type.
If you don't have such nodes and really want to work with just arrays, then it gets more complicated, as WFC-specific part of the addon is built with assumption that there is some sort of map node. You'll have to

write a custom WFCProblem, perhaps, most of WFC2DProblem can be reused, except for map-related logic
create and use a problem and solver manually in your code, like it's done in the sudoku example


KOGITO-5135: [SceSim Designer] HiDPI is not working as expected

JIRA: KOGITO-5135: [SceSim Designer] HiDPI is not working as expected
VS Code plugin: plugin
--
It's the same fix introduced by https://github.com/kiegroup/kogito-editors-java/pull/12, but applied in the SceSim editor.
--
Before:

After:

@tiagobento Could you please double-check if the SceSim table appears with HiDPI on macOS? I believe QE do not have resources to check it.
(the artifact is attached in the description) :-)


Fix fill in the blank

Checklist:

[ ] I have read and followed the contribution guidelines.
[ ] I have read and followed the how to open a pull request guide.
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

You can reach out on the Discord server if you are having issues, but keeping opening and closing PRs is quite disrupting


Do not allow folders with same title under same parent

Description
Papermerge DMS should not allow creating duplicate folders i.e. two folders with same name under same parent.
From user experience point of view it is very confusing to see multiple folders with same name.

Info:
Backend version: 2.1.1
Frontend version: 2.1.0b12

Backend changes: https://github.com/papermerge/papermerge-core/pull/105
Frontend changes: https://github.com/papermerge/papermerge.js/pull/35


Allow custom keys in send() method

The send method expects text and prompt_settings keys, but only three keys are allowed in prompt settings (i.e. use_declarative_memory, use_episodic_memory and use_procedural_memory.
It could be useful to allow custom keys to be sent via WebSocket to share custom data in plugins.

You are right, I will fix it as soon as possible.


Remove system JS, fix issues with importing large files, and select the proper diagnostic during code navigation

This address issue #225, where the result-pane cannot scroll and as the user moves through the source code document the selection does not always cause the correct diagnostic to be selected. This was due to the fact that the "location ranges" in SARIF are largey "empty" (or a single point). So if you manage to put the cursor "just right" in VSCode then it would select. This has been addressed by seeing if the range is "empty" and "single line" and if it is, then just match on the line.
The issue with the result-pane not scrolling (and being empty some times) was due to code that was accidentally left in when trying to find a java-script module loader that would work in vscode's WebView. For note: RequireJS works fine, SystemJS, not so much :). I forget to remove some of the SystemJS code. That was PR #211
Also, for future referece, when you call spawn in node, it automatically quotes parameters. (Ugh). I thought that was an issue that was causing the multi-tool converter to fail, which I later found is not the cause, it is due to missing .Net dependencies (ugh).

Regarding module loading, what issues were you having (in Rusty's version) before you switched to RequireJS?

When adding more imports for typing in typescript, that causes the generated code to require a different module loader. The module loader required depends on how you configure tsconfig.explorer.json.
We can certainly revisit this for sure. All I'm after is making sure the web-view code maintains type-safety.

In reply to: 611812837 [](ancestors = 611812837)


Upgrade azure storage sdk to v10

[x] Upgrade sdk to azure-storage-blob v10, #434

[x] Update azure-storage-spring-boot-starter README

[x] Update storage spring boot starter sample

Hi @sophiaso, is there an ETA for azure storage sdk v10 update?

Hi @SuhanKoh, probably being released within two weeks.

Hi @SuhanKoh, starter with azure storage sdk v10 has been released, maven link


Extract apache2 role

Move apache2 role from datastore_setup role in datastore role
Move files directory to datastore_setup role
Genericise apache2 conf file variable in apache2 role
Specify apache2.conf file in datastore_setup files as datastore apache2 conf file
Update apache2 role include to common role from datastore role
Server rebuilt and changes tested and working

Also, I was re-reading articles on commit messages lately and would suggest we pay more attention to noting the 'why' in our commit messages, rather than just the what: https://chris.beams.io/posts/git-commit/#why-not-how (This is something I need to improve on too!)


Add a --width=COLUMN:VALUE option

Fix #366

Thinking more about this, I wonder if this wouldn't be better if handled through a configuration file. We have none at the moment, but the idea was raised in the past already, so maybe it'd be time to introduce this?

I like the idea or a config file for such things.

I like the idea of a config file for such things.

Ok; thank you. Let's move foward with #373 then.


Jobs stuck when trying to untar an archive

Since today, trying to untar a tar.xz archive on windows-latest seems not to be possible:

MWE1: tc.extractTar stuck
MWE2: tar -x -J --force-local -f failure
MWE3: tar -xf distrib stuck
MWE4: tar -xJf distrib stuck

/cc @ericsciple

@eine the image has been deployed. Could you check the behavior, please?

@miketimofeev I restarted an old job, and I also pushed some new. In all cases, runs are still stuck:

https://github.com/eine/setup-msys2/actions/runs/38608071
https://github.com/eine/setup-msys2/actions/runs/38609226

@eine thanks for the update, we will continue investigation

@eine I'm able to reproduce it. Could you give an example of a successful build with untar?

@eine I'm able to reproduce it. Could you give an example of a successful build with untar?

I'm not sure I understand what you mean. This commits shows what was used in setup-msys2 before something broke upstream, and how it was fixed using 7z instead: https://github.com/numworks/setup-msys2/commit/b3452aa847865e86d92d65d049cef96a52ab6418 Then, I tried all the examples above, none of which did work. Is using untar different from any of those?
Note that I am ok with using 7z. Furthermore, I hope #342 to be merged soon. Therefore, I don't have any actual build where I need to use tar or untar.

@eine sorry for confusing, I mean successful setup-msys2 with tar -xJf. But it looks like we've already found the root cause - default windows tar.exe(C:\windows\system32\tar.exe) is used instead of tar comes along with Git and that "Windows tar" can't extract from such xz archives. We're working on getting back Git tar.exe to PATH.

@miketimofeev, please, note that this is not the first chapter in the series of "conflicts between multiple installed versions of tar". I do think that the decission to make BSD's tar the default instead of Git for Windows' (MINGW's) was on purpose. See actions/toolkit#165. Precisely, the action (MWE1 above) is expected to handle diferences between versions of tar. Moreover, if/when MSYS2 is installed (see #30 and #342) the environment might change, as it would be sensible to replace Git for Windows' tar with MSYS2's.

@eine yeah, we're still working on the best way to deliver MSYS2, so it's just a question of time. I've made this PR to fix that particular issue until MSYS2 isn't delivered.
https://github.com/actions/virtual-environments/pull/415

@eine PR has been merged. I will let you know when new image is available

@eine, unfortunately, this git tar breaks more than fixes. We have to roll back the changes. Please use 7z or consider adding C:\Program Files\Git\usr\bin to the path before your run.

@miketimofeev, as said, I'm ok with using 7z. However, if tc.extractTar is broken, it should be removed or a warning should be added.

@ericsciple could you take care of tc.extractTar, please?

@eine

if tc.extractTar is broken

Can you clarify? The function finds tar in the PATH and calls it with the supplied flags (or default if not overridden).
For a .tar.xz file, it sounds like tar uses external tool xz to decompress (also must be in PATH?).
Adding git tar to the PATH for the hosted Windows runner won't fix for folks using self-hosted Windows runners.
If possible, may want to switch to a more common archive format on Windows (zip).
Other options might be:

If you need the version of tar bundled with git, then you could locate git using io.which, and then use relative path to effectively add C:\Program Files\Git\usr\bin to the PATH before calling extractTar.
Download or use a carry a different tool to expand the archive. It sounds like 7z will which. Could consider checking io.which to locate 7z, and downloading/caching if not found. Also could try 7zdec.exe which is very small. If it handles the file format then could carry that file with your action. It's what tool-cache uses for extract7z

@ericsciple, It seems to be fixed now. ´extractTar´ fails, as expected: https://github.com/eine/setup-msys2/runs/481303190?check_suite_focus=true


Set the dispatch queue explicitly

A signal dispatches listener calls synchronously on the posting thread by default.
Added the dispatchOnQueue method to specify the queue explicitly. Updated the readme file and implemented unit tests.

Just a few small comments, looks good otherwise. Thanks for the contribution!

Thanks. I updated the pull request accordingly.

Travis failed on one of the asynchronous waits. Might make sense to increase the wait time to 0.2 seconds for example.

Increased the wait time to 0.2s for both tests. Unit tests shouldn't fail occasionally this time.

Looks good. Thanks!


Cannot read property 'type' of undefined - Fresh Init on Existing MySQL

Bug description
A fresh prisma init on an existing MySQL Database gave me the following error:
  RelationalIntrospection Querying schemas. +0ms
? Please select the schema you want to introspect ambitionbox
  RelationalIntrospection Querying schemas. +1s

Introspecting database XXXX...  RelationalIntrospection Introspecting models in schema ambitionbox. +87ms
  RelationalIntrospection Querying tables. +0ms
  RelationalIntrospection Querying columns for schema ambitionbox. +2ms
  RelationalIntrospectionResult Datamodel inferrence started. +1s
  RelationalIntrospectionResult Basic types inferred. +9ms
  RelationalIntrospectionResult Id fields resolved. +1ms
  RelationalIntrospectionResult Default values inferred. +3ms
  RelationalIntrospectionResult Relations resolved. +2ms
  RelationalIntrospectionResult Relations enums resolved. +0ms
 !
TypeError: Cannot read property 'type' of undefined
    at _loop_3 (/Users/abhisheksoni/.config/yarn/global/node_modules/prisma-db-introspection/src/databases/relational/relationalIntrospectionResult.ts:360:28)
    at MysqlIntrospectionResult.RelationalIntrospectionResult.hideJoinTypes (/Users/abhisheksoni/.config/yarn/global/node_modules/prisma-db-introspection/dist/databases/relational/relationalIntrospectionResult.js:535:17)
    at MysqlIntrospectionResult.RelationalIntrospectionResult.infer (/Users/abhisheksoni/.config/yarn/global/node_modules/prisma-db-introspection/src/databases/relational/relationalIntrospectionResult.ts:523:18)
    at MysqlIntrospectionResult.RelationalIntrospectionResult.getDatamodel (/Users/abhisheksoni/.config/yarn/global/node_modules/prisma-db-introspection/src/databases/relational/relationalIntrospectionResult.ts:58:22)
    at MysqlIntrospectionResult.IntrospectionResult.getNormalizedDatamodel (/Users/abhisheksoni/.config/yarn/global/node_modules/prisma-db-introspection/src/common/introspectionResult.ts:23:24)
    at EndpointDialog.<anonymous> (/Users/abhisheksoni/.config/yarn/global/node_modules/prisma-cli-core/src/utils/EndpointDialog.ts:409:44)
    at step (/Users/abhisheksoni/.config/yarn/global/node_modules/prisma-cli-core/dist/utils/EndpointDialog.js:43:23)
    at Object.next (/Users/abhisheksoni/.config/yarn/global/node_modules/prisma-cli-core/dist/utils/EndpointDialog.js:24:53)
    at fulfilled (/Users/abhisheksoni/.config/yarn/global/node_modules/prisma-cli-core/dist/utils/EndpointDialog.js:15:58)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  util timed out +0ms
  output Exiting with code: 0 +0ms

Environment & setup

OS: Mac OS
Database: MySQL
Prisma version: v10.15.0
Node.js version: v10.15.0

The output indicates this is Prisma 1 - I moved your issue to the correct repository.

pretty much same issue here 1.5 months later
did you ever resolve this ?

Nope. Still the same.


Converting the flutter app to LIFF

There doesn't seem to be anything to be done in terms of development.
I have successfully converted my application to LIFF.
LIFF: https://liff.line.me/2005806035-vQq6OnZ1
App URL: https://flutter-bird.netlify.app
The LINE Messenger API allows us to receive URLs via LINE.


remove per layer realize in llama

previously needed due to kernel buffer count limit, seems fine to remove now

it found a variable scope bug!

I think I'm hitting the same one in mac benchmark, might be unrealized and just nondeterminism.

Yea, it's non deterministic. https://github.com/tinygrad/tinygrad/actions/runs/9148100711/attempts/1
@Qazalin we need that toposort fuzzer. I will also investigate where non-determinism is coming from.

this was changed to contiguous


feat: Added Vite vanilla application documentation

This PR includes documentation for the new Vite application examples PR26 in the coolify-examples repo.

Thank you for the PR!


Fixed typo

Resolved a typo on L147 (case-sensetive to case-sensitive)

@Natfan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks @Natfan.


step 6 dm feature

I had forgotten to remove one thing from the .js file for step 5, which was preventing the user from being able to post messages on other users' boards. I also made the changes shown in the guide for step 6, and the messages are set to be public. Thank you!

Please clarify the diff between user and recipient.

The user is the person who is logged in at the time, and the recipient is the person who the message is directed to.


[DOC] add readme to published package

Change in the documentation
We currently don't have a readme being published.
We can do follow these steps to do that: https://devblogs.microsoft.com/nuget/add-a-readme-to-your-nuget-package/#add-a-readme-to-your-package

@toddbaert and @beeme1mr it seems my PR didn't fix the issue. Could you please reopen this task?

I was reading this article and it seems we have some badges that are not in the Nuget whitelist: https://learn.microsoft.com/en-us/NuGet/nuget-org/package-readme-on-nuget-org#allowed-domains-for-images-and-badges
Since I am not the package owner, it is hard to understand what is going on under the hood. Could someone help me with this bit here?
@beeme1mr @toddbaert

Hey @askpt, here's what I discovered. First, the readme isn't live on NuGet yet because we haven't released an update. We were waiting for support for events before releasing an update. That feature was just added, so a release should happen soon.
I also spent some time looking into the markdown restrictions that NuGet has. Unfortunately, they don't support some of the HTML elements we use and they're rendered as plain text. Here's a GitHub issue that shows all the missing features. It also looks like https://bestpractices.coreinfrastructure.org/projects/6250/badge will be blocked but the NuGet team has a process to get a new domain added to their allow list.
I think the biggest issue is the lack of HTML support in NuGet. We may want to write a script that strips HTML. We already have x-hide-in-docs-start and e x-hide-in-docs-end tags that could be used to remove unwanted content.
What do you think @askpt? FYI @toddbaert

Sorry @beeme1mr got confused between the contrib and SDK packages. I thought there was a new version for the SDK with the PR that introduces the NuGet feature.
In relation to your point, might be useful looking into a new tag just to show/hide when published to the NuGet.
For the badges, you're right. Might be worth trying to have the other team to add the domains to the whitelist.

I'll submit a request to add the domain.

As suspected, the HTML is not rendered correctly. We need to revisit this issue to fix them: https://www.nuget.org/packages/OpenFeature

As suspected, the HTML is not rendered correctly. We need to revisit this issue to fix them: https://www.nuget.org/packages/OpenFeature

:weary:


The referenced paper may be wrong

In SPlisHSPlasH\Viscosity\Viscosity_Peer2016.h and SPlisHSPlasH\Elasticity\Elasticity_Peer2018.h, the author quoted the same paper:
[PGBT17] Andreas Peer, Christoph Gissler, Stefan Band, and Matthias Teschner. An implicit SPH formulation for incompressible linearly elastic solids. Computer Graphics Forum, 2017. URL: http://dx.doi.org/10.1111/cgf.13317
It is obviously wrong for the viscosity method, because it is about the elasticity. Moreover, the name of the file should be "Elasticity_Peer2017" rather than 2018 according to your naming convention.

Thanks for pointing this out. I will correct it in the next version


Why is it not working in Greenland?

May you give some more details so we can compare with the iOS library? A snippet of how you are calling the library and with what parameters would help.

When I try Greenland location it gives this error "java.lang. IllegalStateException at com.batoulapps.adhan2.PrayerTimes.<init(PrayerTimes.kt:168)"

Try Greenland's Latitude & Longitude. you can face it.

@shohrab-swl we can only troubleshoot this issue if you provide a code sample.


how to comment single line as a multile line?

for example

int main() {
     /* std::cout << "Hello World\n";  */
}

and if i select multiple lines, it should comment as

int main() {
     /* std::cout << "Hello World\n";  */
     /* ... */
     /* return 0; */

}

Yeah I have this problem too. I have to switch back to vim-commentary because of this  :cry:

Hi, thanks for your interest in kommentary, unfortunately I'll not be adding any new features, I'm sorry I never got to this issue.


What is the effect of taking over the render loop in useRender?

Hi, just a short question. When would I want to use the takeOverRenderloop in useRender? Seems like my setup is working fine without it.

take over means you're responsible for rendering yourself by calling gl.render(scene, cam). this can be useful if you want to stack rendercalls (heads up display) or if you use effect composers. otherwise 3fiber will render for you, and useRender is just a callback that's called every frame.


Issue in line 48

In the code in line 48 is a Error.
Error: Button.__init__() got an unexpected keyword argument 'custom_id'

The code is not starting. discord-components does not exist. I forked this repo and will renew this code.


Small fix python example for mender configure

As you can see from logs created inside the same file on the device this is the value of sys.argv.
14:41:02,820 root INFO ['/usr/lib/mender-configure/apply-device-config.d/example_script.py', '/var/lib/mender-configure/device-config.json'
Also run into troubles with the arguments of subprocess.run so I prefered to let all the command inside a list.
External Contributor Checklist

🚨 Please review the guidelines for contributing to this repository.

[ ] Make sure that all commits are signed with git --signoff. Also note that the signoff author must match the author of the commit.

Description
Please describe your pull request.
Thank you!

Also @JuanPabloMF you have to signoff your commit :)

Follow-up here: https://github.com/mendersoftware/mender-docs/pull/1694

Thank you @JuanPabloMF


demos does not work with Samsung A41 Android 12 with Chrome 128 & Firefox 132

Hi
I've tested many "demos" but the "registration" does not work, it throw "The operation either timed out or was not allowed" with recent environment (Samsung A41 Android 12 with Chrome 128 & Firefox 132).

It works with Samsung and Android 14


se_extractor

Where is the "se_extractor" library imported in the example? I cannot find any resources for this library online.
实例中的“se_extractor”库在哪里导入？我从网上找不到这个库的资源

it's py script in repo - https://github.com/myshell-ai/OpenVoice/blob/main/se_extractor.py

No File, any new link?


Allow for configurable pomodoro lengths

My team uses 50 minute pomodoros with 10 minute breaks in between. Would it be possible to add to the startwork command a optional parameter to say how long your pomodoro will be?
I don't do much ruby or I'd make a pull request myself.

Technically, that is pretty straightforward to build.
The original idea was to keep as close as possible to the published "Pomodoro technique", which specifies 25 minutes. I believe this because it's a typical amount of time that people can focus without getting distracted.
However, this is a question that comes up somewhat regularly, so I guess I may get around to doing it, although, it won't be until I've dealt with the other things that are outstanding.

I have a coworker who codes more ruby, and we looked at it.
It feels like if startwork were changed to the following:
def startwork
return help_response if help_requested?
return already_active_response if task_active?
task = Task.create(user: @user, team: @team)
<EMAIL_ADDRESS>if start_dnd?
durationParam = params[:duration]
duration = durationParam != nil ? durationParam : unit_duration.minutes
EndTaskWorker.perform_in(duration,
task.id,
params[:response_url],
start_dnd?)
render json: response_json(started_work_message, response_type)
end
It might be sufficient, however we haven't tested this at all. How do you test these things on your box? do you have a instance of slack that you can run it against?
We could submit a pull request if you want (my coworker wants to make a test app, but I am willing to test this out in whatever way you usually do).
Thanks!

The Slack API is quite particular about how it accepts and provides different arguments, so params[:duration] won't work with Slack.
The alternative, if you want this quicker than I can do it, is you fork the repo, change the value in the code and deploy a new copy onto your own server. It's all quite open and free to play around with.

Happily figured out that task duration was customizable but came across an issue: it appears as though the "time's up" notification only appears for 25-minute tasks. Also, under custom times, it looks like distractions aren't recorded at all. Is this a known issue?
Thanks for the work on Tomatobot!


luci-app=bcp38: improve interface selection dropdown

Certain types of interface were excluded from bcp38's concept of
upstream wan interface e.g. pppoa-wan
Shameless copy the interface list generation from luci-app-sqm which
solved exactly the same problem and gives additional clues by displaying
the firewall zone (typically wan/lan etc)
Run-tested-on: DGN3500
Signed-off-by: Kevin Darbyshire-Bryant<EMAIL_ADDRESS>

Merged, thanks!


Adding Support for 9216 (RTD) module

[X] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Adds support for 9216 module in module models enum.
Why should this Pull Request be merged?
required for pull request: https://github.com/ni/niveristand-scan-engine-module-libraries/pull/28
What testing has been done?
same testing as linked pull request:
SEECD deploys with VS 2017 (with the 9216 module added to system definition) correctly
The 9216 settings were changed to exercise all options of device-specific config.
Deploy and test successful to Linux64 target (9045).

This build is expected to fail. I will work with @dbendele to get a build before submitting this (likely after the code has been reviewed and any feedback is addressed).

Main - On Load.vi

[ ] Your new mutation case appears to be based off of case # 4, which added support for the 9214. This is actually more complicated than it needs to be; you can use the beginning logic from case # 5,6 to do the same thing.

The reason that the 9214 case needed to be handled differently than yours was that the 9214 was previously represented in shipping code as a different class, and needed to be explicitly converted. Since you are introducing a new module, this doesn't apply and the standard "fix how LabVIEW broke my enums" conversion needs to be run.
It does look like all of the mutation here is a bit wonky, since we end up running some mutation we ought to run once multiple times (although to no detriment). I might file a bug on that.

https://github.com/ni/niveristand-scan-engine-ethercat-custom-device/pull/77/commits/7afc6e0b9c85b461cd988b9c0b8a920b37caa60a
resolves Ryan's review feedback.

build of this commit was aborted because it did not correctly reference the export from the related/dependent pull request for the updated modules component.

Thanks for guiding the effort towards my first commit to this repo.


Break up into components

Right now, this is a simple SPA with everything contained in /pages/index.js.
Really, I need a <Layout />, and <Header /> components, so we can easily create other pages.

hi @gregrickaby, would like to take this up. Please assign

Hi @gregrickaby , what a nice project. Could you assign this to me?
Sorry, let me clarify what you mean.
So do you want to put only <Layout /> component inside the index.js? And then put <Sitehead /> and the rest inside the layout?

Exactly!
Then I can create other pages and update the 404 page to match sitewide layout.

Hi @gregrickaby  Please kindly check this #70 PR.
But I think I broke the changes by accidentally click merge 'main' to my branch.
I want to make sure if it's still okay.


Point Releases

I've written up a draft of the RFC here:
https://github.com/Mark-Simulacrum/rfcs/blob/point-releases/text/0000-point-releases-on-a-schedule.md
Please leave initial feedback in this issue. Eventually I guess I'll probably publish it for wider review within the community (preRFC and so forth).

Some more drawbacks:

Increased workload for the release team, e.g. with RELEASES.md, the release post, and the releasing itself. The amount of work hours is maybe 5h total?

More alternatives:

We could leave this more as a guideline within the 2-4 week window, and leave some example-driven cases of when a PR would be reason enough to do a point release (e.g. "soundness hole fix", "stability hole fix").

Week 3: all stable backport nominations must be approved during compiler team meeting

(Not just compiler team that might want to backport.)

Increased workload for the release team, e.g. with RELEASES.md, the release post, and the releasing itself. The amount of work hours is maybe 5h total?

The RFC might not be doing enough to say this, but it should just be RELEASES.md. I estimate the added work on the release team side at approximately 1.5 hours spread across multiple days (writing release notes should be relatively quick, as should backporting -- we would not accept backports that don't merge cleanly). The release process itself is mostly a matter of bumping the channel file, making an announcement on internals, and then running a single command on the chosen date.

We could leave this more as a guideline within the 2-4 week window, and leave some example-driven cases of when a PR would be reason enough to do a point release (e.g. "soundness hole fix", "stability hole fix").

I'm not sure I follow this alternative. This is the status quo alternative, right? i.e., basically not accepting this RFC? (And as such is already listed in the RFC, I believe, but do correct me if I didn't make that clear enough).

The compiler team is not the only team that wants to backport, but I think they're the best suited for judging whether a backport should happen or not today. To my knowledge they are the only team with regular meetings that has the placement to judge such backports. They are also, I expect, reasonably able to do so for pretty much all PRs out there that we would want to backport.

The RFC might not be doing enough to say this, but it should just be RELEASES.md.

Hmm; we did have release blog posts for past point releases though, e.g.:

https://blog.rust-lang.org/2019/05/14/Rust-1.34.2.html
https://blog.rust-lang.org/2019/04/25/Rust-1.34.1.html
https://blog.rust-lang.org/2018/12/20/Rust-1.31.1.html
...

So this would be a policy change, right?

I'm not sure I follow this alternative. This is the status quo alternative, right? i.e., basically not accepting this RFC? (And as such is already listed in the RFC, I believe, but do correct me if I didn't make that clear enough).

It's closer to the status quo, but I'm imagining this as "status quo + clearer guidelines around what to do and when to do". Basically, I think we don't have a lot of clarity right now on what would merit a point release, or at least not a shared articulated vision.

The compiler team is not the only team that wants to backport, but I think they're the best suited for judging whether a backport should happen or not today. To my knowledge they are the only team with regular meetings that has the placement to judge such backports. They are also, I expect, reasonably able to do so for pretty much all PRs out there that we would want to backport.

Fair points.

Yes, the avoidance of a blog post is a policy change and explicitly intended to mitigate the drawback of increased noise for the community. Though the RFC does not explicitly discuss this (it should, I think) I would expect us to issue blog posts for changes that today (before this RFC) would warrant a point release -- specifically, those that you've listed in your clearer guidelines suggestion.
I think if we do go with the clearer guidelines, then I would opt to close the RFC and pursue those guidelines without an RFC (just a forge PR, basically).

I think a brief blog post would be warranted only if the point release causes previously-compiling code to no longer compile (e.g. for soundness hole fixes).
I would also like to add something to our standard blog post verbiage to the effect that "a bugfix release, 1.XX.1, will be made available on [date]." That would ensure that these extra releases are not a surprise.

There is a drawback that I don't see mentioned in the RFC: if we start making regular point releases, they won't be something exceptional people need to upgrade to ASAP anymore.
That has a slight advantage for us: it allows fixing regressions sooner without people noticing that much. When we released 1.26.1, 1.26.2, 1.27.1 and 1.27.2 in quick succession to fix match ergonomics people started to criticize us, and rightfully so, because that feature didn't live up to our quality standards when it was stabilized. Having regular point releases would make it slightly harder for people to notice us fixing features post-release.
This is not something I'd like for us to push though: public scrutiny when we screw something up is good and needed, as it allows us to improve our processes and do better next time.
Also I feel like we need to maintain the exceptionality of our point releases. When a feature needs to be unstabilized or there is an unsoundness, we need people to update ASAP to limit problems in the ecosystem (i.e. new crates using the removed features). Currently point releases are a great way to do that, but if we start to make them regular I worry they might become less effective.

Hm, it's an interesting perspective that more frequent point releases decrease the likelihood that folks will update immediately. Do you feel that the point that any "significant" point release would get a blog post would help alleviate that? I imagine that today most people don't follow even our release schedule, rather they see a blog post "new rust release!" and consider updating at that point.

Honestly I don't know, but I'd slightly prefer not to risk. At least to me the motivation doesn't seem that much worth the risk.

Thinking on this more, I would prefer if the RFC was instead a fixed time commitment, say 3–4 stable releases. After which we can review if we want to continue. If people want to try it out new releases I'm happy to support that, but I don't think we should have commit to doing it for the foreseeable future without trying it out first.

I think if we choose to pursue a fixed time commitment approach, then I would personally forgo the RFC and just try things out, though maybe not for quite that long.
@pietroalbini Okay. I guess then it's more "correct" in some sense to say that your main problem is insufficient motivation, so other fixes won't actually help, right? i.e., you don't perceive a problem, so fixing it through expenditure of effort isn't worth it.
I can certainly agree that there's not much of a problem, though I would like to remove the concept of stable-nominations in that case -- i.e., say that we will not do point releases except in exceptional circumstances (as has been our policy so far), and that as such we don't want to spend release team and compiler team time on reviewing those backports.

I think if we choose to pursue a fixed time commitment approach, then I would personally forgo the RFC and just try things out, though maybe not for quite that long.

I'm also fine with that, though we should at least make a blog/internals post about trying it out.

Okay. I guess then it's more "correct" in some sense to say that your main problem is insufficient motivation, so other fixes won't actually help, right? i.e., you don't perceive a problem, so fixing it through expenditure of effort isn't worth it.

Yeah. To be clear I still perceive it as a problem, but not as a problem important enough to overcome the drawbacks of addressing it.

I can certainly agree that there's not much of a problem, though I would like to remove the concept of stable-nominations in that case -- i.e., say that we will not do point releases except in exceptional circumstances (as has been our policy so far), and that as such we don't want to spend release team and compiler team time on reviewing those backports.

I think having stable-nominated is still worth it, but maybe we can reform it by having the compiler team look at it and approve it only if the release team decides there is an issue worthy of a point release.
At least from the infrastructure side it's still helpful to keep track of PRs we'd need to backport to stable if we ended up making a point release, for example if an external URL died and we switched to our own mirrors.

Sure, yes, that's a good point re:not removing stable-nominated entirely. The suggested process change there seems fine too.
I have increasingly been thinking that I agree with you that there are many downsides here, and perhaps not enough benefits. I'll leave this open for now, but am currently leaning towards not posting it. :)

I think having stable-nominated is still worth it, but maybe we can reform it by having the compiler team look at it and approve it only if the release team decides there is an issue worthy of a point release.

That seems like a good time saving measure for the compiler team potentially (though cc @nikomatsakis @pnkfelix). I agree with the sentiment that having us review what falls under "exceptional circumstances" is still a good idea.

Personally, I think it would be worth trying. Even going into a release cycle with the expectation that we will err on the side of doing a point-release might save us some time discussing it during meetings.


Fix python dependencies

What does this PR do?
Fixes the python dependencies that had problems exposed while working on the AWS CI scripts.
The version numbers were conflicting with the apt package virtinst causing pip to become corrupted. We are installing virtinst on the same host as drb-python as the host VM will be the build server and running the host hypervisor.
Do you have any concerns with this PR?
no
How can the reviewer verify this PR?
Run snaps-boot CI scripts but change the requirements-git.txt drb-python line item from the branch 'master' to this one 'aws_ci'
Any background context you want to provide?
Screenshots or logs (if appropriate)
Questions:

Have you connected this PR to the issue it resolves?
none for this repo, but the one in snaps-boot is issue #260
Does the documentation need an update?
no
Does this add new Python dependencies?
no
Have you added unit or functional tests for this PR?
no
Does this patch update any configuration files?
no

Still having issues with the enum dependency


🚀 Feature: Add docs for local grafana tempo integration

Which component is this feature for?
Anthropic Instrumentation
🔖 Feature description
An addition to the grafana tempo docs that includes instructions on how to connect it with a local grafana instance.
🎤 Why is this feature needed ?
I'm evaluating traceloop for my team. I don't have much grafana experience and so trying to get this working with a local version of grafana has honestly been an absolute nightmare. (even though I know it should have been really simple)
✌ How do you aim to achieve this?
Add a blurb under the "Without Grafana Agent" section:
If you are running tempo locally set the environment variable to point to tempo's http ingest port
default: TRACELOOP_BASE_URL=<IP_ADDRESS>:4318
🔄 Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?

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

Are you willing to submit PR?
None

@zioproto @DSgUY @henryxparker if any of you are willing to update our docs at https://github.com/traceloop/docs with the things you learned here that would be tremendously helpful for the community! ❤ I just can't seem to get enough time to test this myself so I can't be certain how to fix our current guide.

I'm still trying but sure...

I manage to get the traces. can i configure metrucs and logs? Maybe using prometheus, promtail and loki?

I think grafana agent can translate the otel metrics format to Prometheus - https://grafana.com/docs/agent/latest/flow/tasks/opentelemetry-to-lgtm-stack/

Btw @DSgUY traceloop as a platform can also integrate with grafana if that helps


Verify non-deterministic iterators

We are seeing that some queries with similar start locations are assigned different graph ids. this implies that the distance metrics for the rtrees (vertex rtree, edge rtree) may need deterministic tie-breakers.
Similarly, we should review iterators to confirm all have deterministic tie-breakers:

graph iterators
a* queue

It doesn't look like rstar supports tiebreakers for the distance function used in nearest neighbors link


Add more tests for empty for statements

@hevrard commented on #203:
"
ForStmtTest.java could have all cases of absence of for loop header components, right now it has:
for ( ; 1; 1)
for (1; ;1)
for (1; 1; )
For the sake of completeness we could add:
for(;;)
for(;;1)
for(;1;)
for(1;;)
for(1;1;1):
"
Not urgent but would be good to do.

Closed via #507.


multiple chain-split triggerd by masternode paymentcheck

running 3 clients for mining, one for x11, scrypt and sha256.
in the last two days multiple chain split happend leading to chain-reorgs or completly full fork.
the chainsplits are a result of failed checks of MN payments, but on the mining node the check was successfull.
example:
block found on node 1 (scrypt)
2020-08-03 10:38:21 UpdateTip: new best=bd366c7ab43990f5897149d2f8bae73f7a12202f05c14e5d59d962f0d85c2fa3 height=74418 version=0x20000002 algo=1 (scrypt) log2_work=76.09157479 tx=107295 date='2020-08-03 10:38:18' progress=1.000000 cache=1.5MiB(11328txo)
2020-08-03 10:38:21 AddToWallet 846245fe299e325c90e40297d7e1b2bb73043e52a2aacf623a5dc5a27d2cee48  new
2020-08-03 10:38:21 ProcessNewBlock : ACCEPTED
same block rejected on node 2 (x11):
2020-08-03 10:38:22 CMasternodeBlockPayees::IsTransactionValid -- ERROR: Missing required payment, possible payees: 'PV7YZ6F3Fy6jx1B7ShZwz5GgtT9AYdyVpt', amount: 20.000006 PYRK
2020-08-03 10:38:22 IsBlockPayeeValid -- ERROR: Invalid masternode payment detected at height 74418: CTransaction(hash=846245fe29, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000,<PHONE_NUMBER>), coinbase 03b22201041ae9275f08810005a08d0200006d696e696e6768756200fabe6d6dacb3fcb6fac5843891a365af87831e5e77daf4713487b1ce888c6e9ac9da9f0e1000000000000000, nSequence=0)
    CTxOut(nValue=20.00000668, scriptPubKey=76a91437c8d53d99ec26af960d2ee6)
    CTxOut(nValue=70.00002344, scriptPubKey=76a9147d3c5787255efc06a90c6073)
2020-08-03 10:38:22 ERROR: ConnectBlock(): couldn't find masternode or superblock payments
2020-08-03 10:38:22 InvalidChainFound: invalid block=bd366c7ab43990f5897149d2f8bae73f7a12202f05c14e5d59d962f0d85c2fa3  height=74418  log2_work=76.09157479  date=2020-08-03 10:38:18
2020-08-03 10:38:22 InvalidChainFound:  current best=00000000000000124c1b884b459e7b8824fa7e6b2804bbd5cec426330a6e6c22  height=74417  log2_work=76.09155878  date=2020-08-03 10:32:25
2020-08-03 10:38:22 ERROR: ConnectTip(): ConnectBlock bd366c7ab43990f5897149d2f8bae73f7a12202f05c14e5d59d962f0d85c2fa3 failed

we will be doing some updates soon to update these items:
DIP0002 - Special Transactions
DIP0003 - Deterministic Masternode Lists
DIP0004 - Simplified Verification of Deterministic Masternode Lists
Automatic InstantSend for "simple" transactions
Multiple improvements to PrivateSend
New Masternode Tab for DIP0003 Masternodes

Still seeing a lot of forks happening with 4 nodes on v<IP_ADDRESS>

This issue should now be fixed in the v0.13.0 release


Fixed homepage visitor counter to track unique visits only once per user session

#Title : Fixed homepage visitor counter to track unique visits only once per user session
Fix #359
Description
This PR addresses the issue where the visitor count increments each time a user returns to the homepage, even if they have already been counted. The visitor count now only increments on the first visit per user session, ensuring each visitor is counted only once.
@Anuj3553 Pls assign me this issue, give me labels, level.

Hyy @ygowthamr,  I'm assigning this issue to you.


Update Create Post flow design on Desktop to Match Figma

Update Create Post flow design to match Figma
https://www.figma.com/file/4cV84H1jyMo0rJEAl3HNnJ/FightPandemics-landing-page?node-id=1628%3A13260
Closes #172

Hmm yeah @limaneto I see you have a fully custom Form component and some related components here. Why not use react-hook-form library and keep it consistent with the other forms? I will actually open a ticket about this, I haven't checked yet how much difference there is between all the different forms, so we can make some components more reusable.

Hmm yeah @limaneto I see you have a fully custom Form component and some related components here. Why not use react-hook-form library and keep it consistent with the other forms? I will actually open a ticket about this, I haven't checked yet how much difference there is between all the different forms, so we can make some components more reusable.

can we do it in another ticket? I think this issue here is really overdue.

Hi,
I was reviewing https://feature172style-create-post.fightpandemics.xyz/feed.
I have a question about Tag section. On Figma design tags are group by four. (Legal is repeated twice). There is an Others tag not Other. Personally I prefer Other.

Hi,
I was reviewing https://feature172style-create-post.fightpandemics.xyz/feed.
I have a question about Tag section. On Figma design tags are group by four. (Legal is repeated twice). There is an Others tag not Other.

I dont understand the question

Hi,
I was reviewing https://feature172style-create-post.fightpandemics.xyz/feed.
I have a question about Tag section. On Figma design tags are group by four. (Legal is repeated twice). There is an Others tag not Other.

I dont understand the question
Hi @limaneto,
My question was about section 2 What are you offering. Add tags to make your post more visible
On figma design tags are group by four:

I was using this link: https://feature172style-create-post.fightpandemics.xyz/feed where tags in the section 2 were group by 5. Could we have them group by 4 like in figma design?
If a link/case is no longer valid. Please ignore my question. @galeza

I don't think it makes a lot of sense to set a predefined number of columns since it depends of the number of letters in each tag. You can test is, increase the number of letters in each tag through html and you will see the number of columns change

Is this ready to merge?

Is this ready to merge?

missing one approval more


Update docs with Google AppEngine instructions

Extends the documentation to explain how to run BaGet on Google AppEngine, using Google Cloud Storage (enabled by #233) and Google Cloud SQL (enabled by #206).

This looks great so far! Thanks for expanding this documentation. I left some minor comments, I’ll merge this after :)


Wrong units for the cost?

The description says 'costs are in milliseconds', however fprof output is in milliseconds and erlgrind multiplies these values by 1000, so the costs must be in microseconds?

Yeah it's got to be microseconds. fprof docs clearly say in milliseconds http://erlang.org/doc/man/fprof.html


输入sql，开发环境没有提示框

Describe the bug

Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

第二张图是开发环境，没有提示框

提供下完整代码


MultiFieldPanel help_text no longer renders in 4.0

Issue Summary
In Wagtail 4.0, the help_text argument in the MultiFieldPanel is no longer rendered, whereas it was rendered in 2.x and 3.0.x.
Steps to Reproduce

Start fresh Wagtail installations for 4.0 and 3.0.2 as per the instructions at Getting Started. For each:
Merge in the application at https://github.com/dkirkham/wagtail-ui-testpage
Add 'testpage' to INSTALLED_APPS in settings/base.py
Migrate and runserver
Login to the Wagtail admin interface
Create a child Testpage of the home page
Go to the Event Details tab
Observe the Orderables Header multifield.

In 3.0.2, the help_text content appears at the right when hovering over the multifield:

In 4.0, the help_text is not rendered:

The help_text is carried through the 4.0 code and is available in the template context.

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: (yes)

Comments
This issue could be considered a bug, a documentation bug or a feature request.
At the moment, I'm illustrating a difference in functional behaviour, in that the help_text that was visible in 3.0.2 is no longer visible. If this was the design intent with the new UI, then it is a documentation bug in that it should have been commented in the Upgrade Considerations part of the 4.0 release notes.
In my initial Slack support discussion thread (here) it was suggested that the solution might be to use a HelpPanel. This may be a reasonable and more flexible solution – given the reason I originally used the MultiFieldPanel was mainly to get the red banners. If the UI team think this is the best solution, then that should be documented. But to maintain the original function, it might still make sense to at least render the help_text if it is provided.
Incidently, the InlinePanel label that is rendered in the 4.0, as part of the InlinePanel and above the button that instantiates each new Orderable form, may be superfluous. This should also be considered by the UI team.
Technical details

Python version: Testing with 3.9, but probably irrelevant
Django version: Testing with default versions for each wagtail release, but probably irrelevant
Wagtail version: As per the instructions - 3.0.2 and 4.0
Browser version: Screenshots with Firefox 103, but probably irrelevant

@dkirkham thank you for reporting this! I implemented most of the changes to MultiFieldPanel, and I wasn’t aware it supports a help text. I don’t think I’ve ever seen this in action nor in the docs.
Do you have any thoughts on your side on whether this should be considered a bug or not? I’ll investigate on my end as well.

Hi @thibaudcolas,
I had to go back to my original code, and I can see in one of the earliest commits in that project I have MultiFieldPanels with help_text parameters. That was with Wagtail 2.7.1, early in 2020.
Whether I did look at the Wagtail source code at the time, saw something in Kalob's excellent videos or a StackOverflow answer, or serendipitously confused FieldPanels with Fields which do support help_text, I don't know.
While I agree the help_text parameter is not documented, it is in the code for MultiFieldPanels parent Panel class and the value is passed to the rendering context. The change in the templates between 3.0 and 4.0 resulted in the change of behaviour.
Because my use depends on undocumented behaviour, it is difficult to argue this is a bug. However, I've used this behaviour and I've found some instances of this in public GitHub repos that also do, so the idea of using help_text within a MultiFieldPanel appears to be in the wild.
Given this, it might make sense to support rendering help_text if it is present, which will be a simple addition to the relevant template. If there is a specific desire not to support this behaviour, then a warning might make sense, with the suggestion to use a HelpPanel instead. Some documentation to this effect against MultiFieldPanel would also help.
I'm happy to change my code whichever way you decide, and if you want, I could prepare a Wagtail PR accordingly.

Idea - we drop the concept of help_text on panels (it is confusing and gets muddied up with help_text on fields), and we migrate to something like description or subtitle.
I think this is a super useful feature and recall using it a long time ago on MultiFieldPanel but as it's not documented currently maybe we have a little room to move (make this useful again) without pulling the whole code out.

I haven’t checked the code @lb-, but I presume the help_text from each Field is passed to help_text in the corresponding FieldPanel, so most of the current functionality would need to be kept.
Given that, would your suggestion apply just to MultiFieldPanels or to all panel types?
Or is it easier to keep the <=3.0.x behaviour, albeit adapted to the new UI, with one or two lines of template code?

I got to investigate this a bit,

I found 3 such MultiFieldPanel help_text definitions on sites I have access to the code for
This seems to have worked for all panels at the top level, because the rendering actually came from our ObjectList’s object_list.html template, it wasn’t specific to any panel type.

While I was looking into this, I realised we’re also no longer rendering help_text for InlinePanel, which is clearly a bug.

Considering all of the above, I think I’m leaning towards at least restoring the previous behavior for help_text in MultiFieldPanel (and FieldRowPanel) for Wagtail 4.0. I’m not sure what would be the best way to go about this, there are a few options:

Re-add the help_text rendering for all ObjectList children, as before. I find it a bit confusing that help_text would only work for those panels when used without nesting, but at least we’d be back to feature parity with Wagtail 3
Add the help_text rendering separately to InlinePanel, MultiFieldPanel, and any other panel type we see relevant.
More involved changes as suggested by LB

Options 1. and 2. should only be a few lines of template code to the effect of:
{% if panel.help_text %}

{{ panel.help_text }}

{% endif %}

My hunch is that option 2. would make more sense with the current direction of the panels API. @gasman since you’ve worked on this very recently I assume the best approach will be more obvious to you?

@dkirkham sorry I was away and only seeing your message now! We proceeded with the fix for InlinePanel + adding support for help_text everywhere else it used to work.
This will be fixed in the upcoming v4.1 (scheduled for 01/11/2022) and v4.0.3 (no set date) releases.

@thibaudcolas no worries, looks like the changes were much more comprehensive than I had in mind. I'll give the changes a test in my own project when I get a chance.


Highlight row selection onclick

Feature request while I'm thinking about it:
It'd be great if when you selected an item (either by clicking on the table row or the map point), beyond highlighting it on the map layer, if it also oriented/highlighted the matching table row.

+1 for that feature


Investigate how to correctly use mina-replayer for the purposes of generating ledgers at block heights

This enables us to compare the indexer's Ledgers directly with what the Archive Node produces at each block height.
Reading material:

https://github.com/MinaProtocol/mina/blob/8904a8e8a9b2a557126cb6de2100fd488474f6aa/scripts/archive/fix-all-balances.sh#L23

These are Gareth's note when he ran it:
Basically, you pick a block state hash, and it uses that to get all the transactions and internal commands to that point. You also need to append this info to the input ledger. It then checks the resulting ledger at that point but you can also verify that externally - there is a weird off by one in that if you specify a block height of 1000 it'll actually produce the ledger for block 999 which I think is because it accounts for the genesis block.
curl -s "https://raw.githubusercontent.com/MinaProtocol/mina/compatible/genesis_ledgers/mainnet.json" | jq '{target_epoch_ledgers_state_hash:"'3NK8ukCSK6uqQjquoNdbSQHgaoNDJvbJvbFdW5xNWNBF7rkcQ9RK'",genesis_ledger:{add_genesis_winner: true, accounts: .ledger.accounts}}' > replayer_input.json

/usr/local/bin/mina-replayer --archive-uri<EMAIL_ADDRESS>--input-file replayer_input.json --output-file /dev/null --continue-on-error > replayer.log

tail -f replayer.log

I had issues when doing a much larger number of blocks
out of shared memory\
  \nHINT:  You might need to increase max_pred_locks_per_transaction.\

I also took the resulting ledger file and then use mina ledger hash
Notes from Paul Steckler:

If you run the replayer with a --checkpoint-interval of 1, you'll get a checkpoint file with a ledger after every block. At least, I think that will work.

Outcomes:

Document correct usage to generate AN ledgers with the replayer for each block height

Note: There is a memory leak in the replayer where you can only replay up to 1000 blocks then it crashes.

#/bin/bash

# Use this script to generate ledgers from the AN. This is useful for
# us to compare ledgers with the indexer.

state_hash=3NL9qBsNibXPm5Nh8cSg5CCqrbzX5VUVY9gJzAbg7EVCF3hfhazG
mina_replayer=$(which mina-replayer)
connection_string=

curl -s "https://raw.githubusercontent.com/MinaProtocol/mina/compatible/genesis_ledgers/mainnet.json" | jq '{target_epoch_ledgers_state_hash:"'$state_hash'",genesis_ledger:{add_genesis_winner: true, accounts: .ledger.accounts}}' > replayer_input.json

$mina_replayer --checkpoint-interval 1 --archive-uri $connection_string --input-file replayer_input.json --output-file /dev/null --continue-on-error > replayer.log


test

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why
Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests.
How
How did you build this feature or fix this bug and why?
Test Plan
Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction.

/changelog-entry new-feature test

/changelog-entry bug-fix test

/changelog-entry bug-fix test

/changelog-entry bug-fix test

/changelog-entry bug-fix test

/changelog-entry bug-fix test

/changelog-entry bug-fix test

/changelog-entry bug-fix test

/changelog-entry bug-fix test


update deps (handles both yarn and npm package managers)

resolves #1

There is no package.json in your pull request. So no packages are updated. Maybe you have forgotten to commit the file?


Provide a nicer login page rather than Spring Security default

If Spring support it, then maybe a configurable Public mode (IE not logged in yet) that would let you see running containers and start new ones depending on a global setting?


Split API structs into separate package

All the structs are currently private structs in the v1 package. This
means if you want to create a client in golang you have to reimplement
(or copy/paste) structs etc. This Splits them out to a separate package
for clarity

"stats" have been added to the API response, but this patch applies cleanly for a backport. So if this is something that can get merged in I can rework this for whichever version makes sense.

cc @fabxc @juliusv @beorn7

can you explain what is the use case?
I think so far the v1 api has been used only through the http json requests.
Also why not just export the structs than moving them in a separate package?

Use Case
The use case is still to use them over the HTTP Api -- but specifically if your client is in golang right now that is a pain because (from the original message): This means if you want to create a client in golang you have to reimplement (or copy/paste) structs etc.
Separate Package
The main reason to split them out is for docs clarity. I've submitted some PRs in the past to export structs, and the usual complaint it that it pollutes the package godoc space. If we'd prefer to not move these to a separate package I'll gladly change the PR,

best if @brian-brazil or @fabxc  jumps on this one with some input.

It's indeed a bit inconvenient if one wants to implement something on top. However, isolated struct-packages are more of an anti-pattern. I think just exporting them within the package they are currently in would be perfectly fine.

I'm not sure we want these specific structs exported. All the other things we have exported have obviously been internals, and we gave appropriate warnings to the users of them that their use was unsupported which was understood and accepted.
For the structs backing our actual public APIs, that's not really going to be the case. I think this sort of thing belongs in https://github.com/prometheus/client_golang/tree/master/api

if you are importing a package just to use its types you are doing somehting wrong.
Package should be imported for its functionality!

That is what I belive in :clap:  :smile:

This PR now has conflicting instructions I have both  I think just exporting them within the package they are currently in would be perfectly fine. and I'm not sure we want these specific structs exported. Which one are we working with here?
These particular structs are in use both by the server (as they are what is marshaled out) and the client (as they are receiving them). From the rest of @brian-brazil 's comment it sounds like you want me to move these structs to the client_golang package? If so, do you want the api to require that package or do you expect a copy/paste? I'm fine to move the code there, but it really seems like the structs should stay with this package-- since they'd have the same compatibility guarantees as the prometheus v1 API anyways.

I'm proposing that we leave things as-is.

Meaning the expectation for clients is that they copy/paste or make their own structs? That seems like unnecessary complexity/work for http clients in golang

I don't think this makes sense overall.


Request for convert

Can you convert below package as flutter
https://github.com/SwapnilSoni1999/messages-web

@selvam920 this is not related to whatsapp_bot_flutter , let's discuss on Telegram , my telegram id:  @rohitsangwan01


Fix use of GuiSliderBar in examples.

Fixed a couple of examples as they weren't compiling. Happy Christmas!

@badlydrawnrod Ouch! I updated raygui but not those examples... Thanks for the review!

Just ran into this trying to build 3.5.0.
Any chance is a micro version bump?

Just ran into this trying to build 3.5.0.
Any chance is a micro version bump?


Update meta-rust to include 1.36

Can one of the admins verify this patch?

@resin-jenkins test this PR

@resin-jenkins add to whitelist

@resin-jenkins add to whitelist

@balena-ci retest


Cannot train canned estimators in multiple estimator.train() calls when using tf.keras.optimizers or tf.optimizers

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
Platform: Code run in google Colab
Python version: Python 3
Tensorflow version: v2.0.0-rc1-51-g2646d23 2.0.0-rc2

Describe the current behavior
When training a canned estimator with multiple tf.train calls while using any tf.keras.optimizer the optimizer raises an exception.
Describe the expected behavior
Repeated tf.train calls train for the given amount of steps.
Code to reproduce the issue
Lightly edited example using canned estimators:
https://gist.github.com/JoshEZiegler/2a923a707d831ca7efd33dbfbf9779c9
Other info / logs
RuntimeError                              Traceback (most recent call last)
 in ()
5 classifier.train(
6     input_fn=lambda: input_fn(train, train_y, training=True),
----> 7     steps=500)
7 frames
/tensorflow-2.0.0-rc2/python3.6/tensorflow_core/python/keras/optimizer_v2/optimizer_v2.py in iterations(self, variable)
660   def iterations(self, variable):
661     if self._iterations is not None:
--> 662       raise RuntimeError("Cannot set iterations to a new Variable after "
663                          "the Optimizer weights have been created")
664     self._iterations = variable
RuntimeError: Cannot set iterations to a new Variable after the Optimizer weights have been created

@JoshEZiegler ,
Hi, i tried running the given gist for TF-2.0 and 2.0rc1 i did not face any error. Can you provide gist of colab where you are facing the issue ? Thanks!

I'm not sure what you mean by a gist of colab. The gist I provided was saved from colab and shows to me a link to open the ipynb in colab. It may have been still processing something when you saw it? I'm a bit unfamiliar with particulars of colab/gists so I could certainly be making a mistake.
After checking the traceback, it appears that the issue I had occurred with 2.0rc2 so this could be specific to that version (maybe that's what you're saying here). In that case maybe this is solved in the most recent release?

I tried versions 2.0.0-rc1 and 2.0.0 with this same ipynb in colab but they both gave me the same error.
Changing to tf.optimizers rather than keras does not change it either.

@JoshEZiegler ,
I tried with versions 2.0, 2.0rc1,2.0rc2 and didn't face any error. Please find gist of colab for respective versions.

Here is a link directly to the code in colab with TF 2.0.0:
https://colab.research.google.com/gist/JoshEZiegler/2a923a707d831ca7efd33dbfbf9779c9/premade.ipynb
TF 2.0.0-rc2:
https://colab.research.google.com/gist/JoshEZiegler/6191d345f7dbd5f8e1152ac64fc890cb/premade.ipynb
TF 2.0.0-rc1:
https://colab.research.google.com/gist/JoshEZiegler/9f73f47ed7d52a6a88ccf7355e5856b8/premade.ipynb#scrollTo=USjm2yKd_pt5

I tried running the linked code and I confirm I also see an error:

RuntimeError: Cannot set iterations to a new Variable after the Optimizer weights have been created

With some investigation, it looks like running estimator.train() multiple times is ok with the default optimizer, or by specifying the optimizer with a string. I believe that this is because the estimator.train() actually creates a new instance of the string-specified optimizer with each call, but retains the optimizer object if one was specified in the train call (see below).
A possible workaround for the above error could be to modify this function to return a fresh optimizer with the same parameters as the opt instance specified. However, I'm not sure if this is easily achievable or if there are any use cases that this would break...
From /tensorflow/estimator/blob/master/tensorflow_estimator/python/estimator/canned/optimizers.py
def get_optimizer_instance(opt, learning_rate=None):

if isinstance(opt, six.string_types):

    if opt in six.iterkeys(_OPTIMIZER_CLS_NAMES):
      if not learning_rate:
        raise ValueError('learning_rate must be specified when opt is string.')
      return _OPTIMIZER_CLS_NAMES[opt](learning_rate=learning_rate)
    raise ValueError(
        'Unsupported optimizer name: {}. Supported names are: {}'.format(
            opt, tuple(sorted(six.iterkeys(_OPTIMIZER_CLS_NAMES)))))
  if callable(opt):
    opt = opt()
  if not isinstance(opt, optimizer_lib.Optimizer):
    raise ValueError(
        'The given object is not an Optimizer instance. Given: {}'.format(opt))
  return opt

@JoshEZiegler I'm not sure if this is applicable here, but I got the same error in different context and solution for me was to pass a callable instead of the instance as optimizer parameter allows that (docs). In your case you can pass optimizer=tf.keras.optimizers.Ftrl, I think.

@awolant I believe that workaround ends up being equivalent to what I mentioned just above your comment: passing a string to specify the optimizer. The key use case excluded by these workarounds is manual tuning of the hyperparams of the optimizer. It's unclear to me if there's a way to do that without passing an instance of optimizer...

@JoshEZiegler Right. My use case was a bit different and I missed that. But since we can pass any callable, then maybe something like this will work for you:
from functools import partial
AdamWithParams = partial(Adam, learning_rate = 0.1)

...

optimizer = AdamWithParams

More on what partial is you can find in  the docs. In my code it worked as expected.

@awolant Nice! Thanks, that sounds like the perfect workaround.
I'll leave this issue open because I don't believe that is the intended way to use optimizers with Estimators. At the very least not the way it is done in the TF docs.

Can you try with the latest tf-nightly? This should be already fixed.

This issue still shows up with tf-nightly-2.2.0.dev20200306. See this colab notebook.
Was there a specific version where you believe it should work?

Have you resolved it in TF-v2

I have got the same issue here too

Experienced the same issue in the latest tf-nightly, and reopening.
RuntimeError: Cannot set `iterations` to a new Variable after the Optimizer weights have been created

@mustafa-qamaruddin @JoshEZiegler Could you provide your use case of calling estimator.train() multiple times in a training pipeline?  If the model needs to train with more steps, you can increase the steps arg in the train() method. I feel it's arguable to call train() method multiple times with the same optimizer in the training pipeline.
I'm working on a fix, and would like to check it in if more context on the use cases are provided. Thanks!

@yhliang2018 Sure, my use was to manually log loss/accuracy/metrics for plotting, etc within a notebook.
To get around this error I went ahead and switched to using tensorboard for achieving this same thing so I'm no longer affected by this.
Hopefully this is the type of context you're looking for?
  steps_per_period = steps / periods

  #create DNNRegressor Object
  my_optimizer = tf.optimizers.SGD(learning_rate=learning_rate, momentum=0.9, clipnorm=5.0)
  dnn_regressor = tf.estimator.DNNRegressor(
    feature_columns = construct_feature_columns(samples),
    hidden_units = hidden_units,
    optimizer = my_optimizer
  )

  # Create input functions.
  training_input_fn = lambda: input_fn(samples,
                                          targets,
                                          batch_size=batch_size)
  predict_training_input_fn = lambda: input_fn(samples,
                                                  targets,
                                                  num_epochs=1,
                                                  shuffle=False)
  predict_validation_input_fn = lambda: input_fn(test_samples,
                                                    test_targets,
                                                    num_epochs=1,
                                                    shuffle=False)
  # Train the model, but do so inside a loop so that we can periodically assess
  # loss metrics.
  print("Training model...")
  print("RMSE (on training data):")
  training_rmse = []
  validation_rmse = []
  for period in range (0, periods):
    # Train the model, starting from the prior state.
    print("Period[%s]" % (period+1))
    dnn_regressor.train(
        input_fn=training_input_fn,
        steps=steps_per_period
    )

@JoshEZiegler Thanks a lot for providing your use case. Yes, tensorboard is definitely a good option to check such info.
I think it's still good to support such use cases when you prefer to log/check the model related info manually. I will have the fix submitted soon, and let you know when it's available in tf-nightly.

More thoughts on this issue: if people create an optimizer instance for canned estimator, it's natural that people think the created optimizer object is the one used in model optimization process. However, if different optimizer instances are created to support estimator.train() call, the optimizer for the model optimization is always the new one, which confused people a lot in some use cases. One example:
    dnn_opt = tf.keras.optimizers.SGD(1.)
    linear_opt = tf.keras.optimizers.SGD(0.5)
    input_fn = ...
    est = dnn_linear_combined.DNNLinearCombinedClassifierV2(
        ...
        linear_optimizer=linear_opt,
        ...
        dnn_optimizer=dnn_opt)
    num_steps = 1
    est.train(input_fn, steps=num_steps)
    assert num_steps == est.get_variable_value(linear_opt.iterations.name)  # The linear_opt is never used in the optimizer, so it breaks the access of linear_opt.iterations.
    assert num_steps == est.get_variable_value(dnn_opt.iterations.name)  # Same as above, dnn_opt is never used either and its iterations cannot be accessed.

@JoshEZiegler given this, how about let's hold to check in the fix for now, and wait for more feedbacks?

Experienced the same issue in the latest tf-nightly, and reopening.
RuntimeError: Cannot set `iterations` to a new Variable after the Optimizer weights have been created

i got the same error, have you solved it ?

@JoshEZiegler Right. My use case was a bit different and I missed that. But since we can pass any callable, then maybe something like this will work for you:
from functools import partial
AdamWithParams = partial(Adam, learning_rate = 0.1)

...

optimizer = AdamWithParams

More on what partial is you can find in the docs. In my code it worked as expected.

This workaround could be an option, but possibly not for your use case.

@yhliang2018 This issue still shows up with tf-nightly-2.2.0.dev20200306. See this colab notebook.
Was there a specific version where you believe it should work?

The same error occurs when running this same colab notebook using the latest tf-nightly.

Instead of partial, use lambda to create optimizer object each time. It's way more easier in this way.
linear_regressor = tf.estimator.LinearRegressor(
    feature_columns=feature_columns,
    optimizer=lambda:tf.keras.optimizers.SGD(learning_rate=0.0000001, clipnorm=5.0),
)

Hi There,
This is a stale issue. As you are using an older version of tensorflow, we are checking to see if you still need help on this issue. Please test the issue with the latest TensorFlow (TF2.7 and tf-nightly). If the issue still persists with the newer versions of TF, please feel free to open it in keras-team/keras repository by providing details about the issue and a standalone code to reproduce the issue. Thanks!
Please note that Keras development has moved to a separate Keras-team/keras repository to focus entirely on only Keras. Thanks!


secureTextEntry prop changing causes autoCapitalize not to work

Description
If I have a text field that is set to secureTextEntry being true, then I change it to false, autoCapitalize does not work. The characters stay lower-case
React Native Version
0.71.11
Output of npx react-native info
System:
OS: macOS 13.5.2
CPU: (10) arm64 Apple M1 Max
Memory: 6.37 GB / 64.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.14.2 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 9.5.0 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.0 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
Languages:
Java: 20.0.1 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: ^18.2.0 => 18.2.0
react-native: 0.71.11 => 0.71.11
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
using the code below, tap on the input. Enter text. See that it is all lowercase instead of capitalized
Snack, screenshot, or link to a repository
Had some issues getting it working in snack.expo.dev, but this is essentially the code that causes issues
import { useState } from 'react';
import { TextInput } from 'react-native';

export default function App() {
  const [ isFocused, setIsFocused ] = useState(true);

  return (
    <TextInput
      autoCapitalize="characters"
      secureTextEntry={!isFocused}
      onFocus={() => setIsFocused(true)}
      onBlur={() => setIsFocused(false)}
    />
  );
}

Hello,
Thanks for the issue. I have been contributing to facebook/react-native for 4 years and specialize in the Text/TextInput components. I currently have 58 facebook/react-native PRs:
https://github.com/facebook/react-native/pulls?q=is%3Apr+author%3Afabriziobertoglio1987+
It is the suggested approach from the react-native core team (see this discussion).
I'm publishing several fixes for Text and TextInput component in a separate library react-native-improved.

The Component is based on ReactTextView, it is the same implementation from react-native.
It will include several bug fixes.
You can use the library until the PR is merged and released with react-native.
You can use side by side both components from react-native and react-native-improved, depending on where you need the fix.
I will also publish the PR to facebook/react-native (daily fixes and releases).

The advantages would be:

Increased engagement with the community, issues are quickly fixed.
No limitations when merging PRs (react-native main branch is used on facebook marketplace).
Only Meta employees can merge and review facebook/react-native PRs.
Allows us to further experiment and develop react-native.

 I'm working on a list of priorities. Thanks


Make CONTRIBUTING.md reference development.md

Currently they are totally independent but mention somewhat overlapping facts.

Completed.
https://github.com/quantumlib/Cirq/pull/736


Fix local initialisation of IPFSTool/IPFSDaemon

Proposed changes
This PR updates the IPFSDaemon to perform ipfs installation check only when initialised locally.
Fix
https://github.com/valory-xyz/open-aea/pull/212#discussion_r914481029
Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[x] Lint and unit tests pass locally with my changes and CI passes too
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Why not keep the logic in the daemon instead of splitting it in both the tool and the daemon?

Which logic exactly?

Why not keep the logic in the daemon instead of splitting it in both the tool and the daemon?

Which logic exactly?

The newly added one, to check if the host is remote or not. I mean why pass around a flag to the daemon and not directly check in the daemon?

The newly added one, to check if the host is remote or not. I mean why pass around a flag to the daemon and not directly check in the daemon?

I think daemon class does not concern with checking if the host is remote or local. IPFSTool seems the right place to put the logic and is_remote variable.


Tween.is_active() always true after tween.stop() and then tween.start()

Godot version:3.2

OS/device including version: Several OS (Win10 / MacOS)
Issue description:
Tween never gets finished when tween.start() is called after tween.stop() without calling tween.resume()
Steps to reproduce:
Start() a tween.
is_active() become true (normal)
Stop() the tween before it finished.
is_active() become false (normal)
Start() the tween again.
is_active() become true (normal)
but in this case when the tween is over, it never switch is_active() to false.
Completed events are not fired.
Minimal reproduction project:
tween_bug.zip

Confirmed in 3.2.2 RC 3 (1468c0b4d4592406502c7e4eaa2121f1d0a7e5f6).

Just leaving this here as a note to myself, or to anyone else that may try and fix this
In the engine source, Node::set_internal_process is called in Tween::_tween_process at the end of the function when all the tween data has been successfully processed. It's on these lines (3.2 commit a662b853)
https://github.com/godotengine/godot/blob/a662b853dd5de7d47a8c5ebee3ae35cf66490d3f/scene/animation/tween.cpp#L801-L804
Notice that the signal tween_all_completed is emitted when the Tween is supposedly finished processing data. This signal does not fire when the bug is triggered, meaning that the culprit is somewhere in Tween::_tween_process

I would like to work on this issue if there nobody

@ChristopheLY That patch works for me. All that's left is for you to make a pull request!

Thanks a lot for your efforts to fix this issue but the commited fix in 3.2.3 RC1 introduce another bug : https://github.com/godotengine/godot/issues/40679

I think this issue should to be re-opened with the revert of commit  8ef40b9

I think the issue should be re-opened with the above revert of  8ef40b9 commit.

No because the issue is still fixed in the master branch.


Modifying assertIs(x, False) to assertFalse(x) changes the meaning for falsey value of x

Hello, and thank you for your work on teyit.
In the following case:
-       self.assertIs(inferred.value, False)
+       self.assertFalse(inferred.value)

If inferred.value is equal to [] or {} for example, the code does not do what it was doing before. (The same problem also apply to  assertIs(x, True) to assertTrue(x)
import unittest

class TeyitTest(unittest.TestCase):

    def test_teyit(self):
        self.assertFalse(False)
        self.assertFalse([])
        self.assertIs(False, False)
        self.assertIs([], False)

        self.assertFalse(False)
        self.assertFalse([])
        self.assertIs(False, False)
>       self.assertIs([], False)
E       AssertionError: [] is not False

Context: Trying to add teyit to astroid pre-commit in https://github.com/PyCQA/astroid/pull/1703

Any movement on this? With teyit being recommend in the Python 3.12 "What's New", it would be nice to see this addressed.