Instruction addrs, block labels & llvm disassembly

Adds more information and structure to the json inserted into the gtirb output.
This sacrifices some compactness for readability and convenience.
This also adds llvm-16 as a dependency of this package.
For each instruction we now have an address (just block_address + i * opcode_size),  the llvm disassembly, and the opcode itself.
For each block if a label can be found in any of the Module.symbols that refers to the block uuid then it is added.
The output now looks as below, so we will hold off on merging this until the basil gtirb loader is updated accordingly.
  "JgXUTTeoR9qjEjJwNU/5+w==": {
    "label": "main",
    "addr": 1812,
    "instructions": [
      {
        "assembly": "adrp x0, #131072",
        "addr": 1812,
        "opcode_le": "00 01 00 90",
        "opcode_be": "0x90000100",
        "semantics": [
          "Stmt_Assign(LExpr_Array(LExpr_Var(_R),Expr_LitInt(\"0\")),Expr_LitBits(\"0000000000000000000000000000000000000000000000100000000000000000\"))"
        ]
      },
      {
        "assembly": "add x0, x0, #28",
        "addr": 1816,
        "opcode_le": "00 70 00 91",
        "opcode_be": "0x91007000",
        "semantics": [
          "Stmt_Assign(LExpr_Array(LExpr_Var(_R),Expr_LitInt(\"0\")),Expr_TApply(add_bits.0,[(Expr_LitInt(\"64\"))],[(Expr_Array(Expr_Var(_R),Expr_LitInt(\"0\")));(Expr_LitBits(\"000000000000000000
0000000000000000000000000000000000000000011100\"))]))"
        ]
      },

I'm not sure any of this really serves much purpose. Readability of the internal JSON does not matter - no one needs to directly read the internal JSON, and we have debug-gts.py to create more human-readable outputs.
What does the LLVM disassembly look like? I don't see it in your example output. I also don't see the point in adding that and the opcode to the internal JSON for the semantics - those aren't going to be any use to BASIL so they will just take up space. If they are necessary for something else, it would make more sense to add those to debug-gts.py output.
The labels you add will in practice just be the function name for function entry blocks, so adding it to the internal semantics representation doesn't really serve much purpose when we already have access to that information.
We can already derive the address of blocks and instructions from the GTIRB data structures, so there is not much benefit to duplicating that information. It would be useful to have the addresses of instructions displayed in debug-gts.py though (the addresses of blocks are already displayed).
It would be easier to add support for changes like this to BASIL after the changes have been merged in - it is not necessary to wait for BASIL to be updated.

I think there is benefit to having a readable/debuggable format in the internal json.

What does the LLVM disassembly look like? I don't see it in your example output

This line is the LLVM disassembly
        "assembly": "adrp x0, #131072",

What is that benefit supposed to be? As I said, no one needs to directly read the internal JSON. The debug-gts.py output already contains most of this information, and would be a more suitable location for the rest of this.

As I see it, the goal of this PR is to consolidate the gtirb processing into one tool. debug-gts.py was a bit of a quick-fix solution to the unreadable gtirb problem.
Regarding space, increasing the gtirb size could lead to a faster increase in the git repository size. But I think a better solution here is to (eventually) move the gtirb files outside of git. Is this done for reproducibility of the results (i.e. avoiding compiler and ddisasm differences)? If so, this might be solvable by making the compiler->ddisasm pipeline deterministsic. Otherwise, the binary files could also be stored elsewhere with less space constraints.
One more advantage of Ocaml is we can use Aslp's pp_stmt method to obtain pretty-printed semantics.  This can provide slightly nicer output such as, for adds x1, x2, x3,
constant bits ( 64 ) Cse0__5 = add_bits.0 {{ 64 }} ( __array _R [ 2 ],__array _R [ 3 ] ) ;
PSTATE . V = not_bits.0 {{ 1 }} ( cvt_bool_bv.0 {{  }} ( eq_bits.0 {{ 65 }} ( SignExtend.0 {{ 64,65 }} ( Cse0__5,65 ),add_bits.0 {{ 65 }} ( SignExtend.0 {{ 64,65 }} ( __array _R [ 2 ],65 ),SignExtend.0 {{ 64,65 }} ( __array _R [ 3 ],65 ) ) ) ) ) ;
PSTATE . C = not_bits.0 {{ 1 }} ( cvt_bool_bv.0 {{  }} ( eq_bits.0 {{ 65 }} ( ZeroExtend.0 {{ 64,65 }} ( Cse0__5,65 ),add_bits.0 {{ 65 }} ( ZeroExtend.0 {{ 64,65 }} ( __array _R [ 2 ],65 ),ZeroExtend.0 {{ 64,65 }} ( __array _R [ 3 ],65 ) ) ) ) ) ;
PSTATE . Z = cvt_bool_bv.0 {{  }} ( eq_bits.0 {{ 64 }} ( Cse0__5,'0000000000000000000000000000000000000000000000000000000000000000' ) ) ;
PSTATE . N = Cse0__5 [ 63 +: 1 ] ;
__array _R [ 1 ] = Cse0__5 ;

This is not trivial to replicate in other languages.

The .gtirb and executable files are not included in the BASIL repo, but the .gts files are. Reproducibility of the results is necessary - we want to be testing BASIL for specific .gts files, not testing the entire pipeline all at once. Making the pipeline deterministic and only storing the test source files is not a solution to this, because changes to the lifting/disassembly pipeline would then propagate to BASIL and it would be more difficult to identify the source of issues. It would also significantly slow the execution of tests.
Storing all this information directly in the .gts does nothing for convenience, as it will still be necessary to run a script to extract the json from the .gts file in order to actually read it, meaning we end up in exactly the same place except with extra redundancy.
Since the .json files are directly derivable from the .gts at present, it would be possible to not store the .json files and only create them locally (from the .gts files which are in the repo) in order to save space.
There is no point to adding further information to the .gts files unless it is necessary for BASIL, or not directly derivable from the information that is already there.

Well, the point of making the compile/ddisasm pipeline reproducible is to also pin the pipeline, thus avoiding changes, and producing byte-for-byte identical gts files from only the c source files - addressing the need for reproducible results. However, this approach is looking like a lot of work and might not be practical.
My second point was that storing binary files (of any kind) in git can quickly bloat the repository size. At the moment, the .gts files are 57MB and it will increase by this much every time the files are updated. If size is a concern, it might be a good idea to avoid committing .gts files at all? The reproducible pipeline is only one such solution for this.
As for this PR, I would like to see the pretty-printed semantics included but I am otherwise neutral.

We can't avoid committing the .gts files at present, and ultimately the reproducible pipeline is a separate issue to the question of what should be contained within the .gts files right now. I don't have a problem if you want to pursue a stable, reproducible pipeline, but we also aren't at a stage where the pipeline is stable.
I'm not necessarily opposed to including the pretty-printed semantics (though they aren't in this PR), they're something that may not be directly derivable from what's already there. I suppose it may be possible to replace debug-gts.py with something written in OCaml that serves the same purpose and can make use of the ASLp pretty printer but that's probably a lot of hassle - maybe worth pursuing though?


Test jsonrpc client

[Current coverage][cc-pull] is 81.70%

Merging [#46][cc-pull] into [master][cc-base-branch] will increase coverage by 6.78%

File ...ces/daemonservice.py was modified. more

Misses -20
Partials 0
Hits +20

@@             master        #46   diff @@
==========================================
  Files             7          7
  Lines           319        317     -2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            239        259    +20
+ Misses           80         58    -22
  Partials          0          0

Powered by Codecov. Last updated by [94aadfb...3fce189][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ascribe/transactions/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/ascribe/transactions/compare/94aadfb456d8495ac6a1517595f623a3e6e6953e...3fce1892fb548aeaa3fca6d090a0abc604b05dc8
[cc-pull]: https://codecov.io/gh/ascribe/transactions/pull/46?src=pr


docs(ExampleTodoList.md): Rename todo(s) to todo(s)Reducer

Because of too many todos in town.

This example is incorrect. Now it uses todosReducer key in state which is probably not the desired effect. You probably want to change combineReducers call to accept todos: todosReducer instead of using the same name shortcut notation.
That said we use this convention (reducer named after the state field) all over the docs. We find it good enough, and changing it in a single particular case doesn't seem to help much. Therefore I'm closing.
Thanks for contributing!

Oh yes, forgot that -- you are totally right!
I felt, it would really help a newcomer to have names underlying the nature of the entities they represent.
I've thought that was the only place in that example where reducers are defined, but you are certainly right in that names should be consistent within the guide.


[gh-commits] Show Project and Task commits

https://trello.com/c/igQQQKBm
Instructions for local testing

Run migrations (./derrick migrate or python manage.py migrate)
Switch to new GitHub app:

Start your local dev server.
Go to http://localhost:8080/admin/socialaccount/socialapp/
Go to the “GitHub” app.
Change “Client id” and “Secret key” to match the values on “Client ID” and “Client secret” here: https://github.com/organizations/oddbird/settings/apps/metashare-dev
Click save.

Logout and log back in to the app.
Run management command to populate commit lists for existing tasks (./derrick manage resync_all_gh_commit_data or python manage.py resync_all_gh_commit_data)

For any tasks where you've already captured changes, you should now see the list of commits. If you don't have any captured changes locally, continue to step 5:

Create a new scratch org and capture changes:

Create Dev scratch org.
Click "View Org" to open the org.
Click the "Object Manager" tab.
Click "Contact"
Click "Fields & Relationships" on the left.
Click the "New" button.
Choose "Text" and click the "Next" button.
Enter a Field Label (e.g. "Favorite Color") and Length. Click the "Next" button.
Deselect all profiles in the Visible column except for System Administrator (not required, but it'll make for less noise in the changes). Click the "Next" button.
Deselect all page layouts except for "Contact Layout" (not required). Click the "Save" button.
Return to MetaShare and click "check again". It should show 3 uncaptured changes.
Click the Capture Task Changes button.
Select the field and layout but not the profile. Add a commit message and click the button to capture.

Run management command to populate commit lists again (./derrick manage resync_all_gh_commit_data or python manage.py resync_all_gh_commit_data)

You should now see the new commit.

 I want to view the git history for changes on a specific task branch.

Todo:

Only refetch all histories when there's a force push.
Take commits from commits key and put them on correct history in other cases.

@jgerigmeyer or @duggiemitchell, I think that this branch is ready for client-side work. It should be storing and showing commits accurately, I believe.

 Switch from GitHub oAuth app to GitHub App.

@jgerigmeyer or @duggiemitchell I've just added provisional frontend stuff to this, I'll add tests and types to it soon and then pass it off for styling.

@stacyk or @mirisuzanne I think this is ready for styling.

@wlonk I'm not sure how this is handling the case of a commit from a task branch being merged back into the project. At that point the commit should be removed from the task commits list, but I don't see that check happening anywhere. (Basically, any commit to a project should be removed from any child task commits list.)

I wasn't clear on what behavior we'd prefer there. There's an argument for leaving them in for historical info. Perhaps GitHub does that better though? I'll remove them on merge.

@wlonk I think we would like to see the list of commits since the task was started, even after it has been merged.

@stacyk This is ready for style cleanup. The easiest way to test is to edit a Task via the admin and manually enter the following (or similar) in the new commits field:
[
  {
    "id": "bee3758e221b5f4314c3e1c62abd1463bc9abe26",
    "url": "https://github.com/oddbird/MetaShare-Test/commit/bee3758e221b5f4314c3e1c62abd1463bc9abe26",
    "author": {
      "name": "jgerigmeyer",
      "email"<EMAIL_ADDRESS>      "username": "jgerigmeyer",
      "avatar_url": "https://avatars1.githubusercontent.com/u/552316?v=4"
    },
    "message": "Add CustomField for Contact.Favorite_Color.",
    "timestamp": "2019-11-06T20:28:15Z"
  },
  {
    "id": "bee3758e221b5sha",
    "url": "https://github.com/oddbird/MetaShare-Test/commit/bee3758e221b5f4314c3e1c62abd1463bc9abe26",
    "author": {
      "name": "Sondra",
      "email"<EMAIL_ADDRESS>      "username": "sondra"
    },
    "message": "Really Really Really Really Really Really Really Really Really Long\n\nMerge pull request #108 from oddbird/upgrade-py-deps\n\n📦 Update Python dependencies",
    "timestamp": "2019-10-06T20:28:15Z"
  }
]

@davisagli we should talk about that when you're free, as there are complications if we ever need to re-sync with GitHub.

@davisagli @mirisuzanne This is ready for review. Up to you each if you want to take the time to test functionally (I just did, and am happy to demo on Thursday) -- but it'd be great if you have a minute to look at the code and sign off in general?

@jgerigmeyer I'll try to take a look tomorrow. I'll be traveling on Thursday so won't make it to our normal weekly meeting.

@davisagli I'd appreciate another look if you're able. Then we can, I hope, merge this!


Suggestion for logging

I propose that out-of-the-box, all messages are logged like this:

Command payloads at DEBUG
User-friendly events at INFO
Event payloads at DEBUG
Query payloads at TRACE
Query
return values at TRACE

I think that would be in-line with "convention over configuration".

I think a well placed LoggingInterceptor, potentially adjusted to chance logging levels, covers this point already.

(c) @smcvb https://github.com/AxonFramework/extension-tracing/issues/15
Here is how I'm doing it here:
@Bean
fun eventLogger(tracer: Tracer): MessageDispatchInterceptor<EventMessage<*>> {
    return MessageDispatchInterceptor {
        BiFunction { _, event ->
            try {
                val description = (event.payload as Describable).description()
                log.info("[${tracer.id()}]: $description")
                if (log.isDebugEnabled) {
                    log.debug("[${tracer.id()}]: ${event.payload}")
                }
            } catch (e: ClassCastException) {
                log.error("[${tracer.id()}]: ${event.name()} " +
                        "does not implement ${Describable::class.simpleName}")
                log.info("[${tracer.id()}]: ${event.payload}")
            }
            event
        }
    }
}

@Bean
fun commandLogger(tracer: Tracer): MessageDispatchInterceptor<CommandMessage<*>> {
    return MessageDispatchInterceptor {
        BiFunction { _, command ->
            if (log.isDebugEnabled) {
                log.debug("[${tracer.id()}]: ${command.payload}")
            }
            command
        }
    }
}

@Bean
fun queryLogger(tracer: Tracer): MessageDispatchInterceptor<QueryMessage<*, *>> {
    return MessageDispatchInterceptor {
        BiFunction { _, query ->
            if (log.isTraceEnabled) {
                val payload = query.payload.toString()
                log.trace("[${tracer.id()}]: $payload")
            }
            query
        }
    }
}

@Bean
fun queryLoggerReturnValue(tracer: Tracer): MessageHandlerInterceptor<QueryMessage<*, *>> {
    return MessageHandlerInterceptor { unitOfWork, chain ->
        if (!log.isTraceEnabled) {
            return@MessageHandlerInterceptor chain.proceed()
        }
        val span = tracer.activeSpan()!!
        val traceId = span.context().toTraceId()
        val logAction: (Any?) -> Unit = {
            //fixme sometimes we can't see payload in the ui, maybe span is finished earlier then the future?
            span.setTag("axon.return.message.payload", it.toString())
            log.trace("[$traceId]: ${unitOfWork.message.payloadType.simpleName} returned: $it")
        }
        val returnValue: Any? = chain.proceed()
        if (returnValue == null) {
            logAction(null)
            return@MessageHandlerInterceptor returnValue
        }
        if (returnValue is CompletableFuture<*>) {
            returnValue.thenAccept(logAction)
        } else {
            logAction(returnValue)
        }
        return@MessageHandlerInterceptor returnValue
    }
}

What's your feel with enhancing the LoggingInterceptor to specify these levels per type of message, making it configurable through a builder to provide more flexibility, and to configure this interceptor by default, @Sam-Kruglov?

Sorry for the late response.
I see, so you want to have a single big MessageHandlerInterceptor with a bunch of instanceOf to see what type of message it is and to be able to configure the logging levels of each thing I mentioned here. I see no problem with that, we would only need to make sure to check logger.is[Debug/Trace/Info]Enabled somehow to avoid calling toString() and other expensive methods for no reason.

Moving issue to release 4.8.0 in favor of time we need to spent on releasing 4.7.0

We do not envision having sufficient time to work on this before our intended release of 4.8.0.
Added, we aim to direct our attention to the following major release.
Due to this, it is unclear at this stage when the issue will be resolved.


[Kubernetes] Scheduled Jobs

Closes #6323
What's Changed

[x] Overriden NautobotDataBaseScheduler.apply_async method to distinguish between Celery and Kubernetes Jobs
[x] Added celery-beat-deployment.yaml
[x] Restored docker-compose.min.yaml  in case that re-generations of Kubernetes deployment files are needed in the future

Screenshots

Run kubectl apply -f development/kubernetes/celery-beat-deployment.yaml

See the Kubernetes pod setup

Run kubectl exec --stdin --tty nautobot-679bdc765-snfps -- /bin/bash  and then nautobot-server nbshell to create a Scheduled Job in nbshell

See that a Kubernetes Job and Kubernetes Job Pod is created

See that a new Job Result with the status SUCCESS is created.

TODO

[x] Explanation of Change(s)
[x] Added change log fragment(s) (for more information see the documentation)
[x] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example App Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

unittest failure is #6509. I'm going to pick that one up and look into it.

Can you compare the resulting JobResult from a k8s scheduled job versus a Celery scheduled job to make sure they're both fully/correctly populated?

Here is a comparison of the fields populated. Kubernetes is on the left and Celery is on the right. The main differences lie within the celery_kwargs field. I wonder if it is acceptable since we are not using celery workers to execute the job anyway.

Regarding the difference in celery_kwargs, do the nautobot_job_profile and time-limit parameters get set appropriately for the executing job in some other fashion?
Can we fix up the difference in name (Job.name versus Job.class_path)?


[Enhancement] Method needlessly defines parameter with concrete classes[EventMeshUtil]

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request

located at:
eventmesh-runtime/src/main/java/org/apache/eventmesh/runtime/util/EventMeshUtil.java line 247
analysis and explanation:
This method uses concrete classes for parameters when only methods defined in an implemented interface or superclass are used. Consider increasing the abstraction of the interface to make low impact changes easier to accomplish in the future.
Describe the solution you'd like
Use Collection instead of List.
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Does this problem still need to be solved? I want to contribute to it.

@tooo-bad I recommend you to submit PRs one by one to get familiar with the collaboration of community.


Update to v5

Merging from EmergingTechnologyAdvisors/node-serialport to update to v5
The only commit that is mine is https://github.com/ms-iot/node-serialport/commit/53c29918accf96ab5f997bdbbe43c5c5ab6a2805

@bfjelds could you please CR when you get a chance. It's a merge so there's just my commit (	53c2991) to  look at.


An answer for handling categorical variables

Provided an answer for "what do we do with categorical variables"
Listed popular encoding techniques

Thank you for your contribution!


Hotfix 1.2.1 - Forgot an important piece of the puzzle...

If doing builds locally, or on a feature / bugfix branch in a CI job, we need to skip the actual 'deploy' step. The primary method of doing this is to set maven.deploy.skip=true
Refactored (generalized) configuration scanning in the build extension, which is what's responsible for removing plugins we don't want to run in 'master'.

The assumption is that we only ever want to run our own plugins in the master branch. This should probably be configurable, but I'm waiting for a 'valid' use case to emerge before I create an issue for that.

lgtm


DG Review by the tutor

Overall you guys have done a good job. Some of the comments I have added for a figure is applicable to multiple figures. So it would be great if all of you in the team go through the comments and improve your own sections. Otherwise Kudos to the entire team. Keep up the good work

[Figure 2] What is happening here? Why do you need two parsers for each command and parent creates child?

[Figure 4] Since the overall goal in the design section is to convey the design, you do not need to always have class diagrams to convey the low-level details. It may make the diagram complicate and difficult to understand. Instead, you can still have architecture-like diagram to show the inter-connection of sub-componenents of a component and for the selected sub-component you can elaborate more with a class diagram. You dont need to stick to the exact format of AB3 DG especially for the decisions on UML diagram type you want

[Figure 4 & 5] Why there are multiple formattings used to draw the diagram

[Figure 9] Multiple arrows in a flow do not adhere to the standard UML. You may avoid it.

[Figure 9 & 13] Does your system show an error message during else path. Then you may have it before reaching the merge node

[Figure 11] So finally doesnt the system show the list of modules?

[Figure 13] Why do you need the activities to be repeated. You may have a merge node since the rest of the flow is same for both if and else paths

[Figure 15] When the user execute the add lesson command, at the end, the lesson/lesson list should be saved. Why does the diagram says ModManager is saved?

[Figure 17] Doesnt the system shows the list of classes to the user?

[Figure 19] Same issue here. Doesn't the system shows the list of results?

[Figure 26] Why is there an empty object and lifeline?

[Figure 27] Unless it is very important to highlight, you do not need to give exact wording translation of your if condition, which will be diffifult for the user to understand. Instead you can give a generic explanation.

[Appendix B] You may change the action to be singular since the you can only one module, task etc at a time. Otherwise it will give an idea, you system is supposed to allow adding list of module, task etc.

[Appendix B] What do you mean by this

[Appendix C] If the system still displays an empty list, then this extension will not be valid and it comes under list all modules steps

[Appendix D] What do you mean by noticeable sluggishness? Be specific

[ Appendix D] These are constraints of the project which you can be conveyed as part of your value proposition. It is not an NRF. NRF should depict the functionalities with constraints under which the system will be implemented

[Appendix D] It would be better if you can have your app-specific NRF

Thanks a lot for your feedback!
Closed for v1.4.


"Add Regions While Sculpting" Not work with the height brush

Terrain3D version
master
System information
godot4.3
Is the issue reproducable in the demo?
Yes
Issue description
https://github.com/user-attachments/assets/3f484cc0-98c6-4e5b-9893-ccb74c75393e
Logs
No response

Thanks, fixed in d606879b08b52304ebb7225f2a6b47349aeb78a5


Fix window exiting with no message to user if _create_window fails

When running godot 4.3 on an old Windows desktop with an ATI Radeon 3000 GPU and forcing it to run with lib angle, it would briefly show a black window and then exit with no error message to the user.   With this pull request the user will at least get an error message if _create_window fails

Thank you!


websocket server not response

websocket server not response ,details describe in Steps to Reproduce, Any suggestions are welcome!
Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

I define a class  named websocketServer extended from WebSocketServer.
in websocketServer I overide onOpen method as belows:
@Override
public void onOpen(WebSocket conn, ClientHandshake clientHandshake) {
sleep(4100);// 4.1seconds
conn.close();
}
2. I new websocketServer(36669),and call start method;
3.In client,I send a websocket connection to server.
4.About 20% probability can not connect if sleep 4.1 seconds in onOpen, if sleep 200 seconds in onOpen， the next client 100% probability can not connect .
5.webserversocket version is java-websocket-1.3.7.jar
Debug log (for bugs)

In server shell console,I find message as below:
shell@N10:/ $ netstat -tunlp | grep 36669
tcp6       2      0 :::36669               :::*                   LISTEN
tcp6     533      0 ::ffff:<IP_ADDRESS>:36669 ::ffff:<IP_ADDRESS>:50736 CLOSE_WAIT
tcp6       7      0 ::ffff:<IP_ADDRESS>:36669 ::ffff:<IP_ADDRESS>:44200 CLOSE_WAIT
tcp6     533      0 ::ffff:<IP_ADDRESS>:36669 ::ffff:<IP_ADDRESS>:51189 CLOSE_WAIT
tcp6       7      0 ::ffff:<IP_ADDRESS>:36669 ::ffff:<IP_ADDRESS>:43207 CLOSE_WAIT
tcp6       7      0 ::ffff:<IP_ADDRESS>:36669 ::ffff:<IP_ADDRESS>:43106 CLOSE_WAIT
Context

Your Environment

Version used:
Java version:
Operating System and version:Android 5.1.1
Endpoint Name and version:
Link to your project:

Hello @xmulxs,
Please use the latest version 1.3.7!
Greetings
marci4

Hi,marci4,
I test the issue with 1.3.7, and all is ok. but I  find a function named getMacFromIp may blocks callback onOpen as below:
@Override
public void onOpen(WebSocket conn, ClientHandshake clientHandshake) {
sleep(4100);// 4.1seconds
getMacFromIp(szIp);
conn.close();
}
When testing with 1.3.7,I make function getmacFromIp in "Not block". So The testing may not explain any problem.
I think when getMacFromIp  blocks, It  cause the CLOSE_WAIT phenomenon. What I want to kown is  whether onOpen function blocks cause connect failure?

Hi,marci4,I think I find the problem, The  reason is " onOpen callback block for a long time cause the connection failure". When I sleep for 100 seconds in onOpen the next client indeed can't connect to server.

version 1.3.7 has the same problem, if sleep 200 seconds in onOpen， the next client 100% probability can not connect .

Is there any reason why you wanna sleep the connection?
Maybe use a separate timer for this?
Greetings
marci4

Hi,maric4 Thank you for your answer， Now I just new a thread in onOpen function  for doing blocking things  instead of  directly sleeping in onOpen that may block onOpen.


Collaboration With PteroApiWraooer

I have recently made an API wrapper for pterodactyl called- 'pteroApiWrapper' for nodejs, if you agree we can collaborate and make the best API wrapper ever of pterodactyl panel in nodeJS, contact me on discord - Arnav G. Or contact me on email-<EMAIL_ADDRESS>or just reply to this issue

Hello, let's discuss that in discord. This is my dev-server https://discord.gg/A2SDjxQshJ


File matching debug

Provide a command to output a list of files matched for a hook.
$ goose matches some-command
file.txt

Fixed in #46.


fix: remove entities dependency

What does this PR change?
Removes unnecessary unity entities dependency.
Before:

After:

How to test the changes?

Ensure the landscape works as normal in genesis and worlds
Performance is the same or better

Our Code Review Standards
https://github.com/decentraland/unity-renderer/blob/master/docs/code-review-standards.md

Member

I believe Bounds still represents an AABB:
https://docs.unity3d.com/ScriptReference/Bounds.html#:~:text=An axis-aligned bounding box,bounds%2C Mesh.


Convert the CircleCI workflow to a GitHub Actions workflow

Summary
This pull request converts the CircleCI workflows to GitHub actions workflows. Github Actions Importer was used to convert the workflows initially, then I edited them manually to correct errors in translation.
Issues

facebook/home-robot/build -> home_robot

RuntimeError: Format missing, but need one (identified source as text as no file with that name was found).

Full Error

  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'error'
  error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [10 lines of output]
/tmp/pip-install-qrj2sd_2/trimesh_7e72dfdab9294065833084684cd6df2f/setup.py:10: DeprecationWarning: Due to possible ambiguity, 'convert()' is deprecated and will be removed in pypandoc 1.8. Use 'convert_file()'  or 'convert_text()'.
long_description = pypandoc.convert('README.md', 'rst')
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "/tmp/pip-install-qrj2sd_2/trimesh_7e72dfdab9294065833084684cd6df2f/setup.py", line 10, in
long_description = pypandoc.convert('README.md', 'rst')
File "/home/runner/.local/lib/python3.10/site-packages/pypandoc/init.py", line 70, in convert
raise RuntimeError("Format missing, but need one (identified source as text as no "
RuntimeError: Format missing, but need one (identified source as text as no file with that name was found).
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

facebook/home-robot/build -> home_robot_sim

[Errno 13] Permission denied: '/usr/local/lib/python3.10/dist-packages/test-easy-install-3396.write-test'

Full Error

× python setup.py develop did not run successfully.
│ exit code: 1
╰─> [32 lines of output]
    running develop
    /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:158: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
      warnings.warn(
    WARNING: The user site-packages directory is disabled.
    /usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
      warnings.warn(
    error: can't create or remove files in install directory
The following error occurred while trying to add or remove files in the
installation directory:

    [Errno 13] Permission denied: '/usr/local/lib/python3.10/dist-packages/test-easy-install-3396.write-test'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /usr/local/lib/python3.10/dist-packages/

Perhaps your account does not have write access to this directory?  If the
installation directory is a system-owned directory, you may need to sign in
as the administrator or "root" account.  If you do not have administrative
access to this machine, you may wish to choose a different installation
directory, preferably one that is listed in your PYTHONPATH environment
variable.

For information on other options, you may wish to consult the
documentation at:

  https://setuptools.pypa.io/en/latest/deprecated/easy_install.html

Please make the appropriate changes for your system and try again.

[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.

How did you test this change?
I tested these changes in a forked repo.
https://fburl.com/workplace/f6mz6tmw

Hi @jk0 , it seems like the tests are failing on the forked repo. Can you please check why?


fix: Monaco editor is white in dark theme

Description
Changes proposed in this pull request:

fixed theme names in Monaco Editor

Related issue(s)

/retest

/retest

/retest


Ascii three dot (⋮) are not inline with other vertical lines.

Sorry if duplicate. I mean this:

Is it just my font? I'm using vscode terminal.

Unfortunately, this is a font issue so there's not much I can do within Ariadne to fix this.
With Iosevka Fixed Slab, I see the following:

It doesn't work with my jupyter's font either, this time it is on the left:

And the rest of characters are ok in both fonts, so maybe this only works by coincidence on your font? If it is not and it works in other fonts as well, feel free to close this.

If you can find a similar Unicode character that behaves correctly, I'm happy to look into substituting it. Alternatively, there's the ASCII-only diagnostic rendering mode which might be more generally portable.

⸽ is working for me, though it is too close to the up and down lines. Ascii colon : is also ok. Strangely, every other character in this class changes the spaces width before that character in my font.

I think the ASCII-only mode uses :, so hopefully this behaves a bit better. That said, removing the box characters tool in favour of ASCII is probably not a good long-term solution. It's frustrating that fonts have such inconsistent behaviour...
If you know of / can think of a better solution to this I'm happy to have a go at implementing it.

i would suggest using characters from the box-drawing character class for this purpose, as fonts typically require those characters to line up perfectly, in this case, i would suggest ┆ (U+2506, light triple-dash vertical), or its siblings, ┊ and ╎ (quadruple and double-dash vertical).

This is a good idea. I've made this change in 93f959c.


Not mapping nested array in response

Trying to map a response like
	"customer": {
		"first_name": "John",
		"last_name": "Doe",
		....
	},
	"orders": [],
	"devices": [{
		"validated": false,
		"device_id": "XXXX-XXXX-XXXX",
		"device_type": null
	}],
	"id": "54d1fe8650747b05339f2f81",
	"participants": [{
		....
	}],
	"primary_email": null,
	"emails": [{
		"validated": false,
		"primary": 0,
		"email"<EMAIL_ADDRESS>	}]
}```

But for some reason RestKit fails to map the 'emails' part.

* Starting mapping operation...
* Mapping one to many relationship value at keyPath 'emails' to 'emails'
* Starting mapping operation...
* Finished mapping operation successfully...
* Destination object
accountId : 54d1fe8650747b05339f2f81
emails : (null)
devices : (null)
participants : (null)
orders : (null) rejected attribute value (
    "\naddress<EMAIL_ADDRESS>: 0\nprimary : 0"
) for keyPath emails. Skipping...

Later on devices for example gets mapped correctly. Weird thing is that an earlier request does map the email part

```{
	....
	"emails": [{
		"validated": false,
		"validation_token": "f735dbe9098949341eddfef56157a20471254dd6",
		"primary": 0,
		"email"<EMAIL_ADDRESS>	}]
}```

Mapping all looks fine

Asked to map source object {
    customer =     {
        "first_name" = fawefawef;
        "last_name" = wefa;
       ....
    };
    devices =     (
                {
            "device_id" = "XXXX-XXXX-XXXX";
            "device_type" = "<null>";
            validated = 0;
        }
    );
    emails =     (
                {
            email =<EMAIL_ADDRESS>            primary = 0;
            validated = 0;
        }
    );
    id = 54d1fe8650747b05339f2f81;
    participants =     (
                {
            ....
        }
    );
    "primary_email" = "<null>";
} with mapping <RKObjectMapping:0x7fabca49e400 objectClass=XXAccount propertyMappings=(
    "<RKRelationshipMapping: 0x7fabca415ff0 emails => emails>",
    "<RKRelationshipMapping: 0x7fabca0c3410 devices => devices>",
    "<RKRelationshipMapping: 0x7fabca0d4630 participants => participants>",
    "<RKRelationshipMapping: 0x7fabca4867e0 orders => orders>",
    "<RKAttributeMapping: 0x7fabca4992b0 id => accountId>"
)>

Why does RestKit log this? A don't really know what it means and can't find any documentation.

**rejected attribute value (
    "\naddress<EMAIL_ADDRESS>: 0\nprimary : 0"
) for keyPath emails. Skipping...**

Can you provide your mappings definition?

Le 4 févr. 2015 à 12:21, Mark Molina<EMAIL_ADDRESS><EMAIL_ADDRESS>a écrit :
Trying to map a response like
{
"customer": {
"first_name": "John",
"last_name": "Doe",
....
},
"orders": [],
"devices": [{
"validated": false,
"device_id": "XXXX-XXXX-XXXX",
"device_type": null
}],
"id": "54d1fe8650747b05339f2f81",
"participants": [{
....
}],
"primary_email": null,
"emails": [{
"validated": false,
"primary": 0,
"email"<EMAIL_ADDRESS><EMAIL_ADDRESS>}]
}
But for some reason RestKit fails to map the 'emails' part.
Starting mapping operation...
Mapping one to many relationship value at keyPath 'emails' to 'emails'
Starting mapping operation...
Finished mapping operation successfully...
Destination object
accountId : 54d1fe8650747b05339f2f81
emails : (null)
devices : (null)
participants : (null)
orders : (null) rejected attribute value (
"\naddress<EMAIL_ADDRESS><EMAIL_ADDRESS>: 0\nprimary : 0"
) for keyPath emails. Skipping...
Later on devices for example gets mapped correctly. Weird thing is that an earlier request does map the email part
{
....
"emails": [{
"validated": false,
"validation_token": "f735dbe9098949341eddfef56157a20471254dd6",
"primary": 0,
"email"<EMAIL_ADDRESS><EMAIL_ADDRESS>}]
}
Mapping all looks fine
Asked to map source object {
customer = {
"first_name" = fawefawef;
"last_name" = wefa;
....
};
devices = (
{
"device_id" = "XXXX-XXXX-XXXX";
"device_type" = "";
validated = 0;
}
);
emails = (
{
email =<EMAIL_ADDRESS><EMAIL_ADDRESS>primary = 0;
validated = 0;
}
);
id = 54d1fe8650747b05339f2f81;
participants = (
{
....
}
);
"primary_email" = "";
} with mapping " emails>",
" devices>",
" participants>",
" orders>",
" accountId>"
)>
Why does it RestKit log this? A don't really know what it means and can't find any documentation.
rejected attribute value (
"\naddress<EMAIL_ADDRESS><EMAIL_ADDRESS>: 0\nprimary : 0"
) for keyPath emails. Skipping...
—
Reply to this email directly or view it on GitHub https://github.com/RestKit/RestKit/issues/2151.

Well.. Tried to do that dynamically for all requests based on the model.
{
    RKObjectMapping *mapping = nil;

    mapping = [RKObjectMapping mappingForClass:class];

    if (mapping) {

        // Turn modelAttributes belonging to class into a NSMutableDictionary that RestKit can use
        NSMutableArray *modelAttributes = [class getModelAttributes];
        NSMutableDictionary *attributeDictionary = [NSMutableDictionary new];

        for (int n = 0; n < modelAttributes.count; n++) {

            TBModelAttribute *modelAttribute = modelAttributes[n];
            if(modelAttribute.callType==CallTypeResponse || modelAttribute.callType==CallTypeAll) {

                if (modelAttribute.usingModel==nil) {
                    // Not using a model, just return standard mapping
                    [attributeDictionary setValue:modelAttribute.classProperty forKey:modelAttribute.jsonKey];
                } else {
                    // We need relationship mapper
                    [mapping addPropertyMapping:[RKRelationshipMapping relationshipMappingFromKeyPath:modelAttribute.jsonKey
                                                                                toKeyPath:modelAttribute.classProperty
                                                                                withMapping:[self getResponseMappingForModel:modelAttribute.usingModel withObjectManager:objectManager]]];
                }
            }
        }

        [mapping addAttributeMappingsFromDictionary:attributeDictionary];
    }

    return mapping;
}```

Bit hard to understand but this used to work fine. Also when breaking it down and stepping through the mapping process everything looks fine as well.

I had a similar issue no longer than yesterday. You may have look here : http://stackoverflow.com/questions/28257259/restkit-0-24-mapping-using-addconnectionforrelationship/28295348?noredirect=1#comment44960947_28295348 http://stackoverflow.com/questions/28257259/restkit-0-24-mapping-using-addconnectionforrelationship/28295348?noredirect=1#comment44960947_28295348
Because since your data mapping is dynamic and no insight on the getModelAttribute it’s difficult to provide more support

Le 4 févr. 2015 à 12:28, Mark Molina<EMAIL_ADDRESS><EMAIL_ADDRESS>a écrit :
Well.. Tried to do that dynamically for all requests based on the model.
{
RKObjectMapping *mapping = nil;

mapping = [RKObjectMapping mappingForClass:class];

if (mapping) {

    // Turn modelAttributes belonging to class into a NSMutableDictionary that RestKit can use
    NSMutableArray *modelAttributes = [class getModelAttributes];
    NSMutableDictionary *attributeDictionary = [NSMutableDictionary new];

    for (int n = 0; n < modelAttributes.count; n++) {

        TBModelAttribute *modelAttribute = modelAttributes[n];
        if(modelAttribute.callType==CallTypeResponse || modelAttribute.callType==CallTypeAll) {

            if (modelAttribute.usingModel==nil) {
                // Not using a model, just return standard mapping
                [attributeDictionary setValue:modelAttribute.classProperty forKey:modelAttribute.jsonKey];
            } else {
                // We need relationship mapper
                [mapping addPropertyMapping:[RKRelationshipMapping relationshipMappingFromKeyPath:modelAttribute.jsonKey
                                                                                toKeyPath:modelAttribute.classProperty
                                                                                withMapping:[self getResponseMappingForModel:modelAttribute.usingModel withObjectManager:objectManager]]];
            }
        }
    }

    [mapping addAttributeMappingsFromDictionary:attributeDictionary];
}

return mapping;
}```

Bit hard to understand but this used to work fine. Also when breaking it down and stepping through the mapping process everything looks fine as well.

—
Reply to this email directly or view it on GitHub <https://github.com/RestKit/RestKit/issues/2151#issuecomment-72839602>.

Thanks for the info. I will check your post. I'll also try to log as much info as I can on the mapping.

Apparently the mapping of the array goes fine. Looks like it's going wrong when setting the relation

Found transformable value at keyPath 'email'. Transforming from class '__NSCFString' to 'NSString'
Mapping attribute value keyPath 'email' to 'address'
Mapped attribute value from keyPath 'email' to 'address'. Value<EMAIL_ADDRESS>Found transformable value at keyPath 'validated'. Transforming from class '__NSCFBoolean' to 'NSNumber'
Mapping attribute value keyPath 'validated' to 'validated'
Mapped attribute value from keyPath 'validated' to 'validated'. Value: 0
Found transformable value at keyPath 'primary'. Transforming from class '__NSCFNumber' to 'NSNumber'
Mapping attribute value keyPath 'primary' to 'primary'
Mapped attribute value from keyPath 'primary' to 'primary'. Value: 0
Finished mapping operation successfully...
Found transformable value at keyPath 'emails'. Transforming from class '__NSArrayM' to 'NSArray'
Destination object
accountId : 54d22edf50747b05339f2fa2
emails : (null)
devices : (null)
participants : (null)
orders : (null) rejected attribute value (
"\naddress<EMAIL_ADDRESS>: 0\nprimary : 0"
) for keyPath emails. Skipping...

"rejected attribute value" means that the validateValue:forKeyPath:error: implementation returned NO.   If you have custom validation routines in there, I would check those implementations.  You could set performsKeyValueValidation to NO on the mapping to avoid that check, but presumably there is a reason it is returning NO.  RestKit should be logging the validation error immediately after the log above, which should give further info.

Well the there's really no other error in there. Before the skipping error Restkit just does it's normal mapping and that all looks fine. I compared it with the mapping of "devices" in our  request since it's the same structure.
Added the log from that request here
http://pastebin.com/rXNgXDyb

RestKit is handling it correctly.  -validateValue: is returning NO, therefore the assignment should be skipped.  The implementation of -validateValue: is beyond RestKit's control.
It looks like RKLogValidationError() is called with the underlying error, which should give you more information on the problem.  However if CoreData is defined, and the error is not of the NSCocoaErrorDomain, then nothing will get logged.  That probably is a bug which should be fixed.  You could modify that function in RestKit to always log the error (such as what the non-CoreData situation does), and run with that -- it should give you better information.  That part should probably be a RestKit fix -- just log out the error if it's not a NSCocoaErrorDomain as expected; right now it's silent and that is critical information.  Custom implementations can always return errors with custom domains.

Yep... Custom implementations -_-


BUG: test_partial_correctness()のテストが通っていない

概要
commit id: 93a43e4

Conclusion
The main dataset of this project has become PrfNdim. So, this issue is not important.


3++ Publishing (Onto server)

Publishing appropriate data to the Onto Server via the orchestration tool.

#243

21/12/21 - we need to understand how to test this without updating the Term Server. This will need to be agreed with Maxine.

Meeting already held with Likin and James to make sure that we don't cause live issues with duplicate items.
Awaiting sample files from James and Likin before giving go ahead for any test loading.

Initial testing activities started 17/06/22

@maxChappell - I'm just reviewing the GitHub board. Is this issue something you and Likin will test, or we will be involved? I just want to check if it is in the correct place.

18/8/22 - @maxChappell will speak to Likin about this as we need to know if this is in the correct place on the GitHub board.

If Maxine has a request, can she raise with me and not Likin please.
On Fri, 19 Aug 2022, 10:07 AngelaFaulding, @.***> wrote:

18/8/22 - @maxChappell https://github.com/maxChappell will speak to
Likin about this as we need to know if this is in the correct place on the
GitHub board.
—
Reply to this email directly, view it on GitHub
https://github.com/NHSDigital/DataDictionaryPublication/issues/305#issuecomment-1220437767,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANX7SHE5SGUZANVO2XF6VK3VZ5FEPANCNFSM5KN32UVA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

Testing not completed. Will need to be tested as and when project resumes.

Now to be done post migration.


Use /tp @p in Command Block NOT /tp @s. Please Document

[Enter feedback here]
/tp command is very useful. /tp @s in Command Block won't work. /tp @p does.  Please document this well

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

ID: 308afc9e-0653-f1eb-6637-968d0d58b6a0
Version Independent ID: 9406eeab-b4bc-e7ad-3bc3-5810e4a4746b
Content: Introduction to Commands
Content Source: creator/Documents/CommandsIntroduction.md
Product: gaming
GitHub Login: @docsbryce
Microsoft Alias: v-bbortree

Hi @teachingvalues - Good point! I added it to the '/tp' section of the Popular Commands Page: https://learn.microsoft.com/minecraft/creator/documents/commandspopularcommands


Add ehcache3 xml samples

This PR adds two samples for

Creating clustered cache using XML configuration
Exporting programmatic configuration to XML

@cljohnso Thanks for reviewing.
Regarding batch and shell scripts, they are copied from existing samples, so we need to modify scripts in all samples. I am thinking of creating another PR to fix scripts, wdyt?
I have pushed changes to fix other comments.

@cljohnso : let me know if something's missing; I have testing 3 clients scripts on Mac with the latest changes, included the TC TQL samples with 2 client paths.


Crit hack indicator brokey

Does not show anything correctly

Turn it off. The crit hack is not perfect and the bucket doesn't mean anything regarding if you can crit or not.


chef-client requires specifying default formatter output when redirecting to file

Description
chef-client requires specifying the default formatter output (-F doc) when redirecting stdout to a file.
According to the chef-client doc, -F doc is the default formatter output, but something happens when redirecting that requires it to be specified.
Chef Version
12.5.1
Platform Version
RHEL 6.8
Replication Case

Run chef-client > my_log.log. This will result in a totally empty file (0 bytes).

Run chef-client -F doc > my_log.log. This will result in output being redirected correctly. The file will contain what would've originally been printed to stdout.

Client Output
No output from chef-client. It correctly avoids stdout but isn't redirected correctly.
NOTE: CHEF CLIENT BUGS ONLY
This issue tracker is for the code contained within this repo -- chef-client, base knife functionality (not
plugins), chef-apply, chef-solo, chef-client -z, etc.

Server issues
ChefDK issues
Cookbook Issues (see the https://github.com/chef-cookbooks repos or search Supermarket or GitHub/Google)

As mentioned on IRC, this is intentional. The formatter system only activates by default if STDOUT is a TTY. Otherwise it should enable the logging system. It sounds like maybe you were having issues with the log level though?

@coderanger sorry about that, I posted this before we discussed in Slack.
Given that it's intentional, I was thinking that there might be room to improve the documentation on the formatter (-F) flag? All it says is: The output format: doc (default) or min. The documentation for -l does state: Default value: warn (when a terminal is available) or info (when a terminal is not available). but I wasn't able to make the connection between formatting being turned off and logging being turned on in the absence of TTY until I just started trying random stuff.

By the way, this still doesn't really explain why my file was totally empty. If > results in turning off formatting and turning on logging, and info is the default log level (according to the documentation for -l), then I should've gotten something in my file. As it is, it seems like once you use > you lose pretty much all defaults and get no output.

dup of at least:

https://github.com/chef/chef/issues/2514
https://tickets.opscode.com/browse/CHEF-4874
https://tickets.opscode.com/browse/CHEF-4316
https://tickets.opscode.com/browse/CHEF-5218

requires a major version bump to change.   it was missed in Chef 12.0.0 in Dec 2014.
this is why 2+ years between major releases is a horribly bad thing.
this will be fixed in April with Chef 13: https://github.com/chef/chef-rfc/pull/232

I was bitten by this as well when setting a push job with knife job start --capture, adding -F doc makes the output available to knife output --channel.


Gemfile.lock issues

bundle install did not install all gems.
on jekyll serve I got this error
WARN: Unresolved specs during Gem::Specification.reset:
jekyll-watch (~> 1.1)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
Configuration file: /Users/mike/Src/ThingStudio/documentation-theme-jekyll/_config.yml
Dependency Error: Yikes! It looks like you don't have kramdown or one of its dependencies installed. In order to use Jekyll as currently configured, you'll need to install this gem. The full error message from Ruby is: 'cannot load such file -- kramdown' If you run into trouble, you can find helpful resources at http://jekyllrb.com/help/!
I had to remove Gemfile.lock  and re-run bundle install to get it to work.

For anyone else who runs into a similar error, it may also related to this (original issue) and  this.
If you're using Github pages, update the gem and then find older versions of dependent gems being installed, it's probably due to the bug with bundler mentioned in those issues. I solved this yesterday by doing this hacky workaround in my Gemfile and then re-running bundle install:
`source "https://rubygems.org"
gem "rails"
gem 'github-pages', '105'     // specifying a version fixes this issue (for now)
gem 'jekyll'`

Thanks for the feedback. I'm not sure if this helped, but I just deleted Gemfile.lock, re-ran Bundle install (which creates a new Gemfile.lock), and updated the theme. Hopefully this might help avoid any outdated gems.

That's the first thing I did yesterday - I wish it would have worked for me! Glad it was an easy fix for you, though. Thanks, Tom.


Contents flicker in 2018.4.2 (and maybe other versions?)

Click around the window with preview contents populated and observe the flicker. Shown in gif when selecting preview steps.

If you click and hold on the Breadcrumbs, it shows the contents that flicker. I think that's the issue.
It appears to preview the first column as if you've pressed "Preview Steps". Notice it also does this if you click and hold on Preview Steps.


Facebook auth changed ? Protobuf

I think they changed from json to protobuf, any idea how to solve that ?

there are several ways to resolve this, one way is to decompile the tinder android app or ios whatever you fancy, and look for those fields and properly name them.
Another is just to guess the name of the fields and hopefully you label them right lol.

I have extracted all of the protobuf .proto files here: gitee.com/auf/tinder-grpc-exploration
I will put up the Python version in a bit.

I have extracted all of the protobuf .proto files here: gitee.com/auf/tinder-grpc-exploration
I will put up the Python version in a bit.

Hey @jimtje , what's the status on the protobuf auth? Have you figured out how to do it?

I have extracted all of the protobuf .proto files here: gitee.com/auf/tinder-grpc-exploration
I will put up the Python version in a bit.

Hey, how did you extracted the protobuf? I decompiled the apk with jadx and see the proto descriptors, looks like a lot of work to convert it to something more usable.
Thanks


Cue time remaining Feedbacks appear to be just under a second ahead

Cue time remaining Feedbacks appear to be just under a second ahead on the button display vs the qlab app and the variables page in companion. Might be a companion issue...
Companion 3.2.2 - Raspberry Pi
Qlab 5.3.8 - macOS Sonoma14.3 / Monterey 12.7.5
Thanks
Matt

Ah okay, I understand I’m using tenths, so basically not seeing the .9 of 1.9?
I’ll try turning that off.
Thanks
From: John Knight Jr @.>
Sent: Tuesday, May 21, 2024 6:10 PM
To: bitfocus/companion-module-figure53-qlab-advance @.>
Cc: Matchaow @.>; Author @.>
Subject: Re: [bitfocus/companion-module-figure53-qlab-advance] Cue time remaining Feedbacks appear to be just under a second ahead (Issue #127)
Have you tried the 'Use Tenths?' option?
Companion is not perfectly synchronized due to the communication delays and count-out is not rounded.
Without the 'Use Tenths?' option set, 1 second is poor resolution for a count-out.
For example, is the digit changing at exactly 2 seconds or 2.7, or 2.2?
A display of 1 second could actually be 1.9 seconds, so the counter was adjusted to compensate.
—
Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-figure53-qlab-advance/issues/127#issuecomment-2123076226 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BDIJO3RO4UIPCD66GTIIDZTZDN5YDAVCNFSM6AAAAABIBJG2Q6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRTGA3TMMRSGY .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/BDIJO3T5UJNYOYXMFHOBR4TZDN5YDA5CNFSM6AAAAABIBJG2Q6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT6ROJIE.gif Message ID: @.*** @.***> >

Tried without tenths which has made the display count just under a second behind now, so would prefer to be ahead!
From: John Knight Jr @.>
Sent: Tuesday, May 21, 2024 6:10 PM
To: bitfocus/companion-module-figure53-qlab-advance @.>
Cc: Matchaow @.>; Author @.>
Subject: Re: [bitfocus/companion-module-figure53-qlab-advance] Cue time remaining Feedbacks appear to be just under a second ahead (Issue #127)
Have you tried the 'Use Tenths?' option?
Companion is not perfectly synchronized due to the communication delays and count-out is not rounded.
Without the 'Use Tenths?' option set, 1 second is poor resolution for a count-out.
For example, is the digit changing at exactly 2 seconds or 2.7, or 2.2?
A display of 1 second could actually be 1.9 seconds, so the counter was adjusted to compensate.
—
Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-figure53-qlab-advance/issues/127#issuecomment-2123076226 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BDIJO3RO4UIPCD66GTIIDZTZDN5YDAVCNFSM6AAAAABIBJG2Q6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRTGA3TMMRSGY .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/BDIJO3T5UJNYOYXMFHOBR4TZDN5YDA5CNFSM6AAAAABIBJG2Q6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT6ROJIE.gif Message ID: @.*** @.***> >


Support for Openshift Origin v1.4.x

As promised in #51, this PR makes this cookbook compatible with the recently released Openshift Origin 1.4.x. I will be adding changeset (and editing the description of this PR) as I successfully deploy more components of the platform.
Note: I use the experimental openshift v1.4.1 packages from the buildlogs centos paas repository (see openshift/origin#12567).
To test, check the 'origin-1.4.x' branch of my Vagrant VM: https://github.com/PerfectMemory/origin-provision-bug-demo . or use the kitchen integration test of this project.
I have successfully deployed and tested so far:

[X] master/node deployment (in standalone and openshift_HA configuration)
[X] the hosted router addon (had to add missing router-certs secret in default project)
[X] the hosted docker-registry addon
[X] the cookbook's kitchen integration tests
[X] metric addon using my own cookbook (had to add 'view' role to hawkular SA in openshift-infra project and backported the fix to this PR)
[X] logging addon using my own cookbook (worked without modifications with v1.4.1 images)

Not in this PR but manually verified:

[X] integration test for this cookbook's "hosted metrics" feature #52 , waiting for merge to submit PR
[X] integration test for this cookbook's "sample templates", waiting for merge to submit PR

It would be nice to find out if the main configuration files (master-config.yml, scheduler.json, node-config.yaml) have changed between OSE v1.3.x and OSE v1.4.x , but for now the current set of configuration files seem to work.
Bugs/Gotchas with OSE 1.4.x so far:

the origin-node service spams the following line (times 2) every 10 seconds openshift/origin#11548:

Jan 28 09:28:30 master origin-node[28774]: I0128 09:28:30.715289   28774 conversion.go:133] failed to handle multiple devices for container. Skipping Filesystem stats

docker 1.12 seems unstable, containers that fail their "exec" liveness/readiness probe are redeployed as expected, however the pods stay stuck in Terminating state forever; as a workaround I forced node['cookbook-openshift3']['docker_version'] = '1.10.3-59.el7.centos' in my openshift-base role.

I believe that all changes in this PR are backward-compatible with version 1.3.x while supporting version 1.4.x when it is released to the official CentOS PaaS repository. My platform is already working with version 1.4.1 in the VM and all features seem to work.

I seem to encounter this issue often : https://github.com/kubernetes/kubernetes/issues/25456 ... containers fail their liveness/readiness then kubelet tries to recreate them, then the container stays in Terminating state forever. I don't know if it is due to docker 1.12 or to the new openshift release, will try to force docker version to 1.10.x

@IshentRas @ianmiell my PR should be usable now, can you review it, thank you!

Sorry I have been busy/stuck for the last few days. Reviewing now

Thank you for the merge, I'll submit more PRs at end of this week ;)

Thanks for the hard work guys @ianmiell  @jperville  :+1:
I am now working on bringing the new templates files in as well and I'll do a cut of this version as we have done a lot already :-)

Thanks Will. I wanted to discuss the possibility of us being able to do
releases independently of you - eg with a test framework we're all happy
with etc.. I'm fighting arguments to manage a downstream fork.
Also, a cut as soon as possible would be great, as we have a few releases
blocked waiting for a tag.
Let's talk soon.
On Wed, Feb 1, 2017 at 9:56 PM, William Burton<EMAIL_ADDRESS>wrote:

Thanks for the hard work guys @ianmiell https://github.com/ianmiell
@jperville https://github.com/jperville 👍
I am now working on bringing the new templates files in as well and I'll
do a cut of this version as we have done a lot already :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IshentRas/cookbook-openshift3/pull/60#issuecomment-276795627,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGrczRYu98X6HAjf3UPJdbacc8xLr98tks5rYP97gaJpZM4Lwe5P
.

--
My book on Docker in Practice: Get 39% off with the code 39miell
http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62

releasing it now

Sure, I think I have already given you the right to release.. Need to check if that is not working but it should.

Yes, but a) I don't know the process (my problem!), and b) I'm wary of
making a 'bad' release and giving you headaches. Let's catch up when we can.
On Thu, Feb 2, 2017 at 8:49 AM, William Burton<EMAIL_ADDRESS>wrote:

Sure, I think I have already given you the right to release.. Need to
check if that is not working but it should.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IshentRas/cookbook-openshift3/pull/60#issuecomment-276899980,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGrczfgqmvDIUh_9xytnwQpUfh4zF1JBks5rYZiLgaJpZM4Lwe5P
.

--
My book on Docker in Practice: Get 39% off with the code 39miell
http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62

Oh, if you mean tagging, I'm sure I have write access to the repo and can
do that.
The deployment to supermarket is what I don't think I can do (and we like
to have done to help our governance process push through). Unless that's
automated?
On Thu, Feb 2, 2017 at 8:53 AM, Ian Miell<EMAIL_ADDRESS>wrote:

Yes, but a) I don't know the process (my problem!), and b) I'm wary of
making a 'bad' release and giving you headaches. Let's catch up when we can.
On Thu, Feb 2, 2017 at 8:49 AM, William Burton<EMAIL_ADDRESS>wrote:

Sure, I think I have already given you the right to release.. Need to
check if that is not working but it should.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IshentRas/cookbook-openshift3/pull/60#issuecomment-276899980,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGrczfgqmvDIUh_9xytnwQpUfh4zF1JBks5rYZiLgaJpZM4Lwe5P
.

--
My book on Docker in Practice: Get 39% off with the code 39miell
http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62

--
My book on Docker in Practice: Get 39% off with the code 39miell
http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62

There are not such things :-)
We have been inspired by a failure culture :+1:


Timeline and Milestone

Hey Folks,
Do you have a timeline for this plugin? Can we set a milestone so we can keep track of it?

@jbosch-noaa will get a milestone in order with some targets based on functionality to be included

any update on moving from pre-release to release?

The stable release was issued a while ago
https://github.com/ioos/cc-plugin-ugrid/tree/v1.0.0
but we never got a PyPI release
https://pypi.org/project/cc-plugin-ugrid
@daltonkell or @Bobfrat do you have the PyPI credentials to make the release?

The Readme.md file states: Note this code is in a pre-release state. Check back soon for the first release

The v1.0.0 is note pre-release. The README should be updated.

I'll get with @daltonkell and @benjwadams and get it sorted.


V1 Timeseries Returns Values when no Office Present

A user reported they could get values using V1 without specifying the office.
Should we consider making Office required for the timeseries endpoint?

It won't hurt V1 and would fix the issue brought up below with V2.
curl --location 'https://cwms-data.usace.army.mil/cwms-data/timeseries?name=Troy-Cuivre.Stage.Inst.15Minutes.0.lrgsShef-rev&begin=2024-05-09T09%3A00-05%3A00'

Querying using V1 gives:
{
    "time-series": {
        brevity
        "time-series": [
            {
                "office": "MVS",
                brevity
                "regular-interval-values": {
                    "segments": [
                        {
                           brevity
                            "values": [
                                [
                                    8.25,
                                    0
                                ],
                                [
                                    8.24,
                                    0
                                ],
                                [
                                    8.24,
                                    0
                                ]
                            ]
                        }
                    ]
                }
            }
        ]
    }
}

Knowing that an office is required to find data using V2 (Are there docs to this? I/we know it from experience)
curl -X 'GET' \
  'https://cwms-data.usace.army.mil/cwms-data/timeseries?name=Troy-Cuivre.Stage.Inst.15Minutes.0.lrgsShef-rev' \
  -H 'accept: application/json;version=2'

gives
{
    "message": "Not found.",
    "incidentIdentifier": "-178818237359880300",
    "details": {}
}

Where it makes sense it would not be found, but it's not obvious to the end user that this is because the office is missing. (this happened)
curl -X 'GET' \
  'https://cwms-data.usace.army.mil/cwms-data/timeseries?name=Troy-Cuivre.Stage.Inst.15Minutes.0.lrgsShef-rev&office=MVS' \
  -H 'accept: application/json;version=2'

And then adding the office=MVS (in this case) fixes it (for the future reader with this problem)

We can mark parameters as required in the swagger annotations but that wouldn't work in this case b/c it is optional in V1.
There is already an issue to go thru the controllers and determine if all the parameters that are marked as required actually are required and to document when one is required in V2 but not in V1.   https://github.com/USACE/cwms-data-api/issues/562
There is a Controllers helper method for getting required parameters from the request context that should be used when a parameter is required.  When that method is used and the parameter isn't included then the user will get a sensible error message explaining which required parameter isn't provided.
Easily fixable on a case-by-case basis.  I envision #562 as a more systematic approach.

it is optional in V1
Suppose the choice is nice. At first I was just thinking adding it to the annotations and not actually enforcing it on the API itself.

Even just a note about it is helpful. Thank you for hopping on this! I know it has come up a few times, and again today. Thought to document it for new users being onboarded to the API.


Connection issue with Bullseye ?

Hi,
I seem to be having issues connecting to Pis running Bullseye, I get "Oops, could not establish a connection. Please check hostname and your network. "
I'm connecting with a pub key and passphrase, as a control; fresh install of Buster & Bullseye, just updates applied, same keys installed on both, both cards booted on the same PiZeroW. I am able to connect to both using my normal SSH client (Bitvise).
This is the debug log for a failed connection.
I am using an RSA key...
Any ideas ?
13:09:52.755 [main] WARN  d.e.r.activity.SettingsActivity - Enabling debug logging. Be warned that the log file can get huge because of this.
13:09:52.769 [main] DEBUG d.e.r.activity.helper.LoggingHelper - Logging was configured, debug logging enabled: true
13:10:00.592 [main] DEBUG d.e.rpicheck.activity.MainActivity - Load average preference: FIVE_MINUTES
13:10:00.594 [AsyncTask #1] INFO  d.e.rpicheck.ssh.impl.RaspiQuery - New RaspiQuery for host: <IP_ADDRESS>
13:10:00.596 [AsyncTask #1] INFO  d.e.rpicheck.ssh.impl.RaspiQuery - Connecting to host: <IP_ADDRESS> on port 1234.
13:10:00.624 [AsyncTask #1] INFO  d.e.rpicheck.ssh.impl.RaspiQuery - Using no host key verification.
13:10:00.624 [AsyncTask #1] INFO  d.e.rpicheck.ssh.impl.RaspiQuery - Using private/public key authentification with passphrase.
13:10:01.501 [reader] ERROR n.s.sshj.transport.TransportImpl - Dying because - {}
net.schmizz.sshj.transport.TransportException: Unable to reach a settlement: [diffie-hellman-group14-sha1, diffie-hellman-group1-sha1] and [curve25519-sha256<EMAIL_ADDRESS>ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, diffie-hellman-group-exchange-sha256, diffie-hellman-group16-sha512, diffie-hellman-group18-sha512, diffie-hellman-group14-sha256]
at net.schmizz.sshj.transport.Proposal.firstMatch(Proposal.java:145) ~[na:0.0]
at net.schmizz.sshj.transport.Proposal.negotiate(Proposal.java:127) ~[na:0.0]
at net.schmizz.sshj.transport.KeyExchanger.gotKexInit(KeyExchanger.java:219) ~[na:0.0]
at net.schmizz.sshj.transport.KeyExchanger.handle(KeyExchanger.java:344) ~[na:0.0]
at net.schmizz.sshj.transport.TransportImpl.handle(TransportImpl.java:484) ~[na:0.0]
at net.schmizz.sshj.transport.Decoder.decode(Decoder.java:107) ~[na:0.0]
at net.schmizz.sshj.transport.Decoder.received(Decoder.java:175) ~[na:0.0]
at net.schmizz.sshj.transport.Reader.run(Reader.java:61) ~[na:0.0]
13:10:01.504 [AsyncTask #1] ERROR net.schmizz.concurrent.Promise - <<kex done>> woke to: net.schmizz.sshj.transport.TransportException: Unable to reach a settlement: [diffie-hellman-group14-sha1, diffie-hellman-group1-sha1] and [curve25519-sha256<EMAIL_ADDRESS>ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, diffie-hellman-group-exchange-sha256, diffie-hellman-group16-sha512, diffie-hellman-group18-sha512, diffie-hellman-group14-sha256]
13:10:01.514 [AsyncTask #1] ERROR d.e.rpicheck.activity.SSHQueryTask - Could not establish a connection to host '<IP_ADDRESS>:1234'. Check your connection and settings.
de.eidottermihi.rpicheck.ssh.impl.RaspiQueryException: Could not establish a connection to host '<IP_ADDRESS>:1234'. Check your connection and settings.
at de.eidottermihi.rpicheck.ssh.impl.RaspiQuery.connectWithPubKeyAuthAndPassphrase(RaspiQuery.java:1140) ~[na:0.0]
at de.eidottermihi.rpicheck.activity.SSHQueryTask.doInBackground(SSHQueryTask.java:92) ~[na:0.0]
at de.eidottermihi.rpicheck.activity.SSHQueryTask.doInBackground(SSHQueryTask.java:46) ~[na:0.0]
at android.os.AsyncTask$3.call(AsyncTask.java:378) ~[na:0.0]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:0.0]
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:289) ~[na:0.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) ~[na:0.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) ~[na:0.0]
at java.lang.Thread.run(Thread.java:919) ~[na:0.0]
Caused by: net.schmizz.sshj.transport.TransportException: Unable to reach a settlement: [diffie-hellman-group14-sha1, diffie-hellman-group1-sha1] and [curve25519-sha256<EMAIL_ADDRESS>ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, diffie-hellman-group-exchange-sha256, diffie-hellman-group16-sha512, diffie-hellman-group18-sha512, diffie-hellman-group14-sha256]
at net.schmizz.sshj.transport.Proposal.firstMatch(Proposal.java:145) ~[na:0.0]
at net.schmizz.sshj.transport.Proposal.negotiate(Proposal.java:127) ~[na:0.0]
at net.schmizz.sshj.transport.KeyExchanger.gotKexInit(KeyExchanger.java:219) ~[na:0.0]
at net.schmizz.sshj.transport.KeyExchanger.handle(KeyExchanger.java:344) ~[na:0.0]
at net.schmizz.sshj.transport.TransportImpl.handle(TransportImpl.java:484) ~[na:0.0]
at net.schmizz.sshj.transport.Decoder.decode(Decoder.java:107) ~[na:0.0]
at net.schmizz.sshj.transport.Decoder.received(Decoder.java:175) ~[na:0.0]
at net.schmizz.sshj.transport.Reader.run(Reader.java:61) ~[na:0.0]
13:10:01.516 [AsyncTask #1] DEBUG d.e.rpicheck.activity.SSHQueryTask - Query time: 921 ms.
13:10:01.526 [main] DEBUG d.e.rpicheck.activity.MainActivity - Query caused exception. Showing dialog.
13:10:09.258 [main] DEBUG d.e.rpicheck.activity.MainActivity - Saving instance state (current device)
13:10:09.259 [main] DEBUG d.e.rpicheck.activity.MainActivity - Adding current device to all

Hi,
I think I have found the issue, in Debian 10  the KexAlgorithms diffie-hellman-group14-sha1 has been depreciated because of security concerns, it appears rpicheck only uses this and so connections fail on 10..
You can get around this by editing /etc/ssh/sshd_config  and adding KexAlgorithms diffie-hellman-group14-sha1  I cant recommend though because of the security concern.

Yes thats helps. Don't forget the "+" in order to add this method to the defaults instead of replacing all methods
KexAlgorithms +diffie-hellman-group14-sha1


Adding recipe for OpenSuse and infrastructure agent install

The only thing I might remove is the logs and flex recipes from the deploy configs:
"https://raw.githubusercontent.com/newrelic/open-install-library/main/recipes/newrelic/logs/logs.yml",
"https://raw.githubusercontent.com/newrelic/open-install-library/main/recipes/newrelic/flex/flex.yml"

My thinking is these recipes should get tested in separate deploy configs once they're more fully developed (the existing version of these recipes were more so contrived for demo purposes).

I could see several tests, some specific to the targeted recipes, and some others more integrated where we tests all the recipes that will be installed. I don't really want to maintain multiple set of definition files at this time given a linux distro and all that can be installed, and I don't want to lose the coverage to make sure all the pieces install correctly at this time either.
This will likely change overtime, I suspect as soon as we can just run the cli to install all the recipes that can be installed.
Would it be ok to proceed as-is for now and revisit later?

Yep, that makes sense 👍


Alternative Audio Storage Option

Is your feature request related to a problem? Please describe.
I would like to generate speech using text-to-speech API, then store the mp3 not locally on my machine, but on a server (or in a amazon bucket or firease storage bucket). The way the repo is currently structured, this seems not to be supported.
Describe the solution you'd like
Ideally an alternative return value in form of the blob audio should be provided (instead of writing to the filesystem).
Describe alternatives you've considered
Using elevenlabs API directly (which I'm doing currently).

Thanks for raising the issue @dcts
If you're using V1, you can change the response type like this
const voiceResponse = voice.textToSpeechStream({
    textInput:       "mozzy is cool",                // The text you wish to convert to speech
    responseType:    "arraybuffer",               // The streaming type (arraybuffer, stream, json)
  });

We're using Axios to make our requests which has limited support for Blob streaming however you can use ArrayBuffers instead.
You can also check the V2 docs to reference different variables you can pass.


FYPO:0004021	long polar microtubules

Comment from Meredith:
The definition of this term is not right
I suggest an update to FYPO to distinguish between mitotic interpolar microtubules and mitotic polar microtubules. The current term describing 'polar microtubules' - meaning microtubules that form the bipolar spindle - should be called 'interpolar microtubules.' The term 'polar microtubules' should be redefined to mean spindle microtubules that come from each pole but do not overlap in the middle.
(I never knew this)

"We use the term polar MTs for single or bundled nuclear MTs emanating from an SPB and the term interpolar MTs for the shaft of interdigitating polar MTs that
runs between the poles; in some studies, the latter have been called the central or core spindle. (Note that in anaphase, cytoplasmic as- tral MTs develop; these have not been measured in our study.) "

oh boy, here we go ...
At present, FYPO follows GO for the definition of "polar microtubule" (GO:0005827), and deviating would be Bad Ontology Practice™. So this ought to be updated in GO CC first and then I'll make FYPO consistent with it.
The GO:0005827 definition goes back a long time, and I suspect no one knew then that there were spindle MTs that aren't astral and neither connect to a kinetochore nor interdigitate with MTs from the opposite pole.
Furthermore, I would very strongly discourage GO from changing the meaning of "polar microtubule" from "ones that overlap" to "ones that explicitly don't overlap", and I really wish Meredith's lab hadn't done so. The current def is so long-established that GO cites a textbook for it, and the term has been used with that meaning extensively for a decade and a half.
Instead, in GO, "polar microtubule" could be broadened to be a parent of both overlapping and non-overlapping MTs that extend from a pole along the long axis of the spindle. They'll need a name for the non-overlapping MTs that Meredith calls "polar MTs" ... hope I can come up with something nicer than "non-overlapping polar microtubule" :P I like using "interpolar microtubule" for the MTs that overlap (old meaning of "polar MTs").
i.e. suggest to GO
polar microtubule GO:new1 (or GO:0005827?) - any MT that originates at one spindle pole and extends along the long axis of the spindle
- [i] interpolar microtubule - GO:0005827 (or GO:new1?) - any MT that originates at one spindle pole, extends along the long axis of the spindle, and overlaps at the spindle midzone with microtubules originating at the opposite pole
- [i] NEED NAME GO:new2 - any MT that originates at one spindle pole and extends along the long axis of the spindle, but does not overlap with microtubules originating at the opposite pole

and the name of GO:new2 should not be "polar microtubule"

Hmmph. Will e-mail Meredith for clarification tomorrow... Too tired now for this one ;)

did that paper look as complicated to you as it did to me?

Yes! Meredith did a brilliant job...she came to the curation session in Banff and then she was away.
I could not have done it  as this well myself without taking 2 days I'm sure! its very cool stuff though.


TS compat: enable default importing

This enables TypeScript developers that don't use esModuleInterop to consume this library when compiling for both the commonjs and es2015 module systems from the same source code.
In the current state, there are two options:
If I use
import * as escape from 'escape-string-regexp';
escape('foo');

it compiles fine in both cases, but throws an error like escape is not a function in the es2015 build at runtime. The commonjs build runs fine.
Now if I use
import escape from 'escape-string-regexp';
escape('foo');

instead, it throws a compile error, and if you ignore it, there's an error like escape_string_regexp_1.default is not a function at runtime in the commonjs build. The es2015 build runs fine.
The latter is the easier thing to fix, and it's what I fixed in this PR. In essence, I'm changing the "correct" way (for the TS compiler) from the former to the latter, and making it run in either module environment.
It's also a breaking change for TS users without esModuleInterop, though.

Huh. These tests now pass for me locally, but they still fail on Travis.

The TypeScript teams says we shouldn't do this. See: https://github.com/sindresorhus/mem/issues/31

That other issue was closed because it makes a point about this "just being for intellisense". Now, in a world of node being able to handle ESM without a transpiler as well (and TS producing ES modules as output too), this isn't true anymore. It is entirely impossible to use this package in a way that is compatible with both ESM and CJS output, if you have esModuleInterop off, without having two entirely separate code bases. As I showed, there is no syntax that works on runtime (!) with both output formats.


Corrects variable name so label color variants work.

Apologies... this PR should be rolled back. It was correct before. To get my label colors to work, I should have set $use-label-variation-colors to the colors I want to use, or $colors-variation-names if I want to use all of them.


SELinux v6.0.6 Recipe Compile Error in ../selinux/resources/boolean.rb  - uninitialized constant Chef::SELinux::Cookbook

:speaking_head: Foreword
Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.
:ghost: Brief Description
SELinux v6.0.6 Recipe Compile Error in ../selinux/resources/boolean.rb  - uninitialized constant Chef::SELinux::Cookbook
:pancakes: Cookbook version
selinux (6.0.6)
:woman_cook:  Chef-Infra Version
Version of chef-client in your environment.
chef_version=18.0.161
:tophat: Platform details
RHEL 9
Steps To Reproduce
Steps to reproduce the behavior:
chef-client
================================================================================
Recipe Compile Error in /var/chef/cache/cookbooks/selinux/resources/boolean.rb
NameError
uninitialized constant Chef::SELinux::Cookbook
Cookbook Trace: (most recent call first)
/var/chef/cache/cookbooks/selinux/resources/boolean.rb:40:in block in class_from_file'   /var/chef/cache/cookbooks/selinux/resources/boolean.rb:39:in class_from_file'
Relevant File Content:
/var/chef/cache/cookbooks/selinux/resources/boolean.rb:
33:            description: 'Set to true for value setting to survive reboot'
34:
35:  load_current_value do |new_resource|
36:    value shell_out!("getsebool #{new_resource.boolean}").stdout.split('-->').map(&:strip).last
37:  end
38:
39:  action_class do
40>>   include SELinux::Cookbook::StateHelpers
41:  end
42:
43:  action :set do
44:    if selinux_disabled?
45:      Chef::Log.warn("Unable to set SELinux boolean #{new_resource.name} as SELinux is disabled")
46:      return
47:    end
48:
49:    converge_if_changed do
System Info:
chef_version=18.0.161
platform=redhat
platform_version=9.0
ruby=ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux]
program_name=/usr/bin/chef-client
executable=/opt/chef/bin/chef-client
:police_car: Expected behavior
For it to Run a bought one.
:heavy_plus_sign: Additional context
Add any other context about the problem here. e.g. related issues or existing pull requests.

Can you verify if this is an issue with chef-client 17 as chef-client 18 introduces it's own native selinux resources and I'd suggest using them over the cookbook?

Hi,
The issue does not exist using CHEF v17 on RHEL9, we'll check out the new native resources though, thanks!

Closing since Chef-client 18 has resources built in and supersedes the need for this cookbook.


'Gentle introduction' is inaccessible

Go to this URL (or click the 'Gentle introduction' link on the homepage) and you get 404 Not Found:
https://www.lexonomy.eu/docs/intro/
Probably these lines in lexonomy.py is causing it by thinking that everything in the docs directory are static files:
# serve static files
@route('/<path:re:(widgets|furniture|libs|docs).*>')
def server_static(path):
    return static_file(path, root="./")

Not everything in the docs directory is a static file.

...how is this actually supposed to work (or how did it work)?
there exists a markdown file intro.md which links to, i think, all the 0x-0y.png files but not, for example,

lexonomy_httpd.con
mode-laic.png
text-editor-asklongstring.png
web.config
...
now, how is this markdown file supposed to become 'rendered'?
is this something we introduced when moving the 'wiki' from github into this repository (because obviously, a .md file in a wiki on github would get rendered)
do we need to 'render this'

offline (ideally automatically before/during git commit)?
online?

In the Node.js backend this is (or rather: was) handled in the following way.

There is (or rather: was) a line of code in lexonomy.js that says that static files can be found in the /docs directory (as well as a couple of other locations). If an HTTP request arrives asking for something in this directory, and if such a file exists there, then Node,.js serves this file. If not, then Node.js proceeds to number 2.

There is a GET handler in lexonomy.js (lines 220 - 226) which handles requests to URLs like /docs/blablabla/. The handler assumes that a file like docs/blablabla.md exists, opens it, converts it contents from Markdown to HTML, and serves it to the user through the template views/doc.ejs.

In the Node.js backend this is (or rather: was) handled in the following way.

There is (or rather: was) a line of code in lexonomy.js that says that static files can be found in the /docs directory (as well as a couple of other locations). If an HTTP request arrives asking for something in this directory, and if such a file exists there, then Node,.js serves this file. If not, then Node.js proceeds to number 2.

ok, likely around here (just for reference): 9eaa7c946f1573db9a120761ec2ba5ae196dc2c8

There is a GET handler in lexonomy.js (lines 220 - 226) which handles requests to URLs like /docs/blablabla/. The handler assumes that a file like docs/blablabla.md exists, opens it, converts it contents from Markdown to HTML, and serves it to the user through the template views/doc.ejs.

and this one, for reference, as well:
https://github.com/elexis-eu/lexonomy/blob/0e0d68b8dd106e7539617a9be8bd0419fc0f784e/website/lexonomy.js#L219-L226
So far, it seems, we have keept the EJS templating in place. Insofar, we could

(re)use the existing EJS templates
and use (something like) https://github.com/Python-Markdown/markdown to insert HTML (of the markdown) on the fly

(possible) alternative:

use bottle's templating engine (but this would probably only make sense if we wanted to move away more parts - and not only docs/)
other ideas...

@mjakubicek have you given this already a thought?

short term solution is just to forward requests to this path to NodeJS
long term is rewrite for the bottlepy templates like everything else (so far there is just one template in bottlepy - the consent.tpl)

Embarrassingly, it still isn't working:
https://www.lexonomy.eu/docs/intro/

ok, i see - but this time it's a 'deployment' issue: 'someone' needs to update https://www.lexonomy.eu because https://lexonomy.elex.is works.
(i think, we can stuff it into this issue for the time being - generally, i'd consider it a different issue...)

This is already fixed in beta

Today https://www.lexonomy.eu/docs/intro/ is still not working.

Thanks for information, somehow we drop intro in the new interface. It is back in now


Enable additional styles for vector layers

We would like to add category feature styles to vector layers to style for example retail places type and pitch score areas.

categorized and graduated themes are now enabled for MVT layers.


Notebook JSON is invalid: 'execution_count' is a required property

[E 20:56:09.963 NotebookApp] Notebook JSON is invalid: 'execution_count' is a required property
Failed validating 'required' in code_cell:

On instance['cells'][3]:
{'cell_type': 'code',
 'id': 'b3bb4f042e4b3050',
 'metadata': {'collapsed': False},
 'outputs': ['...0 outputs...'],
 'source': 'from agency_swarm import set_openai_key\n'
           'set_openai_key("YOUR_OPE...'}

Getting this error when I open the notebook for the first time.

@OrwellianOwl seems like PyCharm is messing with Jupyter. Can you pull and try again? Reopen if the problem persists.


Set priority class for kube-scheduler and cluster-autoscaler

How to categorize this PR?

/area control-plane
/kind bug
What this PR does / why we need it:
See https://github.com/gardener/gardener/issues/5634#issuecomment-1279953592
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/5634
Release note:

`kube-scheduler` and `cluster-autoscaler` Pods now run with the appropriate priority set according to the following [document](https://github.com/gardener/gardener/blob/v1.57.1/docs/development/priority-classes.md). Previously these Pods were running without a priority class set and were preempted in favour of less important Pods.

/lgtm
/approve
/retest


Add sunshine

Adds support for sunshine, an nVidia gamestream host.

The format of package definitions has changed. Please read 01-main/CONTRIBUTING and EXTREPO, update your implementation and submit a new PR.


Electron fetcher not available

Description:
The Copilot output shows the message "Using Helix fetcher, Electron fetcher is not available" repeatedly. This prevents Copilot from utilizing Electron fetcher for data fetching tasks.
Expected Behavior:
Copilot should have access to the Electron fetcher functionality as expected.
Steps to Reproduce:

Using WSL plugin connect to wsl2.
Use Copilot to perform tasks that involve data fetching.

Additional Information:

Output:
2024-05-08 15:27:22.587 [info] [fetcher] Using Helix fetcher, Electron fetcher is not available.
2024-05-08 15:27:24.641 [info] [fetcher] Using Helix fetcher, Electron fetcher is not available.
2024-05-08 15:27:24.641 [info] [code-referencing] Public code references are enabled.
2024-05-08 15:27:24.642 [info] [auth] Successfully authenticated

Environment: Using VS Code with Copilot, possibly on Windows Subsystem for Linux (WSL).
-## Copilot

Version: 1.187.0

Build: prod

Editor: vscode/1.89.0

Environment

http_proxy: http://<IP_ADDRESS>:7890
https_proxy: http://<IP_ADDRESS>:7890
no_proxy: <IP_ADDRESS>,login.microsoftonline.com,192.168.,172.31.,172.30.,172.29.,172.28.,172.27.,172.26.,172.25.,172.24.,172.23.,172.22.,172.21.,172.20.,172.19.,172.18.,172.17.,172.16.,10.,127.*,localhost,
SSL_CERT_FILE: n/a
SSL_CERT_DIR: n/a
OPENSSL_CONF: n/a

Feature Flags

Send Restricted Telemetry: enabled
Chat: enabled

Node setup

Number of root certificates: 141
Operating system: Linux
Operating system version: <IP_ADDRESS>-microsoft-standard-WSL2
Operating system architecture: x64
NODE_OPTIONS: n/a
NODE_EXTRA_CA_CERTS: n/a
NODE_TLS_REJECT_UNAUTHORIZED: n/a
tls default min version: TLSv1.2
tls default max version: TLSv1.3

Network Configuration

Proxy host: <IP_ADDRESS>
Proxy port: 7890
Kerberos SPN: n/a
Reject unauthorized: enabled
Fetcher: HelixFetcher

Reachability

github.com: HTTP 200 -
copilot-proxy.githubusercontent.com: HTTP 200 -
api.githubcopilot.com: HTTP 200 -
default.exp-tas.com: HTTP 200 -

VS Code Configuration

HTTP proxy:
HTTP proxy authentication: n/a
Proxy Strict SSL: true
Extension HTTP proxy support: override

Extensions

Is win-ca installed?: false
Is mac-ca installed?: false

Authentication

GitHub username: aqlkzf

@aqlkzf can you confirm the issue you are seeing. Is this just about presence of the logs or some bug this causes with using Copilot?

Same here. Copilot does not recommend code complete.
2024-05-09 23:39:52.614 [info] [fetcher] Using Helix fetcher, Electron fetcher is not available.
2024-05-09 23:39:52.614 [info] [code-referencing] Public code references are enabled.
2024-05-09 23:39:52.615 [info] [auth] Sucessfully authenticated

Possibly related: https://github.com/orgs/community/discussions/123220
For me it is no longer working at all, crashing on startup with this error inside of electronFetcher.ts:
2024-05-10 06:19:24.171 [error] Activating extension GitHub.copilot failed due to an error:
2024-05-10 06:19:24.171 [error] TypeError: Invalid version. Must be a string. Got type "undefined".
    at new SemVer (/home/david/.vscode-server/extensions/github.copilot-1.188.867/node_modules/semver/classes/semver.js:19:13)
    at compare (/home/david/.vscode-server/extensions/github.copilot-1.188.867/node_modules/semver/functions/compare.js:3:3)
    at lt (/home/david/.vscode-server/extensions/github.copilot-1.188.867/node_modules/semver/functions/lt.js:2:29)
    at Function.create (/home/david/.vscode-server/extensions/github.copilot-1.188.867/extension/src/electronFetcher.ts:15:13)
    at createExtensionContext (/home/david/.vscode-server/extensions/github.copilot-1.188.867/extension/src/extension.ts:222:38)
    at activate (/home/david/.vscode-server/extensions/github.copilot-1.188.867/extension/src/extension.ts:98:23)
    at Function.kb (/home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:161:13465)
    at Function.jb (/home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:161:13175)
    at /home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:161:11197
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at h.n (/home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:145:6281)
    at h.m (/home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:145:6244)
    at h.l (/home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:145:5701)

Possibly related: https://github.com/orgs/community/discussions/123220
For me it is no longer working at all, crashing on startup with this error inside of electronFetcher.ts:
2024-05-10 06:19:24.171 [error] Activating extension GitHub.copilot failed due to an error:
2024-05-10 06:19:24.171 [error] TypeError: Invalid version. Must be a string. Got type "undefined".
    at new SemVer (/home/david/.vscode-server/extensions/github.copilot-1.188.867/node_modules/semver/classes/semver.js:19:13)
    at compare (/home/david/.vscode-server/extensions/github.copilot-1.188.867/node_modules/semver/functions/compare.js:3:3)
    at lt (/home/david/.vscode-server/extensions/github.copilot-1.188.867/node_modules/semver/functions/lt.js:2:29)
    at Function.create (/home/david/.vscode-server/extensions/github.copilot-1.188.867/extension/src/electronFetcher.ts:15:13)
    at createExtensionContext (/home/david/.vscode-server/extensions/github.copilot-1.188.867/extension/src/extension.ts:222:38)
    at activate (/home/david/.vscode-server/extensions/github.copilot-1.188.867/extension/src/extension.ts:98:23)
    at Function.kb (/home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:161:13465)
    at Function.jb (/home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:161:13175)
    at /home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:161:11197
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at h.n (/home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:145:6281)
    at h.m (/home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:145:6244)
    at h.l (/home/david/.vscode-server/bin/b58957e67ee1e712cebf466b995adf4c5307b2bd/out/vs/workbench/api/node/extensionHostProcess.js:145:5701)

EDIT: I found the following workaround:

Open the file ~/.vscode-server/extensions/github.copilot-1.188.867/dist/extension.js and search for create(t,a=process.versions){if(!(0,Ipe.lt)(a.electron,"28.2.5"))
Insert ??'0.0.0' after a.electron so it looks like this now: create(t,a=process.versions){if(!(0,Ipe.lt)(a.electron??'0.0.0',"28.2.5"))
Save and restart VS Code

not work

This is as designed.
Under remote scenarios, like WSL, the remote extension host is executing in a pure nodejs runtime. In such environments (the remote extension host), Electron itself and the Chromium's network stack are not available, so the Electron Fetcher cannot be used. So it is completely expected that in such scenarios the Helix Fetcher is used.
Are you observing any other network related issues besides the log statement?

I'm getting the same error as @CherryDT, though Copilot doesn't work only while I'm in a devcontainer. Outside it works just fine.

This is as designed.
Under remote scenarios, like WSL, the remote extension host is executing in a pure nodejs runtime. In such environments (the remote extension host), Electron itself and the Chromium's network stack are not available, so the Electron Fetcher cannot be used. So it is completely expected that in such scenarios the Helix Fetcher is used.
Are you observing any other network related issues besides the log statement?

Thanks for your attention.
Sometimes copilot can work but is really slow, it takes a long time for copilot to collect information and send requests (Not the Internet connection issue). If I do not use copilot in wsl, just use it in my Windows system, It's much faster for complementation.


Added updated for prevent_destroy to true

changed the value to prevent the S3 ACM bucket from being deleted.
prevent_destroy = true

not required


Feature/dpcs subtable

Looks like it's working, though there should be more testing and debugging.